Database Users

[Q] i flashed a wrog rom and i cant go to download mode now !!?!

i mistakly flashed an international Rom that was suitable for samsung galaxy s i9000 on samsung vibrant T-Mobile
now when i turning on the phone, many forse close errors coms up and they cant be okey!!
they just stay on the home screen and i cant do anything!
im tried all the ways to go to download mode ,but none of them works!
when i pull the battry out and bring it back and hold both volume up and down and connect the usb cable to the phone,it just go to charging mode,not downloading !!
any one can helpe me plz?

Try plugging in the usb without the battery then hold both volume buttons insert battery then press power works for some
Currently running ______________! (<----Insert Rom Name Here)

It may have been because your keys are now remapped, try different combinations

jpelagio11 said:
Try plugging in the usb without the battery then hold both volume buttons insert battery then press power works for some
Currently running ______________! (<----Insert Rom Name Here)
Click to expand...
Click to collapse
i tried it too,but still doesnt work!
runing rom version : Froyo | I9000JPJPG
anthonys2r said:
It may have been because your keys are now remapped, try different combinations
Click to expand...
Click to collapse
which keys for example?

This should work!
This should work but you have to follow to the word, please:
Get your phone into DOWNLOAD mode by turning off your phone (leave battery in) and plugging it in (use USB that is connected to your PC). Wait for the green charging screen to come up. Hold Volume Up + Volume down, then press and hold Power. Let go of POWER as soon as the screen goes BLACK.
Let me know how it went.
Cheers!

Battery pull, put battery back in. Hold Vol up AND Vol down at the same time, and then plug in USB hold for 5 seconds while still holding the volume buttons.

If you had debugging checked, you can use ADB to get the phone into download mode.
Code:
adb reboot download

i tested all the ways befor but not answering
until i used the adb
i finally succed to rich the download mod page
bout when i started odin and start flashing official rom,the process doesnt start really and stoped at loading
(there was 2 pit files in official rom page,one of them ziped with the odin file download link : s1_odin_20100513
and another one was simple link for downloading suitable pit for the rom : s1_odin_20100512
and i tested s1_odin_20100512 pit )
i waited about a 45 minuts ,but nothing changes!
i restarted the pc but still the same
atlast i forsed to remove the cable and tets in again
but the pc couldnt know the phone and no connection was happend!
i removed the battery and put it back again
and when i powerd on the phone it shows the brake icon
i tested all the ways in this threades (except hardware metods):
http://forum.xda-developers.com/showthread.php?t=854924
http://forum.xda-developers.com/showpost.php?p=9663212&postcount=53
http://forum.xda-developers.com/showthread.php?t=804305
but not answering yet
can any one help me?

Can you still get into Download Mode the way I mentioned above, without ADB at this point? And if you do, does Odin see the COM5? If both true, i'll send you the link to the two files you need to flash to Stock. Don’t worry about Windows seeing your phone now, but Odin must see it.
Sent from my SGH-T959 using XDA App

roumenjr said:
Can you still get into Download Mode the way I mentioned above, without ADB at this point? And if you do, does Odin see the COM5? If both true, i'll send you the link to the two files you need to flash to Stock. Don’t worry about Windows seeing your phone now, but Odin must see it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Go here: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
They have the correct, working files, i tried it myself. It is very important to only have 2 checked boxes on Odin when you flash and nothing else. In my case it failed the first time, I repeated the entire process again and it passed, it shouldn't take longer than 10 min. Good luck!

Just for good measure, it's not a bad idea to reinstall the Windows drivers. Also, Odin v1.3 has the best results imho. Try flashing JFD with the partition box checked off.
Sent from my frozen yogurt powered Vibrant

