Related
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .
1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update
sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.
There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM
neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.
Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.
This is new: http://www.androidpolice.com/2015/08/05/google-announces-new-update-policy-for-nexus-devices-including-monthly-security-patches-for-3-years-and-major-otas-for-2-years-from-release/
That would be a real pain for us rooted users....but I guess the security patches are a good thing
A real pain...
Sent from another Nexus..
6...
No pain, it literally takes minutes to flash stock, update, root using the toolkit. [emoji1]
I wonder if there are again going to be separate builds for each carrier.
meldroc said:
I wonder if there are again going to be separate builds for each carrier.
Click to expand...
Click to collapse
That's a good point...maybe?
I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!
ArmoredCavalry said:
I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!
Click to expand...
Click to collapse
There is, stay stock or learn how to manually update to new versions. It's quick to do.
Xplicit84 said:
There is, stay stock or learn how to manually update to new versions. It's quick to do.
Click to expand...
Click to collapse
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.
ArmoredCavalry said:
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.
Click to expand...
Click to collapse
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.
Xplicit84 said:
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.
Click to expand...
Click to collapse
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?
ArmoredCavalry said:
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?
Click to expand...
Click to collapse
I would also like that if it was possible...
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
and that's exactly what I am going to do...
hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
jj14 said:
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?
ArmoredCavalry said:
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?
Click to expand...
Click to collapse
Is there a chance that google will publish a new Nexus factory image that can't be rooted? Sure - in theory, that is possible. But unlikely.
Till date, all nexus devices have been rooted (thanks @Chainfire)
jj14 said:
. . . Your phone will need to be stock (unrooted) to apply the OTA.
. . . use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Recently I used both methods just to see if there were differences.
Both had the same results. That means among others that my settings were gone.
- LCD_density defaults (384)
- WiFi interval defaults (was 200)
- Needed to flash Black Google Now Launcher and uninstall Google.app updates to get my black background back.
When this happens every month . . . [email protected]#$%&
jj14 said:
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?
Does google always post a whole new image for each ota? What about the carrier variants like tmobile? Is there a new image for each ota?
Thanks. I'm not a N6 owner yet but I plan to be stock rooted and am trying to determine the ota update process in advance.
@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images
cam30era said:
@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks cam30era. I was a bit concerned that being a stock rooted device might be too much trouble, especially with the security updates. But this looks manageable to me.
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Vref said:
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Click to expand...
Click to collapse
Have you tried switching ports?
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
DJBhardwaj said:
Have you tried switching ports?
Click to expand...
Click to collapse
Nope...didn't think that would be an issue but I can always try.
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
mgrass said:
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
Click to expand...
Click to collapse
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
You're talking about flashing the factory images with fastboot, he's talking about sideloading the full OTA.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Heisenberg said:
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Click to expand...
Click to collapse
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Vref said:
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Click to expand...
Click to collapse
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Vref said:
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Click to expand...
Click to collapse
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Dunno how or why it finally took but this isn't the first time I've had to switch from port to port (like a drunken sailor) to get it to see the phone but I've always attributed that to Android File Transfer being a little b!tch. I can tell you when I restored from Pure Nexus and relocked the bootloader two weeks ago it worked 4.0....not a clue as to why it got all fussy today.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
billamin said:
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
Click to expand...
Click to collapse
Cool. Glad you got it working.
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!
Huntereb said:
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!
Click to expand...
Click to collapse
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
I haven't tested on modern phone but i know that if you want to install successfully an OTA update you need: 1) stock recovery (with TWRP it will fail) 2) an untouched system partition (you must install supersu in systemless mode).
Another way is via flashfire from the play store.
Hope this could help you
luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yeah, you're wrong
Enviado desde mi XT1681 mediante Tapatalk
Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can still take OEM updates even if you have unlocked your bootloader. Your phone needs to have stock rom and stock recovery. Since you installed TWRP, its failing to update. Flash stock recovery image and you'll be able to update just fine.
luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yes it has but that feature no name like onekey navigation....you can set in fingerprint gesture menu whatever you want
I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?
welp11 said:
I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?
Click to expand...
Click to collapse
You will get all updates via OTA:highfive:, the unlock of bootloader won't prevent you to get updates:laugh:
In extrema ratio flash via fastboot but you won't need that:good:
luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Wait, so if an ota rolls out, it'll fail. But you can manually flash with fastboot. But even after fastboot flashing, it'll still notify you that an update is waiting?? Even if you manually applied that update?
I'd rather not freeze the service as I do want to know when the next ota comes along that I'll want to flash.