Related
Is there a way to unlock and root and reflash stock software with out being able to use the screen??
Yes if you know how to use fastboot and adb
Oh well they're already overnighting me a new one.
Hey everyone, made a tutorial showing how to unlock the bootloader on your Nexus 9! I'll make rooting videos and more soon enough.
Hope they help.
How to unlock the bootloader:
https://www.youtube.com/watch?v=AJEORWbf658
How to root the Nexus 9:
http://youtu.be/5jwoPx5mB7Y
Unboxing and hands on:
https://www.youtube.com/watch?v=8K5WAmwRH7o
Doing it as soon as i get home .
That's the first nexus device I've seen that doesn't use Google's bootloader, very interesting!
Sent from my Nexus 10 using Tapatalk
Good news: You can unlock the bootloader under the development tab in settings. http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
lary50 said:
Good news: You can unlock the bootloader under the development tab in settings. http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Click to expand...
Click to collapse
Thanks for that, I kept getting permission denied. All is well now ?
I wonder what HTC means when they say ,"this *may* void your warranty" when unlocking the bootloader. Did the all the other nexus devices say that in the bootloader before they were unlocked?
Deltadroid said:
Did the all the other nexus devices say that in the bootloader before they were unlocked?
Click to expand...
Click to collapse
My nexus 4 did.
I guess it's fine as long as it's not being permanently marked with some bit set somewhere so their service department can see. The device can be locked again.
pantmunu said:
Doing it as soon as i get home .
Click to expand...
Click to collapse
same there but them i get it i will
Edit: no need to set up adb or fastboot
i have ubuntu haha
Deltadroid said:
I wonder what HTC means when they say ,"this *may* void your warranty" when unlocking the bootloader. Did the all the other nexus devices say that in the bootloader before they were unlocked?
Click to expand...
Click to collapse
They did. Although you can just type fastboot oem lock and it should relock the bootloader without wiping any data.
Will wait till root is available to unlock it
mk92595 said:
Will wait till root is available to unlock it
Click to expand...
Click to collapse
No way. Unlocking wipes the device, but rooting doesnt. I plan to unlock mine the second I get it. That way I can start loading data and stuff onto it and start using it. Then, when root is available, I don't have to wipe my data at that point to do it becuase I was already proactive about unlocking the bootloader.
qbking77 said:
Hey everyone, made a tutorial showing how to unlock the bootloader on your Nexus 9! I'll make rooting videos and more soon enough.
Hope they help.
How to unlock the bootloader:
https://www.youtube.com/watch?v=AJEORWbf658
Unboxing and hands on:
https://www.youtube.com/watch?v=8K5WAmwRH7o
Click to expand...
Click to collapse
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
berendspruijt said:
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
Click to expand...
Click to collapse
Same there win 8
But I unlocked it
On Ubuntu
berendspruijt said:
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
Click to expand...
Click to collapse
If you're on Windows, it could be a driver problem. You can check on it in Windows device manager. If you need to install the driver, Open the Android SDK manager and make sure the USB driver is installed, and install any available updates. If that doesn't work, you can find the Google nexus USB driver by itself and install it using the windows device manager. You can search for the relevant step by step guides here on the forum or elsewhere online.
mrkvchm said:
No way. Unlocking wipes the device, but rooting doesnt. I plan to unlock mine the second I get it. That way I can start loading data and stuff onto it and start using it. Then, when root is available, I don't have to wipe my data at that point to do it becuase I was already proactive about unlocking the bootloader.
Click to expand...
Click to collapse
I already installed everything I need. also with ADB you can backup apps easily.
mk92595 said:
I already installed everything I need. also with ADB you can backup apps easily.
Click to expand...
Click to collapse
But you'll have to reinstall everything when you unlock the bootloader. I know its not hard to do with ADB, but I don't understand why you'd bother backing up and restoring everything when you can just unlock the bootloader right away and save yourself from wiping to root once you're already established on the device. Well, to each his own I guess.
If i unlock my nexus9 do i still get android OTA's?
hill67 said:
If i unlock my nexus9 do i still get android OTA's?
Click to expand...
Click to collapse
Yes
mrkvchm said:
But you'll have to reinstall everything when you unlock the bootloader. I know its not hard to do with ADB, but I don't understand why you'd bother backing up and restoring everything when you can just unlock the bootloader right away and save yourself from wiping to root once you're already established on the device. Well, to each his own I guess.
Click to expand...
Click to collapse
I already have my Nexus 9. Everything is already installed.
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.
Hi,
I have the OnePlus 5 8GB.
I unlocked my bootload, rooted my phone, all good.
But then I realized android pay is not working with rooted phones, so i wanted to undo it.
for some reason i ran this because i found it in a guide to lock the bootloader again (yes, it was was stupid):
./fastboot flashing lock
After that i got the message that my device is corrupt and cant boot. So i ran ./fastboot oem unlock and that message disappeard.
I tried booting, but nothing happend for 10 minutes, still boot animation. so i went into fastboot, flashed twrp and tried doing a factory reset, but whatever i do, I get tons of these error messages:
Updating partition details...
Error opening: '/data/misc/[...]
Error opening: '/data/user_de/0/[...['
(No such file or directory)
What can I do?
I can even ADB sideload because of those errors.
edit:
also it shows nothing for bootloader version or baseband version in the fastboot screen.
https://imgur.com/a/z2KN3
doesnt look good. cant copy anything to device or from device
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Eric214 said:
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Click to expand...
Click to collapse
Anything I should do to have them not reject the RMA?
thx for the Magisk advice, using it now.
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
TheCorax said:
Anything I should do to have them not reject the RMA?
Click to expand...
Click to collapse
Since it's obvious someone tampered with the software, they may reject it.
You don't lose warranty if you root, but they won't cover the cost if anything happens to it due to the user's intervention.
If you manage to get the stock ROM onto the phone, you may be able to flash it from TWRP.
TheCorax said:
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
Click to expand...
Click to collapse
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
elbuenzurdo said:
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Yes it works again. That what I meant by android is launching.
TheCorax said:
Yes it works again. That what I meant by android is launching.
Click to expand...
Click to collapse
How do you do to get your device recognized? I have a similar problem for that command. But muy device just turned off and doesnt do nothing, Im trying flash it but nothing atm.
I have a leeco le s3 x626
I'm searching all over the internet for a method to root this damned phone. All of the thread that i saw mention to unlock the bootloader but, apparently, there was an official method before but now it's not available anymore. I'm struggling to find even the drivers for this phone. There is an updated guide?
I am also suffering bro. please inform if you get to know anything about unlocking bootloader of this phone for free.
mahesh_gupta said:
I am also suffering bro. please inform if you get to know anything about unlocking bootloader of this phone for free.
Click to expand...
Click to collapse
I'm also struggling. I have one of these and I'm not sure if DC-Unlocker still works or not, because I'm having issues with the correct drivers. I have the right drivers for fastboot, but not for regular adb mode. The phone always registers as CDC Serial