Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with superCID when I Did hex editing CWS__001 to 111111 (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
What is the purpose of updating the firmware? If you just want to be on the latest Android 4.2.2 Sense 5 update you can flash one of the ROMs from our development section.
Sent from my Evita
ted77usa said:
Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with
superCID (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
Click to expand...
Click to collapse
Only real reason to upgrade with ruu is if you want to run certain cm10 roms. Being they require 2.14 hboot and certain firmware updates to run properly.
Sent from my HTC One XL using XDA Premium 4 mobile app
ted77usa said:
Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with
superCID (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
Click to expand...
Click to collapse
You just need to s-off, then run the ruu. You won't have to relock bootloader anymore before ruu anymore after you s-off, you just need to reflash recovery and flash your rom afterwards. S-off is super easy also takes only minutes.
DvineLord said:
You just need to s-off, then run the ruu. You won't have to relock bootloader anymore before ruu anymore after you s-off, you just need to reflash recovery and flash your rom afterwards. S-off is super easy also takes only minutes.
Click to expand...
Click to collapse
Any link please.....
timmaaa said:
What is the purpose of updating the firmware? If you just want to be on the latest Android 4.2.2 Sense 5 update you can flash one of the ROMs from our development section.
Sent from my Evita
Click to expand...
Click to collapse
Swyped from T3DRO1CS RedHoXence
Search for "Facepalm s-off" within our forum.
Sent from my Evita
ted77usa said:
Any link please.....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
timmaaa said:
Search for "Facepalm s-off" within our forum.
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
So like u guys suggested.....either updated firmware to 2.15 or just flash the jb sense 5 ROM with beastmode kernel on top to overcome the signal drop and bootloop issue.
In case I'm fail.....would I be able to go back to bootloader using power + volume down? then recovery ...and restore my backup?
Swyped from T3DRO1CS RedHoXence
Yeah that's right, if you're going to update the firmware you'll need s-off first though. And yes, you can always get to the bootloader (and then recovery) issuing that button combo.
Sent from my Evita
timmaaa said:
Yeah that's right, if you're going to update the firmware you'll need s-off first though. And yes, you can always get to the bootloader (and then recovery) issuing that button combo.
Sent from my Evita
Click to expand...
Click to collapse
In order to do s-off I need supercid first right? And seem like I already have supercid when I did hex editing cws__001 to 111111 but it not show on my bootloader since I'm still S-ON right?
Is there any way to check if I'm supercid?
Swyped from T3DRO1CS RedHoXence
ted77usa said:
In case I'm fail.....would I be able to go back to recovery using power + volume down? And restore my backup?
Click to expand...
Click to collapse
That button combo gets you into bootloader. From there you can boot recovery. There is no button combo for recovery.
The 2 are related, but separate, and completely different things.
But yes, depending on what "fails" you should be able to get to recovery and restore your nandroid.
Keep in mind, that since you are S-on, you will need to flash boot.img for the ROM using fastboot, and same thing if you try to restore a nandroid. One more reason why S-off should be considered.
---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------
ted77usa said:
In order to do s-off I need supercid first right? And seem like I already have supercid when I did hex editing cws__001 to 111111 but it not show on my bootloader since I'm still S-ON right?
Is there any way to check if I'm supercid?
Click to expand...
Click to collapse
I already answered that question when you posted it in another, non-related thread.
redpoint73 said:
That button combo gets you into bootloader. From there you can boot recovery. There is no button combo for recovery.
The 2 are related, but separate, and completely different things.
But yes, depending on what "fails" you should be able to get to recovery and restore your nandroid.
Keep in mind, that since you are S-on, you will need to flash boot.img for the ROM using fastboot, and same thing if you try to restore a nandroid. One more reason why S-off should be considered.
---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------
I already answered that question when you posted it in another, non-related thread.
Click to expand...
Click to collapse
On nandroid backup files I saw boot.emms and recovery.emms files do do I still need to flash boot.img seperately incase in failing ? Or just restore my backup? I'm sorry that's y i reposted here and deleted the other post......
Swyped from T3DRO1CS RedHoXence
As long as you have a backup of the boot.img you can flash it via fastboot after restoring your system backup. You need to rename it to boot.img though. It's probably worth getting s-off to be honest, it only takes a few minutes and it'll save you a ton of hassle in the future.
Sent from my Evita
ted77usa said:
On nandroid backup files I saw boot.emms and recovery.emms files do do I still need to flash boot.img seperately incase in failing ?
Click to expand...
Click to collapse
You will still need to flash it with hboot.
boot.img will not flash in recovery, due to the s-on limitations.
redpoint73 said:
You will still need to flash it with hboot.
boot.img will not flash in recovery, due to the s-on limitations.
Click to expand...
Click to collapse
Just wondering why on ICS ROM I can restore my back up without flashing boot .img with S-ON?
Swyped from T3DRO1CS RedHoXence
ted77usa said:
Just wondering why on ICS ROM I can restore my back up without flashing boot .img with S-ON?
Click to expand...
Click to collapse
Because the boot.img that was still on the phone was the same (or similar enough) that it worked with the ROM that was on your nandroid.
BTW, of course I meant "flash with fastboot" not hboot.
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
DvineLord said:
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
Click to expand...
Click to collapse
That's what I thought......
Swyped from T3DRO1CS RedHoXence
DvineLord said:
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
Click to expand...
Click to collapse
Ahh, crap. Forgot that boot.img was flashable in recovery on hboot 1.09. That hboot was so long ago, and rarely pops up here anymore. And it was the hboot I was on at one time!
Forget everything I said about boot.img!
But if you ever update hboot to any version 1.14 or higher, everything I said becomes true again.
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
Ahh, crap. Forgot that boot.img was flashable in recovery on hboot 1.09. That hboot was so long ago, and rarely pops up here anymore. And it was the hboot I was on at one time!
Forget everything I said about boot.img!
But if you ever update hboot to any version 1.14 or higher, everything I said becomes true again.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
So your saying is better to keep my 1.09 hboot for now like timmaa said on earlier post.....just install JB ROM sense 5 and flash beastmode kernel on top of it if I have signal drop and reboot issue......
Swyped from T3DRO1CS RedHoXence
Related
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
Hi,
Download hboot 1.17 HERE
Then you can use an RUU for that firmware.
which ruu can i use now???
i only want to restore my htc sensation completely!
james0912 said:
which ruu can i use now???
i only want to restore my htc sensation completely!
Click to expand...
Click to collapse
Hi,
You need an RUU that matches your area and carrier.
Look HERE
malybru said:
Hi,
Download hboot 1.17 HERE
Then you can use an RUU for that firmware.
Click to expand...
Click to collapse
Hey malybru can you flash this file with the stock recovery? Also this only changes the Hboot version correct?
T-Macgnolia said:
Hey malybru can you flash this file with the stock recovery? Also this only changes the Hboot version correct?
Click to expand...
Click to collapse
Hi,
It's a PG58IMG.zip .
So, it's just placed on the sd card.
Recovery is not involved.
Yes,it will only change the hboot.
malybru said:
Hi,
It's a PG58IMG.zip .
So, it's just placed on the sd card.
Recovery is not involved.
Yes,it will only change the hboot.
Click to expand...
Click to collapse
Man I had a duh money, I realized after I posted that that that file will flash automatically when you boot to Hboot, as that is the file name that Hboot looks for. But still doesn't Hboot use the recovery to flash the file?
T-Macgnolia said:
Man I had a duh money, I realized after I posted that that that file will flash automatically when you boot to Hboot, as that is the file name that Hboot looks for. But still doesn't Hboot use the recovery to flash the file?
Click to expand...
Click to collapse
Hi,
I knew you knew that.
I just posted for general information.
I think it flashes in bootloader,before recovery starts.
malybru said:
Hi,
I knew you knew that.
I just posted for general information.
I think it flashes in bootloader,before recovery starts.
Click to expand...
Click to collapse
Ok this will be my last post here cause I don't want to hyjack this thread.
This has brought a question to mind and I will have to see if I can find the answer some how. The question is what does Hboot use to flash the PG58IMG.zip. I personally have always thought it used recovery to flash the file.
T-Macgnolia said:
Ok this will be my last post here cause I don't want to hyjack this thread.
This has brought a question to mind and I will have to see if I can find the answer some how. The question is what does Hboot use to flash the PG58IMG.zip. I personally have always thought it used recovery to flash the file.
Click to expand...
Click to collapse
It uses the bootloader to flash the file. If you put it on your sd card and reboot into bootloader (volume down button + power button) you will be asked to update. Choose yes using the volume buttons and the file will be flashed, easy as that
Sent from my HTC Sensation using XDA
james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
When you install a rom by a RUU, it will also flash the stock Hboot version. Take a look at the shipped roms thread.
Sent from my HTC Sensation using XDA
james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
Hboot 1.27 is clearly ICS.
Download official RUU from here (RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed)
This is the latest official ICS RUU for unbranded Europe Sensation.
If your device is branded or your region is not Europe then search for the appropriare RUU.
Run the exe from pc with phone usb plugged. It will restore your phone as "out of the box".
Hope it helped.
Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
3) Which Custom ROM am I able to flash at the moment? Any, based on ICS?
FnH84 said:
Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
3) Which Custom ROM am I able to flash at the moment? Any, based on ICS?
Click to expand...
Click to collapse
Hi,
1. I think that you can just run the RUU in the post above yours.(If your phone is European)
2.Downgrading is not possible on hboot 1.27.000
HTC have locked you out of this possibility.
3.As you say.Any 3.32. based ICS ROM.
malybru said:
Hi,
1. I think that you can just run the RUU in the post above yours.(If your phone is European)
2.Downgrading is not possible on hboot 1.27.000
HTC have locked you out of this possibility.
3.As you say.Any 3.32. based ICS ROM.
Click to expand...
Click to collapse
Thank you very much Not planning un-root but was just wondering, in case I have to do that at some point, it's good to know how
FnH84 said:
Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
Click to expand...
Click to collapse
It can be done only by running corresponding RUU which can be found based on your firmware(in your case it is 3.32) and cid (to get cid "fastboot getvar cid")...if you are unbranded i.e. cid is HTC__001..then you can run the above mentioned ruu...or else you should get the appropriate one...if you can't find it then post your cid along with radio..we can find the appropriate one for you
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
Click to expand...
Click to collapse
If you are S-ON you can't downgrade...not by running a RUU or by flashing firmware directly...that's why people use revolutionary first to get soff and then they'll flash unlocked firmware to update the hboot and all...
It you are SOFF you can literally do anything ..upgrade, downgrade..its your choice..
3 ) Which Custom ROM am I able to flash at the moment? Any, based on ICS?
Click to expand...
Click to collapse
As you are unlocked via HTC dev..if you update your recovery with 4EXT latest one which has smartflash mode ON(exclusive SON flash)..you could have any ROM
Edit: I'm bit late huh anyways for more detailed answer look ay my post
sent from my blazing fast pyramid through sonic waves
When I update to OTA ICS on tmobile will this update also update my hboot version?
Right now im 1.18 i think, im assuming hboot will change bc you need to be hboot 1.23 or higher for ICS?
Yes it will. If you're not s-off then I suggest you use revolutionary now while you can...
GROGG88 said:
Yes it will. If you're not s-off then I suggest you use revolutionary now while you can...
Click to expand...
Click to collapse
Thanks, I am s-off via revolutionary, and ive read that s-off wont change.
Ok so is their anyway to downgrade Hboot version after it gets upgraded. The reason why is i know the only hboot which supports both ICS and GB is 1.23, i like that flexibility
el7145 said:
Thanks, I am s-off via revolutionary, and ive read that s-off wont change.
Ok so is their anyway to downgrade Hboot version after it gets upgraded. The reason why is i know the only hboot which supports both ICS and GB is 1.23, i like that flexibility
Click to expand...
Click to collapse
You're s-off. You can use whatever hboot you want (that's ICS compatible). I'd recommend 1.27.1100 revolutionary's unlocked bootloader...
If you're s-off then you don't really need to worry about changing your hboot though. You'll need to flash other firmware to go back to GB anyways, so why not just include 1.18 in that package?
GROGG88 said:
You're s-off. You can use whatever hboot you want (that's ICS compatible). I'd recommend 1.27.1100 revolutionary's unlocked bootloader...
If you're s-off then you don't really need to worry about changing your hboot though. You'll need to flash other firmware to go back to GB anyways, so why not just include 1.18 in that package?
Click to expand...
Click to collapse
why do u recommend 1.27.1100?
For me (due to my very noob status) flashing back to a GB rom from ICS would involve an xtra step of flashing hboot, id rather only have to flash the firmware, i dont know how yet to put things in "packages" With 1.23 i wouldnt need to worry at all about hboot, whether GB or ICS
el7145 said:
why do u recommend 1.27.1100?
For me (due to my very noob status) flashing back to a GB rom from ICS would involve an xtra step of flashing hboot, id rather only have to flash the firmware, i dont know how yet to put things in "packages" With 1.23 i wouldnt need to worry at all about hboot, whether GB or ICS
Click to expand...
Click to collapse
I would recommend 1.27.1100 because it's unlocked, but really it doesn't matter.
Your hboot can be part of your firmware package. Just take your GB firmware package, unzip it, put your desired hboot in there, and rezip it. There's nothing difficult about it...
I use 4ext recovery control, and a couple firmware packages to swap back and forth all the time.
1. Use any file explorer to transfer the firmware package to the root of my sdcard.
2. Use 4ext recovery control "power menu" to reboot into recovery.
3. Flash rom or restore backup. (format or superwipe if necessary)
4. Use 4ext recovery power menu to reboot into bootloader.
5. Volume up to select bootloader from fastboot menu.
6. Flash firmware through bootloader.
7. Power to reboot... Done!
Click to expand...
Click to collapse
Works going either way, no battery pulls, no connecting to PC, no headaches! It takes about 10 minutes or less to go back and forth...
I just restored my stock rom this morning using the method I noted above with a firmware I packaged for stock GB which includes stock recovery and hboot...
Alright man, thanks for all your help, this clears it all up for me
GROGG88 said:
You're s-off. You can use whatever hboot you want (that's ICS compatible). I'd recommend 1.27.1100 revolutionary's unlocked bootloader...
If you're s-off then you don't really need to worry about changing your hboot though. You'll need to flash other firmware to go back to GB anyways, so why not just include 1.18 in that package?
Click to expand...
Click to collapse
So what's the advantage of having a unlocked hboot since from what you've told me before we can still flash CWM and root and install custom ROM on it as long asI am s-off?
I've updated everything now with OTA. Seems to run fine and no need to reinstall the apps and contacts.
I want to make a backup of this NAND now..so I guess I need CWM install to do the backup? But should I unlock the bootloader? Also, how about doing it via the officical HTC website? Does that work too or I have to flash the unlocked bootloader?
If you are already soff then there is no need to soff again through HTC dev
Sent from my sensational sensation 4g
newr said:
So what's the advantage of having a unlocked hboot since from what you've told me before we can still flash CWM and root and install custom ROM on it as long asI am s-off?
I've updated everything now with OTA. Seems to run fine and no need to reinstall the apps and contacts.
I want to make a backup of this NAND now..so I guess I need CWM install to do the backup? But should I unlock the bootloader? Also, how about doing it via the officical HTC website? Does that work too or I have to flash the unlocked bootloader?
Click to expand...
Click to collapse
Honestly, I can't tell you why people recommend it. I flash custom recoveries and radios with locked hboot frequently.
Sent from my HTC Sensation 4G using Tapatalk 2
GROGG88 said:
Honestly, I can't tell you why people recommend it. I flash custom recoveries and radios with locked hboot frequently.
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
Ok...I won't bother with it then.
---------- Post added at 02:06 AM ---------- Previous post was at 01:11 AM ----------
GROGG88 said:
Honestly, I can't tell you why people recommend it. I flash custom recoveries and radios with locked hboot frequently.
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
Hmm..I just tried flashing CWM 5.0.2.0 via fastboot...I get error saying incorrect CID. Do I have to superCID to flash CWM? I didn't have to do that before. Is this the problem with locked bootloader? If so, guess I have to flash the bootloader...is there a tutorial about that and will I lose all the data? I went to the HTCdev unlock page and was going to try there..but it says it will erase all the data!
newr said:
Ok...I won't bother with it then.
Click to expand...
Click to collapse
Actually, it has just been brought to my attention that some users who used juopunutbear to s-off may have issues with a locked bootloader...
Sent from my HTC Sensation 4G using Tapatalk 2
GROGG88 said:
Actually, it has just been brought to my attention that some users who used juopunutbear to s-off may have issues with a locked bootloader...
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
Hmm.. I used revolutionary before to s-off...
---------- Post added at 02:29 AM ---------- Previous post was at 02:07 AM ----------
newr said:
Ok...I won't bother with it then.
---------- Post added at 02:06 AM ---------- Previous post was at 01:11 AM ----------
Hmm..I just tried flashing CWM 5.0.2.0 via fastboot...I get error saying incorrect CID. Do I have to superCID to flash CWM? I didn't have to do that before. Is this the problem with locked bootloader? If so, guess I have to flash the bootloader...is there a tutorial about that and will I lose all the data? I went to the HTCdev unlock page and was going to try there..but it says it will erase all the data!
Click to expand...
Click to collapse
Ok, so I change to superCID and flashed CWM and it's working now! Strange that I have to superCID to have it working since I didn't have to when I first when through the process with GB.
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
seth50k said:
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
Click to expand...
Click to collapse
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
31ken31 said:
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
seth50k said:
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
Click to expand...
Click to collapse
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
RollTribe said:
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
Click to expand...
Click to collapse
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
seth50k said:
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
Click to expand...
Click to collapse
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
RollTribe said:
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
Click to expand...
Click to collapse
I've tried running RUU, it gets about halfway and fails. Do I need to flash the stock recovery and relock first, then run a RUU?
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
breezedragon said:
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
seth50k said:
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
Click to expand...
Click to collapse
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
exad said:
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Unlock, flash a sense rooted rom, soff and then ruu up to 3.18
Sent from my One X using xda app-developers app
RollTribe said:
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
seth50k said:
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
Click to expand...
Click to collapse
Yup, you can swap the last two if you want
RollTribe said:
Yup, you can swap the last two if you want
Click to expand...
Click to collapse
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yep, looks like it's bricked. http://forum.xda-developers.com/showthread.php?t=2181929
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
RollTribe said:
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
Click to expand...
Click to collapse
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Sorry about your phone. It's Jtagg or new phone.
---------- Post added at 02:34 PM ---------- Previous post was at 02:34 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Click to expand...
Click to collapse
They state on their site that after unlocking the bootloader, RUU/OTA could brick you.
If you plan to try warranty with HTC, do not mention that you unlocked. They will charge you 200 straight up no matter what you say.
RollTribe said:
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
But was it the 3.18? It applies specifically for the AT&T 3.18 (and for some 3.17 JB RUUs on other carriers, and reported by some folks on this forum).
If you were able to run the 3.18 RUU successfully with SuperCID and S-on, I believe this is the first I've heard of it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
Click to expand...
Click to collapse
SuperCID as implemented on the AT&T One X is a mod/hack, and therefore not explicitly "allowed" by HTC. They can't really be held responsible for the effects of it.
SuperCID shouldn't be "expected" to brick under these conditions (worked fine with pre-JB RUUs), and nobody here has really been able to explain exactly why the phone bricks from SuperCID. But unfortunately, it does.
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.
*** WHAT MY PROBLEM IS***
PLEASE can someone confirm any AOSP ROM that works with 2.15 HBOOT?
***WHAT I KNOW***
( i know the CM 10.2 thread says that RUU 3.18 which will make the hboot 2.14 but since 2.15 is latest i assume it should support)
(i also know that [HBOOT 2.15 is essential for SENSE 5 4.2.2 to run,i believe that's the only reason people go for 2.15)
***WHAT I HAVE TRIED***
NOW from what i have tried is that the 1st stable cm 10 release doesn't work with 2.15 (obviously too old build) my screen also became responsive(i believe that because of touch panel firmware) then with the latest stable release of cm 10.1 it specified that it needs hboot 2.14 and hence couldn't flash.
with PAC 4.3 it does gets installed but screen is unresponsive and infinite bootloops!:silly:
***WILL THIS WORK***
so now if i RUU 3.18 i will have to unlock boot loader and root it (M SOFF SUPER CID) which i m not really ready to do!
now there are methods that can help u downgrade/upgrade your firmware , can i do that?
also will using torched kernel help in me in any way?
***WHY DO I WANT AOSP***
Viper XL 4.2.2 best ROM ever hats off but the thing is i dont know why but i have Signal issues i tried flashing the recommended RADIO version.
since the vendor had already RUUd my device that was meant from some ASIAN region and already came with SENSE 5 and i dint mess up with it in any way still i had signal issues (which are unpredictable) i found by GSAM BATTERY monitor that around 30 to 40% of my battery is consumed by RADIO.
also the best signal is around -81db
i also had some issues with camera!
and then there is the numerous options i can have with AOSP.
****LASTLY CAN ANYONE HELP****
:angel:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
954wrecker said:
He makes it hard to understand but he is S-ON so he is screwed at this point
Sent from my HTC One XL
Click to expand...
Click to collapse
no no no i am SOFF i know for sure!!!
exad said:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
Click to expand...
Click to collapse
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
954wrecker said:
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
Click to expand...
Click to collapse
LOL u are right thanks!
its just that m kinda paranoid cause every day in the Help and Troubleshooting section there is some thread dats says BRICKED so always to be on the safer side!
Sonone said:
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
Click to expand...
Click to collapse
yes
exad said:
yes
Click to expand...
Click to collapse
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Sonone said:
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Click to expand...
Click to collapse
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
exad said:
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
Click to expand...
Click to collapse
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
redpoint73 said:
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
Click to expand...
Click to collapse
as always thank you...
since u recoomend thats the safest way i will try out that.
have to download the RUU 3.18!!!
*waiting*