[Q] Help !!!HTC One SV VERY LAG - HTC One SV

Problems test in these rom:
4.1.2 HTC sense 4+ (Lag and Hang)
4.2.2 HTC Sense 5 (Lag and Hang)
4.1.2 HtC SENSE (Lag and Hang ONLY IF MOBILE DATA IS ON)
Phone Info:
HTC One SV - K2_UL
PL80150 - ASIA version
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.00.0000
RADIO-1.14.40a.00.01_2
OpenDSP-v9.2.02.68.1214
eMMC-boot
Feb 19 2013,20:16:40:20038
PLS HELP!!!!!!!!

kcreeps said:
Problems: Lags and Hang in 4.1.2 HtC SENSE (when mobile data is on) 4.1.2 HTC sense 4+and 4.2.2 HTC Sense 5
Click to expand...
Click to collapse
Can you be a little more specific?
Does it ONLY lag when data is on?
And stops lagging when data is turned off?
When does it start to lag
How long has the phone been booted
Home screen lag?
What app or apps lag?
You give us more details, and we will give you more help.

Yes
russellvone said:
Can you be a little more specific?
Does it ONLY lag when data is on?
And stops lagging when data is turned off?
When does it start to lag
How long has the phone been booted
Home screen lag?
What app or apps lag?
You give us more details, and we will give you more help.
Click to expand...
Click to collapse
in 4.1.2 HTC Sense 4 it runs smooth but when turning mobile data it lags. in other versions of JB it lags even mobile data is not on. i just flash firmware from here http://forum.xda-developers.com/showthread.php?t=2516661

old.splatterhand said:
@Bazdir
Some links for first post:
Your backup at androidfilehost:
http://www.androidfilehost.com/?fid=23212708291675772
Firmware.zip for k2ul at Dev-host: http://d-h.st/uwh
Click to expand...
Click to collapse
This is what you used?
---------- Post added at 12:48 AM ---------- Previous post was at 12:38 AM ----------
kcreeps said:
in 4.1.2 HTC Sense 4 it runs smooth but when turning mobile data it lags. in other versions of JB it lags even mobile data is not on. i just flash firmware from here http://forum.xda-developers.com/showthread.php?t=2516661
Click to expand...
Click to collapse
Alright, do you have a backup of your original 4.1.2 ROM?
Maybe compare your radio(baseband)
It might have been flashed to wrong one for your network if you flashed another carriers radio.

russellvone said:
This is what you used?
---------- Post added at 12:48 AM ---------- Previous post was at 12:38 AM ----------
Alright, do you have a backup of your original 4.1.2 ROM?
Maybe compare your radio(baseband)
It might have been flashed to wrong one for your network if you flashed another carriers radio.
Click to expand...
Click to collapse
Yes exactly and everything went wrong. I also think its because the radio. I flash different radio for K2_UL but I think what I need is for PL80150 which is Asia K2_UL version. hopefully I wish someone could upload

kcreeps said:
Yes exactly and everything went wrong
Click to expand...
Click to collapse
I have these 4.1.2 HTC Sense 4 as my stock rom backup from TWRP but it also has a problem as I said before it lags and hang when turning mobile data on and I notice that the battery is not reducing and increasing anymore it stucks at 77% aside from that everything works fine

kcreeps said:
Yes exactly and everything went wrong
Click to expand...
Click to collapse
Find the 4.1.2 OTA update for your phone
And flash the radio img from inside the firmware zip
---------- Post added at 01:17 AM ---------- Previous post was at 01:10 AM ----------
kcreeps said:
I have these 4.1.2 HTC Sense 4 as my stock rom backup from TWRP but it also has a problem as I said before it lags and hang when turning mobile data on and I notice that the battery is not reducing and increasing anymore it stucks at 77% asidefrom that everything works fine
Click to expand...
Click to collapse
Yes, that is definitely radio issue
I'll do some recon see if I can find a link
http://forum.xda-developers.com/showthread.php?t=2305793
?I think this base off PL80150
not sure if it has the radio.img inside it though......

