I have a mytouch 3g and it no longer boots into recovery. All I get it the first line:
Build : RA-saphire-v1.7.0G and nothing else.
The phone is still accessable via adb in recovery.
I have flashed recovery.img serveral times using fastboot but to know avail Looking at the kernel output, It appears that the mtdblock4 is corrupt and the recovery process hangs because of yaffs issues. Also just trying to mount /cache causes the command to hang.
Below is the relevant output:
Any suggestions on how to un-corrupt the cache partition?
[ 6.736572] Creating 6 MTD partitions on "msm_nand":
[ 6.736602] 0x0000024c0000-0x000002500000 : "misc"
[ 6.738555] 0x0000026c0000-0x000002bc0000 : "recovery"
[ 6.739868] 0x000002bc0000-0x000002e40000 : "boot"
[ 6.741058] 0x000002e40000-0x000008840000 : "system"
[ 6.742462] 0x000008840000-0x00000d840000 : "cache"
[ 6.743835] 0x00000d840000-0x000020000000 : "userdata"
..
[ 10.782379] yaffs: passed flags ""
[ 10.782714] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
[ 12.179199] yaffs tragedy: Bad object type, 1 != 3, for object 4 at chunk 21738 during scan
[ 12.179901] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.180511] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.719390] yaffs tragedy: Bad object type, 1 != 3, for object 265 at chunk 17735 during scan
[ 13.914916] Unable to handle kernel paging request at virtual address cd7c40e4
**** RECOVERY HANGS HERE ******
gustden said:
I have a mytouch 3g and it no longer boots into recovery. All I get it the first line:
Build : RA-saphire-v1.7.0G and nothing else.
The phone is still accessable via adb in recovery.
I have flashed recovery.img serveral times using fastboot but to know avail Looking at the kernel output, It appears that the mtdblock4 is corrupt and the recovery process hangs because of yaffs issues. Also just trying to mount /cache causes the command to hang.
Below is the relevant output:
Any suggestions on how to un-corrupt the cache partition?
[ 6.736572] Creating 6 MTD partitions on "msm_nand":
[ 6.736602] 0x0000024c0000-0x000002500000 : "misc"
[ 6.738555] 0x0000026c0000-0x000002bc0000 : "recovery"
[ 6.739868] 0x000002bc0000-0x000002e40000 : "boot"
[ 6.741058] 0x000002e40000-0x000008840000 : "system"
[ 6.742462] 0x000008840000-0x00000d840000 : "cache"
[ 6.743835] 0x00000d840000-0x000020000000 : "userdata"
..
[ 10.782379] yaffs: passed flags ""
[ 10.782714] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
[ 12.179199] yaffs tragedy: Bad object type, 1 != 3, for object 4 at chunk 21738 during scan
[ 12.179901] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.180511] ==>> yaffs bug: fs/yaffs2/yaffs_guts.c 6666
[ 12.719390] yaffs tragedy: Bad object type, 1 != 3, for object 265 at chunk 17735 during scan
[ 13.914916] Unable to handle kernel paging request at virtual address cd7c40e4
**** RECOVERY HANGS HERE ******
Click to expand...
Click to collapse
Did you try to install recovery via ROM Manager (acceable at market)??? And you must have root to do it. If you dont go to the www.theunlockr.com and how to's section has everything for magic
I have tried everything I can think of. Here is my lastest attempt:
1. Flash sappimg.zip using goldcard ( to get fastboot access )
2. Flashed recovery.img via fastboot
3. Flashed hboot.nb0 via fastboot
4. Flashed boot.img via fastboot
The phone does not boot, so installing anyting from market is impossible.
If you look at the output in the original post, booting into recovery fails trying to mount the CACHE partion. Is there any way to zero out the nand memory in the cache segment?
Try this:
Code:
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot erase data
It failed when I initially tried to do a fastboot erase cache...
I was able to create a file the size of cache space, consisting of all 0x00s and flashed that to the cache partition.
It gave me an error about no space left on the device, but now the "fastboot erase cache" works just fine I would think that both do the same thing!
Many thanks, everything seems normal at the moment!!!
Hi
I am having the same problem where mtdblock4 is corrupt (a crash just after flashing a rom)
Having a mt3g Fender I am s-on
I am not having any luck with the gold card I keep getting 'model ID incorrect'.. I have tried 2 sdcards many times..
is there anyway I can do this from adb? I am pretty much out of ideas.. I will keep at the gold card problem.. I made a gold card successfully for the initial rooting
any help is much appreciated
Edit:
Ok I managed to get this fixed without a goldcard!
I unzipped Ohsaka-SuperWipe_v2.zip
then used adb to push erase_image and SuperWipe.sh to /tmp/SuperWipe
chmod +x those then ./SuperWipe.sh
and problem solved..
what a PITA!
1. how to root kitkat rom 4.4.2 on alcatel 6040d? tried almost all apps and tutorials but i failed to root.
2. how to install custom recovery? flashed the twrp recovery in the attachment but still i have the stock recovery.
3. tried to install cwm via mtk tools and sp flash tools but i always got factory_NONmodified_recovery.img as result. no modified recovery created.
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\bryanjay420\Desktop\Alcatel\MtkDroidTools\backups\TCL-S950_140926_ForFlashtoolFromReadBack_141012-005842\
--- scatter is write to the file:
C:\Users\bryanjay420\Desktop\Alcatel\MtkDroidTools\backups\TCL-S950_140926_ForFlashtoolFromReadBack_141012-005842\MT6589_Android_scatter_emmc.txtcopying is complete
-- preloader.bin ...it is copied ... cut OK
-- MBR ...it is copied
-- EBR1 ...it is copied
-- pmt ...it is copied
- PMT tables found
- PMT tables OK, 23 blocks found
--- Kernel Block Map to PMT mismatch!
-------------------------------------------
BlockName Offset
-------------------------------------------
Kernel: __NODL_BMTPOOL 0x00000000FFFF00A8
PMT: Not present! ??????????
-------------------------------------------
--- scatter from PMTis write to the file:
C:\Users\bryanjay420\Desktop\Alcatel\MtkDroidTools\backups\TCL-S950_140926_ForFlashtoolFromReadBack_141012-005842\MT6589_Android_scatter_emmc_PMT.txt
- Use it if SP FlashTool errors of 8038 or 4050 occurs
-- pro_info ...it is copied
-- nvram.bin ...it is copied
-- protect_f ...it is copied
-- protect_s ...it is copied
-- seccfg ...it is copied
-- uboot.bin ...it is copied
-- boot.img ...it is copied
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
-- recovery.img ...it is copied
-- secro.img ...it is copied
-- misc ...it is copied
-- logo.bin ...it is copied
-- EBR2 ...it is copied
-- custpack2.img ...it is copied
-- mobile_info.img ...it is copied
-- expdb ...it is copied
-- system.img ...it is copied
--- task is complete ---
Click to expand...
Click to collapse
Hi, can anyone with a D802 upload for me the img file for fota partition
I flashed the wrong partition file and the tot method is giving me this error:
Error: fota partition was changed
LAF retrieve GTP failed
Partition Change fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
just wipe it..
It looks like a new update is out for the Qualcomm, factory unlocked version of the Moto E4. I see the update number as "npqs26.69-27-3" and a description of "Security updates through September 1, 2017".
Anyone know how the update can be applied for those of us that are rooted? Has anyone already performed the update? Any issues to report?
You have to go fully stock to update. Probably will involve wiping the device.
I have the Verizon variant Moto E4, bought from Walmart in $40 deal in August, unlocked from eBay and then it started working for me for my AT&T SIM, yesterday I mistakenly updated the same to NDQ26.69-23-3 and now it is not working for my AT&T Sim. can anyone suggest what to do ? Has anyone run into this issue ?
Update unsuccessful on unlocked and rooted Moto E4 Qualcomm Perry
I have a moto e4 (qualcomm, perry) bought from Amazon (unlocked, no added) and have a CDMA trackfone-verizon sim. Phone is working fine, but the update will not apply. It gives me an error and indicates the update was unsuccessful. The bootloader is unlocked and the phone is rooted.
The issue seems to be the sha1 sum of by boot partition (see last_log below). I downloaded the stock rom for this device from https :// firmware.center/firmware/Motorola/Moto%20E4/Stock/
I believe the right one is PERRY_NPQ26.69-27_cid50_subsidy-DEFAULT_regulatory-XT1768_CFC_CANADA.xml.zip because Settings->About Phone->Build number is "NPQ26.69-27" and cat /proc/cpuinfo indicates "Device: perry". Does anybody else find it frustrating that I cannot get this file directly from motorola?
Inside that zip is a boot.img file. The sha1 sum of that file (computed with openssl sha1 boot.img) is 8f6e5f9814b84c48054bc9fd3df9f91610b85e09, which exactly matches the red text in the log file below. Also the length, 16777216, matches my current boot partition to the byte. I was hoping that simply writing this to the boot partition would fix the issue, but that was a big mistake. I copied the file to the phone and executed:
$ dd if=/dev/block/bootdevice/by-name/boot of=boot.img.orig #to save a backup of the original partition
$ dd if=boot.img of=/dev/block/bootdevice/by-name/boot
this bricked the device and it wouldn't boot. Didn't even make it to the Motorola splash screen. After some digging I was able to use fastboot on my PC to restore the boot.img.orig using:
PC$ fastboot flash:raw boot boot.img.orig
This restored the device to functioning order, but I was still not able to install the update. After this, tried to boot the stock boot image without flashing it using:
PC$ fastboot boot boot.img
This caused it to hang forever at the blue motorola splash screen. Power cycling cleared the issue as expected.
As you probably guessed by now, I am an experienced linux user, but new to android and really don't know what I am doing. @madbat99 suggests that I will have to flash the complete stock rom, wiping the device. I know how to backup, both with a backup app and with twrp, so wiping won't be a huge issue. Does anybody know how to flash a full rom? I am using gentoo linux and have fastboot and adb installed and can communicate with the bootloader, I have just never flashed a phone before. Should I expect to have to relock the bootloader for the update to apply? Afterwords, I am going to have to re-unlock the bootloader, re-root the device and then restore all my backups, correct?
I really want to apply this update due to the large gaping security holes it patches.
The relevant section of /cache/recovery/last_log are: (I bolded what I think is the real error)
[ 1.687300] I:whole-file signature verified against RSA key 0
[ 1.687314] I:verify_file returned 0
[ 1.687376] Installing update...
[ 1.729707] installing gptupgrade updater extensions
[ 1.739414] file_contexts.bin is taken from /file_contexts.bin
[ 1.740818] Mount command parameters gotten in updater script
[ 1.740855] mount point :/oem location: /dev/block/bootdevice/by-name/oem , file system type :ext4
[ 1.741029] secontext for the mount point /oem is ubject_remfs:s0
[ 1.744665] Source: motorola/perry/perry:7.1.1/NPQ26.69-27/31:user/release-keys
[ 1.744695] Target: motorola/perry/perry:7.1.1/NPQS26.69-27-3/3:user/release-keys
[ 1.744704] Verifying current system...
[ 2.115566] contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938
[ 2.115605] file "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" doesn't have any of expected sha1 sums; checking cache
[ 2.115664] failed to stat "/cache/saved.file": No such file or directory
[ 2.115675] failed to load cache file
[ 2.115687] dump_badfile is failed: EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938 is not present
[ 2.115720] script aborted: E3005: "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" has unexpected contents.
[ 2.154752] E:Error in /cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.154825] (Status 7)
[ 2.187583]
[ 2.209427] W:failed to read uncrypt status: No such file or directory
[ 2.209642] I:/cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.209652] 0
[ 2.209660] time_total: 1
[ 2.209668] retry: 0
[ 2.209675] target_build: 3
[ 2.209682] source_build: 31
[ 2.209689] error: 3005
[ 2.209699] Installation aborted.
maurerpe said:
I have a moto e4 (qualcomm, perry) bought from Amazon (unlocked, no added) and have a CDMA trackfone-verizon sim. Phone is working fine, but the update will not apply. It gives me an error and indicates the update was unsuccessful. The bootloader is unlocked and the phone is rooted.
The issue seems to be the sha1 sum of by boot partition (see last_log below). I downloaded the stock rom for this device from https :// firmware.center/firmware/Motorola/Moto%20E4/Stock/
I believe the right one is PERRY_NPQ26.69-27_cid50_subsidy-DEFAULT_regulatory-XT1768_CFC_CANADA.xml.zip because Settings->About Phone->Build number is "NPQ26.69-27" and cat /proc/cpuinfo indicates "Device: perry". Does anybody else find it frustrating that I cannot get this file directly from motorola?
Inside that zip is a boot.img file. The sha1 sum of that file (computed with openssl sha1 boot.img) is 8f6e5f9814b84c48054bc9fd3df9f91610b85e09, which exactly matches the red text in the log file below. Also the length, 16777216, matches my current boot partition to the byte. I was hoping that simply writing this to the boot partition would fix the issue, but that was a big mistake. I copied the file to the phone and executed:
$ dd if=/dev/block/bootdevice/by-name/boot of=boot.img.orig #to save a backup of the original partition
$ dd if=boot.img of=/dev/block/bootdevice/by-name/boot
this bricked the device and it wouldn't boot. Didn't even make it to the Motorola splash screen. After some digging I was able to use fastboot on my PC to restore the boot.img.orig using:
PC$ fastboot flash:raw boot boot.img.orig
This restored the device to functioning order, but I was still not able to install the update. After this, tried to boot the stock boot image without flashing it using:
PC$ fastboot boot boot.img
This caused it to hang forever at the blue motorola splash screen. Power cycling cleared the issue as expected.
As you probably guessed by now, I am an experienced linux user, but new to android and really don't know what I am doing. @madbat99 suggests that I will have to flash the complete stock rom, wiping the device. I know how to backup, both with a backup app and with twrp, so wiping won't be a huge issue. Does anybody know how to flash a full rom? I am using gentoo linux and have fastboot and adb installed and can communicate with the bootloader, I have just never flashed a phone before. Should I expect to have to relock the bootloader for the update to apply? Afterwords, I am going to have to re-unlock the bootloader, re-root the device and then restore all my backups, correct?
I really want to apply this update due to the large gaping security holes it patches.
The relevant section of /cache/recovery/last_log are: (I bolded what I think is the real error)
[ 1.687300] I:whole-file signature verified against RSA key 0
[ 1.687314] I:verify_file returned 0
[ 1.687376] Installing update...
[ 1.729707] installing gptupgrade updater extensions
[ 1.739414] file_contexts.bin is taken from /file_contexts.bin
[ 1.740818] Mount command parameters gotten in updater script
[ 1.740855] mount point :/oem location: /dev/block/bootdevice/by-name/oem , file system type :ext4
[ 1.741029] secontext for the mount point /oem is ubject_remfs:s0
[ 1.744665] Source: motorola/perry/perry:7.1.1/NPQ26.69-27/31:user/release-keys
[ 1.744695] Target: motorola/perry/perry:7.1.1/NPQS26.69-27-3/3:user/release-keys
[ 1.744704] Verifying current system...
[ 2.115566] contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938
[ 2.115605] file "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" doesn't have any of expected sha1 sums; checking cache
[ 2.115664] failed to stat "/cache/saved.file": No such file or directory
[ 2.115675] failed to load cache file
[ 2.115687] dump_badfile is failed: EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938 is not present
[ 2.115720] script aborted: E3005: "EMMC:/dev/block/bootdevice/by-name/boot:16777216:8f6e5f9814b84c48054bc9fd3df9f91610b85e09:16777216:aa4a543db08521bc2bb6860f0d8e463d199db938" has unexpected contents.
[ 2.154752] E:Error in /cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.154825] (Status 7)
[ 2.187583]
[ 2.209427] W:failed to read uncrypt status: No such file or directory
[ 2.209642] I:/cache/Blur_Version.26.11.31.perry.retail.en.US.zip
[ 2.209652] 0
[ 2.209660] time_total: 1
[ 2.209668] retry: 0
[ 2.209675] target_build: 3
[ 2.209682] source_build: 31
[ 2.209689] error: 3005
[ 2.209699] Installation aborted.
Click to expand...
Click to collapse
I hate to quote a post that long but you cannot install an official update on a rooted device with custom recovery.
If you have the correct firmware for your device, you need to extract it, rename .xml files to .img and flash with fastboot.
But it really needs to be correct firmware. I don't know the correct one for your device.
Might help
---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------
z82anu said:
I have the Verizon variant Moto E4, bought from Walmart in $40 deal in August, unlocked from eBay and then it started working for me for my AT&T SIM, yesterday I mistakenly updated the same to NDQ26.69-23-3 and now it is not working for my AT&T Sim. can anyone suggest what to do ? Has anyone run into this issue ?
Click to expand...
Click to collapse
i have the verizon variant and updated to this patch back in October when it came out and i'm still using my cricket sim in it with no problems. are you still having the issue?
madbat99 said:
I hate to quote a post that long but you cannot install an official update on a rooted device with custom recovery.
If you have the correct firmware for your device, you need to extract it, rename .xml files to .img and flash with fastboot.
But it really needs to be correct firmware. I don't know the correct one for your device.
Might help
---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------
Click to expand...
Click to collapse
Thank you @madbat99 . Using this method I was able to flash back to stock and install the update. The update works fine with my tracfone-verizon sim. I am not having the issue reported by @z82anu
To automate the process, I wrote a perl script that parses the servicefile.xml or flashfile.xml, verifies all the steps are valid, verifies that all files exist, verifies the md5 sums, and then executes the appropriate fastboot commands. It can be downloaded from https://github.com/maurerpe/stock-flash Hopefully, this will help other linux users looking to flash back to stock. Should work on window and Mac as well, but I haven't tested it.
I'm trying to reflash factory image to my Nexus player. Everything I've tried ends in an error. I have flashed alot of things (Nvidia Shield, Nexus player, Adt-1, Fire tv, Phones) so I'm not a total newbie but this has me scratching my head. It has TWRP installed and lineage 15.1 nightly flashed to it. I'm selling it so want to go back to factory. Any help would be appreciated. Thanks in advance.
Ok I can flash Lineage Os no problem. II can flash Pure Nexus no problem. When I try to flash a factory image it always errors. Here is what shows in Minimal adb.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (12260 KB)...
OKAY [ 1.588s]
writing 'bootloader'...
OKAY [ 4.586s]
finished. total time: 6.185s
rebooting into bootloader...
OKAY [ 0.576s]
finished. total time: 0.590s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (7 MB) to disk... took 0.033s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (9 MB) to disk... took 0.053s
archive does not contain 'recovery.sig'
extracting system.img (972 MB) to disk... took 5.153s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Press any key to exit...
I had the same issue. TWRP was still there, so I wiped System and Cache and formatted Data from TWRP (not sure if this is needed). I unzipped the archive that has the factory images on my laptop and rebooted into the bootloader and and ran:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Worked perfectly. Note that this erases everything and the device will boot to the setup screen, just like new.