[NEED HELP] Korean Pie on LM-G10V Problem (Softbricked?) - LG G7 ThinQ Questions & Answers

So, I happened to follow the steps in this video : https://www.youtube.com/watch?v=qJ4w7G8zl7s on how to install the Korean Pie Kdz to ANY G7 but it resulted to me having issues with the phone such as : The phone would Reboot by itself randomly and my WiFI Mac address turned 02:00:00:00:00.
UNIT INFO
Before the Procedure
I was running an LM-G710V 10b with an unlocked boot loader
Flashed with Oreo AOSP Treble
Has Fastboot access
No Recovery Access
Magisk Installed but no TWRP.
After the Procedure
the Phone model shows LM-G710N 20c
I can not access Fastboot mode thru either button combo or ADB (Both would only reboot the phone normally).
OEM unlock in developer options is greyed out saying Bootloader is already unlocked
No ROOT ACCESS
Can Access Download mode and (useless)Stock Recovery (Thru ADB)
Phone boots normally, however it would reboot randomly.
Additional Notes:
I used LGUP 1.14.3 and the kdz from this thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/pie-korean-kdz-g710n20c00lgukrop0107-t3891207
LGUP can still recognize the phone, however the model now is LM-G710N, and unfortunately LG Bridge does not recognize the phone.
Any Help or Inputs in resolving this would be greatly Appreciated !

xElouise said:
So, I happened to follow the steps in this video :
on how to install the Korean Pie Kdz to ANY G7 but it resulted to me having issues with the phone such as : The phone would Reboot by itself randomly and my WiFI Mac address turned 02:00:00:00:00.
UNIT INFO
Before the Procedure
Flashed with Oreo AOSP Treble
Has Fastboot access
No Recovery Access
Magisk Installed but no TWRP.
After the Procedure
I can not access Fastboot mode thru either button combo or ADB (Both would only reboot the phone normally).
OEM unlock in developer options is greyed out saying Bootloader is already unlocked
No ROOT ACCESS
Can Access Download mode and (useless)Stock Recovery (Thru ADB)
Phone boots normally, however it would reboot randomly.
Additional Notes:
I used LGUP 1.14.3 and the kdz from this thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/pie-korean-kdz-g710n20c00lgukrop0107-t3891207
LGUP can still recognize the phone, however the model now is LM-G710N, and unfortunately LG Bridge does not recognize the phone.
Any Help or Inputs in resolving this would be greatly Appreciated !
Click to expand...
Click to collapse
That shouldn't happen at all. You can try to make the same procedure again but flashing an Oreo kdz.
Edit: also what model was your phone originally?

LameMonster82 said:
That shouldn't happen at all. You can try to make the same procedure again but flashing an Oreo kdz.
Edit: also what model was your phone originally?
Click to expand...
Click to collapse
It's the retail unit LM-G710V 10b.
I don't know what Oreo kdz would be applicable for this unit.
*Typo on Title, Should be LM-G710V
-Update-
So i tried to flash another kdz "G710VMX10j_00_USC_US_OP_1120.kdz" , it completed but gave me a Kernel Crash (entered Sahara Mode) at first boot, then rebooted normally but still my Phone model remained LMG710N but it's now 10j instead of 20c. It still reboots randomly.
-Pics-
Snapped a pick of the Kernel Crash & After Oreo kdz flash : https://imgur.com/a/tgZoXCk
-UPDATE 02-
02/06/19
So I Tried it with SALT and this comes up on the main GUI
https://imgur.com/a/lKUeLqG
SALT also can not read the phone's partitions.
Attachments are some logs from SALT.
-Opinion-
I am suspecting the the problem lies within the phone itself. Maybe some corrupted partitions that became unflashable.
LGUP DFT says there is a mismatch on PRIMARY GPT no matter what kdz i flash.

Related

