Phone reboots and gets stuck on "HTC Inc" bootscreen - Droid Incredible Q&A, Help & Troubleshooting

I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!

al2x said:
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
Click to expand...
Click to collapse
This used to happen with me on OMGB, its one of the reasons I switched to CM7. When I rebooted it used to get stuck on the splash screen. Mine, however, would work after a battery pull. I'm not sure, I'd try a fresh install, if that doesnt help, try out CM7, its a pretty stable.

Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!

al2x said:
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
Click to expand...
Click to collapse
I'm not saying thats 100% the case. I'm just saying that used to happen to me when I ran OMGB. I couldn't find a fix, so I just switched ROMs. I don't think CM7 has a just stock gingerbread look. But how can you not like all the features they packed into it?

AOSP + SD
Perhaps try flashing a Sense ROM and see if the issue persists.
Why?
AOSP ROMs interact quite a bit w/ the SD card. So, if there are issues w/ the SD card, the Sense ROM may not present as many funky issues.
After that test, I'd try another SD card and see if the issue persists.
If a different SD yields no wonky stuff, the answer was faulty SD card.

continual spontaneous reboots
I have the same issue. I was using CM6.1 I think and it's been fine for awhile and then it just started spontaneously rebooting. I can no longer get into Clockwork, all I can do is hold volume down and power to start it and from there, nothing will start the phone. I get the HTC spash and after about 3 seconds, it reboots and gets stuck in that cycle. Nothing has really changed and it rebooted on it's own to start the problem.
So, it's not like I installed something and rebooted. I'm interested in hearing if others are having the issues and what exactly their thoughts are.

Related

Dark Dream locked up my phone, how to uninstal?

Ive been running CyanogenMod V4.0.4 for a while now with No problems
last night I decided to Install a theme with the CM updater and went with Dark Dream
everything seemed fine till about 12 noon today
In those 2 hours I lost 3g and can only get on edge
Rebooting fixed this for a short while. Then it was stuck on edge again
rebooting took forever and it was still stuck on edge.
then the phone rebooted itself about 3 times randomly
Now i cant get the phone to boot past the G1 screen
any ideas? I do have a nandroid backup from last week and even though thats easy I am hoping i dont have to do that
Thanks in advance
I forgot to add that it is the latest stable release of the theme from the CM updater
and i cant boot into recovery mode, it is just stuck on the G1 screen
basically, if you flash a theme, and then want rid of that theme, you flash over the current cm your running. so if you still have it, try flashing it over the top.
if not, nandroid restore.
double. pardon my dust
p.s there is a new cyanogen mod out, id upgrade to that if i were you.
isnt the newest CM still experimental ?
at any rate My phone is stuck on the G1 screen and i cant get into recovery
Ok, went away while the Phone was stuck on the G1 screen
battery died in a hurry, plugged it in and it booted fine
Still on edge but once charged ill see if i can get a better signal
I guess I like the theme enough to give it another try as i dont see anyone else with these issues
and for the record i did try the latest CM experimental build 4.1.999
and it was BLAZING fast. the only reason i went back to 4.04 is because I couldnt get my browser and market working even with a wipe following the CM steps
I may try to wipe the SD card and re do the partion if things are still not stable with the theme and 4.0.4 .. thank god for nandroid haha
Yea- this doesn't surprise me, as that theme messed up my phone bigtime- try to pull the battery, do a "recovery boot" when you put it back in, and see if you get there after that- chris
Hmm, well the phone seems fine for now
but you have me wondering if it will happen again
I couldn't get the phone to go into recovery, I think i got lucky after waiting a while
I guess I will look into re doing the partion and trying 4.1.999 again
I really loved the speed and smoothness and if i can get market and the browser working like everyone else it will be great. i can wait on bluetooth to work as i dont use it much lately
this should be in the Q&A thread
but anyways i would flash cyans latest release if i were you
I don't understand. This theme works fine for me! Never had any trouble with it.
Just like when some people have an issue with a rom that others dont
I imagine it could be any number of reasons.
now i am running 4.1.9.9 and though i had issues with the phone turning off and freezing on the G1 screen it hasnt happened in 4 days and i havent done a thing
You have to remember that sometimes the .zip files simply get errors for some reason. If you read around you will find a number of people who try and install only to get an error, then then restore via nandroid and re-download the file and re-apply and it works. If you are using the browsers google chrome, Safari, or EI, I would say switch to firefox when it comes to downloads of .zip files. I have noticed that I have 100x more errors when not using firefox.
i had dark dream on 404 before and it slowed my phone down so much i didnt even care for the theme anymore. seems all cyanogen roms WITH a theme die. except his his older ones.

