Database Info

build my own update.zip error

i try to build my own update.zip
i use haykuro's build 4.9 update.zip, and i add the chinese fonts in to update.zip
but the error happen in recovery utility
the error message is
Code:
E:Can't chown/mod /system/xbin/su
(No such file of directory)
E:Failure at line 121:
set_perm 0 0 06775 SYSTEM:xbin/su
Installation aborted
my working process is
1.upzip haykuro's build 4.9 update.zip
2.add chinese fonts in to system/fonts
3.zip the directory
4.resign the update.zip using signapk.jar
5.put the signed file into sd card
6.enter recovery utility
all the process is working in windows xp sp3
my device is ADP1
recovery utility version is JF v1.4.3
thanks a lot.
===UPDATE===
i get the reason of this trouble
because Chinese font size is too big
original haykuro's build 4.9 rom got 2000k free space
but Chinese font need 3000k
so some file can't flash to system

Your unzip program probably screwed up the archive.
In any case, why are you bothering inserting it into an update? You can put files into /system by remounting it as rw. Also, i'm curious; why are you bothering to add new fonts? The default fontset already has support for zhcn and zhtw.

it can't show the chinese text in original haykuro's build 4.9 rom
{
"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"
}
because the font file is not the same with haykuro's build 4.5
in build 4.5 the font file (DroidSansFallback.ttf) size is 3081908 byte
but in build 4.9 the file size is 117072 byte
so i add chinese font in to update.zip by myself
but get some trouble

Copy the font to your sdcard. Then use Terminal Emulator to remount /system and copy the font from sdcard to the font directory. Or connect Dream to PC and adb push it into the font directory. Should work after you cold reboot.

are you sure you didnt edit the isntall script? it says "set_prem" but should be "set_perm" (prem vs perm) as far as i recall.
Code:
set_prem 0 0 06775 SYSTEM:xbin/su

Darkrift said:
are you sure you didnt edit the isntall script? it says "set_prem" but should be "set_perm" (prem vs perm) as far as i recall.
Code:
set_prem 0 0 06775 SYSTEM:xbin/su
Click to expand...
Click to collapse
i didn't edit isntall script.
that is my spell error and i correct it
thanks

jashsu said:
Copy the font to your sdcard. Then use Terminal Emulator to remount /system and copy the font from sdcard to the font directory. Or connect Dream to PC and adb push it into the font directory. Should work after you cold reboot.
Click to expand...
Click to collapse
i think that is a good idea.
i will try later

I see, you want to show the os interface in zhtw as well. Hope it will work. Did you import your G1? I heard rumors that 中華電信 is going to introduce G1 for TW. Their prepaid 3G data rates are terrible -_-; I spent ~3000NT just for email and Google Reader in one month!

jashsu said:
I see, you want to show the os interface in zhtw as well. Hope it will work. Did you import your G1? I heard rumors that 中華電信 is going to introduce G1 for TW. Their prepaid 3G data rates are terrible -_-; I spent ~3000NT just for email and Google Reader in one month!
Click to expand...
Click to collapse
i think it will introduce HTC Magic for TW
because the haykuro's build 4.9 update.zip has some customize file in system\customize\
CHT__601.xml
Code:
<set name="plenty" max="15">
<item name="title">Hami</item>
<item name="url">http://hami.emome.net</item>
</set>
emome.net is Chunghwa's mobile web site
so, i think Chunghwa is high probability introduce HTC Magic for TW
if your are Taiwanese Android user, you can go to http://android.cool3c.com to join discussion.

[Q] ICS port how to pack custom rom? devs please help.

Hello everyone,
I'd like to pay back the community that have been helping me with my cellphone, and also helped me learn a lot on how to help myself.. so i decided to give back.. i have been customizing GB and for my own personal use, now i am trying to customize ICS port by xbsall. the only problem i have is packing the rom in a flashable zip. I searched everywhere with no success all i need is how to pack the system and data to .img file.
I'd appreciate the help and i will be posting my custom rom the forums soon.
Special thanks to xbsall, defcomg, and everyone working on making the ICS possible on the O3D.

