Ok so im not new to the rooting scene but am new to the flashing scene. I know a good jist of it but cant seam to figure out the whole firmware process.
I want to install this ROM: http://forum.xda-developers.com/showthread.php?t=2699616
I am currently running 4.4.2 with 1.58.xx firmware unlocked S-OFF and rooted. and this ROM requires 2.22.1540.4
Now I have found the 2.22.1540.4 firmware and know that i have to relock my bootloader and such but my phone says my ID is CWS__001 and i cant find any with that.
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
And last question say i am flashing a new firmware and it screws up, since my custom recovery gets removed how do i flash my nandroid backup.
also if successfully flash the new firmware am i able to flash my old backup to restore to a old firmware or do i need to reflash the old firmware first.
sorry for so many questions i just dont want to blow up my phone due to stupid mistakes.
EDIT: so I think i managed to update my firmware. In bootloader it shows 2.22.1540.3 under os but in the phone settings it still says 4.4.2 and 1.58.xxx. I am assuming all i need is a updated firmware to run the mods and not a updated software? correct me if im wrong.
What exactly did you flash (link it if you can)? I think you are confusing software (OS or ROM) with firmware. Firmware as its mostly commonly discussed here (updating to run 2.xx based ROMs) refers to the hboot, radio, recovery, and other modules (media, WiFi, Bluetooth and more) deployed with an RUU or OTA. You have only flashed firmware if you installed an RUU/OTA or manually flashed it with fastboot.
devonjerothe said:
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
Click to expand...
Click to collapse
Yes, 2.23 firmware will work as well. But again, make sure you are talking about the right thing (firmware versus software/OS).
Related
Hi all, back when the unlock was released for this phone I installed a custom GB rom on my brother's phone. I am very experienced.with flashing and rooting etc so this wasn't a problem. Now with S-Off things have gotten a bit more complicated, not to mention the mainver nonsense I've been reading about. To make matters worse I haven't found a good thread outlining all these details on what needs to be done for the transition from GB to ICS; everyone basically assumes you're already on ICS and either S-On or S-Off.
So I have a few questions I'm hoping someone can answer.
1. I want to keep my brother's phone S-On. I have reviewed the S-Off method and deem it too risky for hardware that is not my own. That said, what's the best path to getting to a custom ICS OTA based rom from GB firmware?
a. Should I flash stock GB, relock phone, install OTA, unlock phone, install custom ICS rom?
b. Should I directly install a certain firmware from the boot loader along with a custom ICS OTA based rom from recovery? If so, which firmware should I flash? Is there any mainver stuff I need to tweak?
c. Or something else?
2. I always perform backups before flashing a new rom to ensure if something goes wrong I can restore to the previous rom image. However, if I backup a GB rom that runs on an older firmware and install ICS based on a newer firmware, would restoring to GB be as simple as going into recovery and restoring his old GB rom? Or would I have to flash the old firmware first?
3. I've noticed some roms like Viper use aroma installer which can handle multiple situations of installation. Would the situation I am describing (GB firmware, S-On) be handled? I am unsure how many different firmware versions there are out there. I don't know if referring to the "old firmware" means an older ICS firmware or GB firmware.
Thank you all for your help. It is frustrating for me to be this confused about how to upgrade a phone considering the amount of times I've done it in the past. I appreciate any responses or links that could help me better understand what I must do.
so your s-on and unlocked? or locked either way
re-lock if you are unlocked and then run
the ics offical .exe RUU from
here
http://forum.xda-developers.com/showpost.php?p=29979907&postcount=133
after you do that then unlock and flash a custom recovery then flash a ics rom of your choice
Div033 said:
Hi all, back when the unlock was released for this phone I installed a custom GB rom on my brother's phone. I am very experienced.with flashing and rooting etc so this wasn't a problem. Now with S-Off things have gotten a bit more complicated, not to mention the mainver nonsense I've been reading about. To make matters worse I haven't found a good thread outlining all these details on what needs to be done for the transition from GB to ICS; everyone basically assumes you're already on ICS and either S-On or S-Off.
So I have a few questions I'm hoping someone can answer.
1. I want to keep my brother's phone S-On. I have reviewed the S-Off method and deem it too risky for hardware that is not my own. That said, what's the best path to getting to a custom ICS OTA based rom from GB firmware?
a. Should I flash stock GB, relock phone, install OTA, unlock phone, install custom ICS rom?
b. Should I directly install a certain firmware from the boot loader along with a custom ICS OTA based rom from recovery? If so, which firmware should I flash? Is there any mainver stuff I need to tweak?
c. Or something else?
2. I always perform backups before flashing a new rom to ensure if something goes wrong I can restore to the previous rom image. However, if I backup a GB rom that runs on an older firmware and install ICS based on a newer firmware, would restoring to GB be as simple as going into recovery and restoring his old GB rom? Or would I have to flash the old firmware first?
3. I've noticed some roms like Viper use aroma installer which can handle multiple situations of installation. Would the situation I am describing (GB firmware, S-On) be handled? I am unsure how many different firmware versions there are out there. I don't know if referring to the "old firmware" means an older ICS firmware or GB firmware.
Thank you all for your help. It is frustrating for me to be this confused about how to upgrade a phone considering the amount of times I've done it in the past. I appreciate any responses or links that could help me better understand what I must do.
Click to expand...
Click to collapse
Try CleanROM, I've been using it since I got it. Very easy to install with S-On.
nstallation for S-ON Devices on Gingerbread firmware
Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
Reboot to recovery
wipe data / Factory Reset
Flash ROM
Flash GB Fimrware Patch
Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
Reboot
Profit!
Click to expand...
Click to collapse
The phone might say something about the SD card not working, so make sure you download the Gingerbread Firmware patch. Just Flash it like a rom and you're all god
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
bloodbath said:
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
Click to expand...
Click to collapse
you need to flash the original recovery to install ota updates,, you will lose root access doing so
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
All you need to do is put the stock Tmo recovery on your one. Then go update with ota and you will still be unlocked but you do lose root.
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
bloodbath said:
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
Click to expand...
Click to collapse
I'm sorry I was wrong you will lose root after you update ota. But you can do ota while being unlocked so no need to relock bootloader just flash the stock Tmo recovery and update.
chong67 said:
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
Click to expand...
Click to collapse
U mean something like this!? https://copy.com/aSLnP
Team-Noctural.com/androidtechy.com/droidnow.com
Hello,
I wanted to have newer android and have rooted and flashed HTC Amaze with Hasoons toolkit using TWRP recovery system. After flashing Cyanogenmod 10 ROM through ADB Sideload and flashing Cyanogenmod 10 ROM kernel (boot.img file which was included in the zipped folder) manually with Hasoons toolkit, the phone started to boot normally, load welcome screen, but after several seconds it freezes and then restarts. Can you please help what can be the cause of this problem and how can I repair? The phone is rooted and bootloader unlocked, but its still S-ON.
Before installing the Cyanogenmod I have tried to flash other ROMs, but on all of them after flashing kernel, the phone was freezing on booting mode and then just restarting continuously.
I hope there should be some way out and the phone is not bricked. If something I have backed up the data and will try to restore, but would prefer to repair Cyanogenmod ROM.
Thank you guys in advance for your help.
ratijs100 said:
Hello,
I wanted to have newer android and have rooted and flashed HTC Amaze with Hasoons toolkit using TWRP recovery system. After flashing Cyanogenmod 10 ROM through ADB Sideload and flashing Cyanogenmod 10 ROM kernel (boot.img file which was included in the zipped folder) manually with Hasoons toolkit, the phone started to boot normally, load welcome screen, but after several seconds it freezes and then restarts. Can you please help what can be the cause of this problem and how can I repair? The phone is rooted and bootloader unlocked, but its still S-ON.
Before installing the Cyanogenmod I have tried to flash other ROMs, but on all of them after flashing kernel, the phone was freezing on booting mode and then just restarting continuously.
I hope there should be some way out and the phone is not bricked. If something I have backed up the data and will try to restore, but would prefer to repair Cyanogenmod ROM.
Thank you guys in advance for your help.
Click to expand...
Click to collapse
Did you follow the directions posted in the pinned threads at the top of the forums and update to ICS before unlocking and flashing these other ROMs?
I ask because if you say you're unlocked, but s-on, and you need to be on an ICS radio baseband prior to flashing any newer ROM. If you were already on ICS prior to these flash attempts then I suggest you try again with the latest version of 4ext instead of TWRP, and make sure to enable smart-flash. TWRP doesn't flash kernels properly on HTC handsets with s-on, while 4ext does when smart-flash is enabled. Of course all of this comes with the stipulation that you're doing this on a T-Mobile US version handset.
If you're on an Asian or non-branded international version it gets a bit more complicated because you must attain s-off before attempting to flash. This is because these handsets never got an ICS update. So there is no carrier image to flash to, and the only way to install the updated firmware with the ICS baseband is to attain s-off first then flash the T-Mobile US image.
Again, if you haven't I strongly suggest reading the pinned threads at the top of the different forums here as they contain all of the info you need to successfully flash your device to an updated ROM. Good luck.
Ciao
Odysseus1962 said:
Did you follow the directions posted in the pinned threads at the top of the forums and update to ICS before unlocking and flashing these other ROMs?
I ask because if you say you're unlocked, but s-on, and you need to be on an ICS radio baseband prior to flashing any newer ROM. If you were already on ICS prior to these flash attempts then I suggest you try again with the latest version of 4ext instead of TWRP, and make sure to enable smart-flash. TWRP doesn't flash kernels properly on HTC handsets with s-on, while 4ext does when smart-flash is enabled. Of course all of this comes with the stipulation that you're doing this on a T-Mobile US version handset.
If you're on an Asian or non-branded international version it gets a bit more complicated because you must attain s-off before attempting to flash. This is because these handsets never got an ICS update. So there is no carrier image to flash to, and the only way to install the updated firmware with the ICS baseband is to attain s-off first then flash the T-Mobile US image.
Again, if you haven't I strongly suggest reading the pinned threads at the top of the different forums here as they contain all of the info you need to successfully flash your device to an updated ROM. Good luck.
Ciao
Click to expand...
Click to collapse
Thank you for information. It is non-branded international version. It means I will have to try S-off and then flash the ROM with 4ext.
ratijs100 said:
Thank you for information. It is non-branded international version. It means I will have to try S-off and then flash the ROM with 4ext.
Click to expand...
Click to collapse
Please read the pinned threads first. You're going to have to relock your bootloader before proceeding, so save the binary unlock blob you got from HTC as you'll need it to unlock again. Place the stock image in the root of your external SD card and flash from hboot. Then after getting s-off and superCID then you can flash the T-Mobile ICS image. Again read the pinned threads thoroughly or you'll be posting about how to unbrick your handset. Good luck.
Ciao
I had the same issues and had to turn off security with the joupunut bear program. Just to be safe with future flashing I've understood it works best. You should first s-off your phone and then go about flashing whichever firmware you want. Make sure you upgrade to the stock ics rom first as a pre requisite towards flashing any other rom and you'll be fine. Do a search on the stuff needed to gain s-off here in the forums. Report back if you need more assistance
Sent from my T-Mobile myTouch using xda app-developers app
I'm fairly new to the rooting and flashing scene and had a quick question about firmware.
I'm currently running Dirty Unicorns 9/26 official build with furnace kernel 1.0.9. I wanted to try arhd 20.1, so I made a backup, factory wiped and flashed it. I went thru the aroma installer and everything installed fine, once it finished, however, it turned off and wouldn't turn back on. I finally got it working again into the bootloader, but when I try and boot it, it just hangs on the HTC logo screen with the red text.
I browsed the thread to see what the issue could be, and although I couldn't find the someone else who had that problem, most of the problems people are having are because they didn't upgrade to the latest firmware.
So is that what the issue could've been? I downloaded the new firmware, just need to flash it, but before I do, I want to ask, will I have to flash a custom recovery again if I flash the new firmware? And will I also lose my data?
I'm soff with sunshine, twrp is my recovery
Probably due to outdated firmware, you are correct. Flashing a Sense ROM based on a newer version number (1.x, 2.x, 3.x) than your current firmware will often result in long boot time The phone probably will boot, just take a really long time (like 10 minutes) with no boot animation, making many folks think its "stuck" on the boot screen. Other issues are also common, such as broken WiFi.
Although, if you intend on flashing the firmware associated withe ARHD 20 (firmware 3.28) be aware that this is an "international" based firmware, and those are known to not play well with AT&T's network (at least for past 2.x firmware). You can give it a try, but you may have reception issues and may need to flash another firmware, or at least a different radio.
I know...I'm probably gonna kick myself for admitting I can't find the firmware version I'm on...but I can't...I'm on dirty unicorns as well...want to update firmware so I can try various Roms and I don't know which one to download...im still s-on but I know there's a thread that said I can still update...just can't find the number... any number that resembles the ones in many lists. I googled it but it doesn't tell me
rjcormier said:
I know...I'm probably gonna kick myself for admitting I can't find the firmware version I'm on...but I can't...I'm on dirty unicorns as well...want to update firmware so I can try various Roms and I don't know which one to download...im still s-on but I know there's a thread that said I can still update...just can't find the number... any number that resembles the ones in many lists. I googled it but it doesn't tell me
Click to expand...
Click to collapse
Your confusion is not without reason. There is in fact technically no "number" for firmware. That being the base, its been the normal thing here on XDA to refer to the software number which the firmware deployed with. So "firmware 3.28" actually just refers to the various modules (hboot, radio, recovery, kernel, WiFi, Bluetooth, and others) that deployed with the 3.28 OTA software. But the number 3.28 is just for the OS, which can easily be changed simply by flashing the ROM; while the firmware is actually not touched when you flash a ROM. In your case, since Dirty Unicorn is AOSP, its software number probably has nothing to do with HTC's software numbering scheme.
Best you can do is go by hboot and radio number. Either boot into bootloader, and get those numbers there and post them. Or adb getvar all (delete IMEI if you cut and paste the getvar output).
Wonders_Never_Cease has all the recent AT&T firmwares posted here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
But s-off is required to update firmware manually. If you want to stay s-on and update firmware, your alternative is to return to stock ROM and recovery, and OTA to update the firmware. Or relock the bootloader and RUU. Either way, 2.23 is the latest firmware/software you can update this way, until AT&T officially rolls out 3.xx.
Your confusion is not without reason. There is in fact technically no "number" for firmware. That being the base, its been the normal thing here on XDA to refer to the software number which the firmware deployed with. So "firmware 3.28" actually just refers to the various modules (hboot, radio, recovery, kernel, WiFi, Bluetooth, and others) that deployed with the 3.28 OTA software. But the number 3.28 is just for the OS, which can easily be changed simply by flashing the ROM; while the firmware is actually not touched when you flash a ROM. In your case, since Dirty Unicorn is AOSP, its software number probably has nothing to do with HTC's software numbering scheme.
Best you can do is go by hboot and radio number. Either boot into bootloader, and get those numbers there and post them. Or adb getvar all (delete IMEI if you cut and paste the getvar output).
Wonders_Never_Cease has all the recent AT&T firmwares posted here: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
But s-off is required to update firmware manually. If you want to stay s-on and update firmware, your alternative is to return to stock ROM and recovery, and OTA to update the firmware. Or relock the bootloader and RUU. Either way, 2.23 is the latest firmware/software you can update this way, until AT&T officially rolls out 3.xx.
Click to expand...
Click to collapse
Thank you! Soo hboot is 3.16.0.0000, and radio is 1.16.21331931
rjcormier said:
Thank you! Soo hboot is 3.16.0.0000, and radio is 1.16.21331931
Click to expand...
Click to collapse
I believe those are the hboot and radio numbers that go with the 1.58 software. You can update to 2.23 firmware by RUU (the OTA was actually pulled/cancelled). But that means you will only be able to run custom ROMs based on Sense software 2.x. The newer ROMs are based on Sense software 3.x. So if you want to run those, you either need to S-off, or wait until AT&T releases 3.x.
redpoint73 said:
I believe those are the hboot and radio numbers that go with the 1.58 software. You can update to 2.23 firmware by RUU (the OTA was actually pulled/cancelled). But that means you will only be able to run custom ROMs based on Sense software 2.x. The newer ROMs are based on Sense software 3.x. So if you want to run those, you either need to S-off, or wait until AT&T releases 3.x.
Click to expand...
Click to collapse
OK thank you for your help!
There is a master list of stock recovery versions for the HTC One. How do I determine which version I should be using?
None of those. That is hardly a "master" list. It's over 3 years old, never updated past the original Kitkat (M8 release) recoveries, and woefully obsolete. You'll want your recovery number to match your OS number (main version on bootloader screen or getvar all). Also, none of those are valid for AT&T version M8 (which is what I assume you have, since this section is specifically for the AT&T M8). It would need to have "502" in the version number x.xx.502.x which specifically denotes AT&T.
Why exactly do you want stock recovery? Most folks want this, in order to get OTA updates. But you will also need a stock, never rooted ROM (unrooting doesn't work), and also must be connected to the AT&T network. It's probably easier to relock the bootloader, and update by RUU. Note that RUU will wipe all data from the phone. See RUU section in my Index thread: https://forum.xda-developers.com/showthread.php?t=2751432
If you really want stock recovery, you should be able to extract it from the firmware.zip. Find the right firmware version number from the firmware collection, and extract recovery.img from the "Stock, Full Wipe" firmware zip:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
That is definitely helpful. Thank you. I didn't realize that I could pull the bootloader out of the firmware.zip. The phone was AT&T and later unlocked and made in to a rooted Cyanogenmod phone. I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
mortifyxda said:
I didn't realize that I could pull the bootloader out of the firmware.zip.
Click to expand...
Click to collapse
Recovery and bootloader are two completely different things! You can pull recovery.img from firmware.zip, and flash with fastboot. I would not do this with bootloader, which would require s-off (to flash manually) and it would still be risky. Better to flash the whole firmware.zip or RUU, if you want to update bootloader. But I don't think that is what you meant.
mortifyxda said:
I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
Click to expand...
Click to collapse
Your description is confusing, and I think you're mixing the terms up again. 6.12.1540.4 is the version number for the US Developer's Edition, which is Sense, and not the same as Google Play Edition (GPE) which is not Sense.
To OTA, the version number of the current stock ROM needs to match your firmware number (in bootloader and getar all), and you also need matching stock recovery.
To be clear, what is the current ROM (and version number) as shown in Settings? And also do fastboot getvar all, and post the result (delete IMEI and serial number). Need those pieces of info, before I can properly advise what stock recovery to use.