yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] luridphantom:
there is a way to do it involving using the dsu loader feature to temp boot a pre-rooted gsi image, using that to dump the boot image using dd, then booting normally into the system to patch the boot image using magisk

due to work i have no time for a full writeup. its for the very technically experienced and if you're not familiar with rooting, has a high risk of bricking your device

all the problems people have are related to flashing an incorrect rooted boot img to their device. if you follow the hints in the first paragraph you will have no problems as i did
[Android Q&A, Help & Troubleshooting] menriquez:
thanks again for your replies and work on this project. it might make some sense to mention to people that unlocking your bootloader will reset your device and you will have to set it up again and such.

i'm very slowly working my way thru your guide as i really want to get this particular phone rooted and cleared of any crap so ill keep everyone posted with my progress and questions....
[Android Q&A, Help & Troubleshooting] menriquez:
ok...a few more questions...isnt TWRP able to flash GSI images as well? Also, exactly which version GSI would you want to use to get at the preexisting boot.img system (using DD of course)?

There are Android 11, 12, and even 13beta versions of GSIs [ https://developer.android.com/topic/generic-system-image/releases ] but after spending the last hour researching, im coming to the conclusion that we wont be able to find a GSI that is compatable with our cheap -o phone here..

In fact, going to developer options on the phone and hitting "DSU Loader" gives me the cryptic "No DSU Available for this device" message....so good luck going the route you had mentioned.
[Android Q&A, Help & Troubleshooting] luridphantom:
the boot loader is unlock able and it's a given that you need it unlocked otherwise forget about flashing or rooting
[Android Q&A, Help & Troubleshooting] luridphantom:
there is no twrp for it, you need to download the recovery img i posted earlier and build it yourself if you want to go that route

since you're that curious, you need to install an app that determines what treble build you need, then download the actual gsi from https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/

load it into an app called dsu loader that will handle the temp flashing for you, then you will have temp root at the boot logo. don't forget to reboot once you're done pulling your boot img to get back to your normal state
[Android Q&A, Help & Troubleshooting] Impr0ve:
woot!!! I was able to fix all my phones thanks to this, here is the boot.img if it would help anybody this is only for build SV55216_01.01.08.220413 though so only use if you have that build thanks luridphantom this was the info I needed to get it working again :)
[Android Q&A, Help & Troubleshooting] luridphantom:
congrats man glad you figured out all the clues
[Android Q&A, Help & Troubleshooting] Tapout007:
I did as well, actually logged in for once to post the boot.img /magisk boot.img (for same phone/version) as ^^^. thank you for that gsi hint.... Never played with gsi's and can definitely use the info in the future.
[Android Q&A, Help & Troubleshooting] Tapout007:
Now to get qcsuper working on it ....
[Android Q&A, Help & Troubleshooting] Impr0ve:
do you think we could use qcsuper to unlock the device for any sim? also what were you gonna use it for?
[Android Q&A, Help & Troubleshooting] Unitethedivided:
Can someone plz explain to me how those rooting directions work since in order to use the twrp app to backup existing recovery it expects you to already be rooted and does anyone have the boot image for the 01.01.0822413 firmware! Plz and ty guys
[Android Q&A, Help & Troubleshooting] Unitethedivided:
Nvm just saw it was posted thanks for the img
[Android Q&A, Help & Troubleshooting] adjustall:
How are you OEM unlocking? I don't have that option nor developer options on build SV55216_01.01.08.220413

Edit:

Derp.. A web search for"Enable adb debugging on your device" answered it.
[Android Q&A, Help & Troubleshooting] fstopkid:
I have this same build as well, but would you mind explaining how you unlocked the bootloader please?
[Android Q&A, Help & Troubleshooting] luridphantom:
install adb, adb reboot bootloader, fastboot flashing unlock
[Android Q&A, Help & Troubleshooting] adjustall:
I get "No DSU available for this device"
[Android Q&A, Help & Troubleshooting] adjustall:
Mind sharing your steps?
[Android Q&A, Help & Troubleshooting] luridphantom:
all the clues you need are in post #44, just use dd to pull the boot image once you get temp root
[Android Q&A, Help & Troubleshooting] adjustall:
So from what I have gathered. FYI, have not tested all of this YMMV

Using two schok volt sv55 phones:

https://xdaforums.com/t/umx-u696cl-unofficial-root-thread.4446111/

Using one phone:

1. OEM Unlock your device.

a. "Settings" -> About Phone": tap "Build number until a notification for "developer options" appears.​

