Database Info

[Q4DEV] Desire HD - where is the hidden partition??

When you take a look at the original ROM file for the ACE device you will see this files below:
- hboot... bla, bla, bla (which is self spelling)
- boot.img (...no comment...)
- recovery.img (...no comment again...)
- system.img (...we all know what's inside)
...a few more files and...
- lib.img (...uhhh??? what's this???)
{
"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"
}
When you open the lib.img there you can find all the files which belongs to the /system/lib folder.
So far - everything seems to be O.k. BUT now my problem and question.
When I use the PD98IMG.zip to install my device and do a backup with the RECOVERY tool and create .tar files - the /system/lib folder within the backup is empty.
When I do a wipe of my device and erase EVERYTHING on it and I try to restore my backup file this fails. This was driving me nearly crazy until I have found that the /lib folder has his own partition.
First I need to restore the original PD98IMG.zip and after this I'm able to successfully restore my backup.
On the one hand this is a great thing because this will offer more space within the /system partition and this will give the DEV's more options for porting ROM's from and to other devices.
On the other hand - where the hell is the /lib folder or partition or whatever located on the DHD device???
Regards!

I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps

fshami said:
I think these files are from the Sense 3.0 leaked ROM for ace rite?
For some reason they've made a separate lib.img & if you want to know how exact & where it is extracted during the installation, unpack boot.img & check init.rc / init.spade.rc..
You'll see few lines in either of the files related to extraction of lib.img..
hope this helps
Click to expand...
Click to collapse
Yep m8, this is related to the leaked 3.06 ROM for the ACE.
I guess this might be interesting for some DEV's and this is also a thing which needs to be covered by the guy's who are developing the kernels and ramdisk for the ACE.
Also the 4EXT Recovery should be adjust for the ACE device.
From my point of view this is a good solution to get more space on the /system partition.
The next thing is /data/at folder within the original dzdata.img and the sub folders. This folders will be mounted automatically to the /system partition. Don't know how...
Let me give an example for WhatsApp.apk
The original dzdata.img contains this folder structure:
/data/app
/data/at/app
/data/at/lib
/data/at/plugin
If I store this file within /data/at/app I can use WhatsApp without creating an hard link to the /system/apps folder.
All this things might be interesting for the DEV's.

Just a quick (related) question. How do you unpack dzdata.img?

It might not be a hidden/new partition. Quite the contrary. Notice that with the 3.06, there's a new hboot shipped. I'm theorizing, that it changes the partition layout, chopping up /system into smaller partitions. Now, as we all probably use the eng hboot and a custom update-script for unsigned roms, this doesn't concern us.
Or at least that's my theory. I remember in the sapphire/magic days, the new radio would allot more flash space to /system to fit in SenseUI, while old radio would allot more space to /data.

(TOOL) (Root) ADB Partition Backup Restore Tool for Windows

ADB Partition Backup Restore Tool is a Partition Management app for all rooted Phones. with the help of this tool you can backup any partition from your device to your PC, also there is a flash option which you can use to write any partition..
Feature:
Read Partition directly to PC
Write Partition from PC
support almost all rooted phones
Requirement:
rooted phone, windows pc/laptop
Why:
read & flash critical partition like modem or EFS without custom recovery​
Download;
file attached below
Disclaimer:
flashing wrong file to wrong block cause immediate bootloop
How to use:​
Install adb driver
enable debugging
connect device
Run tool, click Start Partition Manager, once partition table readed, Select Read button to Read a partition and flash button to write a partition..
Here is My another similar tool for Xiaomi which use Sideload & work without root (only for xiaomi)
Your browser is not able to display this video.

Can you add window size scaling. Currently it is set to a fixed 1709x822.
{
"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"
}

ze7zez said:
Can you add window size scaling. Currently it is set to a fixed 1709x822.
View attachment 5747165
Click to expand...
Click to collapse
added in new attachment

After connecting to a PC and making a copy of any partition, an error is displayed:
"Reading" boot_b ".img: Pulling" boot_b ".img: ADB: Error: Failed to Stat Remote Object '/Sdcard/boot_B.img': No Such File or Directory"
There is no "boot_b.img" file on the card on the smartphone card (OnePlus8pro), no pop-up has erected in Magiska to give any root permissions.
What am I doing wrong?
regards

qriozum said:
After connecting to a PC and making a copy of any partition, an error is displayed:
"Reading" boot_b ".img: Pulling" boot_b ".img: ADB: Error: Failed to Stat Remote Object '/Sdcard/boot_B.img': No Such File or Directory"
There is no "boot_b.img" file on the card on the smartphone card (OnePlus8pro), no pop-up has erected in Magiska to give any root permissions.
What am I doing wrong?
regards
View attachment 5833457
Click to expand...
Click to collapse
inside magisk superuser allow SharedUID

Question Device bricked, possibly damaged super partition?

When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
{
"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"
}
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
Fastboot Enhance shows I have a super partition 11.5GB in size:
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?

Hello. I have an idea as follows. if you need to do that, look for a rom specifically for flashing super.img, not a rom that contains a lot of images like this

bubugugu said:
When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
View attachment 5769945
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
View attachment 5769943
Fastboot Enhance shows I have a super partition 11.5GB in size:
View attachment 5769965
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
View attachment 5769959
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?
Click to expand...
Click to collapse
Did you every solve this? I'm having the same problem.

FX file Explorer - How to make a file write accessible?

I'm Rooted and using Androids FX file Explorer, to try to add a ring tone to the ringtones system folder.
/system/media/audio/ringtones
Would someone explain how to make the file write accessable or direct me to a link to how to do this?
{
"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"
}
I searched but all I could find were links how to do it through a command promt, which is not what I'm looking for.
Android 13
galaxy A22 plus
Rooted with Majiks systemless-ly activated

20GT said:
I'm using Androids FX file Explorer, to try to add a ring tone to the ringtones system folder.
/system/media/audio/ringtones
Would someone explain how to make the file write accessable or direct me to a link to how to do this?
View attachment 5836745
I searched but all I could find were links how to do it through a command promt, which is not what I'm looking for.
Android 13
galaxy A22 plus
Click to expand...
Click to collapse
after android 8 (in preparation for project Treble), system partition is mounted during boot as read-only by default (as you can find out through the partition's mount flags). so there's 2 ways to achieve what you want:
you remove the shared_block feature from Super.img and mount system as R/W. There are tools to do this, but they're not tested on Samsung devices. Like this Tool.
you root your phone with Magisk and make a Magisk module to add your files systemless-ly. Here is the Developer Guide.
Of course, You would need an unlocked Bootloader. Here is the guide for Unlocking and Rooting. I also advise you to flash TWRP before experimenting with the Module you create. Good luck.

Slim K said:
after android 8 (in preparation for project Treble), system partition is mounted during boot as read-only by default (as you can find out through the partition's mount flags). so there's 2 ways to achieve what you want:
you remove the shared_block feature from Super.img and mount system as R/W. There are tools to do this, but they're not tested on Samsung devices. Like this Tool.
you root your phone with Magisk and make a Magisk module to add your files systemless-ly. Here is the Developer Guide.
Of course, You would need an unlocked Bootloader. Here is the guide for Unlocking and Rooting. I also advise you to flash TWRP before experimenting with the Module you create. Good luck.
Click to expand...
Click to collapse
Sorry I forgot to mention that I'm already Rooted with systemless-ly already activated.

Just tested Fx file explorer on my privious phone and it works correctly after mounting the folder.
I passed the root check. is there a diffent option/checkmark to allow Fx access to root or give Fx pemisions in majiks on android 13?

FIX NT Code - Enabled LTE & Mobile Data

It is known that after cross-flashing and then removing the NT code, we will lose the LTE network and mobile data. In order to use our network and mobile data again we need to flash the patched modem partition, see more about that in this thread Modem Patched, Fixed LTE & Mobile data.
This time I will show you how to fix the NT code without using a patched modem.
So let's go...
It is recommended to make a full partition backup before any cross-flashing. Performing this tutorial will require a backup of our original FTM partition before cross-flashing.
When we finish cross-flashing e.g. EU firmware when boot to android for the first time of course we will have NT code error, flash our original FTM to EU firmware then apply the instructions depending on whether you have root or not.
Spoiler: Non-root users
We will download the HxD hex editor with which we will edit the partition.
When we flash the original FTM it is not necessary to exit the partition manager from Qfill because we will make a backup copy of the OP_a partition.
My original FTM is from an AT&T device, yours will probably be the same or a different device.
In the downloaded hex editor, we will open our original FTM partition and OP_a partition.
We will open FTM in HxD then we will find NT code at address 14000 in my case it is ATT NT code where we can see mcc/mnc[xxxxxx],subset[xx] in case 310410,FF, after finding NT code we will leave FTM open in HxD
.
{
"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"
}
Open OP_a in HxD and find the string FFFFFF,11 which means EU NT code it's our EU croosflahed firmware.
Inside OP_a partition "FFFFFF,11" we will overwrite with our correct NT code in my ATT case "310410,FF".
Now that we have entered the correct mcc/mnc[xxxxxx],subset[xx] we can save the changes then flash back the modified OP_a partition.
Extra feature;
If we want to display a menu for selecting 5G under Network Mode, do this.
Find inside OP_a "networksettings.OPEN_EU" then rename the .apk extension to .bak, save the changes.
Spoiler: Rooted users
Magisk module soon..
Ok for this initial part we are done now you have NT code removed and network and mobile data fixed.
Soon there will be a magisk module for rooted devices.
Note: If you use this method of fixing the NT code then it is not necessary to use a patched modem, otherwise you will be using it.
Note: For JP variants, I'm not sure about this method because the devices don't have an OP partition.

Nice work

I converted from Verizon to EU fixed as instructed but got NT Code error, do you have a detailed guide for Verizon to switch to E

go to path as picture and see which nt code inside cust_path_mapping,, if EU code it means that you did not change nt code . Nt code inside file and ftm must be some.
Or easy way just edit FTM and flash patched modem.