Database Users

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.

A500 suddenly died

Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.

Dopius_Fishius said:
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Click to expand...
Click to collapse
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD

Moscow Desire said:
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Click to expand...
Click to collapse
Thanks MD. I looked up the threads you suggested, and after a lot of screwing around I have installed the APX drivers and used blackthund3r's APX Flash Util 0.3 (The link is broken to the current version) to attempt a recovery of my tab.
Its now sitting at an Acer screen, "Entering Acer Download Mode" while the flash util is sitting at:
Nvflash started
[resume mode]
It's been there for about 10 minutes now, no progress to report. Is it worth just sitting it out, or now that the damn tab shows SOME signs of life, can I just restart it and reset to factory?

And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...

Dopius_Fishius said:
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Click to expand...
Click to collapse
erm for now i would make sure you have all backups of data, cpud etc,.. just incase. you can just sit em on your computer i always try to keep a nandroid of all 3 of my devices each month or so.:good:
edit: and of course keep the link for the thread MD recommended.

Gee. Sounds exactly like mine....
The only thing I haven't tried is an update .zip, but I don't hold out much hope.
Considering parting out at this point....

Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.

Dopius_Fishius said:
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Click to expand...
Click to collapse
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD

Moscow Desire said:
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Click to expand...
Click to collapse
Tried the update.zip - nada
Tried timmiedean yesterday, went into Acer Download mode OK, failed....
If dolps is like mien, the first time he tries to go into recovery, it will crash again...

It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....

tennessee_titan said:
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
Click to expand...
Click to collapse
I told you maaaannnn, go see me cousin in Jamaica maaaannnnn. She do some good things you see
Glad it's running again.
MD

First, is this a SOD?
I can kill it by booting into recovery and get it back by using Blackthunder flash tool to go into APX and letting it sit for 20 minutes or so. Close the program, unplug, reboot and it is back. I would like to use timmiedean (td) and go back to square 1, but it fails at the image detect ( displays ICS 4.0.3 Civato as the current image, a red X for the new image). Has td been proven to work reverting from ICS? Will a boot recovery reflash and a new ROM flash solve this? Is there another way to get out of ICS back to HC?
Any suggestions/comments welcome!
EDIT: I flashed FLEXxx V4. Shut it off, problem still there....

Really frustrated. Trying to use the timmiedean tool, but it requires that the unit be shut off in the middle of the process, which kills it. Does anyone know the whereabouts of the blackthund3r revert tool, or the .apx package for his flash tool. I can't find it...

I'm done with this one. On Ebay for parts.... GONE!!!
Have an A100 now, rooted, unlocked,. on Relix
1 more A500 coming next week

OTA Bootloop Help

I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?

toopty said:
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
Click to expand...
Click to collapse
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!

cgillie92 said:
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
Click to expand...
Click to collapse
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.

toopty said:
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
Click to expand...
Click to collapse
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.

cgillie92 said:
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
Click to expand...
Click to collapse
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.

toopty said:
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
Click to expand...
Click to collapse
I hope someone helps us out. I really cant afford a new one because the warranty is void. I was going back to stock because of all of the little bugs that need to be ironed out in roms. cause kit kat is around the corner hopefully and my problem virtually is the same i might have had my brightness on auto or something prior to that.

Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620

Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.

Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
After following the instructions on the above link i was able to get fastboot status on my phone. It did not fully restore my phone however. I was able to flash twrp via fastboot. I was then able to boot into twrp and run the command at this link via twrp terminal http://forum.xda-developers.com/showthread.php?t=2451696
Thanks to everyone for all your help.

toopty said:
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Click to expand...
Click to collapse
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/

cgillie92 said:
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
Click to expand...
Click to collapse
Ignore all the message, unplug you phone get ready to type the command, plug it in and immediately press enter to run the command. it took some trial and error, and i had to use this other post to help me out. I actually got fastboot working first, then used this post to http://forum.xda-developers.com/showthread.php?t=2477595 to get download mode working, and to flash twrp recovery. After that i used this post to run the command line from with twrp. http://forum.xda-developers.com/showthread.php?t=2451696 . I didn't have to flash the factory tot to my phone, but i have that option now because download mode is working. This process will work, there is hope for you getting your phone back. I'm fully recovered. I decided 12B is not worth it in the mean time, but if you want 12B you need to flash the factory tot and then upgrade. There is a way to root 12B, but as of this time you are unable to get Custom Recovery on it.

Fried my G2

