Database Info

[Recovery] TWRP 3.2.2.0 for redmi 6 pro ( sakura )

{
"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"
}
IM NOT THE CREATOR OF THIS TWRP, FOUND IT SPMEWHERE AND WANTED TO SHARE IT​
installation:
1. Setup ADB/Fastboot
2. Download the twrp from here : download
3. Power off your device.
4. Hold volume down + power button to boot into the bootloader.
5. Connect your device to your PC with a USB cable.
6. Open the command prompt on your PC.
7. Type cmmand : fastboot flash recovery "filename of recovery.img"
done
If u have anti rollback enabled :
first method:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
2nd method:
fastboot flash antirbpass "recovery.img"
changelog:
What's new in 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
for further questions and discussion join telegram group here

nofx161 said:
IM NOT THE CREATOR OF THIS TWRP, FOUND IT SPMEWHERE AND WANTED TO SHARE IT​
installation:
1. Setup ADB/Fastboot
2. Download the twrp from here : download
3. Power off your device.
4. Hold volume down + power button to boot into the bootloader.
5. Connect your device to your PC with a USB cable.
6. Open the command prompt on your PC.
7. Type cmmand : fastboot flash recovery "filename of recovery.img"
done
changelog:
What's new in 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
for further questions and discussion join telegram group here
Click to expand...
Click to collapse
C : \ adb> fastboot flash recovery sakura . img
sending 'recovery' (47604 KB)...
OKAY [ 1.562s]
writing 'recovery'...
FAILED (remote: rollback version downgrade)
finished. total time: 1.578s

evl01 said:
C : \ adb> fastboot flash recovery sakura . img
sending 'recovery' (47604 KB)...
OKAY [ 1.562s]
writing 'recovery'...
FAILED (remote: rollback version downgrade)
finished. total time: 1.578s
Click to expand...
Click to collapse
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"

nofx161 said:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"
Click to expand...
Click to collapse
Now is asking for a password to decrypt. What should I put there?
---------- Post added at 10:53 PM ---------- Previous post was at 10:48 PM ----------
evl01 said:
Now is asking for a password to decrypt. What should I put there?
Click to expand...
Click to collapse
When I put cancel, I can enter to recovery but I can't use any storage. It's 0mb

If you factory reset through twrp and reboot recovery it should be OK. But keep in mind to do a backup of your stuff first.

Hello,
TWRP is released under GPLv3+. It means that if you submit a build of TWRP, you need to distribute its source code and instructions to build it.
Where did you find this build if you "found it somewhere and wanted to share it"? You are basically violating the license by just "sharing" it.
Read the pinned post for more information (applies to GPLv2 like GPLv3).

nofx161 said:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"
Click to expand...
Click to collapse
Thanks for the information, I lost connection with terminal after booting into TWRP, and didn't know what to do next as TWRP was o MB .
And terminal showed "FInished" with no error in your second command, but twrp was still not installed after holding down power + volumn down. :/
Is there anything i did wrong? Please reply Mr.Sakura

How to check if anti rollback is enabled?

Fastboot getvar anti

It just says anti: and no number. What does this means?

Mine shows the same so I think there is no anti rollback on our 2 devices.

mine also says "anti"..no number

Please be careful while flashing recovery that are found "somewhere".

Well, after flashing latest miuipro still anti with no count

Please delete this thread! False information!

any solution it is show 0mb internal

Do a factory reset in twrp or flash disable encryption.zip

forum.xda-developers.com/redmi-6-pro/development/recovery-twrp-v3-2-x-redmi-6-prosakura-t3851959
Check my post in above link

Doubt
coolek33 said:
If you factory reset through twrp and reboot recovery it should be OK. But keep in mind to do a backup of your stuff first.
Click to expand...
Click to collapse
How will i access the internal storage later if i format it totally ???

You will access it but it will be empty. So U can use sd card/usb otg for flashing

Realme x50 Pro Root ?

Hello there ! I'd like to root my Realme x50 Pro, is there any way to do it please ? :3
Thanks in advance for your help !

To root you need to unlock your bootloader, activate usb debugging and oem unlock. On your computer you need adb intalled. After do these step:
1. Extract the ozip of your phone firmware to have the boot.img and the vbmeta.img.
2. Copy the boot.img on your phone and patch it with magisk manager.
3. Copy the patched boot.img (rename it boot.img) and the vbmeta.img on your adb directorie.
4. Boot your phone to fastboot and launch adb on your computer.
5. enter these command:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Tada you now root.

Is fingerprint working with this method?

sco-mito said:
Is fingerprint working with this method?
Click to expand...
Click to collapse
+1

Yes

If I do that and I fail/want to remove it, is the factory reset enough ? I don't want to f**k up my phone x)

You have to flash the stock boot.img before.

deleted

crusader974 said:
Yes
Click to expand...
Click to collapse
fingerprint don't works for me
have you do somthing if for you it works?

Naokimaru said:
If I do that and I fail/want to remove it, is the factory reset enough ? I don't want to f**k up my phone x)
Click to expand...
Click to collapse
just flash vbmeta and after stock boot and don't need to reset factory

crusader974 said:
To root you need to unlock your bootloader, activate usb debugging and oem unlock. On your computer you need adb intalled. After do these step:
1. Extract the ozip of your phone firmware to have the boot.img and the vbmeta.img.
2. Copy the boot.img on your phone and patch it with magisk manager.
3. Copy the patched boot.img (rename it boot.img) and the vbmeta.img on your adb directorie.
4. Boot your phone to fastboot and launch adb on your computer.
5. enter these command:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Tada you now root.
Click to expand...
Click to collapse
hi, when i do an firmware update, for exemple the last 024. i unroot my phone, i install the update, i do your process, i reboot and always reboot on recovery. my phone can't decrypt. i reinstall the update by usb my boot reboot well. impossible to re-root my phone except if i make a full wipe-data. do you now how i can root?

crusader974 said:
To root you need to unlock your bootloader, activate usb debugging and oem unlock. On your computer you need adb intalled. After do these step:
1. Extract the ozip of your phone firmware to have the boot.img and the vbmeta.img.
2. Copy the boot.img on your phone and patch it with magisk manager.
3. Copy the patched boot.img (rename it boot.img) and the vbmeta.img on your adb directorie.
4. Boot your phone to fastboot and launch adb on your computer.
5. enter these command:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Tada you now root.
Click to expand...
Click to collapse
how to extract the ozip file
please show me the way
thanks a lot.

zhengye75 said:
how to extract the ozip file
please show me the way
thanks a lot.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/...rom-firmware-from-twrp-orangefox-etc.4065277/
It works for me.

corneo said:
Try this: https://forum.xda-developers.com/t/...rom-firmware-from-twrp-orangefox-etc.4065277/
It works for me.
Click to expand...
Click to collapse
thanks a lot

It's a bit easier to use these files. But be aware to use the right files. I extracted and patched the files from EU rom. Works on RMX2075 too. Please use the instructions above
rmx2076eu_a38 (A10 11/20 Patch)
magisk_patched_rmx2076eu_a38.img
drive.google.com
vbmeta_rmx2076eu_a38.img
drive.google.com
boot_rmx2076eu_a38.img
drive.google.com
rmx2076eu_a40 (A10 12/20 Patch)
vbmeta_rmx2076eu_a40.img
drive.google.com
magisk_patched_rmx2076eu_a40.img
drive.google.com
boot_rmx2076eu_a40.img
drive.google.com

Edit: same method
I update this post because there's another way of extracting an ozip that worked for me : just followed this tutorial : https://www.droidwin.com/extract-ozip-realme-stock-firmware/

corneo said:
It's a bit easier to use these files. But be aware to use the right files. I extracted and patched the files from EU rom. Works on RMX2075 too. Please use the instructions above
rmx2076eu_a38 (A10 11/20 Patch)
magisk_patched_rmx2076eu_a38.img
drive.google.com
vbmeta_rmx2076eu_a38.img
drive.google.com
boot_rmx2076eu_a38.img
drive.google.com
rmx2076eu_a40 (A10 12/20 Patch)
vbmeta_rmx2076eu_a40.img
drive.google.com
magisk_patched_rmx2076eu_a40.img
drive.google.com
boot_rmx2076eu_a40.img
drive.google.com
Click to expand...
Click to collapse
Where did you get these latest image files ? The latest version here is the september version. Thanks for sharing !
Edit: seems that https://www.realme.com/fr/support/software-update is more updated than "/eu/" ! Still, not the latest version here.

