Develop Bugs

[Q] Any idea what just happened? (bricked for a few minutes?)

This evening I was playing around with my Evo and got thinking, "I really like how everything is running right now! I've been running SteelH I.2 ROM stable for a few weeks, launcherpro, all my homescreens setup... perfect! I should take a backup."
I reboot into recovery, take a nandroid backup, then go to reboot the phone. Backup completed without any errors, but the phone would not restart. It sat at the white HTC and would not budge. I removed the battery several times and rebooted, but nothing. I could still get into recovery, so I wiped data, cache, dalvik and attempted to reboot. Again, nothing... just sat at the HTC screen. At this point I was thinking, "great... gonna have a long night ahead of me troubleshooting this one." I restored the backup I had just taken about 30 minutes earlier, but wasn't very confident that it would help at all... reboot, and after a few seconds, my boot screen starts loading!
So, here is what I am wondering.... I had not done any "hacking" since the last reboot... just installed/uninstalled a few apps from the market. What could have caused my phone to react like this? Also, if it wouldn't reboot in the first place, why did restoring the backup work? I had just taken the backup a few minutes earlier....
thanks!

Well, that certainly is unique. I've had problems doing nandroid back-ups (recovering from and creating them) before but it always booted just fine no matter what happened. Maybe there was a small software error that was fixed when you recovered.
Either way, I wouldn't worry about it. Recovering a nandroid back-up = problem got deleted.
That's why I tell everyone to nandroid before doing anything

[Q] Help (Boot Related)

Okay, so I researched my issue and didn't really find an answer. I'm not sure it is even the same issue, let me explain.
I rooted my phone using unrevoked, the latest one. I haven't flashed any roms or anything. I just deleted some bloatware and use wireless tether and shootme...etc....
The other while I was surfing the net on my laptop, I lost the signal. I went to my room and saw my phone rebooting. I didn't think too much of it until I realized it kept repeating after the 4g screen. I instinctively removed the battery and let it cool down. I replaced the battery and the same thing still happened. I wouldn't boot past the 4g screen.
I made a nandroid backup about a month ago and decided to just backup once again. I backed it up and restored the backup from a month ago. It worked fine. Now I tried to restore the most recent one and it wouldn't work at all. The same repetition of the boot screen, I believe it is called boot loop. I don't know.
My question is how would I be able to restore that most recent back up and why isn't it working? What could've possibly occurred to cause this malfunction?
I also read somewhere that battstatpro could be the culprit?
Cliffnotes:
Rooted phone a month ago
Did a nandroid backup & titanium backup (same day)
Phone stopped working while using wireless tether
Stuck in bootloop?
How do I fix it?
Thank you

wutitizshorty said:
Okay, so I researched my issue and didn't really find an answer. I'm not sure it is even the same issue, let me explain.
I rooted my phone using unrevoked, the latest one. I haven't flashed any roms or anything. I just deleted some bloatware and use wireless tether and shootme...etc....
The other while I was surfing the net on my laptop, I lost the signal. I went to my room and saw my phone rebooting. I didn't think too much of it until I realized it kept repeating after the 4g screen. I instinctively removed the battery and let it cool down. I replaced the battery and the same thing still happened. I wouldn't boot past the 4g screen.
I made a nandroid backup about a month ago and decided to just backup once again. I backed it up and restored the backup from a month ago. It worked fine. Now I tried to restore the most recent one and it wouldn't work at all. The same repetition of the boot screen, I believe it is called boot loop. I don't know.
My question is how would I be able to restore that most recent back up and why isn't it working? What could've possibly occurred to cause this malfunction?
I also read somewhere that battstatpro could be the culprit?
Cliffnotes:
Rooted phone a month ago
Did a nandroid backup & titanium backup (same day)
Phone stopped working while using wireless tether
Stuck in bootloop?
How do I fix it?
Thank you
Click to expand...
Click to collapse
Well I can't say for sure what caused the phone to initially wack out and go into a bootloop, but I'll tell you why the nandroid backup didn't work. The reason you can restore you're original backup, from a month ago when you rooted, is because you created that backup when your device was operating correctly. Since this most recent backup was created when you're phone wouldn't even boot to begin with, it will not work. The backup takes an exact copy of your entire system the way that it is when you make that backup. Since your phone was inoperable at the time of the backup, whatever it is that is broken was also copied to that backup, thus the reason it wont work. A nandroid restore will only be as good as your phone was when you created that backup.

Thank you. Is there anyway where I would be able to pull any information off that backup or fix that backup or at least get it to boot?

wutitizshorty said:
Thank you. Is there anyway where I would be able to pull any information off that backup or fix that backup or at least get it to boot?
Click to expand...
Click to collapse
Your welcome. I've never tried accessing any info or data from nandroid backup before, but I found this thread on how to do it. I've never tried it, so can't confirm nor deny if it works, but it looks like you're answer may be in this thread here: http://forum.xda-developers.com/showthread.php?t=890508

