Database Users

DEsire Z/G2 added to official bootloader unlock program

Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/

noob here with a question... rooting is the same as unlocked bootloader??

coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.

thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?

coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.

I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?

flash custom recovery first, from there flash the rom

if you're s-on, bootloader is still locked....

artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying

I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.

how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.

pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!

flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.

HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.

Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.

I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.

[Q] Help with 4.4.4 OTA

I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len

If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492

sfobrien said:
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
Click to expand...
Click to collapse
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP

Lenster45 said:
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Click to expand...
Click to collapse
Since you took the OTA your bootloader may be locked. After you get it unlocked I gave you where to get the recovery you need, the one you have is not KitKat friendly.

Lenster45 said:
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
Click to expand...
Click to collapse
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.

charesa39;53763629
EDIT: Oh said:
Strange, had a friend who took the OTA awhile back and it locked the bootloader. It was a JB version maybe they changed it with KitKat ? ( he could have locked it prior to my getting it going who knows) Thanks for the info, have never used an OTA since I got my N10 when it first came out.
Click to expand...
Click to collapse

charesa39 said:
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
Click to expand...
Click to collapse
That did it. Thanks

Hi,
Could you add a [SOLVED] tag to the title, as it is now solved ?
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505

[Q] File recovery From Bootloop'ed Nexus 4

Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?

Your bootloader is locked, correct?

ashyossi said:
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Click to expand...
Click to collapse
If your bootloader is unlocked you can try flashing TWRP recovery which has a built in file manager and mtp function to copy files to computer. You can also try to "dirty flash" another lollipop rom which will not wipe the data, but may not work.

Yeah, this is the only option, however, this can only happen if his bootloader is unlocked

lolcakes203 said:
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
Click to expand...
Click to collapse
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?

ashyossi said:
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
Click to expand...
Click to collapse
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.

theminikiller said:
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
Click to expand...
Click to collapse
and flushing the same STOCK rom that i got as OTA should work or does it only work with custom ROM's?

i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?

ashyossi said:
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
Click to expand...
Click to collapse
Yes, after you've flashed twrp you should be able to access your files from a computer if you're booted in recovery.

soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?

ashyossi said:
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
Click to expand...
Click to collapse
When the storage is completely empty, are you booted in recovery, the bootloader or just trying to boot normally? When you say it's empty, do you actually see the device on your computer? If so, is it completely empty with no folders or files or anything, or just stock stuff?

Can you check mount and make sure all the storage volumes are mounted? It's usually blank when they are all manually unmounted.

Needing help with Safestrap Recovery, Will not boot to recovery

Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.

Safestrap no longer works with lollipop. Flashfire is the only real way to install zips after android 5.0.
Cheers,
B.D.