roumenjr said:
Can you still get into Download Mode the way I mentioned above, without ADB at this point? And if you do, does Odin see the COM5? If both true, i'll send you the link to the two files you need to flash to Stock. Don’t worry about Windows seeing your phone now, but Odin must see it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i tried the above way for now
but the screen just goes balck an after 2 sec it shows the same brake avatar
no way to reach the downlod mod
roumenjr said:
Go here: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
They have the correct, working files, i tried it myself. It is very important to only have 2 checked boxes on Odin when you flash and nothing else. In my case it failed the first time, I repeated the entire process again and it passed, it shouldn't take longer than 10 min. Good luck!
Click to expand...
Click to collapse
unfortunatly i checked the "repartition" box by the advice from one of my friends and process stoped at loading and i hade to remove the cable and u know what happened aftar it......

Ups...., I've seen a lot of people screaming because they checked that box, but everything has a way around it.
Try this if you haven't already:
1. Remove SD and SIM card
2. Remove battery
3. Plug the phone into USB (connected to PC)
4. Press and Hold Vol-up and Vol-down buttons
5. Install the battery back in while holding the buttons
Anyway, what is that brake avatar you are talking about look like? (can you post a pic)
Also, regardless of the screen on the phone, after the boot procedure, if you start Odin, does it see the phone (COM.....green)?
If none of the above helps, look up ADB guide, that's another way to manipulate the phone. Let me know how it goes with Odin.

roumenjr said:
Ups...., I've seen a lot of people screaming because they checked that box, but everything has a way around it.
Try this if you haven't already:
1. Remove SD and SIM card
2. Remove battery
3. Plug the phone into USB (connected to PC)
4. Press and Hold Vol-up and Vol-down buttons
5. Install the battery back in while holding the buttons
Anyway, what is that brake avatar you are talking about look like? (can you post a pic)
Also, regardless of the screen on the phone, after the boot procedure, if you start Odin, does it see the phone (COM.....green)?
If none of the above helps, look up ADB guide, that's another way to manipulate the phone. Let me know how it goes with Odin.
Click to expand...
Click to collapse
i was done all of this ways befor ,but i tested again and nothing happened again
odin couldnt reconize the phone and the phone doesnt go to download mode with the pulling the volum keys!
i really cant understand that whats going on with this phone that any way work on it!
im going to try adb for my last chance
here is the brake avatar:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i hope in can hepl

i extracted android sdk on the root of my windows drive
started cmd
and typed :
Code:
c:
cd toos
adb reboot download
in last time i could reach the downloading mode with this orders
but here i got this answer from cmd :
device not found
am i entered the correct orders?
and is this a true way?

Ah, OK. Now that I see the avatar you have been talking about I can tell you it's not soo bad. I was sitting where you are just a week ago, also by flashing the wrong ROM. The difference is that I did not have so much trouble getting into download. Do this to check if the ROM you flashed did not disble your vol buttons.
-pull the battery out to make sure the phone is off and put it back in (do not power it)
-connect the charger to the wall outlet (not PC) and then to the phone
-once the battery animation comes up, wait for the screen to turn off (about 1-2min)
-once off, press (not hold) the vol up button, the battery animation should come back (this would be a good sign)
-do the same using the vol down button once the animation dissapears again
-if true for both buttons, use one of them to bring the animation back on the screen, hold both (vol up and vol down) buttons, press and hold power button (do not let go of the vol buttons), AS SOON AS THE SCREEN GOES BLACK, let go of the power (still holding the vol buttons) until you see Downoad Mode.
If you manage to get into Download, re-install the USB drivers on Windows just in case, unplug you phone from the wall, it will stay in Download. If you're using a desktop PC, use the USB ports in the back, dirctly on the mother board and not the extensions in the front of the box since they might run less power, as in my case and Winsows would not see the phone. If you're using a laptop, I gues it wouldn't matter inless you have a USB hub, if you do, remove it. One more thing to consider, make sure you have the latest Odin, or maybe try a different version, uninstall and install it back on after the drivers.
If you don't get into download, leave the phone on and start Odin a few times to see if it catches anything, unplug the USB, plug it back in and start Odin.....etc.
I hope you left USB debugging ON the last time your phone was up and running. Consider doing these steps a few times before you give up, I had to do some of the procedures twice before success. In the meantime I will see if someone has some extra commands for ADB.
Good Luck!

HDRAGON said:
i extracted android sdk on the root of my windows drive
started cmd
and typed :
Code:
c:
cd toos
adb reboot download
in last time i could reach the downloading mode with this orders
but here i got this answer from cmd :
device not found
am i entered the correct orders?
and is this a true way?
Click to expand...
Click to collapse
No, here:
1. Open Command Prompt:
type: cd C:\Program Files\Droid Explorer\SDK\Tools\
then type: adb devices
(you should get feedback off this command telling you details about your phone)
Then type: adb reboot download
or try: su
reboot download
If you still can't get there, try this:
mount -o rw,remount -t yaffs2 /dev/block/stl9 /system
and then repeat the previous steps.

Once you get back into download mode.....
If you are running Windows 7:
Reboot your system and hit F8 to get the safe mode options, then select to disable driver signature enforcement. Make sure you right click on Odin when you start it up and select run as admin.
If you do not disable driver signature enforcement ODIN will not work on windows 7. It'll freeze in the beginning of the flash.

imitebewrong said:
Once you get back into download mode.....
If you are running Windows 7:
Reboot your system and hit F8 to get the safe mode options, then select to disable driver signature enforcement. Make sure you right click on Odin when you start it up and select run as admin.
If you do not disable driver signature enforcement ODIN will not work on windows 7. It'll freeze in the beginning of the flash.
Click to expand...
Click to collapse
I did mine on Win 7 and didn't have to do anything special, installed and ran...
Then again, there are different cases.

im currently stuck at that same "brake screen" It takes me about 20 mins each time to get into download mode where odin and xp recognize the device but when i start odin it freezes at file analysis. i know it had debugging on before. when i try to adb it hangs for a sec then says device not found.
im going nuts
edit...1 click odin was the problem. used the regular with the correct files. boom. im up and running

LG G2 Stuck with grey lines after using auto rec. please for god sake help me.

ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device; LG G2 D802 32GB

Some one please?

DroidsRugly said:
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
Device; LG G2 D802 32GB
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.

This is why I worry messing around with my G2

Have you tried long holding the power button?
Sent from my Nexus 6 using Tapatalk

Same thing here. Any answers? I can hold the power button and it turns off for a second then turns itself on and these lines show up again. Same setup after using AutoRec on 4.4.2 rom.

This is a known problem. Have LG send you a new one

blastagator said:
This is a known problem. Have LG send you a new one
Click to expand...
Click to collapse
Sadly way outside the warranty. So it's pretty much toast?

did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?

stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.

walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
Make sure you're phone is fully charged. I had a problem entering download mode with low battery. I also had to try different usb ports on my laptop for whatever reason.

Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.

walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
And sadly this was my phone. I switched for a while and was coming back and wanted an upgrade to the software. I hadn't updated from 4.4.2 as it had sat in a drawer, then did AutoRec (which I thought I had done before) and boom phone is completely unusable.
---------- Post added 27th December 2015 at 12:07 AM ---------- Previous post was 26th December 2015 at 11:55 PM ----------
dark_prince said:
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
Click to expand...
Click to collapse
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.

walkingagh said:
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
Click to expand...
Click to collapse
Expand under "Ports Com Ports & LPT"
And you will see LGE Com Port Device.
Just flash the kdz away if u see so. otherwise go through the tot method if u see the com port devices to change the com port address to com41 and then flash tot.
I tried this on Windows 10, Windows 8.1, Windows 8 and Windows 7 (all 64-bit versions) and it worked on all of those. Even with USB 3.0 supported laptop.

Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files

wzedlare said:
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
Click to expand...
Click to collapse
Any good tutorials on fastboot? And those files come from a bootstack correct?

stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Same problem with me tried Kdz Method. But no luck any idea? It's been 3 months em using it like this. Any help?
Sent from my LG-D800 using Tapatalk