Thanks...I'll check it out

Stuck at boot splash after creating backup

I'm on an EVO 4G running Fresh 3.5.0.1 with Netarchy Toastmod 4.3.4 cfs havs-less no sbc. I'm currently using ClockworkMod recovery 2.6.0.1.
Last weekend, I wanted to try Synergy with GodMode. I don't know if it wasn't in the thread when I read it (I see the thread's been updated since my attempt), or if I just missed it, but either way, I was unaware that I couldn't install the GodMode ROM with ClockworkMod.
So I did a Nandroid backup and attempted install (I'll admit, I initially forgot to wipe data/davlik/cache). It seemed to install fine, but then couldn't make it past the boot splash. So I figured I'd cut my losses and just restore my backup. After restoring, it once again got stuck at the bootsplash (never had this issue in the past). And when I say stuck, I mean I let it sit at the boot splash screen for 5-10 minutes, pulled the battery, repeated (including wiping everything), and it could never get past it. To get the phone working again, I had to restore to a much earlier Gingerbread Deck backup that I had made while fooling around with that ROM, then I was able to restore the most recent backup without issue.
Fast forward to this evening. I figured I'd try again, but now I know I need Amon_RA's recovery. So my plan was to do another Nandroid backup, install Amon_RA, and try Synergy with GodMode. I never made it past the first step... after creating the backup (no changes were made, just the backup created), the phone wouldn't progress past the boot splash. I had to go to an earlier restore point (last weekend's) to get the phone to work. Tried restoring today's backup after getting it to work on the old backup, no luck.
Thinking perhaps the attempted GodMode install messed something up, I did a fresh install of Fresh 3.5.0.1 (pun semi-intended), fresh install of my kernel, and then tried restoring the most recent backup. Once again, couldn't get past the boot splash.
I feel like something is seriously wrong, and I don't feel comfortable going into recovery to make any changes until I have some insight into what the issue is.
To make matters worse, I rely on 4G tethering for internet, and have no landline, so if the phone is bricked while trying to resolve this issue, I'll have no resources to get help.
Any help is GREATLY appreciated. I've searched, but it seems that the problems everyone has that are like this occur immediately after changes are made and are remedied by wiping data/davlik/cache. I made no changes this evening, and wiped everything multiple times in my many attempts.
Edit: Almost forgot, some things did stand out as I was trying to get it to work.
While whiping Davlik, I was given the line:
E:Can't mount /dev/block/mmcblk0p2
(File exists)
While restoring today's backup:
sd-ext.img not found. Skipping restore of /sd-ext/.

There was a nandroid restore issue using a previous version of twrp that was remedied by restoring nandroid and then flashing the rom over top of the nandroid. Maybe try that
Sent From My Pocket

Ok I had the same problem. I wiped everything three times also wiped dilvak (might have spelled wrong) cache, and wiped battery stats. Then flashed it. It took forever also close to 15 mins. This is what I did I hope it helps.

Just a followup: I decided I could do without restoring to that specific backup (tried restoring it after wiping data a few more times, but oh well). I only installed a couple apps and changed a couple other things since the last backup that worked, so I installed Amon_Ra since it seems to be the consensus that it's a better recovery and made a backup with that... rebooted just fine afterwards.

[Q] I think I finally hosed my phone. Help

So I was running Synergy + God Mode and today my phone decided to reboot itself. Well not it keeps locking up at the htc EVO 4G white screen or sometimes will get as far as the Synergy splash screen but will just loop.
So to back up a bit I previously had moved the Dalvik cache to the sd card as well as most all apps. This has been running fine for weeks.
I was able to get it to boot once after I removed the sd card but now it won't even with that. I tried wiping the phone from recovery and still nothing.
Any ideas? this is annoying. I've never run into an issue this bad before. I've always been able to repair either with a nandroid backup or just a wipe.
I tried restoring a nandroid backup and it just sat there with the lines getting longer and longer 1 dot at a time. Actually filled the whole screen and never actually finished.

Try a RRU
Sent from my PC36100 using XDA App

I would try an RUU.exe
Which HBOOT do you have? If you can get to HBOOT, then you should be able to go back to stock and solve most problems

I'm running the 0.76.200 HBOOT.
I will probably end up having to go back to stock but would like to keep that as a last resort.

I think I narrowed down my problem. Anytime I go into recovery and try and wipe anything that has to do with the ext3 partition it either locks up or for instance I'm now trying to repair the ext3 partition and it just keeps adding dots. Just keeps working and seems to get nowhere.
I can still access everything else on the SD card just errors of sorts when dealing with the ext partition.

well got it working after RUU but i still wish I knew what caused it in the first place

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