hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
dzap said:
My Evo 3D has been doing this consistently with the new kernel from the OTA update (I use MeanROM though), but I have seen others on Stock report the same.
It was doing it annoyingly constantly every couple hours when I would just not actively use it.
Now though it has settled down a bit and I'm wondering if it's not a bug but a feature? Because almost like clockwork every night it will reboot on it's own late at night. if I'm using the phone..it won't do it..but it seems to wait for a period of long idle time or something.
I have only had this issue on Kernel 2.6.35.13. Check and see if that is your kernel version as it's the newest one that is blazing smooth and fast (stock) and why I have chosen not to flash another kernel over it yet.
Click to expand...
Click to collapse
i can't tell what kernel on here, its i flashed silver needle and then the rom and it nevered booted up.
I had the same problem using ROMs from XDA. Found that I used RUU to back to stock and it stopped. Haven't had a single reboot since I went back to stock where I would get reboots constantly, to the point the phone was useless.
Since I have S-Off, used the root patch to get root access, but only can be done with S-off...
djcro said:
hi, i have a 3d evo with s-on & h-boot 1.50 and i used gui to flash silver needle & went to recovery to flash viper rom and the phone keeps rebooting and i have read other posts and tired to flash other kernals & roms and nothings working. even tired to use my friends phone and tired to use his back-up but didn't work. any new ideas?? thanks in advance
Click to expand...
Click to collapse
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
cobraboy85 said:
nobody has asked this yet... so I will...
are you on the latest version of viper? silver needle is a 2.3.3 kernel... viper is 2.3.4.
that is your issue if that is the case. flash a kernel that is meant for that build.
sent from Evo
Click to expand...
Click to collapse
yeah, most likely your issue is flashing a kernel NOT COMPATIBLE with the new base....
oh and your only compatible kernel at this time is stock
i tried to do the ruu step and none of the verisons workked, anybody have anymore ideas?? this is were i downloaded the ruu's from for sprint http://www.filefactory.com/f/4ef0ef536face67a/
Related
ok, is there ANY POSSIBLE WAY to downgrade from the leaked firmware we had to flash for the RUU back to the stock one that came with the phone?
this phone has been utter garbage ever since i've done it (7 hour battery life, down from 15-17 hours...random reboots ALL THE TIME etc) and i'm sick of it, to the point where i'm ready to sell the phone and get something else.
is there ANY way to go back?
It is possible but as far as I know you'll need s-off
Sent from my cm_tenderloin using xda premium
well crap. here's hoping they get a nice method that's proven to work, because i need to drop this crap firmware. these reboots are reaaaaaaally annoying me. just had two within 10 minutes.
unless you have s-off there isnt.
but you should try reflashing the RUU.
I know youve probably heard this so many times but i cannot stress how important it is that you let it finish.
and then install a ROM and you should be fine
poison, i've reflashed the RUU three times already. the initial time, where it hung at the white htc screen after 10 min, i battery pulled, rebooted, and let it finished...
then the second time where it didn't hang, and a third time where it didn't hang, and it went through everything twice.
nope you're stuck here for now... but have you tried doing a full wipe and starting from scratch? I know plenty of people are using the latest leak firmware without any significant issues.
yeah man, i wipe it all..data,cache,dalvik,system,boot etc
my buddy did the leaked firmware and gets like 7 hour battery life too, when both of us got 17 hours pre-leak firmware. so it's not just me
Go back to the Inc for now I'm honestly thinking of it lately, feeling a bit nostalgic of Sense 2.1.
i used my inc with stock sense 1.5 from the froyo upgrade..it was so fast and apps opened instantly. damn good phone!
Or run a gb Rom....all you need to do is flash the sd card fix after installing the Rom and you are good to go. I was having some heat issues before on ics and my phone acted funny , went back to gb and my phone is back to being perfect.
Sent from my ADR6425LVW using XDA
hmm really? so maybe it's a combo of the new firmware and ics? if gb runs fine, that is
Sent from my ADR6425LVW using XDA App
jayochs said:
hmm really? so maybe it's a combo of the new firmware and ics? if gb runs fine, that is
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Just out of curiosity, what kernel are you using?
whichever kernel the devs make us flash. joel's, nils', etc
jayochs said:
whichever kernel the devs make us flash. joel's, nils', etc
Click to expand...
Click to collapse
Give SebastianFM's kernel a shot. Its been working amazing for me. Most of the weird issues I had were gone after wiping caches and flashing that kernel. I kinda made my own Senseless ROM out of the first couple ICS leaks - its still mostly based off the first 4.0.1 leak, but its playing very nicely with Sebastians kernel.
I find that the kernel generally has much more influence on things like charging, heat, performance, battery life, etc., than the ROM does.
hmm...is there a way to go back to the stock kernel incase it F's things up? cuz i know nils' rom,w hich i'm running now, boots you back to bootloader to install it..
maybe i'll give it a shot. does it help with the constant 1.5 ghz processing speed with screen on?
and are you on new firmware?
jayochs said:
hmm...is there a way to go back to the stock kernel incase it F's things up? cuz i know nils' rom,w hich i'm running now, boots you back to bootloader to install it..
maybe i'll give it a shot. does it help with the constant 1.5 ghz processing speed with screen on?
and are you on new firmware?
Click to expand...
Click to collapse
yeah, if you're using Nils ROM, it has the boot.img inside the PH98IMG.zip file. So you can open the zip, find PH98IMG.zip, and extract boot.img from it. That is your backup of the kernel that comes with Nils' ROM. You can re-flash this from fastboot if you need it later.
Then, using your file manager, go to /system/lib/modules and make a backup of the .ko files in there, as these are specific to the current kernel. If you do end up rolling back to the stock kernel, you'll need to also go back and restore these modules to get wifi working again with the original kernel.
After you've backed up your modules (just save them to a folder on your SD card or something) just flash Sebastians kernel from recovery. It will then reboot to bootloader and flash the kernel, just like you're used to with your ROM install.
Oh, and yes Sebastians kernel does scale correctly. I use setCPU profiles to set the frequencies I want, and while the min/max frequencies do still jump around all over the place in between the range I've specified, watching the current frequency shows that it does scale in between min and max correctly.
**edit
Also, I'm on hboot/firmware 2.11 from the last OTA. I have not installed the leaked firmware.
thanks man! i'd thank ya but i already used my 8 today lol...so i'm on new leak firmware, would that still work with this kernel then?
jayochs said:
thanks man! i'd thank ya but i already used my 8 today lol...so i'm on new leak firmware, would that still work with this kernel then?
Click to expand...
Click to collapse
I have no way to say so for certain since I haven't flashed that firmware - but this kernel works the best of all the rest so far on my phone. The kernel is based off the kernel FROM the leak though, so my guess is you should have no issues at all.
sweet! thanks, i'll give it a shot soon!
jayochs said:
sweet! thanks, i'll give it a shot soon!
Click to expand...
Click to collapse
The Problems you've been having sound a lot like the ones I have too. Sebastian's kernel made my phone run real hot. I would stick with either the stock ICS kernel or wipe and flash a GingerBread ROM. I flashed Ineffabilis 1.4 the other day and ran it for a couple days. My phone never hit over 90F. On most of the ICS ROMS my phone would jump over 100F most times
Every time i try to install and Ics related Rom my phone says installing apps since its from Ics and it also says updating and when it finishes booting it restarts and it does this every time i install a Ics ROM and i let it boot up like 10 times and the same things happen. Anybody with a similar problem and a fix. And yes when i installed the Roms i wiped the phone data and cleared Dalvik cache and cache and battery stats i did every thing you're suppose to do with all of these Roms.
Whenever I install an ICS rom, my phone will boot until I see the wallpaper, then it reboots and repeats. Havent found one that works.
I am using 4ext to flash
superwipe has been used
I was going to try some anthrax kernel, but it has now vanished...probably wouldn't have saved me.
I might just have to wait til next month :'(
Im on hboot 1.5 <----- even though it was assumed
I hate to ask but did you flash boot.img separately? That seems to be the big problem with some users on hboot 1.5. Also our current firmware doesn't support 3.0 kernels I believe unless you are on the leaked version which I think was modified to run. Don't install the VM firmware though as a lot of people have lost certain functionality with there phone.
Sent from my AOSP 3VO
thefsfempire said:
I hate to ask but did you flash boot.img separately? That seems to be the big problem with some users on hboot 1.5. Also our current firmware doesn't support 3.0 kernels I believe unless you are on the leaked version which I think was modified to run. Don't install the VM firmware though as a lot of people have lost certain functionality with there phone.
Sent from my AOSP 3VO
Click to expand...
Click to collapse
well no i just installed zip from SD on clockwork mod 4.0.1.4 and ik about the horrible vm leak and the ROM that i use and that i was trying to replace was ZR3D gt 3.0 ROM. Also i have s-on just in case that work and how coincidental that one of the roms i tried to install was newt one s like the one u have but RC3 can u tell me your info (way u rooted, s on or off etc.) i really want newt one s and booster shot.
Us s-on ppl can't use the new roms to their best functionality... why you ask.?
1. Because almost all the ics roms use HTC Linux 3.0 stock kernel
2. Our s-on hboots are not happy with the stuff in 3.0
You can use chad's htcleak test kernel (invix me your email) and the rom will work buuuuut there are some issues with that!!!
Sent from my PG86100 using XDA
joecrusher said:
well no i just installed zip from SD on clockwork mod 4.0.1.4 and ik about the horrible vm leak and the ROM that i use and that i was trying to replace was ZR3D gt 3.0 ROM. Also i have s-on just in case that work and how coincidental that one of the roms i tried to install was newt one s like the one u have but RC3 can u tell me your info (way u rooted, s on or off etc.) i really want newt one s and booster shot.
Click to expand...
Click to collapse
Depends on what rom you are using. I think you should download twrp-shooter-2.1.0.img recovery since its an ext 4 touch recovery. Try flashing the rom using that recovery. Also if you are using an Newt S One rom make sure you have the patch and the boot.img that comes with it if u are using the earlier versions. IF u do u must flash the rom then the patch and boot into fastboot and flash the boot.img adn it will boot your phone up. Other thatn that try flashing ics roms using an ext 4 recovery. Hope this helps solves your problems.
OK so ive figured some things out, you probably know them, thats not what i made this thread for.
xhausx s-on kernel installer will not install a kernel if going from JB to Sense.
And for some reason, if coming from PA 2.99, with the latest 2.1 komodo rls 21, HTC dumlock will not let you get back to sense either...
Trying to go back to mean rom at the moment and it has taken me a couple hours lol, its rediculous, thought i could do it without fastboot, or flash image gui, and i was wrong. So i started looking around, found out it was a buck, then i found this forum.
http://forum.xda-developers.com/showthread.php?t=1772769
Thought it might be a tad helpful, it contains the apk for flash image gui at the right version for our phone.
Enjoy and have a wonderful day.
Woot.
got back mean rom aparantly a big issue was with the v6.5 release of meanrom. put 6.4 on there and it worked just fine.
Still tho, a free Flash Image GUI a big plus. So check it out.
Though joeykrim offers his app free thru the forum, it is a good gesture to purchase it for a $1 to show support for such a great tool. It saves a lot of headache for many.
Sent from my EVO using Tapatalk 2
I haven't had issues with the kernel installer on meanrom and I switch between sense and aosp quite often. Dumlock should always work because recovery is flashed into the boot partition essentially replacing boot and allowing twrp to flash the kernel directly. I don't see how it would fail.
If anyone can confirm the jb/kernel installer issue or provide a log from it I should be able to fix it. I haven't tested it yet with 4.2 JB but unless they changed something major it should still work the same.
Many devs provide their tools for free on here, but as mentioned by one_love_420 please show your support and get the donate version if it's something you feel is worthy of it. A lot of hard work goes into some of these apps.
Indeed
xHausx said:
If anyone can confirm the jb/kernel installer issue or provide a log from it I should be able to fix it. I haven't tested it yet with 4.2 JB but unless they changed something major it should still work the same.
Many devs provide their tools for free on here, but as mentioned by one_love_420 please show your support and get the donate version if it's something you feel is worthy of it. A lot of hard work goes into some of these apps.
Click to expand...
Click to collapse
I was just throwing it out there for those who wanted the link, just saw it was a buck on the app store and was looking around to see if it supported our phone yet (last i had checked the one on the app store didnt) a quick google search told me it did and provided me a free link, so just sharing.
I also wanted to say that,
When coming from the original PA (not lens flares) to Super LTE which had the s-on kernel installer, super lte would get stuck in a boot loop. And then when going from PA (lens flares) with the rls 21 komodo kernel, to mean rom (latest) it wouldnt boot, so i just went with what i knew and stated it couldnt, tho i havnt attempted to reproduce the effect since as i am currently sticking with mean rom. You would not believe the fear i had when i couldnt boot my phone for a while and couldnt find out why, then upon trying to unroot using the latest RUU to simply quick fix the problem, the RUU gave me an error, lol i thought my phone was gone.
But it ended up being a problem with mean rom, i went back to PA and then used the dumlock to install an older version of mean rom and all was well.
om4 said:
I haven't had issues with the kernel installer on meanrom and I switch between sense and aosp quite often. Dumlock should always work because recovery is flashed into the boot partition essentially replacing boot and allowing twrp to flash the kernel directly. I don't see how it would fail.
Click to expand...
Click to collapse
Oh and i totally agree with you, i know how the dumlock works and i didnt see what the problem could be at the time, it was just a problem with the latest release of mean rom, flashed and got stuck at the white HTC screen and being s-on that ment i couldnt use the dumlock anymore or anything for that matter. so i was flippin out trying to find the problem before the obvious hit me. I just had assumed with mean rom always being so stable that the newest release wouldnt have bothered my phone. Guess i was wrong though, still have no idea whats wrong with it but that version of mean rom still wont install and work lol. Its all good though, this post might as well serve as a quick shot to a link that you may or may not have known was there.
I'm not sure what I did but I never had any trouble recovery back to sense till now. Every other time I've flashed from job to sense it hasn't been a problem. I have tried Meanrom 6.5, and stock.goodies. with no luck. When I try to flash the boot.IMG, the button is grey out and won't let me flash.
I'm stumped.
Sent from my EVO using Tapatalk 2
Just what the title states, I have just switched over from HTC sense based Operation Jelly Bean 3.15.651.16 to Official BlakCM. My EVo 4gLTE is s-off and rooted with latest TWRP 2.5 for recovery. I followed defection as how to install this particular ROM. What I am not sure on is the kernel. Do I need to install a custom kernel to run this Rom properly and which one if that is the case. I also have the latest base band 1.12.11.1210 installed without TP firmware upgrade. Thanks
You don't need to run custom kernel to run cm10 roms. You can if you want to and komodo is the only one I know of
Sent from my EVO using xda app-developers app
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
LemonNinja said:
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
Click to expand...
Click to collapse
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
cpt.kraker said:
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
Click to expand...
Click to collapse
Both have to be flashed in recovery, only if you are s-off... But thicklizard has s-on kernel installers...
Sent from my EVO
Komodo a no go.
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
cpt.kraker said:
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
Click to expand...
Click to collapse
Might want to hit Thick up and see if he can get you pointed in the right direction.
Sent from my EVO using xda premium
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
talroot said:
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
Click to expand...
Click to collapse
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Ah, I want to say rls29 was recommended somewhere back on that thread. I haven't tried any of them yet though.
cpt.kraker said:
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Click to expand...
Click to collapse
You might need to run the kernel stabilizer in thick's dev host forum... I got the same result as you until I flashed th stabilizer...
Sent from my EVO
I very thoroughly apologize if this has been asked and discussed before, but apparently my search skills aren't the best. Anywho, her's the issue.
I've used a number of different ROM's since I first got my DNA back in January. I've used older Tranquil releases. But anything after 2.1 I believe it was, I haven't had WiFi. I have it just fine with all other ROM's. But no matter what I do for Tranquil (even up to and including RLS 4.2), there's no WiFi connection. It says it's trying to find sources or something and eventually errors out. I have no idea what the problem is. If I go back to 2.1 or 2.0, WiFi works great. This kind of sucks as I really enjoyed the earlier Tranquil releases and would like to continue using them. I'm currently using NOS m7's latest release for 4.1.2 (couldn't get their 4.2.2 release to work for some reason, just sat at the HTC screen for over 30 minutes, even after wiping the entire phone and attempting to sideload).
Anyway, if someone can tell me how to get WiFi to work on Tranquil releases after 2.1, that would be awesome. And again, I apologize if this has been covered before. I tried posting in the official thread but my lack of post count keeps me from doing so.
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
thatotherguy.. said:
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Attempting to get the 2.06 update and then reunlock at the moment, but it's not recognizing the phone in Fastboot. Recognizes fine when it's on, but not Fastboot.
aweber1nj said:
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
Click to expand...
Click to collapse
It does it right from the beginning. Any other ROM and my WiFi network shows immediately. Any release past 2.1 and no WiFi at all.
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
thatotherguy.. said:
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've used this same cord to ADB push and sideload while in Recovery before. Plus it reads just fine when the phone is on as normal. Wouldn't that make it fine? (Note: Not being sarcastic or anything, genuine question. I know how things can be misinterpreted over the 'net so I kinda like to point out how I mean things.)
Edit: I got it to work so far. I'm reflashing back to complete stock now. Apparently a driver wasn't installed for it to be detected in Fastboot. I'll post back after I get back to stock, completely update to newest, and reflash Tranquil RLS4.2.
So I got everything installed, running again, latest updates, reunlocked, TWRP back on, flashed RLS 4.2... No WiFi still... What am I doing wrong here?
Edit: NOS M7 3.0.4 is doing the same thing it was before, also. It's not even getting passed the HTC screen, no matter how long I let it sit. This is quite frustrating. I put M7 2.0.3 back on and everything works as it should. Anyone have an possible solutions?
Do you upgrade your firmware?
Sent from my HTC6435LVW using Tapatalk 4 Beta
It was upgraded to 2.06 when everything was completely stock..
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
matthall9815 said:
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
Click to expand...
Click to collapse
Other than being rooted with the custom ROM, it's whatever the normal S is (can't remember off the top of my head). I rooted and tried the Moonshine thing but it never took (on stock 2.06) so I just went through and reunlocked with my original packet from the HTCDEV website and went about things that way.
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
matthall9815 said:
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
Click to expand...
Click to collapse
You're right. My battery life has been absolutely terrible. I can get maybe 6-8 hours until I'm at 30% or under, and that's not doing anything. Much less if I actually want to do anything with the phone. I'll give those two links a look. Thanks. :good:
Edit: So, I've noticed it's now S-On and the kernel isn't showing on the device. I copied the .zip over to the main directory where I always do, and it's not showing on the phone. But it shows just fine in Windows.
Edit again: Got it to flash using Sideload. Before I do anything else, is it okay to now flash RLS4.2 and see if WiFi works? Now that that's on there, it should be good, right? Or do I need to flash RLS4.2 and then reflash this kernal?
Yet another Edit: It took me a while, but I noticed a LOT of things were missing on the phone after flashing the 2.06 kernel. The one that made me notice was FaceBook. And Google Play Store wasn't there anymore, either. I've reflashed to Digital Dream 2.2 and everything is back to normal. This is really frustrating.
Pm me when you're working on this again I think there are a couple things that are confusing.
Sent from my HTC6435LVW using Tapatalk 4
I finally got it to connect.
I was running DigitalDream 2.2 while trying to figure this all out. I ended up getting S-Off and reflashing. For me to S-Off while already on DigitalDream 2.2, I used the first part of the Mooshine Method (downloading their 2.06firmware zip file, flashing that, rebooting) then used the FacePalm method. That successfully got me S-Off. I noticed that even on DG2.2 after that, I had no WiFi. So I decided to try flashing Tranquil 4.2 and now I have WiFi working. Hope this helps anyone that has the same issue I did.