We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for extra (extra thanks..)
(may U?)
does this work on hboot 1.14?
byliu88 said:
does this work on hboot 1.14?
Click to expand...
Click to collapse
double that?
Will this remove the HTC red warning at the very bottom??
Sent from my HTC One S using Tapatalk 2
Elloco305 said:
Will this remove the HTC red warning at the very bottom??
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Nothing removes that except SOFF.
Sent from my HTC One S running ViperOneS!
invasion2 said:
Nothing removes that except SOFF.
Sent from my HTC One S running ViperOneS!
Click to expand...
Click to collapse
Don't scream at me Bro!
I figured that much though just thought I'd ask. Lol
Sent from my HTC One S using Tapatalk 2
Hmm think I might try this tomorrow to see if it works on 1.14.
---------- Post added at 03:07 AM ---------- Previous post was at 02:38 AM ----------
Changed my mind lol but unpacking the boot.img is not working.
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
Darn... no luck for hboot 1.14 I see. Updating was such a bad decision.
byliu88 said:
Darn... no luck for hboot 1.14 I see. Updating was such a bad decision.
Click to expand...
Click to collapse
nelikp is have a go doing it because he says the image I did didn't convert right.
I have a Nandroid of the axiom build (an awesome sense ROM popular here a few months ago before the devs fell under the SG3 spell) which I had been using on my phone until about a week ago, and for whatever reason this ROM, which has custom boot animation, has a splash screen without the red overlay text. I don't know why.. But if anyone wants to look at it, let me know. Because a pristine splash screen without S-Off is possible. I would think you could look at the partitions for the splash and maybe figure out if there is something different.
Just thought I would offer. I am trying to get up to speed on building ROMs, but am not quite there yet, otherwise I would examine it.
Sent from my HTC One S using xda premium
syntropic said:
I have a Nandroid of the axiom build (an awesome sense ROM popular here a few months ago before the devs fell under the SG3 spell) which I had been using on my phone until about a week ago, and for whatever reason this ROM, which has custom boot animation, has a splash screen without the red overlay text. I don't know why.. But if anyone wants to look at it, let me know. Because a pristine splash screen without S-Off is possible. I would think you could look at the partitions for the splash and maybe figure out if there is something different.
Just thought I would offer. I am trying to get up to speed on building ROMs, but am not quite there yet, otherwise I would examine it.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
As far as I know we can't flash those partitions without the need of S-OFF or using adb to push those partitions manually.
So it should be not possible flashing those from recovery, same reason we can't flash the kernel in it.
Gesendet von meinem HTC One S
v3n3 said:
As far as I know we can't flash those partitions without the need of S-OFF or using adb to push those partitions manually.
So it should be not possible flashing those from recovery, same reason we can't flash the kernel in it.
Gesendet von meinem HTC One S
Click to expand...
Click to collapse
There is another way here but need to be 1.09 lower Hboot for it to work. I think this boot.img mod just dont work for us and nelikp never got back to me.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
How did you fixed that error?
alexeius said:
How did you fixed that error?
Click to expand...
Click to collapse
When you install Cygwin you be asked if you like to install plug-ins or something like that, when it does that search for cpio and select to install all and do the same for perl.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
I had the same problems. I followed your guide step by step and encountered boot loop without the change. Im on Hboot 1.09.0000. I realy wanted to get this image as my kernel logo -=*( woah is me...
essentialmindz said:
I had the same problems. I followed your guide step by step and encountered boot loop without the change. Im on Hboot 1.09.0000. I realy wanted to get this image as my kernel logo -=*( woah is me...
Click to expand...
Click to collapse
I got same thing so give up. Boot you in luck with that Hboot you can use this thread here to do what you want to.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You are looking for a special modded Clockworkmod recovery?
Clockworkmod Recovery v4.0.0.5
removed downloadlinks cause of issues with the new unity kernel.
please use this very special recovery
Just have a look on this site: 4EXTRecovery v1.1.1 | STAY @EXT4 | Convert EXT4 without losing data | Advanced Backup
Clockworkmod Recovery v3.2.0.0
downloadlink:
PG88IMG-RECOVERYIMG-3.2.0.0.zip
Clockworkmod Recovery v3.1.0.1
downloadlink:
PG88IMG-RECOVERYIMG-3.1.0.1.zip
or visit my blog dev page: lbc mod android development - custom recovery
Install Instructions:
download the zip package
rename it to PG88IMG.zip
put that file on the root of your sd card
start you phone in bootloader (hboot not fastboot)
the bootloader will ask you if you want to install recovery.img
confrim
reboot
rename the file again into something else (cause bootloader will always try to flash if a PG88IMG.zip file is on your sd card
loveboatcaptain said:
Hey Guys,
just have the first booting version of ClockworkMod Recovery v.3.0.2.4 on my phone.
View attachment 575564
a full working beta will come in the next days.
Install instructions will follow, too.
CREDITS: this is basicly the work of HCDR.Jacob how helped my to build this, cause my macbook sucked at building from source. so give him a big tanks too ;-)
see you later with a download for everyone with s-off
regards
Click to expand...
Click to collapse
woohoo
you are great
Ah mr mac user succeeded gratz
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
Ah mr mac user succeeded gratz
Click to expand...
Click to collapse
Yeah, with a little help from my friends ;-)
Jacob is fixing the last bugs and than i think were done and can do some tests before release.
regards
Maybe ours work for you to, koush made ours public today. Ill give u the info tomorrow, should be all the same
Sent from my HTC Incredible S using XDA Premium App
the beta tests have finished...
we talked to koush and he put it into ROM MANAGER just in this minute...
so happy flashing for all with s-off and root.
regards
p.s. don´t forget to thank HCDR.Jacob. He build it together and fixed the bugs and of course koush for pushing it so quick to ROM MANAGER.
thx to this great community
loveboatcaptain said:
Hey Guys,
[ROMmanager]
regards
Click to expand...
Click to collapse
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
dont know said:
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
Click to expand...
Click to collapse
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
loveboatcaptain said:
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
Click to expand...
Click to collapse
It's a very light desense I want (only get rid of the ad-ware inkluded and some others like twitter..)
I'm on ADW because of the cool themes available.
THANKS for the possibility of real rooting (unsecure and clockwork) again..
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
M0ng0 said:
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
Click to expand...
Click to collapse
Hey, today i unlocked mine with an xtc clip.
Then I flashed the unsecured Boot Image. I hope it is called so .
After that worked successful, i rooted it with SuperOneKlick.
Maybe this works for you too.
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
MarylandCookie said:
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
Click to expand...
Click to collapse
hey dude,
i ported the recovery together with a friend. so i´m your man ;-)
i never noticed that there is a problem with formating cache partition, cause i don´t touch it with my updater-script.
so first question:
why you will add that to your updater-script? me for myself prefere the way of wiping my phone manually. and that works very well with CMR. i also tested it in the mount/partition menu.
i would not like it, when a script wipes stuff and i did not know about.
i only use format for system in my full update.zip´s. in updates for my rom i did not wipe anything.
second question: did you know that cache partition is always mounted when recovery starts? perhaps thats the problem.
regards
mih_ said:
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
Click to expand...
Click to collapse
those fastboot commands only works with an ENG S-Off bootloader. which we dont have. we have SHIP S-Off... there are differences between those both.
our bootloader can everything the ENG can with fastboot commands. we have to use a zip file to flash things like recovery or splash.
you have to add your recovery backup img into my PG88IMG-unsecured_bootimg.zip file from this post [BOOT] Root for S-Off with unsecured Boot Image rename it to PG88IMG.zip and add your recovery.img into that zip file and remove the boot.img file.
than put the file on the root of your sdcard and reboot into bootloader.
the file will be flashed automaticly.
after reboot your phone, rename the file again to something else, cause every time you are in bootloader and this file is named PG88IMG.zip on your sdcard thhe bootloader will try to flash it.
just a little tipp at the end: you can add every img file into this zip. system and data img files from nandroid backups are working too ;-)
regards
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
mih_ said:
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
Click to expand...
Click to collapse
Could you PLEASE give me a short (or long ) description how to install the ota?
No idea what to do with the linked code...
EDIT Extracted the boot.img from ota and copoed it to PG88IMG.zip - restart - run ota-update -> fail
EDIT2 I'm an idiot: instead of boot.img it is a great idea to try it with recovery.img *LOL*
You just have to replace clockworkmod ecovery with stock one.
I've taken it from OTA downloaded.
It contains file firmware.zip inside, which contains recovery.img as well.
You can flash it with tool flash_image (http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/vision_utilities/flash_image.zip)
Just put it somewhere to device, where you can run it (for instance/data/local/bin/, /system/bin/ if remounted to rw, /sdcard if remounted to exec)
and run from device or adb shell like%
su
flash_image recovery /sdcard/recovery.img
after that, you can reboot to hboot, check out that you do not have cwm recovery anymore, boot to android and install OTA as usual from menu...
does the recovery also do a backup of the radio?
(my wifi is broken sinve ota update - and I'm an stock recovery now, so can't test at the moment)
Cache being mounted or unmounted isnt the issue.
I can wipe cache manually but automatting it in the script seems the break the whole process.
Its good for testing and having a fresh install.
Lets android re-build everything.
Take from Clockworks How to:
wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
How to mod a stock kernel Tutorial (with Windows)
by: broodplank1337
In this tutorial I will explain how to unsecure a kernel and how to add init.d / custom bootanimation support to a stock kernel, in this tutorial we will be using Cygwin as shell, with Dsixda's Android Kitchen.
Requirements:
- Cygwin with Packages and Dsixda's Android Kitchen
- JRE or JDK
- Winrar
- A stock Kernel
- Some common sense
Chapters:
1. Getting the kernel
2. Setting up Cygwin
3. Setting up the Kitchen
4. Modifying the Kernel
5. Testing results
Chapter 1. Getting the Kernel
Since the kernel that you are going to use is a stock kernel, it can be found within the latest stock firmware. for example for the i9001, I have this Odin flashable: "I9001XXKQE_I9001ATOKP3_I9001XXKPL_HOME.tar.md5". Open this file with Winrar and you will see the boot.img in there, just extract it and your currently done. It may also be a zImage!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Chapter 2. Setting up Cygwin
The Cygwin package you downloaded needs to be extracted, the default folder of a Cygwin installation is: "C:\cygwin". This is recommended in most cases. Once unpacked navigate to the "home" folder. In this home folder you need to create a folder that has the same username as your current windows username. Once you made that folder you have to extract the contents of "kitchen.rar" to that folder. So you will get a folder structure like this: C:\cygwin\home\username\kitchen
Chapter 3. Setting up Kitchen
Go to the original_update folder (located in: C:\cygwin\home\username\kitchen) and open dummyrom.zip with Winrar, now move your own boot.img inside the zip and choose "Store" as compression, Press ok to update the archive. If you have an zImage instead, please remove the boot.img from the archive first. Now browse to the system folder inside the archive and replace the build.prop with a build.prop from your phone. Also choose "Store" as compression and update the archive.
Starting the Kitchen:
1. Open Cygwin (X:\Cygwin\Cygwin.bat)
2. Once loaded, enter: "cd kitchen" > Enter
3. now type "sh menu" The kitchen menu will now start...
Setting up a working folder:
1. Press 1 > Enter
2. Press Enter and wait...
3. Choose (1) dummyrom.zip > Enter
4. Choose "y" > Enter > Enter a new name (I chose WORKING_KERNEL) > Enter
(now wait until the zip is extracted)
5. Choose 2 > Enter
6. Enter to return to main menu
Chapter 4. Modifying the Kernel
Unsecuring the kernel (to use properly with ADB)
1. Press 2 > Enter (to add root permissions)
2. Press "s" > Enter (now wait until the process is done)
3. Press Enter to return to main menu
Adding init.d support (for using startup scripts in /system/etc/init.d)
1. Press 0 > Enter
2. Press 17 > Enter (to add init.d support)
3. Enter "y" > Enter (now wait until the process is done)
4. Press Enter to return to main menu
Adding custom bootanimation support
Since the bootanimation support is already inside the dummyrom.zip file, you don't need to add it again.
Chapter 5. Testing the results
Now you will find a working boot.img / zImage under: C:\cygwin\home\username\kitchen\WORKING_KERNEL\
You can copy this file directly to your phone but it won't have bootanimation support.
That's why you need to enter in the Kitchen menu:
1. Press 99 > Enter
2. Press 1 > Enter
3. Press "n" > Enter
4. Press "y" > Enter
5. Press "y" > Enter > "EnterANewZipName" > Enter
6. Now your cwm zip will be located at: C:\cygwin\home\username\kitchen\OUTPUT_ZIP
The zip that can be found in the directory above can be flashable in CWM. Ejoy your own stock kernel with init.d/bootanimation support!
Great tutorial! Btw, this works also with cm9 kernels?
Sent from my GT-I9001 using xda premium
Third post reserved for further use.
Just joking.You should make a tutorial to teach.us how to make an overclocked kernel and so on.
Btw nice tutorial from a great dev.
RyanJWZ said:
Great tutorial! Btw, this works also with cm9 kernels?
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Thank you
And honestly I have no idea if it's working on CM9 kernels, I think it does work actually, you should give it a try
Costinutz32 said:
Third post reserved for further use.
Just joking.You should make a tutorial to teach.us how to make an overclocked kernel and so on.
Btw nice tutorial from a great dev.
Click to expand...
Click to collapse
lol hehe, I wish I knew how to do that, If I knew that I would have posted a tutorial for sure . I'm totally inexperienced with coding kernels unfortunately
and thanks btw ^^
edit: added screenshots
how to check init.d work?
kingsonwongs said:
how to check init.d work?
Click to expand...
Click to collapse
for example:
/system/etc/init.d/00test
Code:
#!/system/bin/sh
su -c "echo "pass" > /sdcard/pass"
If a file called "pass" will appear on your sdcard it's working
this is more a tutorial for how to make a rom flashable for cwm with kitchen
bootanimation with kitchen is not working for me, had to modify the init.rc manually in boot.img. but you can use the kitchen for extract the boot.img.
however, the headline of this thread is a bit confusing, the tutorial is ok.
i guess, it is not complete.
for set up working folder, you will need
system.ext4.tar
cache.ext4.tar
boot.img
from a nandroid backup of your rom
texten said:
this is more a tutorial for how to make a rom flashable for cwm with kitchen
bootanimation with kitchen is not working for me, had to modify the init.rc manually in boot.img. but you can use the kitchen for extract the boot.img.
however, the headline of this thread is a bit confusing, the tutorial is ok.
i guess, it is not complete.
for set up working folder, you will need
system.ext4.tar
cache.ext4.tar
boot.img
from a nandroid backup of your rom
Click to expand...
Click to collapse
Well actually, I've kept the dummyrom.zip so minimalistic that boot.img is fully compatible with the kitchen (it needed app/bin folder and build.prop), but all other things are basically removed.
And you don't need all those files, we are not trying to create a working rom here, and the bootanimation is idd not working correctly, that's why I added the AOSP bootanimation library to the dummyrom.zip
broodplank1337 said:
Well actually, I've kept the dummyrom.zip so minimalistic that boot.img is fully compatible with the kitchen (it needed app/bin folder and build.prop), but all other things are basically removed.
And you don't need all those files, we are not trying to create a working rom here, and the bootanimation is idd not working correctly, that's why I added the AOSP bootanimation library to the dummyrom.zip
Click to expand...
Click to collapse
ah, ok i didn't know about the dummyrom.zip
but only for extract boot.img and make the small changesfor init.d and bootanimation, you can use other methods, not the kitchen.
the setup for kitchen is much more work as needed for this.
you can also use the tool "disk internals linux reader" and change everything you want manually.
just my 2 cents.
maybe with alle that what you have done for this tutorial, you can change/expand it to "how to make a rom with kitchen"...
well whatever. do it as you want. good luck.
texten said:
ah, ok i didn't know about the dummyrom.zip
but only for extract boot.img and make the small changesfor init.d and bootanimation, you can use other methods, not the kitchen.
the setup for kitchen is much more work as needed for this.
you can also use the tool "disk internals linux reader" and change everything you want manually.
just my 2 cents.
maybe with alle that what you have done for this tutorial, you can change/expand it to "how to make a rom with kitchen"...
well whatever. do it as you want. good luck.
Click to expand...
Click to collapse
about that, you're right, it can be done allot easier, but the thing is, I never got any working kernel when I manually packed them (or with some scripts), so I'm very thankful to the kitchen, which allows me to make an actual working boot.img
Hey brood i tried this tutorial with my stock XXKG3 kernel and did it step by step
Then i flashed the output.zip and added the folder init.d in system/etc/ and the pass script you posted above but there isnt any pass file on my sdcard ):
what went wrong?
//edit: tried pushing a bootanimation (sanim.zip) to /system/media/ but after the reboot it shows the old galaxy s plus bootanimation );
EternalFame said:
Hey brood i tried this tutorial with my stock XXKG3 kernel and did it step by step
Then i flashed the output.zip and added the folder init.d in system/etc/ and the pass script you posted above but there isnt any pass file on my sdcard ):
what went wrong?
//edit: tried pushing a bootanimation (sanim.zip) to /system/media/ but after the reboot it shows the old galaxy s plus bootanimation );
Click to expand...
Click to collapse
hmm the init.d part should work. try it without "su -c" this time
the name of the bootanimation has to be "bootanimation.zip" instead of "sanim.zip"
broodplank1337 said:
hmm the init.d part should work. try it without "su -c" this time
the name of the bootanimation has to be "bootanimation.zip" instead of "sanim.zip"
Click to expand...
Click to collapse
also doesnt work without su -c and renamed to bootanimation.zip but theres still stock bootanim ):
isnt this tut working with 2.3.3 kernel?
BTW: here is my kernel:
www.hengelmueller.bplaced.net/OUTPUT_ZIP.zip
Sent from my GT-I9001 using XDA
EternalFame said:
also doesnt work without su -c and renamed to bootanimation.zip but theres still stock bootanim ):
isnt this tut working with 2.3.3 kernel?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
Hmm then I don't know atm what the problem, but about the bootanimation, did you build a zip from the working folder? Or did you just copy boot.img? Since it needs the bootanimation library which is included in dummyrom.zip
broodplank1337 said:
Hmm then I don't know atm what the problem, but about the bootanimation, did you build a zip from the working folder? Or did you just copy boot.img? Since it needs the bootanimation library which is included in dummyrom.zip
Click to expand...
Click to collapse
i have the bootanimation file in system/bin so that shouldnt be the problem ):
could you pls try with my kernel from the link i posted above?
it drives me nuts that i am not able to do such "easy" things ): ^^
btw: do i need something in init.rc or something which tells the system when it should execute the scripts?
Sent from my GT-I9001 using XDA
Search in the init.rc for system/bin/samsungani and replace it with system/bin/bootanimation.
This should work I guess. AT least this is what i did with my Stock Kernels.
Sent from my GT-I9001 using XDA
Does not work either ):
could you pls try with my kernel above?
Sent from my GT-I9001 using XDA
Tried also with skyhigh and feacore and init.d also doesnt work
could it be that they dont work with 2.3.3 ?
Sent from my GT-I9001 using XDA
EternalFame said:
Tried also with skyhigh and feacore and init.d also doesnt work
could it be that they dont work with 2.3.3 ?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
does your init.d folder and the scripts inside have the right permissions?
broodplank1337 said:
does your init.d folder and the scripts inside have the right permissions?
Click to expand...
Click to collapse
Which permissions do i need?
Sent from my GT-I9001 using XDA
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: HTC One S, EVO 4G LTE, EVO 3D CDMA and GSM, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Nexus 7, Samsung Google Galaxy Nexus (GSM & CDMA), Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Credits for HTC One S Testing:
Special Thanks to: Smokem_I
Tecardo, orenfl and mteezy
Confirmed Compatible Hboot Versions:
1.06, 1.09, 1.13, 1.14 (US and EU), and 2.15 (thx DisruptiveMind)
Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into kernel /sbin, etc).
Custom Recovery
Supports both CWM and TWRP!
Future Support:
Will continue to test kernels as they are released to ensure compatibility!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using Official HTC method
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
2) Download kernel zip file to /sdcard.
3) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
3) Flash Image GUI will validate the kernel zip file is contains the minimum required files
4) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
5) Reboot
Basic Troubleshooting:
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Glad to see you post it for everyone to try. Always loved this apk.
Just to show working on one s
Sent from my HTC One S using Tapatalk 2
Thanks mate looks like a handy tool. Salt I had no time to help test this, would have loved to. seems you have gotten it to work decently now. Very good. Thanks a lot!
sent from a bugged One s....
Awesome bro! It's great to finally be able to flash a rom on the go without the need of fastboot! Flashed several roms with this so far and haven't had any issues. We were in desperate need of something like this! Thanks for taking the time to add support for our device!
Sent from my BluMagic Viper One S using Tapatalk 2
Can't say thank you enough! Works like a dream, hell you even put a smile on my miserable old face
So once we know that the ketnal is supported by a Rom we can just flash away once its unlocked and rioted obviously
New favourite app lol good job on this.
snwman said:
So once we know that the ketnal is supported by a Rom we can just flash away once its unlocked and rioted obviously
Click to expand...
Click to collapse
It supports all roms available for the One S. The Viper Beta Team tested it extensively before release. We didn't encounter any issues or roms that weren't compatible. Also don't forget to hit joeykrim's thanks button or better yet show him support by buying from the Play Store
Darknites said:
New favourite app lol good job on this.
Click to expand...
Click to collapse
Soon to be everyone's favorite app once they find it! This is the must have app for the One S.
Sent from my BluMagic Viper One S using Tapatalk 2
Smokem_I said:
It supports all roms available for the One S. The Viper Beta Team tested it extensively before release. We didn't encounter any issues or roms that weren't compatible. Also don't forget to hit joeykrim's thanks button or better yet show him support by buying from the Play Store
Soon to be everyone's favorite app once they find it! This is the must have app for the One S.
Sent from my BluMagic Viper One S using Tapatalk 2
Click to expand...
Click to collapse
I think if it states on the title 'for ALL hboot versions' or something similar it may help attract people. I can't understand how this is staying so quiet! I've been flashing boot.img using this app from stock roms to asop and different recovery version like there was no tomorrow. Its just all so easy off to buy the market version now to show the dev some love.
This won't stay quiet for long. Once more users realize they don't have to use fast boot to flash kernels or use a workaround like htc dumlock which takes alot more work. They will all be using this. Its a must have app for any device that does not have s-off this app was a lifesaver for me on my evo 3d. Even once it got s-off I still used regularly to flash kernels on the fly. I have low hboot but still been using this for the past couple weeks since we started testing. All I have to say for those that don't know is NO MORE FASTBOOT!
Sent from my HTC One S using Tapatalk 2
If you have any feature suggestions, please let me know! Appreciate all the positive support!
shadowch31 said:
I think if it states on the title 'for ALL hboot versions' or something similar it may help attract people. I can't understand how this is staying so quiet! I've been flashing boot.img using this app from stock roms to asop and different recovery version like there was no tomorrow. Its just all so easy off to buy the market version now to show the dev some love.
Click to expand...
Click to collapse
Good comments. I listed in the OP and copied below for convenience, which hboot versions were confirmed. If I'm missing any hboot versions, please let me know.
Confirmed Compatible Hboot Versions:
joeykrim said:
1.06, 1.09, 1.13, 1.14 (US and EU)
Click to expand...
Click to collapse
This is directed to anybody/everybody, in regards to methods that can spread the news, it might be worthwhile to write up a simple guide post explaining the steps, very similar to what I have in the OP.
Another method would be to reach out to the ROM/kernel developers and ask them to link back to this thread, or a guide thread, on the various methods to load their software including using this application as one of the methods.
Just throwing out ideas! Appreciate all the help and support!
snwman said:
So once we know that the ketnal is supported by a Rom we can just flash away once its unlocked and rioted obviously
Click to expand...
Click to collapse
If you refer to the last section of the OP with the guides, they explain step-by-step process that answer your question. I've pasted below for your convenience. Thanks for the support!
joeykrim said:
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using Official HTC method
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
2) Download kernel zip file to /sdcard.
3) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
3) Flash Image GUI will validate the kernel zip file is contains the minimum required files
4) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
5) Reboot
Click to expand...
Click to collapse
Get the rom devs to put the info in there threads should help out a bit.
Edit, dam it didnt see there was a 2nd page seem you have that idea already.
Hi there , let me understand if for example i want to change the rom ? Right now i am on aokp , if i download the kernel from viper 1.2.0 and flash it and then after reboot i will remain on twrp and flash his 1.2.0 rom will WORK?
I kind of tired of using computer to change roms and kernels etc ...
Ps : i wanted to sell my phone becouse of this (i really mis my old sgs/sgs2 method to flash roms/radios/kernels)
Good work
Sent from my HTC One S using Tapatalk 2
scufutz said:
Hi there , let me understand if for example i want to change the rom ? Right now i am on aokp , if i download the kernel from viper 1.2.0 and flash it and then after reboot i will remain on twrp and flash his 1.2.0 rom will WORK?
I kind of tired of using computer to change roms and kernels etc ...
Ps : i wanted to sell my phone becouse of this (i really mis my old sgs/sgs2 method to flash roms/radios/kernels)
Good work
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Even easier than that.
Simply download the rom and direct the program to it on your sdcard it will then extract the boot.img and any other files it may need such as wlan.ko - flash the kernel and an option to boot normally or boot to recovery is offered, boot to recovery and flash the rom and hey presto. Who needs s-off when we have this method!
Yes I know S-Off would be nice for other things but for now this is by far the lesser of two evils.
I was thinking is it possible to have it just point to the boot.img file so that i can still delete it from the rom zip to speed up install of the rom? Which takes over 5 mins if it has it.
Darknites said:
I was thinking is it possible to have it just point to the boot.img file so that i can still delete it from the rom zip to speed up install of the rom? Which takes over 5 mins if it has it.
Click to expand...
Click to collapse
Well it does that? Maybe I'm not understanding but you select the rom and it extracts the needed files and flashes them, then simply remove the boot.img from the zip and flash it to see if it works. Never tried flashing a rom without the boot.img so cannot say.
IMO removing the boot image isn't gonna cut off any time. In the long run u spent more time navigating through your file manger to go and delete it than it would for it to just flash. Were talking a matter or seconds in recovery. That's just my thoughts though do as you please.
Sent from my HTC One S using Tapatalk 2
mteezey said:
IMO removing the boot image isn't gonna cut off any time. In the long run u spent more time navigating through your file manger to go and delete it than it would for it to just flash. Were talking a matter or seconds in recovery. That's just my thoughts though do as you please.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Em its takes me over 5 minutes to flash a rom with the boot.img in the zip but if i remove the boot.img its less then a minute. With that in mind i would like to remove the boot.img from the zip and then when i copy the rom to sd i copy over boot.img as well.
Why is the HTC One S not listed in supported devices if its posted in HTC One S Apps & Themes?
I love you! This is great! Going to test it soon, next time I need to flash my rom.
We need to make you App look sexy as well!
Sent from my HTC One S using xda app-developers app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits
This is not work at all thanks to the XDA DEVELOPERS who made porting easy all credit goes to them iam just sharing it..
So lately so many custom Roms are ported and i thought let's share how to port a custom Rom in easy steps!! Did i said easy steps? yes!! porting is that easy shuffling things from here to there replacing files and you are done so let's start how to port a rom.
Notice
First Iam not Responsible if you somehow brick your phone always make a backup. Second This will not work on MIUI and LEWA SINCE YOU NEED THE RAMDISK FILES in next tutorial i will tell you how to pack and unpack the boot.img to get the Ram disk...
Things you Need
Open Mind other wise not possible
Any working Rom for your phone
Rom to port
Rooted Phone
Remeber!!! All Rom will not work on your device
First of all you need to choose a porting rom of phone with similar spec's as your phone have i.e Processor,Ram,internal Storage,size,Camera and same android version otherwise it will not boot up
Then make two folders one named base and second named port
Put any working Rom files for your phone to folder named base
Then put the downloaded working Rom you want to port to the folder named port
Copy these files from stock to port:
System/etc/firmware (whole folder).
System/lib/modules (whole folder).
System/usr/keylayout/generic.kl
Meta inf/.../update script
Meta inf/.../ update binary
Boot.img
Repack it in Zip folder not Rar..Put it into the root of your SD go into recovery wipe data wipe cache and flash your created Rom and you are done Happy Porting Please give feedback if got success and need anyhelp.. Dont Forget to click the thanx button. This is all i need in Return
OFFICIAL THREAD
SaadUsmani said:
Credits
This is not work at all thanks to the XDA DEVELOPERS who made porting easy all credit goes to them iam just sharing it..
So lately so many custom Roms are ported and i thought let's share how to port a custom Rom in easy steps!! Did i said easy steps? yes!! porting is that easy shuffling things from here to there replacing files and you are done so let's start how to port a rom.
Notice
First Iam not Responsible if you somehow brick your phone always make a backup. Second This will not work on MIUI and LEWA SINCE YOU NEED THE RAMDISK FILES in next tutorial i will tell you how to pack and unpack the boot.img to get the Ram disk...
Things you Need
Open Mind other wise not possible
Any working Rom for your phone
Rom to port
Rooted Phone
Remeber!!! All Rom will not work on your device
First of all you need to choose a porting rom of phone with similar spec's as your phone have i.e Processor,Ram,internal Storage,size,Camera and same android version otherwise it will not boot up
Then make two folders one named base and second named port
Put any working Rom files for your phone to folder named base
Then put the downloaded working Rom you want to port to the folder named port
Copy these files from stock to port:
System/etc/firmware (whole folder).
System/lib/modules (whole folder).
System/usr/keylayout/generic.kl
Meta inf/.../update script
Meta inf/.../ update binary
Boot.img
Repack it in Zip folder not Rar..Put it into the root of your SD go into recovery wipe data wipe cache and flash your created Rom and you are done Happy Porting Please give feedback if got success and need anyhelp.. Dont Forget to click the thanx button. This is all i need in Return
OFFICIAL THREAD
Click to expand...
Click to collapse
Question: I have a stock rom of my Samsung Express i437. I have located everything you mention in the System folder but there is nothing named Meta Inf/ in my ROM and no file named "update script" or "update binary". So can you give me some guidance here on what I am supposed to do. All the other folders and files have been located. Where do I find Meta inf/.../update script and Meta inf/.../ update binary?
Can I use this tutorial to port flymeOS to SGS Advance?
d14gvn said:
Can I use this tutorial to port flymeOS to SGS Advance?
Click to expand...
Click to collapse
i have ported mtk roms using this tutorial...u can give it a try since always make a backup before doing anythng..
nice guide but d14gvn remember those files arent the only files we need i saw on many other porting threads that we would need to replace whole folders for a port rom to work
SaadUsmani said:
Credits
This is not work at all thanks to the XDA DEVELOPERS who made porting easy all credit goes to them iam just sharing it..
So lately so many custom Roms are ported and i thought let's share how to port a custom Rom in easy steps!! Did i said easy steps? yes!! porting is that easy shuffling things from here to there replacing files and you are done so let's start how to port a rom.
Notice
First Iam not Responsible if you somehow brick your phone always make a backup. Second This will not work on MIUI and LEWA SINCE YOU NEED THE RAMDISK FILES in next tutorial i will tell you how to pack and unpack the boot.img to get the Ram disk...
Things you Need
Open Mind other wise not possible
Any working Rom for your phone
Rom to port
Rooted Phone
Remeber!!! All Rom will not work on your device
First of all you need to choose a porting rom of phone with similar spec's as your phone have i.e Processor,Ram,internal Storage,size,Camera and same android version otherwise it will not boot up
Then make two folders one named base and second named port
Put any working Rom files for your phone to folder named base
Then put the downloaded working Rom you want to port to the folder named port
Copy these files from stock to port:
System/etc/firmware (whole folder).
System/lib/modules (whole folder).
System/usr/keylayout/generic.kl
Meta inf/.../update script
Meta inf/.../ update binary
Boot.img
Repack it in Zip folder not Rar..Put it into the root of your SD go into recovery wipe data wipe cache and flash your created Rom and you are done Happy Porting Please give feedback if got success and need anyhelp.. Dont Forget to click the thanx button. This is all i need in Return
OFFICIAL THREAD
Click to expand...
Click to collapse
I used this guide to port a custom rom from htc one s to htc sensation .. when i tried to flash it it gave me error 7 .. i searched the internet i fixed iit by deleting the assert lines .. now it gives me error 6 >> i know my only problem is in update script .. what do i have to edit to make it work ?
FahmiFitu said:
I used this guide to port a custom rom from htc one s to htc sensation .. when i tried to flash it it gave me error 7 .. i searched the internet i fixed iit by deleting the assert lines .. now it gives me error 6 >> i know my only problem is in update script .. what do i have to edit to make it work ?
Click to expand...
Click to collapse
status 6 error is due to wrong updater script so edit ur updater script very carefully specialy in writing those mounting lines of run program nd also remove format system line if any !!
qmobilea2 said:
status 6 error is due to wrong updater script so edit ur updater script very carefully specialy in writing those mounting lines of run program nd also remove format system line if any !!
Click to expand...
Click to collapse
Okay I fixed this prob now when i flash the rom status 0 comes out and i cant flash roms no more. I have to format and repartition my sd card.
Best regards
FahmiFitu said:
Okay I fixed this prob now when i flash the rom status 0 comes out and i cant flash roms no more. I have to format and repartition my sd card.
Best regards
Click to expand...
Click to collapse
Now this Status 0 error is due to update binary file located in meta-inf folder.
To fix this just took out update binary file from any rom which works on ur phone nd then copy it nd paste it in ur port rom's meta-inf folder.
Problem done now u will not get any status 0 ,6,7 error.!!
Nd one more thing this guide is for mediatek smart phones not htc or samsung phones!!
Sent from my A2 using xda app-developers app
ikaster17 said:
nice guide but d14gvn remember those files arent the only files we need i saw on many other porting threads that we would need to replace whole folders for a port rom to work
Click to expand...
Click to collapse
i have ported so many roms following these steps dont wory it will work but i have tried it on mtk processor dont knw it will work on samsung or not
exactly!!
FahmiFitu said:
Okay I fixed this prob now when i flash the rom status 0 comes out and i cant flash roms no more. I have to format and repartition my sd card.
Best regards
Click to expand...
Click to collapse
qmobilea2 said:
Now this Status 0 error is due to update binary file located in meta-inf folder.
To fix this just took out update binary file from any rom which works on ur phone nd then copy it nd paste it in ur port rom's meta-inf folder.
Problem done now u will not get any status 0 ,6,7 error.!!
Nd one more thing this guide is for mediatek smart phones not htc or samsung phones!!
Sent from my A2 using xda app-developers app
Click to expand...
Click to collapse
exactly!! i have already told i have only tried successfuly porting rom for mtk based phones... iam not sure it wil work on samsung or not....
Unfortunately setting has stopped
Unfortunately system ui has stopped
these were error getting
SaadUsmani said:
exactly!! i have already told i have only tried successfuly porting rom for mtk based phones... iam not sure it wil work on samsung or not....
Click to expand...
Click to collapse
How to port rom Lewa on SoC MT6589?
thienhoa said:
How to port rom Lewa on SoC MT6589?
Click to expand...
Click to collapse
try porting with same method but u have to do some changes in boot.img i'll post that tutorial soon too..
4peace1 said:
Unfortunately setting has stopped
Unfortunately system ui has stopped
these were error getting
Click to expand...
Click to collapse
try porting some other rom..
SaadUsmani said:
try porting some other rom..
Click to expand...
Click to collapse
Can you give me link or suggestion to rom i can port for my Gionee E3
4peace1 said:
Can you give me link or suggestion to rom i can port for my Gionee E3
Click to expand...
Click to collapse
try from needrom,com there are lot of custom rom available on it...
SaadUsmani said:
try porting with same method but u have to do some changes in boot.img i'll post that tutorial soon too..
Click to expand...
Click to collapse
Thank
I repack ramdisk boot.img Lewa with kernel boot.img Base
=> Boot loop
thienhoa said:
Thank
I repack ramdisk boot.img Lewa with kernel boot.img Base
=> Boot loop
Click to expand...
Click to collapse
it is not necesary that every rom will work but for the lewa did u changed zImage from the lewa boot.img to stock?
Need help
I was have ported ROM using this method..
I used same specs devices to port the rom..based on MTK6589
All went right..
successfully flashed booted up..but there is some problems..plz help how to fix it..
1. No sound is coming from the SPEAKER..headphones r working
2. Back camera not working...the camera app just stops working and closes..
Help plzz..
Please note, this software is no longer maintained. Due to my hectic work life sadly, I no longer have time for programming. I have attached a copy of the last version to this post.
[ ABOUT ]
Tar To Flashable Zip is a multi-platform utility designed to build flashable Android recoveries from various input formats. The supported input formats are .img from your local filesystem as well as compressed .tar or .tar.md5 archives.
Tar To Flashable Zip runs on Windows XP and newer, Linux/Ubuntu, and on OSX ( supposedly, not tested )
I'll also be putting this utility on my web site within the next couple of days
[ REQUIREMENTS ]
Tar To Flashable Zip is written in Python, so it needs Python to be installed on your machine as well.
Windows users will need to install either of the software pairs listed below from their prospective developers or drop down to the "REQUIRED SOFTWARE" section and download the zip archive I'm hosting which contains the first required software pair listed below.
Linux/Ubuntu users should use their update mechanism to update Python and install wxPython to the equivalent of either of the software pairs listed below.
Mac users will need to do what ever they need to do, sorry for the lack of information, to install/update Python to their equivalent of either of the software pairs listed below.
Python 2.7.5 + wxPython 2.8
OR
Python 3.3 + wxPython 2.9 Phoenix ( Snapshot nightly builds )
NOTE::
I feel I must explain why the above softwares are required. For those of you who already know me, I've written a couple tools for Android that run on Windows only as I am a Windows programmer. In any case, I've had several requests to make Linux versions of the same utility apps. Since I'm not a Linux programmer, I was unable to grant those requests.
I'm here to help everyone that I can help. That's just me... That being said, after some reasearch I found Python to be the easiest way for me to be able to help more people with the utilities that I develop. Python will enable me to develop more and more useful utilities for the Android community while requiring less of my time to develop them. So in the end, installing Python is a win - win situation
[ REQUIRED SOFTWARE ]
Tar To Flashable Zip was written in Python. Therefore the Python interpreter is required. Tar To Flashable Zip's GUI uses wxPython. The archive linked below for Windows users has both Python 2.7.5 and wxPython 2.8. Obviously after extracting the archives contents you need to run Python's installer msi to install Python first. Then install wxPython. The installers will install 32-bit versions of Python and wxPython. This is fine even if you are using a 64-bit machine.
Windows XP and newer users -> python-2.7.5_win32+wxPython-2.8_win32.zip
Linux/Ubuntu users -> Please use your update tool to update Python to 2.7.5 and wxPython 2.8 or update Python to 3.3 and wxPython to 2.9 Phoenix
Mac users -> Please see the "REQUIREMENTS" section above
[ DOWNLOADS ]
See belowhttp://d-h.st/QFr
[ THANKS ]
@CodyF86 - For his Python expertise and beta testing
Works great! Everyone should learn Python btw, it's amazing!
Working on P3110 =) Good work
Waiting for tar.md5 to zip
Thanks @Android-Andi.
Support for .tar.md5 as well as .IMG files coming soon
Update available. Check the OP
Support for extracting from .tar.md5 archives had been added however there is no checksum verification provided at this time.
View "CHANGELOG.txt" for complete details;
What about 64bit Windows 7 users
Sent from my GT-I9152 using XDA Premium 4 mobile app
BalaN83 said:
What about 64bit Windows 7 users
Sent from my GT-I9152 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Install the 32 bit versions of python and wxpython. I develop on a windows 7 64 bit PC. 32 bit works on 64 bit too
Sent from my LG-P509
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
I found my mountable according to the files I have as a zip, it shows as /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6.
I've tried putting both those in the recovery mount space and hit convert, but nothing happens.
The file name I am useing is E4GT-EL29-directbootCWM-v3.tar.md5 from rwilco site here http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Not sure if that helps or not
easyrider77 said:
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Somewhat new to this stuff so I'm kinda learning as I go, so please be gentle with me
I'm not sure what my "mount" point is for my phone, Samsung Epic 4g touch SPH-D710
I am currently looking for a file I can open and look at it to learn this stuff but am not sure where to look or what file to go to.
Only thing I have is a tar file, and it has a zimage file in it (the kernel), it's the EL29 direct boot tar file.
Only 2 files available that I can find and that's the odin one click exe and this tar file, no zips, so I'm not even sure this will work, but I'd sure like to find out.
What I wanna do in short is make a flashable zip of this tar file to use in CWM recovery.
Hope that's not to much info, I always tend to do that
I found my mountable according to the files I have as a zip, it shows as /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6.
I've tried putting both those in the recovery mount space and hit convert, but nothing happens.
The file name I am useing is E4GT-EL29-directbootCWM-v3.tar.md5 from rwilco site here http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Not sure if that helps or not
Click to expand...
Click to collapse
Sorry, currently this tool does not support zImage format. Does your device support fastboot? If so and my memory serves me correctly, fastboot can flash zImage formatted images.
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Sent from my GT-N7100 using XDA Premium 4 mobile app
Well this is good!
I tested it successfully... on my Windows XP SP3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think there is a misunderstanding about this tool. Most of the users think that this tool can convert the whole tar/tar.md5 file to a ROM zip file. Actually it does with recovery.img only.... It's already specified in the thread... but not in the thread title....
zaharakis said:
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Click to expand...
Click to collapse
zaharakis said:
I tried your advice today to convert an .tar.md5 rom to .zip.
Everything worked as you say but the .zip file I'm taking as result is 7.5 mb from a tar.md5 rom 2.02 giga. ..
Is me or something else ? Regards
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not sure what exactly the problem is. This tool is only supposed to extract "recovery.img" from a .tar.md5 archive and then create a flashable zip. I've never seen a recovery of any kind that is 2+ GB in size. Most recoveries average around 10 MB, give or take a few MB.
Thread title has been update to reflect that this tool is for recoveries only.
shinobisoft said:
I'm not sure what exactly the problem is. This tool is only supposed to extract "recovery.img" from a .tar.md5 archive and then create a flashable zip. I've never seen a recovery of any kind that is 2+ GB in size. Most recoveries average around 10 MB, give or take a few MB.
Thread title has been update to reflect that this tool is for recoveries only.
Click to expand...
Click to collapse
No recovery,I tried to make a full rom.tar.md5 file to zip..
Sent from my GT-N7100 using XDA Premium 4 mobile app
zaharakis said:
No recovery,I tried to make a full rom.tar.md5 file to zip..
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry, you'll need to use ODIN to flash a ROM from .tar.md5 archive.
shinobisoft said:
Sorry, you'll need to use ODIN to flash a ROM from .tar.md5 archive.
Click to expand...
Click to collapse
Thank u mate ☺ I know it. I just wanted to make a flashable .zip file of rom to have it in my sdcard .
Sent from my GT-N7100 using XDA Premium 4 mobile app
Reverse?
is it possible to make a flashible zip into a tar? Just curious
majicmazo said:
is it possible to make a flashible zip into a tar? Just curious
Click to expand...
Click to collapse
Yes, but not with this utility.
Sent from my LG-P769 using Tapatalk
How to use on Mac
For those who wanna use this on a Mac OS X here is what you do.
Go to:
https://www.python.org/downloads/
Download the 2.7.7 python .dmg.
Mount the .dmg and run the Python.mpkg
Once the installer is done go to your applications folder. There will be a new folder there called Python 2.7.
Open that folder. Inside will be a Python Launcher.app (Looks like a Rocket Ship). The Python preferences window will come up.
Under Settings for file Type, change it from Python Script to Python GUI Script. Close out the preferences.
In the menu bar it should still say Python Launcher. Go to File / Open. Search for the TarToFlashableZip_1.0.0.1 folder you get from the zip you download in the original post. Find the TarToFlashableZip.pyw.
The tool will open. Load in your recovery.img or .tar file. Make sure you have chosen the right recovery partition and hit convert.
Thanks to the op for this tool. Very handy.
No way to use it on windows 7?
shinobisoft said:
[ ABOUT ]
Tar To Flashable Zip runs on Windows XP and newer, Linux/Ubuntu, and on OSX ( supposedly, not tested )
Click to expand...
Click to collapse
Hello
Thanks for this tool.
Is there no way to use this tool on windows 7?
Regards
Dr.Ghobar
Dr.Ghobar said:
Hello
Thanks for this tool.
Is there no way to use this tool on windows 7?
Regards
Dr.Ghobar
Click to expand...
Click to collapse
It requires Python to be installed on your system. I believe I stated such in the OP. This was developed on a computer running Windows 7 Professional...
Sent from my SM-G360P using Tapatalk