Related
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
timour79 said:
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
Click to expand...
Click to collapse
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Billchen0014 said:
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Click to expand...
Click to collapse
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
Alright, thanks
Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
What's your reason for wanting it relocked?
Sent from my HTC Vision using xda app-developers app
noneabove said:
What's your reason for wanting it relocked?
Click to expand...
Click to collapse
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Nate2 said:
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Click to expand...
Click to collapse
Well I dont want to completely void the warranty, unless rooting already does that. If it was mine then i would've unlocked and rooted. I'd probably already have a rom and kernel on it. But it's actually my dad's, and he said I can root it if I don't do anything too serious(like I said, I just want Superuser so I can use things like the sixaxis controller app.)
comminus said:
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
Click to expand...
Click to collapse
Would that be manual rooting?
NRT questions
hey there
have some newb questions about rooting along the same lines of the OP. hope you can help me
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
sorry for the newb questions but there are so many different guides out there and some of them refer to older versions of the NRT so just want to clarify these points.
timour79 said:
Would that be manual rooting?
Click to expand...
Click to collapse
No. All you are doing there is unlocking the bootloader. Unlocking the bootloader is the equivalent of pre-heating your oven. You haven't messed with any ingredients or cooked anything yet.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Lemegeton300 said:
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
Click to expand...
Click to collapse
1. The chances are pretty slim for permanently bricking. That is the beauty of Nexus devices - the entire factory image is available to be flashed back on if you screw things up. That is the equivalent of reformatting your harddrive & reinstalling your OS on your desktop.
2. mkskip's toolkit will install it for you. I am sure wug's will too.
3. You don't have to install CWM, especially if you are thinking that you will pretty much always stay stock. But, the bug might hit you in a month or two to start playing around, and then CWM or TWRP is your friend. I installed CWM & made a backup pretty quickly in case I do something I shouldn't, such as accidentally deleting a vital system app. That way you do not have to do the factory reinstall route. Every few weeks you can make yourself a fresh backup just for fun.
4. You should be fine - the drivers must be working if the toolkit is doing backups for you. I am assuming you are using mkskips toolkit based on this question - his instructions say that sometimes in 1 step it says drivers didn't install correctly when they actually do - Windows is...Windows. If you want to be sure, ask away on mkskip's thread. He is quite helpful.
5. If you reflash the factory image & the bootloader is relocked, there is nothing for them to see...not that they'd really care since the point of a Nexus is to develop on it. You would only be returning it for a hardware issue, and the software unlocking has no impact on the hardware problem, since your hardware issue would've happened no matter what software you had on it. The only way a software thing could cause a hardware issue would be if you over-overclocked it & cooked some parts. You'd really have to work at doing that since these things usually shut down when the temperature gets too high.
In short: root it & enjoy it!
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Lemegeton300 said:
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes. When you restore a backup it will be just as it was when you made it. Have fun!
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Scyntherei said:
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Click to expand...
Click to collapse
+1 the QFuse status didn't change when unlocking the bootloader. The media exaggerated about the qfuse and nothing has happened. Everything about the phone still works properly.
Thanks very much, I wasn't aware of this, I should read more. Awesome news.
But to answer the first question.
Very few people put in effort to root a phone with an unlocked bootloader, not matter what fuses are blown.
A phone with an unlocked bootloader has root by default.
Swatto86 said:
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Click to expand...
Click to collapse
last i read you have to flash a kernel in order to root the phone therefore you need to unlock the bootloader to do so, i would like to just root myself but i don't know if you can.
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Why people are afraid to unlock the bootloader? Nexus devices don't lose the warranty when you unlock it, you can also lock it again.
Enviado desde mi Nexus 7 mediante Tapatalk
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
No
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
The answer is no.
To do what you want, someone would need to develop and exploit.
There is no motivation to do that when all one has to do is unlock the bootloader.
On phones where a bootloader unlock exists, root methods require unlocking the bootloader.
This is to install a custom recovery so yiou can flash SU.
Unlocked bootloader = root, no matter what.
You will need to invest the time and backup your device.
@TS, did you read the unlock/root guide in general section? It clearly states you need an unlocked bootloader + custom recovery to root your device..
Sent from my Nexus 5X using XDA-Developers mobile app
I think this should be possible now with Quadrooter vulnerabilities?
sushah23 said:
I think this should be possible now with Quadrooter vulnerabilities?
Click to expand...
Click to collapse
DOA.
But nobody is going to put in time and effort.
What is the point? Unlock the bootloader and flash. It does not void the warranty.
There is even a defined method to get the monthly security update.
With the exploit, it will only work until the next OTA patches it.
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
LiquidAlloy said:
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
Click to expand...
Click to collapse
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Jammol said:
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Click to expand...
Click to collapse
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
LiquidAlloy said:
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
Click to expand...
Click to collapse
In all honesty it's not even more convenient. Once you've used the command line you'll never go back to a toolkit. It's actually easier, much faster and you have way more control over what you do.
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
Use Helium app for individual apps backup. Worked great to backup a few apps/data when I changed from one Nexus 6P to another. Might be a bit buggy to get working to get the backup, but after that everything is fine.
you can do it with KINGROOT
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Mohit M'S said:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Click to expand...
Click to collapse
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
DJBhardwaj said:
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
Click to expand...
Click to collapse
Your device is corrupt and can't be checked for corruption
Mohit M'S said:
Your device is corrupt and can't be checked for corruption
Click to expand...
Click to collapse
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Device is locked
Mohit M'S said:
Device is locked
Click to expand...
Click to collapse
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
DJBhardwaj said:
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
Click to expand...
Click to collapse
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Mohit M'S said:
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Click to expand...
Click to collapse
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Heisenberg said:
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Click to expand...
Click to collapse
OK OK but after unlocking it there is any way to relock it and remove this error message
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, of course. Infact that's the reason I asked you about the lock status on the first place. Stock ROM with locked bootloader shouldn't give this warning. It should make it go away.
That is why, I asked you to perform a flash manually. Please refer to Heisenberg's guide for the steps.
Here is the link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, after locking the bootloader the message should disappear. But, I'd strongly recommend leaving it unlocked and just dealing with the message. If an OTA ever fails or something else goes wrong you'll need fastboot to flash the factory images to recover your device, you'll be forced to unlock the bootloader, this will wipe the device and you'll lose all of your data because there'll be no way to back it up first.
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Sorry message is Device can't be trusted or it may not work properly
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
Did you reflash manually?
DJBhardwaj said:
Did you reflash manually?
Click to expand...
Click to collapse
Nope gonna do this by today or tomorrow
Mohit M'S said:
Nope gonna do this by today or tomorrow
Click to expand...
Click to collapse
Sure and then let us know. And keep the bootloader unlocked, it will help you to deal with a few issues (if any), in the future, as already mentioned above by Heisenberg.
-_____- why do people still use toolkits? Try getting use to Adb; it would save you a lot of time dealing with errors.
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
uicnren said:
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
Click to expand...
Click to collapse
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..??
Ruined my phone
Mohit M'S said:
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..
Ruined my phone
Click to expand...
Click to collapse
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
uicnren said:
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
Click to expand...
Click to collapse
U didn't understand what I said I have already reverted my to stock ROM and relocked the bootloader but even then message is coming device can't be trusted or may not work properly and I'm not even getting any updates not even April update and all friends got this I'm currently pure stock
Problem are:-
Message is still there
Updates r not coming
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Why would you want to do this?
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Is there any way to remove the Bootloader unlock warning ⚠ without relocking bootloader?
Sent from my XT1572 using Tapatalk
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Theres no reason really to relock it. Once its unlocked, the bootloader will show that it was unlocked regardless if you relock it.
atishey23 said:
Is there any way to remove the Bootloader unlock warning without relocking bootloader?
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Yes
Pyramid Head said:
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Click to expand...
Click to collapse
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
psandeepn said:
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
Click to expand...
Click to collapse
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
jason2678 said:
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
Click to expand...
Click to collapse
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
The answer is maybe... it depends what you have changed and what this OTA updater script actually checks for.
We know that a stock bootloader (which can be unlocked, that is not relevant), stock recovery, and stock system image are required to take an OTA. If the system image has been modified it can fail, and we know the updater has the ability to see if /system has EVER been mounted R/W and can fail for that condition although so far it doesn't seem Moto is going that extreme.
We do know a modified logo does not affect an OTA, in fact, you can even relock the bootloader with a modified logo so it must not be a significant check.
jason2678 said:
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
Click to expand...
Click to collapse
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
iks8 said:
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
Click to expand...
Click to collapse
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
acejavelin said:
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
Click to expand...
Click to collapse
You're right sorry
Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds ?
romeoh said:
Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds
Click to expand...
Click to collapse
You can't, you would have to modify the bootloader to get rid of it, which is pretty dangerous and could hard brick your phone.
awsomjgp said:
You can't, you would have to modify the bootloader to get rid of it, which is pretty dangerous and could hard brick your phone.
Click to expand...
Click to collapse
Ok, but as I know the only version that doesn't contain this warning screen is B20, so If I started from the very beginning by flashing back the B20 then removing the bootloader from the next versions (B27,B29,B15,B19) and flashing them from twrp would that work? ?
romeoh said:
Ok, but as I know the only version that doesn't contain this warning screen is B20, so If I started from the very beginning by flashing back the B20 then removing the bootloader from the next versions (B27,B29,B15,B19) and flashing them from twrp would that work? ?
Click to expand...
Click to collapse
If you are going to try that then just flash the b20 stack first and see if it boots.
Not completely sure whats in the bootstack zips but I've always assumed it is bootloader and modem.
Pretty sure 6.x bootloader will not work on 7.x but you can always try it out.
lafester said:
If you are going to try that then just flash the b20 stack first and see if it boots.
Not completely sure whats in the bootstack zips but I've always assumed it is bootloader and modem.
Pretty sure 6.x bootloader will not work on 7.x but you can always try it out.
Click to expand...
Click to collapse
Tbh I don't have the courage to try it that's why I'm asking may be one of our good developers knows the right way to do it ?
Saw this in post #496 of Full Updates / Back to Stock Files via TWRP
.......[snip] ......
"EDIT : managed to work fastboot and get rid of the bootscreen as in attachment :
Just refollow the steps in this guide to unlock bootloader (even if you think/thought you were unlocked (you are but has to be 'rewritten"), just do it again to flash the proper aboot...)
https://forum.xda-developers.com/axo...flash-t3517379
I had permission denied in 8) so i retried in twrp recovery.
All went fine.
And also the annoying boot screen ("that your device is corrupted due to unlock state...") is GONE too...."
I actually find the unlocked bootloader convenient. Rather than try to remember which buttons to press to get into recovery/fastboot, I can just do it from that screen so long as one of the volume buttons is depressed during the first 5 seconds of booting. I don't find it intrusive or bothersome at all.
If yours is taking 20 seconds to start booting then there is some other problem. It should start within ~5 seconds.
romeoh said:
Hi everybody, I'm wondering if anyone has figured out how to remove the bootloader unlocked warning? it became so annoying after upgrading to 7.1.1 and now it stays for at least 15 to 20 seconds
Click to expand...
Click to collapse
u can give me the method for unlock bootloader for 7.1.1
mr.mgmg said:
u can give me the method for unlock bootloader for 7.1.1
Click to expand...
Click to collapse
I was already unlocked when I updated to 7.1.1. You can try this method it's so simple and easy. Tbh I'm not sure if it will work on 7.1.1, but I think all what you need to do is to revert back to 7.0 then unlock bootloader, take the ota update and flash twrp from fasboot and from twrp flash SuperSu 2.79 for root. http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page25
romeoh said:
I was already unlocked when I updated to 7.1.1. You can try this method it's so simple and easy. Tbh I'm not sure if it will work on 7.1.1, but I think all what you need to do is to revert back to 7.0 then unlock bootloader, take the ota update and flash twrp from fasboot and from twrp flash SuperSu 2.79 for root. http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page25
Click to expand...
Click to collapse
thanks for help
but im a fried if this method brick my phone