[Q] HTC Rogers Magic+ keeps restarting - myTouch 3G, Magic General

Hi
I own a HTC magic from rogers. Im on android 2.1 and 32a motherboard. I tried to root my phone today by using super one click, and it said it was successful. So then i tried to install a rom using Rom manager from the market. I made a custom recovery then tried to install a cyanogen mod 6.1 EB1. It told me to restart my phone so i did. Now my phone just show the rogers screen and restarts. I have tried to hold the power button with the back/home/volume button to no avail. Is my phone bricked?
Thanks for your time

patel1 said:
Hi
I own a HTC magic from rogers. Im on android 2.1 and 32a motherboard. I tried to root my phone today by using super one click, and it said it was successful. So then i tried to install a rom using Rom manager from the market. I made a custom recovery then tried to install a cyanogen mod 6.1 EB1. It told me to restart my phone so i did. Now my phone just show the rogers screen and restarts. I have tried to hold the power button with the back/home/volume button to no avail. Is my phone bricked?
Thanks for your time
Click to expand...
Click to collapse
Pull the battery, put the battery back in, and hold (home+power) until you get into the recovery or the phone starts bootlooping again and let me know what happens.
Sent from my HTC Glacier using Tapatalk

hey thanks for the quick response
Ive tried what you said, it keeps on bootlooping, do you have any other suggestions?
Thanks so much

patel1 said:
hey thanks for the quick response
Ive tried what you said, it keeps on bootlooping, do you have any other suggestions?
Thanks so much
Click to expand...
Click to collapse
Did you leave the battery out for a few seconds. Does it go right back into the bootloop or does it start to boot normally and then starts the loop? Did you try doing the same thing holding back and power?
Sent from my HTC Glacier using Tapatalk

yea, ive tried all the possible of holding buttons (home, back, volume down) and pressing power and none of them have any effect. The phone keeps boot looping. Basically what happens is then i press power, it shows the rogers logo for about 10 seconds, then turns off, then turns back on and shows the rogers logo again. This cycle keeps going on and on. Do you have any more suggestions
Thanks

This has happend to many people trying to use the rom-manager. It's mainly because RM is more for the 32B devices.
But you can still save the phone... just keep pushing the back button and keep restarting..'
I know someone who did for an hour, but he managed to get into fastboot :0)

Hey thanks for the advice
When you mean press back and restarting, do you mean constantly press back while the phone is in bootloop, or take out the battery and put it back in and press back

patel,
i have had the same problem as you. forget rom-manager with phone =\
Google "htc magic keeps restarting" should find info on how to get it into fastboot - i think.
I fixed my problem by downloading the 1.5 sense update from htc's website.
Plug my constantly rebooting phone to my computer and run the RUU update.
Then the phone should automatically grab 2.1 ota - i did this back in december.
So it fixed this problem and i never dared to try and put a custom rom on this phone again.
good luck.

What is the RUU update youare speaking of is it the regular download from HTC?

Related

