Related
So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
nachos011 said:
So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
Click to expand...
Click to collapse
try taking sd card out and boot into hboot
May be restoring the nandroid could help. I am not sure, but you can try.
Sent from my HTC Wildfire using Tapatalk
he can't get to the nandroid though if he can't get into recovery,
have you had any luck nachos?
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Quite strange...I had similar issue when I first flashed my HTC Desire where the screen was just blank, but it was at the time when the Desire moved from AMOLED to SLCD and some of the flashing caused it not to work...I thought I also bricked my phone but then flashed again then worked. Created a GoldCard just in case...good luck and just be aware that some phones may require a GoldCard to flash properly.
nachos011 said:
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Click to expand...
Click to collapse
So what you were facing was the black screen and everytime you put the battery back in and hit power it would vibrate 3 times? I am having the same problem. I was actually flashing it with this and it shut down and now I can't get it back on. But you say that after pulling the battery and replacing it numerous times it came back on?
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Could you give more info on Rom recovery kernel you were attempting etc?
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Click to expand...
Click to collapse
Um sorry to say but your screwed. Sounds like a true brick to me
Sent from my HTC Glacier using XDA Premium App
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
TeeJay3800 said:
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
Click to expand...
Click to collapse
He already stated that he could not boot into h boot
Sent from my HTC Glacier using XDA Premium App
mark manning said:
He already stated that he could not boot into h boot
Click to expand...
Click to collapse
He did? I only saw that he could not boot into recovery. I was thinking if his recovery is screwed up, he could still use fastboot to flash a new recovery and then be able to wipe and start over. If he can't get into the bootloader or recovery, then yeah, it's the dreaded B word.
I'd really like to know what kernel he was trying to flash.
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
Me too......
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
First thing I asked.. still no reply kinda sucks when they can't help by responding so we can help them..
Sent from my HTC Glaciee using XDA Premium App
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
Unfortunatly its the same procedure, hold volume down and power on. So if when u do that nothing happens and adb doesn't work your phone is done.
Sent from my HTC Glacier using XDA Premium App
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
I'm not sure what the exact status of your phone is, but usually flashing a kernel does not brick the phone. If anything the ROM won't run right or there will be other problems, but never do they prevent the phone from booting into recovery (the recovery partition uses a completely different kernel). When you try turning it on again, don't bother trying to let it boot normally. Hold down power and volume down and see if you can get into recovery. Then run all three wipe options and flash a new ROM.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
It's happened to me before where I thought I had completely bricked the phone. It crashed in CM7 RC2 when I tried to mess with the DSP settings. After that, I went through the same situation as you. I got tired of it, left it charging overnight while it was stuck on the splash screen. The next morning, it was on like nothing happened. I'm thinking it just needed to sort itself out. Not really a fix or suggestion, but at least an indication that there is hope.
Nah, its dead man. Not on its entirety but virtually. I know that JTAG could be an option albeit, im not sure.
I can assure you though that there must be something extra u must have missed that caused this, did you play with radio's or SPL's? Cause that is how i bricked a magic lol
blah
mine bricked on restoring. got to the point of not responding to anything - power button and even charge indicator no longer worked.
sorry to hear OP. it's bricked.
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
By saying that you used the visionary app to obtain root, is that all you did? Then installed rom manager and etc etc etc? Did you go through the full root method to get S=OFF as well?
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Jay10826 said:
If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Yes it probably is
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Not really, if you were able to run a custom ROM with no problems before then you were rooted properly. Somwhere after you must have gone wrong, not sure where
blah
okay i almost just bricked my hero i was playing around with different prl/radio combos again and when i flashed the 2.2.27 radio using cm witch i do all the time. first it updated the radio image succes reboot now and i did. then it went to the usual black screen with the android guy but it turned of and didnt reboot so i turned it back on and got to the splash screen then it immediately powered of again. so i tried to reboot to recovery and same thing. then i went to hboot and pressed home to get to recovery. so at this point im starting to panic a little because wouldnt have internet access on my computer without my phone,but i remembered i still had the 2.2.27 ruu on my computer and i went to fast boot usb but nothing poped up on my computer i heard the notification noise though so i tried the ruu anyway and luckily it worked! so from there my phone was able to restart normally after the ruu finished and i was able to z4 it and use rom manager to install recovery. so all is well now im just wondering if this has happened to anyone else doing a normal radio update because nothing like this has ever happened to me before and im definitely going to be more careful for now on lol.
dude you crack me up.. at least you have a computer to do all of this stuff at.. thats why i dont flash radios, i do most of what i do on phone, so near bricks put me without a phone for a while.. and i cant have that.. thankfully i havent near bricked my phone in like 6 months (knock on wood)..
yea that was a close call for sure lol.
I unsuccessfully tried to fix my friends moto Droid x after he ran out of battery while flashing a rom. What a retard.
Sent from my HERO200 using XDA App
All this just to get a better signal lmao wow real close call
®patience is a virtue©
Hi, I have a really strange problem.
I had this build of MIUI on my phone for a few months, no problems
droidforums[.net]/forum/dro...-6-stable[.html]
but a few days ago, my phone started giving whacky battery readings (would drop from 40% to 5% in a few seconds) and i wanted to go into CWM to reset the battery stats.
So I had my phone plugged into my car charger, and when I booted into recovery, it didnt do anything, and the screen stayed black for a few minutes (I assumed it was out of power)
When it booted again, ALL OF MY DATA had been cleared and MIUI WAS NOT EVEN THE SAME AS THE ONE I HAD FLASHED. Same version number, sure, but completely different theme and boot animation. (I believe its currently the stock theme)
Well whats even wierder is that I have no data or wifi. Wifi gets stuck on "Obtaining IP address"
And whats even wierderer than than is that every time i boot my phone up, I am greeted with the android activation screen, no matter how many times I hit skip the set up
I obviously cant activate my phone without a connection
it also resets itself every time i turn it on. Any app that I install from my SD card will be gone.
It gets worse. Droid 2 bootstrap does nothing, even though it reports success. I cant use ROM manager as it has to install CWM from the server.
The reboot recovery option from the boot menu just reboots the phone, and there is no blue LED on boot that I can see to press volume down.
(Holding volume down gives me the android with the box and arrow, and nothing else, I know this has to do with recovery but not much else)
So can anyone tell me how to get CWM working again???
THANKS!
Does your MIUI have a boot menu? If it does you should see a light right before it goes to the boot animation.
Albinoman said:
Does your MIUI have a boot menu? If it does you should see a light right before it goes to the boot animation.
Click to expand...
Click to collapse
Nope. nothing. not even su cat.jpg works
I would suggest you sbf back to gingerbread then re-flash your rom.
Albinoman said:
I would suggest you sbf back to gingerbread then re-flash your rom.
Click to expand...
Click to collapse
Is there any way I can avoid this? last time I sbfed it didnt work out so well
You could try a data wipe in stock recovery.
Sent from my DROID2 using xda premium
Actually, i cant even get into stock recovery. I see the android and the box after I press x, but pressing the search key does nothing and the search key works.
You have to press both volume buttons at the same time.
Sent from my DROID2 using xda premium
Albinoman said:
You have to press both volume buttons at the same time.
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
I did this, reset to factory deafualts, and absolutely no difference. I cannot find a single sbf file that is still up (megaupload and multiupload are the only ones I can find)
Can somebody please give me a mirror or give me a way to fix this?
Full GB sbf. http://forum.xda-developers.com/showthread.php?t=1505035
Hey guys, I know this is the 1000th time you've seen this thread. However, I might be a little different.
I've read all the red blinking threads before posting this one.
ROM: CM10 Stable Snapshot
Kernel: Franco r53
Okay, yesterday as I was downloading and I opened a game, my phone screen just turned off completely. I'm assuming it was due to overheating as the phone was getting pretty hot.
So I assumed it died, no big deal. I tried to boot up using power button, no luck.
Then I panicked and started searching XDA for all these red blinking LED of doom threads.
I managed to get the phone to boot up to the Google screen by having it on a wall charger + hold the power button for 10 seconds. But then it just shuts down. I managed to make it stick with bootloader, but only on the wall charger, which isn't much help. On a USB connection with my computer, I'm not able to even open boot loader as it would just open and turn off the phone within a few seconds.
Threw it on the charger over night, no luck.
This morning, nothing has changed.
So what's weird about my situation is, I can get it into fast boot, but only when it's on a wall charger, nothing else. And getting it to Google logo for a few seconds.
Edit: I can't RMA, because when it boots to Google logo, it says bootloader is unlocked (the little icon). And I also bought the phone off Swappa, so it's not attached to my account (is it even possible to claim warranty?)
Interesting this sounds like a hardware problem all right. Simply because you said it works on the mains charger which has an output of 1.2a were as the USB to PC chargers phone at rate of 400ma. I would try getting a replacement if you can. Also are you able to boot into recovery through boot loader if so you could try wiping everything or restoring from back up.
Okay, something weird. I tried a different method of getting into fastboot, and it worked (connected to PC).
Hold volume - (DOWN) by itself WHILE plugging in the USB cable. And now I'm in fastboot. Now I'm just trying to find a way to erase cache via toolkit x)
Edit: Weird, toolkit picks up the ADB device but manual adb doesn't using adb devices command.
I've read another user who fixed this by removing the back, then disconnecting and reconnecting the battery connector. Sorry I can't find the post but I'm sure it was in one of the I bricked my phone threads.
Yeah, I saw that, too. But I don't have the equipments for it, unfortunately
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
draikz said:
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
Click to expand...
Click to collapse
Adb won't work from bootloader, you should have fastboot access though
I'm in fastboot now.
I cannot get into recovery =[ When I select recovery, it would just turn off the phone and the blinking lights begins again.
Try charging overnight with other charger, not stock
Sent from my Nexus 4 using xda premium
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
draikz said:
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
Click to expand...
Click to collapse
That's a good sign! Sounds like it was in some serious deep hibernation! The fact that the battery icon popped up shows u didn't brick it or anything, its just really really dead! However when I had my problem, I had just a red light on all the time, it never blinked
Sent from my Google Nexus 4
Mine is constantly blinking. :'(
And it's probably not dead because I did manage to get it into fastboot. And I got adb to pick up using fast boot.
Every after reflashing recovery, I can't get into anything other than fastboot. When I try to select "Recovery" from the fastboot menu, it just turns off and continues to blink ;[
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
rayford85 said:
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
Click to expand...
Click to collapse
Okay, trying that now. It's been on the charger all night.
How does one ADB with the phone "powered off"?
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Lownita said:
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Click to expand...
Click to collapse
I'm not really sure. I'm just assuming that it died from heat.
joshnichols189 said:
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
draikz said:
I'm not really sure. I'm just assuming that it died from heat.
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
Click to expand...
Click to collapse
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
rayford85 said:
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
draikz said:
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
Click to expand...
Click to collapse
IF ur going to rma it don't forget to lock the bootloader :angel: