Related
UPDATE: I kept finding bugs in josh1x's rom, so i installed the LOS17 GSI instead. Guide for that outline in reply #11
Figured this out and thought i'd write a simple tutorial that covers stock (i was at 20e) to lineage. You'll need the LG USB Drivers and adb/fastboot. There are a couple other things to download through out the tutorial and the unlock tutorial in step 1.
LG USB Drivers 4.2.0
ADB/Fastboot
LGUP with partition DL
Note: I was able to reach download mode and fastboot at any point in this process and even when it went wrong (kernel crashes, boot loops etc) while figuring out this tutorial. I found that i could just hold vol down or up in a bootloop with the usb connected to get to the mode i wanted.
Typical combos:
-Download mode: power off phone with usb disconnected. hold vol up and plug in cable
--NOTE: after wiping laf_a and boot_b, you must switch to slot b to access download mode (run command: fastboot -ab)
-fastboot: power off phone with usb disconnected, hold vol down and plug in cable. or adb reboot bootloader
--NOTE: after wiping laf_a and boot_b, you can only access fastboot from slot a by holding vol up on boot (for 20e/21d, on 11g vol down still works).
-Recovery: power off. hold power and vol down, when you see the white LG G7 logo temporarily release just the power button. Continue to hold power and vol down till you get to the option menu. Select Yes three times.
Guide:
1. Follow the universal unlock method here.
1.5. You need to zero out laf_a and boot_b before flashing 21d/20e to maintain fastboot access. Use adb to run the following commands
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
1.75. Enable usb debugging (should already be done). Open LGUP and connect to your phone. dont close it. If you open it after booting to DL mode it wont recognize it
2. 21d ULM firmware (here) must be flashed to use the latest twrp (20e works as well). The 11g twrp cannot install lineageos. I would imagine the EU firmware could be flashed as well, but I used ULM.
Code:
Boot into fastboot
fastboot -ab
Boot into download mode
Use the lg up linked in this post to flash 20e/21d without laf_a and boot_b with partition dl mode
3. Format userdata to decrpyt your file system so TWRP can access it. Then flash TWRP; boot_twrp-june.img can be found here. It's from Josh1x's post here. Note: this TWRP is non persistant.
Code:
Boot to bootloader
fastboot format userdata
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Select restart in fastboot
Boot to recovery
4. Obtain the latest lineage build here. This is from Josh1x's post here. I attempted to flash gapps at this point and it failed, see the next steps.
Code:
Wipe everything
Transfer lineageos to your phone and install it
Restart normally
5. Gapps
Code:
Reboot to bootloader
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Reboot to recovery
Transfer opengapps 9.0 to your phone and install.
Reboot to bootloader
6. We need to flash the stock lineage boot image (here) again now that we are done. The file was obtained with this method
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Restart normally
if you have magisk, it would be magisk_patched_boot.img (here). this one was made from the above image with magisk on my phone.
Code:
fastboot flash boot_a magisk_patched_boot.img
fastboot flash boot_b magisk_patched_boot.img
Restart normally
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
I am so glad to be off of stock, enjoy guys and girls!
Bugs (from my ULM phone)
-flash doesnt work in the camera. also probably why gcam crashes (gcam works on an EM phone somehow)
-brightness slider is calibrated incorrectly compared to stock. way too bright when set to 0%
NOTE: using ULM vendor fixed the flash and brightness, but gcam still doesnt work. This would make it the most functional rom for this phone at this point (vibrate does work).
Being that since day1 of g710pm/ulm could be boot unlocked, all ypu had to do is flash the eu firmware and go to lineage frlm there due to twrp incompatibility.
I have not tested it, but does being on lineage based off EU blobs, do you still get full LTE and/or volte.
If sprint users have switched to eu/lineage do you have full lte/ril compatibility.
Ah crap I didn't know that. I tried unlocking through LG when I got it a couple months ago and that didn't work of course. At that time the phone was working well (not going on a background apps killing spree), so I didn't bother. I couldn't find anything on here at the time for unlocking, but I obviously missed that.
LTE and wifi are working fine. Maybe that has something to do with me never flashing the EU rom to install lineage? Anyways, I couldn't find a volte toggle, but I'd assume it is working. I'm on Verizon and I believe they are killing their cdma network, so I'll find out.
Would this work on sprint phones? There is a warning at the end of the unlocking guide about sprint phones loosing fastboot when upgrading to ulm pie.
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Emanel000000 said:
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Click to expand...
Click to collapse
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Have you tried the other twrps?
sirbow2 said:
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Click to expand...
Click to collapse
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk)
Click to expand...
Click to collapse
oh yea. i see, yes, they might as they are from the lineage rom.
Emanel000000 said:
... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
sirbow2 said:
oh yea. i see, yes, they might as they are from the lineage rom.
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
Click to expand...
Click to collapse
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
Emanel000000 said:
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Click to expand...
Click to collapse
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Edit: Update 2: dont use the vendor in this post. I patched the ULM vendor, but vibrate and gcam are still an issue with a GSI. links here: https://forum.xda-developers.com/showpost.php?p=81563763&postcount=41 Also, using the ulm vendor on Josh1x's rom fixed everything but gcam.
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
sirbow2 said:
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Click to expand...
Click to collapse
i just had 20c for em it doesnt matter the version
sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Thanks. You're process got my audio working on GSI. Not sure what incorrect image I was installing or what the issue was.
Just need to disable the LED notification and get vibration working.
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
thats what i was kind of thinking the issue was. thats over my head though.
sirbow2 said:
thats what i was kind of thinking the issue was. thats over my head though.
Click to expand...
Click to collapse
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
loonycgb2 said:
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
Click to expand...
Click to collapse
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
sirbow2 said:
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
Click to expand...
Click to collapse
Once you got twrp running with stock then do the normal thing of format userdat to decrypt it then flash the no dmverity zip mentioned in the thread or magisk then backup vendor via twrp or dd...
That will give you a usable vendor for lineage and such.
All josh1x or whoever did to the EM vendor was modify fstab to remove the force encrypt so that way decrypted roms would work.
sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Nevermind
I tried using the vendor from ULM 20e and it doesnt work, i even tried flashing dm verity right after. How would one modify the vendor partition anyways?
This is an attempt at rooting the UMIDIGI F2. Caution be advised, we are not responsible for your mistakes; but rest assured, most of them can be corrected.
Rooting the F2
Disclaimers
This is important, please read thoughtfully.
whatever you do, never ever use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEIs and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
Once bootloader is unlocked, warranty is considered void. By following this guide, you consent to that happening. Safety net CTS will not pass anymore unless you flash Magisk which hides the unlocked bootloader.
Never relock your bootloader while running anything unofficial as the phone will not boot until you unlock again.
And, once again, a lot of bad things can happen like bootloops, if that happens to you don't freak out and reflash stock, redoing the rooting process from the start. It might be time consuming, but that's your safest bet!
More important even, have fun rooting, it's before all a hobby!
Various Resources
>>> Latest official stock ROM <<<
Minimal ADB and Fastboot by shimp208
> Magisk (and Manager) by topjohnwu <
Mediatek SP Flash Tool
Latest unofficial TWRP
Unlocking Bootloader
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate "Developer options" through Settings > About Phone > Tap Build Number multiple times.
2) Open "Developer options" in Settings > System > Tap Advanced.
Enable "OEM Unlocking" and enter your password to confirm. Enable "USB Debugging" as well.
3) On Windows, download and install Minimal ADB and Fastboot by shimp208
On Linux, use your packet manager to install android-tools-adb and android-tools-fastboot
4) Open command prompt (Win + R > type cmd) or a terminal on linux.
5) Plug your phone, accept the prompt about adb and the PC signature.
6) Type adb reboot bootloader to reboot in fastboot mode.
THESE NEXT TWO STEPS WILL COMPLETELY WIPE YOUR DATA
7) Unlock the bootloader using fastboot flashing unlock and pressing Vol+
8) Unlock the secure partitions using fastboot flashing unlock_critical and pressing Vol+
9) Restart using fastboot reboot
You will now always see "Orange State" at boot; this is completely fine and will only delay your boot by 5 seconds.
Rooting using Magisk patched boot.img
This is "experimental" and is probably overkill, but everyone managed to install Magisk with it.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT by selecting the scatter file, pressing download an rebooting the phone (Make sure it is in "Download Mode" and not "Format + Download")
2) Patch boot.img by copying it to your device, using Magisk Manager to patch it, and get back the magisk_patched.img in the Download folder back to your PC.
3) Start ADB while booted; run adb reboot bootloader. Alternative is to reboot to recovery and selecting "reboot to bootloader"
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
You can try without --disable-verity --disable-verification if those commands are not recognized. I have not tested without them.
6) fastboot --disable-verity --disable-verification flash boot magisk_patched.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img (recovery.img from stock)
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (vbmeta.img from stock)
9) fastboot reboot
When rebooting, install Magisk Manager. It will prompt to finalize the installation, you can do so.
Congratulations ! You are now a proud Magisk user ! All credits goes to @topjohnwu he's the real MVP here.
Returning to stock / Resolving issues
The best way to resolve any issue is to return to stock. Here is the method.
1) Download latest stock ROM ("SPFT .zip") on UMIDIGI's forums
2) Download SP Flash Tool if you don't have it yet (Windows only)
3) Extract stock ROM in SP Flash Tool directory
4) Open SP Flash Tool, Download Tab, "Choose" in Scatter-loading file, select the scatter file in the stock ROM directory.
5) If you want to keep your data, untick "userdata" partition
6) Press Download and connect your device via USB. Reboot the phone or turn it off and everything will be flashed.
7) If you want a full stock experience, I recommend relocking the bootloader so that SafetyNet will pass. Get into fastboot mode by using adb reboot bootloader and use fastboot flashing lock_critical followed by fastboot flashing lock. This will wipe your data once more.
You should be good to go.
TWRP
Device Tree
>> Download my latest build here <<
Flash in Bootloader mode with fastboot flash recovery twrp_f2.img
Android 10 and TWRP aren't compatible yet. /system and /vendor cannot be mounted. /data partition is encrypted. You can still flash .img and some zips that alter different partitions. Nothing I can do about it.
Misc
Different boot modes
Recovery / TWRP :
Turn off the phone (or reboot)
Press Vol+ and Power until some choice comes up to you
Navigate using Vol+, select Recovery Mode using Vol-
Bootloader mode :
Boot into TWRP, select Reboot, Bootloader
Or use adb reboot bootloader either in recovery or system
Or use fastboot reboot-bootloader in fastboot mode
Magisk and EdXposed
Fixing Magisk bootloop
Two techniques that could work after installing a module that broke everything :
Hook your device up to a computer (or other device you can run adb from) and execute the following command:
adb wait-for-device shell magisk --remove-modules
After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot.
Click to expand...
Click to collapse
-----
You could also try :
If you can't boot your device, this can be done by placing a file in /cache (/data/cache on A/B devices) named ".disable_magisk" (without quotation marks and with the leading dot). This will enable Core Only Mode and you can boot up your device, uninstall the troublesome module and then go into the Manager settings, disable Core Only Mode and reboot. In TWRP you can create the file through the TWRP terminal with the touch command, see below for an example.
Click to expand...
Click to collapse
Installing EdXposed
Please use the latest YAHFA or Sandhook canary build. I have a report of Xposed-SandHook-v0.4.6.1 (4504)-tdgptedc-release working.
_cab13_ said:
This is an attempt at rooting the UMIDIGI F2. For now, unsuccessful. Any help would be appreciated!
Click to expand...
Click to collapse
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate the "for developers" item in the settings (7 times click on the "build number" in the "about phone" settings at the bottom)
2) Go to "Settings"(the main screen of the application) go to "for developers" and move the switches to the enabled position near the items "USB Debugging" and " Unlocking the bootloader"
3) Then download platform tools from here https://developer.andr...eleases/platform-tools
4) Unpack the archive from platform tools to the root of the C: drive(so that the platform-tools folder is in the root of the C drive: )
5) if the process does not go install VCOM driver
6) Switch your smartphone to fastboot mode:
6.1) connect the included phone to the computer
6.2) Open the command prompt
6.2.1) Click Win+R
6.2.2) in the window that appears, write "cmd" and click " OK"
6.3) in the command line when the phone is turned on, write(without quotes)
6.3.1) " cd " (note that there is a space after "cd") and drag the "platform-tools" folder with the cursor to the command line window, press Enter
6.3.2) the Following command "adb reboot bootloader"
6.3.3) Your phone should reboot into Fastboot mode or a window should appear on the phone asking for debugging permission for this computer - put a check mark "Always allow debugging from this computer" and click "OK", repeat point 6.3.2
7) After that, on the computer in the same command line, enter " fastboot flashing unlock"
8) when the smartphone screen will prompt confirm by pressing vol+
9) after you see Finished, restart your device
Now the logo will be labeled Orange state when loading
I've rooted my F2. I used magisk to patch the boot.img then flashed the boot.img through fastboot on Linux. It didn't work with magisk 20.1. Had to used the newest magisk manager. I am interested in your twrp if you have one to try. Would you upload it so I may try to flash it.
Please upload your patched boot.img file. Thanks
I would love to have that boot image as well! What magisk version did you use then ? I can start crafting a guide.
EDIT: what boxes did you tick in Magisk Manager ?
EDIT 2: did you pad the boot image with DD ? Or maybe you wiped the boot partition beforehand to make it all zeroes ? It seems to be the missing thing and a known bug in Magisk.
Magisk 20.2 was what I used. Then flashed the boot through fastboot using Debian Linux.
Rooted f2 boot IMG
I've tried everything to get it rooted but any magisk patched boot image I flash just sends it into a bootloop including the one posted in this thread. It doesn't matter whether I flash it in Linux or Windows, in fastboot or in SP Flash Tool. What stock build are you guys on, the European or the Global? It seems that the boot.img is the same in both.
Apparently the issue is that the bootloader really doesn't like the fact that the image is not the full size of the partition. I'll try to dd it to the "max" size so it completely replaces the boot image and not only parts of it.
Seems to be an issue with the bootloader which doesn't like being flashed with a smaller boot image than it's partition size. Could you try padding it ? https://github.com/topjohnwu/Magisk/issues/2005
With this command
Code:
dd if=/dev/zero of=magisk_patched.img bs=1 count=1 seek=33554431
EDIT: Double post, my internet is pretty bad, I thought the first one didn't go. Can't delete apparently.
When I unlocked the bootloader I also unlocked critical areas
fastboot flashing unlock_critical
Warning---- this will wipe your phone again just like the bootloader unlock.
Haha seems to be the key to it ! Thanks for the update !
I've tried everything as well. Still bootloop. Your patched image doesn't work for me. I've unlocked critical as well as regular unlock.
1. Did you tick any box in Magisk Manager ?
2. Did you relock afterwards ?
3. What firmware version ?
I downloaded the new update today and I haven't been able to root the boot.IMG so far. I will keep trying and note anything that is successful.
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
_cab13_ said:
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
Click to expand...
Click to collapse
This worked for me to reroot after the update today. Not sure what part of it is necessary for the boot image to work right though. I left off the userdata.img so I could keep my files in place.
_cab13_ said:
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
Click to expand...
Click to collapse
Confirmed working, thanks. I ended up patching the new boot.img myself and that also worked. I own a Note 10 + and OnePlus 7 Pro and honestly I think the Umidigi is an awesome deal, everything is pretty good on the device. It's something I wanted to try out and I'm actually impressed.
Did one of you already tried some treble roms on the f2? lineagOS, Havoc 3.0 or aosp?
ubuntuh said:
Did one of you already tried some treble roms on the f2? lineagOS, Havoc 3.0 or aosp?
Click to expand...
Click to collapse
Currently there is no twrp recovery for the f2. I've tried a couple ports of twrp but can't get past the splash screen.
We don't need TWRP to flash ROMs. Fastboot / SPFT should suffice.
_cab13_ said:
We don't need TWRP to flash ROMs. Fastboot / SPFT should suffice.
Click to expand...
Click to collapse
True. Twrp just makes it quicker and has easier backup option
Code:
* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* before flashing GSI! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
you cant have magisk patched boot image installed unless you have also flashed a different product img
- under developer options enable oem unlocking
- adb reboot bootloader
- fastboot flashing unlock
- fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product (DONT DO THIS IF YOU WANT TO FLASH MAGISK. IF YOU DO THEN FOLLOW THIS GUIDE REGARDING MAGISK AND PRODUCT PARTITION https://forum.xda-developers.com/t/tutorial-magisk-on-gsi-on-devices-with-dynamic-partition.4311045/)
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot recovery
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Sarticle said:
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Click to expand...
Click to collapse
thats complete bs
your device must be launched with android 10 or newer to be able to have dynamic partitions.
google play certification has nothing to do with it.
and if you flash product partition you might get away without reinstalling magisk or xposed
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
thirtythr33 said:
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
Click to expand...
Click to collapse
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
ok the reason I ask is I am given the option to flash my backup boot image to super in twrp flash image screen, that's why I asked, and since twrp is reporting that I'm missing system_ext, product, and odm, that flashing to super would fix that, a long shot but I'm desperate.
so to be clear is it shared between slots or does each slot have it's own super? (or the partitions found in it)
kusti420 said:
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
also stock recovery must be installed
and you cant have magisk patched boot image installed
- under developer options enable oem unlocking
- fastboot flashing unlock and then fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
or if you dont have a custom recovery then you can just factory reset in stock recovery
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Click to expand...
Click to collapse
this is all done on pc right? is everything in order?
JordanPahlevi said:
this is all done on pc right? is everything in order?
Click to expand...
Click to collapse
yes its done on pc and everything is indeed in order
Flash gsi with twrp can't ?
Blacxx said:
Flash gsi with twrp can't ?
Click to expand...
Click to collapse
you can only do it in twrp if you rebuild the whole super partition with the gsi of your choice and flash that
Android prevents apps or pretty much anything from mounting the system.
Stephanie_Sy said:
Android prevents apps or pretty much anything from mounting the system.
Click to expand...
Click to collapse
mounting isnt the problem, it mounts just fine, but its read only, thats the problem
How did you port twrp for infinix zero 8? I need one for infinix note 10
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Parvej789 said:
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Click to expand...
Click to collapse
follow the tutorial and flash product partition
this may be of interest or help to Samsung users in particular.
getting fastboot via TWRP to work on windows 7 to 10. it worked for me on windows 10 pro and enabled me to flash GSIs successfully.
Latest ADB Fastboot and USB Drivers installer tool for windows
All praise and All Thanks to God ADB Fastboot and USB Driver installer tool for Windows, which will always install the latest version. To update the adb fastboot and usb drivers again, just rerun the tool. OS Requirements: Windows 7 and above Steps: 1. Connect the phone in USB Debugging mode...
eu.community.samsung.com
it's not just for Samsung users though, it'll install the latest ADB and Fastboot drivers and download Microsoft dependencies. but now us Samsung users can have Fastboot and do
Code:
fastboot flash system system.img
... so yay !!
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
i flashed using these commands on my v60 tmobile
--AB devices--
fastboot devices
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_insertslothere
Example
fastboot delete-logical-partition product_a
fastboot delete-logical-partition productb
fastboot flash system system.img
fastboot reboot recovery
i flashed 3 gsi A10s, los 17.1 didnt boot, pixel experiance and RR Remix booted but never entered android. and when i tried to flash my kdz it flashes all parititons except for super.img it fails everytime on different modes of LG up. I flashed super.img via Qfil but phon wont boot.
i even tried using ChonDoe_Flasher via twrp in a folder it flashes but it still wont boot at all. at this point i cant use LGup because i get stuck in download mode. any help would be greatly appreciated
blaze2051 said:
Try :
Click to expand...
Click to collapse
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Parvej789 said:
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Click to expand...
Click to collapse
i finally got a working rom install since i cant go back to oem stock, it wasnt the commands it was the roms, they just dont boot at all. except one 1 rom did boot. all others LOS 16-18 RR Remix and Pixel experiamce all failed to boot except for E foundation rom
/http://doc.e.foundation/how-tos/understand-and-use-gsi 7
/http://doc.e.foundation/how-tos/install-GSI 7
New linksto download the latest official
dev /e/ G.S.I. android.10 Q
Once you know which system image you need
Arm A 2 (system-arm-a.img.xz)
Arm A/B 3 (system-arm-ab.img.xz)
Arm64 A 11 (system-arm64-a.img.xz)
Arm64 A/B 31 (system-arm64-ab.img.xz)
Binder 64 A 1 (system-a64-a.img.xz)
Binder 64 A/B 4 (system-a64-ab.img.xz)
I no know.
Dynamic
gsi ROM
GsI Rom Link : Tested rom
Tecno kd7 work
*Official Android 11 :
1. AOSP 11.0 v313_system-roar-arusson
Download link AOSP 11.0 v313
*Unofficial QAndroid 11 :
1. Pixel Experience Plus 11.0 v313
Thanks for ponces
Download link PixelExperience_Plus_arm64-ab-11.0-20211011-UNOFFICIAL.img.xz
*Unofficial Android 12 :
1.Pixel Experience 12.0 v400.e
Thanks for ponces
Full googel rom. my used 5 day . 1 bug : bootanimation not vew full size
Download link :PixelExperience_arm64-ab-12.0-20211226-UNOFFICIAL.img.xz
Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?
Any help on rooting ColorOS 12 updated on Oneplus Nord?
Hi, I am undergoing the same issue. But, sort of have an idea how to fix it. Unfortunately I am a bit worried to try it out. I know there is no vendor_boot image to patch. But isn't it the same thing to patch vendor.img? Could you try patching that and let me know of the results?
I tried patching vendor image. There was an error in magosk.
I'm going to try flashing Twrp recovery on the phone and try installing magisk to root it. Will let you know how it goes
No luck, doesn't work for Android 12. Waiting on some update for rooting the Nord
puru said:
Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?
Click to expand...
Click to collapse
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
This worked. I am still testing though.
Link to canary - https://github.com/topjohnwu/magisk-files/blob/canary/app-debug.apk
Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
Can anyone confirm this does work without having to wipe the entire phone's data?
Thank you
Hi
This works and data is intact.
Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?
robuser007 said:
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?
Click to expand...
Click to collapse
Install OOS12, install magisk and patch the boot.img, then boot into the bootloader and type the commands. After an ota, magisk must be installed in the inactive slot.
Does this also work with Magisk v25 released today?
Where can I find those files? I guess I have to move those to the fastboot folder on my pc ?
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
robuser007 said:
Does this also work with Magisk v25 released today?
Click to expand...
Click to collapse
No, I'm not able to have a bootable magisk patched boot image, also using magisk canary release.
After I flash the patched img the Nord goes in bootloop, the only way to have it working is to flash back original boot.img
About the vbmeta.img & vbmeta_system.img I have used the extracted from payload_output folder, I think is correct?!?
Did you manage to solve this ? I really want to upgrade but not loose root.
I rollback to stable Android 11, I have tested the new version for one day and is graphically bugged everywhere, seems they release a beta, not a stable version.
I rollback to stable Android 11 with Orange Fox recovery, Root, safetynet-fix ok, ecc ecc
I have tested the new version for one day and is graphically bugged everywhere, then no recovery, no root, Color OS seems not for me for the moment.
What do you mean with graphically bugged everywhere ?
How can I stay on having root, does it work with latest canary?
robuser007 said:
Did you manage to solve this ? I really want to upgrade but not loose root.
Click to expand...
Click to collapse
I'm also not upgrading because of 'loose of root"
Still not able to find fix of safety net fix for A12..
all method i tried but safetynet is not fix.... CTS profile always FAILED...
nobody has any method which is working...
In a moment of weakness, I finally allowed my G Stylus to update to Android 12, and my stability has been a nightmare since then. I have been reading through many guides here and elsewhere to getting a GSI installed.
So far, I have unlocked the bootloader and followed the instructions for installing TWRP using adb/fastboot for my device. When try to flash a GSI, the partitions in TWRP don't look like anything I've seen in guides. The options it shows me are:
-Boot
-Dtbo
-Persist
-Super (system system_ext product vendor)
-Install Recovery Ramdisk
I tried installing on Super, as I found a thread mentioning it should contain both vendor and system. However, when I flash the img for a gsi to it, it will only boot to bootoader. I can get it into TWRP recovery but the screen is entirely unresponsive, even attempting to power off prompt's a restart. I was able to use Moto's Rescue program to get it back in working order, but each time this happens I have to start over at square one.
I tried with a GSI for crDroid on my first attempt, and then LineageOS on a follow-up attempt, both I had the same issue.
I'm new to Android modding, so I could really use some guidance through getting this set up. I've extensively referenced guides on here and elsewhere, but I've struggled with parsing and figuring out what I need to do in this case. Currently my device has TWRP installed but I'll be doing nothing else until I know what the best way forward is. I'd be happy to provide additional info.
Edit: Just found the dedicated 5G section. Sorry about this.
I am not sure why people use TWRP and a GSI/crDroid /w LineageOS rom.
All you need to do is install the magisk module L Speed
Remember this phone has 2 boot partitions....1 is secured (even if you have the bootloader unlocked and your rooted) So if you trip the SafetyNet your going to have bootloading issues and boot loops
Not sure what the previous comment was about, what does safetynet have to do with anything? It fails the second you unlock the bootloader.
First, you'll want to make sure to have installed at least one OTA update so both your slots are occupied. You could also install copy-partitions from a custom recovery. Otherwise your phone might brick if it ever switches to slot b.
Download and extract the official firmware for your device that matches what is installed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
And reflash your vbmeta partition(s) from fastboot to disable verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_system.img
Then you need to reboot into fastbootd (you can also get into it from a custom recovery)
Code:
fastboot reboot fastboot
From there you can erase your system, install the GSI, wipe data, and reboot
Code:
fastboot erase system
fastboot flash system GSI_system.img
fastboot -w
fastboot reboot