Related
For those who want an easy way to create and sign CWM flashable zips via windows, look no further... this is about as easy as it gets!
1. Unzip contents of package to a folder we'll call this folder "tools"
2. in "tools" you will now have the included files plus and "update" folder
3. in "update" folder you have "META-INF," "system," & "data" folders
4. place any files you want copied to system in "system" folder, make sure your structure is proper.
5. place any files you want copied to data in "data" folder, make sure structure is proper.
6. once you have everything set in place, you have four options:
• 6a: drag the folder on top of "DRAGandDROPzipANDsign.bat" wait for it to finish, you will end up with {folder_name}_update.zip in the same folder as 7za.exe
• 6b: double click SIGNandZIPmanual.bat, type the name of the working folder, hit enter, wait for it to finish, it will loop back and allow you to complete another task, or hit X + Enter exit.
• 6c: double click SIGNonlyMANUAL.bat, enter just the zip filename you want to sign (no extension), hit enter and wait for it to finish. It will loop back and allow you to sign another one or hit X + Enter to exit.
• 6d: drag a ZIP on top of DRAGandDROPsignONLY.bat to sign/re-sign a zip that's already been built.
Click to expand...
Click to collapse
I suggest if you are using this method to replace any system files, to delete the existing file first by adding some lines to the updater-script found in the META-INF folder. as follows:
Code:
delete("/system/app/Rosie.apk");
these lines can be added below the
Code:
mount("MTD", "data", "/data");
line... make sure filenames correct because they are case sensitive.
Hopefully this will make your lives a little easier =)
LATEST VERSION MIRROR: CLICK HERE
Code:
CHANGELOG:
1.1 - Current
~~* Silent update, forgot to include a couple of the updated files... oops! =)
1.0 - Update
~~* All drag & drop versions now support dragging and dropping from anywhere, not just the "working" directory.
~~* Fixed manual versions, where the loopback to work with more files was not working properly.
~~* Now deletes the unsigned zip after building the signed zip.
~~* Cleaned up folder a bit, now works from _bin folder, and outputs to _out folder. Batch file should stay in "main" folder, one level above _bin folder.
0.9 - Update
~~* Added sign only, manual plus drag & drop versions
~~* Included FR translation (google) of the d&d zip and sign
0.8 - Update
~~* removed the random .apk that was accidentally included in 0.6, not sure what happened to 0.7... lol
0.6 - Initial forum release
quick little update... apparently I had included a small .apk in the update folder... my bad, sorry for the waste of bandwidth =)
as the great homer simpson would say: DOH!
Hi ...
I'm not developer but it seems what you're doing will help other developers (and in the end: I'll benefit from that)...
Here's a "thank you" note..
... note: this post is just my way to become a post-whore like you.... j/k
would it also work for Amon-RA?
bestofrhcp said:
would it also work for Amon-RA?
Click to expand...
Click to collapse
yes, latest versions of amon-ra and cwm are both work only with edify scripts, so yes. you just need to know what your specific system & data paths are, system should be the same for everyone, but some devices use userdata /userdata instead of data /data... hopefully that makes sense =)
hope this helps =)
a new version, for the "manual" script will actually loop back when finished building/signing a zip, so that you can do multiple build/sign sessions, without having to reopen the script after every build/sign session will be updated shortly... I've already tested it and got it working... no real changes to the drag-and-drop file as it's not really necessary... I am trying to figure out a way to do a drag and drop sign only script, so once I have that figured out I will updated again...
updated =)
Thanks! This will save me from using Terminal Emulator after each cm nightly flash.
wilnotdie said:
thanks! This will save me from using terminal emulator after each cm nightly flash.
Click to expand...
Click to collapse
oops! Oops! ^~^
UDPATED... sorry if you downloaded 1.0, download again now @ 1.1... forgot to include a couple of the updated files... double checked everything this time though... =) enjoy!
looks like you might be able to answer my question
was playing around and deleted systemui.apk from system\app folder...
was trying to replace with another one... that did not work...
so i tired putting back the original one... and that does not install either...
is there a way to install that back on ?
if it is just guide me a lil bit...
will this procedure actually install the file?
http://forum.xda-developers.com/showthread.php?t=1268661
thank you
heart_crafter said:
looks like you might be able to answer my question
was playing around and deleted systemui.apk from system\app folder...
was trying to replace with another one... that did not work...
so i tired putting back the original one... and that does not install either...
is there a way to install that back on ?
if it is just guide me a lil bit...
will this procedure actually install the file?
http://forum.xda-developers.com/showthread.php?t=1268661
thank you
Click to expand...
Click to collapse
just do this
Code:
adb remount
adb push SystemUI.apk /system/app
adb reboot
no need to "install" it, it just needs to be in the system/app folder at boot time... you might actually want to "adb reboot recovery" instead of "adb reboot" and then clear dalvik before rebooting into OS again...
I tried testing it by droping a apk in a folder called app and then dropping the app folder in data and then went ahead and used the .bat. I went into recovery, flashed it without an error but nothing was installed once i booted. Any ideas? Dont scripts very like some have a run program system/xbin/busybox etc?
edit. I was able to move the folder from data to system and then ran the script and flashed it and it worked, it should up once it booted. Is there any way to get it to flash data/app?
benjamminzIS said:
just do this
Code:
adb remount
adb push SystemUI.apk /system/app
adb reboot
no need to "install" it, it just needs to be in the system/app folder at boot time... you might actually want to "adb reboot recovery" instead of "adb reboot" and then clear dalvik before rebooting into OS again...
Click to expand...
Click to collapse
thanks for the code...
but i already had copied the file into system/app... and it wasnt working (wasnt installing) just did a dalvic wipe now... and looked at that file permission and it was different from all other system apps... so i matched them up.. and rebooted ... and systemtray is back
thank you!
jgrimberg1979 said:
edit. I was able to move the folder from data to system and then ran the script and flashed it and it worked, it should up once it booted. Is there any way to get it to flash data/app?
Click to expand...
Click to collapse
here's the hint from the first post:
benjamminzIS said:
I suggest if you are using this method to replace any system files, to delete the existing file first by adding some lines to the updater-script found in the META-INF folder. as follows:
Code:
delete("/system/app/Rosie.apk");
these lines can be added below the
Code:
mount("MTD", "data", "/data");
line... make sure filenames correct because they are case sensitive.
Click to expand...
Click to collapse
copy the extract_package line that references "system" and change "system" to "data" in all cases, or if you have no need to copy anything to system then just change all "system" cases to "data" rename the "system" folder to "data" then add your files as necessary...
I am not sure i understand. Let me try and clarify what i am in trying to do. I am trying to build a flashable zip that contains an apk that i want to essential be installed in data/app directory. thats it.
What i see from the script below is that you have everything covered, system and data, so i am assuming if nothing is in the folder as system then it will be skipped over, correct
ui_print("");
ui_print("");
ui_print("Clearing dalvik cache ...");
delete_recursive("/data/dalvik-cache");
mount("MTD", "system", "/system");
mount("MTD", "data", "/data");
ui_print("");
ui_print("");
ui_print("Installing files to system ...");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("");
ui_print("");
ui_print("Installing files to data ...");
show_progress(0.700000, 50);
package_extract_dir("data", "/data");
unmount("/data");
show_progress(10.000000, 1);
ui_print("Done.");
jgrimberg1979 said:
I am not sure i understand. Let me try and clarify what i am in trying to do. I am trying to build a flashable zip that contains an apk that i want to essential be installed in data/app directory. thats it.
Click to expand...
Click to collapse
oh ok... sorry... yeah I think for anything that goes to data, there needs to be an install command try adding install("/data/app/filename.apk"); for each file, after the package_extract_dir("data", "/data"); function... not sure if that is correct, but maybe?
I am trying to edit the updater script in NexusHD2 Gingerbread latest version so it will flash the kernel properly with cLK without having to install a second zip for kernel after installing rom zip.... here is what I do.... In the updater-script that's in nexushd2, i take these lines:
ui_print("Copying zImage and initrd.gz to boot...");
package_extract_dir("boot", "/boot");
And replace them with this:
ui_print("installing Kernel");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
And then I delete the /boot directory in the nexushd2 zip file and put in the boot.img from the kernel zip.... I get error in .zip, status 6 when I try to install the finished zip file.... anyone know what I can do to fix this? Thanks in advance for any help.....oh yea, I also tried the boot.img from my clockwork backup.... and if it matters.... im using wordpad for windows to do this....thanks in advance for any help....my thoughts were that its maybe something to do with the/tmp not being mounted..... but the script I took the lines from to extract and mount the boot.img was from hyperdroid rom... and it didn't have anything in that script about mounting /tmp that I saw.....
EDIT: Just tried to do the same in jedit instead of wordpad and had the same result.... does updater-binary file need to also be changed? If so, how do I do that? If I can't do it with windows, I also have latest ubuntu.....
here's updater-script if you want to have a look
https://gitorious.org/android-leo-r...META-INF/com/google/android/updater-script.lk
Thanks for the reply.... can you verify this is what I did wrong, I can't try it at the moment....
format("yaffs2", "MTD", "boot");
mount("yaffs2", "MTD", "boot", "/boot");
that's what I had in my updater script..... but I need to take out yaffs 2 on both lines so it looks like this:
format("MTD", "boot");
mount("MTD", "boot", "/boot");
?? From what I can see on yours, I can take out the yaffs2 line on every format and mount option?
diesburg said:
Thanks for the reply.... can you verify this is what I did wrong, I can't try it at the moment....
format("yaffs2", "MTD", "boot");
mount("yaffs2", "MTD", "boot", "/boot");
that's what I had in my updater script..... but I need to take out yaffs 2 on both lines so it looks like this:
format("MTD", "boot");
mount("MTD", "boot", "/boot");
?? From what I can see on yours, I can take out the yaffs2 line on every format and mount option?
Click to expand...
Click to collapse
It depends on the update-script you are using, so I presume, that would be the case.
give it a go, and see what happens
I'm using update-script and update-binary(if update-binary would make any difference) that was already in the nexushd2 roms and just editing them to do boot.img instead of initrd and zimage from the /boot directory.... but I will try here in a while and see how it works out and post results....
I tried quite a few different things based on the changes I mentioned above and nothings works.... I think I give up....lol... maybe theres a good reason why tytung doesn't make a separate one for cLK.....maybe it's a ***** to do with his rom for some reason....lol
diesburg said:
I tried quite a few different things based on the changes I mentioned above and nothings works.... I think I give up....lol... maybe theres a good reason why tytung doesn't make a separate one for cLK.....maybe it's a ***** to do with his rom for some reason....lol
Click to expand...
Click to collapse
No technical reason.
It will waste my time to upload two versions for MAGLDR and cLK.
And it will also waste people's time to download two big files if they want to try both bootloaders.
Flashing two zip files is completely not a problem.
The attached is modified META-INF for cLK.
Thanks for sharing the meta inf files... I know it's not a big deal to flash 2 files.... but I got nothing but time on my days off from work... so I figured what the hell, why not make one of my hd'2 favorite roms just a little more convenient to flash.... I loaded it with a few apps on the system partition... at least my favorite apps that work being in system/apps without force closing..... and next im gonna do data/apps in the zip file also... so when I install the zip, it's all already there for me besides account sign-ins.....I know there's CWM for all that restoring apps.... I just like the idea of having a zip with everything I like already in it...lol..and im not worried about magldr as ill never be switching back to it.... unless of course they can get super mario brothers 3 instead of tetris in the bootloader.... lmao... anyways, thanks for the help tytung....
The Team Lambent Corrosion member presents:
UpdatezipCreator
I've found some time to build a new app that can create updates (as zip archive flashable via recovery).
Features:
-Simply to use interface
-Edify & Amend scripts
-Automatic signing
-Signing single ZIPs
-Drag&Drop
I hope that app will work without any bugs
Changelog:
1.0.0.1
-adding update-binary to edify scripts (possibility of choosing own update-binary)
-added default scripts for edify scripts
-settings not stored in my documents
1.0.0.2
-Adding folders
-Drag&Drop
-Signing single zip archive
1.0.0.3
-Fixed bug with the wrong name of edify scripts
1.0.0.4
-Not signed archive is kept in temporary directory
-Functions library (inserting functions)
1.0.0.5
-Problem with update_ont_signed path solved (I hope so)
1.0.0.6
-Log mode
1.0.0.7
-Signing bug fixed
1.0.0.8
-Handling linux newline character in scripts
10/05/2013 - updated links due to many requests (unfortunately, my dropbox accounts was generating to much traffic )
DOWNLOAD:
Rar archive - about 540 kb
Source code - about 1,3 MB - Visual Studio C#
Installer - about 850 kb
Now this'll get success!
I can't wait to get back to my laptop and try it! Thanks OP!
Sent from my Nexus S 4G using xda premium
Awesome
benzyniarz1 said:
The Team Lambent Corrosion member presents:
UpdatezipCreator
I've found some time to build a new app that can create updates (as zip archive flashable via recovery).
Features:
-Edify & Amend scripts
-Signing
I hope that app will work without any bugs
Changelog:
1.0.0.1
-adding update-binary to edify scripts (possibility of choosing own update-binary)
-added default scripts for edify scripts
-settings not stored in my documents
1.0.0.2
-Adding folders
-Drag&Drop
-Signing single zip archive
DOWNLOAD:
Rar archive - about 390 kb
Source code - about 500 kb - Visual Studio C#
Click to expand...
Click to collapse
Dude, this rocks!! Is there any way you can post a update script for HTC thunderbolt? I will def be donating!
I cant seem to get CWR to take any of my zips. I am getting in error "status 4" any ideas?
jgrimberg1979 said:
Dude, this rocks!! Is there any way you can post a update script for HTC thunderbolt? I will def be donating!
Click to expand...
Click to collapse
Thanks, but what do you mean by update-script for the HTC thunderbolt? Scripts built-in are universal (amend) or almost universal (you need only to change mounting point manually). If you don't know how, I can prepare the specify script for your device.
I'm going to use phoneDatabase from amend2edify to prepare the mount points for different devices.
jgrimberg1979 said:
I cant seem to get CWR to take any of my zips. I am getting in error "status 4" any ideas?
Click to expand...
Click to collapse
1. Are you have a full root kernel in the phone?
2. Are you tried to use the both update-scripts? (amend or edify)
3. If you were using edify, did you changed mounting point in script?
I think that CWM scripts should work on the CWR..
If you could make one for me that would be awesome. I tried using both amend and edify.
benzyniarz1 said:
Thanks, but what do you mean by update-script for the HTC thunderbolt? Scripts built-in are universal (amend) or almost universal (you need only to change mounting point manually). If you don't know how, I can prepare the specify script for your device.
I'm going to use phoneDatabase from amend2edify to prepare the mount points for different devices.
1. Are you have a full root kernel in the phone?
2. Are you tried to use the both update-scripts? (amend or edify)
3. If you were using edify, did you changed mounting point in script?
I think that CWM scripts should work on the CWR..
Click to expand...
Click to collapse
Yes I am full root and s-off
Yes I tried using both
I am not sure how to do that
jgrimberg1979 said:
Yes I am full root and s-off
Yes I tried using both
I am not sure how to do that
Click to expand...
Click to collapse
You've tried edify, but didn't change the mounting point, so it couldn't work.. You need to change the line
mount("/dev/block/stl6", "system", "/system", "rw");
Click to expand...
Click to collapse
to:
mount("/dev/block/mmcblk0p25", "system", "/system", "rw");
Click to expand...
Click to collapse
Here is a prepared update-script for your device. Load it in update-script tab page in the app before making update.zip. I hope it will work. Do not forget to check the edify script in options.
So, here are steps:
Add files you want to
Check the edify script and built-in update-binary in the options page
Load prepared file or change "mount" line manually in a update-script page
Create zip archive
You can also try to mount system via (instead of "mount(..."):
run_program("/sbin/busybox", "mount", "-t", "auto", "/dev/block/mmcblk0p25", "/system");
Click to expand...
Click to collapse
It also should work.
Thanks! I will test it out tonight and get back to you.
Sent from my ADR6400L using Tapatalk
benzyniarz1 said:
You've tried edify, but didn't change the mounting point, so it couldn't work.. You need to change the line
to:
Here is a prepared update-script for your device. Load it in update-script tab page in the app before making update.zip. I hope it will work. Do not forget to check the edify script in options.
So, here are steps:
Add files you want to
Check the edify script and built-in update-binary in the options page
Load prepared file or change "mount" line manually in a update-script page
Create zip archive
You can also try to mount system via (instead of "mount(..."):
It also should work.
Click to expand...
Click to collapse
I cant get it to work. I am getting an error status 25. I have tried all the combinations. I have tried the different update binary and updater scripts and i get the same outcome.
update.. It looks like for my phone i need an updater-script rather than update script. Here is a link to the successful zip. I had to open the finished zip(ur program) and delete the update-script and replace it with an updater-script. Is there any way you can adjust it so it will have the right scripts each time so i dont have to manually change anything? That would be awesome. I have been looking for something like this for years. so nice to have simple gui and not have to use update.zip creator and then use amend2edify to make a zip. here is a link http://www.mediafire.com/?29vyc5sojdm946b
Thanks a lot.. it's all my fault. I've not noticed, that amend scripts require "update-script" name and edify scripts "updater-script"...
The new version has been released, please try it now
simply changelog:
1.0.0.3
-Fixed bug with the wrong name of edify scripts
benzyniarz1 said:
Thanks a lot.. it's all my fault. I've not noticed, that amend scripts require "update-script" name and edify scripts "updater-script"...
The new version has been released, please try it now
simply changelog:
1.0.0.3
-Fixed bug with the wrong name of edify scripts
Click to expand...
Click to collapse
It is still not working. I think it may be something with the signing process or something. to get the zips to work i have to take the zipnotsigned in the folder use 7zip and delete the update-binary and delete updater script and replace it work the scripts that i used in the zip that i uploaded for you and then resign it. Once i do that it will flash just fine.
jgrimberg1979 said:
It is still not working. I think it may be something with the signing process or something. to get the zips to work i have to take the zipnotsigned in the folder use 7zip and delete the update-binary and delete updater script and replace it work the scripts that i used in the zip that i uploaded for you and then resign it. Once i do that it will flash just fine.
Click to expand...
Click to collapse
Ok, so.. please try this.. maybe the problem is with mount command.
Step like before:
Add files you want to
Check the edify script and built-in update-binary in the options page
Load prepared file or change "mount" line manually in a update-script page
Create zip archive
benzyniarz1 said:
Ok, so.. please try this.. maybe the problem is with mount command.
Step like before:
Add files you want to
Check the edify script and built-in update-binary in the options page
Load prepared file or change "mount" line manually in a update-script page
Create zip archive
Click to expand...
Click to collapse
That is an update-script, should i just rename it to updater-script?
It still isn't working. It does work if I use the updater-script and update-binary by means of going into the unsigned zip and dropping them in to replace the ones that are in there and then signing the zip. I has got to be something with the way the program is handling the scripts, because i could type the exact same thing in the edit window and it still wont flash. Either that or it is update-binary. Do you want me to upload the scripts? Here is the updater-script that works when i drop it in the zip with 7z.
ui_print("Script generated by amend2edify v1.0.1.2.");
ui_print("Using mount points for Thunderbolt.");
ui_print("***********************************************");
ui_print("Performing Update...");
ui_print("Mounting mount points...");
run_program("/sbin/mount", "/dev/block/mmcblk0p25", "/system");
run_program("/sbin/mount", "/dev/block/mmcblk0p26", "/data");
run_program("/sbin/mount", "/dev/block/mmcblk0p27", "/cache");
package_extract_dir("data", "/data");
ui_print("Unmounting mount points...");
run_program("/sbin/umount", "/system");
run_program("/sbin/umount", "/data");
run_program("/sbin/umount", "/cache");
ui_print("Update Complete.");
jgrimberg1979 said:
That is an update-script, should i just rename it to updater-script?
Click to expand...
Click to collapse
No, you don't have to. App is automatically changing the name (update-script or updater-script) depending on chosen script type in options.
jgrimberg1979 said:
It still isn't working. It does work if I use the updater-script and update-binary by means of going into the unsigned zip and dropping them in to replace the ones that are in there and then signing the zip. I has got to be something with the way the program is handling the scripts, because i could type the exact same thing in the edit window and it still wont flash. Either that or it is update-binary. Do you want me to upload the scripts? Here is the updater-script that works when i drop it in the zip with 7z.
ui_print("Script generated by amend2edify v1.0.1.2.");
ui_print("Using mount points for Thunderbolt.");
ui_print("***********************************************");
ui_print("Performing Update...");
ui_print("Mounting mount points...");
run_program("/sbin/mount", "/dev/block/mmcblk0p25", "/system");
run_program("/sbin/mount", "/dev/block/mmcblk0p26", "/data");
run_program("/sbin/mount", "/dev/block/mmcblk0p27", "/cache");
package_extract_dir("data", "/data");
ui_print("Unmounting mount points...");
run_program("/sbin/umount", "/system");
run_program("/sbin/umount", "/data");
run_program("/sbin/umount", "/cache");
ui_print("Update Complete.");
Click to expand...
Click to collapse
It looks like the update-binary you are using is the same like used in my app, so it can't be the problem.
I have no idea why it's not working if you type these commands in the editor. The output file should be the same as if you put your updater-script with the same commands via 7zip!..
However.. I've got idea - try to type these commands, and choose in options own update-binary that works for you. If it still won't work, please send me output archive.
oo one more thing - how do you sing the archive to get it work? via my app?
This is exactly what I was looking for.
Thanks.
Is there a way to make this work on a Mac?
If not, I can use my gf's laptop.
Thanks for your hard work.
benzyniarz1 said:
No, you don't have to. App is automatically changing the name (update-script or updater-script) depending on chosen script type in options.
It looks like the update-binary you are using is the same like used in my app, so it can't be the problem.
I have no idea why it's not working if you type these commands in the editor. The output file should be the same as if you put your updater-script with the same commands via 7zip!..
However.. I've got idea - try to type these commands, and choose in options own update-binary that works for you. If it still won't work, please send me output archive.
oo one more thing - how do you sing the archive to get it work? via my app?[/QUOT
I used a couple of processes but i used your app for signing after making the script edits with 7zip
Click to expand...
Click to collapse
lozonw said:
This is exactly what I was looking for.
Thanks.
Is there a way to make this work on a Mac?
If not, I can use my gf's laptop.
Thanks for your hard work.
Click to expand...
Click to collapse
Thanks!
I think it's possible..
Just look at http://www.mono-project.com/Main_Page.
You need only to compile sources via Mono on a Mac.
jgrimberg1979 said:
I used a couple of processes but i used your app for signing after making the script edits with 7zip
Click to expand...
Click to collapse
Strange.. so update-binary is not a problem, signing is not a problem too... updater-scripts only stays, but I have no idea why it's not working when you paste a script in editor but when the replace an updater-script with the same script via 7zip it's working...
Maybe it's sth wrong with ICSharpCode.SharpZipLib library? Maybe it is worth trying to use Zip64?
Hi there, I have a N C booting off the SD card with CM7. I installed LCD Changer and evidently made a change using that tool that has now caused my NC CM7 not to boot. Basically, I can power it on, and it starts with the boot process and I see the blue 'android' text on the screen but then nothing happens. I took the SD card out and looked around the files on my Linux system but could not figure out what files I need to change to get it to boot again. Any help would be appreciated.
thx.
hokudog said:
Hi there, I have a N C booting off the SD card with CM7. I installed LCD Changer and evidently made a change using that tool that has now caused my NC CM7 not to boot. Basically, I can power it on, and it starts with the boot process and I see the blue 'android' text on the screen but then nothing happens. I took the SD card out and looked around the files on my Linux system but could not figure out what files I need to change to get it to boot again. Any help would be appreciated.
thx.
Click to expand...
Click to collapse
If you can get to your build.prop file in the /system directory, look for this:
lcd_density= [whatever it's set to]
and change it to:
lcd_density=160
That may not be your only problem, so if it doesn't boot, reflash your ROM.
I was not able to find a build.prop file with the SD card removed (I think its generated dynamically) and since it will not boot I can't get access to it as well.
You can install a fixed build.prop easily by modifying any installer .zip file. The trick is to modify the /META-INF/com/google/android/updater-script in the .zip file. Manualnooter is a great example to learn the structure from. I pared mine down to this:
PHP:
ui_print("Mounting partitions...");
mount("vfat", "/dev/block/mmcblk0p1", "/boot");
mount("ext2", "/dev/block/mmcblk0p5", "/system");
mount("ext3", "/dev/block/mmcblk0p6", "/data");
ui_print("Restoring build.prop to /system...");
package_extract_file("system/build.prop", "/system/build.prop");
ui_print("Chmodding installed apks...");
set_perm(0, 0, 0644, "/system/build.prop");
ui_print("Unmounting Partitions...");
unmount("/boot");
unmount("/system");
unmount("/data");
ui_print("All done!");
ui_print("Please Remove the SDCard, Reboot, Enjoy!");
(The extraneous mount/unmount commands are just there in case I break something else.)
Copy the correct build.prop to system/build.prop in the .zip, boot CWM and install it normally and you should be all set. You can grab a build.prop from the cm .zips. I deleted all the other extraneous .zip contents just to avoid any confusion.
Figuring this out was quicker than rebuilding my NC from scratch, and I've used this technique a couple of times since.
Thanks for the info but sorry if this is a total noob question but what exactly do you mean by "Copy the correct build.prop to system/build.prop in the .zip, boot CWM and install it normally"? While zip file are you referring to? I had hoped to be able to copy/edit a file to the file system of the SD card via my PC and then boot the nook.
I suggested making a copy of one of the manualnooter zip files and modifying it. Copy the file to the corresponding folder in the zip archive.
hokudog said:
Thanks for the info but sorry if this is a total noob question but what exactly do you mean by "Copy the correct build.prop to system/build.prop in the .zip, boot CWM and install it normally"? While zip file are you referring to? I had hoped to be able to copy/edit a file to the file system of the SD card via my PC and then boot the nook.
Click to expand...
Click to collapse
The simplest thing for you to do is remove the sdcard from the NC, put the sdcard in a card reader, copy the the CM7 ROM to the /boot partition, and reflash.
[Guide] How to create your own AIO TWRP flashable update ZIP (AIO=All-in-One)
I didn't see this posted and hopefully there's non or I've just wasted my time in making this.
All credit goes to @inside!out from Team MT. He posted this guide in a Russian language website so this is an interpretation of what I understood to the best of my language skills.
Application of use: Making this file is just for convenience purpose more suited for [email protected] like myself.:cyclops:
Disclaimer: Use an follow this steps at your own risk. I'm not responsible for anything that might happen to your lovely phone. So you better have some skills on what you're doing and how to go around in solving problems.
Knowledge level: Medium
Requirements:
1. A working PC with Note++ and 7-Zip applications installed. These applications are free, just Google them for download links.
2. The update.zip and update_data_full_hw_xx.zip files for your specific Honor 8 model.
Here is @yalokiy 's guide on How to find beta links for update.zip and update_data_full_hw_xx.zip:
https://forum.xda-developers.com/honor-8/how-to/guide-how-to-beta-links-update-zip-t3534004
Step 1:
Create a working folder in your PC and name it whatever you want, e.g. "work place".
Step 2:
Extract the content of each zip file into two separate folders. For example "update" and "update_data".
Step 3:
Rename the UPDATE.APP file from the update.zip to UPDATE0.APP. Then move that file into the update_data folder.
Step 4:
Open the "updater_script" file that is inside the "update_data/META-INF/com/google/android/" folder and open it in a new NOTE++ window.
Once it's opened you'll see something like this:
Code:
ui_print("Verifying current userdata...");
mount("f2fs","EMMC","/dev/block/platform/hi_mci.0/by-name/userdata", "/data");
mountencrypt("/data");
ui_print("Removing unneeded files...");
delete(
" ");
ui_print("Patching userdata files...");
ui_print("Removing empty directorys...");
delete_recursive(
" ");
ui_print("Unpacking data new files...");
delete_recursive("/data/hw_init");
package_extract_dir("data", "/data");
.........................
cut
.........................
ui_print("write radio image ...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
Step 5:
Copy these two lines that are located at the end of the script:
Code:
ui_print("write radio image ...");
assert(update_huawei_pkg_from_ota_zip( "UPDATE.APP"));
and paste the copy just below it, to look like this:
Code:
ui_print("write radio image ...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
ui_print("write radio image...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
Step 6:
Modify the text to look like this and save the changes:
Code:
ui_print("Flashing update0.app...");
assert(update_huawei_pkg_from_ota_zip("UPDATE0.APP"));
ui_print("Update data full hw...");
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
Step 7:
Exit NOTE++ and create a zip file with the content inside the update_data folder (i.e. data, META-INF, UPDATE.APP, and UPDATE0.APP) using the 7-Zip application.
You can later rename the ZIP file to whatever you like. I named my "AIO_TWRP_update_FRD-L14C567B360.zip".
I'll be later adding a download link of my ZIP file for the FRD-L14 once it's uploaded. Done.
Note: If you want to use the content of this guide and rewrite it to your liking be my guest, just remember to give credit to the people involved in creating it.
Great! I'll test this when I've time! Very useful:good:!
Dominikrod said:
[Guide] How to create your own AIO TWRP flashable update ZIP (AIO=All-in-One)
Click to expand...
Click to collapse
Good job, mate!