Database Users

[LINUX][TO STOCK][HEIMDALL]Console Short Guide: Back to Stock With Heimdall

Use this guide at your own risk.
Here is a short guide to use Heimdall on a linux console (Non a Graphical Interface) to back your phone to stock.
I assume you have Heimdall already installed.
1. Download stock files to flash (see link below under STOCK Files)
2. Put the phone in downloading mode (press 1 + power button)
3. Plug the phone to the computer.
4. Check if the phone is detected using this command:
Code:
heimdall detect
If device is detected you'll see a console message like this:
Code:
Device Detected
If not see below under DETECT DEVICE.
5. Use this command to flash files. You must run this command from the folder where the stock files are:
Code:
heimdall flash --repartition --cache cache.rfs --factoryfs factoryfs.rfs --modem modem.bin --param param.lfs --recovery recovery.bin --kernel zImage --pit SPH-D700.pit --data datafs.rfs
If everithing is done without errors your phone will be rebooted and you'll see the stock rom working on it .
Thanks.
STOCK Files:
You can find some packages in this nubecoder post: http://forum.xda-developers.com/showthread.php?t=1584346
You have to rename the files name in the console code above to match with the files in the package downloaded if necessary.
DEVICE DETECT
I use Archlinux and I didn't nothing to enable this, it works by default.
UBUNTU:
This text is copied from http://developer.android.com/guide/developing/device.html
If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. To set up device detection on Ubuntu Linux:
Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
NOTE: 04e8 is Samsung id Vendor.
After this open a linux console and use this command as root:
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
Thanks.

Hi dude,
I have my SGS2 soft bricked and I'm trying to recover it. I've already opened a post here.
Fed up with Odin errors I've decided to try Heimdall.
However, it fails when I try to flash a kernel and I think that my partitions system is damaged.
Find attached my heimdall print-pit result, System partition is missing.
Hope you can help me.
Regards,
Mario.

Usage for GT-P6200
In your example you use:
heimdall flash --repartition --cache cache.rfs --factoryfs factoryfs.rfs --modem modem.bin --param param.lfs --recovery recovery.bin --kernel zImage --pit SPH-D700.pit --data datafs.rfs
I have a Samsung Galaxy Tab Plus GT-P6200 which will not format /data thus I would like to use the --repartition option however my files provided are a little different being:
boot.bin
cache.img
factoryfs.img
hidden.img
modem.bin
param.lfs
recovery.img
Sbl.bin
zImage
How would I go about building the command string for this ?
As for the pit file I have this and will place it in the same folder

[GUIDE] Help for flash more faster when you use fastboot line command

HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND​
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip" or this tool : platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
OR
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
CD to where your fastboot or platform tools were installed
The line command is :
Code:
[B]C:\Users\R2D2>cd c:\platform-tools[/B]
Code:
[B]C:\platform-tools>[/B]
OR
Code:
[B]C:\Users\R2D2>cd c:\fastboot[/B]
Code:
[B]C:\fastboot>[/B]
Enter
Code:
[B]C:\fastboot>fastboot flash recovery recovery.img[/B]
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048

Modify boot.img to have true root

I am trying to unpack boot.img and modify the property in default.prop file.
But after I flash the modified boot.img, the phone cannot boot.
I think the only step that I can go wrong is the parameter of mkbootimg.
And here is the command line that I use.
./mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.cpio.gz --base 0x81000000 --pagesize 4096 --ramdiskaddr 0x81800000 -o boot.img
Original boot.img is attached, it is actually nexus4 4.4 boot.img.
Thanks!

What do you mean by true root? And the android kernel is just different from the default Linux kernel, so I'd say their commands might not be interchangeable.
Sent from my Nexus 4 using Tapatalk

[Q] [SOLVED] Compiling and packing custom kernel for Galaxy Note 3

