Related
I am currently trying to root my LG Rebel 3 [L158VL] (Android 7.0)
I've been reading all around and I've installed ADB and Fastboot on my system (Windows 10 Pro 64-bit) however I have not been able to enter fastboot on my phone. If anyone could help me out and walk me through this. I've also been looking into using Lineage OS but they don't seem to support my device (not surprising as it's a Tracfone from Wal-Mart) and I was wondering if there was a version I could use on my phone, I'd appreciate if anyone could help me with that. However, I mostly need help with fastboot.
Any help or advice you can provide will be great, thank you in advanced
- Grey
UPDATE: 11/29/2018 8:34PM
I have tried several other methods but my phone absolutely refuses to boot into fastboot or the bootloader. It's like it's locked and I would like to know if there is a way to unlock/allow my device to boot into what I want it to.
Wasting your time
Tracfone has removed the fastboot and download modes. You still have EDL mode. Adb reboot EDL. However youd still have to unlock the bootloader or have some kind of patched system.img in order to avoid a brick. I cant recall the thread but it did mention the possibility of changing the partition table amd flashing a .laf which is your download mode/bootloader/fastboot.
I also read somewhere where it might be possible to flash using python but that may have been in the files that were from the CIAhttps://github.com/troydo42/CIA-Hacking-Tools mobile security exploits. Tracfone is verizon based so if you could manage to flash it somehow then you should be able to load a verizon rom. Please anyone feel free to expand or correct me.
deshaney said:
Tracfone has removed the fastboot and download modes. You still have EDL mode. Adb reboot EDL. However youd still have to unlock the bootloader or have some kind of patched system.img in order to avoid a brick. I cant recall the thread but it did mention the possibility of changing the partition table amd flashing a .laf which is your download mode/bootloader/fastboot.
I also read somewhere where it might be possible to flash using python but that may have been in the files that were from the CIAhttps://github.com/troydo42/CIA-Hacking-Tools mobile security exploits. Tracfone is verizon based so if you could manage to flash it somehow then you should be able to load a verizon rom. Please anyone feel free to expand or correct me.
Click to expand...
Click to collapse
I think I might remember the thread your're talking about. it required that you used a patched version of lg up that unlocks the dev features and let's you flash the partitions in any order you want. I believe lg up requires the phone to be in download mode but I can't say for sure
Is there away to self root the LG rebel 3?
I want to self root it so I don't have to use my work computer to do so
There's no way to root this a phone with the following, is there?
OP N10 5G / TMO / BE2025.BE88CB / 11.0.2.BE88CB
- Bootloader unlocked.
- Not rooted.
Seems to me there's no MSM tool for the BE88CB (TMO) variant, no TWRP, and no flashed boot images available.
Do I have this right? Rooting is impossible?
How much of a loss do you want to risk? (I think a refurb is ~$250 now for an international).
I'd try the TWRP for the international one, and you can flash Magisk directly from that (rename .apk to .zip); I've never needed the boot images.
If that doesn't work, I think you can MSM the ENTIRE international recovery image over it... even if you lose some of the T-mo bands (m-wave?) it is still pretty quick (mine is a international phone, on Tmo, 5G works great for me).
If the bootloader is unlocked, you should be in good shape.
YMMV, no refunds, at your own risk, etc. I have gotten braver in my old age, though.
I've been through this thread: https://forum.xda-developers.com/t/...bile-metro-w-locked-bootloader.4297501/page-5
But both links to MSM the TMO to GLO are dead, so the MSM is currently not available.
The TWRP for the international... I'll happily try that, do you know where it is? I've tried booting to 3.5.2_10-1 and it boots but the touchscreen doesn't work via `fastboot boot` (not `fastboot flash boot` ) which can be found here: https://forum.xda-developers.com/t/twrp-3-5-2_10-billie-twrp-for-oneplus-nord-n10-5g-beta.4256333/
bouyakasha said:
There's no way to root this a phone with the following, is there?
OP N10 5G / TMO / BE2025.BE88CB / 11.0.2.BE88CB
- Bootloader unlocked.
- Not rooted.
Seems to me there's no MSM tool for the BE88CB (TMO) variant, no TWRP, and no flashed boot images available.
Do I have this right? Rooting is impossible?
Click to expand...
Click to collapse
nah man you can actually unlock the bootloader without tmo carrier unlock and root...see my guide to do that, its as straight forward as any other oneplus, but basically you have to request the bootloader unlock code from oneplus, then assuming your carrier unlocked or use the guide to break the carrier lock functionality. If your already at that point grab the boot image for your version, store on device, root that image with magisk manager then flash it in bootloader
https://github.com/nylar357/nord_oem
nylar357 said:
nah man you can actually unlock the bootloader without tmo carrier unlock and root...see my guide to do that, its as straight forward as any other oneplus, but basically you have to request the bootloader unlock code from oneplus, then assuming your carrier unlocked or use the guide to break the carrier lock functionality. If your already at that point grab the boot image for your version, store on device, root that image with magisk manager then flash it in bootloader
https://github.com/nylar357/nord_oem
Click to expand...
Click to collapse
As you can see in my message, bootloader is unlocked.
@nylar357 How can I "grab" boot image for 11.0.2 when not rooted?
bouyakasha said:
As you can see in my message, bootloader is unlocked.
@nylar357 How can I "grab" boot image for 11.0.2 when not rooted?
Click to expand...
Click to collapse
Root N10 using Magisk
Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...
forum.xda-developers.com
I'm sure you can find your img files here...
??? there is a MSM tool for TMo.
[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Use readback mode to get the stock root image.
Where can i get stock image for BE2025?
Need a stock image for metro pc n10 5g android 11 build 11.BE88CF so i can root. My device is now oem unlock by waiting 90 days. Cant find image on google.
forum.xda-developers.com
See last post for detailed instruction.
JazzieBoi said:
Root N10 using Magisk
Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...
forum.xda-developers.com
I'm sure you can find your img files here...
Click to expand...
Click to collapse
Nope. Not there for 11.0.2.BE88CB
arda99 said:
??? there is a MSM tool for TMo.
[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Use readback mode to get the stock root image.
Where can i get stock image for BE2025?
Need a stock image for metro pc n10 5g android 11 build 11.BE88CF so i can root. My device is now oem unlock by waiting 90 days. Cant find image on google.
forum.xda-developers.com
See last post for detailed instruction.
Click to expand...
Click to collapse
Trying this now, thank you.
arda99 said:
??? there is a MSM tool for TMo.
[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Use readback mode to get the stock root image.
Where can i get stock image for BE2025?
Need a stock image for metro pc n10 5g android 11 build 11.BE88CF so i can root. My device is now oem unlock by waiting 90 days. Cant find image on google.
forum.xda-developers.com
See last post for detailed instruction.
Click to expand...
Click to collapse
Thank you so much, this worked!!!
bouyakasha said:
Thank you so much, this worked!!!
Click to expand...
Click to collapse
So there's been an MSM download tool for the B88 this whole time while everybody was saying "there's no MSM for TMobile". ?!?!
bouyakasha said:
As you can see in my message, bootloader is unlocked.
@nylar357 How can I "grab" boot image for 11.0.2 when not rooted?
Click to expand...
Click to collapse
Use twrp
"If ever attacked by a polar bear, just remember x = r*cos(theta), y=r*sin(theta) and you can convert it into a harmless rectangular bear."
Great signature @SomeRandomGuy
Oops
you can install the global rom on both lito(metro) or billie. With or without locking the bootloader. that same process will unbrick the device as well, ive done it several times. if for some reason msm and the global rom disappeared, I do have it.
bouyakasha said:
Nope. Not there for 11.0.2.BE88CB
Click to expand...
Click to collapse
Here's one not rooted. Came from a restore package on telegram, you might check it out...it's 11.02 or 10.5.12 for restore .no msm needed...worked for me with fastboot.
##copy/pasted from telegram, I did NOT make these, just helping people save time.....oh if your on Linux run dos2unix on the bat file, you'll also have to change reboot-bootloader to reboot bootloader and set-active-slot becomes set_active a/b
**********************
I've put together two bundles to restore the OnePlus Nord N10 5G to Factory OS without the need for MSM Download Tool. One for OOS10 and one for OOS11.
Simply boot into the bootloader (Fastboot mode) and run the script! ("OnePlusNordN10_Restore.bat") (Roughly 5 minute duration to restore, give or take)
Note that all custom ROMs currently available require you to be on OOS10 in order to boot successfully. We hope to change this soon, but this is how it is for now until OnePlus properly re-syncs their Android 11 Kernel.
These are for the International variants only! If you require the European firmware, you will have to extract it's OTA payload and replace the appropriate files.
OnePlus OxygenOS 10.5.12
OnePlusNordN105G_Restore_OOS10.5.12_BE86AA
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
MD5: A5BF4C91124B75513159A8F55AEE944E
SHA-1: 57C5C87DF8CDB169076C57717A7F0F3045D361F3
OnePlus OxygenOS 11.0.2
OnePlusNordN105G_Restore_OOS11.0.2
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
MD5: 0CBA0395C8838F29B6728AF20B9CCA54
SHA-1: 160ACE7C2739027609785C5615FDB60601E824DF
Delete.
I have been through hell and high water today with this Nord N200 5G today. Soft Brick after Soft Brick. iI only flashed TWRP and try to boot into OS after exiting TWRP but i get No OS you sure you want to reboot?. I also can't figure out how to get my internal storage viewed in TWRP. I've read multiple guides and still can't figure it out. I"m pretty new to this so . and they try to flash Magisk for root as well as super su during on adventure fiasco after fiasco today. The Bootloader and OEM unlock was simple straight forward. Most Guides though are not in LAMENS terms and have abbreviations that new people do not understand. i have had to reflash my phone 20+ today with factory due to the NO OS problem with TWRP and can't get it so i can view my internal data from twrp even though i've followed several guides and the ones that says to do the wipe thing i always get the error about it can't mount the data or it has encountered and error 255 and by got try looking things up for those and you you get sent all over the place. So If there is Anyone Out There That would like to help an old geezer out to be able to get a stable TWRP and a Stable root going on please Respond. Sorry Had to Vent......
Oh yea and not to mention Unable to install 3.6.2
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
weirdfate said:
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
Click to expand...
Click to collapse
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
jova33 said:
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
Click to expand...
Click to collapse
Obviously not who you were asking but I just updated to Lineage and it was fairly straightforward following the directions, just make sure you're on Android 11. Updates can be done through settings menu, I just actually applied an update and it worked fine. It can check for updates every day, week, month if you choose I don't know if it will automatically update it though. Camera I have not tried as I don't use it as an everyday phone but generally from what I've seen it's common to have quality go down using software other than stock but I could be wrong.
I can't speak on the difference in camera quality because I dont use it much. There is some loss of function between the stock camera app and the aftermarket rom camera app
This phone has no official twrp so it has tons of decrypting issues which explains almost all of your problems.
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
swee08315 said:
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Click to expand...
Click to collapse
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
MiniNinja2024 said:
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
swee08315 said:
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
Click to expand...
Click to collapse
how do i get the phone completely unbricked cause it's saying something like The Image[boot,recovery] has been destroyed please flash correct image or contact customer service to fix it
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Will be trying again in a week when i get my new unlock token. just took the phone to the store, said that the bricking of the phone happend during an update. They didn't have any Nord N200's in stock so they ordered one and said they would have it in the store in a day or two. onto the next phone til then. any ideas on a TCL A509DL Trac Phone?
MiniNinja2024 said:
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Click to expand...
Click to collapse
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
MiniNinja2024 said:
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
Click to expand...
Click to collapse
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
i don't have another machine only the one i'm using running MX linux. and with all the Distro's of linux i have installed and used there is no need to install drivers for phones for every phone, 3 that i have connected to my computer it' has recognized all 3 phones and runs adb and fastboot commands fine on them. Lol, Took me a minute to read your name but Love the Name.
Haha, don't flash it. Boot it. I ended up stop using it and am now using the Lineage OS Recovery. SUPER stable. I am in the works making a new TWRP as well... This unofficial variant just isn't working for me either. So, I figured since im making it doe myself, might as well release it
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
You can. Use virtualbox. I wouldn't bother with qemu.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
There is a command line alternative for Linux. It is originally made for flashing android boards, but works with phones as well.
Springles2 said:
You can. Use virtualbox. I wouldn't bother with qemu.
Click to expand...
Click to collapse
Interesting, that's actually useful to know. Thanks.
MiniNinja2024 said:
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I do adb push (File) partition
Hello,
I found a firmware file for the Nord N20 5g. However, it is CPH2459_11_A.06, while my phone says it is GN2200_11_A.06. Would it still be possible to do a local update to pull the boot image, or must the CPH and GN match? I have the T-Mobile version, bootloader unlocked, and network unlocked , along with the July security patch.
Thanks!
Take a full-backup of your firmware and find out.. lol.
DrScrad said:
Take a full-backup of your firmware and find out.. lol
Click to expand...
Click to collapse
I'm unfortunately not that brave
Rogo00 said:
I'm unfortunately not that brave
Click to expand...
Click to collapse
Want me to give it a go?
DrScrad said:
Want me to give it a go?
Click to expand...
Click to collapse
It would be awesome just to see if it works, but I don't know if it would harm your phone or not, and I would feel terrible if it did.
i would try flashing to inactive slot then switch over and maintain your functional system
PsYk0n4uT said:
i would try flashing to inactive slot then switch over and maintain your functional system
Click to expand...
Click to collapse
I'm still too new to rooting to do this successfully, I'm afraid
cph2459 is the unlocked version of the N20 5G correct? could you link the firmware please?
It is the unlocked version. I have the TMO version but it is network unlocked. The firmware can be found here: https://mega.nz/file/MXckFawK#IZ1ypD5Ftqw5Oz3oaeHLahqfUeaD6DlTzHCjeR3oseg
Also, this one is GN2200, but it is 11_A.05. Would it downgrade with the current patch? https://mega.nz/file/lX1H3Z5C#hUVmdbWUFI0bt0WQZVfaenTfVwoOqlfn2oexY5uC-Hs
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
PsYk0n4uT said:
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
Click to expand...
Click to collapse
I see. Basically I'm just trying to obtain root access. You mentioned prerooted gsi? I will need to read up more on this. Man this would be a lot easier with TWRP lol
waiting to hear from someone about a twrp that has been in the works. we tried one yesterday that didnt work. a different device tree is needed from the one that was used.
using DSU loader you can temporarily load a prerooted gsi and back everything up and move it to your pc and then move the boot.img to your internal storage where you can easily find it with the magisk app. install and load the magisk app and patch the boot.img then move the patched boot image to your pc and flash it in fastboot. that will give you a permanent root unless you prefer to stick with the gsi you sideloaded. but keep in mind any gsi you load with DSU Sideloader will be gone when you reboot the phone and your back to your regular system. you can use the sticky command if you want to keep the gsi installed but be sure to allocate plenty of space for your gsi if you plan on using it long term
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
PsYk0n4uT said:
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
Click to expand...
Click to collapse
I didn't know you did the July patch as well. I will check it out now
Also if and when you do flash the magisk patched boot images, do this command before and/or after flashing the boot.img:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Someone else has tried this and lost radios..... Can maybe get everything working again by reflashing the FULL BACKUP you took before cross flashing.... This would be an experiment though so don't attempt if your not ready to spend some time researching and unbricking your device should it be necessary
I tried it. I'm bootlooped
bricklife4me said:
I tried it. I'm bootlooped
Click to expand...
Click to collapse
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
DrScrad said:
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
Click to expand...
Click to collapse
I have a samsung a02, pixel 7 pro, moto g 5 g , oneplus n20 , iphone 12, iphone 6 , 4 tablets, and two LG
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:
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
DSU Sideloader
A simple app made to help users easily install GSIs via DSU's Android feature.
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?
Install app
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)
Select a GSI to install
*accepted formats are: gz, xz and img
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)
Tap on "Install GSI via DSU"
Wait until finishes! (it may take a some time)
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
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:
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
DSU Sideloader Github Releases(downloads) [**Most will want to use the app-release.apk NOT app-debug.apk**]:
Releases · VegaBobo/DSU-Sideloader
A simple app made to help users easily install GSIs via DSU's Android feature. - VegaBobo/DSU-Sideloader
github.com
Partitions Backup & Restore:
Download Partitions Backup & Restore APKs for Android - APKMirror
Download Partitions Backup & Restore APKs for Android - APKMirror Free and safe Android APK downloads
www.apkmirror.com
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
Also remember that if you do a full backup from inside a sideloaded GSI and you ever have to restore that full backup(all partitions) including userdata.......... you will upon flashing all of it back return to the exact same state, booting into that GSI(or returning to your stock system after rebooting if that happens to be the case)
I already unlock bootloader
But still show install failed
Tin2233 said:
I already unlock bootloader
But still show install failed
Click to expand...
Click to collapse
fastboot flashing unlock after flashing the token?
also make sure your using the reboot button from notifications instead of your regular reboot through power menu. if your unrooted you will HAVE to do the adb commands as directed in the app..
also you may want to try different versions, vdklite or whatever of your chosen gsi. make sure its 64bit as well, binder64 may or may not work on this device
PsYk0n4uT said:
fastboot flashing unlock after flashing the token?
also make sure your using the reboot button from notifications instead of your regular reboot through power menu. if your unrooted you will HAVE to do the adb commands as directed in the app..
also you may want to try different versions, vdklite or whatever of your chosen gsi. make sure its 64bit as well, binder64 may or may not work on this device
Click to expand...
Click to collapse
I unlock bootloader before flashing the token
I use ADB to flash the token
and I execute as required
Only show notifications "installation failed "
Maybe it's because I'm using a Samsung device（support dynamic partition）
And I flash pixel experience gsi normal version(android 12 and 13 both fail）
Sorry my English is bad...
Tin2233 said:
I unlock bootloader before flashing the token
I use ADB to flash the token
and I execute as required
Only show notifications "installation failed "
Maybe it's because I'm using a Samsung device（support dynamic partition）
And I flash pixel experience gsi normal version(android 12 and 13 both fail）
Sorry my English is bad...
Click to expand...
Click to collapse
tbh im not sure about samsung, but if it has a/b partitions it may be possible, samsung has always been a weird device, as much as ive been a samsung fan over the years, i had to move away from samsung due to most everything being too locked down. i like to mod my devices and USA model samsung devices were the bane of my existence having Awesome hardware on the flagship devices yet not being able to do much of anything with them. i assumed you meant the oneplus Nord n20, but the sideloader works on many devices and im not sure about samsung. you may HAVE to use binder 32/64 or a completely different gsi build type for those devices and then again, it may not be possible at all on samsung, ive gotten rid of all my samsung devices so i cant even test to see if its just samsung in general or simply something thats needs to be done differently on your device. have you tried using dsu in dev options? will it let you install one of the different "supported" gsi's in dsu updater ? or does it fail? also you have to make sure your inactive slot is empty for this to work either way. also i mostly used odin when i was messing with my samsung devices so i couldnt tell you much in the way of fastboot operations in samsung devices
Samsung's dev option no DSU....
Thank you
I understand
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
I have the One Plus Nord N20 GN2200 with the bootloader unlocked and I was able to get DSU SideLoader to work a couple of times. Now no matter what I try I get "install failed," pretty much instantly. Also, even in developer options if I use the DSUs available for download, they are now stating "install failed." A couple days ago I was able to temporarily boot into one of the Android 13 Beta GSIs through developer options and this worked, so I am quite confused now as to what is preventing this from working. Do you have any ideas on what I can try to sort this out? I wiped all my data through recovery, and verified bootloader as being unlocked. The only thing I noticed is that secure boot is enabled on the fastboot menu on my phone. I am 100 percent certain that the bootloader is unlocked since Google Pay and other services are now not supported (since they detect bootloader as being unlocked) and phone clearly states Device State - UNLOCKED in Fastboot Mode. Lastly, I do have logs from DSU SideLoader, but I looked through them on the computer and they don't provide any valuable insight.
Have you rooted the device
PsYk0n4uT said:
Have you rooted the device
Click to expand...
Click to collapse
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
alecstoner said:
I have the One Plus Nord N20 GN2200 with the bootloader unlocked and I was able to get DSU SideLoader to work a couple of times. Now no matter what I try I get "install failed," pretty much instantly. Also, even in developer options if I use the DSUs available for download, they are now stating "install failed." A couple days ago I was able to temporarily boot into one of the Android 13 Beta GSIs through developer options and this worked, so I am quite confused now as to what is preventing this from working. Do you have any ideas on what I can try to sort this out? I wiped all my data through recovery, and verified bootloader as being unlocked. The only thing I noticed is that secure boot is enabled on the fastboot menu on my phone. I am 100 percent certain that the bootloader is unlocked since Google Pay and other services are now not supported (since they detect bootloader as being unlocked) and phone clearly states Device State - UNLOCKED in Fastboot Mode. Lastly, I do have logs from DSU SideLoader, but I looked through them on the computer and they don't provide any valuable insight.
Click to expand...
Click to collapse
secure boot has been enabled the whole time i was testing gsi`s with dsu sideloader...... Im pretty sure my July device has Pixel experience GSI hardflashed and secureboot is still enabled.
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.
alecstoner said:
I have the One Plus Nord N20 GN2200 with the bootloader unlocked and I was able to get DSU SideLoader to work a couple of times. Now no matter what I try I get "install failed," pretty much instantly. Also, even in developer options if I use the DSUs available for download, they are now stating "install failed." A couple days ago I was able to temporarily boot into one of the Android 13 Beta GSIs through developer options and this worked, so I am quite confused now as to what is preventing this from working. Do you have any ideas on what I can try to sort this out? I wiped all my data through recovery, and verified bootloader as being unlocked. The only thing I noticed is that secure boot is enabled on the fastboot menu on my phone. I am 100 percent certain that the bootloader is unlocked since Google Pay and other services are now not supported (since they detect bootloader as being unlocked) and phone clearly states Device State - UNLOCKED in Fastboot Mode. Lastly, I do have logs from DSU SideLoader, but I looked through them on the computer and they don't provide any valuable insight.
Click to expand...
Click to collapse
Did you get this figured out? I am having the exact same issue.
kbmonday said:
Did you get this figured out? I am having the exact same issue.
Click to expand...
Click to collapse
Hey man, unfortunately I have not.
I have found a possible explanation. The security patch was installed automatically without my knowledge 2 days ago. I'll try to revert and see what happens.
check this out
PsYk0n4uT said:
check this out
Click to expand...
Click to collapse
I attempted this fix, but it didn't help in my case. On a more positive note I did find out what the issue is, but I don't really know how to fix it:
[TABLE]
[TR]
[TD][liblp]Invalid partition metadata header table size.
11-12 19:52:11.495 10973 10976 E gsid : Could not read metadata file /metadata/gsi/dsu/dsu/lp_metadata
11-12 19:52:11.495 1901 7313 I DynamicSystemService: Failed to install userdata
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: java.io.IOException: Failed to start installation with requested size: 42949672960
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: java.io.IOException: Failed to start installation with requested size: 42949672960
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at com.android.dynsystem.InstallationAsyncTask.installUserdata(InstallationAsyncTask.java:334)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at com.android.dynsystem.InstallationAsyncTask.doInBackground(InstallationAsyncTask.java:186)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at com.android.dynsystem.InstallationAsyncTask.doInBackground(InstallationAsyncTask.java:46)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at android.os.AsyncTask$3.call(AsyncTask.java:394)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-12 19:52:11.498 10567 10965 E InstallationAsyncTask: at java.lang.Thread.run(Thread.java:923)
11-12 19:52:11.501 10973 10976 E gsid : [liblp]Invalid partition metadata header table size.
11-12 19:52:11.501 10973 10976 E gsid : Could not read metadata file /metadata/gsi/dsu/dsu/lp_metadata
11-12 19:52:11.508 10567 10567 D InstallationAsyncTask: onPostExecute(), URL: file:///storage/emulated/0/dsu/workspace_dsuhelper/lineage-20.0-20221111-UNOFFICIAL-arm64_bvS.img.gz, result: 3
11-12 19:52:11.509 10567 10567 D DynSystemInstallationService: status=NOT_STARTED, cause=ERROR_IO, detail=java.io.IOException: Failed to start installation with requested size: 42949672960[/TD]
[/TR]
[/TABLE]
Tin2233 said:
I unlock bootloader before flashing the token
I use ADB to flash the token
and I execute as required
Only show notifications "installation failed "
Maybe it's because I'm using a Samsung device（support dynamic partition）
And I flash pixel experience gsi normal version(android 12 and 13 both fail）
Sorry my English is bad...
Click to expand...
Click to collapse
Hey, i noticed ONE step you were lacking in your steps taken to unlock your bootloader. Did you remember to flash the DM-Verity disabler? For most android 12 devices, it has become CRITICAL that you disable this, if you unlock your bootloader AND install a custom recovery! You dont have to do it, if just rooting, but if you installed TWRP (or other non stock recovery), with dm-verity still enabled, you will basically brick your device. DM-verity uses its RSA key hash to verify ANY partitions blocks AS THEY ARE ACCESSED! Meaning it does its security checks in real time, and if it sees a single block has been changed, it will get a different hash response and will stop your progress dead in its tracks! Sometimes without warning, and if your device was in the process of attempting a GSI/GSU flash, then the recovery partition would fail DM-Verity's checks, which when a partitions data fails to match EXACTLY to the hash/signature that it is expecting, it is already loading as a low level flasher, and does not have any protection thru Fastboot or EDL, to roll the "currently being installed" CHANGES TO THE FILE SYSTEM, back! It just crashes itself leaving your device with partitions mismatching, data corrupted, and chaos ensuing cuz you might have a new kernel, custom recovery, and old stock image all simultaneously existing on your main partition. You see how that would be a nightmare? And with Oneplus starting to push security updates without permission, you will slowly see more and more Fastboot functionality removed, until its like my 10T 5G - that has NO fastboot at all other than "FASTBOOTd" which is actually just a glorified recovery. No flashing capability, unless specific permissions are enabled in the HAL config... (which cant be done without unlocked bootloader, root, and a bootable device!)
But make no mistake... they are coming for your bootloader! If you havent unlocked and you are considering, i would advise EVERYONE to flip that dev option toggle, and unlock while you can! Cuz once they remove your access to fastboot, you are at the mercy of hoping an exploit becomes available to circumvent system checks, and let you downgrade. Although most downgrades will STILL keep the radio fw and others used for informing the OS that you have updated those components. Heres more about DM-Verity, but make note, that EVERY Android 12 device, (android 11 and 10 as well) has DM-Verity ENABLED from the factory. So all you bootloader unlocking, custom recovery flashing, ROM flashing ladies and gents out there, ALWAYS REMEMBER to read the details, and responses from ppl who might be having problems, cuz not one problem with these devices is UNIQUE! Some ppl may just not have attempted whatever triggers the error. But 'DM-VERITY' will brick your device, mid flash if it doesnt get the response it was expecting, to verify that your partitions arent corrupt or modified!
To me, THIS would almost definitely apply to your situation, because ESPECIALLY Samsung devices, but others as well, have DM-verity, and VB_meta active, and those are parts of the Trust Zone's secure boot library! And if they dont like what you're doing, they will MAKE SURE that you are stopped, and also make sure that you can never do it again! ( or at least make it damn hard to try again, such as what it sounds like is happening to you!
Hope some of that info helped you discover what may be the problem.
DM-Verity
ScarletWizard said:
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
Click to expand...
Click to collapse
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