System update shows me the update. I downloaded it, converted it to zip, patched boot image and shared it. The website is not up to date.

With Android 11 it doesn't work. Extract the files from the OTA update, performing the steps that previously worked and the smartphone does not start, always goes to the bootloader.
{
"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"
}

Download RMX2075_11_C.18: https://nfs6ou.s.cld.pt
If anyone can root with this new version, share it.

[GUIDE] [HOWTO] Ulefone Note 9P unlock & root

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Ulefone Note 9P​
There are a number of "easy" tutorials on how to root the rather new Ulefone Note 9P, but none of them works as inteded, as of today.
After I've found (by my own research) how to unlock the phone, I'm sharing the easy procedure here in hope someone can go a step further and actually root it.
Ulefone Note 9P unlock procedure
- become a developer by tapping 7 times the build number in Phone settings;
- from the Developer Menu, enable OEM unlock and USB Debug
- Install Android platform_tools on your PC (I'm personally on Linux/Ubuntu, so for me it's just a matter of unpacking the archive and fixing some missing libraries)
- Connect the phone to the PC via an USB DATA cable
- Give consensus for USB debug, and allow the PC to access
- "./adb devices" should list the connected phone as "device" (it it's "unauthorized", go to Developer Menu and delete past authorizations for USB Debug)
- "./adb reboot fastboot"
- "./fastboot devices" (check the phone is still there)
- "./fastboot flashing unlock_critical" (OEM unlock and USER DATA WIPEOUT!)
Now my Ulefone Note 9P is actually unlocked (check: from the Developer Menu, you can't re-enable OEM Lock, since it is grayed and reports the bootloader is unlocked already).
Ulefone Note 9P root procedure (help is needed here!)
- Download MagiskManager-v7.5.1.apk
- "./adb install MagiskManager-v7.5.1.apk"
- MagiskManager icon is now on the phone screen
- Download Ulefone Note 9P stock Android 10 image (GQ3092SH1_HC_M629_Ulefone_EEA_20200701_V12.tar.gz)
- Unpack the archive and extract "boot.img"
- Copy the boot.img to the phone via standard file transfer, putting e.g. in the "Download" folder on the phone
- Open MagiskManager on the phone, it says Magisk is not installed
- Click Install, then Install (again), then "Select and update a file"
- Browse and search the boot.img you just downloaded to the phone
- Magisk starts to patch it, then saves the result as "magisk_patched.img" in the same folder
- Transfer the "magisk_patched.img" from the phone back to the PC via standard file transfer
- Download "Smart Phone Flash Tool" (SP_Flash_Tool-5.1916_Linux.zip)
- Open it: a "scatter file" is required for any operation, and it can be found in the same directory where you unpacked the stock ROM (filename: "MT6765_Android_scatter.txt")
- In the Download tab, unselect all partitions, then only select the "boot" partition;
- click on the left, where the filename is, and browse where "magisk_patched.img" is, the select it)
- Now click "Download" in the SP Flash Tool: it waits for the kernel to find the "Product: MT65xx Preloader // Manufacturer: MediaTek"
- reboot the phone while still leaving it connected to the PC
- during reboot, the SP Flash Tool activates and writes the boot partition to the phone.
- Then, currently, the Ulefone Note 9P enters a reboot loop, as soon as you detach it from the PC (it won't even boot until then).
Ulefone Note 9P unbrick procedure
- So the Ulefone Note 9P is in a bootloop now!
- Luckily, even that short boot time is enough to access the "MT65xx Preloader" device in the phone.
- So start the SP Falsh Tool, load scatterfile as before, unselect all partitions then select only boot;
- In the "boot" row, all left, there's the filename: browse and select the original "boot.img" from the stock ROM
- Click Download, and wait for the Preloader to apper...
- Ulefone Note 9P is now able to boot normally, it's still unlocked, but also unrooted...
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device

[email protected] said:
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Ulefone Note 9P​
.......
Please keep discussion focused, on questions pertaining to this Device
Click to expand...
Click to collapse
With newer devices you also need to disable verification, in order to boot other unsigned images. Not just bootloader unlock.
This device has three verification partitions that need disabled.
vbmeta
vbmeta_system
vbmeta_vendor
All are found in same stock firmware archive you have mentioned in guide.
flash them in fastboot like this
Code:
fastboot --disable-verity --disable-verification flash vbmeta /some-directorty-on-your-pc/vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system /some-directorty-on-your-pc/vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor /some-directorty-on-your-pc/vbmeta_vendor.img
now you can either flash the magisk-modified-boot.img to boot in fastboot or back to spflash tool.
it will not bootloop. but sorry, root was still not working.
Can confirm flashing GSI roms works also. even the new android 11 GSI.
if interested I have been using tags on my posts, when for devices that do not have there own forum section.
https://forum.xda-developers.com/tags.php?tag=ulefone+note+9p

Installing gsi arm 64 on redmi 9a

Everything is at your own risk!!!
GSI select only with architecture A64-AB (also may be called arm32-binder64-ab) starting from Android 10
This method really works, no one expected that redmi 9A can run gsi arm-64ab now there is such a possibility
You do it on your own, I don't belong to this
Installing the driver for fastboot
USB DRIVER
on your phone go into fastboot mode connect usb phone to computer
open cmd, go to the Redmi + 9A + GSI + Installer folder, there we will have the path, copy it and go to cmd, cd the path of the folder.
prescribe
fastboot reboot fastboot - our phone has rebooted
We go to the folder Redmi + 9A + GSI + Installer and copy the system image there necessarily A64-AB or arm32-binder64-ab
this image.img needs to be renamed > system.img then we press flash-twrp.bat and we have the installation
We extract from the archive https://drive.google.c...8AJoGd&export=download folder to the root of drive C, connect the phone in fastboot mode to the computer and open the command line on the computer, into which we insert the lines in turn:
cd C:\9A\fastboot
Fastboot flash dtbo dtbo.img
Fastboot flash boot boot.img
fastboot flash super super.img
Fastboot flash vbmeta_vendor vbmeta_vendor.img
Fastboot flash vbmeta_system vbmeta_system.img
Fastboot flash recovery recovery.img
Fastboot flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Fastboot erase userdata
fastboot reboot
fastboot
Click to expand...
Click to collapse
When the device successfully reboots into the system, we transfer it back to fastboot mode and again open the command line on the computer, into which we insert the lines in turn:
fastboot reboot fastboot
Click to expand...
Click to collapse
GSI auto installer for Redmi 9A
1) Download the GSI image and rename it to system.img (GSI can also be in *.xz and *.zip archives, you need to unpack) https://sourceforge.net/p/amber-gsi/activity/?page=0&limit=100#60984432478b418cb8a7ea05
2) Unzip the archive Attached fileRedmi+9A+GSI+Installer.zip ( 3.84 MB )
3) Put system.img in it
4) Run flash-twrp.bat
5) The smartphone will reboot and you will get a working unofficial firmware
First, unlock the bootloader!
https://sourceforge.net/p/amber-gsi/activity/?page=0&limit=100#60984432478b418cb8a7ea05
{
"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"
}

