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
Related
Hi
Does anybody know where i can find One S (S4) odex stock roms for tmobile. Basically i can't get ota updates and i think my problem is that my current stock rom is deodex.
none of the develops in the One S community wants to make it.. dont know why....
the closest u get is the nandroid in the dev section.. thats what im running now...
Why not run a RUU from the Shipped ROMs thread in development section
I'd like it too actually. I tried flashing stock recovery and relocking my bootloader, but out still said tampered and still couldn't flash an ruu... I'm hoping getting all stock could help with that.
There are no RUU's for tmobile uk sadly, so i need to super cid my phone to get the international version. Also i dont know how to super cid
I found another version of the RUU for TMOUS so I'll try that in the near future and see what happens.
Because the cramp just won't go away!
Does anybody have a stock nandroid for tmobile UK?
Sent from my HTC One S using xda app-developers app
If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!
mylegiscramped said:
If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!
Click to expand...
Click to collapse
I'm just curious are you from UK or USA. I supercid my phone yesterday and tried flashing three different ruu's but none of them worked. But then again my bootloader is unlocked so I'm not sure whether locking it will help.
Sent from my HTC One S using xda app-developers app
I'm from us, but please don't hate me i didn't decide to be birthed here
I'm assuming your a tmobile UK user due to your post. I'm not really familiar as to what to do with your situation as I've never dealt with UK RUU Issues. I would assume you probably can't use any of the RUUs from anywhere else. You would think T-Mobile would have an international one out. I would probably not risk damaging your device using other carriers unless someone tells you it works. I don't see why trying a tmous RUU would harm you though. There are two versions of it out a 1.54 and 1.84 I believe. I don't know what effect itll have on your phone though so don't blame me if it bricks if you try.
Ive got a huge problem I supercid my phone last night and after that I couldn't call or text anyone as well as recieve. I even unsupercid my phone and back to the original HTC__001 cid. So can anyone give me a solution. Btw I relocked my bootloader and ran the European RUU and it worked
Sent from my HTC One S using xda app-developers app
Maybe try to run the RUU again? Or a factory reset.
_______________________________________
Because the cramp just won't go away!
No no this happened due to me trying to super cid. I just did the ruu right now. I think I need to flash a radio but not sure how to
Sent from my HTC One S using xda app-developers app
That's possible I suppose. Here is how.
After flashing your device properly, start it up and let everything run a few minutes so the ROM can get settled in, I assume you've done that already.
Next you download the radio image you need, I'm not sure which it is I don't know what your running.
Then reboot to fast boot.
Enter
Code:
fastboot flash radio radio.IMG
Then reboot your phone with
Code:
fastboot reboot
Or you can do it through a menu on the device.
Then you should have your radio set.
Someone please correct if anything is wrong.
_______________________________________
Because the cramp just won't go away!
My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app
I'm not sure which radio you need. This is what I have.
HBOOT-1.14.004
RADIO-1.08ts.50.02.16
I googled quick, but haven't been able to find anything as of yet. Maybe check the wiki?
lonegunman0 said:
My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Your not flashing any radio with that HBOOT.
HTC One S
Flash radio
fmedrano1977 said:
Your not flashing any radio with that HBOOT.
HTC One S
Click to expand...
Click to collapse
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will
lonegunman0 said:
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will
Click to expand...
Click to collapse
He is saying you CAN'T flash radios, new, old, it doesn't matter. Your hboot does not support it. You are SOL.
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
1.06, flash the new radio seperately once your on 1.06.
usaff22 said:
1.06, flash the new radio seperately once your on 1.06.
Click to expand...
Click to collapse
Thanks for the info, which radio is that though?
<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions
alexskin said:
<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions
Click to expand...
Click to collapse
Alright I'll try it out. thanks!
byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043
Kamilr97 said:
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
Thanks,
Yikes! Now I see why a lot of people don't even attempt this
I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix
fjjfrank said:
I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix
Click to expand...
Click to collapse
I downgraded from 1.14 to 1.06 too, installed 1.53 RUU and then experienced wifi issues on Trickdroid 8.
I had to flash "extra partitions" to make it work. Seems to be some partitions required for wifi to work on versions based on latest sense kernels.
I flashed extra partitions 2.35 and wifi did not work. Then I flashed 1.84 and wifi on Trickdroid 8 would connect, but from time to time (very frequently every 15 seconds on average) disconnect and reconnect, randomly (was annoying and killing my battery). I moved to trickdroid 7 TMOUS version and wifi works perfectly, never disconnects.
(My phone was from T-Mobile)
Here are the links, taken from this post: http://forum.xda-developers.com/showthread.php?t=1657831&page=271
2.35 Extra Partitions
https://www.dropbox.com/s/7gtuvbynr3...rtitions.zip?m
1.84 Extra Partitions
https://www.dropbox.com/s/mmjcqisgoo...rtitions.zip?m
NOTE: On CM rom I never had issues even without flashing extra partitions, and even when I was on hboot 1.14.
Hope this helps,
Regards,
Diego
---------- Post added at 07:57 PM ---------- Previous post was at 07:51 PM ----------
And regarding the topic from this post, hboot is like the BIOS of the phone. You gain nothing from upgrading it, only gain restrictions from 1.13 and above. So as far as I read it is better to stick to 1.06
Regarding the procedure to downgrade, for the one that asked, it can make you panic on the step when you upload hboot 1.06. For me, it failed 3 times, and I had to go to work after third time with a "bricked" phone -.-
But I came back, tried from my laptop instead of my PC, and worked on the first attemp!. Seemed to be my PC USB not working properly or not being fast enough/not having enough power, who knows.
It seems scary but is fairly straight through, the procedure is perfectly detailed. Did it from an Ubuntu 12.04 live image.
Regards,
Diego
HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.
byliu88 said:
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.
Click to expand...
Click to collapse
oke thanks
i am from the netherlands and i have got a unbranded one s
witch hboot can i install without updating my bootloader
So after having Jellybean updated on my Telstra One XL I decided to much around with recoveries and custom ROMs to see if I could get them running. I realised that this was going to cause issues, but I was fine with mucking around with it.
I unlocked the phone and got a recovery installed and of course the touchscreen didn't work in recovery. So I mucked around with it and managed to get ROMs installed via manual boot.img flashing and manual ROM flashing via:
Code:
adb shell recovery --update_package=/sdcard/rom.zip
My test was with CM10 and it got up and running. The only issue is that touchscreen doesn't work. Which made any progression through the setup phase impossible
If anyone has any clues as to how to get this up and going again I'm all ears.
I tried to use JET to roll back the HBOOT and try to roll back the firmware, but the RUUs wanted none of it.
Thanks in advance,
Anthony
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
twistedddx said:
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
Click to expand...
Click to collapse
No I didn't, must've missed that. Thanks, I will try that.
Didn't work with any RUU either.
EDIT: Got the RUU installed, thank you very much. I was an idiot and forgot to relock my bootloader again
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
DESERT.TECH said:
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Not really relevant.
twistedddx said:
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
Click to expand...
Click to collapse
RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Tried the unbricking process, but it won't work. Going to get it replaced now.
Antonioffaxii said:
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Click to expand...
Click to collapse
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
twistedddx said:
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
Click to expand...
Click to collapse
I couldn't restore it in anyway, I had work so I took it with me and had it replaced.
Now I have one that works again!
Start telling them already installed the versions (RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2) and
(RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2) on my HTC One X AT&T.
This could by having the 'superCID' and re-locked.
My problem is now when I try to install the version (RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1) the application
gives me the error (HTC Error 31) but this not happened to me with previous versions.
NOTE: I now that the HTC Error 31 is because it is the device's original RUU.
Anyone know how to fix this?
I read somewhere that there is a problem with the 'superCID'. They know about this?
Or any solution using the (OTA_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1)?
NOTE: I also know that there is a type of encryption in ROM.zip for JB
I appreciate the help
Thanks
I create a new thread because I can not find where this the same case with some solution for this.
Unless we have soff we can only flash our carriers ruu's so you're stuck on ics unless you root
a box of kittens said:
Unless we have soff we can only flash our carriers ruu's so you're stuck on ics unless you root
Click to expand...
Click to collapse
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.
Re: [Q] Someone knows how to install the (RUU 3.17.707.2 JB) in the HTC One X AT&T
twistedddx said:
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.
Click to expand...
Click to collapse
I could swear turge fixed one and posted it. But from what I understand ruu's don't like supercid and may brick your phone.
*edit* never mind I'm dumb that's just a flashable zip not an ruu.
Sent from my One X using xda app-developers app
twistedddx said:
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.
Click to expand...
Click to collapse
And how it could change my CID (superCID 11111111) to HTC__044?
Or any solution using the OTA RUU.
Thanks :good:
twistedddx said:
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.
Click to expand...
Click to collapse
I see...so everything would go smoothly if the cid was that?
Re: [Q] Someone knows how to install the (RUU 3.17.707.2 JB) in the HTC One X AT&T
a box of kittens said:
I see...so everything would go smoothly if the cid was that?
Click to expand...
Click to collapse
So long as bootloader was locked, hboot is not newer than ruu to be flashed, last ota or ruu Rom version is not newer than ruu to be flashed and that it is not 3.17.707.1 ruu as it is broken.
But yes cid is what blocks ruu from other regions, it is the reason why supercid is desired.
Supercid doesn't brick phones, or at least not in 99% of cases. Those that bricked with supercid need to be pay more attention to what they really did, as I bet the issue will be found somewhere else, Eg in their method, other mods, hardware failure, etc.
Supercid is done so your phone has an "all" region so you can flash a ruu or ota from anywhere. Those claiming it causes bricks are going against what Htc created supercid for.
---------- Post added at 11:37 PM ---------- Previous post was at 11:34 PM ----------
exad said:
I could swear turge fixed one and posted it.
Click to expand...
Click to collapse
Turge can't fix a ruu, he does not have access to the tools required. And if he did he definately would not be using them to fix a ruu for the public.
Turge used ota updates for the base of his viperxl and also posted a stock system image of an ota base also.
I'd like to return to stock JB for moonshine S-OFF, and the software version that was last installed before I rooted was 3.14.531.17 710RD. This was the small update that was released to fix the battery drain after the release of JB for the One S. It was released right after 3.14.531.11, which I see an RUU for. My question is: Can I use the 3.14.531.11 RUU (detailed RUU name: RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2) even though I upgraded, before rooting and installing CM10.1, to 3.14.531.17? All other relevant information matches.
Thanks.
EDIT: Nevermind, stupid question. Of course that number denotes the software version so I'll be fine for S-OFF as long as I don't OTA upgrade to 3.14.531.17.
can someone confirm this? been trying to find info on this, having no luck.
I don't know if you need them to match but I do know here is the link for the last updates RUU
noknife said:
can someone confirm this? been trying to find info on this, having no luck.
Click to expand...
Click to collapse
Yes, this is correct. Use that RUU.exe to return to stock, and it will also work when using Moonshine.
That RUU.exe is for U.S. tmobile users.
tivofool said:
Yes, this is correct. Use that RUU.exe to return to stock, and it will also work when using Moonshine.
That RUU.exe is for U.S. tmobile users.
Click to expand...
Click to collapse
Thanks for the info. Would have responded sooner but didn't notice your response till now. still quite knew to android (haven't even owned mine a month) , so have been reading A LOT.. You knew exactly what I was trying to achieve there. Success!! Got s-off, and supercid. Running MaximusHD 10.0.0 right now. One more quick question though if you don't mind. Can there be issues switching between mods, as long as I don't go ruu obviously. Thanks for your time.
noknife said:
snipped.... Can there be issues switching between mods, as long as I don't go ruu obviously. Thanks for your time.
Click to expand...
Click to collapse
Mods? I don't use any mods on Maximus, so I don't know about that.
If you mean switching between ROMs when you have Maximus installed, then yes, you need to downgrade your firmware to try any other rom after Maximus is installed.
tivofool said:
Mods? I don't use any mods on Maximus, so I don't know about that.
If you mean switching between ROMs when you have Maximus installed, then yes, you need to downgrade your firmware to try any other rom after Maximus is installed.
Click to expand...
Click to collapse
ha, yeah meant roms, still getting used to the auto correct. not only first android, first smart phone.ha. that's the answer i was looking for. thanks for reading between my clumsiness, think i'll leave her alone for now then. it's easy enough so far, but all it takes is once. thanks for the info