Can not Extract Zip - Magisk

I've posted before/then it worked (once)/I deleted etc.
I read in another post to try to install busybox, I can not from the Manager.
I thought I'd screwed up the system R/W in TWRP (this is LineageOS 16.x on a Galaxy S5) but it is R/W.
It's not a critical thing, but does bug me. It's taken a month of twiddling everyday to get the phone JUST where I want it and everything working JUST the way I want them to - except this.
I've been looking for a zip of 19.3 (this did work fine with 18.x) to install via TWRP, but can not find one - I'm assuming that there might have been an error installing 19.x through the manager.
As I'm going to put the whole enchilada on my wifes phone this weekend (I REALLY don't need that to backfire ...), I'd like to figure this out. I have NOT tried installing the zips from recovery, but copied to a PC they are intact and the zip is not damaged.
MANY THANKS!

Related

Correct root and TWRP recovery for OOS 4.1.6 on OP3T - please.

I've been all over the OP3T forums looking for current information about the correct versions of TWRP and (Magisk or SuperSU) to use with stock OOS 4.1.6. I kept my old TWRP 3.0.4-1 and when I tried to apply SuperSU 2.79 SR3 I got an unusable system and had to restore from nandroid backup. I updated to TWRP 3.1.1-2 as per the Official TWRP app and now every time I try to reboot to system from TWRP it warns "No OS installed", but the reboot works fine. I have Magisk 13.2 ready to install but I'm reluctant until I know I have the right combination - the TWRP 3.1.1-2 backup is missing some partitions and I want to make sure I can at least recover my system if Magisk screws things up.
I've been all over the forums and all the relevant threads were closed months ago, or are written about OOS 4.0.3 or 4.1.1, or describes some hideous way someone turned their 3T into a pile of molten lava. Is there any current information about what combination of TWRP and a root zip will work with the latest OOS 4.1.6? Everything is stock except the unlocked bootloader. I don't want to flash a different ROM, I don't care about passing SafetyNet, I just want to root and go on with my life.
A couple of numbers is all I ask. I can't be the only one. Please - I've been without root for a week and it's bugging me.
TWRP 3.1.1-2 has got at least one major bug where it reports the OP3T as a OP3. That'll mess up your OP3T specific installations... Don't know if there are any other bugs, since I'm staying on 3.1.1-0 until they fix that bug. You also have the option of using blu_spark's TWRP. I've never tried it, but many users swears by it.
What works for me:
OOS 4.1.6
Franco Kernel r25
TWRP 3.1.1-0 (official)
Magisk v13.2
Magisk Manager 5.0.6
No issues whatsoever (for me)...
Thanks for that. I'd rather not change kernels, though. How likely is it that the same combination works with the stock kernel? Does anyone have that running?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
Scratch that request. Things seem to be turning around - su works in terminal emulator, lets me ls privileged directories like /data. Root Explorer is working again. The only thing that isn't is AdAway, which can't write the hosts file. Otherwise the system seems to be rooted and working OK.
I'm still nervous that TWRP can't see that there's an OS on the phone, and I haven't seen any other reports of this.
It looks like Magisk can't mount /system read-write. Adaway won't install, and neither will Busybox. Titanium Backup also reports problems. I tried installing Busybox and the installation failed when it tried to remount system /rw.
Will look for solutions to this problem and report back here.
I've found many solutions to this problem, like installing busybox (Stericson Busybox apparently doesn't work in OOS 4.1.6, tried two others. Problem is, busybox will only install into a partition on /system, which requires that /system be read/write.
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
JMB2K said:
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
Click to expand...
Click to collapse
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
mobilityguy said:
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
Click to expand...
Click to collapse
I seem to remember having that problem once before.... Can't recall what I did, I think it involved something with the terminal... I'm not at my desk right now, I'll look into it shortly and see if I can remember
Problem solved. The more I looked at the symptoms, the more I realized that the OTA I took after unrooting with SuperSU corrupted the system partition somehow. The first time I tried applying the OTA with the stock recovery it failed, but I was able to reboot and apply 4.1.6. That's when the trouble began - I was unable to reapply SuperSU. Fortunately I had done a nandroid backup between the upgrade and the attempt to re-root, and after the SuperSU script failed I was able to restore the backup (made and restored using TWRP 3.0.4-1) and continue working. It was either at that point or earlier, during the OTA itself, that /system was damaged - not badly enough to prevent the phone from working perfectly well, but enough to keep TWRP from mounting /system read/write. From that point on I was doomed. None of my other attempts to fix the problem had a chance as long as TWRP was restricted to mounting /system read-only. Then it got worse.
After a semi-failed attempt to install Magisk (rooted applications worked as long as they didn't try writing to /system) I restored my pre-root 4.1.6 backup one more time. After that, TWRP wouldn't mount /system at all, which prevented me from making any more nandroid backups.
It was time to act. I could keep using the phone unrooted, but the longer I went on the more work would be required to put things completely right. The risk would increase because I couldn't take any more snapshots of the phone to fall back to if I munged the device again. I also had a positive reason to fix things - during the two days the phone was rooted but couldn't access /system, Titanium Backup kicked in and did a full backup of all my software and settings.
With a damaged file system and full backups, there was no reason for halfway measures. I copied all my user data off the phone and used LloydSmallwood's unbrick tool to flash the phone back to its original OOS 3.5.4 state. That took care of rebuilding all file structures. As soon as I rebooted, OOS upgraded to 4.1.6 in one step, taking care of the system upgrade. Unlocked the bootloader, installed TWRP 3.1.1-0 (not 3.1.1-2, which has a serious bug for the 3T as someone posted above). I was able to mount and unmount /system from TWRP's mount screen, no problem. Ran Magisk 13.3 script without a problem, installed Titanium Backup, and tested an app restore. No problem. I'm now in the midst of copying all my stuff back onto the phone, after which I'll restore all missing apps and be back in business (I hope).
It's possible I could have done something tricky like reformatting /system and restoring the partition from my last good nandroid backup. But I always would have been concerned that problems would have popped up later, maybe during the Android O upgrade, when it would be way too late to recover my then-current setup. After seeing virtually every combination of working and non-working features, it just made sense to build from a clean system.
So thanks have been given to LloydSmallwood for his absolutely indispensable unbrick tool (this is the second time it has saved my phone). I should also thank my Galaxy S3, running the current build of LineageOS, which has gotten me through the two days it took to set my OnePlus straight. The Galaxy has performed better than a five year old phone running brand-new software should ever be expected to - if it supported LTE I could consider using it as a daily driver. This has been an education, and a reminder of how important it is to keep good backups at every step throughout an upgrade - and routinely during production use.
Thanks to all who gave advice in this thread.

Error 255: can not install rom(s)

Hi Guys!
I've just started customising the phone after receiving it Friday.
I've unlocked the bootloader and installed twrp.
But now when I try to install a rom, I get error 255 and the installation is terminated immediately.
I found two mentions of this error:
- Unmount partitions in twrp
- make a change to a text file inside the roms zip file before installing it
I unmounted all partitions except sd card, did not work.
I looked inside the textfile in the zip but could not find the line mentiond in the post I found (it was for a different phone)
So now I'm stuck.
I do have the phone running the stock rom again and it may even be rooted (installing magisk worked) but have to check after putting the backup back.
Any thoughts?
I have tried two versions of aospExtended and cosmic
Edit:
Maybe the stuff is still encrypted?
What twrp are you using?
Ah, maybe there is some sort of answer immediately, thanks for the quick reply.
I took it from this page from check yourscreen:
https://androidfilehost.com/?fid=889964283620777591
But now notice that ...9 is not the most recent.... I read 15 and 16 as 1.6
Will try again shortly.
Can I install the newer one through twrp or should I use fastboot?
EDIT: version 16 is working!
Thanks so much

Magisk cannot actually patch a boot image? [Galaxy S8/SM-G955F, Android 7.0]

Hello all,
Hope this isn't a needless duplicate, but I've done a fair amount of searching and I can't find that this question has been answered anywhere.
If I understand correctly, it should be possible to use a 100% stock phone to produce a patched boot.img which can then be flashed to that same phone? From the instructions in topjohnwu's main thread about Magisk, I'm lead to believe Magisk can "bootstrap" itself in this way:
1) Install Magisk Manager and copy a stock boot.img extracted from the OTA
2) Use the "Install" menu item to produce a patched_boot.img, which can then be lifted off the phone and used (with ODIN) to flash the phone.
I never get to item 2.
My MagiskManager says "Magisk is not installed" which is obviously true, however, the instructions seem to say one can proceed from there, and yet I can't see how. I've created an /sdcard/magisk folder and an /sdcard/MagiskManager folder and stuck a(n unpatched) boot.img file in either of them; as well, I've just stuck one in /sdcard/ for good measure (the "root" of user-accessible storage) And yet no go.
Am I misunderstanding something? Is the patching of the boot image supposed to be happening somewhere else than on the (stock) phone? Poking around, I see that topjohnwu's "Magisk" git tree includes something called "magiskboot", but that doesn't seem to be part of the Magisk Manager package.
TL;DR: From what topjohnwu writes, it's supposed to be possible to install Magisk WITHOUT having a custom recovery installed, but I cannot find a way to actually do it with the provided tools and instructions.
You need internet access to download the Magisk zip to patch the image. No internet - no install button...
Ouch. Thanks for the help, Didgeridoohan, that's the answer right there. I like to get my phones set up "just right", which includes getting root and then backup up and freezing various things (for example using Titanium Backup), before ever allowing the phone to go online for the first time and triggering connections and synchronisations and registrations of the tonnes and tonnes of shovelware crap that seems to come in with the tide on any modern smartphone these days.
Thanks for the explanation. I guess I can get it taken care of with SuperSU, freeze the things I don't like and then get my download happening in Magisk Manager. Then when I'm ready with my patched boot.img, I can re-flash the stock ROM.
Wouldn't be a terrible feature to be able to just set up the files MagiskManager expects to find so that this all could work in an offline configuration, though!
Tangib1e said:
Ouch. Thanks for the help, Didgeridoohan, that's the answer right there. I like to get my phones set up "just right", which includes getting root and then backup up and freezing various things (for example using Titanium Backup), before ever allowing the phone to go online for the first time and triggering connections and synchronisations and registrations of the tonnes and tonnes of shovelware crap that seems to come in with the tide on any modern smartphone these days.
Thanks for the explanation. I guess I can get it taken care of with SuperSU, freeze the things I don't like and then get my download happening in Magisk Manager. Then when I'm ready with my patched boot.img, I can re-flash the stock ROM.
Wouldn't be a terrible feature to be able to just set up the files MagiskManager expects to find so that this all could work in an offline configuration, though!
Click to expand...
Click to collapse
If you have another device, you can use that one to patch the boot.img. just put magisk manager and the stock boot.img on that one and patch it. Then move it to your PC for flashing in Odin. Make sure that, in the patched boot format settings in magisk manager, you select .tar for the format of the patched image.
Didgeridoohan said:
You need internet access to download the Magisk zip to patch the image. No internet - no install button...
Click to expand...
Click to collapse
The app should really display a message if the phone is offline

