hi guys, i've unlocked the bootloader with the dc-unlocker2client , And i want to go back to the original boot loader, i've tried to re flash the 137 and eve the 129 chinese rom but the annoying message on boot startup still exist..
so how to go back?
youre mixing up two things: the bootloader and the boot image
the former (bootloader) you unlock via fastboot and the unlock code that you read out via dc-unlocker. this is the reason why u receive the message at bootup and u can relock the bootloader via fastboot as well (fastboot oem relock XXXXXXXXX)
the latter is the boot image that u have to decrypt in order to be able to root properly and not be stuck in a boot loop. the boot.img is reflashed once u install a new stock firmware. but the bootloader lock state is untouched by this, thats why u manually have to relock it using fastboot!
cheers
thats weird.. i entered the fastboot mode
and opened the minimal adb - and wrote the command : fastboot oem relock XXXXXXXXX
the XXXX is my unlock code from the dc software i guess..
and its says : failed : stat not match
so.. how can i lock it again?
http://postimg.org/image/50dz3y0vf/
U should flash stock recovery first...then relock your bootloader
Related
OTA softbricked? the device of my friend
Although the bootloader is unlocked, I was able to flash new firmware with fastboot with succes!! The device is now booting 4.1.1 (10.4.2.20)again
So, I tried to flash TWRP through fastboot (it's still responding to fastboot), but that fails:
Code:
FAILED <remote: <InvalidState>>
Thinking it is because the bootloader is locked, installed unlocking tool. Run it, at the last step, where you have to click the -normally- bar with image of locked lock to unlock, I get the dreaded network error, more importantly: the lock image is UNlocked
What could be the case now?
n/m http://forum.xda-developers.com/showthread.php?t=2037266
fastboot is available, flashing is not
I have a serious problem: my device's partitions are all erased and formatted and the boot loader is locked which is why I can't install a recovery or anything else. fastboot oem unlock doesn't work for any reason. It just boots and does nothing. After entering fastboot again it says it's locked.
The alternative method with adb doesn't work as I don't have a recovery nor do I have a system.img on the device. I can only enter fastboot now and flash the radio. How can I flash stock CM11S now? I need to unlock the bootloader and fastboot won't let me!
h**p://forum.xda-developers.com/showpost.php?p=55952004&postcount=457
Guy with a similar problem, who found a solution... Give it a try!
How on earth did you manage to erase all the partitions?
Transmitted via Bacon
I am trying to restore my stock ROM so I can do a carrier reset. (I use ting and my phone was sprint).
I am using ubuntu but have a windows install as well.
I Unlocked the bootloader with htcdev, installed TWRP, and rooted with SuperSU, and flashed the ARHD 20.0 rom because sprintzone makes me angry. It read that it is actually a GSM rom and I have a CDMA sim card so I won't be using that anymore.
Current predicament:
RELOCKED
S-ON
RECOVERY MODE fails with "failed to boot to recovery mode"
phone will not boot to system, just goes straight to bootloader. Download mode works.
I want to fix recovery mode but I can't do it because the bootloader is locked.
MAIN PROBLEM: fastboot flash unlocktoken unlock_code.bin reports success, but the phone immediately reboots bootloader with RELOCKED, so I cannot flash any recovery image. I also cannot turn S-OFF because I cannot boot into system or gain access through recovery mode to install the sunshine app.
I have gathered that I need to flash an RUU image, but I can't do that because my MID and CID are not supported (according to other threads) and S-OFF.
I tried to install the RUU anyway with:
fastboot oem rebootRUU
fastboot flash zip 0PJAIMG.zip ##(sprint version)
but it threw: Invalid sparse file format at header magi fastboot: /libsparse/sparse.c:144: write_all_blocks: Assertion 'pad >= 0' failed. so no luck.
Is there another way I can restore manually from fastboot without an RUU? I couldn't find a system.img or bootloader.img or anything like that. Will it work if I go buy an external SD card and but the RUU on that? or maybe someone knows what is wrong with the unlock process.
Johnnyappleseeds said:
I am trying to restore my stock ROM so I can do a carrier reset. (I use ting and my phone was sprint).
I am using ubuntu but have a windows install as well.
I Unlocked the bootloader with htcdev, installed TWRP, and rooted with SuperSU, and flashed the ARHD 20.0 rom because sprintzone makes me angry. It read that it is actually a GSM rom and I have a CDMA sim card so I won't be using that anymore.
Current predicament:
RELOCKED
S-ON
RECOVERY MODE fails with "failed to boot to recovery mode"
phone will not boot to system, just goes straight to bootloader. Download mode works.
I want to fix recovery mode but I can't do it because the bootloader is locked.
MAIN PROBLEM: fastboot flash unlocktoken unlock_code.bin reports success, but the phone immediately reboots bootloader with RELOCKED, so I cannot flash any recovery image. I also cannot turn S-OFF because I cannot boot into system or gain access through recovery mode to install the sunshine app.
I have gathered that I need to flash an RUU image, but I can't do that because my MID and CID are not supported (according to other threads) and S-OFF.
I tried to install the RUU anyway with:
fastboot oem rebootRUU
fastboot flash zip 0PJAIMG.zip ##(sprint version)
but it threw: Invalid sparse file format at header magi fastboot: /libsparse/sparse.c:144: write_all_blocks: Assertion 'pad >= 0' failed. so no luck.
Is there another way I can restore manually from fastboot without an RUU? I couldn't find a system.img or bootloader.img or anything like that. Will it work if I go buy an external SD card and but the RUU on that? or maybe someone knows what is wrong with the unlock process.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried using sp flashtools instead to see if that works ? I think you may be better asking in the m9 forums here
https://forum.xda-developers.com/one-m9/help
hopefully one of the experts has come across this before
Good Luck
Sawdoctor
Hi all
Iam trying to unlock my bootloader in moto m to root the device.
when trying
fastboot oem get_unlock_data>> it shows as failed remote unknown error
also i used command fastboot oem unlock,it says as unlocked
then tried to flash it with twrp recovery image>it says as done but I cant able to go to twrp.
Please help me to fix the issue
Once you have flashed the twrp image, can you boot into android? Does adb work? If yes, try and run "adb reboot recovery" and report results.
arunanbu44 said:
Hi all
Iam trying to unlock my bootloader in moto m to root the device.
when trying
fastboot oem get_unlock_data>> it shows as failed remote unknown error
also i used command fastboot oem unlock,it says as unlocked
then tried to flash it with twrp recovery image>it says as done but I cant able to go to twrp.
Please help me to fix the issue
Click to expand...
Click to collapse
3 easy steps:
1. fastboot oem unlock in bootloader mode. Accept the message on the phone's screen. Read carefully.
2. Fastboot boot twrp.img
3. flash / sideload latest supersu.zip
Or the distributed boot / system / data (rom) for restoration?
I figured to HTCDEV unlock to allow fastboot to write to recovery
and then fastboot boot twrp to backup whats there before overlaying it.
why not try it?
https://forum.xda-developers.com/showthread.php?t=2798853
fuzzynco said:
Or the distributed boot / system / data (rom) for restoration?
I figured to HTCDEV unlock to allow fastboot to write to recovery
and then fastboot boot twrp to backup whats there before overlaying it.
Click to expand...
Click to collapse
Yes.
Captain_Throwback said:
One thing to note is that you CAN fastboot boot TWRP on this device, so if you don't want to overwrite stock recovery, you don't have to
Click to expand...
Click to collapse
Just make sure to do that from the bootloader menu, not the download mode. Download didn't work for me, command line in Windows was stuck on booting and the download mode said finished flashing, that's it. Once rebooted to the bootloader menu everything was fine. That's how I backed my original recovery as well. You'll probably need to unlock the bootloader on htcdev first though, at least that's what I did.
BolecDST said:
Just make sure to do that from the bootloader menu, not the download mode. Download didn't work for me, command line in Windows was stuck on booting and the download mode said finished flashing, that's it. Once rebooted to the bootloader menu everything was fine. That's how I backed my original recovery as well. You'll probably need to unlock the bootloader on htcdev first though, at least that's what I did.
Click to expand...
Click to collapse
Yes, I figured that, (htcdev.com bootloader unlock).
Thanks for the pointer, I really don't know which mode is for what ...
I think bootloader mode is for direct fastboot flashing
fastboot flash <partition> <file>
or fastboot boot <file>
and download mode & RUU mode is for things packaged
like an RUU. fastboot flash zip <file>
fastboot oem <--->
fuzzynco said:
Yes, I figured that, (htcdev.com bootloader unlock).
Thanks for the pointer, I really don't know which mode is for what ...
I think bootloader mode is for direct fastboot flashing
fastboot flash <partition> <file>
or fastboot boot <file>
and download mode & RUU mode is for things packaged
like an RUU. fastboot flash zip <file>
fastboot oem <--->
Click to expand...
Click to collapse
Recovery is to be flashed in download mode as has been on the HTC 10 the case. In fact download mode can be viewed at as fastboot mode of the phone.
Sent from my htc_pmeuhl using XDA Labs
Left a note here.
My first-batch U11 can be booted to twrp with "fastboot boot twrp-blahblah.img" under bootloader menu (I wish I didn't remember it wrong)
But it can't be done after it came back from repair (no power issue with unknown reason), which motherboard had been replaced and updated to Oreo already.
Anyway, it seems that stock-recovery backup is not required since there's reliable source of stock-recovery which inside the OTA file.