Nakerenski said:
Hi!! I just recently rooted my phone. I heard Safestrap was the only recovery that would work with my sm-n900v. I installed 3.65 saftstrap, with busybox, and selected install recovery. then i hit reboot recovery. Instead of going into recovery, it just rebooted. so, no what. Would like to know what I did wrong or what I need to do to fix this and or another recovery that will work and not trip a security warning when the phone boots and show the yellow triangle of doom as i call it. any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Yeah I'm having the same problem EXACT problem, feel like I bought this phone for no reason. But, I'm having the idea of downgrading to 4.3 somehow (If it's even possible, Odin maybe?) and installing SafeStrap there, and from there I'll install a custom 6.0 ROM.

You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.

bftb0 said:
You can't downgrade from 5.x to any version of 4.x afaik.
As the prior respondents noted, Safestrap doesn't work with 5.x.
So it's a non-starter if you are already on OB6 or OF1.
From any root shell it is possible to (manually, using "dd") overwrite the recovery/boot partition with whatever recovery/boot image you prefer, but that will do you no good as unsigned kernels can not be booted unless the bootloader is unlocked. You will simply get your "triangle of doom" if the bootloader is still locked.
From OB6 or OF1, the sequence is:
- get rooted
- get unlocked
- do what you want*
*making sure you never over flash your unlocked bootloader.
Click to expand...
Click to collapse
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by
bftb0 said:
- get unlocked
Click to expand...
Click to collapse
do you mean to SIM-unlock? Cheers.

GoatH3ad said:
Ahh Ok, good to know. But how should I unlock my bootloader, if it's even possible? And by do you mean to SIM-unlock? Cheers.
Click to expand...
Click to collapse
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.

bftb0 said:
Bootloader unlock, not SIM/carrier unlock
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Use the binary provided in post #218, not in the OP
It's a good idea to read the entire thread before you dive in.
Click to expand...
Click to collapse
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.

GoatH3ad said:
So I downloaded the manual unlocker app the guy (donc113) said i needed, didn't install the app. Then I downloaded his binary (unlock.zip) and put it in /system/bin/ like he said, I also extracted the contents in /system/bin/ as well. I installed the manual unlocker app he provided, ran it twice as he stated I needed to do. Went to ROM Manager by Clockworkmod and went to Recovery Setup, Install ClockworkMod Recovery, Selected my phone, clicked Flash ClockworkMod Recovery. Rebooted to Recovery and it still says I need to take the phone to the Verizon store. What exactly did I do wrong? I've done everything Donc113 provided and my bootloader is STILL locked apparently.
Click to expand...
Click to collapse
Did you:
- Check to make sure your phone CID value starts with 0x15 ?
- Record any error messages that occurred in either of the two runs of the unlocker program?
- Boot into Odin Mode to see if it says "MODE: DEVELOPER" in the last line of text over in the upper left hand side of the Odin/Download screen?
The symptoms you mention sound as if you are rooted, but failed to unlock the bootloader.
I note that you would not be asking these questions if you had read THE WHOLE THREAD as I suggested. Would you prefer that I stop helping?

Soft Brick/possible full brick in need of help

I was trying to root and unlock boot loader. I was on the latest update B29 and tried following the guide but used the B27 files. I flashed the files got into TWRP but for some reason my system got wiped. I can get into fastboot, recovery, and EDL but when i try to boot my phone regular it boots ZTE boot screen real quick and then goes into a BLACK screen and stays there? Any Suggestions on what I can do? If I try to unlock the bootloader it says failed cannot do remotely probably because my phone system get erased and so the option isnt clicked in phone to allow oem unlock.
I was going to try flashing;
- ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip
- ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip
There is some kind of problems with android file host does anyone have a copy of these two files hosted somewhere else?
Thanks

Did you make the backups shown in both the twrp flashing guide and the unlock bootloader guide?
Could you provide a little more detail on what you did so far?
neo4uo said:
I was trying to root and unlock boot loader. I was on the latest update B29 and tried following the guide but used the B27 files. I flashed the files got into TWRP but for some reason my system got wiped. I can get into fastboot, recovery, and EDL but when i try to boot my phone regular it boots ZTE boot screen real quick and then goes into a BLACK screen and stays there? Any Suggestions on what I can do? If I try to unlock the bootloader it says failed cannot do remotely probably because my phone system get erased and so the option isnt clicked in phone to allow oem unlock.
I was going to try flashing;
- ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip
- ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip
There is some kind of problems with android file host does anyone have a copy of these two files hosted somewhere else?
Thanks
Click to expand...
Click to collapse

lafester said:
Did you make the backups shown in both the twrp flashing guide and the unlock bootloader guide?
Could you provide a little more detail on what you did so far?
Click to expand...
Click to collapse
I ended up going to ZTE site and getting there B20 image and flashed back my backed up recovery and boot and flashed the update zip with there recovery and I am back in business now. I was trying to unlock and root but somewhere or how my system got deleted so it would not boot. What is the easiest way to unlock the BL and then root? Is DrakenFX the most up to date way? Anyways thanks for the reply, I was going to download DrakenFX files for stock recovery, but Android File Host is having some problems and you can not download anything from them right now

neo4uo said:
I ended up going to ZTE site and getting there B20 image and flashed back my backed up recovery and boot and flashed the update zip with there recovery and I am back in business now. I was trying to unlock and root but somewhere or how my system got deleted so it would not boot. What is the easiest way to unlock the BL and then root? Is DrakenFX the most up to date way? Anyways thanks for the reply, I was going to download DrakenFX files for stock recovery, but Android File Host is having some problems and you can not download anything from them right now
Click to expand...
Click to collapse
Yes, flash twrp and flash drakenfx unlockbootloader file. Look for the newbie guide to unlocking and follow. Read the thread first as always.