[SOLVED] ZE550ML bricked after Marshmallow Beta - Now fastboot but no more serial no

Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Have you tried to re flash fastboot (fastboot flash droidboot.img)?
About the serial number, I think 0123..DEF is normal because I mine is like yours, too. But everything is fine.
fanfan54 said:
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Click to expand...
Click to collapse
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Serial number restored by Asus Flash Tool, now I can flash with fastboot
Hakataben said:
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Click to expand...
Click to collapse
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
fanfan54 said:
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
Click to expand...
Click to collapse
If you want to use Marshmallow, I recommend to flash pre-rooted lollipop first, then to flash marshmallow. In your situation, you should unbrick your Z008 at first. After that, you can change system to Marshmallow easily.
Pre-rooted Z008 systems are here. http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
In my case, I needed to have rooted and bootloader-unlocked again to enter in recovery.
Yay!
ASUS Flash Tool flashed the 2.20.40.149 successfully
It's saying "Optimizing app 45 of 119", but I think I had 179 when upgrading to Marshmallow...
And my Android was in french before. But I think I'll be able to fix this
I'll check soon if I've still all my data and apps...
(also, I tried to film everything, if it works I could eventually upload a video tutorial )
Thanks
Another problem... Edit 1
Android boots, I haven't any installation "Welcome" popup because I did not reset it, but as a consequence it crashes at start :
"Unfortunately, android.process.media stopped"
"Unfortunately, android.process.acore stopped"
And it reboots
Maybe it's because these are Marshmallow apps... Will I have to reset it?
Or where can I find system.img for Marshmallow?
Edit 2 Just managed to access to recovery menu
Definitely solved
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
ZF2/ZE550ML/Z008/Android 6.0.1/WW-4.21.40.54 ~ download --> here.
ZF2/ZE551ML/Z00A/Android 6.0.1/WW-4.21.40.61 ~ download --> here.
Click to expand...
Click to collapse
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
fanfan54 said:
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
Click to expand...
Click to collapse
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
muhammed cy said:
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
Click to expand...
Click to collapse
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
help me
fanfan54 said:
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
Click to expand...
Click to collapse
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
iwakpauz said:
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
Click to expand...
Click to collapse
Hello, I already sent it to you by email. Here is the link : https://yadi.sk/d/XAUyR8eRtuKdA
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
ayuinaba said:
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
Click to expand...
Click to collapse
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
timbernot said:
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
Click to expand...
Click to collapse
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
ayuinaba said:
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
Click to expand...
Click to collapse
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
timbernot said:
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
Click to expand...
Click to collapse
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
ayuinaba said:
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
Click to expand...
Click to collapse
Marvelous stuff. ,its been a pleasure helping you
Happy flashing
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
PS, should see the lengths some people go to restore serial
Why ? Lol When it
Only takes 3 mins max this way

LG G4 H815 stuck, download mode only, no adb

Hello hello,
I unlocked bootloader, installed TWRP 2.8.7.0 (adb -> fastboot method) and then I flashed SuperSU 2.46 zip. After reboot from TWRP my phone stuck.
I can't access TWRP or i don't know how to…
System isn't starting BUT sometimes after few minutes of seeing LG logo i see standard wallpaper and suddenly animation freezes. That's all.
When i go to recovery mode (voldown+power, release power and press power again) I can "do" factory reset. I choose 2xYES and i see green android. Then phone is restarting but i should enter to TWRP, right?
I tried to flash stock system (kdz, tot, dz) via:
- LG Flash Tool 2014
- LG Flash Tool 1.8.6.527
- LGUP
- LG Bridge
but nothing…
My phone PID and IMEI is null :/ (and "CUMSS" to :?)
I tried fix that with QPST (2 different versions) but in device manager my phone is only detected as COM port. No "Android Device". I can't read and write anything…
adb isn't working
I tried all USB 2.0 ports, different drivers, roms (even not for 815), dlls.
I fought 3 days and still have brick, not smartphone
I have only download mode working.
I can send commands to com port (Send_Command.exe) but sometimes nothing happen, sometimes i see "fail" after sent command.
Any ideas? Can I install recovery through download mode? Or maybe somebody know how to send files to phone in download mode but without adb?
I had stock rom MM V20L. What else you need to know?
Thanks for any suggestions, sorry for chaos in post and my english.
After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815
2 0 said:
After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815
Click to expand...
Click to collapse
where did you founf v20L kdz i need it because my phone wont flash any kdz i think its to prevent downgrades
https://lg-firmwares.com/lg-h815-firmwares/
Try some from skdubg's link. This is probable the same as mine
PLS Europe PL/Poland H81520l_00_0928.kdz 1.68 G 2016-11-25
Click to expand...
Click to collapse
download-file/?fileId=4325 I can't post links
This is MD5 of my file 8f685baf42869c50ec5f1b7770aa3957 *H81520l_00_0928.kdz
If you still can't flash then i will upload my kdz somewhere. GL
LG G4 Model F500L Stuck on download mode After Downgrade
Hi
i have a problem with my LG G4 Model F500L i try to downgrade from Marsmallow to Lolilpop By Flashing with LGUP Tool when i flash it. it error at 16% boot fail. So i disconnect USB and pull out battery and when i turn on it stuck on download mode.. i have try to flash with any firmware and any LG Tools but it's still fail at writing boot step i had try with Optopus box but it's still fail at wrting boot fail what is the problem . i need help now.... i just bought my phone for a week. Thanks for your helping ....