stuck at splash screen, have tried all the solutions.

Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Difinitus said:
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Click to expand...
Click to collapse
What do you mean by safe mode? Which donut ROM are you trying to flash? Which recovery image do you have? How long was it stuck on the splash screen. You need to give more details for us to be able to help out. What radio and spl do you have?
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Difinitus said:
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Click to expand...
Click to collapse
I'm not sure what you mean by extract update.zip. I think you are talking about fastboot there. Have you tried to flash the rom in the recovery image? you know, by pressing power and home to get to the recovery, then flashing it through there. go into fastboot by pressing power and back and it will tell you what radio and spl you have. once you have that, write that so we can further get a grasp as to your problem. if in fact you still have the 32A configuration, you might want to flash over the 32B radio and and try to flash a 32B rom.
That is my problem, I can't get past the "MyTouch 3G" green screen. I've tried the Home button, Back button, Vol Down button and holding them for several minutes with no result, it stays at the very first screen when it turns on.
I've tried flashbooting from adb but it says "waiting for devices" and my computer isn't picking up any kind of device.
I'm having the exact same problem except im stuck on the vodafone screen. I also tried flashboot form adb but "waiting for devices" is shown and pc wont detect the device.
Did this before.
If you can get into recovery mode, Hold Home button while powering on, you can restore a nandroid backup, if you took one, or put the sappimg.nbh file or the correct items to flash whatever rom.
I had a stock 1.5 Mytouch. I wanted to root and get the 1.6 version of cyanogen, forgot to flash the HTC_ADP_1.6_DRC83_rooted_base as part of the process and had got stuck in the neverending mytouch logo.
If you can get into recovery:
wipe, then put the update.zip files directly on the card.(use a SD adapter, ...)
Choose apply any update from SD
Choose the base files, then the rom if its a newer version
Once those two updates run, reboot the phone.
My never ending logo disappeared, and the phone booted. Newb mistake on my part.
Wait at least a minute or two once this is done.
since the phone is stuck on the original logo and isnt responding to buttons when loading up... do we manually remove and reinsert the battery while holding the home button?
I have tried getting into recovery mode, but it doesn't do anything past the splash screen. Holding the home button while trying to power on the device won't do much.
hey difinitus keep me updated if u somehow get it to work
Even when you take the battery out for a significant time it turns on immediately to the logo screen. Whats the longest you have left the phone sitting at the logo screen.
A small thought, since it was trying to load a rom you had on your memory card, try taking the battery out, and removing the memory card, and then turn it on and wait a bit and see if you get a different result. Its a thought.
If that doesnt work put the memory card back in and turn it on and once its on remove the memory card.
Perhaps the rom on your memory card is corrupt and it is unable to continue to load it, you could even try putting the rom on again using your memory card reader and your computer, thus erasing the existing one.
try plug usb in to phone
take battery out
prees and hold home button
re-insert battery while still holding button
let go after about 3-5 sec
have you tried getting into fastboot by holding back and powering on the phone once you took out the battery? cuz fastboot doesn't initialize after the splash screen, it just pops up as soon as you hit back and power
@Tech no boy; I have tried using several different update.zip and a .nbh and also tried reformatting.
@sitimber; have tried that before, the splash screen still pops up. It just vibrates once and goes to the logo, with any combination of buttons and steps.
@tazz9690; Yes, no matter what I do it still goes to the splash screen. I've been saying that for several posts now.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.

Stuck in bootloader

