Related
While I tried to root using TWRP and all the suggested ways i continued to get errors, bootloops, corrupted boot, etc. I downloaded the rooted developers OS Image, then used magisk to patch the boot image. If anyone has any interest in the Boot.img or the developers OS image, let me know i can post links and instructions if needed. This will require the bootloader unlocked (i have read you can unlock with a keyboard, but i never had any luck and used a controller). Please reply with requests if needed.
Just one question: When you install the NEXT developer image, how will you go about retaining Magisk and your boot.img patch? Don't need a step-by-step-- just in simple terms. Curious.
EDIT: Found my answer: https://forum.xda-developers.com/showpost.php?p=77162700&postcount=85
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
laharl_22 said:
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
Click to expand...
Click to collapse
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Michajin said:
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Click to expand...
Click to collapse
Thanks it work
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
laharl_22 said:
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
Click to expand...
Click to collapse
I am assuming you have a nvidia shield 2017
Download the full image from nvidia here
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
Connect via fastboot (plug in controller press A - B and power on)
From fastboot connect with a computer via A-A usb cable
unzip the file from nvidia into the folder where your fastboot drivers are
run the flash-all.bat file
Michajin said:
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
Click to expand...
Click to collapse
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
samjoandco said:
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
Click to expand...
Click to collapse
As far as i know Unlocking erases data anyways. You unlock you have to reinstall everything anyways.
The boot image works only on developer image? Thanks
gas80 said:
The boot image works only on developer image? Thanks
Click to expand...
Click to collapse
I don't know what the differences are between the dev image and the regular version. I believe the dev version is just pre-rooted. I think it will work, but i have only tested on the dev image. Flash at your own risk.
Hi there,
I need help. Im looking for a ROM thats flashable with TWRP so i can install it. Previously I had Lineageos installed but it wasnt running smooth enough.
I cant install the rooted recovery file from Nvidia with TWRP.
The reason why im wanting to use TWRP is because i want to use Magisk with the Shield.
Ive allready patched a stock boot image with magisk version 17.1
my current Twrp version is 3.2.1-1
Thank you very much
cheers
[Edit]
I solved the problem by following this post
thanks
Michajin said:
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
Click to expand...
Click to collapse
Could you please upload it on google drive. That would be greatly appreciated. :good:
gambaaa said:
Could you please upload it on google drive. That would be greatly appreciated. :good:
Click to expand...
Click to collapse
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
Goodluck,
Michajin
Michajin said:
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
https://drive.google.com/open?id=15sJ6YFmwiAZX0mXQk_ANq5Nfvs9E8oJF
Goodluck,
Michajin
Click to expand...
Click to collapse
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
gambaaa said:
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
Click to expand...
Click to collapse
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Michajin said:
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Click to expand...
Click to collapse
Wonderful! Thanks for the explanation!
TWRP Official Recovery for A20 and A20e
Developed and maintained by @Topser99
SM-A205xxx
Download TWRP for a20
Download TWRP Open Recovery for a20
dl.twrp.me
SM-A202F/K
Download TWRP for a20e
Download TWRP Open Recovery for a20e
dl.twrp.me
Also available for installation via the Official TWRP app from Playstore
Hmm, https://dl.twrp.me/a20dd/ leads me to a 404 error. Any new link?
CawfeeOG said:
Hmm, https://dl.twrp.me/a20dd/ leads me to a 404 error. Any new link?
Click to expand...
Click to collapse
Found the new link I believe: https://dl.twrp.me/a20
However no matter what I try, I am getting an error after flashing in Oodin and trying to reboot to recovery manually.
The error is in download mode:
Code:
Recovery: Error validating footer. (Something cut off here because of the A20's front camera)
CUSTOM RECOOVERY
VBMETA A205WVLS7BUA1, 37649171R
Any idea how to proceed? I'm flashing AP via the .tar version of TWRP in Odin from stock Android Q for my region
CawfeeOG said:
Found the new link I believe: https://dl.twrp.me/a20
However no matter what I try, I am getting an error after flashing in Oodin and trying to reboot to recovery manually.
The error is in download mode:
Code:
Recovery: Error validating footer. (Something cut off here because of the A20's front camera)
CUSTOM RECOOVERY
VBMETA A205WVLS7BUA1, 37649171R
Any idea how to proceed? I'm flashing AP via the .tar version of TWRP in Odin from stock Android Q for my region
Click to expand...
Click to collapse
@Topser99
CawfeeOG said:
Found the new link I believe: https://dl.twrp.me/a20
However no matter what I try, I am getting an error after flashing in Oodin and trying to reboot to recovery manually.
The error is in download mode:
Code:
Recovery: Error validating footer. (Something cut off here because of the A20's front camera)
CUSTOM RECOOVERY
VBMETA A205WVLS7BUA1, 37649171R
Any idea how to proceed? I'm flashing AP via the .tar version of TWRP in Odin from stock Android Q for my region
Click to expand...
Click to collapse
If you can't extract and re-compress the files yourself, then you don't have to use them, and that's my opinion.
Topser99 said:
If you can't extract and re-compress the files yourself, then you don't have to use them, and that's my opinion.
Click to expand...
Click to collapse
What do you mean extract and re-compress? The guide over here mentions nothing about needing to re-compress or extract anything.
Edit: To anyone stuck like myself. I solved it with this guide: https://forum.xda-developers.com/t/...-q-complete-guide-for-the-a20-a205xx.4095589/
My guess is it's something to do with vbmeta.img and boot.img not being included with the new TWRP tar. should Re-compressing a new tar file with those files included in the tar as recovery.tar might solve the issue, though I cannot verify as I'm fine with the working older TWRP.
I am following what is said under "Odin Install Method (No Root Required)" mentioned on this page.
Samsung Galaxy A20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
There's no reason to be rude when I'm following the directions and trying to get assistance for something that has once gone smoothly for me in the past, but ok you do you, boo.
CawfeeOG said:
What do you mean extract and re-compress? The guide over here mentions nothing about needing to re-compress or extract anything.
Edit: To anyone stuck like myself. I solved it with this guide: https://forum.xda-developers.com/t/...-q-complete-guide-for-the-a20-a205xx.4095589/
My guess is it's something to do with vbmeta.img and boot.img not being included with the new TWRP tar. should Re-compressing a new tar file with those files included in the tar as recovery.tar might solve the issue, though I cannot verify as I'm fine with the working older TWRP.
I am following what is said under "Odin Install Method (No Root Required)" mentioned on this page.
Samsung Galaxy A20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
There's no reason to be rude when I'm following the directions and trying to get assistance for something that has once gone smoothly for me in the past, but ok you do you, boo.
Click to expand...
Click to collapse
Is there a reason? It doesn't matter. But you have to learn for yourself. That is important, we are not thinking to help you forever.
Topser99 said:
Is there a reason? It doesn't matter. But you have to learn for yourself. That is important, we are not thinking to help you forever.
Click to expand...
Click to collapse
Knowledge is to be passed on, not to be kept to oneself forever.
Trust me, if I didn't make attempts at figuring it out myself, I wouldn't have bothered asking questions. I also ask questions to avoid breaking my devices, as I'm not one who can just go buying a new phone whenever I please.
I may be the first one asking questions about this, but I won't be the last. Maybe create a better-worded guide and you won't have to deal with such people.
Which Twrp should i use for SM-A205F_A205FXXU3ASJ2 running one UI 3.1
@Topser99 any idea ?
suriyaraj said:
Which Twrp should i use for SM-A205F_A205FXXU3ASJ2 running one UI 3.1
@Topser99 any idea ?
Click to expand...
Click to collapse
I am looking for that too but I couldn't find any answer . If you find out the answer can you pls tell me plsssss
physwizz said:
TWRP Official Recovery for A20 and A20e
Developed and maintained by @Topser99
SM-A205xxx
Download TWRP for a20
Download TWRP Open Recovery for a20
dl.twrp.me
SM-A202F/K
Download TWRP for a20e
Download TWRP Open Recovery for a20e
dl.twrp.me
Also available for installation via the Official TWRP app from Playstore
Click to expand...
Click to collapse
guys everytime i flash it just gives Error validating footer CUSTOM RECOVERY
shadowhansen1 said:
guys everytime i flash it just gives Error validating footer CUSTOM RECOVERY
Click to expand...
Click to collapse
Try here
TWRP 3.4 and 3.5 for A20
@Topser99 has provided us with some newly modified recoveries. They all have TWRP 3.4 and also now 3.5 ⇨NewUpdate -update kernel By : @physwizz Follow : @ULtimaTe_Pie2 Follow :mad:Galaxy_A20_official System and System_root...
forum.xda-developers.com
physwizz said:
Try here
TWRP 3.4 and 3.5 for A20
@Topser99 has provided us with some newly modified recoveries. They all have TWRP 3.4 and also now 3.5 ⇨NewUpdate -update kernel By : @physwizz Follow : @ULtimaTe_Pie2 Follow :mad:Galaxy_A20_official System and System_root...
forum.xda-developers.com
Click to expand...
Click to collapse
for a20e
shadowhansen1 said:
for a20e
Click to expand...
Click to collapse
AstrakoBot in Galaxy A20/A20e Official📱
t.me
CawfeeOG said:
Knowledge is to be passed on, not to be kept to oneself forever.
Trust me, if I didn't make attempts at figuring it out myself, I wouldn't have bothered asking questions. I also ask questions to avoid breaking my devices, as I'm not one who can just go buying a new phone whenever I please.
I may be the first one asking questions about this, but I won't be the last. Maybe create a better-worded guide and you won't have to deal with such people.
Click to expand...
Click to collapse
i found a workaround in this, i kept having that error too
download the recovery from the post above from @physwizz (https://forum.xda-developers.com/t/twrp-official-recovery-for-a20-and-a20e.4267815/post-86192489), and the latest official TWRP recovery, pick up the vbmeta.img inside the compressed .tar from the first one and put it inside the official TWRP compressed one.
It worked for me. (SM-A202F)
Drvaggensberg said:
i found a workaround in this, i kept having that error too
download the recovery from the post above from @physwizz (https://forum.xda-developers.com/t/twrp-official-recovery-for-a20-and-a20e.4267815/post-86192489), and the latest official TWRP recovery, pick up the vbmeta.img inside the compressed .tar from the first one and put it inside the official TWRP compressed one.
It worked for me. (SM-A202F)
Click to expand...
Click to collapse
great work
You can also do it by patching the full ap file and flashing that via odin before you use the official TWRP
physwizz said:
AstrakoBot in Galaxy A20/A20e Official📱
t.me
Click to expand...
Click to collapse
Hi i have this problem too but i cant open that link
gigi3000 said:
Hi i have this problem too but i cant open that link
Click to expand...
Click to collapse
Here
many, many thanks
Official twrp-3.7.0_9-0 is out for A205 on TWRP website.
Hey guys,
I've tried to update my Nord 2 to the newest software (A.12) but every time I try it, it just reboots after a couple seconds and displays an error message:"Verification error". I've tried rebooting it multiple times, without any success. It is rooted with magisk and the bootloader is open, but I don't have TWRP installed. Could you guys hook me up with a solution?
Regards
Take a look: https://forum.xda-developers.com/t/...rooted-nord-2-any-incremental-update.4347813/
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
AdamBarath said:
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
Click to expand...
Click to collapse
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Raygen said:
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Click to expand...
Click to collapse
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
AdamBarath said:
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
Click to expand...
Click to collapse
Yup, the order is:
Backup EVERYTHING.
Flash stock boot image for your current version (A.11)
Flash update.zip via recovery
Flash patched vbmeta via fstboot
Re flash TWRP via fastboot
Reflash magisk:
Flash the .zip it via recovery (not reccomended). OR,
Download and flash an already patched boot image for the updated version (A.12). OR,
Extract your stock updated boot image (A.12) with adb shell and dd (or download it), boot into system, patch the image with the magisk app, flash the patched boot image in recovery.
If during one of these steps you get back the stock recovery, just boot into fastboot and reflash twrp. Without magisk installed the rom tends to restore the stock recovery by itself.
Thank you for your help!
Worked like a charm!
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
HTCore said:
Long story short, I rooted my N200 T-Mobile variant to A12 DE2118_11_C.15 (Full OTA) not a long time ago with no issues. However to be able to update to DE2118_11_C.16 (Incremental update, w/July 2022 Patch) I had to uninstall Magisk first, then update it to c.16. Now my phone is updated to c.16 but I am very unsure how to root it again to avoid bootloop;
1. Can I use c.15 stock boot image since c.16 was an incremental update? or I need c.16 version?
2. If c.16 boot image is already extracted please share.
3. If none above, how and where I can find the OTA file to extract payload.bin and then boot.img?
I would really appreciate if somebody help me with this, thank you.
Click to expand...
Click to collapse
The steps below is what I do since Android 12 update:
**Automatic system updates should be unchecked on Developer options.**
Prerequisites: Rooted with Magisk (v25.2 recommended) / Have stock boot image available.
Preparation:
A. Restore active slot boot img with stock boot on adb shell with root
ex) dd if=/sdcard/boot_a.img of=/dev/block/bootdevice/by-name/boot_a
OR
B. Uninstall Magisk with Restore Image option if available
--------------------------------------------------------------------------------------------------------------
**If you do A first and Direct Install with Magisk, then B option will be available.
1. Update OTA and DO NOT PRESS Restart Button.
2. Backup the new stock boot image. If your current boot is b, then new stock boot is a
ex) dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img
3. Patch the newly extracted stock boot with Magisk -> Reboot -> Reboot to fastboot
4. Flash the newly magisk patched image
ex) fastboot flash boot_a new_magisk_boot.img
5. Reboot
OR you can try to install Magisk with in-active slot option at Step #3, then restart with OTA, not with Magisk; however, I've been told that it sometimes makes an issue such as bootloop. Up to you.
follow A1.1 to get your boot.img.
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
After your phone is rooted again, go in developer options and disable automatic system updates so it won't restart without your consent in future OTAs. when it asks for you to restart, go into the magisk app and press install and then "install to inactive slot". Then go back to the system update screen and press restart.
That's it. If you followed the steps correctly, your device should be updated and you should still have root!
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
HTCore said:
Thank you both of you for your help and thorough explanation.
I suppose since I already restarted my device after update I have no chance with @lentm's method.
Now I'm going to follow what @justauserthatusesaphone posted and see what happens.
I will post the result here if somebody else is interested too.
Click to expand...
Click to collapse
All you need is the stock boot img file, and here's the latest one:
11_C.16_DE18CB_tmobile_stock.7z is available for download
Click to access the 11_C.16_DE18CB_tmobile_stock.7z (35.3 MB) download with TransferNow
www.transfernow.net
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
HTCore said:
Thank you for posting boot.img @lentm!
I was middle of what @justauserthatusesaphone posted when you attached the boot.img! So thank you very much being mindful of others!
However, just to learn more and be prepared for future updates I tried the other method and it worked perfectly! My device is now rooted with latest update thanks both of you guys!
Next I'm gonna use your method for another N200 which hasn't been updated yet and experience that one as well.
Click to expand...
Click to collapse
glad to hear you got it!
lentm's link didn't work for me so for anyone else who needs the stock image here is a non-expiring link for stock boot image for Tmobile DE2118 11_C.16:
boot_11_C.16_DE2118_tmobile_stock.img | by towardsdawn for Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Brisingrmischief said:
Could someone please tell me if it's possible to root this device running the latest July 5th update mentioned above without a pc ?
And if so where to find or how to do it ?!
I've been searching everywhere and have only come across a bunch of "one clock root options" that haven't worked .
Click to expand...
Click to collapse
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
towardsdawn said:
One click root APKs don't have access to fastboot to flash a rooted boot.img, which is what you need to do for permanent root for newer Android devices. Also I wouldn't trust those anyway, most are not open source and might contain malware/ads/etc.
You can have a temporary root if your bootloader is unlocked by using a DSU, however if your bootloader has not been unlocked (which you need a PC to do) do NOT attempt to do this. Multiple people have reported bricking their devices attempting to do this so you have been warned.
All files on the DSU will be deleted when you discard the DSU since it is a different system image from the original. If you really know what you're doing you might be able to flash a Magisk rooted boot.img to the original system image from the DSU, I don't know how to do this. You can play around with making the DSU persist through reboots using this guide, I don't know if that works with updates or if all files will have to be discarded if you want to update. I recommend using DSU sideloader with a GSI from phhusson, when it says to run the shell script over ADB you can use a terminal app like Termux instead.
Click to expand...
Click to collapse
Thank you for your help !
I assume that since my bootloader is not unlocked and I don't have access to a pc I'm pretty much out of luck on rooting this device until I can get access to one .
Guess I'll have find a way to access one .
Much appreciated though !
Hi everyone, I prefer remain with the Chinese rom for a while but I'd like to root my moto x40 with magisk.
I've tried but after flashing the patched boot.img the phone boot normally. the firmware has vbmeta so I followed the procedure suggested by the guide in this situations.
the weird thing is the patched root remain exactly with the same original dimensions.
I think this is an a type partition firmware due to boot.img presence but there is also a file called vendor_boot.img. according with this article seems an a/b type.
Vendor Boot Partitions | Android Open Source Project
source.android.com
I attach a screen of the firmware content, the log of patched boot file and the adb process.
Please, can anyone explain me how can I root successfully? thanks
Did you unlock the bootloader? Once done you need to flash a patched init_boot.img instead of boot.img through fastboot.
This guide should be useful (it's for the Pixel 7s, but should work with this phone, and of course use the init_boot.img from the original ROM file for your phone)
Hope that helps
hi, thank you for the answer.
yes the bootloader was unlocked.
This rom is the same as my phone's. I had take by lolinet.
unfortunately magisk is unable to patch vendor_boot , I'm trying to attach it.
Is Someone able to patch?
vendor_boot.img
Shared with Dropbox
www.dropbox.com
This is my vendor-boot
Do you lose VPN access after bootloader unlocked?
No, I didn't lose
mikaelcbr2 said:
hi, thank you for the answer.
yes the bootloader was unlocked.
This rom is the same as my phone's. I had take by lolinet.
unfortunately magisk is unable to patch vendor_boot , I'm trying to attach it.
Is Someone able to patch?
Click to expand...
Click to collapse
You need to patch init_boot.img using Magisk, and flash both init_boot_a and init_boot_b with the patched file through fastboot
sooyong94 said:
You need to patch init_boot.img using Magisk, and flash both init_boot_a and init_boot_b with the patched file through fastboot
Click to expand...
Click to collapse
Yes I followed the guide, thanks