Dear XDA,
Can anyone fix this zip file I made. It is for the required WiFi drivers in the patch.
New link:https://mega.co.nz/#!h8UmkArY!KYOutdsQE5ngoTHd7V72C8mwT9qOSOmKU9RqmGc0osg
Your regards,
AlpyzDX
Perhaps you could go into some more detail, such as what the patch is supposed to do, and also what problems you're having.
Off the top, your entire directory structure is messed up. You have one main directory, patch, and beneath that two subdirectories named "META-INF" and "install". META-INF must be in the root of the zip. The "install" directory also must be in the root of the zip, and needs to be renamed to "system" since the files you're trying to copy to the device reside in a folder in /system. Taking a cursory look at your updater-script there seems to be nothing out of the ordinary there.
Related
Hi I downloaded this android peeing on Apple logo bootscreen, it installed well so I got too excited and wanted to put tux hammering the Windows logo before android pee on the Apple, I made all 70 png's but did not touch anything either than creating the images. I then zipped them according to the original names but when I flash it I get ..... E: wrong digest, system/media/bootanimation.zip
I have tried several times but no luck, yet the original one would easy install. Help guys
Sent from my HTC Hero VillainRom 12, flykernel11 using XDA App
any idea someone
You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did
kyouko said:
You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did
Click to expand...
Click to collapse
Too bad everyone doesn't do that.
I have decided to change the part1 folder images with custom ones, I will upload the whole zip later so when you help me I won't have to re edit it again, thanx for your replies
Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside "google" create a folder named "android" <- forgot about this step
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip
thanks mate I will download it today, thanks for the tutorial man its highly appreciative, thanks a lot
kyouko said:
Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip
Click to expand...
Click to collapse
I got an error when flashing the signed zip I got no update file found
elliotn said:
I got an error when flashing the signed zip I got no update file found
Click to expand...
Click to collapse
LOL uhh, I'll take a look at it and test it out... and edit my previous post with w/e I did wrong
Forgot to add the ''android'' folder in the zip. Fixed and should work now
I am trying to take a keyboard that somebody made into a flashable .zip file, and implement it into a rom that I am working on. What I did was flash the .zip through cwm, then found the apk, backed it up, and then placed it in the /system/app folder on the new rom. The problem is as soon as the rom boots, I get a force close error. So I took a look at the .zip file, there are two folders meta-inf and system. inside system there is an app folder and lib folder. My question is can I just take the apk and lib file out and place them directly into /system/app and system/lib on the new rom? and if so do i need to do anything with the META-INF folder? any ideas would be GREATLY appreciated!!!
thanks
the META-INF folder may have some script that does some other manipulation of the filesystem or runs helper apps during installation. See what's in META-INF/com/google/android/update-script.
in http://forum.xda-developers.com/showthread.php?t=1058809
It says: "Download, unzip to your rom folder, restart twice.."
Is this just for that ROM or will it work for all?
What exactly do I do?
After unzipping, there are several levels of folders. which level goes where and does "rom folder" mean "Android" folder?
Download, unzip, copy "root" & "update" & "zImage" to your Android folder, reboot twice, have fun !
ROM folder = "Android" (or whatever your ROM's folder is called)
Just copy the folders and the file to the top level of your folder .
And a Kernel (technically) should work with all ROMs.
Your sd card should look like this:
G:/SDCARD/Android/root/
G:/SDCARD/Android/update/
G:/SDCARD/Android/zImage
Well it depends on your build, what build are you using?
because some builds have different path than Android, and others don't support putting new files in the folder build as far as I can remember.
so some require you to put these files manually using ADB push commands, or root explorer and apps of the like.
Not all builds support different kernels, so make sure you check if the kernel you want is compatible with the build you have.
and make a backup before you do anything or you might regret it.
manual kernel installation means:
copying the zImage to the build folder to replace the original, run android then push/copy-paste kernel files each to it's respective folder on the device. it's not that hard to be done.
These are the steps explaining you how to create a custom firmware based on the SmartQ firmware releases.
Warning : Creating a firmware and changing the files may cause your device to stop working, I won't be held responsible for any damage caused by this.
Creating a firmware file is actually very easy, not much is involved and nothing more than some basic software is required to create the files. If you don't understand the steps below than maybe you shouldn't fiddle around with this and wait for other members to create these.
There is nothing explained here about the flashing itself, as I will create a seperate How-To about that with pictures explaining the steps of the recovery.
Also there is nothing explained about kernel building itself, I have no clue how to do that and I'll leave that up to SmartQ.
Use the instructions below to make your own Firmware file with the software you want in it and make all configuration changes you want.
1. If you haven't already download the latest official firmware from SmartQ.
2. Extract the zip file. You then have 2 files, a Chinese .txt file with the release notes. And a file called "SmartQT15".
3. Rename the file "SmartQT15" to "SmartQT15.zip". Accept any warning about making the file useless, as in fact you are making it useful.
4. Extract the zip file. Then you end up with 4 new folders :
"boot" - This will be the files required for booting the OS. And possibly the recovery.
"data" - The user apps and data are in this folder.
"META-INF" - The certificate SmartQ used is in this folder and also the update script that manages the update process.
"system" - The actual Android OS.Stay clear of the boot folder, unless you are 100% sure about what you are doing, this may cause a bricked device without the possibility to reflash.
Add apps to the app subfolder in the data folder. Make sure if you do add apps to set the permissions in the update script file and make changes accordingly. The data-extra.tar file is extracted during the update process.
In the "META-INF\com\google\android" folder you can find the updater-script file, you can edit this with Notepad++. This file tells the CWM based recovery what to do and in this file the permissions are set for apps. Also is it required to edit this if you want to create a pre-rooted firmware.
Be carefull what to change in the system folder it can cause your OS not to boot, but it should be no problem to revert back to another build that did work previously as you didn't touch the boot folder and the recovery should work normally.
Once you have made all the changes you wanted to do. You follow the steps back.
5. zip the 4 folders backup using Winzip or WinRAR, whatever suits you best (You can use compression, I tried out Fast, Normal, Good compression in WinRAR and the firmware flashed without problems). Make sure you have the 4 folders in the "root" of your zip file. Use for filename "SmartQT15.zip"
6. Rename the "SmartQT15.zip" file to "SmartQT15" and accept any warning again about changing the extension of your file.
You have now created a flashable firmware file for the SmartQ Ten3 T15.
Copy his file to the root of an empty microSD card and follow my How-To about flashing Custom Firmwares.
Don't use the guide to flash original SmartQ firmwares as this won't work, by changing the firmware package you break the firmware signature and the recovery will check for this during flashing.
Signature checking can be disabled though in the recovery as I will explain in the new How-To.
If you have any questions feel free to post below and I'll do my best to answer them, all the above is based on my experience and from what I could find out on the Internet.
I don't know the first thing about Android development, especially making flashable zips, but what I DO know is that I was just able to update my profile and prl on my n5 running the January 9th nighty of cm12. Here's how I did it:
1 extract the zip I'm adding here to your internal storage.
2 copy the extracted folder to your system/app/ folder. As a folder, not just the apk.
3 go through the subfolders until you get to the lib folder, then copy the two files inside to system/lib/
4 set the proper permission for all the files and folders involved.
Now let me be clear, I know this is overly complicated, my hope is that someone can respond to this this thread and post a flashable zip that would make this much much easier. Also I don't know if this will work with any other rom, just the one I have right now.
bray424 said:
I don't know the first thing about Android development, especially making flashable zips, but what I DO know is that I was just able to update my profile and prl on my n5 running the January 9th nighty of cm12. Here's how I did it:
1 extract the zip I'm adding here to your internal storage.
2 copy the extracted folder to your system/app/ folder. As a folder, not just the apk.
3 go through the subfolders until you get to the lib folder, then copy the two files inside to system/lib/
4 set the proper permission for all the files and folders involved.
Now let me be clear, I know this is overly complicated, my hope is that someone can respond to this this thread and post a flashable zip that would make this much much easier. Also I don't know if this will work with any other rom, just the one I have right now.
Click to expand...
Click to collapse
Pretty sure there was already a few "Sprint fix" zips around lol.
Well now I feel dumb. But happy too because either way I won't have to worry about it anymore.
Sent from my Nexus 5 using XDA Free mobile app