Database Users

[Solved] Stuck in Boot Loader

* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
{
"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"
}
Image of recovery that I can not get to.
Current state of device. can not get anywhere else.
Close up of date.
Picture of odin failing. I tried to flash using the option called PDA by the way.
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
solved - cant find where to set this thread to solved thought.
Any help is greatly appreciated.

Nyreb said:
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
View attachment 2637629
Image of recovery that I can not get to.
View attachment 2637596
Current state of device. can not get anywhere else.
View attachment 2637598
Close up of date.
View attachment 2637611
Picture of odin failing. I tried to flash using the option called PDA by the way.
View attachment 2637622
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Shoot me a email at [email protected]... We can talk more about your issues there..... Thx lj

Solution
Thanks to lj50036, my nexus now actually works.
Here's what he told me to do:
----------
1.) start here http://forum.xda-developers.com/showthread.php?t=2588979
This will install abd fastboot and the drivers for your tablet just follow instructions.
2.) Now open cmd as admin and type
fastboot
should see commands and options listed
3.) now type
cd /
this will move root to c drive.
4.) plug in tablet, boot into bootloader (holding down power, volume up and down I think) and type
fastboot devices
this output serial number of device and then type of device (Fastboot)
5.) go to https://developers.google.com/android/nexus/images#mantaray or google factory images and find Nexus 10. use what ever version you want. download, unzip and you should see something along the lines of this (the kot49h will be what ever version of the image you used.)
6,) move everything but the 2 .sh files to root of c drive (c:/)
and then in cmd prompt type
dir
this will print out file names, data, and other information of c:/. make sure you see the 3 files you moved from the factory image you unzipped.
7.) if so, make sure tablet is in bootloader still, and type
flash-all.bat in cmd prompt.
--About halfway through it reboots your nexus and because my nexus wont reboot its self, and will only come on when its plugged into wall outlet for a bit, I just did that and plugged in and it worked fine.
-- once the whole process runs, my nexus rebooted into recovery mode, and after a minute rebooted correctly and I was able to start setting up.
----------------
Thank you again to lj50036

@Nyreb
Change the forum name to include (SOLVED)

@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.

spudsmac said:
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
Click to expand...
Click to collapse
Shoot me a email.... Sounds like you need some help....

So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!

spudsmac said:
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
Click to expand...
Click to collapse
What happen in android some time, and I may be way off in left field here but, it has happened this way on the tf700, tf300, tf201, and the nexus 10... Just what I have help people with is that....
The storage no matter what command you issue in fastboot e.g
Code:
fastboot erase boot
fastboot erase system
fastboot -w
It just will not erase everything, and by doing these commands your really only telling the tab and or phone that you are going to be putting other
data in those partitions, so if you just flash exactly what was already on the tablet it does not like it...
@spudsmac had upgraded to 4.4.2 and was trying to install cm11 when things went wrong
So by us trying to reset the tablet to factory 4.4.2 firmware it would not take it... Just froze at android guy with x
So when, we went one version older on the firmware... Magic happened and he was golden....
Thx Josh

Need Help! Tablet Stuck and Fastboot Not Working

I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"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 was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.

If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.

share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?

NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.

share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.

Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.

I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.

I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.

answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks

aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.

[FIX][Noob Friendly] No recovery, No download mode, No booting android, qhsusb_bulk?

