![]() Scrub\aml_autoscript - for scrubbing the nand flash (amlogic 8726mx) Use these scripts at your own risk - and remember to remove after using!Įrase\aml_autoscript - for erasing the nand flash (amlogic 8726mx) #brick #unbricking #amlogic #8726mx #sdcard #aml_autoscript I'll do some tests if there is another way, and if it slows the procedure down.Įdit2: dumper now updated and rereleashed. So, dumping works but some extracting is needed for restoring. Also if one dumps system with dd, that bad block Every one of these amlogic devices seem to have it, so System and boot (recovery) are at least needed.Įdit: dumper offline, as it has some problem dumping system partition because ![]() Then leave sd card otherwise empty and it will boot into usb burning mode. If not, maybe you can make a bootable sd card usingĪ bootloader taken from another batch firmware. Your could try my new USB Dumper package if it can save something from it.īootloader must be ok. Voila! uboot tries to load OS fron internal flash, fails, and after a while tried to load recovery from MicroSD! Just select firmware on SD card, and flash it!Ĭlick to expand.Shaunmt (freaktab, here too) has done a lot of stuff for these but what I searched, Place on it TWRP (from SMT_TWRP_Next7HD8G-NXM7000NBD_WMN.zip) and native firmware update pack. It's bad, but you already have live native (!!) boot loader on internal flash, and it can boot something useful!ħ. So firmware pieces are placed in wrong places. But if you are unlucky (like I), you'll have MTD map mismatching between native uboot/kernel and kernel from USB recovery uImage. zip as update.zip and run that script:Īdditional ROM erase (steps 4,5) added to force erasing default environment created by this uboot.Ħ. If all is OK - it'll appear as USB device again.ĥ. Place usb_spl.bin, u-boot-orig.bin and uImage_recovery into folder with scripts, and run erase flash (config_progress_erase.xml)Ĥ. Install drivers from USB burning tool, connect to deviceģ. Power off the device (ensure that CPU is cold), short-circuit two pins on flash like in first post, and connect device to PC. We have a device with trash in ROM, that tries to load and hangs.ġ. And serial console helps me too much to investigate what happens. Main trouble was that uImage_recovery had different mtdblock map. and archive with USB recovery software for some Amlogic MX TV box (with usb_spl.bin, u-boot-orig.bin, uImage_recovery that supports flashing via USB, and script). I found firmware update pack Next7HD8G_SMT_Stock_Rom_081213-signed.zip, modified recovery SMT_TWRP_Next7HD8G-NXM7000NBD_WMN.zip, USB Burning Tool 1. ![]() Nothing of mentioned methods helps me to unbrick it. I have an experience of unbricking of Nextbook NX007HD8G (it was flashed with something wrong, and even not booted). : failed because no connected device ,current step is 18Ĭould anyone please help me ? It would be highly appreciative.and thanks to everyone who contributed to this s highly informational. ![]() : Transfer Complete! total size is 4002649 Bytes : load command: setenv recovery_command -usb_burning After a combination of files (u-boot/usb_spl) i manage to load including the original Odys u-boot.bin (from firmware v1.05) but on boot executing command, the tablet is disconecting and the usb burning tool start scannig for tablet restart? This is the way aml burning tool is working (loading boot, starting boot, disconect and reconnect the tablet or do i miss something in burning script. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |