Database Develop

[ROOT] EU LMV405EBW - Magisk

I couldn't find any guide for rooting the V40, so I thought I'd write down the steps I took to root my new EUR V40 - LMV405EBW. Maybe it will help others. Sorry if this is somewhat confusing, I didn't have time to make a polished version. It's basically made from my notes during the process with the commands copied from bash history.
-First, unlock the bootloader following LG's instructions here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
There's no TWRP for the V40 and the one made for G7 doesn't work. I don't have the time and knowledge to even attempt to compile TWRP for the V40, so I proceeded with just patching an original boot image with Magisk.
You can get the patched boot images that I used from here:
Oreo 10e: boot_a_magisk_patched_10e.img
Oreo 20f: boot_a_magisk_patched_10f.img
Pie 20a: boot_a_magisk_patched_20a.img
Pie 20b: boot_a_magisk_patched_20b.img
Pie 20f: boot_a_magisk_patched_20f.img
Pie 20g: boot_a_magisk_patched_20g.img
Q 30b: boot_a_magisk_patched_30b.img (this requires flashing to the active boot partition).
Q 30c: boot_a_magisk_patched_30c.img (this requires flashing to the active boot partition)
Q 30d: boot_a_magisk_patched_30d.image (this may or may not work with "fastboot boot" and could require flashing to the active boot partition. I haven't tested if live boot still works. I just did fastboot flash boot_x img_file).
You can try to boot it with with fastboot if you have a LNV405EBW and skip the KDZ extraction part.
Installing Magisk:
Flashing this image isn't necessary, just straight boot should be sufficient and safe.
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
Code:
adb reboot bootloader
fastboot boot boot_a_magisk_patched_10e.img
After the phone boots the OS with the external boot image, open Magisk Manager and tap on Install. Select the option to Direct install to the active slot. I played it safe and decided to NOT flash also on the inactive slot. I've left it alone so I can use it in case of need of recovery.
You'll probably notice that you don't have a connection to the carrier. Just ignore it, it will back once the phone is booted normally.
Reboot and you will have permanent root until you switch the A/B slots.
In case my patched boot image doesn't work, you can just make your own.
Tools needed:
Magisk Manager 7.0.0 installed on the phone
LG Bridge installed on a Windows machine.
a Linux machine or VM (I used the latest ubuntu desktop), python3 with the zstandard module installed and kdztools from steadfasterX's repo. Maybe kdztools would work on Windows too, I haven't tried it.
adb, fastboot
You need to procure an original ROM file for your phone model. It can be downloaded easily with LG Bridge. Just connect the phone to a Windows PC, start LG bridge, go to the Software update tab and click on Update error recovery. Wait for the download to start and disconnect the phone. Ignore LG Bridge complains about not being able to flash after the downloading stage is completed. Don't click anything in Bridge and before closing it go to C:\Users\<your_username>\AppData\Local\LG Electronics\LG Bridge\SWUpgrade and copy your KDZ somewhere else. Preferably send it to the Linux VM to the LG work folder, it'll be needed there.
On Linux open a terminal:
Code:
cd ~/Documents
mkdir LG
cd LG
git clone https://github.com/steadfasterX/kdztools.git
cd kdztools
nano undz.py -c
For kdztools to be able to extract the V40 images, I needed to edit undz.py and comment the lines 88-90. So, this block should all be commented or undz will fail to extract the boot partitions.
Code:
#if len(dz_item['pad']) != 0:
# print("[!] Error: pad is not empty", file=sys.stderr)
# sys.exit(1)
To extract, with the KDZ copied to ~/Documents/LG/
Code:
cd ~/Documents/LG/kdztools
./unkdz.py -f ../V405EBW10e_00_OPEN_EU_DS_OP_0109.kdz -x
cd kdzextracted/
List the partitions contents and look for the IDs of boot_a and/or boot_b. In my case they were 44 for boot_a and 63 for boot_b
Code:
../undz.py -f V40510e_00.dz -l
Extract boot_a or boot_b or both, they're identical:
Code:
../undz.py -f V40510e_00.dz -s 44
../undz.py -f V40510e_00.dz -s 63
You can find the extracted boot images in the dzextracted subfolder. Get boot_a.image or boot_b.image or both from there and send them to the phone in a location accessible by Magisk Manager. The Download folder should do fine.
Open Magisk Manager and tap Install, select Patch Boot Image file and patch the image file(s) you extracted. Get the patched_boot.img that Magisk Manager saves in the Download folder and send it to a PC where you have adb and fastboot.
Go to the beginning of the post to the Installing Magisk section.

Damned tempting, but I'll wait until after Pie drops.
Sent from my LM-V405 using Tapatalk

Glad to see this, hopefully it's a start for all of us.

If anything, at least a way to unlock the bootloader via legitimate channels! Gonna be generating that string, next chance I get, to be ready.
Sent from my LM-V405 using Tapatalk

Once runningnak3d gets a hold of this, we should be good with the v40. Cool beans.

Hey do the unlock codes online work for $ 12-15 on sprint? I used to flash phones back in the day and got a great deal on a bad IMEI sprint lg v40, but so far I can see there isn’t a way yet. On top off all that I m in Europe and don’t want to get the error message that I m out of the Region. I would have to go to USA just to unlock the phone.

@runningnak3d

Can't I install the firmware on a different device?

V version can not unlock BL, so envious

Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)