russellvone said:
Find the 4.1.2 OTA update for your phone
And flash the radio img from inside the firmware zip
---------- Post added at 01:17 AM ---------- Previous post was at 01:10 AM ----------
Yes, that is definitely radio issue
I'll do some recon see if I can find a link
http://forum.xda-developers.com/showthread.php?t=2305793
?I think this base off PL80150
not sure if it has the radio.img inside it though......
Click to expand...
Click to collapse
ok thanks I will try it. thank you very much

kcreeps said:
ok thanks I will try it. thank you very much
Click to expand...
Click to collapse
I just flash the rom and found out that there is no firmware.zip and it also lags. i think i need the stock radio for my device.

kcreeps said:
I just flash the rom and found out that there is no firmware.zip and it also lags. i think i need the stock radio for my device.
Click to expand...
Click to collapse
Yes definitely need stock radio

Solved
I found out that flashing RUU doesnt help me fix the problem. Its the s-off by facepalm now it runs back to normal

kcreeps said:
I found out that flashing RUU doesnt help me fix the problem. Its the s-off by facepalm now it runs back to normal
Click to expand...
Click to collapse
Are you saying it was Facepalm's s-off that fixed the problem, ?
#EDIT#
just read your
[My S-Off experience] post, your saying that Facepalm's s-off was the problem,
I've noticed that others like @old.splatterhand used Facepalm's s-off but has not expressed any lag issues.
I'm would appreciate if you would list your device info in your original post
Modelid
CID
Carrier
Country
Language
Etc...
Just to inform others more clearly of which device is affected this way

I think his account is deleted... Keeps telling me 'invalid id number'. Anyways, if the account is still up and going.... Its not S-Off that is screwing your phone up. You flashed a radio.img that you apparently did not confirm prior to if it was proper for your device. Also, you failed to make a backup of your original radio.img. For the record, twrp and or cwm does not touch the radio.img. This is something you will need from YOUR ota or a personal dump using either a dd or cat command. You failed to do this as well. I read in your other thread that you went back to S-On? In addition, I read you applied an RUU prior to? If you restored with an RUU then you are good to go with your radio.img. You can go back to S-Off now, but this time lets leave the radio image alone until you know exactly what you are doing.
OTHER VIEWERS READING THIS:
Just because you go S-Off or unlock your bootloader DOES NOT MEAN you can just start flashing away at anything with anything! This is how problems arise and bricks! So take caution at what you plan to do and if you don't know then find out before you proceed, otherwise DO NOT DO IT!
--- Happy Hunting
Sent from my C525c using XDA Premium 4 mobile app

I've flashe stock RUU and everything get back to stock Hboot, radio, recovery, boot everything. but after flashing with an s-off device my phone still lags when turning mobile data on ever flashing every rom I have like 4.1.2 and 4.2.2 from old.splattered and still experienceing the lag ang hang. so I've decided to s-on my device "fastboot oem writesecureflag 3" and everything works fine. I just here to share my experience with s-off I dont know why that happens but It just happen now I already have stock 4.2.2 and I can say everything is fine now. sorry I'm not always online coz I already fixed my phone.. Big thanks to all users here at xda

Related

[Q] HTC Sensation: Phone ON, but screen BLANK after Android 2.3.4 OTA update!

