Database Users

[GUIDE] How to upgrade, root & flash Samsung Galaxy Ace S5830 [DOWNLOAD LINKS | CWM5]

[GUIDE] How to upgrade, root & flash Samsung Galaxy Ace S5830 [DOWNLOAD LINKS | CWM5]
Hey guys,
in this tutorial I will show you how to upgrade and root your Samsung Galaxy Ace S5830. This method is the simplest way to do it.
Shall not be liable for any resulting damage to your phone! Everything you do at your own risk!
If you want to upgrade to newer version then Gingerbread I suggest you to make full procedure, not only flash recovery.
WARNING
If you don't understand what is root, ROM, phone, flash, CMD etc. watch this movie
You will need these files:
Brain
PC with Windows XP SP2 or later
Samsung Galaxy Ace GT-S5830
USB to Micro-USB cable
.Net Framework 2.0 or later
Android Software Development Kit (SDK)
Samsung Kies or Samsung Android USB Drivers
ODIN 4.38 + OPS
SuperOneClick (for 2.2> firmwares) or Universal Gingerbread Root or Unroot (for 2.3< firmwares)
ClockworkMod Recovery 5.0.2.6 (Fixed!)
New firmware
*Optional Custom ROM
Newest firmware:
Release name: S5830DXKT7
Release date: November 2012
Country: Vietnam
CSC: S5830OLBKT3
Android Version: Gingerbread 2.3.6
DOWNLOADS
Dropbox
Google Drive
YouTube Tutorial
Thanks to GadgetCheck!​​​​
A. Preparing your PC:
Install .Net Framework 2.0
Install Android SDK
Download SDK Tools & Platform-tools in Android SDK
Right click on Computer and select Properties
Select Advanced System Settings then Advanced and Click the Environment Variables button.
Click on the variable called 'Path' and then click on Edit. Now add the target directory to the value of the variable, using a semi-colon as a separator.
Add system path to Android SDK and Android SDK Tools folders
x86
Code:
C:\Program Files\Android\android-sdk
C:\Program Files\Android\android-sdk\platform-tools
x64
Code:
C:\Program Files (x86)\Android\android-sdk
C:\Program Files (x86)\Android\android-sdk\platform-tools
Now your PC is ready!
B. Preparing your phone (only for 2.2.x users! If you only want to root your phone, go to step D, if your phone don't have root skip this steps):
Install Samsung Kies
Turn on your phone
Enable Debugging at Apliccations>Programming
Connect your phone into PC via cable
Launch SuperOneClick
Click "Unroot"
Wait
When the process is complete turn off SOC and unplug your phone
Reboot to apply changes
Now you have unrooted phone!
C. Flashing the newest firmware:
Turn off your phone
Remove your SIM Card and SD Card
Extract previously downloaded firmware
Open ODIN 4.38 on your PC and change OPS file name to
Code:
Cooper_v1.0.ops
Select from extracted archive: OPS-OPS, Boot-APBOOT, Phone-MODEM, PDA-CODE, CSC-CSC (leave EFS and One Package empty)
If archive contains only <filename>.tar.md5 select it as PDA and OPS as OPS, leave other fields EMPTY
Connect your phone via USB into PC
When the screen is turned on hold POWER+VOLUME DOWN+HOME and wait until the phone enters the Download Mode
If ODIN detected and recognized your phone should light up the first square to the left side
Press "Start" button and wait, the process should take ~5 minutes
If all goes well your phone should reboot automatically
Square should change the color to blue and display "PASS" it means that flashing process was successful and we have the newest firmware
Disconnect your phone
Turn off your phone
Insert your SIM Card and SD Card again
Turn on your phone
Now you have the newest firmware!
Da. Rooting for 2.2.1:
Turn on your phone
Enable Debugging at Apliccations>Programming
Connect your phone into PC via cable
Launch Super One Click 2.3.3
Click "Root"
Wait until the program will root your phone
When the process is complete turn off SOC and unplug your phone
Reboot
Now you have root!
Db. Rooting for 2.3.x (NEW METHOD!):
Download file called universal_gb_root_v25.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file universal_gb_root_v25.zip
After the update completed - reboot
Now you have rooted S5830
OPTIONAL Unrooting for 2.3.x:
Download file called universal_gb_unroot_v9.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file universal_gb_unroot_v9.zip
After the update completed - reboot
Now you have unrooted S5830[/QUOTE]
OLD ROOTING METHOD FOR 2.3.x
Rooting for 2.3.x (Thanks to russian forum-user with nickname may213) (if it doesn't work try D method):
Code:
upd_1.zip [URL="https://hotfile.com/dl/193725879/700f6be/upd_1.zip.html"]HotFile[/URL]
Download file called upd_1.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file upd_1.zip
After the update completed - reboot
Now you have rooted S5830
Unrooting for 2.3.x (Thanks to ingbrzy) (if it doesn't work try D method):
Code:
unroot.zip [URL="https://hotfile.com/dl/193725835/d31c709/unroot.zip.html"]HotFile[/URL]
Download file called unroot.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file unroot.zip
After the update completed - reboot
Now you have unrooted S5830
Click to expand...
Click to collapse
E. Flash Custom Recovery:
Put recovery-clockwork-5.0.2.6-galaxyace.zip into SD Card
Turn off your phone
Press POWER+HOME BUTTON
Select Update Zip From SD-Card option. [If you are on previous version of CWM recovery then you might need to select Install Zip From SD Card and then Choose Zip From SD Card Option simultaneously. ]
Select recovery-clockwork-5.0.2.6-galaxyace.zip and flash it
Reboot your device
F*. Flash Custom ROM:
Select Custom ROM
Put Custom ROM .zip into SD Card
Turn off your phone
Press POWER+HOME BUTTON
Wipe All
Select "Install zip from sd card"
Select "Choose zip"
Select .zip with your Custom ROM
Select "Yes"
Reboot into system
That's ALL!!!
Now you have the newest firmware and root and probably Custom ROM!
Please don't send me messages on IM because i don't have much time to read it and reply. I've maded special thread for problems and issues: http://forum.xda-developers.com/showthread.php?p=22230605#post22230605
If I helped you, click "Thanks" also you can vote it into main page, rate this thread or donate me
If you have problems with one of this steps post it in this thread I will try help you!

about to root mine.will let u know wat happens.

jnrphil said:
about to root mine.will let u know wat happens.
Click to expand...
Click to collapse
What do you mean?

it worked!!!thanx

You're welcome
Sent from my GT-S5830 using XDA App

hubix said:
You're welcome
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Why I cannot find the DXKC1 firmware?

Hello, i need FW DXKC1. Can you help me? I don't find it on samfirmware . Please!!!
P/S: Sorry for my bad english ~.~

Where are you from? I need to know this to tell you the newest available ROM for your phone.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App

i'm from Vietnam, my FW is XXKC1 but i need DXKC1
I have found the problem, sometime my ACE freeze
when the phone freezes,and i have to take the battery out to get it work.

hi hubix, do you know where to find this galaxy rom: S5830DXKA9 if you know please post a link. or do you know how to extract a rom from galaxy ace because i want to share my S5830DXKB1 firmware which i currently have now.

If you can't find it at samfirmware it doesnt exist. Link: http://www.samfirmware.com/WEBPROTECT-S5830.htm
The newest Asia firmware is S5830ZCKA7
I've related names of the newest ROM for any continent in the 1st post.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App

hubix said:
If you can't find it at samfirmware it doesnt exist. Link: http://www.samfirmware.com/WEBPROTECT-S5830.htm
The newest Asia firmware is S5830ZCKA7
I've related names of the newest ROM for any continent in the 1st post.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
Click to expand...
Click to collapse
Actually, i'm from the philippines and when i connec to Kies its prompting me to upgrade my firmware from xxxxDKA9 to xxxxDKC1, so i assume it is an asian firmware, but when i check in samfirmware.com this xxxDKC1 is under the European firmware. Nonetheless, i have upgraded my firmware via kies and now it is xxxDKC1, and i dont see any issue/s on it so far.

It fixes wifi disconnecting bug, LED Flashlight + stock camera program bug and it's more stable for me
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App

Congratulations body, very good explained , very good tutorial!

Thank you very much

can't open downloaded attachments
i can't open downloaded attachments, another mirror please...

I've edited 1st post. Now you have official mirrors there

hubix, thank you...

tomdotnet said:
hubix, thank you...
Click to expand...
Click to collapse
No problem

i've followed all the steps and Odin detects the device, but when i start the process the phone never reboots - keeps the "Downloading..." text in the screen - and i'm "stuck" at the first step, "mibib download..". any ideas?
this is the debug message..
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..

How to use Heimdall

Heimdall is an open-source alternative to flashing firmware to devices. It claims to be safer and a better alternative to Odin pretty much.
Although Heimdall is safer, it is still a firmware flashing tool, and like all firmware flashing tools, there could be dire consequences for not following instructions. I take no responsibility for what unexpected results or damage that may happen when following this guide. (I followed this guide on my tab though and it worked great)
- You should probably backup all important data prior to using Heimdall
First, you'll have to acquire Heimdall. You can find Heimdall releases and information here: http://www.glassechidna.com.au/products/heimdall/
- Heimdall is for Windows, OS X, and Linux
- I recommend using the command-line version over the GUI
zImage Guide
Note: For flashing of just the kernel to your device
- Command for flashing zImage
Code:
heimdall flash --kernel zImage --verbose
Files Needed:
zImage
ROM, Kernel, Modem, etc. Guide
Note: For flashing a ROM, Kernel, and Modem to your device, or for "re-stocking"
- Command for flashing complete ROM, Kernel, and Modem
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Files Needed for Command Above:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
From this point on, this will mostly be a Windows-based guide. I'll use a Samsung Galaxy Tab 7" P1000 GSM and I'll re-stock using files from Overcome, and then flash the Overcome kernel afterwards. You may have to modify parts of the guide for different devices, kernels, ROMs, Operating Systems, etc.
Windows Driver Preparation
1. Install Samsung's Drivers (SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
Note: You should reboot your computer after installing, even if it doesn't tell you to. Drivers wouldn't initialize until I rebooted.
2. Connect your Tab to your computer at least once in Normal, Recovery, and Download mode so that all drivers initialize
3. Reboot your tab to Download mode
4. Run zadig.exe
5. Go to Options > List All Devices
6. Select Samsung USB Composite Device from the dropdown box
7. Click Install Driver (accept any unsigned driver prompts you get)
8. Once Zadig says the drivers are installed successfully, close it
Windows Flashing Preparation
1. Make a folder specifically for Heimdall someplace safe
2. Copy heimdall.exe and libusb-1.0.dll to the Heimdall folder
3. Acquire GB-Stock-Safe-v5.zip, and Overcome_Kernel_v4.0.0.tar
4. Extract the contents of GB-Stock-Safe-v5.zip in a folder somewhere
Note: In the GB-Stock-Safe-v5.zip extracted folder should at least be modem folders, gt-p1000_mr.pit, and GB_Stock_Safe_v5.tar
5. Take the modem.bin from the modem of your choosing and throw it in the Heimdall folder
6. Take gt-p1000_mr.pit and throw it in the Heimdall folder
7. Extract the contents of GB_Stock_Safe_v5.tar into the Heimdall folder
Note: You should have 13 files total equaling around 391MB
Windows Flashing (Re-stocking)
1. Reboot your tab into Download mode
2. Connect it to your PC with the same USB port you used to prepare drivers
3. Open Command Prompt
4. cd into the Heimdall folder
5. Type (or copy/paste)
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
and press Enter
Note: This will take maybe 2 minutes, but quicker then Odin
Note: When flashing is complete, tab will automatically reboot
Note: You will have to manually wipe caches and factory reset from Recovery if you see it fails to mount /data on initial boot (if you see red text, then it failed)
6. When tab finishes booting, complete the Setup Wizard
Note: If you are going to flash another ROM (such as icedBOCA, CM9, etc), then just press Next through all of setup. Language will be Italian, but this does not matter for now
Note: If you just want to return to a pure factory state, this is as far as you should go
Note: This does not seem to wipe the internal SD card. For the cleanest experience possible, I recommend manually formatting the internal SD card right after the Setup Wizard
Windows Flashing (Overcome Kernel)
Note: This will convert partitions to ext4 and give you CWM recovery
Note: This is to be done after you have re-stocked
1. Acquire Overcome_Kernel_v4.0.0.tar
Note: You should have this already if you followed Windows Flashing Preparation
2. Copy heimdall.exe and libusb-1.0.dll to a new Heimdall folder
Note: Or use the same Heimdall folder you had previously
Note: I'll refer to the new folder as Heimdall2
3. Extract the zImage file from Overcome_Kernel_v4.0.0.tar to the Heimdall2 folder
4. Reboot your tab into Download mode
5. Connect it to your PC with the same USB port you used to prepare drivers
6. Open Command Prompt
7. cd into the Heimdall2 folder
8. Type (or copy/paste)
Code:
heimdall flash --kernel zImage --verbose
Note: This should take less then 5 seconds
Note: Your tab should automatically reboot when completed
9. Your tab should now convert partitions to ext4
Note: This is known as the Voodoo lagfix
Note: You will be stuck on the SGT bootscreen until this process is done
Note: You will hear a "sexy" voice telling you the steps of the ext4 process
Note: This process should take maybe 3-5 minutes
Note: Your tab will automatically reboot when complete, so you can walk away if needed
10. You are now on Gingerbread with Overcome kernel
- From this point on, you can now proceed to install (most, if not all) any compatible ROM/Kernel you want
- You should not need Heimdall from this point on also, as most ROM's and Kernels offer .zip packages that can be flashed from CWM/Recovery
Note: For any new ROM you flash, I recommend doing a data wipe afterwards, that way, you can gain access to the Setup Wizard and properly setup your Google Account, Market Sync, etc.
Windows Troubleshooting and Q&A
Q: I get a libusb error when trying to flash anything with Heimdall
A: This is due to either improper driver installation or using another USB port then the one you used to install the drivers
Note: You have to use zadig
Note: I would recommend uninstalling all previous USB filter drivers as well if you have problems
Q: Is it possible to use both Heimdall and Odin?
A: Yes, but it is recommended to have two USB ports. Do the zadig driver install on one USB port, and that port will be for Heimdall, and the second USB port will be untouched, and you'll be able to use Odin on it
Note: You cannot use Heimdall and Odin on the same port without uninstalling/installing the libusb filter driver from zadig that Heimdall needs
Q: Is Heimdall really faster then Odin?
A: Indeed. It's faster to start the flashing process, and faster to flash in-general. For instance, to re-stock my tab, I simply plug it into my Heimdall USB port, run a batch file (simply containing the command used above), and it's re-stocked in about 1 minute. With Odin, you have to manually select the files, and then flashing itself takes 2-3 minutes.

it would appear Heimdall does not work on Windows Consumer Preview (zadig fails, saying the OS rejects unsigned drivers)

Good tutorial, thanks.
Is this tool only feasible for Samsung devices, or also for most other Android ones?
Two annoyances from this tool:
1. It does not have some facility (like a specific command line option) to reveal to the user that the connection to a "download mode" device (i.e., no way to tell if the driver is working)
2. After the --print-pit option (I used this to confirm that the communication is setup properly) will reboot the device, I think just printing something will cause a device reboot is extremely unexpected...
By the way, your title seems to misspelled the keyword "heimdall".

factoryfs.rfs is the Factory installed filesystem and its the main rom

I have data.img... where I put it? datafs?
I am using heimdall frontend 1.3.1

what to do if wipe cache and recovery fail, the red text mount data? I followed all your steps but still stuck at samsung screen.

How to flash hidden.rfs by heimdall?
Sent from my GT-P1000

goofey2012 said:
How to flash hidden.rfs by heimdall?
Sent from my GT-P1000
Click to expand...
Click to collapse
--hidden hidden.rfs
zeroxia said:
annoyances from this tool:
1. It does not have some facility (like a specific command line option) to reveal to the user that the connection to a "download mode" device (i.e., no way to tell if the driver is working)
By the way, your title seems to misspelled the keyword "heimdall".
Click to expand...
Click to collapse
heimdall detect
zeroxia said:
2. After the --print-pit option (I used this to confirm that the communication is setup properly) will reboot the device, I think just printing something will cause a device reboot is extremely unexpected...
Click to expand...
Click to collapse
heimdall print-pit --no-reboot

Thanks!!!

heimdall syntax / files confusion
Hello all.
I imagine this is a noob question but I am stuck and reluctant to flash random files in hopes of getting it right.
I have these files from an extracted tar.md5 (T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar.md5).
I'm trying to use heimdall to restore a SGS3 (d2tmo/T999) with a Stock ROM without bumping the flash counter. I only use Linux, so...
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
SS_DL.dll (not needed, eh?)
system.img.ext4
tz.mbn
But I do not know what to do with the "*.mbn" files or the "NON-HLOS.bin"
I'm guessing the syntax is something like:
heimdall flash --primary-boot boot.img --cache cache.img.ext4 --recovery recovery.img --factoryfs system.img.ext4 ...
But I have a lot of files left over. Would someone kindly confirm that part is correct and fill in the rest of the blanks?
$ heimdall version
v1.4 RC1
Thank you for your time,

this is actually a Galaxy Tab 7" forum.
But anyway, your questions was answered (somewhat) by the heimdall author
https://github.com/Benjamin-Dobell/Heimdall/issues/82
look for the last comment

Thank you
priyana said:
this is actually a Galaxy Tab 7" forum.
But anyway, your questions was answered (somewhat) by the heimdall author
look for the last comment
Click to expand...
Click to collapse
Thank you -- and sorry about that.
I just saw the title and didn't pay attention to the device model.
My bad.

Jesus is a prophet
GoSooners345 said:
factoryfs.rfs is the Factory installed filesystem and its the main rom
Click to expand...
Click to collapse
Thanks alot will try

What will happen if in heimdall i choose the 512.pit file with re-partition ticked and flash my SGS?
Will i have to install a stock rom, then a GB and lastely the latest rom of my preference?

Send me link for zadig file .thqnkx in advance
Sent from my GT-P1000 using xda app-developers app

CM 10.1 flashing feedback
espionage724 said:
Heimdall is an open-source alternative to flashing firmware to devices. It claims to be safer and a better alternative to Odin pretty much.
Although Heimdall is safer, it is still a firmware flashing tool, and like all firmware flashing tools, there could be dire consequences for not following instructions. I take no responsibility for what unexpected results or damage that may happen when following this guide. (I followed this guide on my tab though and it worked great)
- You should probably backup all important data prior to using Heimdall
First, you'll have to acquire Heimdall. You can find Heimdall releases and information here: http://www.glassechidna.com.au/products/heimdall/
- Heimdall is for Windows, OS X, and Linux
- I recommend using the command-line version over the GUI
zImage Guide
Note: For flashing of just the kernel to your device
- Command for flashing zImage
Code:
heimdall flash --kernel zImage --verbose
Files Needed:
zImage
ROM, Kernel, Modem, etc. Guide
Note: For flashing a ROM, Kernel, and Modem to your device, or for "re-stocking"
- Command for flashing complete ROM, Kernel, and Modem
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Files Needed for Command Above:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
From this point on, this will mostly be a Windows-based guide. I'll use a Samsung Galaxy Tab 7" P1000 GSM and I'll re-stock using files from Overcome, and then flash the Overcome kernel afterwards. You may have to modify parts of the guide for different devices, kernels, ROMs, Operating Systems, etc.
Windows Driver Preparation
1. Install Samsung's Drivers (SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
Note: You should reboot your computer after installing, even if it doesn't tell you to. Drivers wouldn't initialize until I rebooted.
2. Connect your Tab to your computer at least once in Normal, Recovery, and Download mode so that all drivers initialize
3. Reboot your tab to Download mode
4. Run zadig.exe
5. Go to Options > List All Devices
6. Select Samsung USB Composite Device from the dropdown box
7. Click Install Driver (accept any unsigned driver prompts you get)
8. Once Zadig says the drivers are installed successfully, close it
Windows Flashing Preparation
1. Make a folder specifically for Heimdall someplace safe
2. Copy heimdall.exe and libusb-1.0.dll to the Heimdall folder
3. Acquire GB-Stock-Safe-v5.zip, and Overcome_Kernel_v4.0.0.tar
4. Extract the contents of GB-Stock-Safe-v5.zip in a folder somewhere
Note: In the GB-Stock-Safe-v5.zip extracted folder should at least be modem folders, gt-p1000_mr.pit, and GB_Stock_Safe_v5.tar
5. Take the modem.bin from the modem of your choosing and throw it in the Heimdall folder
6. Take gt-p1000_mr.pit and throw it in the Heimdall folder
7. Extract the contents of GB_Stock_Safe_v5.tar into the Heimdall folder
Note: You should have 13 files total equaling around 391MB
Windows Flashing (Re-stocking)
1. Reboot your tab into Download mode
2. Connect it to your PC with the same USB port you used to prepare drivers
3. Open Command Prompt
4. cd into the Heimdall folder
5. Type (or copy/paste)
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
and press Enter
Note: This will take maybe 2 minutes, but quicker then Odin
Note: When flashing is complete, tab will automatically reboot
Note: You will have to manually wipe caches and factory reset from Recovery if you see it fails to mount /data on initial boot (if you see red text, then it failed)
6. When tab finishes booting, complete the Setup Wizard
Note: If you are going to flash another ROM (such as icedBOCA, CM9, etc), then just press Next through all of setup. Language will be Italian, but this does not matter for now
Note: If you just want to return to a pure factory state, this is as far as you should go
Note: This does not seem to wipe the internal SD card. For the cleanest experience possible, I recommend manually formatting the internal SD card right after the Setup Wizard
Windows Flashing (Overcome Kernel)
Note: This will convert partitions to ext4 and give you CWM recovery
Note: This is to be done after you have re-stocked
1. Acquire Overcome_Kernel_v4.0.0.tar
Note: You should have this already if you followed Windows Flashing Preparation
2. Copy heimdall.exe and libusb-1.0.dll to a new Heimdall folder
Note: Or use the same Heimdall folder you had previously
Note: I'll refer to the new folder as Heimdall2
3. Extract the zImage file from Overcome_Kernel_v4.0.0.tar to the Heimdall2 folder
4. Reboot your tab into Download mode
5. Connect it to your PC with the same USB port you used to prepare drivers
6. Open Command Prompt
7. cd into the Heimdall2 folder
8. Type (or copy/paste)
Code:
heimdall flash --kernel zImage --verbose
Note: This should take less then 5 seconds
Note: Your tab should automatically reboot when completed
9. Your tab should now convert partitions to ext4
Note: This is known as the Voodoo lagfix
Note: You will be stuck on the SGT bootscreen until this process is done
Note: You will hear a "sexy" voice telling you the steps of the ext4 process
Note: This process should take maybe 3-5 minutes
Note: Your tab will automatically reboot when complete, so you can walk away if needed
10. You are now on Gingerbread with Overcome kernel
- From this point on, you can now proceed to install (most, if not all) any compatible ROM/Kernel you want
- You should not need Heimdall from this point on also, as most ROM's and Kernels offer .zip packages that can be flashed from CWM/Recovery
Note: For any new ROM you flash, I recommend doing a data wipe afterwards, that way, you can gain access to the Setup Wizard and properly setup your Google Account, Market Sync, etc.
Windows Troubleshooting and Q&A
Q: I get a libusb error when trying to flash anything with Heimdall
A: This is due to either improper driver installation or using another USB port then the one you used to install the drivers
Note: You have to use zadig
Note: I would recommend uninstalling all previous USB filter drivers as well if you have problems
Q: Is it possible to use both Heimdall and Odin?
A: Yes, but it is recommended to have two USB ports. Do the zadig driver install on one USB port, and that port will be for Heimdall, and the second USB port will be untouched, and you'll be able to use Odin on it
Note: You cannot use Heimdall and Odin on the same port without uninstalling/installing the libusb filter driver from zadig that Heimdall needs
Q: Is Heimdall really faster then Odin?
A: Indeed. It's faster to start the flashing process, and faster to flash in-general. For instance, to re-stock my tab, I simply plug it into my Heimdall USB port, run a batch file (simply containing the command used above), and it's re-stocked in about 1 minute. With Odin, you have to manually select the files, and then flashing itself takes 2-3 minutes.
Click to expand...
Click to collapse
I flashed GT p1000 GSM through this method. CM10.1 4.2.2 worked really well. No bugs yet. Will feedback further.soon.
Mensreaorder out!

Great
Sent from my GT-I9300 using xda premium

please post a link to the required files
Hi...i downloaded heimdall, but was unable to find all the required files like dbdata.rfs, param etc... Please post a link containing the full package.

But you need to say which tab model/variant is yours,
Sent from my GT-P1000 using xda app-developers app

Details on the problem
priyana said:
But you need to say which tab model/variant is yours,
Sent from my GT-P1000 using xda app-developers app[/QUOTE
Hi Priyana. I'm using the Galaxy tab p1000 asian version. I was running cm 9.1 on it for the last 6 months without any problems, but recently tried out the bluetooth tethering and the software went into an infinite bootloop. I tried recovery by trying a full wipe, but when i tried to restore one of the old backups it all crashed again. My device is now able to go into download mode with power+vol down button combo. Also when the power button is long pressed, i get the Samsung galaxy tab frozen splash screen and on connecting the charger there is a battery icon but no charging progress.
Odin did not recognize the device despite waiting and watching as recommended, hence i tried flashing with heimdall 1.4 version and the GB stock safe rom by following the instructions. Device drivers get installed and heimdall detects my device.Was able to figure out the files and run Heimdall (my previous question is hence irrelevant), but to no avail. Am attaching the log after the Heimdall run. Please help.
Click to expand...
Click to collapse

[GUIDE] Rooting s3 mini from Linux with heimdall

Hey.
Just wanted to share my rooting experience.
My girlfriend just bought her S3 mini few days ago - and because Samsung Dive sucks balls (can be erased by doing factory reset), I felt the need to root, so cerberus anti-theft (http://cerberusapp.com, try it out, its awesome) could be written to /system (which requires root & survives factory resets).
Because I use Ubuntu Linux, I couldn't use Odin. Also from what I've read Odin reflashes whole phone, including bootloaders, recovery images and so on.
Because I've had XXALJL build originally in my phone, I've used this uk rooted rom as my rooting source.
Also, because the baseband is identical, I only flashed the system image, where /system/bin/su resides.
If you have a different baseband than your rooted image, this guide will not help you and you probably need to either: a) use odin to reflash everything. b) use your brain to figure your what to flash and where.
So here we go!
Flashing
I'm using ubuntu 12.10, 64 bit:
Code:
[email protected]:~/Downloads/rooted# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.10
DISTRIB_CODENAME=quantal
DISTRIB_DESCRIPTION="Ubuntu 12.10"
Code:
[email protected]:~/Downloads/rooted# uname -a
Linux cyrix 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
The only thing you should be concerned about is whether you're using 32 or 64 bit OS.
I've used heimdall 1.3.1, because 1.3.2 has issues and I didn't want to risk. Perhaps 1.3.2 or 1.4-RC1 would work just fine too, but I've used 1.3.1 and that did work for me.
Get heimdall 1.3.1 from http://www.glassechidna.com.au/products/heimdall/ (choose 32 bit (i386) or 64 bit (x64) debian package appropriately). Install those. And lets get down to bussiness.
I RECOMMEND RUNNING ALL COMMANDS FROM ROOT USER
Some guides recommend rebooting your pc after heimdall install (it inserts some udev rules). I didn't do that (completely forgot), but do it, just to be on a safe side.
So first step is to determine what partition identifier does your system partition has. Put your device into download mode (power off. Then hold vol down + home + power & click vol up once).
After doing that, connect your usb cable to computer and run:
Code:
# heimdall detect
It should say:
Code:
Device detected
If it doesn't - none of the following commands will probably work.
Then - lets see what our PIT (partition information table? not sure about the acronym) looks like:
Code:
# heimdall print-pit
What we are looking for is system partition. Mine looked like this:
Code:
--- Entry #21 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 20
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 524288
Partition Block Count: 2457600
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
From this we can see that our partition identifier is 20.
So extract the downloaded .rar ROM file, then again, extract rooted.tar and go into that directory. And lets flash our system image (around 900mb).
If everything is fine it should look like this:
Code:
[email protected]:~/Downloads/rooted# heimdall flash --20 system.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading SYSTEM
100%
SYSTEM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Do not touch your PC while flashing. Do not move the phone. Do not fiddle with the cables. Hold your breath and wait. If all is fine, the phone should turn off itself. Wait until you get charging screen, then turn it back on.
You should have supersu installed. You can also install terminal emulator and try running su to make sure you have the root.
Congrats on having root!

Great tutorial! Thanks a lot, from a fellow Linux user!

Hi dudes,
I have mi SGS2 soft bricked and I'm trying to recover it.
I've already opened a post here.
The thing is that I have discovered Heimdall by chance.
Fed up with the errors from Odin I decided to try in Linux.
I think my System partition is missing.
Find attached my result for heimdall print-pit.
Hope you can help me.
Regards,
Mario.

thanks for remaind me about heimdall, that was long time since heard about this tool. :beer:

Thanks! (But should I backup something first?)
Thanks, exactly what I was looking for
One quick question: by rooting with Heimdall (on Linux), will I loose all my apps/accounts ? (It will take ages to recover them all..)
(also, where could I get updated as new Heimdall-friendly firmwares become available?)
Thank you again for your time.
arturaz said:
Hey.
Just wanted to share my rooting experience.
My girlfriend just bought her S3 mini few days ago - and because Samsung Dive sucks balls (can be erased by doing factory reset), I felt the need to root, so cerberus anti-theft (http://cerberusapp.com, try it out, its awesome) could be written to /system (which requires root & survives factory resets).
Because I use Ubuntu Linux, I couldn't use Odin. Also from what I've read Odin reflashes whole phone, including bootloaders, recovery images and so on.
Because I've had XXALJL build originally in my phone, I've used this uk rooted rom as my rooting source.
Also, because the baseband is identical, I only flashed the system image, where /system/bin/su resides.
If you have a different baseband than your rooted image, this guide will not help you and you probably need to either: a) use odin to reflash everything. b) use your brain to figure your what to flash and where.
So here we go!
Flashing
I'm using ubuntu 12.10, 64 bit:
Code:
[email protected]:~/Downloads/rooted# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.10
DISTRIB_CODENAME=quantal
DISTRIB_DESCRIPTION="Ubuntu 12.10"
Code:
[email protected]:~/Downloads/rooted# uname -a
Linux cyrix 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
The only thing you should be concerned about is whether you're using 32 or 64 bit OS.
I've used heimdall 1.3.1, because 1.3.2 has issues and I didn't want to risk. Perhaps 1.3.2 or 1.4-RC1 would work just fine too, but I've used 1.3.1 and that did work for me.
Get heimdall 1.3.1 from http://www.glassechidna.com.au/products/heimdall/ (choose 32 bit (i386) or 64 bit (x64) debian package appropriately). Install those. And lets get down to bussiness.
I RECOMMEND RUNNING ALL COMMANDS FROM ROOT USER
Some guides recommend rebooting your pc after heimdall install (it inserts some udev rules). I didn't do that (completely forgot), but do it, just to be on a safe side.
So first step is to determine what partition identifier does your system partition has. Put your device into download mode (power off. Then hold vol down + home + power & click vol up once).
After doing that, connect your usb cable to computer and run:
Code:
# heimdall detect
It should say:
Code:
Device detected
If it doesn't - none of the following commands will probably work.
Then - lets see what our PIT (partition information table? not sure about the acronym) looks like:
Code:
# heimdall print-pit
What we are looking for is system partition. Mine looked like this:
Code:
--- Entry #21 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 20
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 524288
Partition Block Count: 2457600
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
From this we can see that our partition identifier is 20.
So extract the downloaded .rar ROM file, then again, extract rooted.tar and go into that directory. And lets flash our system image (around 900mb).
If everything is fine it should look like this:
Code:
[email protected]:~/Downloads/rooted# heimdall flash --20 system.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading SYSTEM
100%
SYSTEM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Do not touch your PC while flashing. Do not move the phone. Do not fiddle with the cables. Hold your breath and wait. If all is fine, the phone should turn off itself. Wait until you get charging screen, then turn it back on.
You should have supersu installed. You can also install terminal emulator and try running su to make sure you have the root.
Congrats on having root!
Click to expand...
Click to collapse

pminervini said:
Thanks, exactly what I was looking for
One quick question: by rooting with Heimdall (on Linux), will I loose all my apps/accounts ? (It will take ages to recover them all..)
(also, where could I get updated as new Heimdall-friendly firmwares become available?)
Thank you again for your time.
Click to expand...
Click to collapse
This only rewrites /system partition, while all your apps/accounts are stored in /data. So in theory you shouldn't lose things. However I do recommend you always backup your stuff with `adb backup` before doing this. You can never be too sure.
As for new firmwares - no idea. OTAs should probably work.

Thanks For the other Debian guys out there, I've just found out "adb" comes available for Sid ( packages debian org /sid/android-tools-adb -- there is a similar package in the Ubuntu repos) and requires MTP mode with USB debug on: bernaerts dyndns org /linux/245-ubuntu-precise-install-android-sdk
While the backup goes on (I'm doing "adb backup -apk -shared -all -f 08062013.ab", hope it's right), I'm looking for the right image file.
May this one fit? "Android 4.1.2 XXAMD3 official firmware"
www hotfile com /dl/209515302/bd1d1a3/I8190XXAMD3_I8190OXAAMD3_DBT.zip.html
UPDATE: no it's not, i should look for something fitting GT-I8190N; checking what I can do from OTA..
UPDATE 2: I've found this file: GT-I8190N-BTU-I8190NXXALL6-1356151513.rar ; I'm going to try to push its system.img with heimdall *crossed fingers*
Thank you again for all your help, you're awesome!
arturaz said:
This only rewrites /system partition, while all your apps/accounts are stored in /data. So in theory you shouldn't lose things. However I do recommend you always backup your stuff with `adb backup` before doing this. You can never be too sure.
As for new firmwares - no idea. OTAs should probably work.
Click to expand...
Click to collapse

After a weekend trying to revive the I8190N (at least it was raining..) I tried to sum up my problem with Heimdall here:
forum xda-developers com/showthread.php?t=2317198
pminervini said:
Thanks For the other Debian guys out there, I've just found out "adb" comes available for Sid ( packages debian org /sid/android-tools-adb -- there is a similar package in the Ubuntu repos) and requires MTP mode with USB debug on: bernaerts dyndns org /linux/245-ubuntu-precise-install-android-sdk
While the backup goes on (I'm doing "adb backup -apk -shared -all -f 08062013.ab", hope it's right), I'm looking for the right image file.
May this one fit? "Android 4.1.2 XXAMD3 official firmware"
www hotfile com /dl/209515302/bd1d1a3/I8190XXAMD3_I8190OXAAMD3_DBT.zip.html
UPDATE: no it's not, i should look for something fitting GT-I8190N; checking what I can do from OTA..
UPDATE 2: I've found this file: GT-I8190N-BTU-I8190NXXALL6-1356151513.rar ; I'm going to try to push its system.img with heimdall *crossed fingers*
Thank you again for all your help, you're awesome!
Click to expand...
Click to collapse

Is there any way to make Phone to original Samsung phone with heimdall? Unroot, Stockrecovery etc?

arturaz said:
Just wanted to share my rooting experience....
Click to expand...
Click to collapse
Thank you, arturaz!
Why did I waste so much of my valuable lifetime by trying to get Odin to work on XP/W7 in a VBox?
Gonna donate to Benjamin now. He really deserves a beer or two
BTW: heimdall can be found in the Debian testing branch now. Look out for "heimdall-flash" (Don't be confused by some "heimdal"-packages [only one 'L'], which are something completely different)

Hey I'm using Linux Mint 32bits, I wonder if I can use the ubuntu 32 version for the software Heimdall ? if so, which one ?
Thanks

I'm not sure I understand the question.

Hello,
lov8 said:
Hey I'm using Linux Mint 32bits, I wonder if I can use the ubuntu 32 version for the software Heimdall ?
Click to expand...
Click to collapse
because linux mint and fork ubuntu I would say yes
lov8 said:
if so, which one ?
Click to expand...
Click to collapse
????

Fred6681 said:
Hello,
????
Click to expand...
Click to collapse
Ah! I have the version 1.4 RC1 from the Linux mint repository. I hope this version is stable enough. I will give it a try in a few days .. :-/

Alternatively you can root your phone by flashing a custom recovery using heimdall, then going in recovery mode and installing supersu.
Tested with heimdall 1.40 and TWRP custom recovery, worked fine.
You have just to pay attention and find the right partition id for flashing "recovery.img".

Why no solution to "Device not detected" ?!
Im using Ubuntu 13.10 64, the S3 Mini is in download mode but not seen by Heimdall... any solutions?
Thanks

ateap0tist said:
Why no solution to "Device not detected" ?!
Im using Ubuntu 13.10 64, the S3 Mini is in download mode but not seen by Heimdall... any solutions?
Thanks
Click to expand...
Click to collapse
Which version of heimdall are you using?

Clostry said:
Which version of heimdall are you using?
Click to expand...
Click to collapse
Heimdall v. 1.4

Can you post the output of this commands? With phone in download mode attached ofc.
Code:
lsusb
heimdall detect --usb-log-level debug

heimdall tar gz error
When I try to load the system.img file (from cm10.2_golden.maclaw.20140118.ODIN_TWRP.tar.md5) from heimdall, before beginning to flash, I get the following error: Tar header contained an invalid file size.
I tried to load the uncopressed file too, then the file cm10.2_golden.maclaw.20140119.zip not for odin and I get the same error, what am I doing of wrong?
Thanks

Firmware Upgrade Guide For RK3188 RK3288 RK3368 Devices

UPD: Rreflashing guide for linux Host PC added.
BEFORE START
What you need:
1. Image file
2. Host PC (Windows)
3. USB OTG Cable
Supported host OS:
1. Windows XP （32/64bit)
2. Windows 7 (32/64bit)
3. Windows 8 (32/64bit)
All manipulations I show using UGOOS devices example. Procedure is common for all RK SoC based devices.
The first thing you need to do is to DOWNLOAD the firmware archive.
Inside archive you find: BatchTool or Android Tool - tools for reflashing and DriverAssitant - tool that helps you to install device drivers and firmware image file.
INSTALLING DRIVERS
If you need to install the drivers, you can find setup file in the program folder.
Launch RK DriverAssitant and press “Install Driver” button.
During installation a couple of times program will ask whether you want to install the driver. In the end of installation you can see diolog window: "Install driver ok".
Ugoos UT-3
1. Turn off the device.
2. Connect device to PC via USB using OTG- port.
3. Press and hold the hardware reset button.
4. Turn on the device.
Ugoos UM-3
1. Press and hold the hardware reset button.
2. Connect device to PC via USB using OTG- port.
UPGRADE FIRMWARE WITH ROCKCHIP BATCH TOOL
Run the Rockchip Batch Tool and click on the “…” to choose file with firmware pack.
If everything is correctly done and the driver is installed on your computer,
you will see green light on one of the indicators.
Now click the “Upgrade” button to reflash the device. When progress is finished you will see a sign indicating a successful operation.
UPGRADE FIRMWARE WITH ANDROID TOOL
Run the Android Tool and click on the “Upgrade Firmware”.
If everything is correctly done and the driver is installed on your computer, you will see “Found One Loader Device “
Click on button “Firmware” and specify the path to the firmware file.
You need to wait until the program downloading information about the firmware, then it will display some information on the screen. Now click the Upgrade button to reflash the device. At the end you will see a sign indicating a successful operation.
For flashing dualboot or clear linux firmware
1. Run the Android Tool. If you everything is correctly done and the driver is installed on your computer, you will see “Found One Loader Device.
2. Default program configured to flash"clear" android on your device. If you want install “Dualboot” or “Clear linux” click right mouse button by program window, and then select “Load config”.
3. Then choose one of configurations files:
 config.cfg - if want flash only Android
 config_dualboot.cfg - if want flash dualboot
 config_linux.cfg - if want flash only linux
4. Now click the Upgrade button to reflash the device. At the end you will see a sign indicating a successful operation.
For Linux Host PC users:
Rockchip provides a command line utility named "upgrade_tool" under Linux, which support flashing of both update.img and partition images.
In addition, we have two choices with regard to open source tools:
rkflashtool https://github.com/linux-rockchip/rkflashtool
rkflashkit https://github.com/linuxerwang/rkflashkit
Both of them only support flashing partition images, not update.img. rkflashtool is a command line tool, and flashkit has a nice and easy to use GUI with command line support lately added.
If you use Upgrade Tool:
There is no need to install device driver. Just connect the device and host PC.
Download Linux_Upgrade_Tool, and install it to host filesystem:
tar xf Linux_UpgradeTool_v1.2.tar.gz
cd Linux_UpgradeTool_v1.2
sudo mv upgrade_tool /usr/local/bin
sudo chown root:root /usr/local/bin/upgrade_tool
Click to expand...
Click to collapse
Flash update.img:
sudo upgrade_tool uf update.img
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"
}
Flash partition images:
sudo upgrade_tool di -b /path/to/boot.img
sudo upgrade_tool di -k /path/to/kernel.img
sudo upgrade_tool di -s /path/to/system.img
sudo upgrade_tool di -r /path/to/recovery.img
sudo upgrade_tool di -m /path/to/misc.img
sudo upgrade_tool di resource /path/to/resource.img
sudo upgrade_tool di -p paramater # flash parameter
sudo upgrade_tool ul bootloader.bin # flash bootloader
Click to expand...
Click to collapse
If errors occur due to flash problem, you can try to low format, or erase the flash:
upgrade_tool lf # low format flash
upgrade_tool ef # erase flash
Click to expand...
Click to collapse
Following instruction is for rkflashkit utility.
Install:
sudo apt-get install build-essential fakeroot
git clone https://github.com/linuxerwang/rkflashkit
cd rkflashkit
./waf debian
sudo apt-get install python-gtk2
sudo dpkg -i rkflashkit_0.1.2_all.deb
Click to expand...
Click to collapse
GUI:
sudo rkflashkit
Click to expand...
Click to collapse
Command line:
$ rkflashkit --help
Usage: <cmd> [args] [<cmd> [args]...]
part List partition
flash @<PARTITION> <IMAGE FILE> Flash partition with image file
cmp @<PARTITION> <IMAGE FILE> Compare partition with image file
backup @<PARTITION> <IMAGE FILE> Backup partition to image file
erase @<PARTITION> Erase partition
reboot Reboot device
Click to expand...
Click to collapse
For example, flash device with boot.img and kernel.img, then reboot:
sudo rkflashkit flash @boot boot.img @kernel.img kernel.img reboot
Click to expand...
Click to collapse
UPD:
REFLASHING IN MASKROM MODE
If you have problems with standard reflashing options, or your device had bricked
IMPORTANT: users can perform further manipulations only at their own risk, and only if all other reflashing options can’t help.
Before reflashing in maskrom mode we need to make the same steps as before:
Installing RK drivers
Installing Android Tool or Batch Tool
CONNECTING TO PC in MASKROM MODE
Maskrom mode is reflashing way, when you block reading data from NAND using hardware short circuit of NAND pins.
1. Open device housing and detect NAND (is standalone chip with 48 pins on two sides) on PCBA. In some boxes you also need detached heatsink or cooler in order to reach NAND
2. Place PCBA in front of you so you can clearly read NAND’s name and board number
3. You should choose 6th-7th or 7th-8th pin from NAND bottom on the right side or 6th-7th or 7th-8th pin from first pin (first pin is marked on PCBA with a point or ) and circuit it during plugging to Host PC and powering on (check pin sequence for other devices very clearly)
Ugoos UM3 example
Ugoos UT3s example
Ugoos UT4 example
After circuit and attaching to host PC, Android tool will show you message in progress bar: Found one maskrom device
Then start upgrade. The reflashing process should run several steps
You also can use Batch tool for this action. Device indication should turn blue instead of green for maskrom mode.
There are photos of several well spread NAND chips and circuit schemas:

Hi,
I'm using a new RK3368 device. The device is recognized when I use Batch tool, and I was able to flash it that way. But I need it to be recognized in Android tool so I can flash the recovery. It says "No device found". Any advice on how to get it to recognize so I can install TWRP recovery?
Thanks!

mekler22 said:
Hi,
I'm using a new RK3368 device. The device is recognized when I use Batch tool, and I was able to flash it that way. But I need it to be recognized in Android tool so I can flash the recovery. It says "No device found". Any advice on how to get it to recognize so I can install TWRP recovery?
Thanks!
Click to expand...
Click to collapse
Looks strange, first thing come to mind is to change Android tool. Try to use Android Tool 2.35.
And where did you get TWRP for rk3368?

Such_A_Victor said:
Looks strange, first thing come to mind is to change Android tool. Try to use Android Tool 2.35.
And where did you get TWRP for rk3368?
Click to expand...
Click to collapse
I did use android tool 2.35
I got the TWRP from here: http://freaktab.com/forum/tv-player...t-method-for-lollipop-rk3368-players-no-iroot

mekler22 said:
I did use android tool 2.35
I got the TWRP from here: http://freaktab.com/forum/tv-player...t-method-for-lollipop-rk3368-players-no-iroot
Click to expand...
Click to collapse
What Win version on your computer? Win 8.1 has a lot of problems with AT as I know.

Windows 10 64 bit

mekler22 said:
Windows 10 64 bit
Click to expand...
Click to collapse
So strange.
Stupid question but, did you start AT under admin rights? If do, one more thing I can offer is to send you my Android Tool 2.35.
I reflashed RK3368 device with it just yesterday.

I flash TWRP on my RK3368 based Z4 android tv box but and it seems working fine but after flash my microUSB port is not detecting any devices not even detected in PC in boot loader mods. I have stock ROM image as update.img format. Is there any ways I can extract recovery image from this ROM file and get back to stock recovery image.
My TWRP works fine and I rroted my devices using TWRP but TWRP csnnot flash this TV box firmware in update.img format. any ways which I can update firmware using TWRP.
thanks for help.

vinaysharma76 said:
I flash TWRP on my RK3368 based Z4 android tv box but and it seems working fine but after flash my microUSB port is not detecting any devices not even detected in PC in boot loader mods. I have stock ROM image as update.img format. Is there any ways I can extract recovery image from this ROM file and get back to stock recovery image.
My TWRP works fine and I rroted my devices using TWRP but TWRP csnnot flash this TV box firmware in update.img format. any ways which I can update firmware using TWRP.
thanks for help.
Click to expand...
Click to collapse
You can use Rk 3xxx firmware tools for extracting recovery image from ROM and than flash it with Androidtool

Such_A_Victor said:
You can use Rk 3xxx firmware tools for extracting recovery image from ROM and than flash it with Androidtool
Click to expand...
Click to collapse
Can you provide link for same. Thanks for help. Appriciated.
---------- Post added at 02:07 PM ---------- Previous post was at 01:37 PM ----------
Such_A_Victor said:
You can use Rk 3xxx firmware tools for extracting recovery image from ROM and than flash it with Androidtool
Click to expand...
Click to collapse
vinaysharma76 said:
Can you provide link for same. Thanks for help. Appriciated.
Click to expand...
Click to collapse
Never mind I got the link for tool and tried to unpack update.img from my tvbox but it failed to extract component images.

vinaysharma76 said:
Can you provide link for same. Thanks for help. Appriciated.
---------- Post added at 02:07 PM ---------- Previous post was at 01:37 PM ----------
Never mind I got the link for tool and tried to unpack update.img from my tvbox but it failed to extract component images.
Click to expand...
Click to collapse
is your update.img a full package? What did you exactly do?

Such_A_Victor said:
is your update.img a full package? What did you exactly do?
Click to expand...
Click to collapse
Yes its full package and I flashed this before using Android tool. but later updated recovery with TWRP. now I need stock recovery image to get back to stock recovery.

vinaysharma76 said:
Yes its full package and I flashed this before using Android tool. but later updated recovery with TWRP. now I need stock recovery image to get back to stock recovery.
Click to expand...
Click to collapse
https://mega.nz/#!f1k1SCjQ!71PD5Mu17OgoLprCZbaZwwuIWELgf4GOMuXef9YSq14
try again with this tool.
Also can extract recovery from device using this tool

will try thanks bro for help.
---------- Post added at 02:55 PM ---------- Previous post was at 02:40 PM ----------
Such_A_Victor said:
https://mega.nz/#!f1k1SCjQ!71PD5Mu17OgoLprCZbaZwwuIWELgf4GOMuXef9YSq14
try again with this tool.
Also can extract recovery from device using this tool
Click to expand...
Click to collapse
It worked Thanks a Ton for quick help.

Ugoos just released new firmware for RK3288 devices
http://ugoos.net/blog/rk3288-ut3-ut3s-um3-beta-android-lollipop-5.1-firmware_v3.0.4-lightbiz-ugoos_launcher
Massive changelog from previous version:
1. IPTVLauncher was replased by Ugoos Launcher
2. Added Chinese and Russian localization in Settings
3. Now firmware has only one partition
4. Added Multiuser support
5. Updated Multiwindow mode
5. Included Wifi optimization
6. Added support Fireasy app
7. Added samba server
8. Fixed bug with button "Dismiss all" in "Recent Apps" window
9. Added support Google Widevine DRM
10. Fixed bug with wrong colors in some apps (black background in ES File Explorer)
11. Added ability to select usb sound card in Sound Device manager
12. Added usb 3G Modems support

How can i know which firmware i must download? I have an Android tv box Emish X800 RK3368....

riccardosimo said:
How can i know which firmware i must download? I have an Android tv box Emish X800 RK3368....
Click to expand...
Click to collapse
Looks strange but I can't find official web site. Are there any info about mufacturee site on the box or instractions?

Hello,
I have a IPPLI Mars i8 Tv box with rk3188.
And i am unable to flash firmware after a previous wrong/failed attempt of firmware upgrade, and now tv box has no display.
Please help.

Such_A_Victor said:
Looks strange but I can't find official web site. Are there any info about mufacturee site on the box or instractions?
Click to expand...
Click to collapse
http://www.emish.com.cn/ this is the site.. but there isn't my tv box

prisim said:
Hello,
I have a IPPLI Mars i8 Tv box with rk3188.
And i am unable to flash firmware after a previous wrong/failed attempt of firmware upgrade, and now tv box has no display.
Please help.
Click to expand...
Click to collapse
What firmware and tools do you use? Did tools detect you device as connected?

[Guide] Flashing Firmware on Linux/Ubuntu using Heimdall

Flashing Bootloader/Modem/Recovery etc with Heimdall on Linux
Tested on G930F / G935F
Code:
* I am not responsible for bricked devices
* You are choosing to make these modifications.
Guide for flashing Bootloader & Modem on G935F :
1. Install Heimdall
Ubuntu users can execute the following command in terminal :
sudo apt-get install heimdall-flash heimdall-flash-frontend
Click to expand...
Click to collapse
2. Download the Bootloader & Modem you wish to flash.
3. Remove the .md5 extension (erase .md5 from the name)
4. Decompress the renamed tar files and you will get cm.bin, param.bin,modem.bin & sboot.bin.
5. Place the files in a folder and cd to that folder from terminal . e.g cd Downloads
6. Launch Heimall using :
sudo heimdall-frontend
Click to expand...
Click to collapse
4. Detect device & download device pit
5. Open pit file in heimdall and select partitions CM, Radio, Param and Bootloader specifying location of each file respectively
6. Flash

How do you flash a firmware that's in zip file. .. the same way?? Trying to root sprint s7 with heimdall....

oct01 said:
How do you flash a firmware that's in zip file. .. the same way?? Trying to root sprint s7 with heimdall....
Click to expand...
Click to collapse
Don't do it. Your device has a locked bootloader. This guide is only for G935F.

Thank you

Can I install TWRP this way?

yes, you can install twrp , but its more easy if you use the terminal
Code:
heidmall flash --RECOVERY recovery.img
and it should take less than a minute , all done

Wasted the last 8(!) hours of my life with this crap. Do yourself a favour and just grab a Window$ computer, install Samsung drivers and use the latest Odin -- it took less than 5 min in total.

smoneck said:
Wasted the last 8(!) hours of my life with this crap. Do yourself a favour and just grab a Window$ computer, install Samsung drivers and use the latest Odin -- it took less than 5 min in total.
Click to expand...
Click to collapse
I use Linux for years heimdall v frustratingly hit & miss _ sometimes works sometimes no.pit file printed dodgy USB cables / ports et al one day device recognised next day nothing sadly I have to concur flashing is much easier using Doze and Odin . . .