b. "Settings" -> "System" -> "advanced" -> "developer options": enable " USB debugging", enable "OEM unlocking"​

c. adb reboot bootloader​

d. while at the boot loader menu: fastboot flashing unlock (this wipes all non factory info from phone)​

2. Root your device.

a. Boot rooted rom via DSU Sideloader.​

b. back up your rom​

c. follow directions in post https://xdaforums.com/t/schok-volt-sv55-firmware.4406171/post-86936121​
[Android Q&A, Help & Troubleshooting] luridphantom:
don't think there's a twrp build for this phone

you don't even need twrp for backup if you know how to use dd to pull each partition and note their locations while you have temp root
[Android Q&A, Help & Troubleshooting] Unitethedivided:
Me too so plz anyone that can help
[Android Q&A, Help & Troubleshooting] Impr0ve:
do I have to pull them individually or can I just do mmcblk0? and what about the swap do I need that also? is there a good tutorial already for this? is it ok to dd while in use and not in gsi?
[Android Q&A, Help & Troubleshooting] luridphantom:
i believe you need to pull them individually because each partition is symlinked and there is no mmcblk0. i might be wrong though so feel free to try dding your entire nand if you want but be careful of what goes in the input and output params. if you got some scripting savvy try using wildcards to automate partition dumping for you.

if you're already rooted just use this app https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en_US&gl=US
[Android Q&A, Help & Troubleshooting] heybrother_:
This process has rendered my phone stuck in a bootloop. oes anyone have the stock ROM please. Whatever build is fine. Also if you have the vbmeta img that would be awesome.
[Android Q&A, Help & Troubleshooting] luridphantom:
if your boot loader is unlocked, just try flashing all the posted boot images if you can't follow the more complicated steps throughout the thread

and you can disable vbmeta by flashing an empty one
[Android Q&A, Help & Troubleshooting] Smil3yWulf:
Hey I Flashed youre Boot, now i dont WIFI working i didnt know what version i was ..Now i need Stock Boot and Recovery from SV55216_01.01.06.211209
[Android Q&A, Help & Troubleshooting] adjustall:
build?

It is not possible to do this via DSU. There isn't enough space on my brand new phone. DSU loader complains.
[Android Q&A, Help & Troubleshooting] Impr0ve:
I did it with dsu you just have to clear some space maybe backup some of your stuff somewheres so you can clear it out and then try again
[Android Q&A, Help & Troubleshooting] adjustall:
There's nothing on this phone yet. Which one did you use? I've tried lineage-18.1-20220715-UNOFFICIAL-a64_bvS-vndklite and lineage-18.1-20220715-UNOFFICIAL-a64_bgS-vndklite
[Android Q&A, Help & Troubleshooting] Impr0ve:
I used lineage-18.1-20220715-UNOFFICIAL-a64_bgS.img.xz and had no problems are you using this https://github.com/VegaBobo/DSU-Sideloader I used that to load it
[Android Q&A, Help & Troubleshooting] adjustall:
lineage-18.1-20220715-UNOFFICIAL-a64_bgS.img.xz worked without issue. Thanks. The others would sit at the boot screen.

I did change the user space to 1GB for all of them just in case.
[Android Q&A, Help & Troubleshooting] luridphantom:
just a quick note if you're stuck on the boot screen like i was when using the dsu loader, you can still adb shell -> su to get a root shell to do whatever you need
[Android Q&A, Help & Troubleshooting] Lyrin:
What's the name of the app?
[Android Q&A, Help & Troubleshooting] funkybluemonkey3:
OrangeFox_10_Recovery-UMX_U693CL boots fine on this device. Here's stock recovery and boot from SV55216_01.01.09.220716 if needed. recovery boot
[Android Q&A, Help & Troubleshooting] Lyrin:
THANK YOU! I was nearly pulling my hair out trying to dump this!
[Android Q&A, Help & Troubleshooting] funkybluemonkey3:
Yay I'm helping!!! lol
[Android Q&A, Help & Troubleshooting] Lyrin:
Do you know if it's possible to flash one of the LineageOS images from page 3? lineage-18.1-20220715-UNOFFICIAL-a64_bgS.img.xz worked for DSU, and I'd like to use it instead of the stock rom.
[Android Q&A, Help & Troubleshooting] luridphantom:
if it works for dsu it should work when you flash it. just back up everything before doing so
[Android Q&A, Help & Troubleshooting] Lyrin:
How should I do that? I tried OrangeFox_10_Recovery-UMX_U693CL as the other guy mentioned, but it doesn't work when I flash it, I just got a messed up screen when booting it.
[Android Q&A, Help & Troubleshooting] luridphantom:
some other folks around here got it but when temp booted into the dsu from dsu loader you need to make a backup through dd
[Android Q&A, Help & Troubleshooting] Lyrin:
I've made the backup, but I'm not sure how to flash the GSI now. I looked at this guide, but fastboot says there's no system partition to erase. So I'm not sure how to proceed.

