How To Guide DSU Sideloader for gaining temporary/permanent root, testing GSI's or installing GSI's Semi-permanently, pulling boot image, AND making your backups

Search This thread

PsYk0n4uT

Senior Member
im afraid to attempt root. today i unlocked bootloade. i have the oct 5 OTA update. has any achieved root with the latest ota update


UPDATE. I have Lineos sideloaded with DSU 1.02 feb 18


DOES THISMEAN IM ROOTED TEMP? AND MAY SOMONE show me a guide to back up partiton


apparently im not rooted, The GSI is not prerooted?

where can i get a prerooted GSI?lin
So I think lineage has a version that's prerooted I may be wrong tho.... I'm almost positive they do tho. Look for a version that has bgs or bvs ... Also u need phussons su binary/root app for it to work in any of the roms using phhusson patches which I believe lineage posted on the phusson GSI GitHub page DOES. U won't use magisk with it. But u will use magisk later after pulling your partitions it that's the route you choose to go in rooting ur device and since there are no roms built yet it seems to be nearly the only option for now but u need the root app for root to work in those gsi's as it's not included even if it's prerooted. I used crdroid which was rooted by default and I can't remember if I had to use the phusson root app/su binary or not but I think maybe I didn't need to with crdroid it's been a while tho so I can't recall...... If u look at the notes when downloading the lineage gsi it tells u that the root app isnt installed by default or the GSI doesn't come with it even tho it's prerooted and u need it to handle root requests
 
  • Like
Reactions: ScarletWizard

PsYk0n4uT

Senior Member
So I think lineage has a version that's prerooted I may be wrong tho.... I'm almost positive they do tho. Look for a version that has bgs or bvs ... Also u need phussons su binary/root app for it to work in any of the roms using phhusson patches which I believe lineage posted on the phusson GSI GitHub page DOES. U won't use magisk with it. But u will use magisk later after pulling your partitions it that's the route you choose to go in rooting ur device and since there are no roms built yet it seems to be nearly the only option for now but u need the root app for root to work in those gsi's as it's not included even if it's prerooted. I used crdroid which was rooted by default and I can't remember if I had to use the phusson root app/su binary or not but I think maybe I didn't need to with crdroid it's been a while tho so I can't recall...... If u look at the notes when downloading the lineage gsi it tells u that the root app isnt installed by default or the GSI doesn't come with it even tho it's prerooted and u need it to handle root requests
Also as a side note if u want ur virtual/sideloaded system to be RW as in being able to make changes to )system u need to grab one that doesn't have "secure" in the filename... Yes I think people have rooted the October update.. but don't quote me on that.... The worst that can happen is it doesn't boot and u just reflash the original boot image. And since you were sure to play it safe and backup ALL of your partitions while in prerooted GSI, you should have a copy of it
 
  • Like
Reactions: ScarletWizard

kbmonday

New member
Feb 22, 2011
4
2
I was able to get the Lineage OS image working on mine, but only just once. I still have not figured out my propblem.
 

ScarletWizard

Senior Member
Aug 31, 2022
684
102
Moto G 5G
I was able to get the Lineage OS image working on mine, but only just once. I still have not figured out my propblem.
Start from scratch. Delete the lineage zip from your device. delete the contents of the folder dsu told you to create. wipe cache on the dsu app redownload the lineage and proceed.

I'm running version 1.02 of dsu. I can confirm this version works flawless
 

ScarletWizard

Senior Member
Aug 31, 2022
684
102
Moto G 5G
3rd pic.That's the lineage version that worked for me. What version are you using?

1st picture is the folder you need to delete.

2nd pic Is the dsu version I'm using.
Screenshot_2022-11-28-15-53-16-08_b3847c8680707ba5e0e5722b3f44809a.jpg
Screenshot_2022-11-28-15-51-41-07_fc704e6b13c4fb26bf5e411f75da84f2.jpg

screenshot_2022-11-28-15-53-34-73_b3847c8680707ba5e0e5722b3f44809a-jpg.5772673
 

Attachments

  • Screenshot_2022-11-28-15-53-34-73_b3847c8680707ba5e0e5722b3f44809a.jpg
    Screenshot_2022-11-28-15-53-34-73_b3847c8680707ba5e0e5722b3f44809a.jpg
    586.7 KB · Views: 183

PsYk0n4uT

