Hey, i have android 10 stable installed in my phone. Just before i updated my phone (while i still was on 9.0.9), i also unlocked my bootloader, nothing else, no twrp or root. Now i would like to relock my phone again, because google pay is not working anymore, and im not willing to root my phone, because updating problems all the time etc. so can i relock my bootloader just by using command "fastboot oem lock" on fastboot mode? or do i have to do something else before that? also, is there possibility to brick phone somehow? if so, is there a way to fix it, while using OOS with android 10? i know this is stupid question but i hope someone could anwer it. Its not first time, when something is changed due new android update, and all previous guides are wrong.. =/
only reason i unlocked my phone, was that when i had oneplus 1, it bricked somehow oneday, and only way to get it back working, was empying whole phone, but there was possibility to recover data, if bootloader is unlocked, but i didnt have that, so i lost everything.. so i unlocked this one, to prevent that problem, but now i have new, because Android Pay is not working..
I think you can use "Fastboot oem lock" as always, but it will wipe all your data (It's no way to skip that). I think it won't brick your phone
Yes, it won't brick your phone, just wipe your data.
Relocking succeed, thank you..
Related
Dear all,
I am new on Android, the Nexus 5 is my first android device. I freshly come from a 5 years old iPhone 3G.
2 Weeks ago I unlocked the bootloader of my device and rooted it following the tutorials provided by the XDA community without any problem.
Today, I saw that the OTA to upgrade from the Android version 4.4 to the version 4.4.2 was available directly from the device.
Since I did not want this update to be a problem with my rooted device, I downloaded the following apps: BootUnlocker for Nexus Devices and OTA RootKeeper (I do realize using RootKeeper was stupid since anyway the last update was released on July 25, 3 months before KitKat...). But anyway, this is what I did. I used those apps to Lock my Bootloader and unRoot my phone, thinking that this will reduce the chances of potential conflict with the OTA update.
Afterward, I downloaded and tried to instal the OTA directly from the Nexus 5. It ends up that I got stuck on the recovery menu. It was then impossible to get back on android and I did not know what to do.
This is where I did something totally crazy. Usually I spend time reading tutorials and finding information before doing anything that I do not fully understand. But at this stage I simply thought that the update could not properly instal due to the root. So I went on Advanced Wipe, I ticked all the options (data, system, Cash, Dalvik... all of them), and wiped the device.
As a result, my Nexus 5 has currently a Locked Bootloader and no OS installed. This means that I cannot activate the developer menu (no OS) to tick the option USB debugging. Thus, I cannot unlock my bootloader and in consequence I cannot instal the factory image and get back to stock.
Please, If you can give me some advice, explain me how can I unlock the bootloader in these conditions. Let me know... I really don't know what to do now.
PS: sorry my english is not perfect but I do hope you clearly understand my problem.
Yoyo-san said:
Dear all,
I am new on Android, the Nexus 5 is my first android device. I freshly come from a 5 years old iPhone 3G.
2 Weeks ago I unlocked the bootloader of my device and rooted it following the tutorials provided by the XDA community without any problem.
Today, I saw that the OTA to upgrade from the Android version 4.4 to the version 4.4.2 was available directly from the device.
Since I did not want this update to be a problem with my rooted device, I downloaded the following apps: BootUnlocker for Nexus Devices and OTA RootKeeper (I do realize using RootKeeper was stupid since anyway the last update was released on July 25, 3 months before KitKat...). But anyway, this is what I did. I used those apps to Lock my Bootloader and unRoot my phone, thinking that this will reduce the chances of potential conflict with the OTA update.
Afterward, I downloaded and tried to instal the OTA directly from the Nexus 5. It ends up that I got stuck on the recovery menu. It was then impossible to get back on android and I did not know what to do.
This is where I did something totally crazy. Usually I spend time reading tutorials and finding information before doing anything that I do not fully understand. But at this stage I simply thought that the update could not properly instal due to the root. So I went on Advanced Wipe, I ticked all the options (data, system, Cash, Dalvik... all of them), and wiped the device.
As a result, my Nexus 5 has currently a Locked Bootloader and no OS installed. This means that I cannot activate the developer menu (no OS) to tick the option USB debugging. Thus, I cannot unlock my bootloader and in consequence I cannot instal the factory image and get back to stock.
Please, If you can give me some advice, explain me how can I unlock the bootloader in these conditions. Let me know... I really don't know what to do now.
PS: sorry my english is not perfect but I do hope you clearly understand my problem.
Click to expand...
Click to collapse
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
rootSU said:
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
Click to expand...
Click to collapse
Dear RootSU,
So this means that I am not stuck at all and that I am simply limited by my current knowledge about android?
If this is the case, then "alleluia"! I will document myself to be able to fix this thing.
Yoyo-san said:
So this means that I am not stuck at all and that I am simply limited by my current knowledge about android?
Click to expand...
Click to collapse
Pretty much
You should be able to unlock the bootloader as you did before.
Boot phone to fastboot mode, download fastboot and adb kit to you computer... it can be found here on forums easy, and in comand line to unlock bootloader you need type "fastboot oem unlock".
More complete guide you can find here http://forum.xda-developers.com/showthread.php?t=2507905 =)
rootSU said:
Pretty much
You should be able to unlock the bootloader as you did before.
Click to expand...
Click to collapse
It's ok now!
As you said, I could unlock the Bootloader the same way I did before. Then I install the factory image 4.4.2, which I rooted directly.
Thanks a lot RootSu, you've shown me my mistakes and put me on the way to fix my problem.
Thanks also for your concern Biggreen. =)
Problem solved!
rootSU said:
You've got it all wrong. You do not need USB debugging to unlock bootloader. to unlock bootloader you must use FASTBOOT commands, which means you MUST be in the bootloader itself. USB debugging ONLY works in android.
Click to expand...
Click to collapse
Dear RootSU,
One more question, could you explain me why I got stuck into the recovery menu when I first tried to update via the OTA? Will I get the same kind of problem when I'll update with the v4.4.3 in the future?
Thanks
Yoyo-san said:
Dear RootSU,
One more question, could you explain me why I got stuck into the recovery menu when I first tried to update via the OTA? Will I get the same kind of problem when I'll update with the v4.4.3 in the future?
Thanks
Click to expand...
Click to collapse
I am not sure on the extact reason. OTA itself will not install with a custom recovery. You have to download the OTA and boot to recovery then manually flash.
There is a good "OTA Helpdesk" sticky thread in general you should read as theres lots of advice there
hi there...i've got the same problem... i wiped everythink and now i'm not able to switch on my phone....i just want to get out of this somehow...i'm very much new to this and i just want to get my stock android back that's it...somebody please help....
Do you see the battery icon when you connect the phone to a charger? Does the LED turn red when you connect the phone to a charger? Maybe leave the phone connected for a couple of hours and then try to power on?
Hi guys,
It might sound dumb but I was wondering if it was possible to relock the bootloader while keeping root.
In fact, I did not want to modify my Honor 8 that much too soon but I enjoy playing some games on my phone using a pad, I did not want to spend alot so I just went with a pad I already have, the DualShock 4. It works well except the button mapping in native Android games, that's why I have to root to use Sixaxis app to solve the issue.
So I may have to root my device soon but I don't plan any other modification to the system atm and I particularly hate the warning message when you boot (gosh, I hated it on my Moto G but it was easy to replace).
That leads me to the thread title: Is it possible to root and then get rid of the unlocking message (relock the bootloader or anything else would be okayish)?
I just want to get root access on the phone for my gamepad issue and eventually setup some typical things such as a real adblocking solution (DNS66 is not bad but hosts file is still the way to go imo) and maybe Xposed.
Is there a way to reduce the modification on the phone? (Thus the idea of relocking it, I was thinking that maybe, once relocked it won't show the message. But maybe relocking just wipe the phone again? (as unlocking it does))
Thank you guys
thats possible to relock bootloader .but if u used flash custom recovery and SuperSu.zip to root your phone , after rooted device , please reflash stock recovery vi fastboot and relock your bootloader
I don't think it's possible to relock the bootloader and keep your device rooted.
DarkGuyver said:
I don't think it's possible to relock the bootloader and keep your device rooted.
Click to expand...
Click to collapse
It was possible with the Nexus 5 and a few other phones to root it and then relock it. Obviously the only way to know if that's the case on this phone is to try it. But you just have to make sure that the stock recovery is there instead of twrp before relocking.
One brave soul needs to try it though. [emoji4]
Sent from my FRD-L04 using Tapatalk
Well, I'll wait until someone who has a rooted device give it a try.
That screen would really annoy me... I always thought it was dumb to put that kind of screen... Damn, no need to remind us that it is unlocked if WE DID IT OURSELVES.
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
I opened up the developer options on my Moto G Stylus and went under OEM Unlocking and selected the allow the bootloader to be unlocked option. That was either last week or a few weeks ago because I wanted to root it and put a custom rom on it. I didn't rooted it yet because I'm not sure what roms are good, I only had cyanogin mod roms on my other phones and I'm not sure which rom is the safest and best to use so I still use the stock rom. I turned on Pandora to play music before I went to sleep. When I woke up my phone was in some kind of recovery mode and said something like the operating system failed to boot. Two options were available, 1- to try booting again, and 2-factory reset the phone which would erase all data. I selected 1, and my phone booted up. Could this be because the bootloader is unlocked? Does having the bootloader unlocked leave it suspectable to being hacked? Could my phone have been hacked?
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
k3dar7 said:
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
Click to expand...
Click to collapse
Would selecting the bootloader option to be unlocked in the developer options make my phone more vulnerable to be hacked?
A few hours later my phone did the same thing and went into recovery mode saying that my phone could not load the OS and might be infected or something. I had the same options to either try to load the OS again or factory data reset the phone. How could this happen?
I factory data reset my phone this time. I just hope I don't have some kind of malware.
Mine was hacked like this. Changed stuff so it won't boot back to original. Got into system files and remote control my phone. Is there a way to get back to original without computer? It's useless now