Database Info

[QUESTION] Huawei Y6 ii compact LYO-L21

I just successfully rooted and customized few features on my Y6 ii compact , and after changing my boot animation i noticed i can't rly change splash logo when i change my logo.img in /cust folder nothing happends .
Did any of you guys manage to change it and how?
also if any1 needs help rooting or installing TWRP i would be glad to help.... tnx in advance .

heroinmage said:
I just successfully rooted and customized few features on my Y6 ii compact , and after changing my boot animation i noticed i can't rly change splash logo when i change my logo.img in /cust folder nothing happends .
Did any of you guys manage to change it and how?
Click to expand...
Click to collapse
In Mediatek powered phones, splash logo resides on a separate partition called logo. You have to flash your logo.img/logo.bin to that partition. The logo.img you see in /cust folder is likely just a backup.
also if any1 needs help rooting or installing TWRP i would be glad to help.... tnx in advance .
Click to expand...
Click to collapse
Share what you've learned. That's why XDA is here. If you accomplished something that hasn't yet been accomplished, the community welcomes you to share your discovery!

Nonta72 said:
In Mediatek powered phones, splash logo resides on a separate partition called logo. You have to flash your logo.img/logo.bin to that partition. The logo.img you see in /cust folder is likely just a backup.
Well i can't seem to find that partition in TWRPfile explorer or from Rom toolbox root browser, are those partition accessible only by shell? anyways i will upload my files and update my post.
Click to expand...
Click to collapse

heroinmage said:
Well i can't seem to find that partition in TWRPfile explorer or from Rom toolbox root browser, are those partition accessible only by shell?
Click to expand...
Click to collapse
This partition isn't accessible or usable by the user once the system has been initiated.

Nonta72 said:
This partition isn't accessible or usable by the user once the system has been initiated.
Click to expand...
Click to collapse
alright i saw some guide on some wordpress website to go to TWRP make boot partition backup , then to move that bacup to some folder i can access from pc ,alter logo , and put it back to original place + use that backup . Now im stuck before splash screen logo because phone can't load that logo and he is just rebooting after 10 sec or so . Only thing i managed to access is fastboot. Problem is i can't find any rom for my devices with .img format files so i can't rly flash them. Do you maybe have some idea ?

heroinmage said:
alright i saw some guide on some wordpress website to go to TWRP make boot partition backup , then to move that bacup to some folder i can access from pc ,alter logo , and put it back to original place + use that backup . Now im stuck before splash screen logo because phone can't load that logo and he is just rebooting after 10 sec or so . Only thing i managed to access is fastboot. Problem is i can't find any rom for my devices with .img format files so i can't rly flash them. Do you maybe have some idea ?
Click to expand...
Click to collapse
You just need to do more searches.
Huawei Stock roms come in update.app format. It's a compressed file that contains all the img files (boot.img, recovery.img, system.img, logo.img, cache.img etc). There is already a thread to unpack such file and extract the img files. The tool is available here.
Now, once you get your logo.img, you can use dd in adb or terminal to flash it. This is not intended for normal users. I wouldn't advice it.
And no, you cannot use another phone's logo.img/logo.bin in your phone even if it's from another huawei.

Could not flash MIUI 11.0.6 on Redmi Note 7 Pro using Mi Flash tool

Brothers, I am getting the below error when I tried to flash MIUI 11.0.6 on my Redmi note 7 pro. Currently am on havoc os and I want to go back to stock Rom.
"could not found file flash_all.bat"
Please help me to fix this issue..

ziyadh.aj said:
Brothers, I am getting the below error when I tried to flash MIUI 11.0.6 on my Redmi note 7 pro. Currently am on havoc os and I want to go back to stock Rom.
"could not found file flash_all.bat"
Please help me to fix this issue..
Click to expand...
Click to collapse
did you selected the target path correctly. it seems the problem is that you haven't selected the right path to the ROM or the ROM file hasn't been extracted properly(maybe missing files).
first check if you have selected the right path
if it is correct then check if ROM has been extracted properly.
meanwhile from which version are you trying to flash?

Try all flash files from desktop path and mainly create a folder like this without a space eg: (Redminote7pro)

kiruba Developer said:
Try all flash files from desktop path and mainly create a folder like this without a space eg: (Redminote7pro)
Click to expand...
Click to collapse
yes , mi flash tool only support source file on desktop

mathan7 said:
yes , mi flash tool only support source file on desktop
Click to expand...
Click to collapse
Sorry I want to correct you here, you can flash from anywhere in drive but the address should not have spaces.

Persist image corrupt ?

Hi, i own an Oneplus 8 India Version.
As soon as i purchased the first thing I did was to take the persist.img backup as that seemed to be an important thing to do from my reading through the articles.
After a few months now, I seem to be in need of using this image and realized the image file is not accessible. from the articles and videos I read/seen, everyone is able to EXTRACT the image file using the 7zip or similar tools. However, i am unable to extract using any of the tools.
I took the latest persist.img from the already troubled device and that too is not working. 7zip says "Can not open the file ...."
command i used was this :
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
similarly, i manually copied the file using root file manager aad that too is giving the error