Hey folks. I recently borked my Verizon G2. I was running a CM11 nightly, decided to try out Mahdi ROM, but apparently something went wrong. Everything flashed just fine according to TWRP, but now I can't boot up. When I turn on the phone I get a black screen with small text that says
Code:
[660] Fastboot mode started
[710] udc_start()
if I plug the phone in to my PC from that screen, it adds
Code:
[870] -reset-
[880] - portchange-
[3720] fastboot: processing commands
When I enter download mode and plug the phone into my PC, it shows a screen that says "Firmware update" with a standard "do not unplug" warning, then there is a box at the bottom that says "B53" in gray text, and "ROOTED" in red.
I've tried several methods of restoring, but none of them worked for me, and they didn't even seem to have any effect at all. Here are links to the posts I've followed to try to fix it.
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2448960
So I'm lost, and I have already gone a few days without a phone, and I need it for work and whatnot. Can anyone help?

Try this
http://forum.xda-developers.com/showthread.php?p=48765620
Sent from my LG-D802 using Tapatalk

mrm43 said:
Try this
http://forum.xda-developers.com/showthread.php?p=48765620
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Couldn't get that to work

If you can boot into recovery, do a FULL wipe, then try to flash back to stock again. The restore to stock fails if you do not wipe your device before hand. Also, you don't need to use any special method to flash back to stock, just install kg's usb driver form their site, then install their mobile support tool (again from their site) when the tool opens, go up to the right hand corner and press device recovery or something like that and connect your device in DL mode, then the tool will restore the device back to the stock rom.

MalignantQuechnitlan said:
If you can boot into recovery, do a FULL wipe, then try to flash back to stock again. The restore to stock fails if you do not wipe your device before hand. Also, you don't need to use any special method to flash back to stock, just install kg's usb driver form their site, then install their mobile support tool (again from their site) when the tool opens, go up to the right hand corner and press device recovery or something like that and connect your device in DL mode, then the tool will restore the device back to the stock rom.
Click to expand...
Click to collapse
Full wipe meaning advanced wipe and check every single box including storage...EVERY box...lol.. And yes this will help you get booted back up.. Been there done that.

joewaz said:
Full wipe meaning advanced wipe and check every single box including storage...EVERY box...lol.. And yes this will help you get booted back up.. Been there done that.
Click to expand...
Click to collapse
all of this happened to me, and i'm past it, but i never found out if this phone is truly unbrickable?

Finally got it up and running again. Have to start from scratch, but at least I have a phone. What finally worked for me was the LG Mobile Support Tool. I plugged in my phone and let it do its thing. It took a while but it worked. Now to go about re-rooting...
Thanks for all your help folks!

cedbled said:
all of this happened to me, and i'm past it, but i never found out if this phone is truly unbrickable?
Click to expand...
Click to collapse
Lol with all the crap I've done to it I don't think you can brick it.. A few times my heart jumped out of my chest but I managed to get the ticker back in my chest lol

[Q] Did I turn my G2 into a non-recoverable brick?

Good evening everyone,
I will start off by saying that I really didn't do things by the book this time around. I have run out of ideas even as to what to Google to find similar cases to mine.
I wanted to flash Cyanogenmod onto my G2. Since I already had CWM installed, I loaded the ROM and Gapps. After wiping the phone, I went to flash from the zip. The flash failed. I tried again, and it happened again. I wiped the cache and dalvik again, and tried again. Still no flash.
At this point I go for the reboot only to realize that my phone is now stuck in a bootloop that is contantly landing me back into recovery.
I believe I really screwed up from here as I read about a way to exit the cwm bootloop by flashing a new "exitrecovery.zip" file. Since ADP wouldn't push the file for some reason, I used that function where the phone waits the file to be pushed and flashes it. That succeeded.
The phone switched off (after hanging on CWM for a bit) and now won't do anything at all. No boot logo, nothing. Can't get into CWM anymore either.
The computer brings up a bunch off drives which it wants me to format when I plug the phone in. Only one of them has a folder called "image" on it.
The display switches on, but won't do anything there.
Holding power+up reboots it after a few seconds and so does power=down.
I am thinking of just seeing if I can get it assessed by my carrier, hoping they'll have the tools to just reflash it... somehow. Else, is there a way to potentially fix this?

Back to stock
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.

Rule number 1.
ALWAYS MAKE A BACKUP.

bodom_hc said:
Rule number 1.
ALWAYS MAKE A BACKUP.
Click to expand...
Click to collapse
I have a backup I made with CWM.
If that helps, please point me into the right direction to restore it. I fail to see how I can do that without even being able to start cwm up.
missiveusa said:
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.
Click to expand...
Click to collapse
I will try this, but the screen never shows anything at all