It's applicable for redmi 9AT too?

I found that Treble Info apk , gives good info about the device, it tells you if it works for your device, and if it works, it recommends which GSI image to download/flash
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=&gl=US
another mirror:
https://www.apkmirror.com/apk/hacki...lease/treble-info-5-0-6-android-apk-download/
I also made a guide on how to flash it. No fishy .bat files.
Xiaomi Redmi 9A 9i 9AT 10A
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com

Download link doesn't properly work.

NorthenPL said:
Download link doesn't properly work.
Click to expand...
Click to collapse
It's fake because coincidentally the download link is the only one that is incorrectly inserted

[Solved][Need help] Why my phone just stuck in the bootscreen and couldn't boot into android

Phone: Realme V11 5G (RMX3121)
I wanted to flash a GSI image to my phone yesterday, but after flashing the system.img, I couldn't boot it. So I decided to go back to realme UI. I found an `ofp` image for my device and decrypted it using `mct ofp extractor` and merged `super.img` using `simg2img` tool. I use `MTK Flash Tool` to flash the image. But it still didn't work. When I reboot, it stays on the white "realme" screen for a long time and then goes to another screen. At that time, `adb` can relocate my phone. But after about 10 minutes, it will reboot.
{
"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"
}

With regards to your ADB issue:
ADB client on PC finds its host counterpart ADBD on phone, but can't talk with it because of missing RSA key: the device is shown as unauthorized,
Possible fix
1. Revoke USB debugging authorization in Developer options.
2. Restart ADB Server:
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
4. Now Check the device
It is now authorized!

