Database Info

[STOCK][DUMP] Storage/Catalog for files related to the G7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I've been making a catalog with a lot of files related to the G7.
That includes boot, system and vendor images as well as some KDZ files that i need.​
You can probably find most of the stuff you need here.​
The link: https://drive.google.com/open?id=1bZwJVypZZLT6m9r_N2u1rJAxCz8kdiH2​Folder content and how to navigate:
Boot images
This folder contains some boot images for the g7 (specifically G710EM)
If the image has _patched in its name it means that it has Magisk included.
If the image has twrp_ in its name it means that it has TWRP included.
If it has both then it means that it has TWRP and Magisk included.
"TWRP_Pie.img" is for phones that run custom ROMs (9.0 + 8.1) with 8.0 vendor (old guide) (10b-10f)
"TWRP_RealPie.img" is for phones that run custom ROMs (9.0 + 8.1) with 9.0 vendor (new guide) (20c)
Click to expand...
Click to collapse
KDZs
This folder mostly contains KDZs for the G710EM but it also contains some KDZs from G710N and V405/409 (LG v40)
Still that doesn't mean that its finished because KDZ files take a lot of storage and i don't have terabytes of it.
Theres also LGUP installers and a LGUP dll for the G7 in "LGUP" folder.
ANd of course a lonely driver installer in the "Drivers" folder.
Click to expand...
Click to collapse
Other files
Nothing to care about. Move on.
Click to expand...
Click to collapse
Stock images
It contains plenty of images for different firmware versions (Mostly for the G710EM but its specified when its not from it).
It has System images, Vendor images, Boot images, apple images and some other not specified.
Everything completly pulled from stock.
Click to expand...
Click to collapse
Vendors
This folder contains patched vendor images for the G7.
"vendor_10b_securityoff.img" was the first vendor to be used for AOSP now we have a new guide with new files.
"vendor_10k_securityoff.img" same as above but for v10k firmware.
"vendor_gsi.img" this vendor is based on 20c G710N and its used for AOSP (new guide)
Click to expand...
Click to collapse
If you have any questions please ask them here!​

Thank you!
The boot_v10s.img in v10s folder is unpatched? I've to flash boot_10s-magisk.img in order to root the device?

pi3troz said:
Thank you!
The boot_v10s.img in v10s folder is unpatched? I've to flash boot_10s-magisk.img in order to root the device?
Click to expand...
Click to collapse
Yeah

LameMonster82 said:
Yeah
Click to expand...
Click to collapse
Thanks mate

Which one do I need to get magisk on Korean Pie upgraded G710EM model?

Michiel0912 said:
Which one do I need to get magisk on Korean Pie upgraded G710EM model?
Click to expand...
Click to collapse
Try TWRP_RealPie.img

Tried it. Did a data format to have access to data in TWRP but after booting I get a decryption unsuccessful message and keeps looping.

Michiel0912 said:
Tried it. Did a data format to have access to data in TWRP but after booting I get a decryption unsuccessful message and keeps looping.
Click to expand...
Click to collapse
Install back stock boot image. While TWRP works on stock data must stay untoched
Edit: you can download magisk manager and manually patch the stock boot image

Ok, I patched the boot image and everything is working. I will send you a link so you can put it on your drive. It is stock 20c boot with Magisk patch.
https://1drv.ms/u/s!AnYjRY0QyVw8jzHXdUC04lE9R5ER

Michiel0912 said:
Ok, I patched the boot image and everything is working. I will send you a link so you can put it on your drive. It is stock 20c boot with Magisk patch.
https://1drv.ms/u/s!AnYjRY0QyVw8jzHXdUC04lE9R5ER
Click to expand...
Click to collapse
No need. I have some boot images on my PC already patched. Also most people that are using this tutorial can't really use it

Can we use lg v40 kdz on lg g7?

sdiown said:
Can we use lg v40 kdz on lg g7?
Click to expand...
Click to collapse
No

