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
Related
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
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.
I recently flashed to the ViperXL Rom, and I am seeing only a couple issues. I can live with a once a day random reboot, but what is more problematic is my radio shutting down. I have seen this behavior:
1. When waking up from sleep mode I have no "bars" and a little "x" by the radio. Like it has shut itself down while asleep. Generally it wakes up, but this would preclude incoming calls and texts while asleep. This may be a configuration item, but if it is I can not find it.
2. Sometimes it just doesn't come back on and I have to reboot. When I do I get a notice that it is recognizing my SIM card and I have to select my carrier again. I am wondering if I am on the wrong radio. I am in upstate NY on ATT.
I also have this problem but on magiorom 4.02
Sent from my HTC One XL using Tapatalk now Free
Did you look through the Viper (and MagioRom thread, for the second poster) thread? This issue (and its fix) has been mentioned a ridiculous amount of times. You can either flash the Beastmode kernel or upgrade to the 2.15 firmware (s-off required).
Sent from my Evita
radio signal lost
You will have to flash Radio from viper hub install hboot 2.14 or 2.15 from ruu 3.18.
You can flash radio only if you are s-off.
S-off facepalm thread is in evita resource compilation.
Install beastmode 3.2 and beastmode 3.5 to stop random reboots.
X elemental does not work well. It gives random reboots.
timmaaa said:
Did you look through the Viper (and MagioRom thread, for the second poster) thread? This issue (and its fix) has been mentioned a ridiculous amount of times. You can either flash the Beastmode kernel or upgrade to the 2.15 firmware (s-off required).
Sent from my Evita
Click to expand...
Click to collapse
Forum Search was not working this morning. I will try to find this data.
klaypigeon said:
Forum Search was not working this morning. I will try to find this data.
Click to expand...
Click to collapse
Here u go bro,
http://forum.xda-developers.com/showthread.php?t=2165880
http://forum.xda-developers.com/showthread.php?t=2423735
Posted in wrong forum section, too. This obviously belong in Q&A, Help & Troubleshooting.
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
elias.acab said:
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
dr3amsINdigital said:
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
Click to expand...
Click to collapse
Oh I see, thanks!
Sent from my One S using xda app-developers app
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
rolo143 said:
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Moonshine S-OFF: http://forum.xda-developers.com/showthread.php?t=2325590
or
Facepalm S-OFF: http://forum.xda-developers.com/showthread.php?t=2155135
Absolutely right.
And how to remove the red warning text you can find here.
Keep in mind that once you're s-off and want to return to s-on (warranty, whatever...) you'll need to reflash any stock bootloader. Else you'll definitely brick your phone. Best thing is to run any RUU before you set s-on flag on your phone then. It'll automatically restore the stock bootloader that comes with it.
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
hongha_222 said:
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
Click to expand...
Click to collapse
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
rolo143 said:
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Your device must have s-off without s-off you WON'T BE ABLE TO RUN ROM.
Click to expand...
Click to collapse
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
hongha_222 said:
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
Click to expand...
Click to collapse
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
tsphan said:
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
Click to expand...
Click to collapse
you're right but I don't see any problem when I try the rcdata fix.
b) Type "mount" to see a list of mounts. I saw that the data block (p35) was being mounted again in /sdcard, which should be (p36). Checking /etc/fstab shows that the /sdcard was commented out!
I can do S-Off with hboot 2.16.
flashed with s-on
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
mattdbr said:
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
Click to expand...
Click to collapse
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
tivofool said:
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
Click to expand...
Click to collapse
Ok, will do. Sorry I didn't notice the S. Thanks
Let me start off by saying i have everything updated. Radio,Ruu,Root,Recovery,SuperCid,S-Off
On any non-sense based rom when i turn the phone on there is data. After i decide to connect to Wi-Fi or Turn off the data to conserve battery everything is fine. After I turn Wi-Fi off or Turn data back on It does not work and to use it I must restart the phone. This is driving me insane! I spent hours updating everything so i could install a new rom (Because i thought it was a problem with the rom) but even after that no luck! If anyone knows a way to fix this ridiculous problem please HELP!!!
Saying that you've "updating everything" is almost like saying nothing, updated to exactly? You need to provide exact details. Bootloader details, radio version, ROM version/build, kernel version/build.
Sent from my Evita
timmaaa said:
Saying that you've "updating everything" is almost like saying nothing, updated to exactly? You need to provide exact details. Bootloader details, radio version, ROM version/build, kernel version/build.
Sent from my Evita
Click to expand...
Click to collapse
Sorry noob here.
HTC ATT 3.18 (0.24p.32.09.06_10.130.32.34) Radio
3.18 RUU
SuperCid 11111111
Facepalm S-Off
AOKP Version: aokp_evita_jb-mr1_milestone-2
Kernel Version: 3.4.10-g8d6810dd
[email protected] #1
Sun Jul 21 19:30:37 CEST 2013
It was doing this also before I updated the Radio, Ruu, and had no s-off
Did you try a different Rom? Did you try it on sense after you ran the ruu? What twrp and hboot versions do you have?
Sent from my VENOMized HoxL
area51avenger said:
Did you try a different Rom? Did you try it on sense after you ran the ruu? What twrp and hboot versions do you have?
Click to expand...
Click to collapse
I did try others after the RUU update. It does not work on any non-sense based roms. It worked on ViperRom which is sense, but i don't like sense. Like i said I tried many things and it's driving me insane!
HBOOT - 2.14.0000
TWRP - v2.6.3.0
Try downgrading twrp to 2.6.0.0 and reflash aokp
Sent from my VENOMized HoxL
I'd try running the RUU again, and also using TWRP 2.6 instead of 2.6.3, I've seen bugs reported on that version.
Sent from my Evita
I found how to fix it. Go to Mobile Networks Settings- Access Point Names- Change From ATT to ATT LTE. Fixed