ultimate goal is to run the latest 4.2.2 rom from Magio without the reboots and data loss. So from what I understand I need to update the fw. Therfore I need S-Off and Super CID. Can I use the X-Factor Exploit to get Super CID while on 1.09 or do I need to get to 2.2. If so, how do I get to 2.2? I'm sure I have more questions but that's my first hurdle. Any assistance is appreciated and kudos will be given. Thanks
What's the status of the phone? Have you done anything to it or did you just get it and also what firmware are you on?
Sent from my HTC One XL using XDA Premium 4 mobile app
If that's under build number is 5.08.111 and I'm currently running magio rom 4.0.2.
No, he's asking for your bootloader details, can you post them please? Also, is your phone an at&t model?
Sent from my Evita
Yes it's at&t. I don't see something that says firmware but here is the info it does give me.
Evita PDT Ship S-On RL
Hboot 1.09
Radio 0.24p.32.09.06
Opendsp v34.1.0.45.1219
I thought that the fw version was usually found in the software version in settings>about but mine just says magio 4.0.2
djlobes said:
Yes it's at&t. I don't see something that says firmware but here is the info it does give me.
Evita PDT Ship S-On RL
Hboot 1.09
Radio 0.24p.32.09.06
Opendsp v34.1.0.45.1219
Hope that helps. Thanks
Click to expand...
Click to collapse
Did u flashed newer radio?....coz I use old radio + 1.09 hboot work fine for me ...no signal drop and no wifi issue.....with stock kernel from Magio ROM btw I used 1.89 radio ....0.18
Swyped from T3DRO1CS RedHoXence
It's standard procedure to give as much information as possible when asking a question here, that includes bootloader details. The info you gave wasn't the firmware by the way, that's just ROM information, when someone is asking for firmware version they're asking for bootloader details.
Anyway, you basically have two options:
You can leave your firmware as it is and flash the Beastmode kernel which should stop your signal loss and reboot problems. You're s-on but luckily you're on hboot 1.09 so you'll have no problems flashing kernels in recovery (anyone with s-on and hboot greater than 1.09 needs to flash the boot.img via fastboot for ROMs and kernels).
The other option is to get s-off and upgrade your firmware to the 2.15 version.
My suggestion would be to flash the Beastmode kernel first, if that doesn't work then move on to upgrading your firmware.
The fact that your phone is an at&t model almost certainly means you have SuperCID. If you want to check though you can give the following fastboot command:
Code:
fastboot oem readcid
If it comes back as 11111111 you have SuperCID, if it comes back as CWS__001 you don't.
Sent from my Evita
Thanks to both of you. I just flashed beastmode 3.5 and 1.85 radio. I'll see if that helps.
djlobes said:
Thanks to both of you. I just flashed beastmode 3.5 and 1.85 radio. I'll see if that helps.
Click to expand...
Click to collapse
I used old radio with stock kernel that came with the ROM.......different phone different place make it different.....u can try flashing beastmode kernel like timmaaa said if doesn't work
Swyped from T3DRO1CS RedHoXence
The radio alone probably won't fix signal drops. There are some lucky people that it works for though.
Sent from my Evita
djlobes said:
Can I use the X-Factor Exploit to get Super CID while on 1.09 or do I need to get to 2.2. If so, how do I get to 2.2?
Click to expand...
Click to collapse
I think you are confusing build numbers and hboot versions. For the AT&T version:
Build 1.73 and 1.85 = hboot 1.09
Build 2.20 = hboot 1.14
Build 3.18 = hboot 2.14
I believe the facepalm s-off should work with any hboot. Really getting SuperCID is the main hurdle (seems to be most problematic). S-off is very easy after that.
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
ted77usa said:
Did u flashed newer radio?....coz I use old radio + 1.09 hboot work fine for me ...no signal drop and no wifi issue.....with stock kernel from Magio ROM btw I used 1.89 radio
Click to expand...
Click to collapse
Did you ever have signal drops? I don't think everyone necessarily had signal drops with Sense 5. And if you did, I wouldn't think flashing an older radio would fix it (as timmaaa suggests).
redpoint73 said:
I think you are confusing build numbers and hboot versions. For the AT&T version:
Build 1.73 and 1.85 = hboot 1.09
Build 2.20 = hboot 1.14
Build 3.18 = hboot 2.14
I believe the facepalm s-off should work with any hboot. Really getting SuperCID is the main hurdle (seems to be most problematic). S-off is very easy after that.
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
Did you ever have signal drops? I don't think everyone necessarily had signal drops with Sense 5. And if you did, I wouldn't think flashing an older radio would fix it (as timmaaa suggests).
Click to expand...
Click to collapse
I still used 1.89 radio+1.09 hboot....work fine same as before.....plus now i'm using beastmode v2 and is ok too .... I think radio work better with build release.....for example ATT 1.85/1.82 radio with 1.85/1.82 build ....1.89 telstra radio with telstra build 1.89 or maybe sense 5 good with 5.08 radio with 5.08 Germany build( I will try this later on ) to match radio+ril on build version
Swyped From BlueICESense_HoXatt
ted77usa said:
I still used 1.89 radio+1.09 hboot....work fine same as before.....plus now i'm using beastmode v2 and is ok too .... I think radio work better with build release.....for example ATT 1.85/1.82 radio with 1.85/1.82 build ....1.89 telstra radio with telstra build 1.89 or maybe sense 5 good with 5.08 radio with 5.08 Germany build( I will try this later on ) to match radio+ril on build version
Click to expand...
Click to collapse
You seem to be contradicting yourself, so I'm not quite sure what you are trying to say.
The 1.31 baseband that came with 5.08 will work best for most people, since the signal drop issue seems to be caused by older radios being incompatible with the Sense 5 power save feature. And yes, using the radio and RIL that is intended for the ROM is often (but not always) the best option. Although some people have complained about power reception with the 1.31 radio, and better reception by flashing an older radio (as always, the "best" radio is very location specific, and no single radio works best for everyone).
Its still not clear from what you are saying whether you actually suffered the signal drop issue, or not. But it seems like you are saying you never had the issue to begin with. Not everyone suffers the signal drop issue. If you didn't suffer the issue on the older radio, then it may simply not apply to you (location or reception dependent, is my guess). And flashing Beastmode wouldn't make a difference either.
If you didn't have the issue to begin with, flashing a new radio or kernel isn't going to make a difference. If you are not sick in the first place, taking medicine (even the wrong one) isn't going to make a difference. You will still not feel sick.
redpoint73 said:
You seem to be contradicting yourself, so I'm not quite sure what you are trying to say.
The 1.31 baseband that came with 5.08 will work best for most people, since the signal drop issue seems to be caused by older radios being incompatible with the Sense 5 power save feature. And yes, using the radio and RIL that is intended for the ROM is often (but not always) the best option. Although some people have complained about power reception with the 1.31 radio, and better reception by flashing an older radio (as always, the "best" radio is very location specific, and no single radio works best for everyone).
Its still not clear from what you are saying whether you actually suffered the signal drop issue, or not. But it seems like you are saying you never had the issue to begin with. Not everyone suffers the signal drop issue. If you didn't suffer the issue on the older radio, then it may simply not apply to you (location or reception dependent, is my guess). And flashing Beastmode wouldn't make a difference either.
If you didn't have the issue to begin with, flashing a new radio or kernel isn't going to make a difference. If you are not sick in the first place, taking medicine (even the wrong one) isn't going to make a difference. You will still not feel sick.
Click to expand...
Click to collapse
Well, what I'm trying to say is that I don't have issue with signal and wifi on sense 5 Rom.... since I'm still using older radio ......I thought might help other to understand to try using older radio if they have issues.....but like u said it depend on their location it self......and they just need to try it them self.....
Swyped From BlueICESense_JBE
..... Do you play ingress?
Sent from my One X using Tapatalk 4
Related
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
Hello
can someone comment on the options with and progress for ROMS on base RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe base?
I see folks like me who have busted wifi or bricked outcomes and a lot fo snark thrown thier way. hard to keep it all straight.
Thanks in advance.
jimn235 said:
Hello
can someone comment on the options with and progress for ROMS on base RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe base?
I see folks like me who have busted wifi or bricked outcomes and a lot fo snark thrown thier way. hard to keep it all straight.
Thanks in advance.
Click to expand...
Click to collapse
Their Wifi breaks because they can't search for the fix. There are extra partitions that you have to flash in order to switch back and forth between all older bases and the newest Tmobile release.
T-Mobile Trickdroid and UnKnown_Retriution both work, and are both based on the latest T-Mobile release.
As for the partition, find them here http://forum.xda-developers.com/showpost.php?p=32170653&postcount=2668 I'm pretty sure you need a 1.09 hboot or lower to flash them.
Thanks. I don't think I had a choice of base I've had this 1 week. I'm hboot 1.14. I probably did the ota thoughtlessly in the first 5 minutes of owning this. Great phone but I like the nexus 7 base a little bettter for features. Looking forward to jellybean.
xxquicksh0txx said:
Their Wifi breaks because they can't search for the fix. There are extra partitions that you have to flash in order to switch back and forth between all older bases and the newest Tmobile release.
T-Mobile Trickdroid and UnKnown_Retriution both work, and are both based on the latest T-Mobile release.
As for the partition, find them here http://forum.xda-developers.com/showpost.php?p=32170653&postcount=2668 I'm pretty sure you need a 1.09 hboot or lower to flash them.
Click to expand...
Click to collapse
Im also on Hbot 14 and from what I keep reading there is no fix for our wifi issue since the patches ore for 9 and down. however, I'll try one of those roms. Thanks!
If you ran the T-Mobile update, which gives you HBOOT 1.14, your stuck with only running that same base roms for Wi-Fi to work. The only other option is to super cid and run RUU's 2.21 or 2.31 for it Wi-Fi to work on non 2.35 based roms.
HTC One™ S
fmedrano1977 said:
If you ran the T-Mobile update, which gives you HBOOT 1.14, your stuck with only running that same base roms for Wi-Fi to work. The only other option is to super cid and run RUU's 2.21 or 2.31 for it Wi-Fi to work on non 2.35 based roms.
HTC One™ S
Click to expand...
Click to collapse
So... To recap... 235 is current, the mod writers haven't caught up yet, and supercid involving 'dd' is an option for the impatient based on One X supercid.
dd is the quickest way to blow up a boot sector with a typo. I'm patient but at least this thread exists for the other unwary ota'rs
Might wanna try this if its true. I was reading the super cid thread but they didn't really touch bases on the subject. I wouldn't mind running strickly US sense roms but all the developement is on the Euro side and I need me some wifi so besides the eye candy its as good as it gets for us 1.14s. Hopefully you're right.
However, will super cid and new ruu save those files where the lower hboots have them? Also will I still have 1.14 ?
Seems weird to me that an OTA did that. I wonder if you could go into the TMo OTA edit some stuff and run the update and not get screwed. If only I knew more... I would dream less lol
Your stuck on HBOOT 1.14. Running RUU 2.21 or 2.31 will allow you to run any EU based rom with working Wi-Fi.
HTC One™ S
fmedrano1977 said:
Your stuck on HBOOT 1.14. Running RUU 2.21 or 2.31 will allow you to run any EU based rom with working Wi-Fi.
HTC One™ S
Click to expand...
Click to collapse
definitely want to try this
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
I am on stock T-Mobile rom:
Android version 4.0.4
HTC Sense version 4.1
Software number 2.35.531.7 710RD
HTC SDK API level 4.23
HTC Extension version HTCExtension_403_1_GA_20
Kernel version [email protected]#1
Baseband version 1.08ts.50.02.16_10.08e.50.04L
Build number 2.35.531.7 CL96068 release-keys
Browser verion WebKit/534.30
I want to flash a new radio since the version I have the signal keeps dropping and I cannot flash any radio. I am rooted, I go to TWRP and successfully flash a different radio but when I check the settings again it still say 1.08ts. I even tried an older RUU but it keeps failing. I do not want to flash another countries RUU since I'm afraid it will brick it.
Is there away to change just the radio?
There is a universal radio flasher in the dev section.
Sent from my HTC One S using xda app-developers app
bstylz911 said:
There is a universal radio flasher
Click to expand...
Click to collapse
..but you have to be on a low hboot (1.06 or 1.09) or s-off for that. On sense ROMs anyway.
so that means I would have to wait until a newer RUU comes out?
princeferoz said:
so that means I would have to wait until a newer RUU comes out?
Click to expand...
Click to collapse
I would S-Off the device and then flash the radio installer.
That way you can quickly and easily try a bunch of different radios.
what rom are you on
when you say ck settings, are you talking about Phone/Settings/About Phone
i would have to re-read the OPs on the cm and sense radio installer, but thought with them you could be on a higher hboot, since radio is put into system partition and bypasses htc restrictions. may be wrong--
i did some reading but no time to read all. you need to read them for yourself. talking about the cm and sense radio installer threads
my understanding is with cm rom and cm radio installer you can flash radio if above .09 hboot. it puts radio in system
with sense it puts it to phone. but there was a temporary installer that put it into system and could be used with higher hboots.
don't know if that installer is still available for dl from tecardo
some reading and a nandroid advised as i have no time to read both threads
princeferoz said:
so that means I would have to wait until a newer RUU comes out?
Click to expand...
Click to collapse
Just s off. Its not as hard as it looks.
I'm on hboot 1.14 and s offed. Glad I did
Sent from my HTC One S using xda app-developers app
Thanks for all your help. I was able to get S-Off and flashed a new radio but the radio still keeps fluctuating.
princeferoz said:
Thanks for all your help. I was able to get S-Off and flashed a new radio but the radio still keeps fluctuating.
Click to expand...
Click to collapse
am pretty sure you flashed the radio properly the first time but fail to check radio version on fastboot since it doesn't show correct radio on settings>"about phone" (known bug)
the radio flashed properly and it shows the correct radio in settings but the signal still fluctuates.
Let me start off by saying i have everything updated. Radio,Ruu,Root,Recovery,SuperCid,S-Off
On any non-sense based rom when i turn the phone on there is data. After i decide to connect to Wi-Fi or Turn off the data to conserve battery everything is fine. After I turn Wi-Fi off or Turn data back on It does not work and to use it I must restart the phone. This is driving me insane! I spent hours updating everything so i could install a new rom (Because i thought it was a problem with the rom) but even after that no luck! If anyone knows a way to fix this ridiculous problem please HELP!!!
Saying that you've "updating everything" is almost like saying nothing, updated to exactly? You need to provide exact details. Bootloader details, radio version, ROM version/build, kernel version/build.
Sent from my Evita
timmaaa said:
Saying that you've "updating everything" is almost like saying nothing, updated to exactly? You need to provide exact details. Bootloader details, radio version, ROM version/build, kernel version/build.
Sent from my Evita
Click to expand...
Click to collapse
Sorry noob here.
HTC ATT 3.18 (0.24p.32.09.06_10.130.32.34) Radio
3.18 RUU
SuperCid 11111111
Facepalm S-Off
AOKP Version: aokp_evita_jb-mr1_milestone-2
Kernel Version: 3.4.10-g8d6810dd
[email protected] #1
Sun Jul 21 19:30:37 CEST 2013
It was doing this also before I updated the Radio, Ruu, and had no s-off
Did you try a different Rom? Did you try it on sense after you ran the ruu? What twrp and hboot versions do you have?
Sent from my VENOMized HoxL
area51avenger said:
Did you try a different Rom? Did you try it on sense after you ran the ruu? What twrp and hboot versions do you have?
Click to expand...
Click to collapse
I did try others after the RUU update. It does not work on any non-sense based roms. It worked on ViperRom which is sense, but i don't like sense. Like i said I tried many things and it's driving me insane!
HBOOT - 2.14.0000
TWRP - v2.6.3.0
Try downgrading twrp to 2.6.0.0 and reflash aokp
Sent from my VENOMized HoxL
I'd try running the RUU again, and also using TWRP 2.6 instead of 2.6.3, I've seen bugs reported on that version.
Sent from my Evita
I found how to fix it. Go to Mobile Networks Settings- Access Point Names- Change From ATT to ATT LTE. Fixed