Related
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things
jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.
The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App
xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App
Thanks for the clarification. I'll do some more reading in the dev section
Thanks a lot, this really helped me out a lot. I will proceed to rooting
So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
I'm no expert at all but I ran motoapocolyps and if didn't do anything. It will either fail and your phone will be fine or, depending on what update you last took, unlock it. My phone is past due for unlocking the bootloader unless there is a way to downgrade it.
Hi
aviwdoowks said:
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
Click to expand...
Click to collapse
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
aviwdoowks said:
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
Click to expand...
Click to collapse
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
RikRong said:
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
Click to expand...
Click to collapse
"You can't cover up a BL unlock." <- THANK YOU! That is what I was trying to confirm....
I was thinking that since you can do this to cover up the unlocked bl warning: http://forum.xda-developers.com/showthread.php?t=1901444
that you can also do something to cover up the AP screen as well.
Since I'm rooted, and this phone is supposed to get 4.4, I'm not too upset that I can't unlock (Though with 4.4 I'll probably lose root ).. The stock rom is pretty nice on these, and root gives me pretty much anything I want for customization.
Thanks!
dreamersipaq said:
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
Click to expand...
Click to collapse
I am the one confused! I need to learn my codes.
Is it possible to re-lock and unlocked bootloader?
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Reason I ask is because I had it unlocked, got an OTA update from Verizon for kitkat, and soft bricked my phone. Got stuck in a boot loop with the unlocked bootloader warning message.
I just flashed back to 4.0.4 using RDS Lite 6.1.4. Id like to reset the boot loader to locked before updating to kitkat again.
It's not possible to re-lock. I've updated to KK and can confirm that the BL is, in fact, still unlocked.
I have read somewhere that when you unlock the bootloader, it actually physically blows some kind of physical fuse. or maybe I miusread it.
Someone had made a special logo.img you can flash to get rid of that message.
Although if you really want a locked BL phone, I'd be more than happy to trade you.
MxPhenom 216 said:
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Click to expand...
Click to collapse
Not that it helps, but in Australia, we do not get the nasty warning message after unlocking the bootloader. And I think that the phones are actually sold with an unlocked bootloader.
GnatGoSplat said:
Although if you really want a locked BL phone, I'd be more than happy to trade you.
Click to expand...
Click to collapse
:laugh:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Mohit M'S said:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Click to expand...
Click to collapse
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
DJBhardwaj said:
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
Click to expand...
Click to collapse
Your device is corrupt and can't be checked for corruption
Mohit M'S said:
Your device is corrupt and can't be checked for corruption
Click to expand...
Click to collapse
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Device is locked
Mohit M'S said:
Device is locked
Click to expand...
Click to collapse
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
DJBhardwaj said:
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
Click to expand...
Click to collapse
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Mohit M'S said:
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Click to expand...
Click to collapse
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Heisenberg said:
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Click to expand...
Click to collapse
OK OK but after unlocking it there is any way to relock it and remove this error message
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, of course. Infact that's the reason I asked you about the lock status on the first place. Stock ROM with locked bootloader shouldn't give this warning. It should make it go away.
That is why, I asked you to perform a flash manually. Please refer to Heisenberg's guide for the steps.
Here is the link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, after locking the bootloader the message should disappear. But, I'd strongly recommend leaving it unlocked and just dealing with the message. If an OTA ever fails or something else goes wrong you'll need fastboot to flash the factory images to recover your device, you'll be forced to unlock the bootloader, this will wipe the device and you'll lose all of your data because there'll be no way to back it up first.
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Sorry message is Device can't be trusted or it may not work properly
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
Did you reflash manually?
DJBhardwaj said:
Did you reflash manually?
Click to expand...
Click to collapse
Nope gonna do this by today or tomorrow
Mohit M'S said:
Nope gonna do this by today or tomorrow
Click to expand...
Click to collapse
Sure and then let us know. And keep the bootloader unlocked, it will help you to deal with a few issues (if any), in the future, as already mentioned above by Heisenberg.
-_____- why do people still use toolkits? Try getting use to Adb; it would save you a lot of time dealing with errors.
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
uicnren said:
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
Click to expand...
Click to collapse
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..??
Ruined my phone
Mohit M'S said:
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..
Ruined my phone
Click to expand...
Click to collapse
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
uicnren said:
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
Click to expand...
Click to collapse
U didn't understand what I said I have already reverted my to stock ROM and relocked the bootloader but even then message is coming device can't be trusted or may not work properly and I'm not even getting any updates not even April update and all friends got this I'm currently pure stock
Problem are:-
Message is still there
Updates r not coming
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.