You can try this out:
ROM Factory v1.7.1[May/12/2012]
Although P920 isn't on the "Supported Devices" list...
or this:
[KITCHEN] Android Kitchen, v0.214 [Linux / Mac / Windows]
Just be careful.

Mount .IMG As Dir Named system
Code:
mkdir system
sudo mount -t ext4 -o loop system.img system/
New System
Code:
sudo cp -ar system new_system
Create New .img
Code:
sudo ./make_ext4fs -l 700m -a system system.img new_system/system
Source

defcomg said:
Mount .IMG As Dir Named system
Code:
mkdir system
sudo mount -t ext4 -o loop system.img system/
New System
Code:
sudo cp -ar system new_system
Create New .img
Code:
sudo ./make_ext4fs -l 700m -a system system.img new_system/system
Source
Click to expand...
Click to collapse
Thanks guys, I am gonna try and report back..

BadSoul said:
Thanks guys, I am gonna try and report back..
Click to expand...
Click to collapse
I tried those methods and none of it created me a .img packed rom.
Any other suggestions? please
Thank you

BadSoul said:
I tried those methods and none of it created me a .img packed rom.
Any other suggestions? please
Thank you
Click to expand...
Click to collapse
Lets suppose you have made the changes to your system the way you like it. (add/remove apps , etc)
Now in order to make your system.img
boot into cwm/twrp
connect to pc
use the following command to make the img file
adb shell
dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
wait until it ends
your system.img is ready and packed into your emmc
make sure your emmc has plenty of space to fit it
now you can make a zip file with it and use the command
package_extract_file("system.img", "/dev/block/mmcblk0p7");
in your updater script to unpack
happy cooking
_____________________________________________________
the cmd output should look like this
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # cd dev
cd dev
/dev # cd block
cd block
/dev/block # dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
1445274+0 records in
1445274+0 records out
739980288 bytes (705.7MB) copied, 126.201996 seconds, 5.6MB/s
/dev/block #reboot

Thank you very much xbsall. That worked perfectly.
Do you know can i create data.img also? most of my customization is in the data. I'd really appreciate it.
What block is it in?
Thanks for the great work.

mmcblk0p8 is data
Sent from my LG-P920 using xda app-developers app

iodak said:
mmcblk0p8 is data
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Awesome! thanks iodak, xbsall, defcomg and TMProduct1onZ.. I really appreciate the help.

