OBSOLETE, PLEASE DELETE THIS THREAD
Hi,
sorry for posting on a common problem (as I read).
I run Elelinux 6.2.0 Speedmachine V4 and current Clockwork Mod (2.5.0.7?) on my HTC Hero (GSM).
After some reading I just updated the radio to current SU version and it went ok as far as I can tell (never did this before).
I flashed the update through Clockwork Recovery and when it told me to reboot via menu I did.
My Hero rebooted and then I had some kind of installation screen. After wome waiting the phone rebooted again and is now stuck on the "HERO" boot screen. I didn't remove the battery or stuff during the update, so I hope it's not bricked.
It lays here since about an hour now and before removing the battery to try to boot again I wanted to ask you guys if this is ok or if should wait even longer.
Greetings,
slacker
/EDIT
Sorry for posting. Just removed the battery, rebooted and everything's ok.
Could some mod please delete this thread?
Thanks.
Related
hmm.. gettin worried.. my g1 is stuck on the android blinking screen. what happened was i had glosssuite installed and then openhome started to force close.. restarted the phone and now its just stuck looping the and android screen.. please help..
oh and open home was my default home
(edit) would there be any way i can uninstall openhome or fully format everything thourgh the console?
OMG!! im really sorry for flooding with my question and then answered by myself post.. i found out how to fix it.. i just installed rc33 agian, sorry for the double post too..
Just wipe and reflash rc33, or restore a nandroid backup (if you had one).
No worries mate; you should be fine.
Yea that's what I did it took me 3hours to finally figure it out last nite
1. wiped(alt+W) did not work
2. searched through busybox site to find a command to fully format, but thats a no go
3. i finally installed a fresh copy of JF RC33(i thought i did before i made this thread, but didn't too high)
yea anyone having the same problem just do what i did.. step #3
I didn't want this to be my first post and I've been holding out for a couple of days now, but here goes.
When the CM6.0 zip installation finishes, I tell clockwork to Reboot Now.
When it reboots, I get the white screen with green HTC letters. I do not ever get to the screen with the black writing on it. It then proceeds to the cyanogen mod boot screen with the swirling circle, but that's all it ever does. It will stay in the "boot loop" forever if I let it. The phone never progresses past that point.
I am able to do a nandroid recovery back to before the CM6 ROM and everything is OK, but its not FROYO nor is it rooted. I followed the instructions from here //forum.xda-developers.com/showthread.php?t=730002
Any help will be greatly appreciated.
Are you connected to the PC when you reboot?
No, I've tried twice and both times I was unplugged.
Let me run down some quick troubleshooting answers
I used CyanogenMod-6.0.0-liberty-signed.zip
I have the Android USB Drivers
I installed HTC Sync, but uninstalled to leave the drivers.
HBOOT is good
Clockwork installed like clockwork.
I did not install the Android SDK, I didn't think this mattered since I had the drivers from the Sync install.
Your best bet is to hop in the IRC and ask for help. http://webchat.freenode.net/?channels=#liberatedAria
I'll have to get on when I get off of work. Thanks for the linkage and taking a look at my issue!
OK, so the guys over on the IRC helped me out....very quickly I might add. I didn't want to start a new thread for this very reason...super simple fix!
My issue was that I did not perform a wipe through clockwork before installing cm6.zip.
According to Yoshiofthewire and jznomoney, the cyanogen boot loader will loop if the old HTC files are still on there. Performing the wipe through clockwork and reflashing did the trick!
Thanks to you all! now to set the rest of the phone up. Amazing resource!
matroe11 said:
OK, so the guys over on the IRC helped me out....very quickly I might add. I didn't want to start a new thread for this very reason...super simple fix!
My issue was that I did not perform a wipe through clockwork before installing cm6.zip.
According to Yoshiofthewire and jznomoney, the cyanogen boot loader will loop if the old HTC files are still on there. Performing the wipe through clockwork and reflashing did the trick!
Thanks to you all! now to set the rest of the phone up. Amazing resource!
Click to expand...
Click to collapse
No problem. I was gonna suggest that you didn't wipe, but I wasn't sure without being able to talk to you. Figured it was faster to send you to IRC. Glad everything is working. Enjoy.
Hello,
Last night I tried to install another radio fw on my Hero because of bad reception since the last one I installed.
I placed the new radio on my SD, rebooted and forgot to push the right buttons to access the "Android system recovery" (RA?) part.
Because it takes ages to wait for the phone to boot I pulled the battery and tried it again witch failed again, pulled the battery again etc.
When I finally managed to acces the "Android system recovery" part I flashed the new GSM radio to my GSM Hero. All the steps in described in the manual I used worked and all looked well.
After rebooting the phone started till the point of the Villainrom logo. I kept the phone on for hours till the battery was fully drained but it stays the same.
I can still acces the "Android system recovery", fast boot etc,
Tried the following:
-Wipe
-Restore backup
I'm getting pretty desperate!!
I's there anyone who has recovered his Hero from such a situation?
Please help..
If you can get to the recovery screen then you're not bricked. just reflash your rom and gapps add on and you should be fine or do a nandroid restore.
Hi pwraggcan,
I already restored a Nadroid backup.. Did not do the trick....
Also I tried to reflash the radio fw... Nothing helps. It just hangs at the unfolding Villainrom Logo which every few minutes restarts unfolding (I don't know how to call it otherwise, I do not mean that the phone restarts).
You're not bricked, so you're OK.
Re-flash the ROM you had installed after wiping your /data
Failing that, remove the SD card as that sometimes helps get the phone to boot.
If all else fails set up adb and get us a logcat.
Download the ROM again, full wipe & try again... Just to make sure the download didn't go bad?
Sent from my HTC Hero using XDA App
pulser_g2 said:
You're not bricked, so you're OK.
Re-flash the ROM you had installed after wiping your /data
Failing that, remove the SD card as that sometimes helps get the phone to boot.
Click to expand...
Click to collapse
Thanx pulser_g2!!
I started with the simple solution, removing my SD..
Without the SD is just starts!!!
HAPPY!!
Thank you for your quick replies!
RealR74 said:
Thanx pulser_g2!!
I started with the simple solution, removing my SD..
Without the SD is just starts!!!
HAPPY!!
Thank you for your quick replies!
Click to expand...
Click to collapse
You're welcome
Clear out your SD on your computer (back it up first), format it, and you should be good to go
It's usually the SD when this happens
I rooted my G2 via the instructions and download in this thread:
http://forum.xda-developers.com/showthread.php?t=928160
I did not flash the hboot.
Phone seemed to work fine after that. But then I downloaded ClockWorkMod Rom Manager and downloaded CM7. When I installed it, my phone comes up to the boot screen, runs for a second, then reboots.... it just keeps rebooting.
Using the factory reset, I can get back into the recovery, so I tried to install CM6.1 from my sd card, but the exact same thing happens (endless boot screen reboots).
What can I do? Thank you for any help.
Sorry mods,
I put this in the Android Dev and Hacking section.
This should probably be deleted.
OK heres the deal. I have done tons of searching and it looks like I SHOULD be able to get out of this, but I cant figure it out and I may have gone to far(by unrooting with 4.24 and bootloader 2.16).
So long story short, my launch day evo got lost about a month after I got it. Got a replacement from Sprint(or whoever their insurance is), my original Evo got found about a month or so after that. It has not been powered on since then(a year realistically) with no battery or SD card in it. I got bored and decided to power it up and update everything(because I cant do **** with my new Evo3d, yet since im on a Mac and have no access to a PC). Here are where things went bad.
Phone was rooted with the very original Toast method including S-off with the .76 Eng boot loader. I was running some form of CM6 on it when I lost it.
-Went to power it up and it boot looped at the white Evo4g screen.
-Went into bootloader and tried to get into recovery(had Amon RA 1.7 I think). No go.
-Flashed the new TWRP recovery and got into recovery just fine.
-Flashed the CM7.1.0-RC1
-reboot into a boot loop
-battery pull and a reboot and it loaded, but after about 30 seconds, reboot into a boot loop.
-Thought maybe TWRP didnt like the phone so I flashed Amon RA 2.3
-went into recovery just fine. Did complete wipes of everything using Calkulin Wipe all.zip
-re-flashed CM7.1.0 RC1
-boot loop
-flashed latest radios
-rebooted back into recovery
-reflashed cm7.1.0 rc1
-boot loop
During all of the reboots I would occasionally get the CM7 splash screen and then a reboot into boot loops. I THINK everything was flashing ok.
At this point I was frustrated and was thinking it was something I was doing that was jacked up so I decided to unroot and I flashed the newest RUU(which obviously removes root, S-off, .76 boot loader, etc...) so I did it. Figured I was just trying to get the phone running to sell anyway. Flashed was successful, chose to reboot and guess what. Boot loop. I pulled the battery out for about 10 minutes and it boots into the rom, runs for about 10-15 seconds in the rom and then reboots, back into the rom at least, but only about 10-15 seconds later, another reboot.
Every thread I read on these infinite boot loops were guys saying they couldnt even get into recovery or flash anything, which I had no problem doing(obviously cant really do that anymore with losing root and s-off). So I am stuck.
So current state of the phone is boot loader 2.16 S-on with 4.24.651.1 with all current radios, etc... flashed(as far as I can tell) from the RUU posted on Goo-inside.me.
Does anybody have any ideas for me to try? It seems like I am so close to getting it running because it will run for about 60 seconds but then reboot. I am guessing a hardware issue, but I honestly at this point have no clue.
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thats what I am leaning towards, but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
drdrewdown said:
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
Click to expand...
Click to collapse
I know. I probably should have posted up and waited, but I got impatient and thought that was a last ditch effort anyway since I tried everything else I knew to try.
rjacobs said:
but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
Click to expand...
Click to collapse
because in the boot loader and recovery menu I'm sure the phone is not accessing radios, audio components, gps, and all manner of other hardware components that get activated once the phone tries to boot up for real.
It sounds like according to this thread: http://forum.xda-developers.com/showthread.php?t=805612&page=4
That my NV is FUBAR, but since I ran RUU and lost S-off, I cant do the fix. Oh well, I am sure eventually somebody will crack the boot loader and then I can fix it. Otherwise I have to send it off to HTC and I am sure pay them to fix it.
Just to clarify. The thread you linked to is for people who wrote nv items to their device.
What I'm afraid you are experiencing is the bootloop commonly complained about by those running CM roms.
I have yet to find a solution to the CM bootloop and all signs point to hardware failure.
Sent from my Evo using XDA Premium App