Flash failed, stuck in download mode (H815)

Hi guys,
for the last months I was using LineageOs, but since they dropped development for our device I wanted to get rid of it.
I tried to get AOSP running but failed. Next I flashed a stock kdz file in Download Mode using LGUP and it worked,
I was back to stock. I tried to install AOSP through TWRP but failed again and eventually ended up doing a hard reset.
This temporarily bricked the device because now the stock android booted and Android Device Protection (FRP) was
active and didn't let me log in. Desperate to find a solution I flashed random kdz/tot files for the device that I found on
the Internet until one finally worked (LGH815 EU Nougat 7.0 BySezerSimsek), the FRP thing was gone. Then I tried to at
least get back to stock again, but when I tried to flash the stock kdz file LGUP aborts at 25% with Error Code 0x2000.
Every time I start the phone now, it goes directly in this firmware update/download mode.
The device shows up as "LGE AndroidNet USB Serial Port" In Windows Device Manager
In Download mode it says "633A B92 Official" on the display
I already tried:
Different dll files for LGUP
Using LG Flash Tool 2014 instead
Putting dump file on SD card
Should I put it in 9008 mode and work with QFIL or what am I supposed to do now?
Thank you.
I'm still able to get into fastboot mode btw. But I'm going to wait for replies here
before I make things worse. If that's even possible at this point. :silly:
h4yabu5a said:
I'm still able to get into fastboot mode btw. But I'm going to wait for replies here
before I make things worse. If that's even possible at this point. :silly:
Click to expand...
Click to collapse
:highfive:<-
jason_l367 said:
:highfive:<-
Click to expand...
Click to collapse
My phone is alive again, thanks Jason:laugh:
Just a short recap what I've done now in case it helps someone with the same problem, the full instructions
are in Jasons link.
I used the KDZ and TOT Extractor to extract the LGUP8994.dll file out of a stock Marshmallow v20p KDZ.
I renamed the dll to LGUP_8994.dll and moved it to C:\..\LG Electronics\LGUP\model\8994, overriding the
existing file. Now LGUP was able to flash the v20p KDZ without the 0x2000 Error.

Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose by Seasee606

