I've been reading on unlocking, rooting, and rom flashing wiki/forum post for some days already. I'd like to clear up some question before actually rooting it.
Most procedures mentioned that, fastboot oem unlock is the first procedure.
However, what is the effect of this operation? Does it means, fastboot flash command will failed without unlock it first?
I've read a term call CID unlock, does oem unlock refers to CID unlock?
Regarding recovery mode, with the stock/vanilla recovery mode on N1, there is a options to 'apply sdcard:update.zip'. So, with a properly crafted update.zip, I can root it, am I understanding correct?
I'm puzzled on this, as all procedure I come across refers to custom recovery mode.
[email protected] said:
Most procedures mentioned that, fastboot oem unlock is the first procedure.
However, what is the effect of this operation? Does it means, fastboot flash command will failed without unlock it first?
Click to expand...
Click to collapse
Yes.
[email protected] said:
I've read a term call CID unlock, does oem unlock refers to CID unlock?
Click to expand...
Click to collapse
CID unlock = SIM unlock.
Read Nexus One FAQ, question 13. Link in my signature.
[email protected] said:
Regarding recovery mode, with the stock/vanilla recovery mode on N1, there is a options to 'apply sdcard:update.zip'. So, with a properly crafted update.zip, I can root it, am I understanding correct?
Click to expand...
Click to collapse
Yes, if you happen to have the key with which Google sign their updates. But that's not the case - so you can't create a "properly crafted update.zip", no matter how much you try, unless you work at Google and can get this key.
Thanks very much for your answer!
Related
I used a XTC CLIP to unlock my Nexus One. It was done and the HBOOT showed S-OFF, but I cannot excute fastboot command to flash recovery. It showed FAILED not allowed. That seemed the phone wasn't really S-OFF. Is there anyone could help please?
HBOOT 0.35.0017
I was just upgrade to 2.3.6
Did you do "fastboot oem unlock"? You have S-OFF but does not mean your bootloader is unlocked. If you don't like the lock on your bootscreen, you can do "fastboot oem lock" to lock up the bootloader after you have flashed your recovery. This is possible when you have S-OFF.
madballs said:
Did you do "fastboot oem unlock"? You have S-OFF but does not mean your bootloader is unlocked. If you don't like the lock on your bootscreen, you can do "fastboot oem lock" to lock up the bootloader after you have flashed your recovery. This is possible when you have S-OFF.
Click to expand...
Click to collapse
I don't want to excute "fastboot oem unlock" because I don't want to lose my data. Is there any way to unlock my Nexus One by using XTC Clip? What should I do?
No, there is none. But there's another way.
You can use BLACKROSE hack in the Development section to use engineering commands and fastboot flash without having to execute fastboot oem unlock, if you're worried about losing data.
Jack_R1 said:
No, there is none. But there's another way.
You can use BLACKROSE hack in the Development section to use engineering commands and fastboot flash without having to execute fastboot oem unlock, if you're worried about losing data.
Click to expand...
Click to collapse
Thank you very much. I want to backup my /data folder so I need root my phone. That's why I wanted my phone to be S-OFF. Is there a way to root my phone without unlock the bootloader? The BLACKROSE hack needs S-OFF or Root first and I cannot do that.
apathy0422 said:
Thank you very much. I want to backup my /data folder so I need root my phone. That's why I wanted my phone to be S-OFF. Is there a way to root my phone without unlock the bootloader? The BLACKROSE hack needs S-OFF or Root first and I cannot do that.
Click to expand...
Click to collapse
Sorry, but you are out of luck. There is no way to back up your data if you are on 2.3.6 with a locked bootloader and without root.
can anyone tell me whether the below process will make the bootloader locked again.
i have backed up the stock rom version 2.2 using CM Recovery
if i restore to 2.2 and update the same to 2.3.6 will i have my locked bootloader again.
please revert.
kishoreks said:
can anyone tell me whether the below process will make the bootloader locked again.
i have backed up the stock rom version 2.2 using CM Recovery
if i restore to 2.2 and update the same to 2.3.6 will i have my locked bootloader again.
please revert.
Click to expand...
Click to collapse
No. You cannot relock your bootloader that way.
Sent from my Nexus One using Tapatalk
Where to download blackrose.exe ?
n1one said:
Where to download blackrose.exe ?
Click to expand...
Click to collapse
There is a thread in the N1 development section.
Sent from my Galaxy Nexus using Tapatalk
I dont see blackrose.exe in that folder.
Pls send me the link to download blockrose.exe
n1one said:
I dont see blackrose.exe in that folder.
Pls send me the link to download blockrose.exe
Click to expand...
Click to collapse
I'll say it again: there is a thread in the N1 development forum with Blackrose in the title. You can download what you need in the first post. If you can't find it, I suggest you spend some time searching instead of trying to flash custom bootloaders.
Sent from my Galaxy Nexus using Tapatalk
I tried fastboot flash hboot #### method also, but it failed "signature verify" . My aim is to partition system memory to 220. so that i can install full ICS on nexus one.
I see still S-off in my bootloader. Pls help.
Hey Folks,
I was curious to know if you have unlocked your bootloader, and then locked it again via fastboot oem lock command, if you wanted to unlock the bootloader maybe in the distant future again, would you need to use the same unlock key that was given to you by moto?
Thanks!
alternetconcept said:
Hey Folks,
I was curious to know if you have unlocked your bootloader, and then locked it again via fastboot oem lock command, if you wanted to unlock the bootloader maybe in the distant future again, would you need to use the same unlock key that was given to you by moto?
Thanks!
Click to expand...
Click to collapse
Yes the one you got in your mail.
Take care not to lose it.
I am not sure if they give it again
adity said:
Yes the one you got in your mail.
Take care not to lose it.
I am not sure if they give it again
Click to expand...
Click to collapse
Ah okay great.
Thank you!
I've unlocked my bootloader but have never once considered relocking it. Why would you lock it after unlocking it in the first place? I can't think of a single benefit.
nhizzat said:
I've unlocked my bootloader but have never once considered relocking it. Why would you lock it after unlocking it in the first place? I can't think of a single benefit.
Click to expand...
Click to collapse
I've seen some people claim they want to be as "close to stock as possible" when selling their phone. Unfortunately it doesn't really make a difference.
There are 3 states for the 2013 Moto X bootloader:
LOCKED Status:0
Unlocked Status:3
Locked Status:2
note: Status 2 is also known as relocked.
As users we can toggle it to either Status 2 or Status 3, but we can never set it back to Status 0. On Status 2 or 3, you'll get the Bootloader Unlocked warning message at reboot (where replacing the LOGO.BIN with custom one will hide the message).
alternetconcept said:
Hey Folks,
I was curious to know if you have unlocked your bootloader, and then locked it again via fastboot oem lock command, if you wanted to unlock the bootloader maybe in the distant future again, would you need to use the same unlock key that was given to you by moto?
Thanks!
Click to expand...
Click to collapse
Have you managed to lock it?
alexhdkn said:
Have you managed to lock it?
Click to expand...
Click to collapse
I didn't actually. I just tried right now but got the following message.
(bootloader) FAIL: Please run fastboot oem lock begin first!
The reason I wanted to re-lock it was for purposes of my phone getting stolen. I'm assuming if it was relocked, the person wouldn't get the joy of installing a custom recovery.
Yeah kind of silly. In any case, couldn't get it to lock.
alternetconcept said:
I didn't actually. I just tried right now but got the following message.
(bootloader) FAIL: Please run fastboot oem lock begin first!
The reason I wanted to re-lock it was for purposes of my phone getting stolen. I'm assuming if it was relocked, the person wouldn't get the joy of installing a custom recovery.
Yeah kind of silly. In any case, couldn't get it to lock.
Click to expand...
Click to collapse
There is a process to re-lock which involves flashing the stock rom first, etc. and it does wipe the phone.
So if you re-lock, you'll also lose root. (at least until you unlock, flash custom recovery and root).
KidJoe said:
There is a process to re-lock which involves flashing the stock rom first, etc. and it does wipe the phone.
So if you re-lock, you'll also lose root. (at least until you unlock, flash custom recovery and root).
Click to expand...
Click to collapse
Yeah. I think I realized that I would need to wipe my phone again to re-lock it. I turned it back to stock so I can get the OTA which should hopefully come out soon.
I guess once they allow us to download stock 5.0.2, I'll do a re-lock then.
Thanks though for the info.
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
First check here... http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Get the sdk tools and once set up, see if you can do adb devices and have the phone show up on the PC, if so, do adb push (name of rom file) then boot to twrp and install. If that doesn't work, check the same page above (since you don't have an OS not sure what would happen) try the unlock instructions for fastboot ( I would wait for someone else to comment before trying this). You might want to message this user http://forum.xda-developers.com/member.php?u=2872010 rootSU and see if he can give guidance, he has lots of experience.
Locked Bootloader
I still can't seem to get past the fact that my bootloader is locked...
Thanks though.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexu...tboot-t3066052.
Flashing
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
SidedX said:
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
Click to expand...
Click to collapse
Sorry my bad, here it is http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Follow the instructions as i posted, place the download rom in the /android-sdk/platform-tools/ folder and boot in bootloader and select recovery, select adb sideload there and type in cmd: adb sideload name.zip.
Unlocked Bootloader
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
SidedX said:
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
Click to expand...
Click to collapse
It worked for other users, but hey if you have a better option try that.
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
SidedX said:
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
Click to expand...
Click to collapse
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Thanks
I see, I was able to adb push /sdcard/. a factory image to get back in with a locked bootloader, thank you.
gee2012 said:
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Click to expand...
Click to collapse
hallelujah!
cam30era said:
hallelujah!
Click to expand...
Click to collapse
That covered the spiritual moment of the day
With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.
I would like the flash script if someone would share it
Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?
ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?
Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.
ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that
Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!
diculpe por que mi pc no ve el fastboot de mi one zoom?
ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes
Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks
I tried to install Android 12 Developer Preview 3 on my Pixel 5 via OTA Sideload but it failed at 94% with the message 'adb: failed to read command: No error' on cmd and 'Install from ADB completed with status 0' on phone.
After this when I try to boot, I get the following message: 'Can't find valid operating system. The device will not start.' (attached image)
I'm able to access the bootloader but when I tried going into recovery mode through the bootloader, it shows the same message: 'Can't find valid operating system. The device will not start.'
Seems like the recovery is corrupted as well.
Unfortunately I had not enabled OEM unlocking in the developer options before trying to install the Developer Preview, which is now not letting me unlock the bootloader.
Please help me fix the issue or help me find a way to unlock the bootloader without enabling OEM unlock.
Thanks in advance.
I had the same thing happen to me just now. Have you managed to figure anything out?
Nothing from my side, since bootloader is locked I can't flash the system image and I can't unlock bootloader because my OEM unlock is turned off in developer settings and the Recovery and Rescue mode are also corrupted.
I contacted Google support and their only solution was to bring it in for service as my device is still under warranty.
I'm in the same boat here with a Pixel 4a 5G. Got to 94%.
First time I've experienced an issue while sideloading. . .
Contacted google support and they are shipping me a refurbed replacement... disappointed, to say the least.
Not sure what to make of this, it's developer preview and now beta. Issues will possibly occur and it warns you of such.
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As an additional this let me get my phone back to loading the custom ROM I was on, to then reenable debugging mode, I then rebooted back into fastboot mode and used Googles online factory restore mode to flash stock ROM back on and I was back up and running
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
leddra3k said:
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
Click to expand...
Click to collapse
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
V0latyle said:
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
Click to expand...
Click to collapse
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
leddra3k said:
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I am aware. However, this tool does not function like adb and is not meant for flashing factory images like the Android Flash Tool is. The Pixel Repair Tool works specifically from Rescue Mode.
leddra3k said:
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
Click to expand...
Click to collapse
It sounds like your Platform Tools may be out of date. Current version is 31.0.3, Aug '21.