So pretty stuck at this point as well. KDZ method stalls at 60%.
UPDATE FASTBOOT WORKING! Took forever to figure out the drivers, but it's working. I have no clue what to do now.
Fastboot won't recognize the device though I have the fastboot driver installed and running. Any ideas?
TOT is just kinda giving up on me. Still chasing down any leads, but the phone feels pretty borked at this point.

Update: Now in download mode! Man this has been crazy. TOT working! Okay so here is how I did it.
First, I downloaded google's ADB drivers and installed the LG drivers as well. I am not sure which one did it. Then I plugged my phone in and went to device manager. For me, it had an unrecognized device and fastboot wasn't working. So I had to manually assign the driver.
Right click on the device and update driver > Let me choose > all devices > Google > LGE mobile ADB interface.
Now fastboot should be working.
Then I used the srktool_2.1. Option 4 then option 4 again, select model number. It reboots to black screen. From there I was able to completely power off (10 second hold on power button). And when it booted back up all the drivers installed. I was able to TOT back to stock using this guide. http://forum.xda-developers.com/showthread.php?t=2432476. KDZ might work as well.
Unfortunately the screen damage looks to be permanent. But I think this is worth more now than it was 30 minutes ago!

hard bricked a6000..

Okay , i dont know what really happened but.. I was running CM12 with custom kernel.. it were fine *for2days* , then there were some annoying bugs with the video and audio playbacks and also wifi.. Before i flashed cm12 i did twrp backup, so i restored it and when i rebooted to system.. the phone didnt seem to turn on. just a black screen and vibrating every 2 seconds. PC doesnt recognize it , i cant get to the boot logo , just vibrating.. I cant go in recovery neither download nor fastboot or anything else.. just vibrating every 2 seconds or less.

edit.. it stopped vibrating when i pulled out the battery for 10mins. now its doing nothing, just black screen. ill charge it for several hours and try again

smirnofz951 said:
edit.. it stopped vibrating when i pulled out the battery for 10mins. now its doing nothing, just black screen. ill charge it for several hours and try again
Click to expand...
Click to collapse
I think its not possible to revive your Lenovo A6000.
I too had a similar experience. The Motherboard of the phone may have have fried .
So I suggest you to visit the Lenovo Service Center & say that the phone doesn't turn ON after you updated to the new update version.
Say nothing about rooting or your custom ROM.
I hope you are still under warranty & they will probably repair it for Free. Also Enquire abt the charges if any.

Qualcomm Hs USB Qdloader 9008 (or 9006) mode
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you

kartixda said:
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
I tried everything. But when i connect my phone to PC its just vibrating , its not recognized by pc.. Vibrating in different intervals, sometimes stops for a 5 - 10 seconds. I dont know what really happened to that phone. I just restored my twrp backup, rebooted and thats it... It cant be hardware issue.

averagegeek said:
I think its not possible to revive your Lenovo A6000.
I too had a similar experience. The Motherboard of the phone may have have fried .
So I suggest you to visit the Lenovo Service Center & say that the phone doesn't turn ON after you updated to the new update version.
Say nothing about rooting or your custom ROM.
I hope you are still under warranty & they will probably repair it for Free. Also Enquire abt the charges if any.
Click to expand...
Click to collapse
Yea i'm under warranty , ill go tomorrow and see what they will do.

Are u able to go into fastboot mode by pressing power + volume down .If yes then it is very easy to recover!

smirnofz951 said:
Yea i'm under warranty , ill go tomorrow and see what they will do.
Click to expand...
Click to collapse
Let me know what they said
Sent from my Lenovo A6000/Plus using Tapatalk

Sourav_8434 said:
Are u able to go into fastboot mode by pressing power + volume down .If yes then it is very easy to recover!
Click to expand...
Click to collapse
Its not going into fastboot mode. Just vibrating in intervals.

averagegeek said:
Let me know what they said
Sent from my Lenovo A6000/Plus using Tapatalk
Click to expand...
Click to collapse
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?

smirnofz951 said:
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?
Click to expand...
Click to collapse
I think they dont

Sourav_8434 said:
I think they dont
Click to expand...
Click to collapse
Thanks for supporting, ill let you guys know if something happen.

