Related
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
Apologies for the double post but I'm dying to get my wildfire back working.
Rooted it yesterday with unrevoked, attempted to add the Openfire ROM this morning with everything going fine untill the reboot. I'm now stuck on the white HTC screen and have been for the last hour. Any help would be great, cheers.
did u do nandriod back up first
Sent from my Archos5 using the XDA mobile application powered by Tapatalk
I backed up the stock firmware I already had manually, before it prompted on the flash.
did you do a full wipe before flashing the rom?
No i didn't, thought it would be safer incase something went wrong?
run your restore then I couldn't get it to work either
Sent from my Archos5 using the XDA mobile application powered by Tapatalk
if you did a nandroid backup of your stock rom then you should be fine to wipe, since you did not wipe and flashed the new rom over your stock rom, apps and settings will conflict, therefore not work...
Right I see, I'm currently going through what I'm guessing is the restore....recovery - Nandroid, I'll let you know how I get on.
Thanks again.
Nope I seem to be getting nowhere here, can someone point me in the direction of the restore?
you didn't do nandroid backup did you haha, you'll have to install an RUU file to return to stock rom, or just do a full wipe and flash a new rom like openfire or wildpuzzle.
Where can I find the RUU file and how do I access my SD card? USB won't let me get to it, I'm guessing the phone is in charge mode?
go into recovery - partitons menu - mount sd card (or somthing like that) to open your memory card
Spot on, I'm on downloading an ruu file now, going to load it up with a stock rom then try flashing it again, but wiping it this time.
Infact how do I do a full wipe? I'm after the easiest way to get the phone booting up so I can flash it properly?
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
go into clockwork recovery and click the title "wipe data/factory reset" and then flash the ROM you want to use.. to install a ROM:
- "install zip from sdcard"
- "Choose zip from sdcard"
- "click the zipfile"
- "yes"
- "reboot"
and if you want to install RUU dont ask me never done that
Reggie24 said:
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
Click to expand...
Click to collapse
How did u restored it .....????
sunny_16977 said:
How did u restored it .....????
Click to expand...
Click to collapse
From the HBOOT screen go to recovery, then nandroid, restore, and to the appropriate time/date.
I've still had no luck with actually flashing the phone though. Back to Android 2.1 for me.
I'm 99% percent sure you have the OC issue some ppl incl myself on here have - try reinstalling openfire if thats what you wanna use - and then go to wildpuzzle thread - dl 0050 and flash it. If i'm correct phone will be fine and use openfire - but will NOT be overclockable. I wish Jacob had my phone or got hold of a phone w that problem...
I had problems with the Wildpuzzle 8.0.11 ROM, it would just sit there (did a ADB logcat on it, but I've lost the actual log... sorry! ) ignoring a duplicate entry (yeah, I did a full wipe . Removed WP and put on the latest OpenFire ROM... omg... what a difference to the stock ROM! Soooo much faster, even before I overclocked it.
I'd say, if you have boot issues with WP give OpenFire a go. Certainly worked a treat on my Wildfire.
So I successfully rooted my WF with unrevoked.
I made a Backup with Nandroid.
I saved the ROM on my SD card and selected Wipe / Reset Factory Settings and Wipe cache (or so).
Then I selected my ROM (0001_WildPuzzleROM_v8.0.11) and it installed.
It showed my some kind of BIOS (?) and then got into an infinite picture of an Android. I'm saying infinite because the instructions linked in the WildPussel Release Post says its about 12 minutes and I didn't touch it for about half an hour.
So I took out the battery and used my Recovery image made with Nandroid.
I tried to flash standart 2.2 Froyo (0050_htc_froyo_2.2_orginal_kernel_v2) but I had the same results, an infinite screen of the HTC logo (about 25 mins).
What could be my mistake? I could make a video of me trying to do it.
Osskyw said:
What could be my mistake? I could make a video of me trying to do it.
Click to expand...
Click to collapse
Did you do a full wipe before flashing new rom?
Also it may help to post in the right forum [ROM]WildPuzzleROM_2.2 Froyo v8.0.11
Osskyw said:
So I successfully rooted my WF with unrevoked.
I made a Backup with Nandroid.
I saved the ROM on my SD card and selected Wipe / Reset Factory Settings and Wipe cache (or so).
Then I selected my ROM (0001_WildPuzzleROM_v8.0.11) and it installed.
It showed my some kind of BIOS (?) and then got into an infinite picture of an Android. I'm saying infinite because the instructions linked in the WildPussel Release Post says its about 12 minutes and I didn't touch it for about half an hour.
So I took out the battery and used my Recovery image made with Nandroid.
I tried to flash standart 2.2 Froyo (0050_htc_froyo_2.2_orginal_kernel_v2) but I had the same results, an infinite screen of the HTC logo (about 25 mins).
What could be my mistake? I could make a video of me trying to do it.
Click to expand...
Click to collapse
Thats the weird part, flashing the ROM just seem not to work.
Either way, in your recovery console select wipe data. This will remove the existing stock Rom data which may cause boot looping. After wiping, flash the Rom again.
Sent from my HTC Wildfire using XDA App
That's what I did...
It tried it 3 times again today.
3rd time I just cleaned both, ROM and Cache twice each, seems like it worked.
So i have a desire hd from Three, which is unlocked and unbranded, i rooted the phone via the visionary method, got s-off, used rom manager to install clockwork mod recovery which was 2.5.1 something rather, then i created a backup, upgraded to clockwork 3.0.0.1, tried to install the cyanogenmod 6.1.3 via rom manager but didnt work, so i downloaded the zip file manually and tried to update via clockwork mod recovery now in 3.0, restarted, and am now stuck at the main HTC screen. Pulled the battery, then went back into clockwork recovery, tried to recover the backup i made, rebooted, but still stuck on htc white screen... dont know what to do help!
You could try flashing a RUU to go back to stock 1.32 would be best or you would need to downgrade to root, or you could try getting another rom image on your SD card isnt clockwork 3 4 ginger bread nightlies?
Just throwing ideas out there. Personally I would go woth the RUU.
Thanks for the reply, i remember finding some links with ruu's but i'm not sure which one i need and how to use it ?
Sorry just thought the other thing is how long did you leave it. I have read about people leaving for 30 mins and then it boots..
Start downloading this. Its the RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed
http://www.multiupload.com/N333WKVW6M
while downloading leave your phone to boot it might surprise you..
I left it for a while but maybe not long enough, perhaps 15 minutes at one point? i'll try again, should i wipe data in clockwork and then reflash the cyanogenmod again? is it ok to keep the phone plugged into the computer via usb?
Sorry, once downloaded just run the EXE, it will walk you through the steps.
The Dev section has a lot of useful stuff in it for this sort of thing the 1st post http://forum.xda-developers.com/showthread.php?t=936214 is pretty usefull.
djamorpheus said:
I left it for a while but maybe not long enough, perhaps 15 minutes at one point? i'll try again, should i wipe data in clockwork and then reflash the cyanogenmod again? is it ok to keep the phone plugged into the computer via usb?
Click to expand...
Click to collapse
Worth a go whilst downloading, I would wipe 1st. Its good you still have your recovey partition (clockwork) so you should be fine. Use the RUU as the last resort as it will wipe recovery part and loose SOFF etc.. But should fix the phone.
Right so i've wiped data/factory reset and cache partition and dalvik cache, then went to choose zip from sd, chose update-cm-6.1.3-DesireHD-signed.zip, says Welcome to CyanogenMod-6.1.2-desireHD (strange?) completed. Now went to Reboot system now and waiting, still on HTC screen.
is it possible to put another rom on the sd card? i dont have a computer that i can plug the mini sd into, possible in recovery mode?
djamorpheus said:
is it possible to put another rom on the sd card? i dont have a computer that i can plug the mini sd into, possible in recovery mode?
Click to expand...
Click to collapse
yes, but i dont know how of the top of my head, i will have a look in the dev forums, i think you use fastboot and u can push files. Hopefully someone with a bit more knowledge will see this post soon. I will have a look though.
so its been 30 minutes, and it's still at the htc screen... what should i do? should i try the RUU ? i dont want to brick my phone...
from what i can find fastboot will not push files, adb but may not connect on splash screen. You could just try pulling the battery and leaving it again to boot for a bit, mine has hung before like that. The Ruu should go through and connect to phone and go through flashing. Do you have another phone that could take the SD card? im gonna boot my phone to recovery and try to push a rom to it or file.
ok i am reading this post,http://forum.xda-developers.com/showthread.php?t=558812
what i would do is goto recovery mode,
he command is:
adb shell mount /sdcard
adb push c:\******.*** /sdcard
exemple with g:\update.zip :
adb push g:\update.zip /sdcard
usefull when wrong rom flashed and no sdcard reader ^^
So i downloaded a cyanogenmod 7 nightly build, installed with with clockwork 3.0.0.5, and it worked, booted in, but had a continuous logo loop, going to try leedroid
Good luck, Leedroid rocks, thats what i use. I would say if it is still looping try the ruu and then start again. The RUU will esentially factory reset.
Installed the latest Cyanogen nightly build #23, and it works perfectly now should i keep it? or should i try leedroid? i kind of want to keep using htc sense, as i have all my contacts on it..
Up to you really. I went back to leedroid because it seems faster and more stable for me and I like some of the sense widgets.
Sent from my Desire HD using XDA App
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!