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.
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
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
Hey all, so i decided i wanted to try out some radios (was running viper xl)
and tried flashing a few different radios
from this thread and
http://forum.xda-developers.com/showthread.php?t=1694012
this section
"These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files."
anyways, now i have been problems, phone randomly thinks sim card is being removed/inserted.
and having random reboots
tried flashing the 3.18 ruu
and flashed viper again,
and am still having these problems
so what else can i do?
any suggestions would be great
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
timmaaa said:
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
Click to expand...
Click to collapse
4.2.0
which firmware do i need to upgrade to ?
(i do belive my hboot was 2.15 before) but i cant seem to remember which ruu that would be
edit:
think i just found it
http://forum.xda-developers.com/showthread.php?t=2517148
is that the correct version?
Yeah that's the one you need.
Sent from my MID-1040
Thanks it had been forever since I'd run an ruu , completely forgot about the firmware upgrade
Sent from my HTC One XL using Tapatalk
No problems.
Sent from my MID-1040
timmaaa said:
No problems.
Sent from my MID-1040
Click to expand...
Click to collapse
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
deepsouth06 said:
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
Click to expand...
Click to collapse
Please post your bootloader details, your recovery version, your current ROM and kernel, and the exact problem you're facing.
Sent from my Evita
timmaaa said:
Please post your bootloader details, your recovery version, your current ROM and kerncontinuehe exact problem you're facing.
Sent from my Evita
Click to expand...
Click to collapse
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
timmaaa said:
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
Click to expand...
Click to collapse
Ok, I read something similar to what you are saying and I did flash a radio 1.31 from this link with is 2.15 firmware. http://forum.xda-developers.com/show....php?t=2517148. However the same problem was still happening. After flashing the current radio (from the above attachment), what I have noticed is that the No Sim icon only seems to happen when I have WiFi turned on for an extended time, this was just a brief observation from last night and this morning.
I am about to flash a stock RUU (possibly the 5.18) to 1) get the phone up to date with the latest firmware and 2) to see if this will help with my Sim Card problems. Or should I use a different RUU to start from Stock again?
Also When looking at the Radios thread I dont see any radios that are 1.31 and up for ATT. All of them seem to begin with 0.xx. The thread i am looking at is http://forum.xda-developers.com/showthread.php?t=1694012
The latest RUU is probably your best bet.
Sent from my Evita
timmaaa said:
The latest RUU is probably your best bet.
Sent from my Evita
Click to expand...
Click to collapse
With S-Off and my CID all 1s I wouldnt have to worry about doing the root again? After the RUU i should be able to install TWRP again and then a custom rom?
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
deepsouth06 said:
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
Click to expand...
Click to collapse
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
timmaaa said:
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
Click to expand...
Click to collapse
Much thanks. I will be trying this out.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
redpoint73 said:
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
Click to expand...
Click to collapse
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
deepsouth06 said:
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
Click to expand...
Click to collapse
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
redpoint73 said:
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
Click to expand...
Click to collapse
No i havent tried taking it out. I will try that out tonight. If all else fails I may end up going for a referb phone, but now with 5.18 I might hold off for as long as i can.
Thanks for your help as well.
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Sorry for the long post.
deepsouth06 said:
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Click to expand...
Click to collapse
I doubt that Google Play would have that effect on the SIM. I think its just a coincidence (red herring).
deepsouth06 said:
Sorry for the long post.
Click to expand...
Click to collapse
No need to be sorry. More detail is almost always better. Its the short posts that I have a problem with; where people ask for help and don't give any specifics or details. Makes it much harder to help.