Related
Hi,
is it possible to backup a stock htc one, as shipped from new before rooting, so that i can restore back to stock. I know this is possible on tablets I have had in the past by running recovery via fastboot from a pc, but how can this be done with a htc one?
Yes. This works like a charm if you do it properly: http://forum.xda-developers.com/showthread.php?t=1420351
P.s., it works on the HTC One. Not only on Nexus.
Sent from my One using Tapatalk 4
Thanks. Im waiting for my phone from htc repair (tomorrow) so ill try it out then.
Sent from my GT-I9300 using XDA Premium 4 mobile app
I think fastboot boot recovery.img stopped working with 1.54, but it's worth a go. Anyway, there are plenty of stock recoveries floating around.
BenPope said:
I think fastboot boot recovery.img stopped working with 1.54, but it's worth a go. Anyway, there are plenty of stock recoveries floating around.
Click to expand...
Click to collapse
I did ask HTC to reflash stock (as when received from ee) so, hopefully I will get 1.44 bootloader. I am pretty sure I flashed recovery via fastboot on 1.54 previously after the last repair. I'll see if my memory is correct tomorrow hopefully. Its seems so long since I had the htc one I have forgotten. I have been playing with the s3 for nearly two weeks now. Hopefully I will have a crack free htc one tomorrow, else I suppose it will be another two weeks!!
I'll update here.
zaphodbeeb said:
I am pretty sure I flashed recovery via fastboot on 1.54
Click to expand...
Click to collapse
I said fastboot boot, not fastboot flash recovery.
fastboot boot would allow a nandroid backup of stock recovery.
Doooh. My bad...
Sent from my GT-I9300 using XDA Premium 4 mobile app
Hi,I should be getting my htc one back today at long last, hopefully with 1.44 bootloader. Thanks for the excellent info above. Looks just the job. Can I ask if this will also restore s-on after doing an s-off. i.e.
- backup factory 1.44 device
- root s-off revone etc
- restore from backup (back to s-on)
- root s-off moonshine etc
- restore from original backup to restore s-on
A nandroid backup will not restore your hboot or S-ON.
With 1.44 hboot you will be able to
- boot recovery and take a stock nandroid that includes your stock recovery
- S-OFF, S-ON, lock bootloader without a trace
With 1.54 hboot you will be able to
- flash recovery and take a stock nandroid that includes your custom recovery, but you can get a stock recovery from xda
- S-ON, lock bootloader but it will show as relocked
deeevan said:
A nandroid backup will not restore your hboot or S-ON.
With 1.44 hboot you will be able to
- boot recovery and take a stock nandroid that includes your stock recovery
- S-OFF, S-ON, lock bootloader without a trace
With 1.54 hboot you will be able to
- flash recovery and take a stock nandroid that includes your custom recovery, but you can get a stock recovery from xda
- S-ON, lock bootloader but it will show as relocked
Click to expand...
Click to collapse
Hi, thanks for this. In this case if my HTC One is returned with 1.54 I will be returning it/exchanging it for an s4. I am negotiating with HTC/EE at the moment so this is very useful to know before I do anything with the device. If I cant get s-off I wont accept it.
That's going to be a hard one to argue. I refuse this phone because you have applied a valid update that does not allow me to do an unauthorised modification to allow further modifications undetected?
deeevan said:
That's going to be a hard one to argue. I refuse this phone because you have applied a valid update that does not allow me to do an unauthorised modification to allow further modifications undetected?
Click to expand...
Click to collapse
Ah yes normally, but they have served me so poorly and thanks to the sale of goods act 1979 section 48B. Read about my HTC experience here http://forum.xda-developers.com/showthread.php?t=2425001.
Firstly, Aussie dont have RUU, so I am going to use Europe since aussie are 1.28.980.17 for 4.1.2
Currently, I am on stock 4.2.2 with CWM recovery and "RELOCKED" bootloader (I typed fastboot oem lock) and s-off.
But, I want to try this and not quite sure if it is going to work or not.
1. Since I relocked bootloader, I cant flash stock recovery.
2. Use RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe to get 1.44 hboot.
3. unlock bootloader again using revone
4. Flash CWM then restore from my own 4.1.2 CWM backup.
5. Flash stock 1.29.980.17 firmware.zip
6. Lock bootloader and s-on
7. OTA update for 4.2.2
Is this going to work?
Thanks in advance :laugh:
reservin said:
Firstly, Aussie dont have RUU, so I am going to use Europe since aussie are 1.28.980.17 for 4.1.2
Currently, I am on stock 4.2.2 with CWM recovery and "RELOCKED" bootloader (I typed fastboot oem lock) and s-off.
But, I want to try this and not quite sure if it is going to work or not.
1. Since I relocked bootloader, I cant flash stock recovery.
2. Use RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe to get 1.44 hboot.
3. unlock bootloader again using revone
4. Flash CWM then restore from my own 4.1.2 CWM backup.
5. Flash stock 1.29.980.17 firmware.zip
6. Lock bootloader and s-on
7. OTA update for 4.2.2
Is this going to work?
Thanks in advance :laugh:
Click to expand...
Click to collapse
Your method will work, but you could also see if someone has uploaded a nandroid backup of your Aussie stock. Just a thought.
kibmikey1 said:
Your method will work, but you could also see if someone has uploaded a nandroid backup of your Aussie stock. Just a thought.
Click to expand...
Click to collapse
So flashing RUU doesnt require unlocked bootloader. is it right?
Yeah I saw aussie stock unbranded CWM as well.
Thanks!!
BTW, after I restore from nandroid backup, then receive OTA of 4.2.2, does that contains 4.2.2 firmware.zip as well?
If it is, then I do not need flash 1.29.980.17 firmware.zip before right?
reservin said:
So flashing RUU doesnt require unlocked bootloader. is it right?
Yeah I saw aussie stock unbranded CWM as well.
Thanks!!
BTW, after I restore from nandroid backup, then receive OTA of 4.2.2, does that contains 4.2.2 firmware.zip as well?
If it is, then I do not need flash 1.29.980.17 firmware.zip before right?
Click to expand...
Click to collapse
4.2.2. OTA, as far as I know, will contain the firmware, but you could flash it just to make sure everything is right. All the OTA will do is write over it anyway, so no harm, no foul either way. I would double check what firmware you need for the rom you're flashing, just to be sure.
Here's a link to that nandroid backup, too. Hope it goes smoothly.
kibmikey1 said:
4.2.2. OTA, as far as I know, will contain the firmware, but you could flash it just to make sure everything is right. All the OTA will do is write over it anyway, so no harm, no foul either way. I would double check what firmware you need for the rom you're flashing, just to be sure.
Here's a link to that nandroid backup, too. Hope it goes smoothly.
Click to expand...
Click to collapse
I successfully flashed Europe RUU with 1.44 hboot!
Now I am restoring nandroid 4.1.2 backup. I still need aussie 4.1.2 firmware.zip as well right?
You do realise that if you go to S On then update to 4.2.2 you will have hboot 1.54 and will be unable to get S Off back ?
Sent from my HTC One using xda app-developers app
paul_59 said:
You do realise that if you go to S On then update to 4.2.2 you will have hboot 1.54 and will be unable to get S Off back ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yep. I need to visit service center next week.
Now i am not sure if OTA still can be applied on Australian rom + European firmware with locked bootloader and s-on..
So I'm trying to flash a new RUU for GPE HTC One Jelly Bean 4.3. The RUU is suppose to work for unlocked devices; the person who posted the download links had two, with one for unlocked devices and the other for locked devices. I think I messed up somewhere because I had a custom kernel installed via .zip, then booted back to the stock GPE kernel with "fastboot flash boot boot.img"; the system booted up fine but the 3 dot menu was missing so I went back to the customer kernel. The system wouldn't get past the Google screen and now I'm trying to flash the RUU but it won't work. If I do it on my computer via commands, I get "<bootloader> zip info parsing," then "FAILED <remote: 99 unknown fail>". So now I'm in TWRP recovery with the RUU on my SD card; tried flashing it on my phone and it says "Updating partition details...", "E: unable to mount ' /data'", "E: unable to mount internal storage", E: unable to mount ' /data," then lastly "Error flashing zip." I wiped the cache, data, and system; it won't wipe the Dalvik cache and gives me the same error when I do it. Can someone help me?
Edit: When I also try to wipe via "fastboot -w" it comes up with an error saying "FAILED <remote: not allowed>.
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
InflatedTitan said:
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
May be the alcohol but I'm having trouble keeping up lol. You're having questions with the hboot trying to s-off? If you can't s-off, nor ruu BC the firmware doesn't match with the most recent ruu then you may be stuck or hopefully someone with more advanced knowledge can help you a little better
Sent from my HTC One using Tapatalk 2
yorkies88888 said:
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
Click to expand...
Click to collapse
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
CoryTallman said:
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
Click to expand...
Click to collapse
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
yorkies88888 said:
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
Click to expand...
Click to collapse
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
wwjdd44 said:
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
Click to expand...
Click to collapse
It's of no use to him; he can't run it because he's on 1.54 and s-on.
iElvis said:
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
Click to expand...
Click to collapse
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
yorkies88888 said:
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
Click to expand...
Click to collapse
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
nkk71 said:
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
yorkies88888 said:
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Click to expand...
Click to collapse
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
nkk71 said:
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
yorkies88888 said:
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
Click to expand...
Click to collapse
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
nkk71 said:
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
yorkies88888 said:
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
Click to expand...
Click to collapse
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
iElvis said:
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
Click to expand...
Click to collapse
nkk71 said:
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
yorkies88888 said:
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
Click to expand...
Click to collapse
No. No rom will change your bootloader or splash screen. You need s-off to do that.
Hi All,
I have the M7 UL with a CID of HTC__001, it has hboot 1.44 s-off and I want to know if I really need to update the firmware/radio at all? I believe the current firmware is that of the 1.29.401.1 and since this was from the time of the Android 4.1.2 ROM and I am running a custom 4.3 ROM, I'm not sure what to do. I'm, not actually having any problems, so is it really necessary?
If so, do I need to upgrade hboot as well or can I get newer firmware/radio while keeping hboot 1.44 ?
beartiger said:
Hi All,
I have the M7 UL with a CID of HTC__001, it has hboot 1.44 s-off and I want to know if I really need to update the firmware/radio at all? I believe the current firmware is that of the 1.29.401.1 and since this was from the time of the Android 4.1.2 ROM and I am running a custom 4.3 ROM, I'm not sure what to do. I'm, not actually having any problems, so is it really necessary?
If so, do I need to upgrade hboot as well or can I get newer firmware/radio while keeping hboot 1.44 ?
Click to expand...
Click to collapse
At this point in time, you don't NEED to upgrade firmware, but there COULD be benefits such as the updated touchscreen drivers.
And since you're s-off, you can flash new firmware(s) including updated hboot, and still be able to downgrade anytime you choose.
Updating firmware or hboot will not change your s-off status, and therefore allow you to downgrade at your choice.
Sent from my HTC One using xda app-developers app
Ive got a quick question regarding this, is firmware ROM dependent - i.e does it matter if im on the 4.3 Sense ROM or the 4.3 Play ROM to flash the 4.3 Firmware?
TheOozyMan said:
Ive got a quick question regarding this, is firmware ROM dependent - i.e does it matter if im on the 4.3 Sense ROM or the 4.3 Play ROM to flash the 4.3 Firmware?
Click to expand...
Click to collapse
Nope. Like I said, currently the ROMs are firmware independent. This could change in the future, but for now it doesn't matter.
Sent from my HTC One using xda app-developers app
Thanks again for the help, I have another question about firmware flashing. I want to flash the latest firmware.zip on my HTC one and I'm already S-OFF. Can I just do this in TWRP and can I do it anytime or do I need to do it before I flash a ROM?
TheOozyMan said:
Thanks again for the help, I have another question about firmware flashing. I want to flash the latest firmware.zip on my HTC one and I'm already S-OFF. Can I just do this in TWRP and can I do it anytime or do I need to do it before I flash a ROM?
Click to expand...
Click to collapse
Firmware needs to be flashed in fastboot.
"fastboot oem rebootRUU"
"fastboot flash zip firmware.zip"
"fastboot flash zip firmware.zip"
(Yes, twice)
Be sure to check an make sure everything was successful.
"fastboot reboot"
Sent from my HTC One using XDA Premium 4 mobile app
Thanks, but I read somewhere that you need to flash firmware and then flash a ROM? Is that true?
Also whats the worst thing that could happen if I messed something up, could I just restore a nandroid?
TheOozyMan said:
Thanks, but I read somewhere that you need to flash firmware and then flash a ROM? Is that true?
Also whats the worst thing that could happen if I messed something up, could I just restore a nandroid?
Click to expand...
Click to collapse
The worst thing that could happen is a brick-- but that's unlikely.
Nandroids don't backup/restore firmware.
I'd recommend NOT updating hboot.img, or sbl??.img when updating firmware.
Only include these in firmware.zip: android-info.txt, adsp.img, radio.img, rcdata.img, tp_SYN3302.img, rpm.img and tz.img.
These get you (in order) the DSP, radio, radio config data, touch pad driver, and some misc stuff (rpm and tz).
Hi, I want to get 3.22 firmware and 4.3.
So, i'm planning to go back to stock by using recovery mode (odexed) by mike1986's guide.
http://forum.xda-developers.com/showthread.php?t=2265618
Then, after going to stock, i would update through HTC OTA to get the 3.22 firmware.. would this work?
By the way, I'm s-on with 1.54 hboot, so i think the only way for me to get the latest firmware(3.22) is through HTC OTA update in the stock rom.
Thanks everybody!!
Anyone? will this work?
If you're just going to flash a custom ROM and kernel, why are you trying to get the OTA?
Sent from my HTC One using XDA Premium 4 mobile app
so I could get 3.22 firmware? haha does that make sense?
Is there anyway that I can get 3.22 firmware with s-on and 1.54 hboot?
rainierzam said:
so I could get 3.22 firmware? haha does that make sense?
Is there anyway that I can get 3.22 firmware with s-on and 1.54 hboot?
Click to expand...
Click to collapse
Nope, only through official stock updates afaik...
But yeah, I think you're steps are right:
1. Restore stock nandroid backup
2. Restore stock recovery
3. Re-lock the device using (I believe) fastboot...
But not completely sure myself still either...
I'm also wondering how to go back to stock. HBoot 1.54, S-on. Im on .206 so the first method wont work for me I think. I can't find a decent tutorial. Still quite noobish when it comes to this stuff
Hi guys,
I am the same, S-ON with hboot 1.54 ,, and all I want to do is to get the last update firmware , as I understand it is something that can't be flashed with a ROM like ARHD 22 so what are the right steps please. and what are the risks if there is any.
thanks.
It seems this is the way:
1. Restore stock rom/nandroid backup
2. Restore stock recovery
3. Relock the bootloader using fastboot, with this command: fastboot oem lock
That SHOULD be it I think,
Should I get the odexed of v4.1.2 1.29.1540.17 then wait for the htc one update in the phone to get the 3.22 firmware?
rainierzam said:
Should I get the odexed of v4.1.2 1.29.1540.17 then wait for the htc one update in the phone to get the 3.22 firmware?
Click to expand...
Click to collapse
I've been asking myself the same questions today and researched about it, then made this post for clarification http://forum.xda-developers.com/showthread.php?t=2462048
Basically, afaik I'm running 3.22 having updated from 3.17 (Maximus HD 13.0) to 3.22 (Maximus HD 14.0) via OTA. I also have and always have had hboot 1.54 and S-On
Ah, you're looking for the firmware upgrade. When I flashed the 1.29.1540.16 RUU to grab the update and get a system dump I had to downgrade my firmware and hboot in order to get the RUU to flash. I'm s-off and I was on GPe firmware, so this may not pertain to anyone in this thread.
I believe the stock nandroid and recovery would be the only way to go for s-on devices. If you're already on the latest firmware (prior to the new 4.3 OTA) and hboot, there isn't a newer RUU yet. And since you can't downgrade due to s-on, you'll have to use a nandroid and flash a stock recovery.
I may be completely wrong, so please correct me if I am.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
Ah, you're looking for the firmware upgrade. When I flashed the 1.29.1540.16 RUU to grab the update and get a system dump I had to downgrade my firmware and hboot in order to get the RUU to flash. I'm s-off and I was on GPe firmware, so this may not pertain to anyone in this thread.
I believe the stock nandroid and recovery would be the only way to go for s-on devices. If you're already on the latest firmware (prior to the new 4.3 OTA) and hboot, there isn't a newer RUU yet. And since you can't downgrade due to s-on, you'll have to use a nandroid and flash a stock recovery.
I may be completely wrong, so please correct me if I am.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was under the same impression, but as it turns out 'build number' in your Settings/About/Software/More IS the firmware version, and mine is 3.22.1540, and I don't have S-On, I have hboot 1.54 and I just did an OTA from a custom rom on base 3.17 to the one on 3.22
ieldra said:
I was under the same impression, but as it turns out 'build number' in your Settings/About/Software/More IS the firmware version, and mine is 3.22.1540, and I don't have S-On, I have hboot 1.54 and I just did an OTA from a custom rom on base 3.17 to the one on 3.22
Click to expand...
Click to collapse
So it was the official OTA from HTC, or an OTA that the developer of the custom rom pushed out?
But if you have S-off you could just downgrade, RUU, then receive the OTA anyway, so it doesn't really apply.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
So it was the official OTA from HTC, or an OTA that the developer of the custom rom pushed out?
But if you have S-off you could just downgrade, RUU, then receive the OTA anyway, so it doesn't really apply.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Custom developer, but I still am running the latest firmware am I not? Only thing I am uncertain about is whether the baseband version corresponds to the one on 3.22, and why does it say "OS-2.24.901.1" on my bootloader
ieldra said:
Custom developer, but I still am running the latest firmware am I not? Only thing I am uncertain about is whether the baseband version corresponds to the one on 3.22, and why does it say "OS-2.24.901.1" on my bootloader
Click to expand...
Click to collapse
OTA's from dev's will not include firmware. The version you are seeing in the setting menu is the version listed in the build.prop, it isn't actually showing the devices firmware version.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
OTA's from dev's will not include firmware. The version you are seeing in the setting menu is the version listed in the build.prop, it isn't actually showing the devices firmware version.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So having S-On, hboot 1.54 and no recovery of my stock android, what can I do to update my firmware and radio ? My CID is CID_401, I can't find any RUUs or nandroid backs for it
Edit:I think I have a TWRP backup of my phone i made one day after buying it, although I think it is after I upgraded to 4.2.2 OTA (stock) and unlocked and rooted. However it should still be a stock backup. Will this help in anyway? (Note: I use CWM now)
ieldra said:
So having S-On, hboot 1.54 and no recovery of my stock android, what can I do to update my firmware and radio ? My CID is CID_401, I can't find any RUUs or nandroid backs for it
Edit:I think I have a TWRP backup of my phone i made one day after buying it, although I think it is after I upgraded to 4.2.2 OTA (stock) and unlocked and rooted. However it should still be a stock backup. Will this help in anyway? (Note: I use CWM now)
Click to expand...
Click to collapse
Radios are flashable in recovery.
The backup will work if you can find a stock recovery to flash, then relock the boot loader and receive OTA. If there's even an OTA for your CID yet.
Though the backup being rooted may cause the OTA to fail.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
Radios are flashable in recovery.
The backup will work if you can find a stock recovery to flash, then relock the boot loader and receive OTA. If there's even an OTA for your CID yet.
Though the backup being rooted may cause the OTA to fail.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
is the stock recovery CID dependent ? Also, can I not simply unroot if I am rooted?
ieldra said:
is the stock recovery CID dependent ? Also, can I not simply unroot if I am rooted?
Click to expand...
Click to collapse
These are questions I do not know the answers to. I'm one of the lucky ones with s-off, but hopefully someone more knowledgeable on the subject can help.
Sent from my HTC One using XDA Premium 4 mobile app
Hey, on returning to stock using stock recovery, could i use the odexed or de odexed version of 4.3 to get the 3.22 firmware? The rom is posted in the one android development. Coukd i use this instead of mike1986's stock rom?
Sent from my HTC One using Tapatalk 2