My g4 is in a state of half alive half dead.
I explained in another post my issue.
Seemingly people say lg up tool is now the only method Unlike the old flash tool method to unbrick or kdz stock is this Only cause of 6.0 firmware?
When i plug in phone to pc in download mode Lg up tool shows device model as unknown. And says please select a device model which theres no butons to do that.
Lg flash tool 2014 won't flash 20i kdz it errors out connection upon extracting kdz software at around 80% Even leting it sit don't work like people say to do
Ive tried 10n kdz also that says software upgrade in progress fails at 9% then says unplug phone from pc and retry.
There is no Com in the download mode screen at any point.
All i did by mistake was fastboot oem relock bootloader Whilw rooted and on micromods Rom ONLY cause i wasnt sure if that' was the cause of the failed Flash tool errors. Now i have secure boot error 1003. Now I knew that was a No no with Nexus phones but i suspected Lg kdz over writes all that stuff.
Theres gotta be a way with one of the 2 tools Or a way to adb re unlock the bootloader and maybe salvage my Underlying twrp recovery and O.S
ANY HELP HELPS
Sent from my LGMS631 using XDA Free mobile app
Good night guys.-
I wonder if there is any solution for brick G4 for this version , since I have seen it is releasing some files from multiple versions except those to remove the brick my device.
Thank you
It depends on how you bricked it and what state it's in.
Does your phone turn on?
what's on the display?
when you plug it into a computer does it show up as a device and if so what kind?
what did you do to brick it?
lart2150 said:
It depends on how you bricked it and what state it's in.
Does your phone turn on?
what's on the display?
when you plug it into a computer does it show up as a device and if so what kind?
what did you do to brick it?
Click to expand...
Click to collapse
the screen or the LED is not lit , the pc recognize me as " qhsusb_bulk "
I don't think we have a fix for qhsusb_bulk yet. sounds like you flashed a boot loader for a different device.
I Fixed it on my H811. For those who need help, i have written the thread
Visit http://forum.xda-developers.com/tmobile-g4/general/lg-g4-h811-complete-unbrick-guide-100-t3461629
I need help please.
I have a H811 T-mobile LG G4. I unlocked the bootloader, flashed TWRP, flashed MM-20e Global rom which is ported rom from H815 20e. Everything worked well untill I deciced to relock the bootloader! I have issued a command fastboot oem lock and the device began to bootloop. "Secure Booting Error, Error Code 1003, MODIFIED".
I Have tried LG Bridge but it says "Can't check internal storage".
I Have tried LGUP with several kdz files including H81120o but it says "Invalid kdz file" (LGUP sees my device as H81520e now)
I have tried LG Flash tool and nothing works.
Your help would be highly appreciated.
I had messed up a couple settings on the custom ROM I was running. I wanted to get back the stock setting so I went to recovery and did a wipe. I rebooted and found I lost supersu. I went to reboot back to recovery to flash supersu and It wouldn't boot into recovery. I went to adb on computer and couldn't reboot it there either. I found I could put the phone into Download mode. I tried the flashtool and LGUP and neither will communicate with the phone to be able to flash stock firmware. I don't mind too much because I can JUMP, its just the boot animation says Xperia.
ADB commands only produce "Waiting for device"
Flashtool says, "Wrong dll file"
LGUP won't let me use a current KDZ but only a tot file and the only one I found is 10n.
Relevant thoughts welcome as I continue to scour these pages.
Apparently LGUP considers going from 20r to 20p and upgrade. Lesson learned. 1) When your phone is bricked playing with other tool settings can't hurt anything. 2) Sometimes the OP of a thread can be a little ambiguous, read and reread. If one thing doesn't work, check for (possible) variations.
I was using refurbish setting on LGUP because that's what seemed to apply.
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?
I found a similar thread: Stuck on LG Bootscreen only download mode, LGUP didn't work that DIDN'T have an answer, in case anybody asks.
Basically, no fastboot, no recovery, download mode but LG Flash Tool 2014 AND LGUP don't seem to recognize it.
I was originally on the latest T-Mobile Firmware, then I unlocked the bootloader, installed TWRP, and installed the H-ROM.
I don't remember what exactly happened, but a bunch of factory resets and a few reboots into and out of TWRP later, I'm assuming I've bootlooped. Neither LGUP nor LG Bridge will work, but I can still boot into download mode. Is the only solution really the freezer/hair dryer method, or is it possible to use software to fix it?
Please delete, this thread is no longer needed as the phone is currently fixed.