I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Raistlin1 said:
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Click to expand...
Click to collapse
I would get into bootloader mode and reflash the system.img.
JulesJam said:
I would get into bootloader mode and reflash the system.img.
Click to expand...
Click to collapse
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
I even tried using someone's toolkit to return completely stock u rooted 4.4 but that doesn't work either.
Been reading tons of threads on here but can't seem to get it to flash.
Raistlin1 said:
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
Click to expand...
Click to collapse
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
JulesJam said:
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
Click to expand...
Click to collapse
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Raistlin1 said:
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Click to expand...
Click to collapse
I would try flashing the sparsechunks if you can't flash the single file image.
JulesJam said:
I would try flashing the sparsechunks if you can't flash the single file image.
Click to expand...
Click to collapse
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
I am really screwing myself, now while in bootloader and I try to boot or recovery I get failed to validate. Never had these problems flashing my N5, oh well.
Raistlin1 said:
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
Click to expand...
Click to collapse
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
JulesJam said:
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
Click to expand...
Click to collapse
I am getting bootloader failed to erase partition, failed remote failure.
MDM says phone is on latest version. mfastboot is the size you stated.
Raistlin1 said:
I am getting bootloader failed to erase partition, failed remote failure.
Click to expand...
Click to collapse
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
JulesJam said:
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
Click to expand...
Click to collapse
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Raistlin1 said:
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Click to expand...
Click to collapse
Can you reflash stock recovery?
Your bootloader is locked correct?
JulesJam said:
Can you reflash stock recovery?
Your bootloader is locked correct?
Click to expand...
Click to collapse
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Raistlin1 said:
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Click to expand...
Click to collapse
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
I am spent, going to bed and will pick up again tomorrow. Thanks for helping out.
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Raistlin1 said:
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Click to expand...
Click to collapse
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
JulesJam said:
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
Click to expand...
Click to collapse
As of now I can only get into fastboot mode, I don't believe the phone can even cycle through trying to boot any more. I tried rebooting from fastboot mode but there was an error and it failed.
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Raistlin1 said:
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Click to expand...
Click to collapse
http://www.graffixnyc.com/motox.php
JulesJam said:
http://www.graffixnyc.com/motox.php
Click to expand...
Click to collapse
Downloaded the 5.0 file from there, started flashing those files and it worked up until recovery, then I got the same bootloader message I was getting previously. Tried them over again and they all failed.
When in recovery adb devices starts the daemon and then says list of devices attached but I don't see anything after that.
I think it is fubar`d, going to have to file a warrant claim or use the moto care I purchased.
Bricked. Red "Your device is corrupt. It can't be trusted and may not work properly"
Following this guide I ended up bricking my Nexus 6. Please ask questions as this is my first time rooting a device.
http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
After typing "fastboot reboot" my phone begun rebooting, stopped and went to the red "Your device is corrupt. It can't be trusted and may not work properly". Now I am able to get to the fastboot menu. I am also able to get to the android recovery menu. Can anyone point me in the direction to get my phone working again?
Thank you in advance
You can get into fastboot. So restore to stock image. Or since you have custom recovery restore your working backup.
Then read the thread on root. Not just the first post. Read the most recent ones... They are the ones with the most up to date info. Never flash stuff or follow guides with out reading like the last 3-4 pages of the thread as well as the full OP AT A MINIMUM.
1)download google factory image
2)Extract everything in one folder.
3)Delete userdata.img from folder(because once i left it in folder and started flashing images one by one and ended up with empty internal storage.lost everything)
4)use these commands to flash
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
5)reboot
You don't have to delete userdata.img... Just dont flash it, and don't use flashall
Your manually typing these commands. Just don't type it. Understand what the partitions are and don't flash the ones you don't want.
And on that point, rather then flash the stock recovery, flash something like TWRP since your trying to root.
Wow. Thank you guys. I really appreciate it. Great group here.
Got it back up and running with 6.0.1 with your help. Since I have gotten this far I think I'll try out some ROM's.
Thanks again.
Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?
touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!
after unlocking, falshind twrp and wipeing the complete device I can't do anything at all now.
I can boot in twrp or to fastboot but the device can't be found in either modes.
I tried to mount the sd card or MTP but they don't do anything either. Also tried to sideload onto the device but of course it doesn't work.
I'm all out of ideas what to do now. Anybody got some ideas what I could try?
Extract system from fastboot firmware and flash in fastboot with command fastboot flash system system.img after flashing system flash twrp and install rom or simply just flash fastboot firmware with Miflash
yes, thank you very much. this was the trick!
you get everything bacc up and running ok?
Hoping I could get some help for this old phone. I've spent over 5 hours trying to get twrp installed and having no success in what should be one of the quickest steps in the whole rooting/flashing game. Reaching out for help before I lose my mind...
I've tried 2 different builds of oreo and 2 different builds of pie (all stock) and for each build I flashed different twrp versions from this link https://androidfilehost.com/?w=files&flid=232371. I even tried the android 9/10 versions on the android 8 builds. No errors in fastboot. If I try using power plus either of the volume keys it just boots right to android. If I try using the fastboot command (fastboot boot recovery.img) it freezes at the Sony logo. Doesn't seem to be an issue with twrp because I couldn't find a single mention of anyone else having this issue in any of the threads I've read while trying to troubleshoot. Any suggestions?
Is your bootloader locked?
betacrypt said:
Is your bootloader locked?
Click to expand...
Click to collapse
Oh, right, I should have mentioned that it's definitely unlocked. I checked in the service menu and I get the warning at startup.
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
betacrypt said:
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
Click to expand...
Click to collapse
So I managed to get this working. I tried the fastboot erase command but still had no success. Googled "fastboot erase twrp" or something like that and found a thread discussing how twrp was suspected of corrupting someone's data partition and running a "fastboot erase userdata" command to reformat the partition. I didn't think this would help my situation but figured I had nothing to lose at this point. Ran the "erase userdata" command, set up the phone again, but had no success at first.
I re-ran the "erase recovery" command and had no success with twrp 3.3.1. Then I tried 3.2.1 and initially had no success with hardware buttons or the "boot recovery" command. What I did this final time though, which I don't think I did on my previous attempts, was that instead of going back immediately and trying to re-flash twrp after the frozen sony screen, I gave up this time. BUT....I also said "f* it...let me try booting into recovery with the hardware buttons one last time." Lo and behold, I finally got into twrp!
I don't know if running the "erase recovery" command is what was needed, or it was just some quirky glitch where I needed the phone to freeze. Nevertheless, many thanks for responding and prompting me to make the last few attempts. Flashed magisk with no issue afterwards.