I can't understand the steps that I have to do in order to get root on stock Korean Pie.
Do I have to follow this ones?
1. Download the patched Boot.img
2. Reboot to fastboot (and unlock bootloader????)
3. Flash the new boot.img with the commands fastboot flash boot_a pathtoboot.imghere and then fastboot flash boot_b pathtoboot.imghere
4. Reboot and install Magisk Manager Apk

delpere said:
I can't understand the steps that I have to do in order to get root on stock Korean Pie.
Do I have to follow this ones?
1. Download the patched Boot.img
2. Reboot to fastboot (and unlock bootloader????)
3. Flash the new boot.img with the commands fastboot flash boot_a pathtoboot.imghere and then fastboot flash boot_b pathtoboot.imghere
4. Reboot and install Magisk Manager Apk
Click to expand...
Click to collapse
Yes that's correct
Edit: right now there's no magisk patched Korean pie boot image on my gdrive so I will make one later. Don't install any other one. It will not work

I have seen that you uploaded the patched boot image for the G710N on Google Drive.
Can I use that for my G710EM?

delpere said:
I have seen that you uploaded the patched boot image for the G710N on Google Drive.
Can I use that for my G710EM?
Click to expand...
Click to collapse
If the software version matches then yes

Is anyone working on a bootloader unlock for other G7 models? I have a G7+ (LG710EAW)

What about installing only the TWRP on Korean Pie?
Do I need only to use this command?
HTML:
fastboot --set-active=a flash boot_a [TWRP_RealPie.img full path]
Thank you so much.

delpere said:
What about installing only the TWRP on Korean Pie?
Do I need only to use this command?
fastboot --set-active=a flash boot_a [TWRP_RealPie.img full path]
Thank you so much.
Click to expand...
Click to collapse
Yeah

An excellent compilation of files - everything what's posible to been necessary in one place ... But there is a question: when to expect boot v10t with magisk?

[HELP]Blank Flash For Moto G7 Power

my Moto G7 Power has suffered a hard brick and need the blank flash anyone has?
If you send me the download link.​

Have you checked this?

lubo777 said:
Have you checked this?
Click to expand...
Click to collapse
already,no work

Can you use the fastboot menu - it's it working (power on with volume down pressed)?

lubo777 said:
Can you use the fastboot menu - it's it working (power on with volume down pressed)?
Click to expand...
Click to collapse
so I need the blankflash the screen does not turn on I must have changed the boot,need to return to the fastboot screen only this

it can't understand you-can you boot in to the fastboot menu?

lubo777 said:
it can't understand you-can you boot in to the fastboot menu?
Click to expand...
Click to collapse
no

lubo777 said:
it can't understand you-can you boot in to the fastboot menu?
Click to expand...
Click to collapse
Im urgently need the blank flash for it

They found solution?

Update:
I finally got around to Unlocking the bootloader, and rooting.
The Terminal Emulator method wasn't working for me.
I flashed the new TWRP
[PORT] Unofficial TWRP for G7 Power by Geofferey
and used the steps in this thread
[GUIDE] How to create 'mmcblk0.img' from a working device? by kalyansundhar
and used
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/XT1955.5.mmcblk0.img bs=1000000000 count=30
The mmcblk0.img is almost 30gb, I'm compressing it, and uploading now may take awhile.
Old Post
I believe if someone with a rooted Moto G7 can pull a copy of the mmcblk0.img from their device with
Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
using these commands
Code:
su
GRANT Terminal emulator a Root Access
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
How to Unbrick (Debrick) Qualcomm Android Devices Using your SD Card
https://www.aryk.store/2019/09/unbrick-qualcomm-android-using-sd-card.html
and
[GUIDE] How to create 'mmcblk0.img' from a working device? by kalyansundhar
That mmcblk0.img can be used to boot the non-working G7 into Fastboot mode, as described in the links below
and then you just need to reflash the firmware.
[Guide] [Unbrick] How to revive a hard bricked Moto G5 by TheFixItMan
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
https://android.stackexchange.com/questions/125135/how-to-pull-mmcblk0-to-a-windows-pc
Edit:

Could you do the job you mentioned to repair my Moto g7 power?

patrick10K said:
Could you do the job you mentioned to repair my Moto g7 power?
Click to expand...
Click to collapse
I'm uploading a mmcblk0.img that I pulled from my XT1955-5 but my internet isn't great.