No recovery, No download mode, No booting android, No fastboot? - In this case you are right here!
You are in the following situation:
If you power on your device, it goes to the LG logo and becomes black with running backlight quickly.
You have no access to the recovery mode.
You can't enter download mode.
There is no way to boot into the android system.
Usually your device is shown as qhsusb_bulk in Windows device manager.
Sometimes Windows recognizes about 13 partitions.
What you will need:
A working linux distribution (no way around that, but don't be afraid, e.g. slax)
If you want to run Linux in a Virtual Machine (no installation), preferably the VMWare Player (only for 64bit OSes) or an older Version of VMWare Player that supports 32bit.
A windows machine
A kdz for your device: 1, 2 or 3
The kdz extractor for WINDOWS!
Your broken G2
A micro USB cable
A little introduction:
We saw it a few times in the past months that people did weird things with their phone and didn't have anything more than a bootloader. This means no access to recovery nor download mode nor a booting android system. The last case was @petrasl27 (Thanks for the screenshots btw. ;D ). @bender_007 and @Art Vanderlay did an awesome job and helped petrasl27 to recover his phone within one hour. So thanks to those two! For those who want to read the original discussion, read a few pages here!
This thread here is similar to this one here, but I would say quite a bit easier to understand.
Disclaimer: I am not responsible for your phone. I did everything with my best knowledge, but I can't guarantee that your phone is working afterwards and every single command is written correctly. But I hope so, and it should ofc. If you have any issues, feel free to ask for help. We are kind, no worries. If you find mistakes, hit me up and I will correct them ASAP.
Let's start!
1) Install Linux
The easiest way is just do download the VMWare Player, installing, running it and using the .iso you downloaded before (pick other 3.x Linux Kernel if you downloaded slax). If you are unsure how to get Linux running, google it or ask here. Make sure, the usb port which you are going to use is linked through to the virtual machine.
You can also make the iso bootable and run the Linux as live system.
2) Extract the kdz
Switch to Windows, open the kdz extractor. Tick everything in the upper window, and click on extract kdz. Then open the .dz which just was created in the working directory of the kdz extractor. Tick "aboot_xxxxxx.bin", "boot_xxxxxx.bin" and "laf_xxxxxx.bin" in the lower window and hit extract dz. Then move the .bin files to your Linux desktop by using an USB stick, online storage or something like this.
Rename the files to "aboot.img", "boot.img" and "laf.img".
3) Preparing everything
Remove all your USB devices (except your G2 and your Keyboard & Mouse) from your computer, open a Terminal and type
Code:
ls /dev/sd*
The sda, sda1, sda2 etc. should be the partitions on your computer. But there should be a few others with sdb, sdb1, sdb2, etc. but no more. The sdb ones should be numbered from 1 to 36. This is your G2. Keep in mind how the three letters are (sdb, sdx, what so ever). (Make sure you run this as Super User, if you don't use slax!)
Then type
Code:
gdisk -l /dev/<insert the three letters you found out with the command above>
example:
Code:
gdisk -l /dev/sdb
It should now look something 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"
}
Keep the numbers of the marked partitions in mind. In this case aboot=5, boot=7, laf=23.
4) Preparing everything
If you've managed it to get here, you are almost done. It's almost time for the final step now:
Open a terminal and type
Code:
cd Desktop
ls
You should now see the filenames of the 3 files (aboot.img, boot.img, laf.img) on your desktop in the terminal. If you do not, you either didn't type "cd Desktop" properly (The linux terminal is case sensitive!!!) or you haven't copied the files to the desktop.
5) Flashing the stuff
Code:
dd if=aboot.img of=/dev/<the 3 letters of your G2><the number of your aboot partition>
dd if=boot.img of=/dev/<the 3 letters of your G2><the number of your boot partition>
dd if=laf.img of=/dev/<the 3 letters of your G2><the number of your laf partition>
example (in my case):
Code:
dd if=aboot.img of=/dev/sdb5
dd if=boot.img of=/dev/sdb7
dd if=laf.img of=/dev/sdb23
6) Go back to stock using the kdz method
Now just follow this thread to get back to stock.

Reserved - just in case^^

bricked my lg g2 d802..plz help
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...

hbk4 said:
i'm from india .
i had installed lollipop 5.0.2 v30b via kdz flash method on my lg g2 d802 (indian version ) .
since then i had issues wirth my bluetooth and wifi.both were not working .
in my attempts to flash back to stock 4.2.2 , i came across ur thread and i flashed "D802_PATCH_RETURN_KK_droidth" via philz latest cwm recovery ,
but after that everything went mayhem ..
i got boot error message repeatedly and was unable to enter even recovery .
after several tries i somehow managed to enter recovery mode , but stil phone wont go past it.
I GUESS I ACCIDENTALLY FLASHED A KERNEL FOR MY OLD GALAXY NOTE(due to confusion between the saved files in the download folder ) , On my g2 too....but not sure...
after i restatred the moB , it wont turn on .
battery was 85 % ..
i'm not a newbie to flashing roms and have done aTLEAST >50 times with my lg g2 and galaxy note 2 and previously sgs2 , but this is the first time i got into a hard brick mode.
when i took the phone to servie center, they told the mob is just out of warranty and so wont get any warrany related help.
they told that the EFS HAS BEEN CONVERTED TO READ ONLY mode somehow due to improper flahing and also added that the EFS IS BEING SHOWN AS 16 PARTITION S.
they tried to repair the boot sector and recovery using OCTOPLUS TOOL BOX , but failed and told me that the latest models like G2 is not supported as if now in their TOOL BOX.
THE ONE suggestion given by them was change of PCB which is almost same as a new mob.
I'M STUCK WITHOUT MY FAV MOB G2 .......PLS HELP ME OUT SOMEHOW AND HELP ME OUT...
Click to expand...
Click to collapse
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.