smirnofz951 said:
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?
Click to expand...
Click to collapse
I hope they don't. Probably they will replace the Motherboard .
I also had the same issue as yours. I told the same as you did & they haven't charged for me.
I expect that even if they found out ,they will probably ignore it

its recognizd what i should donow

Okay , the phone came back. For first 3 days it was in Sofia,Bulgaria and they didn't found out why its not booting. Then, they texted me that the phone is shipped to India ( i dont really know why ). 10 days later the phone arrived here with changed motherboard. They did not charged me and my warranty is still alive. I'm fully sure that its software issue , really don't know whats the point of changing mobo. Anyway , thanks for supporting.
Lol lol lol just booted in recovery and its still twrp .. how its possible when they said its changed mobo

Help ME!! Bricked my Lenovo A6000 plus
kartixda said:
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
I too have the same problem.The device is completely gone black but responds to power button.My PC detects Qualcomm Usb drivers 9008 .I tried flashing the stock rom but it is taking sooo long and does not finish flashing.{I even kept it overnight to flash}.Please help me recover my phone.

PLease Help
Hello,
I tried flashing the stock rom of a6000+ using twrp but after that my phone got bricked.
i am not able to boot in recovery mode. My device is not getting recognized in adb.
in the device manager section it show TP-Link Android Device->Android Bootloader Interface.
Please Help Me Unbrick My Phone.
the phone just restarts itself even if it is connected to computer.
email:[email protected]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kartixda said:
Qualcomm Hs USB Qdloader 9008 (or 9006) mode
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
hello, I have a bricked A6000, maybe you can help...
now it is shown as qualcomm Hs USB qdloader 9008 in device manager. what should i do next?

Lg g3 auto-rec "hard brick" fix

