I'm using the Aokp m6 rom but from my understan
ding, it doesn't come with a recovery? it says I have stock recovery in my recovery tools apk. I have the glitch kernel/recovery that I use on M5 but last night when I wiped my cache/dalvik cache it threw me for a bootloop and I apparently didn't have any recovery installed? I have the twrp open script recovery that I can use on the m6 rom but I like all of the extra options on the devil recovery. thanks in advance!
are you using the old official M6 with Glitch or the Devil M6? you might want to use the devil m6 build if you want devil
Well I have the Milestone 5 that is glitched and the milestone 6 that comes with the devil kernel but I'm looking for the devil kernel/recovery that's in a zip file that I can flash through cwm recovery like I have for aokp m5 which contains the glitch recovery and what not. Because when I did a factory reset on the aokp m6devild rom,i was stuck with no recovery. Or did I just do something wrong?
GarrettVW67 said:
I'm using the Aokp m6 rom but from my understan
ding, it doesn't come with a recovery? it says I have stock recovery in my recovery tools apk. I have the glitch kernel/recovery that I use on M5 but last night when I wiped my cache/dalvik cache it threw me for a bootloop and I apparently didn't have any recovery installed? I have the twrp open script recovery that I can use on the m6 rom but I like all of the extra options on the devil recovery. thanks in advance!
Click to expand...
Click to collapse
Best of my recollection, that version came with the cwm recovery but the devil kernel build inside.
are you talking about this tool? http://forum.xda-developers.com/showthread.php?t=2334554
as far as I know, most of those type will not work for the fascinate,,, but I have not looked at that one,,,
our recovery is also packaged with the boot partition and cannot be flashed/installed separately, which is how most of these tools work.
going off my menory this should be what you want...
Devil3_1.6.1
.zip for install thru current recovery
Devil3_1.6.1_zip_fas_CFS_BLN_CMC_20120930.zip
http://www.androidfilehost.com/?fid=23043426517778454
.tar for install by ODIN
Devil3_1.6.1_tar_fas_CFS_BLN_CMC_20120930.tar
http://www.androidfilehost.com/?fid=23043426517778453
.
thanks hhp, that's what I was looking for. Actually it was a collection of old roms you uploaded that I've been getting everything from. Am I crazy for wanting to use ICS? I read reports of people loving their jb roms on their fassy and claiming 2days without charging but I literally have to walk arounaround with my charger on every jb rom I've tried. Do you have any suggestions on whether I should use gb or ics for the most battery life? I don't care so much about tweaks anymore, I just want my phone to not die on me everywhere I go. And is glitch or devil better for battery life?
GarrettVW67 said:
thanks hhp, that's what I was looking for. Actually it was a collection of old roms you uploaded that I've been getting everything from. Am I crazy for wanting to use ICS? I read reports of people loving their jb roms on their fassy and claiming 2days without charging but I literally have to walk arounaround with my charger on every jb rom I've tried. Do you have any suggestions on whether I should use gb or ics for the most battery life? I don't care so much about tweaks anymore, I just want my phone to not die on me everywhere I go. And is glitch or devil better for battery life?
Click to expand...
Click to collapse
yay i'm not alone. been using ICS for a while now and I myself have been trying different things for.. gee some time. right now i'm running the official milestone 6 (glitch, devil doesn't like my phone) and i've been trying to get decent battery life for a while.. trying calibration crap even though that's been confirmed a myth, wiped battery stats too many times to count, ugh... i did get 2 days of moderate usage at one point with AOKP.
but yeah as i said devil doesn't like my phone so i'm stuck (even though glitch is amazing). i'm not too much of an overclocker and i haven't even changed governors and i get 2 days of light usage usually.
how much battery do you get? apparently you use gummy.. i've never been a big gummy person. just my 2 cents
@GarrettVW67 I really got nothing for you on that one. I get 4-6 hours of heavy usage. And I'm 98% time beside a power outlet and usually less than 2 hours without charging access.
And I like having compatibility with all the current apps
hhp_211 said:
@GarrettVW67 I really got nothing for you on that one. I get 4-6 hours of heavy usage. And I'm 98% time beside a power outlet and usually less than 2 hours without charging access.
And I like having compatibility with all the current apps
Click to expand...
Click to collapse
ics is compatible with all the current apps. hell, gingerbread is still compatible with most things these days.
Related
I am a noob & have had issues with UVJK6 charging my battery. Sometimes it does not charge when the phone shows it is charging. Can I just use CWM to flash from this to obsidian?
Thanks for any help.
rpolito73 said:
I am a noob & have had issues with UVJK6 charging my battery. Sometimes it does not charge when the phone shows it is charging. Can I just use CWM to flash from this to obsidian?
Thanks for any help.
Click to expand...
Click to collapse
im assuming you mean the JK6 modem....
you MUST use ClockworkMod Recovery to flash anything....
download the JK6 modem from the Team Whiskey website....put the zip on the root of your sd card....reboot into recovery and select install zip from sd card...
i doubt if that will fix your charging problem...
The charge problem only happens about once a day. I pull the battery for about 10 mins then its fine. I'm not sure about the kernel thing.
My phone reads Firmware version - 2.2 Baseband version T959UVJK6 Kernel version 2.6.32.9 Build number FROYO.UVJK6
Is there a place I can learn more basic information about these mean?
I really have no knowledge about kernels, basebands or builds but know enough to look on here to understand how to use CWM to flash to what I thought was the stock froyo rom.
I like it and the only prob is that it makes me nervous with the daily prob with the charge. Everything was fine until about 4 days after I flashed.
It has the lightning bolt on the battery, says charging on Battery Status Pro but it actually loses %....
I just started using Launcher Pro - could this be it?
rpolito73 said:
The charge problem only happens about once a day. I pull the battery for about 10 mins then its fine. I'm not sure about the kernel thing.
My phone reads Firmware version - 2.2 Baseband version T959UVJK6 Kernel version 2.6.32.9 Build number FROYO.UVJK6
Is there a place I can learn more basic information about these mean?
I really have no knowledge about kernels, basebands or builds but know enough to look on here to understand how to use CWM to flash to what I thought was the stock froyo rom.
I like it and the only prob is that it makes me nervous with the daily prob with the charge. Everything was fine until about 4 days after I flashed.
It has the lightning bolt on the battery, says charging on Battery Status Pro but it actually loses %....
I just started using Launcher Pro - could this be it?
Click to expand...
Click to collapse
it could not be LauncherPro....alot of things could be the cause of a battery drain....simple things like changing your wallpaper to a darker/black one can improve battery life.....reconditioning your battery can reduce battery drain....one of the main causes of battery drain is the modem...the JK6 is the battery killer in my eyes....try a battery recondition...if all else fails you could Odin back to stock and see if that solves your problem
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/
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
Guyz I recently install jb v5 with phantom kernel. I had some problems with led,sound and battery.. I was charging the phone everyday..I install v4 but same any help?
Sent from my ST25i using xda premium
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Re
MagicMagicD said:
Hi,
First things first, don't panic!
I have the same setup as you and I'm currently @ 67% after 24 hours so it definitely isn't a problem with the ROM.
Did you follow the instructions from the first post?
Flash custom kernel Phantom[1.0.7]-Performance-CWMTouch
Boot to recovery and flash ST25i_6.2.A.1.100_unofficial.zip..
Full wipe recommended when flashing the first time.
Wipe caches when updating
Reboot to system
Wait for POWER OFF button when you did full wipe if not then just turn off
Flash latest Phantom kernel
Reboot to system
Everything should work now
For point 3/4 above, what did you wipe?
Also what ROM did you have on your phone previously?
Click to expand...
Click to collapse
Let me tell you exacly.. I had a problem with the phone .. About led so i decide to change the version and use v4 .. But i recharge it full and i had it on my desk w/o using it for 3 days. The battery was at 40 % and i use it only 1 time for 1 call .. Nothing more...
I flash the kernel wth flashtool. Wipe everything.Install Jb wipe cache and then use the phone. Wait for power off buttom then open again..
I don't know what is the recovery mode btw.. I search it but i didn't find something usefull .I still don't know if i will use Jb Unofficial yet...
I haven't tried v4 of that ROM but I can say for sure that the LED bar doesn't work very well on V5, at least nowhere near as well as DevSwift1's V3 ROM with the latest Phantom kernel.
It does seem to be quite good on battery though; I'm on 1 day, 12 hours uptime with 47% charge left, although I don't use it a whole lot to be fair -- mostly just for music during the day.
I guess you must have used a recovery to flash the ROM zip file... as in CWM (ClockWorkMod)? The Phantom kernel comes with one installed; 1.0.7 has CWM Touch whereas 1.1.0 (the latest version) has a non-Touch version.
The only thing I can suggest is that you try reflashing it again; I'll tell you exactly what I did...
Using Flashtool, put Phantom kernel 1.0.7 on the device and then go into CWM Touch by restarting the phone and repeatedly pressing the Volume Down button when you see the LED bar light up.
Once there do a wipe of data and cache and then go in to the advanced menu and wipe Dalvik cache too.
Next go back to the main CWM menu and flash the zip, then reboot and wait for the phone to start up (should take a while).
Once it has settled down restart it and let it start up again (should take less time)
Finally, use Flashtool to put the latest version of the Phantom kernel on, restart and you're done.
With all that said, I expect I'll be going back to V3 of DevSwift1's JB ROM this weekend as although it's not quite as smooth as pipi14's ROM, the LED bar does work a lot better and for me that is quite important.
Good luck, keep us informed how you got on.
A
Thanks a lot for the informations mate. You help me a lot . But i'm the only one who have this problem with led and battery?
What Jb version you suggest me to use? (link )
What kernel you suggest me to use ? (link)
Any other good apps who will help me ?
Again Thanks a lot .
Btw what is "recovery flash" . I read at pipi's site flash in recovery. What exactly is this?
I've personally tried two Jelly Bean roms:
DevSwift1's V3 ROM (it's now up to V4 which is based on an Xperia Go firmware and has lower-res graphics and some other issues compared to V3, which was ported from the Xperia P).
link
pipi14's V5 ROM (which you have tried and are currently using.)
link
As for kernels I've only used the one that came included with DevSwift1's V3 ROM and Phantom kernel's from v1.0.7 upwards. I know that a number of people have used the Experimental v8 kernel with success on JB but it looks to be more complicated than Phantom.
Experimental v8 kernel
Phantom kernel
From my own experience I will say that I think pipi14's V5 ROM is smoother but I can't get the LED bar working how I want and although it still had a few issues on DevSwift1's V3 ROM it was definitely better.
As far as apps go, it seems the fewer apps the better if you want to stick with JB on your Xperia U -- it doesn't have enough memory and the more apps you have running the worse it will be. Task killers will not help and will probably end up draining your battery more than they help.
A custom recovery is basically a low-level program that you can use to flash new kernels, ROM's and other things on to your phone. ClockWorkMod (CWM) is the most common but others are available. You must have used a recovery to flash JB to your phone before, and if you have a Phantom kernel it comes bundled with one. To get in to recovery mode you need to restart your phone and then press the Volume Down button when you see the boot logo (e.g. Phantom).
a
That's the reason why sony will not send the updates to official JB version .
I will not use Jb now . If they fix it about the bugs i will use . Thanks for the info mate
Btw i use something custom like tera check this http://forum.xda-developers.com/showthread.php?t=2141726&highlight=tera
It's nice based on the ICS w/o so much battery drain and leds bug. I suggest you use this .
Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
loswr86 said:
Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
Click to expand...
Click to collapse
Answers to your first two questions:
1) After (although it S-ON it technically shouldn't matter)
2) No
Here are some tips, this could be as simple as a battery going bad, i consider a replacement one, either original HTC or Laza would be my recommendation. Also, I would consider going S-OFF, then going through @REV3NT3CH's full downgrade/upgrade guide from start to finish, this seems to be fix for many "odd" issues in the Rezound, I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
acejavelin said:
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
Click to expand...
Click to collapse
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
loswr86 said:
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
Click to expand...
Click to collapse
Always use the kernel that comes with a ROM, until you know it's stable and unless you have a good reason to switch... it is the best match to the ROM and the benefits you get from another kernel are generally marginal at best unless you need a specific feature that is not included in the ROM's kernel.
Proper sequence when installing a ROM when S-ON would be to wipe everything but external SD, then flash ROM, immediately reboot into bootloader and start fastboot, flash the boot.img with "fastboot flash boot boot.img" then reboot. Any other sequence could give questionable results.
Using Titanium backup to restore information in between JB and KitKat (either way) is not recommended, even with root access TiBu has issues restoring into /system in KitKat. It is highly recommended to reinstall all apps from the Play Store and use something like SMS Backup & Restore to handle text message migration.
I would again recommend a new battery, and going S-OFF especially now that the "wire trick" is no longer required using Rumrunner or Firewater S-OFF, then going through the downgrade/upgrade process I mentioned earlier.
So I have been unsuccessful at getting Windows drivers working for my rez. HTC sync and Windows used to identify it, but after I originally rooted it back in Dec, I wiped my laptop clean and set up a dual boot. Since then I haven't been able to get HTC sync to identify the phone, and ADB only works if I am in the TWRP or bootloader. Same with mounting and moving files, recovery only. Since the rumrunner S-OFF exploit needs me to be in Android, I'm in a pickle.
Things I have tried:
Current HTC sync software (Doesn't recognize the phone)
Downloaded and installed the driver from the Rav3nt3ch guide mentioned earlier
Also tried the old version of HTC sync that is mentioned in the same article
acejavelin said:
I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
Click to expand...
Click to collapse
to make sense of it. the reason it works is through some flashings or wrong deleteion of files the files that are integrated in system that a ROM does not have these RUU.exe files and OTA (ph98img.zip) files do have and repairs the phone to its neccesary needed state again. a good example to prove it is a typical rom is about 160mb in size and only contains bare necessities really..where as the ruu or ota is usually around 600mb in size and also full flashes the phone to proper partitions and such...as stated in my guide be sure to let phone fully boot and go through first setup of those particular roms....some people skip this step thus not activating their verizon service
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
loswr86 said:
So I have been unsuccessful at getting Windows drivers working for my rez.
Click to expand...
Click to collapse
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
REV3NT3CH said:
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
Click to expand...
Click to collapse
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
loswr86 said:
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
Click to expand...
Click to collapse
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
REV3NT3CH said:
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
Click to expand...
Click to collapse
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
loswr86 said:
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
Click to expand...
Click to collapse
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
The battery power can not be recognised by the phone?
REV3NT3CH said:
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
Click to expand...
Click to collapse
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
loswr86 said:
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
Click to expand...
Click to collapse
eh...always search the threads bud...all of what you need and updated is here
---------- Post added at 07:50 PM ---------- Previous post was at 07:49 PM ----------
Hermosa said:
The battery power can not be recognised by the phone?
Click to expand...
Click to collapse
on older twrp or miscompiled recoveries it will simply just read as 66% and stay there....a good example...phils touch needs this battery reading part fixed as well as it shows 66% for battery currently
6.0.3.6 installed. Hopefully this oversight is what it takes to improve my experience with android modding. Thanks for your help fellas.
I don't remember having this much trouble modding my old HTC tilt back in the day.
Flashing clockworkmod 6.0.3.6, reinstalling CM 11 via CWM and then flashing the boot.img seems to have fixed my battery issues. After a few days of use, battery is holding charge much better. A note on what I think I was doing wrong, for others:
-I had originally flashed TWRP 5.X
-Then I followed this article explaining how to install custom roms whlie s-on
-I then loaded the various custom roms via the above method with the CWM 6.0.3.1 (Listed on their website)
-Chaos insued
Don't do this.