Develop Bugs

[Q] Trying to downgrade system to unlock bootloader

Hello Everyone. I'm trying to downgrade the software on my Asus Zenfone 2 to version 2.19.40.20 (currently 2.19.40.20) so I can unlock my bootloader. I've heard that the way to do this is following rooting procedure 1 from the main information thread but flashing the version of the files that you want your system to be. However when I download the zip it has the system.img file broken up in some weird way (apparently you need a tool called WinRar to put it back together again but I really don't want to have to go buy a piece of software I'm only gonna need once). Does anyone know how to put the files back together again, have a put together 2.19.40.20 system.img I can use or have some alternative solution to my problem. I'm currently using a Linux system too so if at all possible I would like for any software to be compatible with Linux. If anyone has any insight I would be highly appreciative.

Don't try to flash selectively, as that is very likely to brick your phone. What you want is the correct full ROM package containing a system.img, boot.img/kernel, fastboot (droidboot.img IIRC), IFWI.zip, and some other important partitions whose names escape me. Don't try to extract parts of it (e.g. just the system.img, boot.img, or bootloader), because the components appear to be interdependent. In particular, flashing the wrong version of the bootloader without flashing the corresponding kernel/system image will more than likely brick it. You should be able to supply the full ROM to fastboot (e.g. fastboot update <package_file>). Double check everything and back up before you proceed! @Tuanies should have some pointers for you in case I missed anything, and I would wait to hear from him before you try this.

WinRAR is free. It's a very small program that takes seconds to download and install. It is very simple to put the system image components back together with WinRAR and then you will have that file plus the other three you need. Please try it, I'm sure you'll manage it.

All I suggest is to get the full firmware of 2.19.40.20 and flash the images one by one, and sideload the firmware using adb...
Hope this helps
Good luck.

I'd just download the full package from that's ~1GB and sideload that via recovery in its entirety. If this is too complicated, I'd advise against attempting it.

Seriously it is just about writing 3 lines on adb... Not that hard
Sent from my ASUS_Z008D using Tapatalk

I did finally manage to get WinRar working. I had to go install it on my brother's computer. After I had the files to flash I had no trouble.

This seems like a good place to ask this I was on .22 and tried unlocking boot loader did not seem to work so I went back into my 2.19 folder and flashed back to 2.19 but was still unable to unlock though it appears possibly unlocked on boot loader shows bootloader unk and question marks on last 2 entries, but apparently I am unable to flash over the bootloader in fastboot it says fail cmd err can anyone tell me what that means? And how to get around it, tried flashing non tethered twrp says it wrote it but won't boot to it
Sent from my ASUS_Z00AD using Tapatalk

You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.

robopilot99 said:
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
Click to expand...
Click to collapse
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
Click to expand...
Click to collapse
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great

jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
Click to expand...
Click to collapse
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue. Did you manage to somehow flash the other 3 files?

robopilot99 said:
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue.
Click to expand...
Click to collapse
Yep I figure that might be it, just not sure what to do next, every other file flashes whether I am going up or down thinking of trying to flash older than 19 and then hopefully able to its to 2.19, but hopefully someone knows the proper way
Sent from my ASUS_Z00AD using Tapatalk

The files that I flashed I got from here. Don't know if that's where you are getting yours.

What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.

robopilot99 said:
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
Click to expand...
Click to collapse
I am using the pre rooted ones from shakalaka and i can get boot, recovery and system to flash but unable to get droidboot to flash and that is what I can't figure out even when i downgrade with all the other files i can't get bootloader unlocked

I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.

robopilot99 said:
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
Click to expand...
Click to collapse
They are the same files that you are using from mega.nz and my fastboot knowledge is not great either, so I'll just wait around and see if anyone with more knowledge can help me out, thanks for yoyr help though it's appreciated

@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"

Niropa said:
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Click to expand...
Click to collapse
Thanks Niropa, I knew there was reason this works now I really appreciate the help

Just a quick note to let everyone know that everything worked without a hitch now have unlocked bootloader and twrp installed.
Sent from my ASUS_Z00AD using Tapatalk

Stock recovery (unlocked, US)? Safe N upgrade from rooted M

I flashed the chinese TWRP and rooted a few months back. Now, I want to upgrade to N, and will probably forgo rooting (main reasons I rooted on M was for some N features via xposed).
I was looking for a stock recovery.img for my specific variant, in order to flash that and then OTA, but I haven't had any luck. Then, I thought it might be best to just flash a stock M factory image and then OTA, to be safe, but I can't even find the US unlocked factory image anywhere on moto's site.
Can anyone link me to the right factory image and/or recovery? Thanks!

