Related
I am 100% stock.
I did the update using Minimal ABD and Fastboot. Once that was finished, the phone booted up (after optimizing all my apps) and gave me a System UI error and would never get past that (even if I hit OK or Report). I turned it off and then went it came back on, it went straight to the Google Logo. It didn't even vibrate like it usually does when it boots up.
If I hold down all 3 buttons, it will boot to the bootloader screen, but anything I do from there, just goes back to the Google logo and that's it. I had to go to Recovery and get another error, then hit power + volume up, and I did a factory wipe. However, after that, it still does the same thing. Goes to the Google Logo and nothing else. I've wiped it a few times now and no luck.
Any suggestions on what to do?
Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
edit: Didn't realize update file was sent out through OTA. Try flashing factory 5.0.1 then flash the update which is in the cache folder. Extract and save that 5.1 OTA file somewhere else before flashing 5.0.1, if not its gone. Best suggestion is to wait go back to 5.0.1 and wait for 5.1 factory image.
DevilMR said:
Which ROM did you flash? There is no 5.1 factory image at the moment. If you are flashing through ADB, try manually erasing then flashing each file first instead of using flash-all. Don't forget to flash userdata.
Click to expand...
Click to collapse
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post
mikebio said:
Sorry, no ROM, just the OTA.zip I tried. I used it from here: (can't link) but AndroidPolice FLASH ALL THINGS post
Click to expand...
Click to collapse
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?
meest said:
Most likely going to have to download the 5.0.1 factory image and reflash that if you didn't make a backup before doing the OTA.
I'm assuming you don't have a 3rd party recovery since your title says "STOCK" correct?
Click to expand...
Click to collapse
This is correct. I also can't get my computer to recognize my Nexus anymore. Any tips on that?
OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.
DevilMR said:
OK, i see what you did. Try flashing factory 5.0.1, then flash that 5.1 update. I rather wait for factory 5.1.
Click to expand...
Click to collapse
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Nevermind, got it... I am going to reflash factory image... I tried 5.0.1 and it failed.
mikebio said:
Will do. Do you know the exact USB driver I need for nexus 6? When I plug it into my computer now, it comes up Shamu and I can't get the phone to be recognized by Nexus Root Toolkit or Minimal ADB & Fastboot
Click to expand...
Click to collapse
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html
meest said:
If I remember right I just downloaded the google driver pack and pointed windows to that directory and it found one.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
The issue is, it comes up Fastboot Shamu and it isn't recognized. Only when I put in into Apply update from ADB does it show up Nexus 6 on Windows... Not sure what to do. I can't flash right now because of this.
How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
I wonder the same thing. I tried to get rid of the red triange but it's impossible. I've tried a full wipe and flash everything from stock but no dice.
Also i'm unable to boot to recovery. It just freezes... Same thing if I flash back the 5.1.1 image. TWRP is working though.
Any ideas?
Does anyone have a solution to get rid of the triangle WITHOUT twrp or root? I flashed TWRP to see if I could install a custom HOSTS file and the message started popping up on boot, but even after reflashing everything from the official M image and wiping data and cache it still pops up. Any suggestions? o_o
Did you flash userdata too? Tried factory reset on top?
pszyman said:
Did you flash userdata too? Tried factory reset on top?
Click to expand...
Click to collapse
I formatted userdata because I have a 64GB device and the userdata image included is for 32GB. this is what I did without the file names because I'm mobile:
Code:
Fastboot flash bootloader mboot.img
Fastboot reboot-bootloader
Fastboot flash mradio.img
Fastboot flash system msystem.img
Fastboot flash boot mboot.img
Fastboot flash recovery mrecovery.img
Fastboot format userdata
Fastboot format cache
And then I booted and got the device corrupt message. I did all of that a few times to make sure I didn't miss anything and I have no idea what it's detecting as modified. I haven't tried factory resetting from the device itself, I figured formatting userdata would be enough but ill try that tomorrow unless anyone has other ideas.
I had this same issue today too after I flashed twrp. The only way to resolve it was to flash stock and unroot using nexus toolkit to a lollipop stock image. In time I'm sure it will be a smoother process to go to android m with twrp and root, but until then, I'm sticking with lollipop.
Sent from my Nexus 6 using Tapatalk
530farm said:
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
Click to expand...
Click to collapse
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Well, the issue is this corrupted message stays even after the full stock reinstall. Some say it went away after the factory reset but returned back after a while later, after spontaneous reboot or so.
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
What I've done to get back to stock was - flash clean image and next factory reset. No corrupted message. So far so good.
I believe to get rid of it...you will have to lock and unlock bootloader again...which will factory reset in the process. Hopefully someone finds a workaround for a factory reset...I am going to continue to run it with the error message until someone does. I dont want to factory reset. The message doesnt cause any issues to my knowledge...its just a warning to the user.
dansoh said:
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Click to expand...
Click to collapse
kidhudi said:
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
Click to expand...
Click to collapse
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
inspiron41 said:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
Click to expand...
Click to collapse
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
I flashed the kernel from here http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958 and it went away.
PhantomGamers said:
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
Click to expand...
Click to collapse
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
djkinetic said:
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
Click to expand...
Click to collapse
I guess I'll have to resort to that if factory resetting doesn't fix it, sucks though cuz I would have been happy with stock.
I somehow managed to soft brick my N6 using NRT to flash 6.0 factory image. At the time, N6 was stock no root. It will not boot past the Google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...I l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no OS loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 XT1103 64GB
nexus 6
dray said:
i somehow managed to soft brick my n6 using nrt to flash 6.0 factory image. At the time, n6 was stock no root. It will not boot past the google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...i l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no os loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 xt1103 64gb
Click to expand...
Click to collapse
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
dray said:
I somehow managed to soft brick my N6 using NRT to flash 6.0 factory image. At the time, N6 was stock no root. It will not boot past the Google boot screen. I have tried factory/data reset, clearing cache, and manually flashing fastboot files which fail at system.img during process...I l am also getting a "target reported max download of 5326722560 bytes" message prior to every file flash but it seems to complete. I currently can boot into bootloader and customer recovery....no OS loaded at the moment. Any assistance would be greatly appreciated...
Nexus 6 XT1103 64GB
Click to expand...
Click to collapse
Whats the system.img failure? Is it that it's too big? If so, your fastboot is out of date Update it to the latest.
drizzel57 said:
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
Click to expand...
Click to collapse
Nothing you can do. Send it for repair. There is no fix.
Ok I followed this tutorial to a tee and it worked like a champ:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
drizzel57 said:
i have the same problem . I tried nrt and cannot get the bootloader to unlock, only thing is i am rooted. No os loaded at the time either on teamwin.
Click to expand...
Click to collapse
My situation was a little different...I managed to unlock bootloader and load custom recovery before things went a little wonky
dray said:
Ok I followed this tutorial to a tee and it worked like a champ:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I nay have jut foudn the culperate, i flashed the ewer 7.1.1 onto my ohne afte factory resttubg then i rebooted anyeverthing was greatso i decided to go back int recovery and fkash thaoks for the 7.1.1 ans the enwest auperau 79, or whicher its at now
Valhalla875 said:
I nay have jut foudn the culperate, i flashed the ewer 7.1.1 onto my ohne afte factory resttubg then i rebooted anyeverthing was greatso i decided to go back int recovery and fkash thaoks for the 7.1.1 ans the enwest auperau 79, or whicher its at now
Click to expand...
Click to collapse
Wow dude... Now that was one hell of a hard to read post...
5.1 said:
Wow dude... Now that was one hell of a hard to read post...
Click to expand...
Click to collapse
You instantly made me laugh. I almost forgot about looking a solution for my problem
Hi,
I'm hoping for some suggestions regarding my boot looping Nexus 6. Here's the details:
- Brand new device.
- First boot & setup. OK.
- Unlocked bootoader. OK.
- Reboot back into 5.0. OK.
- Tried to flash 6.0, initially using flash-all.bat from shamu-mra58k-factory-5b07088c.tgz. Failed.
- Extracted zip inside shamu-mra58k-factory-5b07088c.tgz and flashed all .IMG manually.
- Phone now stuck in boot loop. Google logo appears, sits there for 5-10 seconds then reboots.
I so far have tried:
- Multiple reflashes of 6.0 factory image. Boot loop remains.
- Multiple flashes of 5.1.1 factory image. Boot loop remains.
- Tried flashing Cyanogenmod cm-12.1-20151021-NIGHTLY-shamu.zip via recovery. Flash successful. Boot loop remains.
- Flashing gpt.bin and reflash 6.0 images. Boot loop remains.
This is the first time I've encountered issues. I've successfully flashed factory images to my Nexus 4 many times over the
last couple of years.
Does anyone have any suggestions re a fix, if at all possible? Any tips/suggestions would be greatly appreciated!
If i need to return it, should I flash to 6.0 and lock? Will they be able to tell that the bootloader has
been unlocked previously?
Thanks!!
I recovered mine in a bootloop with wugfresh bootloop option ticked.
Sent from my Nexus 6 using XDA Free mobile app
yes, i do have a suggestion.. do not use flash-all. flash each partition individually. flaah-all is kinda broken and is not flashing the system.img.
Use this guide
http://forum.xda-developers.com/showthread.php?t=2954008
Use method two. As @simms22 said flash all is kinda borked on n6.
Sent from my Nexus 6 using Tapatalk
seeker02uk said:
I recovered mine in a bootloop with wugfresh bootloop option ticked.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hi @Seeker02u,
I've tried that a couple of times, no luck. Thanks for the suggestion anyway!
Hi @toknitup420,
I've run through method two numerous times this week with no success. It's still gets stuck on the Google logo and reboots. Thanks for the suggestion and link.
toknitup420 said:
Use this guide
http://forum.xda-developers.com/showthread.php?t=2954008
Use method two. As @simms22 said flash all is kinda borked on n6.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hi @simms22,
I've run through the flashing process manually flashing each .img individually a number of times now, all without success.
simms22 said:
yes, i do have a suggestion.. do not use flash-all. flash each partition individually. flaah-all is kinda broken and is not flashing the system.img.
Click to expand...
Click to collapse
davisco98 said:
Hi @simms22,
I've run through the flashing process manually flashing each .img individually a number of times now, all without success.
Click to expand...
Click to collapse
good, im glad that you finally got it
Uh hey hang on! I'm having the same problem, and I'm going to try your suggestion in lieu of a better option, but reread his reply. He said it DID NOT work for him. ("withOUT success")
My SIM-less Nexus 6 (which I'd previously flashed to MRA58X from 58K using the Wugfresh NRT) got the download notification re. the 6.0.1 update last night. It got that notification 3X, and the install failed each time. My attempts to sideload the OTA link version to MMB29K from MRA58X also failed multiple times, evidently because of a "non-standard" release key. Here's the error message:
Package expects build fingerprint google/shamu/shamu:6.0/mra58x/2353551: user/release-keys or google/shamu/shamu:6.0.1/mmb29k/2419427:user/release-keys;
this device has google/shamu/shamu:6.0/mra58k/2256973:user/release-keys
Error in @/cache/recovery/block.map (Status 7)
Right now, I really just want to know a couple of things:
What's a release key?
Why would my MRA58X phone be using a 58K release key?
Is there any way to find out if my now MMB29K phone is also using a "bad" release key?
It's an unrooted and unlocked Nexus 6. The only modification-like thing that I've done to it is flash factory images to it using the Wugfresh NRT. I flashed it from LYZ28N to MRA58K , from MRA58K to MRA58X (after T-Mobile approved the X build), and finally from MRA58X to MMB29K.
well, if your system is moddified in any way, it will always fail. moddified does not only include root. you can always flash the factory image, not ota.
Can you flash a factory image over the top of a rooted 6.0? Or do you have to wipe first?
I'm kinda bummed lately, i just want to keep my root for adblock, but keeping the phone up to date is more of a chore than i remember back in the earlier nexus days.
propain4444 said:
Can you flash a factory image over the top of a rooted 6.0? Or do you have to wipe first?
I'm kinda bummed lately, i just want to keep my root for adblock, but keeping the phone up to date is more of a chore than i remember back in the earlier nexus days.
Click to expand...
Click to collapse
Just flash the factory image (no need to do any wipe).
I too am having trouble updating to 6.0.1 with root/ custom kernel. I am flashing factory image via fastboot but fails everytime flashing system image. "unknown error" I feel like a dang noob...lol
dray said:
I too am having trouble updating to 6.0.1 with root/ custom kernel. I am flashing factory image via fastboot but fails everytime flashing system image. "unknown error" I feel like a dang noob...lol
Click to expand...
Click to collapse
unzip the factory image, then flash each part separately. flash-all is broken.
simms22 said:
unzip the factory image, then flash each part separately. flash-all is broken.
Click to expand...
Click to collapse
I'm sorry I should have been more clear. Yes that is what I am doing. Unzipped and flashing manually. Everything flashes just fine except system.img ?
dray said:
I'm sorry I should have been more clear. Yes that is what I am doing. Unzipped and flashing manually. Everything flashes just fine except system.img ?
Click to expand...
Click to collapse
odd. thats tne way it always works, since flash-all is broken.
simms22 said:
odd. thats tne way it always works, since flash-all is broken.
Click to expand...
Click to collapse
Yeah IDK WTH is going on. I'm at a loss.
dray said:
I'm sorry I should have been more clear. Yes that is what I am doing. Unzipped and flashing manually. Everything flashes just fine except system.img
Click to expand...
Click to collapse
Update fastboot to the new one. The system img is too big for the old one.
istperson said:
Update fastboot to the new one. The system img is too big for the old one.
Click to expand...
Click to collapse
Yes good idea I will try this. Where do I get the updated fastboot files?
Well, I feel better knowing that I'm clearly not the only one who's clueless about release keys and their connection to OS updates.