link ??

sd_shadow said:
I'm uploading a mmcblk0.img that I pulled from my XT1955-5 but my internet isn't great.
Click to expand...
Click to collapse
Is friend available now?

I finally got a copy uploaded.
XT1955.5.mmcblk0.img.zip
https://mega.nz/#!WKgHmIaB!CO57014-m-5NPcrI9Jt2-MCdnW4e7dajS7O5CpjeapY
Note: you have to change the block size in the command
Code:
bs=1000000000
it needs to be unzipped, and then follow steps in
[Guide] [Unbrick] How to revive a hard bricked Moto G5 by TheFixItMan
It should work for anything with a Snapdragon 632
G7, G7 Play but not the G7 Plus that has a Snapdragon 636

sd_shadow said:
I finally got a copy uploaded.
XT1955.5.mmcblk0.img.zip
https://mega.nz/#!WKgHmIaB!CO57014-m-5NPcrI9Jt2-MCdnW4e7dajS7O5CpjeapY
it needs to be unzipped, and then follow steps in
[Guide] [Unbrick] How to revive a hard bricked Moto G5 by TheFixItMan
It should work for anything with a Snapdragon 632
G7, G7 Play but not the G7 Plus that has a Snapdragon 636
Click to expand...
Click to collapse
it didn't work

podrias cargar loader.img???

patrick10K said:
it didn't work
Click to expand...
Click to collapse
Did you change the block size to match your device?
Ask who ever pulled the image what block size they used and then substitute those figures in the command in the guide to write the image
Also make sure your sd card is large enough - I'd say at least 64gb for this device

TheFixItMan said:
Did you change the block size to match your device?
Ask who ever pulled the image what block size they used and then substitute those figures in the command in the guide to write the image
Also make sure your sd card is large enough - I'd say at least 64gb for this device
Click to expand...
Click to collapse
I have a doubt my moto g7 power se brick why I restored the persist file of a motorcycle g4 plus in twrp that's why it was brick
Will there be a solution with the guide you mention?
---------- Post added at 08:49 PM ---------- Previous post was at 08:42 PM ----------
TheFixItMan said:
Did you change the block size to match your device?
Ask who ever pulled the image what block size they used and then substitute those figures in the command in the guide to write the image
Also make sure your sd card is large enough - I'd say at least 64gb for this device
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

patrick10K said:
I have a doubt my moto g7 power se brick why I restored the persist file of a motorcycle g4 plus in twrp that's why it was brick
Will there be a solution with the guide you mention?
Click to expand...
Click to collapse
It should load the bootloader off the sdcard (when you press the corresponding buttons to enter bootloader mode) where you can then reflash stock firmware
I've no idea what other damage to the motherboard flashing files from another device has caused
The persist partition maybe rebuilt on first boot - I'm not sure

How to get Android 11/ Realme Ui 2.0 on Realme C12. Update: Solved.

Greeting!
Anyone here that can help me. I have a Realme C12 a year ago It was updated to Android 11 but it was very unstable so I flashed back to Android 10. Now I want to flash Android 11 again but I tried flashing RMX2189_11_C.11 but it bricked my phone. Anyone know where I can download Android 11 Firmware for Sp Flash Tool.

Where you got C.11 update file to flash?

HemanthJabalpuri said:
Where you got C.11 update file to flash?
Click to expand...
Click to collapse
There are so many website to download them.
Such as:
Download Realme C12 RMX2189 Stock Firmware [Flash File]
www.firmware27.info
Realme C12 Firmware (RMX2189, RMX2184) - Realme Firmware
Realme C12 Firmware (RMX2189, RMX2184), Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com
I have tried every file. OZIP. Ofp. Every version with Ui 2.0 on both my Realme C12 but they don't work. Realme Flash Tool also say a error that suggest that the file is not for this device. But it is.
So if you can help me. Find Realme Ui 2.0 so I can flash with Realme Flash Tool, or using recovery, or SP Flash tool. I would really appreciate.
Btw I have flash the stock ROM which I got from here:
but I still need Ui 2.0. Also one of my Realme C12 did get the updated RMX2189_11_C.04. I updated it normally from the settings and all but that also made my phone stuck on Orange State. So I flashed back to stock.