Hello.
I'm trying adding several drivers into my SM-N9005 firmware. My phone runs Omega ROM v21, whose kernel doesn't support kernel module drivers, so I decided to recompile Omega's kernel from sources with needed options. The sources were taken from here:
https://github.com/omega-roms/N9005_Omega_Kernel_KK_4.4.2
The compilation was easy, the drivers were compiled too, I have my zImage now.
I downloaded Omega's flashable kernel-only zip N9005_Omega_Kernel_KK_v1.1_XXUFNF4_ramdisk.zip from Omega's repo, unpacked boot.img from the zip and tried disassembling it with split_boot script from bootimg_tools found here:
http://forum.xda-developers.com/showthread.php?t=2319018
I got the following output:
Page size: 2048 (0x00000800)
Kernel size: 8259720 (0x007e0888)
Ramdisk size: 1581598 (0x0018221e)
Second size: 0 (0x00000000)
Board name:
Command line: 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3'
Base address: (0x01dfff00)
Writing boot/boot.img-kernel ... complete.
Writing boot/boot.img-ramdisk.cpio.gz ... complete.
Unpacking ramdisk... complete.
So I got original Omega's kernel boot.img-kernel and ramdisk boot.img-ramdisk.cpio.gz. Next I decided to reassemble it and flush back, coz' if it works - my kernel might work too.
I took mkbootimg tool from the same package and created new boot.img with it, using parameters I got previously from split_boot script:
./mkbootimg --kernel boot/boot.img-kernel --ramdisk boot/boot.img-ramdisk.cpio.gz --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --base 0x01dfff00 --pagesize 2048 -o boot.img
So I got new boot.img with size 9846784 bytes, whereas original Omega's boot is 11149312 bytes.
I packed my boot.img into original Omega's kernel zip N9005_Omega_Kernel_KK_v1.1_XXUFNF4_ramdisk.zip, replacing existing original boot.img inside, renamed the zip and flushed with recovery.
Now my phone falls into download mode, saying 'Could not do normal boot'. Flashing back original Omega's kernel restores the phone to normal state, so the problem is with reassembling boot.img
What am I missing? Please, help.

The answer was easy: Android Image Kitchen v1.6 for Linux from http://forum.xda-developers.com/showthread.php?t=2073775
My kernel is rebuilt and my device is now working ok! Thanks to the authors.

jeweller_by said:
The answer was easy: Android Image Kitchen v1.6 for Linux from http://forum.xda-developers.com/showthread.php?t=2073775
My kernel is rebuilt and my device is now working ok! Thanks to the authors.
Click to expand...
Click to collapse
Thanks!

Flashing AOSP in Korean Variants (S-K-L)

If you're here you probably have a Korean variant and knows that we can't flash international (F) versions, we get stuck at ¨Patching System Image Unconditionnally¨
Quick Explanation for Korean users
The Korean variants have a smaller System Image Partition and thus we can't flash the normal AOSPs.
There're 2 ways to be able to flash it:
1 - The devs could build a lteskt build, but we're just few users so they would just spend their time...
2 - Resize the system image yourself and be able to flash it
I'm not a dev or an expert,but I can help you guys to resize it
YOU MUST READ THIS BEFORE PROCEED
This guide take into account that you have some basic knowledge on Linux (like install the required packges).
Manual
-Download the archive in attached files (All the files other than the scripts are from @xpirt tutorial)
-Extract it
Nougat :
-Extract system.transfer.list system.new.dat to the folder
-Open terminal and enter the commands
Code:
./sdat2img.py system.transfer.list system.new.dat system.img
resize2fs system.img 3124019K
ext2simg system.img system_new.img
./img2sdat.py system_new.img OUT 4
-Now move all files in OUT folder inside your ROM zip and you're ready to flash
Oreo:
-Extract system.transfer.list system.new.dat.br to the folder
-Open terminal and enter the commands
Code:
brotli --decompress --in system.new.dat.br --out system.new.dat
./sdat2img.py system.transfer.list system.new.dat system.img
resize2fs system.img 3124019K
ext2simg system.img system_new.img
./img2sdat.py system_new.img OUT 4
-Now move all files in OUT folder inside your ROM zip
-In your ROM.zip enter in META-INF/com/google/android/updater-script and replace system.new.dat.br for system.new.dat
-Save it and you're ready to flash it
Auto
-Download the archive in attached files (All the files other than the scripts are from @xpirt tutorial)
-Extract it
-Copy the ROM (zip) you want inside the folder
-Run the script for the version you want
Code:
. Nougat.sh
or
Code:
. Oreo.sh
-You'll get a zeroflteskt.zip ready to flash
NOTES FOR OREO ROMS
There're two scripts because Oreo (8.1) uses a new one/more compress method brotli, so first you need to decompress system.new.dat.br to system.new.dat and then continue the process, BUT you'll notice that the final zip size is larger than original, Why? Because I have disabled the brotli compression (In my tests it takes to much to compress the system.new.dat to system.new.dat.br and I think its not worth the time just to get some free MBs) . So the final result won't have the system.new.dat.br, but system.new.dat just like Nougat.
Credits to @xpirt tutorial and all github contributors

