hello everyone,
After months and months of using different ROMs, I tried yesterday the RR rom, followed as always different steps & wipe, did install the ROM & Gapps, there was an error message, don't recall which one, but after it rebooted directly and arrive to:
Fastboot mode started
udc_start()
Now i'm unable to go back to recovery mode nor entering the Download mode with vol-/+ and USB or do anything else. Have i bricked it?
can anyone give me advice please?
What I'd try first - make sure your battery is charged (100 per cent preferable). If you can get it to communicate whrough ADB using some key combos, you basically won. You can just flash a stock ROM from there.
If your PC recognizes it as a G-Pad, yay for you. Use the LG Flash Tool to recover and flash a stock ROM (I assume you have the software, in case not just google it). If it's only connected to the PC discovered as a QHSUSB_DLOAD - refer to this thread and follow step by step - it might help you:
https://forum.xda-developers.com/lg-g-pad-83/help/how-recovered-lg-g-pad-detected-t3207079.
Really tho. Most problems can be helped by prperly and fully charging the tablet and trying the LG tools.
Cheers.
Related
I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..
dylanraga said:
I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..
Click to expand...
Click to collapse
Hate to say two things to you bro:
1) You didn't search very hard, because there was a related thread on page 3 with "QHSUSB_DLOAD" in the title
http://forum.xda-developers.com/showthread.php?t=2781522
I forgive though, but just letting you know.
2) You're screwed. The phone is hard bricked. No way to get it back to life.
How do I know? Well, look who's the creator of the thread just linked to.
Read the entire thread. It's not very long.
PS: PM me if your phone is still under warranty and you want advice on how to get it replaced. If you still aren't under warranty, then you're doubly screwed.
Hi
Really appreciate any ideas on how to fix my LG G3.
Purchased phone on eBay - not sure where it's from but have asked buyer (if anyone knows how, I suspect this is part of my problem). Decided to flash new ROM but, when I installed AndroidNowHD1.4, I started to see lots of com.phone.android that made the phone essentially unusable. I then tried another ROM - SphinxG3NeoV2 - to see if that made a difference. Now when the phone boots, it goes to a Fastboot prompt.
I can get into Recovery OK, and Download mode. When I try the LGFlashTool to install TOT/DLL firmware, it's failing and seems to have an issue getting the IMEI and PID from the phone. Ive also tried installing a KDZ file using a FlashTool and that also is failing.
Many thanks in advance for suggestions!
Cheers,
Gavin
gavjs said:
Hi
Really appreciate any ideas on how to fix my LG G3.
Purchased phone on eBay - not sure where it's from but have asked buyer (if anyone knows how, I suspect this is part of my problem). Decided to flash new ROM but, when I installed AndroidNowHD1.4, I started to see lots of com.phone.android that made the phone essentially unusable. I then tried another ROM - SphinxG3NeoV2 - to see if that made a difference. Now when the phone boots, it goes to a Fastboot prompt.
I can get into Recovery OK, and Download mode. When I try the LGFlashTool to install TOT/DLL firmware, it's failing and seems to have an issue getting the IMEI and PID from the phone. Ive also tried installing a KDZ file using a FlashTool and that also is failing.
Many thanks in advance for suggestions!
Cheers,
Gavin
Click to expand...
Click to collapse
What is it that makes you say it has issues with the IMEI when flashing out of interest?
What the error with flash tool?
We can help you unless you get specific with the error messages dude.
Unbrick
gavjs said:
Hi
Really appreciate any ideas on how to fix my LG G3.
Purchased phone on eBay - not sure where it's from but have asked buyer (if anyone knows how, I suspect this is part of my problem). Decided to flash new ROM but, when I installed AndroidNowHD1.4, I started to see lots of com.phone.android that made the phone essentially unusable. I then tried another ROM - SphinxG3NeoV2 - to see if that made a difference. Now when the phone boots, it goes to a Fastboot prompt.
I can get into Recovery OK, and Download mode. When I try the LGFlashTool to install TOT/DLL firmware, it's failing and seems to have an issue getting the IMEI and PID from the phone. Ive also tried installing a KDZ file using a FlashTool and that also is failing.
Many thanks in advance for suggestions!
Cheers,
Gavin
Click to expand...
Click to collapse
Hi there,
I had the softbrick when I tried flashing the TWRP recovery image and screwed up. The phone didn't start up anymore and didn't go into recovery either. Just a black screen saying [680]fastboot. (on a D855).
Solution:
* Go to youtube,
* Type Unbrick LG G3,
* Open the video from ZEDOMAX,
* Follow the tutorial, all the links are in the description below.
With me, the first time I tried flashing the stock ROM it stoppedd at 15%, the seccond time at 94%, the third time it went all the way. Make sure wait long enough before you disconnect the USB cable. (The screen must be on 3!)
This should solve you problem.
Appologies for the weirdd description to get to the video. I'm new here so I can't popst direct links yet
WJ
Note 3 / SlimROM
LG G3 / StockROM
Hi
Many thanks for responding.
WJ - I was following a similar video but when I watched your suggestion, he made a bit of a deal about digging out an old windows laptop. I was using windows in VMWARE on my mac. I tried it using Boot Camp and it seems to have worked.
Cheers,
Gavin
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Search for the Hard Bricked thread by Naman Bhalla and use it. The links in it may point to older versions, so find out if any later versions are available.
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If pc detects phone try /adb devices ,if it detects phone, go like this: /adb reboot bootloader then it should reboot into fastboot. If so try fastboot flash recovery "yourrecovery.img" (I suggest stock recovery of oos you had before brick). The next step, if you boot into recovery is to adb sideload stock oos. Command for that is /adb sideload "youroosfile.zip"
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
ach3fck said:
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
Click to expand...
Click to collapse
That's right I even recover a CB8 dead OP3
toolkit
try oneplus 3 toolkit
Try the Unbrick tool, everything that is bricked can be solved...
So I've had a read through other threads on different sites and youtube videos etc.
Basically I was trying to root my phone using magisk following the video where TK roots a oneplus 5, but was switching out the software for the oneplus 3 version of twrp.
All was going well, connected phone to pc, unlocked it, copied the files across, flashed and installed twrp then when it rebooted after installing twrp it came up with an error saying that "dm-verirty" is not started in enforcing mode, and the phone wouldn't boot past that.
I relocked the OEM, as I couldn't get it to recovery mode (stock) so tried that and now I can get it into recovery mode.
It will happily go into fastboot mode, have tried reflashing stock recovery and trying to update the os via adb.
Have been looking at the Mega Unbrick Guide - but can't get my phone to show up on my pc to even begin there.
Would appreciate any and all help, plus tips for what to do after I get it back to stock as I'm still keen to root my phone but don't want to screw it up again and have to go through all of this again.
The Mega Unbrick guide is your best hope. Did you install all the drivers on your PC? Specially the Qualcomm ones? Also, make sure to press the volume up button like it says in the instructions for 40 seconds. Otherwise it doesn't show up. If all fails, try using a different PC.