Related
We can no longer unlock your bootloader with codes. Please do not ask me or ash for bootloader unlock codes. We can not help you.
This thread is now here for historical purposes representing times when people were free to do what they wanted with their devices. Fsck yourself with a rake, Verizon.
The bootloader has been unlocked. Let's get our freaking root on.
Disclaimer: Read through these instructions in their entirety. If these don't make sense to you, you do not need to be rooting your phone. Nobody here has the time required to teach you how to use cmd in Windows. We will not baby step you through how to use ClockworkMod Recovery. Root is not a mythical land with fairies and unicorns where nothing ever goes bad. If you don't know how to properly install a driver in Windows, you probably don't need an Android device to begin with, let alone a rooted one.
These instructions are intentionally left vague. Do your research on these terms. Understand what you are doing before you do it.
tldr: if you fsck your phone up, it's on you and only you.
Easy Way (YRMV!)
This is by far the easiest method. You will have to read between the lines here. I will not detail all the steps. Please record your experiences in this thread and let me know how it all goes! We're all still learning. This is basically copied from Bin4ry's CWMR Thread so thanks go to him! The easy steps below assume a lot of basic knowledge steps. Like unlocking the bootloader. If you're unsure of what to do, you probably shouldn't be doing it.
Download the CWM recovery from multiupload
Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Copy this to your memory card and flash it with the booted recovery
Reboot and test root
Second Method: Advanced User Instructions
Unlock your bootloader. Check out Ash's thread: thread
Download Doom's all in one kernel from here
Use fastboot to "hot boot" the kernel: fastboot boot boot.img
Your phone may or may not boot. It doesn't matter. Let it be for a while, then power it off.
Doom's kernel will have rooted your stock system.
If You're On A Mac...
Or maybe just need some general help with some more detailed insturctions than are labeled here, check out the awesome post that Cubsfan3493 made for everyone. He's even got a downloadable PDF with pictures. Go give him some thanks at his post!
Is the R800x running 2.3.2 or 2.3.3. There's reports that Gingerbreak and alternatives are no longer working in 2.3.3.
It's running 2.3.2 right now. OTA updates say its up to date. I'm trying to figure out if I'm just having a generic issue with the breaks (like memory cards for example) or if Verizon maybe patched the exploit in their 2.3.2 build.
I have tried pretty much everything as well, I really hope some dev's start to pop their noises in here as I am a bit sad about the activity so far
I've been trying to root mine as well. The discussion I've been having is in this thread
http://forum.xda-developers.com/showthread.php?t=1097856
I'll keep an eye on both threads, but I have had no luck so far.
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
Yes i think verizon fixed the exploit gingerbreak uses before releasing the handset in the usa. When i was on build number 3.0.A.2.184 (uk xplay R800i) it rooted in like 30 seconds.
But in the new update 3.0.1.A.0.145 the exploit has been fixed. So all devices around the world have been left unrootable (for now ) the devs will figure away out.
I think the uk version 2.3.3 build 3.0.1.A.0.145 has been rooted (for unlocked bootladers) http://forum.xda-developers.com/showthread.php?t=1098736 So if your bootloader is unlocked soon it maybe possible. If its locked your stuck waiting with the rest of us for a rooting method on locked devices.
I saw you updated from another post, did you lose root access after the update?
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
build number - 3.0.E.2.89
A shame they didn't let us all have unlocked bootloaders.
axiomjunglist said:
I saw you updated from another post, did you lose root access after the update?
Click to expand...
Click to collapse
Yes i did. But the fixes added in the update are worth loosing root, for the time being . Being unable to root only applies to people with a locked bootloader. But im guessing devs from the arc and play forum are possibly looking for ways to root with a locked bootloader
Yeah I have the option to unlock my bootloader but don't want to just yet. I'll hold off on the update until a new version of gingerbreak arrives
Sent from my R800a using XDA App
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Mills00013 said:
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Click to expand...
Click to collapse
Wonder if you pop a pre-paid SIM in the slot (or try a friend's AT&T/T-Mobile SIM) and disabled the CDMA radio if you could get an IMEI to pop up on the keypad using *#06#. Might work? I have no clue... and you'd still have to send it to SE and hope they clear it.
I have a few SIMs here that I could try. Ill see what I come up with in a little bit. My gut is telling me that Verizon probably has the SIM slot firmware disabled. Thats only because they havn't officially mentioned it anywhere. In fact, the slot itself is actually hidden by a piece of plastic that you have to remove. One wouldnt have any idea it was there unless you were looking for it and even then you feel like you're breaking your phone to access it.
I also considered hooking it up to QPST to see if it would grab some serial numbers out of the device. Can anyone confirm if this is a qualcomm chip inside the phone?
I just tried a T-mo and an AT&T SIM, neither give me any sort of insertion notification or acknowledgement that they are present. So I'd say the slot is firmware disabled. But it should still have an IMEI, right? That would be programmed by Qualcomm out of the factory before Ericsson would have even installed it. Or am I taking crazy pills?
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
b00sted said:
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
Click to expand...
Click to collapse
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
ace518 said:
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
Click to expand...
Click to collapse
ya I just tried too and fail :/ #sadpanda
Neither the adb devices nor the fastboot devices codes have anything to do with the IMEI number.
Enviado desde mi R800i usando Tapatalk
I am willing to donate towards the first person that can get root and CWM on this!
I'm new to rooting phones I have a Moto Photon 4G. Ido have root access but when i try to boot into Android Recovery i get a message saying fail boot 2 entering RSD mode. So I'm not able to flash any roms to my phone. It's getting frustrating I have used google to find a solution but I'm a NOOB haha so I'm not really sure what I'm looking for. Please can anyone help?
Have you unlocked it? Can't do much without unlocking and installing a custom recovery.
If not, start here.
I'm pretty sure it's unlocked but how can I be sure. I used Root check basic and it confirmed I do have root accsess.
Root and unlocking are two separate processes. When you boot the phone, if you're unlocked, it will say unlocked in the upper left on the screen with the red m.
Sent from my MB855 using XDA
My phone is not unlock so what is the next step I need to take to unlock it? Thank you all for your help. I'm begging lol please help it's making me crazy
The link Kevets gave you will tell you everything you need to know. And if you look for qbking77 on youtube he has walkthroughs for the process.
Sent from my MB855 using XDA
if you email me i'll give you the link i can't post links yet.
shows step by step how to unlock my phone but i get stuck on this part below
Now click your start menu and type "cmd", right click the cmd program and copy it to your unlock pack directory.
i'm not sure how to copy it.
Open the newly copied cmd.exe and type "fastboot oem unlock xxxxxxxxxxxxxxxx" WITHOUT THE " " MARKS and replaces the x's with your code that you got from the above step.
The links were helpful but some are outdated or my comp says they contain malware and wont allow me to proceed any further and yes qbking77 has very helpful videos
bigdaddy619 said:
motorolaphoton.webs.com/ unlocking
shows step by step how to unlock my phone but i get stuck on this part below
Now click your start menu and type "cmd", right click the cmd program and copy it to your unlock pack directory.
i'm not sure how to copy it.
Open the newly copied cmd.exe and type "fastboot oem unlock xxxxxxxxxxxxxxxx" WITHOUT THE " " MARKS and replaces the x's with your code that you got from the above step.
The links were helpful but some are outdated or my comp says they contain malware and wont allow me to proceed any further and yes qbking77 has very helpful videos
Click to expand...
Click to collapse
Once the cmd.exe comes up in your start menu, right click it and choose "copy." Then open your unlock pack directory (where you unzipped the unlock pack zip file) and right click, then choose "paste." Then double click the pasted cmd.exe. I'm not sure what has you stuck exactly.
Sent from my MB855 using XDA
I give up apparently I'm to stupid to do it Thanks for your help
I have watched qbking77 videos
How to install the Android SDK, ADB and Fastboot on your PC
How to unlock the Motorola Photon 4G bootloader
Installing Android SDK, ADB and Fastboot didn't work for me.
Hope this helps
Try my site and tell me if that helps.
https://sites.google.com/site/mophocorner/
You need to unlock your phone and flash CWM in order to put a custom rom on it. Rooting it is he easy stuff. If you flash a custom rom 99.5% of the time it is pre rooted so...
I have tried that method with no success. Thanks for your help
You have to use RSD-lite to flash the stock phone rom back onto your phone before you can unlock it.
I did the same thing you did when I first tried to load a custom rom, and many other people here have done the same thing as well, we have all gotten through it. It took me about 5 hours of trying to get everything straightened out, and the next day I was running overclocked CM7 with jokers kernel.
Close please
Sent from my MB855 using xda app-developers app
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock" and also flash back to STOCK images (if changed) or else it wont boot
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
duarian said:
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
Click to expand...
Click to collapse
No, it doesn't send anything to Google, that's why they give you the option to relock the bootloader .
can this be done on linux using fastboot included in sdk?
jrod091 said:
can this be done on linux using fastboot included in sdk?
Click to expand...
Click to collapse
of course man fastboot is fastboot
matt95 said:
of course man fastboot is fastboot
Click to expand...
Click to collapse
You will probably need to run fastboot as root, though.
gnustomp said:
You will probably need to run fastboot as root, though.
Click to expand...
Click to collapse
It isn't needed, if the sdk folder is in the PATH it will work normally
udimars30 said:
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock"
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Video coming soon, after i get my hands on it!
Click to expand...
Click to collapse
Thanks！I will try it!
Re-lock
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
matt95 said:
It isn't needed, if the sdk folder is in the PATH it will work normally
Click to expand...
Click to collapse
I just put it in /usr/bin with adb, I've only had my SGSII as far as android devices, Si want sure, thanks though!
Sent from my SGH-I777 using xda app-developers app
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Lumsdoni said:
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Click to expand...
Click to collapse
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Sdk has been updated
Sent from my SGH-I777 using xda app-developers app
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
yeah thanks for reminding dude
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
---------- Post added at 02:31 PM ---------- Previous post was at 02:15 PM ----------
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Lumsdoni said:
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
Click to expand...
Click to collapse
It would appear it is a lot simpler now as you can download a sdk / eclipse bundle from here
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
I unlocked the bootloader but now the tab will not start? I starts to the X of JB and then nothing happens... Help
---------- Post added at 10:56 PM ---------- Previous post was at 10:18 PM ----------
I have the Solution :good:
If you have the same problem - Go into Stock-Recovery and make a "Factory Reset" then reboot the system.
EniGmA1987 said:
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
Click to expand...
Click to collapse
It's may be wrong, I'm basing it on my XOOM days where it wouldn't boot it you relocked with anything other than stock. If that's different now, feel free to ignore me
Sent from my GT-I9300 using Tapatalk 2
I know that when an update comes out I have to relock the bootloader, but if I unlock it after the update does it wipe the device again
Sent from my Galaxy Nexus
I have 3 questions
1. Unlocking nexus 10 means rooting it ?
2. Is unlocking or rooting tablets legal in US?
3. I ordered nexus 10 but read n
ot so good things about the limited applications are supported for 10 inch screen .. Is there any workaround to have apps look as good as iPad I mean using the entire screen ...any custom ROMs available yet
Sent from my SGH-I897
Jose-MXL said:
CAN ANYONE IN THIS THREAD AND WITH THE INTENTIONS OF UNLOCKING THE BOOTLOADER PLEASE CAPTURE THE OTA PER THE POST BELOW:
http://forum.xda-developers.com/axon-7/how-to/to-unlock-bootloader-hold-help-t3437617
Sorry the harsh capitals, we need more visibility on this.
In case someone with the intentions of unlocking the bootloader reads this, there is an OTA being pushed to devices when they request the bootloader unlock, it is very important for development to capture these OTAs.
Click to expand...
Click to collapse
OK guys this seems to be great NEWS , yeahhh....
Here is the link for the step provided by [email protected] Community.
https://community.zteusa.com/docs/DOC-1193?et=watches.email.document
And I'll add as attachment the PDF file for the steps..so far seems like is super easy.
I'll be writing the steps here later today , I'm using my phone as we speak and is not easy getting all that info here hehehe.
P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS WILL WIPE INTERNAL STORAGE AND DATA .....
P.S.S. Looks like one of the Steps for Unlocking is a FOTA (Forcce OTA) without it the steps above are useless
Copy-Paste from the other thread:
If you read the document looks like unlocking the bootloader boils down to "fastboot oem unlock", like you'd do on any Nexus
If this is the case, it's pretty good, because it means that the procedure isn't tied to the phone's IMEI.
Btw, I've tried doing it, and it didn't work, so I guess there'll be another OTA soon to actually activate the unlocking, and that must be the OTA that it's been referred to in the instructions
AlesG87 said:
Copy-Paste from the other thread:
If you read the document looks like unlocking the bootloader boils down to "fastboot oem unlock", like you'd do on any Nexus
If this is the case, it's pretty good, because it means that the procedure isn't tied to the phone's IMEI.
Btw, I've tried doing it, and it didn't work, so I guess there'll be another OTA soon to actually activate the unlocking, and that must be the OTA that it's been referred to in the instructions
Click to expand...
Click to collapse
Did you enable "OEM Unlocking" under Developer Options?
yep, it was enabled
I think they push out an OTA update specific to your device to let this happen. We need someone to capture it.
Actually. It sounds like they will send you a specific file for your device that you will install per instructions.
AlesG87 said:
yep, it was enabled
Click to expand...
Click to collapse
dennis96411 said:
I think they push out an OTA update specific to your device to let this happen. We need someone to capture it.
Click to expand...
Click to collapse
mmmm, i'm doing a Device Backup (Data/Apps , MMS,Text and internal storage) and give it a try...report back as soon i get something.
AlesG87 said:
yep, it was enabled
Click to expand...
Click to collapse
At which point in the process did you notice it not working for you? You do have the B20 update installed, correct?
Well, I skipped all the useless stuff about the SDK since I'm on linux, just made sure adb debug and unlock switches were on and did
adb reboot bootloader
fastboot oem unlock
Got "FAILED (remote: unknown command)" response in the terminal
AlesG87 said:
Well, I skipped all the useless stuff about the SDK since I'm on linux, just made sure adb debug and unlock switches were on and did
adb reboot bootloader
fastboot oem unlock
Got "FAILED (remote: unknown command)" response in the terminal
Click to expand...
Click to collapse
What about "fastboot devices"?
swehes said:
Actually. It sounds like they will send you a specific file for your device that you will install per instructions.
Click to expand...
Click to collapse
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Wait, try to save the OTA for research purposes before you install!
charlie.s said:
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Click to expand...
Click to collapse
Same here, I was pushed an update.
charlie.s said:
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Click to expand...
Click to collapse
were you able to capture it?
and yeah Doesn't work without the OTA for unlocking :'( .....
I hope someone can save it and upload it here so the developers can have a look.
Worked for me. I updated the phone via settings. The file was about 50MB...I think. When connected to the PC, you have to choose "install driver" instead of MTP/PTP.
"P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS MAY or WILL WIPE INTERNAL STORAGE AND DATA ....."
There's no MAY, I just did it and it WILL erase your data.
Rats -- I hit the trigger too quickly, so I can't capture the file. For future reference, how can I do that?
CandyFoxJ said:
"P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS MAY or WILL WIPE INTERNAL STORAGE AND DATA ....."
There's no MAY, I just did it and it WILL erase your data.
Click to expand...
Click to collapse
Unlocking/locking the bootloader will always format the userdata partition.
charlie.s said:
Rats -- I hit the trigger too quickly, so I can't capture the file. For future reference, how can I do that?
Click to expand...
Click to collapse
Does the update install as soon as it finishes downloading?
WARNING: This ABSOLUTELY HAS THE POTENTIAL TO BRICK YOUR DEVICE. Please tread carefully. I am NOT responsible if you damage your device. This can be very dangerous, PLEASE do not do this unless you know you absolutely want/need to. You have been warned.
Important information:
This is for US Model x727 running the 5.8.019s version of the US ROM. If you flashed the chinese ROM, this will not help you at all.
Afterwards you should still have US ROM and features at version 5.8.019s
Your device should be persistently unlocked after successfully performing this procedure.
This zip file replaces the aboot and xbl (basically, the bootloader) with the versions from the LE_ZL1_LEX720-CN-FN-WAXCNFN5801811021S-5.8.018S.zip ROM file. I can't guarantee this will work for everyone (or even anyone). I can only tell you that it worked for me.
NOTE: If this makes you happy, please consider donating by clicking on the "donate to me" button under my handle at the left. I am broke and trying to recoup the cost of this device
Requirements (what I *think* you'll need):
US Le Pro3 running the US ROM updated to 5.8.019s OTA (If you're running the chinese ROM because you were impatient and didn't want to wait for the grownups to work out a procedure, this will not help you).
TWRP Image (I used the chinese one)
Zip File listed below
Somewhere to put the zip file for flashing if you don't want to have to wipe your device (I've heard of people successfully using an OTG storage device? I just wiped mine so you're on your own to figure this out)
This is the procedure I followed:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Run "fastboot boot recovery_twrp.img" (or whatever the twrp image filename is on your computer) to boot up to TWRP
NOTE: If you don't read chinese and you haven't done this before, you'll be presented with a screen in chinese with two buttons next to each other and a swipe underneath them. THE BUTTON ON THE RIGHT lets you change the language. Press it, thank me later.
If you have an OTG device with the bootloader replacement zip on it, skip this step. If you have to use your device's storage, and your storage is encrypted, you'll have to wipe all the data. Go to Wipe, choose Format Data and follow the instructions. YOU WILL LOSE EVERYTHING ON YOUR DEVICE. Be warned.
If you wiped your data partition, you'll need to push the zip file to the storage. Run "adb push x727-5.8.019s_bootloader-unlock.zip /sdcard/"
Now press "Install", select the x727-5.8.019s_bootloader-unlock.zip file and flash it.
Reboot back to your system. If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Your system should still be running the full US ROM, but it should also now be persistently unlocked. Don't do any updates, your device likely won't remain unlocked if you run an update. And there's no guarantee you'll be able to re-unlock after doing so.
NOTE: If you flash TWRP to the recovery partition, the OS will likely reset it to the factory recovery UNLESS YOU ROOT THE SYSTEM. Your device is still unlocked, the recovery was just restored by the system, don't freak out. Be warned. I don't have time to answer stupid questions, neither does anyone else.
Download: x727-5.8.019s_bootloader-unlock.zip
MD5: 8eff2a1e29c9959259e7db1dd5c74a67
Special thanks to @hondajohn88 for taking the leap and experimenting with the chinese rom on his own device.
Reserved
Is it possible to have the chinese bands with the US rom on the x727? because I'm bringing the phone to asia and i need band 41
How about pulling us the modem image from the US version now since you have it unlocked. The Grossoshop is great except a few of us have flashed this over the CN ROM and the CN modem seems to be lacking a few bands.
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Kick ass man!!! I get my phone next week when my dad comes down to visit me in Colombia. Can't wait to do this once it arrives
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Its going to be pointless for me to try .. I don't understand why you guy can have temp bootloader while I cant
And yes, I am on 19s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\adb>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.091s]
finished. total time: 0.094s
bulls4ever said:
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Click to expand...
Click to collapse
Yeah I absolutely have tried like 6 different adb/fastboot's and nothing works for me either.
Not my first rodeo with annoying Windows drivers too.
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
bulls4ever said:
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Click to expand...
Click to collapse
It won't be the fix. If adb/fastboot recognize the devices, changing versions shouldn't work. Sorry :-/ That being said, I suppose there's no hurt in trying. FWIW this is what worked for me on my Windows 7 box:
Code:
C:\Users\dr4stic>adb version
Android Debug Bridge version 1.0.36
Revision 19394af606f6-android
C:\Users\dr4stic>fastboot --version
fastboot version 19394af606f6-android
I got them by installing the Android SDK. The SDK manager indicates that my "Android SDK Platform Tools" (that the tools come from) are at version 24.0.4 and I can upgrade to revision 25.
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
ExTREmE99 said:
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Click to expand...
Click to collapse
I did, but I didn't really need to. They're in the 5.8.019s OTA. They're the emmc_appsboot.mbn and xbl.elf files in the firmware-updates folder.
dr4stic said:
It won't be the fix. If adb/fastboot recognize the devices, it won't work. Sorry :-/
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
Click to expand...
Click to collapse
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
---------- Post added at 06:39 PM ---------- Previous post was at 06:36 PM ----------
no donuts
C:\adb>adb version
Android Debug Bridge version 1.0.36
Revision e02fe72a18c3-android
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.015s
C:\adb>
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
Click to expand...
Click to collapse
Who knows, maybe the lower version is misinterpreting the output. If you're really determined you can try upgrading your version of adb/fastboot. Like I said I use the sdk from google, so it's as updated as it'll get. Anything else is just someone repackaging what already exists.
After you "fastboot oem unlock-go" try booting the twrp image anyway. I doubt it'll work if it's misinterpreting the response (it would have be interpret it properly to send the boot image to the device for booting), but who knows. Maybe it will work anyway.
Saikou0taku said:
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
Click to expand...
Click to collapse
yes
Going to try the Android SDK shortly
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
Click to expand...
Click to collapse
You know... if worse comes to worst and you desperately want to unlock, couldn't you just try installing the Chinese ROM listed by some of the other users? I don't know how that ROM would react to your phone being that it isn't unlocking at all, maybe it'll brick it, maybe it won't (I doubt it). The consequences of that would completely be of your own undertaking...
That being said, the chinese rom people talk about is signed by LeEco and thus would likely install without question. And it's bootloader would then be unlocked. We could make plans to return you to stock US firmwares at a later date. I suspect we're gonna have to get a solution together for that at some point anyway... My only suggestion would be that you do it while coming from the 5.8.019s (which you already are) because that's where my firmwares are coming from.
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
bulls4ever said:
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
Click to expand...
Click to collapse
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
dr4stic said:
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
Click to expand...
Click to collapse
I'm going to use this method later today and can report back any issues. By the way, you are the man!
Is super super flash able after bootloader is unlocked?
yeah .. windows wasn't the issue. I tested on Ubuntu and it was a no go.
Is it possible that LeEco released like 2 versions being the first a mistake of leaving the bootloader sort of unlocked and then a second with it locked?
I am running out of reasons for not being able to unlock it while some are able to