| Wizzup | uvos__: check @ mbm.bin | 00:14 |
|---|---|---|
| Wizzup | glad it didn't brick | 00:14 |
| tmlind | uvos__: good to hear the flakey wlan d4 is back alive :) and nice try on the xoom2 allow-mbmloader-flashing-mbm.bin :) | 06:43 |
| uvos | tmlind: Wizzup: so either the mbm flash was not harmless or this tablet has the wierdedst fault ever.... | 08:38 |
| uvos | tmlind: Wizzup: It has honeycomb installed. I was playing around with the preinstalled games and noticed most just force close and dont run, also the device isent clean theres a google account registerd and there are some pictures on it, so i went into recovery to reset it and that seamd to work... but once it rebooted it was still the same. wierd maybe the recovery is broken. So i did the mbm flashing thing and it seamed to | 08:47 |
| uvos | work fine, when i was done i restored the mbm it started with (the one from 1.6.0) and that went fine too. Then i decided to upgrade it to VRZ_9.8.2OT (android 4.1) to have the latest kernel for kexecboot. i could not do it from android recovery because it just errors out with "no sdcard inserted" great but whatever. so i whent and flashed everything via fastboot boot system preinstall and so on and fasboot responds with OK | 08:47 |
| uvos | every time an it looks like its working. | 08:47 |
| uvos | so i reboot aaand.... is honycomb again. wtf? i try again. same thing. i try flashing VZ_7.7.1 (android 4.0), nothing changes. i try flashing just an empty logo.bin. that works but the logo dosent change. So i boot honycomb again and make a terrible discovery, the entire devce is read only, like i can take a picture with the camera and it will do its thing but the picture never appears. i can change device settings only for them | 08:51 |
| uvos | to dissapear as soon as i navigate away. | 08:51 |
| uvos | i cant say for sure that the mbm thing dident cause this, but the failure to factory suggests it did not. i think the flash chip in the deivce has entered some kind of safe mode due to a high error rate or something. I also think i dident truly test the xoom2 mbm bin since flashing mbm also has no effect its version never changes, sadly i wasent paying attention to this when doing the above. | 08:54 |
| uvos | *failure to factory resett | 08:54 |
| uvos | this might also explain why all the screws on the back are missing | 08:55 |
| uvos | someone wanted to open this one up for repair maybe? | 08:55 |
| uvos | im kind of impressed android manages to run perfectly fine with absolutly everything being read only | 08:58 |
| uvos | ok i think i never changed mbm | 09:01 |
| uvos | its version 0A.6C | 09:02 |
| uvos | and mbm.bin vom VRZ_MZ609_1.6.0_279_CFC_1FF (ie honycomb) has this in the header | 09:02 |
| uvos | and mbm bin VRZ_9.8.2OT_127_MZ609_CFC_1FF.xml and xoom2 allow-mbmloader-flashing-mbm.bin dose not. | 09:03 |
| uvos | ok imanaged to get adb shell, i works if you dont navigate away form settings :P | 09:10 |
| uvos | dmesg is full of [ 42.663024] mmcblk1: card err 0x80900 | 09:10 |
| uvos | ok so thats it | 09:10 |
| uvos | flash chip on this one is dead :( | 09:10 |
| Wizzup | uvos: argh | 10:49 |
| uvos | Wizzup: really wierd that it failed like that :| but i have seen sdcards do the same thing. | 10:51 |
| Wizzup | uvos: yeah, where they accept all writes but just drop them | 10:51 |
| Wizzup | it is emmc thought right? | 10:52 |
| uvos | yeah | 10:52 |
| Wizzup | well, i have the other two here with me, was planning to give one to parazyd | 10:52 |
| uvos | ok | 10:52 |
| Wizzup | let me see if I can find another one online somehow | 10:52 |
| uvos | do you want me to send it back? so that you have one for spares? | 10:52 |
| uvos | battery/display etc | 10:53 |
| Wizzup | don't think it's that useful rn, but if you want to get rid of it, then sure | 10:54 |
| uvos | ok | 10:54 |
| Wizzup | (also I won't be home for a while so don't send it to that addr :-)) | 10:54 |
| uvos | ok | 10:54 |
| uvos | ill keep it around for now | 10:54 |
| Wizzup | I guess emmc is typically bga so not easy to replace either | 10:54 |
| uvos | yes | 10:55 |
| uvos | not worth trying imo | 10:55 |
| Wizzup | agreed | 10:55 |
| uvos | also you would have to get mbm on there somehow | 10:55 |
| Wizzup | there seem to be a bunch available online, but more expensive than what I paid for these | 10:55 |
| Wizzup | mhm | 10:55 |
| parazyd | Wizzup: Feel free to give the one for me to uvos | 10:55 |
| parazyd | Maybe worth testing it before too | 10:56 |
| uvos | side note | 10:57 |
| uvos | why are we buying xyboards instead of xoom 2? | 10:57 |
| uvos | afaik its the same device except no verizon branding | 10:57 |
| uvos | and was sold in eu | 10:58 |
| Wizzup | uvos: got a model number/link? | 11:00 |
| Wizzup | I searched before and didn't really find that much | 11:01 |
| uvos | MZ607 | 11:01 |
| uvos | and yeah german ebay has none | 11:01 |
| uvos | there are some MZ616 but at absurd prices | 11:01 |
| uvos | thats the equivalent to the us 10 inch xyboard | 11:01 |
| Wizzup | well, let me check the ones I have first, hope that they work | 11:05 |
| Wizzup | uvos: I might have some time today to check, do you have some instructions for me? (It will take 2-3 hours before I am in a position to do anything) | 11:17 |
| Wizzup | I can also ping you when I'm ready | 11:17 |
| uvos | what do you want to try? | 11:19 |
| uvos | i mean you can test the particular fault mine has by taking a picture and seeing if it saves it | 11:19 |
| uvos | by enabling debug mode (settings->applications->debuging->usb debug) and entering adb shell from pc (with usb connnected to device) and checking dmesg for errors | 11:20 |
| Wizzup | uvos: end goal being enabling leste with clownboot or similar | 11:21 |
| uvos | no need for clown boot | 11:23 |
| uvos | you can either check the mbm i linked some time ago | 11:23 |
| uvos | and try and see if it allows flashing to utags | 11:23 |
| uvos | if thats to risky for you, you have to upgrade the device to android 4 and then dd over the utags and kexecboot to the respective partitons | 11:24 |
| uvos | but this is also risky because if it goes wrong you have no way of clearing utags | 11:24 |
| uvos | (you have to root the device first for this to work too) | 11:25 |
| uvos | also you have to build utags and kexecboot yourself | 11:25 |
| uvos | because rn we have no images | 11:25 |
| uvos | but tmlind allread has the needed changes on the repos | 11:25 |
| Wizzup | well, sounds like ew need to start with extracting some information | 11:28 |
| parazyd | Wiki will be down for a bit | 11:29 |
| parazyd | About to start upgrading | 11:29 |
| Wizzup | ty | 11:29 |
| parazyd | Scary update process tbh | 11:39 |
| parazyd | Luckily we use sqlite so a backup is just cp -ra | 11:39 |
| parazyd | (I hope) | 11:39 |
| Wizzup | uvos: also the procedure will help me with the droid3 that I brought | 11:41 |
| parazyd | https://leste.maemo.org/Special:Version | 11:42 |
| parazyd | Looks ok? Except the logo is gone | 11:42 |
| parazyd | dreamer: ^ | 11:42 |
| parazyd | ok logo was in a different dir. Now there. | 11:43 |
| parazyd | Editing works | 11:44 |
| uvos | Wizzup: not really the d3 dosent/cant use utagboot so procedure is totaly different | 11:44 |
| Wizzup | uvos: ok, my intentions remain the same, but understood | 11:45 |
| Wizzup | I general I hardly know much about android | 11:45 |
| uvos | d3 has kinda a problem | 11:46 |
| uvos | in that for clown boot you need a mainline kernel that works | 11:46 |
| uvos | but to make/debug a mainline kernel you need clown boot | 11:46 |
| Wizzup | oh like a chicken-egg problem | 11:46 |
| Wizzup | mhm | 11:46 |
| uvos | the bonic avoided this by booting the d4 kernel and mostly working like that (minus sensors and buttons) | 11:47 |
| uvos | so you have to boot mainline via safestrap at first | 11:47 |
| uvos | like leste did way back | 11:47 |
| dreamer | parazyd: nice! | 12:13 |
| dreamer | looks fine yeah | 12:13 |
| dreamer | will try to poke at Cargo docs some more | 12:13 |
| parazyd | Awesome | 12:13 |
| uvos | http://uvos.xyz/xyboard | 12:15 |
| uvos | xyboard is of nice construction 0 adhesive and everything is screwed into a thick cast magenisum midframe | 12:17 |
| parazyd | Good times | 12:23 |
| mighty17[m] | uvos: maemo isnt booting | 16:43 |
| * mighty17[m] uploaded an image: (849KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/dfcXMrhgVKrtiPNOBreVVfFj/image.png > | 16:43 | |
| mighty17[m] | do i need to change something in the boot partition? | 16:43 |
| mighty17[m] | or did i build the kernel wrong? (i used envkernel to build it) | 16:45 |
| uvos | what is mmcblk0? | 17:04 |
| uvos | emmc? sdcard? | 17:04 |
| uvos | thats a kernel bug btw | 17:04 |
| uvos | since its spamming false hotplug messages | 17:05 |
| uvos | mighty17[m]: ^^^ | 17:05 |
| mighty17[m] | <uvos "what is mmcblk0?"> sdcard, the only thing for d4 was .img.xz | 17:05 |
| mighty17[m] | i followed getting started of maemo | 17:06 |
| uvos | right but that dosent mean that mmcblk0 is sdcard on your device | 17:06 |
| uvos | if it is | 17:06 |
| uvos | thats fine | 17:07 |
| mighty17[m] | it is but it still shows pmOS initramfs somehow | 17:07 |
| mighty17[m] | how do u build kernel for maemi | 17:07 |
| mighty17[m] | maemo* | 17:07 |
| uvos | for d4? just like a pc | 17:07 |
| uvos | you get the kernel from kernel.org and build it | 17:07 |
| uvos | yeah the initramfs needs to be gone | 17:08 |
| uvos | wo dont use a initramfs | 17:08 |
| uvos | just root=/dev/whatever in cmdline for root | 17:08 |
| mighty17[m] | <uvos "just root=/dev/whatever in cmdli"> ohkay | 17:35 |
| mighty17[m] | <uvos "you get the kernel from kernel.o"> just make right? | 17:35 |
| mighty17[m] | and to put it in boot.img? | 17:35 |
| buZz | mighty17[m]: those reply methods arent really useful ;) | 17:35 |
| buZz | and quite spammy | 17:36 |
| buZz | beside the advertizing you do for matrix.org at every line ;) | 17:36 |
| mighty17[m] | oh damn :( | 17:36 |
| mighty17[m] | sorry | 17:36 |
| buZz | np, just saying | 17:36 |
| uvos | i think the reply feature its fine | 17:37 |
| uvos | but use it a bit less | 17:37 |
| uvos | anyhow | 17:37 |
| buZz | right, it just feels like 'i'm using it cause its a option' and not really motivated for aiding conversation | 17:37 |
| uvos | yeah just use it when its needed to differentiate what you are replying to | 17:38 |
| uvos | anyhow again | 17:38 |
| mighty17[m] | oh well im more used to matrix, i'll try to use it less | 17:38 |
| mighty17[m] | anyways back to boot.img | 17:38 |
| uvos | mighty17[m]: you need a arm-linux-gnueabihf- toolchain | 17:38 |
| uvos | your distro very likely provides this | 17:38 |
| mighty17[m] | yup | 17:38 |
| uvos | and then its "make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- omap2plus_defconfig modules omap4-droid4-xt894.dtb zImage -j16" | 17:38 |
| mighty17[m] | export ARCH=arm and CROSS_COMPILE | 17:39 |
| uvos | replace the dtb with yours ofc | 17:39 |
| mighty17[m] | oh so just the zImage nice | 17:39 |
| uvos | no | 17:39 |
| uvos | so then you have the linux image | 17:39 |
| uvos | you need to package this into boot.img | 17:39 |
| uvos | this you do with mkbootimg | 17:39 |
| uvos | which is something that is part of asop | 17:39 |
| mighty17[m] | yup correct, even pmOS does it like this | 17:40 |
| uvos | right | 17:40 |
| uvos | but dont supply a initramfs | 17:40 |
| mighty17[m] | but pmOS has its own downstream boot.img, here what am i supposed to use | 17:40 |
| uvos | your own | 17:40 |
| uvos | build your own | 17:40 |
| mighty17[m] | i dont understand | 17:41 |
| uvos | with no initramfs and CONFIG_FORCE_CMDLINE (or so sorry dont know the exact name) | 17:41 |
| uvos | set to something like this CMDLINE=console=tty0 debug earlycon ro rootwait rootfstype=ext4 root=/dev/mmcblk0p2 | 17:41 |
| uvos | ofc replace the partition with where you have the rootfs | 17:41 |
| uvos | and add the modules to the rootfs with "make ARCH=arm modules_install INSTALL_MOD_PATH=" | 17:42 |
| uvos | by mounting it on pc | 17:42 |
| uvos | and idk how your bootloader supplies the dts | 17:43 |
| uvos | that varies wildly | 17:43 |
| mighty17[m] | yes cmdline is fine for now, using my defconfig | 17:43 |
| uvos | some android phones have a seperate partion that you just dd the dtb to | 17:43 |
| uvos | others have it appended to boot | 17:43 |
| mighty17[m] | nope this is a normal device which appends to boot | 17:44 |
| uvos | yeah so if you did all that | 17:44 |
| uvos | then it should work | 17:44 |
| mighty17[m] | https://wiki.postmarketos.org/wiki/Mainlining_Guide#non-QCDT_devices basically this works | 17:44 |
| uvos | maybe also go into the rootfs and rm /etc/fstab | 17:44 |
| uvos | but it should work with it too if your sdcard is mmcblk0 | 17:44 |
| mighty17[m] | i still dont get, this wont generate a boot.img | 17:45 |
| uvos | ? | 17:46 |
| uvos | compile the kernel from the tree | 17:46 |
| uvos | use mkbootimg to generate the image from the files that makes | 17:46 |
| uvos | and then append the dts | 17:46 |
| uvos | idk what the hangup is | 17:46 |
| mighty17[m] | oh right yes yes | 17:47 |
| uvos | after appening the dts install the modules to rootfs | 17:47 |
| uvos | and then it should work | 17:47 |
| mighty17[m] | ohk, thanks a lot!! | 17:47 |
| parazyd | Hey all, unrelated to Leste, but would you consider voting for "streamflow-finance" here https://sola.na/season-vote ? It won't take a minute (no captcha or some bs), and it might win me a small grant. | 19:37 |
| parazyd | Thanks for considering :) | 19:37 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
