[I9000][Heimdall][Jan.30.2012] Firmware packages for stock ROMs - Galaxy S I9000 General

Heimdall firmware packages for stock GT-I9000 firmwares​
Heimdall 1.3 included support for "Heimdall Firmware Packages," an XML-driven way to define, create, and distribute firmwares. This is a powerful tool for ROM developers, but I haven't seen it being used yet. In order to encourage and support the use of these new firmware packages, I've packaged up a few stock Samsung firmwares for use with Heimdall.
For those that don't know, Heimdall is an open-source, cross-platform tool written by Benjamin Dobell which can flash complete ROMs, kernels, modems, etc to Samsung Galaxy S devices. It's preferable over Odin as its source code is open and it is therefore undergoing public development, and we can review the code. In comparison, Odin is a closed-source, Windows-only internal Samsung utility, and what we know very little about it.
Downloads​
These are stock ROMs, just as you'd find on Samfirmware or wherever else. I have not modified them other than unpacking and repacking for flashing with Heimdall (meaning they are odexed). If the upstream firmware includes bootloaders, I've included them*. I'll do my best to indicate additional information next to each ROM.
Gingerbread:
XXJVQ (2.3.4): MultiUpload
XXJVR (2.3.4): MultiUpload
XXJVS (2.3.5): MultiUpload / BayFiles
XXJVT (2.3.5): MultiUpload
XWJVZ (2.3.6): MultiUpload, BayFiles / MediaFire (md5sum: dbfcb621f666b224751a3bd2bf9abbba)
XXJVU (2.3.6): BayFiles (md5sum: ede04385b889651c31ce669044ec5ee6)
*Note: Even though I've included bootloaders you'll be able to remove them in Heimdall's GUI right before flashing if you so please.
Froyo:
XWJSD (2.2.1): MirrorCreator - thanks Motthat
Credits...​
Thanks to Benjamin Dobell for writing Heimdall. Thanks to [Ramad] for the idea of listing unadulterated stock ROMs. Thanks to Supercurio for being a role model of openness and transparency. We need more pro-community devs.

Flashing instructions
Flashing instructions​
Make sure you've installed Heimdall version 1.3 or higher. Do not unzip the firmware package, we open it up directly in the heimdall frontend graphical user interface! This procedure will wipe your device and you will lose all your installed applications.
Step 1: Open Heimdall's frontend (heimdall-frontend on Linux)
Step 2: Load the downloaded tar.gz into Heimdall
{
"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"
}
Step 3: Press "Load / Customize"
Step 4: Reboot your phone in Download mode and connect it to your computer
Step 5 (optional): Customize the installation before flashing by removing or adding different files (such as pre-rooted kernels or different modems)
Step 6: Press "Start"
Your phone will begin to flash and then reboot.

Reserved...

It's great to see some Heimdall Firmware Packages for the GT-I9000. The instructions and screenshots you've included should make it super easy for beginners to get going. Keep up the good work!

I put together an XWJSD package (latest 2.2.1 firmware) which you're welcome to add to the collection. http://mir.cr/0XZMZGFA

Mothatt said:
I put together an XWJSD package (latest 2.2.1 firmware) which you're welcome to add to the collection. http://mir.cr/0XZMZGFA
Click to expand...
Click to collapse
Ok, cool. I thought it might be useful to have some Froyo packages around. I've added it, thanks!

You are both legendy legends from the land of the legendary legend people! I was beginning to get beside myself with frustration - no matter how hard I tried I simply couldn't get kies/samsung drivers installed ON ANYTHING - I tried about 4 different Win7 x64 machines, a 2008R2 and even a Vista x86 and NONE of them would get me a working install. I inherently mistrust odin and when I saw heimdall (so I could run it on Linux) I was just over the moon. Not having any heimdall-native packages though, I got pretty frustrated and ended up soft-bricking my phone at about 2am this morning . So after arriving after a long day at work I was very happy to see some packages finally get released and what's more - my phone was back up and running from the death-screen in under 10 minutes!
So now I can experiment with lots of funky ROMs and I know I'll always be able to get my I9000 back again!
You both rock.
A

AntonDreams said:
You are both legendy legends from the land of the legendary legend people! I was beginning to get beside myself with frustration - no matter how hard I tried I simply couldn't get kies/samsung drivers installed ON ANYTHING - I tried about 4 different Win7 x64 machines, a 2008R2 and even a Vista x86 and NONE of them would get me a working install. I inherently mistrust odin and when I saw heimdall (so I could run it on Linux) I was just over the moon. Not having any heimdall-native packages though, I got pretty frustrated and ended up soft-bricking my phone at about 2am this morning . So after arriving after a long day at work I was very happy to see some packages finally get released and what's more - my phone was back up and running from the death-screen in under 10 minutes!
So now I can experiment with lots of funky ROMs and I know I'll always be able to get my I9000 back again!
You both rock.
A
Click to expand...
Click to collapse
Yes, we're really lucky that this phone is so robust and the bootloaders are open. As long as download mode is working you can resurrect your phone (and even sometimes when download mode isn't working)!

Thanks for these man, it really is the best way to flash everything, pity it isn't as widely used as it should be! Keep it up

First of all thank you!
Kies for Mac was really harassing me for such a long time nor I could using Odin on Parallels.
After playing with some roms and messing up my device (Samsung Galaxy S)I was happy to come back to an official release.
Your guide to Heimdall was simply great.
Now that I'm on Gingerbread JVR 2.3.4 I wanted to root my phone.
Here I found CF-Root and I downaloaded the zip file for my firmware (JVR)
http://forum.xda-developers.com/showthread.php?t=788108
The file is zip and when you unpack you get a Zimage file.
I'm using Heimdall fronted 1.3.0 how can I flash this file in order to toot my phone ?

Realy glad that you let us take one more step to the use of Heimdall.
Is this JVR rom NEE/XEE csc compatible?
Don't want to screw up to KOR again

zidz said:
Realy glad that you let us take one more step to the use of Heimdall.
Is this JVR rom NEE/XEE csc compatible?
Don't want to screw up to KOR again
Click to expand...
Click to collapse
I'm not sure... I've never bothered to figure out what the deal with CSCs is. I downloaded XXJVR from samfirmware, does that help ?

aorth said:
I'm not sure... I've never bothered to figure out what the deal with CSCs is. I downloaded XXJVR from samfirmware, does that help ?
Click to expand...
Click to collapse
I've downloaded it from SamFirmware, that one is a KOR one :/

enomis74 said:
Your guide to Heimdall was simply great.
Now that I'm on Gingerbread JVR 2.3.4 I wanted to root my phone.
Here I found CF-Root and I downaloaded the zip file for my firmware (JVR)
http://forum.xda-developers.com/showthread.php?t=788108
The file is zip and when you unpack you get a Zimage file.
I'm using Heimdall fronted 1.3.0 how can I flash this file in order to toot my phone ?
Click to expand...
Click to collapse
Anyone?????

jaystarrr said:
Anyone?????
Click to expand...
Click to collapse
On the flash page add the pit file then Click the Add Button under Partition (Files) Section. Choose Kernel from the Partition Name dropdown box, then click browse and select the zImage file.

Error loading firmware tar.gz file
Hi,
Do you know what can be this error, i installed heimdall and frontend, downloaded tar.gz files from this post, and i get "Failed to open package:
/home/jtextori/Téléchargements/XXJVQ_heimdall.tar.gz" ??
Thanks

If you root it you must reflash the orginal KERNEL

Don't know if it is what you mean, but moving the file into a directory without accentuated characters allowed to load the file into heimdall-frontend ! it was that simple !

Thx soo much for the job! and also thx for the heimdall developper. happy to can do a flash to my galaxy phone from my mac.

jtextori said:
Hi,
Do you know what can be this error, i installed heimdall and frontend, downloaded tar.gz files from this post, and i get "Failed to open package:
/home/jtextori/Téléchargements/XXJVQ_heimdall.tar.gz" ??
Thanks
Click to expand...
Click to collapse
maybe the file are bad downloaded and are bad. my md5 is: 502288c2261cdfbe41ce401128cffb27
and the file size are 259.060.144 bytes (259,1 MB)

