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
Related
Hey People,
So i rooted(Unrevoked) my Wildfire today, everything went fine it seemed. but after putting OpenFire on, it just did'n get past the OPENFIRE screen. i let it run for an hour+ in the end i got so hot i pulled the battery.
now i tried to Nandroid restore it, but it suddenly went B(lack)SoD on me and now the orange Charge light i just blinking and i can't seem to revive the phone HELP! Please
Kind Regards
Vicster
if you still can use nandroid. why don't use flash to another rom
so you can't boot back into recovery?
if you can, make sure you do a full wipe before installing a rom (always do a wipe when installing a new rom)
THanks for your reply's the phone suddenly came back to life...!! thanks alot everyone!
pnukeid said:
if you still can use nandroid. why don't use flash to another rom
Click to expand...
Click to collapse
I bricked mine as well. It bootloops and then goes into the recovery. How do I put a rom on it so I can choose it to be flashed? I had a restore point but it won't work after I restore it.
nemuro said:
I bricked mine as well. It bootloops and then goes into the recovery. How do I put a rom on it so I can choose it to be flashed? I had a restore point but it won't work after I restore it.
Click to expand...
Click to collapse
in recovery, mount your sd card or usb, and put a rom into it. make sure your phone is plugged into your pc.
or take your sd card out and put a rom on it and put it back into the phone, then boot into recovery and flash it, simple enough?
vicster said:
THanks for your reply's the phone suddenly came back to life...!! thanks alot everyone!
Click to expand...
Click to collapse
lucky you! My wildfire cant go into recovery, battery drains out in 2-3 hours, now even with a new battery. I am so sad
@kevin2516
I was desperate enough to not do a search in the recovery menu. I did the thing with the sd card. I don't understand why my backup started bootlooping...
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
gloscherrybomb said:
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
Click to expand...
Click to collapse
Hook your phone up to the comp with it powered off, type in "adb logcat" into your computer's Terminal, and display the results.
gloscherrybomb said:
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
Click to expand...
Click to collapse
Ok so once it boots into Clockwork recovery you have a couple of options, first did you ever make a back up of any of your roms? If yes , scroll down to backup and restore and select it, next choose Restore, It will give you a list of any roms you have backup before, choose one and it will restore to one of those backup roms, option two if you have a complete rom zip file on your sd card you can choose install zip from SD card, choose zip from SD card, apply and your good, if you dont have a rom zip on your SDcard you can put one there by selecting mounts and storage in Clockwork recovery, Mount USB storage, and put a rom on the root of you SDcard, then go back and run my option two that I just gave you, If for some reason you cant mount the sdcard, shut the phone down, remove the sdcard, use a card reader to install a zip to the root of the sdcard and then follow option two.
Remember before you flash anything wipe data/ and cache.
Panic over, having reset it numerous times and left it for well over 30 mins, it has now managed to load up properly.
Very strange!
Mods feel free to delete this topic if you like...
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
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great