LameMonster82 said:
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
Click to expand...
Click to collapse
Or I could find you stupid for not noticing the patched image is in my first post.

DLS123 said:
I find you stupid for not noticing the patched images are in my first post.
Click to expand...
Click to collapse
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.

LameMonster82 said:
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
Click to expand...
Click to collapse
I mentioned in the description 1 line below the link that it's for 10e. There was no other update in a long time. I don't think there can be any confusion for now. I can edit and label the file when there's will be another fw update.

It looks like unlocking the bootloader breaks Widevine L1 on the V40 and downgrades is to L3. No more HD or UHD Netflix.
I couldn't find any other solution than to re-lock the bootloader to restore L1.
This doesn't happen on the V30.

@DLS123
Thank you for all!
I ask you for more details; i'm stuck at flashing first image in adb; it returns an error; have LMV405EBW with 10f. unlocked bootloader of course
Thx again for your support!

@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.

DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
i suppose is something wrong in this instructions.

daphix said:
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
Anyway; understand now what to do;
Steps are below:
- first install magisk manager
- download magisk zip from magisk site or from magisk manager himself on phone
- download patched_boot_a.img to phone from our good contributor
- use magisk manager and select inslall image of patched_boot_a.img from phone
- magisk manager will generate a magisk patched image
- transfer this magisk patched image (not patched_boot_a.img) to pc in ADB folder
- flash with Adb this magisk patched image from pc to phone.
Thx to our friend!
---------- Post added at 09:53 AM ---------- Previous post was at 09:21 AM ----------
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Hi;
using Magisk mamanger and your file was generated a file: magisk_patched.img
pls support; trying to flash that image from PC with adb not work:
fastboot flash partition_a magisk_patched.img
Click to expand...
Click to collapse

@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.

DLS123 said:
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
Click to expand...
Click to collapse
Hi , thank you for reply;
I tried many combinations of your commands;
maybe due that am noob, but succesion below simply is not working:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img

