Related
i have to send my phone back to LG (or Google? not sure which one its actually going to end up at) because of overheating issues. they're sending me a replacement tomorrow with a shipping label for my old one to send back. they're holding funds for my new one until they've checked over the old one an verified that i do need a replacement, then if its all good they release the funds back into my account, but if its not all hunky dory they take the money, and i really can't afford that. i had it rooted and the bootloader unlocked and a custom kernel. i've flashed the stock kernel, unrooted and checked with Root Checker Basic, which tells me "Sorry! This device does not have proper root access". I've re-locked the bootloader, and checked that as well. I've flashed a few different things, including mod that makes the screen more sensitive, i've reverted that now though as it was to sensitive. i've also flashed lots of different ROMs including CyanogenMod, AOKP, Paranoid Android (i think thats the name) and more, a few weeks ago i flashed back to the stock rom, because i found problems with all the other ones. please ask if you need more information. back to the original question: will LG, or Google, whoever it goes to, be able to know that any of that has been done?
Thanks, Raf
rafspeik said:
i have to send my phone back to LG (or Google? not sure which one its actually going to end up at) because of overheating issues. they're sending me a replacement tomorrow with a shipping label for my old one to send back. they're holding funds for my new one until they've checked over the old one an verified that i do need a replacement, then if its all good they release the funds back into my account, but if its not all hunky dory they take the money, and i really can't afford that. i had it rooted and the bootloader unlocked and a custom kernel. i've flashed the stock kernel, unrooted and checked with Root Checker Basic, which tells me "Sorry! This device does not have proper root access". I've re-locked the bootloader, and checked that as well. I've flashed a few different things, including mod that makes the screen more sensitive, i've reverted that now though as it was to sensitive. i've also flashed lots of different ROMs including CyanogenMod, AOKP, Paranoid Android (i think thats the name) and more, a few weeks ago i flashed back to the stock rom, because i found problems with all the other ones. please ask if you need more information. back to the original question: will LG, or Google, whoever it goes to, be able to know that any of that has been done?
Thanks, Raf
Click to expand...
Click to collapse
No, if you flashed a factory image and the bootloader is locked they can`t tell what you flashed in the past .
gee2012 said:
No, if you flashed a factory image and the bootloader is locked they can`t tell what you flashed in the past .
Click to expand...
Click to collapse
i was reading this http://forum.xda-developers.com/showthread.php?t=1580829&nocache=1 and on the third post, bzmotoninja83 says that modern phones can detect bootloader locks/unlocks
rafspeik said:
i was reading this http://forum.xda-developers.com/showthread.php?t=1580829&nocache=1 and on the third post, bzmotoninja83 says that modern phones can detect bootloader locks/unlocks
Click to expand...
Click to collapse
Nope, not afaik. Samsung has binary flash counters (which can be reset though). Nexus devices don`t have that. So they look at the device as it comes in, not rooted and a locked bootloader.
gee2012 said:
Nope, not afaik. Samsung has binary flash counters (which can be reset though). Nexus devices don`t have that. So they look at the device as it comes in, not rooted and a locked bootloader.
Click to expand...
Click to collapse
great! thanks for your help
Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
It does "fix" the bootloader unlock exploit though
http://www.droid-life.com/2013/07/1...the-kernel-exploit-for-unlocking-bootloaders/
scoobaspeaz said:
Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
Click to expand...
Click to collapse
So, stock recovery to install this?
I would assume you would need to be 100% stock, including the recovery, to install this.
scoobaspeaz said:
I would assume you would need to be 100% stock, including the recovery, to install this.
Click to expand...
Click to collapse
hmm put it on my internal storage and its not found, I think stock recovery wants to see it on a sdcard.
If your boot loader is unlocked before the update, it should stay unlocked. You just will not be able to unlock with methods out there now.
Sent from my Razr HD using xda app-developers app
I received the OTA today on my Max HD. It was build 9.18.79.
Sent using xda premium
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1
Thanks for the reply! A few more questions if you don't mind (would hate to do something wrong... like I did last time... luckily I was able to revert back to an original version and fix the install... sigh...):
4) With protecting root, I need the SuperSU Pro version, yes? To be able to use the survival mode, yes? Will Voodoo OTA Rootkeeper do the same thing? Is it possible to use both "to be sure"?
5) I have everything backed up with Titanium Backup. Should I bother getting the pro version and backing everything up using the cloud backup and hypershell? Or won't this matter since if root doesn't keep I won't be able to use Titanium Backup?
6) I also have performed the VZW Wireless Hotspot hack using SQLite. Am I going to have to undo the hack in order for the OTA update to work?
Thanks again for all your help!
Update - I decided to attempt the update and hope for the best. System update 9.18.79.xx updating from 9.16.6.xx.
I purchased the SuperSU Pro from the Play Store, and used the survival mode in SuperSU. I also used the Voodoo OTA Rootkeeper and protected root. I figured if one didn't work the other might... Voodoo worked to protect and re-install root access (not sure about SuperSU as I tried Voodoo first to restore root after the install).
I am unsure if the bootloader is still unlocked, but from what people have said there doesn't seem to be a reason to believe it is re-locked. I haven't tested it out to know for sure though.
It appears that the entire update installed correctly. No errors, and the baseband version was updated to the new radio (xxx.15P).
I did not undo the VZW Wireless Hotspot hack prior to installing the update.
Hopefully this post helps others out there.
My final question... what does updating the radio/baseband do exactly?
i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options
rodmc123 said:
i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options
Click to expand...
Click to collapse
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
KachowPow said:
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1
Click to expand...
Click to collapse
So any idea how one might fix this?
LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
I tried to take the 9.18.79 update I protected the root (I'm not unlocked) before I did so I also temporarily un-rooted (I've always been told to do this before and update) Now I an no longer rooted and it can't find any SU binary codes. Gonna have to flash back to 9.6.16 and try it again I guess or stay on 9.6.16 in order to maintain root for now. If you find a solution please share.
IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
I agree with Lenny. This same thing happened to me when I tried to take the liquid smooth ROM. Follow his instructions above. You'll lose all your pics, vids, files, etc. But at least you'll have a working phone again.
Went smoothly here
All my devices except this one are rooted and some are rom'd. I thought long and hard about whether to void this warranty but decided one day it would be out of updates from VZW and I would want to flash something. I have been denying the OTA for the last day so I figured now or never.
Here are the simple steps:
Download and install Moto device manager (for the USB drivers) here
Enable USB debugging in developer options on the phone
run motochopper here
run motoapocolypse here
install voodooOTA root keeper from Play and backup root
apply OTA
It went error free. The phone has the 15P radio update, unlocked BL and root.
larsdennert said:
It went error free. The phone has the 15P radio update, unlocked BL and root.
Click to expand...
Click to collapse
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?
bananapeapod said:
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?
Click to expand...
Click to collapse
Yes, the bootloader won't get locked again after it is unlocked. Moto would be shooting themselves having to reinstate warranties if they did that. Yes I wanted the option of flashing later becuase the ota will install sooner or later. I also want to stay on the upgrade path for now to have current radios.
I still have an Eris lying around that is long out of support but i have gb on it.
IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
that's what i want to do, but i cant because my power button is broken! so i cant enter to fastboot mode without the power button.. i will have to open my phone and try to fix the power button myself.
Just to make a point and to clear up any confusion, this Update will not lock the Bootloader. If you have an Unlocked Bootloader then you will have an Unlocked Bootloader after the update, regardless if it fully works or not, and even if you lose Root, the Bootloader will still be Unlocked. If Root is lost with an Unlocked Bootloader, I suggest downgrading through an FXZ of either 9.16.6 or 9.16.9 and restore Root.
My Galaxy S4 stopped working and I'm planning to send it back to get a replacement. However, I rooted my phone before this happened and I'm planning to un-root it before sending it back. I was planning on using the Triangle Away app as well to reset the flash counter but apparently I need to unlock the bootloader first. I read in this thread that you can flash a recovery and root the phone at the same time.
Would using that tool help me in unlocking the bootloader so that I can use the Triangle Away app to reset the counter and un-root my phone using Odin afterwards? The topic creator mentioned that TWRP will auto-lok anything you flash and works as a bootloader unlock but can anyone confirm this? I bricked my Galaxy S3 two weeks ago and don't want to face the same problems with this newly aquired Galaxy S4.
Is it worth it to go through all the trouble to just reset the flash counter or would un-rooting the phone be enough to send the phone back for a replacement?
http://forum.xda-developers.com/showpost.php?p=42320414&postcount=2
Thanks, that guide looks really helpful. I do have one question though, it seems the Triangle Away app needs the boot loader unlocked in order to run successfully on the AT&T Galaxy S4 so what would be a good and simple way to unlock the bootloader and is there a way to check whether or not mine is unlocked? Would running the CASUAL tool take care of this (even if my device is already rooted)?
What guide/method did you use to root? Did you not use the bootloader exploit at that time?
I used the Motochopper tool located on this thread. I hadn't researched enough to know about the CASUAL tool at the time
Un-Rooting
Zernell said:
I used the Motochopper tool located on this thread. I hadn't researched enough to know about the CASUAL tool at the time
Click to expand...
Click to collapse
Go Here to unroot without flashing
http://androidtechy.com/index.php/2013-04-28-19-55-53/how-to-diy/48
pharrisworth said:
Go Here to unroot without flashing
http://androidtechy.com/index.php/2013-04-28-19-55-53/how-to-diy/48
Click to expand...
Click to collapse
Hmm...yeah I can see that method would probably work, but that wouldn't reset the flash counter to 0 would it? If the seller happens to notice that, then they won't send me a replacement and will probably tell me my warranty is void; hence why I'm trying to get the Triangle Away app to work but need the boot loader unlocked first in order to do that.
Un-Rooting
Zernell said:
Hmm...yeah I can see that method would probably work, but that wouldn't reset the flash counter to 0 would it? If the seller happens to notice that, then they won't send me a replacement and will probably tell me my warranty is void; hence why I'm trying to get the Triangle Away app to work but need the boot loader unlocked first in order to do that.
Click to expand...
Click to collapse
Well if all you did was ROOT the flash counter shouldn't be affected. Iused the same tool. I took the additional step of replacing Superuser with SU user. to rid myself of the "custom" unlocked symbolon boot up. However, the phone was NEVER really unlocked.
Thanks for the replies! I managed to un-root the phone by just flashing the AT&T stock firmware using Odin. Hopefully the binary counter won't be an issue.
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.
Hello
My son used an S4 years ago, and now I want to use it as my daughter's first phone. I booted the phone, and found all kinds of things from 2017. I also see that the phone is rooted on software I337UCUGOK2 with Android 5.01.
We're using Simple Mobile, so I would like to use it.
1. Can I simply insert the simple mobile sim? When I booted the phone, I saw a Samsung logo and an unlocked lock image. So I either have the bootloader unlocked or it's sim unlocked; it's been a while.
2. Being on Android 5, I'd like to bring it up to a recent version. I see that Lineage 16 is out. Can I flash that?
Thank you
nabril15 said:
Hello
My son used an S4 years ago, and now I want to use it as my daughter's first phone. I booted the phone, and found all kinds of things from 2017. I also see that the phone is rooted on software I337UCUGOK2 with Android 5.01.
We're using Simple Mobile, so I would like to use it.
1. Can I simply insert the simple mobile sim? When I booted the phone, I saw a Samsung logo and an unlocked lock image. So I either have the bootloader unlocked or it's sim unlocked; it's been a while.
2. Being on Android 5, I'd like to bring it up to a recent version. I see that Lineage 16 is out. Can I flash that?
Thank you
Click to expand...
Click to collapse
To answer your questions:
1. Yes just insert the SIM. The unlocked image on boot up just means you're rooted and/or running a custom TW ROM.
2. You are stuck with lollipop. Only an S4 running the old MDL firmware can boot lineage OS due to a flaw exploit which was patched in later firmware. All other firmwares are locked and yours is one of them.
StoneyJSG said:
2. You are stuck with lollipop. Only an S4 running the old MDL firmware can boot lineage OS due to a flaw exploit which was patched in later firmware. All other firmwares are locked and yours is one of them.
Click to expand...
Click to collapse
Thanks a lot stoney. And I have no way of going backwards, I presume?
nabril15 said:
Thanks a lot stoney. And I have no way of going backwards, I presume?
Click to expand...
Click to collapse
No problem. And you are correct, once the phone has been updated past the MDL firmware, there is no going back. Check Ebay, you might be able to find one still on the MDL firmware. I have an AT&T S4 that's still on the MDL firmware that I bought off Ebay. If you find one, I have a guide here in the forums that covers how to operate the MDL firmware and such.
@StoneyJSG or anyone
Might you know how I can clear dalvik cache? I don't have twrp installed, and that's the only way that I know how to.
Can I simply erase the contents of the /data/dalvik-cache directory?
nabril15 said:
@StoneyJSG or anyone
Might you know how I can clear dalvik cache? I don't have twrp installed, and that's the only way that I know how to.
Can I simply erase the contents of the /data/dalvik-cache directory?
Click to expand...
Click to collapse
If you have root, you can use an app called root cleaner. It has an option to clear dalvik.