Edit: I figured out how to do it, and I ended up having to delete the product partition to have enough space for the GSI, but after flashing I get stuck on an infinite loading screen for LineageOS.

Edit 2: I got it working! Apparently using Google Apps breaks it, even though the image working for DSU before. The issue I'm facing now, is that I can't get it to connect to my provider's network. I can make calls, but not use mobile data.

Edit 3: Figured it out, apparently the GSI defaults to 3G instead of LTE for some reason.
[Android Q&A, Help & Troubleshooting] Lyrin:
I'm back again, trying to install a GSI on another phone, but somehow the wifi chip seems to have gotten disabled? I'm trying to enable wifi in settings, but it fails. It happened after I flashed a rom, but going back to other roms that were working isn't working, so I'm not sure what to do.

Edit: I found a post saying I should flash the persist image. Can someone dump the one for 01.01.08? That's the version this phone uses. Vendor may be useful too.
[Android Q&A, Help & Troubleshooting] :
A
[Android Q&A, Help & Troubleshooting] edsel_man:
I've flashed my SV55 with funkybluemonkey3's boot.img posted Aug 24, 2022 on page 4, and I got my WiFi and audio working again, which stopped working when I flashed either Impr0ve's boot.img from Jul 22, 2022 on page 3 or luridphantom's newschokboot.img posted on May 18, 2022 on page 1.

To anyone who has lost functionality flashing with the first few images posted on this thread, I highly recommend flashing with funkybluemonkey3's boot.img.
[Android Q&A, Help & Troubleshooting] Hamood_sail:
I tried this boot but still the same problem my wifi can't work does any one have the boot for SV55216_01.01.07.220105
[Android Q&A, Help & Troubleshooting] X_shinobi.apk_X:
Wipe data and cache, if possible delvik cache
[Android Q&A, Help & Troubleshooting] #SCCTV:
post #73 I was able to root with boot image from my same build SV55216_01.01.09.220716 image from successfully installed GSI image lineage-19.1-20221011-UNOFFICIAL-a64_bgS.img.xz that has Gapps embedded here

https://sourceforge.net/projects/an...1-20221011-UNOFFICIAL-a64_bgS.img.xz/download

Device connected to network can detect in and outgoing calls but it crashes no sound any time you attempt to use voice or open a dialer and dial out immediately cuts off and no system sound. On GSI ROM dialer will answer no sound and then crash reboot the system. Can I fix through edit build prop??? Can I send a logicat file for help?

I have tried all boot images on this post no success...

Wipe data and cache if possible delvik cache, this did not fix these issues

This recovery worked for me

OrangeFox_11_Recovery-UMX_U693CL
[Android Q&A, Help & Troubleshooting] somnomania:
I just attempted to root this phone as well, and am having the same difficulty as others with the wifi not working, the system hanging periodically, and the sound not working. I used funkybluemonkey3's boot.img. I don't know what "wipe data and cache" means in this context; for apps? For the phone itself? If the latter, how do I do that? Would love to get this working, I've been trying to root a different piece of crap from Assurance Wireless with no success yet, and it'd be cool if I finally had a working phone in my life.
[Android Q&A, Help & Troubleshooting] #SCCTV:
I think we are screwed until we get firmware or a firmware image or TWRP image or Fox recovery image. Someone posted a clue I didn't figure it out until I replaced the boot image. Not sure why they didn't give clear instructions, just clues and not fully articulating on a tech board to help individuals it's like setting you up for failure. From my research you can use the image that I linked in my first reply it's rooted. Then you have to install the DSU loader and a phh Superuser app through ADB. For the temp root then you do a partition backup of stock os. I am assisting the best that I can I'm still learning. I used a bunch of different magic modules to replace the sound system framework nothing worked. I believe something is off with the boot image that we flash for a particular build and the only fix would be a firmware snatch of the Boot image. I thought since we had no sound w/ phone dialer crashes, just replacing each of those would fix the corrupted stock OS.

*Before flashing this phone with a GSI , we should have been linked to this important topic right here and that would have stopped most of us from having errors.

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​

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

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...

