Alright, HBoot is the bootloader - sort of like BIOS, it tells the phone what to do when I push the power button.
But what about upgrading to HBoot .35? It's recommended/required for Gingerbread, and I'm fine with performing the upgrade, I just have a few questions as to what would happen after the upgrade and reverting back.
Would the upgrade unlock my bootloader (if it were still locked)?
Would I still be able to use Nandroid to restore to a previous version of Android even if it had used a different HBoot?
Would Nandroid revert my HBoot back to .33? I know Nandroid backs up a folder called "Boot", and from what I had read that's the bootloader.
If it's not possible to revert HBoot via Nandroid, would my only other option be ADB?
And finally, is there anything else which simply cannot be stressed enough, that I should know?
Nandroid does not touch the HBOOT. HBOOT is the bootloader, boot.img is the boot image comprising the kernel and some configuration files required for the booting process.
Nevertheless, all Android versions should be able to run with higher versions of HBOOT. You might not be able to restore old Eclair builds because of the radio version, but HBOOT should not be a problem.
I imagine the OP refers about the upgrade because some gingerbread ROMS recommend having the latest HBOOT.
SPL:
[HBOOT-0.35.0017]
http://android.clients.google.com/pa...-0.35.0017.zip
Thanks you guys, you definitely helped clear up some confusion.
How do I flash it?
bryanchapman9999 said:
How do I flash it?
Click to expand...
Click to collapse
Via recovery - coun't be simpler
bryanchapman9999 said:
Via recovery - coun't be simpler
Click to expand...
Click to collapse
You just download the file and flash it from recovery (clockworkmod in my case)? I read in some threads you have to rename it and what not to a certain file name and go into the bootloader and it asks you if you want to upgrade?
I'm confused.
Just some additional info -- The NAND flash of our N1's has 5 partitions: misc, boot, cache, system, and userdata. The misc partition (mtd0) is the HBOOT. Nandroid does not back that up.
Sent from my Nexus One using XDA App
omer1112 said:
You just download the file and flash it from recovery (clockworkmod in my case)? I read in some threads you have to rename it and what not to a certain file name and go into the bootloader and it asks you if you want to upgrade?
I'm confused.
Click to expand...
Click to collapse
You don't have to rename it. You can flash it: 1) in recovery, 2) using flash_image via adb or a terminal, or 3) (I think) using fastboot.
Sent from my Nexus One using XDA App
G0belet said:
Nandroid does not touch the HBOOT. HBOOT is the bootloader, boot.img is the boot image comprising the kernel and some configuration files required for the booting process.
Nevertheless, all Android versions should be able to run with higher versions of HBOOT. You might not be able to restore old Eclair builds because of the radio version, but HBOOT should not be a problem.
Click to expand...
Click to collapse
While I believe you about higher HBOOT being ok for earlier versions I would feel safer having a copy of my current HBOOT as a flashable zip. Is it possible to revert simply by flashing a zip and does anyone know of a link to the older HBOOT?
ellesshoo said:
While I believe you about higher HBOOT being ok for earlier versions I would feel safer having a copy of my current HBOOT as a flashable zip. Is it possible to revert simply by flashing a zip and does anyone know of a link to the older HBOOT?
Click to expand...
Click to collapse
Just so I know what you are trying to accomplish: why would you ever want to downgrade? Most Nexus One's now should have the 0.35 HBOOT (some came with it out of the box, most got updated with the latest OTA package, and some upgraded manually). The version of HBOOT you have doesn't make any difference, aside from one: the newer HBOOT is larger than the older one. Basically it takes some space away from the recovery partition and adds it to the misc (HBOOT) partition. Some recoveries (like Amon_RA 2.0) are quite large and may not fit in the recovery partition if you are on the latest HBOOT, however, Amon_RA's latest recover is smaller, and fits no problem. Aside from that, there is no real differences between the two HBOOTs, and no reason to ever downgrade. And besides, word on the street is that 0.35 will be a prerequisite from installing OTA Gingerbread.
The new HBOOT isn't larger, it adds space to BOOT partition, not HBOOT. This allows to overcome a problem some Nexus Ones have - if a bad sector is present in BOOT partition, some kernels would fail to flash on the older HBOOT - not having enough space to write boot.img. New HBOOT solves it by making the recovery smaller and adding the space to BOOT partition instead.
cmarti said:
I imagine the OP refers about the upgrade because some gingerbread ROMS recommend having the latest HBOOT.
SPL:
[HBOOT-0.35.0017]
http://android.clients.google.com/pa...-0.35.0017.zip
Click to expand...
Click to collapse
The link to that HBOOT ZIP is broken...anyone have an updated link ?
marcelol said:
The link to that HBOOT ZIP is broken...anyone have an updated link ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=9389909&postcount=109
I just wanted to add my voice to the throngs of people saying "This saved me!!" Because it just did. So, thanks!
Related
Note: You *MUST* be s-OFF for this to work properly. If you're not, it won't work.
1. Download this zip file: http://www.mediafire.com/?mi4utrhbacdbbxt mirror: http://www.megaupload.com/?d=LSR7QG9W
2. Rename it to PB31IMG.zip (uppercase name and lowercase extension matters, make sure it's not .zip.zip also) and push it to the root of your sdcard, so it's /sdcard/PB31IMG.zip
2 1/2. MAKE A NANDROID BACKUP (in case you ever want to go back)
3. Reboot into HBOOT by holding vol down while booting up, or by typing "adb reboot oem-42"
4. Hit vol-up when it asks if you want to apply the zip.
5. Wait for it to finish, then reboot when it asks you to.
Congrats, now you're back to stock 2.1-update1 with the original 1.00 radio.
thanks to aiccucs for his work in compiling the stock zip!
Cheers, mate.
just curious but don't you also need to put back the stock recovery back on? and that zip is stock without root, right?
the337 said:
just curious but don't you also need to put back the stock recovery back on? and that zip is stock without root, right?
Click to expand...
Click to collapse
Completely stock without root. Includes stock system, kernel, recovery, radio, and HBOOT as well as a data wipe. The only thing not stock is the fact you're still going to be S-OFF, but that's nothing really to worry about. VZW techs don't really know how to check that .
Doing this will 100% allow you to receive the OTA when Verizon finally releases it right?
ZFriedenreich said:
Doing this will 100% allow you to receive the OTA when Verizon finally releases it right?
Click to expand...
Click to collapse
Yes.
/10char
good work A++++
I had originally pulled the stock Rom image from the RUU (ran the RUU and snagged the image from the temp folder). I was able to flash back to that but had to do some trickery first pushing some files over to the phone in and then running some commands in ADB. Is this just that same image extracted directly from the stock RUU? Or has this been modified in some way?
I'm assuming it's either been modified to allow flashing without pushing those other two files first, or s-off disables the check that would normally throw a "image you are attempting to flash is older" error.
I thought we could just flash stock recovery and apply the OTA... This route, we lose all our settings and apps, correct?
Sent from my Incredible via TapaTalk...
Awesome post! Thanks man
Sent from my ADR6300 using XDA App
And having S-Off, if VZW tries to remove our root ability, all we would have to do is install SU back on correct?
Can't you just apply the ruu's with the new clockworkmod?
Sent from my ADR6300 using XDA App
I got the following quote from http://unrevoked.com/rootwiki/doku.php/public/forever
"How can I use S-OFF to recover from an unrooted update?
S-OFF gives your device permanent NAND unlock in the booted system, and also disables HBOOT's signature checking on firmware zip files. So, even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system. We have provided ClockworkMod and Amon-Ra recovery images for you to use for this purpose. "
Hatman41 said:
I got the following quote from http://unrevoked.com/rootwiki/doku.php/public/forever
"How can I use S-OFF to recover from an unrooted update?
S-OFF gives your device permanent NAND unlock in the booted system, and also disables HBOOT's signature checking on firmware zip files. So, even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system. We have provided ClockworkMod and Amon-Ra recovery images for you to use for this purpose. "
Click to expand...
Click to collapse
Yeah, I don't think we need to revert to original hboot/radio/etc... I think we just need stock recovery and a stock rom to get the OTA
anyone besides the OP tried this yet?
kentoe said:
Yeah, I don't think we need to revert to original hboot/radio/etc... I think we just need stock recovery and a stock rom to get the OTA
Click to expand...
Click to collapse
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
What about reverting everything back if we have S-ON? Sorry if this is a n00b question.
Ruggerxpunk said:
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes, so therefore you wouldn't have to do anything besides going back to a stock rom.
Xxq TZ pxX said:
What about reverting everything back if we have S-ON? Sorry if this is a n00b question.
Click to expand...
Click to collapse
You can use this.
http://forum.xda-developers.com/showthread.php?t=727263
Ruggerxpunk said:
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Also know if your rooted with s-on you cannot flash proper otas because the signature check is there and it want allow you to flash a legit signed ota with clockwork. Also know if you accept the ota you will loose root. And won't be able to gain it back without s-off. I really don't understand why people are so apprehensive. Live a little man. It's just a phone. Not a ferrari. Even though it runs like one.
Hi!
I just want to flash my Voda-Nexus with the original android-version from google (like discussed in this thread) and the newest radio-version.
My simple question:
How can i do this
(Or comes radio 5.12.00.08 via OTA?)
It looks like this version http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
includes an older radio.
If you still have locked bootloader:
Flash the newest Android, root, install custom recovery, flash radio.
If your bootloader is unlocked:
Flash the newest Android, flash radio using fastboot.
Jack_R1 said:
If you still have locked bootloader:
Flash the newest Android, root, install custom recovery, flash radio.
(...)
Click to expand...
Click to collapse
I was thinking about this way too. Only problem i see, is that some users seem to have problems with OTA-updates, when a custom recovery is installed. And to get back the stock recovery i have to unlock the bootloader, haven't i?
Isn't it possible to simple replace the old radio.img from the passimg.zip with the newest one? Or can i simply kick out the radio.img-file from the .zip-folder?
hmm, sounds too easy to be true...
BTW:
Do only Korean people get radio-updates?
You can't do anything with official ZIPs, once you do - they won't pass stock recovery verification.
When you install a newer radio, you can PASSIMG any build over it, and most probably it won't downgrade the radio, it can only upgrade it or leave it alone.
No, you don't need to unlock to put stock recovery on. It's enough to copy 2 scripts that should be deleted back on the phone, and they'll reflash your recovery to stock. Look at the Wiki, find the 2 files that needed to be deleted, back them up before flashing custom recovery, restore them, reboot.
So first I'll install the newest radio before flashing stock rom via passimg.zip-methode.
Then i flash the passimg.zip
If the radio is reseted to a previous version (what should most likely not appear, like you said) I'll backup recovery-from-boot.p and install-recovery.sh, which are installed right now on the phone.
Then root, install a custom recovery, install the newest radio, put the backuped files back in place and reboot. Optionally i will unroot.
After that i should have an unrooted stock rom with stock recovery.
Right?
thanks in advance!
In my experience, PASSIMG does replace the radio with whatever is in the zip, even if it's a downgrade.
Sent from my Nexus One using XDA App
So the most important thing to know for me is, if it really helps to just put those 2 files back.
I've read a few threads about reseting the recovery to stock, but all suggestions include the use of the SDK, which i would like to avoid.
n0w4y said:
....
Right?
thanks in advance!
Click to expand...
Click to collapse
Yep. That would cover all the possible variants.
I'm a brand new Canadian Incredible S owner looking to root and flash new roms. I've been reading a lot of forum posts and have some questions about flashing roms and radios. I'm coming from the Desire (Bravo) and on that phone, I've always flashed roms and radios via CWM recovery. However, it seems that for the IncS, many users have instead flashed them through HBOOT.
Here's what I want to do:
- Apply S-OFF via Alpharevx, install CWM, and root
- Take the 2.30.405.1 stock GB ruu, extract the rom.zip, remove the HBOOT and recovery files, and root it via dsixda's kitchen
- Flash the rooted GB rom and radio via CWM
So...can it be done this way through CWM? Or does the flashing of both the rom and radio have to go through HBOOT?
I apologize if this topic has been mentioned before, but it seems as if things aren't quite as simple as my old Desire was and I want to make sure that what I'm planning to do won't ruin the phone.
I'm not sure about this, but I think you can flash .zip ( Rom, radio, recovery etc) either through hboot or recovery, only difference being that for hboot the zip has to have the specific name ( PG32IMG.zip or sometimes like that). Could somebody confirm if this is correct ?
bracketologist said:
I'm a brand new Canadian Incredible S owner looking to root and flash new roms. I've been reading a lot of forum posts and have some questions about flashing roms and radios. I'm coming from the Desire (Bravo) and on that phone, I've always flashed roms and radios via CWM recovery. However, it seems that for the IncS, many users have instead flashed them through HBOOT.
Here's what I want to do:
- Apply S-OFF via Alpharevx, install CWM, and root
- Take the 2.30.405.1 stock GB ruu, extract the rom.zip, remove the HBOOT and recovery files, and root it via dsixda's kitchen
- Flash the rooted GB rom and radio via CWM
So...can it be done this way through CWM? Or does the flashing of both the rom and radio have to go through HBOOT?
I apologize if this topic has been mentioned before, but it seems as if things aren't quite as simple as my old Desire was and I want to make sure that what I'm planning to do won't ruin the phone.
Click to expand...
Click to collapse
The latest version of dsixda's HTC kitchen now supports adding a radio.img to the rom.zip file that gets generated, so you can just flash your custom rom using CWM and not have to flash the GB radio separately.
Thanks for the info. If I do this through CWM, do I still have to worry about changing the Model ID since I have the Canadian model? Or is that something that only comes up if I flash through HBOOT?
And I'm guessing that I only have to worry about having the ENG HBOOT if I flash the radio through HBOOT. This also shouldn't be an issue if I do it through CWM as well. Is this right?
bracketologist said:
Thanks for the info. If I do this through CWM, do I still have to worry about changing the Model ID since I have the Canadian model? Or is that something that only comes up if I flash through HBOOT?
And I'm guessing that I only have to worry about having the ENG HBOOT if I flash the radio through HBOOT. This also shouldn't be an issue if I do it through CWM as well. Is this right?
Click to expand...
Click to collapse
No you don't have to worry about changing the Model ID when you flash a custom ROM using CWM. It only comes into play when flashing a PG32IMG.zip using HBOOT.
In fact I have already done the process you are going to undertake. I have a Canadian IncS and I took the latest 2.30.405.1 WWE ROM.zip and cooked it using dsixda's kitchen and my Phone Info now shows Model Number HTC IncS S710e, not S710a as it did before.
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
shepppster said:
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
Click to expand...
Click to collapse
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
https://www.androidfilehost.com/?fid=95897840722644637 - Thanks to LIabtoofer
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -http://techerrata.com/browse/twrp2/m7
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
an0ther said:
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
Click to expand...
Click to collapse
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
shepppster said:
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
Click to expand...
Click to collapse
I do not recommend you just grab the latest firmware update and flash it to you phone, There is a very good chance you will brick your device with a firmware incompatibility
As your on 2.xx firmware jumping strait to 6.xx or 7.xx is a big jump and skipping firmware updates should never be recommended.
To safely update your firmware you need to flash 3.xx, 4.xx, 5.xx and so on untill your updated to the latest firmware. I was able to find the 5.xx and 6.xx firmwares for your device here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/161/ but you will still need to find 3.xx and 4.xx. ALternativly because your s-off with super cid you could switch to a different firmware brand HTC 401 for example. all of which can be found here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you will need to flash atleast these 4 updates to get to the latest safely
3.62.401.1
4.19.401.11
5.11.401.10
6.09.401.12
On the other hand if your not comfortable flashing firmware you could just install a Guru Reset rom then update your phone through OTA updates although that will take much longer than flashing the firmware manually. This reset rom will give you stock with working OTA's if installed with the following options http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
Stock Recovery = Yes
Stock Radio =Yes
Root = No
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
shepppster said:
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
Click to expand...
Click to collapse
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
shepppster said:
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
Click to expand...
Click to collapse
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Danny201281 said:
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
shepppster said:
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
Click to expand...
Click to collapse
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Danny201281 said:
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Click to expand...
Click to collapse
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
shepppster said:
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
Click to expand...
Click to collapse
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Danny201281 said:
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Click to expand...
Click to collapse
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
shepppster said:
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
Click to expand...
Click to collapse
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Danny201281 said:
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Click to expand...
Click to collapse
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
shepppster said:
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
Click to expand...
Click to collapse
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
Click to expand...
Click to collapse
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Danny201281 said:
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Click to expand...
Click to collapse
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
you don't have to delete anything from the firmware's just flash them sequentially till you get to the last one
then just flash TWRP and your rom to the phone
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Danny201281 said:
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Click to expand...
Click to collapse
I already have it on my internal memory and also on a USB stick via OTG lead,and in my Fastboot folder (so 3 options).
I Will have to re-install/flash img of TWRP again (if i didnt delete the recovery in the firmware zip files and,as the firmwares will give me stock recovery)- reboot into bootloader launch TWRP recovery find the rom on SD or push in adb or flash from memstick...but job done!
Any issues installing TWRP over an old one? (I intend to use the same version as I have now) I assume it will see the old TWRP folder and old bkup in the SD card too? if not I am goin for it!
Shepps
Let's not get into the whole debate that millions of others have about sunshine.
Anyway, I have seen conflicting information, and am somewhat confused. Many say you can still install custom roms with S-On and even install custom recoveries, while others say you can't install some roms unless you are S-Off.
Now, I know I can't flash a custom radio while S-On, or "convert" it into a play or dev or whatever edition.
I am fine with that (I assume I can still flash official radios released for it?), I don't want to convert it into a different type of M8 or switch carriers or anything. I just want to have rooted custom roms.
In that regard, just what would I be limited to exactly? Again, half the posts say you can still flash custom and rooted roms with S-On, and others say you need S-Off for custom roms, do they mean custom roms that are for dev/play/etc editions would require S-Off? Or are there custom roms designed for a regular Sprint M8 that would still need S-Off? Or am I even limited to only stock versions/mods of the Sprint rom? What about installing recoveries?
S-off isn't required to flash a ROM, but in some cases you have to flash the kernel separately from the ROM.
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Cyber Akuma said:
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Click to expand...
Click to collapse
Hit the second link in my sig and read the section pertaining to S-on kernel flashing.
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Cyber Akuma said:
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Click to expand...
Click to collapse
Meaning any changes that you make are only temporary and won't survive a reboot.
Though again, changes like installing a custom ROM? Or do you not need access to /system to install a custom rom?
It certainly helps to have S-OFF, but I haven't found it all that necessary. I'm currently on the ViperOneM8 3.2.1 with S-ON, and I'm not having any issues. Nothing that cannot be fixed anyway. At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it. The trouble was with Venom Tweaks, it just wouldn't run. Thankfully I had a back-up, loaded it up, and it's all good. Other than that, no problem. And I'm not even sure if S-ON was the problem, but I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
But yeah, I would give ViperOneM8 a try, though be careful. Make sure you have all the right firmware installed BEFORE you start doing any rooting. It will save you a lot of headache.
Amer28 said:
At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it.
Click to expand...
Click to collapse
Amer28 said:
I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
Click to expand...
Click to collapse
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Cyber Akuma said:
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Click to expand...
Click to collapse
I'm not hundred percent sure on this. I don't do any modding or anything myself, but it is my understanding that you actually 'can' write to the system partition. Just not 'some' stuff. It's essentially like having safe mode on, it just ensures that you don't completely brick the phone.
Again, please do not quote me on any on this. I'm merely humoring the subject, not an expert in any sense of the word.
You can flash virtually any custom ROM with S-On as long as you unlock your Bootloader at HtcDev... I can explain details later on, I am just busy atm...
---------- Post added at 11:09 PM ---------- Previous post was at 10:19 PM ----------
Some more details:
Basically you have 2 options to enable Custom Roms on the HTC One M8
1. Unlock bootloader at http://www.htcdev.com/bootloader/
2. Gain S-Off
For 99% of the ROMs it makes no difference which way you go. You can flash a custom recovery with both ways and you can flash custom ROMs with both ways. There is no such thing as a limitation during writing /system.
The difference is that with S-Off you can change your device IDs (e.g. CID) and in consequence you can flash firmware (like radio firmware, adsp firmware, etc.) that is not meant for your device. So playing with S-Off is quite "risky" you can "easily" achive a brick.
With S-On, you can only flash firmware which is signed for your device.
I would give the recommendation as follows: If you decide to go with S-On (which I would do if you have no specific reason for S-Off) then after flashing a custom recovery, take a backup of your stock ROM. Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
elandroido said:
Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
Click to expand...
Click to collapse
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Well you can flash a radio which is signed for your device. But the safer way imho is to go the OTA way, because that really dates up everything. There might be other firmware components that can receive an update and when you go OTA everything stays consistent. But oft course you can also take the manual way, if you find a proper firmware zip.
Cyber Akuma said:
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Click to expand...
Click to collapse
You can flash the full, signed firmware such as what OMJ provides in his RUU thread, but you cannot flash unsigned firmware to your device while S-on. You can still update your radios, you just have to jump through a few more hoops to do so, unlike those who have S-off.
You might want to take a look at the first post in the thread linked below for more info:
http://forum.xda-developers.com/showthread.php?t=1680928