Senior Member
Also for those of you having issues with DSU sideloader not working or failing after one attempt. I found out today that the issue is probably because there's no automated cleanup of the virtual B partitions inside of super. So when you update or sideload a GSI, the _cow files from an update or DSU get left behind and there's no room for the new GSI to install. If your rooted already you can delete the _cow files in super and should solve the issue hopefully. If you get a chance to install a GSI try to dump your partitions immediately so that in case you need to reinstall a GSI or whatever later without root, you could probably dump the super with some tools and delete the cow files and repack it and flash super...

As for what to use for dumping your firmware I suggest using Partitions Backup & Restore by wanam either grab it on playstore or apkmirror or APKPure
 
  • Like
Reactions: ScarletWizard

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hello, I just wanted to post this as an answer to many questions regarding not being able to use DSU to install a GSI for testing or gaining root.
    The DSU install in developer options is NOT what we are using for installing GSI's temporarily for pulling boot images. And wont work for that.
    You can use DSU sideloader to install GSI's tempoarily or use the sticky feature to make it semi-permanent. but if you plan on using the GSI long term make sure to set your userdata to a reasonable size because your gonna want to install apps and download things. take note that if you dont use the sticky feature, once you reboot the phone it goes back to your regular stock OS or whatever you were running on before and you lose everything in the GSI that you havent saved to external media/sdcard/cloud. If you use the sticky feature you can reboot the phone and retain the GSI installation.

    *This is NOT mine and i take absolutely NO credit for it and am just providing it here to make it easy to find for other N20 users and newcomers looking to pull their boot images to patch with magisk and root OR for testing GSI's.
    If you want a permanent GSI install you will need to flash. BUT that being said, i have used the sticky feature to stay in a GSI for a few weeks. Definitely gonna want to set that user data pretty high if you wanna stay in one long term. This isnt the best way to install a GSI if you plan on staying in it permanently but it would work if you want to keep your stock installed in case of system failure for some reason.... Best to pull a FULL system backup while in a rooted GSI and save it to your PC or in the cloud.........PLEASE make that your #1 priority once you get root because NOBODY can help you restore your EFS partitions should you screw those up. They contain your IMEI and device-specific info that you cant get ANYWHERE else and NEVER will be able to either.
    My suggestion is to install a prerooted GSI, then use Partitions Backup & restore app found here https://www.apkmirror.com/apk/wanam/partitions-backup/ or on playstore and change options to save the backups as RAW (.img) then open the folder their saved to /storage/emulated/0/Partitions Backups/ and use zarchiver or any other compression tool to compress them all into a single archive to save some space and make them easier to manage and/or upload....... (you may want to change screen timeout/'turn off display after' in android settings to 30 mins to keep the screen from turning off while you do your backup because it takes a while (your stock full backup will be about12gb after all the .img's are compressed)...

    Now heres where you can find DSU sideloader and also a copy/paste from the github page:

    DSU Sideloader​


    A simple app made to help users easily install GSIs via DSU's Android feature.


    preview


    Requirements​


    • Android 10 or higher
    • Unlocked Bootloader
    • Device with Dynamic Partitions
    • A GSI you want to use!

    Community GSIs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list


    Google GSIs: https://developer.android.com/topic/generic-system-image/releases


    *Remember to use GSIs compatible with your architeture, vndk implementation..


    You don't need root to use this app, however, running on non-rooted devices, requires adb (you will be prompted to run a shell script to invoke DSU installation activity)


    Rooted devices via Magisk, should be running Magisk v24 or higher, older versions may break DSU feature.


    We highly recommend using this app with Stock ROM, Custom ROMs aren't supported.


    How to use?​


    1. Install app
    2. When opening for the first time, you need to give read/write permission to a folder, create a new folder and allow access
      *this folder will be used to store temporary files, like extracted GSIs from compressed files)
    3. Select a GSI to install
      *accepted formats are: gz, xz and img
    4. You can customize installation as you want
      *like changing userdata size for dynamic system
      *changing gsi file size is not recommended (let app do it automatically)
    5. Tap on "Install GSI via DSU"
    6. Wait until finishes! (it may take a some time)
    7. Once it finishes, next step may vary:
      • On rooted devices, DSU screen will appear, prompting you to confirm installation, after that, check your notifications, DSU should start installing GSI
      • On non-rooted devices, you will be prompted to run a command in adb, once you run, DSU screen will appear asking you to confirm installation, after that, DSU should start installing GSI
    8. Once dynamic system is ready, you can boot it through notifications

    Other information​


    • DSU feature may be broken in some ROMs.
    • gsid does not let you install GSIs via DSU when you have less than 40% of free storage.
    • gsid checks if selected GSI size is multiple of 512 (preventing corrupted system images).
    • If you have disabled/debloated system apps, make sure "Dynamic System Updates" app is not disabled.
    • To use "ADB mode" on rooted device, deny root permission.

    About DSU​


    DSU (Dynamic System Updates), is a feature introduced on Android 10, that let developers boot GSIs without touching current system partition, this is done by creating new partitions to hold a GSI and a separated userdata, to boot on them when desired.


    Unfortunelly, DSU depends on Dynamic Partitions (your device need to support, otherwise, won't work), and most GSIs requires unlocked bootloader to get them booting properly (since only OEM-Signed GSIs are allowed to boot on locked bootloader).


    GSIs can be installed via DSU without root access, using ADB, running some commands, you can read more about installation process here: https://developer.android.com/topic/dsu


    Once installation finishes, Android creates a persistent notification allowing you to boot into "Dynamic System" (GSI installed via DSU), and you can boot into installed GSI, without touching your system partition, or breaking the "real userdata" partition.


    After booting Dynamic System, you can try and test whatever you want, when you need to switch back to device's original system image, everything you need to do, is just, a simple reboot!


    When doing a long test, that may requires lots of reboots, this can be a pain, however, is possible to enable "sticky mode", that enforces dynamic system, instead of device's original system image, once tests are done, you can disable sticky mode and return to original system image.


    That is basically a quickly explanation about DSU, a amazing feature, like a "dual-boot" solution, limited, however, very safe (since no read-only partition will be modified, and if GSI does not boot, just a simple reboot will return you to the original device's system image).


    You can read more about DSU here: https://source.android.com/devices/tech/ota/dynamic-system-updates


    How to enable Sticky Mode?​


    Reboot to Dynamic System, and:


    • use this command on adb: adb shell gsi_tool enable
    • or from local adb shell: gsi_tool enable
    • or from local rooted shell (eg. Termux on rooted GSI): su -c 'gsi_tool enable'

    When sticky mode is enabled, device will always boot into dynamic system, instead of device's original system image.


    To disable, use the same command, instead of enable , use disable


    ****Special Thanks To VegaBobo for this awesome app to make this a simple process And to AndyYan for the suggestion!!***

    DSU Sideloader GitHub main:

    DSU Sideloader Github Releases(downloads) [**Most will want to use the app-release.apk NOT app-debug.apk**]:

    Partitions Backup & Restore:
    or on playstore at https://play.google.com/store/apps/details?id=ma.wanam.partitions


    Please consider donating to the developers who work hard and spend their valuable time to provide these awesome apps/mods that bring joy to your life!


    ****Special Thanks To VegaBobo for this awesome app to make this a simple process And to AndyYan for the suggestion and time spent on mods/ROMs!!***
    Also shout out to Wanam for this awesome backup tool thats STILL relevant and working as great as ever.

    11/11/2022: received response from developer about the issues with DSU sideloader failing
    2
    I was able to get this to work a couple of times, but now every installation attempt immediately fails. My bootloader is unlocked and I have tried other images as well, even unzipping as a raw system image to expedite the process. BUT... for the life of me, I just cannot get an install to actually finish anymore. I have tried doing a complete system format and wipe, to no avail. I have seen a couple of other people who have had this problem but can't find a solution anywhere. Any help would be much appreciated. Thanks

    As an aside, I have not installed any updates so it SHOULD be working. If I can figure out the issue I'll post the solution.
    1
    ok if theres no dsu option in dev options then you likely cant use this as its a wrapper that lets you use that built-in function for sideloading things that Arent approved by the3 manufacturer
    1
    Have you rooted the device
    Your not alone in that, as ever since not long after rooting the device/modifying bootloader I haven't been able to sideload gsi's either. Not really sure what the issue is. But I'm pretty sure I never had that issue until another "system update" was available. So I'm not sure if it has anything to do with the system update that's been downloaded and that is always trying to install but failing being the culprit of DSU failing or not but that's my latest theory. If anyone knows where the updates are downloaded to maybe that would be a good place to start, by deleting the downloaded update and getting updates completely disabled so it's not perpetually attempting to install a system update that will never succeed so long as your not completely stock. It seems looking over other threads for previous devices that others had this issue until updating to latest security patch. So this seems the likely culprit. Probably just need to delete the update that's waiting to be installed and sideload the gsi using DSU sideloader before it has a chance of attempting to update again