How to remove persistent /supersu dir from unrooted device?

Context: my motorola g4 is 5 years old and saw many different kinds of root attempts and amateurish handling (like modifying the system image) in its early days. I settled on magisk when it became a thing. Now I'm trying to go back to being rootless, including removing left-behind stuff like addon.d scripts.
TWRP shows a /supersu folder in the root fs, containing the usual apk, sh scripts, etc. I can delete this folder, but next time I boot my device (even just recovery!) it gets restored _somehow_. This is the only remaining trace of rooting I'm aware of, aside from the image just "not being untouched stock" anymore.
I'd like to get this folder permanently removed, without erasing my data.
Things I've tried:
- flash the stock rom: somehow it's defective (Package Installer crashes and I can't fix it by any means), despite it being the same zip I flashed two years ago and still use today, so this is not an option
- flashed stock boot
- unSU https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
- installed supersu just to run its own unroot procedure, then ran unsu again, then flashed stock boot again
It just keeps coming back after every time I delete it and I'm out of ideas to stop it. All the threads I've found online offered only the above solutions that don't work.
Thanks for any good tips
@Marnes That sounds like it's TWRP's superuser. It won't exist if you are not booted to TWRP and it'll be repopulated everytime you boot to TWRP...
@Didgeridoohan I hadn't considered that possibility... I guess there's no way to verify it since checking after a regular boot if the folder is there would require rooting again. Thanks for the input!

