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!
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.
After doing a twrp backup of my phone because i wanted to sell it and recover my stuff, and it suddenly stopped working after trying powering on.
The PC recognized it as qusb_bulk, i downloaded the drivers for it. Now it shows as Qualcomm HS-USB QDLoader 9008, but i tried the blankflash for the g5plus (presumably nougat) and one for the z2play and both of them failed. Here's the log.
**** Log buffer [000001] 2018-12-01_22:19:03 ****
[ -0.000] Opening device: \\.\COM4
[ -0.000] Detecting device
[ 4.032] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.032] Check qboot_log.txt for more details
[ 4.032] Total time: 4.032s
[ 4.032]
[ 4.032] qboot version 3.40
[ 4.032]
[ 4.032] DEVICE {
[ 4.032] name = "\\.\COM4",
[ 4.032] flags = "0x64",
[ 4.032] addr = "0x61FE5C",
[ 4.032] api.bnr = "0x1B2DE8",
[ 4.032] }
[ 4.032]
[ 4.032]
[ 4.032] Backup & Restore {
[ 4.032] num_entries = 0,
[ 4.032] restoring = "false",
[ 4.032] backup_error = "not started",
[ 4.032] restore_error = "not started",
[ 4.032] }
[ 4.032]
And another question i have is, can i make a blankflash file for the g5plus?, i have another one working (in terrible condition) but it works and it has oreo.
Thanks in advance.
Update: just as @[email protected] says it took a long time before it finally flash, almost 2 hours, and got the bootloader, i flashed the last oreo firmware. The phone works fine now and i still have imei and 4G.
Thanks y'all for helping me.
red002 said:
After doing a twrp backup of my phone because i wanted to sell it and recover my stuff, and it suddenly stopped working after trying powering on.
The PC recognized it as qusb_bulk, i downloaded the drivers for it. Now it shows as Qualcomm HS-USB QDLoader 9008, but i tried the blankflash for the g5plus (presumably nougat) and one for the z2play and both of them failed. Here's the log.
**** Log buffer [000001] 2018-12-01_22:19:03 ****
[ -0.000] Opening device: \.\COM4
[ -0.000] Detecting device
[ 4.032] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.032] Check qboot_log.txt for more details
[ 4.032] Total time: 4.032s
[ 4.032]
[ 4.032] qboot version 3.40
[ 4.032]
[ 4.032] DEVICE {
[ 4.032] name = "\.\COM4",
[ 4.032] flags = "0x64",
[ 4.032] addr = "0x61FE5C",
[ 4.032] api.bnr = "0x1B2DE8",
[ 4.032] }
[ 4.032]
[ 4.032]
[ 4.032] Backup & Restore {
[ 4.032] num_entries = 0,
[ 4.032] restoring = "false",
[ 4.032] backup_error = "not started",
[ 4.032] restore_error = "not started",
[ 4.032] }
[ 4.032]
And another question i have is, can i make a blankflash file for the g5plus?, i have another one working (in terrible condition) but it works and it has oreo.
Thanks in advance.
Click to expand...
Click to collapse
You can't make a blank flash file as it required Motorola digital signature, so if you are able to create one it won't work. But as you are having a other Moto g5+ then I think you can recover your device by using mmcblk0 method as it is the only way I know.
Here is the procedure of making mmcblk0
Below are the steps I followed to create a mmcblk0.img from a working device.
What is needed? -
a) A Working device of same model XT168x where 'x' could be 2,3,4,5,etc depending on region.
b) It should be a rooted one.
c) A working linux system. Any variant would do.
Steps to follow in working device:
1) Reboot device to TWRP recovery.
2) Take a backup of system,data and boot partitions. While taking backup, select the storage as Micro SDCard.
3) Once backup is complete, do a factory reset. This step is required as you don't want your friends personal files and settings.
3a) Power off the device.
4) Remove the SIM and existing SDCard.
5) Insert a new 32GB SDCard Class 10 UHS-1 into the device. This should be formatted as FAT32 or exFAT.
6) Boot the device.
7) Once booted, connect the device to computer using USB.
8) Open a terminal in your linux.
9) adb devices (This step assumes that adb and fastboot are in linux system path)
10) adb shell
11) su -
12) You are in root shell now.
13) cat /proc/partitions.
13a) Above step would list out all partitions.
14) Note the size of mmcblk0 partition.
15) Now run 'dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1000000000 count=30' without quotes. 'bs' stands for block size. Here in the above command I am giving a block size of 1GB. In my case mmcblk0 partition size was nearly 30GB. So the above command worked for me. If you are experiencing problem, then play with the numbers. For example you could try decreasing the 'bs' value and increase the 'count' value. Ultimately 'bs' multiplied by count should be the partition size. If everything goes fine, you will have a mmcblk0.img in your sdcard. One more point to note. <STORAGE-ID> in the command is the place holder. The actual ID would be a hexadecimal value. You can get your storage id by doing a 'ls /storage' in root shell. In my case the SDCard was referred as 7368-9BEE.
16)Above step would take some time as it has to create a image of 30G size. Once complete, copy the image from SDcard to your computer.
17) Power off the device and remove the SDcard from device.
18) Insert your friend's SIM card and SDCard.
19) Boot to TWRP recovery.
20) Restore the backup you took in step 2 above.
After making mmcblk0 file put that sd card in the bricked device and boot into bootloader. Once you boot in bootloader Remove the sd card and flash stock ROM.
riyan65 said:
You can't make a blank flash file as it required Motorola digital signature, so if you are able to create one it won't work. But as you are having a other Moto g5+ then I think you can recover your device by using mmcblk0 method as it is the only way I know.
Here is the procedure of making mmcblk0
Below are the steps I followed to create a mmcblk0.img from a working device.
What is needed? -
a) A Working device of same model XT168x where 'x' could be 2,3,4,5,etc depending on region.
b) It should be a rooted one.
c) A working linux system. Any variant would do.
Steps to follow in working device:
1) Reboot device to TWRP recovery.
2) Take a backup of system,data and boot partitions. While taking backup, select the storage as Micro SDCard.
3) Once backup is complete, do a factory reset. This step is required as you don't want your friends personal files and settings.
3a) Power off the device.
4) Remove the SIM and existing SDCard.
5) Insert a new 32GB SDCard Class 10 UHS-1 into the device. This should be formatted as FAT32 or exFAT.
6) Boot the device.
7) Once booted, connect the device to computer using USB.
8) Open a terminal in your linux.
9) adb devices (This step assumes that adb and fastboot are in linux system path)
10) adb shell
11) su -
12) You are in root shell now.
13) cat /proc/partitions.
13a) Above step would list out all partitions.
14) Note the size of mmcblk0 partition.
15) Now run 'dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1000000000 count=30' without quotes. 'bs' stands for block size. Here in the above command I am giving a block size of 1GB. In my case mmcblk0 partition size was nearly 30GB. So the above command worked for me. If you are experiencing problem, then play with the numbers. For example you could try decreasing the 'bs' value and increase the 'count' value. Ultimately 'bs' multiplied by count should be the partition size. If everything goes fine, you will have a mmcblk0.img in your sdcard. One more point to note. <STORAGE-ID> in the command is the place holder. The actual ID would be a hexadecimal value. You can get your storage id by doing a 'ls /storage' in root shell. In my case the SDCard was referred as 7368-9BEE.
16)Above step would take some time as it has to create a image of 30G size. Once complete, copy the image from SDcard to your computer.
17) Power off the device and remove the SDcard from device.
18) Insert your friend's SIM card and SDCard.
19) Boot to TWRP recovery.
20) Restore the backup you took in step 2 above.
After making mmcblk0 file put that sd card in the bricked device and boot into bootloader and flash stock ROM.
Click to expand...
Click to collapse
Are there any complications from using another phone's mmcblk0? I've read about this method in a few more threads here (maybe).
My bricked xt1687 that showed qusb_bulk, then Qualcomm HS-USB QDLoader 9008 wouldn't boot into bootloader, or anything else, hence the need for blankflash. OP's errors are normal, when the timing for getting the flash to connect are not exact. He needs to keep trying and eventually he'll get it to write. I purposely bricked one to get rid of the Z play bootloader, and it took 45 minutes of trying before it finally wrote.
psychopac said:
Are there any complications from using another phone's mmcblk0? I've read about this method in a few more threads here (maybe).
Click to expand...
Click to collapse
There should be no complications as I think so. As we are just using this to get bootloader. But there could be chances of losing IMEI on bricked device, nothing more than that.
---------- Post added at 03:20 PM ---------- Previous post was at 03:15 PM ----------
[email protected] said:
My bricked xt1687 that showed qusb_bulk, then Qualcomm HS-USB QDLoader 9008 wouldn't boot into bootloader, or anything else, hence the need for blankflash. OP's errors are normal, when the timing for getting the flash to connect are not exact. He needs to keep trying and eventually he'll get it to write. I purposely bricked one to get rid of the Z play bootloader, and it took 45 minutes of trying before it finally wrote.
Click to expand...
Click to collapse
I don't think the blank flash file is going to work now as we are now on Oreo on with latest firmware. So we need the latest blank flash file with latest bootloader in it.and I don't think we are having the latest bootloader in blank flash file. So I don't think so it will work.but giving a trying is not a problem.
riyan65 said:
There should be no complications as I think so. As we are just using this to get bootloader. But there could be chances of losing IMEI on bricked device, nothing more than that.
---------- Post added at 03:20 PM ---------- Previous post was at 03:15 PM ----------
I don't think the blank flash file is going to work now as we are now on Oreo on with latest firmware. So we need the latest blank flash file with latest bootloader in it.and I don't think we are having the latest bootloader in blank flash file. So I don't think so it will work.but giving a trying is not a problem.
Click to expand...
Click to collapse
I'm not sure that blankflash will not work, as I have a potter device on the addison bootloader that I was able to go from stock nougat to stock oreo via ADB. It still gives bootloader error when trying to write but is fully functional non-the-less.
[email protected] said:
I'm not sure that blankflash will not work, as I have a potter device on the addison bootloader that I was able to go from stock nougat to stock oreo via ADB. It still gives bootloader error when trying to write but is fully functional non-the-less.
Click to expand...
Click to collapse
Now it won't work as at the time of nougat the blank flash file contain Oreo bootloader, so it was able to recover, but now we are now on Oreo, so it won't work.
This just is not true. I just took my "test" phone which has twice been bricked before. It has stock oreo on it, and I hard bricked it to just flashing light and is recognized by pc as qusb_bulk. This phone has never been able to be recovered with potter blankflash, but does recover and rewrite bootloader with addison blankflash. I was able to use addison, then write the addison 2 potter files, and write back stock oreo rom. Whole process took about an hour this morning.
[email protected] said:
This just is not true. I just took my "test" phone which has twice been bricked before. It has stock oreo on it, and I hard bricked it to just flashing light and is recognized by pc as qusb_bulk. This phone has never been able to be recovered with potter blankflash, but does recover and rewrite bootloader with addison blankflash. I was able to use addison, then write the addison 2 potter files, and write back stock oreo rom. Whole process took about an hour this morning.
Click to expand...
Click to collapse
Is that device is having latest firmware 13-3 or it is having a old firmware???
It had the latest debloated rom on it, potter-OPS28.85-17-2-debloated.
I don't think the new stock oreo is dependant on a new bootloader, as I posted before, this device would always show errors trying to write new bootloader from stock adb rom, yet installed, and functioned perfectly. And also, blankflash loads into the processor at the beginning of the bootloader sequence, which is how we get the device out of it's "dead" state.
[email protected] said:
It had the latest debloated rom on it, potter-OPS28.85-17-2-debloated.
I don't think the new stock oreo is dependant on a new bootloader, as I posted before, this device would always show errors trying to write new bootloader from stock adb rom, yet installed, and functioned perfectly. And also, blankflash loads into the processor at the beginning of the bootloader sequence, which is how we get the device out of it's "dead" state.
Click to expand...
Click to collapse
I think the bootloader is same for Moto g5+ and Moto z play that why the blank flash file is working or else it didn't work at all, but we should kept a backup method also so we can able to recover it, if blank flash file don't work.
Need Blank Flash File
red002 said:
After doing a twrp backup of my phone because i wanted to sell it and recover my stuff, and it suddenly stopped working after trying powering on.
The PC recognized it as qusb_bulk, i downloaded the drivers for it. Now it shows as Qualcomm HS-USB QDLoader 9008, but i tried the blankflash for the g5plus (presumably nougat) and one for the z2play and both of them failed. Here's the log.
**** Log buffer [000001] 2018-12-01_22:19:03 ****
[ -0.000] Opening device: \\.\COM4
[ -0.000] Detecting device
[ 4.032] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.032] Check qboot_log.txt for more details
[ 4.032] Total time: 4.032s
[ 4.032]
[ 4.032] qboot version 3.40
[ 4.032]
[ 4.032] DEVICE {
[ 4.032] name = "\\.\COM4",
[ 4.032] flags = "0x64",
[ 4.032] addr = "0x61FE5C",
[ 4.032] api.bnr = "0x1B2DE8",
[ 4.032] }
[ 4.032]
[ 4.032]
[ 4.032] Backup & Restore {
[ 4.032] num_entries = 0,
[ 4.032] restoring = "false",
[ 4.032] backup_error = "not started",
[ 4.032] restore_error = "not started",
[ 4.032] }
[ 4.032]
And another question i have is, can i make a blankflash file for the g5plus?, i have another one working (in terrible condition) but it works and it has oreo.
Thanks in advance.
Update: just as @[email protected] says it took a long time before it finally flash, almost 2 hours, and got the bootloader, i flashed the last oreo firmware. The phone works fine now and i still have imei and 4G.
Thanks y'all for helping me.
Click to expand...
Click to collapse
Can you please provide the link for Blank Flash file that worked for you.
Hello, moto g5 plus is left alone with the led flashing and does not enter anything, does not start. To try to recover it with the BlankFlash tool, is it mandatory to have the bootloader unlocked? please i need your help to try to get it back. thanks