Installing TWRP on bricked, but not rooted Sprint M7? - One (M7) Q&A, Help & Troubleshooting

After not messing with my wife's M7 for quite some time, I am back for another go at it. She managed to mess up her LG G3, so recovering the M7 is now back on the table. My goal has been to try to recover the data on the phone, so I have not tried a factory reset. Deleting the cache partition in the recovery menu also proved futile.
I have HBOOT 1.57, and a looked bootloader. I have ADB and Fastboot on my PC, and can get the phone into FASTBOOT USB, but my attempts to copy over TWRP 2.7.0.1 haven't worked.
What I got was this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (7918 KB)...
OKAY [ 1.132s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.780s
Can it be done with a bricked phone and a locked bootloader, or am I just wildly grasping at false hope?

groovyz1k said:
After not messing with my wife's M7 for quite some time, I am back for another go at it. She managed to mess up her LG G3, so recovering the M7 is now back on the table. My goal has been to try to recover the data on the phone, so I have not tried a factory reset. Deleting the cache partition in the recovery menu also proved futile.
I have HBOOT 1.57, and a looked bootloader. I have ADB and Fastboot on my PC, and can get the phone into FASTBOOT USB, but my attempts to copy over TWRP 2.7.0.1 haven't worked.
What I got was this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (7918 KB)...
OKAY [ 1.132s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.780s
Can it be done with a bricked phone and a locked bootloader, or am I just wildly grasping at false hope?
Click to expand...
Click to collapse
I hate to be the one, but you are wildly grasping for a false hope. You need unlocked bootloader in order to flash custom recovery

That is actually a pretty big relief at this point. I was more mad that I was doing something wrong than I was about recovering the phone. Thanks! I should have asked the question hours earlier so I didn't waste all that time. I picked up some new understanding though, so all was not lost.

Factory Reset seems to have failed!
Mine shows:
-- Wiping data...
Formatting /data...
Backup Data Preload
Backup CW Package
Restore Data Preload
Restore CW Package
Formatting /cache
Data Wipe Complete.
Write host_mode:0 done
Then it gives me the same system recovery menu. Rebooting just put it right back into the same loop.

Related

Help - Stuck in Bootloop

The point in which everything took a turn for the worst was while trying to update firmware via SD update method. At which point it just stayed on android boot screen.
Recovery was broken at this point
I successfully flashed an older CWM version, but that was useless for reflashing the latest Asus firmware.
I tried flashing stock recovery again and it appeared to succeed, but now when I try to boot to recovery, it just goes back to bootloop.
I'm trying to flash the US version now via fastboot I get bootloop again and I'm getting weird errors every time I try regarding filesize. (See below)
I tried flashing CROMbi as well and it went through the install process successfully, but that resulted in bootloop as well.
Tried flashing Asus US firmware again without success,
Kind of pissed that this all started when following the instructions on the Asus site to upgrade to their latest firmware via SD card.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system
asusus.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.457s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
OKAY [ 86.837s]
writing 'system'...
OKAY [ 17.080s]
sending sparse 'system' (415060 KB)...
OKAY [ 57.305s]
writing 'system'...
OKAY [ 11.353s]
finished. total time: 174.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.021s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.
The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk
berndblb said:
The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
The attempted SD update was done with custom recovery as I couldn't get stock recovery to work after the initial SD update with stock recovery.
Thanks for the info. I'll update.
gorilla p said:
Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.
Click to expand...
Click to collapse
That error message means that your internal sdcard is no t available to format. Erasing all partitions is a dangerous thing to do.
The only way you will get back to normal is to try and flash the stock asus rom now as that will recreate everything. I recommend you start with the 4.2.2 one - need to flash it over fastboot - I can't see anything else working as you have erased it all.....
Also you used 0x0b05 which is the code for the last generation of transformers..... You don't need it for the TF701 but not sure if that has caused additional grief now. Probably not but you never know .....
Yeah IO'm getting the same issue that I was having before. I tried both the 4.3 and 4.2 boot.img and the recommended recovery.img file. Each time I ran
fasboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.121s]
booting...
OKAY [ 0.032s]
finished. total time: 1.157s
booting from downloaded boot.img (on tablet)
Then it goes to boot into the image and...bootloop.
C:\Program Files (x86)\Minimal ADB and Fastboot\asus>fastboot flash system asus4
22.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.515s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
OKAY [ 86.861s]
writing 'system'...
OKAY [ 17.098s]
sending sparse 'system' (338700 KB)...
OKAY [ 46.823s]
writing 'system'...
OKAY [ 9.280s]
finished. total time: 161.586s
Bootloop...
Could the inability to flash or boot from stock recovery have anything to do with the CWM recovery protection?
Well after those attempts it's totally shot.
Now I can't even get to fastboot. Every reboot results in "Unrecoverable bootloader error..."
Files RMA. Returned.
Moral of story. Don't do anything on a Tegra device without previous documentation that doesn't have NVFlash available.

XT890 Stuck on Red Logo. Probably damaged partitions.

Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Ye, great chance that the emmc is damaged. But it still looks to me as if it is software damaged, not hardware, because of the successful flash of recovery. And it is on the same memory module.
Just as in the other post of this phone can u try this and give me the output of especially the flash of gpt.bin (partition table file). I never got an exact answer to it, for my liking, maybe i read over it.
If that doesn't flash (give me the output then i know for sure ), try flashing the boot.img and see what happens. I assume nothing will change from flashing the boot.img, but u gotta try something.
Next we can do is have a look at that intel flashing file, it looks promising. I never had to go to this part so i am out of general ideas (think outside the box maybe?). Maybe we can fiddle something from here. It looks to me like it can flash more than fastboot can, u just need the right files and some we can make, hopefully if i read the sources available to us right.
Hazou
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash gpt gpt_s
igned
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'gpt' (32 KB)...
OKAY [ 0.358s]
writing 'gpt'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 1.094s]
finished. total time: 1.460s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motoboot
motoboot
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motoboot' (23273 KB)...
OKAY [ 2.635s]
writing 'motoboot'...
(bootloader) flashing image dnx...
(bootloader) flashing image ifwi...
(bootloader) flashing image bos...
(bootloader) flashing image logo...
(bootloader) flashing image ulogo...
OKAY [ 2.338s]
finished. total time: 4.981s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash boot boot
_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.243s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.799s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash recovery
recovery_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'recovery' (11264 KB)...
OKAY [ 1.338s]
writing 'recovery'...
OKAY [ 1.563s]
finished. total time: 2.907s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motobp mo
tobp
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motobp' (17091 KB)...
OKAY [ 1.714s]
writing 'motobp'...
OKAY [ 76.674s]
finished. total time: 78.396s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash system sy
stem_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.377s]
writing 'system'...
OKAY [ 2.576s]
sending 'system' (102400 KB)...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
OKAY [ 11.154s]
writing 'system'...
FAILED (remote failure)
finished. total time: 25.509s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash cdrom cdr
om_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'cdrom' (53258 KB)...
OKAY [ 4.891s]
writing 'cdrom'...
FAILED (remote: Preflash validation failed)
finished. total time: 6.273s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase cache fail
FAILED (remote failure)
finished. total time: 1.897s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
FAILED (remote failure)
finished. total time: 8.110s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>
So it looks like only few partitions are broken but how to repair it without unlocking bootloader??
Hmm, it does flash a part of the system if I read it correct. After the first one it gives errors to all partitions after it.
Can u reboot to recovery now, we finally flashed it right. Didn't work last time.
The things I wanted to do with the Intel thingy, are already done with flashing motoboot. So the things I had there are done.
Verstuurd van mijn GT-P5110
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Chamelleon said:
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Click to expand...
Click to collapse
Yep, this happens because it has nothing to start.
There is just 1 more think I can think off, because all others are closed (locked) or don't work. Or if unlocked we still don't have access.
Does the command "fastboot oem format" does something?
Verstuurd van mijn GT-P5110
Completely forgot about this command, I'll try it after work.
FAILED (remote: Restricted OEM command)
Then its over I think. We can't flash a custom recovery and fiddle around with it. Because maybe by not asking for system/data partition at start etc u can reformat the emmc with parted or other application.
Sorry, only Motorola can fix it. Or u need to replace the motherboard maybe? But that's something else.
Oh, try 1 more thing. Is it possible to load a custom boot image by the command "fastboot boot (image)"? Don't think so, but who knows. So u won't flash it.
Verstuurd van mijn XT890
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Chamelleon said:
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Click to expand...
Click to collapse
Yup, the defy could do it if i remember correctly. Hoped that this one would either. I am out of ideas now, but will have one more look. Don't expect anything, because we already tried most if not all the things we can do.
Edit:
All other things i can think of need to have adb access, and that can only be done by having an unlocked bootloader or root access. Because with root access u can flash a recovery even when u have a locked bootloader most of the time. But we don't have access to the system as well as the partitions, so we are stuck.
That Intel thingy can only flash the bootloader and the bootloader wont repartition the emmc. But we can try anyway if u want. Its a little bit different then the unbrick methode, just a little.
Verstuurd van mijn XT890
Today I flashed Samsung C3595 with partition table from S5610 and it's working well so "different" methods are not scary for me.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Hi Chameleon.. i'm having a phone with similar issues (I created a post about it). I have tried steps one and two to no success. To unlock it do you do it via the official way (I ask because I don't know much, maybe there are other ways of doing it)
Yup, only official way.
Wysłane z Motorola RAZR i
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
hjahmetoglu said:
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
Click to expand...
Click to collapse
Luckily, u don't have the same problem. U only have to search for a rsd lite flash guide. Flash your latest firmware that is available for your phone and country/brand. And all will most likely be good.
Hazou said:
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
Click to expand...
Click to collapse
Yesterday I tried it and unfortunately nothing changed, still can't erase or write to those partitions.
XT890 Stuck on Red Logo. Probably damaged partitions
I woke up this morning to find that my Motorola XT890 is not working. I followed all the procedures for hard rest got the same result as listed below.
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
Contacted Motorola customer service, followed all the procedures as prescribed by Motorola customer service still stuck at Red Logo. Motorola has requested that I send it in for repair. The phone is 11 months old and under warranty. The unfortunate thing is that this is the second time I am sending the phone to Motorola for repair.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse

[Q][SOLVED] Can't get root back (4.4.4)

I was on 4.4.2, rooted. I did a factory reset, flashed stock 4.4.2 (system, recovery, and boot), then got the 4.4.4 OTA.
Still says "unlocked bootloader."
I installed Titanium -- no root.
I rebooted to bootloader, tried flashing TWRP with:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 1.228s]
finished. total time: 2.002s
Rebooted to recovery -- got 'dead andy' with 'No Command' below.
Tried:
Code:
fastboot boot openrecovery-twrp-2.7.1.1-ghost.img
downloading 'boot.img'...
OKAY [ 0.775s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.875s
Also tried flashing `UPDATE-SuperSU-v1.94.zip` from stock recovery ... got
Code:
qe 0/1
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
I also then tried all of the above with `mfastboot` -- same result.
What do I do now?
d0g said:
I was on 4.4.2, rooted. I did a factory reset, flashed stock 4.4.2 (system, recovery, and boot), then got the 4.4.4 OTA.
Still says "unlocked bootloader."
I installed Titanium -- no root.
I rebooted to bootloader, tried flashing TWRP with:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 1.228s]
finished. total time: 2.002s
Rebooted to recovery -- got 'dead andy' with 'No Command' below.
Tried:
Code:
fastboot boot openrecovery-twrp-2.7.1.1-ghost.img
downloading 'boot.img'...
OKAY [ 0.775s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.875s
Also tried flashing `UPDATE-SuperSU-v1.94.zip` from stock recovery ... got
Code:
qe 0/1
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
What do I do now?
Click to expand...
Click to collapse
The issue is that you have to IMMEDIATELY reboot into custom recovery. Do this (from bootloader screen):
fastboot flash recovery twrp_file_name.img
fastboot reboot-bootloader
Now VOL DOWN to recovery, and VOL UP to select it.
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
samwathegreat said:
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
Click to expand...
Click to collapse
AHA! Thank you thank you!
samwathegreat said:
The issue is that you have to IMMEDIATELY reboot into custom recovery. Do this (from bootloader screen):
fastboot flash recovery twrp_file_name.img
fastboot reboot-bootloader
Now VOL DOWN to recovery, and VOL UP to select it.
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
Click to expand...
Click to collapse
I notice you help out on almost every thread and have helped me more then a few times. Just thought id say thanks from all us that are trying to lose are noob status lol
Sent from my XT1058 using Tapatalk
Hi there.. Am also using moto x and running stock 4.4.4... And i want to Unlock my bootloader and get Root... Can u pls guide me through the steps and file i need? Thank you

[Q] Moto XT1097 AT&T fastboot loop.

I tried to update my moto XT1097 AT&T locked version and it did not complete the update successfully. It goes until flashing the boot.img, failed and don't go any further. I supposed it is because it is a locked phone. After this, the phone went to a fastboot mod loop. Even If I tried to sideload the orignial rom or use the fsaboot comandts to restore the original rom it remains in this mode.
It generates a first error when I tried to issue the command "fastboot flash partition gpt.bin" returning this:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.013s
And the phone display shows "hab check failed for primary_gpt"
I am issuing this command from the folder where the files of the original rom are located.
I tried to use a different gpt.bin file, from other ROMs and the same thing happen. I also tried another Lollipop ROM and not luck at all.
What I understand is that the gpt is the partion table that indicates where begins and where finish the diferent partitions into the phone, so I guess the problem could be resolve if I can change the gpt file into the phone for the original one.
I have tried to follow with the rest of the instalation but the motoboot and the boot files also are rejected and the system files are denied due an authentication problem.
The roms I have tried are:
ATT_XT1097_4.4.4_KXE21.187-38_cid1_CFC.xml
TMO_21.21.42.victara_tmo.tmo.en.US
4.4.4_to_5.0-11OTA
And the first one I used, which reach the same stage every time is:
RETBR_XT1097_5.0_LXE22.46-17_cid12_CFC.xml
I really appreciate any help and ideas you can give me to get my phne back to kitkat. I am not an expert but I am willing to do and learn what it takes
Did you solve this? How?
I am into this problem too. Any news?

Android OS gone! /system partition empty; fastboot and recovery flashes fail.

tl;dr Android OS is missing from my Nexus 6 for an unknown reason, fastboot isn't working (nor is flashing via recovery), /system and /firmware partitions read 0 MB in each. Help!
Context
My Nexus 6 is a replacement I got in the beginning of February after some speaker issues with my original N6. The device was unlocked, encrypted, used TWRP as custom recovery, and rooted (with Chainfire's SuperSU). I was running stock 5.1 (shamu-lmy47d). My root apps were few: AdAway, TitaniumBackup, SuperSU, Solid Explorer, and Cerberus (no account activity with Cerberus in the past two weeks). I'm familiar with fastboot, custom recoveries, flashing, etc. I've been doing this on my Droid X, Nexus 4, Nexus 7, and Nexus 6 for years and never had anything like this happen (nor have I really run into issues I couldn't figure out).
Situation
While using Sync for Reddit, some apps started crashing. Then Sync stopped loading anything. Then seemingly every app on my device reported a crash. Thinking a reboot would fix whatever was going on, I rebooted my phone. The boot animation didn't end after ten minutes, so I shut my phone back off and got into recovery.
I tried rebooting to system from TWRP. The first thing I noticed was that TWRP did not prompt me for a PIN. When I tried rebooting to system, I was greeted with the following message: "No OS installed! Are you sure you wish to reboot?". Confused, I went to the backup page to check partition sizes. TWRP showed "System (0MB)", "Data (56975MB)" (that's 57GB--I probably had 20GB maximum).
TWRP logs read as follows:
Code:
Data successfully decrypted, new block device '/dev/block/dm-0'
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage[/COLOR]
Successfully decrypted with default password.
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.[/COLOR]
Full SELinux support is present.
[COLOR="red"]E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to open '/cache/recovery/.version'.
E:Unable to mount '/data'[/COLOR]
MTP Enabled
A factory reset from TWRP returns the following:
Code:
Factory Reset Complete
[COLOR="red"]Failed[/COLOR]
and in the log:
Code:
[COLOR="red"]E:Unable to mount '/data'
E: Unknown MTP message type: 1[/COLOR]
Formatting Cache using make_ext4fs function.
[COLOR="red"]E:Unable to mount '/cache'[/COLOR]
Updating partition details...
[COLOR="red"]E:unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.[/COLOR]
I will now post the results of several fastboot commands. Some analysis will follow at the end of this post, but I don't really have a clue as to what is going on.
Code:
$ fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 17.483s]
writing 'system'...
OKAY [ 8.162s]
sending sparse 'system' (510197 KB)...
OKAY [ 17.036s]
writing 'system'...
OKAY [ 7.362s]
sending sparse 'system' (515601 KB)...
OKAY [ 17.891s]
writing 'system'...
OKAY [ 8.047s]
sending sparse 'system' (188485 KB)...
OKAY [ 6.661s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 94.184s
Code:
$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.105s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.676s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 13.678s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.08
Baseband Version.....: D4.0-9625-02.95
Serial Number........: ZX1G322CNQ
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7681 KB)...
OKAY [ 0.243s]
writing 'boot'...
(bootloader) Failed to flash partition boot
(bootloader) Failed to flash partition boot
FAILED (remote failure)
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
Code:
$ fastboot -w
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.758s
Code:
$ fastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.002s
I'll try any suggested commands as nothing appears to be working anyways. At this point, I don't care about my data. It's encrypted anyways, so it's probably unrecoverable regardless of if I get my phone working again.
I think the partition table somehow got destroyed or the flash memory failed. What's curious is that /data, /boot, /recovery, /EFS are still intact while /firmware and /system are not. I blame hardware because the issues started while the OS was booted (what on the OS level has permissions to write to /system and /firmware?) and nothing writes to the partitions anymore (they can't even be mounted!).
I'm looking for help in any way, especially the in the following:
(1): Finding the cause of this issue and squashing it if it's a bug in Android, TWRP, or some other software.
(2): Getting my phone back to a working state. Again, I don't care about the data on the device.
(3): (if 2 fails) getting my phone locked and removing TWRP so that I can RMA it--Google has already offered a replacement, but I don't want to send it in unlocked and with TWRP (may cause them to charge me for the replacement)​
If this is indeed a software-caused error (again, I don't think my actions of using Sync for Reddit caused this issue), I'm terrified that this may affect others who are less capable of seeking help, or those who have critical data on their devices.
Thanks for reading. Please offer any guidance you may have.
-Ethan
kudos to you for providing so much detail for your problem. It's a rare sight here. It really helps people who are trying to help you.
I have a feeling your device is completely fried as even fastboot isn't working. I remember I had a similar problem with the OS disappearing but I solved it with a fastboot flash. If that doesn't work for you, I'm not sure what can. But then again, I'm not a seasoned tinkerer when it comes to android partitions. Let's wait for someone with more knowledge to share their opinion.
@rootSU do you have any ideas here? Can he mount in TWRP and possibly push the files needed or is TWRP too broken at this point?
Thank you for providing such details with the errors. I wish everyone was so thorough.
Thanks for the replies so far @exb0 and @Evolution_Freak!
For the record, "fastboot devices" and "adb devices" do work. It just appears that any thing operating on the file system does not work. Strangely, I was able to "adb push" a ZIP over and tried to flash it from recovery (flashing failed, of course). I was also able to move the ZIP around using TWRP.
I wonder if it would be feasible to move files into place manually and get a working system again by doing that. I don't want to do that unless it appears to be my only option and there's a good chance of it actually working.
I don't frequent XDA, so help getting knowledgeable community members would be greatly appreciated.
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
rootSU said:
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
Click to expand...
Click to collapse
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
ethanmad said:
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
You can try and also:
fastboot format system
fastboot format userdata
fastboot format cache
See if you can then flash system.img, userdata.img and cache.img separately.
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Didgeridoohan said:
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Click to expand...
Click to collapse
Yes, it says in his post
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
I had initially thought of this but his phone is still recognized by a PC as it normally should be and not as qhusb bulk. But if this could be a possible solution to his partition problem, then thank you for pointing him in that direction. :good:
IINexusII said:
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
Click to expand...
Click to collapse
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Evolution_Freak said:
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
Click to expand...
Click to collapse
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
Click to expand...
Click to collapse
Had your OEM lock succeeded, with no OS installed, you could have inadvertently bricked yourself. It's in your best interest to leave it unlocked until you're sure you can boot into Android and ensure that the "allow OEM unlock" stays ticked after a reboot. If you'd like more information on that, click the top link in my signature.
First things first though, let's get you up and running.
ethanmad said:
To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
Click to expand...
Click to collapse
That you knew enough to do so IS indicative -- at least from my perspective. Well done! Keep us all posted.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Click to expand...
Click to collapse
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Louie998 said:
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Click to expand...
Click to collapse
Correct. I had to download and install the full SDK to get the latest version. Couldn't flash the OTA with the version that was available from Ubuntu repositories.
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Chainfire said:
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Click to expand...
Click to collapse
That's part of the problem, he can't get anything to flash. Everything attempted errors out.

Categories

Resources