Please help

Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.

crazynapkinman said:
Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.
Click to expand...
Click to collapse
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.

firoz3321 said:
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.
Click to expand...
Click to collapse
Does anyone know if he can flash someone else's backed up persist.img?

crazynapkinman said:
Does anyone know if he can flash someone else's backed up persist.img?
Click to expand...
Click to collapse
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.

firoz3321 said:
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.
Click to expand...
Click to collapse
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img

crazynapkinman said:
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img
Click to expand...
Click to collapse
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.

firoz3321 said:
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.
Click to expand...
Click to collapse
Need to downgrade to 10.
I pulled my persist image off of 10.
---------- Post added at 07:20 PM ---------- Previous post was at 07:08 PM ----------
From what I've read there's not reason to unzip the persist.img
If you backed it up with a WORKING persist present, then you simply need to boot to fastboot and flash your persist.img
It will replace the corrupted partition and you're good to go. No one on any forum I read said they actually extracted anything from the persist.img file itself.
They all had to extract (see backup) the WORKING persist.img and flash that with fastboot command.
You can extract working persist.img with the following command in adb:
dd if=/dev/block/by-name/persist of=/sdcard/persist.img
This will save it to your sdcard. Transfer that backup to your adb folder on pc. Reboot into fastboot and use the following command to flash it:
fastboot flash persist persist.img

I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.

firoz3321 said:
I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.
Click to expand...
Click to collapse
Hopefully you're using the good backup you made and not something you downloaded...
GL!

crazynapkinman said:
Hopefully you're using the good backup you made and not something you downloaded...
GL!
Click to expand...
Click to collapse
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.

firoz3321 said:
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.
Click to expand...
Click to collapse
Received the mobile back and the FP reader is working fine. :angel:

cust.img file for redmi note 5 / 5 pro

how need original cust.img file from miui 12 in found attach file size 172 miga

What the OP meant:
Who ever needs the original Cust file from Miui 12 , here you go it is attached below.

Hi, may I know what this Cust.img file is using for?
Currently I'm on MIUI 12.0.2.0 flash from recovery with my RN5 AI(China Whyred).
Thanks.

chunnone said:
Hi, may I know what this Cust.img file is using for?
Currently I'm on MIUI 12.0.2.0 flash from recovery with my RN5 AI(China Whyred).
Thanks.
Click to expand...
Click to collapse
My answer is mostly based on assumption. Verify the info before doing something serious with it.
cust.img file found in rom file is mainly used for storing bloatware like tictok,likely or Facebook. These app are pre-installed by Company. The cust.img is a disk image (you can mount it!) storing these apps. I may be wrong but I found that not flashing cust.img remove these apps. But I won't tell you to take that risk. Hope I could help you.

[QUESTION] Android 11 boot loop after restoring TWRP backup

Nandoid B/U with TWRP. Seems to backup just fine, but (immediately) restore on the same device causes boot loops.
It looks like the backup filed are something like win000, win001, etc that are actually tar files.
I'm wondering if I got into terminal mode on TWRP, could I just extract the tar files to restore the partition?? I've always used tar to b/u and restore /data/media.
FWIW, the device is a Pixel 3a running android 11 and the version 11 compatible TWRP flash file.
Help if you can...... Thanks

Hi @Boowho 1234,
seems you have accidentially posted in the wrong forum. I have moved your question to the Google Pixel 3a Questions & Answers forum.
regards
alecxs
moderator

alecxs said:
Hi @Boowho 1234,
seems you have accidentially posted in the wrong forum. I have moved your question to the Google Pixel 3a Questions & Answers forum.
regards
alecxs
moderator
Click to expand...
Click to collapse
sorry......

You're welcome! Regarding your question. May you clarify why you want to extract tar files manually - did the restoring via TWRP menu not extract the files successfully? Usually TWRP would throw an Error code in that case, and you can always have a look into /tmp/recovery.log

alecxs said:
You're welcome! Regarding your question. May you clarify why you want to extract tar files manually - did the restoring via TWRP menu not extract the files successfully? Usually TWRP would throw an Error code in that case, and you can always have a look into /tmp/recovery.log
Click to expand...
Click to collapse
Restoring using the TWRP restore option restored the files perfectly. But, upon rebooting back to SYSTEM just boot loops. No error code thrown, but I've not looked at recovery.log

It's probably because of one or more outdated files restored. try to delete this. you should also try to restore on formatted userdata partition (beware of / data/media = /sdcard is not included in backup)
/data/unencrypted
/data/misc/keystore
/data/misc/gatekeeper
/data/misc/vold
/data/system/locksettings.db*
You should ask TWRP maintainer to fix that issue.

I'm now using a Windows .bat file to backup ALL partitions on the device. It works great except throws errors on these two partitions : mmcblk0 and mmcblk0rpmb
I've read that these two partitions are not REALLY partitions at all, but are some sort of "special" files within the /dev/block directory.
The question is do I have a complete Nandroid back up without these two included?? Anyone??
Thanks