@RehanRashid
I made C.11 ozip that you can flash in TWRP, so unlock bootloader and flash TWRP to flash this ozip. Don't forget to use nocrypt variant of TWRP from my thread. Also Format Data using `fastboot -w` after flashing ozip.
RMX2189_11.C.11_1110_202203092226.zip
drive.google.com
Let me know if you get any issues
Thanks

HemanthJabalpuri said:
@RehanRashid
I made C.11 ozip that you can flash in TWRP, so unlock bootloader and flash TWRP to flash this ozip. Don't forget to use nocrypt variant of TWRP from my thread. Also Format Data using `fastboot -w` after flashing ozip.
RMX2189_11.C.11_1110_202203092226.zip
drive.google.com
Let me know if you get any issues
Thanks
Click to expand...
Click to collapse
Thanks Bro. I will update you.

HemanthJabalpuri said:
@RehanRashid
I made C.11 ozip that you can flash in TWRP, so unlock bootloader and flash TWRP to flash this ozip. Don't forget to use nocrypt variant of TWRP from my thread. Also Format Data using `fastboot -w` after flashing ozip.
RMX2189_11.C.11_1110_202203092226.zip
drive.google.com
Let me know if you get any issues
Thanks
Click to expand...
Click to collapse
Bro I have booted into TWRP nocrypt variant. But upon clicking Install or File Manager. All the folders are showing as random names or numbers. The non nocrypt variant works fine.

RehanRashid said:
Bro I have booted into TWRP nocrypt variant. But upon clicking Install or File Manager. All the folders are showing as random names or numbers. The non nocrypt variant works fine.
Click to expand...
Click to collapse
Yeah, it is because decryption is removed from that variant. I thought you can use Micro SD Card. ADB sideload will work too.

HemanthJabalpuri said:
Yeah, it is because decryption is removed from that variant. I thought you can use Micro SD Card.
Click to expand...
Click to collapse
Can you link me the way to do it through ADB Sideload?

HemanthJabalpuri said:
Yeah, it is because decryption is removed from that variant. I thought you can use Micro SD Card. ADB sideload will work too.
Click to expand...
Click to collapse
How to Flash Custom ROM using ADB sideload [Easy Steps]
Flash Custom ROM zip file with ADB and Fastboot commands on any Android phone. Install Custom Firmware without TWRP recovery using CMD.
www.droidthunder.com
This guide?

RehanRashid said:
How to Flash Custom ROM using ADB sideload [Easy Steps]
Flash Custom ROM zip file with ADB and Fastboot commands on any Android phone. Install Custom Firmware without TWRP recovery using CMD.
www.droidthunder.com
This guide?
Click to expand...
Click to collapse
Yes, in short
- Enable enable 'Skip Treble compatible error' in TWRP Settings
- Go to Advanced => ADB Sideload
- Swipe the bar and connect to PC
- Place the .ozip in your PC and run sideload command
- `adb sideload C.11.ozip`
- After completing, boot to bootloader mode and run `fastboot -w`

HemanthJabalpuri said:
Yes, in short
- Enable enable 'Skip Treble compatible error' in TWRP Settings
- Go to Advanced => ADB Sideload
- Swipe the bar and connect to PC
- Place the .ozip in your PC and run sideload command
- `adb sideload C.11.ozip`
- After completing, boot to bootloader mode and run `fastboot -w`
Click to expand...
Click to collapse
Stupid Question but does it matter if the file extension is .zip or .ozip?

HemanthJabalpuri said:
Yes, in short
- Enable enable 'Skip Treble compatible error' in TWRP Settings
- Go to Advanced => ADB Sideload
- Swipe the bar and connect to PC
- Place the .ozip in your PC and run sideload command
- `adb sideload C.11.ozip`
- After completing, boot to bootloader mode and run `fastboot -w`
Click to expand...
Click to collapse
Thanks it worked! Btw how did you get the Zip file. For some reason I dont get update in settings so when the next update rolls out, How can I update then?