Hi all,
I got the Android 2.3.4 OTA update, downloaded and installed it. The Sensation switched on right after update. The HTC boot screen came up, the boot-up sound played, AND THE SCREEN WENT BLANK!!
Now, I know the phone is actually ON, because I can call it from another phone and it rings. Also, the regular gesture on the screen to answer a call works too, but still, nothing shows on the display.. it's totally BLANK..
How can i solve this issue?? Thanks in advance
Try flashing a RUU again, there's a thread with all available RUUs here: http://forum.xda-developers.com/showthread.php?t=1074559
If you have a Tmobile Sensation then select TMOUS and open it after it downloads, and follow instructions. If it doesn't work, you should put the warranty to use if it has warranty.
KCuadrado said:
Try flashing a RUU again, there's a thread with all available RUUs here: http://forum.xda-developers.com/showthread.php?t=1074559
If you have a Tmobile Sensation then select TMOUS and open it after it downloads, and follow instructions. If it doesn't work, you should put the warranty to use if it has warranty.
Click to expand...
Click to collapse
Thanks for the quick reply!
Just wanted to note to you that my phone has never been rooted or has never had any custom firmware or any such thing done. This was the only OS update i've done since i bought it. Other than that, only tiny apps and games have been installed.
Also, the phone is not locked to any network.
Does your instruction still apply? if so, please let me know the way ahead. Thanks again
RUU
MicroWise said:
Thanks for the quick reply!
Just wanted to note to you that my phone has never been rooted or has never had any custom firmware or any such thing done. This was the only OS update i've done since i bought it. Other than that, only tiny apps and games have been installed.
Also, the phone is not locked to any network.
Does your instruction still apply? if so, please let me know the way ahead. Thanks again
Click to expand...
Click to collapse
Yes, the RUU is a file that you open and it's like an OTA update but for computer, something like that. I have a Tmobile Sensation and I flashed this one:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_signed
It's the latest leaked RUU I think, and it's the same version that came with my phone when I got it. I used it to get S-ON too after S-Off and rooting. There's a tutorial for that too here if you want to root. Let me know how it works.
KCuadrado said:
Yes, the RUU is a file that you open and it's like an OTA update but for computer, something like that. I have a Tmobile Sensation and I flashed this one:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_signed
It's the latest leaked RUU I think, and it's the same version that came with my phone when I got it. I used it to get S-ON too after S-Off and rooting. There's a tutorial for that too here if you want to root. Let me know how it works.
Click to expand...
Click to collapse
Yea, that's the thing, my friend. I don't want to do anything like rooting/unrooting etc. etc. all i want is my phone's screen to start working.
before the 2.3.4 OTA update, I had Android 2.3.3 on my phone. is there any way to go back to that version of Android?
You not rooting/unrooting. You're just flashing the stock ROM back onto the phone. See it as reformating a PC hard drive for a clean installation. You will lose all data, mind
EddyOS said:
You not rooting/unrooting. You're just flashing the stock ROM back onto the phone. See it as reformating a PC hard drive for a clean installation. You will lose all data, mind
Click to expand...
Click to collapse
aah ic.. apologies for my stupid questions.. i'me truly a newbie when it comes to stuff like this..
can you please give me directions on which RUU to choose and how to go about doing the installation? umm... please...? *innocent eyes*
Haven't tried taking the battery out yet..? First thing I would do
Hi Tirozz,
Yea i've done all of that:
- took off battery, put it in after 30 seconds, switched it on
- did hard reset by going into that special mode by pressing power and volume down
- took off memory card and switched on
still nothing..
MicroWise, there is a way to get back to Android 2.3.3. Download this RUU if you have a Tmobile Sensation:
http://www.filefactory.com/file/cb7...00P_10.11.9007.15_M_release_193714_signed.exe
Open it in your Windows PC and follow the instructions, then you'll have the stock Android 2.3.3 back again.
If you don't have the TMobile one, download the corresponding one from here:
http://forum.xda-developers.com/showthread.php?t=1074559
Let me know how it goes.
I had the same problem,
& i solve it by installing the previous ROM & don't flash the update
install your compatible Rom form the thread above,
KCuadrado said:
MicroWise, there is a way to get back to Android 2.3.3. Download this RUU if you have a Tmobile Sensation:
http://www.filefactory.com/file/cb7...00P_10.11.9007.15_M_release_193714_signed.exe
Open it in your Windows PC and follow the instructions, then you'll have the stock Android 2.3.3 back again.
If you don't have the TMobile one, download the corresponding one from here:
http://forum.xda-developers.com/showthread.php?t=1074559
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the instructions, KCuadrado. And again, i'm very sorry for being an absolute idiot in this area and bugging you all with it..
my sensation is not a Tmobile.. infact its not tied to ANY operators.. and doesn't have any operator logos on it either.. it is not network locked.. so which RUU do i use from there?
I don't know how to help you now :/
Check the RUU forum thread and ask if someone has a RUU for your HTC. Or you can try rooting and getting SuperCID so you can flash any RUU file, but it's easier to ask on the forum thread for your compatible RUU file.
Alright, Thanks a lot, dude.
I shall go over there
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
KCuadrado said:
I don't know how to help you now :/
Check the RUU forum thread and ask if someone has a RUU for your HTC. Or you can try rooting and getting SuperCID so you can flash any RUU file, but it's easier to ask on the forum thread for your compatible RUU file.
Click to expand...
Click to collapse
Bad idea.. apparently i'm too young on this forum to post anything on that thread.. :/
please help..
Dear,
I have the same problem when i updated my phone to 2.3.4 (Official Arabic ROM)
i changed my ROM & put the ORIGINAL One (T-Mobile) & i update it, everything is OK,
The problem is with the official Arabic ROM only (I think)
is there any solution available ??
Thank you all
hey i have the same problem
REVOLUTIONARY
PYRAMID
HBOOT-1.27.1100
RADIO-10.14.9035.01_M
eMMC-BOOT
Jan 13 2012 ,17.33.34
i have no idea what i have to do
i was reading and reading but nothing concrete
id like to know if could u help me ??
MicroWise said:
Alright, Thanks a lot, dude.
I shall go over there
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
Bad idea.. apparently i'm too young on this forum to post anything on that thread.. :/
please help..
Click to expand...
Click to collapse
What is the model of your phone and what region are you in? I assume it's an XE or XL, not 4g. I will try to help you.. are you at all familiar with adb? What does it say on the screen of the phone when you press the vol- and power power? Can you take a photo and upload it?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
jesusanz33 said:
hey i have the same problem
REVOLUTIONARY
PYRAMID
HBOOT-1.27.1100
RADIO-10.14.9035.01_M
eMMC-BOOT
Jan 13 2012 ,17.33.34
i have no idea what i have to do
i was reading and reading but nothing concrete
id like to know if could u help me ??
Click to expand...
Click to collapse
You can't flash an ota with custom recovery. Nothing concrete? Have you tried using the search function on the forum, hundreds of posts about it?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
so do i have to go back to stock recovery?? how to do that??? and i have s-off and rooted stock rom thx