Ubelsteiner said:
I flashed the chinese TWRP and rooted a few months back. Now, I want to upgrade to N, and will probably forgo rooting (main reasons I rooted on M was for some N features via xposed).
I was looking for a stock recovery.img for my specific variant, in order to flash that and then OTA, but I haven't had any luck. Then, I thought it might be best to just flash a stock M factory image and then OTA, to be safe, but I can't even find the US unlocked factory image anywhere on moto's site.
Can anyone link me to the right factory image and/or recovery? Thanks!
Click to expand...
Click to collapse
There are unsigned images for the RETUS:
https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/
Flashing sparsechunks, boot, recovery, and optionally oem will clear you for an OTA.
---------- Post added at 04:35 PM ---------- Previous post was at 04:31 PM ----------
The partitions they fall under are: system, boot, recovery, and oem respectively (from previous post) when doing your fastboot commands. Be sure to flash the sparsechunks​ consecutively (0 through 10).

DroneDoom said:
There are unsigned images for the RETUS:
https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/
Flashing sparsechunks, boot, recovery, and optionally oem will clear you for an OTA.
---------- Post added at 04:35 PM ---------- Previous post was at 04:31 PM ----------
The partitions they fall under are: system, boot, recovery, and oem respectively (from previous post) when doing your fastboot commands. Be sure to flash the sparsechunks​ consecutively (0 through 10).
Click to expand...
Click to collapse
Thanks! Will give this a try this evening

RETIN New 7.1.1 update error

So took a break from official ROM and went on to Lineage os for sometime which didn't end so well so I went back from that by using: https://forum.xda-developers.com/moto-z-play/development/firmwares-stock-nougat-moto-z-play-t3599838 thread.
Now when I download the update for 7.1.1 phone restarts tries to flash the update but ends up with error and phone restarts stating that the update was unsuccessful.

It happend with me too, I was also try to sideload the 7.1.1 update but it was also failed.
What we can do now anyone please help.

Did you flash the modem? That is what I needed to do.

EspElement said:
Did you flash the modem? That is what I needed to do.
Click to expand...
Click to collapse
Can you please tell me the steps to sideload.
I don't understand what u mean to flash modem.
Please tell me it is very helpful for me..

