Related
This is viewable as a Evernote link with clickable links, and easier text.
https://www.evernote.com/shard/s372/nl/65123625/8cbdf422-6334-4a18-86d3-b0ac271d6987?title=Fix%20Phone
Note- this is a ID-10 error from not correctly folling the steps of Bump
from this tutorial
http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
I should not have used Flashify to flash
twrp-2.8.0.0_d850-signed.img from
http://downloads.codefi.re/thecubed/lg_g3/bump/
as boot This let's me load TWRP {which was not installed before}
this caused the Operating system to vanish.
the phone boots directly into TWRP
phone details
http://www.att.com/cellphones/lg/g3.html
AT&T LG G3 Stock
Rooted with Stump {this worked and i went many moons rooted Thanks guys!}
AT &T D850 AATT D85010D 00_3 2014/07/04
{details from http://www.mylgphones.com/lg-g3-firmware-checking-the-software-version-and-update-history }
i am on a linux computer
ADB was installed by following this guide
http://forum.xda-developers.com/showthread.php?t=1907796
Adb works, and recognizes phone.
Step 7. Create path for ADB
did not work.
all commands require ./
I have downloaded the stock version
BIN_LGD850AT-01-V10d-310-410-JUN-19-2014-0.zip
from
http://downloadandroidfiles.org/directory.php?Directory=/LG G3/Stock Files/ATT D850
it is sitting in Downloads of computer.
I turned phone OFF at 98% battery.
it has no backup.
so, my question How do i get the phone back to stock?
i think I could pull the recovery downloaded onto SD card, flash it and be golden. However I would like some
input before my phone goes kaput.
so how about it guys? what should I do?
More prep
I found this guide for Windows
http://forum.xda-developers.com/showthread.php?t=2772199
These firmware files
http://downloads.codefi.re/wolfgart/LG_G3/D850
and downloaded
BIN_LGD850AT-01-V10d-310-410-JUN-19-2014-0.zip
BIN_LGD850AT-01-V10d-310-410-JUN-19-2014-0.zip
D850_SVC_ENG_V0.9_140707.pdf
I flashed twrp through flashify on my d850 and it worked fine
2SHAYNEZ
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
#RESERVED2
Make sure you have enough space on internal storage before flashing the backup zip. You'll likely need 10GB+. this new zip now checks free storage on internal and aborts if not enough. it also now creates a flashable restore zip so now youll have the restore zip internal storage/dump/backup.zip and you can flash this zip when you get a non 9008 brick
Dumps can be done with aosp or custom roms but please try to backup only stock roms if possible. Thanks Everyone!
EDIT: NEW ZIP HAS BEEN ATTACHED.
#RESERVED3
#RESERVED4
I'll be releasing the flashable zip to dump your partitions later today!
Added a flashable backup zip. please flash in twrp and then upload Backup.zip from internal storage Dump folder somewhere and send link here. ill make a restore zip so we can make the v30 almost unbrickable :good:
LG V30 bricked
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
sicci75 said:
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
Click to expand...
Click to collapse
Your mistake was not following any of the rooting Instructions in this V30 forum. If you did, you know we don't use SuperSu, we use Magisk. That's probably what messed up your phone.
I understand you obtained an "official" bootloader unlock code from LG for your H930 -- which is not necessary now for almost a year with the WTF exploit -- but you still need to follow the rooting instructions guide.
The unlocked bootloader warning screen is normal. Ignore it, it's just a harmless annoyance. You would have learned that if you read the instructions.
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
If/when you recover, your bootloader should still be unlocked, but you'll have install TWRP again and this time use Magisk. Read the WTF instructions, but you can skip the bootloader part, as you've already done that. You can start with Section 6. Read those instructions on a web browser, not an app.
ChazzMatt said:
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
Click to expand...
Click to collapse
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
sicci75 said:
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
Click to expand...
Click to collapse
Are you able to get into Download mode?
You want the "patched" version, but be sure to read the installation instructions.
Yes, you can use that KDZ.
If for some reason your bootloader is not still unlocked, you can run your code again.
ChazzMatt said:
Are you able to get into Download mode?
Click to expand...
Click to collapse
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
sicci75 said:
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
Click to expand...
Click to collapse
Glad to help.
Sent via open market LG US998 V30/V30+
So just uploaded a new zip in post 3. this new zip now checks for free space and will abort if theres not enough to create the backup and flashable restore zip. need at least 10GB in Internal Storage. the zip will now create automatically a flashable restore zip :good: i designed this around the v30 but in theory it should be able to work on all qualcomm devices and maybe even some other SoCs as well. but this has not been tested on other devices. ive fully tested this on my ls998 and everything works great! Enjoy!
john, did i ever tell you, that i like your work and efforts? good man! :good:
Lg v30 h932 brick
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 03:26 AM ---------- Previous post was at 03:23 AM ----------
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
It was a big mistake and I don't know what to do, my phone does nothing, totally dead
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 04:04 AM ---------- Previous post was at 03:26 AM ----------
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?!!!
JohnFawkes said:
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
robertojha said:
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
Click to expand...
Click to collapse
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Lg v30 h932 brick
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
From what I know, there is no fire hose for the H932.
Sent from my LG-H932 using XDA Labs
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
robertojha said:
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
Click to expand...
Click to collapse
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
From what I know, there is no fire hose for the H932.
Click to expand...
Click to collapse
Ah, yeah you're right.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
BROKEN1981 said:
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Click to expand...
Click to collapse
The T-Mobile root guide does say flash the LAF partition of the H933. But only the LAF partition. Some people do not pay attention and flash the entire H933 kdz over the T-Mobile H932 and brick their phone.
Just had a guy in the Frankenstein thread who said he followed instructions. I didn't believe, told him so, and asked him to tell me step-by-step what he did... Turns out rather than flash US998 Nougat, then Master Reset, then Oreo of choice -- he flashed 20f (Oreo), Master Reset, 20g Oreo.
I asked him why he did that. He said US998 20f was Nougat. That's like saying a banana is an apple. "10" is Nougat, "20" is Oreo. Plus, in my instructions I have specific download links to all requisite firmware, which he ignored.
He said he downloaded KDZ from LG-Firmwares website who told him US998 20f was Nougat -- which they didn't. But even if they did, who cares? You're following MY instructions, so use my download links. Once he downloaded actual Nougat from my download link -- hey that worked!
Also use the Dev Patched LGUP which I recommend. Some guy over the telegram thread said he was following my instructions, but used Uppercut. Of course that's going to fail. None of my instruction mention Uppercut and never will because it doesn't work on Oreo or later and conflicts with Dev Patched LGUP. I always include the specific version of Dev Patched LGUP you should be using. (The Dev for Uppercut is amazing, but it just doesn't work on our phones past Nougat. If it's NOT in the Instructions, don't use it.)
This isn't a recipe where you can substitute your own ingredients.
You need to read carefully and pay attention.
I'm happy to help -- but while some people's problems are quite preventable, once occurred may not be fixable.
I bought a LG V35 recently. When I got the phone, I found its rooted already and looks like bootloader is unlocked since the 1st screen shows the warning unlocked messages. See attachments.
After I got into the system, I could see magisk and used root permission without any problem.
I wanted to do a system backup in the customer recovery like twrp or CWM. (I thought it should be there, since phone is rooted) But after I clicked "reboot to recovery" with TaiBackup APP, I could not get into recovery and screen shows "erasing data" and then rebooted. When system was started up again, phone was done a factory reset and magisk did not work any more...(I checked, I still can see the unlocked bootloader messages at that time)
Then I had to send my phone to the seller and got rooted again. I really do not understand how the seller rooted this phone!!
Now I am wondering if I can flash any custom recovery like twrp? I do not see LG V35 in official twrp's support device list. Dare I try the twrp for LG G7 or LG V30 or others?
If I have to try twrp for LG G7, is there anybody knows how to do a recovery backup via ADB beforehand? Anything I can do to minimize the risk?
He probably dumped the boot image with LGUP, and manually patched it with Magisk on another device
crumbling9999 said:
He probably dumped the boot image with LGUP, and manually patched it with Magisk on another device
Click to expand...
Click to collapse
Yes, I searched with google about patching magisk boot img and now I agree with you.
Now, when I trying to install some modules in magisk, I will get "installation failed". See the attachment.
I googled and tried to find the solution. It is said that I could update/re-install the magisk manager apk to solve the problem. But the seller told me DO NOT touch the magisk and even update it.
Do you know if I can update the magisk manager when rooted in the patching boot img way?
Do you know if I can install xposed in the magisk in this case?
Are there some DONTs when rooted in the patching boot img way?
Thanks for your reply.
Mate just start first with a backup via LGUP than check if you can reboot to bootloader. Then read a bit G7 thread and if you are confident in your knowledge and skills continue - it is an easy job to firstly backup your both boot mages, patch them and flash them back to your phone if you have fastboot.
vlad48 said:
Mate just start first with a backup via LGUP than check if you can reboot to bootloader. Then read a bit G7 thread and if you are confident in your knowledge and skills continue - it is an easy job to firstly backup your both boot mages, patch them and flash them back to your phone if you have fastboot.
Click to expand...
Click to collapse
Please tell me how to backup both boot images? Thx
alex.coffen said:
Yes, I searched with google about patching magisk boot img and now I agree with you.
Now, when I trying to install some modules in magisk, I will get "installation failed". See the attachment.
I googled and tried to find the solution. It is said that I could update/re-install the magisk manager apk to solve the problem. But the seller told me DO NOT touch the magisk and even update it.
Do you know if I can update the magisk manager when rooted in the patching boot img way?
Do you know if I can install xposed in the magisk in this case?
Are there some DONTs when rooted in the patching boot img way?
Thanks for your reply.
Click to expand...
Click to collapse
Is there somebody can tell me how to solve the issue that i can not install any module in magisk?
Can i update the magisk framework to 18.1 when the root method is coming from the patching boot image?
Since you have full fastboot, grab a copy of TWRP for the G7 and try booting it. I verified today that laf from the G7 boots just fine on the V35, so TWRP should work until (yes I am being optimistic here) I can get the V35 rooted and build our own TWRP.
In case you are new, the command will be:
Code:
fastboot boot twrp.img
Where twrp.img is whatever the filename of TWRP is. If the touch screen works, and the rest of the functionality is there, you can use that for now. However, you will have to have a PC and fastboot boot it every time you want to get into TWRP.
On SD845 and later devices (which the G7 and V35 have), recovery is no longer a separate partition -- it is included in boot. So, you do NOT want to flash the G7 version because while the G7 kernel may work fine for laf, and TWRP, it probably wouldn't be ideal to use as a system kernel.
Let me know if you have any questions.
I do have a question for you. Where did you get your phone from? I have a hard time believing that there are so many V35s out there with engineering bootloaders -- so I would like to get my hands on one and figure out how they unlocked the bootloader.
-- Brian
runningnak3d said:
Since you have full fastboot, grab a copy of TWRP for the G7 and try booting it. I verified today that laf from the G7 boots just fine on the V35, so TWRP should work until (yes I am being optimistic here) I can get the V35 rooted and build our own TWRP.
In case you are new, the command will be:
Code:
fastboot boot twrp.img
Where twrp.img is whatever the filename of TWRP is. If the touch screen works, and the rest of the functionality is there, you can use that for now. However, you will have to have a PC and fastboot boot it every time you want to get into TWRP.
On SD845 and later devices (which the G7 and V35 have), recovery is no longer a separate partition -- it is included in boot. So, you do NOT want to flash the G7 version because while the G7 kernel may work fine for laf, and TWRP, it probably wouldn't be ideal to use as a system kernel.
Let me know if you have any questions.
I do have a question for you. Where did you get your phone from? I have a hard time believing that there are so many V35s out there with engineering bootloaders -- so I would like to get my hands on one and figure out how they unlocked the bootloader.
-- Brian
Click to expand...
Click to collapse
Thanks for your answers.
I bought this phone from taobao which is a bigest famous online shopping site in China. I do not know how they unlocked the bootloader and tell me if something I can help with.
I unlocked LG G2/G4/oneplus 5T myself so I know the basic knowledges about how to execute ADB command and the normal root process. But I do not know the one using patched magisk boot img way.
As far as I understand, you meant that we can temporarily boot into the G7 twrp to use its functions but we cannot actually flash the twrp to the phone. Booting to G7 twrp image, is it safe? (The "safe" I mean is that, if I encounter problems, at least I still can startup the phone with rooted. Otherwise, I need to send my phone to the seller who is 2000KM away to root it again...Last time I booted into its recovery, all my data was erased...) Anyway, I will try it as you suggested, but I will put it the 2nd priority.
The 1st priority is that, I truely want to solve the problem I met about installing magisk module failed. See my attachment. I want to know if I can fix the problem by updating the magisk framework. I need the "safe" way as I just said.
So if I click "yes" in the 33.jpg I attached, do you know which would happen?
A. brick the phone
B. restart and get a factory reset, then I cannot use root any more
C. nothing changed, still install module failed but root can work
D. Solve the problem and can install module successfully
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
vlad48 said:
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
Click to expand...
Click to collapse
Thanks for explaining. That is what I worry about. Some questions for you:
1. I have used LGUP to dump boot_a and boot_b. (Very slow, took 1 hour. I renamed them to boot_a_org.img and boot_b_org.img, they are no difference with cksum). So this is currently boot images patched by seller? So, no matter what problems I encounter, I can flash boot_a_org.img(boot_b_org.img) back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
2. You mentioned "Patch it via Magisk Manager". I can directly patch boot_a_org.img to do it? I think boot_a_org.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
3. "Patch it via Magisk Manager". can only be done in my V35 phone, or it is OK to do it in other phones?
4. Can I try to boot into G7 twrp then I can flash the newest magisk via twrp? In this way I can fix my problem?
Thank you very much in advance.
1. Download LGUP from HERE
(make sure you put it in the right place afterwards: C:\Program Files (x86)\LG Electronics\LGUP)
2. Shut down your phone and then press VOL+ button and connect it via USB cable to your computer (The phone will boot in download mode).
3. Start LGUP.exe and select DUMP mode. DUMP only those partitions (place checkbox):
abl_a
abl_b
boot_a
boot_b
xbl_a
xbl_b
This will finish our backup preparation, so report back once done.
(Also just come to a better idea - compress and upload somewhere your boot_a file I'll try to patch it with latest Magisk and upload it back to you)
vlad48 said:
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
Click to expand...
Click to collapse
Laf has new security that prevents reading for now. LG UP 1.14 and 1.15 can't read .. and I can't find a copy of 1.16.
-- Brian
@runningnak3d maybe you are mixing V40 with V35. Using this DUMP only version of LGUP bootloader unlocked phones are able to dump all (even non kdz partitions) so he will be able to perform this operation.
vlad48 said:
@runningnak3d maybe you are mixing V40 with V35. Using this DUMP only version of LGUP bootloader unlocked phones are able to dump all (even non kdz partitions) so he will be able to perform this operation.
Click to expand...
Click to collapse
This only works for v35 phones with unlocked bootloader?
Yes, I have already dumped those part:
abl_a
abl_b
boot_a ============> I rename this one to boot.img
boot_b
xbl_a
xbl_b
Could you teach me what is each one used for?
So boot.img is currently boot image patched by seller? So, no matter what problems I encounter, I can flash boot.img back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
You mentioned "Patch it via Magisk Manager". I can directly patch boot.img to do it? I think boot.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
alex.coffen said:
Yes, I have already dumped those part:
abl_a
abl_b
boot_a ============> I rename this one to boot.img
boot_b
xbl_a
xbl_b
Could you teach me what is each one used for?
So boot.img is currently boot image patched by seller? So, no matter what problems I encounter, I can flash boot.img back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
You mentioned "Patch it via Magisk Manager". I can directly patch boot.img to do it? I think boot.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
Click to expand...
Click to collapse
The files I dumped from LGUP are bin file or img file?
I try to patch the boot.img file but everytime I get error. See attachment.
@alex.coffen Yes if you backup your boot image and do not boot into RECOVERY everything will be safe.
It appears your DUMP was not done properly. Please if possible open your boot.img with HEX editor and take a look at it - if there are only 0-es there than it appears something is wrong with your dump.
vlad48 said:
@alex.coffen Yes if you backup your boot image and do not boot into RECOVERY everything will be safe.
It appears your DUMP was not done properly. Please if possible open your boot.img with HEX editor and take a look at it - if there are only 0-es there than it appears something is wrong with your dump.
Click to expand...
Click to collapse
Yes, all 0-es. What should I do? I have already re-installed the USB dirver 4.2.0. See attachment.
Since I failed to use LGUP dump boot img, I think about another way.
I installed termintor on my phone. Under directory /dev/block/bootdevice/by-name, I execute "ls -l" then I can find all partitions, for one example:
boot_a -> /dev/block/sde11
In this case, do you know if I can use "dd if=/dev/block/sde11 of=/storage/emulated/0/Download/boot_a.img" to get the boot img?
@runningnak3d, @vlad48
Since I failed to use LGUP to dump boot img, I think about another way.
I installed termintor on my phone. Under directory /dev/block/bootdevice/by-name, I execute "ls -l" then I can find all partitions, for one example:
boot_a -> /dev/block/sde11
In this case, do you know if I can use "dd if=/dev/block/sde11 of=/storage/emulated/0/Download/boot_a.img" to get the boot img?
@runningnak3d, @vlad48
Hi there, sorry for my bad English!.
I had a small LG G3 f460L working fine untill today i decision root my device. I just in android 6.0 base, coz my app(apk) i needed only run in android 6.0 or higher because of that i dont downadge my phone to lower base. I try kingroot, kingoroot, ioroot... etc but nothing work. Because my phone dont have stock recovery( nẻver mind), i was try flash LAF and RECOVERY partion by LGUP patched! all done, my phone got brick, i start normally but can't boot to download mode and recovery both. So, i think there is no way to flash other rom with this situation, i got a big decision: brick my phone. in this moment i try kingoroot again, and wow,. It's worrking, my phone is rooted. But, i can flash anything because my recovery partion got error. 2nd i got big decison. BRICK MY PHONE to got 9008 QHSloader. I succeeded with that intention. But, GOD pls/ My phone is not in list supportted by Boarddiag chipset and other tools. My chipset is APQ8084.
Have anyone here can give me a model APQ8084 support file or other way to save my phone. ! Thanks you so much!:crying:
About your recovery problem you could try and install this:
https://forum.xda-developers.com/lg...460-recovery-unofficial-twrp-3-0-0-0-t3330573
As for your laf partition problem if you have a backup of this partition you can flash it back like this (assuming this is on the root of your sdcard path):
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
If you don't have a backup of your laf partition I am afraid you have to apply a much harder solution.
Download the same firmware as the one you have installed on your device and extract the laf partition from there.(If you bother to download a whole kdz or tot you could also extract your stock recovery too in case you don't have a backup and you need it).
Here you could find your stock firmware:
https://lg-firmwares.com/lg-f460l-firmwares/
Also here you will find the tool and the instructions to extract it:
httQHSloaderm.xda-developers.com/showthread.php?t=2600575
I hope I helped you.
Sorry man! I forgot the part "9008 QHSloader".So if you don't have access to your rom any more you are probably screwed!?
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.