About a year ago, I tried installing a custom ROM for my ASUS ZenFone 5 (A500CG). I went through all the shenanigans of doing so (rooting, flashing, unlocking the bootloader). After succeeding in installing the ROM, I discovered the so-called "FREEZING BUG" of the Z5 wherein if you tried to unlock the bootloader, the phone would freeze/hang then reboot invariably. I didn't really like the ROM anyway, so I went back to my stock KitKat, also thinking that it would fix the "freezing". After the return, my Z5 still experiences the bug (FREEZING). With a bit of research, I found out that unlocking the Z5's bootloader is the culprit. I went to re-lock it, and as if nothing happened, it was fixed! No more freezing!
And today, I heard of CyanogenMod 13.1. I knew the Z5 would not be blessed with the new Android 6.0 update along with its 1st-Generation siblings. So I thought, "Meh. I'll give the custom ROM a shot." And I indeed liked CM 13.1. I wanted to keep it, but because I had to unlock my bootloader to get it to work, I'm back with the old, dreaded freezing bug.
Sorry for the long story, but my question is this:
Is it possible to keep the CyanogenMod with a locked bootloader? If so, how?
And if not, is there any way at all to fix the "FREEZING" problem of the Z5 whenever you try to unlock its bootloader?
Any help is appreciated!
cnswico said:
About a year ago, I tried installing a custom ROM for my ASUS ZenFone 5 (A500CG). I went through all the shenanigans of doing so (rooting, flashing, unlocking the bootloader). After succeeding in installing the ROM, I discovered the so-called "FREEZING BUG" of the Z5 wherein if you tried to unlock the bootloader, the phone would freeze/hang then reboot invariably. I didn't really like the ROM anyway, so I went back to my stock KitKat, also thinking that it would fix the "freezing". After the return, my Z5 still experiences the bug (FREEZING). With a bit of research, I found out that unlocking the Z5's bootloader is the culprit. I went to re-lock it, and as if nothing happened, it was fixed! No more freezing!
And today, I heard of CyanogenMod 13.1. I knew the Z5 would not be blessed with the new Android 6.0 update along with its 1st-Generation siblings. So I thought, "Meh. I'll give the custom ROM a shot." And I indeed liked CM 13.1. I wanted to keep it, but because I had to unlock my bootloader to get it to work, I'm back with the old, dreaded freezing bug.
Sorry for the long story, but my question is this:
Is it possible to keep the CyanogenMod with a locked bootloader? If so, how?
And if not, is there any way at all to fix the "FREEZING" problem of the Z5 whenever you try to unlock its bootloader?
Any help is appreciated!
Click to expand...
Click to collapse
Yes you can relock it Flash android M and after lock bootloader. http://forum.xda-developers.com/android/help/root-zenfone-5bootloader-unlock-recovery-t2896589
swiczak said:
Yes you can relock it Flash android M and after lock bootloader. http://forum.xda-developers.com/android/help/root-zenfone-5bootloader-unlock-recovery-t2896589
Click to expand...
Click to collapse
It is a false information.
Custom kernel for CM13 (or any Marshmallow custom rom) does not has a signature. (kernel by Asus has it)
So locked bootloader stop booting due to it.
Ok. I guess a custom ROM really just can't work with a locked bootloader. However, is there really even a way to fix the ZenFone 5's "freezing" problem even with the bootloader unlocked?:crying:
cnswico said:
Ok. I guess a custom ROM really just can't work with a locked bootloader. However, is there really even a way to fix the ZenFone 5's "freezing" problem even with the bootloader unlocked?:crying:
Click to expand...
Click to collapse
Unfortunately, for now, you can't, either you get the freeze bug or the camera bug when you unlock the bootloader on some ZF5s.
jephimax said:
Unfortunately, for now, you can't, either you get the freeze bug or the camera bug when you unlock the bootloader on some ZF5s.
Click to expand...
Click to collapse
Damn ASUS wouldn't give the Z5 the 6.0 update. Perhaps they want you to get a new phone? I really needed the new 6.0 stuff.
Anyway, thanks for the heads-up!
cnswico said:
Damn ASUS wouldn't give the Z5 the 6.0 update. Perhaps they want you to get a new phone? I really needed the new 6.0 stuff.
Anyway, thanks for the heads-up!
Click to expand...
Click to collapse
Actually if i get a new phone it won't be another Asus. They need to know
There's no fully solution for unlocking bootloader and they are not giving the private sources for signing kernels, or unlocking bootloader properly, or about GPS/FM bug.
If you want to get these features work proper only Asus can provide this things.
U can try AOSP 5.0.2
Sent from my ASUS_T00F using XDA-Developers mobile app
adhit_barker said:
U can try AOSP 5.0.2
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
No good, bruh. I need a 6.0 ROM. Or if you can suggest a way to use an SD card as adopted storage for non-Marshmallow firmwares.
Sent from my ASUS_T00J using XDA-Developers mobile app
Related
I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE CAUSED BY THE INFORMATION POSTED HERE. THIS IS NOT A TUTORIAL.
First of all , i know there is a thread about removing the Unlocked bootloader logo. This thread is started just to present some information based on my personal experience.
I owe a Motorola Razr I with unlocked bootloader :laugh:.......
A couple of weeks ago i decided to come back to ICS from the JB fastboot i was using(orange UK). Instead of using fastboot files made by mattlgroff I decided to fully flash the original ICS firmware for my phone using RSDlite. After the firmware was flashed i pushed the signed logo to the device.Of course the phone didn't finish booting and got stuck in bootloop. My phone became then a brick with a black screen and green led and i had to use the files from here to unbrick my phone. Big thanks to U1138 for finding the solution for unbricking.
When my phone phone finally booted i was so excited i didn't realize the ugly Bootloader unlocked logo is gone. I realized that yesterday while restarting the device and thought it's good to share it with everyone else and maybe will find a way for everyone to get rid of the ugly message on the boot screen.
free2live said:
I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE CAUSED BY THE INFORMATION POSTED HERE. THIS IS NOT A TUTORIAL.
First of all , i know there is a thread about removing the Unlocked bootloader logo. This thread is started just to present some information based on my personal experience.
I owe a Motorola Razr I with unlocked bootloader :laugh:.......
A couple of weeks ago i decided to come back to ICS from the JB fastboot i was using(orange UK). Instead of using fastboot files made by mattlgroff I decided to fully flash the original ICS firmware for my phone using RSDlite. After the firmware was flashed i pushed the signed logo to the device.Of course the phone didn't finish booting and got stuck in bootloop. My phone became then a brick with a black screen and green led and i had to use the files from here to unbrick my phone. Big thanks to U1138 for finding the solution for unbricking.
When my phone phone finally booted i was so excited i didn't realize the ugly Bootloader unlocked logo is gone. I realized that yesterday while restarting the device and thought it's good to share it with everyone else and maybe will find a way for everyone to get rid of the ugly message on the boot screen.
Click to expand...
Click to collapse
Is it still working after several reboots?
free2live said:
... [/COLOR][/SIZE]
Click to expand...
Click to collapse
So you suggest going back to ICS, bricking your device, unbricking it and flashing JB again in order to get rid of the bootloader logo?
Orbbman said:
So you suggest going back to ICS, bricking your device, unbricking it and flashing JB again in order to get rid of the bootloader logo?
Click to expand...
Click to collapse
I'm not suggesting anything. Only if you know what you are doing you can try it and even then take extra caution. It might be just a particular case.
Sent from my XT890 using xda premium
Thorstenk said:
Is it still working after several reboots?
Click to expand...
Click to collapse
Yes mate. I have like this for more than 1 week and i do reboot my device quite often due to poor network signal at my work.
Sent from my XT890 using xda premium
here's a short video to proof the unlocked bootloader message is gone
I am not a hundred perent sure of that, but I think this worked on your device because you unlocked your bootloader while on ICS then, upgraded to JB using matt's fastboot.
For someone who upgraded to JB using the OTA and only then unlocked their bootloader, this won't work because the motoboot file version is already the highest (homemade fastboot does not flash motoboot, that's why you were able to flash after a downgrade)
JackyJack said:
I am not a hundred perent sure of that, but I think this worked on your device because you unlocked your bootloader while on ICS then, upgraded to JB using matt's fastboot.
For someone who upgraded to JB using the OTA and only then unlocked their bootloader, this won't work because the motoboot file version is already the highest (homemade fastboot does not flash motoboot, that's why you were able to flash after a downgrade)
Click to expand...
Click to collapse
It maybe be possible. I did unlock bootloader while on ICS
Sent from my XT890 using xda premium
Anyone can confirm that intentionally bricking the phone by downgrading to ICS and reviving it deletes the unlocked sign?
Don't work with me
my logo returned to normal after restoring Pi-llama rom through cwm.
Could you be a bit more precise?
What do you mean with normal, no unlocked bootloader message left?
And what do you mean with restored?
Thanks!
densets said:
my logo returned to normal after restoring Pi-llama rom through cwm.
Click to expand...
Click to collapse
Thorstenk said:
Could you be a bit more precise?
What do you mean with normal, no unlocked bootloader message left?
And what do you mean with restored?
Thanks!
Click to expand...
Click to collapse
i unlocked my bootloader on ics telcel then went to 320002e.u. and did an update to 40002e.u.and my sing of unlocked bootloader disappear. but i hate is reading the warning message of unlocked bootloader in jelly bean how can i eraseed that.
http://forum.xda-developers.com/showthread.php?t=2226504
Yes, its for unlocking the bootloaders for the Snapdragon Motorolas (Atrix HD, RAZR HD and RAZR M) but after unlocking their bootloaders the same message appears (the same that we have), @tucstwo has provided a file to remove the unlocked message for these phones, I don't know if that zip could be compatible with the RAZR i, but giving the fact that the zip file removes the unlocked message for these phones ALREADY RUNNING JELLY BEAN, maybe someone can give a try and see what happens...
Link of the zip file is on the 2nd post.
don't work...
LOL try some king of custom upgrade we known that we have some chance of brick our phone and we get this risk like a bet with more chance to win, but intencionally brick the phone that cost here in brazil more than $500 we have to be a great crazy.
Does this also work on ICS?
AGISCI said:
Does this also work on ICS?
Click to expand...
Click to collapse
I can't tell you if it works or no. This is what happened to me not a tutorial.
Sent from Razr I using a bat ^o^
matheusgallo said:
Don't work with me
Click to expand...
Click to collapse
Did anybody try this method?
http://androidforums.com/motorola-razr-i/700911-bootloader-unlocked-under-jb.html
piskr said:
Did anybody try this method?
http://androidforums.com/motorola-razr-i/700911-bootloader-unlocked-under-jb.html
Click to expand...
Click to collapse
Yes! It dont work. Do not even try!
Ok, My Nexus 4 NOT LOCK BOOTLOADER after update for Kitkat, and no lock in any Stock and Customs ROMS !
just stays on: "LOCK-STATE: unlocked"
The commando line fastboot oem lock not work :crying:
help me I'm desperate
Help pls ... how to lock my device ? .-.
Well first of all, why would you like to re-lock your bootloader?
mumaster20 said:
Well first of all, why would you like to re-lock your bootloader?
Click to expand...
Click to collapse
my friend said that the OTA updates require locked bootloader, then I would like to lock it again ...
and how this under warranty, also wanted to make everything from factory
Your friend is wrong. You don't need locked bootloader to get OTA.
To get OTA update, you need stock rom and stock recovery, locked or unlocked doesn't matter.
You can also flash the factory stock image without wiping your data (see link in my signature).
If you have root you can use this app to lock and unlock your bootloader: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
eksasol said:
Your friend is wrong. You don't need locked bootloader to get OTA.
To get OTA update, you need stock rom and stock recovery, locked or unlocked doesn't matter.
You can also flash the factory stock image without wiping your data (see link in my signature).
If you have root you can use this app to lock and unlock your bootloader: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Yes, i understand .... so, my bootloader not lock with the app BootUnlocker, or command line, i tested all methods and nothing :crying:
AndreyVilella said:
Yes, i understand .... so, my bootloader not lock with the app BootUnlocker, or command line, i tested all methods and nothing :crying:
Click to expand...
Click to collapse
I guess something is up with your phone physical memory, but it doesn't matter, it really should not affect your warrenty (but the custom rom and recoveries will). Makes zero different to OTA updates either.
eksasol said:
I guess something is up with your phone physical memory, but it doesn't matter, it really should not affect your warrenty (but the custom rom and recoveries will). Makes zero different to OTA updates either.
Click to expand...
Click to collapse
Ok, thanks, then I can rest easy while the warranty? I just be with a recovery image and also manufactures and without Root?
AndreyVilella said:
Ok, thanks, then I can rest easy while the warranty? I just be with a recovery image and also manufactures and without Root?
Click to expand...
Click to collapse
Honestly, I don't think they care if you have root either, but that's base on other user feedbacks. It seems LG warrenty is picky about other things and not very good from the feedbacks from what I read actually, but I haven't had first hand experience. But people have sent in rooted devices for repair.
I think just have factory image and stock recovery and stock kernel.
Solution !
eksasol said:
Honestly, I don't think they care if you have root either, but that's base on other user feedbacks. It seems LG warrenty is picky about other things and not very good from the feedbacks from what I read actually, but I haven't had first hand experience. But people have sent in rooted devices for repair.
I think just have factory image and stock recovery and stock kernel.
Click to expand...
Click to collapse
Ok, Thanks ! I will continue in Stock image with bootloader Unlocked ...
Don't buy this crappy xioami.
Nowadays xioami LOCKed BOOTLOADERs
Start from RN3 RNP Mi4c
The rest will be lock too.......VIA STOCK ROM
Hugo Barra is smart
We are stupid includes me. Bcos I bought new RN3
then only learned that bootloader is LOCKed
Too much hustle to unlock.
For so many many days past by waiting for unlock code
So what, just apply for unlock and wait. For this price of hardware it's worth it. I hope there will be some reasonable custom AOSP rom.
Gibol666 said:
So what, just apply for unlock and wait. For this price of hardware it's worth it. I hope there will be some reasonable custom AOSP rom.
Click to expand...
Click to collapse
See the thing is by their terms just because you request one doesn't mean you will get it. It is up to them.
As for aosp I wouldn't count on it, most developers won't touch their devices nor do they support them.
zelendel said:
As for aosp I wouldn't count on it, most developers won't touch their devices nor do they support them.
Click to expand...
Click to collapse
Why shouldn't we cont on developers to work on this ROM? I see that the Redmi 2 has plenty of custom ROMs available right here on XDA forum.
Sent from my Redmi 3 using Tapatalk
They locked the bootloader for a reason. There has already been reports of Xiaomi refusing to provide an unlock code to users.
Most roms for Xiaomi devices are ports at best with the one exception being the one CM supports. Development teams know this, and on top of their constant gpl violations leave a bad taste.
Don't get me wrong. I hope things work out but in ref to aosp based development there won't really be much
Can anyone tell me what is bootloader for?, why is it important to unlock it?
http://www.addictivetips.com/mobile...-bootloader-on-android-phones-complete-guide/
I've recieved the unlock confirmation today. Now just waiting for developer rom to be released
Gibol666 said:
I've recieved the unlock confirmation today. Now just waiting for developer rom to be released
Click to expand...
Click to collapse
Well, so it IS possible!
For how long did you wait?
Eleven or twelve days, not that long compared to 3weeks+ that some people reported
Gibol666 said:
I've recieved the unlock confirmation today. Now just waiting for developer rom to be released
Click to expand...
Click to collapse
Is it really need to unlock bootloader in other to flash developer ROM?
I know a lot of mi4 owners who regularly use weekly developer without haven't ever unlocked their bootloader.
So is it really necessary for our redmi3 to unlock the bootloader in other to flash developer ROM?
Cause I really like to remain virgin while being able to ***** around ?
Sent from my Redmi 3 using Tapatalk
No. You got it wrong. You need to flash the developer ROM in order to unlock bootloader ( to be able to flash other ROMs.)
Gibol666 said:
No. You got it wrong. You need to flash the developer ROM in order to unlock bootloader ( to be able to flash other ROMs.)
Click to expand...
Click to collapse
so let me get this straight, i don't need to unlock bootloader in order for me to use Global ROM or Developer ROM, but if i want to use other ROM (Custom), i need to unlock it. How about if i want to root?
spiderclan said:
so let me get this straight, i don't need to unlock bootloader in order for me to use Global ROM or Developer ROM, but if i want to use other ROM (Custom), i need to unlock it. How about if i want to root?
Click to expand...
Click to collapse
Nope, rooting the device has nothing to do with the locked bootloader. But I am not entirely sure if there is a way to root the redmi 3 just yet.
Unlocked bootloader is needed for:
- Custom roms that don't use the stock kernel
- Custom kernels
- Non stock-based roms (CM for example)
unlock confirmation received
I've recieved the unlock confirmation today.
What must I do to unlock the bootloader?
The sms says:" Your unlock request has been approved. Go t XXXXXX to download the unlocking tool"
Thanks in advance
felison69 said:
I've recieved the unlock confirmation today.
What must I do to unlock the bootloader?
The sms says:" Your unlock request has been approved. Go t XXXXXX to download the unlocking tool"
Thanks in advance
Click to expand...
Click to collapse
http://en.miui.com/unlock/download_en.html
Download Mi Unlock, BUT....
http://en.miui.com/thread-202290-1-1.html
Here you can read that :
2. The unlocking procedure only supports MIUI China developer version (6.1.12 or later version) currently. MIUI China stable version will get supported in future updates
Click to expand...
Click to collapse
So we need to wait for the dev. rom for redmi 3.
According to this thread should be out anytime soon :
http://en.miui.com/thread-228054-1-1.html
BUT....
Update*
[Developer rom has been out for awhile and the latest version is now 6.2.24. However, it is currently not due for public release. Fret not as even with the latest developer rom, boot loader cannot be unlock yet as Redmi 3 has yet to be integrated into MIUI Unlock System.
Click to expand...
Click to collapse
No unlock yet =(
I am a bit confused about this locking. On most phones i had i initially booted them into fastboot then flashed TWRP then via TWRP flashed custom roms (zips). So which part did they lock ? Fastboot so you cannot flash TWRP or the bootloader itself(TWRP,CWM,etc) (theoretically you could flash it but not access) ? Thanks for clarifying for me.
csman said:
I am a bit confused about this locking. On most phones i had i initially booted them into fastboot then flashed TWRP then via TWRP flashed custom roms (zips). So which part did they lock ? Fastboot so you cannot flash TWRP or the bootloader itself(TWRP,CWM,etc) (theoretically you could flash it but not access) ? Thanks for clarifying for me.
Click to expand...
Click to collapse
You can't flash anything at will with it locked. Even in Fastboot it won't work unless signed by Xiaomi. And they are not giving everyone unlock codes. Mainly if you mention you want to remove miui. Also if you are not active in their forums they won't do it.
zelendel said:
You can't flash anything at will with it locked.
Click to expand...
Click to collapse
Nonsense. You can flash (unofficial) full roms using fastboot in download mode, no problem at all...
Only flashing in fastboot mode (recoverys, xposed, custom kernels) wouldn't work with locked bl.
I also don't like the idea of locked bootloaders but, well... you do it once, use unlocked roms and are happy with it. not big of a deal, so stop whining...
Had it on my Razr i, now on the Redmi 3. Got my approval for it after not even 2 weeks at the beginning of february, now waiting for the suitable dev rom to unlock.
Just let it all settle a bit, the device by now is just too fresh out...
zelendel said:
They locked the bootloader for a reason.
Click to expand...
Click to collapse
The reason was to prevent resellers from preinstalling tampered roms.
So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk
Hey! I got this phone recently and wanted to try some ROMs out. But since I never unlocked the bootloader on a MIUI device, I have a few questions. Is it worth it to unlock the bootloader? Which MIUI features do I lose and can I regain them by relocking the bootloader through MiFlash? Thanks in advance
Correct me if i'm wrong
Unlocking bootloader won't take away any feature. There are more can be done and explore such as mod and custome firmware. No harm on unlocking bootloader
AFAIK the only thing that can be picky is the Playstore with the certification, that most of the time unlocking the bootloader change the status to unverify on MIUI, on custom ROMs it depends of the ROM i guess.
BlackGarnett said:
AFAIK the only thing that can be picky is the Playstore with the certification, that most of the time unlocking the bootloader change the status to unverify on MIUI, on custom ROMs it depends of the ROM i guess.
Click to expand...
Click to collapse
Is PixelExp fine?
Matt 123456789 said:
Is PixelExp fine?
Click to expand...
Click to collapse
If you are talking about PE from Nameless, he said he was working on it (1 week ago kinda) it might be fixed on recent builds (I'm on MIUI), also some users said that (on that-time-build) it could also be working by clearing cache+data of the playstore. :good: