Related
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
HEIMDALL FLASHER SGSIII/SGNII SUPPORT!!!
{
"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"
}
HEIMDALL FLASHER - it's a smart tool for flash Firmware in LINUX
I'll show how to flash SGSIII in UBUNTU
supported Devices
Samsung Galaxy SIII GT-I9300, I9305
Samsung Galaxy NoteII GT-N7100, N7105
Samsung Galaxy Note10.1-N8000
(Instructions and menu)
PUSH THE BUTTON
* Before use.
Make sure that all the files have executable permissions tool.
Place the firmware files in the folder "FLASH" or place the zip file with the firmware to the root of the instrument
* Menu options.
0 - Configure tools - need to do this once, it will compile and install the components in the system
Flash Menu
1 - Extract ROM - will extract the firmware files to the folder "FLASH" and display the report on file (zip file must be located in the root of the tool)
2 - Download mod - Reboot your device in flashing mode (must be enabled debugging USB)
3 - Heimdall detect device - show connection status
4 - STANDART - flash the standard firmware (the files are shown in parentheses)
5 - FULL - full flash firmware with bootloader (the files are shown in parentheses)
6 - MODEM - flash the radio (the files are shown in parentheses)
7 - KERNEL - flash the kernel (the files are shown in parentheses)
8 - RECOVERY - flash rekaveri (the files are shown in parentheses)
9 - Download PIT file - extract the file from the device PIT
Root Menu (Root access is required)
10 - DOWNGRADE BOOTLOADER - downgrade bootloader (Requires ROOT and should be included debugging USB)
11 - EFS backup - save the image section efs (the image will be saved in the root of the tool)
12 - EFS restore - restore partition efs (image must be in the root of the tool)
13 - Exit - exit
So:
1. Unpack archive and run script Heimdall_Flasher (unpack package of ROM .tar.md5 into folder FLASH)
2. Configure tools - (need only first time, it's will compile and install necessary components on your PC)
3. Download Mode - reboot device into Flash mode
4. Heimdall detect device - it's will show status of connect and images for flash
5. Choose flash option - after flash device will reboot
6. Exit - Enjoy
7. v.0.0.2 Added option Download PIT - Conect device, choose option 2 (Download mode), after this option 9 (download PIT file), Input any smart name of created PIT and push Enter
HEIMDALL FLASHER v.0.0.5
v.0.0.4 - added item DOWNGRADE BOOTLOADER
v.0.0.5 - added item Extract ROM
- Item added backup / restore efs
DOWNLOAD HEIMDALL FLASHER v.0.0.5
Credits:
Special thanx and very respect
Benjamin Dobell for Heimdall 1.4 Release Candidate 2 sources
Odia - for Downgradw bootloader
Nice tool for linux power users thank's :good:
thay said:
Nice tool for linux power users thank's :good:
Click to expand...
Click to collapse
All Linux users are power users
Thanks for the link
Hi
The link seems broken. Could tout please check ?
Sent from my GT-N7000 using xda premium
laloutre said:
Hi
The link seems broken. Could tout please check ?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Checked - downloaded normal...
There must be something on my side. I'm gonna try on another computer. Thanks
Sent from my GT-N7000 using xda premium
I am on ubuntu 12.04 and downloaded your program and everything works except when i get to the command
Heimdall SGSIII/SGNII Flasher v.0.0.2
============================================================
Connect your device into PC in debug mode, and choose option
1 - Configure tools
2 - Download mode
3 - Heimdall detect device
4 - Flash ROM (need: boot.img, recovery.img, system.img, cache.img, hidden.img, modem.bin)
5 - Flash CSC (need: cache.img hidden.img)
6 - Flash MODEM (need: modem.bin)
7 - Flash KERNEL (need: boot.img)
8 - Flash RECOVERY (need: recovery.img)
9 - Download PIT file
10 - Exit
Enter option: 8
Warning Flash! Do not turn off target!!
total 7572
-rw-rw-r-- 1 joe joe 7751680 Dec 8 20:24 cwm6-recovery-n7100-121014.tar
./tools/Flash_RECOVERY: line 7: heimdall: command not found
any help is appreaciated, guess the nexus line has spoiled me haha
I am on Debian Wheezy and your tool work with my N7000.
But like Heimdall 1.3.1, i can't flash bootloader :
Code:
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...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "BOOT" does not exist in the specified PIT.
Ending session...
.
And i don't understand why when i wan't to flash, the script automatically download pit ???
Tos69400 said:
I am on Debian Wheezy and your tool work with my N7000.
But like Heimdall 1.3.1, i can't flash bootloader :
Code:
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...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "BOOT" does not exist in the specified PIT.
Ending session...
.
And i don't understand why when i wan't to flash, the script automatically download pit ???
Click to expand...
Click to collapse
HEIMDALL_FLASHER SGNI SGSII
Use this...
as i9000 said:
HEIMDALL_FLASHER SGNI SGSII
Use this...
Click to expand...
Click to collapse
OK when i have more time i can test your new one.
Thanks for your work.
Tos69400 said:
OK when i have more time i can test your new one.But can you tell me what's the diffrence with your thread here : http://forum.xda-developers.com/showthread.php?p=33074572#post33074572
Thanks for your work.
Click to expand...
Click to collapse
difference in the name of partitions
SGNII
Code:
heimdall detect --verbose
sudo heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin
SGNI
Code:
heimdall detect --verbose
sudo heimdall flash --KERNEL zImage --FACTORYFS factoryfs.img --CACHE cache.img --HIDDEN hidden.img --MODEM modem.bin
Same problem.
Tos69400 said:
Same problem.
Click to expand...
Click to collapse
write - what are you doing?
The problem is the same with the old and the new version :
Code:
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...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "BOOT" does not exist in the specified PIT.
Ending session...
.
I have read the script and i can't understand why it automatically download the pit from phone and i don't now where is it (to remove him).
Like heimdall 1.3.1, i can't flash bootloader.
Tos69400 said:
The problem is the same with the old and the new version :
Code:
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...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "BOOT" does not exist in the specified PIT.
Ending session...
.
I have read the script and i can't understand why it automatically download the pit from phone and i don't now where is it (to remove him).
Like heimdall 1.3.1, i can't flash bootloader.
Click to expand...
Click to collapse
Sorry, I test it, you can't flash boot.bin from N7000, heimdall does not see it...
Thanks for your test. I have post un giithub so i am waiting for the answer.
Envoyé depuis mon N7000
Tos69400 said:
Thanks for your test. I have post un giithub so i am waiting for the answer.
Envoyé depuis mon N7000
Click to expand...
Click to collapse
there is one way to do it - to put windows on a virtual machine and flash via a pc odin ...
I have a second desktop with odinPC. Can you tell me what xan i do with it in order to help BenjaminDobell to make heimdall compatible with n7000 and boot partition ?
Envoyé depuis mon N7000
i'm curious.
The s3 and note 2 stock roms have a lot of extras packages.
simg2img.img
sboot.bin
tz.img
What are they?
And being specific the NOTE2 N71000. Then I try to flash the modem heimdal give me the answer of no partition found.
Any light?
thanks
Tos69400 said:
I have a second desktop with odinPC. Can you tell me what xan i do with it in order to help BenjaminDobell to make heimdall compatible with n7000 and boot partition ?
Envoyé depuis mon N7000
Click to expand...
Click to collapse
For flash N7000 boot.bin, you can to use ver.1.3.2, it is can see all partitions of SGNI...
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
So i noticed while searching around to fix things on my device there was a lack of linux support in general, and almost none for the S5, so I thought I would make a support thread for any linux users. This thread will be mainly for posting how-to's for linux but can also be a place to ask any questions you have.
HOW-TO'S:
How to install adb
I'm on linux mint, and this tutorial is based off of how to threads for linux mint, but there shouldn't be much difference in commands other than filenames.
To start you'll need to download the sdk, then run these commands one at a time.
Code:
cd ~
tar -zxvf ~/[download path here]/android-sdk_r23.0.2-linux.tgz
mv android-sdk-linux android
Then we need to update the SDK.
Code:
cd ~
android/tools/android
This should bring up the android SDK manager, the ones you'll want to update/install are:
-Everything under "Android 4.4.2 (API 19)
-Under the tools dropdown, check "Android SDK tools", "Android SDK Platform-tools" and "Android SDK Build-tools" revision 20
Once all that is done you'll need to set your path to include adb.
Code:
cd ~
gedit .bashrc
In the text editor that opens paste the following then save and exit
Code:
export PATH=${PATH}:~/android/sdk/platform-tools
Then we need to make it executable
Code:
cd ~
chmod a+x .bashrc
Then you need to setup device rules
Code:
cd ~
sudo gedit /etc/udev/rules.d/51-android.rules
There is a list of vendor IDs on the android dev website, but for this case Samsung's ID is 04e8 so just paste the following then save and exit.
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
Then we need to make the rules executable
Code:
cd ~
sudo chmod a+x /etc/udev/rules.d/*
Then you should be able to use adb from terminal once you plug your phone in and just do "adb devices" and a prompt should come up on your phone, if it doesnt make sure you have USB debugging enabled on your phone, if it is then unplug your phone and run
Code:
adb kill-server
adb start-server
Then plug your device back in and do "adb devices".
If you are having issues with the server not starting with sufficient permissions you need to add the full path to adb start-server to rc.local, this can be done with the folowing commands.
Code:
cd ~
sudo gedit /etc/rc.local
Then you will need to paste the following above exit 0
Code:
/home/[path]/android/platform-tools/adb start-server
Make sure to replace [path] with the actual name of your home directory then save and exit and reboot your computer, you should be able to use adb properly now.
How to flash odin image files
UNTESTED ON S5
If you have no windows computer available or do but would like to flash on linux, you can try heimdall, but apparently it doesnt fully support the s5 by default and would need to have a patch made to support the new protocol, it may work I havent had a chance to test it though. Another option is jOdin, that has a more familar interface but it has a heimdall backbone afaik so you still need a patch, so for now until said patch is made by the dev or by someone in the community, or it is tested, the only option is get to a windows computer. This section will be updated once one of the two is done.
Thanks so much, I can't believe there isn't more activity in here. I'm about to set my brand new s5 up (root, recovery) using ubuntu, so I'll post what I've learned in here : )
skorasaurus said:
Thanks so much, I can't believe there isn't more activity in here. I'm about to set my brand new s5 up (root, recovery) using ubuntu, so I'll post what I've learned in here : )
Click to expand...
Click to collapse
Nice, tell us how you doing, if you can flash a Firmware with Linux.
ice [N]ation
There is a gs5 pull request on the heimdall github, this could be good....
Sent from my SM-G900P using XDA Free mobile app
I am still getting a handshake error, is it working for anybody else?
miked63017 said:
I am still getting a handshake error, is it working for anybody else?
Click to expand...
Click to collapse
I got it to output my pit file, will test flashing tomorrow and maybe do a pull request or fork if it works.
Users of Debian Wheezy must install libusb-1.0-0-dev from wheezy-backports before compiling Heimdall (apt-get -t wheezy-backports install libusb-1.0-0-dev). I had no luck using it to get anything useful out of my S5.
My experiences in rooting my phone are detailed here: http://forum.xda-developers.com/gal...-build-date-june-3-2014-t2891621/post55826720. I suppose that once Heimdall is modified to talk fluently with the S5, then http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 should make for a good model for this guide.
dgriffi said:
Users of Debian Wheezy must install libusb-1.0-0-dev from wheezy-backports before compiling Heimdall (apt-get -t wheezy-backports install libusb-1.0-0-dev). I had no luck using it to get anything useful out of my S5.
My experiences in rooting my phone are detailed here: http://forum.xda-developers.com/gal...-build-date-june-3-2014-t2891621/post55826720. I suppose that once Heimdall is modified to talk fluently with the S5, then http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 should make for a good model for this guide.
Click to expand...
Click to collapse
Yes heimdall will work once it can talk to the s5. However, i have ran into that same problem with the tar that was mentioned in that second link. I have noticed that some files i download from the rogerwilco sites give me that issue, the all in ones from there work fine though. Did you download that tar from the rogerwilco site? Other times it has happened to me was because of a bad download, and redownloading fixed my problem. If the tar is corrupt, even heimdall wont help.
BTW i used libusb-1.0 source from github, heimdall source from github and modified heimdall source in a few places based on the simple usb logger output i got when flashing with odin. I dont think my patches would ever be merged in because it might break compatibility with other models since i had to change the buffer size. Also, i work on opensuse 64bit 13.1, in case anybody ends up trying to follow along. I plan on trying a flash a little later today.
miked63017 said:
Yes heimdall will work once it can talk to the s5. However, i have ran into that same problem with the tar that was mentioned in that second link. I have noticed that some files i download from the rogerwilco sites give me that issue, the all in ones from there work fine though. Did you download that tar from the rogerwilco site? Other times it has happened to me was because of a bad download, and redownloading fixed my problem. If the tar is corrupt, even heimdall wont help.
BTW i used libusb-1.0 source from github, heimdall source from github and modified heimdall source in a few places based on the simple usb logger output i got when flashing with odin. I dont think my patches would ever be merged in because it might break compatibility with other models since i had to change the buffer size. Also, i work on opensuse 64bit 13.1, in case anybody ends up trying to follow along. I plan on trying a flash a little later today.
Click to expand...
Click to collapse
I downloaded from sammobile.com.
Well flashing was a no go, and i cant get consistently working setup ATM. Maybe i will poke around some more throughout the week.
No way,
*with libusb
*with kernel compiled with 32 and 64 bits,
*Debian, LMDE and Ubuntu 14.04.1 (I'm using the latter).
*with jodin3 from my notebook and from the web all with negative results.
Might as well try to flash with heimdall from TTY?
ice [N]ation
Not much progress other than learning a lot about libusb, anybody else have any luck?
miked63017 said:
Not much progress other than learning a lot about libusb, anybody else have any luck?
Click to expand...
Click to collapse
I don't think so :/
ice [N]ation
Any news?
ice [N]ation
As i said, i discusssed it with miked63017, and he informed me there needs to be a modification to get heimdall to work with the s5, this was also mentioned earlier in the thread, jOdin fram what i can tell is a java front end for heimdall so same situation. As was also mentioned a fork was made of heimdall mentioning the s5, that may be worth testing, otherwise something needs to be worked on, privately or as a group.
Sent from my SM-G900A using Tapatalk
Well, I'm willing to help in my humble place
ice [N]ation
Rakuu said:
As i said, i discusssed it with miked63017, and he informed me there needs to be a modification to get heimdall to work with the s5, this was also mentioned earlier in the thread, jOdin fram what i can tell is a java front end for heimdall so same situation. As was also mentioned a fork was made of heimdall mentioning the s5, that may be worth testing, otherwise something needs to be worked on, privately or as a group.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I tested the fork with no luck. Then the thought crossed my mind to rewrite it in ruby, because I am alot better with it than I am with c++. I started, only got as far as finding the device, but it is really ambitious and will take a long time to complete. If anybody thinks they can help I will put it on githib, but be warned it is in really early stages. Let me know otherwise I will keep it to myself until its further along.
Was anyone ever able to get heimdall working on your S5 in Linux? I have been having similar problems getting it to run in Xubuntu 14.10 with my Note 4.
I compiled Heimdall with the S5 patch, even installed the latest libusb, no luck whatsoever. I am getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
I just came across this, but didn't try it out yet.
DieHappy said:
Was anyone ever able to get heimdall working on your S5 in Linux? I have been having similar problems getting it to run in Xubuntu 14.10 with my Note 4.
I compiled Heimdall with the S5 patch, even installed the latest libusb, no luck whatsoever. I am getting the following error:
Code:
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
I just came across this, but didn't try it out yet.
Click to expand...
Click to collapse
Never got it working but might try your link tomorrow if i have time
Sent from my SM-G900P using XDA Free mobile app
Disclaimer :
I'm not responsible for bricked devices, dead SD cards. This guide have not tested by anyone yet and because of that have a high chance to damage your device .Please think twice before deciding to do this guide !!!
Hello all, I was successful to extract the ofp firmware for the CN and GLOBAL version. The firmware is kind of QFIL based firmware and include patch0.xml , rawprogram0.xml , prog_firehose_ddr.elf that can be loaded on the Qualcomm QFIL tool for flashing a stock rom on EDL mode .
I do not have this phone yet so this is not tested by me but it should work .
This should work on bricked devices with locked bootloader .
This is not a full guide as I haven't tested it yet, but I will share you of my idea. I suggest to not try this if your not in hard brick and the bootloder is not locked .
Warning- This process will wipe your internal storage .
1. Extract the firmware and the 1-Qualcomm USB Driver + QFIL.7z.
2. You should install the Qualcomm USB Driver
3. Install QPST.2.7.480 , move the firmware to C:\Program Files (x86)\Qualcomm\QPST\bin .
4. Run as administration the QFIL software ,it found on C:\Program Files (x86)\Qualcomm\QPST\bin .
5. Click on the Configuration tab and then on the FireHose configuration .
6. Click on the Device Type and choose ufs .
7. Tick the "Reset after Download" and press OK.
8. Tick the flat boot circle option .
9. Click Browse on the Programmer Path and choose prog_firehose_ddr.elf in the firmware file .
10. Click Load XML and choose "rawprogram0.xml" and then choose "patch0.xml" .
Open windows device manger, boot you phone to EDL by connecting a cable to you PC and then press and hold power bottom and volume + bottom .You should see Qualcomm HS-USB QDLoader 9008, It is really important to be on QDLoader 9008 .Do not try to proceed to 11 if it does not show as QDLoader 9008 .
11. you will see the Port on the QFIL software and then choose Download .
Download -
Qualcomm USB Driver + QFIL - https://mega.nz/file/pU8FRILJ#y54f4lnq6p3T7TCITGyWRw0Kuf4ymgOt4srQ654NqUo
Extracted RMX1931EX_11_A.09 OFP (Global firmware) - https://mega.nz/file/YQ80wSwB#wflYZ-hI5O96QjTq4oc4pnovn6UoAtry2lHn7ThmbLo
CHECK MD5 !!! - 58A5C6D75787029B664FD5583F265872
Extracted RMX1931_11_A.11 OFP (CN firmware) - https://mega.nz/file/lMMlQK4K#bOCrQrg7tkKj2n6VNhS__4bBQw1RdsxTSI5XrzRpMG0
CHECK MD5 !!! - A0CCED006DF8FC0B06B0669A8325883F
Please download the firmware according to your realme x2 pro model, This probably wont work and may damage your device if you have a CN model and try flash a EU firmware and the opposite EU model and try flash a CN firmware .
UPDATE-
After long testing it seem that we can not write to or read from this phone without the realme tool, It must have a special code . I will stop searching for a way because it seems impossible without the Realme tool.
Thanks to @shilpakar7, @Designguru and @iamkgehlot for testing tools and files for many hours .
English is not my native language, please excuse any errors on my part.
Reserved
Fingers crossed ? if it works, it's going to help alot of folks!
luisarriaga said:
Fingers crossed ? if it works, it's going to help alot of folks!
Click to expand...
Click to collapse
Yes I know, It also will remove the fear of hard brick when locking the bootloder .
Furthermore if it will work for the realme x2 pro, it will work on many Realme devices that have a snapdragon CPU including the realme x2 .I just need to extract the ofp firmware of each device .
Yes absolutely! It's the only android smartphone I never unlocked the bootloader, first of all because of loosing FP if you install twrp, and there's the risk of relocking it. Let's wait for some feedback ?
Here is what I have currently
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Designguru said:
Here is what I have currently
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Click to expand...
Click to collapse
Try to immediately start flashing(choose Download ) after you have put your phone into EDL mode .Also does you see Qualcomm HS-USB QDLoader 9008 on windows device manager ?
or965 said:
Try to immediately start flashing(choose Download ) after you have put your phone into EDL mode .Also does you see Qualcomm HS-USB QDLoader 9008 on windows device manager ?
Click to expand...
Click to collapse
Here is another problem I'm seeing. I put all the files in C:\ as per your instructions. When I download from QFIL, it shows Working Folder is C:\Users\<username>\AppData\Roaming\Qualcomm\QFIL\COMPORT_3. I copied over all the files into this folder as well and am seeing the errors posted earlier.
Yes I'm showing HS-USB QDLoader 9008 (COM#)
Designguru said:
Here is another problem I'm seeing. I put all the files in C:\ as per your instructions. When I download from QFIL, it shows Working Folder is C:\Users\<username>\AppData\Roaming\Qualcomm\QFIL\COMPORT_3. I copied over all the files into this folder as well and am seeing the errors posted earlier.
Yes I'm showing HS-USB QDLoader 9008 (COM#)
Click to expand...
Click to collapse
Try uninstall the qfil and install this version https://mega.nz/file/hFdDDKBK#szUu2TqPdd6VO_XLKfYIu9pJ6yYT0LbaeZqTaIEQ8Fo
put the firmware on C:\Program Files (x86)\Qualcomm\QPST\bin
or965 said:
Try uninstall the qfil and install this version https://mega.nz/file/hFdDDKBK#szUu2TqPdd6VO_XLKfYIu9pJ6yYT0LbaeZqTaIEQ8Fo
put the firmware on C:\Program Files (x86)\Qualcomm\QPST\bin
Click to expand...
Click to collapse
Done. Here is where it fails now
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
19:17:51: DEBUG: XML FILE (115 bytes): CharsInBuffer=315-115=200
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
19:17:51: DEBUG: XML FILE (94 bytes): CharsInBuffer=200-94=106
-------------------------------------------------------------------------------------------
Designguru said:
Done. Here is where it fails now
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
19:17:51: DEBUG: XML FILE (115 bytes): CharsInBuffer=315-115=200
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
-------------------------------------------------------------------------------------------
19:17:51: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
19:17:51: DEBUG: XML FILE (94 bytes): CharsInBuffer=200-94=106
-------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
or965 said:
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
Click to expand...
Click to collapse
When I hit flash, here is what I get under status
"The filename,directory name, or volume label syntax is incorrect (0x8007007b: Open programmer "MPRG*hex")
what about using qpst tool as mentioned in https://www.getdroidtips.com/stock-rom-realme-x2-pro/ Method 3. The above mentioned url contains guide for chinese ROM but since you have ofp firmware for global version. Will this method work?
it fails during dowload process. I have attached the log.
Total to be tansferd with <program> or <read> is 8.98 GB
09:09:35: INFO: Sending <configure>
09:09:35: INFO: TARGET SAID: 'INFO: Binary build date: May 17 2019 @ 23:12:26'
09:09:35: INFO: TARGET SAID: 'INFO: Binary build date: May 17 2019 @ 23:12:26
'
09:09:35: INFO: TARGET SAID: 'INFO: Chip serial num: 1387265276 (0x52affcfc)'
09:09:35: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
09:09:35: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
09:09:35: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
09:09:35: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
09:09:35: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
Writing log to 'C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt', might take a minute
Log is 'C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_4\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
or965 said:
Maybe we should try to use other software to flash ,try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash ,if you have an error, try to go to the firmware and change setting.xml name to flash_local.xml and try to flash again .
Click to expand...
Click to collapse
Let me provide a couple of tips here: When pointing to the path of your extracted files in C : copy paste the path directory using the mouse.
If you have a firehose connection error , disconnect the usb cable and reconnect only to a usb2 port ( use a hub if needed) QPST can be setup to not start until you connect the phone.
Next, if facing a signature issue. temporarily disable antivirus and firewall and Windows signature enforcement if absolutely necessary.
This can all be easily re enabled afterwards.
If you face any other issues, refer to my old guide for troubleshooting ideas. here for additional things to try. I have personally helped possibly over a hundred people unbrick their phone
These steps are identical for most qualcomm phones. obviously use only qfil repair files made for your device and not from my link.
PS : Firehose fail error does not necessarily mean that the process will fail, just wait longer, up to 15 to 20 minutes, sometimes you will get that error and it will sort itself out. restart the process all over again, but wait for 15 minutes on each attempt. Also disconnect peripheral devices from other usb ports. it is very important that you use a USB 2 port or a usb hub.
Once the rom is restored the phone should reboot to the set screen up on it's own.
tsongming said:
Let me provide a couple of tips here: When pointing to the path of your extracted files in C : copy paste the path directory using the mouse.
If you have a firehose connection error , disconnect the usb cable and reconnect only to a usb2 port ( use a hub if needed) QPST can be setup to not start until you connect the phone.
Next, if facing a signature issue. temporarily disable antivirus and firewall and Windows signature enforcement if absolutely necessary.
This can all be easily re enabled afterwards.
If you face any other issues, refer to my old guide for troubleshooting ideas. here for additional things to try. I have personally helped possibly over a hundred people unbrick their phone
These steps are identical for most qualcomm phones. obviously use only qfil repair files made for your device and not from my link.
PS : Firehose fail error does not necessarily mean that the process will fail, just wait longer, up to 15 to 20 minutes, sometimes you will get that error and it will sort itself out. restart the process all over again, but wait for 15 minutes on each attempt. Also disconnect peripheral devices from other usb ports. it is very important that you use a USB 2 port or a usb hub.
Once the rom is restored the phone should reboot to the set screen up on it's own.
Click to expand...
Click to collapse
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
https://pastebin.com/vYjC5rxq
And here is my log from C:\Users\Pawan-PC\AppData\Roaming\Qualcomm\QFIL\COMPORT_5 port_tra
ce.txt
https://pastebin.com/2VynsCD7
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
First just a friendly tip, when people spend time helping at the very least, click the thank you button otherwise what is their motivation? When posting logs, post it as an attachment ( XDA Rules) its clutters threads.
The bootloader destroyed is no big deal, it's resolved by flashing the boot image. The real issue is the key mismatch error. You need to use the fastboot rom only from your device model. Example : Global versus Chinese.
Finally, I do not own that phone so there isn't ,much more I can contribute. However, I am, certain that you will eventually solve it, try another fastboot rom, be patient ( this could take days the first time) and take notes, so when you are finished you can help other people.
I would suggest that you contact others within the realme community that have had bricks. for example I have seen that people have had success with other real me 3s. You may better off joining Telegram and connecting with user's on the Global scale. You can find telegram groups by searching keywords.
Finally, @or965 stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Good Luck.
Click to expand...
Click to collapse
ok thank you for your advice, I will definitely take it as a reminder. I have uploaded the log file to pastebin.com and postel the url link. Since you don't personally have the device, I shouldn't have asked for more help. Anyways thank you for your valuable time. Since this is so frustating, I guess i will just send it to service center for repair.
tsongming said:
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
First just a friendly tip, when people spend time helping at the very least, click the thank you button otherwise what is their motivation? When posting logs, post it as an attachment ( XDA Rules) its clutters threads.
The bootloader destroyed is no big deal, it's resolved by flashing the boot image. The real issue is the key mismatch error. You need to use the fastboot rom only from your device model. Example : Global versus Chinese.
Finally, I do not own that phone so there isn't ,much more I can contribute. However, I am, certain that you will eventually solve it, try another fastboot rom, be patient ( this could take days the first time) and take notes, so when you are finished you can help other people.
I would suggest that you contact others within the realme community that have had bricks. for example I have seen that people have had success with other real me 3s. You may better off joining Telegram and connecting with user's on the Global scale. You can find telegram groups by searching keywords.
Finally, @or965 stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Good Luck.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Designguru said:
When I hit flash, here is what I get under status
"The filename,directory name, or volume label syntax is incorrect (0x8007007b: Open programmer "MPRG*hex")
Click to expand...
Click to collapse
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 and try to flash with miflash like I write in the last message .
shilpakar7 said:
can you please check my log mentioned above.
Edit:
Now the QFIL says download succeed (command prompt flashes for few seconds) but it doesn't flash the firmware , since i am stuck in same problem.(bootloop displaying " your recover/bootloader has been destroyed...").
Here is my log
https://pastebin.com/vYjC5rxq
Click to expand...
Click to collapse
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 .
try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash.
Finally said:
@or965[/user] stated that he successfully restored his phone that is identical to yours...I think. I would definitely speak with him and if he helps you unbrick your phone, I would absolutely buy him a beer.
Click to expand...
Click to collapse
I did not have this device yet so I do not successfully restored my phone .
or965 said:
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 and try to flash with miflash like I write in the last message .
Please crate a folder Realme_x2_pro on your root C drive and move the firmware to it,then rename the firmware to RMX1931EX_11_A_09 .
try to download this - https://mega.nz/file/tM9CDIbS#BOqaetCpD2NKEjXPLO_EGB9RHTcTTY0HMpRzMqYVhDA
Unpack and open MiPhone20160401, click next and then install this driver software anyway ,go to
C:\Program Files\Xiaomi\MiPhone and run MiFlash, click browse and choose the folder of the firmware ,boot into edl mode ,click refresh and when you see the device click flash.
I did not have this device yet so I do not successfully restored my phone .
Click to expand...
Click to collapse
this method also not working. The status tab on MiFlash displays same message as mentioned by designguru