Thank you for method.You say right. Few user korea and because system image partition is smaller so it hard to support from dev.I don't have computer so i only can wait dev...

Wyzp said:
If you're here you probably have a Korean variant and knows that we can't flash international (F) versions, we get stuck at ¨Patching System Image Unconditionnally¨
Quick Explanation for Korean users
The Korean variants have a smaller System Image Partition and thus we can't flash the normal AOSPs.
There're 2 ways to be able to flash it:
1 - The devs could build a lteskt build, but we're just few users so they would just spend their time...
2 - Resize the system image yourself and be able to flash it
I'm not a dev or an expert,but I can help you guys to resize it
YOU MUST READ THIS BEFORE PROCEED
This guide take into account that you have some basic knowledge on Linux (like install the required packges).
Manual
-Download the archive in attached files (All the files other than the scripts are from @xpirt tutorial)
-Extract it
Nougat :
-Extract system.transfer.list system.new.dat to the folder
-Open terminal and enter the commands
Code:
./sdat2img.py system.transfer.list system.new.dat system.img
resize2fs system.img 3124019K
ext2simg system.img system_new.img
./img2sdat.py system_new.img OUT 4
-Now move all files in OUT folder inside your ROM zip and you're ready to flash
Oreo:
-Extract system.transfer.list system.new.dat.br to the folder
-Open terminal and enter the commands
Code:
brotli --decompress --in system.new.dat.br --out system.new.dat
./sdat2img.py system.transfer.list system.new.dat system.img
resize2fs system.img 3124019K
ext2simg system.img system_new.img
./img2sdat.py system_new.img OUT 4
-Now move all files in OUT folder inside your ROM zip
-In your ROM.zip enter in META-INF/com/google/android/updater-script and replace system.new.dat.br for system.new.dat
-Save it and you're ready to flash it
Auto
-Download the archive in attached files (All the files other than the scripts are from @xpirt tutorial)
-Extract it
-Copy the ROM (zip) you want inside the folder
-Run the script for the version you want
Code:
. Nougat.sh
or
Code:
. Oreo.sh
-You'll get a zeroflteskt.zip ready to flash
NOTES FOR OREO ROMS
There're two scripts because Oreo (8.1) uses a new one/more compress method brotli, so first you need to decompress system.new.dat.br to system.new.dat and then continue the process, BUT you'll notice that the final zip size is larger than original, Why? Because I have disabled the brotli compression (In my tests it takes to much to compress the system.new.dat to system.new.dat.br and I think its not worth the time just to get some free MBs) . So the final result won't have the system.new.dat.br, but system.new.dat just like Nougat.
Credits to @xpirt tutorial and all github contributors
Click to expand...
Click to collapse
a huge thank for your suggestion pro :good::good::good::good::good::good::good:

Hey guy!
i try create a lineage rom for my s7 korea throught your guide. when i run this code: "ext2simg system.img system_new.img" my ubuntu show error command not found. i try search "ext2simg" command on google but no result. Can you check your script and show me how i can handle this problem.
Thanks

can i try this with s7 (sm-g930s) ??

The Syntax is out of date. Be shure to use python2 with img2sdat.py. And for the Orea script the brotli command is used differently in recent versions:
It may look like this now:
Oreo.sh
Code:
unzip *.zip -d ./ROM
cd ROM
mv system.transfer.list system.new.dat.br system.patch.dat ../
cd ../
brotli --decompress -o system.new.dat system.new.dat.br
./sdat2img.py system.transfer.list system.new.dat system.img
rm system.transfer.list system.new.dat.br system.new.dat system.patch.dat
resize2fs system.img 3124019K
ext2simg system.img system_new.img
python2 img2sdat.py system_new.img OUT 4
rm system.img system_new.img
cd OUT
mv system.transfer.list system.new.dat system.patch.dat ../
cd ../
mv system.transfer.list system.new.dat system.patch.dat ./ROM
rm *.zip
cd ROM
sed -i -e 's/system.new.dat.br/system.new.dat/g' ./META-INF/com/google/android/updater-script
zip -r zerofteskt_ROM.zip ./
mv zerofteskt_ROM.zip ../
cd ../
rm -r ROM