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
don't flash it if you don't have the exact build or you'll mess up your phone
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.
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
Used the boot for the same build right down to the 220716 and I still lost Wi-Fi and sound??
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 ?
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
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?
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
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
Last edited:
SV55216_01.02.04.230415: boot/recovery and Magisk-patched boot images plus vbmeta.
Last edited:
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
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
Last edited:
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.imgthen 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.
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?
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!
When trying to flash, it says download is not allowed on locked devices.
Thanks!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
433Figured 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.2just 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 need2
just do adb reboot bootloader and fastboot oem unlock
plenty of tutorials in xda to show you how to do that
New posts
-
-
TCL 2021 Android TVs (C05/G05/BeyondTV6/BeyondTV4)- Latest: sidhuskids00
