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.
Related
Can anybody share a 1G data.img? I am not familiar with linux but I want more space on my polaris.
regards
EDIT: the solution here http://forum.xda-developers.com/showthread.php?t=741383
Code:
This can be done with any data.img... even existing one one.
Boot phone in windows mobile. attach to linux box(linux computer or live cd) in disk mode(when u attach hd2 to computer it will ask mode,select disk mode).
go to terminal.
go to the /media
then go to the directory which represents your hd2 phone, then to [B]andboot [/B]directory.
then enter following commands
e2fsck -f data.img
(if it asks to fix say y)
resize2fs -p data.img 512000
(this is for half gb, change it as per requirement)
e2fsck -f data.img
Then reboot the phone.
You may see green screen. if so, simply reboot again.
works like a charm.
no need to download huge file. can be done with a used data.img at any time and any number of times.
Last edited by bhaveshdj; 1st August 2010 at 03:43 PM. Reason: to give more info
You need to install ubuntu first / You do not need any partitions
Install normally first, system to NAND and data to data.img
Remove the card from the phone
Move the card to the phone and reboot
You are done.
Storage shows 2,36 G for me now (2,13 G free after installing 60 programs), and I still have 11,55G for music, maps and so on !
kk last kernel + incubus26jc's RLS14
{
"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"
}
Note: do not ask me to share it because it constains all personal configuration and I do not know yet how to clean it.
Now the question is: when I want to update to next release, what do I have to do? install data to data.img and resize it again? or I can overwrite with my old&big data.img file?
you can create it using boot script generator (select the size)
ok I thought your tool required the nbh posted in your thread.
I have created the sh file but before I flash may be you can help me:
1. What I want to do is to install all apps to my 16g sd. Typically in windows mobile I keep 6g in music, 4g in onroad and offroad navigators and maps 1g on installed apps and 2g on non installed apps.
2. After quite a lot of reading, I do not understand which options do I have with incubus26jc's froyo 2.2. for pola100: apps2sd? dataimg? ext2 partition? linux swap on a third partition?
3. Your tool can help creating partitions? does it exist an easy way to create partitions from windows with no linux and no money?
4. Which set-up would you recommend to me data.img or ext2? I like it fast boot and fast performance so I am trying nand install.
5. I can not flash from the sdcard so I flash the nbh from windows and leave the rar file in andboot. If I leave your sh in andboot will it work?
6. If I do not use the script generated by your app and resize data.img manually will I have to do it everytime I try a new ROM?
thanks so much for your help so far.
new nbh has all you need to make it works inside.
i'm writing a new tool to partition sd card but is in alpha version and i need dzo release my file...
Well it seems not easy to me:
I stick to Kakt_Kaffe kernel + incubus rls 14 since i have wifi and camera with no probs. I have installed ubuntu and formated the sd card with fat32,ext and lynux-swap but I can not install data to the partition. sigh
I have also tried with the same kernel your script and I does not boot.
I will try to resize my data.img in ubunto (reinstalling now because I rebooted ubuntu without noticing it was downloading a system uptade)
If you need beta testers for the sd partitioner I can do some testing.
Solution in first post.
Now the question is: when I want to update to next release, what do I have to do? install data to data.img and resize it again? or I can overwrite with my old&big data.img file?
Hey together.
(at first: I do not want use a finished custom rom. I am happy as my Rome is now running)
I Would like to deodex my JB Stock Rom to coustomize my self with Mods and other but for almost everything i used a deodexed Rom. I tried xUltima and the Android Kitchen, v0.223 by dsixda and both doesn't work.
On the Android Kitchen, v0.223 by dsixda i can't find my TWRP Backup and i don't know how i convert it or somthig else.
On xUltima i become instantly an Error. When i delete the odex file which caused the error i become instantly a another error.
Here is a Picture from xUltima:
{
"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 have no idee how i fix this.
no one an idea?
Make a imitation ROM:
Create a dump.
Download Rhythm Manager's version of file manager.
Now go to / (self explanatory) and copy system.
It'll take a while, but copy it to sdcard.
Now copy the file onto computer. Find a ROM and copy the META_INF.
Make a empty boot.img.
Put the boot.img, system, and meta_inf into a zip folder. THis would be your ROM.
You can take it from there.
mr_verystock said:
Make a imitation ROM:
Create a dump.
Download Rhythm Manager's version of file manager.
Now go to / (self explanatory) and copy system.
It'll take a while, but copy it to sdcard.
Now copy the file onto computer. Find a ROM and copy the META_INF.
Make a empty boot.img.
Put the boot.img, system, and meta_inf into a zip folder. THis would be your ROM.
You can take it from there.
Click to expand...
Click to collapse
okay sounds quite simple but i have some questsions. it does not matter whitch META_INF i use? And how i make a empty boot.img? Can i put the Deodexed file back in the Data und Jar Folder or must i flash it?
Specimann said:
okay sounds quite simple but i have some questsions. 1) it does not matter whitch META_INF i use? 2) And how i make a empty boot.img? Can i put the Deodexed file back in the Data und Jar Folder or must i flash it?
Click to expand...
Click to collapse
1) Yes. Any ROM is okay. Just get it from an actual ROM.
2) Step 1: unhide extension by going explorer.exe --> organize --> Folder and search options --> view --> uncheck Hide extension ... --> click apply to folders--> Apply. Now simply make a .txt file on desktop and rename the extension as img, and the file name make it boot.
Hello,
This is the question and the answer on the same post. (I hope I'm posting on the right place)
As you can read from this post and next three pages since, I have problems with persist partition after being formated by accident with CWM
The problem with formating PERSIST partition is that you will kill your wifi. And will not turn on anymore, buttons will look grayed out, etc. There are many threads about, here on XDA.
And of course, you will be unable to re-flash the partition with rsd or fastboot. (Flashing back your original and full stock will not help)
I was pointed to the fix for this accident which is on this post on Atrix HD section. (credit to the guys who helped me)
And thanks to post above I was able to fix my phone´s wifi and bring back to life.
But, after decompress the IMG file of persist partition I saw the WCNSS_qcom_wlan_nv from stock XT925 ROM has only 28 KB. So small compared with Atrix file. On the post fix above you will find the same file but with 1.7 MB
I tested the fix using both. And any file will work. The one from Atrix thread or the one from your own persist partition or the ones here.
Brief instructions:
You have to copy the file WCNSS_qcom_wlan_nv to the persist partition on home root, aka /persist
(Don't worry if you see an empty folder)
{
"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"
}
Then. Apply the permissions as follows
Then. Restart. your phone will create the rest of the files and links there.
That's it .
Below you will find four files extracted of several Roms. Rename it to delete the words up to W.
However, all files has the same size and same md5. So. Code is the same for each.
Anyway, is up to you.
One interesting thing I watch with this problem is: the MAC Address did not change at all.
You can change between the files and MAC will remain.
Linuxser said:
Hello,
This is the question and the answer on the same post. (I hope I'm posting on the right place)
As you can read from this post and next three pages since, I have problems with persist partition after being formated by accident with CWM
The problem with formating PERSIST partition is that you will kill your wifi. And will not turn on anymore, buttons will look grayed out, etc. There are many threads about, here on XDA.
And of course, you will be unable to re-flash the partition with rsd or fastboot. (Flashing back your original and full stock will not help)
I was pointed to the fix for this accident which is on this post on Atrix HD section. (credit to the guys who helped me)
And thanks to post above I was able to fix my phone´s wifi and bring back to life.
But, after decompress the IMG file of persist partition I saw the WCNSS_qcom_wlan_nv from stock XT925 ROM has only 28 KB. So small compared with Atrix file. On the post fix above you will find the same file but with 1.7 MB
I tested the fix using both. And any file will work. The one from Atrix thread or the one from your own persist partition or the ones here.
Brief instructions:
You have to copy the file WCNSS_qcom_wlan_nv to the persist partition on home root, aka /persist
(Don't worry if you see an empty folder)
View attachment 2661839
Then. Apply the permissions as follows
View attachment 2661840
Then. Restart. your phone will create the rest of the files and links there.
That's it .
Below you will find four files extracted of several Roms. Rename it to delete the words up to W.
However, all files has the same size and same md5. So. Code is the same for each.
Anyway, is up to you.
One interesting thing I watch with this problem is: the MAC Address did not change at all.
You can change between the files and MAC will remain.
Click to expand...
Click to collapse
hello!
I do not understand because if everyone could fix with this method , I could not . I've tried on es explorer, root explorer, x plore and the permissions part too. but the wifi still gret and i not turn on ... Might you know what this happening? can be the own wifi problem (chip ) into the phone?
Hi.
What was you triyng for?
Did you lost the file?
Remember this file is for JB.
Hi what is secret to using file manager on phone Android 10+ with su access to read and write in system - remove bloat apps? I have su access, but I read in 10+ file system not allow from file manager, only need use adb. How to use file manager with su to remove manually on Android 10+? I get error when deleting app from any file manager with su access "cannot delete". Danke.
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
{
"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"
}
SirisRui said:
Well, i guess that i can reply your question. It seems that we can't mount R/W due to Google's use of dynamic partitions for new version android devices.
However, we still have a way to fix it. Use su permissions and dd command to export those partitions which you want to modify (for example: system, product, vendor, and oem, but oem special), unpack and then repack, at last reboot you devices into fastbootd mode and flash back those partitions into you devices. reboot, now, you can R/W those partitions .
if you need to edit oem partition. You need edit a file in vendor partition firstly. Export and unpacking vendor partition. Finding a file which called "fstab.qcom". Open it and delect（,avb_keys=/product/etc/security/avb/oem.avbpubkey）code inside. Repacking and flash into you devices again. After this, the repackaged oem partition can be mounted correctly by flashing it again otherwise the oem partition can not be mounted (no files inside).
View attachment 5577955
Click to expand...
Click to collapse
Wow very complex but thank you for explain!
So been playing with GSIs.. though none are amazing.. so thinking about porting the Tab S7 to the S6 using the same method.. (Just flashing the system.img file using the Treble method).
I have downloaded the latest S7 ROM
SM-T870_XSA_T870XXU2DWB2
Extracted the AP, BL, CSC & HOME tar files.
Then extacted the super.img
Converted the super.img to raw and extracted that too.
I was expecting to see a 1,2,3 4.ext files which should translate to vendor.img, boot.img, system.img etc.
Though instead i got the full file structure. (pic below).. within this structure is a System folder.. though not sure how i get to a flashable system.img file?
Little help?
Super.img Extract:
{
"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"
}
And within that folder is the System Folder:
btw here the link to the ROM https://samfw.com/firmware/SM-T870/XSA/T870XXU2DWB2
Wish I could help since I would love one ui 5 on this one, I can only make a suggestion though, hopefully not stupid.
Take a look at the T866N firmware/rom, the device is almost identical except from SD855 vs the + variant and the inclusion of 5G, even if the lte/4g/5g modem is broken I think it would be worth it.
Also I'll mention some guy that did this on S21 to S20 successfully @LeeXDA18
Edit: My bad, thought the 5G variant got One UI 5 for some reason, still maybe lee has some clue on this.
its very strange.. i have just extracted the .tar file from the A12 S6 Firmware and i get what i expected..
Looks like the S7 uses a new method of firmware deployment..
I'll give it a try too, for the meanwhile hopefully this guy here has some insight @ShaDisNX255
no one can help on how to create a System.img from an Android 13 ROM for the Tab s7, s8 or s9?]
Just tried the M-X800_EUX_X800XXU3BWC1_f ROM.. though this one despite converts to RAW without issue. I then cannot extract the RAW file.. i am amazed that each of these Firmware's has a different structure!
just tried the S6 Lite ROM too.
SM-P610_XSA_P610XXU2FWC4_f
That RAW extracts without issue.
Though once again i am left with a full folder structure.. how do i get this structure into a flashable System.img?
so i extracted the super.img as above.. and from what i can see it's the same folder structure as a system.img..
so i have tried to flash it within TWRP to the System partition leaving other partitions intact. (treble method).
though now getting an error "Size of image is larger than the target device"
S6 AP is 6.9GB
S7 AP is 7.9GB
so am back to needing to be able to create a new system.img file.. looks like it may need a big debloat.. time to build a linux host..
I dont know if we would be able to shave 1gb of debloat.. this might be a lost cause without repartitioning the System partition on the device.. i dont have any experience with that..
the saga continues..
if anyone wants to play around with the super.img/system.img you can find the link below.
it's untouched from samsung's AP_T870XXU2DWB2_T870XXU2DWB2_MQB62030429_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar.md5 file.
It needs to be extracted debloated and then compressed back into a system.img (in linux).
Or our device needs it's System Partition extended so it can be flashed as is..
easyupload.io
easyupload.io
easyupload.io
Link above.
No one able to help with this project?
would like to but im not able to help for now