X727 (US Model) Persistent bootloader unlock from 5.8.019s - LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D

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

Related

[How-to]Unlock/Re-lock Nexus 10 Bootloader

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

New fastboot unlocking command

Hi Guys, Just to let everyone know the command for unlocking the bootloader is now "fastboot flashing unlock" oem unlock will return an error and no longer functions.
Isn't the command just "fastboot oem unlock"?
overlord727 said:
Isn't the command just "fastboot oem unlock"?
Click to expand...
Click to collapse
Not anymore it would seem.... fastboot oem unlock returns an error
according to the android developer FAQ, "flashing" is the correct command, but I can't figure out why.
https://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
it made me start to wonder if OEM would somehow trigger the fuse, whereas FLASHING is specifically designed not to. anyone know why there's a "unlock bootloader" switch in the developer options within Android?
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Kitch16 said:
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
Click to expand...
Click to collapse
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Kitch16 said:
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Click to expand...
Click to collapse
Yes, Confirmed on my 6P.
Cheers bud, saved me spending more than the 30 mins I have already done pulling my hair out.
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
Tung_meister said:
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Yes, Confirmed on my 6P.
Click to expand...
Click to collapse
Did it trip your eFuse?
Kitch16 said:
Did it trip your eFuse?
Click to expand...
Click to collapse
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Born<ICs said:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Click to expand...
Click to collapse
TWRP isn't available for the Nexus 6P yet!
But when it is available, we'll have to cross that bridge when we come to it.
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Born<ICs said:
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Click to expand...
Click to collapse
I got in to Fastboot by holding volume down and powering on the phone as normal.
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
So what causes the Qfuse to blow?
Being a Nexus device shouldn't command be fastboot oem unlock. Curious
On the official Google Developers Factory Images page it’s still “fastboot oem unlock”.
http://forum.xda-developers.com/nexus-6p/general/fastboot-unlocking-command-t3233722/page2
To add to this also make sure your Android SDK is fully up to date
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
indianajonze said:
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
Click to expand...
Click to collapse
Does qfuse trip if you relock bootloader?
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
GCbard said:
Does qfuse trip if you relocation bootloader?
Click to expand...
Click to collapse
Does qfuse trip if one flashes a rom?

Question about unlocking bootloader

Will huawei give any trouble if we unlock the bootloader, does anyone think its worth it? I would like to try cm when it does release and right now I'm thinking of trying the mod to turn on and off swap
Sent from my KIW-L24 using Tapatalk
Turning on and off swap is the main reason I want to unlock the bootloader at the moment. Just haven't had time yet.
Arobase40 said:
If you're talking about commercial and customers side, and for what I know Huawei won't give any kind of supports with unlocked devices.
On the legal side it may depend on your country or region laws for the hardware warranty : Europe is more protective with customers...
So the answer is YES, you may have trouble with Huawei and with unlock devices if you're seeking after any kind of supports. Otherwise you can do what you want as the device is yours...
Click to expand...
Click to collapse
Yea was wondering about that and if I ever needed any repairs, I ended up doing it anyway everyone here seems to be unlocking anyway
Sent from my KIW-L24 using Tapatalk
Silly question, but what is swap?
Sent from my KIW-L24 using Tapatalk
Is there a tool made for this device yet for flashing adb fastboot? I used adb fastboot to unlock my L24 but when trying to flash the recovery.img that is where I hit a wall. I am not to up on adb fastboot besides simple commands for logs and unlocking a bootloader such as this. when I open a comand prompt it doesn't see the img file and give me a fail message. I just thought I would check to see if anyone has made their own tool yet. Thank you for your time.
Arobase40 said:
I may probably misunderstand your post but if you passed the bootloader unlocking process the rest of the procedure should be straightforward...
The "recovery.img file" (could be named differently) should be in your local system folder (Windows or Linux) and not in the phone (so no adb shell command) and make sure you ticked the USB debug mode in the developer panel...
The full procedure is here :
http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190
Click to expand...
Click to collapse
Yes, that was the post I was using as a guide. All the commands worked great to it came to the part where I had to flash recovery in bootloader mode. It wouldn't/couldn't find the destination file. I will just have to read some more and figure this out. Thank you for your reply. I'm almost done, just have to get recovery flashed now and I'll be good to go.
"Chance Favors the Prepared"
Probably 70% chance of having some hassle with warranty with bootloader unlocked, they will also blame any glitches on software or roms you using.
I scenario where phone 100% power dead they likely never look into bootloader or rom status so won't matter .
your region & person dealing with it will make huge difference on the day ...
Arobase40 said:
I still don't understand your actual position and troubles...
- Is your bootloader already unlocked ?
- If yes, so I guess you have already installed the Honor drivers and setup the adb software ???
- Which OS are you using ?
I don't know what you call the destination file, but you simply need to download the recovery file in step 8, and then continue to step 11.
If the downloaded file is "kiwi_twrp_3-21_recovery.img" save it to for example to your C:\temp folder.
When you open the command prompt, simply "cd c:\temp"and change the command "fastboot flash recovery twrp_kiwi.img"with "fastboot flash kiwi_twrp_3-21_recovery.img" or rename the original name to a simpler one, what suite you the best.
---------- Post added at 01:44 PM ---------- Previous post was at 01:34 PM ----------
I have written different posts about warranty and the fact that manufacturers say you'll be out of warranty if you unlocked or rooted your devices has no chance to be applied according to your local laws. The manufacturers contractual rules has no value if the local laws say differently !
Click to expand...
Click to collapse
Thank you Sir. That is exactly what I needed. I needed to know where to put the .img TWRP file, the destination, and his to access that file then with the command prompt.
Yes, my bootloader was unlocked successfully and adb had no problems picking up my device. It just couldn't locate the file that I was typing into the command prompt window. A lot of the roles that are out for use have spoiled me and that is all automate because everything is located in the same folder. I need to learn this though.
Thank you again.
"Chance Favors the Prepared"
Again, thank you. That was all I needed. It worked great once I put the TWRP.img file where it needed to be. I am unlocked, have custom recovery installed and am now rooted.
Chance Favors the Prepared "