I gave up on unlocking the bootloader of my V50 sprint version because I thought it was impossible. Not until I stumbled upon this guide in the LG G8 forum.
I think it is good to have the information in the LG V50 thread also. The thread is owned by Seasee606.
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
good idea !
I ve put this thread in the LG V50 wiki : https://android.fandom.com/wiki/V50_ThinQ ! - everybody is welcome to contribute
I ve just received my korean V50 and I ll try to bootloaderunlock-root it as soon as I ll have the time ...
pierro78 said:
good idea !
I ve put this thread in the LG V50 wiki : https://android.fandom.com/wiki/V50_ThinQ ! - everybody is welcome to contribute
I ve just received my korean V50 and I ll try to bootloaderunlock-root it as soon as I ll have the time ...
Click to expand...
Click to collapse
I don't think it's been confirmed to work on the G8 let alone a single V50
ldeveraux said:
I don't think it's been confirmed to work on the G8 let alone a single V50
Click to expand...
Click to collapse
did you see there are at least 2 custom roms for the V50 ?? then how do you think people bl unlock their V50 ??
pierro78 said:
did you see there are at least 2 custom roms for the V50 ?? then how do you think people bl unlock their V50 ??
Click to expand...
Click to collapse
Did you look at the original G8 thread? People bricking left and right, zero help from the developer who posted the method. I think one guy who says he got it working on a Sprint V50. Have fun bricking your phone!
people on the V50 telegram (founded by the LineageOS dev) seem to be helpful ...
pierro78 said:
people on the V50 telegram (founded by the LineageOS dev) seem to be helpful ...
Click to expand...
Click to collapse
I'm on xda so I don't have to resort to telegram. we've been over this.
I ve just done it on my V500N
took me about 2 hours so not so easy but not impossible
maybe I was lucky ?
couple of difficulties :
* first I could not get into EDL mode but I took the LG USB cable from the box and this worked
* the first time I exited the QFIL partition manager the phone rebooted to EDL mode but was not recognized as "qualcomm device" (there was an unknown usb device in the device manager) ... I just manually rebooted into EDL mode and the phone was recognized as "qualcomm device" this time and I could continue the method without issue ...
(deleted) (see below)
pierro78 said:
nice (and strange !) surprise :
* after bootloader unlock I was supposed to enter "fastboot flash abl_a abl_a.bin" and "fastboot flash abl_b abl_b.bin" but the phone rebooted without issue (telling me first I was bl-unlocked)
Click to expand...
Click to collapse
Oh I had to "fastboot flash abl_a abl_a.bin" and "fastboot flash abl_b abl_b.bin" otherwise my software version would be LM-G850N20z (instead of V500N20z)
I successully unlocked my V50 sprint version. It was fairly easy to do it.
1) To be safe, use the original LG cable. was not successful unlocking the bootloader the first time when I used a generic cable. Even though I was able to enter EDL mode.
2) Make sure to verify that the correct abl_a.bin and abl_b.bin versions are downloaded. The size should be about 1MB.
3) One part in the guide that was not clear was which abl engineering image to flash on a and b partitions. Well, it is the downloaded abl_a.bin that should be flashed in the abl_a and abl_b partitions.
I can see this is very recent which gives me hope, I just bought a v50 (v450vm) on a whim and am wanting to flash twrp and install an aftermarket rom on it. Is there a working version of twrp for this model and has anyone had any success in flashing it? I'm really wanting to the try the new unofficial dotOS version that was recently posted. Thanks in advance for any help/info provided.
I finally got around to rooting my Sprint V50 (LM-V450PM), and I agree that the overall process wasn't difficult. It's just that the guide has little to no explanation for specific models, causing a lot of confusion among users in that thread. It also doesn't help that the guide's OP pretty much posted it, edited it once, and never returned to XDA. And the TWRP installation guide posted by someone else is poorly laid out and has been rightfully criticized by others.
So, here are some pointers from my experience:
- Getting into EDL mode is a bit tricky in getting the timing right, so it may take a few tries to get used to it.
- As has already been mentioned, it's a good idea to use the LG OEM cable to connect the phone to the computer. Some people have been getting a "Sahara fail error" in QFIL that might be due to different cables
- You are backing up the abl and boot partition files for both A and B slots because you don't know yet which slot is active on the phone until you enter fastboot mode, which gets enabled after flashing the modified abl engineering file to replace both abl_a and abl_b partitions.
- For getting root, the newer Magisk versions no longer have a separate Manager APK and ZIP files; they are combined into one APK file now. So, instead of the Manager, you just install the single APK file from the Magisk website. From there, you should be able to patch your boot image file just like it says in the guide.
For TWRP:
- As lallolu mentioned in another post, there are two different versions: One for USA models and one for non-U.S. variants. I'm assuming that the U.S. one is for the Sprint and Verizon V50 while the non-U.S. is for all other types.
- You flash the TWRP ZIP package inside Magisk manually as a module. Note that this will remove root as it tells you on the progress screen when done flashing.
- Since for some reason, the touch screen is not active when entering recovery from a reboot, you need to turn off the phone and then enter recovery via the button combination. Some V50 models appear to have the button combination disabled, and there is a separate guide on here for getting it back, but on the Sprint model, it's still enabled: With the phone off, hold volume-up + power, and when the logo shows up, briefly release the power button while still holding volume-up and then hold power again alongside holding volume-up until the factory reset screen shows up. Answer YES twice, and you will eventually enter TWRP.
- TWRP will greet you with a password, but you just hit cancel to continue and get to the main menu. From there, you'll need to go to Wipe and Format Data (where it will ask you to type "yes") to remove encryption.
- Now you want to get root back by flashing Magisk. All you need to do is rename the Magisk APK file extension to ZIP and flash that in TWRP. Right after that, you should also flash a file called Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip which is also needed to remove encryption.
- Reboot into the system, go through the initial setup, and everything should be set.
For the Verizon model, I'm assuming that the "Enable OEM unlock" switch in the Developer Settings doesn't exist, and so the Verizon FRP image used for the Verizon G8 should also be used. The button combination to enter recovery may also be different. But everything else should be identical to the process for the Sprint model.
C D said:
I finally got around to rooting my Sprint V50 (LM-V450PM), and I agree that the overall process wasn't difficult. It's just that the guide has little to no explanation for specific models, causing a lot of confusion among users in that thread. It also doesn't help that the guide's OP pretty much posted it, edited it once, and never returned to XDA. And the TWRP installation guide posted by someone else is poorly laid out and has been rightfully criticized by others.
So, here are some pointers from my experience:
- Getting into EDL mode is a bit tricky in getting the timing right, so it may take a few tries to get used to it.
- As has already been mentioned, it's a good idea to use the LG OEM cable to connect the phone to the computer. Some people have been getting a "Sahara fail error" in QFIL that might be due to different cables
- You are backing up the abl and boot partition files for both A and B slots because you don't know yet which slot is active on the phone until you enter fastboot mode, which gets enabled after flashing the modified abl engineering file to replace both abl_a and abl_b partitions.
- For getting root, the newer Magisk versions no longer have a separate Manager APK and ZIP files; they are combined into one APK file now. So, instead of the Manager, you just install the single APK file from the Magisk website. From there, you should be able to patch your boot image file just like it says in the guide.
For TWRP:
- As lallolu mentioned in another post, there are two different versions: One for USA models and one for non-U.S. variants. I'm assuming that the U.S. one is for the Sprint and Verizon V50 while the non-U.S. is for all other types.
- You flash the TWRP ZIP package inside Magisk manually. Note that this will remove root as it tells you on the progress screen when done flashing.
- Since for some reason, the touch screen is not active when entering recovery from a reboot, you need to turn off the phone and then enter recovery via the button combination. Some V50 models appear to have the button combination disabled, and there is a separate guide on here for getting it back, but on the Sprint model, it's still enabled: With the phone off, hold volume-up + power, and when the logo shows up, briefly release the power button while still holding volume-up and then hold power again alongside holding volume-up until the factory reset screen shows up. Answer YES twice, and you will eventually enter TWRP.
- TWRP will greet you with a password, but you just hit cancel to continue and get to the main menu. From there, you'll need to go to Wipe and Format Data (where it will ask you to type "yes") to remove encryption.
- Now you want to get root back by flashing Magisk. All you need to do is rename the Magisk APK file extension to ZIP and flash that in TWRP. Right after that, you should also flash a file called Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip which is also needed to remove encryption.
- Reboot into the system, go through the initial setup, and everything should be set.
For the Verizon model, I'm assuming that the "Enable OEM unlock" switch in the Developer Settings doesn't exist, and so the Verizon FRP image used for the Verizon G8 should also be used. Everything else should be identical to the process for the Sprint model.
Click to expand...
Click to collapse
I tried tge volume up+power but twrp don't show up
Khmer_Boy said:
I tried tge volume up+power but twrp don't show up
Click to expand...
Click to collapse
Did you briefly release the power button and then hold it down again? It may take a few tries to get it right if you are not used to doing this. The white factory reset screen will show up if you did it correctly.
I got into the white factory reset screen by doing the volume down+power. What do i do? Select erase or just exit?
Khmer_Boy said:
I got into the white factory reset screen by doing the volume down+power. What do i do? Select erase or just exit?
Click to expand...
Click to collapse
As I mentioned above, you have to answer YES twice. If TWRP is installed, it will go there, and nothing will be erased. If it isn't installed, then the phone will do a factory reset.
C D said:
As I mentioned above, you have to answer YES twice. If TWRP is installed, it will go there, and nothing will be erased. If it isn't installed, then the phone will do a factory reset.
Click to expand...
Click to collapse
Ok. I got into TWRP, but it doesn’t recognize The internal storage. Is there a work around to it?
Khmer_Boy said:
Ok. I got into TWRP, but it doesn’t recognize The internal storage. Is there a work around to it?
Click to expand...
Click to collapse
Did you format data like I mentioned above?
C D said:
Did you format data like I mentioned above?
Click to expand...
Click to collapse
I’m going to give it another try