Finally A605FN with ROOTED Android 10 and WORKING lockscreen/keystore !!!

Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
You are amazing.... you did it MASTER.
IEarlyer i also tryed but I gived up.... when I made root I allways lost the encryption the keystore no screenlock etc ... that was unusable.
Another time I was able install working recovery but the system crashed allways. But now its perfect.
The only beauty flaw is the lack of custom roms for a6plus but now I can customize for myself.
Many respect.
Thanks for your kind words
respect and appreciation to you.
You are a true moddfanatic.
Its not about how to keep in use the old phones. Its a passion .
Im the same just lwith mouch less expertion.
Simce You solved this problem I quickly founf the next.
Thr Last 2 -3 ays II spend with a experiment to to open Sansung native callrecder. I tried mouch ways...
all Csc changers
Secret codes
and dparrser mode
wtth activity hacks
with disrcibe files edit
With an apps replacing from customrom.
Wasnnot good .Tomorrow I flash with Odin csc f
So thats what I told ya.
Really I never use this feature !!!!!!
But I can let away I WANT to solve
If a problem prevents you from doing what you imagined, it is unacceptable to us.
caiuse Its about our force in this doddned )mazrix
Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?
JulioM18 said:
Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?
Click to expand...
Click to collapse
This: https://github.com/mcmilk/7-Zip-zstd/releases
It is a moded version of 7zip with support for Zstandard. You need this to extract the boot.img from the firmware files.
Hope it helps
It works on Samsung A605GN. I just tested IT. Thanks!
The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
It's been so long since this forum was published, and recently I came across it, purely by chance, since I gave up trying to root my A6+ (A605GN). I tried endless tutorials and invested many hours of my time and rest, and here is my reward.
I am totally grateful for giving you the time to explain these steps in detail, and help the community that has this device (still) and can configure it to their liking.
A big hug and blessings. You have saved my life. <3

Categories

Resources