RehanRashid said:
Stupid Question but does it matter if the file extension is .zip or .ozip?
Click to expand...
Click to collapse
Ah, I forgot that it is a zip file. Anyway, it doesn't matter ozip or zip.
RehanRashid said:
Thanks it worked! Btw how did you get the Zip file. For some reason I dont get update in settings so when the next update rolls out, How can I update then?
Click to expand...
Click to collapse
I got C.11 update(at that time it latest) when I am on C.05 and grabbed the update. I don't know how to update to newer versions like C.13 if you can't get it in settings. I can't make newer versions right now since I don't have PC anymore to experiment things.
Thanks

@RehanRashid
I guess you are still in C.11 and if it is then Can you please run below commands and give me getprop.txt file in Internal Storage please. with this I will try to make C.13 zip
`adb shell`
`getprop >/sdcard/getprop.txt`

HemanthJabalpuri said:
@RehanRashid
I guess you are still in C.11 and if it is then Can you please run below commands and give me getprop.txt file in Internal Storage please. with this I will try to make C.13 zip
`adb shell`
`getprop >/sdcard/getprop.txt`
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry bro for some reason, I never got an notification for your message. Hopefully, I can still help.

Rooting Pixel 4a

I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.

XZNZI said:
I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.
Click to expand...
Click to collapse
Not a lot to go on from you description,, So is this what's been done? Bootloader unlocked, oem unlocking toggled, magisk installed,,, magisk patched boot.img available and the adb command sent "fastboot flash boot patchedboot.img" ??

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.

XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
What version of ADB Platform Tools are you using?
Are you absolutely sure you're using the right firmware?
Why did you downgrade?
Are you following one of the several guides? If not, you should be.

XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
Maybe some of the steps on this page might help you:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com

EngineerMind said:
Maybe some of the steps on this page might help you:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Click to expand...
Click to collapse
That guide is very out of date.

V0latyle said:
That guide is very out of date.
Click to expand...
Click to collapse
It is, but since he mentioned Android 10, some of it might help him with his issue because it relates to Andorid 10

XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com

hammered58 said:
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
I download a mini version of the andriod tools and rooted my phone. I attempted to flash TWRP 3.5 for Android 10 for Pixel which failed. Error: Not allowed to flash to recovery. Debugging on Unlocked and rooted..

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery​View attachment Samsung-Logo-MSP.webp​
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers
Note :-​
Samsung binery is impossible to downagrade. ​This method will do install old stock as a custom rom (signature removed stock rom). So this method only can downgarde android version. ​This method cannot downgrade modem or radio or bootlooder such as (aboot,lk,non-holes) like critical images. if you try that it will dead your device​
Click to expand...
Click to collapse
Not Tested in All Devices. So I Don't know this method is working for all samsung devices. Proofs are at the end. You Have to try and tell
What you need​
Latest binery of stock rom that you need to downgrade​
Bootloader Unlocked Device​
Lz4 Unpacker​
Simg2img.exe​
Hxd​
Android Image kitchen​
Odin​
7zip​
Windows Computer
​If you have super.img device shipped with Android 10 or Android 10+​You must have unlocked bootloader​If your device cannot use magisk this method will not work for you. (A20s user cannot do this) ​
1. Unlock your device bootloader​2. Download the Latest binery of stock rom that you need to downgrade (samfw)​3. Extract the whole Ap.....tar.md5​Get all boot.img.lz4 recovery.img.lz4 super.img .lz4(vendor.img.ext4.lz4 and system.img.ext4.lz4)​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Convert .lz4 to img​Grag and drop lz4 file to lz4.exe​​5. Then Patched the boot.img with magisk and unpack and repack recovery.img using android image kitchen (aik)​6. Then paste simg2img.exe to where converted super.img located.​
7. Then open cmd from there and type simg2img super.img super.raw​then you will get a super.raw​
8. Open HXD and grag and drop super.raw to hxd​​9. Then CTRL+F and search all the U number of the firmware you downloded​According to me it is U4​
9. Then Find a phases like this and fill all phases with zero bytes (there should be more than one)​
10. Then Save it and remove the super.raw.bak​11. Then Rename the super.raw to super.img and make tar with 7zip including patched boot.img recovery.img and super.img​12. Flash it and Format data​
Patched vbmeta is not essential due to magisk patched boot.img​
If you Have System.img and Vendor.img Device Shipped with Android 7 8 9​​1.Do all the steps untill number 6​2.Then convert system.img.ext4 and vendor.img.ext4 to raw by open cmd then, simg2img.exe system.ext4.img.raw and same to vendor​3.Open both System.ext4.img.raw form Hxd and Countinue with step 9​4.Then save Both vendor and system and delete the .bak files​5.Then rename system.img.ext4.raw to system.img.exe4 and vendor.img.ext4.raw to vendor.img.ext4​6.Then Convert to Lz4 by open cmd and lz4 -1 system.img.ext4​7.Then Make tar using Magisk patched boot.img and repacked recovery.img and system.img.ext4.lz4 and vendor.img.ext4.lz4​8. Flash and wipe Data​
Patched vbmeta is not essential due to magisk patched boot.img​​Proof Tested Devices,​
Samsung Galaxy M01 (Qualcomm)
Downgrade Android 12 to android 10 (u4 to u3)
Samsung Galaxy A71 Qualcomm
Android 13 to Android 10 (U8 to U3)
Updates​
Some users said they cannot flash super.img in a51 and s20 exyons version. May be this method will not work for exyons. I dont know that need to test more
Downgrade success for s20 fe 5g qcom using this method
Still not tested on MTK
Video Tutorial​
Remove Signature from Super or System/Vendor​
Downloads​Hxd
This method also can use for update android version without upgrading binery version.​