xbsall with dsixda's kitchen would there have to be a new edify_defs created for SU760 if using your XBSA404 port? The reason I am asking is I am getting an error Status 0 when creating a ROM in the kitchen. I think this may be due to the device being ro.product.device=SU760 in build.prop but not having an edify_defs for the SU760? any help appreciated.
Status 0 might be two things: 1) You used an update-script (Amend format, which is very old) when you should be using an updater-script (Edify format), or the other way around; OR 2) Your updater-script is using the "MTD" partition type when mounting a partition rather than another type such as EMMC (and thus, you need the device defined under the kitchen's /tools/edify_defs folder).

Havent used dsixda kitchen for a long long long... long time.
So i cant help you with it.
Tell me what you wanna do to your ROM.

xbsall said:
Havent used dsixda kitchen for a long long long... long time.
So i cant help you with it.
Tell me what you wanna do to your ROM.
Click to expand...
Click to collapse
Just trying to start with a basic platform by de-odexing and zip alligning and build on it from there
dsixda's kitchen seemed like the easiest method and i've managed with some degree of success but required the update binary from other peoples ROM's which I would rather not do.

Lol just adb pull/push them..

xbsall said:
Lol just adb pull/push them..
Click to expand...
Click to collapse
lol thats fine but i'd rather have a flashable zip without having to use others update binary and modified updater script :victory:
---------- Post added at 10:16 PM ---------- Previous post was at 10:13 PM ----------
I'll keep messing around with the kitchen in the meantime :laugh:
BTW that looks tremendous is it ROM: XBSA V3b ICS ROM for Optimus3D P920 with ACiD Audio?
{
"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 its v3b

nexus 5 internal storage GONE!

Hi,
My Phone restart itself several times and the sdsard0 partition is damage,
I didn'y backup my photos, are there any way to get back the photos?
My phone is stock, locked, non root, 4.4.4 KTU84P.
{
"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"
}
IMEI is also losted But the photos is the most important in this stage

Google auto back up wasn't turned on?
Sent from my Nexus 5 using XDA Free mobile app

Only synced Contacts , Chrome and app data

Really nothing can do?

Looks like ya may have to format the card in windows and hope it restores. Im gonna add that your photos and more than likely gone. I have all my photos auto back up to google and Dropbox daily. If ya manage to fix it, I'd definitely look into a service to back your stuff up.
Sent from my Nexus 5 using XDA Free mobile app

OP, not sure if you'll be able to access your data after this, but can't hurt to try: check general section for a how-to fix a corrupted /data partition.

still not working
Method1:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
--------------------------------------------------------------------------------------------------------------------------
Method2:
[GUIDE] to fix persist partition
Result :

This looks bad, worst case you need to flash a factory image in order to at least restore the IMEI.
If you´re brave enough, try to boot from eg. Gparted Live ( look it up on the web ) and try to restore the file system with this partition tool. Maybe your device can be identified again as a Nexus 5. But be warned, I would try this method as the last resort only since there is a risk involved of losing your partition table.
Only try this if fastboot and all other methods fail.

nat510 said:
still not working
Method1:
~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
--------------------------------------------------------------------------------------------------------------------------
Method2:
[GUIDE] to fix persist partition
Result :
Click to expand...
Click to collapse
when trying to fix /data, was it mounted? if it was, you might need to unmount it first.
also, that last error when flashing factory images... not a good omen

flash a cwm recovey
connect phone to your pc
open cmd
type adb shell
type parted /dev/block/mmcblk0
type print
post the screenshot of the output

beekay201 said:
when trying to fix /data, was it mounted? if it was, you might need to unmount it first.
also, that last error when flashing factory images... not a good omen
Click to expand...
Click to collapse
Oops, I forgot...
But still not working

bitdomo said:
flash a cwm recovey
connect phone to your pc
open cmd
type adb shell
type parted /dev/block/mmcblk0
type print
post the screenshot of the output
Click to expand...
Click to collapse
and

nat510 said:
and
Click to expand...
Click to collapse
On the first picture you are not the root.
The prompt on the second picture looks like you have twrp and not cwm. twrp does not have parted included.
Also in your previous posts I saw you were using the wrong commands to flash lollipop 5.1.1.
You used fastboot flash update -w hammerhead.......zip which is wrong. That command wipes /data and /cache then tries to flash hammerhead.......zip to the "update" partition and it fails there. There is no update partition.
The correct command is fastboot -w update hammerhead....zip, but it would be better if your run the flash-all.bat as it will flash the bootloader and the modem too.

bitdomo said:
On the first picture you are not the root.
The prompt on the second picture looks like you have twrp and not cwm. twrp does not have parted included.
Also in your previous posts I saw you were using the wrong commands to flash lollipop 5.1.1.
You used fastboot flash update -w hammerhead.......zip which is wrong. That command wipes /data and /cache then tries to flash hammerhead.......zip to the "update" partition and it fails there. There is no update partition.
The correct command is fastboot -w update hammerhead....zip, but it would be better if your run the flash-all.bat as it will flash the bootloader and the modem too.
Click to expand...
Click to collapse
O......low level mistake.
The partition problem seems to be fixed:good:

How To Guide [GUIDE] How to make your System RW / Super R/W read/write-able

Welcome to the one and only, the original, universal
SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac​
This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware.
This allows you to mount your device as R/W and fully debloat your device and customize your MIUI experience to make it run as smooth as silk!
MIUI 12 is great but it has a little bit too much bloatware.
Be very careful and make lots of backups before messing with your System ! One small error could cause irreversible bootloop!
Enjoy debloating and customizing your fully read/write-able Android device!
NOTE: Before launching this script make sure you've got full read/write (rw) access to the /data partition by first decrypting and then mounting /data partition as r/w !
Visit official project thread​
{
"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"
}

PS C:\adb> adb shell "ls -Alg /dev/block/by-name | grep 'super'"
lrwxrwxrwx 1 root 16 1970-02-02 16:40 super -> /dev/block/sda23
POCO X3 pro

/

so does this work on x3 pro?
edit, it didnt. threw some devblock warnings about not mounting

@gsser Yes it works! Try latest version! Good luck!

lebigmac said:
@gsser it can work depending on how much effort you decide to put into it.
Click to expand...
Click to collapse
well if it is like that, then why is there even a non complete script when it can be done by the owner...
And since you have already asked how it is on x3 pro im saying it doesnt work.
"I'm looking forward to hearing from the Poco X3 Pro users how the script performs on your device."

It is mostly because of current recoveries for x3 pro doesnt support /data yet, but the script can use sdcard rather than internal storage.

@gsser Thanks for the screenshot and feedback. Please download latest v1.32
Feel free to send me your log files if you get any errors and I'll take a look. Thanks.

lebigmac said:
@gsser Thanks for the screenshot and feedback. Please download latest v1.31 that I uploaded today. And feel free to edit the script with your favorite text editor and change the super image dump path in line #333 to this. Then save file.
Code:
sDumpTarget="/sdcard/super_original.bin"
Feel free to send me your log files if you get any errors so I can take a look. Thanks.
Click to expand...
Click to collapse
Only lines i could find about data were these and i edited the path to my sdcard, flashed it.
Edit just seen you edited your reply. Ill try

I'm not 100% sure if your changes will work properly. Feel free to give it a try.
Keep in mind if you change variables the script might not work as expected.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. That's why it's better to launch script from /data/local/tmp
Poco x3 pro recovery don't have full r/w access to /data/local/tmp ?! That's crazy!
You can try launch script directly from android and it should work as expected.

lebigmac said:
I'm not 100% sure if your changes will work properly. Feel free to give it a try.
You can also use /sdcard path it should be the same thing as what you wrote. Good luck.
Please report back any errors thanks.
Keep in mind if you change LOC variable you must also copy the whole script folder to that new location.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. Is better to launch script from /data/local/path
You don't have full access to /data/local/path in poco x3 pro?
Click to expand...
Click to collapse
This is how the folder looks rightnow. Do i need to do anything about it? Also what is LOC :c
Edit nvm, lol im blind

Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.

lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Click to expand...
Click to collapse
Yeah ill just change than only line

lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.
Click to expand...
Click to collapse
All available recoveries have issue mounting data, some cant even mount mtp.
Ill try android one and see what happens.

If your /data partition is not mounted then you can try manually mounting /data partition before running script.
mount /data

lebigmac said:
LOC is a safety path check feature I had to implement because some folks were launching the script from God knows where and overwriting God knows what with dd lol.
Did you try manually mounting /data partition before running script?
mount -o remount,rw /data
Click to expand...
Click to collapse
Yeah, ill try android version then flash it with fastboot but im a bit confused. Do i execute this command or do i need to do other things? Sorry im a noob at these things
./makesysrw.sh in=./files/super/super_original.bin out=./custom/path/super_fixed.bin size=50
Actually ill stop here since i dont get the whole thing, i dont understand at all :/ once i tried to use linux and it was not fun for me... Im bad with command lines and scripts

After copying script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
chmod +x ./systemrw.sh
./systemrw.sh size=50

lebigmac said:
After installing script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/makesysrw_1.31
chmod +x ./makesysrw.sh
./makesysrw.sh size=25
Click to expand...
Click to collapse
now this is what i like

are you sure your bootloader is unlocked?

now do i need to flash the super_fixed.bin in script folder's files folder in fastboot? original super is approx. 8gb and fixed one is nearly half of it

Android 10+ system file r/w access

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!