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
Related
So after having Jellybean updated on my Telstra One XL I decided to much around with recoveries and custom ROMs to see if I could get them running. I realised that this was going to cause issues, but I was fine with mucking around with it.
I unlocked the phone and got a recovery installed and of course the touchscreen didn't work in recovery. So I mucked around with it and managed to get ROMs installed via manual boot.img flashing and manual ROM flashing via:
Code:
adb shell recovery --update_package=/sdcard/rom.zip
My test was with CM10 and it got up and running. The only issue is that touchscreen doesn't work. Which made any progression through the setup phase impossible
If anyone has any clues as to how to get this up and going again I'm all ears.
I tried to use JET to roll back the HBOOT and try to roll back the firmware, but the RUUs wanted none of it.
Thanks in advance,
Anthony
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
twistedddx said:
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
Click to expand...
Click to collapse
No I didn't, must've missed that. Thanks, I will try that.
Didn't work with any RUU either.
EDIT: Got the RUU installed, thank you very much. I was an idiot and forgot to relock my bootloader again
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
DESERT.TECH said:
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Not really relevant.
twistedddx said:
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
Click to expand...
Click to collapse
RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Tried the unbricking process, but it won't work. Going to get it replaced now.
Antonioffaxii said:
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Click to expand...
Click to collapse
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
twistedddx said:
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
Click to expand...
Click to collapse
I couldn't restore it in anyway, I had work so I took it with me and had it replaced.
Now I have one that works again!
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.
Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)
first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium
exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.
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