jwoegerbauer said:
With regards to your ADB issue:
ADB client on PC finds its host counterpart ADBD on phone, but can't talk with it because of missing RSA key: the device is shown as unauthorized,
Possible fix
1. Revoke USB debugging authorization in Developer options.
2. Restart ADB Server:
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
4. Now Check the device
It is now authorized!
Click to expand...
Click to collapse
I can't boot into the system and authorize the device XD

Hello, thank you so much for your development work

alfaputra said:
Hello, thank you so much for your development work
Click to expand...
Click to collapse
So strange, it makes me wonder if you're a robot. I'm just facing a problem and need to solve it. I am not a developer.

you forgot to disable dm-verity. assuming your phone has vbmeta partition and supports fastboot mode, flash the vbmeta.img with following flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
btw by "merged super.img using simg2img tool" you probably mean "extracted" - simg2img is a decompression conversion from OTA to raw partition image

WinghongZau said:
I can't boot into the system and authorize the device XD
Click to expand...
Click to collapse
But anyone can boot a phone into recovery mode and then issue the mentioned ADB commands there

aIecxs said:
you forgot to disable dm-verity. assuming your phone has vbmeta partition and supports fastboot mode, flash the vbmeta.img with following flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
btw by "merged super.img using simg2img tool" you probably mean "extracted" - simg2img is a decompression conversion from OTA to raw partition image
Click to expand...
Click to collapse
yeah now i have disabled it. but I actually use `simg2img` to merge 3 `super.x.img.xxxxx` file into `super.img`. now I flashed a Android 11 GSI for it and stuck in `android` screen.

WinghongZau said:
yeah now i have disabled it. but I actually use `simg2img` to merge 3 `super.x.img.xxxxx` file into `super.img`. now I flashed a Android 11 GSI for it and stuck in `android` screen.
Click to expand...
Click to collapse

can you explain how you merge 3 super.x.img.xxxxx with simg2img?

aIecxs said:
can you explain how you merge 3 super.x.img.xxxxx with simg2img?
Click to expand...
Click to collapse
Code:
simg2img super.0.img.xxx super.1.img.xxx super.2.img.xxx super.img
maybe it is the extract, i'm not sure.

didn't know simg2img accepts more than two arguments (haven't used for while)
maybe concatenate parts yourself (windows/linux?)
or try this ROM maybe
https://forum.xda-developers.com/t/discontinued-gsi-11-lineageos-18-x-gsi-all-archs.4205461

aIecxs said:
didn't know simg2img accepts more than two arguments (haven't used for while)
maybe concatenate parts yourself (windows/linux?)
or try this ROM maybe
https://forum.xda-developers.com/t/discontinued-gsi-11-lineageos-18-x-gsi-all-archs.4205461
Click to expand...
Click to collapse
Maybe we're not talking about the same thing XD.
> simg2img
Usage: simg2img <sparse_image_files> <raw_image_file>

yes we do, but the usage has changed
nevertheless, you could try old usage (linux)
Code:
cat super.?.img.xxx > super.img.xxx
simg2img super.img.xxx super.img

aIecxs said:
yes we do, but the usage has changed
nevertheless, you could try old usage (linux)
Code:
cat super.?.img.xxx > super.img.xxx
simg2img super.img.xxx super.img
Click to expand...
Click to collapse
could you tell me why I flashed AOSP for my phone but it got stuck on the "android" logo and when I flashed Pixel Experience it got stuck on the google logo? I'm so irritable due to it.

it stuck on it's logo, what's the difference?
possible reasons
- avb/dm-verity not disabled
- broken encryption
- broken ROM
- interrupted flashing progress
- you did not factory reset
- you did not wait long enough

aIecxs said:
it stuck on it's logo, what's the difference?
possible reasons
- avb/dm-verity not disabled
- broken encryption
- broken ROM
- interrupted flashing progress
- you did not factory reset
- you did not wait long enough
Click to expand...
Click to collapse
thx. if I have some questions I will reply you tomorrow. maybe my english isn't good. never mind it.