Hey thanks fuser, thats the trick for XP. With cygwin commandline signing works under xp for me. Now comes the next step, finding a working youtube...

JDfense
I read in this thread that you need to:Hi fuser, i have a questions about repacking boot.img but no luck maybe you can give me direction for me to make unsecure boot.img.
I use unpack and repack.sh from patmoss (lokum rom) and try to remove initgoldfish.rc to keep new initramfs-cpio is less then original but still no luck maybe you can help me, thanks in advanced
Sent from my Aurora-II using Tapatalk
But I'm unsure of exactly how to modify the script and what part of it needs to be deleted. I haven't had any time to experiment with it lately. Let me know if you figure it out before I do.UPDATE: [Problem SOLVED]
So basically remove gzip part from repack.sh script and it works just fine. Just remember that this method doesn't allow bigger ramdisks than original.
Thanks for you're fast reply, now i must read first then try to modify the scriptI read in this thread that you need to:
But I'm unsure of exactly how to modify the script and what part of it needs to be deleted. I haven't had any time to experiment with it lately. Let me know if you figure it out before I do.
You need to use the boot scripts in my developers tools folder. The onda apk tools are also in my developers tools folder. Amlogic devices have a specific magic header so you can't use other unpacking scripts. I guess you could strip the header first but why do the extra step. So they scripts will unpack the .img fine but I don't know how to repack it. Gotta figure out what the whole removing gzip thing is. If anyone know figures out how to repack the boot.img please let me know.Hi fuser-invent,
I make some progress with my rom, but still not ready. Your work helps a lot to learn, how amlogic roms are built.
I found no kitchen for amlogic devices?
I tried to open the boot.img, but no success so fare. Last choice I will try your hint - the onda kitchen. I want to replace the ainol novo... writing and I think, I will find it in the boog.img or is it the logo.img in the stock, which I can't open too. Boot.img seems not to be a gzip file with a header, tried it to open in ubuntu.
The framework-res of the crystal JB is very large with about 12MB, maybe bad for the performance. For my other tablets, I have only about 6MB for the framework-res in JB.
Next thing are the maps.apk. Do we really need 4 versions for different dpi?
I needed some time to study the user-script(1109) difference between stock and yours, but I didn't find the cause for error with the twrp. Since I took your user-script, I had no problems to flash with twrp recovery, but why?Copy and paste is not the real thing, but without understanding it is worse.![]()
![]()
JDfense
Do you have a mediafire account?Thanks fuser-invent. I see you have in some points the same trouble.
I try it again with the boot.img and the 'magic' header. Yes, I have assumed that the bootlogo.rle will be in the boot.img. With the bootanimation I'm done.
I think, we have to careful with the framework-res or we end in a bootloop.
If I find out, how to repack boot.img, I let you know. Does Troy explain something about boot.img? For shure, he will know how to do the trick.![]()
user-script from stock rom allways produces a status 7 errors.
JDfense
I just looked at the META folder, I don't think you can hash stuff out in the updater-script, so just completely delete the first three lines instead of using a #. Also later on when you are labeling the rooting section and a random # after the rooting section, you need to delete those lines or use this instead:Yes, I have a mediafire account. Here is the meta-inf from stock 1109 with rooting and no assert lines. After that I compared it with your user-script, but with any change, I always got the status 7 error. Finally I took your Meta-inf and all work fine with TWRP, but why is that?![]()
http://www.mediafire.com/download.php?l2e6wtyp8burguc
Right now I take a look in that magic unpack script. It seems to be for the recovery, but boot.img has the same format, I assume. In rockship devices recovery.img and boot.img have the same format, too.
Yes framework will not brick my device, but it is one of the most important apks for the rom.
JDfense
ui_print("Rooting");
I haven't even had time to attempt to try and figure it out yet. Maybe sometime next week. I remember back when I first got them I did some google research and didn't find a solution, so I guess it will be down to trial and error.Hi fuser, how about the repack script? The unpack script work fine but still stuck on repack script
Sent from my Aurora-II using Tapatalk HD
Hmm.. the problem may be the windows formatting ... use notepad++I just looked at the META folder, I don't think you can hash stuff out in the updater-script, so just completely delete the first three lines instead of using a #. Also later on when you are labeling the rooting section and a random # after the rooting section, you need to delete those lines or use this instead:
If you use that, you can label your different sections to keep things organized but it will show up in the recovery when it gets to that line and "print" whatever you put in there.Code:ui_print("Rooting");
The unpack scripts work with the boot.img and recovery.img, I've tested them with both.
I have used always notepad++. Thats not the cause.Hmm.. the problem may be the windows formatting ... use notepad++
haven't not tested with TWRP but #comments and empty lines are ok at least in stock updater-script.
That gzip thing is already removed in those unpack/repack scripts of Christian Troy, and those perl versions fix that wrong "Trailer!!!" problem.
(I think I saw similar sh scripts posted by somebody in Troy's TWRP thread...)