Database Info

Bricked and Stuck

Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans

If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:

Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh

Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans

flashing problems

I’m stuck without knowing what to do next.
What did I do? A lot, not knowning exact in which order. I started with stock ICS ROM, rooted and unlocked.
First I tried to install NVFlash, but because in the ATX mode the TF300T wasn’t recognized on my PC the last steps didn’t succeed. Trying all the drivers suggested on this forum didn’t help to solve it.
Though I can manage a connection with the PC in ATX and USB mode. Adb commands works.
I have TWRP installed because I want to ‘see’ the miniSD card for flashing.
When I try to install stock ROM I get the message: unable to Mount “\staging”. Installation failed.
A full whipe and whiping Dalvik are done with no effect.
When I try to install a JB ROM it looks as if it’s succesful, but after a reboot the black screen with bootloader in the left upper corner and NVidia logo right under keeps looking at me.
So turning back to ICS stock doesn’t work and JB neither.
I thought to have a wrong bootloader but which do I need and how to install?
Reading 200 pages for a solution didn’t work for me, maybe I looked at the wrong places but I’m at the end of solutions.
If anyone can help me I’m very gratefull
Regards, Henk-Jan

problem solved
henk-jan said:
I’m stuck without knowing what to do next.
What did I do? A lot, not knowning exact in which order. I started with stock ICS ROM, rooted and unlocked.
First I tried to install NVFlash, but because in the ATX mode the TF300T wasn’t recognized on my PC the last steps didn’t succeed. Trying all the drivers suggested on this forum didn’t help to solve it.
Though I can manage a connection with the PC in ATX and USB mode. Adb commands works.
I have TWRP installed because I want to ‘see’ the miniSD card for flashing.
When I try to install stock ROM I get the message: unable to Mount “\staging”. Installation failed.
A full whipe and whiping Dalvik are done with no effect.
When I try to install a JB ROM it looks as if it’s succesful, but after a reboot the black screen with bootloader in the left upper corner and NVidia logo right under keeps looking at me.
So turning back to ICS stock doesn’t work and JB neither.
I thought to have a wrong bootloader but which do I need and how to install?
Reading 200 pages for a solution didn’t work for me, maybe I looked at the wrong places but I’m at the end of solutions.
If anyone can help me I’m very gratefull
Regards, Henk-Jan
Click to expand...
Click to collapse
What did I do to solve it? Taking the right stock rom
I thought I had to flash 9.4.3.30 but it had to be 9.4.3.29 and that did the trick
I'm happy now

That's great to hear you got your tablet working again. Great job! Maybe next time post this in the Q&A forum where it belongs.

Ramrod421 said:
That's great to hear you got your tablet working again. Great job! Maybe next time post this in the Q&A forum where it belongs.
Click to expand...
Click to collapse
Your absolutely right, thanks for your instruction.

In QHSUSB_DLOAD Mode, nothing working

Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.

usaff22 said:
Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.
Click to expand...
Click to collapse
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/

dc211 said:
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/
Click to expand...
Click to collapse
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip

usaff22 said:
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip
Click to expand...
Click to collapse
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.

dc211 said:
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.
Click to expand...
Click to collapse
Thanks, I knew it wouldn't work after I saw someone on the One XL forums who tried it on his with a USB Y Cable, and didn't look for the zip on the internal storage. I used to think it would work after doing it on my brother's Sensation, but it was a no go for me.
At this stage I think I will have to visit my carrier. Hopefully they can give me a replacement or get it fixed somehow.

This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade

Fofff said:
This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade
Click to expand...
Click to collapse
I tried that, my partitions won't show so it is of no help to me unfortunately.

Help, Goes straight to TWRP on startup

Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc

To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.

Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...

splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks

Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.

I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.

splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.

lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.

Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.

steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.

I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/

[Q] TF101 cwm loop. I've looked (and looked), but..see thread

Alright, I hate being that guy. You know, the one who posts the same question as 50 other people because he is too lazy to search. But in my defense, I have spent the last three days pouring over thread after thread and still can't find the answer, so please be patient and gimme a break!
So, I'm stuck in CWM 5.8.3.4 loop after flashing Katkiss and not knowing I couldn't use the "boot to recovery" option. I've got no access to my micro SD card and my x64 Win 7 won't recognize the TF101 so I can't put my own recover zip on. Cold boot goes to the screen that lets me boot Android or Wipe. If I pick Android, it hangs (for hours). I've wiped everything and reinstalled Katkiss, Revolver, Revolution, but I have the same problems.
Is there a thread that starts from the BEGINNING of the fix and sees it through? I've found dozens of threads that say, "Just input (code), flash, and you're done!", but I guess I'm not that far along. I've bricked Dinc/Dinc2, Razrs, etc., but never had trouble fixing them like this TF101.
I've got ADB, JDK, Ubuntu, etc. since I've tried numerous times. Also, I've had no luck with the one-touch fixes. I know I'm missing something easy, I just can't figure it out.
Thank you.
Incidentally, I've tried ***http://www.transformerforums.com/fo...ry-bootloop-fix-tested-my-c10-windows.html*** , but the SDK files come in a zip, not exe and none of the files execute/install in such a way that will let me input commands. I know I'm missing something because a soft brick isn't that big of a deal.
Huh. I don't know what happened, but it involved me cleaning the screen, accidentally pushing buttons, and rebooting, and now it works. No clue, but as long as I never shut it off again, I'm set!

You're gonna need to get the PC to recognise it to fix it I'd say
Easiest way would be using Easyflasher to get TWRP recovery installed, it sounds like you have stock recovery installed at the minute
http://forum.xda-developers.com/showthread.php?t=1688012
Few people have needed new cables to get the PC to recognise the TF again, might just be needing the correct drivers though which are also linked on that page
Basically install the drivers, put the TF into APX mode,
(Vol Up & Power from powered off state while plugged into the PC)
Then run Easyflasher as admin and choose to flash TWRP (CWM is probably the reason for the bootloop, it doesn't play nice with JB ROMs)
Once you have TWRP installed, flash whichever ROM you want from new recovery and you should be good to go

I appreciate the suggestion, but that isn't doing it. I have the tab booted up and recognized by Windows, but when I try to update to a different CWM or TWRP, nothing happens. I can reboot into CWM 5.8.3.4 all day, but it won't say anything about any different recoveries I've tried to install, though the recoveries appear to be installing correctly according to the dialog given on the tablet.
I've also tried running NVflash, but nothing happens (apx drivers installed). The BAT file briefly says USB not recognized and closes.
Further, I've tried Easyflasher / one click root+recovery and I just get messages saying "ADB server out of date. Killing." The tab still reboots, but upon rebooting, it gets stuck in CWM 5.8.3.4 unless I force cold boot.
I guess the best way to describe this is to say that no matter what I do with the tab or different recoveries, I can't get rid of CWM 5.8.3.4 and no matter what I do, it default boots into CWM.

It default boots into CWM.... I think that is the key here
I remember something about that from a while ago, having to hold Power & Volume Down to boot normally, as if the OS and Recovery partitions were reversed
Unfortunately I can't remember the solution atm, but if you head over to transformerforums.com or give frederuco a PM from here or over there, Im pretty sure I remember him having a solution some time back

I shot him a message. Thanks for the suggestion.
I swear all I did was root, install Katkiss, and reboot into recovery. Is this a common problem to have THIS much trouble with such a simple process? I know now that booting into recovery can cause a loop, but this seems like way too much.

It's having CWM as your recovery when you flash a JB ROM that causes the problems
CWM & JB = Problems
TWRP is the recovery to use once you get out of this mess, good luck