Hello everyone, first let me give major props to my man @bender_007 for creating the amazing LG G Series Autorec Apps which make installing TWRP on LG G Devices a simple process and for also helping me and others who ignorantly misused his app, thanks B!
Anyway recently I bought a LG G3 on Verizon that was on 35b 5.1.1 Lollipop and I rooted. Boy was I eager to get some TWRP poppin on this beast, however flashing TWRP thru Flashify and TWRP Manager left me unsuccessful giving me Secure Booting Error. So desperate I seen Autorec on the Play Store, installed immediately. From there I went through the app's proccesses and from there attempted to boot into recovery hoping for some success.... I did not realize this was went for 24b 5.0.1 until it was late, I mean hey he says it in the description. The phone was dead it wouldn't show anything on the display when I held the power button and it only vibrated, I was f***ed.... At least that is what I thought. I used the method below that me and @bender_007 were collaborating upon as he tried to help me. So please give him credit. I cannot guarantee this will work for you but it worked for me and you don't have to worry about opening up your phone and shorting pins, that nonsense if this works for you.
MATERIALS
A FUNCTIONAL COMPUTER (PREFERABLY WINDOWS, I USED WINDOWS 7)
LG FLASH TOOL 2014: http://www.mediafire.com/?fwrcd3pdj0svjtb
LG DRIVERS-
UNIVERSAL: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
VERIZON:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
THE LATEST KDZ FOR YOUR PHONE MODEL (GOOGLE IT)
Your Dead but Still Amazing LG G3 and a USB Cable
Note: IF DONE PROPERLY YOU WILL STILL HAVE ALL YOUR EXSISTING DATA PRE-BRICK
PROCEDURE
1. Gather all materials, and know the locations of all your downloaded files.
2. Install the drivers for your phone.
3. Unzip LGFlashTool_2014.zip
4. Move the .KDZ you should've downloaded to the LGFLASHTOOL_2014 folder.
5. Open Device Manager (press start, type in Device Manager into search bar, hit enter)
6. Click View, "Show Hidden Devices"
7. PLUG in USB CABLE TO COMPUTER ONLY!
8. THIS STEP IS VERY VERY VERY IMPORTANT! TAKE THE BATTERY OUT OF YOUR LG G3. PUT IT BACK IN. CLOSE THE BACK. HOLD VOLUME UP ONLY, WHILE HOLDING POWER UP DO NOT LET GO PLUG IN OTHER HALF OF USB CABLE INTO PHONE. KEEP HOLDING VOLUME UP FOR 20 SECONDS. YOURE PHONES SCREEN WILL STILL BE BLACK AND IT SHOULDVE VIBRATED ABOUT 2 SECONDS AFTER YOU PLUGGED IN WIRE (You'll know when you do it right when COMPUTER says installing drivers in bottom right corner.)
9. In Device Manager under Modems there should be something like LGandroidNET I DONT REMEMBER EXACTLY THIS IS ALL OFF THE TOP OF MY HEAD. Anyway, if it says that then you are good, believe it or not your in download mode. (IF YOU DO NOT SEE THIS REPEAT STEP 8)
10. Go to LGFlashTool_2014 folder and run the LGFlashTool2014.exe application.
11. Change PhoneMode to Emergency
12. For "SELECT KDZ FILE" open the folder of the the FlashTool, it should be on it by default and pick the KDZ file.
13. Click "Normal Flash"
14. On the next SCREEN click "START" at the bottom
15. Now there should be a pop-up that says "Select Country & Language" Do not mess with this, just click "OK"
16. There should be a SCREEN now that has a % or whatever... From HERE TO THE END OF IT DO NOT UNPLUG YOUR PHONE!!!
17. When you hit like 85% your phone will boot up do not UNPLUG still and once it hits 100% your done! Safe to UNPLUG and YOU FIXED YOUR PHONE!!!!!!
If you have any questions please ask I have pure empathy for anyone who goes through this hell.

The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?

wombatthing said:
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
Click to expand...
Click to collapse
Okay I'm here to provide my best assistance and for that you'll have to answer a few questions?
1. What is your device model? ex. VS985 Verizon
2. What KDZ did you attempt to flash? ex. VS98547a_01.kdz
Looking forward to your reply.
Sent from my VS985 4G using Tapatalk

@wombatthing I would go to device manager go to view "Show Hidden devices" then disconnect your phone take out battery put it back in close back then hold volume up for 20 SECONDS while doing that connect to computer. It probably won't say installing drivers because you said it worked the First time, from there see if it's under Modems. Good luck my friend in here for any questions
Sent from my VS985 4G using Tapatalk

Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks

Ray1000 said:
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Click to expand...
Click to collapse
My friend all is good. First of all as long as it says LGandroidnet you are good you should be in download mode, in lg flash took for mode click emergency and not diag then click normal flash THIS WILL KEEP YOURE DATA IF YOU SEE CRS FLASH OR SOMETHING LIKE THAT THEN ITLL RESET YOURE PHONE just do Emergency and Normal Flash and it should work. Hope I help if you have questions please ask.

@Ray1000 "Emergency" Mode is just Download Mode flashing. Diag is not that's why you were unsuccessful.

Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00

For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64

mackleroar said:
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
Click to expand...
Click to collapse
Sorry for the late response. First of all you are welcome. I don't know if you fixed the problem yet but I'll help anyway. First remove youre battery for at least 10 seconds then put battery in, hold up and connect charger for 20 seconds. Of you are unsuccessful try reinstalling drivers. Best of luck my friend.
Sent from my VS985 4G using Tapatalk

Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!

Perezvon said:
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Im having the same problem!!!!!! I've tried everything. I will let you know if I fix it and please let me know if you get your's running?

Does anyone know if this method will work for the Sprint LS990 variant? I too had my phone broke by autorec and I lost download bit have access to TWRP and can flash roms but can't do a factory reset with the LG Flash Tool.
Sent from my LG-ls990 using Tapatalk

Failed to flash
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!

i also cannot find the Qualcomm's driver on windows 10 & phone looses communication with flash tool..

vajee555 said:
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
Click to expand...
Click to collapse
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me

ayarihime said:
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
Click to expand...
Click to collapse
Hello. I managed to get my device to work. Flashed a stock MM rom and now stucked with damn Mcfee kill switch. Can not go to download mode either . Any idea how to fix this? Thanks!

Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC

mjmaxint said:
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
Click to expand...
Click to collapse
Hello, I had to short some other two pins to get it identified by my PC. The pins mentioned it this post did not work for me. Follow the link given below and it will work for you. Thank me later.
http://forum.gsmhosting.com/vbb/f494/how-hard-unbricked-lg-g3-all-variants-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/

He guys thank you very much. My LG3 was already down for months after many failed attempts and I was about to bin it. Decided to give it one last try, found your instructions and it works, I now have Marshmallow!! (However I downloaded the KDZ file from "downloadmirror.de" and I am not sure if that was a good idea.

[HELP][Samsung A3] - Broken Screen - Recover Files

Hi,
I've a Samsung A3 with a broken screen and I need to recover some files from it.
The device isn't rooted, have a default recover and ROM.
I'm trying to access via adb, but always shows unauthorized with the command adb devices -l.
Other idea is connect the device trough some cable, is possible with MLH?
Is the A3 compatible with MLH?

The files are accessible, dont worry. You will need TWRP on the device, and ADB configured on the PC/MAC. After that, you can "PULL" the files out of there.
OR JUST USE KIES.
PS, not sure about MHL cables, none worked for me.

PlutoDelic said:
The files are accessible, dont worry. You will need TWRP on the device, and ADB configured on the PC/MAC. After that, you can "PULL" the files out of there.
OR JUST USE KIES.
PS, not sure about MHL cables, none worked for me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-twrp-2-8-7-0-galaxy-a3-sm-t3153682
To install TWRP I had read that the phone must be rooted.
My great dificulty is how I can root and install twrp on the phone without a screen to see each process stage...
Regarding KIES I never connected the phone to the PC, so I need to autorize KIES to acess phone... and with a broken screen I can't do it.
tks

You dont need root for TWRP.

PlutoDelic said:
You dont need root for TWRP.
Click to expand...
Click to collapse
I saw that is mentioned here http://forum.xda-developers.com/andr...a3-sm-t3153682 .
The following procedure dont require root but it's needed a working screen ("Settings > Developer Options > USB Debugging").
http://www.xda-developers.com/how-to-install-twrp/

Use KIES then.

Ok, I'll put this to bed right now for anyone else that happens to read that misinformation posted all over the net.
You DO NOT and never have had required to have root or enable USB debugging to install custom recovery.
Recovery is a mini OS that has absolutely no connection to the main system OS. USB debugging and root are only required for the main OS.
You dont even need an OS installed to use recovery.
Install TWRP with ODIN and then use the tool below. You can do all this without a screen. Odin will tell you what's happening.
http://forum.xda-developers.com/showthread.php?t=2786395
IMPORTANT: You must disable auto reboot in Odin then when Odin says PASS after flashing you must IMMEDIATELY boot to recovery by holding POWER + HOME + VOL DOWN
as soon as you see REMOVED in Odins windows quickly change to POWER + HOME + VOL UP.
This may take you a few tries as the timing is critical.
Note: If your device still boots to the OS and you dont have a security locked screen then you should still be able to use MTP to transfer files. Just plug your usb cable in.
If worse comes to worse and you cannot do the above I will modify the boot.img to give you adb support without needing usb debugging enabled.

???
luciofsl said:
Hi,
I've a Samsung A3 with a broken screen and I need to recover some files from it.
The device isn't rooted, have a default recover and ROM.
I'm trying to access via adb, but always shows unauthorized with the command adb devices -l.
Other idea is connect the device trough some cable, is possible with MLH?
Is the A3 compatible with MLH?
Click to expand...
Click to collapse
Hello guys. I have the same problem as the OP, I have no to little experience in android and anything around it, but I am pretty messed up and i could use some help here :<
I have Galaxy A3 (2016), with broken screen (totally black), stock rom, without usb debugging enabled and a lock pattern in use...
I tried everything I could comprehend from the replys here and many posts around, but I got nothing... I am not even sure that I could get into recovery mode to install TWRP with odin, as it failed (whenever it could pass the the "SetupConnection")...
Is there anything I can do, maybe someone can help me on something i am missing here? :F

Doggy17 said:
Hello guys. I have the same problem as the OP, I have no to little experience in android and anything around it, but I am pretty messed up and i could use some help here :<
I have Galaxy A3 (2016), with broken screen (totally black), stock rom, without usb debugging enabled and a lock pattern in use...
I tried everything I could comprehend from the replys here and many posts around, but I got nothing... I am not even sure that I could get into recovery mode to install TWRP with odin, as it failed (whenever it could pass the the "SetupConnection")...
Is there anything I can do, maybe someone can help me on something i am missing here? :F
Click to expand...
Click to collapse
Ensure you have the Samsung USB drivers installed.
You need to put your device in download mode.
Boot holding power + home + vol down.
Hold for around 5 seconds then after another 5 seconds press volume up.
Run odin then plug the usb cable in. You will see the 'added' message if you are in download mode.

ashyx said:
Ensure you have the Samsung USB drivers installed.
You need to put your device in download mode.
Boot holding power + home + vol down.
Hold for around 5 seconds then after another 5 seconds press volume up.
Run odin then plug the usb cable in. You will see the 'added' message if you are in download mode.
Click to expand...
Click to collapse
Hmm.. I used Odin 3.12 and twrp_3.0.2-1_sm-a310.tar . What seems to be the problem here? Am I using wrong version of something?? :<
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Doggy17 said:
Hmm.. I used Odin 3.12 and twrp_3.0.2-1_sm-a310.tar . What seems to be the problem here? Am I using wrong version of something?? :<
Click to expand...
Click to collapse
You don't have oem unlock enabled.

ashyx said:
You don't have oem unlock enabled.
Click to expand...
Click to collapse
Is there something I can do though?? Please don't say no!

Doggy17 said:
Is there something I can do though?? Please don't say no!
Click to expand...
Click to collapse
Which firmware was your device running?

ashyx said:
Which firmware was your device running?
Click to expand...
Click to collapse
I am not quite sure. It's got Greek baseband so I believe that this must be it "SM-A310F_20160827_A310FXXU2BPH8_A310FOXX2BPI8_6.0.1".

ashyx said:
Which firmware was your device running?
Click to expand...
Click to collapse
Doggy17 said:
I am not quite sure. It's got Greek baseband so I believe that this must be it "SM-A310F_20160827_A310FXXU2BPH8_A310FOXX2BPI8_6.0.1".
Click to expand...
Click to collapse
Is there a way to determine the firmware by the phone as it is now somehow?

Guys, is there anything that I could possibly do, or should I just forget about it?

luciofsl said:
Other idea is connect the device trough some cable, is possible with MLH?
Is the A3 compatible with MLH?
Click to expand...
Click to collapse
Samsung A3 support OTG, but not compatible with MHL.
So does the screen switch on? Or is it completely black?
If can you see the screen display, buy an OTG cable to plug a mouse into your Samsung, and click on your phone to make a backup.

Evening. I have a relatives Galaxy A5 with a completely blank screen and no touch. USB debugging is OFF. Im not sure what version of Android is on the phone. I have installed Custom recovery as far as I can tell. I cannot get the phone into Recovery mode. I have been trying to get the phone to turn off by having it plugged into the charger and holding Volume- & Power (As the battery is non removable) then Power & Volume+ & Home but its a no go. I tried Kies but its saying the phone is locked and it needs a password but I cant type it in with a blank screen and no touch. Does the A5 2015 have OTG support? Theres some important info on the phone so he really needs it. Help Please

wagoera said:
Maybe you can try Broken Android Data Extraction tool to help you recover files from Samsung A3 with broken screen. It can help you access files and extract them out from a broken screen or dead Samsung mobile phone.
Click to expand...
Click to collapse
It's always best to at least read the previous post before you post.