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?
Related
So I just rooted my device and then tried to install a lag fix... when I rebooted my phone after the script, I heard the T-Mobile jingle and then it came to a blank screen. When I pressed the power button there was no response. If I press any of the white keys at the bottom, they just light up. I CAN turn my phone off and go into recovery mode.
This thing has kind of shaken me up so I am willing to go back to an unrooted phone.
PLEASE HELP!
Nandroid, my friend.
Since you are able to boot into recovery, do a nandroid restore.
If you do not have your own nandroid backup There is a thread in the Dev forum you can dowload one from. Just search "[ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)" (I can't hotlink yet. sorry)
This is all assuming you have installed clockwork recovery, which you should have done before you attempted any modding of any sort. Also always remember to create a nandroid of your current system before trying something that is still in beta.
i got same problem here and a don't have clockwork recovery :-(
Then you have to use odin if you don't have clockwork...
My phones have been flashed more than Girls Gone Wild..
[email protected]
I think I found a fix that works...
I just went to recovery mode, and deleted all user data.
I then rebooted and still had a blank screen for about 10 seconds, and then my lock screen came up.
Worked for me! Thanks everyone.
nearblack said:
So I just rooted my device and then tried to install a lag fix... when I rebooted my phone after the script, I heard the T-Mobile jingle and then it came to a blank screen. When I pressed the power button there was no response. If I press any of the white keys at the bottom, they just light up. I CAN turn my phone off and go into recovery mode.
This thing has kind of shaken me up so I am willing to go back to an unrooted phone.
PLEASE HELP!
Click to expand...
Click to collapse
Sorry to resurrect old posts, but I would like to know If after rooting and lag fixing it, it didn't show ABSOLUTELY NOTHING on boot screen and you were only able to hear the sounds and the buttons lit up...
I have a Vibrant on this situation and would like to know I this procedure can fix it.
Best Regards.
Just wait 10 mins if nothing do a battery pull...boot...wait another 10. It will boot after that. Had same issue on two vibrants.
Sent from my SGH-T959 using XDA App
Happendd to me. Just let it sit there. It'll boot.
Sent from my SGH-T959 using XDA App
This happen to me I tired volume up+down+ power nothing happen...... here's what I found...Unplug ur battery n plug it back in with ur usb n when it turns on use adb on ur computer..... adb reboot recovery n do a data wipe
Hope this helps
Sent from my SGH-T959 using XDA App
Thanks for your answers, will try them all and report results.
Best Regards.
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 guys, recieved my phone back from T-Mobile all repaired and working again
I ran the Advanced Hack kit http://forum.xda-developers.com/showthread.php?t=1259821&highlight=ace+hack+kit, followed the instructions, it all went well, said it completed. Phone hung on T-Mobile flash screen for 15 mins. Pulled battery, powered up, hanging for another 15 mins.
Powered up into Hboot, still S-On.
I can access Clockwork recovery OK also.
Phone still hanging, so selected restore factory settings. Hangs at flash screen.
I restored my Back-up of RCMix3D (probably a bad idea, but ran out of things to try). Rebooted, hangs at T-Mobile screen again.
I'm pulling my hair out now, what can I try??
I wanted to try the Hack tool again, but it won't connect without the phone booted. Also, I tried running an RUU, again it won't run without the phone booted.
I just copied the stock T-Mobile PD98IMG to the SD card, updated, went smoothly, now won't boot at all
bumping to the top
All sorted now guys, attn1 helped me out loads last night, this guy's a genius!!
Big thanks to him for all the help, donation going his way on pay day!
Edit, a mod may as well close this
mushtafa said:
All sorted now guys, attn1 helped me out loads last night, this guy's a genius!!
Big thanks to him for all the help, donation going his way on pay day!
Edit, a mod may as well close this
Click to expand...
Click to collapse
Well,
if you talk to attn1 again, please tell him to contact me.. I'm stuck with my dhd aswell.
My problem is:
Few months ago i rooted my unbranded DHD, installed CyanogenMod 7.1, it worked perfectly fine for a couple of months, but a few days ago, my phone was on but did not respond anymore. I tried to reboot it, but it got stuck at the white screen with the HTC logo (sometimes it bootloops, other times it freezes)
I rebooted the phone with the volume down key pressed, so it would give me that menu,
scrolled down to "Recovery", i get the recovery menu from ClockworkMod, but then my volume key does not work ! i can not do whipe or anything else, the phone freezes.
I mounted the SD card in my PC, cleared it, put a rom in root of SD card and call the rom "PD98IMG.zip" and put the SD card back in my phone. I start the phone with the volume key down pressed, i get that
white screen with the menu and it then finds the .zip file.
It then reads the image, parses the image and then tries to load "NV.img" on which my phone freezes again.
I tried CyanogenMod and LeeDroid, and a stock rom. They all do the same thing, as written above.
When i connect my phone to my PC, my pc tries to install the driver, but gives me an error, saying the device is not known. I have installed both HTC Sync and the SDK. Tried it when i had only HTC Sync
installed, did not work either.
I also tried a RUU (.exe file) but this program tells me there is no device connected...
My phone is over a year old, so i have no warenty anymore, that's why i rooted it.
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
The same thing just happened to me! Someone please help us! IS there a solution to this?
dsljk2009 said:
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
Click to expand...
Click to collapse
colbyrainey said:
The same thing just happened to me! Someone please help us! IS there a solution to this?
Click to expand...
Click to collapse
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
colbyrainey said:
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
Click to expand...
Click to collapse
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
jocyrus said:
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
Click to expand...
Click to collapse
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
audit13 said:
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
Click to expand...
Click to collapse
It didn't work. Any other suggestions? :|
jocyrus said:
It didn't work. Any other suggestions? :|
Click to expand...
Click to collapse
Don't know of any other methods because holding down the power button got the phone to turn off and allow me to get into download mode. From download mode, I was able to restore a stock 5.01 ROM to my phone via LG Mobile Support Tools.
LG G2 Bluescreen then no boot after disconnecting battery
Found my LG G2 with a completely blue screen. It would not turn off. Took it apart and disconnected the battery. Reconnected the battery and there was only a blank black screen and the phone would not boot. Zilch. Even with pressing the power button with the volume down to boot into recovery.....still zilch.
I sucessfully got my phone to work again using a hair dryer trick on an LG G3, which I found here.
1. I took the back off the phone, disconnected the battery, and removed the SIM card.
2. I then used a hairdryer on high heat and blew the heat over the uncovered areas for 10 minutes.
3. I let the phone from hot to warm, reconnected the battery and put it all back together with the SIM card replaced.
4. I booted into recovery and restored a TWRP backup, and my LG G2 is working like a champ again.
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.