Database Develop

Unable to Reflash via LG Flash Tool

Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock ROM.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
Came back to it after a few weeks and issue has been resolved. Despite error warnings fastboot operated correctly, only manually. Any script etc. that booted device into fastboot would never find the device. Simple as flashing recovery and restoring a backup.
tl;dr: I'm not very bright.

FiniteDGk said:
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock KDZ.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
EDIT: Forgot to include that I see the proper devices in device manager.
EDIT 2: Device is properly configured and can be found in ADB when powered on.
Click to expand...
Click to collapse
where u able to fix it? i currently have no recovery or OS it just stays at the LG screen i can only get into Download mode i tried to flash a kdz but it cant read my phone....it turns on but thats it i cant got past the LG screen and when i connect my phone now i get different device drivers than before like LGE AndroidNet USB Serial Port and USB Modem....idk what to do

Can someone PLEASE help me boot my phone into FASTBOOT mode? ( T mobile h811) on CM13

When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?

did you ever unlock the phone....?

Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.

Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)

Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.

aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed

You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.

I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit

Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know

TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.

I reasked the question in Q and A. Please help some one.

You start over. LG bridge.

Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?

The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?

Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing

thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks

* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h

the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.

Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.

travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.

Cannot install TWRP recovery

Which is weird as it worked before.
Basic stuff. Android 6.0.1, MIUI 8.1
Bootloader unlocked
USB ADB drivers installed
Debugging on
Run TWRP and device is recognised, TWRP isntalled successfully but when I reboot phone into recovery, I get the standard "phone connected to usb cable" graphic. Im at a loss to know it wont go into TWRP, suggestions please?
Need to root to adjust in cqll volume settings, thx.

2bullish said:
Which is weird as it worked before.
Basic stuff. Android 6.0.1, MIUI 8.1
Bootloader unlocked
USB ADB drivers installed
Debugging on
Run TWRP and device is recognised, TWRP isntalled successfully but when I reboot phone into recovery, I get the standard "phone connected to usb cable" graphic. Im at a loss to know it wont go into TWRP, suggestions please?
Need to root to adjust in cqll volume settings, thx.
Click to expand...
Click to collapse
Not sure about alle the steps you did or did not do.
But if you install TWRP and then reboot back to MIUI, it will overwrite the recovery again.
From the TWRP.me site:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

Ok, followed all the steps exactly, the phone boots into twrp, then i reboot in system, or let it reboot by disconnecting, same thing happens. Black screen MI logo, bootloader unlock, in red, at the bottom of the screen with an open padlock.
Now it wont boot at all.

This is weird, I can boot into fastboot and recovery but when i try to flash, the device is redognised but i cannot see it in the drop down menu to find the rom. Grrrrrr im stuck.

2bullish said:
This is weird, I can boot into fastboot and recovery but when i try to flash, the device is redognised but i cannot see it in the drop down menu to find the rom. Grrrrrr im stuck.
Click to expand...
Click to collapse
OK, if you want to keep MIUI, just flash MIUI again and it should install the needed firmware, recovery etc.
You can use the recovery zip for this or the fastboot gz version to install (both should work).
If you want a custom rom installed, go to the Lineage thread (i use that since feb, with weekly updates) or another one.
Read the first few post carefully, but if you want to install it (Lineage), do flash the firmware first via recovery before flashing the rom (don't forget this one).

Update. I can get into TWRP recovery but have no back up.
If I try to boot into system I get a black screen with Mi logo and a red unlocked boot loader padlock graphic.
If i boot into fast boot and run miflash, the phone is recognised but the sd storage does not appear in the drop down at all.
I cannot use the pcsuite software and if the phone is not in TWRP or fastboot mode it is on the black screen with logo with red unlocked padlock and is not recognised by the PC. I dont know what else to do, any help will be greatly appreciated.

Found out the problem it was supersu, gonna try a different version

2bullish said:
Found out the problem it was supersu, gonna try a different version
Click to expand...
Click to collapse
Glad you found the problem.
I think that MIUI has already build in the SU via the Developer options, but i'm not sure of that.
If you think of Lineage, just flash the Lineage Su addon after the Lineage rom.
Works great.

2bullish said:
Update. I can get into TWRP recovery but have no back up.
If I try to boot into system I get a black screen with Mi logo and a red unlocked boot loader padlock graphic.
If i boot into fast boot and run miflash, the phone is recognised but the sd storage does not appear in the drop down at all.
I cannot use the pcsuite software and if the phone is not in TWRP or fastboot mode it is on the black screen with logo with red unlocked padlock and is not recognised by the PC. I dont know what else to do, any help will be greatly appreciated.
Click to expand...
Click to collapse
MIUI has some sort of verification on boot. If it detects a custom recovery different from stock one, it won't boot. You need to use zcx twrp. It can bypass this verification.

I really ****ed up

So, I ****ed up.
Earlier this night i hard bricked my device while trying to uninstall Magisk. Used a guide that worked and was back on stock OOS 3.5.0.
In the old Oxygen OS I installed TWRP. But the thing with the recovery was that you needed to boot recovery from the command line with the command
Code:
fastboot boot twrp.img
. If I booted into recovery in any other way the screen is just black and never boots.
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
I relocked it, and when it was done I got the prompt to fill in the password to start Android. But the thing was I did not use any security options, no fingerprint or pin code. So zero luck there. And now I can't boot into recovery because I didn't flash the stock recovery because I'm a retard, so when I'm trying to boot recovery it's just black. So I have no chance to come back. Please help...

So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!

thes3usa said:
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply, I tried to do the method with the MSMDownload thing yesterday, but the computer did not recognize the device. It was late in the night (5am) so I went to bed. This morning I took my other computer and plugged my phone in, it recognized it and I was able to fully recover the phone!

avveawesome said:
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
Click to expand...
Click to collapse
This isn't good idea. As already noted, never relock the bootloader on this device with TWRP, root, etc. It should only be relocked after returning to full stock condition.
Also, never install an incremental OTA when you have TWRP (root, etc.), only the full update zips should be used in that case.
Try to stick to these forums for advice. Maybe the guidance your found above is not specific to this device?

"Broken" Oneplus 3T - can it be saved?

Hi!
This phone has been given to me as broken. Yet the bootloader and fastboot work, so maybe there is something I can do? (I would love to install Ubuntu Touch on it!)
State of the phone, and approximately what I've done until now:
- fastboot works (sometimes I can access it from the PC, sometimes I can't)
- adb doesn't
- no system boot
- bootloader and fastboot only show up when phone is plugged in. If I unplug it the screen goes black.
- Can't access the recovery. Tried flashing TWRP (both official and modified found on XDA) or stock recovery, tried booting it from terminal.
- I have the dm-verity message show up ("dm-verity in not started in enforcing mode") when trying to boot. Threads I've found explaining how to disable it say it requires TWRP or adb (I think), and I can't access either
- tried modified boot.img, stock boot (can't remember exactly)
I have little hope, but maybe someone can come up with a good idea?
Thanks for reading!