Help rooting....stuck looping....

Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
riley614 said:
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
What is your HBOOT version?
Hboot 0.92
Radio 2.15.00.07.28
Clockwork 2.5.1.2
Un.Rev. 3
Un.Rev. Forever
Incredibly re-engineered 2.2
Update -
Managed to get Un.Rev. to install with cw. And installed a Rom. Now I still get random reboots. Everything will be fine...ill update and install a bunch of apps. and I can use the phone for a while. Then all of a sudden it reboots over and over. To get it to stop, I have to re-do everything. Wipe cache, wipe dalvik, wipe battery stats, data/factory reset. I get an error after dalvik clear though "can't mount /dev/block/mmeblk12 (file exists)"
That puts me to square one.
Everything will be ok and then.....reboots...randomly at different points. sometimes right away and some times after an hour or two. No real pattern. I have a gut feeling it has to do with onboard memory?
Are you overclocking? What kernel are you using?
Try installing a different kernel, make sure it is a sense based kernel as you are using a sense based rom.
You can pick one from here - http://forum.xda-developers.com/showthread.php?t=866736
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
I had the exact same issue when i received my refurbished phone. It is not uncommon that these issues - and others, will occur. Even before rooting i was having the issue.
I did notice that it will happen when i pushed the phone a bit, like talking and trying to download something from the market at the same time.
My suggestion is to unroot, everything stock, test the phone and see if it happens again. The Verizon representative tried to reset the phone and it started boot looping right in front him! And then they order another refurbished phone, which also had issues. Long story short, they gave me a new phone after i begged. (thank u VZ local store, which btw i sent a few customers your way )
According to some inside people i talked to, the 3rd party companies (or individuals) that fix these phones do a terrible job at it and the Verizon stores see quite a few people everyday with similar issues. I have no way of verifying this, just what i was told.
riley614 said:
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
Click to expand...
Click to collapse
I would still try another kernel first, HeyItsLou or Ziggy IMO. If you still have the problems then, flash back to complete stock and take it to Verizon.
Yea, ill give that a try. If I have no luck, ill send it back. After unrooting of course.
Sent from my ADR6300 using XDA App
Riley, were you able to fix it? I'm really interested in some analysis of the problem and investigating issues with refurbished phones boot looping. Someone else just posted a similar problem.
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
riley614 said:
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
Click to expand...
Click to collapse
Sorry to hear that, as i said i had the same issue and i had to get another one. if you get a second "lemon" refurb go to Verizon and talk to a manager. They might do an out of the box replacement and put it in the system as defective under warranty. Good luck.

[Q] Looping Boot Image

Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Have you use amo-ra?
Sent from my evil evo!!
rsjc741 said:
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Click to expand...
Click to collapse
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
klquicksall said:
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
Click to expand...
Click to collapse
Thanks
I should face-palm myself. I just read the sticked post and I'm going to try some of his suggestions. He pointed out why cyanogenmod wouldn't work.
My whole consept of the framework went out of the window, and now I think of it more like a standard linux distro, in terms of kernel->ROM relationship.
I don't think I need to have a custom kernel for the Gingerbread beta-4, but i'll look it up just in case... Though I don't have a clear idea on how to flash that.
And to the person 2 above, im using Cyanclockwork. For whatever reason, I like its design verse RA recovery. I might try RA recovery just to see if it works better, as everyone has said it does.
I think i needed to clear all my caches and then load the ROM.
So I did a wipe of everything (data, darvik, cache) and trying to install the GB ROM. My boot screen is *still* looping. Do I need to get another kernel? Is it like flashing a ROM? Where are they at? I didn't see any in the software section...

HTC EVO stuck in BAD boot loop.. need HELP

I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.

[Q] Remove Lag?

First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
EVoorhees said:
First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
Click to expand...
Click to collapse
yea that problem happens when some one flashed venom ROM or other sense based roms....check out my antivenom super wipe thread ....as for solution there really isnt one...buuut a good way to stop it from happening...everytime you do a backup or flash superwipe...every now and then just for the proventitive maintenance i super wipe aleast onces ever few weeks...doing that i havent had ANY death lag since the dawn of it
EVoorhees said:
First off, hi again XDA.
Second, I've been having this problem for a while now... One day, I was working on something and I was running Team PSYCHO's JB ROM (...or someone close to that name) and all of a sudden my phone said "Shutting Down..." and turned off. I went home, plugged it in, left it charging for about three or four hours. I go to turn my phone back on and find out it's lagging out all the way. I thought it was just a root issue that happened because no matter how many times I attempted to take the battery out and restart it, it didn't want to stop lagging. I wiped the cache, almost everything (I didn't wipe the /system because I wanted to get something off there if I could, and yeah....that didn't turn out so well.) So, I go to unroot my phone and find a PGIMG32 file from XDA that everyone was using, just to be denied by my phone saying that the radio/firmware is higher than the one trying to be installed, aborting, so-on-and-so-forth. Tried doing CM9, lag. Tried going back to the JB ROM, lag-city. Decided to go to CM7, it worked fine (for the most part, still had some lag here and there.)
So, I switched back to MIUI and Venom (I now use the Venom wiper everytime I switch a ROM) to find out that those two were still laggy. Currently, I am sitting on MIUI and I am going to try that INC2 respiratory that someone put up (100% forgot the name, but saw the thread.)
My question is, does anyone know how to get rid of this lag?
Thanks again.
P.S. I don't get an upgrade until March, so if it could just last me out until then.
Click to expand...
Click to collapse
Try connecting your phone to your PC, mounting as disk drive so the PC reads the card and not your phone. If the lag goes away then it could be something with the SD card maybe. Don't unroot yet before researching. Be sure you are checking md5 before flashing to ensure a good download. If you narrow down to a SD issue, remove any files you need, and wipe and reformat the card.
Sent from my Incredible 2 using xda app-developers app

Categories

Resources