Develop Bugs

Rooted, Flashed Evo Classic, Loved it... now it keeps rebooting!

I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?

I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.

Did you wipe dalvik? And what recovery are you using?

I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.

Is it rebooting if you don't use that particular app at all?

Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik

Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.

Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.

I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.

Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots

I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.

You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.

Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.

Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you

[Q]Desire Z keeps rebooting after few seconds on home screen

Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you

cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App

could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.

+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd

cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App

I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.

I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.

well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far

Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon

Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve

Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve

the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.

Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve

I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium

Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve

Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve

Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium

[Q] Brick?

Hey guys. I just updated to Wicked Sensations 1.2 from 1.1. I used 1.1 for a few weeks and loved it, naturally I wanted 1.2 when it came out and I read the changelog. So I downloaded it, put it on the ext SD card. Booted to Clockwork Mod Recovery. I did a Nandroid backup. Then I wiped data 3 times, wiped Dalvik cache 3 times, and then installed from zip file. The install went great. I rebooted after it was done and the rom launched fine. I went through the initial setup and restored my Nova Home Screen settings. Then I went to try out the included Wifi Tether app. I launched it, it asked for root access, I granted it. Something didn't work as it was initializing, so I closed it and rebooted the phone, just to make sure all of it's processes were killed and my normal wifi would work normally. On reboot, the phone decided it needed to "Upgrade Apps". So I waited about an hour and it never left that screen. It didn't show me any sort of progress like it had before either when it optimized apps for Jellybean coming from ICS. So I popped the battery out. Now I'm doomed. Stuck on the boot screen with the "SAMSUNG" text with the animated glow effect. I also can't seem to get it into recovery mode to restore any of my backups.
Any thoughts? I'm fairly new to this so don't rule out dumb mistakes. Also, I noticed in the Wicked Sensations 1.2 instructions that I could have upgraded without doing a full data wipe, but it said to do a full wipe and clean install if you had any trouble with the upgrade, so I don't think that is the cause of my problems. Do I need to turn to Odin?

You have a soft brick since you can get up the boot logo screen....time to bust out Odin to save the day.
http://forum.xda-developers.com/showthread.php?t=1941546
Sent from my SPH-L710 using xda app-developers app

Thanks a bunch. I wasn't sweating too bad since I could turn it off and on and see a spark of life in it. Thanks for the link too. I'll confirm success or failure later tonight after a good few hours drive back home.

That fixed it for me. Thanks again.

[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

[Q] Can't boot to recovery, apps and photos randomly deleting

Unfortunately this is one of those please help threads. I have gone back a forth flashing roms trying to find something i like and just having some fun with it. when i finally decided to go back to color os some strange things started happening.
1. I can longer boot into recovery by holding down power & Vol -
2. Apps randomly delete. the icons stay but i get an error message saying the app no longer exsits
3. The photo album will purge all photos after a couple reboots.
This isnt my first android phone or first time flashing roms. I can usually search my way out of most of the mistakes i make but i cannot figure this one out. any help or suggestions would be greatly appreciated.

g2theno said:
Unfortunately this is one of those please help threads. I have gone back a forth flashing roms trying to find something i like and just having some fun with it. when i finally decided to go back to color os some strange things started happening.
1. I can longer boot into recovery by holding down power & Vol -
2. Apps randomly delete. the icons stay but i get an error message saying the app no longer exsits
3. The photo album will purge all photos after a couple reboots.
This isnt my first android phone or first time flashing roms. I can usually search my way out of most of the mistakes i make but i cannot figure this one out. any help or suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I also messed up something to my find 7a and what I did is to go back to all stock. Meaning flash back stock recovery and stock ROM. Then I started to flash back custom recoveries and ROMs. All is fine now.
Hope this fixes your problem too.

tantrums said:
I also messed up something to my find 7a and what I did is to go back to all stock. Meaning flash back stock recovery and stock ROM. Then I started to flash back custom recoveries and ROMs. All is fine now.
Hope this fixes your problem too.
Click to expand...
Click to collapse
I did try going back to complete stock. Thats when the problem actually started happening.
I flashed the stock recovery i downloaded from the oppo forums with fastboot. i then booted into the recovery which is still very difficult to get in to and flashed color os. it takes me like ten attempts before i get in. i then setup my phone for regular use. things seemed normal till that evening. when i tried launching a few apps and received error messages saying app wasn't installed. so i reinstalled them and then it happened again. i also launched the camera app a little later and realized the pictures i had taken were also gone.
When i am able to get into recovery i noticed there used to be a lot more folders under install zip from sdcard. now i only have maybe 5 to pick from when before there was probably 10 or more.
Thank you for your suggestion.

g2theno said:
I did try going back to complete stock. Thats when the problem actually started happening.
I flashed the stock recovery i downloaded from the oppo forums with fastboot. i then booted into the recovery which is still very difficult to get in to and flashed color os. it takes me like ten attempts before i get in. i then setup my phone for regular use. things seemed normal till that evening. when i tried launching a few apps and received error messages saying app wasn't installed. so i reinstalled them and then it happened again. i also launched the camera app a little later and realized the pictures i had taken were also gone.
When i am able to get into recovery i noticed there used to be a lot more folders under install zip from sdcard. now i only have maybe 5 to pick from when before there was probably 10 or more.
Thank you for your suggestion.
Click to expand...
Click to collapse
It might be something to do with your sd card it might be corrupt, try putting it in a laptop and format or fix errors, but for your recovery issue, I would try fastboot installing all the recoveries til one works then make sure ur flashing the correct stock Tom and go from there
Sent from my X9077 using XDA Premium 4 mobile app