Interesting.. I'll try it when I get back my pc

tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding

oznear said:
tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding
Click to expand...
Click to collapse
Try with replace vendor/firmware from u4 stock (dosent depend on android version)

Hi, If I flashed it through Odin, do I still need to supply the BL, CP, CSC? Thanks in advance.

A10 -> A9 9 on SD S10: the flashing itself works but device's now stuck on booting - cannot get to A9 recovery

jq555888 said:
Android 10 -> Android 9 on snapdragon S10: the flashing itself appeared to work but device's now stuck on booting - cannot get to Android 9's recovery for some reason which I suspect is due to a different partition layout (device's shipped with Android 9); tried to erase userdata with Android 10's recovery but still can't get it to finish booting. Any ideas?
Click to expand...
Click to collapse
You used latest version of android 9?

smiley9000 said:
You used latest version of android 9?
Click to expand...
Click to collapse
Yeah - this was last version of A10 - A9

jq555888 said:
Yeah - this was going from G9700ZHU4DTL2 (last version of Android 10) to G9700ZCS2ASJU (last version of Android 9)
Click to expand...
Click to collapse
stuck in android boot animation?

smiley9000 said:
stuck in android boot animation?
Click to expand...
Click to collapse
yes! it's like the startup screen

jq555888 said:
yes! it's like the startup screen where it usually says the phone's model (with the text "this phone is not running official software"). it's the one after pressing the side button, but not the "SAMSUNG" screen.
Click to expand...
Click to collapse
enable usb debugging and try to get logs

smiley9000 said:
enable usb debugging and try to get logs
Click to expand...
Click to collapse
thank you! any way to achieve this by modifying the official A9 rom?

jq555888 said:
thank you! any way to achieve this by modifying the official A9 rom?
booting to twrp for A9 also fails not sure if it's a parition problem but A10 twrp works
Click to expand...
Click to collapse
maybe due to kernel

hello ! i have a problem with Android image kitchen , when i click repackimg.bat he say me
Fichier introuvable
Paramètre incorrect.
Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers
Packing ramdisk (as root) . . .
Windows sudo required but not found.
*** Reinstall Android Image Kitchen, then add ***
*** sudo.exe to your antivirus exceptions! ***
Error!
how can i fix this pls?

Thanks for taking the trouble to make this thread @smiley9000
Anyone tried this on s10e exynos variant with android 12 - downgrade to android 10 ?