Related

(GUIDE) How To S-Off and ROOT Aria 2.2.2

Thanks to AlphaRev Team we can now S-Off the Aria(Removes Security Flag)
**This is for any Aria either shipped with or upgraded to 2.2.2 Firmware**
For an alternative guide check out post #84 by zervic in THIS Thread
Requirements you must have:
*All Drivers installed on Windows PC (See Aria Superthread)
*Aria S/W v2.2.2 (either from the Update RUU or Factory Shipped)
***WARNING*** Installing the Aria Update RUU will format the phone. Any info not backed up will be lost. SD Card is not affected
---If you have ClockworkMod installed you can make a Nandroid backup which can be restored later
*HBOOT 1.02 (installs with the Update RUU)
Difficulty Level= Medium/Some experience required
How To S-Off
-If you have s/w version 2.1 or Custom ROM follow installation instructions for Un-Rooting in the Aria Superthread
if needed: Download ATT Aria Shipping ROM 2.2.2
1- Make sure USB Debugging is checked in Applications/Development
2- Go to Revolutionary Website and click "Download For Windows". a form will pop up which we will fill out later
3- Save file to PC and keep web page open
4- Plug in phone with data cable then run downloaded program Alpharevx.exe
{
"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- Take note of where it reads "Enter Beta Key [Serial: your personal serial ]
5- On AlphaRev website fill in the short form with your info including the alphanumeric serial given from the program (case sensative)
6- Click "Generate Key" and copy the beta key into the AlphaRev.exe program (case sensative) and press Enter
Congrats!! you should now have S-Off. If fail, check the alphanumeric serial and key for accuracy
_____________________________________________________________________________________________________________​
Install Clockwork Recovery
Download CWM 2.5.0.1 OR CWM 2.5.1.7 Off-Mode(no annoying recovery screen while charging)
Download Android Flasher
1- Extract Clockwork Recovery.zip to folder
2- Connect Phone with data cable then Run Android Flasher
3- Check box "Recovery" and click Begin
4- Navigate to Clockwork Recovery folder extracted earlier and select "Recovery.img" click Open
Once complete the phone will boot into recovery
If you made a Nandroid backup before running AlphaRevX it can now be restored
NOTE: you may also install CWM using ADB command, but this is much quicker
___________________________________________________________________________________________________________​
How To Install Superuser Permissions
Three options to aquire this:
1- Restore your Nandroid backup from CWM Recovery
2- Install a Custom ROM which includes SU
3- Follow the steps below to add SU to the Stock 2.2.2 ROM
Newer SU 3.0.6 Signed
-Older SU 2.3.6.1
-Copy SU_2361.zip to SD Card
-Boot into CWM Recovery
-Select Install Zip file from SD
-Select Choose Zip File
-Select SU-2.3.6.1-ef-signed.zip and confirm install
-Reboot and you now have SU in the App Drawer
Enjoy!! and please support the Dev's that make this possible
Thanks for creating a guide.
zedbra said:
How To Install Superuser Permissions
-Download SU 2.3.6.1
-Copy SU_2361.zip to SD Card
-Boot into CWM Recovery
-Select Install Zip file from SD
-Select Choose Zip File
-Select SU-2.3.6.1-ef-signed.zip and confirm install
-Reboot and you now have SU in the App Drawer
Click to expand...
Click to collapse
Just wanted to point out that this step is OPTIONAL. This will allow you to acquire root with your default, stock ROM. However, if you intend to install a custom ROM (Cyanogenmod, Liberated, etc.) then you should just skip this step entirely and go straight to installing the ROM of your choice.
Sweet write up! If I'm not busy this weekend, I may take a jab at it. Thanks duder.
Finally, a well done step by step writeup, that pulls all of the pieces together along with the necessary links.
Well done.
Thanks
Thank you for the comments guys!!
@drumist thanks for pointing that out. this was explained in the guide i made on other forums. fixed it here now
@cHarley04 the download for 2.2 RUU is linked in the Aria Superthread, which is linked in the first step on how to S-Off
maybe i will include the direct link for simplicity
I was just about to do this and went to alpharevs sight and the windows download link is replaced with, "windows version is under review, sorry". Noooo! I'm off today, kids and wife are asleep and my little little aria almost saw the future. Oh well, next weekend hopefully that puppys up and running. I know there's a Linux download link but I like sticking to what I always use, sucky windows.
tommyguns818 said:
I was just about to do this and went to alpharevs sight and the windows download link is replaced with, "windows version is under review, sorry". Noooo! I'm off today, kids and wife are asleep and my little little aria almost saw the future. Oh well, next weekend hopefully that puppys up and running. I know there's a Linux download link but I like sticking to what I always use, sucky windows.
Click to expand...
Click to collapse
same here
got excited at the first sight
but...
Yeah I would have no idea how to run a virtual linux instance so I could do this... hopefully AlphaRev gets the windows version cleared soon, so I can root and use wifi hotspot.
Suleeto said:
Yeah I would have no idea how to run a virtual linux instance so I could do this... hopefully AlphaRev gets the windows version cleared soon, so I can root and use wifi hotspot.
Click to expand...
Click to collapse
Vm player is easy to set up a virtual machine with and you can get it free from vmware.
Sent from my Liberty using XDA App
mtnlion said:
Vm player is easy to set up a virtual machine with and you can get it free from vmware.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
this is true, you could also burn the live ubuntu CD. then just boot PC from CD Rom
EDIT: Windows support is back online
yay!!!
got s-off but now im trying to load off mode charging recovery through android flasher and its giving me ERROR: the process adb.exe not found and fastboot.exe not found?n Ive downloaded and extracted it and try opening through android flasher and when i click on the image file a pop up says, adb is not recognized as an internal or external command. How do i go about installing a recovery?
Have you got the recovery.img out and put it on your download folder?
Signatures are fancy.
im trying to understand attn1 instructions and im stuck at #4. Extract recovery.img from the archive to the same directory/folder/map as fastboot? where can i find this? Thanks for the fast response. noob alert!
tommyguns818 said:
im trying to understand attn1 instructions and im stuck at #4. Extract recovery.img from the archive to the same directory/folder/map as fastboot? where can i find this? Thanks for the fast response. noob alert!
Click to expand...
Click to collapse
open up the clockworkrecovery rar with winrar or a program like it and youll see a file that says recovery.img that's the file you'll want to extract into the adb folder with the fastboot.exe
so guys is this still for only 2.1 users or can you already have the 2.2.2 installed
bkeaver said:
so guys is this still for only 2.1 users or can you already have the 2.2.2 installed
Click to expand...
Click to collapse
This is specifically for, 2.2.2
The first step in the process, is to upgrade to 2.2.2 if you don't have it.
If you already have 2.2.2, you just skip that step.
cHarley04 said:
This is specifically for, 2.2.2
The first step in the process, is to upgrade to 2.2.2 if you don't have it.
If you already have 2.2.2, you just skip that step.
Click to expand...
Click to collapse
let me ask 1 more way so that I am not mis-understanding..
if my wife took the OTA update from AT&T and it upgraded her phone to 2.2.2 which put the security in place preventing you from rooting this will allow me to undo that?
sorry for the extra question
I'm a knucklehead sandwich!!!! I was missing the fastboot.exe!! It was late and I was a few beers deep. All good now. S-off woooohooo!!!!!
bkeaver said:
let me ask 1 more way so that I am not mis-understanding..
if my wife took the OTA update from AT&T and it upgraded her phone to 2.2.2 which put the security in place preventing you from rooting this will allow me to undo that?
sorry for the extra question
Click to expand...
Click to collapse
Yes!!!
Sent from my HTC Aria using XDA App
@Tommyguns, glad you got iy M8
@bkeaver, yes the guide is for factory phones with 2.2(same as OTA update), and for those who want to upgrade from 2.1 using the 2.2 update RUU.
pretty sure it says that in the guide, but i will check and make adjustments for clarity if needed
Edited first post. also please take special attention to anything posted in RED
zedbra said:
Requirements you must have:
*All Drivers installed on Windows PC (See Aria Superthread)
*Aria S/W v2.2.2 (either from the Update RUU or Factory Shipped)
***WARNING*** Installing the Aria Update RUU will format the phone. Any info not backed up will be lost. SD Card is not affected
---If you have ClockworkMod installed you can make a Nandroid backup which can be restored later
*HBOOT 1.02 (installs with the Update RUU)
Click to expand...
Click to collapse

[HOW-TO]Heimdall One-Click - ROM Packaging and Distribution System

Introduction
Heimdall One-Click is a open-source stack of software intended to eliminate our dependence on Odin and provide an unrivaled safe method to perform a complete flash of a device. Heimdall One-Click will work on any device which Heimdall covers. Heimdall One-click and Heimdall One-Click Packager can be used to distribute custom or stock firmware upgrades or downgrades currently on most Samsung devices. Each of the sections in this post could be an entire post on its own. I want to consolodate this information into a single area here on XDA.
Heimdall One-Click is a project which I have been perfecting for months. After 147 revisions I feel it is time to release. It is my hope that the use of this software will enable users to safely flash and understand what is going on while they are flashing firmware. Heimdall One-Click is based on Heimdall by Benjamin Dobell.
The basic outline goes like this...
Obtain firmware
Use Heimdall frontend to package a tar.gz
Select your tar.gz file with Heimdall One-Click. Your final package will be a executable cross-platform JAR file for redistribution which will deploy everything needed to flash your ROM.
{
"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"
}
It's really that simple. See the Downloads and Source section. I will now discuss how everything works in depth.
Warning
You have the power to damage your device and others! Several times during the development cycle I had asked myself if it was ethical to release a packager. A lack of skill can easily brick a device. Building a flashable package is a skill and I do not want to see any One-Click Nukes released into the public. So I want to set some rules-of-thumb:
1. If you are unsure, do not package bootloaders into a distribution.
2. If you are going to package bootloaders, include boot.bin, Params.lfs, Sbl.bin and repartitioning option should be checked.
3. Always flash the firmware from Heimdall-Frontend before creating a one-click. Never assume it will work.
4. Please watch this video in its entirety before attempting to package a one-click.
Heimdall & Heimdall Frontend
Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung devices. Heimdall is an "upstream package" contained within Heimdall One-Click. Heimdall is Maintained by Benjamin Dobell http://forum.xda-developers.com/member.php?u=2710388 from Glass Echidna. Heimdall has its own discussion thread here: http://forum.xda-developers.com/archive/index.php/t-1104826.html
Heimdall Frontend allows a graphical user interface for flashing firmware, packaging and deploying Heimdall tar.gz files. It also provides several additional tools. Heimdall Frontend has its own discussion thread here: http://forum.xda-developers.com/archive/index.php/t-1104826.html
Heimdall One-Click Packager
Heimdall One-Click packager is a tool which will take a Heimdall tar.gz file and package it into a Heimdall One-Click. Heimdall One-Click Packager is an open-source cross-platform(win/linux/mac) program with no dependencies. After execution, the user selects a tar.gz package for one-click and the program:
1. Decompresses firmware.xml from tar.gz
2. Deploys an empty one-click java jar.
3. Writes the Tar.gz and firmware.xml into the one-click jar thereby creating a new one-click executable firmware package.
Heimdall One-Click
Heimdall One-Click's job is simple; it deploys firmware with one click while keeping the user informed. Heimdall One-Click is an open-source cross-platform(win/linux/mac), dependency installing, easy-to-use, automation tool which can install firmware onto a device in download mode. Heimdall One-Click's operation is very simple from the outside, but the operation is very complex inside. See source code for more information. Heimdall One-Click has several safety features built in which make it the safest method of deploying firmware to any compatible device.
Why use Heimdall One-Click over Odin or other methods of software distribution?
Heimdall is Open-Source software. Without Open-Source software we would not have android or custom ROMs. Open-Source developers should support and expand the work of other Open-Source developers.
Odin is closed source and propritary. Not only is the application proprietary, but the drivers are also proprietary. Open-Source developers do not support Closed-Source work as it is a hindrance to development.
Heimdall supports Open-Source Tar.GZ compression which ensures file integrity and provides higher compression than zip formats. A 500 megabyte ROM can compress to less than 200 megabytes.
Heimdall can restore operation to a device which does not even have access to recovery mode. Heimdall does not require the kernel to be operational, it works at a higher level in the Secondary Bootloader.
A Heimdall One-Click is a single executable file which contains everything needed to flash a ROM.
A Heimdall One-Click works on Windows, Linux or Mac OS-X.
A Heimdall One-Click is not a final output format. Once you make a One-Click, the contents are not lost forever. The ROM package contained within can be unzipped using your favorite archive program, modified and redistributed.
Easiest, most portable, and foolproof method of flashing
Heimdall One-Click has been designed to be the easiest, most portable and foolproof method of flashing. The requirements are that the user knows how to put their device into "Download Mode" and that the user has Java installed on their computer.
Heimdall One-Click contains:
A deployable and unpackable firmware located in /com/adamoutler/heimdalloneclick/
Installer routines
Windows Drivers
Windows C++ Redistributable Package
Windows Heimdall binary
Linux32 Debian package
Linux64 Debian package
Mac OS-X Installation package
You can find a repository of prepackaged ROMs here at the Team Komin website: http://files.teamkomin.com/ Please note, some of these were packaged during beta testing so not all of them are high quality builds.
Obtaining firmware
Before you can package a ROM for distribution, you must have firmware to package. Here are two methods of obtaining firmware.
Obtaining firmware from a live device
The following commands can be used on most Samsung Android devices to make a backup of everything but bootloaders. Bootloaders must be obtained from official builds and cannot be pulled off a working device after you have finished developing. This may not work on devices designed for RFS filesystems if the filesystems have been converted
Open a terminal to your device (terminal emulator or QuickSSHD, or adb shell)
Enter the following commands into the terminal
Code:
su
#Remove the target folder if it is present
rm -r -f /sdcard/firmwarepackage
#Write all zeros to data partition to zero flash memory until the partition is full
dd if=/dev/zero of=/data/big_zero bs=1048576
#Remove the zerod out dummy file
rm -r -f /data/big_zero
#Mount The /system folder as RW so we can read and write to it
mount -o remount,rw /system /system
#Drop all zeros into a file on the /system partition until it is full
dd if=/dev/zero of=/system/big_zero bs=1048576
#Remove the zerod out dummy file
rm /system/big_zero
#Make our folder to write the firmware package onto the SDCard
mkdir /sdcard/firmwarepackage
#Begin transfer of all relevant blocks to sdcard
dd if=/dev/block/stl9 of=/sdcard/firmwarepackage/factoryfs.img bs=4096
dd if=/dev/block/bml7 of=/sdcard/firmwarepackage/zImage bs=4096
dd if=/dev/block/stl10 of=/sdcard/firmwarepackage/dbdata.img bs=4096
dd if=/dev/block/stl11 of=/sdcard/firmwarepackage/cache.img bs=4096
dd if=/dev/block/bml12 of=/sdcard/firmwarepackage/modem.bin bs=4096
#Done
echo done
copy the files from your sdcard in the firmwarepackage folder to your desktop/laptop computer.
Never mount an RFS filesystem to your computer Your computer is not equipped to handle the RFS filesystem. All permissions data will be lost and the filesystem will be rendered useless.
Using Heimdall Frontend, you can download the part.pit from the options tab to obtain the partition tables for custom ROM use.
Use Heimdall frontend to package a tar.gz
Use Heimdall One-Click Packager to make a One-Click
Obtaining firmware from Odin packages
You will need a base firmware package to obtain bootloaders for your device. Firmware can be obtained from several sites. Some of the more common are:
http://Xda-developers.com developer forums
http://rootzwiki.com
http://sammobile.com
http://samfirmware.com
http://sampro.pl
It is important that these firmwares be verified on your own device before distribution.
Totally decompress the entire firmware package down to its individual files
Use heimdall-frontend to create a package
Use One-Click Packager to generate a one-click.
Recommended Distribution Instructions
Once you have verified that your package has been made correctly, you will want to distribute it. Here is a recommended blurb which I have found to be effective from multiple tests. Replace "MY ROM" with your ROM name and MYROM.COM with your download link.
You will need Java installed on your computer Do you have java?
right click and open with Java
Put your device in "Download Mode" and click the flash button
Problems? Enter "Recovery Mode" and select "factory reset"
Download MY ROM!
Code:
[ list=1]
[ *]You will need Java installed on your computer [url=http://www.java.com/en/download/installed.jsp?detect=jre&try=1]Do you have java?[/url]
[ *]right click and open with Java
[ *]Put your device in "Download Mode" and click the flash button
[ *]Problems? Enter "Recovery Mode" and select "factory reset"
[/list]
[ size=4][ url=MYROM.COM]Click here to Download My ROM![/url][/size]
Downloads and Source
Heimdall One-Click Packager: http://code.google.com/p/heimdall-one-click/downloads/list
Heimdall Frontend: http://www.glassechidna.com.au/products/heimdall/
Heimdall One-Click Source Code:http://heimdall-one-click.googlecode.com/svn/trunk/
Heimdall one-Click Change Log:Change Log: http://code.google.com/p/heimdall-one-click/source/list
Heimdall Source Code: https://github.com/Benjamin-Dobell/Heimdall
Conclusion and Disclaimer
The source and applications are released under the MIT License. I have provided these resources at no cost to you without warranty. I will not be held liable. It is up to you to use these programs responsibly.
History
Heimdall One-Click saw its first appearance as "One-Click UnBrick http://forum.xda-developers.com/showthread.php?t=1153310". Since then, it has been tested and distributed as part of UnBrickable Mod, restoration back to stock, and upgrading firmware in the following threads:
http://forum.xda-developers.com/showthread.php?t=1191924 http://forum.xda-developers.com/showthread.php?t=1331381 http://forum.xda-developers.com/showthread.php?t=1330491 http://forum.xda-developers.com/showthread.php?t=1341666 http://forum.xda-developers.com/showthread.php?t=1312391 http://forum.xda-developers.com/showthread.php?t=1333423 http://forum.xda-developers.com/showthread.php?t=1333424 http://forum.xda-developers.com/showthread.php?t=1238093 http://forum.xda-developers.com/showthread.php?t=1266172
http://forum.xda-developers.com/showthread.php?t=1323527 http://forum.xda-developers.com/showthread.php?t=1288130 http://forum.xda-developers.com/showthread.php?t=1216790 http://forum.xda-developers.com/showthread.php?t=1221491
Forward
We are looking to expand Heimdall to work on more devices. We need devices to work with. Please see http://www.glassechidna.com.au/open for more information
RFS is full of bugs, you cannot read/write RFS filesystems on any computer.
RFS is prone to corruption (in many more ways you can expect)
RFS doesn't have a "packer" that zeroes empty portions in order to get filesystem images with good compressibility (IE: free space will be by default full of junk)
Also, compared to the well established update.zip format: this method doesn't provide a clean method to execute post-flashing scripts.
Why I advice not using the method described here to distribute custom ROMs as RFS.
However, distributing official firmwares in this format could be nice, but I'm not sure it's worth the hassle of re-packaging.
Note: for Ext4 based ROMs and devices like Galaxy S II or Galaxy Tab 10.1, this tool can make sense (ext4 fs packing tools are available in AOSP)
Yay!!! Thanks again
Sent from my SGH-I897 using xda premium
Supercurio, your notes on RFS are appreciated, but irrelevant if the guide I've provided is followed.
As a precaution, never mount an RFS Filesystem to your computer directly. It will corrupt the filesystem and Voodoo Lagfix will fail and bootloop. Apply Voodoo Lagfix after pulling the partitions. Flash a kernel, reboot, then pull partitions. This way you can mount it on your computer.
why to use this? using this method you will be able to ensure what is on your device is on your user's device. Rather than expecting that they are running a certain version of a certain firmware prior to applying an update.zip Heimdall One-Click also provides the easiest method to installing a custom kernel in order to get ClockWork Mod on a stock device.
As Supercurio mentioned, repackaging an odin file as a Heimdall One-Click may be a hassel, but Heimdall One-Clicks work on Linux, Windows or Mac OS-X.
I'm not going to go through all methods of development nor the functions of each file. However, if you wish to perform a factory reset, use a params.lfs from an official firmware package. If not, use the params from an active device.
There's downfalls to each method of distribution.
Update.zip requires that the user have a specific version of a specific firmware on their device. Heimdall One-Click does not require this.
Update.zip allows modification of firmware on a device. Heimdall One-Click will obliterate all firmware.
Update.zip is exactly as it says, it is an update. Heimdall One-Click is an entire firmware package.
Update.zip requires knowledge of a proprietery scripting format. Heimdall One-Click requires knowledge of Android filesystems only.
For this reason, packaging as a Heimdall One-Click makes your firmware package immortal rather than having a lifespan/dependency. A properly packaged Heimdall One-Click will always work without any expectation of the firmware on a user's device. It's a very clean way to distribute firmware.
Awesome piece of software, incredibly easy to use, and extremely useful. Thanks for releasing this to the community!
Thank you!
I have a 1007 Captivate and Odin / Keis were unreliable at best.
I'd love to see some Odin 1-Click repackaging for this. I could use them!!!
Downloads / upgrades with the Heimdall method have been easy to monitor and and
part that failed could easily be retried.
Without the Odin 1-click to stock being available (or failing, leaving me in an unknown state), I found the ability to use PIT, and target each section of the ROM to be critical in booting a new ROM if there is any reason the upgrade went awry from within Android.
Stock ROMs repackaged will help Odinphobes!
Erbid
Adam,
Does Heimdall frontend know which cache and dbdata file to use from a stock package, or do i need to manually select them? I've noticed that in a full package, there is a cache and dbdata file in two different places, but I do not know which one should be used. Also, should the param.lfs file be used only if flashing bootloaders, or should it always be included?
Edit
I am using stock firmware for a Captivate.
mrhaley30705 said:
Adam,
Does Heimdall frontend know which cache and dbdata file to use from a stock package, or do i need to manually select them? I've noticed that in a full package, there is a cache and dbdata file in two different places, but I do not know which one should be used. Also, should the param.lfs file be used only if flashing bootloaders, or should it always be included?
Edit
I am using stock firmware for a Captivate.
Click to expand...
Click to collapse
Dbdata goes in dbdata. Cache goes in cache. Paramaribo is a bootloaders. Watch the video.
Ok, I watched the video (great tutorial,btw), but I still don't know what to do about my problem. In a stock captivate package, there is a dbdata and cache file in the pda package, and another dbdata and cache file in the csc package. Which one gets used and which one gets tossed?
mrhaley30705 said:
Ok, I watched the video (great tutorial,btw), but I still don't know what to do about my problem. In a stock captivate package, there is a dbdata and cache file in the pda package, and another dbdata and cache file in the csc package. Which one gets used and which one gets tossed?
Click to expand...
Click to collapse
Just use one or the other.
Ok, thanks.
Just so I know, what does the dbdata and cache files do? What is in them?
mrhaley30705 said:
Ok, thanks.
Just so I know, what does the dbdata and cache files do? What is in them?
Click to expand...
Click to collapse
The database data and cache. Dbdata is where things like contacts are stored. Cache is where application preloading data is stored.
Ok, thanks again.
Any chance you are going to attempt a mobile Heimdall, similar to Mobile Odin I've been hearing about?
mrhaley30705 said:
Ok, thanks again.
Any chance you are going to attempt a mobile Heimdall, similar to Mobile Odin I've been hearing about?
Click to expand...
Click to collapse
No. ThaT method requires the device to be running and be rooted. This is way more valuable. I had considered it... until we figure out how to flash a PBL, that wont happen. Like, the software on the device, modifies the PBL as it is written.
I finally had a chance to try this. It is so easy. Your video is spot on (love the Spider Man reference ) This is so much easier than making a tar.md5 file for Odin.
One question, in your video, I noticed your terminal screen was transparent. How did you do that? It looks cool.
this seems to be a very valuable tool for developers and I am very glad you posted it,,watched the video,,sounds like a good thing,, could not see what you were doing,,read the post repeatedly,,yep this will be useful to the devs,, truly had hoped it would be useful to those of us on here that have figured out how to follow instructions and flash roms but really do not understand what we are doing,,now I understand why odin is so useful,,it allows people to do the job without knowing how to make the tools to do the job ( although I would like to learn that) unfortunately this seems to be a common "open source" mindset,,thats why apple sells so many overpriced machines,, they expect people to know nothing and intend to keep them that way,,so their machines are simplified and locked,, but they work without having to know how to program them,,without having to understand the whole command line BS,,yes I am guilty of being uneducated,,I am not guilty of being stupid,, I do not use tools or equipment that assumes I do not know,, I do not use tools or equipment that assumes I know more than I do,,I will continue to follow this because I still have hopes it will become useful,,to the common run of the mill user,,thanks for your work,, it is impressive,,now to get it useable to those of us that do not have years of programming experience,,that went to school when punch cards were still in existance
stayintwisted said:
this seems to be a very valuable tool for developers and I am very glad you posted it,,watched the video,,sounds like a good thing,, could not see what you were doing,,read the post repeatedly,,yep this will be useful to the devs,, truly had hoped it would be useful to those of us on here that have figured out how to follow instructions and flash roms but really do not understand what we are doing,,now I understand why odin is so useful,,it allows people to do the job without knowing how to make the tools to do the job ( although I would like to learn that) unfortunately this seems to be a common "open source" mindset,,thats why apple sells so many overpriced machines,, they expect people to know nothing and intend to keep them that way,,so their machines are simplified and locked,, but they work without having to know how to program them,,without having to understand the whole command line BS,,yes I am guilty of being uneducated,,I am not guilty of being stupid,, I do not use tools or equipment that assumes I do not know,, I do not use tools or equipment that assumes I know more than I do,,I will continue to follow this because I still have hopes it will become useful,,to the common run of the mill user,,thanks for your work,, it is impressive,,now to get it useable to those of us that do not have years of programming experience,,that went to school when punch cards were still in existance
Click to expand...
Click to collapse
what?
get some firmware, make a heimdall package, run the one-click maker. No matter what level you're at, this is as easy as it gets. It does not get easier.
ok sorry to have bothered you,, I will try to find someplace to learn enough to understand what you consider stupidly simple,,I will just stick to odin and cwm they just work,,was my error for thinking that you would be able to write at a level I would understand,, but it is still going to be a very useful tool for those who can use it and I thank you for the work you have put into it
stayintwisted said:
ok sorry to have bothered you,, I will try to find someplace to learn enough to understand what you consider stupidly simple,,I will just stick to odin and cwm they just work,,was my error for thinking that you would be able to write at a level I would understand,, but it is still going to be a very useful tool for those who can use it and I thank you for the work you have put into it
Click to expand...
Click to collapse
If you're not a developer, you don't have anything to package and this thread does not apply to you. The end result is a one-click and probly is what you are looking for. This tool is for packaging your work. You must have something to package.
This IS super simple. I did it. On2 different operating systems. It's literally point and click, but a minimal amount of typing involved. And i am no good at command line. I also don't claim to be a developer, or even an advanced user.

I9100][rom 4.1.2 xxlsj [Cleaned Thread]

All credits goes to Izap for leak​
Before making any post about how to, why doesn't this work? what do i do know, help. please read 1.st and second post where i will write and answer as many questions as possible!
Before flashing this rom, make sure you have a fully working backup in case you want to go back to your old rom
Consider that this may brick your phone if you doing it wrong, however we will provide information for a successful flash​
Thank You @yahyoh (See More at http://forum.xda-developers.com/showpost.php?p=34184248&postcount=581)
{
"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"
}
CHECKSUM.md5 so you can additionally check if above are correct before flashing.
Flashing this will wipe your device.
Screenshot included so you can see its legit.
PDA - LSJ
Modem - LS6 (GSM version)
CSC - LS1 Open version
SGS II XXLSJ Review
Thank You @prads5801
http://www.androidnova.org/official-jelly-bean-leaked-for-samsung-galaxy-sii/
LINKS
PDA
Thank You @layercake87
part1: http://www26.zippyshare.com/v/7484635/file.html
part2: http://www26.zippyshare.com/v/15776471/file.html
part3: http://www26.zippyshare.com/v/15844801/file.html
Magnet Link (EMMC/PDA/MODEM/CSC)
Thank You @DimICE
MagnetURL
Torrent Link
Thank You @ingbrzy
http://uloz.to/xnTcG9P/i9100xxlsj-zip
Google Drive
Thank You @fr3nlysmil3
GoogleDrive
Sammobile Link
Thank You @Sammobile
hotfile.com/dl/179607505/5cd1648/I9100XXLSJ_I9100OXXLS1_OXX.zip.html
Flashable Modem
Thank You @Bieniu
https://www.dropbox.com/s/sn7f0rp6eo9amv8/Modem_I9100XXLS6_CWM.zip
How to Root
Here!
How to get Ripple Lockscreen With 4 Icons/Smart Rotation (Odexed Only!)
Thank You @jarari2
http://forum.xda-developers.com/showthread.php?t=1997919
How to get Ripple Lockscreen With 4 Icons/Smart Rotation (Deodexed Only!)
Thank You @LegendK95
http://forum.xda-developers.com/showthread.php?t=1998682
How to get transparent statusbar (Deodexed Only!)
How to change dpi
Thank You @ paper_heart_21
http://forum.xda-developers.com/showthread.php?p=34342269
Thank You @nims11
http://forum.xda-developers.com/showthread.php?t=1999407
Custom Kernel
How to get more toggles/black statusbar
Thank You @Mirko ddd
http://forum.xda-developers.com/showthread.php?p=34303835#post34303835
How to get 4 Way Reboot *Deodexed*
Thank You @mythtrandyr
http://forum.xda-developers.com/showthread.php?t=1999598
How to get Popup Browser
Thank You @Gyebro
http://forum.xda-developers.com/showthread.php?t=2001818
Rooted/CWM/More Secure Kernel
Thank You @Phil3759
http://www.mediafire.com/file/p5r503u1run77w2/PhilZ-cwm6-XXLSJ-OXX-3.1-signed.zip
http://www.mediafire.com/file/6gpa6xclotu36uj/PhilZ-cwm6-XXLSJ-OXX-3.1.tar.md5
Flash Instructions
Thank You @MajorAly
http://forum.xda-developers.com/showpost.php?p=34219382&postcount=1463
Problems/Solutions
MRNoob Wrote
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
MD5 hash value is invalid
CODE_I9100XXLSJ.tar.md5 is invalid.
End...
Sorry im a noob, what to do
Click to expand...
Click to collapse
Simply rename the CODE_I9100XXLSJ.tar.md5 to .tar
ant987 said:
NOBODY is reading the suggests given by a lot of users! Change the extension from .MD5 to .TAR
Click to expand...
Click to collapse
I Think Many people needs to apologise to Izap for flaming/hating him
This is how it will be if you don't try to read the op
it will be constantly update a few hours forward
Does this have ripple effect?
Yes but its been disabled for our DPI resolution however you can set 180 DPI and reboot and ripples will be there
Can i use Syiah/DorimanX kernel?
NO! as they haven't updated their kernel for this leak
My SIM is locked, now what?
Try restore IMEI from earlier release or download This and do as BANK$ did
BANK$ said:
i installed a 4.0.4 official rom and unlocked again with this app..then i installed jb again with no problems
Click to expand...
Click to collapse
About the 50GB Dropbox space, will i get it?
If you didn't get it while the S3 Giveaway was out then yes, if you got the space and still have it then no
Does this leak support Multi-View?
No & samsung haven't planned to add this feature to our device.
Do we have the palm features as in S3?
No this was also deleted in 4.1.2
How do i take a screenshot?
Press and hold HOME+POWER button
How can i revert to my old rom
You can either flash a CWM flashable and restore from there or flash a safe kernel and restore from there
will this format my internal sd card
No, it will not wipe your internal SD-Card
Basic Information of the files
emmc_EXT4_16GB.pit.html (PIT NOT NEEDED/NOT RECCOMENDED)
emmc_EXT4_32GB.pit.html (PIT NOT NEEDED/NOT RECCOMENDED)
CODE_I9100XXLSJ.tar PDA (ODIN)
56160234/MODEM_I9100XXLS6.tar.md5.html Phone
CSC_HOME_OXX_I9100OXXLS1.tar.md5.html CSC (Mobile Odin = Cache)
###############################################
# #
# GT-I9100 Kernel MMC_CAP_ERASE bug detection #
# By Tungstwenty - forum.xda-developers.com #
# [email protected] #
# #
###############################################
Detecting safety of kernel: zImage
Kernel: Linux version 3.0.31-462349 ([email protected]) (gcc version 4.4.3 (GCC) ) #3 SMP PREEMPT Tue Nov 6 02:42:23 KST 2012
1 ocurrences of the bad code signature
0 ocurrences of the good code signature
***************
!!! WARNING !!!
***************
The kernel appears to have MMC_CAP_ERASE *enabled*, which is dangerous on many devices
Unpacked kernel code stored at: zImage_unpacked
The unsafe instruction can be found at offset 0x0061ea10
Click to expand...
Click to collapse
you know how you can make the rom deodexed?
there wasnt a need for a new thread
i ll post the rooting method here again if this is main thread now
Easiest way to install the ROM achieve root and CWM recovery:
(make sure your battery is over 50%)
Download the firmware
extract the files and rename the tar.md5 files to .tar (remove the .md5 part)
Download Philz rooted kernel
Download Mobile Odin
copy all the files to your phone
Install mobile odin
open it and let it check for missing files
if u are using the free version u will need to download the flash kernel from chainfire's thread
In Mobile Odin:
go to Open file browse to the folder you copied files in and select the CODE_I9100XXLSJ file
go to Open file again and browse to CSC file do the same for the modem file
Now go to Open file and select Philz kernel
Select wipe data and dalvic cache to avoid running in any errors
this way mobile odin will flash this kernel rather than the stock non rooted kernel
Flash the firmware
your phone will reboot into mobile odin's special recovery and will flash the firmware
the phone will reboot some times just done worry leave it on table
After the phone boots pat your self on the back for doing a good job and thank Samsung for finally providing a good stock firmware since the gingerbread days
View attachment 1486422
bluefa1con said:
there wasnt a need for a new thread
i ll post the rooting method here again if this is main thread now
Easiest way to install the ROM achieve root and CWM recovery:
(make sure your battery is over 50%)
Download the firmware
extract the files and rename the tar.md5 files to .tar (remove the .md5 part)
Download Philz rooted kernel
Download Mobile Odin
copy all the files to your phone
Install mobile odin
open it and let it check for missing files
if u are using the free version u will need to download the flash kernel from chainfire's thread
In Mobile Odin:
go to Open file browse to the folder you copied files in and select the CODE_I9100XXLSJ file
go to Open file again and browse to CSC file do the same for the modem file
Now go to Open file and select Philz kernel
Select wipe data and dalvic cache to avoid running in any errors
this way mobile odin will flash this kernel rather than the stock non rooted kernel
Flash the firmware
your phone will reboot into mobile odin's special recovery and will flash the firmware
the phone will reboot some times just done worry leave it on table
After the phone boots pat your self on the back for doing a good job and thank Samsung for finally providing a good stock firmware since the gingerbread days
View attachment 1486422
Click to expand...
Click to collapse
it is indeed as this is a clean thread where no one need to constantly ask over and over again
and .zip for CWM Recovery flashing please Many people like dualboot, maby rooted... or unrootet but for CWM for dualboot.
Thank U
xmyszka said:
and .zip for CWM Recovery flashing please Many people like dualboot, maby rooted... or unrootet but for CWM for dualboot.
Thank U
Click to expand...
Click to collapse
u cant dual boot this rom with any kernel so there us no point
xmyszka said:
and .zip for CWM Recovery flashing please Many people like dualboot, maby rooted... or unrootet but for CWM for dualboot.
Thank U
Click to expand...
Click to collapse
+1
Yeah it's clean now and after 2~3 pages you will have the same questions again and again
1. Is ripple effect working?
2. How to root
3. Is Siyah working?
4. I got simlocked
5. Do i need PIT?
6. Installed Dorimanx kernel and now my phone wont boot
etc etc
Spyr0s said:
Yeah it's clean now and after 2~3 pages you will have the same questions again and again
1. Is ripple effect working?
2. How to root
3. Is Siyah working?
4. I got simlocked
5. Do i need PIT?
6. Installed Dorimanx kernel and now my phone wont boot
etc etc
Click to expand...
Click to collapse
1. No
2. Use Philz rooted kernel
3. No
4. N/A
5. NO
6. Reflash
just wondering can we change the dpi??? editing the .prop ... ehmmmm
downloading this later
cruzzmz said:
1. No
2. Use Philz rooted kernel
3. No
4. N/A
5. NO
6. Reflash
just wondering can we change the dpi??? editing the .prop ... ehmmmm
Click to expand...
Click to collapse
yes you can 180 is the most ive seen for now
I'm still having problems with network lock. No software can unlock my phone while on JB. EFS Pro can restore unlocked version of my /efs but after a restart it all changes back (different md5sums of nv_data.bin files) - everything works fine on 4.0.4
I'm using PhilZ-cwm6-XXLSJ-OXX-3.1 kernel.
When on 4.0.4 EFSPro says that efs file type is "/EFS" but when on JB: "EXT4" and different permissions(-rwx------ on JB vs -rwxr-xr-x on 4.0.4)
adb remount doesn work.
Recovery backup of JB takes 16.5MB(boot.img and recovery.img take 8MB each), cache, data and system have .dup extension(funny thing is, I can still restore it and have fully working JB rom, wtf)
I tried to manually copy the nv_data.bin and changed its permissions and owner/group, still nothing. Any ideas what can be causing it?
phini said:
I'm still having problems with network lock. No software can unlock my phone while on JB. EFS Pro can restore unlocked version of my /efs but after a restart it all changes back (different md5sums of nv_data.bin files) - everything works fine on 4.0.4
I'm using PhilZ-cwm6-XXLSJ-OXX-3.1 kernel.
When on 4.0.4 EFSPro says that efs file type is "/EFS" but when on JB: "EXT4" and different permissions(-rwx------ on JB vs -rwxr-xr-x on 4.0.4)
adb remount doesn work.
Recovery backup of JB takes 16.5MB(boot.img and recovery.img take 8MB each), cache, data and system have .dup extension
I tried to manually copy the nv_data.bin and changed its permissions and owner/group, still nothing. Any ideas what can be causing it?
Click to expand...
Click to collapse
Pay $2.5 and you will get rid of the lock FOREVER. You can use the app as many times you want (however there shouldnt be a need).
Use GalaxSim: fast, easy, cheap and hassle free
Are we have chances to get ripple effect working? Or maybeb it will be in final release?
Sent from my GT-I9100 using xda premium
dorian95 said:
Are we have chances to get ripple effect working? Or maybeb it will be in final release?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Does this have ripple effect?
Yes but its been disabled for our DPI resolution however you can set 180 DPI and reboot and ripples will be there
READ please!
Sent from my GT-I9100 using xda premium
Yes I understand, but I wonder why they changed that, whats wrong with ripple on default dpi
Sent from my GT-I9100 using xda premium
dorian95 said:
Yes I understand, but I wonder why they changed that, whats wrong with ripple on default dpi
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
cant tell you. Ask/request samsung
Sent from my GT-I9100 using xda premium
dorian95 said:
Yes I understand, but I wonder why they changed that, whats wrong with ripple on default dpi
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
nothing is wrong, it was smooth on Sprint release, however we can get it to work, i only need to know that file its related to
good job
Great job mate [and thanks for root, mirrors and cwm file]!
I've just notice this thread, but anyways I've update a post with all the mirrors (at the original thread):
[more mirrors]
http://forum.xda-developers.com/showpost.php?p=34224784&postcount=1544

[TOOLKIT] Universal Paranoid Android(PA) Porter[ICS/JB]

Tool Aces Present..
Universal PA Porter
About the tool:
This tool can be used to port the great Paranoid Android ROMs from any device. It's based on the guide of adityalahiri13. Thank him too.
How to use:
Make sure you that both the ROMs(Base and PA) have the same resolution. I recommend taking CM as base. Also make sure that the android versions of base and PA ROM matches. Try to use port from a device of same manufacturer, though it may not matter much.
Steps-
1. Place base ROM zip in CM folder.
2. Place PA ROM zip in PA folder.
3. Now click on Main.bat the tool will do some steps.
4. After this it will ask for your device resolution. Choose one among 5.
5. Then it will open build.prop and another file. Copy the lines from another text file to the build.prop below ro.modversion= and write the PA version you are porting infront of ro.pa.version=
6. Save and exit.
7. Now it will open updater-script and another file. Copy the line from another file and paste it to your updater-script below this line:
Code:
set_perm(1000, 1000, 0644, "/system/etc/paranoid/properties.conf");
8. Then it will ask for your android version. Choose ICS or JB, then it will zip the ROM, select name as desired and find your ROM in /PORT folder.
Congrats on your newly ported ROM.
Downloads:
Download the tool from here.
Screenshot:
{
"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"
}
FAQs:
Q. Well I ported this accordingly but it's stuck in bootloop. How to solve it?
A. In some cases this happens. Simply run bootloop.bat and see if it works. If it still doesn't works then run bootloop2.bat. Make sure to check if the ROM boots after running bootloop.bat, if still stuck on bootloop then only run bootloop2.bat
Q. Why you recommend porting from same manufaturer?
A. Well you can port from others also but in some of them you might need some framework modding and also need to do some modding in kernel. But in most cases even from other manufacturers the ROM should work.
Q. How can I help?
A. Pressing THANKS button would be enough.
Click to expand...
Click to collapse
Credits:
1.adityalahiri13- For such a great guide. Thank him too
2. Paranoid Android Team- For such great efforts on such great ROM.​
Reserved
Sent from my ST21i2 using xda premium
wow it will try this, if heped i ll press thanks
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Diablo67 said:
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Click to expand...
Click to collapse
Sorry can't get ur error properly can u send some screens? Also I've tested it and it works ok.. but still I'll try my best to help u out
Press THANKS if I helped,
Best Regards,
AJ
alokbina is now Abhinav2
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Try hypercam to record or press prnt scrn fast...I do the same..
Press THANKS if I helped,
Best Regards,
AJ
alokbina is now Abhinav2
If the tool isn't running at all for you guys, you are either trying to run the .bat file from within the zip, or you extracted the zip file wrong.
Extract the zip with Winrar.
Just right click the file and select "Extract Files..." than click OK.
I haven't tried porting this yet but the tool itself works just fine.
m4nu4l said:
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Click to expand...
Click to collapse
Extract files to just to short path, for example to "c:\porting\" or "d:\porting\".
This problem shows when .bat is deep in folder.
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
aiinjylls said:
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
Click to expand...
Click to collapse
Now after so many reports I think there's some fault with the tool...though I checked it..still if u can try to get the error it's best..anyways I'll try to fix this today itself
Best Regards,
AJ
alokbina is now Abhinav2
Is this still alive? Just curious, thx.
Sent from my Smooth(ROM) Kindle Fire
Diablo67 said:
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Click to expand...
Click to collapse
m4nu4l said:
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Click to expand...
Click to collapse
aiinjylls said:
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
Click to expand...
Click to collapse
I'm really sorry guyz it was my mistake....fixed the tool now Please forgive me if possible guyz....Enjoy :good:
Cheers,
AJ
Do we redownload?
I took a look at main.bat ( noticed a spelling error in command goto del *it said delco* )
I think Bootloop2.bat may have errors. I get system cannot find specified file
Sent from my Galaxy Nexus using xda premium
Getting SOrry error porting.Please Check you have done everything properly
aiinjylls said:
Do we redownload?
I took a look at main.bat ( noticed a spelling error in command goto del *it said delco* )
I think Bootloop2.bat may have errors. I get system cannot find specified file
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes I fixed the errors and now it will work
nlygamz said:
Getting SOrry error porting.Please Check you have done everything properly
Click to expand...
Click to collapse
I've checked it thrice man...just tell me in detail wat all happens....
Cheers,
AJ
stuck in bootloop....damn man.....the PA logo just goes on and on
I redownloaded and it runs through completely without errors
- it skips the build.prop prompt though
The Bootloop.bat runs smoothly
The Bootloop2.bat always gives me "file not found"
I have not successfully booted a ROM, but its working for me
Sent from my Galaxy Nexus using xda premium
nlygamz said:
stuck in bootloop....damn man.....the PA logo just goes on and on
Click to expand...
Click to collapse
Please run the bootloop batch scripts and then try to do a logcat.
Cheers,
AJ
ran bootloop and bootloop2 ....it runs fine now....just need to do some manual handwork in it! Thanx man! Appreciate your help
---------- Post added at 09:37 AM ---------- Previous post was at 09:18 AM ----------
http://postimg.com/image/138000/paport-137438.jpg <<< Check this out @Abhinav2

V570KL WiFi error fix [need testers]

Hello, I think I found what is the issue with WiFi - Vendor configs don't change WiFi Country code but they do change region and that causes the WiFi error. I was able to unpack the .RAW file to a normal folder and then the system.ISO where I was able to edit the build.prop and vendor props.
I prepared a few methods on how to edit the ROM to make WiFi work:
A) Changed the country code in the build.prop to a chosen country [you won't be able to use WiFi abroad of that country].
B) Edited all the vendor props to change WiFi country code to according countries [should work everywhere].
C) Removed the country code line from build.prop files [may work everywhere or nowhere]. -checked more files in the system and came to conclusion that this method won't work
The edited ROM will have to be flashed using Qualcomm flashing tool as there's no way to repack it to .RAW file.
For testers:
Before flashing copy all your files as they will be removed. Also mind the fact that I don't know if this will work or brick your device [if it does brick it then you can flash an unedited ROM to fix it].
Tutorial how to build your ROM:
1. Go to: https://drive.google.com/open?id=1Iph9eTL6dU_x_LAOt7Z9PN7KbwCAHACn
2. Download V570KL.rar
3. Go to Done2 folder and download system folder and IMG_EXTRACTOR_3.1 software from there. [For extractor software you'll have to download Java and Python]
4. Go to main folder and then go to Patch folder and go to Method C folder and download the folder with your country name [if it's not there contact me].
5. Locate your downloaded files and place them into one folder for easier work on them.
6. Unpack V570KL.rar
7. Copy build.prop file from country name folder and replace the build.prop in system folder with it.
PATCHING system.IMG
8. Open Img_Extractor [you need Python and Java for it to work], choose system.IMG and select Repack option. Now locate the edited system file. When it's selected check the byte number if it's the same as the one that system.IMG in V570KL folder has. If it's the same click Repack and wait till it does it's thing. [If the number is not the same edit it to the same number].
9. Replace the system.IMG in V570KL folder with our patched .IMG file.
PATCHING recovery.IMG
10. Reopen Img_Extractor software and choose recovery.IMG option.
11. Locate recovery.img [it's in V570KL folder].
12. Unpack the file, after unpacking locate the unpacked folder and go to initrd folder that's inside of it and there replace default.prop with default.prop located in country patch folder.
13. Go back to Img_Extractor and repack recovery.IMG
PATCHING ROM
14. Prepare edited system.IMG and recovery.IMG
15. Open V570KL folder and paste our patched IMGs in there [replace the old ones or remove them].
16. Our ROM is now ready.
*note - Img_Extractor has to be run with Admin rights to properly unpack/repack the files.
Flashing Tutorial:
QFIL flashing won't be possible as I couldn't get the needed Firehose file for it to work. There is however a Firehose file for V520KL [Asus Zenfone V] which might work but it's pretty risky to do.
A much safer method then will be to flash V570KL ENG rom first with Asus Flashing tool and on this rom we'll be able to unlock bootloader [open path to flashing edited roms].
There's also the VZW Repair Tool that could help us flash the phone, after the phone is detected the software will download OG Verizon ROM that can be replaced [in our case with the ENG ROM], after it's installed we will be able to flash the edited one.
Flashing tutorial downloads:
Asus Flashing Tool - https://www.asusflashtool.com/ [download version 2.0.1 and put your phone into recovery before connecting it to PC]
VZW Repair Tool - https://drive.google.com/drive/folders/15KAGi4XeKf8lwuJ46XO5LZ1mZLM7f5V1
V570KL ENG ROM - https://drive.google.com/open?id=1cizBJWHG1oDduMcImWAE_jSsbfQ5TJi6
Built ROM downloads:
MethodA - UA + camera2api + removed verizon features - https://drive.google.com/drive/folders/1g7jbq2UxQC1XFzqCUjfCa1XIVq23Vs14
MethodB - universal* + camera2api + removed verizon features - https://drive.google.com/drive/folders/1OYNjKjV8H2mhRpdyROgLCM7AeIxj0emw
MethodC - universal - not releasing
MethodC2 - universal + camera2api + removed verizon apps and features - not releasing
universal* - may not work in Ukraine and Russia as there were no vendor files for those countries in the system, however there was a file called EUCommon that may make it work
Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*
Hi friend, I have this phone. I will be glad to work together, I could not do everything according to your instructions. I guess I don't understand English well. I will be happy to work with you with the help of a team viewer. Please contact me
I edited the ROM but I don't know how to flash it, previous flashing methods for this model don't work anymore because of Asus disabling the only flashing tool with V570KL model, V2 doesn't support this model. I also thought of replacing the .RAW files in Verizon repair tool but I don't know if that would work, can't check that.
Anyway I added ENG rom link.
Hello!
So I just bought this phone online so my son could use Daydream. I'm not on Verizon and the plan was to just use WiFi. Well... I have the WiFi problem. I have worked though multiple other methods to try and find a fix and nothing has worked. I'm at the point where I'm about to try OP's method. Because of the possibility of bricking the device, wanted to check in first to see if anyone has continued to work on the problem or if there are any new developments. Once I make the decision to attempt, I will check in and after to let you know what happens.
Thanks!
Rk
Anyone know how to fix wifi issue on my v570kl without breaking it? I'm from ukraine.
Hi! I need your help solving WiFi problem for V570KL for country "UA". I downloaded your rar file from Google Drive along the path "Asus/Patch/Full_MethodA [Ukraine]/UA [Ukraine]/V570KL_edited.rar".
What do I do next? As I understand it, I need to launch the Asus Flash Tool, enter the phone in the recovery and connect the cable to the computer, then select the V570KL_edited.rar file and start flashing. I am asking for your help.
Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
{
"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"
}
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.
SlenderPL said:
Update: I found a secret menu using this code in the dialer app which let's you turn OEM mode on [it should enable bootloader unlocking!].
Code: *#*#759#*#*
Click to expand...
Click to collapse
After giving up for today, I decided to try this path, and...at least using standard unlocking methods, phone doesn't seem to understand what's happening, haha
ASUS guys really wanted to make this the most impossible, don't they?
Pedreo1997 said:
Well, I know this is a dead thread, still I'm coming here quite interested into recovering an investment in this phone I bought on Amazon, based in the replies of the questions of the product, saying it's unlocked... and surprise! As I placed a Movistar (VE) SIM on it for using, I found that I'm unable to use WiFi.
I've been following this steps for days (since Dec. 26, in fact) and everything has been dead end over dead end.
I can say that I've been looking for an stand-alone/offline version of AFT 1.0.0.72 with no success. I keep getting the error of 'Failed to download the version control file via FTP'.
I'm using 3 computers for this: a W7 32-bit notebook, a W10 64-bit desktop and a W11 64-bit laptop. I'm saying this, because... well, for some reason I've noticed about AFT v2:
In W7, it opens but doesn't recognize the phone battery
In W10, it doesn't even open
In W11, it goes smoothly and read phone battery
I'll add it is crucial AFT v2 reading phone battery (that means, phone turning on normally) because otherwise it doesn't do anything at all.
Anyway, when I tried flashing with AFT v2, it was a dead end because it did nothing (that was after program sending the phone into recovery mode). I tried to manually sideload it with 'adb sideload <filename>' with no success, getting an error message saying it can't read the file.
I opened the .zip files... surprise, .RAW files inside! I've used adb sideload before in Huawei phones, and I know the usual is to see .img files, so... I guess I need to decompress (somehow) the .RAW file. I'll take a look in that later.
Still, I want to attempt first the path suggested of VZWSUATool, just to see if I can somehow force it to install the ENG .RAW software. Right now I'm using the W11 64-bit laptop, but if compatibility problems arise, I'll jump back to W7 32-bit notebook.
Update 1 - 21:48 VET / 2023-01-03
Maybe VZWSUATool is another dead end. I've tried it first on the W11 64-bit laptop and it doesn't even starts (there are 2 library errors). I went back to W7 32-bit laptop, and... turned on normally does nothing, so I went into 'How to Repair...', put the phone into Fastboot but and after passing the FRP question, the "Unsupported device" window came up.
Update 2 - 22:19 VET / 2023-01-03
I decided to throw a risky attempt, basically crossing fingers at this point. I know the (sort of) equivalent model to our V570KL is ZS571KL. In AFT 1.0.0.45, the only option "close" to it is ZS570KL. Yeah, I was attempting something a bit absurd, but had not much to lose.
Another failed atttempt.
(Note: It was in Blue = Connected when it started)
Update 3 - 22:45 VET / 2023-01-03
Okay, apparently I'm heading into a new clue this time. Using the W11 64-bit laptop, I decided to force-choosing the .RAW file, and selected 'V570KL_all_VZW_user_V3.8.1.raw'
It recognized the file, rebooted into recovery, and this time recovery DID something. It was a failure, but what does surprise me is the file being, eh... succesfully sideloaded.
I'll try to sideload .RAW file 'V570KL_all_WW_eng_T3.0.6.raw' and see what happens.
Update 4 - 22:53 VET / 2023-01-03
Okay, I'll continue my attempts tomorrow. For now, with ASUS Zenfone Fash Tool V2.0.1.0, in the W11 64-bit Laptop (the only one in where it's working as it should, apparently) is giving the same error as in Update 3 for VZW .raw file, and WW .raw file does, ehm... nothing. I don't know what I'm skipping, I'll re-download the file and see what happens tomorrow after arriving home from work.
Click to expand...
Click to collapse
Update 5 - 16:40 VET / 2023-01-07
I took a break for a couple days for returning to this hell, and... let's see the progress so far:
* ASUS Zenfone Flash Tool V2.0.1.0 is doing nothing to help.
* I investigated there is a way to flash manually (using fastboot) the whole system, so it should be helpful, I think.
* Using a tool our friend SlenderPL left in the GDrive folder 'Asus Tool (RC4)', I unpacked the whole .RAW file. That was at first thinking into creating a .zip file to attempt another way to flash the ROM, but then I did found apparently it has more success chances trying to flash the stock rom, file by file, using 'fastboot flash' command, file by file. However, of course I need the tree, the .xml, the .bat file that tells me the order of how flashing it. It doesn't exist.
Right now I have a folder with the whole .RAW totally unpacked.
* I tried to force flashing, entering into Recovery, and then using sideload, writing:
adb sideload V570KL_all_WW_eng_T3.0.3.raw
Click to expand...
Click to collapse
of course, after placing the .raw file in the same folder of platform-tools on the computer. The phone did read the file, but again I got an error 'E:signature verification failed'.
Let's see whay newer idea I get...
Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?
wivelt said:
Hello, I am the owner of 5 gadgets of this model and I want to solve the issue with Wi-Fi. For a year now I have been studying different options and trying to do the same. The last idea remains, but advice is needed. What if you remove the cover, find the pins for direct connection of the memory to the PC and simply replace the files in the hdd editor to work Wi-Fi?
Click to expand...
Click to collapse
I think it's on the edge of fantasy. Try to do it, and if it works, write a detailed guide. I will be extremely grateful!

Categories

Resources