Hero reboot loop - Hero CDMA Q&A, Help & Troubleshooting

I rooted my Cellular South Hero and installed Fresh Hero 2.3.3. Everything was working great for a couple weeks when all of a sudden after ending a call, it started rebooting continuously. I get the HTC logo and the phone vibrates, then a few seconds later, the screen goes dark and it starts over. The bad thing is, it does the same thing in recovery mode. Recovery will start to boot, but then it reboots. The only mode that will not reboot is the one where you hold VOL UP (not sure what it's called). I tried clearing user data by holding Home and Back, but this didn't help. At first, when going into recovery, it said the MISC partition was full. That went away after I cleared the user data. Not sure if it's relevant, but I thought I'd mention it. Please help!

Yea, this belongs in Q&A, not dev.

oh, sorry about that

Related

Am I Bricked?

Question.
I was on 4.0.4 and the phone started freezing on me. Just freezes and becomes completely unresponsive. To reset I have to pull the battery. Now this had happened about once a day for the last week, but today I had to pull about 12 times. Now 4.0.4 was working well until I tried to go to 4.1.99. That was too laggy and buggy so I restored my nandroid backup. So for the past week I was living with the occasional battery pull.
Tonight, I tried to go to 4.1.9999, and now it freezes on me during the initial sign in process, "SIGNED IN! SLIDE KEYBOARD BACK TO CONTINUE". It does not get past this screen.
I'll do a Nandroid restore to get operational, but that level of operability was pretty weak.
I have AmonRa's recovery, but I only did one wipe prior to the two flashes.
ADDITIONALLY, I try to get to the recovery boot screen now after I pull the battery and the phone wont let me. Still goes right onto the Welcome to TMO G1 Android screen, where it proceeds to lock where I mentioned previously.
Any ideas?
****. I get an ERROR PERFORMING RESTORE! TRY RUNNING 'NANDROID-MOBILE.SH RESTORE' FROM CONSOLE!
The **** has hit the fan!
As of this moment, I can't do a Nandroid restore, and I can't get past the above mentioned slide keyboard back to continue screen. How bad is it?
No. You're not bricked.
When you say you came from 4.04, did you put the htc image and the cyanogen rom on? or did you just try to upgrade?
HTC image first, then the ROM. I wiped first, but only one wipe.
As of right now, I have a phone that won't load beyond that screen. Nandroid wont let me restore.
Help, please?
wipe!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I did. No help.
Wipe, reboot and this is what happens:
HOLY CRAP IT WORKED!!!
thanks guys... lets see its functional at least now.
It says its running 4.1.9999... what do I have to do now?
Your done as long as it's working good.
It's not. I have the same problems. Phone freezes at completely random moments. Same ****.
Phone worked well for a short time, then performance degraded again. Now its back to the same. Freezes almost instantaneously after a reboot.
go to recovery
(go to console)
fix_permissions
when done
type
reboot
wait for pause..
and it will reboot!
that booted me into a blank black screen after the ANDROID boot screen. Frozen again.

Need help please...phone reboot problems

Last night, I downloaded InnovationsOS v3 from the Nexus One Android Development forum. Prior to this I was using FRF50, and I have a rooted Tmobile Nexus One. I wiped the phone back to factory settings and also wiped the Dalvik cache (as I've been told in the past). Flashing went just fine and within a few minutes I had InnovationsOS after a reboot. (Let me just say, with this one minor exception, InnovationsOS looks incredible and I loved every minute of it).
After install, I set up AdFree which removes ads. I decided to do a quick reboot. The reboot wasn't so quick, and it stuck on the startup screen (the Nexus One/Google logo with the unlocked symbol below) for about 3 minutes. I didn't think this was good, so I tried a battery pull hoping for a normal reboot. Instead, what I got was the android falling out of the box. I tried a battery pull again and attempted to enter recovery, which worked. I wiped, and reloaded FRF50, and rebooted. I got the android and the box image, which wouldn't let me even boot into recovery anymore after several battery pulls. After a couple minutes of being completely stumped (and scared lifeless) I let the phone sit, and somehow it booted into recovery, where I wiped (again) and flashed InnovationsOS (again). After it loaded, it rebooted, and it's been working great since then, with the exception of one minor screen/keyboard bug...I press S, and get Z, or I press delete, and I get enter, etc. Plus hitting OK or Cancel on dialog boxes is impossible and need to use the trackball.
So, I would like to reboot to fix this problem and want to know what will happen, and I want to know what I did wrong above. I know all this sounds completely noob for this forum but I'm willing to learn, which is why I've been experimenting with rooting and flashing roms.
Thanks a lot, any help is appreciated.

Hero reboot loop

I rooted my Cellular South Hero and installed Fresh Hero 2.3.3. Everything was working great for a couple weeks when all of a sudden after ending a call, it started rebooting continuously. I get the HTC logo and the phone vibrates, then a few seconds later, the screen goes dark and it starts over. The bad thing is, it does the same thing in recovery mode. Recovery will start to boot, but then it reboots. The only mode that will not reboot is the one where you hold VOL UP (not sure what it's called). I tried clearing user data by holding Home and Back, but this didn't help. At first, when going into recovery, it said the MISC partition was full. That went away after I cleared the user data. Not sure if it's relevant, but I thought I'd mention it. Please help!
sorry about the double post. can this be deleted?

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

[Q] Random reboots, bootloops, etc

Ok so I'm pretty sure my phone is done for, but I thought I'd see if anyone knew a solution before I go buy a new phone
Yesterday I dropped my phone (which was running Slimbean), but I popped the battery back in and it worked fine. Then about three hours later, it randomly shut off while I was using it, then started going into a bootloop. Occasionally it will start up all the way, but I'm lucky if its on for 10 minutes before turns back off and starts bootlooping again. I got it to boot into CWM, (the first time it shut off while I was in CWM) and wiped everything and reflashed Slimbeam, but it didn't change anything. Any ideas?
Go back in and do wipes on everything but external drive reflash wipe cache + dalvik cache + fix permissions then boot. Let sit 10 minutes before doing g any setup with Google or phone. This allows all drivers to load and configure prior to having more data to configure.
Sent from my CM10 Linero Odexed Powered by Evil

Categories

Resources