Related
here's what i'm running. tampered, unlocked bootloader. hboot 1.15 on CM10 rom. s-on.
I want to get apply the newest stock jb rom that was recently released and apply all the latest wimax/radios/profiles, and if possible get s-off. I'm wondering what steps i should take.
I'm assuming once i apply the latest ruu i will get all the wimax/radio/profiles updated and the stock rom. However i'm not sure if i should install a sense based rom before applying the ruu or will running the ruu from cm10. Also i'm on a mac and i know i was able to root everything through my mac but i'm looking for a guide with mac specific instructions. So far I was planning on following this
Make a Nandroid backup: that will save where you are now.
Relock bootloader (here's a video showing how)
Download 2.13 RUU (here's football's link to all shipped RUU's and here's post with a mirror link directly to the 2.13 RUU)
Install the 2.13 RUU via your computer (and here's a video on that process).
Once 2.13 RUU is complete, your firmware will be updated.
Use HTC dev unlock again and install recovery (instructions are in the OP here: you've done it once already if you're here).
Just follow dirty racun instructions. Really simple process man. No need to flash that many times.
And then flash jelly bean rooted stock Rom for firmware
Sent from my EVO using xda premium
champ052005 said:
Just follow dirty racun instructions. Really simple process man. No need to flash that many times.
And then flash jelly bean rooted stock Rom for firmware
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Im in the same situation.
Although I am already Jelly Beaned running MeanBean Rom. But I am S-ON and want to Racoon to be S-Off and install the latest RUU. mY problem begins in The Racoon website, The HTC Driver is not working for my PC ( WINdows 8 ) So am stuck Untill I get a darn Driver to work.
Just make sure your in the bootloader when you go too ruu to avoid any problems
Sent from my EVO using xda premium
Error loading RUU
Tried Rancun and step 8 , 2nd command black screen with HTC in center. Not sure but didn't think that was result I should get. Went back to fastboot and RUU failed to load. So I am hboot 1.19 s-on relocked running MeanBean. What can I do to get radio update radio update and s-off from this point. It sees my phone with latest update but I still need radio update and want to be s-off to make things easier going forward. I even tried running the executable version of the new RUU and it failed also trying to update. t/u
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed (error: i have 3.0.1)
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Flash new radios now my phone is bricked and get teh DLOAD drivers on windows.
I'm gonna take a guess and say you flashed the latest firmware 3.16 without flashing the previous firmware update 3.15.
There is no radio only zip available from the latest OTA update for this very reason.
If this is the case your phone is unrecoverable . back to sprint
Sent from my EVO using xda premium
Shad Stang said:
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Click to expand...
Click to collapse
u must have did something u wasnt suupposed to do cause meanbean would not hurt your phone in anyway bro
I second this, I am having issues as well.
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Cruise was right, i thought i had the radio that came with 3.15 but i really had the radio that came with 1.22 XD.
Need to Update...not sure how!
cruise350 said:
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Click to expand...
Click to collapse
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
KEMODREAMS said:
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
Click to expand...
Click to collapse
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Need to Update...not sure how!
ronniemayo said:
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ok so I did that and it says I'm s-on. Now what? Do I take the OTA update that says "This will update your ROM (MeanBean) to version MeanBean_3.06"? If so, once it's downloaded what do I do? Restart into bootloader? Also my Titanium backup is saying that it "could not acquire root privileges" What does that mean? Thanks for your help.
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Shad Stang said:
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Click to expand...
Click to collapse
You should read Captain _Throwback's firmware thread
You can root the latest OTA just click the link in my sig
Sent from my PoS MoPho
I'd like to update to the new Stock ROM with Goodies- Questions....
1. Hotspot work on this ROM?
2. What firmware/Radio do I need for this or does any of that get updated automatically?
3. Is there a walk through instruction/video for this update...from such an old ROM?
I have:
Hboot 1.12.0000
S-on
Radio 1.02.12.0427
TWRP 2.1.8
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
NaterTots said:
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I turn the device into s-off, then I can use TWRP to update from zip files right?
I read that I don't want to jump firmware to the latest or I could brick the device. So I thought the process might look like this.
PLEASE CORRECT ME IF I'M WRONG:
1. LazyPanda ( http://forum.xda-developers.com/showthread.php?t=1737123 )
to "s-off" the device
2. Run zip for 2.13.651.1 OTA (which one though?)
....Reboot THEN
run zip for 3.16.651.3 OTA
So I don't brick it
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
3. Install Stock ROM with Goodies...
Am I missing something?
What about the radio (comes with the firmware?)? What's the deal with the boot.img or not (I don't see the firmware WITHOUT boot.img included)?
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
premo15 said:
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
Click to expand...
Click to collapse
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
ZenInsight said:
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
Click to expand...
Click to collapse
That's what I was saying in another thread. With samsung phones you just flash and reboot. With these HTC phones you have to update this downgrade that just to flash a rom. I came from a one X and you had to flash the boot.img every time you wanted to flash a rom/kernel/modem.
Sent from my SAMSUNG-SGH-I717
No. Dont s-off then run dirty racun. S-off is what dirty racun does. He's saying Use RUU to get to 3.15, THEN use dirty racun (as per their instructions).
Then STAY at 3.15. Uncles you wanna use a 3.16 sense ROM (which is no different than a 3.15 ROM). If you S-off and update to 3.16 firmware AND flash the 3.16 touch panel image (tp.IMG), you will not be able to use any ROMs that aren't sense 3.16. I would suggest leaving your firmware where it is, and try the ROM you want. Generally, you DO NOT need current firmware to run a current ROM. The two are mutually exclusive (firmware and ROM). I always rock old radios. Newer isn't always better.
From my Evo LTE, yup.
1. S-OFF with DirtyRacun (doesn't really matter which RUU you choose)
2. Install custom recovery through fastboot (latest TWRP should be fine, depending on the ROM you choose - you might need 2.4.0.0 or older if flashing a ROM with an outdated update binary)
3. Flash ROM of your choice.
4. Update to latest firmware using most recent zip from firmware thread (this is done through the bootloader, not recovery)
5. Profit.
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
ZenInsight said:
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
Click to expand...
Click to collapse
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Captain_Throwback said:
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Click to expand...
Click to collapse
Ok. I get it. I lose TWRP once I "s-off", so I have to put it back on.
Just flash 3.16...it doesn't matter anymore about the touchscreen, that's been fixed.
Radio is included in the 3.16 firmware, not the ROM.
Flash the Stock with goodies...and I'll be fine.
Phew.... I hope this is right.
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Funny you say that since 3.15 firmware was causing soft bricks with older hboots. The only problem with the latest update is that aosp roms are stuck with out touch screen support for now.
Captain_Throwback said:
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
Click to expand...
Click to collapse
Alright. Guess I missed something. Last time I was in there , if you didn't do 3.15 prior to 3.16 you were hosed.
But I did see the firmware haus dropped that it was said would be OK regardless of 3.15 or not. Just hadn't seen anyone try it.
Definitely listen to Cap'n. He's the man when it comes to firmwares and radios.
From my Evo LTE, yup.
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Trioculus said:
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Click to expand...
Click to collapse
Did you not download the most recent firmware from my thread? Because there's no way it should've bricked you. I personally updated from 1.22 firmware up to 3.16 with no issues, and someone else updated from 1.13 firmware up to 3.16. What exact file did you use?
EDIT: I just looked, and I don't even have a file available with that name in my thread (anymore). The only one I have is this, which is the extended firmware which eliminates the bricking issue. Sounds like you had an old download.
Captain_Throwback said:
What exact file did you use?
Click to expand...
Click to collapse
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Trioculus said:
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Click to expand...
Click to collapse
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Captain_Throwback said:
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Click to expand...
Click to collapse
ouch..That sucks, man.
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
badtlc said:
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
Click to expand...
Click to collapse
Yes there are a lot of files that cant be updated with roms. The only way to get all of the new firmware is to run the ruu. Turge has figured out how to flash radios now without flashing the ruu so thats good. But thats not everything. I'd wait to run the ruu until the devs change their rom base to the new update. Otherwise no custom rom yet. You can root the stock update after installing, just not many goodies atm.
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Yep I ran ruu and got it running stock but my 2nd x+ still running old one wit elegancia till roms get updated I don't mind unrooting updating and rooting takes 30 min tops just patiently waiting for a update hell if viper gets updated first ill rock that
Sent from my HTC One X+ using XDA Premium HD app
badtlc said:
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
nugzo said:
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
Click to expand...
Click to collapse
Correct, but I wasn't sure if you could update directly to that RUU from a custom ROM and get all the updates like hboot, firmware and radio. I was wondering if I needed to go from a custom ROM back to stock 1.15 and THEN do this 1.19 update to get everything updated properly.
If you update your phone to the latest RUU, you won't be able to installed a custom ROM until the devs update their ROM. You update, you stay stock for a moment. You still can ROOT the stock ROM.
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
[QUOTE"badtlc"]If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?[/QUOTE]
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.[/QUOTE]
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
Click to expand...
Click to collapse
You can do one of two things to get the full update. One is to go back to a 1.15 stock ROM, flash the stock recovery and run the OTA. The other is to run the latest RUU from HTC (the one from the link posted above) after you've flashed the stock recovery and re-locked the bootloader (otherwise the RUU might not proceed). Bare in mind that running the RUU will wipe your phone to factory settings.
I started a thread here http://forum.xda-developers.com/showthread.php?t=2245955 about people's experiences updating and post-update. Once you decide to update feel free to share your experience there!
I have already updated. I went from elegancia. I locked the bootloader, rebooted to fastboot, and then ran the 1.15 stock RUU. After that, I ran the 1.19 update I downloaded from HTC. I was just trying to figure out if I would have went straight from elegancia to 1.19 if everything including radio, kernel, etc. would have updated properly since elegancia was on the phone and not stock version 1.15. I don't know what these RUUs look at before applying their updates.
Hey guys, I have an HTC One that is stuck in a boot loop after an OTA update to 4.4.3. What do I need to do/download to wipe the phone back to factory settings so it will work again?
S-ON, hboot is 1.55, and yes I have tried factory reset in the bootloader menu
ExPwN said:
Hey guys, I have an HTC One that is stuck in a boot loop after an OTA update to 4.4.3. What do I need to do/download to wipe the phone back to factory settings so it will work again?
S-ON, hboot is 1.55, and yes I have tried factory reset in the bootloader menu
Click to expand...
Click to collapse
You've got 4.4.3 update in OTA? Are you using Google Edition HTC One?
Bootloop after OTA generally results if your system is somewhat modified (like custom recovery or changed system files) and you forced install the OTA. You can flash stock RUU (exe or zip) and then try OTA again.
hafizimtiaz said:
You've got 4.4.3 update in OTA? Are you using Google Edition HTC One?
Bootloop after OTA generally results if your system is somewhat modified (like custom recovery or changed system files) and you forced install the OTA. You can flash stock RUU (exe or zip) and then try OTA again.
Click to expand...
Click to collapse
I'm not sure what update it was, it's not my phone. The phone WAS completely stock however. I thought I have to have Soff to flash the RUU
After some googling, I found the RUU, but I have to flash hboot 1.44 which I can't do because S-On. The only way to make S-Off is to have the phone working. So this is just a giant brick now, unless there's a way to turn S-Off from fastboot.
Have you tried flashing an RUU which has the same hboot as yours? I mean, if you try flashing a 4.4.2 RUU exe, what does it say? If exe fails, you can try RUU ZIP. although I am pretty sure that decrypted ZIP flashing requires s-off.