so ive been flashing roms and have never had a problem till today.
i went to flash the new ava-froyo rom and it went fine and booted right up, and then i tried flashing the new radio and that when everything froze.. it was stuck at the white evo 4g screen...
so i rebooted and it did the same freezein at the white screen..
i rebooted again into hboot, and tried going into recovery and it goes to the white screen again and freezes.
so i only have control in hboot and fastboot. yet i cant get a shell connection. the device is recognized, so im just lost at what to do. been reading for hours and cant figure it out.
thanks for any help.
rdkustom said:
so ive been flashing roms and have never had a problem till today.
i went to flash the new ava-froyo rom and it went fine and booted right up, and then i tried flashing the new radio and that when everything froze.. it was stuck at the white evo 4g screen...
so i rebooted and it did the same freezein at the white screen..
i rebooted again into hboot, and tried going into recovery and it goes to the white screen again and freezes.
so i only have control in hboot and fastboot. yet i cant get a shell connection. the device is recognized, so im just lost at what to do. been reading for hours and cant figure it out.
thanks for any help.
Click to expand...
Click to collapse
Wipe three times wipe wipe wipe if that don't work do whitslack startover method
Sent from my PC36100 using Tapatalk
i cant get into recovery to wipe. do u mean clear storage?
and also, ive been trying to load pc16img off my sdcard, but its not reading. i didnt the sdcard fix and still nothing.. thanks for your help
I kinda had the same issue, try the unrevoked recovery reflash
that's what I did and it worked for me
mine was stuck on the red exclamation point... I tried 5 times by pressing power and +vol buttons, but it was just sitting there for ever...
baiatul said:
mine was stuck on the red exclamation point... I tried 5 times by pressing power and +vol buttons, but it was just sitting there for ever...
Click to expand...
Click to collapse
Are you rooted if not then take battery out put back in hold power and vol down once it goes into hboot pull battery back out then put back in boot up regular way. Happen to me was trying something on non rooted phone went into recovery and got that red! Was like oh man so I did that it v came up hope it works for u
Sent from my PC36100 using Tapatalk
rdkustom said:
so ive been flashing roms and have never had a problem till today.
i went to flash the new ava-froyo rom and it went fine and booted right up, and then i tried flashing the new radio and that when everything froze.. it was stuck at the white evo 4g screen...
so i rebooted and it did the same freezein at the white screen..
i rebooted again into hboot, and tried going into recovery and it goes to the white screen again and freezes.
so i only have control in hboot and fastboot. yet i cant get a shell connection. the device is recognized, so im just lost at what to do. been reading for hours and cant figure it out.
thanks for any help.
Click to expand...
Click to collapse
If all fells do power and vol up hook to CPU HTC sync and try load stock ruu on there
Sent from my PC36100 using Tapatalk
so i can only communicate with the phone thru fastboot..
adb isnt seeing the phone, ive also put a pc36img on my memcard and reboot to get it to load, but it wont load it.. so then i did the sdcard fix and still nothing.. thanks again
ewilson said:
Are you rooted if not then take battery out put back in hold power and vol down once it goes into hboot pull battery back out then put back in boot up regular way. Happen to me was trying something on non rooted phone went into recovery and got that red! Was like oh man so I did that it v came up hope it works for u
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Thanks, that's correct. Not rooted. Thanks.
baiatul said:
Thanks, that's correct. Not rooted. Thanks.
Click to expand...
Click to collapse
Ok yes that's what happen to my friend phone I was just seeing what happen. Man I was like oh my lord got scared thought I brick phone what I did was pulled battery put battery back in holding vol down and power once in hboot pull battery wait a min or so put battery back and boot up normal way it came on I was like whew. If that doesn't work pull battery put back in vol. Up and power while phone hooked to CPU do HTC sync and reload stock ruu let me know if it works
Sent from my PC36100 using Tapatalk

Is my HTC Magic totally bricked?

I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.
Starting to think I'm screwed.
PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.
Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.
me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.
I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?
Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1
try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.

Have i bricked my phone?

Hi. I were running a rooted stock rom with the newest radio and spl and ra recovery. I decided to try rom manager(i think thats what its called). I flashed the recovery, i believe it is called clockwork. When i rebooted my phone it just keeps rebooting at the htc logo. I cant enter recovery or anything. Is there a way out of this or can i just throw it in the dumpster?
Can you get into fastboot? Take the battery out and pop it back in. Then try powering on holding down back+power. You should get a screen with three Androids skateboarding. If you can get the port the information here. If you can and it just does the boot loop, do the battery again hitting the back button repeatedly, give that a few tries and see where it gets you.
Sent from my HTC Magic using XDA App
DonJuan692006 said:
Can you get into fastboot? Take the battery out and pop it back in. Then try powering on holding down back+power. You should get a screen with three Androids skateboarding. If you can get the port the information here. If you can and it just does the boot loop, do the battery again hitting the back button repeatedly, give that a few tries and see where it gets you.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Thanks for your reply but i cannot get into fastboot either. Ive tried holding every single key while booting xD. It just keeps doing the same thing. Reboot at the "HTC Magic" screen. I hangs for some seconds so ive also tried to see if i could grab it from adb but without success.
same incident happened to me. cannot reboot back at last sent back to htc centre.....
rickytjp1107 said:
same incident happened to me. cannot reboot back at last sent back to htc centre.....
Click to expand...
Click to collapse
Did they take it back under the warranty? Did you mod your phone?
Do you get the blue led & black screen when pressing trackball + power at boot?
I get blue led but no fastboot or recovery
Sent from my HTC Desire using XDA App
Can u fix this
Sent from my HTC Desire using XDA App
So that means your device isn't fully bricked - your hardware seems to be working, and you should be able to restore the device using JTAG (search the forums). Though I managed to restore mine by resetting some stuff with draining battery and repeatedly trying again. I'd recommend you to try too.

Phone boots to blue screen

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.

Categories

Resources