Help Unbricking PE

[vicinc]

In dingo update.zip there is a folder boot with ntim.bin.crc, u-boot.bin.crc and zImage.crc. they seem to be the boot files and some image? is anyway I can restore the boot partition under adb using any of those. I am getting so desperate that I am at the point of throwing away this device. Spent more than what I paid for it in my time and others time. I will never buy again a device that does not have proper recovery. I am so happy with my Adam and Alex from this point of view. For Adam owners, check the adam post, I did put some update firmware and safe root instructions.

[vicinc]

Kenny or mr Ed. I want to see if my boot is borked compared with a standard ermine.
if you do
adb shell cat /proc/mtd
are you getting as bellow?

c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00080000 "BBM_reserve1"
mtd1: 00100000 00080000 "bootloader-alt"
mtd2: 00100000 00080000 "environment-alt"
mtd3: 00300000 00080000 "kernel-alt"
mtd4: 00300000 00080000 "kernelrecovery-alt"
mtd5: 02e00000 00080000 "maintenance"
mtd6: f5c00000 00080000 "Android"
mtd7: 06400000 00080000 "MRVL_BBM"
mtd8: 00040000 00010000 "bootloader"
mtd9: 00080000 00010000 "bootcode"
mtd10: 00040000 00010000 "environment"
mtd11: 00300000 00010000 "kernel"
mtd12: 00400000 00010000 "kernelrecovery"

[vicinc]

not sure where u-bin is mtd1 or mtd8

[vicinc]

also following another post https://www.mobileread.com/forums/arc.../t-137454.html (Robot who knows what is he talking about) looks like in intstorage is vfat.img and image of the internal sdcard that could be copied and restore to my machine?

[yugami]

thats on the update.zip and just covers the basic internal storage. do you have a .esi in your internal storage (or SDCard if you chose to move the library there)? Pretty much all of the edge eink apps use the library dir structure.

[yugami]

that ls is just of /lib/ need to see /lib/modules that's where the hardware drivers live.

honestly you should just pull them off the update.zip and push them onto your edge from adb and reboot and see what happens.

If you have corrupt files any of these having an issue would kill a lot of functionality. Theres only a small handful of files in there but they driver the eink and some other functionality.

[vicinc]

how is called? I do have an Esi and the files appear complete. I do not understand how is wrong. I am thinking in writing all the mtd with what is in update.zip if I can identify or with something one can extract from their rom. if this fails goes in the bin.

[vicinc]

you are talking of the system/lib ? if I do su, and mount as read write would I be able to overwrite considering they may be running?

[yugami]

cd /lib/modules
# ls
ls
QCSerial2kEntourage.ko
syscopyarea.ko
sd8688.ko
sysfillrect.ko
QCQMI.ko
QCUSBNet2kEntourage.ko
QCQMI-2.6.29.ko
mcypt.ko
ep3522fb.ko
gspca_main.ko
scsi_wait_scan.ko
bt8688.ko
galcore.ko
fb_sys_fops.ko
bmm.ko
udlfb.ko
sysimgblt.ko

[mr_ed]

Originally Posted by vicinc

if you do
adb shell cat /proc/mtd
are you getting as bellow?

Yes, with these three differences (but mine is dingo 1.13)

mtd0: 00a00000 00080000 "BBM_reserve1"
mtd1: 00080000 00080000 "bootloader-alt" ... vs. your 00100000
mtd2: 00080000 00080000 "environment-alt" ... vs. your 00100000
mtd3: 00300000 00080000 "kernel-alt"
mtd4: 00400000 00080000 "kernelrecovery-alt" ... vs. your 00300000
mtd5: 02e00000 00080000 "maintenance"
mtd6: f5c00000 00080000 "Android"
mtd7: 06400000 00080000 "MRVL_BBM"
mtd8: 00040000 00010000 "bootloader"
mtd9: 00080000 00010000 "bootcode"
mtd10: 00040000 00010000 "environment"
mtd11: 00300000 00010000 "kernel"
mtd12: 00400000 00010000 "kernelrecovery"

Have you seen this Android wiki? Look at the page, "HOWTO: Unpack, Edit, and Re-Pack Boot Images" - you wouldn't have to actually unpack and alter the image, you could maybe just take a good one from somebody and skip to the section, "Flashing your new image back onto the phone."

-- Ed

[vicinc]

mr edd. I was thinking on that frame of mind. need the boot images from some working ermine. write them over adb and I may get menu/rotate working again. But I do not have any clue from where to take them. somebody could do for me # cat /dev/mtd/mtd1 > /sdcard/mtd1.img , # cat /dev/mtd/mtd2 > /sdcard/mtd2.img, etc. one of the images is 2.5 gb, I think I can skip that one for the time being, if I could just get the boot working to downgrade to dingo and restart again.

[vicinc]

yugami> c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
# cd /lib/modules
cd /lib/modules
# ls
ls
QCSerial2kEntourage.ko
syscopyarea.ko
sd8688.ko
sysfillrect.ko
QCQMI.ko
QCUSBNet2kEntourage.ko
QCQMI-2.6.29.ko
mcypt.ko
ep3522fb.ko
gspca_main.ko
scsi_wait_scan.ko
bt8688.ko
galcore.ko
fb_sys_fops.ko
bmm.ko
udlfb.ko
sysimgblt.ko
#

[vicinc]

I just did a adb push lib /system/lib where lib was from emine update like my device. and now the device is not starting at all. got stucked at 3 dots on boot.
adb still working. so my only hope now is to restore the mdt partition, at least the boot and safe boot ones. any help will be appreciated. adb still works fortunately

[vicinc]

hmm, repaired permission from shell and is booting up again on lcd side. however still nothing on eink side apps. still believe if i can write the boot partition I may get a restore to dingo. please help.

[vicinc]

yaffs expert from market is able to create an img recovery of the android as well as writing a parting from under android.