[Guide] Magisk Modules Disabler for booting into Magisk core-only Mode

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking img
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work.
1. Same as above but use the overlay.dcoreonly1.zip
2. You will boot with root but modules disabled. Once the bad module is removed, delete the .disable_magisk file in your /cache folder. Dot files are hidden files so if your root explorer can't see hidden files, run the bat file in ADB.
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
***************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode, in case you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-newpixel4.img
You will boot with root but modules disabled. Once the bad module is removed, delete the .disable_magisk file in your /cache folder. Dot files are hidden files so if your root explorer can't see hidden files, run the bat file in ADB.
(You must have root so if you don't, flash your magisk_patched.img and reboot first)
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
Boot Image core-only uploaded 6-17-20
https://www.androidfilehost.com/?fid=4349826312261824031
Boot image Remove Magisk 6-17-20
https://www.androidfilehost.com/?fid=8889791610682872348

Is this for 007 or 011? Thanks for this! I see you're active in xl, but glad you're helping us with the straight 4.
Could have used this, flashed the active edge mod twice and had to re-setup

dubt17 said:
Is this for 007 or 011? Thanks for this! I see you're active in xl, but glad you're helping us with the straight 4.
Could have used this, flashed the active edge mod twice and had to re-setup
Click to expand...
Click to collapse
I would think it would work with either. The 4 and 4 XL might even share boot.img but you are just booting it anyway.

Thanks for your help! I believe lots of people will benefit from your img before TWRP comes out!

Thanks for this one... definitely a must have in the toolbox.

I got bootloop after installing edxposed
I have installed magisk canary, and gpay sql fix
Stuck on booltoop, even after fastboot with this image

spahi4 said:
I got bootloop after installing edxposed
I have installed magisk canary, and gpay sql fix
Stuck on booltoop, even after fastboot with this image
Click to expand...
Click to collapse
Try this one. Made with latest magisk.
https://www.androidfilehost.com/?fid=4349826312261639511

Tulsadiver said:
Try this one. Made with latest magisk.
https://www.androidfilehost.com/?fid=4349826312261639511
Click to expand...
Click to collapse
Any idea what im doing wrong?
PS C:\Users\Sam\Downloads> fastboot boot "C:\Users\Sam\Downloads\image-newpixel4 (1).img"
downloading 'boot.img'...
OKAY [ 1.173s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.795s

1dopewrx05 said:
Any idea what im doing wrong?
PS C:\Users\Sam\Downloads> fastboot boot "C:\Users\Sam\Downloads\image-newpixel4 (1).img"
downloading 'boot.img'...
OKAY [ 1.173s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.795s
Click to expand...
Click to collapse
Try making your own.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557

thanks for the guide but I cant seem to get this working right for me.
the img file provided gives me this error on the fastboot command : FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
when i create my own it boots via fastboot but then goes back to the boot loop state of the G logo and a progress bar
the stock boot img lets me boot up without root
I got into this state by trying to install gravity box, but now im just trying to get core magisk back. any input?

StephenMilone said:
thanks for the guide but I cant seem to get this working right for me.
the img file provided gives me this error on the fastboot command : FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
when i create my own it boots via fastboot but then goes back to the boot loop state of the G logo and a progress bar
the stock boot img lets me boot up without root
I got into this state by trying to install gravity box, but now im just trying to get core magisk back. any input?
Click to expand...
Click to collapse
Upload a current magisk_patched.img

Tulsadiver said:
Upload a current magisk_patched.img
Click to expand...
Click to collapse
https://www.dropbox.com/s/zgd83bjtvbravuo/magisk_patched.img?dl=0
here you go - thanks!!

StephenMilone said:
https://www.dropbox.com/s/zgd83bjtvbravuo/magisk_patched.img?dl=0
here you go - thanks!!
Click to expand...
Click to collapse
Sorry it took so long. I had some things I had to do.
Core only
https://www.androidfilehost.com/?fid=4349826312261694121
Remove
https://www.androidfilehost.com/?fid=4349826312261694123

Tulsadiver said:
Sorry it took so long. I had some things I had to do.
Core only
https://www.androidfilehost.com/?fid=4349826312261694121
Remove
https://www.androidfilehost.com/?fid=4349826312261694123
Click to expand...
Click to collapse
do not apologize at all! and it worked!! thank you so very very much.
any idea what was i doing wrong trying to package it myself?

StephenMilone said:
do not apologize at all! and it worked!! thank you so very very much.
any idea what was i doing wrong trying to package it myself?
Click to expand...
Click to collapse
Hard to say. Pretty straight forward. Just drop the overlay.d folder in the ramdisk folder and repack.

Not sure what i'm doing wrong but this doesn't work for me, I used the img that you sent to StephenMilone but it doesn't work even when I use that. I installed a magisk module and I got stuck in a bootloop but nothing I have tried has worked. Any help would be appreciated, thanks!

Thank you SO MUCH for this. I once again forgot to disable/delete Active Edge Mod on my Pixel 3 before updating the system via OTA, and this just saved me.

March boot fix images uploaded.

I might be doing something wrong... But I had gotten this to work for two months in a row,so couldn't be too much off
June 2020 patch... I can't figure it out... I did the overlay.d and I can't get the phone to boot properly.
Stock boot.img is fine, but patched and asking it to disable isn't working.... Can you generate one for June @Tulsadiver ? Thanks in advanced

sylikc said:
I might be doing something wrong... But I had gotten this to work for two months in a row,so couldn't be too much off
June 2020 patch... I can't figure it out... I did the overlay.d and I can't get the phone to boot properly.
Stock boot.img is fine, but patched and asking it to disable isn't working.... Can you generate one for June @Tulsadiver ? Thanks in advanced
Click to expand...
Click to collapse
Core-only
https://www.androidfilehost.com/?fid=4349826312261824031

[GUIDE][GSI] Flashing GSI's with TWRP Fixes and Workarounds

Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators

Screenshots of Havoc OS gsi running on my zte axon 10:

Android Q Gsi works too
you can also use the zte android 9 stock kernel and vendor

That all is great news.....bravooo

Any issues with the havoc gsi?

blcistheking said:
Any issues with the havoc gsi?
Click to expand...
Click to collapse
Only the Fingerprint is broken

noobstyle1337 said:
Only the Fingerprint is broken
Click to expand...
Click to collapse
its only broken if you have a a2020g, works fine if you have a a2020u, current los kernel is missing a2020g fingerprint firmware from what i can gather.

Bliss 12.7 Android 10 gsi on a2020u.

rafyvitto said:
Follow these easy steps
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
==
Click to expand...
Click to collapse
whenever i try this i just get
"fastboot: unknown option -- disable-verity"

Mr. DR. Professor Electro said:
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Click to expand...
Click to collapse
Skip that step not needed, just flahs the disable encryption zip file in twrp to disable encryption.

i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?

honestly i cant even flash any rom zip i have i just get error 1s , i even wipe data/format before flashing am i doing something wrong am i supposed to be on a or b while doing this or what

Futility's Forgotten Soldier said:
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
Click to expand...
Click to collapse
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.

cant escape bootloop hell and error 255
rafyvitto said:
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Click to expand...
Click to collapse
rafyvitto said:
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
Click to expand...
Click to collapse
having trouble
Steps I followed:
(bootloader been unlocked but double checked to be sure)
Started from LineageOS 16 clean flashed based
booted rom made sure Debug was enable in settings did nothing else
booted to bootloader
>fastboot set_active a
>fastboot boot "D:\Android\Flash\Recovery.img"
In Recovery:
Installed Twrp zip
install zip DisableForcedEncryption.zip
-reboot bootloader
>fastboot flash vbmeta "C:\Users\chris\Downloads\ZTE_Flash\vbmeta.img"
>fastboot format userdata
boot to recovery:
Installed GSI Image of Havoc OS to System image
Flashing system image......
simg2ing '/sdcard1/Havoc-OS-v2.9-20190914-phhgsi_arm64_ab-offical.img' 'dev/block/bootdevice/by-name/system_a'process
ended with ERROR: 255
got creative because nothing i was doing was fixing the problem so i went into fast boot and
>fastboot flash system "location/of/Havoc.img"
now no longer can acess the recovery not even but fastboot boot img command and back in a bootloop hell
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "D:\Android\Flash\Recovery.img"
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
also i have no way to return to the original 10 pro rom whenever i flash it via the EDL tool with one of the US edl
Zips you provided i have boot loop but it gives me enough so i can have bootloader mode accessible but i have to rerun
the bootloader unlock. but flashing Lineage 16 seems to be the only thing to make my phone functional without giving it boot loop hell
ill try do it with bliss later but if there's anywhere i went wrong or how to solve the 255 let me know i really want to try out one of those GSIs
but im running on the US rom and using the TWRP for my pro from the fourms so i just really confused here idk if i could possibly give you anymore details

ok update i got it working
1. the 255 i fixed by
"
Reboot into recovery, TWRP
Go to the terminal in "Advanced"
Type cd /system to change the path to the system folder
Type rm addon.d to remove the addon file
Type exit to quit from the terminal
Now back to TWRP home, try backup/restore again, it should works.
Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won't mess up the filesystem."
secondly what was ruining me was a big dumb mistake on my part you HAVE to do " --disable-verity --disable-verification flash vbmeta vbmeta.img" with the latest ADB tool kit I was using minimal adb and fastboot then got it to work

In step 5,i can not boot into TWRP and phone displays ZTE crashdump mode.
Please help.
Thanks.
Edit: I fixed it and can flashed this rom but it has some bugs.

''Error boot prepare'' Stuck in Fastboot when flashing magisk_patched.img

Trying to root my Pixel 3aXL with LineageOS 17.
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now.
''bootslot: b
enter reason: error boot prepare''

SOLVED
dadu1257 said:
Trying to root my Pixel 3aXL with LineageOS 17.
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now.
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
What the heck, this one was tuff. There were really less documentation and disinformation around.
So the situation is: How do I get Magisk Root on LineageOS 17?
- Do NOT use the ''stock'' boot.img as said in the magisk official tutorial for my phone. Since you have your Custom ROM you want your boot.img from your specific LineagaeOS (don't look for ''custom boot.img for lineage'' you can find here and there.)
- To get the right boot.img check your LIneageOS installation folder, unzip and look for ''payload.bin''.
- Extracting payload.bin to get boot.img doesnt work with 7zip. For me these steps worked well. When you have the right boot.img you can just follow the guide on magisk for your phone.
Get Payloader Dumber (github)
Get/Install Python (customize installation folder to an accessible place)
Extract Payload Dumper to Python Folder
Copy Payload.bin File from your CustomROM to Python Folder
Open Command Prompt there
Run "python -m pip install -r requirements.txt"
Run "python payload_dumper.py payload.bin"
Voila
(taken from https://www.youtube.com/watch?v=L4AGMqJStEI)
Hope this helps

dadu1257 said:
- Do NOT use the ''stock'' boot.img as said in the magisk official tutorial for my phone. Since you have your Custom ROM you want your boot.img from your specific LineagaeOS (don't look for ''custom boot.img for lineage'' you can find here and there.)
Click to expand...
Click to collapse
Great that you got it solved, but I just want to add a clarification:
The "stock" boot image file that the instructions talk about is simply the untouched (stock) boot image of whatever ROM you are currently using. The instructions even mention that you should extract it from your ROM zip if using a custom ROM...
:good:

Best custom ROM for OnePlus Nord 100.

Hi guys, Lineage has just launched an amazing GSI custom rom, here is a link
https://sourceforge.net/projects/andyyan-gsi/files/latest/download
The installation process is simple just go to
How to install GSI ROM on OnePlus n100.
Good morning guys.
forum.xda-developers.com
This rom is on the latest Android version (12), very stable, battery friendly and very customizable and backed with the latest security patches (February 05 2022)
To enjoy double tape anywhere on the screen to sleep just download those two files
APKs - Google Drive
drive.google.com
install them and set lawnchair as a default launcher, activate device administrator for it , go to launcher settings gestures double tap, that's it.

Well, I managed to finally install ... you are correct. Runs completely smooth. Is the partition large enough to install gapps ... and of course, how to install. I would like to use 12.

Unfortunately not, because the ultimate size of the system partition is 2.6gb
If you want to install the Gapps there is another ROM
caos-v224-201029-arm64-bgN.img.xz
You can find it on xda
Notice this ROM ends with bgN.img.xz
If it's g it's full (with gapps)
If it's v it's vanilla (without gapps).
Generally if the xz file exceeds 740mb, then the extracted file will surpass 2.6gb
You can verify this with 7zip the size of the extracted file will be on the right hand of the window of the 7zip program.
I forgot to to tell you that the Gapps will be included on the xz file.

bentalebnordine said:
Unfortunately not, because the ultimate size of the system partition is 2.6gb
If you want to install the Gapps there is another ROM
caos-v224-201029-arm64-bgN.img.xz
You can find it on xda
Notice this ROM ends with bgN.img.xz
If it's g it's full (with gapps)
If it's v it's vanilla (without gapps).
Generally if the xz file exceeds 740mb, then the extracted file will surpass 2.6gb
You can verify this with 7zip the size of the extracted file will be on the right hand of the window of the 7zip program.
I forgot to to tell you that the Gapps will be included on the xz file.
Click to expand...
Click to collapse
I will give it a try, but it is not A12, correct?

It's not, I think it's A10
By the way to activate audio and d2w go to phh settings

bentalebnordine said:
It's not, I think it's A10
By the way to activate audio and d2w go to phh settings
Click to expand...
Click to collapse
I just checked -- the *.img file is 2.2. I will give it a try, though I wish it were a12.

I'm trying to flash a Lineage ROM that's 2.438 GB, but it says "Not enough space to resize partition". You said under 2.6 GB is fine so am i doing something wrong? I assume it's "fastboot flash system" to install.
Edit: Just now tried the one from your post and it's the same problem.

thomaskmaagaard said:
I'm trying to flash a Lineage ROM that's 2.438 GB, but it says "Not enough space to resize partition". You said under 2.6 GB is fine so am i doing something wrong? I assume it's "fastboot flash system" to install.
Edit: Just now tried the one from your post and it's the same problem.
Click to expand...
Click to collapse
Are you coming from Android 11 oxygen OS?

bentalebnordine said:
Are you coming from Android 11 oxygen OS?
Click to expand...
Click to collapse
I am, yes.

thomaskmaagaard said:
I am, yes.
Click to expand...
Click to collapse
Then you should switch to the a slot by running the command
fastboot --set-active=a
And start all over again.

bentalebnordine said:
Then you should switch to the a slot by running the command
fastboot --set-active=a
And start all over again.
Click to expand...
Click to collapse
I did that the first time. Also tried erasing system and product (didn't expect it to make a difference..). Can't seem to get it to flash anything. I can flash stock vbmeta and system and it boots fine again...

thomaskmaagaard said:
I did that the first time. Also tried erasing system and product (didn't expect it to make a difference..). Can't seem to get it to flash anything. I can flash stock vbmeta and system and it boots fine again...
Click to expand...
Click to collapse
I think you should reboot fastboot after switching to slot a. and flash vbmeta and vbmeta_system and run the command
fastboot reboot fastboot.
Then the command
fastboot flash system <your system>.img
Then the command
fastboot - w
Then the command
fastboot reboot
That's it.

bentalebnordine said:
I think you should reboot fastboot after switching to slot a. and flash vbmeta and vbmeta_system and run the command
fastboot reboot fastboot.
Then the command
fastboot flash system <your system>.img
Then the command
fastboot - w
Then the command
fastboot reboot
That's it.
Click to expand...
Click to collapse
I've been trying that, but i don't get past flashing system since it throws that error. It is a be2013 so it shouldn't have any issues. I've never had problems flashing recoveries and boot images.

thomaskmaagaard said:
I've been trying that, but i don't get past flashing system since it throws that error. It is a be2013 so it shouldn't have any issues. I've never had problems flashing recoveries and boot images.
Click to expand...
Click to collapse
Try booting in TWRP for Android 10 that you can find on the roms and recoveries section, if it boots you are correct, if not just boot in TWRP Android 11 click reboot and click reboot in a slot if the courent slot is b.
To boot on TWRP just run the command
fastboot boot twrp.img

So.. I'm thinking, maybe the problem is that I have OOS11 on both slots? Don't ask me why, it's a long story, but I do. Is it only possible to flash over OOS10?

thomaskmaagaard said:
I'm trying to flash a Lineage ROM that's 2.438 GB, but it says "Not enough space to resize partition". You said under 2.6 GB is fine so am i doing something wrong? I assume it's "fastboot flash system" to install.
Edit: Just now tried the one from your post and it's the same problem.
Click to expand...
Click to collapse
yea i was tryna do the same exact thing and i messed around bricked my phone!! recovery.img doesnt even work to fix it,with the exception of twrp flashed in recovery i dont get a dang thing except either a complete black screen or "qualcomm crash dump". im stumped. even got another n100, same exact model, and everything i did before to unlock the network and bootloader isnt working anymore.

fastboot delete-logical-partition product
That command will allow for resizing of system partition and you can flash GAPPS, although its better to find a GSI with GAPPS baked in, as you'll have errors with GAPPS otherwise
Also, anyone with the flash issue of "system partition not big enough" ... the 2.6GB isn't the ROM.img, but after install. Use a GSI ROM that's around 1.9GB at largest, and it should fit. IMG files are compressed, similar to something like a ZIP file
Although every GSI I've tried causes either a bootloop or CrashDump

Your saying, OP, Lineage launched GSI custom rom - what it means? Unofficial fork?
No Gapps? Can't you flash gapps after GSI is flashed?
Caos Rom for with Gapps? What is Caos and GSI difference?

Best gsi rom until now is
https://github.com/ponces/treble_build_pe/releases/download/v413/PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz

The best custom rom for OnePlus n100 until now is
https://github.com/ponces/treble_build_pe/releases/download/v413.1-plus/PixelExperience_Plus_arm64-ab-12.1-20220518-UNOFFICIAL.img.xz
To successfully install it on your device, and the bootloader of your device is already unlocked than read the text file attached.
You will also need these files
OnePlus-USB-Drivers.zip
drive.google.com
Universal ADB Drivers
one_plus_nord_sdk.zip
drive.google.com
And also you need to extract the system image using 7zip program and put it on the one_plus_nord_sdk folder.