[ TOOL ][ UNIVERSAL ][ Win/Linux/Mac ] - Tar To Flashable Zip ( recovery only ) - Miscellaneous Android Development

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

Related

[GUIDE]Full ROM backup/dump for MTK6573 & MTK6516 phones !!![NOT nandroid backup]

Hi all MTK6573/MTK6516 users !!!!
SEE SECOND POST FOR MTK6516 phones.
THIS POST IS FOR MTK6573 phones.
This is for all MTK6573 users with Android 2.3(.x). Also for all B63M phones !!
Follow this guide to backup your FULL ROM !! You can even flash your phone through FlashTools with this COMPLETE backup !!!
ROOT IS REQUIRED !!
Here is the guide:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'MTK-6573-BackUpTools.rar' from attachments and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
NOTE: The backup script is not created by me. Gathered all information from the web !!
Hit THANKS if you find this useful !!
For MTK6516 !!
THIS POST IS FOR MTK6516 phones.
This is for all MTK6516 users with Android 2.2(.x).
Follow this guide to backup your FULL ROM !! You can even flash your phone through FlashTools with this COMPLETE backup !!!
ROOT IS REQUIRED !!
Here is the guide:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'MTK-6516-BackUpTools.rar' from attachments and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
NOTE: The backup script is not created by me. Gathered all information from the web !!
Hit THANKS if you find this useful !!
A few questions!
Hello!
Thank you for this software, it worked with making a dump of my rom. How do you create a scatter file to use in SP Flash Tool? Or do you have another program that I can use to flash these files back onto the phone?
The SP Flash Tool I am using V2.1129.00 does not show as many partitions as what was backed up by my phone with the default MT6573 scatter file that it comes with.
I keep getting errors trying to load/burn the files to my phone.
PLEASE HELP!!
LeStonga said:
Hello!
Thank you for this software, it worked with making a dump of my rom. How do you create a scatter file to use in SP Flash Tool? Or do you have another program that I can use to flash these files back onto the phone?
The SP Flash Tool I am using V2.1129.00 does not show as many partitions as what was backed up by my phone with the default MT6573 scatter file that it comes with.
I keep getting errors trying to load/burn the files to my phone.
PLEASE HELP!!
Click to expand...
Click to collapse
You can try this:
Copy the backup_ folder from your sd card to your computer. Now place a copy of a the scatter file.txt in that folder.
Now in SP Flash tool, browse to the folder and select the scatter file that you placed.....all files will be loaded automatically......
It didnt work . . .
Hello!
I took your advice and attempted to load the scatter file from the same folder that the backup partitions are in.
A few of they files loaded on their own, not all of them, and their are still partitions missing.
When I open the scatter file in txt editor it shows all partitions.
When I open the scatter file in smart phone flash tool i only show
preloader
dsp
uboot*
bootimg*
recovery*
secro
logo*
android*
usrdata
The files above are what shows in sp flash tool program and the ones with the * are the files that load automatically.
I did try a smart phone flash tool version 5.1140 and the scatter file did load correctly with all the partitions, but again not all load and I get an error when I try to load them manually. In addition, I have never been able to successfully use version 5.1140 to flash.
I was able to flash in version 2.1129, but as I said I couldnt load every partition so I am missing my nvram and other partitions.
Can you recommend anything else?
Maybe a different version of sp flash tool that you know works? Maybe a different program all together?
THANKS!
@Bala
Yo, bro, its been awhile since our last chat ! You have been like an android modding/ hacking teacher/ guru & i'm sure alot of users will benefit from all of it...
@LeStonga
Yes, in fact your are correct, there is a software by linerty(these russians are so 'terror', not only hacking but coming out with tools to make it easier) that converts the extracted firmware.info back into scatter.txt...You can find the tuts & tools here.
The tuts even show you ways to upload with FlashTool too ! i know there is an upload function but never knew the way to use it though...
Hello balamu96m!
Thank you for your suggestions, that was the website which I first followed instructions for.
As you can see however, even when Bruno (administrator of the tutorial you provided in the link) opened his scatter file, nvram partition is not shown. I was able to use the program balamu96m pointed me to and it made perfect backups of all my partitions.
My problem is that sp flash tool loads my scatter file and it is the same as Bruno's which is lacking several partitions, especially the nvram partition.
If i use an updated sp flash tool (v5), when I load my scatter file all of my partitions are shown, including nvram, but I have never had any success flashing my phone with that version.
Maybe I can use that version but someone has to help me set up the configurations to flash . .. i.e. download with or without battery, com, baud rate, etc.
Sp flash tool V2.11 was easy to use and straight forward, but even though my scatter lists all my partitions (when i open in a text editor), it only loads the partitions shown in bruno's tutorial, not including nvram.
yuweng said:
@Bala
Yo, bro, its been awhile since our last chat ! You have been like an android modding/ hacking teacher/ guru & i'm sure alot of users will benefit from all of it...
@LeStonga
Yes, in fact your are correct, there is a software by linerty(these russians are so 'terror', not only hacking but coming out with tools to make it easier) that converts the extracted firmware.info back into scatter.txt...You can find the tuts & tools here.
The tuts even show you ways to upload with FlashTool too ! i know there is an upload function but never knew the way to use it though...
Click to expand...
Click to collapse
Hi yuweng bro!
It seems miui is going to release their source code........i read in the russian forum at 4pda that one mtk6573 was running miui 4 (ics).......is that true??
So when miui sources are out, can we build one for our mi-357/350n??
Waiting for your reply
@Bala
AFAIK, Miui public part of their source code before the launch of their first android phone, Xiaomi M1 & now launching their next version M2 which is based on ARM Cortex-A8 & coincidentally, its just been launch today ! Its fully supported by the Miui team & it has two ROM, one ROM for daily use & the other one for you to flash their 'nightly' built. Best is that you can switch over to either one of them at any time ! Great for android enthusiastic...
However, of all hundreds over MT65xx android phone manufacturer all over the world, non of them actually ported it to Miui ! There is only one answer to this, it will be copied over to all other MT65xx ! Thats what Chinese are best at...(Oopps, i'm a Chinese too...)
So, i think you won't see an official Miui phone on MT65xx platform... Currently, official Miui ROM is for single SIM... You can check out Miui sources here & here
If its really true that the russian has ported Miui to MT65xx, very soon we'll have Miui running on every MT65xx...
What you said on the other thread is true, if Mediatek keep on keeping their source code, i think very soon they can keep it to themself forever.... No android enthusiastic will ever buy their phone ever... Even HTC has released the source code for a whole bunch of devices recently after been pressured by android enthusiastic...
@LeStonga
AFAIK, FlashTool is not for flashing NVRam(IMEI). However, you can use it to backup NVRam then restore it. Typically, you only need to download boot, recovery, logo, android, usrdata. Normally, i just download 'android' partition only(system.img) I normally put a 'tick' at 'No Action' for NVRam...
{
"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"
}
There is a thread on how to backup & restoring your MT65xx IMEI by cybermaus just over a week ago...
help help
I have android phone china H4300. mediatek mtk6573. yesterday , i deleted stock launcher and format factory the phone. so i don't use it.
please help me up rom (i haved rom) or install the Launcher ,...
thank you
vanlaosonya said:
I have android phone china H4300. mediatek mtk6573. yesterday , i deleted stock launcher and format factory the phone. so i don't use it.
please help me up rom (i haved rom) or install the Launcher ,...
thank you
Click to expand...
Click to collapse
Do you have modded recovery??
balamu96m said:
Do you have modded recovery??
Click to expand...
Click to collapse
i only have stock recovery
Thanks it works on my MT6573 phone
Hey balamu....
Can you please tell me how to restore this backup...???
maitreyapatni said:
Hey balamu....
Can you please tell me how to restore this backup...???
Click to expand...
Click to collapse
Allow me to answer ...
To restore this backup, 1st you need to convert the firmware.info into your own scatter.txt file. Read here : http://bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
Then you run SPflash tool, choose your scatter file and the appropriate area to flash. You don't need to flash all area. Just boot+system (android) to restore is sufficient. You can change the file by double-click at the appropriate row. Untick to deselect, tick to select which area to flash.
Again, no need to flash the whole thing ... some file contains private info such as nvram/userdata. I've read that many device already bricked by flashing wrong file (specially uboot) unless it's from your own backup.
no cache.img, system.img, data.img
hi balamu, i need some help.
i have an mt6516 phone. i followed every step, but 3 files didn't show up i.e cache.img, system.img, data.img
in the end of running script, gscript show "no such files". my question are: is that normal? are those file important? any ideas to get these files?
i really need any help here.
so thx in advance
hisoka8888 said:
hi balamu, i need some help.
i have an mt6516 phone. i followed every step, but 3 files didn't show up i.e cache.img, system.img, data.img
in the end of running script, gscript show "no such files". my question are: is that normal? are those file important? any ideas to get these files?
i really need any help here.
so thx in advance
Click to expand...
Click to collapse
they are really important...................you can retry the process again.......it should work.....!
silly me
found out the problem. looks like i didn't do exactly one of your step "extract into sd card". i actually extract the content into a folder inside the sd card, so gscript can't find the "Install" folder. I copied the folder into sd card and redo the process then those file showed up. LOL.
anyway, nice share... :good::good:
n7000 note copy rom file i loss it help
n7000 note copy rom file i loss it help
mtk 6573
plz send rom file
mail id [email protected]
thanks in adwance
Hi,Thanks for tutorial,I backup my phone,create scatter file and all goes ok but now i have 1 litl problem,my phone is mobiwire aquila mt6573 platform, he got factory recovery e3 and i wanna change to cwm and Bruno say that cwm must be specific for phone so is any chance to find cwm for my phone or any hack/swap from backup recovery or any other method?
Sorry guys on bad english or wrong section
Thanks

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

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

[Tutorial] How to change kernel logo (1st boot srceen) [COMPLETED]

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.

[Repack] Aorth's ClockWorkMod 6.0.1.9 (Odin Format) (All Devices)

What Is This?
I have repacked and mirrored Aorth's builds of ClockWorkMod 6.0.1.9 for various versions of the GT Plus in Odin format. Aorth has posted about these in his CM10 nightly thread here, but the links are sometimes hard to find.
The process of "converting" them is pretty easy if you have access to Linux, you run the following commands:
Code:
mv t869_clockworkmod_6.0.1.2.img recovery.img
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Odin Links
-i815 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6800 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6810 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6200 (Odin) (Heimdall) (Heimdall-Goo.im)
-p6210 (Odin) (Heimdall) (Heimdall-Goo.im)
-t869 (Odin) (Heimdall) (Heimdall-Goo.im)
Odin 1.85
Let me know if any of the links are incorrect.
As I said in my previous post like this, if you find this useful, consider donating to / thanking Aorth, or donating to Android File Host. You can also send me Thanks if you want, of course ;P
Working fine with my p6200 with odin mobile (using the odin file)
Thx soo much!
Enviado desde mi GT-P6200 usando Tapatalk 2
Euphoria_ said:
Working fine with my p6200 with odin mobile (using the odin file)
Thx soo much!
Enviado desde mi GT-P6200 usando Tapatalk 2
Click to expand...
Click to collapse
Oh yeah, I forgot about Odin Mobile. Glad to hear it works
Working fine..installed in a few second..via mobile odin..
Sent from my GT-P6200 using xda premium
Works OK. Flashed thru mobile Odin also. But when I try to reboot from recovery it says root might be lost and ask me fix su/bin? I select no and it reboots fine and root works fine
Edit: allowed recovery to fix and error message goes away. Works perfect now
Sent from my GT-P6200 using Tapatalk 2
attempted with Odin 1.85 on my P6200l. Message received was " MD5 hash value is invalid".
After multiple unsuccessful tries with Heimdall on both Windows 7 and Linux machines, I'm beginning t think maybe it's me... although I had no probs with my SG2..
Any advice would be hugely appreciated.
subdriver57 said:
attempted with Odin 1.85 on my P6200l. Message received was " MD5 hash value is invalid".
After multiple unsuccessful tries with Heimdall on both Windows 7 and Linux machines, I'm beginning t think maybe it's me... although I had no probs with my SG2..
Any advice would be hugely appreciated.
Click to expand...
Click to collapse
MD5 being invalid means the file has somehow become corrupted. I would download it from Aorth and test that via Heimdall next.
The p6200 odin link doesn't seem to work. Will you please check the links?
Sent from my GT-N7100 using xda premium
wtfshouldidonow said:
The p6200 odin link doesn't seem to work. Will you please check the links?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
It looks like AndroidFileHost is having some kind of problem.
In my file management interface, the entire directory I created for the CWM stuff is just straight up gone, and all the links I posted go nowhere.
However, they have a notice up:
"SYSTEM NOTICE: Aware that some of the uploads are not showing up on site. Fixing this now. SQL did not merge completely"
Ostensibly the files/directories are still there, but the system doesn't currently display them since the database that runs the show is broken. That notice is all they posted, no ETA on a fix
If it hasn't been put back online later today I can re-build the needed files as needed, just takes some effort. I can host them on one of the web hosts I actually run if anyone really needs them.
DivinityCycle said:
It looks like AndroidFileHost is having some kind of problem.
In my file management interface, the entire directory I created for the CWM stuff is just straight up gone, and all the links I posted go nowhere.
However, they have a notice up:
"SYSTEM NOTICE: Aware that some of the uploads are not showing up on site. Fixing this now. SQL did not merge completely"
Ostensibly the files/directories are still there, but the system doesn't currently display them since the database that runs the show is broken. That notice is all they posted, no ETA on a fix
If it hasn't been put back online later today I can re-build the needed files as needed, just takes some effort. I can host them on one of the web hosts I actually run if anyone really needs them.
Click to expand...
Click to collapse
I am also desperately looking for the Odin flash files as heimdall does not seem to be responding to my commands.
heimdall flash p6200-clockworkmod-6.0.1.9 was a command that once worked for me, but now that command is just giving me a load of different options of which iv read little about. if anyone could upload these files that would be great
Awology said:
I am also desperately looking for the Odin flash files as heimdall does not seem to be responding to my commands.
heimdall flash p6200-clockworkmod-6.0.1.9 was a command that once worked for me, but now that command is just giving me a load of different options of which iv read little about. if anyone could upload these files that would be great
Click to expand...
Click to collapse
All the files are back online at Android File Host. As with my link in OP
http://www.androidfilehost.com/?fid=9390169635556426744
Just click the big green down arrow
MD5 is invalid ~ oh no does this mean these files have become corrupt. ?
Awology said:
MD5 is invalid ~ oh no does this mean these files have become corrupt. ?
Click to expand...
Click to collapse
Yeah usually means something along the way broke em. In order to convert them, I had to download them to my desktop, upload them to my Linux server, convert them, download them back to my desktop, and then upload them to Android File Host. Its possible that the source files are bad, or that they became corrupted somewhere during that process, or somewhere during your download.
If you have access to a Linux box, its really easy to "convert" the file to work with Odin. That'd be your best bet, re-download them from the original builds Aorth made and uploaded to goo.im, then convert them over, then flash.
DivinityCycle said:
Yeah usually means something along the way broke em. In order to convert them, I had to download them to my desktop, upload them to my Linux server, convert them, download them back to my desktop, and then upload them to Android File Host. Its possible that the source files are bad, or that they became corrupted somewhere during that process, or somewhere during your download.
If you have access to a Linux box, its really easy to "convert" the file to work with Odin. That'd be your best bet, re-download them from the original builds Aorth made and uploaded to goo.im, then convert them over, then flash.
Click to expand...
Click to collapse
Unfortunately iv only got access to windows 7 64bit, iv had it installed via hemidall before and it was pretty easy, so im sure im making a real novice mistake.
This is my screenshot of command prompt, do or anyone else have any suggestions on where i might be going wrong.
{
"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"
}
Awology said:
Unfortunately iv only got access to windows 7 64bit, iv had it installed via hemidall before and it was pretty easy, so im sure im making a real novice mistake.
Yeah, I believe the correct syntax is heimdall flash --recovery (filename here).
So like if you're in the same directory as the file and the filename is somefile.img, the command would be heimdall flash --recovery somefile.img.
I always got this far but then couldn't get it to work under Windows due to driver issues.
Click to expand...
Click to collapse
DivinityCycle said:
Awology said:
Unfortunately iv only got access to windows 7 64bit, iv had it installed via hemidall before and it was pretty easy, so im sure im making a real novice mistake.
Yeah, I believe the correct syntax is heimdall flash --recovery (filename here).
So like if you're in the same directory as the file and the filename is somefile.img, the command would be heimdall flash --recovery somefile.img.
I always got this far but then couldn't get it to work under Windows due to driver issues.
Click to expand...
Click to collapse
Thanks your day saver. i knew i was doing some thing stupid with the commands.
that worked like a charm
Click to expand...
Click to collapse
Here is a link to the Odin package courtesy of "MaxiTheMan", iv not checked it myself but apparently it works..
https://www.box.com/s/9ej7dbekuwcl4w6yurkw
Awology said:
Here is a link to the Odin package courtesy of "MaxiTheMan", iv not checked it myself but apparently it works..
https://www.box.com/s/9ej7dbekuwcl4w6yurkw
Click to expand...
Click to collapse
Hi, I have tried with both the p6800 and p6200 versions. Both give the MD5 invalid message.
Edit 8.30pm : Installed Mobile Odin and flashed ..skipped verifying MD5 ... worked OK. Have since done a system backup and all OK
gazjglusk said:
Hi, I have tried with both the p6800 and p6200 versions. Both give the MD5 invalid message.
Edit 8.30pm : Installed Mobile Odin and flashed ..skipped verifying MD5 ... worked OK. Have since done a system backup and all OK
Click to expand...
Click to collapse
That is one of those "seems like that shouldn't work" type situations. I'm not sure why it'd flash and be OK if the MD5 failed.
DivinityCycle said:
That is one of those "seems like that shouldn't work" type situations. I'm not sure why it'd flash and be OK if the MD5 failed.
Click to expand...
Click to collapse
Yes it's got me tricked. I tried everything about 10 times each and the only way was via Mobile Odin.
Anyway just did a full restore and again all is fine.:good:

[Pre Rooted Stock]No wipe,No flash counter raise + Guide How to make Prerooted ROM

Pre Rooted Stock ROM
Here is complete stock Pre rooted ROM
( MUST READ THIS before flashing DMF2/ME6 or any newer )
July13
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Deodexed - India - Download - Detail here
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Odexed - India - Download
June13
N7100XXDMF2_N7100OLBDMD2_XME - Malaysia - Download - - - Mirror
SuperSu updated to latest 1.34
Package have addition mod zip file which is optional, If you want to install that mod, instead using packed one use this
April 2013
N7100XXDMC3_N7100ODDDMD1_N7100DDDLK6 (INU) -India - Download
March 2013
N7100XXDMC3_N7100OXXDMC2_N7100XXDLK7 (XEO) - Poland - Download
Installation Instruction
- Download ROM and extract to ***.tar.md5 (unzip tool)
- Make sure you have installed Kies OR Samsung USB driver
- Open up the S/W Installation Program by executing the Odin3 v3.04.exe
1. Enable the check mark by click on the following options(default Option)
- Auto Reboot, and F. Reset Time
- Check PDA, and point to ROM file you have extracted
{
"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"
}
File name shown in above image is for demo purpose, you have to select according ROM you have download
2. Now switch off device and Enter into Download Mode
- Enter into Download Mode by pressing Volume Down button, Home Key and
Power Button simultaneously. And then, press Volume UP button in Warning Page to enter the Download Mode.
3. Connect the device to PC via Data Cable.
Make sure that the one of communication port [ID:COM] box is highlighted in
light blue. The device is now connected with the PC and ready to download the
binary file into the device.
4. Start downloading binary file into the device by clicking Start Button on the screen.
the green colored "PASS!" sign will appear on the upper-left box if the binary file has been successfully downloaded into the device.
5. Disconnect the device from the Data cable.
6. Once the device boots up, you can check the version of the binary file or name
by pressing the following code in sequence;
*#1234#
After flashing your device will have SuperSU in application drawer. If you want to unroot it, open SuperSu - settings - Full unroot.
First thing I do recommend after rooting device is
EFS Backup
Why so?
EFS folder contains some important and some basic info related to our device identity like Wi-Fi address, Bluetooth MAC address and the very main IMEI address (nv_data.bin).
Now if this EFS partition accidently corrupted then your phone’s IMEI no. will erased and you can not make voice call further. This kind of damage is often not accepted by the service center of your respected handset’s company.
Here your backup can only be savior for you.
-This is pure samsung stock ROM as it is + Root
-Non wipe
-Won't raise flash counter.
- Non Hotfile link
Again to make it clear, there is no any additional changes except pushing superSU (busybox added to April 2013 and onward), so there won't be have any difference from stock ROM, but you will not need to Root / reset counter. Just note that, flashing prerooted ROM doesn't reset counter, If your flash counter already raised flashing this ROM doesn't reset it, but you can use triangle away to reset counter after flashing this ROM. later you can uninstall triangle away.
Rooting is not difficult but still many users scare from it, this will come handy to them.
There is no plan to make every release Pre rooted, when there will be major update and myself update device that time will make that ROM pre rooted.
There is already thread in dev section by as i9000, which also have deodexed version and many other ROMs with multi CSC and regularly updating too. This thread will update only ROMs which i am using, as well basic aim is to write tutorial abiut how to make pre rooted ROM.
There are two other MB6 and DMB2 India are ready but really finding difficulty to upload. still i will try my best to upload it.
- Password to unzip - when there is any password to unzip, file name itself will have it.
- difference in file size from sammobile stock rom size is just due to different compression method, once you extract it will be same.
How to make prerooted stock ROM.
Requirements :
Ubuntu and login as Root user.
Ext4_utils - extract to home directory
Root files (su and Superuser.apk) - copy to home directory
busybox - copy to home directory (optional)
Procedure :
1.Download ROM you need to preroot and rename stock.tar.md5 (just to make command line input easy)
2.Extract ROM
Code:
tar xvf stock.tar.md5
3.convert system.img to ext4 so we can mount it.
Code:
./simg2img system.img newsys.img
4.delete system.img
Code:
rm -f system.img
5.Create temp folder and mount it
Code:
mkdir temp
mount -o loop newsys.img temp
6.Push root and busybox file to system and change permission
Code:
cp su temp/xbin/su
chmod 06755 temp/xbin/su
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
Code:
cp busybox temp/xbin/busybox
chmod 04755 temp/xbin/busybox
7.Conver newsys img to samsung system.img format
Code:
./mkuserimg.sh -s temp system.img ext4 tempdir 2048M
8.unmount and delete temp folder
Code:
umount temp
rmdir temp
9.create odin flashable tar file (here file names depends on files you have got by extracting ROM)
Code:
tar cvf prerooted.tar boot.img cache.img hidden.img modem.bin recovery.img sboot.bin system.img tz.img
10. add md5 checksum
Code:
md5sum -t prerooted.tar >> prerooted.tar
mv prerooted.tar prerooted.tar.md5
Now Flash prerooted.tar.md5 with odin.
Delete following files from home directory to make it clean
stock.tar.md5
newsys.img
and all files extracted while unpacking tar in step 1.
Credits :
Chainfire for his SuperSu
Phil3759
Credits to following user for referring their works on different forum
jazzor, rizdroid, das7982, faria
Where is it sir?
Sent from my GT-N7100 using xda premium
As I have said
What's your opinion?
Do I update rom
Or
You want guide, how to make it yourself.
Sent from my GT-N7100 using xda premium
My choice is 2
Please provide complete guide
Sent from my GT-N7100 using Tapatalk 2
Make a guide. That way, people learn more.
Sent from my GT-N7100 using xda premium
i thought it was just about placing su in xbin and supersu.apk in app -.-
yeah unpacking repacking and all can be a damn headache
No offense, leave the dev part to those who deserve this denomination and stick with the Guide Guru image that you have built for yourself and for which you get lots of credits and praise. I'd choose option 2.
Thanks for your excellent work of guiding noobs like me and troubleshoot their problems.
P_
))))))
That's the same there! And for a long time!
http://forum.xda-developers.com/showpost.php?p=32260125&postcount=1
:laugh:
2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app
UBUNTU needed for this)
alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda app-developers app
alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
Not with cygwin.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Not with cygwin.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
There are some limitations in cygwin. Ubuntu is best for this.
Sent from my GT-N7100 using xda premium
Please post guide so that we'd learn ourselves
Sent from my GT-N7100 using xda premium
---------- Post added at 09:22 PM ---------- Previous post was at 09:15 PM ----------
sharjackmission said:
2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda premium
Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I can help
How?
Sent from my GT-N7100 using xda premium
Option 1
madhuranand007 said:
Option 1
Click to expand...
Click to collapse
Sure
Within 5 min updating OP
dr.ketan said:
How?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Advice to you ladies
http://forum.xda-developers.com/showthread.php?p=39848357#post39848357
http://forum.xda-developers.com/showthread.php?p=39286842#post39286842
You have incorrectly assembled system img.The composition of the image.
No busybox.No su in bin)))
resolution:
Code:
cd app
chmod 0644 Superuser.apk
My version:
https://hotfile.com/dl/202764580/bcb9aa2/system.img.zip.html

Categories

Resources