Can't Get Back To Unrooted Stock No Matter What I Try

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

[Q] Differences between hboots 1.06, 1.09, 1.13, and 1.14?

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

HTC ONE S - Unbranding process

Hi all,
I've got a HTC ONE S that has Vodafone (UK) branding on it but the phone is unlocked so it takes my Orange sim card. What's the best method to remove the Vodafone branding? I just want a generic handset.
Thanks in advanced.
Are you talking about the actual physical branding or the software branding?. A simple flash to a 3rd party Rom would "debrand" your device.
Sent from my HTC One S using xda app-developers app
DxTcmix said:
Are you talking about the actual physical branding or the software branding?. A simple flash to a 3rd party Rom would "debrand" your device.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Software unbranding mate. It has Vodafone crap on it. Just want it generic.
bouncyball said:
Software unbranding mate. It has Vodafone crap on it. Just want it generic.
Click to expand...
Click to collapse
Just flash a debranded rom, any here exept tmobile roms would do it.
Oh and WRONG SECTION. Read the rules before posting... sheesh.....
masterkamon842 said:
Just flash a debranded rom, any here exept tmobile roms would do it.
Oh and WRONG SECTION. Read the rules before posting... sheesh.....
Click to expand...
Click to collapse
tryout trickdroid's latest version
Apologies for the wrong forum, I realised that afterwards.
Right, I've now rooted my device so could someone recommend me a STOCK rom to clear out the Vodafone crap?
Thank you
EDIT - I have the S4 ONE S (1.5Ghz version)
bouncyball said:
Apologies for the wrong forum, I realised that afterwards.
Right, I've now rooted my device so could someone recommend me a STOCK rom to clear out the Vodafone crap?
Thank you
EDIT - I have the S4 ONE S (1.5Ghz version)
Click to expand...
Click to collapse
Choose wise, choose carefully:
http://www.shipped-roms.com/index.php?category=android&model=Ville
Eu 1.78 is pretty good actually
Sent from my One S using xda app-developers app
JohnKoeMan said:
Choose wise, choose carefully:
http://www.shipped-roms.com/index.php?category=android&model=Ville
Eu 1.78 is pretty good actually
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for that. I updated the phone to JB the other night so will these be compatible?
Also - I tried a ROM last night and it wasn't the right file type but I wiped my old OS. But as a guide told me to make a backup, I did and restored without any problems but lost SuperSU - Is this normal? Shall I just re-install?
Downloaded one but unsure how to install them as they're EXE files. What state does my phone need to be in? It also says
From:
Image Version
3.16.161.9
To:
Image Version:
1.78.401.2
Error [155]: UNKNOWN ERROR
I've tried locking my bootloader again it says 'RELOCKED' but still says TAMPERED
EDIT - In recovery screen also, it says at the top
***TAMPERED***
***UNLOCKED***
Is this normal?
I am getting no where with this and it's becoming very annoying!
I've tried reading through forum and forum, YouTube videos and various different methods!
All I want is my phone to be STOCK and it's taking me over 4 hours this morning to get no where!
bouncyball said:
I am getting no where with this and it's becoming very annoying!
I've tried reading through forum and forum, YouTube videos and various different methods!
All I want is my phone to be STOCK and it's taking me over 4 hours this morning to get no where!
Click to expand...
Click to collapse
Really strange that it says relocked/tampered and tampered/unlocked in recovery...
You might've gone wrong with the relocking of your phone, undoubtedly have you checked this out.
Can you tell me what you've ben trying so far?
And another thing: if you updated to JB, these RUUs might not work any longer since they are ICS mostly.
The best thing for you is to go by a custom ROM, it is at least the easiest thing to do now.
You can always fiddle around to restore to STOCK but as you've experienced yourself already, it isn't easy.
Here's a link to what I used when I bricked my phone, it might be of some help.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
JohnKoeMan said:
Really strange that it says relocked/tampered and tampered/unlocked in recovery...
You might've gone wrong with the relocking of your phone, undoubtedly have you checked this out.
Can you tell me what you've ben trying so far?
And another thing: if you updated to JB, these RUUs might not work any longer since they are ICS mostly.
The best thing for you is to go by a custom ROM, it is at least the easiest thing to do now.
You can always fiddle around to restore to STOCK but as you've experienced yourself already, it isn't easy.
Here's a link to what I used when I bricked my phone, it might be of some help.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Click to expand...
Click to collapse
Thanks for the reply.
EDIT - Locking my handset I'm doing the following ;
Placing my Unlock_code.bin in the DATA folder on the toolkit and pressing RELOCK BOOTLOADER
I've tried the following ;
Running RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.EXE while the phone is on the HOME SCREEN and BOOTLOADER
Running OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.ZIP using Hasoon's Toolkit.
I'm getting ERROR messages 151 when installing from the phones HOME SCREEN and ERROR 131 when installing from Bootloader.
I've tried both methods while the phone is LOCKED and UNLOCKED
Currently my phone is displaying the following in the bootloader menu ;
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11-50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57-1
My goal is put have a stock or stock looking ROM with the Vodafone software removed.
Thanks for reading.
Double post
bouncyball said:
Thanks for the reply.
EDIT - Locking my handset I'm doing the following ;
Placing my Unlock_code.bin in the DATA folder on the toolkit and pressing RELOCK BOOTLOADER
I've tried the following ;
Running RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.EXE while the phone is on the HOME SCREEN and BOOTLOADER
Running OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.ZIP using Hasoon's Toolkit.
I'm getting ERROR messages 151 when installing from the phones HOME SCREEN and ERROR 131 when installing from Bootloader.
I've tried both methods while the phone is LOCKED and UNLOCKED
Currently my phone is displaying the following in the bootloader menu ;
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11-50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57-1
My goal is put have a stock or stock looking ROM with the Vodafone software removed.
Thanks for reading.
Click to expand...
Click to collapse
Error 131 means the RUU is incompatible with your CID. Do you know it? Not sure where to find cid specific RUU but searching XDA will always yield answers.
Lock phone, fastboot usb connect phone, find right RUU and open the .exe
Btw you htc drivers installed on you're pc right?
Sent from my One S using xda app-developers app
JohnKoeMan said:
Error 131 means the RUU is incompatible with your CID. Do you know it? Not sure where to find cid specific RUU but searching XDA will always yield answers.
Lock phone, fastboot usb connect phone, find right RUU and open the .exe
Btw you htc drivers installed on you're pc right?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
bouncyball said:
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
Click to expand...
Click to collapse
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
JohnKoeMan said:
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
Click to expand...
Click to collapse
Ignore that, was for htc one X XD
---------- Post added at 03:24 PM ---------- Previous post was at 03:11 PM ----------
bouncyball said:
Thanks for the reply.
CID is something I've seen pop up - I'll have a look into this. I have HTC drivers yeah.
CID: VODAP001
Click to expand...
Click to collapse
Read this article carefully. It will give you an insight in how difficult the process we're doing is:
http://www.xda-developers.com/android/facepalm-s-off-for-htc-one-s-one-xl-and-droid-dna/
You said you downloaded the latest OTA right? This article states that with the latest OTA update we are no longer able to SUPERCID the phone, meaning only CID-specific RUUs can be applied. I can't find any RUUs for your CID, so this might just be the end of the road for this plan.
So maybe installing a ROM similar to stock might be the only good solution for you.
JohnKoeMan said:
Check here for your RUU and maybe new insight:
http://forum.xda-developers.com/showthread.php?t=1936905&page=2
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
Ignore that, was for htc one X XD
---------- Post added at 03:24 PM ---------- Previous post was at 03:11 PM ----------
Read this article carefully. It will give you an insight in how difficult the process we're doing is:
http://www.xda-developers.com/android/facepalm-s-off-for-htc-one-s-one-xl-and-droid-dna/
You said you downloaded the latest OTA right? This article states that with the latest OTA update we are no longer able to SUPERCID the phone, meaning only CID-specific RUUs can be applied. I can't find any RUUs for your CID, so this might just be the end of the road for this plan.
So maybe installing a ROM similar to stock might be the only good solution for you.
Click to expand...
Click to collapse
Thanks for the information - I'll give this a read in a while. I've also looked into changing the CID of my phone, followed a couple of guides but they don't seem to work, they just crash my phone.
EDIT - So, basically I have to stick with the Vodafone branding on my ONE S unless I flash to a custom ROM?
bouncyball said:
Thanks for the information - I'll give this a read in a while. I've also looked into changing the CID of my phone, followed a couple of guides but they don't seem to work, they just crash my phone.
EDIT - So, basically I have to stick with the Vodafone branding on my ONE S unless I flash to a custom ROM?
Click to expand...
Click to collapse
Yeah, its the only way I guess...
Nothing wrong with custom ROMs, they're the best, trust me! :good:
JohnKoeMan said:
Yeah, its the only way I guess...
Nothing wrong with custom ROMs, they're the best, trust me! :good:
Click to expand...
Click to collapse
Can you recommend me a good one to try? One that's as close to stock as possible that doesn't have any problems. This is my 3rd HTC device and the last 2 devices always had problems, hence why I wanted stock.
EDIT - Also, what steps do I need to take to get it back to before I rooted it? Completely factory before I installed anything.
Still getting nowhere.
I've even managed to change my CID to 11111111 from the Vodafone branded one using HEX editor. Still getting the same error's when I'm trying to install .ZIP and .EXE's when the bootloader is RELOCKED.
Could no one else shed some light on this for me please?
CID is now HTC__001 and still get the same error messages!
How hard can it be to remove a service providers software from a phone?
I would really appreciate someones help - I've tried pretty much all I can try!
Could I install an Android version lower than what I've got? I don't mind it not being JB as it's pretty much the same as ICS!

