Related
I'm trying to install the OpenGapps package for LineageOS 16 on my new Oneplus 7 Pro, but have a problem installing it.
First I tried the "open_gapps-arm64-9.0-micro-20190827.zip" package, but it told me its the wrong platform. Is it not arm64?
Second I tried to install the "open_gapps-arm-9.0-micro-20190827.zip", but gives me an error 70, saying I do not have enough space.
Maybe someone have a solution for this?
Thanks
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
oryanh said:
Try MindtheGapps. I've seen this work for some.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Click to expand...
Click to collapse
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
cbadk said:
Tried it. Still does not work.
I got it semi, but still not working. Seems like the problem is within the way the partitions getting handled. My old Oneplus 5t had a boot, recovery, system partitions. The new one includes the recovery inside the boot it seems instead.
Here's how far I am now:
1) Unlocked the phone
2) Installed TWRP
3) Install Lineage ( This overwrites the TWRP so you have to install it again )
4) Reboot straight from TWRP after flashing the Lineage... back into the Bootloader/Fastboot mode and install the TWRP again.
5) Boot back into TWRP recovery and now I'm able to install OpenGapps ARM64 version.
But after this I cant boot the OS anymore...
Click to expand...
Click to collapse
Format data in twrp then try boot again should work
liam_davenport said:
Format data in twrp then try boot again should work
Click to expand...
Click to collapse
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
cbadk said:
Still no luck. Tried many things now... but here's what happens:
1) Installing the TWRP
2) Format data partition and everything else
3) Reboot back into TWRP
4) Install Lineage ( At this point I'm able to boot into Lineage just fine )
5) Trying to install Open GApps at this point gives me:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: This Open GApps package cannot be installed on this
device's architecture. Please download the correct version for your device.
# Begin User's gapps-config
# End User's gapps-config
It says I need to install the ARM instead of ARM64...
But if I go back into the bootloader and flash the twrp and boot back into the recovery, I'm able to install Open GApps ARM64 just fine. Seems like a weird "device's architecture" detection problem in the Open Gapps or maybe it could be the TWRP... not sure...
Also after this it will no longer boot.
Kinda weird problem....
Click to expand...
Click to collapse
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
liam_davenport said:
Don't wipe system afaik vendor LOS generates it's own, Also might be in the wrong slot make sure the slot changed when rebooting back to recovery to install gapps, I used MindTheGapps latest version from OP worked great.
Click to expand...
Click to collapse
Have not wiped the System and Vendor partition after I installed Lineage... It boots just fine... just not if I install Open GApps....
Tried MindTheGapps latest version, but still no luck.
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
cbadk said:
Okay got it working. The problem was the A/B partition layout they have in this phone... Was not aware of this.
This article describes it pretty well: https://lineageos.org/Changelog-19/
So yeah this is what I did:
1) Boot into Bootloader/Fastboot mode
2) Flash the boot partition with fastboot flash boot twrp-3.3.1-52-guacamole-unified.img
3) Restart into TWRP - Format the data partition and clean the system partition etc.
3) Restart into recovery TWRP once more to get the data partition ready
4) Now you can transfer the lineage-16.0-20190827-nightly-guacamole-signed.zip over to memory.
5) Now flash the zip file and let it complete. This will overwrite the boot partition with TWRP and replace it with Lineage's own boot/recovery image.
6) Now reboot into Lineage's recovery. Now select Apply update > Apply from ADB and send the "MindTheGapps-9.0.0-arm64-20190615_031441.zip" file to the phone with "adb sideload MindTheGapps-9.0.0-arm64-20190615_031441.zip" - You might have to confirm the zip file....
After this is done, the phone should be ready for use.
Click to expand...
Click to collapse
I am facing the same A/B slot problem with my Moto Z2.
After setp 5), did you let the lineage OS fist then reboot into recovery, or did you go straight to the lineage recovery?
Thank you so much for this. I finally fot it sorted. I did find that sometimes you have to ubplug the USB cable and plug it in again to be recognised, but I got it going. Goodby Google!!!!
I am using Gentoo Linux with adb to do this.
came out today. bricked my lg v20 h918
come up showing red text with number of times bootloader is unlocked and will not boot further..
tried direct install.
had to hold button down like going into recovery then select yes twice then getg into twrp then restore boot and lafs etc.
then when all working i tried to install the same version via twrp install same issue. apparently installing to wrong partition..
reinstalling the older 20.1 (hopefully you have it downloaded) from twrp worked fine.
Thanks for the info! Little late for me. Just wanted to post the last known good Magisk for anyone that needs it.
Search for download-magisk-20-1-stable
What did you do after booting into TWRP?
same issue, unfortunately, saw this post too late
same and now im screwed how can we recover this?
it says warranty void !!
number of times bootloader unlocked : 2 (in red
*Welcome to Fastboot mode:
* HOW TO EXIT fastboot mode
use 'fastboot reboot' command if the fastboot is available
i tried to install magisk 18 and then 20.1. they install but im still bricked at this same issue above.
HELP
h918
I was able to get up and running again by flashing H91820h.zip in TWRP, then flash Magisk-v20.1.zip and finally TWRP 3.3.1-0 2019-05-17 .img
Phone booted normally after this process. Hope this helps!
Similar situation. Fortunately, I did a nandroid backup first, so I restored it to get the phone up and running again.
My Success Story
For those of you who, like me, didn't have a known good backup to work with, here's what I did:
Determine ROM version installed if you don't know what it is (I was able to check the /system/build.prop file from TWRP under ro.lge.swversion)
Grab the appropriate ROM .zip file (I got my h910-10r zip file from the H910 Root Post)
Unzip the ROM file
Grab the "boot" file from the ROM and place on an SD card as boot.img
Flash boot.img to the boot partition using the TWRP install function (you'll have to toggle it to show Images in the install screen)
Reflash Magisk v20.1 (you can download it from github)
Wipe Dalvik and Cache
Reboot
Wait for the LONG boot process which will go through the nerve-wracking android is staring screen with the percentage bar as it rebuilds the Dalvik cache (I think that's what it's doing)
As a note, this did not clear any of my data.
Good luck, YMMV.
For anyone with this issue run the latest magisk uninstaller in twrp and restart the phone. If that doesn't work boot back into twrp and install magisk 20.1
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
James.ptrsn said:
For those of you who, like me, didn't have a known good backup to work with, here's what I did:
Determine ROM version installed if you don't know what it is (I was able to check the /system/build.prop file from TWRP under ro.lge.swversion)
Grab the appropriate ROM .zip file (I got my h910-10r zip file from the H910 Root Post)
Unzip the ROM file
Grab the "boot" file from the ROM and place on an SD card as boot.img
Flash boot.img to the boot partition using the TWRP install function (you'll have to toggle it to show Images in the install screen)
Reflash Magisk v20.1 (you can download it from github)
Wipe Dalvik and Cache
Reboot
Wait for the LONG boot process which will go through the nerve-wracking android is staring screen with the percentage bar as it rebuilds the Dalvik cache (I think that's what it's doing)
As a note, this did not clear any of my data.
Good luck, YMMV.
Click to expand...
Click to collapse
Thanks so much, you really saved me. I was panicking for sure. These directions need to be stickied!
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
BadToThePhone said:
For anyone with this issue run the latest magisk uninstaller in twrp and restart the phone. If that doesn't work boot back into twrp and install magisk 20.1
Click to expand...
Click to collapse
Tried didn't work, but thanks, the one above worked for sure, no lost data
lgkahn said:
came out today. bricked my lg v20 h918
come up showing red text with number of times bootloader is unlocked and will not boot further..
tried direct install.
had to hold button down like going into recovery then select yes twice then getg into twrp then restore boot and lafs etc.
then when all working i tried to install the same version via twrp install same issue. apparently installing to wrong partition..
reinstalling the older 20.1 (hopefully you have it downloaded) from twrp worked fine.
Click to expand...
Click to collapse
Unfortunately i wasn't lucky with this.. got stuck in fastboot, my sd and internal storage are both wiped, Rip years of data on that sd.. Can't get a system on the SD or internal storage, Fastboot isn't helping, ADB sideload won't load in twrp, LG Bridge won't detect my phone Am i screwed with this? I can boot to twrp but thats about it
texas7412 said:
Unfortunately i wasn't lucky with this.. got stuck in fastboot, my sd and internal storage are both wiped, Rip years of data on that sd.. Can't get a system on the SD or internal storage, Fastboot isn't helping, ADB sideload won't load in twrp, LG Bridge won't detect my phone Am i screwed with this? I can boot to twrp but thats about it
Click to expand...
Click to collapse
TWRP on my US996 automatically made the phone a usb drive when it got plugged in. Have you looked for it as a usb drive? also have you checked your usb drivers?
James.ptrsn said:
For those of you who, like me, didn't have a known good backup to work with, here's what I did:.......................
Click to expand...
Click to collapse
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from the above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
I'm in the TWRP Recovery file manager and I can't see magisk backup folder.
pendgy said:
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from he above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
Click to expand...
Click to collapse
Thank you. This helped a lot. Can't remember ever being without my phone for this long. Very stressful. This worked for my LG V20. Few things to add. I was super nervous to boot into twrp using the hardware "factory reset" option. Normally it just asks to wipe data once before booting into TWRP but after this happened, it asked two times. Was worried the magisk "update" wiped out my twrp and I was going to actually wipe all of my data using the recovery option. After unsuccessfully trying multiple ways to install twrp via fastboot as a safety net, I bit the bullet and did the double factory reset. Thankfully, it brought me to TWRP. Those of you worried, hope this helps ease your mind that twrp is intact after this debacle.
Next, using @pendgy help, I found the boot.img.gz but was unable to unzip in twrp. I copied the file to the internal sd so I could view on my pc. Connected to pc while in twrp and unzipped the boot.img.gz folder. Then extracted the boot.img into the internal sd. Was then able to install image to boot partition. Rebooted and everything was exactly as it was 17 hours ago when my heart sank. Yay!
Thanks to everyone for the reports and warnings. I saw the update to Magisk Manager yesterday on my Shield K1 and allowed that to update. I didn't update Magisk itself because I don't trust the direct install method through Manager. I saw the notification on my sandbox V20 this morning and dismissed it. My daily V20 hasn't received an update notification yet, but I think I disabled status bar notifications for Magisk on my daily. I'll be sure to not install 20.2 on either phone.
Magisk Manager's update notifications are pretty annoying to be honest. My devices are already rooted. An updated version of Magisk isn't going to make them rooted better.
Oh boy. Learning a lot of hard lessons this morning.
Apparently my TWRP install has been broken/corrupted for who knows how long. I'm now several hours into restoring my phone from basically scratch (had to retry a bunch of times because I'm a dumbdumb and haven't poked around at Android recoveries in ages).
Moral of the story: BACK UP EARLY and BACK UP OFTEN. If you don't have a backup (any kind of backup), the day will inevitably come when you wish you did. Sigh.
Oh well, maybe my phone will run a bit smoother now. Good luck everyone.
pendgy said:
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from the above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
Click to expand...
Click to collapse
How did you unzip the archive with TWRP?
Edit: Nevermind, copied the archive to external SD und unzipped it with 7z on my computer.
fatappel said:
...............................
Next, using @pendgy help, I found the boot.img.gz but was unable to unzip in twrp. I copied the file to the internal sd so I could view on my pc. Connected to pc while in twrp and unzipped the boot.img.gz folder. Then extracted the boot.img into the internal sd. Was then able to install image to boot partition. Rebooted and everything was exactly as it was 17 hours ago when my heart sank. Yay!
Click to expand...
Click to collapse
In fact I did the same I didn't menioned all the stuff with connecting to PC, copying files to PC, extracting archives and copying back to the phone the boot.img file for subsequent flashing via TWRP. This is because I know the forum members here are experienced guys
The lesson learned is that TWRP is rock solid and we shall trust to it
---------- Post added at 23:37 ---------- Previous post was at 23:36 ----------
Attila17 said:
How did you unzip the archive with TWRP?
Click to expand...
Click to collapse
See my last post. I didn't. I used a PC to do that.
I got really ****ed by magisk.
Did the recommended update and now I`m stuck at the fastboot screen
I can fastboot reboot but nothing else
how do I boot into twrp (power vol button down only brings fastboot)
I tried flashing twrp via fastboot but i get failed remote (unknow command)
any help please ?
Hello, I'm new here, so if I'm doing something wrong have mercy .
My 1+7Pro GM1913 is unlocked, rooted with Magisk (I think 22.1), TWRP 3.5.0_9-0-guacamole and OOS (last flashed version was 10.0.11.GM21BA considering I still have on the phone the OnePlus7ProOxygen_21.E.32_OTA_032_all_2101280020_c39273ef1f205b6.zip).
Last time I've flashed something I think was about a month ago, with the last update. No problem so far, until today. This morning my phone had problems with wifi, so I rebooted it.
From that moment on, it boots only to Fastboot Mode. I can get to TWRP and I can access my phone directories from the pc only from TWRP, every other mode makes my phone unreachable from usb, and installing or updating drivers doesn't work.
I would love to avoid any data loss or anything related to having to reinstall every 2FA I have.
I tried deleting everything from /data/adb/modules but nothing changed.
I looked around on XDA but I usually get people stuck on Fastboot only and accessible via usb, which is not my case.
So I was thinking about flashing the latest available OTA, then TWRP, then Magisk from TWRP but I'm not sure if it will works or just worsen my problem.
Has anyone had this problem before? Any idea about how to solve this?
Thanks for anyone willing to help me.
Have a nice day!
EDIT:
Solved flashing the full OTA.zip, twrp.zip, reboot and Magisk.zip after renaming the apk.
I think this will help you:
Twrp --> flash your boot.img (with "payload dumper" it can be extracted from the full OTA update file)
Then flash twrp.zip, reboot in to twrp, flash magisk.zip, wipe dalvik cache
Reboot and provit ;-)
Being a monday and everything, I'll write down what I've done so far, this way if anyone find this post with the same luck as mine maybe it will be less painful for him\her.
I followed this guide on XDA in merit of the "payload dumper" suggested by Ghost323 and followed the instruction on the Github page, which are:
google protobuf for
Code:
python pip install protobuf
Make you sure you have Python 3.6 installed.
Download payload_dumper.py and update_metadata_pb2.py
Extract your OTA zip and place payload.bin in the same folder as these files.
Open PowerShell, Command Prompt, or Terminal depending on your OS.
Enter the following command:
Code:
python -m pip install protobuf
and being my zip a full OTA
When that’s finished, enter this command:
Code:
python payload_dumper.py payload.bin
This will start to extract the images within the payload.bin file to the output folder you are in.
Click to expand...
Click to collapse
All good until the
Code:
python payload_dumper.py payload.bin
gave me a "no module named bdsiff4" error.
So I used
Code:
pip install bsdiff4
and turns out I'm missing Microsoft Visual C++ 14.0, which is absurd because I'm staring at it in my programs and I used it last week.
Anyway, one vs_BuildTools.exe, 12Gb downloaded and a reboot later, this time
Code:
pip install bsdiff4
works and the
Code:
python payload_dumper.py payload.bin
command finally starts.
Once that's done in the output folder I found the boot.img and made a copy into my phone root folder /.
At this point, I was looking for a flashable zip of Magisk, but I found out in a tweet dated 11:55 AM · Jan 22, 2021 that "the Magisk Manager APK *itself* is a custom recovery flashable zip", so back to Github to download the Magisk-v22.1.apk and copy that on the same root folder on my phone, following the instruction under the Magisk v22.0 updated installation guide. Under "Custom Recovery" it is written to rename the .apk into .zip.
On TWRP, Install, Install Image, and selected boot.img.
At that point I can choose between Boot, System Image, Vendor Image and Install Recovery Ramdisk.
But on the installation guide of Magisk is written "Never, ever try to restore either boot or recovery partitions back to stock! You can easily brick your device by doing so, and the only way out is to do a full Odin restore with data wipe."
So now I'm stuck. Please help.
Later I'll flash twrp-installer-3.5.2_9-0-guacamole.zip, reboot to TWRP and flash the Magisk-v22.1.zip.
You can install your full OTA update file in TWRP. Then install TWRP.zip. Restart into TWRP, install Magisk.zip (rename Magisk 22.1.apk to Magisk 22.1.zip). Wipe dalvik cache and reboot into the system.
That should work the same way. The main thing is that your Boot.img is fine again.
Both ways of mine should lead to the same success.
I wish you success.
Yes, flashing the full OTA, twrp, reboot and Magisk gave me back my phone.
However now my SafetyNet is having problems.
Thanks for the help!
Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?
Ork_77 said:
Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?
Click to expand...
Click to collapse
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?
Droidriven said:
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?
Click to expand...
Click to collapse
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.
Ork_77 said:
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.
Click to expand...
Click to collapse
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
...
Droidriven said:
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
Yes...this is exatcly what I did.
Method 2.
Ork_77 said:
Yes...this is exatcly what I did.
Method 2.
Click to expand...
Click to collapse
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.
Droidriven said:
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.
Click to expand...
Click to collapse
Hi Droidriven, thank you for your answers. Perhaps, synthesizing my steps too much, I gave the impression of not being particularly capable in computer science (you even tell me to press "enter" after commands ...). Well, let's say it's not my case.
All steps are performed correctly.
all steps end without errors.
No matter what I do, in the end Magisk appears as n / a, I don't have root, and the data connection doesn't work. Small addition about the latter aspect: when rebooting the wifi connection works for a variable time between 10 and 20 seconds, after which the network appears as without internet (or intranet) but the phone remains connected.
At the reboot, history repeats itself
Restoring the original boot everything returns to normal.
/* excuse windows person in advance for poor grammar */
TL;DR:
LG V20 H918
bootloader unlocked
bootable LOS19.1
no fastboot available
no recovery available
Goal: setup magisk using adb root shell
Is it possible?
What happend:
On stock LG V20 H918 no flashing was available in fastboot, probably done by manufacturer.
No stock recovery available as well.
I was able to unlock bootloader and install TWRP using "lafsploit".
Then I installed LOS 18.1 and Magisk with TWRP.
Everything worked perfectly.
Later I decieded to update to LOS 19.1, and probably forgot some step in the process.
LOS 19.1 boots and works OK, but without root/magisk. TWRP now stucks in splash screen.
I unable to install Magisk or restore backup without TWRP.
I unable to reflash TWRP without fastboot.
But I have acces to adb root shell!!!
So I thought it should be possible to repeat all changes Magisk does when patches boot.img, right?
I examined boot_patch.sh from magisk.akp, then compared original and patched img-s.
Waht I concluded magisk does:
1: create ".backup" folder in root
put there original "init" file
put there ".rmlist" file with what to remove on uninstall
put there ".magisk" file with checksum and other variables
2: create "overlay.d" folder in root
create "sbin" folder in "overlay.d"
put there same ".xz" files mentiond in ".rmlist"
3: perform some modifications to "init" file in root
Will it work if i repeat all this changes through shell?
Or do i need to do something else, like changing that checksum somwhere?
I have all this files from patched "boot.img", including that "init" file.
Is this a guide, or a question?
If this is a guide, you need to write it in such a way that others can easily follow it.
I don't know enough about LG devices to tell you whether you can accomplish what you're trying to do. From what I can see, rooting is extremely complicated. This is why I have a Pixel.
This is a question, I just atempted to give as much information as possible.
IMHO this sitiation should not be specific to this particular device.
In other words, is it possible to install magisk by "patching files" on booted system? (without re-flashing boot.img?)
I had to flash the lineage recovery to replace twrp when i installed the 19.1 rom. You can still install magisk using the lineage recovery.
If I recall however you can also patch the bootloader to install magisk through the installed magisk app itself aswell. As for the specifics of your question of installing it without patching of some way to the bootloader... ive no clue.
I was unable to install recovery, and there was no recovery when I got this phone with "stock ROM". thought it was done this way by oem.
Atempting to boot into recovery results in "brocken android icon" with "no command" text.
Yes, this is how I installed magisk first time: install app -> patch boot image in app -> then re-flash patched image with twrp.
My idea is to do all reqired changes manually, as we have root acces from adb shell:
As for now I mimicked difference betwen patched and original 'boot.img', which coresponds to "Ramdisk Patches" section of Magisk's "boot_patch.sh":
'.backup' and 'root/overlay.d/sbin' folders and their contents, init file and all permissions
Phone boots but no changes in magisk
Also added '99-magisk.sh' to /system/addon.d
It seem to launch, but no changes in magisk too.
Posting in case somebody will search for this.
For magisk to work some changes in kernel may be reqired. If kernel in patched boot image is different from original, then there is no solution this way.
Wiping cache and userdata can possibly fix TWRP bootloop, but If your fastboot unable to flash anything, then it probably also will be unable erase/format cache and userdata.
>>>!!! Backup first if you can, this will erase all your files and apps !!!<<<
Try to do hard factory reset this way, it helped in my case:
- Turn the phone off.
- Press and hold "Vol. down" + "Power btn"
- When LG logo appears, release "Power btn" for ~0.5sec. then push again
- Hold "Vol. down" + "Power btn" until hard reset menu appears.