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.
Related
I ran everything listed below that I got from another post, but I cannot get android to run when I use the system.sqsh file. I can get it to work from the system.img file but I want to run 1.6 and I cannot find one in the .img format. What am I doing wrong?
Instructions for booting android.
Files to download:
basefiles-xxxx.zip
default.txt
haret.exe
system-xxxx.img or system-xxxx.sqsh
resources.zip
updated zImage-xxxx
updated rootfs-xxxx.img
If you are updating clear the root of your sdcard of any old android related files by moving them to a seperate folder or deleting them. If you are changing system images make sure you rename or backup your old data.img it might not be compatible with new or different builds.
Copy all files to the root of your sdcard.
Extract the basefiles.zip and resources.zip (resources.zip is not needed for donut) to the root of your sdcard.
Rename any updated files to there short names. For example if you downloaded zImage-24-10-09 rename it zImage etc...
Edit your default.txt for your panel type and resolution. There are comments in the file that will guide you.
Correct resolutions for different builds:
Donut/Tattoo: mddi.width=240 mddi.height=320 lcd.density=120
Ion/Cupcake: mddi.width=320 mddi.height=427 lcd.density=160 (this is the most common and can be adjusted)
Hero/Rogers: mddi.width=320 mddi.height=480 lcd.density=160
Rename the system image that you downloaded to system.img or system.sqsh depending on what file extension is already there. For example if you downloaded system-08-08-09.img rename it system.img. If you downloaded system-tmo-ota-drc92.sqsh rename it to system.sqsh.
After everything is setup execute haret.exe and tap run.
Any other questions post them in the correct xda thread for the build you are running.
Which build are you trying? Ion/cupcake should be 240x320 also.
I am using system-tmo-ota-drc92.sqsh, and I get this error when trying. The error I get is Failed to find system.img on SD Card /bin/sh: can't access tty; job control t/ #
tomp8588 said:
I am using system-tmo-ota-drc92.sqsh, and I get this error when trying. The error I get is Failed to find system.img on SD Card /bin/sh: can't access tty; job control t/ #
Click to expand...
Click to collapse
put everything into a folder called android on your sdcard make sure your rename system-tmo-ota-drc92.sqsh to system.sqsh
Thanks it worked great. I have been trying to figure this out for a couple of days.
I had the same problem...thanks jamezelle
If I pull a system dump from any stock phone, can I just replace the system folder in the working folder (from a ROM that I already had) in my Kitchen with the system folder that I pulled from the stock phone, then add root permissions? Will I then have to build another boot.img? Will this even work, or am I barking up the wrong tree?
Hello, I am a developer for the Evo and i was curious how i would install a custom kernel (Netarchy-Toastmod) into my rom (Tha Boss Rom. So far i copied all the files into the appropriate folder but what do i do with the boot image. I tried flashing with the files in place but it did not take. Any advice?
KyleCole90 said:
Hello, I am a developer for the Evo and i was curious how i would install a custom kernel (Netarchy-Toastmod) into my rom (Tha Boss Rom. So far i copied all the files into the appropriate folder but what do i do with the boot image. I tried flashing with the files in place but it did not take. Any advice?
Click to expand...
Click to collapse
You probably should ask this in the EVO Android Development forum. However, since I'm here, I'll do my best.
The boot.img should be at the root of the folder structure.
../NewFolder/system
../NewFolder/META-INF
../NewFolder/boot.img
You then have to zip the CONTENTS of ../NewFolder and sign the resulting zip with something like EasySign (http://android.grdlock.net/index.php?&direction=0&order=&directory=Extras).
Or you can just load the original ROM into dsixda's kitchen in the original_update folder (http://forum.xda-developers.com/showthread.php?t=633246), select '1' to create a work folder, copy the files into the correct locations, and then select '99' to zip and sign the ROM. It will then be in the OUTPUT_ZIP folder. The kitchen walks you through these steps really well, if you read the prompts.
Then flash the ROM.
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.
Hey guys,
I just started the long journey of android rom development/cooking using an app called Android Kitchen, and I'm looking for some help from the more experienced. I extracted a custom rom folders (for personal use), and started to edit some of the extracted files (replacing and deleting), but I'm quite lost when it comes to merging flashable .zip folders (like lockscreens and mods) with the extracted rom file.Should I copy and paste whats inside the flashable zip into the rom file? Or should I use note editor to copy what's inside the mod file itself, copy the text, and add it to the original one? I really want to add these mods through this app rather than recovery mode. And can I emulate edited roms on my computer rather than risking my phone?
Thnx...