anujmodi555 said:
Can you please tell me the steps to sideload.
I don't understand what u mean to flash modem.
Please tell me it is very helpful for me..
Click to expand...
Click to collapse
There is a process to backup your EFS which I would recommend first. Let me do some digging and give you the steps.
Here you are:
Make sure you have the right modem for your ROM to flash. What are you on currently?
Then boot into TWRP (not sure if it can be the Chinese one or not) recovery and connect your pc via adb. (in fastboot, type fastboot boot recovery.img < TWRP recovery). Then type the following commands, one line after the other or it could get stuck! (this creates a backup of all the partitions we are going to change to your internal sdcard, just in case):
adb shell
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modem of=/sdcard/NON-HLOS.bin
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modemst2 of=/sdcard/modemst2.img
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/fsg of=/sdcard/fsg.mbn
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/dsp of=/sdcard/adspso.bin
After you are done, reboot into the bootloader and boot into the recovery which is attached below:
fastboot boot recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img (if that doesn't work, just rename the file to recovery.img)
After you changed the language from chinese to english, you can backup your EFS with the recovery.
I then flashed.
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
Key is to stay away from these commands.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img

Thanks
Will I able to install OTA 7.1.1 via twrp recovery...?
I am currently on Android 7.0 April Security patch
CHANNEL - retin
WILL You please explain will I able to flash OTA.zip via sideload..?

EspElement said:
There is a process to backup your EFS which I would recommend first. Let me do some digging and give you the steps.
Here you are:
Make sure you have the right modem for your ROM to flash. What are you on currently?
Then boot into TWRP (not sure if it can be the Chinese one or not) recovery and connect your pc via adb. (in fastboot, type fastboot boot recovery.img < TWRP recovery). Then type the following commands, one line after the other or it could get stuck! (this creates a backup of all the partitions we are going to change to your internal sdcard, just in case):
adb shell
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modem of=/sdcard/NON-HLOS.bin
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/modemst2 of=/sdcard/modemst2.img
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/fsg of=/sdcard/fsg.mbn
dd if=/dev/block/platform/soc/7824900.sdhci/by-name/dsp of=/sdcard/adspso.bin
After you are done, reboot into the bootloader and boot into the recovery which is attached below:
fastboot boot recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img (if that doesn't work, just rename the file to recovery.img)
After you changed the language from chinese to english, you can backup your EFS with the recovery.
I then flashed.
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
Key is to stay away from these commands.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Currently i am on nougat 7.0 which i flashed from the page i mentioned at first post.. I am all on stock.. And i got notification for original 7.1.1 update which on trying to flash gives error.. what modem do i need.. You mean the modem of the rom i currently have?
EDIT: You are legend. Worked like a charm. Thanks alot

Rock_roll said:
Currently i am on nougat 7.0 which i flashed from the page i mentioned at first post.. I am all on stock.. And i got notification for original 7.1.1 update which on trying to flash gives error.. what modem do i need.. You mean the modem of the rom i currently have?
EDIT: You are legend. Worked like a charm. Thanks alot
Click to expand...
Click to collapse
Can you tell me what actually you do please...?
---------- Post added at 06:55 PM ---------- Previous post was at 06:48 PM ----------
After doing all the steps mentioned above what will I do next.
Will I able to install OTA after this ...?

anujmodi555 said:
Can you tell me what actually you do please...?
---------- Post added at 06:55 PM ---------- Previous post was at 06:48 PM ----------
After doing all the steps mentioned above what will I do next.
Will I able to install OTA after this ...?
Click to expand...
Click to collapse
You are on which ROM.. the one I mentioned? You flashed from that topic or you are on untouched official rom

Rock_roll said:
You are on which ROM.. the one I mentioned? You flashed from that topic or you are on untouched official rom
Click to expand...
Click to collapse
I am currently on Android 7.0 retin April Security patch.
I am previously on LOS BUT now on stock 7.0
---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------
anujmodi555 said:
I am currently on Android 7.0 retin April Security patch.
I am previously on LOS BUT now on stock 7.0
Click to expand...
Click to collapse
I have successfully downloaded the Android 7.1.1 OTA but when it is going to install is shows me error and reboot and then it gives me message update is unsuccessful.
When I will try to sideload the OTA package it gives me some "modem" error
---------- Post added at 07:09 PM ---------- Previous post was at 07:06 PM ----------
Can you please tell me the steps you performed for installing the Android 7.1.1 stock OTA successfully.?

anujmodi555 said:
I am currently on Android 7.0 retin April Security patch.
I am previously on LOS BUT now on stock 7.0
---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------
I have successfully downloaded the Android 7.1.1 OTA but when it is going to install is shows me error and reboot and then it gives me message update is unsuccessful.
When I will try to sideload the OTA package it gives me some "modem" error
---------- Post added at 07:09 PM ---------- Previous post was at 07:06 PM ----------
Can you please tell me the steps you performed for installing the Android 7.1.1 stock OTA successfully.?
Click to expand...
Click to collapse
Just flash those files in the sequence he said with those commands..
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
You will find NON-HLOS.bin, fsg.mbn, adspso.bin along with the systemchunk files you downloaded from the post i mentioned in first comment. just flash those and using that command list and download the update and you will not get any error.

Rock_roll said:
Currently i am on nougat 7.0 which i flashed from the page i mentioned at first post.. I am all on stock.. And i got notification for original 7.1.1 update which on trying to flash gives error.. what modem do i need.. You mean the modem of the rom i currently have?
EDIT: You are legend. Worked like a charm. Thanks alot
Click to expand...
Click to collapse
This is awesome!! I am happy for you man!!

[GUIDE] Unbrick your BLN-L24 and other variants after rollback to EMUI 4.1

The process here will work on all variants of 6X but you must use the Huawei Update Extractor Tool to get the necessary images from your devices initial firmware update.app. I have provided the images only for the BLN-L24 variant for which initial firmware is B110. Due to variants having different firmware the BXXX for the rollback might not be the same but the process is
When you attempt to rollback from Nougat/5.0 (B360) to MM/4.1 stock B110 firmware with successful updates using the dload method there is a good chance your phone will be bricked and fail to boot . The first update/downgrade from B360 firmware to B300 will boot the phone but when you do the second update from B300 to B110 firmware the phone will stay on the honor screen. This happened to me and after flashing firmware numerous times and using ADB to flash boot.img the phone was still not working but I was able to recover and get it working again thanks to the Huawei_Multi-Tool_by_Team_MT_v7.1.
Download Images and put them in the Unbrick folder of the Huawei Multi Tool.
System.img
Boot.img
Cust.img
Recovery.img
1. Put phone in fastboot by holding Vol - and connecting usb to computer
2. Unlock bootloader using command fastboot oem unlock xxxxxxxxxxxxxxx where x is your 16 digit unlock code
3. After automatic data reset put phone in fastboot again
4. Start Multi Tool and hit enter to get to main menu
5. Press U for unbrick and hit enter
6. Press 2 and hit enter to start the process
Downgrading from Nougat to MM will relock your bootloader so you must unlock it in order for the multitool to flash the files to unbrick your device. Once unbricked if you relock the bootloader your device will be factory fresh with initial firmware.
Credit to: Team MT for the multi tool and Update Extractor Tool
If this helped you give me a thanks!

No luck for me had to return my phone and get a replacement
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
McRoberts said:
No luck for me had to return my phone and get a replacement
Click to expand...
Click to collapse
At least your method is not just the dload method it does not always work. I know. Thank you. You did great on the method.

McRoberts said:
No luck for me had to return my phone and get a replacement
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
At least your method is not just the dload method it does not always work. I know. Thank you. You did great on the method.
Click to expand...
Click to collapse
Thank you. So you have another 6X now?

Yes I got today so I'm taking my time and reading a lil more. It's such a defeat taking that phone back it's my first real brick.

can i download the recovery img and then flash that using adb to remove twrp and then *try* to restore stock firmware? like.. will my BLN-L24 honor 6x accept that recovery img there?
i used the twrp app to back up my recovery and boot imgs but idk where they were backedup to and where ever they are, if i still have them.. i dont know how to restore them

xSpartacusx said:
can i download the recovery img and then flash that using adb to remove twrp and then *try* to restore stock firmware? like.. will my BLN-L24 honor 6x accept that recovery img there?
i used the twrp app to back up my recovery and boot imgs but idk where they were backedup to and where ever they are, if i still have them.. i dont know how to restore them
Click to expand...
Click to collapse
Look in a folder named TWRP (on your device's storage)

can you repost system.img, it doesn't seem to be available anymore. Thanks.

System. img link is error 404
Hi I wanted to take a shot and see if anyone is still on this thread that may have and is willing to help me out and relink the system.img for the initial release FW for the BLN-L24, any help would be great thanks in advance!

System.img
Boot.img
Cust.img
Recovery.img
Any chance someone has the System.img file and can reupload?
Thanks,
Greg

G4 is Finally Unlocked!

After a year of hard work, @steadfasterX has finally unlocked our device! Hopefully we'll get some new roms soon. Full thread is here: https://forum.xda-developers.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451
Edit: We are currently able to run any custom rom for H811 on our device! One thing is that we must do the modem flash in TWRP that steadfaster mentions in his FAQ.
Edit 2: Currently only stock Lollipop or stock Marshmallow will run on VS986 with everything working. AOSCP and other custom roms will boot but you will not pull the correct APN for Verizon and therefore will have data but no cell service including MMS or voice calls. You must have the stock MM bootloader stack flashed after you go through the UsU process for everything to work correctly and the stock MM modem.

@fates13,
I know you're trying to get Nougat working on your VS986 and it's not 100% working yet.
I suggest people wait until you get things resolved if they rely on their VS986 as their daily phone.
Please post an update here once you think everything is working. The other thread has a lot of posts since it covers other G4 models too.
Thank you

@fates13,
Were you able to get your VS986 to the point of everything worked after UsU unlock and ROM installation?

divineBliss said:
@fates13,
Were you able to get your VS986 to the point of everything worked after UsU unlock and ROM installation?
Click to expand...
Click to collapse
Yes but only stock MM works properly with data and cell. This can probably be fixed by a proper rom developer for our phone. Advanced calling also doesn't work properly so just waiting until @steadfasterX has time to make a UsU patched kernel for stock MM.

fates13 said:
Yes but only stock MM works properly with data and cell. This can probably be fixed by a proper rom developer for our phone. Advanced calling also doesn't work properly so just waiting until @steadfasterX has time to make a UsU patched kernel for stock MM.
Click to expand...
Click to collapse
has anyone got stock MM rooted yet? tried with twrp but I soft bricked it

Was that with UsU on a VS986? How did you try to root it?
ANDROID2468 said:
has anyone got stock MM rooted yet? tried with twrp but I soft bricked it
Click to expand...
Click to collapse

divineBliss said:
Was that with UsU on a VS986? How did you try to root it?
Click to expand...
Click to collapse
yes and I tried rooting with update-superSU.zip

i got stock MM rooted with magisk!!!!

Attempted to root using @steadfasterX's new tool and I was able to do a partial root? My phone would get stuck try to boot the img, however it was able to achieve an unsecured bootloader

wft300001 said:
Attempted to root using @steadfasterX's new tool and I was able to do a partial root? My phone would get stuck try to boot the img, however it was able to achieve an unsecured bootloader
Click to expand...
Click to collapse
just do magisk it worked for me.

ANDROID2468 said:
just do magisk it worked for me and what tool are you talking about?
Click to expand...
Click to collapse
I used SALT, the tool recently released
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
ANDROID2468 said:
just do magisk it worked for me and what tool are you talking about?
Click to expand...
Click to collapse
I used SALT developed by @steadfasterX

wft300001 said:
I used SALT, the tool recently released
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
I used SALT developed by @steadfasterX
Click to expand...
Click to collapse
i sorry I did not read your question right I thought I saw root tool did you get magisk install?

ANDROID2468 said:
i sorry I did not read your question right I thought I saw root tool did you get magisk install?
Click to expand...
Click to collapse
I wasn't able to

Are you able to boot to twrp.
If your still stuck on boot.img go to your salt back ups is located in the home folder and right click in the folder and click open in terminal put your phone in fastboot mode type in terminal "fastboot flash boot boot.img" and after that "fastboot reboot" and see if your phone boots up if you don't have the salt backup let me know

ANDROID2468 said:
Are you able to boot to twrp.
If your still stuck on boot.img go to your salt back ups is located in the home folder and right click in the folder and click open in terminal put your phone in fastboot mode type in terminal "fastboot flash boot boot.img" and after that "fastboot reboot" and see if your phone boots up if you don't have the salt backup let me know
Click to expand...
Click to collapse
How exactly did you install TWRP? Or if you solely used magisk, how did you flash the patched_boot.img?

I was asking you about TWRP to see if you installed it. You flash all the files in fastboot. You get into fastboot by unplugging the battery wait 4 seconds plug it back in hold volume down and plug your phone in to your computer you should be in fastboot mode. You can download TWRP from the unlock Page. I will upload the pach boot.img and paste the link for TWRP later because I'm not at my computer right now. Be careful NOT to flash the aboot.img you should only flash the boot.img (once I upload it) and the recovery.img right now
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
Tros13 said:
How exactly did you install TWRP? Or if you solely used magisk, how did you flash the patched_boot.img?
Click to expand...
Click to collapse
And if you are still confused I will make a video on how to root later

ANDROID2468 said:
I was asking you about TWRP to see if you installed it. You flash all the files in fastboot. You get into fastboot by unplugging the battery wait 4 seconds plug it back in hold volume down and plug your phone in to your computer you should be in fastboot mode. You can download TWRP from the unlock Page. I will upload the pach boot.img and paste the link for TWRP later because I'm not at my computer right now. Be careful NOT to flash the aboot.img you should only flash the boot.img (once I upload it) and the recovery.img right now
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
And if you are still confused I will make a video on how to root later
Click to expand...
Click to collapse
Ah, different person than you were talking to before. The way I read your post, it sounded like maybe you figured out a way to sideload (if that is the correct term) the patched boot image that magisk makes without the part of the UsU method that causes "Once you go this way - there is no way back! SERIOUSLY. The only way to make the device exactly like before is replacing the mainboard. If you're scared: good." Maybe something like this: ?
https://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Was just looking into my options for if I should wait until a method comes out that doesn't make a permanent alteration or if I should just go ahead and take the plunge with UsU. Your thoughts on whether that change that is made could affect me badly in the long run?

Tros13 said:
Ah, different person than you were talking to before. The way I read your post, it sounded like maybe you figured out a way to sideload (if that is the correct term) the patched boot image that magisk makes without the part of the UsU method that causes "Once you go this way - there is no way back! SERIOUSLY. The only way to make the device exactly like before is replacing the mainboard. If you're scared: good." Maybe something like this: ?
https://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Was just looking into my options for if I should wait until a method comes out that doesn't make a permanent alteration or if I should just go ahead and take the plunge with UsU. Your thoughts on whether that change that is made could affect me badly in the long run?
Click to expand...
Click to collapse
sorry about that the only way to root the latest FW is to unlock the bootloader. as long as you flow the guide and read carefully you shud be fine and if it's too scary just downgraded to LP and root that way (look on xda Verizon G4 general tab)

Has any one got calling and texting working on any costum rom for vs986?

Probably a dumb question, but I'm on 13b rooted. I read through the unlock thread and it mentions MM is required and anti rollback <=2. My ARB value is currently 2. Can I just use LGUP to flash stock MM? Will this preserve my ARB value?