Fastboot Loop

Hey guys,
I'm currently stuck in a fastboot loop after trying to install Magisk after flashing the Arrow ROM. I believe I messed up when choosing between boot_a and boot_b and flashing the patched img via QFIL. I initally patched boot_a, but when that didn't work I rebooted and patched boot_b. I did this because when I installed Arrow the instructions asked me to select the device slot that was inactive. I thought this meant it was swapping my device slot from A to B, but I probably got that very wrong. I did go into EDL mode and flash my original boot_a and boot_b in hopes it would reverse my mistake, but that did not work.
When I attempt booting the TWRP zip from the lineage guide archive I get this error "failed to load/authenticate boot image". I'm assuming this is because it wants an .img file and not a zip. If I try flashing the same zip file I get this error "Cannot flash this partition in unlocked state".
I did make a backup of all partitions via TWRP before this, but I'm unsure how I'd go about restoring everything. I do have access to EDL mode.
Any help is appreciated. This isn't a primary device though, so if it's bricked I'm not going to be that upset over it. Just something I wanted to try for fun. Haven't rooted a device in years. The G8 was a bit more difficult than I recall, so I'm sure I made a mistake somewhere.
Update 1
I flashed the ABL enginnering file and have some progress. Now fastboot shows my Active A/B Slot. It is set to B now, it was A originally, which I guess confirms that the Arrow OS instructions did switch from A to B. Maybe patching both through Magisk broke the boot image? If I'm understanding this correctly.
Update 2
While in fastboot (Phone was still looping) I entered the following command to change from Active Slot B to A, "fastboot --set-active=a". I've read this could potentially brick your device, but since my device was originally set to A and it was a brick at the moment already I took the risk. Booted into the recovery mode and selected factory reset. It took about five minutes, but I'm now back to the setup screen in the OS. Glad to be back to this point. Now I just need to figure out how to get Magisk Root working without repeating this process.
Update 3
Almost forgot to boot back into EDL, load up QFIL and push the original abl_a and abl_b files back to your phone. Otherwise you won't have any touch input.
Update 4
I seemed to have messed it up again. I tried locking the bootloader back, so I'd stop getting the error message upon bootup. I've decided there is no benefit to unlocking the bootloader and rooting for my purposes. Just wanted to try it out. After doing so I started getting an error stating the device failed security checks, so I pushed the abl engineering file back to the device to unlock it. After I went to push the stock abl_a and b files and decided to go ahead and push the stock boot_a and boot_b to make sure everything was back to normal. Which I didn't think was a big deal, but now I can't boot into the phone without using the abl engineering file.
At the moment I'm unsure what to do. If I push the abl_a and b stock files the phone goes into a fastboot bootloop again. Can't run any commands that way either. I have to boot the abl enginnering file to do so, which in turn allows me to get into the OS but disables touch input. So at the moment I think it's bricked.
If I could find a TWRP image file to flash with the abl enginnering file I could possibly perform a restore from the original backups I made, but I'm unsure where to find one since TWRP doesn't really exist for the G8. I just have a zip file.
Overall not too much of a loss, but the G8 was a great DAP. Hate to lose it. If anyone has any suggestions I'm all ears.
Absolutely the same issue. I wrote about it in arrowOS thread . But I did not try to flash engineering abl. I'm begging you, if your will find solution, please write here about it. I am also notice you here, if resolve this issue.
Jimmynidas said:
Hey guys,
I'm currently stuck in a fastboot loop after trying to install Magisk after flashing the Arrow ROM. I believe I messed up when choosing between boot_a and boot_b and flashing the patched img via QFIL. I initally patched boot_a, but when that didn't work I rebooted and patched boot_b. I did this because when I installed Arrow the instructions asked me to select the device slot that was inactive. I thought this meant it was swapping my device slot from A to B, but I probably got that very wrong. I did go into EDL mode and flash my original boot_a and boot_b in hopes it would reverse my mistake, but that did not work.
When I attempt booting the TWRP zip from the lineage guide archive I get this error "failed to load/authenticate boot image". I'm assuming this is because it wants an .img file and not a zip. If I try flashing the same zip file I get this error "Cannot flash this partition in unlocked state".
I did make a backup of all partitions via TWRP before this, but I'm unsure how I'd go about restoring everything. I do have access to EDL mode.
Any help is appreciated. This isn't a primary device though, so if it's bricked I'm not going to be that upset over it. Just something I wanted to try for fun. Haven't rooted a device in years. The G8 was a bit more difficult than I recall, so I'm sure I made a mistake somewhere.
Update 1
I flashed the ABL enginnering file and have some progress. Now fastboot shows my Active A/B Slot. It is set to B now, it was A originally, which I guess confirms that the Arrow OS instructions did switch from A to B. Maybe patching both through Magisk broke the boot image? If I'm understanding this correctly.
Update 2
While in fastboot (Phone was still looping) I entered the following command to change from Active Slot B to A, "fastboot --set-active=a". I've read this could potentially brick your device, but since my device was originally set to A and it was a brick at the moment already I took the risk. Booted into the recovery mode and selected factory reset. It took about five minutes, but I'm now back to the setup screen in the OS. Glad to be back to this point. Now I just need to figure out how to get Magisk Root working without repeating this process.
Update 3
Almost forgot to boot back into EDL, load up QFIL and push the original abl_a and abl_b files back to your phone. Otherwise you won't have any touch input.
Update 4
I seemed to have messed it up again. I tried locking the bootloader back, so I'd stop getting the error message upon bootup. I've decided there is no benefit to unlocking the bootloader and rooting for my purposes. Just wanted to try it out. After doing so I started getting an error stating the device failed security checks, so I pushed the abl engineering file back to the device to unlock it. After I went to push the stock abl_a and b files and decided to go ahead and push the stock boot_a and boot_b to make sure everything was back to normal. Which I didn't think was a big deal, but now I can't boot into the phone without using the abl engineering file.
At the moment I'm unsure what to do. If I push the abl_a and b stock files the phone goes into a fastboot bootloop again. Can't run any commands that way either. I have to boot the abl enginnering file to do so, which in turn allows me to get into the OS but disables touch input. So at the moment I think it's bricked.
If I could find a TWRP image file to flash with the abl enginnering file I could possibly perform a restore from the original backups I made, but I'm unsure where to find one since TWRP doesn't really exist for the G8. I just have a zip file.
Overall not too much of a loss, but the G8 was a great DAP. Hate to lose it. If anyone has any suggestions I'm all ears.
Click to expand...
Click to collapse
It's a little confusing to try to determine where you are with this, but I can tell you that for the G8, to get twrp 'injected' into the boot partition, you use magisk and flash the zip, you don't 'boot' it.
So to accomplish that, you need **your specific variant** boot partition with magisk injected into it. You can do that yourself by using the magisk manager, or by simply asking if anyone has that available.
But, you'd then have twrp, and you could flash backups, but, from what you say, it's hard to determine if that's going to help.
If you have one of the variants that has the kdz available, I'd suggest simply use LGUP and flash your kdz, and start from scratch.
Lastly, re locking the bootloader. Numerous people make this mistake, but you can't re-lock it unless you're on pure stock (no modifications at all). If you try to re-lock it and yer not on a freshly flashed stock kdz, you can end with 'edl mode only' device.
cheers
AsItLies said:
It's a little confusing to try to determine where you are with this, but I can tell you that for the G8, to get twrp 'injected' into the boot partition, you use magisk and flash the zip, you don't 'boot' it.
So to accomplish that, you need **your specific variant** boot partition with magisk injected into it. You can do that yourself by using the magisk manager, or by simply asking if anyone has that available.
But, you'd then have twrp, and you could flash backups, but, from what you say, it's hard to determine if that's going to help.
If you have one of the variants that has the kdz available, I'd suggest simply use LGUP and flash your kdz, and start from scratch.
Lastly, re locking the bootloader. Numerous people make this mistake, but you can't re-lock it unless you're on pure stock (no modifications at all). If you try to re-lock it and yer not on a freshly flashed stock kdz, you can end with 'edl mode only' device.
cheers
Click to expand...
Click to collapse
As of right now I have a kdz for my phone, I have a Verizon model. Where I'm having trouble with now is I can't get the phone into Download mode. When I do it says my device failed a routine safety check and then boots to fastboot mode.
I also have a couple patched magisk boot partitions from the initial install. I loaded them via QFIL and I can now get to the Verizon bootup screen, but it gets stuck in a loop.
Update:
I got into Download mode by going into the system recovery and doing a factory reset. Now I need to figure out LG UP.
Last Update (Hopefully) Lol:
I installed the kdz using LGUP and it seems to have worked! I'm back in the stock OS and touch input is working. I'm relieved. I hate leaving things like this in a broken state if it's possible to fix it.
Thank you @AsItLies for responding and helping out!
Pukkaras said:
Absolutely the same issue. I wrote about it in arrowOS thread . But I did not try to flash engineering abl. I'm begging you, if your will find solution, please write here about it. I am also notice you here, if resolve this issue.
Click to expand...
Click to collapse
What I did was put the phone back into EDL mode and open QFIL. I loaded my original magisk patched .img file. This got me out of the Fastboot loop. Then after holding volume down and power to reset the phone out of EDL mode I pressed volume down and power again to boot into the modified system recovery. This took a few attempts as it's really finicky.
Once I was in the modified system recovery I performed a factory reset. This seems to have resolved my "Failed routine security check" error when trying to access Download mode. Now that I was no longer getting that error I booted backup into the modified system recovery and hit power down. Make sure your phone is not plugged into your PC at this time or else it will just boot back up.
Once your phone is off and unplugged, hold volume up and then plug the phone back into the PC. Hold volume up until download mode starts. Now you can go go about installing the kdz of your phone.
Now I'm not sure what model your phone is, but since mine was Verizon I found a Verizon KDZ. Then downloaded LGUP. There are a lot of different variations of LGUP, but for my G8 I needed at least 1.16. So I download the Lab version (Probably not right. It scaled very small, but hey, it worked).
You also need to download the DLL for your phone and place it in your Program FIles (x86)/LG Electronics/LG UP/Model/Common folder. I did have to create the Common folder for some reason, but after I did everything worked fine. Make sure to rename the DLL "lgup_common" (without quotes).
You'll also need the LG Drivers for your phone as well, if you haven't installed them already.
I'll post a couple links for you below of where I got this information or files from. I hope this all helps. If you have any questions just let me know. I'm no expert, but I'll do my best to help.
Links:
This link has the DLL, LG Drivers, and a link to LG UP
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch - Firmware Update
www.mylgphones.com
Link to KDZ: https://lg-firmwares.com/lg-lmg820um-firmwares/
If you have ATT or Sprint I do not believe there are KDZs available.
Please let me know if you have any questions or if I need to clarify anything.
Woo, thats great, that you resolve your problem! I will try to do all like in your manual.
imei.guru said, that for my imei i have :
Model: LGABCD
Region: ABC
LG LMG820N
With such region i did not find kdz at lg-firmwares.com
When my smartphone boot up (when it was worked) i see LG U+ when booting.
Also it was trying to set korean language. What do you think, which kdz should I take? And what version of android?
also solved my problems - here i described here how https://forum.xda-developers.com/t/...lg-g8-alphaplus-alphalm.4354847/post-86038237
Jimmynidas said:
What I did was put the phone back into EDL mode and open QFIL. I loaded my original magisk patched .img file. This got me out of the Fastboot loop. Then after holding volume down and power to reset the phone out of EDL mode I pressed volume down and power again to boot into the modified system recovery. This took a few attempts as it's really finicky.
Once I was in the modified system recovery I performed a factory reset. This seems to have resolved my "Failed routine security check" error when trying to access Download mode. Now that I was no longer getting that error I booted backup into the modified system recovery and hit power down. Make sure your phone is not plugged into your PC at this time or else it will just boot back up.
Once your phone is off and unplugged, hold volume up and then plug the phone back into the PC. Hold volume up until download mode starts. Now you can go go about installing the kdz of your phone.
Now I'm not sure what model your phone is, but since mine was Verizon I found a Verizon KDZ. Then downloaded LGUP. There are a lot of different variations of LGUP, but for my G8 I needed at least 1.16. So I download the Lab version (Probably not right. It scaled very small, but hey, it worked).
You also need to download the DLL for your phone and place it in your Program FIles (x86)/LG Electronics/LG UP/Model/Common folder. I did have to create the Common folder for some reason, but after I did everything worked fine. Make sure to rename the DLL "lgup_common" (without quotes).
You'll also need the LG Drivers for your phone as well, if you haven't installed them already.
I'll post a couple links for you below of where I got this information or files from. I hope this all helps. If you have any questions just let me know. I'm no expert, but I'll do my best to help.
Links:
This link has the DLL, LG Drivers, and a link to LG UP
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch - Firmware Update
www.mylgphones.com
Link to KDZ: https://lg-firmwares.com/lg-lmg820um-firmwares/
If you have ATT or Sprint I do not believe there are KDZs available.
Please let me know if you have any questions or if I need to clarify anything.
Click to expand...
Click to collapse
Can you share the LGUP 1.16 that worked for you. The link you provided has LGUP 1.16 [Orignal from LG] – No patched – Lab Version and that does not work or not even opening after installation. Thanks.
indrajyoti_indra said:
Can you share the LGUP 1.16 that worked for you. The link you provided has LGUP 1.16 [Orignal from LG] – No patched – Lab Version and that does not work or not even opening after installation. Thanks.
Click to expand...
Click to collapse
I just tried installing it from scratch and other than it asking for the LG driver it launched on my end. Are you going into your start menu and opening LGUP?
Jimmynidas said:
I just tried installing it from scratch and other than it asking for the LG driver it launched on my end. Are you going into your start menu and opening LGUP?
Click to expand...
Click to collapse
I find out that Windows 11 is the problem. Something to do with stupid driver signature. Used Windows 10 and that worked. Thanks.

Categories

Resources