I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.
goshxjosh said:
I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.
Click to expand...
Click to collapse
What version of cwm? Try flashing a different recovery version (maybe 2.7.0.5)
Make sure you factory wipe as well as format, system, data, cache.
Bad download maybe?
®patience is a virtue©
is your battery charged well above 30%?
Sent from my HERO200 using XDA App
Guys i had this problem when i flashed my first ROM too ...(alas)
Buy my problem was a simple fix ,
: restart in recovery
: wipe all data
: restart and Enjoy
i have the most recent cwr and i wiped my data and everything. i have been flashing for more that a year now this is the first time ive had this issue. im gonna unroot and reroot the phone.
If you haven't unrooted yet try just reflashing your current recovery.
#Root/Hack-Mod_Always*
This has happened to me with different builds ( of all of the different gingerbread roms) since the switch from 2.3.2 to 2.3.3 and .4.
When this happens, I will either try a different Rom, or use something called Fix Flash that is in the development section for the CDMA Hero. My phone currently is liking the Jaybob build. Also, as silly as this might sound, but formatting the partitions 3x can actually help too ( boot, system, data, and cache).good luck, I've been there.
Sent from my HERO200 using XDA App
Can't get past the HTC screen...
I got a new HERO200 as a replacement for a damaged one and am able to root it with confirmed SU permissions. I have tried clockwork 2.5.0.7 and RA 1.6.2 for the heroc. I tried flashing Cyanogenmod 7 (7.0.2 / 7.0.3 / 7.1.0 / and even a 6), AOSP and it keeps hanging at the HTC screen when I reboot the device out of recovery. The first reboot after flashing a ROM will briefly display the HTC screen and then go black. I have to remove the battery to reset the phone. When I power it up again, it will display the HTC screen and just hang, even after multiple restarts via a battery removal. I have wiped all the data/cache/etc. multiple times as from a previous post in this thread, but without luck. I'm getting very frustrated to say the least and any help would be GREATLY appreciated.
never had a rom not booting, but i haven't tried them all,
try the older version again see if it works
I just run the nightlies and skipped the rc and haven't experience such things. could be something to do with the signing?
Sent from my HERO200 using XDA App
Related
Hey guys i don't know if anyone of you had the same issue but any info/help could be helpful.
I used to flash my N1 A LOT! but today i have this strange issue. I wiped and flashed rodriguezstyle again for a clean start, but i only got the colorful X with the unlocked symbol at the bottom and then just a black screen. i thought I've done something wrong and flashed again, but with the same results.
i changed my sd and downloaded again the rom but still no luck, did a nandroid restore and the phone was working properly. then i got a bit frustrated. downloaded 2-3 more roms but the result was the same.
i read somewhere that flashing with battery <50% may cause some errors so left the phone off to fully charge and tried again... no luck
then i remembered i upgraded the radio and i downgraded it to the old one, but still the same results and nandroid doesn't work... jeeeesh... back to the new radio and to my nandroid, but its no fun owning a smart-phone if you cannot flash it.
anyone with the same issue or any helpful tips/instructions?
Try this:
When the phone hangs at boot, reboot to recovery, wipe cache and dalvik-cache and reboot from recovery. Does that work?
If not, you'll need to logcat the boot process and post the log somewhere for us to have a look at.
So, assuming adb is working on your computer, plug in via usb, use adb logcat > output.log and reboot the phone. Continue logging for about 60 seconds after the phone stops.
Post the log to www.pastebin.com and then link back here.
hmmmm ok i will post results in abt an hour. thanx!
hmmmm i think i sorted it out... reflashed recovery. propably i messed smthing in there! thanx for your effort!
Hello everyone!
Weird problem here, too.
I was backing up my SD card in view of a format/cleanup....and when I went to boot into recovery, my N1 was stuck on the black screen with the white letters at the bottom "Build : RA-nexus-v1.7.0.1"... The phone actually boots great, it is just not loading the recovery image. Is it possible that part of the flash got corrupted? If so, I'm pretty much done flashing my N1, right???
I'll post a log asap (if it could help any)...
Oh and btw i tried to re-flash Amon-RA's recovery twice already...Superboot said it was successful....but I doubt it...
Well try flashing stock rom! I flashed it through fastboot step by step and it worked. Also check if the rom you try to flash needs ext partition or if apps2sd is enabled
Sent from my Nexus One
Test
Sent from my Nexus One using XDA App
Thanks nica.
I had to flash stock boot and rom to fix it...
Sent from my Nexus One using XDA App
anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.
I'm new to this whole flashing custom ROMS business. I have a CDMA HTC Hero 2000 and I downgraded to the original 2.1 before the update just fine, rooted my phone just fine. Then I tried to flash Aloysius to it using instructions I found here: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police
After all was said and done, my phone starts to boot with the "HTC quitely brilliant" logo, following by "SPRINT the Now network" logo and after it shows "Now" for many seconds (as it normally does before pulling up the home screen), it reverts back to the HTC logo and repeats this process until I remove the battery.
I removed the microSD and attempted to boot, same thing. Then I held down HOME+BACK+POWER to do a manual hard reset, this took a little longer but again had the same result.
I may just cry now. Please help!!
Run the official sprint ruu, and see what that does for u. Then read the rooting guide here on xda and try it. I personally recommend amon ra recovery to flash roms, rom manger never seemed to work right. Feel free to pm for more help, dont worry u prob arent bricked unless u flashed a gsm rom (which aloysius isn't)
Sent from my HERO200 using XDA App
That's a bootloop not a brick You could try downloading a different rom and flashing it in recovery, nandroid restoring - if you made one, or flashing the same rom again. just wipe your phone before (data/cache/dalvik)
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
chrisdegraw said:
Didn't get a chance to get on here until now but I fixed it last night.
I did this by going back into reboot recovery mode (by pressing HOME and POWER), going to partition settings, COMPLETELY wiping everything on the sd card, mounting the USB and dragging a new ROM .zip file onto it. (I tired this twice without completely wiping and the phone continued to have problems booting.
The flash worked fine that time and all has been well. Turns out the first one I was trying to apply to it was just an upgrade.
Thanks everyone for your help, makes perfect sense now.
Click to expand...
Click to collapse
Four key words to remember when trying out any new rom
Nandroid is your friend!
additionally, you should always remember to wipe before loading a new rom!
Enjoy!
Yeah, don't ever panic, that was, as everyone said, a bootloop by textbook definition. I've never seen a brick before, but I'm damn sure it won't get as far as the Sprint logo. The only way to brick a CDMA Hero is to flash a GSM Radio/Bootloader to it.
If im running the 2.2 leak version and am having bootlooping issues and am unable to get into clockwork, can I just SBF to official 2.2?
yes you can
Cool reason I asked is because I did it last night and it just keeps boot looping now tried to flash it about 3 different times. Any suggestions as to how i can get it going? The SBF file fully flashes to the phone RSD doesn't give any errors and reboots phone as it normally would but when it starts up it just boot loops I actually left it going for about 30mins last night to see if it would strat up, so far it has not.
Just to make sure- and I know this is a lame question - but just to make sure - you are using the new 2.2 SBF...
VRZ_MB810_2.3.15_1FF_01
Yeah the SBF im using matches that file name. It was late last night so only really got to try and flash it a few times and im stuck at work now just trying to see if anyone else had any similar issues really. Also im on windows 7 64bit if that may cause any issues.
You may want to try wiping the data and cache from the default recovery. Power on your phone with the home key pressed and press the search key. You'll have options for wiping data and cache. Maybe you could still have remnants of the 2.2 leaks in there?
Sent from my DROIDX using XDA App
I think I tried that last night will do again to be sure though and thanks for all the help.
when I SBF'd back to stock 2.2 I had to boot back into recovery and apply the update.zip, once I did that it booted back up without issue.
Lol facepalm. The update.zip heh, did not try that yet. Gonna try it as soon as I get home and ill update when I do. Thanks for all the suggestions.
Got it to boot after doing factory reset thanks again for all the help
http://pastebin.com/trSmUrkT
this is what the logcat loops at the media device dies.
I get this on froyo also
I am using cwm 3.0.0.5
Kenpoman said:
http://pastebin.com/trSmUrkT
this is what the logcat loops at the media device dies.
I get this on froyo also
I am using cwm 3.0.0.5
Click to expand...
Click to collapse
confusing. you mean when you turn on media the phone reboots? or you get FCs on certain media? go into the "live help" IRC link in the first post of the GB thread. much help there.
this is at initial boot just after flashing the rom
and yes i did a complete wipe and formatting yada yada
it just hangs at the HTC screen.
I have gotten it to install before but only some times.
I also have this issue sometimes on a reboot while running .9.9.2
the logcat still shows the same.
I don't go to the IRC because I don't always have time to wait for an answer so I won't waste everyone's time
I had this issue yesterday with the newest 2/1 update. It would flash fine unless I tried to add any circle battery mods. I tried them all. Finally, I went back and flashed the 1/28 update and it stopped bootlooping or getting stuck. Clean install all the way.
wild1z said:
I had this issue yesterday with the newest 2/1 update. It would flash fine unless I tried to add any circle battery mods. I tried them all. Finally, I went back and flashed the 1/28 update and it stopped bootlooping or getting stuck. Clean install all the way.
Click to expand...
Click to collapse
Some have reported that installing the circle battery mods AFTER rebooting the ROM seems to work. Flash the rom, reboot, go back into recovery, flash the battery mod, reboot. However, also know ranger61878 noted that some of the battery mods do not work on all aospGB themes.