Can i Lock Bootloader After Unlocking ?

Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Absolutely you can
https://youtu.be/O6qU57iGhBg
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
Will this work on Mi 8 Lite ?
Yes this method works on all xiaomi devices
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
hamidezat20 said:
https://youtu.be/O6qU57iGhBg
Click to expand...
Click to collapse
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
alxsduarte said:
Hello!
Some people claim that locking up the bootloader on newer Xiaomi devices could brick the phone.
Does this information proceed?
Has anyone tested?
---------- Post added at 08:51 PM ---------- Previous post was at 08:31 PM ----------
This video shows how to install stock ROM. But no to lock bootloader.
I dont understand the language. So, I dont see when he lock bootloader.
Sorry! Bad english... ::laugh:
Click to expand...
Click to collapse
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the right in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
SubwayChamp said:
This video don´t show how to lock bootloader so the essential part is missed, maybe the guy is talking about but most of users won´t understand what he says and is not reflected on the options that he is using.
If you want to lock bootloader using MiFlashTool then at time to flash a stock rom you have to check on "Clean All and Lock" option down at the left in the tool.
Locking bootloader can´t never brick device by itself, the problem is that some users tried to do it using a custom rom, a custom recovery, rooted or with a cross-firmware that was not released originally in the device and happened that after device was locked again then refuses to boot to android system so bootloader detects that some partition/s was/were altered.
If you only unlocked bootloader and you are using all stock and non rooted you can relock it without need of use mi flash but using only the typical fastboot command
Code:
fastboot oem lock
then check if it was correct with
Code:
fastboot oem device-info
BUT never try to lock it of this way if some non-stock file was flashed and currently using on your device be custom rom, custom recovery, root, logo, custom kernel, etc.
Click to expand...
Click to collapse
Thank you, bro!
All my doubts are clear now!
you cant lock bootloader if you firmware was originally chinese and you have changed to global..
if your firmware was global and you unlocked , yes you can lock it again using flashtool and oficial GLOBAL fastboot rom,developer or stable..:good:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock, I've tried multiple drivers and disabling driver signature in Windows 10. It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it? I've searched many times on Google and Youtube but with no success.
I had requested an unlock from Xiaomi and disabled all my other devices from my account.
Any help would be appreciated as this has become unnecessarily complicated, Thanks!
Click to expand...
Click to collapse
Check again if it´s correctly binded your MiAccount on Developer Options and try with other MiUnlock version.
Shillopellos9 said:
Hello, I've been trying to unlock my Mi8 Lite for a while (bootloader) but it is always stuck at 50% on MiUnlock [...] It never gets beyond that point and always shows a '-1' error. Did anyone encounter this or better yet solved it?
Click to expand...
Click to collapse
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
tolga9009 said:
Yes, I had the same issue and got it solved by using Mi Unlock on another PC. My main PC is using AMD Ryzen 2700 CPU, my laptop Intel Core i7-4712HQ. Wasted like 2 hours on my PC, while it worked first try on my laptop. Please note, the software told me to now wait 360 hours - it didn't unlock right away (this looks like expected behavior).
Click to expand...
Click to collapse
Soo i saw your reply and straight away tried unlocking with stock drivers on freshly bought laptop (today) with a Celeron, it worked straight away, Thanks! (i have a Ryzen 1600 desktop)
Witch version of Mi unlock software you suggest for unlocking bootloader?
I have China phone redmi note 8..and i want to flash global ROM but all Google say that if u lock the bootloader again...the phone will brick...so help me
Also, i have a question! My phone is on EU version, but i prefer the global version. Can i lock the bootloader back after i flash the version in fastboot mode?
Flash Mi 8 Lite image with mi flash tool and make sure you select clean all and lock in right bottom..
ThePscho said:
Hi friends!
I'm new in Mi 8 Lite community. I wonder a thing. If i unlock my bootlader, can i lock it again ?
Thanks for your answers.
Click to expand...
Click to collapse
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
alicization said:
You can flash fastboot ROM and set to clean all and lock, then the bootloader will be locked by a script from fastboot ROM
Click to expand...
Click to collapse
Once i unlocked the bootloader, after i set a new password and fp it just kept saying that i need to enter my password every 0 hours. Tbh it did warn me when i accepted the oem unlocking that security features like fp, face recognision and find device will be disabled. So here is the question, is there any way at all to lock the bootloader without factory resetting?
P.S. : I have flashed twrp and miui 12, because i destroyed the miui 11 [:

How to Downgrade (Any model, Any version)

Avoid and pass by a fool and a madman
wga0 said:
There's lots of posts about 'how to downgrade' at this forum, even I wrote it several times, but still many asks or complains there's nothing. Plz search it again. There're lots of info here. I write here a few ways again.
Most Simple, Fast, Safest way
1. Reboot your phone into bootloader
2. Change your active slot
Code:
adb reboot bootloader
fastboot getvar current-slot
fastboot set_active x
-- If your current-slot is a, x means b, and vice-versa
3. Reboot and do factory reset
These steps will revert your phone to the version exactly before the upgrade. That's your last, well worked version before upgrade. No root, No unlock, No flash required. All model, Any version possible.
Limitation: If you flashed the upgrade more than once, your previous version was deleted and this will not work. Then try next method.
Search Factory ROMs
Fortunately, BS Android 10 has no version info, and it seems that it doesn't check the region & model also. It means you can change the region & model, although it's not recommended.
https://forum.blackshark.com/discus...l-rom-joyui11-to-china-rom-joyui11-vice-versa (all the mega links he wrote here are from my post, and he said he tested it 100%... Just for info & not recommended)
So, find the Factory OTAs for your region first and flash it.
If there's none, then search it for most similar region and flash it.
If there's none also, then you can search it for most similar model, but it's not recommended. I guess it's better you to try next method
Limitation: Even if there's factory ROMs for your region, it doesn't guarantee the forward compatibility. You need to try find most good one. (Plz refer this post)
Search Fastboot ROMs
If you lost your previous version, if you can't find the factory ROMs, still you can downgrade with the Fastboot ROMs. BS team never release the Fastboot ROMs, but some people backed it and shares, or you can build it by yourself always. (Plz search about payload_dumper or image extractor)
But be careful. It doesn't check the sign(stock or modified), doesn't check the region, doesn't check the model. Even it doesn't check the image is a real image or not. It only requires 'Unlock bootloader'. If you unlocked your bootloader, you can use this method 100% possible, but it's dangerous if you don't know it exactly.
Limitation: It requires 'unlock'. After unlock, it's 100% possible, but be careful. It off all safeguard.
Click to expand...
Click to collapse
it really has a lot of tutorials, but with this new version and several variants, it is complicated to guide everyone ... I will test it on my DLT-H0 BS2 PRO and come back to talk ...
---------- Post added at 06:24 AM ---------- Previous post was at 05:34 AM ----------
Log error:
c:\adb>fastboot set_active a
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
Nice tutorial, well done.
wga0 said:
Code:
fastboot getvar current-slot
fastboot set_active x
Click to expand...
Click to collapse
You can also run this command, it will change the slot to the other one, with just one command.
Code:
fastboot set_active other
Just tried this tuto for SKR-A0 without root JOYUI11 Android 10. The message: Slot Change is not allowed in Lock State appeared in ADB. Is there any way to downgrade without root or just to make my gps works again with GAPPS? Thx

Categories

Resources