I'm still getting data drops even with the new firmware flashed. I know flashing beastmode will fix this but i though flashing the firmware would also work. Any input?
Sent from my Elemental Sense 5 S-off HTC One XL
Data drops or signal drops?
Sent from my Evita
timmaaa said:
Data drops or signal drops?
Sent from my Evita
Click to expand...
Click to collapse
I can't receive any calls or texts and I have to turn on and off airplane mode to fix. Also data wontnturn on so both I guess
Sent from my Elemental Sense 5 S-off HTC One XL
majortaylor said:
I'm still getting data drops even with the new firmware flashed. I know flashing beastmode will fix this but i though flashing the firmware would also work. Any input?
Click to expand...
Click to collapse
As with most things here, your mileage may vary. Try the Beastmode kernel.
Otherwise, I know some folks have actually gotten better reception by going back to an old 3.17 or 3.18 radio. Although it doesn't seem a "reception" issue per se. But if the other options doesn't work, its worth a try.
timmaaa said:
Data drops or signal drops?
Sent from my Evita
Click to expand...
Click to collapse
I have beastmode ready to flash but I prefer elemental
Sent from my Elemental Sense 5 S-off HTC One XL
Did you remember to flash the firmware twice, per Turge's instructions? Wouldn't hurt to make sure the hboot is indeed updated to 2.15, and the baseband has been updated, just to be sure all the changes actually occurred.
majortaylor said:
I have beastmode ready to flash but I prefer elemental
Sent from my Elemental Sense 5 S-off HTC One XL
Click to expand...
Click to collapse
If your hboot is indeed properly updated to 2.15, and another radio doesn't fix the issue, you might hdd no choice.
Sent from my Evita
Should've be easy via adb if you just follow the steps listed
But if the monkey comes un- spanked you sometimes must install the boot.img yourself via fastboot but only if the monkey in question is albino if not just sideload a wanker and judge him from there, this should get the blind heretics to believe that it has superuser permission, OK. The firmware you use should be free of any viruses or termites to avoid getting CPU rot keep that in mind when choosing which firmware to flash. Flashing should also be done at night to avoid disobedience from the day gods who hate herpes which will have no effect on the outcome of your wifes pregnancy test but still... It's just good practice.
using xda app-developers app
redpoint73 said:
Did you remember to flash the firmware twice, per Turge's instructions? Wouldn't hurt to make sure the hboot is indeed updated to 2.15, and the baseband has been updated, just to be sure all the changes actually occurred.
Click to expand...
Click to collapse
Hboot says 2.15 what's the correct baseband?
Sent from my Elemental Sense 5 S-off HTC One XL
Baseband is still att's 3.18
Sent from my Elemental Sense 5 S-off HTC One XL
majortaylor said:
Baseband is still att's 3.18
Click to expand...
Click to collapse
I'm guessing that you forgot to run it twice. Running it once just upgrades hboot. The radio is the main issue, so run it again, and I'll bet it will fix your signal drop issue.
If you are uneasy about running it again, you can try carl1961's recovery flashable AROMA installer, posted under where it says RECOMENDED: in this thread: http://forum.xda-developers.com/showthread.php?t=2331373
This is actually what I did, as it was right after the Sense 5 stock ROM came out, and I was afraid of bricking from updating the firmware (as a couple folks did early on, before Turge fixed the zip).
redpoint73 said:
I'm guessing that you forgot to run it twice. Running it once just upgrades hboot. The radio is the main issue, so run it again, and I'll bet it will fix your signal drop issue.
If you are uneasy about running it again, you can try carl1961's recovery flashable AROMA installer, posted under where it says RECOMENDED: in this thread: http://forum.xda-developers.com/showthread.php?t=2331373
This is actually what I did, as it was right after the Sense 5 stock ROM came out, and I was afraid of bricking from updating the firmware (as a couple folks did early on, before Turge fixed the zip).
Click to expand...
Click to collapse
Thanks I'll try this. I ran it once and got the 90 error and when I ran it a second time nothing happened so I rebooted into bootloader and saw it updated the hboot.
Sent from my Elemental Sense 5 S-off HTC One XL
redpoint73 said:
I'm guessing that you forgot to run it twice. Running it once just upgrades hboot. The radio is the main issue, so run it again, and I'll bet it will fix your signal drop issue.
If you are uneasy about running it again, you can try carl1961's recovery flashable AROMA installer, posted under where it says RECOMENDED: in this thread: http://forum.xda-developers.com/showthread.php?t=2331373
This is actually what I did, as it was right after the Sense 5 stock ROM came out, and I was afraid of bricking from updating the firmware (as a couple folks did early on, before Turge fixed the zip).
Click to expand...
Click to collapse
What options do I choose in the aroma zip?
Sent from my Elemental Sense 5 S-off HTC One XL
majortaylor said:
What options do I choose in the aroma zip?
Click to expand...
Click to collapse
I think I chose YES (or whatever the affirmative choice is) for everything. It doesn't ask to flash hboot, right?
redpoint73 said:
I think I chose YES (or whatever the affirmative choice is) for everything. It doesn't ask to flash hboot, right?[/QUOTE.
I choose yes to everything but the kernel. And no option for hboot
Sent from my Elemental Sense 5 S-off HTC One XL
Click to expand...
Click to collapse
majortaylor said:
I choose yes to everything but the kernel. And no option for hboot
Click to expand...
Click to collapse
Now that you mention it, I don't remember whether I picked YES for the kernel or not. But I'm on the stock kernel, so it wouldn't have mattered either way. I agree that everything but kernel is the right choice in your case.
redpoint73 said:
Now that you mention it, I don't remember whether I picked YES for the kernel or not. But I'm on the stock kernel, so it wouldn't have mattered either way. I agree that everything but kernel is the right choice in your case.
Click to expand...
Click to collapse
Thanks for all the help! I'll check back in with my results after a few hours
Sent from my Elemental Sense 5 S-off HTC One XL
majortaylor said:
Thanks for all the help! I'll check back in with my results after a few hours
Click to expand...
Click to collapse
You're welcome!
I did almost the same exact thing. It was before Turge had clear instructions in his top post of the stock ROM thread, so I missed the fact that the command to flash was supposed to be typed twice. I was still getting signal drop issues, and I realized that only hboot had updated. But after using the AROMA installer, the signal drop issue has been completely resolved!
Hopefully this fixes it for you, also.
redpoint73 said:
You're welcome!
I did almost the same exact thing. It was before Turge had clear instructions in his top post of the stock ROM thread, so I missed the fact that the command to flash was supposed to be typed twice. I was still getting signal drop issues, and I realized that only hboot had updated. But after using the AROMA installer, the signal drop issue has been completely resolved!
Hopefully this fixes it for you, also.
Click to expand...
Click to collapse
How can I verify I installed correctly? Also what was the options inthe aroma installer about?
Sent from my Elemental Sense 5 S-off HTC One XL
majortaylor said:
How can I verify I installed correctly? Also what was the options inthe aroma installer about?
Click to expand...
Click to collapse
From carl1961's thread (where you got the AROMA installer from):
radio.img
wcnss.img (wifi)
adsp.img Advanced Digital Signal Processor: Sound, Video, etc
Aside from checking the baseband radio has updated to 5.08 radio (1.31a.32.45.16_2_10.141.32.34a), I don't know how else to verify installation.
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
My one x is having major issues since i did the S-OFF. My battery percentage is stuck at 77% and will not change, if I try to use the phone (web browsing, looking at tapatalk) it gets real slow. I have tried going all the way back to stock AT&T rom, relocked bootloader and reinstalled everything to no avail. I am now on CM10.1. Please help me if you can.
jac0b said:
My one x is having major issues since i did the S-OFF. My battery percentage is stuck at 77% and will not change, if I try to use the phone (web browsing, looking at tapatalk) it gets real slow. I have tried going all the way back to stock AT&T rom, relocked bootloader and reinstalled everything to no avail. I am now on CM10.1. Please help me if you can.
Click to expand...
Click to collapse
Sounds like the ruu is not compatible with the rom.
AT&T HTC OneX
Android4.1.1
ViperXL
Venomtester said:
Sounds like the ruu is not compatible with the rom.
AT&T HTC OneX
Android4.1.1
ViperXL
Click to expand...
Click to collapse
What do mean by that?
jac0b said:
What do mean by that?
Click to expand...
Click to collapse
Don't worry about that I don't think he read through the whole post or maybe he misunderstood.... So this was once you did the s off...and it was persistent once you ruud back?
a box of kittens said:
Don't worry about that I don't think he read through the whole post or maybe he misunderstood.... So this was once you did the s off...and it was persistent once you ruud back?
Click to expand...
Click to collapse
Yep, i think since then. I did the S-OFF and then installed the Elemental 4.5 kernel on cleanrom and its been downhill since then.
Is it taking charge? Or does it still chill at 77? Maybe you could try going back to s on and see if the problem still persists...but I can't tell you how to turn the s on flag back on maybe grim knows or beaups.... Did you majorly undervolt? And you were on clean Rom jb right? I just can't think of why your phone is acting up and how it would be software
When you use an ruu to downgrade sometimes you can get the wrong radio version. Older or something to that effect.
Was just saying to try an update your radio version or check to make sure it is the latest one. Sorry.
Sent from my HTC One X using xda premium
Venomtester said:
When you use an ruu to downgrade sometimes you can get the wrong radio version. Older or something to that effect.
Was just saying to try an update your radio version or check to make sure it is the latest one. Sorry.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I went back via RUU to 2.20 but still have the same problem.
jac0b said:
I went back via RUU to 2.20 but still have the same problem.
Click to expand...
Click to collapse
Did you try Back up data, Wipe Cache, Dalvik Cache, and reset?
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
Did you try Back up data, Wipe Cache, Dalvik Cache, and reset?
Click to expand...
Click to collapse
RUU wipes everything. It rewrites recover, radio, all firmware components, and I think hboot. What you describe would not be any more of a reset than RUU.
The fact that the problem persists after RUU is a bit surprising, and troubling.
If not for the fact that the problem arouse right after S-Off, I would say it sounds like a failing battery.
Just seeing if refresh might help. Sounds like a dirty install but not sure.
Sent from my HTC One X using xda premium
Venomtester said:
Just seeing if refresh might help. Sounds like a dirty install but not sure.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
He ruud which wipes everything so a fresh install is out of question now
So he will have to revert back to stock?
Sent from my HTC One X using xda premium
Venomtester said:
So he will have to revert back to stock?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hmm I feel your understanding of an ruu or maybe what did is a bit jarred
Ok so he s offed wasn't doing to well then he ran the ruu which wipes everything and brings your phone back to stock... Than he reunlocked and flashed another Rom and even onstock the problem was persistent
a box of kittens said:
Hmm I feel your understanding of an ruu or maybe what did is a bit jarred
Ok so he s offed wasn't doing to well then he ran the ruu which wipes everything and brings your phone back to stock... Than he reunlocked and flashed another Rom and even onstock the problem was persistent
Click to expand...
Click to collapse
So he downgraded then upgraded. Is he running a custom rom on a lower hboot version? I think s-off you can upgrade and downgrade. S-on you can only go up. Is this correct?
---------- Post added at 04:47 PM ---------- Previous post was at 04:23 PM ----------
Venomtester said:
So he downgraded then upgraded. Is he running a custom rom on a lower hboot version? I think s-off you can upgrade and downgrade. S-on you can only go up. Is this correct?
Click to expand...
Click to collapse
I apologize for any random comments made. I have reset my passwords to stop who ever it is that has been using my account for the past few days.
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
redpoint73 said:
RUU wipes everything. It rewrites recover, radio, all firmware components, and I think hboot. What you describe would not be any more of a reset than RUU.
The fact that the problem persists after RUU is a bit surprising, and troubling.
If not for the fact that the problem arouse right after S-Off, I would say it sounds like a failing battery.
Click to expand...
Click to collapse
A failing battery would cause slow response on the device also?
Yes I wiped everything when I RUU'd.
jac0b said:
A failing battery would cause slow response on the device also?
Yes I wiped everything when I RUU'd.
Click to expand...
Click to collapse
I don't know. RUU pretty much controls it all. Wifi, Camera, Battery etc. I don't think battery itself would cause that sluggish of a response.
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Venomtester said:
I don't know. RUU pretty much controls it all. Wifi, Camera, Battery etc. I don't think battery itself would cause that sluggish of a response.
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Click to expand...
Click to collapse
I also did brick my phone previously and was able to recover it using the unbrick tool.
jac0b said:
I also did brick my phone previously and was able to recover it using the unbrick tool.
Click to expand...
Click to collapse
All the problems started after you did a RUU restore?
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Venomtester said:
All the problems started after you did a RUU restore?
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Click to expand...
Click to collapse
I did the S-OFF then I installed the elemental kernel on cleanrom 3.17. Thats when I started to notice the phone was sluggish and the battery percentage was not moving from 77%. So I came home and restored my phone back to stock and still had the same issue.
Hey guys. I have what I think will be a rather simple/stupid issue.
I'm running ViperXL 3.2.5 with ElementalX kernel 5.0.6-beta. Quick Reboot through Venom Hub/Tweaks will restart but will forever loop the bootanimation. I've let it run for 8hrs (I was sleeping... I'm not that patient) without it ever successfully restarting. Hot rebooting through the system menu does the same. It's worth noting that I did not see this issue with ViperXL 3.2.3 and earlier.
My understanding is quick/hot rebooting is simply restarting the shell. Is it possible for some step in that process to hang and forever loop the bootanimation instead? Any ideas?
If needed I'll see about getting a logcat once I have the opportunity.
Thanks!
Did you ever fix this? I have the same problem on latest rom....
What recovery/ver you running?
I have a feeling this is related to the kernel but I would like to know the recovery/ver first.
Elemental 6.5, TWRP 2.3.1.0
I see, Would you try wiping cache, dalvik, factory reset, flash stock kernel either by extracting it or rerunning the viper rom install and selecting flash stock kernel. Then wipe dalvik cache and see if it still happens. (I can't remember if viper wipes dalvik after kernel install, best to do it anyway)
You may want to do a nandroid backup first so you don't loose everything unnecessarily.
Thanks
I will update when I wake up, its 2.30am here so need sleep lol
liamstears said:
I will update when I wake up, its 2.30am here so need sleep lol
Click to expand...
Click to collapse
No prob bob, I should be up to catch it when you update.
exad said:
No prob bob, I should be up to catch it when you update.
Click to expand...
Click to collapse
Here to update already
Done a complete wipe and install viperxl 3.2.6 only and still its not working...
liamstears said:
Here to update already
Done a complete wipe and install viperxl 3.2.6 only and still its not working...
Click to expand...
Click to collapse
Hmmm.. that's definetely strange. What Hboot are you on? I want to try and flash it and see what happens.
2.14
I wonder if my hardware could be different being as I have UK One XL 32gb
liamstears said:
2.14
I wonder if my hardware could be different being as I have UK One XL 32gb
Click to expand...
Click to collapse
Not sure, but unlikely as OP is in Virginia USA it looks like. lemme just ruu up to 2.14 and I'll flash and post my results.. could take a bit as there's no 3.17 RUU lol. If you're in bed before I post, sorry
Seems I'm running into the same thing. Guess it's the ROM. I'm fresh RUU to 2.14 TWRP 2.3.3.1 Fastboot erase cache and wiped everything.
I got it working! Downgraded my hboot to 1.09 and now it works!
Can you test?
Just on my way to work but I can test when I get home. Can't install HTC drivers at work
Sent from my One X using xda app-developers app
Yikes! I almost forgot I posted this.
As it turns out, I was also on hboot 2.14 (I updated from 1.09 for the heck of it when we achieved S-OFF). My hardware is the AT&T HOXL 16GB, though that does not appear to be a factor here.
I've since moved on to a different ROM (for unrelated reasons) but I'm glad to see someone trace this down.
I might experiment with this myself once I'm home to confirm the fix.
Thanks liamstears!
Please do, would be nice to get a couple of confirmations
liamstears said:
Please do, would be nice to get a couple of confirmations
Click to expand...
Click to collapse
Agreed. I should be able to post my findings in about 8 hours. I will test on both 1.09 hboot and 1.11 which is the default hboot for my Telus one x. I use the 10gb version. I believe 2.14 is the same across all carriers. I'm pretty curious to see what's causing this.
In the end I settled on the 1.14 hboot on my UK 32gb One XL
Reasons are because hot reboot works unlike the 2.14 hboot and it doesn't have the white bar in the top right of the splash screen like 1.09 does
liamstears said:
In the end I settled on the 1.14 hboot on my UK 32gb One XL
Reasons are because hot reboot works unlike the 2.14 hboot and it doesn't have the white bar in the top right of the splash screen like 1.09 does
Click to expand...
Click to collapse
Yeah, works on 1.11 perfectly. Seems like an issue with 2.14 which is really really weird because 3.2.6 is based on 3.17 no? lol
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
Nope, you'll probably brick doing that.
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
RollTribe said:
Nope, you'll probably brick doing that.
Click to expand...
Click to collapse
Yeah i figured it was a long shot, glad i asked first lol. Thanks dude!
pside15 said:
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
Click to expand...
Click to collapse
Oh I'm sure it's not to bad, but I have no idea how to use fastboot or adb (I've lucked by without having to use either, at least to my knowledge). Plus I don't readily have a windows PC, I just want make sure I know what I'm doing before I even attempt it. I've been looking over gunnyman's adb for noobs (http://forum.xda-developers.com/showthread.php?t=1754018), I'll give it a shot sometime next week when I've worked up the courage. Thanks for the advice!
pside15 said:
There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm.
Click to expand...
Click to collapse
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
exad said:
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
Click to expand...
Click to collapse
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
pside15 said:
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
exad said:
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
Click to expand...
Click to collapse
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
pside15 said:
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
Click to expand...
Click to collapse
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
31ken31 said:
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm not saying it's that simple and yes, I agree about following the steps. That's why I said I wouldn't even recommend trying the newer ROMs without updating first. I have seen it work though. That's all I'm saying. Maybe those users were ignorant on exactly what they did but I'm just going on what I've read and responded to.
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
exad said:
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Go to my profile and look at my quoted posts or just go back a bit in the Carbon thread. You will see where I quoted someone who was s-on and on the 1.14 hboot that flashed one of the 3.4 nightlies successfully. He was wondering if his phone was going to mess up now. That's the only specific one I remember off the top of my head but I know I've seen others as well. Like I said I'm just going by what I read. They could be completely wrong, lying, or just ignorant noobs. I live on these forums as well and have absolutely no reason to make something like this up.
Sent from my One X using Tapatalk 2
Hi guys,
I've looked everywhere and I cant find how to solve this problem. I have a One XL running ViperXL 4.20 with S-on and hboot 1.14. I have been trying to install the Beastmode Kernel 3.5 reloaded but when I do I get a bootloop. Ive tried installing the 2.0 version first and I still get a bootloop. I really need this kernel to solve my cell signal drops and random reboots. Can anyone help?
If you can't get Beastmode to work, why don't you get s-off and update to the 2.15 firmware. S-off is a good thing to have anyway.
Sent from my Evita
man im totally out of date...ill try those things and beastmode again perhaps?
lilballer151 said:
man im totally out of date...ill try those things and beastmode again perhaps?
Click to expand...
Click to collapse
If i may even i had that problem with Beastmode.. ( i so wanted it )I was on 2.15 and S-OFF i had to bother Timma and Redpoint many a times with all of my quetions... I tried Twice.. still had no success....
so i would suggest you give Elemental X 8.3.2 a try..
it does have almost all the features of Beastmode 3.5... and like Beastmode it does come with Aroma installer and so u can configure your setting during installation...
P.S this kernel does give a good battery and my benchmarks were good ( i am on vanilla):good:
Elemental kernel won't solve the signal drops and reboots on its own though, only in conjunction with the firmware update.
Sent from my Evita
thanks for the info, so is there a certain way I can stop the celldrop and reboots to happen? its really getting on my nerves
See my post above.
Sent from my Evita
Sorry to keep asking but how do I go about updating my hboot?
Go to Turge's stock Sense 5 ROM thread in the development section, the download and instructions are in the first post.
Sent from my Evita
Same problem
timmaaa said:
Go to Turge's stock Sense 5 ROM thread in the development section, the download and instructions are in the first post.
Sent from my Evita
Click to expand...
Click to collapse
Ive been having same problem on my onex evita , Im on hboot 1.14 with s - on ive tried the facepalm method to s-off but its not working therefore theres no way i can upgrade my firmware. The random reboots and signal drops are quite frustrating. I even tried to revert back to my previous viper xl version 3.XX through the backup i made but unfortunately after the restore the device would boot for 5 seconds and then reboot itself leaving me no option but get back to 4.2.0 with signal drops and couple of reboots . Beastmode would take the device into bootloops pls help me resolve this situation.
All you need to do is work out why s-off isn't working. There's no reason for it to not work, you just need to troubleshoot it.
When you restored your previous backup did you flash the boot.img via fastboot?
Sent from my Evita