I managed to unlock the bootloader and root the phone using the All-In-One-ToolKit. I'm running Viper ROM, after installing the ROM i installed the Kernel "Stock DSB System Write Boot.img" from their instructions. After i downloaded and extracted the Kernel "HTC DNA LK_DNA 0.9.4" I flashed the boot.img trough the Toolkit and then flashed the modules.zip folder trough Recovery Mode. I have two noob questions =/
1) Did i flashed the Kernel Correctly?
2) My current battery is at 92% with the History showing [1h 14m on Battery] Is it normal that i used up 8% already in such a short amount of time? I haven't used the phone at all after i charged it, no txt,calls,facebook,internet....nothing.
Painkiller006 said:
I managed to unlock the bootloader and root the phone using the All-In-One-ToolKit. I'm running Viper ROM, after installing the ROM i installed the Kernel "Stock DSB System Write Boot.img" from their instructions. After i downloaded and extracted the Kernel "HTC DNA LK_DNA 0.9.4" I flashed the boot.img trough the Toolkit and then flashed the modules.zip folder trough Recovery Mode. I have two noob questions =/
1) Did i flashed the Kernel Correctly?
2) My current battery is at 92% with the History showing [1h 14m on Battery] Is it normal that i used up 8% already in such a short amount of time? I haven't used the phone at all after i charged it, no txt,calls,facebook,internet....nothing.
Click to expand...
Click to collapse
Only thing you didn't mention is wipe cache and dalvik cache before or after modules flash. Wonder if battery drain due to initial Google synchronization, etc. If that usage persists, it's definitely abnormal, barring bad reception, etc.
yearn2burn said:
Only thing you didn't mention is wipe cache and dalvik cache before or after modules flash. Wonder if battery drain due to initial Google synchronization, etc. If that usage persists, it's definitely abnormal, barring bad reception, etc.
Click to expand...
Click to collapse
I wiped the cache and dalvik after flashing the modules. So I went home yesterday and flashed the boot.img provided in the Viper thread, then flashed the boot.img from LK followed by the modules and a wipe of the cache and dalvik cache. Seems to be running fine now, battery is currently at 31% with 9h 34m on battery. That should be good battery life right?
Check the thread in DNA development original, there is screen shots of what people get with their battery, that way u can compare.
droid DNA
Painkiller006 said:
I wiped the cache and dalvik after flashing the modules. So I went home yesterday and flashed the boot.img provided in the Viper thread, then flashed the boot.img from LK followed by the modules and a wipe of the cache and dalvik cache. Seems to be running fine now, battery is currently at 31% with 9h 34m on battery. That should be good battery life right?
Click to expand...
Click to collapse
What type of usage did you do in the 9.5 hours? There are pics of under the LK thread in the DNA original dev section. Hope things work out.
I have on it the LK 0.9.4 with the LRS GSM Rome and I am very happy with it, but if you do nothing and just 9.5 hours get along then something is wrong, so I'm from even 20-24 hours and make it something Internet, XDA app, SMS and calls.
On the night in standby do I need only 6-8%
Related
Just to report that for me i couldn't get network(no service) signal for 1 or 2 minutes even after crashing the system server
http://forum.xda-developers.com/showthread.php?t=1037855
I can't post in there yet, if someone can do that for me, i appreciate that.
I don't if it is connected but the signal showed up when i went to the system update on settings.
Settings> System > About Phone > System updates> Then it crashes in here and FC
Once it gets back to the home everything gets alright.
The rom seems a bit laggy yet, but maybe is something configuration or procedure i did wrongly.
Also from time to time, the screen gets lighted (bright) and after that dark again when i am not using it, not even near.
Just flashed it 20min ago.
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
what I did and it worked for me was flash TripNMIUI_BTS_02.zip first, then I rooted it again and installed xRecovery. I then flashed bb.52, booted into xRecovery, cleaned the cache, dalvik, battery, etc. and then flashed this ROM. Do a system crash and once it reboots it should pick up a signal within 10 sec.
aval1392 said:
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
Click to expand...
Click to collapse
As i said before, after the last FC in the settings, it did work normally i have the rom working perfectly fine, what i wanted was to someone that can post there to do this for me, or that trip could see this to add to the install steps so people can try also what worked for me may work for others.
ironjose said:
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
Click to expand...
Click to collapse
I normally try every rom for one or two weeks at least so i can be sure which one is better, so far i've tried one based in this rom, but is wasn't faster than TripNMIUI version.
In TripNMIUI i got 36,5 in Linpack without using any APP2SD tool, also got in Quadrant from 1100 to 1200.
The other roms i tried hardly passed up than 32k in linpack and normally near 900 in quadrant.
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
First off this is the wrong section
Second yea u need to always wipe everything when switching to a new ROM. I use Synergy and the first boot will always be laggy. Synergy let's your Google account download all the apps that u previously had which really slows the phone down. What I'd do is wipe EVERYTHING. Then flash the ROM again. During setup, only setup your Google account and leave for Facebook or whatever other accounts u set up for later as it may speed up things for the first boot. And then I'd just put the phone down n let it do what it needs to do. Synergy is a fast and smooth ROM. The first boot is always laggy on any ROM that allows Google to auto download previous apps. Hope this helps
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App
wetbo529 said:
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
Click to expand...
Click to collapse
Follow these procedures:
- Normally you'd perform a nandroid first after flashing into clockwork recovery, but I don't know that you'd want to do that since the ROM is running poorly; your call (I would anyway)
- Wipe Data I always do this, no matter what. That might sound extreme, but I've never had one issue with any of the three android phones I've owned.
- Wipe Cache
- Wipe Dalvik
- Flash Rom
- Flash Radio (if necessary)
- Reboot
Play with the ROM for a while before you flash a different kernel. You might find one of two things: 1) The kernel that came with the ROM is plenty fast and does everything you need, which leads to 2) The kernel you flashed originally could be the cause of the slowness.
Ir's possible the ROM is the issue, so following the above procedure will rule everything else out. Let us know how it goes.
i have a serious random reboot problem when my phone is in idle. here is what i did...
while on Alien v.3 i .sbf flashed the 1.97.00 radio and then flashed Kholk's kernel
then...
in romracer's CWM:
wiped dalvick cache
wiped cache
wiped data/factory reset
flashed Alien v.4
reboot
skipped blur setup
waited 10 minutes
went through set up (reset apn to default, added gmail account)
reboot into CWM
wiped dalvick cache
wiped cache
flashed Alien theme 4
reboot
restored apps
reboot into CWM
wiped dalvick cache
wiped cache
flashed Kholk's kernel
reboot
i started getting random reboots. i cant figure out what the problem is. i tried flashing a different theme, and still got reboots. tried flashing the stock kernel and still got reboots. i tried re-flashing Alien v.4 and not restoring any apps and still got reboots. argh... any ideas?
can the radio cause a reboot issue? i really dont think its a ROM/Theme thing since noone else seems to be reporting the same problem... am i noobing this whole mod process?
this happens to me too. Turn your wifi off when you aren't using it. Mine only reboots when its in standby with wifi on
fischwrap said:
i have a serious random reboot problem when my phone is in idle. here is what i did...
while on Alien v.3 i .sbf flashed the 1.97.00 radio and then flashed Kholk's kernel
then...
in romracer's CWM:
wiped dalvick cache
wiped cache
wiped data/factory reset
flashed Alien v.4
reboot
skipped blur setup
waited 10 minutes
went through set up (reset apn to default, added gmail account)
reboot into CWM
wiped dalvick cache
wiped cache
flashed Alien theme 4
reboot
restored apps
reboot into CWM
wiped dalvick cache
wiped cache
flashed Kholk's kernel
reboot
i started getting random reboots. i cant figure out what the problem is. i tried flashing a different theme, and still got reboots. tried flashing the stock kernel and still got reboots. i tried re-flashing Alien v.4 and not restoring any apps and still got reboots. argh... any ideas?
can the radio cause a reboot issue? i really dont think its a ROM/Theme thing since noone else seems to be reporting the same problem... am i noobing this whole mod process?
Click to expand...
Click to collapse
try version 4 of alien. It has less bugs, faster and better performance.
Voelker45 said:
try version 4 of alien. It has less bugs, faster and better performance.
Click to expand...
Click to collapse
i was using Alien v.4, but it turns out it wasnt an issue with alien...
i think i figured it out (for those of you who care!)
I hadnt correctly removed the old install-recovery.sh file, so i think that may have resulted in incorrect flashes/installs... so i removed it, then flashed romracer's CWM
also, i sbf flashed this 4.5.91 Radio: http://forum.xda-developers.com/showthread.php?t=1159505&highlight=radio
between those two things, i seem to finally be on a fully functional, seemingly bug-less Atrix running Alien v.4 + Theme on Kholk's kernel and the 4.5.91 radio!
thanks for sharing.
Since installing Alien 4 on the weekend, I've had two spontaneous reboots. Both times were while playing music with the screen off and wifi on. Could be the music app, but I didn't have any reboots in Alien 3 or the other GB roms I tried.
Sent from my MB860 using XDA App
whenever I flash a new ROM (whatever it is) I get a string of random reboots.
Then after a few days it settles down...... seems to be worse if
a.) playing music
b.) bad data reception <---- this has happened to me on stock when I have 5 bars but there is some kind of data issue with the carrier and I open too many data using apps that all time out and causes some kind of kernel panic BAM reboot
I think my phone maybe has an issue when it first runs apps after a fresh build if its deodexed (compiling the cache etc. or the JIT first run whatever I'm not a dev) as that would explain why it settles down after a day or two.
Well I may have spoken too soon... my phone has rebooted twice, with about 90 minutes between each one, since I took it off the charger.
Sent from my MB860 using XDA App
I have heard that if you restore apps with tibu it causes problems. Try a fresh start with apps and no restore
Sent from my MB860 using XDA Premium App
hate to necro an old thread, but since the kernel has been updated and this issue persists i figured it was relevant...
As others in this thread have discovered, it is an issue with WiFi while the phone is asleep. Particularly reboots the phone when moving in and out of known WiFi reception areas. While I'm now using WiFi much more conservatively and saving battery life, its still a troublesome issue. Has anyone else made any attempts to fix it? I will be trying a few things myself soon.
hello masters, I'm newbie here. I'm using Ultimate HD 3.0.2, yeah I know it fast and have a good battery life, it save my battery so well. but three days ago I got bootloop on my xperia ray device because I made a wrong metode to flash my kernel, then I install new Ultimate HD on my device like the first time I install it. all works fine, but the problem is my battery drained quickly like I'm using the stock ics . Just for unlocking from the locked screen it drains 1-2% of battery. I have follow right intsruction such as wipe data/factory reset, wipe dalvik cache, wipe battery stats, format /system, all changed but the battery life is not. can you tell me how to fix it? I think something's wrong in setting or script maybe. thanks before.
*see an attachment, my phone idle percentage is very low now
I know its a little bit late but here you go
http://forum.xda-developers.com/showthread.php?t=1024867
this might still help you
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app