[Q] AT&T HTC One X ROM & Kernel Problem

Hi guys,
I'm newbie about android and please do not be angry to me for this question. I was read lots of topics from xda and another forums but I can't find anything.
I have AT&T HTC One X and i was happy with my phone. Maybe one year ago I rooted my phone and install ATT Stock Root - 3.18.502.6 - JB 4.1.1.zip. So, i followed instructions from xda's web site and everything was fine.
Last two weeks my phone starts to restarts it self. So, I decide to install everything again and open my phone in recovery mode with TWRP and wipe all data. (I don't have any backup of my original data)
I have TRWP's 2.7.1.0 version and I tried to install ATT Stock Root - 3.18.502.6 - JB 4.1.1.zip because I install it one year ago and it works fine. It installs fine but when I press restart my phone stuck at Quietly Brilliant screen and after 2 minutes my phone restarts it self.
Also I can't s-off my phone. I have unlock code bin and I applied it to my phone but something was wrong.
So please can any one help me please. I don't know why my phone acts like that.
Thanks in advance.
Ok so I know your a newbie but do you know your firmware is way out of date? We now have firmware for at&t that is at least 4 realises older than the current. I would say upgrade to a new ROM and firmware. If you don't wish to upgrade I have to ask what kernel you are using?
What he said. Also, did you flash the boot.img from the rom zip via fastboot? As you are s-on, you must perform that additional step.
I suggest he reads timaaas thread. Sounds to me like he should run a ruu to which he can still obtain s off.
Well thanks for suggestions, but I don't know what is the sequence for installing new firmware, rom and kernel. Could you guys please explain the it.
marknoll said:
I suggest he reads timaaas thread. Sounds to me like he should run a ruu to which he can still obtain s off.
Click to expand...
Click to collapse
No, no, no! He can't run an RUU while s-on because it'll brick his phone. I know you mean well but you need to increase your own knowledge before you can start giving advice here, I've seen at least a few times where you've given advice that would result in a brick. I'm sure you don't want that on your conscience.
Sent from my Evita
---------- Post added at 08:56 PM ---------- Previous post was at 08:53 PM ----------
ahrar said:
Well thanks for suggestions, but I don't know what is the sequence for installing new firmware, rom and kernel. Could you guys please explain the it.
Click to expand...
Click to collapse
You more than likely only needed to flash the boot.img from the ROM zip by fastboot. Flash the ROM, then flash the boot.img, and your phone should boot up. Once you're all booted you need to get s-off. Look in my guide thread in my signature for instructions.
Sent from my Evita
timmaaa said:
No, no, no! He can't run an RUU while s-on because it'll brick his phone. I know you mean well but you need to increase your own knowledge before you can start giving advice here, I've seen at least a few times where you've given advice that would result in a brick. I'm sure you don't want that on your conscience.
Sent from my Evita
---------- Post added at 08:56 PM ---------- Previous post was at 08:53 PM ----------
You more than likely only needed to flash the boot.img from the ROM zip by fastboot. Flash the ROM, then flash the boot.img, and your phone should boot up. Once you're all booted you need to get s-off. Look in my guide thread in my signature for instructions.
Sent from my Evita
Click to expand...
Click to collapse
No no. I didn't mean for him to run ruu. I suggested he read your thread to see what requisite is needed to do so. I wasn't suggestioning to ruu..omg no. Lol
marknoll said:
No no. I didn't mean for him to run ruu. I suggested he read your thread to see what requisite is needed to do so. I wasn't suggestioning to ruu..omg no. Lol
Click to expand...
Click to collapse
But that's exactly what you said:
Sounds to me like he should run a ruu...
Click to expand...
Click to collapse
Sent from my Evita
Yes. Run a ruu if he meets the requirementz
marknoll said:
Yes. Run a ruu if he meets the requirementz
Click to expand...
Click to collapse
But he doesn't, and that's the point. Why say that when it's clear that he doesn't meet the requirements? What if he took your advice and ran the RUU? Would you have bought him a nice new phone? Am I making sense here?
Sent via Bacon
Yep

Categories

Resources