Database Info

[Q] Bricked in Recovery mode!

I have a TF101 SN60 - SBK1. I was trying today to root it to instal a stupid USB modem app and i bricked it.
Right now it is in recovery mode and i can`t get it out. Tried all the combination of the buttons and still doesn`t work.
I tried to reput the stock rom from Asus and i had success(2 times) but was still in recovery mode and after that i tried once more and it failled.. now i have 7 " !!!!! phone update failled !!!!" and i am very pissed and mad as i do not know what to do no more. I wasted 5 hours today trying to do something to it but i can`t no more. Please help me with some tips or maybe help me put it back to it`s normal state. Thank you.

Which recovery and version do you have installed, and how did you install it?

almost same issue
I have cwm 6 something and it wont recognize the sd or paths my laptop wont detect it have every method downloaded nothing what can i do about this?? Bricked for a long time !!

sriv2102 said:
I have cwm 6 something and it wont recognize the sd or paths my laptop wont detect it have every method downloaded nothing what can i do about this?? Bricked for a long time !!
Click to expand...
Click to collapse
Have you tried APX mode?
I would try another PC, or get a new charging cable. It is possible for the USB cable to charge but not work for USB. Happened to me.

accidentally formatted my karbonn a9+

i tried to hard rest my Karbonna9+ android phone. i pressed Power+volume+home button. after that there was an error displayed on the screen saying "ENTRY QPST DOWNLOAD". i quickly searched on the internet but wasnt able to find any successful link. but then my computer asked me to format the device, i thought this will reset my phone but unfortunately i was totally wrong. after the format i tried to start my phone again but nothing happened. i also tried different combinations of keys but all nothing happens not even a single pixel lit up lol. then i downloaded cherry mobile flare software and AIO flasher and all the image files and other files required. they didnt work for me too coz my laptop (windows 7, 64 bit) doesn't recognise the device (unknown device or Com5 error). i tried to flash it in fastboot in AIO flasher. it says flashing but nothing really happens even after 10-15 minutes. all the online forums i searched they say enable debugging mode on ur phone in order to reboot but i dont know how the heck i can do it when my phone doesnt even start up lol. I am left with a dead phone now. can anyone please help me out and solve my problem. and please advise me step by step what to do next in order to get my phone working please...

Try this thread and let know if its what you want.

[Q] LG optimus pro G bricked after using exitrecovery.zip

hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....

babaghanush said:
hello,
I hope someone can help me with my AT&T LG Optimus Pro G phone, which I have royally screwed up.
I was experimenting with the cyogen mod and after installation I installed the freegee app and once the cwm recovery was installed, I decided to go into the recovery by holding down up volume and power button.
Once I was in recovery for CWM i couldn't exit out, and the phone constantly booted into recovery after every reboot, even if i took out the battery, and powered it on.
I tried reflashing the cynogen mod through the sd card, and even though I would get success message the phone would still reboot into the cwm recovery.
I started doing research on the internet and i found file exitrecovery.zip that could be used to possibly get the phone out of the cwm recovery.
After installing exitrecovery.zip, I rebooted the phone, and now I have complete black screen. There are no light, no hints the phone is even turning on, and I can't get into recovery( or at least I can't tell). The only thing now is that when i connect the phone to the computer the window tries to install drivers for the device, and eventually prompts to insert a CD for LG drivers. I already have LGUnitedMobileDriver v.3.10.1 connection drivers installed from their website.
Please help, I am really stuck here..... and have no clue what to do. I am fairly new with rooting and modding, and I am extremely miserable.
The phone is still under warranty from LG. Anyone if all else fails, and since the phone has no screen or lights, whether they would replace it?
Attaching the exitrecovery.zip that I used.
sobbing....
Click to expand...
Click to collapse
Find flow ROM with expansion .exe and try it to sew from a computer.

could you further elaborate please
lykosha said:
Find flow ROM with expansion .exe and try it to sew from a computer.
Click to expand...
Click to collapse
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.

babaghanush said:
hi, thanks for your reply. Again I very much new to the rooting and android OS tinkering, and nowhere close to an experienced user.
I tried to use google with your information in regards to how to use flow ROM with expansion.exe, but did not get any leads.
I would appreciate if you could elaborate more on this process.
When my phone is connect to the computer via usb is is constantly trying to install drivers. I had already installed LG usb connection drivers in the past and it was successful. It almost seems it tries to install driver yet fails after receiving no input from the phone, and then request LG CD with drivers.
Click to expand...
Click to collapse
Try to find driver on the web-site of producer. Set them. Overload a vehicle in Bootloader. In the controller of devices on компе must be determined your device. Then on a computer start sewing - .EXE.

Did you get this problem resolved? I have the exact problem with the exact phone!!!

thank you very much

[Completed] HELP!!! Unbrick Xperia S (bootloader problem no flashmode)

I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)

Hi,
You've asked in the correct section: http://forum.xda-developers.com/xperia-s/help/how-to-unbrick-xperia-s-lt26i-tried-t3265523/
so I'll close this thread.

Oneplus 6 unable to be unbricked

Hi everyone,
A couple of days ago I rooted my Op6 and then decide to flash No limits rom via recovery (blu spark), as I was used to do with my last android phone, the Samsung Galaxy Note II.
Unfortunately I missed something and now it is stuck in the bootloader screen. Nothing works from the phone and I couldn’t revive it. I use a Mac but I tried all tools that are adviced here on XDA with my friend’s Sony Vaio but without success.
I managed to update drivers but I cannot run a flash-all.bat and I cannot use MSMdownload tool.
How can I do? Thanks to anyone who will manage to help me!!

EDIT: Sorry, just noticed you say you cant use the MSM tool. This one worked for me.
You could try this
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
Worked for me.

Check the guide about unbricking and if You are unable to use flash-all.bat so you Have to flash commands One by One. It's worked for me a few of months ago.

It doesn’t work either that way. I updated my drivers, but no computer is recognizing the phone.
I tried from changing usb cable or port to changing computer, to change methods.
I didn’t found any solution here on XDA, I tried everything!!

Make sure u use the cable included with the phone. Some cables doesn't work

Neither. I tried with the original and two others that I have.

if possible do you have windows? the flash-all.bat works for windows and is better to use(i was unable to use it normally in linux). What happens when you show flash.bat?

I tried Mac and Windows. On Windows it always shows in terminal "waiting for any device", even if I uploaded the drivers and made everything possible.

Did you put your OP6 into fastboot mode in correct way? I mean you might be doing the wrong procedure when entering fastboot mode.
It happened to me for the first time, I came from Samsung and I thought the phone needs to be stayed on the fastboot menu screen just like Samsung but no.
You need to turn it off and reboot it while pressing home and vol down button simultaneously until the PC recognize.
Good luck unbricking~

I always powered it on via power+volume up before connecting to the usb cable, because connecting it while powered off always resulted to power it on automatically on bootloader screen