Related
Here the latest shipped RUU for SuperSonic
http://www.filefactory.com/file/cfe....15.00.0808_NV_2.15_release_220182_signed.exe
Enjoy!
As always, thanks
Sent from my PC36100 using xda premium
Nice! But just curious. How do you use this? Of all the things I know about rooting and whatnot this is the only thing I'm stumped on...
Sent from my PC36100 using XDA App
You run it on your pc. It returns your phone to stock
We're comin from a pure power source.
Football said:
Here the latest shipped RUU for SuperSonic
http://www.filefactory.com/file/cfe....15.00.0808_NV_2.15_release_220182_signed.exe
Enjoy!
Click to expand...
Click to collapse
Thank you Sir!
as always, thank you!!
exactly what I needed for my newly purchased evo 4G, big thanks!
I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?
Drakhar said:
I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?
Click to expand...
Click to collapse
That's what I am wondering. Every other RUU he uploaded were zip files that you just flashed through HBoot & this one is a exe file. How do you use this? This is a non-Rooted Rom right?
Drakhar said:
I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?
Click to expand...
Click to collapse
Don't know exactly where you coming from and going to, 4.53 to 4.54? But something and that has been working and continued for me.
This ruu.exe is ran from the PC through usb debugging enabled, and having the correct drivers installed, I am on xp so I ran latest drivers maually, for higher o/s ver. its going to regonized the android and try to install autmatically....press stop/cancel you will need to configure it manually to have it install the correct drivers.
assuming you done this already, then enable settings>applic>develop>usb-deb and device powered on to home screen, from pc just double click the .exe and go through simple menu's and continue to process.
good luck and hope it helps..
latest Drivers
RUU4.54
Thank football!!!!
Anybody checked if stagefright libs were updated by HTC?
I have a custom slash screen on my EVO, will this put back on the oem Sprint one back on it? I just bought a E3D and am selling my EVO.
doeboy1984 said:
I have a custom slash screen on my EVO, will this put back on the oem Sprint one back on it? I just bought a E3D and am selling my EVO.
Click to expand...
Click to collapse
it should!!!
brad
my dilemma is that I have a rooted evo running a synergy rom on Hboot .79 and Radio 1.39
thing is that the s status is S-ON on this particular phone and unrevoked forever does not work on that radio version.
I've tried to upgrade the radio through clockwork recovery with the prepackaged zip yet when I reboot the phone still shows the old radio version.
I've tried installing an RUU from the PC but they all error out.
I'm looking for an RUU packaged in an install-able .zip that includes updated Radios Kernels Hboot and ROM in one. Is that even possible so i can fix this phone and get it some updated radios?!
brad560 said:
it should!!!
Click to expand...
Click to collapse
So I know you say it "should" but I don't want to RUU and then still have my batman logo as my splash screen, that would suck. I would ave to re-root it to try and find a splash .img, but I guess I will try it out and see if it works.
skunkd said:
brad
my dilemma is that I have a rooted evo running a synergy rom on Hboot .79 and Radio 1.39
thing is that the s status is S-ON on this particular phone and unrevoked forever does not work on that radio version.
I've tried to upgrade the radio through clockwork recovery with the prepackaged zip yet when I reboot the phone still shows the old radio version.
I've tried installing an RUU from the PC but they all error out.
I'm looking for an RUU packaged in an install-able .zip that includes updated Radios Kernels Hboot and ROM in one. Is that even possible so i can fix this phone and get it some updated radios?!
Click to expand...
Click to collapse
just saw you replied to me, sorry for the lateness. first of all, i would try aman ra for recovery, as many users have had problems with clockwork. as far as the ruu, how can you be s-on and still be rooted?
brad560 said:
just saw you replied to me, sorry for the lateness. first of all, i would try aman ra for recovery, as many users have had problems with clockwork. as far as the ruu, how can you be s-on and still be rooted?
Click to expand...
Click to collapse
I have the opposite issue. I have S-OFF (Revolutionary) but on stock unrooted (brought the phone to Sprint for a broken power button, and they ended up not fixing it, but flashed 4.53 stock rooted).
How the hell do I get this ROM rooted since Revolutionary doesn't want to root it because the bootloader is unlocked and I can't go to recovery because once I'm on the HTC white background fastboot screen, the volume button are locked and my power button is dead anyway...
I'm trying this Ruu .exe hoping it will give me S-ON but I'm doubtful it will happen...
EDIT: Just as I thought, I'm now on stock rooted 4.54 with S-OFF. And no power button
doeboy1984 said:
So I know you say it "should" but I don't want to RUU and then still have my batman logo as my splash screen, that would suck. I would ave to re-root it to try and find a splash .img, but I guess I will try it out and see if it works.
Click to expand...
Click to collapse
They will always update the splash screen, it helps to identify the firmware and rom versions at a glance. During install the setup program will create a temp folder with PC36IMG.zip or update.zip look in this zip file and you should see a splash.img file or something like that (sorry haven't looked HTC updates since my Hero Days).
Sent from my PC36100 using xda premium
Any way to get this to be able to install through the bootloader because my usb port is broken on my phone and it won't stay connected to the computer and I need to get Unrooted, s-off, return to stock, stock hboot because I need to take my phone to Sprint to get phone replaced/fixed. Thanks.
Sent from my PC36100 using xda premium
Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.
antny said:
Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.
Click to expand...
Click to collapse
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?
dc211 said:
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?
Click to expand...
Click to collapse
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.
I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S
dc211 said:
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.
Click to expand...
Click to collapse
I've thanked Football and gone to the link you provided but I don't get the whole Pt.1,2 and 3 thing. What am I supposed to do with that?
Edit: All good, just got it from the Dropbox link.... T-Mobile and Easy Tether don't mix.
fmedrano1977 said:
I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S
Click to expand...
Click to collapse
I don't really care about wifi calling, cool feature but I hardly use it. Is it 4.0.4 and Sense 4.1 though? It wouldnt stop me from using it if it wasn't but I'm just curious haha.
4.0.4 and Sense 4.0
HTC One S
fmedrano1977 said:
4.0.4 and Sense 4.0
HTC One S
Click to expand...
Click to collapse
Cool Cool Cool thanks
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Glad it worked out for you.
antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S
Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?
DoogleDood said:
Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?
Click to expand...
Click to collapse
What are you trying to do?
HTC One S
Nevermind I got it! I wasn't sure if the 3 "parts" of the EU RUU needed to be combined or... what. But upon extracting I found the full file.
fmedrano1977 said:
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S
Click to expand...
Click to collapse
Why thank you sir.
antny said:
Why thank you sir.
Click to expand...
Click to collapse
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!
johnyguy said:
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!
Click to expand...
Click to collapse
I'm honestly not to sure on how to fix this. I've searched it before I went back to stock (going back to stock is a definite fix) and couldn't find much on it. I'm sure something has developed from it by now though. Actually :: navigates to another tab:: http://forum.xda-developers.com/showthread.php?t=1900644 if it's compatible with your ROM, this kernel claims to have a fix for wifi and sound (I don't know what the sound issue is all about) but try that, it might work. But most importantly search, read, search and read some more, especially since you're new to this, I've rooted many phones and I still had problems with the One S. Good luck!
Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402
sylvestk said:
Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402
Click to expand...
Click to collapse
That release gives you the no data when screen is off issue.
HTC One S
Sorry for the repeating post, I know there are many threads out there regarding this problem but I had problems after following those.
I used TWRP and installed "cos-0.7-20130427-NIGHTLY-evita", bootloader is unlocked (via HTCDev) and rooted. But my phone is still returning "ROGER001" when I search for supercid and s-on, hboot 2.14.
I followed this post (to turn s-off) "http://forum.xda-developers.com/showthread.php?t=2155071", but after step 5, I got FAILED (remote: 99 unknown fail) and for the touchscreen firmware (downgrade), I need s-off.
Can anyone help step by step or should I revert back to stock ROM? If I have no other option but reverting back, is there any thread I can follow?
Thanks in advance!
You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)
Wubbz said:
You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)
Click to expand...
Click to collapse
I saw that post to downgrade the touchscreen firmware, but pre-req for that is to turn s-off, can you please guide me how you did the s-off.
All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off
Wubbz said:
All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off
Click to expand...
Click to collapse
Any thread with all the steps?
right here
Wubbz said:
right here
Click to expand...
Click to collapse
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error
jashang87 said:
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error
Click to expand...
Click to collapse
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.
exad said:
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.
Click to expand...
Click to collapse
tried that 5-6 times, still no luck. Is it windows 8 that is causing the problem or how do I check if my phone has SuperCID or not? (it returns "ROGER001" in supercid)
Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app
exad said:
Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"
jashang87 said:
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"
Click to expand...
Click to collapse
From where, I can get RUU for rogers htc one x (hboot-2.14) ?
jashang87 said:
From where, I can get RUU for rogers htc one x (hboot-2.14) ?
Click to expand...
Click to collapse
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.
exad said:
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.
Click to expand...
Click to collapse
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.
jashang87 said:
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.
Click to expand...
Click to collapse
All you need to do is change your cid in fastboot
Sent from my HTC One X using Xparent Green Tapatalk 2
False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app
exad said:
False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Well I tried everything, supercid in fastboot, changing cid manually, tried htc one x all-in-one toolkit. But nothing worked for me, still if there is something else I can try, I will try that.
Downgrade your hboot with jet tool then hex edit your cid.
Sent from my One X using xda app-developers app
I've flashed probably hundreds of roms to my device and I'm wondering if it can cause issues with wifi performance and performance in general. Ive noticed my wifi acting weird lately and have seen a couple posts about running an ruu to fix problems like this.
Im on hboot 1.09, bootloader unlocked, s-off, currently on the sense 5 2.5 ROM.
Am I all good if I do an ruu with the 3.17 ruu posted in the one xl resources thread? Is this the best one to flash if I decide to? Will this upgrade my hboot? If so, does that improve performance/fix issues at all?
JBLogic said:
I've flashed probably hundreds of roms to my device and I'm wondering if it can cause issues with wifi performance and performance in general. Ive noticed my wifi acting weird lately and have seen a couple posts about running an ruu to fix problems like this.
Im on hboot 1.09, bootloader unlocked, s-off, currently on the sense 5 2.5 ROM.
Am I all good if I do an ruu with the 3.17 ruu posted in the one xl resources thread? Is this the best one to flash if I decide to? Will this upgrade my hboot? If so, does that improve performance/fix issues at all?
Click to expand...
Click to collapse
an RUU can clean things up. If you've dirty flashed a lot, then things can get a bit "dirty" and not work the way they should.
I personally run and RUU about every 3-4 months just because I'm anal like that and I like my phone to work the way an OCD person on speed would(perfect and fast as hell).
Since you're and hboot 1.09, I would run the 1.85 RUU. Link can be found in Redpoint's resource thread. But since you're s-off, it essentially wouldn't matter which RUU you ran.
Myrder said:
an RUU can clean things up. If you've dirty flashed a lot, then things can get a bit "dirty" and not work the way they should.
I personally run and RUU about every 3-4 months just because I'm anal like that and I like my phone to work the way an OCD person on speed would(perfect and fast as hell).
Since you're and hboot 1.09, I would run the 1.85 RUU. Link can be found in Redpoint's resource thread. But since you're s-off, it essentially wouldn't matter which RUU you ran.
Click to expand...
Click to collapse
Cool, thanks for the info. Would running a newer ruu do anything beneficial or does it not matter if I plan on using a custom ROM?
Becareful, from my knowledge, you are on a rootable firmware(hboot) if you RUU something like, 4.1.1 you could possibly screw up any chances for root.
Oh, and to do RUU you might need bootloader relocked.
Sent from my HTC One X using xda app-developers app
i4GS said:
Becareful, from my knowledge, you are on a rootable firmware(hboot) if you RUU something like, 4.1.1 you could possibly screw up any chances for root.
Oh, and to do RUU you might need bootloader relocked.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
All firmwares are currently rootable.
He mentioned hes soff no need to relock bootloader.
Sent from my Sony Tablet S using xda app-developers app
hmmm not sure what the issue is now, I tried to run the 1.85 ruu and the 2.20 ruu and neither worked.
I tried on cleanrom 6.5, viper 3.27 and sense 5 2.5. When i run the RUU exe's i received error 170 (usb connection error) the first couple tries, now i keep receiving error 120 (low main battery, less than 30%) which is incorrect, i am fully charged.
any help?
Try a combination of different usb ports and cables.
Sent from my Evita using XDA Premium
Myrder said:
an RUU can clean things up. If you've dirty flashed a lot, then things can get a bit "dirty" and not work the way they should.
I personally run and RUU about every 3-4 months just because I'm anal like that and I like my phone to work the way an OCD person on speed would(perfect and fast as hell).
Since you're and hboot 1.09, I would run the 1.85 RUU. Link can be found in Redpoint's resource thread. But since you're s-off, it essentially wouldn't matter which RUU you ran.
Click to expand...
Click to collapse
I ruu on the 1st of every month and format SD lol. Maybe im ocd too but I like to clean it out and have performance without anything holding it back
Sent from my One X using Tapatalk 2
I still cant get the RUU to work, i keep getting errors 120 and and 170. Tried all 6 USB ports on my PC with two different cables.
Is there a different way I can do the RUU? Flash through fastboot or something?
JBLogic said:
I still cant get the RUU to work, i keep getting errors 120 and and 170. Tried all 6 USB ports on my PC with two different cables.
Is there a different way I can do the RUU? Flash through fastboot or something?
Click to expand...
Click to collapse
Try RUUing while in bootloader/fastboot.
exad said:
Try RUUing while in bootloader/fastboot.
Click to expand...
Click to collapse
THANK YOU! Worked perfect first try.
JBLogic said:
I still cant get the RUU to work, i keep getting errors 120 and and 170. Tried all 6 USB ports on my PC with two different cables.
Is there a different way I can do the RUU? Flash through fastboot or something?
Click to expand...
Click to collapse
Plug the phone while in fastboot mode, and in cmd/terminal rule in:
Fastboot bootRUU or fastboot boot RUU
this will put it in HTC RUU download mode.
try it then.
i4GS said:
Plug the phone while in fastboot mode, and in cmd/terminal rule in:
Fastboot bootRUU or fastboot boot RUU
this will put it in HTC RUU download mode.
try it then.
Click to expand...
Click to collapse
He already got it lol
Sent from my HTC One XL using xda premium
Lol and the command is fastboot oem rebootRUU
Sent from my HTC One X using xda app-developers app
exad said:
Lol and the command is fastboot oem rebootRUU
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Lol sorry for me trying to help !
Then again i never had problems with flashing/rooting i only wonder.
It's great he got it fixed anyways.
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
Nope, you'll probably brick doing that.
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
RollTribe said:
Nope, you'll probably brick doing that.
Click to expand...
Click to collapse
Yeah i figured it was a long shot, glad i asked first lol. Thanks dude!
pside15 said:
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
Click to expand...
Click to collapse
Oh I'm sure it's not to bad, but I have no idea how to use fastboot or adb (I've lucked by without having to use either, at least to my knowledge). Plus I don't readily have a windows PC, I just want make sure I know what I'm doing before I even attempt it. I've been looking over gunnyman's adb for noobs (http://forum.xda-developers.com/showthread.php?t=1754018), I'll give it a shot sometime next week when I've worked up the courage. Thanks for the advice!
pside15 said:
There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm.
Click to expand...
Click to collapse
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
exad said:
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
Click to expand...
Click to collapse
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
pside15 said:
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
exad said:
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
Click to expand...
Click to collapse
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
pside15 said:
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
Click to expand...
Click to collapse
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
31ken31 said:
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm not saying it's that simple and yes, I agree about following the steps. That's why I said I wouldn't even recommend trying the newer ROMs without updating first. I have seen it work though. That's all I'm saying. Maybe those users were ignorant on exactly what they did but I'm just going on what I've read and responded to.
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
exad said:
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Go to my profile and look at my quoted posts or just go back a bit in the Carbon thread. You will see where I quoted someone who was s-on and on the 1.14 hboot that flashed one of the 3.4 nightlies successfully. He was wondering if his phone was going to mess up now. That's the only specific one I remember off the top of my head but I know I've seen others as well. Like I said I'm just going by what I read. They could be completely wrong, lying, or just ignorant noobs. I live on these forums as well and have absolutely no reason to make something like this up.
Sent from my One X using Tapatalk 2