xdaforums.com
[Android Q&A, Help & Troubleshooting] jayleemcnabb81:
At the risk of sounding completely ignorant (which I am semi use to in this area), would there be anything I could do to help? I have 3 of these phones. First one I rooted with the same issues as everyone else (namely no sound) , the 2nd has a bad charging port (which I can work around) and the 3rd I just don't like. So, lmk.

~J~
[Android Q&A, Help & Troubleshooting] robbkm3:
Hi does anyone have or can backup and share the super partition.
[Android Q&A, Help & Troubleshooting] DBlake1:
Figured I'd contribute to this thread a bit. Here's the latest boot.img from the latest OTA that was pushed (2022-10-20, stock and Magisk 25.2 patched). I've had no sound issues as of this moment. Ring and media are working fine as far as I can tell.

I'll try and stay up to date on latest boot IMG and I'll try to capture the next OTA if I can.
[Android Q&A, Help & Troubleshooting] mrhanky89:
any updates? I can't even do the ota update with cell phone data because there is a verification error

i tried relocking and putting stock boot.img but it tells me that the device is corrupt
[Android Q&A, Help & Troubleshooting] Mello1420:
Any chance you could share how or where you got that latest .img?

I still can't get this damn phone to even slightly connect to my computer 😑
[Android Q&A, Help & Troubleshooting] DBlake1:
Mine didn't have any issues connecting via USB (adb and fastboot). Not sure what's going on there.

I unlocked the bootloader and then I used the pre-rooted GSI/DSU method with DSU Sideloader explained somewhere in a thread about this phone. I forget where I read about it on here. It took me like 3 different tries to get it to work, but now since I've done it and dumped the boot.img, I don't have to do it again. ;)
[Android Q&A, Help & Troubleshooting] Mello1420:
Fair enough, I just got into adb and fastboot yesterday but failed to plug into my laptop to check if it was going to cooperate or not. So that's my next step n the rest as you mentioned once I figure it all. Thanks
[Android Q&A, Help & Troubleshooting] rogjr1986:
Why doesn't anybody upload a rooted boot image and then put your phone in fastboot and then fastboot boot said boot image?

That will root your phone temporarily because you're booting that rooted boot image

and then you can dump your boot image with DD
[Android Q&A, Help & Troubleshooting] JohnM_rit:
It went totally flawlessly, because of that. Thank you.

For noobs: with my laptop, I

1. Grabbed the zip with the modified boot.img, above: There are 2x files in the zip, you need the 'magisk_patched-25200_VpP6u.img' file, not the untouched boot.img.

2. Had the ADB and Fastboot command line tools installed on my laptop: https://developer.android.com/studio/releases/platform-tools

3. Turned on the hidden 'Developer Options' (go to 'About Phone' and tap 'Build number', at the bottom, until it says you are a developer)

4. Went into the 'Developer Options' menu, and turned on 'OEM Unlock', 'USB Debugging', and set 'Default USB Configuration' to 'File Transfer' - that last step is so ADB works; I've found it's needed.

5. Sent 'adb devices' from an administrative command prompt, on the laptop, to verify adb was working. If the response is blank, it's not. Check your USB cable connection, etc. Should see a long string of numbers, '12345678901234 device'.

6. Sent 'adb reboot fastboot'. This reboots the device into fastboot to flash the modified magisk boot image.

7. Sent 'fastboot devices' to make sure fastboot was working.

8. Sent 'fastboot flashing unlock'. This prompts you to agree. Using your volume keys, select the unlock option. THIS WILL ERASE EVERYTHING ON THE PHONE!

9. Let the phone erase and reboot. Selected the 'offline setup'. Turned on Developer Options, USB Debugging and File Transfer mode again.

10. ADB Devices, again. Then 'adb reboot fastboot' again.

11. 'fastboot flash boot magisk_patched-25200_VpP6u.img'. Then reboot normally.

12. Grabbed a copy of the Magisk apk from the magisk website, and used Files (built-in file manager) to open/install it.

13. Magisk indicates it needs to reboot to finish setup, select OK and let the device reboot.

