When I try to acces recoveryPLAY or try to unlock the bootloader I get the "failed, phone must bee rooted" I just flashed everything to 2.3.3 before I was rooted and haad a unlocked bootloader, but relocked it to update OTA, now none of the fastboot stuff is working. Anyone have any ideas? I would really really appreciate any help.
You have to unlock the bootloader again. I had the same problem.
Sent from my R800x using XDA App
IfI could unlock the bootloader I would. The unlock code is not working. Its the same code I used over a month ago to unlock my bootloader before I relocked it to update.
Whether I am trying to unlock the bootloader or fastboot recoveryPLAY both come back with "failed, phone must be rooted".
Probably a silly question, but, do you have the unlock command line correct, and have you verified if fastboot is working properly? Try 'fastboot -i 0x0fce getvar version'. It should return a version number if fastboot is working properly.
Sent from my R800x using XDA App
Yes, I have checked everything 4 times and the fastboot getvar is showing the phone is connected. Even using flashtool to flash back to 2.3.2 then trying to use the fastboot commands gives the same results.
Is there a 2.3.2 .FTF files that has root embedded that I can try and flash and see if that works?
What does it say when you try to unlock the bootloader?
Sent from my R800x using XDA App
I have already listed what it says. "Failed, phone must be rooted".
This repsonse is for both commands to either unlock the bootloader or boot into recoveryPLAY.img
And yes my bootloader unlock code is correct when i type it in, and when I used it before the OTA to unlock my bootloader. So the code is the correct code.
That's very strange. If all your command lines are correct, and you are inputting the correct code, it should be working. I only got that message when trying to boot a recovery image without unlocking. Sorry, I don't know what to tell you now.
Sent from my R800x using XDA App
thats okay. I just really hate having no root access and a locked bootloader. I would at least like to have root so I can use TB. I appreciate your attempts to assist me. Thank you
Anyone have any ideas for a solution to this or why this is happening? Everyone else seems to be able to reroot and unlock the way they have always done, except for me nothing is working.....
Bootloader unlock request spits out this:
<bootloader> Unlock phone requested
FAILED <remote: oem unlock failed!>
finished. total tim: 0.003s
Is there a FTF file that has root embedded into it I can use with flashtool? Fastboot is not accepting my code lines for either recoveryPLAY or my attempts to unlock the bootloader.
bump.......
Just realized about 10 minutes ago the unlock code IWas using was for my old xperia play. I found the code that pertained to my current phone and it still gives me the same results.....damn
Can you try wontanserver to go back to 2.3.2?
never heard of it, is it free? Looks like its a website or something
wow.... I am so unintelligent sometimes. I have been fighting with getting this phones bootlaoder to unlock and then it came to me, I am not typing it in caps. So I did and BAM!!!!!! bootloader unlocked. Guess since the 2 months I last unlocked it my brain got soggy like a bowl of runny oatmeal
Ya its free and imho the easiest way to flash any stock firmware from every region. The wontanserver program has it all.
K, I will save that for later. Thank you.
IS your phone R8OOX? ask alejandrox -whatever his name is for you to unlock it
edit: glad you fixxed it
I finally got my bootloader unlocked last night. I was misinterpreting a "0" (zero) as a "O" as in Oh. Got my phone updated i 2.3.3 with root and bootloader unlocked. I would like to thank everyone for their help. Guess I should get me eyes checked.
Related
title says it all
thanks
If you didn't attempt to root it, it should be locked
Sent from my Xoom using XDA Premium App
I just bought mine from someone on craigslist...
Is there a way to tell if it has been unlocked
well heres what happened
i had unlocked and rooted the xoom then attempted to relock it.
relocking failed and bricked the device.
after about 3 hours of trying to figure out how to fix it going through numerous tries of rsd lite and unlocking and relocking i somehow got it to work so i dont know if it unlocked or locked.
i do not have superuser icon in my app drawer though
well ive booted into fastboot and tried the commands fastboot oem unlock and fastboot oem lock and both work so thats not a way to see if it works
im out of ideas
Around last week when I first got my carrier locked Xperia PLAY, I purchased a network unlock code which I was able to unlock it with. So, then I flashed it with the UK Generic .184 FTF file with FlashTool to get rid of all the junk that my carrier included with it and rooted it using the GingerBreak APK.
Now, my question is, since I've network unlocked my PLAY, completely debranded it and rooted it, would I be able to unlock my bootloader now? From what I've read, since my device was originally locked from my carrier, that it never had Fastboot installed on it, which is needed to unlock my bootloader. But I also read that being able to unlock the bootloader on my Xperia PLAY shouldn't even matter because it's already set to S=OFF. Could someone please enlighten me on this?
You can't unlock your bootloader with the current method, it depends on two things: can your phone connect with fastboot when in bootloader mode AND is your IMEI number registered with SE to get the required unlockcode.
No you can only unlock GSM phones ie sim fee none network locked ones, unlocking the sim carrier wont count sadly
svenk919 said:
You can't unlock your bootloader with the current method, it depends on two things: can your phone connect with fastboot when in bootloader mode AND is your IMEI number registered with SE to get the required unlockcode.
Click to expand...
Click to collapse
Yes, I went to their How-To page on the SE Developer's site and was able to get an unlock code by providing my IMEI and other info. When I try to detect it with Fastboot and my PLAY in bootloader mode, Fastboot just hangs at <waiting for device>.
waz000000 said:
No you can only unlock GSM phones ie sim fee none network locked ones, unlocking the sim carrier wont count sadly
Click to expand...
Click to collapse
Cool, thanks for confirming that!
But does it even matter if I'm able to unlock my bootloader? Because I've read somewhere that the PLAY's are set to S=OFF.
From my understanding an unlocked bootloader is necessary for costum roms, if you're content with root and themes unlocking the bootloader won't be that important to you I guess.
I'm pretty content with being able to install custom themes with it only rooted. But I want to be able to overclock it, and that involves flashing a custom kernel to be able to do so, correct?
Flava0ne said:
I'm pretty content with being able to install custom themes with it only rooted. But I want to be able to overclock it, and that involves flashing a custom kernel to be able to do so, correct?
Click to expand...
Click to collapse
afraid so (as it stands atm) there probably will be a way to flash without an unlock at some point though.
Hey there,
I have a few questions for owners of the Nexus 7 or anyone who is able to help me
1. When you fastboot oem unlock to unlock the bootloader, does the device get wiped? I ask because someone mentioned that the Galaxy Nexus from the play store no longer wipes when running that command.
2. When you unlock the bootloader, do you no longer receive OTA updates? and if not, does it just require a simple relock to get back in the update channel? This is mainly for my N7 but also as I recently sold my friend a Galaxy Nexus which I relocked the bootloader too, and I hope he can still get OTA updates for Jelly Bean and the likes.
Any help would be greatly appreciated,
Thanks in advance,
DarkRyoushii
Not sure on number one.
Number two is bootloader state has no effect on ota's
Thanks for the reply. I'm still really curious about the first question though. It would be great if it's the same as the play store nexus because then I won't be pressured to unlock the device when I first get it
Sent from my GT-I9300 using xda app-developers app
I unlocked mine before setup. So I don't know if it wiped anything.
Sent from my Nexus 7 using Tapatalk 2
is "unlocking the bootloader" another word for rooting then? Google results seem to suggest that when I looked up the term. "Unlocking the boot loader allows you to put custom ROMs on your phone" - from a Sonymobile Xperia site.
Salty Wagyu said:
is "unlocking the bootloader" another word for rooting then?
Click to expand...
Click to collapse
It's essentially step one of that process.
"Unlocking the Bootloader" is entirely different than "Rooting", although it is a prerequisite.
The Unlock operation will warn you that it will wipe the device - if it still does.
Anyone who unlocks should be able to tell us if they get that warning.
Unlocking the boot loader will wipe your device:
http://forum.xda-developers.com/showthread.php?p=28267712
'Note: You need to unlock the bootloader in order to use this Superboot. Note that the OEM unlock sequence wipes your device'
Sent from my HTC One X using Tapatalk 2
quick linux/android primer
A bootloader is a small program which directly interfaces with the hardware to load a secondary program. That secondary program can be either a second stage to a bootloader or the actual OS, in this case, android. An OEM locked bootloader will only load a secondary program which is approved by the OEM. It usually does this by signing the code with a digital signature. Unlocking the bootloader will allow unsigned code to be executed. This unsigned code can be Another ROM or an altered version of the existing ROM.
Rooting is the process of obtaining superuser access to the operating system, in this case, android. In Linux and android, the superuser is the only user which can execute certain programs or write to protected filesystems such as /system. It is desirable to have root access to the OS so that you can perform extra functions such as hardware configuration like overclocking the CPU speed.
Without an unlocked bootloader, you can not run the program required to gain root access. As well, you must gain permanent root so you don't lose access when the device reboots.
Hope this clears it up for you.
DarkRyoushii said:
Hey there,
I have a few questions for owners of the Nexus 7 or anyone who is able to help me
1. When you fastboot oem unlock to unlock the bootloader, does the device get wiped? I ask because someone mentioned that the Galaxy Nexus from the play store no longer wipes when running that command.
2. When you unlock the bootloader, do you no longer receive OTA updates? and if not, does it just require a simple relock to get back in the update channel? This is mainly for my N7 but also as I recently sold my friend a Galaxy Nexus which I relocked the bootloader too, and I hope he can still get OTA updates for Jelly Bean and the likes.
Any help would be greatly appreciated,
Thanks in advance,
DarkRyoushii
Click to expand...
Click to collapse
1. Yes, unlocking the bootloader does wipe your device.
2. Unlocking the bootloader and rooting "per se" doesn't prevent you from receiving any OTA updates (thanks albundy2010 for the clarification on this).
Just having root doesn't effect ota either
albundy2010 said:
Just having root doesn't effect ota either
Click to expand...
Click to collapse
You mean on the Nexus 7 or in general ? Because I've never been able to receive OTA updates in my phones while rooted.
Any nexus device for sure and just about every device that I know off.
Stock rooted roms will not have a issue with a ota. The issues come from custom roms?/ changes in /system that the updater script checks for etc.
Think about it for a second. All the I installed the update and lost root! How can I fix it topics. Ota root keepers and so on.
Root alone does not stop ota's. It is what the user ends up doing with root access that does
albundy2010 said:
Any nexus device for sure and just about every device that I know off.
Stock rooted roms will not have a issue with a ota. The issues come from custom roms?/ changes in /system that the updater script checks for etc.
Think about it for a second. All the I installed the update and lost root! How can I fix it topics. Ota root keepers and so on.
Root alone does not stop ota's. It is what the user ends up doing with root access that does
Click to expand...
Click to collapse
You're absolutely right, mate. I totally forgot about the fact I have custom roms in all my Nexus phones, hence my confusion.
Nexus 7 unlock bootloader problem
Hey guys,
I'm having issues unlocking the bootloader on my Nexus 7. I've followed instructions that I've seen all over the web. I have the latest SDK and google usb driver and USB debugging is enabled. I've rebooted both my PC and Nexus 7 with no success in running "fastboot oem unlock" which stays on "waiting on device." I did run "adb devices" and it lists my Nexus 7 by its serial number. Any help would be greatly appreciated.
rmm200 said:
"Unlocking the Bootloader" is entirely different than "Rooting", although it is a prerequisite.
The Unlock operation will warn you that it will wipe the device - if it still does.
Anyone who unlocks should be able to tell us if they get that warning.
Click to expand...
Click to collapse
How was the nook tablet rooted before the uboot exploit was discovered? Trying to understand more about these things.
Sent from my Nook Tablet using xda app-developers app
Unlocking the bootloader erases the userdata & cache. Here's what I got on command line:
E:\downloads\Android\androidsdk\platform-tools>.\fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 66.329s]
finished. total time: 66.331s
The new Device Protection features of Android 5.1 on the Nexus 9 and Nexus 6 can, in certain cases, cause you to have a bootloader which can not be unlocked.
Please have a read of the following links:
https://support.google.com/nexus/answer/6172890?hl=en
http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
What a pita
Sent from my Nexus 5 using XDA Free mobile app
i would never relock my bootloader
people unlock there bootloader for a reason
but to relock it after thats just wrong...
thats one of the things i hate about CM
they recommend you to relock your bootloader...
Agreed, why would you lock your bootloader unless sending in for repairs maybe?
But Google is really messing up the flow. The nexus 6 5.1 OTA is a mess right now but I will leave that for another thread.
Android 5.1 for Nexus 9? You must be joking.
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
No no you can still unlock it
But if you relock it that's the problem
disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
efrant said:
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
Considering this is a tablet, hopefully I won't lose or misplace it
Thanks, guys! Glad I stumbled across this thread before the thing arrived.
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
doitright said:
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
Click to expand...
Click to collapse
Example: I have a device running a stock ROM with no encryption, the stock recovery and a lock screen password. I happen to lose my phone. What happens to the photos of me dancing to Old Time Rock & Roll in my underwear that are stored on the device? If the bootloader is unlocked, someone just plugs it into a PC, boots TWRP and pulls them off. If the bootloader is locked, there is no easy way to see or get the photos off the device.
That is all I was saying about security. Nothing to do with you leaving your device somewhere or losing it, and then finding it again. Strictly about the personal content on the device.
efrant said:
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
bailyc said:
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
Click to expand...
Click to collapse
If you have never booted into Android, then you don't need to check that setting. As I said, that's the way I did it on my N6: take out of box -> charge -> boot directly into bootloader -> "fastboot oem unlock". No other steps required if you don't boot into Android first.
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
lilliput222 said:
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Click to expand...
Click to collapse
Yes, that should work for the N9 as well.
The bootloader on my Nexus 9 Android 5.1.1 is locked forever due to my mistake
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to check "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
quekl84 said:
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
Not possible. You will have to return it to HTC for repair or replacement.
quekl84 said:
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to uncheck "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
cobyman7035 said:
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
Click to expand...
Click to collapse
Yes, I forgot to check the box to allow oem UNLOCK. And now my device is locked forever.
A quick question: A lot of N9 ROMs require flashing an updated bootloader from the factory image. Aren't these bootloaders locked by default? Can we flash a factory bootloader over a custom ROM?
It seems that we might bork our Nexus 9s if we flash a locked bootloader in.
Hi .
Recently I have a phone from polish carier plus.
It worked fine ,but I wanted to have something more than a stock firmware.
Whad I have ?
Resurection Remix worked almost fine ,but nothing to touch me so i changed to Elemental room.
Version 1 almost worked fine (I tell about thist latter) but I wanted to get more and update to ver 4 .Something went wrong and I have a brick.
Erecovery not working
TWRP not working
Charging not working
Fastboot working ,but when i trying to flash twrp it says FAILED (remote: Command not allowed)
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
FFYDU17C08001043 fastboot
rafaelwasosz said:
Hi .
Recently I have a phone from polish carier plus.
It worked fine ,but I wanted to have something more than a stock firmware.
Whad I have ?
Resurection Remix worked almost fine ,but nothing to touch me so i changed to Elemental room.
Version 1 almost worked fine (I tell about thist latter) but I wanted to get more and update to ver 4 .Something went wrong and I have a brick.
Erecovery not working
TWRP not working
Charging not working
Fastboot working ,but when i trying to flash twrp it says FAILED (remote: Command not allowed)
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
FFYDU17C08001043 fastboot
Click to expand...
Click to collapse
you need to unlock your bootloader.
fastboot oem unlock <your_bootloader_code>
dlewando said:
you need to unlock your bootloader.
fastboot oem unlock <your_bootloader_code>
Click to expand...
Click to collapse
Thank You for Your response.
Unfortunatelly i dont have unlock code(i forgotten it ). The phone was unlocked before and i dont remember code.
Any ideas? Please.
Or maybe try to crack it? How long is the code? I remember that was only numbers so.... How many attemp I have to unlock before it lock for ....?
I`ve tried to reverse what i done .And it was because i format system partition to ext4 .Any box ideas how to put that nice phone to working order.....?
I dont have code ,but maybe i can bruteforce it but i need lenght of code or way how to unlock it without code??
rafaelwasosz said:
Thank You for Your response.
Unfortunatelly i dont have unlock code(i forgotten it ). The phone was unlocked before and i dont remember code.
Any ideas? Please.
Or maybe try to crack it? How long is the code? I remember that was only numbers so.... How many attemp I have to unlock before it lock for ....?
I`ve tried to reverse what i done .And it was because i format system partition to ext4 .Any box ideas how to put that nice phone to working order.....?
I dont have code ,but maybe i can bruteforce it but i need lenght of code or way how to unlock it without code??
Click to expand...
Click to collapse
it's a 16digit code, only numbers. i don't remember if you will get a message if the bootloader is unlocked or not or if you need to boot your device to check if bootloader is unlocked. if you get a message, i think it's possible to bruteforce ... there's also a paid method to get the bootloader code:
https://www.dc-unlocker.com/downloads/get/jvObBBIo
you must buy credits to get the feature you want. in your case, you need to buy enough credits to get your bootloader code.