Database Users

[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)

[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.

Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!

yeah! good work!

Srsly. Awsom.
Someone sticky this....

Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.

cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery

cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?

Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi

Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.

distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi

ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.

i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky

In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App

I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App

qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed

distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.

shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.

I can confirm that this method works, without unlocking the BL or erasing the SD part.

This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.

cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.

[Q] Anyone knows the difference between bootloader 4.13 and 4.18 ?

Bootloader is the last thing I would like to touch unless it is absolutely necessary. So is wondering what is the key changes that warrant to flash it.

chimpanzeexda said:
Bootloader is the last thing I would like to touch unless it is absolutely necessary. So is wondering what is the key changes that warrant to flash it.
Click to expand...
Click to collapse
I've been wondering the same... Also, excuse my ignorance, but bootloader is not updated when you do OTA from 4.21 to 4.22 ? It has to be update separately?

dalanik said:
I've been wondering the same... Also, excuse my ignorance, but bootloader is not updated when you do OTA from 4.21 to 4.22 ? It has to be update separately?
Click to expand...
Click to collapse
I upgraded mine using the adb sideload method, and it also changed my bootloader to 4.18. I don't know if there are any significant changes, but I think its best to upgrade to the latest bootloader as you will have the latest and greatest, and most development will stem using 4.18 anyway. So just upgrade.

dalanik said:
I've been wondering the same... Also, excuse my ignorance, but bootloader is not updated when you do OTA from 4.21 to 4.22 ? It has to be update separately?
Click to expand...
Click to collapse
I'm also wondering... by the way, dalanik, the bootloader IS updated via the OTA... it's in the UPDATER SCRIPT. (And it's how I got updated).
Code:
...
....
ui_print("Writing bootloader...");
package_extract_file("bootloader.raw", "/dev/block/platform/sdhci-tegra.3/by-name/USP");
...
..
Interestingly, in the FLASH-ALL.bat/sh script, in the FACTORY IMAGE of JDQ39, the new bootloader is flashed by the more traditional method, using fastboot...
Code:
..
...
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
...
..
----
Anyway, I've subsequently NANDROID restored back to my 4.2.1 based CyanogenMod ROM... with the updated bootloader... only issue is, when in FASTBOOT mode, the Vol UP/DOWN keys, when USB plugged in (to PC or charger, it doesn't matter), sometimes become non-responsive - meaning I can't select recovery, for example. It's a minor quirk, easily resolved by disconnecting and then reconnecting again.
What we need here, is a BOOTLOADER guru; some guy, who knows everything there is to know about BOOTLOADERS... I'm sure there is one out there, somewhere.
Rgrds,
Ged.

If you update your N7 OTA, everything will be updated. You DO NOT NEED to update the bootloader. It's a whole package that is ready for installation.

But I cannot use OTA without reverting back a number of things
I would assume bootloader in android is just the equivalent of GRUB. The reason I don't want to touch it is that it is if I am not mistaken the supervisor of the device so if I get a bad flash, I would lose access to it even in fastboot.

GedBlake said:
Interestingly, in the FLASH-ALL.bat/sh script, in the FACTORY IMAGE of JDQ39, the new bootloader is flashed by the more traditional method, using fastboot...
Click to expand...
Click to collapse
In fact, the bootloader actually flashes it in place in both instances.
"USP" (or "staging") is kind of a garbage partition - do a dd (read dump) of yours right now and you will easily convince yourself that the bootloader ain't in there.
Whenever a hardware reset occurs, the bootloader regains control of the device. I have to presume that on every hardware reset cycle, the existing bootloader inspects the USP. Clearly it can not simply blind-flash whatever is in there; that would suggest that the the bootloader blob thrown into USP has a MIC (crypto Message Integrity Check) and the existing bootloader can perform a signing check on it.
Don't know if the same is true of a fastboot flash - but then who wants to run an experiment where they purposely flash garbage into the bootloader in order to find out?
On other (HTC) devices I had, the bootloader would inspect (bootloader version) strings stored in the misc partition, and resolutely refuse to flash factory ROM files if it got a whiff of a potential downgrade install. That was easily overcome by byte-patching the misc partition from a rooted OS, though.
[speculation]With this USP -> real_bootloader_location funny business going on, I am wondering - if the MIC key is version stepped (that is, the public key provided in the current version of the bootloader is updated with every revision, and the *next* version of the bootloader is signed with this key) then this would create a upgrade-only-lockstep sequence.[/speculation]
Has anybody ever downgraded their bootloader - either with a "recovery-flashable zip", or fastboot? Just curious.

bftb0 said:
Has anybody ever downgraded their bootloader - either with a "recovery-flashable zip", or fastboot? Just curious.
Click to expand...
Click to collapse
I have downgraded my bootloader for my N7 from some version to the 3.44 then upgraded to 4.13 then upgraded to 4.18. The reason I downgraded I cannot remember.
And no I did not use a recovery flashable zip, I went into fastboot and flashed it with an img.

[Q] Everyone keeps talking about bootloader downgrade

But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?

Zalmoxis12 said:
But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Click to expand...
Click to collapse
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.

simon_lefisch said:
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
Click to expand...
Click to collapse
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?

Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
http://searchenterpriselinux.techtarget.com/definition/boot-loader

Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
bootloader loads all the partitions and makes sure they work together, two examples of the stuff bootloader handles:
-bootloader boots
-bootloader then loads kernel making sure nothing wrong and if there is then you get no boot and instead you are thrown to fastboot to fix the problem
-after kernel loads bootloader loads system if corrupted/missing you get stuck in a bootloop unless you have custom recovery then you get stuck in recovery
-bootloader loads rest of partitions while the system/kernel begin to boot rom
when doing ota:
-phone reboots and loads bootloader
-bootloader loads ota into a partition on phone designed to decompile and apply ota into system/kernel partitions
-bootloader makes sure that system/ota are correct and compatible to apply update
-bootloader does root check process in the rtf partition and if rooted bootloader cancels ota process
so in short bootloader is most important asset, it is what decides the kernel to boot(you can mod a bootloader so that you can have too kernels and this is also how you create multi boot for boot more than one rom), it boots the rom, and it handles all other partitions in more than one way

[RUU][GUIDE]Lollipop A5_DUG firmware to fix WiFi

What:
the firmware.zip from hTC desire 816 dual sim A5_DUG CID:HTC__J15,HTC__001,HTC__A07 MID:0P9C70000 OTA update for Europe. (to check for your Device IDs, go to fastboot mode and type "fastboot getvar all")
Why:
users who update from Kitkat to Lollipop using TWRP/CWM backups instead of OTA, run into Wifi or touch problems because TWRP/CWM backups don't contain firmware updates. so by flashing this firmware, they can fix those issues. notice that your current ROM has to be 1.58.401.11 or 2.34.401.1. If you come from any other ROM, this file might not work properly or behave unexpectedly. of course you can try it at your own risk.
Where:
you can find the firmware.zip here (this naturally contains the stock 5.0.2. recovery, so if you need, you can extract it and get the stock recovery). you can also find proper OTA/TWRP/CWM Backups here.
How:
0- download firmware.zip and put it on the same folder as your platform tools (Adb/Fastboot) folder. a good source to get the minimal tools would be here.
1- Reboot your device to bootloader and choose fastboot (use power+volume down combination , or type "adb reboot bootloader" in console)
2- if you're S-On, you'll need to relock your bootloader. to do that, when in Fastboot, type "Fastboot oem lock". if you're S-off, you can skip the relocking part.
3- type "fastboot oem rebootRUU" to put the phone in firmware update mode. you'll see a silver hTC logo in the center of a black screen
4- type "fastboot flash zip firmware.zip" in console and press enter. (*this will also write 5.0.2. stock recovery so you'll lose your custom recovery)
5- type the same "fastboot flash zip firmware.zip" in console again.
6- type "fastboot reboot-bootloader" to reboot.
7-now, in order to have root and install custom recovery(TWRP/CWM) for restoring a Lollipop backup, you'll have to unlock bootloader again. you can try putting your old Unlock_code.bin in platformTools folder and typing "fastboot flash unlocktoken Unlock_code.bin". If that doesn't work, you'll have to go through the process of requesting a new Unlocktoken from htcDEV, which there are various guides for, around XDA.
8- Install TWRP again.
9- Now you can put your TWRP Lollipop backup on phone storage and restore it.
10- If all you need is to just install Stock recovery, download the firmware.zip and extract it. put the recovery.img file in your fastboot folder. then in fastboot mode, type fastboot flash recovery recovery.img. be warned that after this, you will lose your custom recovery and will not be able to use twrp/cwm to backup/restore/flash files.
Who:
This is a continuation of the work done by our good user, 12rithy. you can find necessary firmware for A5_DWG and for S-OFF devices in that thread..
also, the firmware was extracted from OTA uploaded by another good user, crash6x86. If you need the OTA or TWRP/CWM backups of it, you can find them at its thread here.

Can you give a short Video Toturial for this Please,because i dont know how to do this .Please

Harris777 said:
Can you give a short Video Toturial for this Please,because i dont know how to do this .Please
Click to expand...
Click to collapse
I'm afraid that's not possible for me. Also, if you find the instructions too confusing or complex, I advise against tempering with your device because you may run into problems at any stage and it would require a degree of skill and persistence to overcome. It probably won't be worth the effort unless your main motive is to gain experience.
Still, If you've done this before (unlocked and rooted your device, worked with custom recoveries and custom Roms) and if your device is the Europe Dual sim a5_dug, I'll try to help if any part is unclear or if you run into any problems in the process.

There is an easier, quicker way of flashing the firmware, but you must have an sdcard. I'll post later a how to after work.
Sent from my HTC One_M8 using XDA Free mobile app

crash6x86 said:
There is an easier, quicker way of flashing the firmware, but you must have an sdcard. I'll post later a how to after work.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
That would be great, Thanks

seekfind said:
I'm afraid that's not possible for me. Also, if you find the instructions too confusing or complex, I advise against tempering with your device because you may run into problems at any stage and it would require a degree of skill and persistence to overcome. It probably won't be worth the effort unless your main motive is to gain experience.
Still, If you've done this before (unlocked and rooted your device, worked with custom recoveries and custom Roms) and if your device is the Europe Dual sim a5_dug, I'll try to help if any part is unclear or if you run into any problems in the process.
Click to expand...
Click to collapse
yeah i know how to root and install Custom Recovery and ROM but i dont understand how to flash this firmware

Thanks mate . it worked for me, thank you for your effort

Rename the firmware to 0P9CIMG.zip.
Then boot to bootloader.
Follow the on screen directions to update.
I made sure to have a stock recovery, I haven't tried flashing firmware with a custom recovery. I do know that my M8 can flash the firmware with a custom recovery.
After everything updates, remove the firmware update from the sd card.
If anyone has any questions, I'll try to answer them.
Sent from my HTC One_M8 using XDA Free mobile app

crash6x86 said:
Rename the firmware to 0P9CIMG.zip.
Then boot to bootloader.
Follow the on screen directions to update.
I made sure to have a stock recovery, I haven't tried flashing firmware with a custom recovery. I do know that my M8 can flash the firmware with a custom recovery.
After everything updates, remove the firmware update from the sd card.
If anyone has any questions, I'll try to answer them.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
So if you boot to bootloader, it will automatically recognize the file and start updating firmware?
about the second point, you can flash firmware while having a custom recovery but after flashing the firmware you will lose the custom recovery because the firmware includes a stock recovery which will replace your custom one.
The biggest inconvenience here is, that you have to relock your bootloader before flashing firmware, because it won't accept firmware on an unlocked bootloader.
Harris777 said:
yeah i know how to root and install Custom Recovery and ROM but i dont understand how to flash this firmware
Click to expand...
Click to collapse
I remember you saying somewhere that you have a Chinese unicom device. if it's S-on, then this file won't work for you. If it's S-off and you have SuperCID, then you can use it. doing it is as easy as following the steps. if any step is unclear, let me know and I'll explain it.

seekfind said:
So if you boot to bootloader, it will automatically recognize the file and start updating firmware?
about the second point, you can flash firmware while having a custom recovery but after flashing the firmware you will lose the custom recovery because the firmware includes a stock recovery which will replace your custom one.
The biggest inconvenience here is, that you have to relock your bootloader before flashing firmware, because it won't accept firmware on an unlocked bootloader.
I remember you saying somewhere that you have a Chinese unicom device. if it's S-on, then this method won't work for you. If it's S-off and you have SuperCID, then you can use it. doing it is as easy as following the steps. if any step is unclear, let me know and I'll explain it.
Click to expand...
Click to collapse
yes bro i have unicom version it is S-On. you said this method won't work So is there any other way of fixing wifi and touch issue in Lolipop backup ?

seekfind said:
So if you boot to bootloader, it will automatically recognize the file and start updating firmware?
about the second point, you can flash firmware while having a custom recovery but after flashing the firmware you will lose the custom recovery because the firmware includes a stock recovery which will replace your custom one.
The biggest inconvenience here is, that you have to relock your bootloader before flashing firmware, because it won't accept firmware on an unlocked bootloader.
I remember you saying somewhere that you have a Chinese unicom device. if it's S-on, then this method won't work for you. If it's S-off and you have SuperCID, then you can use it. doing it is as easy as following the steps. if any step is unclear, let me know and I'll explain it.
Click to expand...
Click to collapse
I didn't have to lock the boot loader, if I remember correctly. I am s-off and super cid with the desire 816w
Sent from my HTC One_M8 using XDA Free mobile app

crash6x86 said:
I didn't have to lock the boot loader, if I remember correctly. I am s-off and super cid with the desire 816w
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
That explains it. no need for relocking bootloader when you're S-OFF because that's basically a security precaution by hTC. I miss the old days with my S-off hTC One XL. I flashed so many files from different sources that it lead to a Hard-Brick
Harris777 said:
yes bro i have unicom version it is S-On. you said this method won't work So is there any other way of fixing wifi and touch issue in Lolipop backup ?
Click to expand...
Click to collapse
Sorry, I meant this file won't work for you. If your problems are firmware oriented, you'll just have to find the right firmware for your variant (or the right OTA) and flash it using this method. files for the chinese variant are not hard to come by if you look for them over the net.

Hello I was looking for wifi firmware for my HTC Dersire 816 single sim model A5_ul (S-on).. But cant find it any where...

shawon3050 said:
Hello I was looking for wifi firmware for my HTC Dersire 816 single sim model A5_ul (S-on).. But cant find it any where...
Click to expand...
Click to collapse
you should look for A5_ul OTA (not the CWM/TWRP backup). you can also use the RUU from this thread if your variant matches; it will fix the wifi problem

after following your way i will able to update lollipop in my phone but now there is a problem when i clicked to download something it show's (no sd card ).But i already have a SD card .

hello
i need firmware for desire 816 dual sim htc__059
or way to s-off my device and get supercid !!!
i lost my stock rom so , please i need your help on this

Unable to install
It shows an error .. mismatch

komalreddy said:
It shows an error .. mismatch
Click to expand...
Click to collapse
in what step? and what's the error? and your exact device specifications?
wanted_syrian said:
hello
i need firmware for desire 816 dual sim htc__059
or way to s-off my device and get supercid !!!
i lost my stock rom so , please i need your help on this
Click to expand...
Click to collapse
you can find a nandroid backup for your device, which is much easier than s-off.
for s-off you'll have to pay 25$ and use sunshine. you can also take your phone to hTC care..

Installing the firmware it shows error 042

komalreddy said:
Installing the firmware it shows error 042
Click to expand...
Click to collapse
1-did you relock your bootloader before flashing firmware?
2-is your device exactly the same as models I mentioned in the first post?

How to re unlock bootloader

If go to stock and relock bootloader for OTA, what is procedure to unlock again? Do you go back to the Moto site for a new code, or will they expect you to have the original unlock code (thus you could be outta luck if you bought the phone used , with an unlocked bootloader.)

The procedure is the same as when you first unlocked, although if you have the original unlock code you can skip getting a new one from Moto's site (it's the same code anyway), same rules apply, it will wipe everything and you must have OEM Unlocking in Developer options enabled as when the bootloader is relocked this option is turned off and must be turned on again manually.
Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc).

"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?

hometech99 said:
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
Click to expand...
Click to collapse
Here ya go..
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

hometech99 said:
"Be aware you do NOT have to lock the bootloader to get an OTA update, the update script and the OTA server do not care if your bootloader is unlocked or not. The essentials are stock recovery and a stock system and boot image (meaning no root, Xposed, etc)."
Oh good...I'll try that first when ready . There's a thread somewhere with correct bootimage, recovery, and system I think?
Click to expand...
Click to collapse
Just look in my sig... if you read there are links to firmware, and instructions to lock and flash, or just flash the factory image. I would recommend flashing the complete system image though, not just the pieces.

acejavelin said:
I would recommend flashing the complete system image though, not just the pieces.
Click to expand...
Click to collapse
..but your flashboot instructions show the pieces. Did you modify the process, and get the whole system image?
Thanks!

hometech99 said:
..but your flashboot instructions show the pieces. Did you modify the process, and get the whole system image?
Thanks!
Click to expand...
Click to collapse
No, I meant each piece of the full image, don't skip any parts.