I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..

Soufiansky said:
I want to download the first linux programme but it is just for windows 64bits. I'm running windows 7 OS 32Bits..
Click to expand...
Click to collapse
Which one are you refering to?
NVM, adjusted the OP. Either use VirtualBox or download an older version of VMPlayer (which supports 32bit obviously) by picking Version 6.0 as major version.

Sunandroid said:
Which one are you refering to?
Click to expand...
Click to collapse
VMWAREplayer

Soufiansky said:
VMWAREplayer
Click to expand...
Click to collapse
read my post above (edited it).

Sunandroid said:
read my post above (edited it).
Click to expand...
Click to collapse
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.

Soufiansky said:
I can see that it will install Linux OS on my computer , which mean i will have 2OS . Is this safe ? I mean on every boot i should choose the OS to use or what ? Because i never used Linux as i don't need it , but this time it's a must.
Thanks.
Click to expand...
Click to collapse
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.

Sunandroid said:
No, if you are running it as a virtual machine (in VMWare Player or VirtualBox or whatever), it's like a programm you can start on your windows system. After you've unbricked your device, you can easily uninstall the VMWare Player and there is nothing from Linux anymore.
Click to expand...
Click to collapse
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.

Soufiansky said:
I get it , like a virtual OS in the main OS. Installing , will report back.
---------- Post added at 09:40 PM ---------- Previous post was at 09:18 PM ----------
@sunandroid My phone is booting at LG logo and download mode is working , so i see this method isn't for me BUT .kdz method doesn't work , firmware stuck at 24% or 49% , and one LP firmware worked but it just keep rebooting after the process.
Factory reset doesn't work , the blue line down isn't there and it reboot again and again.. Is there a way to boot in fastboot using buttons combinations ? Tried multiple things but didn't work.
Click to expand...
Click to collapse
What button combo do you use to factory reset?

Sunandroid said:
What button combo do you use to factory reset?
Click to expand...
Click to collapse
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..

