Related
Hey everyone! I have recently obtained an HTC Evo 4G and will be making lots of how to videos for it! I do see there are a lot of videos, but not all in one place. I did make many how to videos for the Samsung Epic and other devices and get a great response from everyone!
Please post suggestions to future videos in this thread, or PM me!
I will be posting more how to videos very soon
How to root and clockworkmod the HTC Evo 4G on Android 2.3:
http://www.youtube.com/watch?v=FHyjxKjniKY
How to unroot the HTC Evo 4G to stock Android 2.3.3:
http://www.youtube.com/watch?v=miYjnaaid3s
How to S-ON the HTC EVO 4G Gingerbread From Revolutionary:
http://www.youtube.com/watch?v=r8W6IwvJLG8
How to flash the Synergy Kingdom Rom on the HTC EVO 4G:
http://www.youtube.com/watch?v=uXm9MmaZ6Vk
How to flash the Gingerbread Deck 1.3 Rom on the HTC EVO 4G
http://www.youtube.com/watch?v=drGRHHAnJrw
How to install Amon RA recovery on the HTC EVO 4G
http://www.youtube.com/watch?v=sZSr2DlfdCg
How to install TeamWin Recovery TWRP on the EVO 4G
http://www.youtube.com/watch?v=qeeyUNcBwgA
Youtube Channel:
www.youtube.com/qbking77
You are the one who got me started rooting with my first Android phone, the epic. I am so glad that you are now taking on the EVO 4G. I have contributed to you via paypal in the past and suspect I will be doing so in the near future.
Sent from my PC36100 using Tapatalk
After you are done makin your vids maybe this thread can get stickied to eliminate the repeat questions. Great work.
{ParanoiA} said:
Ur video is for hboot 2.10 not the newer 2.16. It will only work if u used unrevoked to root and not revolutionary. Yes you can get s-on if u rooted with revolutionary but you have to downgrade your hboot with a hacked version. There is a thread around here where someone did it and it is confirmed to work.
Edit: found it
http://forum.xda-developers.com/showthread.php?t=1245649
Sent From My Pocket
Click to expand...
Click to collapse
Thanks for showing me this thread.. I was looking around for it.. I'll be doing a video on that as well
OP updated! Now you can turn S ON after rooting with revolutionary
qbking77 said:
OP updated! Now you can turn S ON after rooting with revolutionary
Click to expand...
Click to collapse
Great job on the videos. I'll be sure to refer people to it if they ask for a guide on how to root/unroot .
Captain_Throwback said:
Great job on the videos. I'll be sure to refer people to it if they ask for a guide on how to root/unroot .
Click to expand...
Click to collapse
Thank you! Means a lot coming from you
i tried this method, it just fails the update.zip and will not turn s back on. i have to go to sprint today and need it stock it wont take the ruu, it wont turn security back on nothing. am i screwed?
aod420247 said:
i tried this method, it just fails the update.zip and will not turn s back on. i have to go to sprint today and need it stock it wont take the ruu, it wont turn security back on nothing. am i screwed?
Click to expand...
Click to collapse
No... if you used revolutionary to root watch my how to s on revolutionary video.
Sent from my MB855 using XDA App
I rooted with the Rev after running the newest RUU and I tried the S-ON zip file but it doesn't return me to S-ON... plus my hboot is at the 6.17. I'm trying to run the S-ON file and the rerun the RUU since I noticed your note that stated the RUU should be ran after the S-ON file... Do I have to root it one again to be able to return to S-ON? I don't think the root should matter since that's on the software level... I need to return this phone asap as my replacement came in... Any help would be appreciated!
gqukyo said:
I rooted with the Rev after running the newest RUU and I tried the S-ON zip file but it doesn't return me to S-ON... plus my hboot is at the 6.17. I'm trying to run the S-ON file and the rerun the RUU since I noticed your note that stated the RUU should be ran after the S-ON file... Do I have to root it one again to be able to return to S-ON? I don't think the root should matter since that's on the software level... I need to return this phone asap as my replacement came in... Any help would be appreciated!
Click to expand...
Click to collapse
I don't understand what it is you did. But what you need to do is:
First, flash a stock (unrooted) ROM. That'll unroot you.
Second, flash the modified HBOOT (6.17) to S-ON.
Third, flash the stock (unrooted) ROM from step 1 to restore stock 2.16 HBOOT.
Captain_Throwback said:
I don't understand what it is you did. But what you need to do is:
First, flash a stock (unrooted) ROM. That'll unroot you.
Second, flash the modified HBOOT (6.17) to S-ON.
Third, flash the stock (unrooted) ROM from step 1 to restore stock 2.16 HBOOT.
Click to expand...
Click to collapse
Thanks for your response. Yeah, that's what I've been doing. I flashed the RUU then I did the S-ON file which looks like the phone took it as I did not get any error msg and it asked me to reboot. I reboot then I pull battery and reboot back to bootloader to see if the S-ON saved but it didn't. Though the Revolutionary pink comment is no longer there, it's still S-OFF...
I will try again though and hope for the best!
---------- Post added at 12:33 PM ---------- Previous post was at 12:15 PM ----------
gqukyo said:
Thanks for your response. Yeah, that's what I've been doing. I flashed the RUU then I did the S-ON file which looks like the phone took it as I did not get any error msg and it asked me to reboot. I reboot then I pull battery and reboot back to bootloader to see if the S-ON saved but it didn't. Though the Revolutionary pink comment is no longer there, it's still S-OFF...
I will try again though and hope for the best!
Click to expand...
Click to collapse
Nope, that didn't work. Still S-OFF with the 6.17 Hboot. I figured I'd try to root it again but as noted, Rev said I was already S-OFF but it couldn't flash the recovery for me and told me to flash my own recovery via fastboot... I haven't done that since the Evo was released...
This is driving me nuts... Even if the phone isn't S-ON, wouldn't the RUU change the Hboot back to the 2.15/2.16? I'm at wits end on what to do...
gqukyo said:
Thanks for your response. Yeah, that's what I've been doing. I flashed the RUU then I did the S-ON file which looks like the phone took it as I did not get any error msg and it asked me to reboot. I reboot then I pull battery and reboot back to bootloader to see if the S-ON saved but it didn't. Though the Revolutionary pink comment is no longer there, it's still S-OFF...
I will try again though and hope for the best!
---------- Post added at 12:33 PM ---------- Previous post was at 12:15 PM ----------
Nope, that didn't work. Still S-OFF with the 6.17 Hboot. I figured I'd try to root it again but as noted, Rev said I was already S-OFF but it couldn't flash the recovery for me and told me to flash my own recovery via fastboot... I haven't done that since the Evo was released...
This is driving me nuts... Even if the phone isn't S-ON, wouldn't the RUU change the Hboot back to the 2.15/2.16? I'm at wits end on what to do...
Click to expand...
Click to collapse
Hmmm. The RUU will only roll back the HBOOT if you're S-ON - because the signature verification is disabled when NAND is unlocked. It just looks at the version number, otherwise, which is why you're stuck.
Have you tried flashing the unrevoked S-ON zip in recovery (you'd need to flash a custom recovery again) and see if that gets you S-ON? Since you're not rooted w/Revolutionary, it could work. I'm really not sure why the modded HBOOT didn't re-lock your NAND. Maybe you should try a different version (I can link you to the one I initially posted, though that may have been the one you used).
Oh this is interesting... so whenever I run the RUU... it turns the hboot back to 2.16 but as soon as I run the S-ON zip and update, it turns it back to the 6.17 hboot and doesn't turn it back to S-ON... I saw the following for returning the Evo 3D's back to S-ON and was wondering it'll work for the Evo 4G?
Then open Command Prompt/Terminal on your computer and navigate to where fastboot is located (on my Windows 7 computer, it's C:/AndroidSDK/tools/. Now, type in the command:
fastboot oem writesecureflag 3
Once this completes you can go into your bootloader and should no longer see "S-OFF" at the top of the screen. It will read "S-ON."
*edit
tried to do the fastboot thing, didnt' pan out... tried to root and S-OFF my refurb'd unit and back to bone stock and that went fine... think there's just something wrong with my phone... guess I'll just return it and hope for the best...
gqukyo said:
Oh this is interesting... so whenever I run the RUU... it turns the hboot back to 2.16 but as soon as I run the S-ON zip and update, it turns it back to the 6.17 hboot and doesn't turn it back to S-ON... I saw the following for returning the Evo 3D's back to S-ON and was wondering it'll work for the Evo 4G?
Then open Command Prompt/Terminal on your computer and navigate to where fastboot is located (on my Windows 7 computer, it's C:/AndroidSDK/tools/. Now, type in the command:
fastboot oem writesecureflag 3
Once this completes you can go into your bootloader and should no longer see "S-OFF" at the top of the screen. It will read "S-ON."
Click to expand...
Click to collapse
I thought that only worked if you had an ENG HBOOT, but who knows - try it and see if it works. It would be nice to have an alternate method for people to use. Out of curiousity, what Hardware version EVO do you have?
OP updated! Added a how to flash a rom video! Let me know what you think.
can sd card be issue for download links being bad.. and cannot recover a back up invalid md5 sum
Kchitown1977 said:
can sd card be issue for download links being bad.. and cannot recover a back up invalid md5 sum
Click to expand...
Click to collapse
If you download links over 3g, yes they can get corrupted.
2 New videos added!! Hope you like them everyone
Another video added! Let me know what you think!
so i tried to flash [ROM][8 FEB]COREDROID SENSATION XE & 4G v4.0 [ICS][SENSE 3.6][FAST|SMOOTH]...i got stuck in bootloop someone told me i needed hboot 1.27.0000 so i loaded it up still stuck in boot loops do i deleted the file on the root of the sd card so i can load into recovery i try to restore my stock rom that i backed up before root still bootloop on htc screens....
my bootloader screen looks like this
***locked*** (am i unrooted now)
Pyramid pvt ship s-off rl
hboot 1.27.0000
radio-11.21.3504.13_1
openadsp-v02.6.0.2226.00.0104
emmc-boot
jan 13 2012, 17:33:34
jaysun3000 said:
so i tried to flash [ROM][8 FEB]COREDROID SENSATION XE & 4G v4.0 [ICS][SENSE 3.6][FAST|SMOOTH]...i got stuck in bootloop someone told me i needed hboot 1.27.0000 so i loaded it up still stuck in boot loops do i deleted the file on the root of the sd card so i can load into recovery i try to restore my stock rom that i backed up before root still bootloop on htc screens....
my bootloader screen looks like this
***locked*** (am i unrooted now)
Pyramid pvt ship s-off rl
hboot 1.27.0000
radio-11.21.3504.13_1
openadsp-v02.6.0.2226.00.0104
emmc-boot
jan 13 2012, 17:33:34
Click to expand...
Click to collapse
ok so i when to hboot 1.17 (tmo) and then flashed my backup i made of my stock rom and now im back in...no more boot loops....but putting that 1.27.0000 hboot that had something to do with ICS i think made me loose root now the boot loader looks like this, btw i still have clockwork mod:
pyramid pvt eng s-off
hboot-1.7.2008 (pg5810000)
emmc-boot
may 13 2011, 21:04:03
was able to get root back had to try installing su-2.3.6.3-ef-signed.zip 3 times 3rd time worked
help!
I have experienced the exact same situation except I have no opinion for back-up in my recovery, so I am just stuck with the boot-loop no matter what I do.
Should I try and root it again?
delete your firmawre from the sd card
on the 1.27 it says locked on the hboot but it doesn't .
try to flash 3.24 firmware i know it works perfect have not tried yet 3.30 ....
you should delete the fw after flashing from root sd card .......
Okay, I will try that. and yes, I know to delete off sd card after flash.
squasha said:
I have experienced the exact same situation except I have no opinion for back-up in my recovery, so I am just stuck with the boot-loop no matter what I do.
Should I try and root it again?
Click to expand...
Click to collapse
Do you mean you don't have a custom recovery (clockwork or EXT4) installed?
If not you can also flash this either via bootloader in pg58img.zip format, or by installing from market if you achieve rom boot.
Sent from my Pyramid-T
Well it's weird, I had clockwork and 4ext at one point but now I have teamwin? I have no idea how this happened.
---------- Post added at 03:33 PM ---------- Previous post was at 03:16 PM ----------
So I tried flashing fw 3.24 on to my phone, it says it worked but it's still in boot loop. Then I tried flashing 3.30 and I am still in bootloop.
---------- Post added at 03:52 PM ---------- Previous post was at 03:33 PM ----------
stringer7 said:
Do you mean you don't have a custom recovery (clockwork or EXT4) installed?
If not you can also flash this either via bootloader in pg58img.zip format, or by installing from market if you achieve rom boot.
Sent from my Pyramid-T
Click to expand...
Click to collapse
I flashed ClockworkMod back on my phone, and tried to do a recovery of the last time I backed up before all this bootlooping occurred. But it's still bootlooping.
Sorry I am so impatient, I just haven't had a phone for two days now and I am anxious to fix this. I also don't have the money to replace this phone either.
What I ended up doing is loading a tmous ruu via bootloader and then flashing my stock backup I made before I rooted and the bootloops stopped. But like I said I had to reroot no issues till this day
If you are not supercid u must find your correct ruu...a list can be found under the friendly fireware thread in sensation general forums I believe
Sent from my HTC Sensation 4G using xda premium
I am in deep trouble, my xe has been in boot loop for over a week, I think I may now own a brick...
a brick because I was too ignorant and did not fully (still don't) understand what I was doing. I successfully s-off'd the device and thought I was flying, I then tried to flash something (and for the life of me, I can't find the thread again to say exactly what I flashed) and then....bootlooping like mad.
tried hard reset, wipe dalvic cache, flashing another rom from the sd = epic fail.
Any ideas? someone said I need a revovery image??? but I nver had one, cant go back to a backup I dont have..
???
steve.bakos said:
I am in deep trouble, my xe has been in boot loop for over a week, I think I may now own a brick...
a brick because I was too ignorant and did not fully (still don't) understand what I was doing. I successfully s-off'd the device and thought I was flying, I then tried to flash something (and for the life of me, I can't find the thread again to say exactly what I flashed) and then....bootlooping like mad.
tried hard reset, wipe dalvic cache, flashing another rom from the sd = epic fail.
Any ideas? someone said I need a revovery image??? but I nver had one, cant go back to a backup I dont have..
???
Click to expand...
Click to collapse
Always make a backup when you are flashing.
You could however try downloading one of Mike's (Android Revolution HD) firmware packages. I believe his 3.30 firmware package has custom unlocked HBOOT in it. Next unless you are SuperCID you'll need an RUU (rom) from HTC that supports your phone.
Put the firmware package on the root of your SD from you computer using a card reader. Flash the firmware. Power off and remove the firmware from SD card. Put the RUU on the SD card root.
See if you can boot into the recovery and flash this RUU. Best bet is something like ARHD, I've never had an issue with SuperCID and Mike's rom. Ideally if you get the phone functioning again. Think about SuperCIDing your phone. That way any rom that is supported by your firmware can get you out of trouble.
Another suggestion is that you've updated to rom that doesn't support your firmware. Try flashing to another firmware package, this may well fix your problem. Try one of the later ones (3.30) if that doesn't work. Track down a 3.12 which works with Gingerbread and ICS Roms.
jaysun3000 said:
What I ended up doing is loading a tmous ruu via bootloader and then flashing my stock backup I made before I rooted and the bootloops stopped. But like I said I had to reroot no issues till this day
If you are not supercid u must find your correct ruu...a list can be found under the friendly fireware thread in sensation general forums I believe
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Okay, I will try that but like I said before, I didn't backup my stock. But I will try loading a ruu.
---------- Post added at 10:14 PM ---------- Previous post was at 09:38 PM ----------
jaysun3000 said:
What I ended up doing is loading a tmous ruu via bootloader and then flashing my stock backup I made before I rooted and the bootloops stopped. But like I said I had to reroot no issues till this day
If you are not supercid u must find your correct ruu...a list can be found under the friendly fireware thread in sensation general forums I believe
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
did you have to reroot to get it to work?
because I just installed the correct firmware and attempted to flash a new rom and I am stil in bootloop.
@squash @jaysun - I would move straight to running ruu, this will return you to stock and you can start again.
Just run the ruu from your PC with device attached via USB and in boot loader.
If you are superCID you can run any ruu.
If not, match to your original software, baseband, carrier (if branded) and device.
http://forum.xda-developers.com/showthread.php?t=1074559
Sent from my Pyramid-T
stringer7 said:
@squash @jaysun - I would move straight to running ruu, this will return you to stock and you can start again.
Just run the ruu from your PC with device attached via USB and in boot loader.
If you are superCID you can run any ruu.
If not, match to your original software, baseband, carrier (if branded) and device.
http://forum.xda-developers.com/showthread.php?t=1074559
Sent from my Pyramid-T
Click to expand...
Click to collapse
I hate asking such noob questions, but I can't seem to match one to my phone.
when in fastboot, my phone says:
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.110
RADIO-11.21.3504.13_2
OpenADSP-v02.6.0.2226.00.0104
eMMC-boot
any idea which of the 53 is the right one? haha.
by the way, thank you so much for helping me out. like I know I am most liekly a pain in the butt, but I am a thankful one!
No worries at all.
So, if you have Sensation xe you need an ruu with "le" in the filename. If it's European, similar - choose European. If your phone was carrier specific e.g. Vodafone IT, pick that one.
That should narrow it to a few candidates.
Now you have to match to your original software and radio version if possible, do you know that?
Sent from my Pyramid-T
stringer7 said:
No worries at all.
So, if you have Sensation xe you need an ruu with "le" in the filename. If it's European, similar - choose European. If your phone was carrier specific e.g. Vodafone IT, pick that one.
That should narrow it to a few candidates.
Now you have to match to your original software and radio version if possible, do you know that?
Sent from my Pyramid-T
Click to expand...
Click to collapse
I have a T-mobile Sensation 4G, I don't know my original software and my radio version was the one I listed in the post above. (which I looked for but didn't see)
---------- Post added at 01:58 AM ---------- Previous post was at 01:00 AM ----------
stringer7 said:
No worries at all.
So, if you have Sensation xe you need an ruu with "le" in the filename. If it's European, similar - choose European. If your phone was carrier specific e.g. Vodafone IT, pick that one.
That should narrow it to a few candidates.
Now you have to match to your original software and radio version if possible, do you know that?
Sent from my Pyramid-T
Click to expand...
Click to collapse
Using the process of elimination, I have come to the conclusion that
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00
is the right one for my phone. I hope this works!
OK good. Worst case is it doesn't work.
In my experience the difficult bit is getting it off filestube! Good luck.
Sent from my Pyramid-T
stringer7 said:
OK good. Worst case is it doesn't work.
In my experience the difficult bit is getting it off filestube! Good luck.
Sent from my Pyramid-T
Click to expand...
Click to collapse
yeah I can tell! My solution was to search the file name and find another file sharing site that has it. I am downloading now. wish me luck!
---------- Post added at 02:47 AM ---------- Previous post was at 02:07 AM ----------
SUCCESS! Thank you all so much for your help. I have never been so excited to use my phone haha thank you thank you thank you!
Result!
Sent from my Pyramid-T
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 there guys,
Been trying to root my XL from Telstra (AUS) but some weird things are going on.
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
http://forum.xda-developers.com/showthread.php?t=1952038
Also, tried to root my phone using this thread below:
http://forum.xda-developers.com/showthread.php?t=1859478
So far, I have achieved to Installed S-OFF and CWM.
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Im uploading some of the current photos taken so you guys can have more information on S-OFF and CWM.
Thanks in advance.
Ps: One of the pictures was a Failed OTA from Telstra, is there a way to go back to and be able to install the OTA from Telstra instead of any custom ROM (In case we cant find what is causing the phone to block the supercid and the super SU)
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Desertum said:
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
Click to expand...
Click to collapse
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Desertum said:
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Click to expand...
Click to collapse
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Desertum said:
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Click to expand...
Click to collapse
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
redpoint73 said:
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
Click to expand...
Click to collapse
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Click to expand...
Click to collapse
No you've got it backwards. The boot.img goes in your fastboot folder on your pc, not on your phone.
You need to fastboot flash the boot.img from each ROM you want to flash. So, if you want to install CM10.2, you must extract the boot.img from the ROM zip and put it in your fastboot folder on your pc (not your sd card in your phone). Then you put the ROM zip on your phone, and install it in recovery (after wiping cache/dalvik cache/factory reset/system), then reboot to bootloader and flash the boot.img using fastboot. You must follow this process for each new ROM you want to flash.
Do a backup of your current setup in recovery before flashing anything new though.
Sent from my Evita
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
By the way, even though our phone doesn't have a physical sd slot, we refer to the stage as the sd card.
Sent from my Evita
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
Click to expand...
Click to collapse
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
Desertum said:
Hello there,
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Click to expand...
Click to collapse
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
Hi there,
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
I was trying to update the RUU, then restart the phone, went into S-off, then into recovery and Wipe factory/data reset, then install the CM10.2 build
Is something missing here?
Thanks.
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Also, what do you mean you "went into s-off"?
Sent from my Evita
Click to expand...
Click to collapse
Sent from my Evita
Desertum said:
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
Click to expand...
Click to collapse
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
Sent from my Evita
Click to expand...
Click to collapse
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
Click to expand...
Click to collapse
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Click to expand...
Click to collapse
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
John uallowt
redpoint73 said:
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
Click to expand...
Click to collapse
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Are you able to do some prompts in regards of what to do?
So far, IMAO I need to to this:
Flash the Correct RUU (Gotta find it first)
Use S-off to Install the Custom ROM (ROM is already copied to the phone's memory)
Install the new Custom ROM, however, not to sure about the GApps, which are google apps.
http://www.reddit.com/r/Android/comments/1kbeoh/gapps_20130813_for_android_43_and_20130812_for/
I guess that you need to copy them before you install the new ROM?
Thank you for your patience.
redpoint73 said:
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Click to expand...
Click to collapse
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Desertum said:
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Click to expand...
Click to collapse
As you've been told at least 3 times now, what you should do is READ READ READ.
None of this is hard to understand once you start diving into it and learning.
I'm personally not going to spoonfeed you any more steps (and suggest against doing it either), as shortcutting the learning process is only going to turn your phone into an expensive paperweight.
timmaaa said:
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Desertum said:
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Click to expand...
Click to collapse
We're getting there, here are the exact steps you need to take:
1) Read a lot.
2) Read some more.
3) Flash a superuser zip on your current stock ROM, or flash a rooted Sense ROM so you have root.
4) Get SuperCID.
5) Get s-off.
6) RUU to latest.
7) Flash whatever ROM you want.
Sent from my Evita
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
Desertum said:
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Click to expand...
Click to collapse
Just go to our Android Development section here and flash one of the new Sense 5 ROMs. They're already rooted.
Don't get information/software from anywhere except XDA by the way.
Sent from my Evita
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Good catch. I missed that.
To the OP: you don't need to RUU to install cm10.2 on your device as you already have the required hboot/firmware. Without s-off you will need to manually flash the boot.img using fastboot though.
Sent from my Evita