14. When prompted, continue your setup of the phone (cloning another phone's accounts across your wifi).

15. Add F-Droid, and then Fox's MMM module manager from F-Droid, to add modules to Magisk.
[Android Q&A, Help & Troubleshooting] alecxs:
actually, this command is for fastbootd. for fastboot mode

adb reboot bootloader
[Android Q&A, Help & Troubleshooting] omb714.1980:
How do I do that, change the size? Fastboot command? Also does anyone have the boot.img for SV55216_01.01.09.220716
[Android Q&A, Help & Troubleshooting] luridphantom:
boot and magisk patched images for sv55216_01.02.01.221020

don't flash it if you don't have the exact build or you'll mess up your phone
[Android Q&A, Help & Troubleshooting] NishiMoon52:
SV55216_01.02.01.221020

Newest OTA update zip releaseed 02/26/23

File size: 148mb
[Android Q&A, Help & Troubleshooting] Jayx0xWolf:
The zip won't open?
[Android Q&A, Help & Troubleshooting] hackerx23:
I unlocked the bootloader by going to about device and tapping build number 7 times to activate developer options. Once in developer options I toggled allow OEM unlock, and USB debugging. I then downloaded bug Yeager on another device and tethered the two I then booted the device I wanted to unlock the bootloader into fastboot and pushed the commands "fastboot flashing unlock". Got a warning about how dangerous it is to unlock the bootloader and that's basically it. Now I'm having the same trouble trying to find a stock image to flash so I could root my device.
[Android Q&A, Help & Troubleshooting] luridphantom:
if your firmware versions match then use one of the boot images in this thread to root

otherwise theres tutorials around here on how to use the dsu loader to pull your boot partition to root it
[Android Q&A, Help & Troubleshooting] Jayx0xWolf:
Used the boot for the same build right down to the 220716 and I still lost Wi-Fi and sound??
[Android Q&A, Help & Troubleshooting] funkybluemonkey3:
I believe the problem is a mismatch with the baseband version and version of the stock ROM loaded. Try matching a boot version to whatever version ROM is on the device currently. @luridphantom Do you still have this device that you can pull current boot and rom from to help @Jayx0xWolf ?
[Android Q&A, Help & Troubleshooting] Jayx0xWolf:
I have another SV55216_01.01.09.220716 and I used the boot image to flash magisk it worked perfectly. Thinking I'll pull it's boot image and flash it see what I get
[Android Q&A, Help & Troubleshooting] luridphantom:
no, i don't update my phones. try asking around
[Android Q&A, Help & Troubleshooting] Jayx0xWolf:
@funkybluemonkey3 I have the latest OTA but it has the boot.image.p files so no help at all
[Android Q&A, Help & Troubleshooting] Jayx0xWolf:
I am somewhat proficient at this sort of work but still a noob in some ways. Can you help me understand why the boot img is good for one device with the 220716 build and not another?
[Android Q&A, Help & Troubleshooting] Jayx0xWolf:
Boot, magisk patched and vbmeta for SV55216_01.02.02.230111

I forgot to add that I fixed two phones l that had the Wi-Fi and audio problem from the wrong boot images. I flashed the super from a working one on both and it didn't matter which I had it just started working and said they that it was at the same model as
[Android Q&A, Help & Troubleshooting] Travisholt92:
Very interesting 🤔
[Android Q&A, Help & Troubleshooting] SierraFife:
SV55216_01.02.04.230415: boot/recovery and Magisk-patched boot images plus vbmeta.
[Android Q&A, Help & Troubleshooting] Jayx0xWolf:
Any luck with a twrp for this phone? If anyone could port i would love to help
[Android Q&A, Help & Troubleshooting] LusciousDark:
I desperately need the stock rom for SV55216_01.02.04.230415

I lost mine and my system. Img has become corrupted and I can only boot into fastboot and recovery. I have the boot recovery vbmeta boot abootbak and oem image files but hasn't helped me
[Android Q&A, Help & Troubleshooting] SierraFife:
I'm still kinda new to this but my phone is running SV55216_01.02.04.230415 so here's what I've done:

(Phone shell)# dd if=/dev/block/mapper/system of=/sdcard/system.img

then used adb to pull system.img to the host machine. It's a ~600 mb file but I compressed it down to about 300.

Is this what you needed? I see a few other options (product, system_ext, vendor) so please let me know if any of those would be useful as well.
[Android Q&A, Help & Troubleshooting] e34rrsff:
I have also messed up my system bit, but flashing the orangefox recovery actually works, kinda. theres no menu, it just gives you root adb access. anyone else know if theres a twrp available?
[Android Q&A, Help & Troubleshooting] e34rrsff:
Can you try contacting schok asking for the stock firmware?
[Android Q&A, Help & Troubleshooting] uslacker99:
Does the phone need to be device (carrier) unlocked before you can flash?

When trying to flash, it says download is not allowed on locked devices.

Thanks!
[Android Q&A, Help & Troubleshooting] luridphantom:
sim and bootloader unlocking are 2 different things