Related
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.
Hello,
I have HBOOT-2.01.0001 RADIO-3822.01.08.14_M eMMC-boot and I'm running newest Cyanogenmod RC 7.2.0 RC1. Yesterday my phone was stock RUU and I went to HTCDEV.com and unlocked it. After that I flashed the recovery to Clockworkmod v.4.0.1.4 through ADB. Put the CM RC 7.2.0 RC1 .zip on the root of the SD card along with Gapps .zip file.
Then I rebooted into Clockworkmod recovery and installed the 2 .zip files and rebooted. It would not boot and was stuck on HTC logo screen. I found out that I had to separately flash the boot.img file from within the CM RC 7.2.0 RC1 .zip and then everything worked fine.
(Oh yeah, forgot to mention that I did do a backup from within the Clockworkmod before flashing the CM rom)
Ok, so I tested Cyanogenmod for a couple of hours and found out that it was a bit faster than the new stock Ice Cream Sandwich (latest update per 20 april 2012) and it had a lot of ekstra features, but the interface and layout is really low end in my opinion. I gave it a honest try and spent some time changing settings and layouts and even downloaded a couple of ADW themes. Nothing that was even near the new ICS.
Bottom line is that I really want to get back to the original stock RUU Ice Cream Sandwich and I'm unable to
Attempt 1:
I have tried to restore the backup that I made in Clockworkmod and it seems to install just fine. But when restarting it gets stuck on HTC logo Screen. So I thought, maybe this has something to do with the boot.img that has to be flashed manually. So I took out the SD card and put it in my PC using a adapter. Found the boot.img file from the backup inside the clockworkmod/Backup folder and flashed the boot.img file and I'm still stuck on HTC logo screen. It will not boot after recovering the backup no matter what I try.
Attempt 2:
After googling a lot I found the website Shipped ROMs and found my model which I believe to be VIVO (I have a HTC Incredible S from april 2011 in Norway (Europe)).
The only logical RUU i can find is: RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed.exe
Since the other 2 RUU's listed are ASIA.
I downloaded the WWE RUU and ran it. I followed the instructions to the point and got the message Error 155 after about 30 seconds right after it is finished with sending.....
Now the phone will not boot again, stuck on HTC logo screen. And so I'm running out of ideas. In other words I'm stuck here
I reflashed the same Cyanogenmod rom and at least that works again
Anybody have any suggestions in how to solve this or any info at all to direct me into the right direction? This would be much appreciated
I'm thinking maybe anybody knows where I can find a stock ROM .zip file for this phone modell that I can flash the same way i do Cyanogenmod (as described above)?
Maybe even an older version like Froyo, but then I hope it is possible to update to latest stock RUU just using the built in "search for update" function in settings.
Yours sincerely,
Mr. T. Nuis
tnuis said:
Hello,
I have HBOOT-2.01.0001 RADIO-3822.01.08.14_M eMMC-boot and I'm running newest Cyanogenmod RC 7.2.0 RC1. Yesterday my phone was stock RUU and I went to HTCDEV.com and unlocked it. After that I flashed the recovery to Clockworkmod v.4.0.1.4 through ADB. Put the CM RC 7.2.0 RC1 .zip on the root of the SD card along with Gapps .zip file.
Then I rebooted into Clockworkmod recovery and installed the 2 .zip files and rebooted. It would not boot and was stuck on HTC logo screen. I found out that I had to separately flash the boot.img file from within the CM RC 7.2.0 RC1 .zip and then everything worked fine.
(Oh yeah, forgot to mention that I did do a backup from within the Clockworkmod before flashing the CM rom)
Ok, so I tested Cyanogenmod for a couple of hours and found out that it was a bit faster than the new stock Ice Cream Sandwich (latest update per 20 april 2012) and it had a lot of ekstra features, but the interface and layout is really low end in my opinion. I gave it a honest try and spent some time changing settings and layouts and even downloaded a couple of ADW themes. Nothing that was even near the new ICS.
Bottom line is that I really want to get back to the original stock RUU Ice Cream Sandwich and I'm unable to
Attempt 1:
I have tried to restore the backup that I made in Clockworkmod and it seems to install just fine. But when restarting it gets stuck on HTC logo Screen. So I thought, maybe this has something to do with the boot.img that has to be flashed manually. So I took out the SD card and put it in my PC using a adapter. Found the boot.img file from the backup inside the clockworkmod/Backup folder and flashed the boot.img file and I'm still stuck on HTC logo screen. It will not boot after recovering the backup no matter what I try.
Attempt 2:
After googling a lot I found the website Shipped ROMs and found my model which I believe to be VIVO (I have a HTC Incredible S from april 2011 in Norway (Europe)).
The only logical RUU i can find is: RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed.exe
Since the other 2 RUU's listed are ASIA.
I downloaded the WWE RUU and ran it. I followed the instructions to the point and got the message Error 155 after about 30 seconds right after it is finished with sending.....
Now the phone will not boot again, stuck on HTC logo screen. And so I'm running out of ideas. In other words I'm stuck here
I reflashed the same Cyanogenmod rom and at least that works again
Anybody have any suggestions in how to solve this or any info at all to direct me into the right direction? This would be much appreciated
I'm thinking maybe anybody knows where I can find a stock ROM .zip file for this phone modell that I can flash the same way i do Cyanogenmod (as described above)?
Maybe even an older version like Froyo, but then I hope it is possible to update to latest stock RUU just using the built in "search for update" function in settings.
Yours sincerely,
Mr. T. Nuis
Click to expand...
Click to collapse
You can only run and use a RUU successfully when you relock your bootloader. That is what the error 155 is telling out.
In the Development section there is a stock, rooted ICS ROM based on the WWE RUU as well as a couple of custom ICS ROMs based on the stock ICS. You can flash these in CWM like you did CM 7.2
Dude follow nonverbose downgrade technique .... I've gone through same problem...he will help u and he is the best
Smal suggestion ,if u want to upgrade to stock ics 4.0.3 or 4.0.4 its waste of time u will definetly go back to custom roms believe me...
Sent from my HTC Incredible S using xda app-developers app
kalyanroxx said:
if u want to upgrade to stock ics 4.0.3 or 4.0.4 its waste of time u will definetly go back to custom roms believe me...
Click to expand...
Click to collapse
lol everyone has different preferences
tpbklake said:
You can only run and use a RUU successfully when you relock your bootloader. That is what the error 155 is telling out.
In the Development section there is a stock, rooted ICS ROM based on the WWE RUU as well as a couple of custom ICS ROMs based on the stock ICS. You can flash these in CWM like you did CM 7.2
Click to expand...
Click to collapse
Ok thanx Do you have a direct link though? I´m unable to find this......
kalyanroxx said:
Dude follow nonverbose downgrade technique .... I've gone through same problem...he will help u and he is the best
Smal suggestion ,if u want to upgrade to stock ics 4.0.3 or 4.0.4 its waste of time u will definetly go back to custom roms believe me...
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Thanx man, could you also provide me with a direct link? I´m unable to find this. I don´t get it. Whenever using the "Search All Forums" all this other stuff comes up. I must be searching wrong....
If you want to install stock RUU again, you need to relock the bootloader as some one already pointed out..
To relock the bootloader, enter your phone's bootloader, connect your phone to your computer --> enter fastboot in your bootloader --> fastboot menu should show fastboot usb once the usb is connected --> open command prompt/terminal on your computer --> type fastboot devices. if your phone is recognized, it should show the device serial number.
Then type fastboot oem lock...your phone's bootloader should be relocked...then install the RUU
Sometimes, you need to format the data and system partition for the RUU to work properly. You need to do this before relocking the bootloader through a custom recovery (i find this easy instead of using ADB). This is not mandatory. I ran into some problem once and formatting data and system partitions worked..But, as I said, it happened only once and it is not mandatory to do this every time you relock your bootloader.
Please correct me if I am wrong...
edit :
you can find Stock RUUs in the following link...select your device and carrier
h_t_t_p://www.htcdev.com/devcenter/downloads
pls remove underscores (i cannot post links as i am new here)
tnuis said:
Ok thanx Do you have a direct link though? I´m unable to find this......
Click to expand...
Click to collapse
Just check my signature for a link.
pavankumarpingali said:
If you want to install stock RUU again, you need to relock the bootloader as some one already pointed out..
To relock the bootloader, enter your phone's bootloader, connect your phone to your computer --> enter fastboot in your bootloader --> fastboot menu should show fastboot usb once the usb is connected --> open command prompt/terminal on your computer --> type fastboot devices. if your phone is recognized, it should show the device serial number.
Then type fastboot oem lock...your phone's bootloader should be relocked...then install the RUU
Sometimes, you need to format the data and system partition for the RUU to work properly. You need to do this before relocking the bootloader through a custom recovery (i find this easy instead of using ADB). This is not mandatory. I ran into some problem once and formatting data and system partitions worked..But, as I said, it happened only once and it is not mandatory to do this every time you relock your bootloader.
Please correct me if I am wrong...
edit :
you can find Stock RUUs in the following link...select your device and carrier
h_t_t_p://www.htcdev.com/devcenter/downloads
pls remove underscores (i cannot post links as i am new here)
Click to expand...
Click to collapse
Will it be installed same way as other ROms are flashed and does it have sence aswell ?? like the original which was factory installed
jaspreet13 said:
Will it be installed same way as other ROms are flashed and does it have sence aswell ?? like the original which was factory installed
Click to expand...
Click to collapse
No, a RUU is a Windows PC App that you run on your PC and then follow the instructions to attach your phone via the USB cable when prompted.
It will install a stock Sense ROM to your IncS. The only version on HTCDEV.com is the final ICS 4.0.4 ROM with Sense 3.6.
tpbklake said:
No, a RUU is a Windows PC App that you run on your PC and then follow the instructions to attach your phone via the USB cable when prompted.
It will install a stock Sense ROM to your IncS. The only version on HTCDEV.com is the final ICS 4.0.4 ROM with Sense 3.6.
Click to expand...
Click to collapse
and the one in your signature line, is that the same rom though the version seems different ?
jaspreet13 said:
and the one in your signature line, is that the same rom though the version seems different ?
Click to expand...
Click to collapse
The one in my signature is built from the 4.14.405.1 RUU and is a fully rooted version of this stock ROM.
You can flash it on an unlocked bootloader from recovery just like you would for other custom ROMs.
Since you have an unlocked bootloader, you would have to manually flash the boot.img file contained in the ROM's zip file just like other custom ROMs.
tpbklake said:
The one in my signature is built from the 4.14.405.1 RUU and is a fully rooted version of this stock ROM.
You can flash it on an unlocked bootloader from recovery just like you would for other custom ROMs.
Since you have an unlocked bootloader, you would have to manually flash the boot.img file contained in the ROM's zip file just like other custom ROMs.
Click to expand...
Click to collapse
and does it has same sense features, lock menu and widgets like original one,,.. coz i find flashing rom easier than installing RUUs, i had downloaded the stock from Dev website it doesnt have any executable file in it...
jaspreet13 said:
and does it has same sense features, lock menu and widgets like original one,,.. coz i find flashing rom easier than installing RUUs, i had downloaded the stock from Dev website it doesnt have any executable file in it...
Click to expand...
Click to collapse
Yes, it has full stock Sense 3.6.
As for the download, sounds like you may have downloaded the kernel source and not the RUU.
tpbklake said:
Yes, it has full stock Sense 3.6.
As for the download, sounds like you may have downloaded the kernel source and not the RUU.
Click to expand...
Click to collapse
I'll then go for the one you have on your signature and have an upgraded version aswell,
so its same way i install other roms by flashing boot img manually
thanks buddy
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
Big question:
If I want a custom ROM that will run root Apps that modify /system, is S-OFF required? Or are there custom ROMs with non-secure kernels?
More minor questions:
When developers (for the M7 etc) put out a custom ROM...
Are all putting out a kernel? are some signed/unsigned? are some secure/insecure?
Must you use a stock-signed kernel if you support folks with S-ON?
Can you boot unsigned kernels with just HTCDev UNLOCKED (and S-ON)? I assume yes, isn't this what CWM and TWRP run on?
S-OFF defeats the secure-kernels ability to keep /system prestine?
Thanks so much!!!
syserr said:
Big question:
If I want a custom ROM that will run root Apps that modify /system, is S-OFF required? Or are there custom ROMs with non-secure kernels?
More minor questions:
When developers (for the M7 etc) put out a custom ROM...
Are all putting out a kernel? are some signed/unsigned? are some secure/insecure?
Must you use a stock-signed kernel if you support folks with S-ON?
Can you boot unsigned kernels with just HTCDev UNLOCKED (and S-ON)? I assume yes, isn't this what CWM and TWRP run on?
S-OFF defeats the secure-kernels ability to keep /system prestine?
Thanks so much!!!
Click to expand...
Click to collapse
yes you can flash custom rom's with s-on and an unlocked bootloader, this is basically why HTC gave you the ability to unlock your bootloader, even they know most users use custom rom's and most are better than their own.
S-off is not required, however, s-off (security off) gives you the ability to do things like backflash, flash different RUU;s, and change firmwares, radios etc, but if you don't know what you are doing or unsure of yourself, it will also no longer stop you from flashing something wrong, making it very easy to mess up or even brick your phone.
and to answer your first question, ive yet to find a custom rom that doesn't come already rooted and with an unsecure kernel, but always be sure to read the op of which rom your interested in as it contains important instructions, even down to which version of recovery you should be using to flash the rom, you'd be very surprised about how many people actually get this wrong and then require help because their rom isn't booting because they couldn't be bothred to read the instructions, it will also state what type of kernel it comes with.
on a different note, you don't you don't have to flash a custom rom, if your happy with your current stock rom, you can just unlock the bootloader, flash a custom recovery and then flash an unsecure kernel like elementalx or kangaroo kernel etc, TWRP recovery itself will set up root for you on exit.
Seanie280672 said:
yes you can flash custom rom's with s-on and an unlocked bootloader, this is basically why HTC gave you the ability to unlock your bootloader, even they know most users use custom rom's and most are better than their own.
S-off is not required, however, s-off (security off) gives you the ability to do things like backflash, flash different RUU;s, and change firmwares, radios etc, but if you don't know what you are doing or unsure of yourself, it will also no longer stop you from flashing something wrong, making it very easy to mess up or even brick your phone.
and to answer your first question, ive yet to find a custom rom that doesn't come already rooted and with an unsecure kernel, but always be sure to read the op of which rom your interested in as it contains important instructions, even down to which version of recovery you should be using to flash the rom, you'd be very surprised about how many people actually get this wrong and then require help because their rom isn't booting because they couldn't be bothred to read the instructions, it will also state what type of kernel it comes with.
on a different note, you don't you don't have to flash a custom rom, if your happy with your current stock rom, you can just unlock the bootloader, flash a custom recovery and then flash an unsecure kernel like elementalx or kangaroo kernel etc, TWRP recovery itself will set up root for you on exit.
Click to expand...
Click to collapse
Thank you for your answer!
I'm beginning to think I don't need S-OFF. I want to be able to back flash and RUU back etc, but it's not necessary. I'm assuming you can back flash HBOOT, where as with S-ON you can never back flash HBOOT.
One thing concerns me... how are unsecure kernels made? (I believe ViperOne, was still secure when I was running it.) Do you have to compile from source? Or can your "unsecurize" a stock secure kernel? Or both?
Thanks!
syserr said:
Thank you for your answer!
I'm beginning to think I don't need S-OFF. I want to be able to back flash and RUU back etc, but it's not necessary. I'm assuming you can back flash HBOOT, where as with S-ON you can never back flash HBOOT.
One thing concerns me... how are unsecure kernels made? (I believe ViperOne, was still secure when I was running it.) Do you have to compile from source? Or can your "unsecurize" a stock secure kernel? Or both?
Thanks!
Click to expand...
Click to collapse
Its my belief that all kernals are built from the stock kernel or the kernel files available from the HTC Dev site, but as im not a developer I cant say for sure, although I would love to learn things like this I just don't have the time and know that it also requires Linux to build a kernal, im clueless when it comes to Linux, and yes it is possible to "unsecurize" a stock kernel, ModPack 007 for lollipop comes with the option to do this very thing, however don't start thinking that an unsecure kernel is so people can hack into your phone, or your phone is going to crash every 5 minutes, its not like that, its unsecure so that you can modify and replace system files etc, ie write protection removed = unsecure kernals.
Kernals like ElementalX and Kangaroo take the modding further than just removing write protection, they add many other features, which can generally be found in the op of each kernel.
If you want to back flash anything, HBOOT, Firmware, RUU etc then you need S-off full stop, theres no other way to do it.
As for S-on, I hate it, I feel totally locked down, im a very big HTC fan and cant wait for the M9, ive owned many HTC's and pretty much the first thing I do after unpacking it and messing about with it for a couple of hours is s-off it, it free's the phone up for anything, however if your not careful and don't know what your doing, you can very easily kill it, s-off means security off, so your device is no longer protected from a bad flash, with s-on it will just error out and boot again in most cases, s-off however in the same situation will turn your nice phone into a paper weight.
when I first got my HTC one M7 it came with HBOOT 1.56, very hard to s-off, firewater was the only tool that could do it, and kept failing, I must of flashed 50+ (probably and exaggeration) rom and kernel combinations to try and get firewater to work, all failed, this was before sunshine s-off was about, thankfully I found a shop in Sheffield which did it by java card, as I travel up there quite a bit it wasn't an issue to get it s-off'd next time I went up there.
Anyone please feel free to correct me if any of this is wrong, like I said im not a dev and its all a learning curve.
Seanie280672 said:
... and yes it is possible to "unsecurize" a stock kernel, ModPack 007 for lollipop comes with the option to do this very thing, however don't start thinking that an unsecure kernel is so people can hack into your phone, or your phone is going to crash every 5 minutes, its not like that, its unsecure so that you can modify and replace system files etc
Click to expand...
Click to collapse
Thanks for all the great info.
I should have clarified my concern about an unsecure kernel. Not that I was worried about getting hacked etc... More I was worried that my options would be limited to only ROMs with a limited number of unsecure kernels. If creating an unsecure kernel was difficult, I'd worry about a shortage. Booting into TWRP for unsecure kernel so I can modify /system is very restrictive to someone that is not used to it.
I compiled my first Linux kernel in 1995. I too want freedom. "Android" is a big field... but HTC and HBOOT are really outside of my Android experience -- it's great to learn so much. Thanks!
I just need a clarification on flashing custom ROMs. I come from other phones like Samsung that when it comes to flashing ROMs, there is no need to flash boot.img via fastboot afterwards. I understand that it is because a htcdev unlocked phone cannot write to the boot partition from its recovery partition.
Question is that I have flashed CM12.1 (and GAPPS) onto the phone but I have not done the part of flashing boot.img via fastboot. I am still able to boot into system and am now using the phone without any incident. Why is that so?
tech_girl said:
I just need a clarification on flashing custom ROMs. I come from other phones like Samsung that when it comes to flashing ROMs, there is no need to flash boot.img via fastboot afterwards. I understand that it is because a htcdev unlocked phone cannot write to the boot partition from its recovery partition.
Question is that I have flashed CM12.1 (and GAPPS) onto the phone but I have not done the part of flashing boot.img via fastboot. I am still able to boot into system and am now using the phone without any incident. Why is that so?
Click to expand...
Click to collapse
With the M7 flashing boot.img is possible during the Rom install. Only older HTC devices required boot.img to be flashed separately :good:
Sent from my HTC One using Tapatalk
Danny201281 said:
With the M7 flashing boot.img is possible during the Rom install. Only older HTC devices required boot.img to be flashed separately :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks Danny201281. This is the procedure as outlined for flashing CM12.1. Does it matter what is the hboot version?
What ROM do you have on your M7?
tech_girl said:
Thanks Danny201281. This is the procedure as outlined for flashing CM12.1. Does it matter what is the hboot version?
What ROM do you have on your M7?
Click to expand...
Click to collapse
Hboot is part of the firmware. Generally it's best to keep to roms based on your current firmware or to update your firmware to match the Rom you wish to use. I think your device was on lollipop firmware after using an RUU in a different thread correct?
If so you should be fine to use any of the latest roms. I'm currently using Android Revolution HD. I've been a long time fan of the Rom. It's kinda close to stock but that keeps things stable and using Sense Toolbox gives me most of the mods I'm looking for.
I'm not a fan of CM roms. There normally very experimental and glitchy. How you find a particular Rom depends very much on what you want from it ?
Sent from my HTC One using Tapatalk