Hi,
I just updated my HW Mate 10 pro to the latest version which includes face recognition. It worked as expected until I rooted the phone with FHMate10Tool. I tried using another method called Magisk but I got an error when trying to apply it through TWRP so I couldnt proceed with this method.
Anyways, after rooting, I get an error saying that my facial features werent recognized, in simple words, front camera wont open, therefore, it wouldnt work.
I even tried to unroot but even after doing factory reset, I can't seem to make it work.
Any thoughts? Please see PS below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for your help!
What your version and model? Mine work fine with magisk root.
maxkento said:
What your version and model? Mine work fine with magisk root.
Click to expand...
Click to collapse
Thanks for your reply.
Model: BLA-L29
Build Number: BLA-L29 8.0.0.135(C605)
EMUI Version: 8.0.0
The weird thing is that I ran a factory reset to remove any root stuff and I still cannot use the face unlock feature due to the error mentioned above.
I had the phone rooted and bootloader unlocked and worked until I rooted the phone.
jeinnerabdel said:
Thanks for your reply.
Model: BLA-L29
Build Number: BLA-L29 8.0.0.135(C605)
EMUI Version: 8.0.0
The weird thing is that I ran a factory reset to remove any root stuff and I still cannot use the face unlock feature due to the error mentioned above.
I had the phone rooted and bootloader unlocked and worked until I rooted the phone.
Click to expand...
Click to collapse
Is this the original firmware or you rebrand the rom?
Hi, I am on BLA-L29 800142(C432)stock & rooted phone with Magisk V16. Face unlock still running without any problems. Maybe it has something to do with the FH rooting tool?
maxkento said:
Is this the original firmware or you rebrand the rom?
Click to expand...
Click to collapse
Original firmware. OTA update.
How your stock camera? Does that work with the front facing?
jeinnerabdel said:
Thanks for your reply.
Model: BLA-L29
Build Number: BLA-L29 8.0.0.135(C605)
EMUI Version: 8.0.0
The weird thing is that I ran a factory reset to remove any root stuff and I still cannot use the face unlock feature due to the error mentioned above.
I had the phone rooted and bootloader unlocked and worked until I rooted the phone.
Click to expand...
Click to collapse
It's because of FH Root tool.
Download your stock ramdisk from here: https://mega.nz/#!BWxElaRA!lUb-u-jXaPSAN8OrbyG4tEKCWttvqPxMPOVBn6h1PRY
Then flash it using 'fastboot flash ramdisk RAMDISK_BLA-L29C605B135.img'
Then flash Magisk from TWRP.
Factory reset only resets /data, root is kept in your ramdisk (Well. App is kept in /data, but it's just an app.)
maxkento said:
How your stock camera? Does that work with the front facing?
Click to expand...
Click to collapse
Yes, both cameras work as expected. The only flaw is for the face recognition for unlock.
ante0 said:
It's because of FH Root tool.
Download your stock ramdisk from here: https://mega.nz/#!BWxElaRA!lUb-u-jXaPSAN8OrbyG4tEKCWttvqPxMPOVBn6h1PRY
Then flash it using 'fastboot flash ramdisk RAMDISK_BLA-L29C605B135.img'
Then flash Magisk from TWRP.
Factory reset only resets /data, root is kept in your ramdisk (Well. App is kept in /data, but it's just an app.)
Click to expand...
Click to collapse
Thanks for your help on this. I just flashed the ramdisk as you told me to. By any chance, do you have the URL to instructions to root with this method? Ive found a few but they dont seem to work for me.
Thanks once again!
jeinnerabdel said:
Thanks for your help on this. I just flashed the ramdisk as you told me to. By any chance, do you have the URL to instructions to root with this method? Ive found a few but they dont seem to work for me.
Thanks once again!
Click to expand...
Click to collapse
Flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Flash Magisk 16 in twrp: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or get the 16.4 beta: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
That's all there is to it
ante0 said:
Flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Flash Magisk 16 in twrp: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or get the 16.4 beta: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
That's all there is to it
Click to expand...
Click to collapse
I just confirmed that after adding the boot image you provided, I get an error stating that there's no boot image (error when trying to get into recovery mode). The good thing is that the phone can boot normally to Android, it just freaked the cr#p out of me!
jeinnerabdel said:
I just confirmed that after adding the boot image you provided, I get an error stating that there's no boot image (error when trying to get into recovery mode). The good thing is that the phone can boot normally to Android, it just freaked the cr#p out of me!
Click to expand...
Click to collapse
It's the stock ramdisk for your firmware, so it shouldn't cause any problems. However, if you have no recovery_ramdisk or it's incorrect it wouldn't be able to get to recovery.
Flash twrp using fastboot flash recovery_ramdisk twrp.img
ante0 said:
It's the stock ramdisk for your firmware, so it shouldn't cause any problems. However, if you have no recovery_ramdisk or it's incorrect it wouldn't be able to get to recovery.
Flash twrp using fastboot flash recovery_ramdisk twrp.img
Click to expand...
Click to collapse
Thanks! Yeah, apparently the ramdisk doesnt belong to this phone. I was able to install TWRP. I'm following the guides you provided as I type this. Let me go through these and I'll get back with you!
It works now! The problem I was having is that I tried installing the Magisk from TWRP as ZIP (which this time I couldnt find anywhere on the phone after copying it via graphical interface in android) so I just ran this command:
adb sideload Filepath\Magisk.zip
This installed Magisk on my home screen and I applied the patch from the app. I rebooted and voilá! it works now. It even had the previous configuration already applied, it recognized my face without even setting it up again.
As the phone was already rooted, Im not sure if this app really roots the phone as it didnt require a factory reset as other methods do, but the issue is now fixed!
Thank you for your support on this matter!
jeinnerabdel said:
It works now! The problem I was having is that I tried installing the Magisk from TWRP as ZIP (which this time I couldnt find anywhere on the phone after copying it via graphical interface in android) so I just ran this command:
adb sideload Filepath\Magisk.zip
This installed Magisk on my home screen and I applied the patch from the app. I rebooted and voilá! it works now. It even had the previous configuration already applied, it recognized my face without even setting it up again.
As the phone was already rooted, Im not sure if this app really roots the phone as it didnt require a factory reset as other methods do, but the issue is now fixed!
Thank you for your support on this matter!
Click to expand...
Click to collapse
It does not require a factory reset. That was only needed before when TWRP couldn't decrypt phone, and it can now thanks to zxz0o0 and Pretoriano80. Then you had to Format Data to flash as Magisk installs some things to /data (contrary to what I said earlier, but it does need to patch ramdisk to function ). SuperSU only places its apk in /data/ while the rest lives in ramdisk.
Related
Heres the latest update from LG.
Must be at least 20f/g with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/showthread.php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
Includes new 20H modem.
**********************
FLASHING INSTRUCTIONS
**********************
1. WARNING, MUST BE IN 20F/G. IF ON LINEAGE, DO NOT FLASH. YOU MUST KDZ TO 20F OR RESTORE 20F BACKUP FIRST.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20H-Stock-Rooted.zip
https://www.androidfilehost.com/?fid=745425885120726661
Sent from my LG-V521 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does it include the modem?
I'm going to try from lineage.
Edit -flashed from lineage worked fine. It rebooted straight from twrp so i wasn't sure if the flash comppeted. After waiting at bootscreen i still wasn't sure so i did the volume down, power button combo and it booted into system fine.
Edit 2 - no root and loss twrp
Airtioteclint said:
Does it include the modem?
I'm going to try from lineage.
Edit -flashed from lineage worked fine. It rebooted straight from twrp so i wasn't sure if the flash comppeted. After waiting at bootscreen i still wasn't sure so i did the volume down, power button combo and it booted into system fine.
Edit 2 - no root and loss twrp
Click to expand...
Click to collapse
Lineage always messes up going back to stock roms. I've had this problem to on 20g to after being on lineage. You'll have to kdz to 20f and get twrp. I had put this on the flashing instructions you must be on 20f/g. .
It does include modem.
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Lineage always messes up going back to stock roms. I've had this problem to on 20g to after being on lineage. You'll have to kdz to 20f and get twrp. I had put this on the flashing instructions you must be on 20f/g. .
It does include modem.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Yeah kdz 20f and was able to get root back. Reinstalled your 20h and everything's working flawlessly. I was having problems with my touchscreen being a little laggy and I think your rom fixed it. :good:
Any way to install this update from SD card on stock recovery? I get error Everytime the regular way. Thanks
Hawksronny said:
Any way to install this update from SD card on stock recovery? I get error Everytime the regular way. Thanks
Click to expand...
Click to collapse
Impossible.
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Impossible.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
So even though there is an option to update from SD in stock recovery, it's impossible? Just want to confirm. Just doesn't make sense to me
Hawksronny said:
So even though there is an option to update from SD in stock recovery, it's impossible? Just want to confirm. Just doesn't make sense to me
Click to expand...
Click to collapse
Then try it! lol
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Then try it! lol
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
I'm no developer. I just want to update without rooting or custom recovery. I try it 2 ways, and fails the normal way, and the stock recovery doesn't recognize the update.zip the 2nd way. I probably have it named wrong. Either way, I doubt it's impossible. Any help would be appreciated. Thanks
Hawksronny said:
I'm no developer. I just want to update without rooting or custom recovery. I try it 2 ways, and fails the normal way, and the stock recovery doesn't recognize the update.zip the 2nd way. I probably have it named wrong. Either way, I doubt it's impossible. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Its very, very impossible to flash this rom except per twrp.
LG uses security keys to flash anything from stock recovery.
Sent from my SM-G955U using Tapatalk
I don't want to flash a rom. I asked how to flash the stock update from the stock recovery because the update errors out when I try to do it the normal ota way. There is an option to update from SD in the stock recovery. It's just that it doesn't recognize the stock update.zip in the stock recovery because I probably don't have it named right. Was just wondering if anyone knew what to name it, where to download the update.zip, how to update with it etc. Didn't mean to offend anybody ?
Hawksronny said:
I don't want to flash a rom. I asked how to flash the stock update from the stock recovery because the update errors out when I try to do it the normal ota way. There is an option to update from SD in the stock recovery. It's just that it doesn't recognize the stock update.zip in the stock recovery because I probably don't have it named right. Was just wondering if anyone knew what to name it, where to download the update.zip, how to update with it etc. Didn't mean to offend anybody ?
Click to expand...
Click to collapse
No offence taken. All good. You just can't do that. [emoji4]
Sent from my SM-G955U using Tapatalk
Should i be able to downgrade from 20h to 20 f to root. I just got a new one on a warranty exchange and get an error in lgup at 4%. Sorry if this is off topic
same question, some body can check antirollback, this tab can downgrade from v521 v20h to v20f or mashmallow or not
Thanks
[ROM] T-Mobile LG G Pad X V521 20i Stock ROM Rooted TWRP\FF Backups Release 7/1/2017
A TWRP backup of a stock rooted v52120i:
Code:
https://drive.google.com/file/d/0B6L7kMY8TK7uZ2lPMUhtVmRINUk/view?usp=sharing
FlashFire Restore from backup:
Code:
https://drive.google.com/file/d/0B6L7kMY8TK7uQlFfY3lJTVl1X1k/view?usp=sharing
To install, move files to designated place (twrp/backups/{phoneid}/) or (FlashFire/backups).
at least 20f and root required.
saw nobody put it up so i decided i would.
Mine still has rooted 10c. How to update to this latest ROM and rooted ? TIA
Does 7.0 improve idling/sleeping battery ?
Yes that is probably one of its biggest changes vs MM.
Follow this guide to a T: https://forum.xda-developers.com/lg-g-pad-83/development/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
then boot into recovery, copy my TWRP backup to internal/microsd/usb, in TWRP restore the system and boot partitions that are automatically checked.
Download the latest systemless or system mode supersu.zip and copy it to the main install folder C:\Program Files x86\Minimal ADB and Fastboot\.
Then in twrp click ADB sideload > do not check anything to erase > open minimal adb/fastboot and type adb sideload whateveryounamedyoursupersuzipfile.zip and you should be good to go.
Shockey0710 said:
Yes that is probably one of its biggest changes vs MM.
Follow this guide to a T: https://forum.xda-developers.com/lg-g-pad-83/development/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
then boot into recovery, copy my TWRP backup to internal/microsd/usb, in TWRP restore the system and boot partitions that are automatically checked.
Download the latest systemless or system mode supersu.zip and copy it to the main install folder C:\Program Files x86\Minimal ADB and Fastboot\.
Then in twrp click ADB sideload > do not check anything to erase > open minimal adb/fastboot and type adb sideload whateveryounamedyoursupersuzipfile.zip and you should be good to go.
Click to expand...
Click to collapse
how did u get 20i ? and got it into permissive mode to obtain root ? know anything about 20h/i changelog ?
abced123 said:
how did u get 20i ? and got it into permissive mode to obtain root ? know anything about 20h/i changelog ?
Click to expand...
Click to collapse
i havent found a changelog nor have i looked though but new kernel version and various security fixes tho, and yes its getenforce permissive. from tmobile fota.
Can I use this in LG-V500???
This is the LG G6's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Good Job!
TheWolfSVK said:
Good Job!
Click to expand...
Click to collapse
Thanks, have you tried it?
mauronofrio said:
Thanks, have you tried it?
Click to expand...
Click to collapse
Downloading it atm
Anyone tried this on LG G6?
This can relock G6 bootloader like for warranty purpose?
Which functions are available/unavailable for G6
The only functions that are not available are flash stock recovery and flash factory image. The others are all available. Locking the bootloader you can brick your phone, the tool will send just a fastboot command. I've tested the bootloader unlocking procedure for lg g6 and twrp flash. There are a lot of others function that i've not tested but they should work (Apk Installer, reboot commands, zip flasher, ....)
mauronofrio said:
The only functions that are not available are flash stock recovery and flash factory image. The others are all available. Locking the bootloader you can brick your phone, the tool will send just a fastboot command. I've tested the bootloader unlocking procedure for lg g6 and twrp flash. There are a lot of others function that i've not tested but they should work (Apk Installer, reboot commands, zip flasher, ....)
Click to expand...
Click to collapse
Hello, sorry i'm a noob at G6 (just got it last week) i came from an easy to unlock/flash Nexus 5X, i have some questions, do i still need the LG Develpoer site to unlock bootloader? or is this done internally in your program?
outlawman007 said:
Hello, sorry i'm a noob at G6 (just got it last week) i came from an easy to unlock/flash Nexus 5X, i have some questions, do i still need the LG Develpoer site to unlock bootloader? or is this done internally in your program?
Click to expand...
Click to collapse
You always need the LG Developer site. This tool is done to simplify processes not to bypass them. With this tool you will never use the terminal anymore.
mauronofrio said:
You always need the LG Developer site. This tool is done to simplify processes not to bypass them. With this tool you will never use the terminal anymore.
Click to expand...
Click to collapse
oh, thank you will try it out when i decide to unlock and flash some custom roms ;D still quite happy with the stock rom it came with ...OR maybee when there is a working option for locking the bootloader, but i guess we will have to wait for that for some time ...
outlawman007 said:
oh, thank you will try it out when i decide to unlock and flash some custom roms ;D still quite happy with the stock rom it came with ,or maybee when there is a working option for locking the bootloader, but i guess we will have to wait for that for some time...
Click to expand...
Click to collapse
The command is there but you can brick your phone. I think you need of a QFIL stock rom to relock bootloader. But i think Lg has a database with all device unlocked...
Awsome tool!
It would be cool if we could lock the bootloader without fear of the dreaded brick
tron4200 said:
It would be cool if we could lock the bootloader without fear of the dreaded brick
Click to expand...
Click to collapse
Yes sure, when there will be a safe guide, it will also be safe to lock the bootloader
Will give this a try once someone has tried it some more.
Just tried to unlock my g6. It works. Then I tried to flash recovery, but, maybe I'd have had to reboot phone prior to flash recovery, infact after reboot the recovery installed was the stock one. So I flashed it via fastboot command manually...
Anyway, simple and working. Gread job!
galerio said:
Just tried to unlock my g6. It works. Then I tried to flash recovery, but, maybe I'd have had to reboot phone prior to flash recovery, infact after reboot the recovery installed was the stock one. So I flashed it via fastboot command manually...
Anyway, simple and working. Gread job!
Click to expand...
Click to collapse
Thanks for feedback, can you please tell me what recovery you have installed through fastboot?? Maybe the recovery in the tool ai wrong or have problems.
Have tried the H870 one, TWRP 3.1.1, the one that the software automatically download from server. The final message saied it was installed correctly, but after reboot, normal recovery was presented (the one that reset phone to factory reset, and infact it has resetted the phone)
---------- Post added at 01:34 PM ---------- Previous post was at 01:15 PM ----------
mauronofrio said:
Thanks for feedback, can you please tell me what recovery you have installed through fastboot?? Maybe the recovery in the tool ai wrong or have problems.
Click to expand...
Click to collapse
Maybe the problem was not your software... Now that I am in twrp I have transferred a rom in the internal storage, I have installed it, but phone is in bootloop. And now, entering in twrp it says the storage is encrypted and asks me for the password.... now, what to do??? Damn...
galerio said:
Have tried the H870 one, TWRP 3.1.1, the one that the software automatically download from server. The final message saied it was installed correctly, but after reboot, normal recovery was presented (the one that reset phone to factory reset, and infact it has resetted the phone)
---------- Post added at 01:34 PM ---------- Previous post was at 01:15 PM ----------
Maybe the problem was not your software... Now that I am in twrp I have transferred a rom in the internal storage, I have installed it, but phone is in bootloop. And now, entering in twrp it says the storage is encrypted and asks me for the password.... now, what to do??? Damn...
Click to expand...
Click to collapse
Format data from twrp
@mauronofrio Ok, I solved and reinstalled from scratch everything. What went wrong, I think, is that after TWRP installation I haven't installed Magisk immediately.
Using a tool like your can induce people to just push a button and not follow every step of a good unlocking procedure. Anyway, it was my fault. Your tool works perfectly
I receive this Android 10 update,update succeeded,but after installing Magisk,my Mi 8 stick to fastbootmode no matter how it restarted.And after some reboots,twrp recovery is not able to decrypt data anymore,so it bricked.
Luckily before bricked,I had revert it back to miui_MI8Global_V10.3.5.0 by Twrp recovery en somehow after wipe data used stock recovery it come to live again.
So anyone has any idea,how to install Magisk without problem.
Magisk version used latest 20.3.
Twrp recovery boot by fastboot boot command.
sm1232 said:
I receive this Android 10 update,update succeeded,but after installing Magisk,my Mi 8 stick to fastbootmode no matter how it restarted.And after some reboots,twrp recovery is not able to decrypt data anymore,so it bricked.
Luckily before bricked,I had revert it back to miui_MI8Global_V10.3.5.0 by Twrp recovery en somehow after wipe data used stock recovery it come to live again.
So anyone has any idea,how to install Magisk without problem.
Magisk version used latest 20.3.
Twrp recovery boot by fastboot boot command.
Click to expand...
Click to collapse
I don't have time to customise instructions for your exact issue.
But you can gleen the majority of what you need to do by following my instructions here: https://xiaomi.eu/community/threads/9-12-19.53895/post-521845 Note : Ensure that you are using latest canary, and follow the instructions precisely in regard to passwords. Next, these instructions are how to not have issues when updating.
You are probably past the point of repairing permissions, so if you do not have a backup of your previous systems boot image, you will most likely need to format user data and start clean. Finally these instructions assume that your bootloader is unlocked.
sm1232 said:
I receive this Android 10 update,update succeeded,but after installing Magisk,my Mi 8 stick to fastbootmode no matter how it restarted.And after some reboots,twrp recovery is not able to decrypt data anymore,so it bricked.
Luckily before bricked,I had revert it back to miui_MI8Global_V10.3.5.0 by Twrp recovery en somehow after wipe data used stock recovery it come to live again.
So anyone has any idea,how to install Magisk without problem.
Magisk version used latest 20.3.
Twrp recovery boot by fastboot boot command.
Click to expand...
Click to collapse
Flash Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip after Magisk
Bortex19 said:
Flash Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip after Magisk
Click to expand...
Click to collapse
As I mentioned he is well past fixing permissions, unless he has the linked boot image that he can reflash. Even then, there would be permission issues. DM verity will not help.
The solution is to use Magisk Canary and follow the instructions that I linked.
Remove passwords.
Extract the boot image,
place in downloads folder,
patch boot image,
boot to recovery and flash Canary magisk . Done
I had the same problem and solved it by flashing dm-verity; It is probably easier and more convenient to try this first and, if it does not work, continue with the rest of the instructions
fixed
thanks for replies.
I use the patch bootimage methode all the time,had never problem with Android 9 (Pie).
Problem only occurs on Android 10.
Fixed:
Factory reset (all data lost),data partition empty.
Flash Magisk.zip by Twrp recovery.
clean dalvik-cache.
reboot,done.
I will try the patch bootimage methode on next Android 10 update.
sm1232 said:
thanks for replies.
I use the patch bootimage methode all the time,had never problem with Android 9 (Pie).
Problem only occurs on Android 10.
Fixed:
Factory reset (all data lost),data partition empty.
Flash Magisk.zip by Twrp recovery.
clean dalvik-cache.
reboot,done.
I will try the patch bootimage methode on next Android 10 update.
Click to expand...
Click to collapse
Hi,
I have only one question: after every update must I do every time factory reset?
slave2007 said:
Hi,
I have only one question: after every update must I do every time factory reset?
Click to expand...
Click to collapse
Till now I don't know ,when the next Android 10 update comes,I will try it and tell you the result.
sm1232 said:
Till now I don't know ,when the next Android 10 update comes,I will try it and tell you the result.
Click to expand...
Click to collapse
Thanks, I hope it is enough one times?
great news
slave2007 said:
Thanks, I hope it is enough one times?
Click to expand...
Click to collapse
Today I receive miui_MI8Global_V11.0.3.0.QEAMIXM update.
Use my method installing Magisk,works without problem.
Hope come true,did it WITHOUT FACTORY RESET.
:laugh:
sm1232 said:
Today I receive miui_MI8Global_V11.0.3.0.QEAMIXM update.
Use my method installing Magisk,works without problem.
Hope come true,did it WITHOUT FACTORY RESET.
:laugh:
Click to expand...
Click to collapse
??
"your method" is dirty install, wipe cache and perhaps install "disable DM verity too? ?
slave2007 said:
??
"your method" is dirty install, wipe cache and perhaps install "disable DM verity too? ?
Click to expand...
Click to collapse
I do not need to install disable dm-verity to avoid bootloop or so.
After format my data partition,used my method installing Magisk,reboot everything works fine.In Magisk manager only keep avb 2.0 dm-verity ticked by default.
After system encrypts the data partition,because Xposed framework Magisk module cause bootloops,I uninstall Magisk used Magiskuninstaller.zip and install Magisk again.After booted in system,in Magisk manager also keep encryption ticked by default.
I guess author of Magisk has done all the works for us to make Magisk works properly automatically. :good:
sm1232 said:
Today I receive miui_MI8Global_V11.0.3.0.QEAMIXM update.
Use my method installing Magisk,works without problem.
Hope come true,did it WITHOUT FACTORY RESET.
:laugh:
Click to expand...
Click to collapse
v11.0.3.0 come out already?? im stuck at v11.0.1.0..
Actually 11.0.6.0 already
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 8 using Tapatalk
That is Android 9 based...
fidows said:
Actually 11.0.6.0 alreadyView attachment 4946525
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
last timr mi 8 got android 10 update, there revert version to 11.0.1.0.. based on Q.. so latest version is 11.0.3.0 for Q, and 11.0.6.0 for Pie..
Twrp is not for galaxy tab a7 lite please i need a rom and twrp for this tablet. Thanks for watch this discussion.
It is a new device it will take some time to get someone to port it for Tab A7. Similar issues were happending with my galaxy A12 which had no custom recovery builds.
One ui core is phenomenal as it is, no offense to Samsung but I do believe that lineage OS or any other stock android OS would somehow increase the performance even more, battery life should may or may not change as it's great already!
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
Hey man that's great. I'm here for it I'll be the first one to try
Could anyone please kindly guide me how to unlock boot loader and root SM-T225.
Thanks in advance.
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
I too have a Tab A7 lite SM-T220 (rooted with Magisk) and cannot find any custom recovery anywhere ;( , if found would flashing say twrp on an already patched Magisk root cause unroot? Peace
vertab7 said:
I too have a Tab A7 lite SM-T220 (rooted with Magisk) and cannot find any custom recovery anywhere ;( , if found would flashing say twrp on an already patched Magisk root cause unroot? Peace
Click to expand...
Click to collapse
.
kzhtun said:
Could anyone please kindly guide me how to unlock boot loader and root SM-T225.
Thanks in advance.
Click to expand...
Click to collapse
.
ramz.pa said:
Hey man that's great. I'm here for it I'll be the first one to try
Click to expand...
Click to collapse
let me know if you find a solution. i want to root.
cewrik said:
.
I used
.https://forum.xda-developers.com/t/guide-sm-t500-t505-galaxy-tab-a7-10-4-unlock-bootloader-root-with-magisk.4185993/
Click to expand...
Click to collapse
method but with SM-T220 specific software NOT the
SM-T500/T505 software, it worked for me
cewrik said:
let me know if you find a solution. i want to root.
Click to expand...
Click to collapse
vertab7 said:
method but with SM-T220 specific software NOT the
SM-T500/T505 software, it worked for me
Click to expand...
Click to collapse
Can you help me, I sent you a private message.
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
Is there a procedure link for rooting by using the Magisk patched AP method and to unlock the bootloader? Thanks in advance!
I tried a lot but still like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cewrik said:
I tried a lot but still like this
View attachment 5488719
Click to expand...
Click to collapse
What version of magisk are you on?
Did you try Universal SafetyNet Fix?
kzhtun said:
Could anyone please kindly guide me how to unlock boot loader and root SM-T225.
Thanks in advance.
Click to expand...
Click to collapse
Check out these guides out. The steps are mostly similar for recent Samsung tablets,
https://forum.xda-developers.com/t/guide-unlock-the-tab-s7-bootloader.4158841/
https://forum.xda-developers.com/t/how-to-root-galaxy-tab-s7-guide.4155897/page-5
xpdragon said:
What version of magisk are you on?
Did you try Universal SafetyNet Fix?
Click to expand...
Click to collapse
v23
what is this ?? Universal SafetyNet Fix
cewrik said:
v23
what is this ?? Universal SafetyNet Fix
Click to expand...
Click to collapse
It is another way to check SafetyNet. Can no longer check SafetyNet directly from latest version of Magisk Canary
xpdragon said:
It is another way to check SafetyNet. Can no longer check SafetyNet directly from latest version of Magisk Canary
Click to expand...
Click to collapse
I want to use xposed. I need full authorization.
R0GUEEE said:
Rooting itself is incredibly easy, just use the Magisk patched AP method after you unlock the bootloader.
As for custom recoveries. I've been working on it for a bit trying to port a working build, but as of this moment the only thing I have is a successful Odin flash with no actual TWRP boot (It just hangs at the "phone is not running Samsung official firmware" indefinitely, not an actual loop). Of course even with the broken recovery flashed, I can still boot to system, so I dunno.
But if anyone wants to give a fresh set of eyes and see if I've missed anything, I've attached a zip of the odin-ready recovery.img and the decompiled twrp build. Just let me know.
TLDR: For anyone just glancing over this, this IS NOT a working TWRP port
Click to expand...
Click to collapse
Have you made any headway? I also spent a significant amount of time attempting to port TWRP. I was able to get TWRP to boot but touch did not work. Plugging in a mouse to a usb dongle, I was about to navigate TWRP but I was not able to do much. I had probelms mounting and editing the DATA partition. Im guessing it was an FSTAB config or an android 11 partitioning problem. I'm pretty fresh to this stuff but still made some progress. I gave up a bit ago but maybe I'll mess around with it a bit more.
tagcart said:
Have you made any headway? I also spent a significant amount of time attempting to port TWRP. I was able to get TWRP to boot but touch did not work. Plugging in a mouse to a usb dongle, I was about to navigate TWRP but I was not able to do much. I had probelms mounting and editing the DATA partition. Im guessing it was an FSTAB config or an android 11 partitioning problem. I'm pretty fresh to this stuff but still made some progress. I gave up a bit ago but maybe I'll mess around with it a bit more.
Click to expand...
Click to collapse
vbmeta or multidisabler flash is required ? . i tried porting twrp from xda guide for all devices. using stock recovery img ang google pixel twrp . all i got was bootloop .
Can i flash by dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery or odin method only works ?
AddictedA1 said:
vbmeta or multidisabler flash is required ? . i tried porting twrp from xda guide for all devices. using stock recovery img ang google pixel twrp . all i got was bootloop .
Can i flash by dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery or odin method only works ?
Click to expand...
Click to collapse
Once booted to twrp, I wasnt able to flash multidisabler because DATA wasnt mountable. In my case, flashing with Odin worked. Unfortunately the linux vm I did all this work on died so I lost all my progress.
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !