Aloha community,
after 3 years of using an iphone i switched back to android with a new shiny z3 compact aka aries.
while staying in touch with android by developing apps and rooting/flashing a few phone from friends i am a bit out of ideas when it comes to my new phone...
what i did so far:
rooted phone,
backed up ta-partition
opened bootloader
installed cwm-recoverey by doomlord
tried to flash cm 12 (edited update-script to allow 'aries') -> install aborts without error message
tried to flash cm 11 -> black screen after reboot need to refresh boot.img in fast boot and restore android from backup
tried aosp 5.0.2 -> works fine but no detection of SIM, Camera, no root... i will wait for the official release from sony.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Since i want to get rid of the whole sony bloatware (which is a pain to remove manually on the phone) and also don't want to do it every time i need to reboot + want to offer the opportunity to others to install a relatively clean rom i tried to make my own rom based on the cwm backup...
therefore i copied the boot.img from the backup + the extracted system.ext4.tar folder in a new folder.
I removed all apps i didn't want / added others
I copied the META-Inf from the DRM-resoter zip and edited the updates-script.
it now reads:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
ui_print(" ");
ui_print(" Deleting /system ");
ui_print(" ");
delete("/system/*");
ui_print(" ");
ui_print(" Extracting Files ");
ui_print(" ");
package_extract_dir("system", "/system");
ui_print(" ");
ui_print(" Setting Permissions ");
ui_print(" ");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/system/framework");
set_perm_recursive(0, 0, 0755, 0644, "/system/priv-app");
ui_print(" ");
ui_print(" Unmounting System ");
ui_print(" ");
unmount("/system");
ui_print("------------------------------------------");
ui_print(" Finished ");
ui_print("------------------------------------------");
i stored the folder as a zip and signed it. Now it should be a flashable rom...
when i try to install it with cwm recovery the installation aborts.
the Log says:
Code:
-- Installing: /storage/sdcard1/custom-signed.zip
Finding update package...
I: Update location: /storage/sdcard1/custom-signed.zip
Opening update package...
Installing update...
Installation aborted.
I: using /data/media for /sdacrd/0/clockworkmod/.last_install_path.
I:Can't partition non mmcblk device: /devices/msn_sdcc.2/mmc_host
can someone tell me where i did something wrong?
if anyone likes to have a look at the rom:
Code:
archy.no-ip.org/owncloud/public.php?service=files&t=bf55a79f9d9660641b115db5da352f5f
I hope you guys can help me!
Greetings
i think i could describe my problem better, updated the start post
Related
Welcome to the Eternity Project's Olympus CWM Kernel Flasher with AUTO Tegrapart recognizer Thread!
What's it?
It is inspired by the idea that koush had with AnyKernel. It is intended for use only for devs. It will copy the CMDLINE of your device and assemble a boot.img with your own cmdline, so you can use the same package for deploying kernels to all different tegrapart devices.
What will it do and how much time will it take
It will take the current device's cmdline and assemble the bootimg. The required files has to be named "eternityImage" (kernel image) and "eternityrd.gz" (ramdisk/initrd).
The process of taking the cmdline and assembling the new bootimg will be done almost instantly. It should take like 0.2 seconds.
What I need
- A PC
- A kernel zImage
- A RamDisk
- Eventually a WiFi module
- A BRAIN
What does it contain:
- Scripts and files that needs to be executed
- Nothing else.
The funny part
Those are the scripts used by the KernelFlasher package. You can modify them (especially the update-script) as you want. Just remember to add credits
Creating the boot image:
Code:
#!/sbin/sh
echo \#!/sbin/sh > /tmp/createnewboot.sh
echo /tmp/mkbootimg --kernel /tmp/eternityImage --ramdisk /tmp/eternityrd.gz --cmdline \"$(cat /proc/cmdline)\" --output /tmp/eternityprj.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?
Recovery update-script
Code:
ui_print(" ");
ui_print("Eternity Project for Motorola Olympus: ATRIX");
ui_print(" ");
ui_print(" ll ll ll ll ll");
ui_print("E ll ll ll ll ll");
ui_print("T ll ll ll ll ll");
ui_print("E oooooooooooooo ");
ui_print("R lllllloooooooooooooollllll");
ui_print("N lllllloooooooooooooollllll");
ui_print("I oooooAP20ooooo ");
ui_print("T lllllloooooooooooooollllll");
ui_print("Y lllllloooooooooooooollllll");
ui_print("P oooooooooooooo ");
ui_print("R ll ll ll ll ll");
ui_print("J ll ll ll ll ll");
ui_print(" ll ll ll ll ll");
ui_print(" ");
ui_print("Update contains: Kernel+Modules");
ui_print("Developed by kholk");
set_progress(1.000000);
ui_print("Converting SYSTEM to EXT4");
run_program("/sbin/tune2fs" , "-O" , "extents,uninit_bg,dir_index" , "/dev/block/mmcblk0p12");
ui_print("Running FSCK...");
run_program("/sbin/e2fsck" , "-pf" , "/dev/block/mmcblk0p12");
ui_print("Extracting Modules...");
mount("ext4" , "EMMC" , "/dev/block/mmcblk0p12" , "/system");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Extracting Kernel Files...");
package_extract_dir("kernel", "/tmp");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
ui_print("Detecting your ATRIX CMDLINE...");
run_program("/tmp/mkbootimg.sh");
ui_print("Detected! Custom EternityProject Kernel created.");
ui_print("Erasing Boot Partition...");
run_program("/sbin/busybox", "dd", "if=/dev/zero", "of=/dev/block/mmcblk0p11");
ui_print("Writing Boot Image...");
run_program("/sbin/busybox", "dd", "if=/tmp/eternityprj.img", "of=/dev/block/mmcblk0p11");
ui_print("All done.");
ui_print("Remember to check for updates frequently!");
ui_print("Enjoy!");
Download
MegaUpload
The Eternity Project Developer,
-kholk
Cool! Now to find out what it does...
wirednix said:
Cool! Now to find out what it does...
Click to expand...
Click to collapse
According to the Eternity Project Kernel thread this appears to be an automated way to determine the correct kernel for AT&T or international, or other Tegra options. It is intended so that devs can release a single package and take user error out of the equation for some releases.
wirednix said:
Cool! Now to find out what it does...
Click to expand...
Click to collapse
kholk said:
What will it do and how much time will it take
It will take the current device's cmdline and assemble the bootimg. The required files has to be named "eternityImage" (kernel image) and "eternityrd.gz" (ramdisk/initrd).
The process of taking the cmdline and assembling the new bootimg will be done almost instantly. It should take like 0.2 seconds.
Click to expand...
Click to collapse
Emh...........
I'm attempting to make an install script for a couple of mods just as before on the Droid X. Unfortunately I'm getting different errors at different times. One of the errors is (Status 0)... and the other is (Status 6).
Also, Mount says that it expects 4 args, got 3.
What changed?
nitro66215 said:
I'm attempting to make an install script for a couple of mods just as before on the Droid X. Unfortunately I'm getting different errors at different times. One of the errors is (Status 0)... and the other is (Status 6).
Also, Mount says that it expects 4 args, got 3.
What changed?
Click to expand...
Click to collapse
You need to use the right Syntax to mount /system . Best way... Busybox.
run program("/sbin/busybox" , "mount", "/system");
DroidTh3ory said:
You need to use the right Syntax to mount /system . Best way... Busybox.
run program("/sbin/busybox" , "mount", "/system");
Click to expand...
Click to collapse
So... I've tried this.... and I get....
Error in /sdcard/update.zip
(Status 6)
For Shi*s and giggles... I just did a test script.
ui_print(" ");
ui_print("Mount Bionic Script...");
run_program("/sbin/busybox", "mount", "/system");
ui_print("Doing Something.......");
ui_print("Installing Files");
ui_print(" ");
ui_print("** Unmounting System **");
unmount("/system");
This errors out. I have the META-INF folder from another Bionic update that someone else created, so I'm assuming that the files within (other than the script) will work as is.
Here is my mod script and update-binary. Make the appropriate folders for your mod and give it a go.
Case and spacing is essential as I am sure you know.
3G ICON VISUAL FIX
DroidTh3ory said:
Here is my mod script and update-binary. Make the appropriate folders for your mod and give it a go.
Case and spacing is essential as I am sure you know.
3G ICON VISUAL FIX
Click to expand...
Click to collapse
ui_print(" ");
show_progress(0.800000, 35);
ui_print(" ");
ui_print("** Mounting this ***** **");
run_program("/sbin/busybox", "mount", "/system");
ui_print(" ");
ui_print("** Installing Your MOD **");
ui_print(" ");
ui_print("** Unmounting System, Rock Out!! **");
unmount("/system");
show_progress(0.050000,0);
Ugh... same error. I only deleted your package extract. I'm using 7-zip and just doing store. Is that still the preferred method?
nitro66215 said:
ui_print(" ");
show_progress(0.800000, 35);
ui_print(" ");
ui_print("** Mounting this ***** **");
run_program("/sbin/busybox", "mount", "/system");
ui_print(" ");
ui_print("** Installing Your MOD **");
ui_print(" ");
ui_print("** Unmounting System, Rock Out!! **");
unmount("/system");
show_progress(0.050000,0);
Ugh... same error. I only deleted your package extract. I'm using 7-zip and just doing store. Is that still the preferred method?
Click to expand...
Click to collapse
What is it installing if there is no package extract?
I don't use 7zip, I just compress in linux... Couldn't really say in that.
DroidTh3ory said:
What is it installing if there is no package extract?
I don't use 7zip, I just compress in linux... Couldn't really say in that.
Click to expand...
Click to collapse
I plan on doing the install later, but I just wanted to do a test script without install. Just some "Hello World" text to make sure I got something going on.
I even just did that....
ui_print("Hello World");
Gave me the same error!
Ok.... so.... It is now working after a reboot of Recovery. Don't ask me why. And I am using standard windows zipping.
I'm new to android and am wondering if there were any tools available to port the full_wipe.zip from the desire hd/inspire 4g to the vivid. It's a great tool that I used on the inspire and will reduce the issues that a lot of users might run into for this device. The later versions even gave the ability to format all of the memory to EXT4. I'm willing to work on a version if someone is able to point me in the right direction.
Edit: this tool might also be an option as a replacement to our current recovery.
http://forum.xda-developers.com/showthread.php?t=1161710
not really sure i understand the need for it?
this is an inspire/dhd script:
Code:
ui_print(" ");
ui_print("-------------------------------- ");
ui_print("| FULL WIPE v 1.5 |");
ui_print("| Fixed For Ext4 |");
ui_print("| Mero01 |");
ui_print("-------------------------------- ");
ui_print(" ");
show_progress(0.500000, 0);
ui_print("-Checking Model ID");
assert(getprop("ro.product.device") == "ace" || getprop("ro.build.product") == "ace" || getprop("ro.product.board") == "ace");
ui_print("-Success!");
ui_print("-Model ID - HTC Ace");
ui_print("-Ok to proceed");
ui_print("Now preparing for a clean install of any EXT4 ROM ");
ui_print("Please be patient");
ui_print("1st boot may take a few minutes");
show_progress(0.500000, 40);
ui_print("-Formatting Data");
format("ext4", "EMMC", "/dev/block/mmcblk0p26");
ui_print("-Formatting System");
format("ext4", "EMMC", "/dev/block/mmcblk0p25");
ui_print("-Writing System");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
show_progress(0.400000, 0);
ui_print("-Formatting Cache");
assert(unmount("/cache"), ui_print("/cache unmounted"));
format("ext4", "EMMC", "/dev/block/mmcblk0p27");
delete_recursive("/sdcard/.data/navigator/Data/Temporary");
show_progress(0.100000, 0);
ui_print(" ");
ui_print("FULL WIPE COMPLETE =]");
ui_print(" ");
ui_print(" ");
ui_print("Make SURE YOU INSTALL A ROM...");
ui_print("Make SURE YOU INSTALL A ROM...");
ui_print("Make SURE YOU INSTALL A ROM...");
unmount("/system");
all it does is print lines and format the following:
/data
/system
/cache
and it goes an extra step and deletes a directory on your sdcard that looks non-volatile....
this is just one of the scripts i had from my inspire days....im sure there are others...
but the real deal is this:
/system is always formatted during a rom install
/cache usually is also, but not always
if you do a wipe/factory reset, it formats /data and /cache
so redundant wipe is redundant....
Would the custom ext4 recovery be a better option? It has the same features as cwm recovery but also adds the wipe functions of the script. I prefer the custom recovery but am not sure to where to start.
Apatche69 said:
Would the custom ext4 recovery be a better option? It has the same features as cwm recovery but also adds the wipe functions of the script. I prefer the custom recovery but am not sure to where to start.
Click to expand...
Click to collapse
since nobody has created an ext4 recovery for our device, its not even close to viable yet
but i dont think you get what im saying.....those functions are INCLUDED in the recovery we have....
wipe data/factory reset will wipe /data and /cache
installing a rom, formats and loads /system
why does anyone feel the need for another script that does the same thing that you can do with one option in recovery?
Apatche69 said:
Would the custom ext4 recovery be a better option? It has the same features as cwm recovery but also adds the wipe functions of the script. I prefer the custom recovery but am not sure to where to start.
Click to expand...
Click to collapse
Follow the superguide ROM flashing guide and you won't need a script like this. Wipe cache, data, dalvik.
Sent from my HTC PH39100 using xda premium
I created two flashable zips that I'd like to use after every rom flash:
One is all my Layers overlay apks and the other is all the font files I want to use.
Here is my updater-script that I use in both zips, the only difference being the ui_print and file names, of course:
Code:
ui_print(" Installing Layers overlays... ");
ui_print(" ");
show_progress(0.99, 30);
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
set_perm_recursive(0, 0, 0644, "/system/vendor/overlay");
show_progress(1.0, 1);
unmount("/system");
ui_print("----------------------------------------------");
ui_print("| Done!!! |");
ui_print("----------------------------------------------");
ui_print(" ");
And here is the error I get in recovery when I flash either zip:
Code:
set_perm_recursive() expects 5+ args, got 4
E:Error executing updater binary in zip '/sdcard/Mods/Zips/Layers-Themes-signed.zip'
Error flashing zip '/sdcard/Mods/Zips/Layers-Themes-signed.zip'
Obviously, I did set
Code:
set_perm_recursive(0, 0, 0644, "/system/vendor/overlay");
to be the right permissions. I know that the contents of that directory, /system/vendor/overlay need to be 644 but I don't know the proper edify script syntax for
Code:
set_perm_recursive(0, 0, 0644, "/system/vendor/overlay");
Does anyone know what I need to do differently to make these zips flash properly?
EDIT: I found this post that said that the correct syntax should be: set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/overlay"); instead. Problem solved!!
I know you figured it out, but the set_perm_recursive needs 5 arguments (as stated in the error message you received). It would be for group:user ownership and then permissions for directories & files (in that order) followed by the directory that you're setting permissions in.
imnuts said:
I know you figured it out, but the set_perm_recursive needs 5 arguments (as stated in the error message you received). It would be for group:user ownership and then permissions for directories & files (in that order) followed by the directory that you're setting permissions in.
Click to expand...
Click to collapse
@imnuts, would it be this?
Code:
set_perm_recursive(0, 0, 0, 0755, 0644, "/system/vendor/overlay");
Hi mates, I need your help, thank you!
I would use my old phone (g900v cdi11 locked bootloader) as a videosurvelliance camera, to do that I need that it can reboot automatically if battery runs out and power appears again. To do that I need to change lpm file inside /system/bin folder, switch off phone, plug the power abd check if script lpm file works, if not edit it and check again. . To do that I have these ideas:
1) flash a rooted LL rom, and use a root file manager and overwhite lpm file, is it that easy and possible?
2) Boot on safestrap (which I've already installed and accessible flashing the KK bootloader with Odin, the version is about 2.7.4, don't remember exactly) and chage from there, but the SS file manager don't see any files, probably it's running not rooted (??), maybe /system not mounted, and I don't know all the Unix command I've to type in console to edit lpm or overwrite it, or eventually with ADB.. it copied but in reality I don't know where, it's not /system/bin.
3) so I need to "flash"/install a .zip file containg the /system/bin/lpm file, but for doing this I need a script, which is actually what I'm asking here
4) Any other ideas? Please remember I have a cid11 g900v, so no root on MM, and some other complications unfortunately.
For the script I've tried to arrange from one SS installation, and I tried to save only these lines, but I'm not sure it will do the job, the idea is to create a zip file with system/bin/lpm file and META-INF/com/google/android/updater-script file:
Code:
ui_print("*************************************");
ui_print("* Change lpm *");
ui_print("*************************************");
ui_print("");
unmount("/system");
ui_print("Writing System Files");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_dir("system", "/system");
set_progress(0.600000);
ui_print("Setting Permissions...");
ui_print(" ");
#PERM
set_metadata_recursive("/system/bin", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
ui_print("------> Done!");
unmount("/system");
ui_print(" ");
ui_print(" Installation complete ");
ui_print(" ");
ui_print(" ");
What is missing eventually?
Thank you!
By the time I solved flashing every time the whole rom (exploded, edited and repacked in Windows), boot It and wit its installation.
It still interesting to read your suggestions, thank you