problem soleved.....finally
Sunandroid said:
Did you follow the guide? Just do this. If things are unclear, just ask and someone will help you.
Click to expand...
Click to collapse
finally , i solved the problem..
with the help of soombons (droidth) , i was able to fix my d802 in just 2 minutes. - USING SRK 2.0 TOOL ...
sharing the link for people with same problems
---
[LG-G2] Unbrick (qhsusb_bulk) by SRK Tool 2.0 (D8…: https://youtu.be/ERZvlJIC9dE
tonnes of thanks to SOOMBONS for the prompt help !..
CHEERS !!!

Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Soufiansky said:
Volume down + power button , just after LG logo i press them again , then yes , yes , it shows the green android but there is no factory reset ( the blue line isn't there if you know what i'm talking about)
Tried also the same thing then power 3 times , same also..
Click to expand...
Click to collapse
Weird. Did you use this method to go back to stock: http://forum.xda-developers.com/showthread.php?t=2432476
This worked fine for me every time I used it. Try to flash a KK ROM again, but do a CSE flash.
chaitea said:
Can anyone help me out on a D801?
The phone goes into bootloop... the LG logo appears for a few seconds, disappears, then reappears. I'm not able to go into download mode, no fastboot, and also no recovery. When I do the volume down + power button combo I can get to the factory reset screen but selecting Yes both times just sends me back to the same LG logo bootloop.
What is weird is that my phone use to display as QHSUSB_BULK and it would bring up a bunch of drives... but now that doesn't happen and my phone isnt even showing in device manager anymore. Also, my phone used to show the first "Download Mode" splash screen when I held the volume up button while plugging it into my comp but it just does the same bootloop. No more errors... just bootloops...
Do I have to short the capacitors like in this thread: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
or this one: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Yeah I guess you have to do as you mentioned. Only thing you could try before doing so:
Hold down the power button for 20 secs. Then wait a few secs and try to get into download mode. Maybe the device shows up as qhusb_bulk again.

Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks

Batou069 said:
Please help, Im stuck!!!
Since yesterday my phone is stuck, only LG Logo, no download mode, no factory mode, no recovery, no nothing but the lg logo.
I tried thw mentioned tool and what the OP posted here, but in both methods I get stuck:
The LG G2 is not recognized as as drive anymore, the one thats supposed to have many partitions, sdb, sdx, what so ever, numbered from 1 to 36.
Without this I cant continue.
Any help? Using D802 international version
Thanks
Click to expand...
Click to collapse
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.

Sunandroid said:
Do you have a windows machine?
If yes, try this http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2 and see if it is displayed as qhusb_bulk in device manager after you've done this.
Click to expand...
Click to collapse
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks

Batou069 said:
Hi, thanks for the quick reply
I have a windows machine, yes, but no idea how to open my device. I hope this wont be necessary...
What happened last: After using a very laggy rom for over a week, I decided to flash PA. I wiped everything except the format, so data/media is kept... i guess that the flash didnt went well, and after reboot im stuck at LG logo... manually putting it into recovery isnt working anymore.
When I connect the phone to the pc only the "LGE Android MTP Device" is identified but with a fail (yellow triangle and exclemation mark in device manager).
SRK Tool -> Disk Managment Tool shows only Disk0 which is c:
In the virtual machine, under VM> removable devices I can see the LGE Android, and when I connect it (disconnect from host) nothing changes, no sdx, sdb or anything like this, only sda (C
I installed the LG Drivers but it wont help. Here I am, with a bricked phone
What do you think?
Thanks
Click to expand...
Click to collapse
Are you sure you can't get into download mode? (hold down the power button for 20 seconds (not shorter!), then holding the vol+ button and connect the phone to a computer)?
I could imagine that you can enter the recovery after holding down the powerbutton for 20 seconds with the button combo. I think so, because the kernel must be working somehow since it still manages to get shown properly on windows.
If none of the options above is working, the pin shortage is probably the easiest way to get into qhsusb_bulk and start freshly (following this thread).

Yoga Tab 2 8" 830f failed update led to soft lock

So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of 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"
}
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
1. download and extract this file someplace on your pc
2. uninstall your existing Phone Flash Tool and from the drivers folder install both files (Intel Phone Flash Tool and Android Driver accepting defaults) reboot pc when finished
3. place your tab in DNX mode (from power off press and hold both volume keys then press pwr to start, in a few you screen will show "Fastboot starting..." message and hang on that. you must get that message on your tab screen, restart from power off until you have it)
4. start the installed Phone Flash Tool and load flash.xml from the extracted YT2-830L... folder then Start Flashing, it will reboot when done
Click to expand...
Click to collapse
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?

AgentXGhost said:
So I downloaded a 16mb OTA update and let the tablet do its thing without touching it. I waited for the tablet to boot up, but it was stuck in a black screen for about 12 minutes until I decided to turn it off and on. It didn't work, so I went to the recovery to do a factory reset and clear the cache, but it still didn't work. I later went to this Russian forum here from this thread. I downloaded a lollipop rom and proceeded to flash it using Phone Flash Tool Ver. 5.2. It went well until 16% in where it failed. Unfortunately, I don't have a screenshot of this.
(image of the files in the rom I downloaded)
After all this happened, I tried to start it up but I got the message "Boot Failed. EFI Hard Drive. Boot Successful - Enter Setup"
And now it won't go into recovery mode, but it does go into fastboot and bios setup.
Since it does go into fastboot, I tried to use a tool from this thread (Temp recovery) to use a temporary cwm recovery to hopefully be able to at least boot into that, but that didn't end up working.
I got another rom from the same Russian site that had differently packaged files but still the same stock lollipop rom.
I tried to just use the recovery from there to manually flash it using fastboot, but it still failed.
I later found this thread with these instructions for this problem.
The file he linked in his post (ionioni ) was gone but I still tried to do this with the roms I had. And guess what? It still didn't work. The instructions said to place the tablet in DNX mode (meaning fastboot), which I did do...only when I put it into fastboot, it was set to DNX_OS which came to say "Wrong device state" in Phone Flash Tool.
I've tried what I could, but failed. Anyone have any suggestions?
Click to expand...
Click to collapse
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.

Holy Sh!t. this just absolutely worked!! I didn't think I could bring this thing back to life, but the files you linked just did it! Really, I don't know how to thank you enough for this.

corasman said:
This is the file you need https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view
And this https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
Hi folks,
had the exact same issue and indeed the 1st link offered (https://drive.google.com/file/d/0B1LaMEhefCBgYzNTOUxJZmtWQ0E/view) worked like a charm.
The second link is to download the "Intel platform flash tool lite", but I used my existing version of the Intel Phone Flash Tool (5.2.1-0) which worked fine with the image.
In other words, Corasman, it appears you have saved 2 people's life (or at least tablets) with your solution, so Thanks ! :good:
Regards.

Make that 3 people! Thank you so much corasman - your post has finally fixed my yoga 2 tablet, which I was sure would be going in the bin. Can't overstate how grateful I am - Cheers!

update 830f with 1050f rom?
updating 830f with 1050 rom? does it work?

hello. I have the same problem. I update OTA to lolipop. Since the table is slow, i tried flashing some ROM (which i cannot recall) and the tablet stopped working. Now, I am trying to flash the link you provided and it succeed. However after that i get blank Screen. what Could be wrong. My table is YT2 830LC. Please help

I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.

i have a same problem with yoga 2 pro 1380f mr corasmancan help me

prabuddhadg said:
I am typing this all over again after my full report vanished. Do not have the patience of typing all that again. Suffice to say I had a similar situation with the boot failed EFI Hard Drive. Boot Successful - Enter Setup" message on my 830LC.
I had even found the bios restore tool for moving back from lollipop to kitkat but it too would hang. And attempts to flash lollipop would fail immediately with the same message as the OP, wrong device state.
So, in spite of it seeming completely counter-intuitive, I flashed the 1050F rom in the link shared by Corasman. Strange as it may seem, my tablet is now alive and working. No calling function, but it is working and calling itself a 1050F.
Now my research has to shift to whether the 830 LC rom can be flashed now.
Click to expand...
Click to collapse
i have same problem with my yoga 830lc this rom not work help me to run my tab agian
---------- Post added at 10:55 AM ---------- Previous post was at 10:47 AM ----------
corasman said:
This is the file you need
And this
Ignore the oops error warning, it's something to do with what G drive can scan.
Click to expand...
Click to collapse
hy sir downlod the rom from google drive but unable to download 2nd link (link not working)
i use latest intel flas tool light but the rom no flash to my device its show errors. plese sir help me to run my tab again

oneplus 6T stuck on fastboot bootloop

hi team, i just bought a new oneplus 6T from china with Hydrogen OS, i changed it to Oxygen OS
but somehow it erased completly and stuck on fastboot bootloop, no bootloader, no recovery no system
i tried MsmdownloadTooln the laptop reconizes the phone but the operation stuck also on "param preprocessing"
please any help i would be greatful :crying::crying:

ritork said:
hi team, i just bought a new oneplus 6T from china with Hydrogen OS, i changed it to Oxygen OS
but somehow it erased completly and stuck on fastboot bootloop, no bootloader, no recovery no system
i tried MsmdownloadTooln the laptop reconizes the phone but the operation stuck also on "param preprocessing"
please any help i would be greatful :crying::crying:
Click to expand...
Click to collapse
Hey there I recently had the same problem with a OnePlus 6T... What I did was I installed everything manually using the ADB tools, in fastboot mode. Everything worked fine afterwards. Follow this guide, it will hopefully help.(It helped me ;D)
https://www.google.com/amp/s/forum....-stock-fastboot-roms-oneplus-6t-t3862516/amp/

Ethos001 said:
Hey there I recently had the same problem with a OnePlus 6T... What I did was I installed everything manually using the ADB tools, in fastboot mode. Everything worked fine afterwards. Follow this guide, it will hopefully help.(It helped me ;D)
https://www.google.com/amp/s/forum....-stock-fastboot-roms-oneplus-6t-t3862516/amp/
Click to expand...
Click to collapse
thanks for ur respond
i did this command "flash-all-partitions" but it showed me only "failed respond"
{
"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"
}

ritork said:
thanks for ur respond
i did this command "flash-all-partitions" but it showed me only "failed respond"
Click to expand...
Click to collapse
Make sure to have unzipped the compressed android file from the guide(whichever you decided to donwload) in the same folder as your ADB and Fastboot tools.
If it is still not working... try to manually flash everything in fastboot mode, that is what I did...
Download the latest version of android pie provided in the link from the guide( Google drive or Android Filehost), and then make sure to unzip the compressed file in the same folder where you installed your ADB and Fastboot Tool. Make sure a TWRP recovery image is in the same folder. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Then, what you should do is to follow the guide where it says:
MANUAL FLASH: Windows - OSX - Linux
Get back to me after you finished. Read twice, execute once :good:

Ethos001 said:
Make sure to have unzipped the compressed android file from the guide(whichever you decided to donwload) in the same folder as your ADB and Fastboot tools.
If it is still not working... try to manually flash everything in fastboot mode, that is what I did...
Download the latest version of android pie provided in the link from the guide( Google drive or Android Filehost), and then make sure to unzip the compressed file in the same folder where you installed your ADB and Fastboot Tool. Make sure a TWRP recovery image is in the same folder. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Then, what you should do is to follow the guide where it says:
MANUAL FLASH: Windows - OSX - Linux
Get back to me after you finished. Read twice, execute once :good:
Click to expand...
Click to collapse
Thanks a lot my friend
It works now after the second try
Thank u very much .. i really apreciate ur support mate

ritork said:
Thanks a lot my friend
It works now after the second try
Thank u very much .. i really apreciate ur support mate
Click to expand...
Click to collapse
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help

Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Thanks again mate <3

Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Hey, i want to flash oxygenos on my chinese variant with hydrogenos. could you help me with the installation in order to avoid this kind of problems(bootloop,brick etc.)?

HackerGames197 said:
Hey, i want to flash oxygenos on my chinese variant with hydrogenos. could you help me with the installation in order to avoid this kind of problems(bootloop,brick etc.)?
Click to expand...
Click to collapse
PM me

Gracie mille !!! First brick and i hope never again but you where there.. Huge thanks.

Download the TOOL ALL IN ONE and if it says fastboot device connected, I think you'll be fine. Make sure right below that you choose OnePlus 6T. Then just download and flash the full rom and it fixed mine, I had the same problem.

bigmikey307 said:
Download the TOOL ALL IN ONE and if it says fastboot device connected, I think you'll be fine. Make sure right below that you choose OnePlus 6T. Then just download and flash the full rom and it fixed mine, I had the same problem.
Click to expand...
Click to collapse
Thanks a lot.
Would you share the link of the TOOL ALL IN ONE?
I also have the same bootloop issue.

Micheal86 said:
Thanks a lot.
Would you share the link of the TOOL ALL IN ONE?
I also have the same bootloop issue.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Hope this helps

I have the same problem
PLeaseeee help me I have a rooted oneplus 6t. I performed a backup and wipe in hope to clear a problem and am now stuck in fastboot mode. Im pretty sure as I tried to reboot it said no os detected, and then I got stuck. I have tried to install the latest oxygen os by manualling flashing 4 files. all tutorials i read have bootloader and other files while i just have - system_matrix , system_manifest , vendor_matrix, vendor_menifest (XML files by the way). I have flashed these files and rebooted only to go back to the fastboot screen.

Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Bro please help me I didn't not much about this things but ill do flashing and customisation i bricked my Oneplus 6t its stuck on bootloader ill try msm tool also its shows param preprocessing ?
And my bootloader is also locked how can i solve this problem pls help me

For anyone running into a similar problem these are the steps I used
1. Download and extract files
a. Qualcomm drivers
b. MSM Oneplus 6t download Tool
2. Disable Driver Signature Enforcement by restarting your pc whilst holding shift, Choose trouble shoot, then going into more recovery ,select Advanced Options > Startup Settings > and then click on Restart.
3. Now PC will restart and Now you will see a list of startup settings that you can change. Select option 7 ‘Disable Driver Signature Enforcement’ by clicking f7
4. Now switch off your phone (by navigating through fast boot options)
5. While switched off hold both vol up + down for 5secs before connecting to your pc. *Your pc should recognise a phone is connected however nothing will be displayed on your phone*
6. Open device manager from start- Under Other devices there should be your phone (although it will be called smthn else), right click that and select update drivers
7. Browse computer for driver software and select folder with extracted QUALCOMM drivers (for me it was called unbrick).
8. The open the MSM application (run as admin tho) it should say device connected
9. Press start and you download should start- if error occurs or download stops unplug, power on, power off and the plug it again, now it should be fine.
10. Wait for download to finish and then your phone should be rebooted
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
mohitgaba14 said:
Bro please help me I didn't not much about this things but ill do flashing and customisation i bricked my Oneplus 6t its stuck on bootloader ill try msm tool also its shows param preprocessing
And my bootloader is also locked how can i solve this problem pls help me
Click to expand...
Click to collapse
Look at the post above