Related
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
reeper250 said:
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
Click to expand...
Click to collapse
Oh my god.. What happend to you g2 ?
First, don't give up, sooner or later you are gonna unbrick your G2 in the end. I have been there too.
If you can get into download mode, you are very lucky.
Just Ignore root thing, it has nothing to do with flashing KDZ/TOT.
You got to learn how to use LG flashtool first.
http://forum.xda-developers.com/showthread.php?t=2432476
My suggestion is that just stick to TOT tool instead of KDZ tool. Sometimes KDZ tool fails during flashing without proper reason.
And that problem often happens when you are going back to stock rom from CM12.1 roms like DU, BlissPop...
But one thing to remember, TOT tool would wipe out your internal memory.
Unplugging you external SD memory is recommended while doing KDZ/TOT flashing.
If you still fail with TOT tool.... It's no good. You may have to try short-circuit method.
Good luck.
ailing said:
Oh my god.. What happend to you g2 ?
First, don't give up, sooner or later you are gonna unbrick your G2 in the end. I have been there too.
If you can get into download mode, you are very lucky.
Just Ignore root thing, it has nothing to do with flashing KDZ/TOT.
You got to learn how to use LG flashtool first.
http://forum.xda-developers.com/showthread.php?t=2432476
My suggestion is that just stick to TOT tool instead of KDZ tool. Sometimes KDZ tool fails during flashing without proper reason.
And that problem often happens when you are going back to stock rom from CM12.1 roms like DU, BlissPop...
But one thing to remember, TOT tool would wipe out your internal memory.
Unplugging you external SD memory is recommended while doing KDZ/TOT flashing.
If you still fail with TOT tool.... It's no good. You may have to try short-circuit method.
Good luck.
Click to expand...
Click to collapse
Failed everything except TOT. The TOT took about 6-8 hours to download...
Flashed TOT and it booted fine, then updated to stock Lollipop with KDZ. It's currently working EXCEPT....
Camera doesn't work still, can't send a text because the "Messaging" app force closes, don't have the flash light, and I can't seem to start ABD to root it.
SD Card is working fine though. Using a 64GB formatted to FAT32 and restored all my pictures, music, etc.
The main thing is the camera and messaging app, plus the flash light is really handy when working on my car.
At least I have a working phone
Managed to get it recognised in device manager and ADB but when rooting it stops at 45%...
reeper250 said:
Managed to get it recognised in device manager and ADB but when rooting it stops at 45%...
Click to expand...
Click to collapse
Oh... I think there's possibility your camera hardware has gone out of order.
When you are in LG stock rom, and still experience problem... well I guess it's not software problem.
Because TOT flashing is complete software factory reset. It revert everything to out of factory state.
And for rooting, sometimes it just get stuck. but suddenly it just get rooted. I can't explain the reason.
But you should remember one thing in mind, don't initialize V3. It's anti virus program, and it blocks rooting.
When you boot for the first time, you maybe was asked if you agree with V3 software, just choose don't agree and skip it.
If you still fail rooting, just flash KDZ/TOT again to go back to KitKat. When you're done with flashing KDZ/TOT, just stay there and don't update KK version because KK update could block rooting.
Of course you should not agree with V3 software install.
Use towel root, it's the most easiest way. go to towelroot.com and download apk. (click logo)
Root your G2 and use KitKat version of autorec to install TWRP.
ailing said:
Oh... I think there's possibility your camera hardware has gone out of order.
When you are in LG stock rom, and still experience problem... well I guess it's not software problem.
Because TOT flashing is complete software factory reset. It revert everything to out of factory state.
And for rooting, sometimes it just get stuck. but suddenly it just get rooted. I can't explain the reason.
But you should remember one thing in mind, don't initialize V3. It's anti virus program, and it blocks rooting.
When you boot for the first time, you maybe was asked if you agree with V3 software, just choose don't agree and skip it.
If you still fail rooting, just flash KDZ/TOT again to go back to KitKat. When you're done with flashing KDZ/TOT, just stay there and don't update KK version because KK update could block rooting.
Of course you should not agree with V3 software install.
Use towel root, it's the most easiest way. go to towelroot.com and download apk. (click logo)
Root your G2 and use KitKat version of autorec to install TWRP.
Click to expand...
Click to collapse
Got root eventually. Not sure why but it worked after like the 6th time...
Is it the bootstack or something that's causing the camera and flash to stop working?
It only started having those issues when I installed the new bootstack.
I'm about to throw this stupid phone against the wall...
I cleared Cache and Dalvik Cache after successfully installing TWRP and it came up with "Security Error" and I can't boot
reeper250 said:
I'm about to throw this stupid phone against the wall...
I cleared Cache and Dalvik Cache after successfully installing TWRP and it came up with "Security Error" and I can't boot
Click to expand...
Click to collapse
I can guarantee TOT flashing would revert everything to factory default state. So Even if bootstack has caused problem, after flashing TOT, everything should be back to normal. Because TOT flashing includes bootstack.
Tot flashing completely wipe out your G2 and rewrite EVERYTHING.
I am 100 percent sure that camera's malfunction has nothing to do with bootstack.
BTW, which version of autorec did you use ? There are two versions of autorec. You should not be mistaken.
Because KitKat autorec would destroy Lollipop's kernel and cause security error.
To my knowledge, XDA forum has only KK version which made by cloudyfa.
Even if you had security error, It's too early to give up.
First, Power off, and holding vol.up and connect USB. If you are lucky again, you would see download mode.
Or try to get into recovery by pressing vol.up and power.
At worst case, you can't get into recovery nor download mode, either.
But That doesn't mean you should throw out g2. You can still revive G2.
Recently I made how to revive bricked G2 (only F320 specific) in Korean. It's already known method.
You have to open back cover and disassemble to try short-circuit.
If you really want to try short-circuit method, I would make short translated version for you.
G2 is really hard to brick. So don't throw up until G2 is real dead.
Good luck
ailing said:
I can guarantee TOT flashing would revert everything to factory default state. So Even if bootstack has caused problem, after flashing TOT, everything should be back to normal. Because TOT flashing includes bootstack.
Tot flashing completely wipe out your G2 and rewrite EVERYTHING.
I am 100 percent sure that camera's malfunction has nothing to do with bootstack.
BTW, which version of autorec did you use ? There are two versions of autorec. You should not be mistaken.
Because KitKat autorec would destroy Lollipop's kernel and cause security error.
To my knowledge, XDA forum has only KK version which made by cloudyfa.
Even if you had security error, It's too early to give up.
First, Power off, and holding vol.up and connect USB. If you are lucky again, you would see download mode.
Or try to get into recovery by pressing vol.up and power.
At worst case, you can't get into recovery nor download mode, either.
But That doesn't mean you should throw out g2. You can still revive G2.
Recently I made how to revive bricked G2 (only F320 specific) in Korean. It's already known method.
You have to open back cover and disassemble to try short-circuit.
If you really want to try short-circuit method, I would make short translated version for you.
G2 is really hard to brick. So don't throw up until G2 is real dead.
Good luck
Click to expand...
Click to collapse
I probably installed the wrong AutoRec then...
Flashed the KDZ again and booted but it's saying "System UI has stopped", com.android.phone has stopped", etc.
I guess I have to TOT flash again and start over... again...
reeper250 said:
I probably installed the wrong AutoRec then...
Flashed the KDZ again and booted but it's saying "System UI has stopped", com.android.phone has stopped", etc.
I guess I have to TOT flash again and start over... again...
Click to expand...
Click to collapse
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
ailing said:
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
Click to expand...
Click to collapse
TOT is for my F320S, just flashed it again and it worked.
Installed AutoRec LP and it worked. Ended up installing Dirty Unicorns 5.1.1 which worked.
Camera and flash still don't work.
I remember this happened to me ages ago but I can't remember how I fixed it
ailing said:
In normal case, after flashing TOT, there should not be any problem at all. Because It's in factory default condition. I mean, it's like the first time you open up the package right after you buy.
As for your case, I think something is seriously wrong.
Make sure you flashed right TOT matched to your F320. As you already know, there are 3 variants, F320S, F320K, F320L.
Ah.. I almost forgot. If you want to try aosp roms other than LG stock rom, you can try when you are in KitKat, too. While you are in KK, don't update KK version. Because updated KK version blocks rooting.
Right after flashing KK tot/kdz, try towel root. It's the easiest rooting tool.
You can download it at towelroot.com
After rooting, install supersu and use KK autorec (which made by cloudyfa) to install TWRP.
But In my opinion you should figure out why stock rom has system UI crash.
In authorized LG service center, engineer uses the same TOT tool. In theory you can't have any problem after flashing TOT. unless there are some damaged hardware.
This is all I can help. Hope you solve the problem.
Click to expand...
Click to collapse
Hello it is easy to provide me links to f320s .tot and .dll ?
LG g2 d802 not accepting fastboot commands
reeper250 said:
I tried updating the bootstack on my LG G2 since it was having WiFi disconnect issues. After updating it with the Lollipop bootstack on a Lollipop ROM (Dirty Unicorns 5.1.1) I couldn't use the camera and flash light.
I then decided to just flash the stock LG G2 Lollipop KDZ and start afresh.
However, my phone became bricked into fastboot mode but I got out of it by flashing all the img files through fastboot. Now it is getting stuck at the LG logo and I can't enter fastboot or recovery now... I can access download mode but it says it's still rooted and when I go to flash a new KDZ (tried multiple versions) it says phone disconnected, or force closes the support tool.
I've been in this situation before but I can't remember how I got out of it...
I'm running Windows 8.1 and have read that you can't flash KDZ through the support tool on Windows 8/8.1 so I'm in the process of installing a Windows 7 virtual machine.
Click to expand...
Click to collapse
if anyone can help me. I dont know if it'is a hard brick or not, but i can go to the fastboot mode only. when i try to erase some partitions tho i get this error FAILED (remote: failed to erase partition) and my phone says Failure sending erase group start command to the card(RD;2).
I've tried to flash files too but nothing seems to work since everything leads me to an error and the phone says this when i try to flash it :Failure sending write group start command to the card(RD;2).
if anyone is able to help me, i would very much appriciate
1，unlocked bootload，https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2，install rec for h850 ，http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3，into rec and flash LG-H85010E-Flashable.Bootloader.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1
xjqlfq said:
1，unlocked bootload，https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2，install rec for h850 ，http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3，into rec and flash LG-H85010E-Flashable.COMPLETE.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1
Click to expand...
Click to collapse
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
thanks，get it
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
fuxi222 said:
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
Click to expand...
Click to collapse
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
At first: Big thanks for your quick response!!!
to 1.: The reason for 10C instead of 10E is simple: you do not have a KDZ file for 10E on your codefire drive (only a ZIP), but for 10C the KDZ was available. And the links to LG server were not working yesterday for me.
I read Uppercut the first time now and will give it a try today in the evening (German time). :fingers-crossed:
to 2.: Understood. Thank you! :good:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:
fuxi222 said:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:
Click to expand...
Click to collapse
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
autoprime said:
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
Click to expand...
Click to collapse
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
fuxi222 said:
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
Click to expand...
Click to collapse
i dont have an H850 so idk.. but any time ive had someone zero cust theyve said errors have gone away. so if they dont for you.. you must be special. try it and find out... then report back. if it doesnt work... ¯\_(ツ)_/¯
old lgup methods = 1.11 + dll msi installer, yes. but i see no reason to use 1.11 simply for refurbish option. most people should be able to use LGUP 1.14 + UPPERCUT for most situations on G4/G5/V20.
i dont know abotu the NT code stuff with LGUP.. again.. I dont have a H850. but if you have TWRP then there's really no need to be messing with LGUP at all unless you want to be 100% stock/unrooted with no TWRP. just zero cust or try flashing the cust.img that's in the folder.
I cant help any more on this NTCode subject without a device that uses it. good luck.
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
Only if someone is on the same point: For me, it is only working to flash the COMPLETE ZIP! When I flash bootloader only, LGUP does not detect the model type of my device anymore (detected type is "Unknown"). I have tried it now for 2 times with similar results...
BTW: I used this method to get rid of the annoying NT code issue: http://forum.xda-developers.com/showpost.php?p=66957161&postcount=4
@autoprime Can't we just flash 10E with the refubrish option? Somehow I'm unable to get into recovery with the button combination after downgrading and updating again, even though I'm doing it properly and I was able to do it before.
EDIT: So refubrish stopped working now too. Dang. I installed the recovery through Dirty Cow, flashed the bootstack and went back to 10E, but I still don't have a recovery. ;_;
Ok, I've tried everything and button combination for recovery still doesn't work, so think if you really wanna risk being unable to easily factory reset your phone.
autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
chrcol said:
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
Click to expand...
Click to collapse
Did u try what I suggested in other thread? Wipe internal storage before first boot, reboot recovery afterwards before booting system; are u clean flashing? Are you trying to restore any data at all besides things like messages and call logs?
Going from an openEU.kdz to a branded .Kdz would definitely require a Twrp data format and a recovery reboot, perhaps do all this b4 using LGUP with kdz.
Yes it is possible to make a .zip from a kdz, but it's not a simple process and there is no EE branded 20a.zip
Autoprime already stated that refurbish option can be used if you use LGUP v1.11 instead of latest 1.14 but don't forget the .DLL file. Also all refurbish does is wipe data and internal storage; which can be done via TWRP using the method I mentioned above. Try what I mentioned and then reflash kdz;forget about any data besides text messages just take the extra 30min to resetup device from scratch.
What version of LGUP are you using? Can u give more info be more descriptive about what's happening?
it is resolved now but I was just trying to get it in a good state to return the phone to EE.
Doing a factory reset in twrp didnt work, but what did work is I did a reset from in the rom, and after the reboot it was properly reset.
What was odd is when I wiped system and data manually in twrp that also didnt work.
I think I forgot to check if I completely wiped the internal storage, photos etc. As I was rushing to get the phone to be sent back. But the description for the reset option in android says it does wipe all personal data so hopefully that did it.
How can I downgrade LS992?
İs this possible for lg g5 H860?
For H850 just download H85010i_00_OPEN_EU_OP_0923.kdz flash it with LGUP 1.4(uppercut) after it's finished reset the phone then just flash android 6 firmware that you like.
i have h850 ,
current firmware is v20a updated via fota
no root , no bootloader unlock ,,, compleatlly stock phone
i want to downgreade to any 6.0.1 firmware without losing data (if possible)
if not, what to check and what steps to do without tripping on cust ot drk or modem or .... issues ?
pleas advice me ....
LGUP corrupts whenever i hit Start, but it works just fine with N kdz (mine is 20a). I have tried to flash bootloader but still ended up with the same outcome.
Lucky patcher does not work on nougat. Application not installed. playstore error 504
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I rooted H850 following autoprime's LG G5 H850 Bootloader Unlock instruction with autoprime's modded "Minimal ADB and Fastboot" {[ 1.) selecting port 41 in device manager (maybe was not necessary) and 2.) pushing TWRP twrp-3.1.1-0-h850.img 3.)booted into recovery (Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.) 4. flashing SuperSU (UPDATE-SuperSU-v2.82-20170528234214.zip) ]}.
Installed 20a with lgup because for a strange (windows 10 folder administrator permission) reason nether UPPERCUT_1.0.0.0.exe nether LGFlashTool.exe worked properly).
Unfortunatly I installed [ROM] [Nougat 7.0] Fulmics ROM 3.3 ◦ v20D ◦ H850 but, because the very big LACK of xposed framework on nougat, I had too much difficulties to patch correctly the core jar with lucky patcher getting a lot of error "app not installed the package appears to be corrupt" and other play store error 504 app not installed.
So I decided to downgrade and leave from any Nougat 7.0 based rom in order to move on Marshmallow 6.0. In particular I used TWRP to wipe everything and flash [STOCK][M] H850 10E OPEN EU ROM autoprime's 10E COMPLETE ZIP then Supersu then framework.
On android this time I skipped google registration and LG software updates with data and wifi OFF.
Then I activated USB debug in developer section
Then I followed these step in that really precise order:
a) installed super su again with twrp (want to be sure to have got ROOT);
b) configure Super Su setting in android to activate pseudo PRO option then uncheck the "separation mount space" in order to share .init;
c) configure Super Su setting giving permission always without asking and also during in boot (to everybody);
d) installed xposed-v87-sdk23-arm64.zip in TWRP
e) installed lucky patcher and using it to unistall every LG apps;
f) activate for the very first time wify in order to update immidiately lucky patcher (update available in lucky patcher settings) than download patch update;
g) installed xposed apk (in android obviosly because I refer to apk pattern) and run it following app procedure for a correct detection of framework then activate Lucky patcher module in xposed apk then reboot to permit lucky patcher using framework;
h) installed busybox (after the check I choose the "smart install").
i) and now I enjoy the freedom that I haven't got in Nougat to test some application before buying them, just to be sure to not waste money for fake apk like voice pro or other expensive one that fools me before so many times. :good:
Update: G5 H850 Genisys Theme 1.3 v10e MM is a great choice for stability and battery life.
Hi guys,
First, English isn't my first language so, sorry if it hurts your eyes :/
Second, I'm new to TWRP / root etc... (since yesterday) and I don't fully understand the exact meening of all words like flash / rom etc...
So: I'm actually blocked in the "Your device can't be checked for corruption. Please lock the bootloader". Apparently it's a normal screen now, when we boot we always see this. OK ( at least that's what I read)
My volume keys aren't doing anything and I can't access my phone anymore.
I can access TWRP if I want.
Thx for responding :good:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
coremania said:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
Click to expand...
Click to collapse
How can I know if ADB recognize my phone?
I can access TWRP so I don't need to flash it again ? Is there a difference between just flash TWRP and flash TWRP with fastboot ?
Sry, my bad, i miss read that you can access twrp, sry, I thought you can't, what happens if you flash a rom, which twrp is installed, what were your steps that you end stuck on bootloader message ?
Edit: if your issue is that you don't know how to start flashing, read the Los thread and follow the op.
Instructions:
1. Install the Universal bootloader and your model specific modem.Failure to do so will not allow flashing the ROM!
2. Update recovery [Recommended -> Official TWRP for Axon7
3. Factory reset if coming from another ROM.
4. Install ROM
5. Install GApps (optionally) [Recommended -> Open GApps (arm64) (7.1) 2017-02-01 or Newer
Download all files from the thread and put them on to your microsdcard, if your twrp is up to date you don't have to do this again. Flash the zip files in the order of the instructions, just press install at twrp and choose the zips, you can add multiple and flash them together.
Man, trust me, I'm not a lazy man and all I want is to have my phone back even if it's stock
I don't understand what you're trying to make me do, sincerely
If you can give me a link where I can have a guide steps by steps or make this guide for me that would be the best thing of my day...
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
I really don't know your issue, except you seem not to read enough. What guide you want ? How I flash a custom rom to my phone ? How to use twrp ?Why you unlocked your bootloader ? How did you manage to have the stock recovery back ?
I have to guess what you want and what you already did . If you need a guide, here are severals in the guide section.
https://forum.xda-developers.com/axon-7/how-to
TheGreatNarchy said:
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
Click to expand...
Click to collapse
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
JTruj1ll0923 said:
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
Click to expand...
Click to collapse
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Choose an username... said:
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Click to expand...
Click to collapse
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
JTruj1ll0923 said:
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
Click to expand...
Click to collapse
The thing is, after you flash the universal bootloader, the TWRP on the sd gets replaced. but the TWRP that you are using is loaded in RAM. So even if you install a TWRP version you'll stay in the version you flashed before until you reboot. If you install the universal bootloader and then install the TWRP img you'll keep everything as-is on the next reboot. I discourage rebooting without a system especially on a G because any interruption might lock the phone in DFU. On an a2017U that wouldn't be a problem because the phone boots into edl if any software error is present
I have screwed my phone big time. It has been screwed for a while and I've been searching for methods to fix it. So awhile back when I didn't know about the sheer amount of models of this phone there are, I tried to flash TWRP. The image was not for my model and my recovery is screwed. I figured that it was no big deal, the phone worked just fine. Not long afterwards, I was goofing with Xposed modules. One of these broke Asus's ZenUI or something, because the phone boots up and Systemui.apk immediately crashes and won't stop. It's just a black screen with the error message box. There is a repair option that pops up in the dialogue box after a while, but it does nothing. I've tried remote wipe with Google services, but my location services are off and I can't turn them on. I've tried Xposed safe mode, but it won't engage. USB debugging is off and I can't enable it or USB mass storage mode, because there is a prompt that I can't tap. I can't get into recovery, because it just goes right to the boot logo. Fastboot works, but I can't flash a new firmware with it, because the bootloader is locked. Does anyone have any suggestions or even a backup of the original recovery.img for the US model? ASUS provides the system but not recovery.img and their support staff gets angry if you ask for it. The root of the issue is Systemui.apk. Since I can't just replace that, I have to restore, and I don't have a way to restore Android to factory settings.
Unofficial bootloader unlock followed by flashing twrp or stock recovery if you can find it. Twrp will allow you to mount your sdcard if you want to try just replacing systemui.apk, otherwise both recoveries can flash back the stock Rom. You might be able to get away with dirty flashing your current rom if replacing the APK doesn't work.
wang1chung said:
Unofficial bootloader unlock followed by flashing twrp or stock recovery if you can find it. Twrp will allow you to mount your sdcard if you want to try just replacing systemui.apk, otherwise both recoveries can flash back the stock Rom. You might be able to get away with dirty flashing your current rom if replacing the APK doesn't work.
Click to expand...
Click to collapse
That's the thing, though. There is no twrp available. There is no stock recovery available. I can't unlock the bootloader, because ASUS never released a working method to do it. I am screwed.
Have you tried to dirty flash the same firmware version you have via Asus flash tool?
wang1chung said:
Have you tried to dirty flash the same firmware version you have via Asus flash tool?
Click to expand...
Click to collapse
Sorry about the delay, but ASUS flash tool doesn't recognize the phone, either in system or fastboot modes. That tool doesn't seem to work with fastboot. Basically I have to do some trickery with fastboot but there isn't much available to do with it.
Sorry, it's not Asus flash tool, it's sp flash tool.
Check out this guide.
wang1chung said:
Sorry, it's not Asus flash tool, it's sp flash tool.
Check out this guide.
Click to expand...
Click to collapse
Tried this. Have the official firmware but need a scatter file. The one in the firmware zip is deemed invalid because it is missing a lot of the required data I suppose. If only I had made a backup of everything while the phone was still working...
Hiya, after redoing lafsploit on my v20, the device only boots to recovery and only twrp 3.4.0-1 works. anything newer and it boots to fastboot.
as we all know, LG has crippled fastboot.
device also crashes/reboots any time you try and write to the device be it flashing roms or copying a file with twrp.
anyway, I'm looking for a solution.
Hey Eriklion,
I am not a pro, in fact I have only rooted my Samsung Galaxy S4 so far, and right now reading everything I can to root my H918, so read what I wrote with a healthy dose of skepticism, because I am most likely completely wrong, but, since no one else is responding I am compelled to try.
If you have followed the thread:
Step by step guide for lg v20 h918 unlocking, downgrading, rooting and twrp
STEP BY STEP GUIDE FOR LG V20 H918 UNLOCKING BOOTLOADER, DOWNGRADING, ROOTING AND INSTALLING CUSTOM ROMS (NOOB FRIENDLY) DISCLAIMER: I'M NOT THE DEVELOPER OF ANY OF THE BELOW SOFTWARE'S AND YOU PROCEED WITH YOUR OWN RISK AS THIS INVOLVES...
forum.xda-developers.com
to KDZ downgrade to "h" and then use lafsploit to flash the TWRP, then in those instructions, there is a slight error:
the instructions do not clearly specify to use only a particular version of the TWRP, yet, that seem to be the requirement.
You can see that discussed in:
H918 Stuck on secure startup "decryption unsuccessful" on boot
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258 and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption...
forum.xda-developers.com
Now, in your case, you do not have a decryption issues, but I think the actual results may vary, depending on what version of recovery you flashed using the lafsploit from FWUL.
As to how to fix..? Well in the latter mentioned thread they seem to all suggest fastboot flashing the correct version of TWRP, being very careful not to forget to use advanced format data from the boot to the TWRP that is immediately follows the TWRP flashing process. However, everything I read seem to be telling me that the flash over the fastboot is impossible for the H918 (and I think you mentioned this in your OP), so IDK what they are talking about.
May-be it is possible to reload the TWRP (this time a correct version) the same way you just installed the 3.4.0-1?
If not, may-be reflashing back the "h" KDZ, and then flashing the correct (3.2.3-4) version of TWRP from FWUL?
And do not forget that advanced format of data partition, which has to be completed no later than the first boot to TWRP immediately after TWRP is flashed on, i.e. before the device gets to complete even one boot to system!
This is all I can say. Please, let us know if your issue is resolved and if yes then how. Good luck!
Hi Eriklion, any progress for your situation?