Related
Hey all, sorry I'm not posting this in the Heimdall thread but I don't have enough posts so making a thread here. I've been getting the error "Handshaking with Loke... Failed ERROR: Failed to receive response!"
I'm trying to follow the instructions on the Cyanogenmod wiki for Galaxy S2 but I just cannot flash the kernel. I have flashed an insecure stock kernel to get root in the past using Odin but Heimdall just doesn't want to work.
Any help will really be appreciated, thanks in advance.
What OS do you run?
It's necessary to tell, because Heimdall runs on Linux, Windows & OSX.
Sent from my GT-I9100 using XDA App
Sorry I forgot to mention, using Windows 7 Ultimate 64-Bit.
Did you update the usb drivers using zadig.exe before trying to use Heimdall?
yup, updated the usb drivers for both ports I used and checked they were updated even when switching cables etc.
So you installed the drivers that come with Heimdall?
Did you make sure that KIES and such our closed?
Did you run as administrator?
A side note:
I can only do one operation at a time. That means that after I downloaded the pit-file I can't flash directly. I have to reboot the phone into download-mode again.
Sent from my GT-I9100 using XDA App
willypiggy said:
Hey all, sorry I'm not posting this in the Heimdall thread but I don't have enough posts so making a thread here. I've been getting the error "Handshaking with Loke... Failed ERROR: Failed to receive response!"
I'm trying to follow the instructions on the Cyanogenmod wiki for Galaxy S2 but I just cannot flash the kernel. I have flashed an insecure stock kernel to get root in the past using Odin but Heimdall just doesn't want to work.
Any help will really be appreciated, thanks in advance.
Click to expand...
Click to collapse
I'm using a Mac so i dont know if this will work for you but the CM update guide links to Heimdall 1.3.1 and ive never been able to make it work... what i had to do was install the Heimdall 1.2.0 command line binaries and flash the CM kernel through the Terminal/Command. heres the link for the windows version https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-1.2.0-win32.zip
I did install the drivers it came with, Kies was not running, I did run as admin.
I tried 1.2 and it just gives me the error "Failed to open file "zImage""
Are you using the Heimdall frontend (like ODIN) or just Heimdall (command line)?
I find the frontend is easy to use if you aren't familiar with using the shell applications... You simply pick the files you need and insert them into the section you want to flash....
Much easier....
I'm using the command line as it says in the guide, I'll give it a go using the frontend and see if that comes up with anything different.
EDIT: Trying to use Odin to flash the kernel seems to have worked, my current kernel is now [email protected] #4 but nothing appears to have changed especially that I still can't seem to see a new version of CWM. Should I proceed wit the second part of the tutorial?
EDIT2: Followed the instructions and now have (what seems to be) fully working cyanogen mod. Not sure why on earth the command line method of flashing wasn't working but odin sure did the trick.
willypiggy said:
I did install the drivers it came with, Kies was not running, I did run as admin.
I tried 1.2 and it just gives me the error "Failed to open file "zImage""
Click to expand...
Click to collapse
Although you've managed to do the job with ODIN, I think I better tell you what you did wrong with Heimdall.
(On Windows) Heimdall comes with its own drivers. You need to install them. To do so, you use the "zadig.exe" file insode the "..\Heimdall\drivers" folder. You install the driver for "Samsung USB Composite device" or "Gadget Serial". Then it works.
TheSniperFan said:
Although you've managed to do the job with ODIN, I think I better tell you what you did wrong with Heimdall.
(On Windows) Heimdall comes with its own drivers. You need to install them. To do so, you use the "zadig.exe" file insode the "..\Heimdall\drivers" folder. You install the driver for "Samsung USB Composite device" or "Gadget Serial". Then it works.
Click to expand...
Click to collapse
Glad Odin did get the job done but I was installing the USB Drivers and I checked and reinstalled them multiple times so it can't be that
You need to rollback the usb drivers to successfully use ODIN. If you didn't need to then you didn't successfully install the Heimdall usb drivers...
I just instaled this:
Release: Heimdall Suite 1.3.2 (Binaries)
Platforms: OS X 10.4+ (Universal – x86/AMD64/Intel 64)
License: MIT License
Includes:
Heimdall command line tool.
Heimdall Frontend.
Codeless kext (aka driver).
And still getting: "Handshaking with Loke... Failed ERROR: Failed to receive response!".
gepardek said:
I just instaled this:
Release: Heimdall Suite 1.3.2 (Binaries)
Platforms: OS X 10.4+ (Universal – x86/AMD64/Intel 64)
License: MIT License
Includes:
Heimdall command line tool.
Heimdall Frontend.
Codeless kext (aka driver).
And still getting: "Handshaking with Loke... Failed ERROR: Failed to receive response!".
Click to expand...
Click to collapse
I know i'm digging up this thread, but i have an answer and a question (relative of course)
ANSWER
I had the same problem. I solved it when i realized that i have had installed Heimdall Suite 1.3.2 (Binaries) (as you did) and also copied (following the directions of a tutorial) the [email protected]/opt/local/lib/.
ALSO after every change, its a MUST to remove the battery (my i9000-international- right now is softbricked thnks to the "swiftness" of my actions ) and reopen the "Download Mode".
QUESTION
As i said i'm using -also- the "Heimdall Suite"; at the "Flash tab" i'm not sure which partitions to associate with which files. I tried to follow the association from the post below, but i couldn't find most of the files the kind dude is proposing.
I'm trying to flash the cm-10.2-20131006-NIGHTLY-galaxysmtd. My phone is a galaxy s1 i9000 international 2.3.6 Android not rooted.
Thank you in advance for any suggestion/advice/curse/direction/documentation
ps: sorry forgot to post the links:
https://gurde.com/2012/08/how-to-install-android-jelly-bean-on-galaxy-s-i9000/#comment-42
http://forum.xda-developers.com/showthread.php?t=2244251
Sorry for the second post but great news!!!!
heimdall's (frontend) function "Print PIT" restored my phone from "softbrickness"!!!
Also found what the partition's acronyms at the "Flash" tab of heimdall means:
IBL+PBL is the boot loader, be extra careful with it;
PIT is the partition table;
EFS contains some important data like IEMEI, be extra careful with it;
SBL is the second boot loader;
SBL2 is the backup of the second boot loader;
PARAM contains some images used as various stage of the boot process;
KERNEL is the kernel;
RECOVERY is the backup of the kernel;
FACTORYFS contains /system file system which is some kind of root file system;
DBDATA contains /data file system which is the database to store application parameters;
CACHE contains /cache file system which contains the Dalvik cache;
MODEM contains the firmware for the modem.
Click to expand...
Click to collapse
the relative bin files i've found at the cm-10.2-20131006-NIGHTLY-galaxysmtd rom are:
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/modem.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/de-DE_gl0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/de-DE_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-GB_kh0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-GB_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-US_lh0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/en-US_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/es-ES_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/es-ES_zl0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/fr-FR_nk0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/fr-FR_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/it-IT_cm0_sg.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/tts/lang_pico/it-IT_ta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/cypress-touchkey.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/fw_bcmdhd.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/fw_bcmdhd_apsta.bin
/Users/Lopofsky/Downloads/cm-10.2-20131006-NIGHTLY-galaxysmtd/system/vendor/firmware/samsung_mfc_fw.bin
Click to expand...
Click to collapse
Also this is my PIT file (in case anyone can give me an insight):
Code:
Entry Count: 13
Unknown 1: 1
Unknown 2: 0
Unknown 3: 7508
Unknown 4: 65
Unknown 5: 64224
Unknown 6: 18
Unknown 7: 55304
Unknown 8: 67
--- Entry #0 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 6684783
Unknown 3: 2097268
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename:
--- Entry #2 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 20
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.rfs
--- Entry #3 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: sbl.bin
--- Entry #4 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 4
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename: sbl.bin
--- Entry #5 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 21
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 22
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1146
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 23
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 0
Unknown 3: 0
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 24
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 140
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Chip Identifier: 0 ((null))
Partition Identifier: 11
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 50
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #12 ---
Unused: Yes
Chip Identifier: 1 ((null))
Partition Identifier: 11
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
reposting just in case somebody knows how to make the file-to-choice association i ask above with the new information i provided.
thank you for your comprehension and sorry for the inconvenience
Hey guys I have a strange situation, when I went on holiday skiing it was so cold my phone went out.
But after that it wouldn't boot anymore, it stays on the samsung screen (with yellow triangle from rooting).
Now I can still get in download mode but not recovery mode.
I tried flashing a official ROM on it, it says its succesfull but it doesn't seem to be as there is still a yellow triangle and it still says custom binary and won't start.
Then I tried flashing kernel / PIT with partitioning etc etc, everything it says is succesfull but still doesn't do anything.
Now I want to send it in for guarantee, so I used a jig to reset the counter and custom binary to official Samsung Rom.
This worked ....
Then after leaving the battery out for a few days, I put it back in and the counter is back to 2 and Custom rom ....
Seems I'm screwed now for guarantee, but it really was do to the cold ....
What could be broken ?
Nobody that can help ?
My guess it is the kernel.
I had faced the same issue and fixed it by flashing the right kernel.
What is your phone model? and what kernel did you flash?
Let's take it step by step. Can you post the history of what files you flashed in order to figure out where the problem happened?
Well the problem happend when I was outside in -25 degrees....
The phone was working at that moment with ICS on it.
I also get this when putting my phone in the charger, the circle is not animating and there is power in the battery .... so this is a still image....
It also stays when u pull it out of the charger...
{
"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"
}
Honestly, I'm starting to think it is a hardware issue and maybe you froze your phone dead. Have you checked the operation temps limits in the user manual?
Is it warm now? Try to keep it like 3 feet away from a heater for like an hour and try to turn it on again. I sure hope only the battery is dead and nothing else. Try to switch batteries with someone else and see what happens.
I'm still puzzled by not being able to get to CWM and only download mode. Let us figure out if it is working or not before trying to flash stuff.
Just to make sure, what is the phone model and last kernel and ROMs you flashed before all this?
The phone is like this already for 2 weeks orso
I switched batteries with a working SII, same result...
I tried everything from this thread, http://forum.xda-developers.com/showthread.php?t=1457458
no results ...
So that was the XXKI3
And I tried the latest official one from Kies ....
Ah phone model is GT-i9100
OK. Following that thread should fix your phone. But let's do it step by step.
1. Remove micro sd card if you have one.
2. get odin.
3. get a good kernel for your phone. Which one were you using? you can get one from here http://forum.xda-developers.com/showthread.php?t=1485162.
4. Now let us try to get to CWM. I had trouble sometimes getting there. Probably you know how. For revision: hold vol.up home and the power while your phone is off. to shut it off you can remove the battery and put it back again. So, keep holding until you see the screen is on and release. it will get there (hopefully).
Try and reply back to see what else we can do.
Tried that with I9100XWKK2_I9100KPNKJ1_I9100XXKI4_HOME.tar
No joy, only download mode ....
It said flashing was successful tho ..
Wow. I, my friend, rest my case.
I would really like to help you out. But don't know how further. I'm really hoping that you are going to figure it out. If you get any step further than what you are on right now I'll be happy to help you.
One last thing is look for a PIT file that works for your phone and check the re-partition option in odin while flashing.
I would finally suggest a trip to a service center.
Do you know by any chance if they accept rooted phones if it is a hardware failure ?
Oh and I got this when checking the PIT with Heimdall,
Initialising connection...
Detecting device...
Claiming interface...
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
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 204800
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 311296
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 344064
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1392640
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5586944
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename:
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
They usually don't care. But, playing the idiocy and ignorance to what is going on card and smooth talking helps a lot in case they are a little picky.
OK. regarding the re-partition, choose the PIT file and a ROM that works and the ROM has the kernel and everything needed for a full install. they are usually bigger in file size 200-500 megabytes.
The thing is my phone is a G model so all the files I use are different than yours and can not recommend them.
Thnx for the help !
I tried a PIT file and a ROM aswell, still no luck ...
So I'll send it in tomorrow for guarantee, cross the fingers that they don't make a hassle....
Afternoon all,
Where to start...
The other day my S2 with CM10.1 nightly 29/03/13 ran out of power (again). No big deal I thought so it got charged up and turned on later. It sat at the bootloader splash screen, and never continued.
The issue is that it won't go into recovery mode, and it won't boot any further than the bootloader. I can't connect via adb, and there's no way of flashing a new ROM or a recovery ROM from the device itself.
I've tried Odin, and it hangs at NAND Write Start whilst trying to push on a clockworkmod recovery image - which is a bit worrying. I've tried different cables and different ports, but this is always the furthest I get. I've used Heimdall to get a copy of the PIT, which is attached below for reference in plain text and binary - so I can communicate with the device, but I'm wondering if it's suffered from a flash corruption or some sort of failure?
My question is...
Can somebody provide a copy of the PIT from a working i9100? I'd like to compare a known good copy with mine.
Is the PIT for a CM10.1 i9100 different from a stock i9100?
If I were to reflash the CM10.1 ROM, will my /data partition be safe?
If I were to 'factory reset' or flash a stock ROM somehow, will my /data partition be safe?
I have backups courtesy of TitaniumBackupPro, and Dropbox, but not of the photo collection (mea culpa) - is there any possible way to grab the /data partition?
Many thanks
Kyle
[email protected]:~/src$ sudo heimdall print-pit
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
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 204800
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 311296
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 344064
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1392640
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5586944
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename:
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
ERROR: Failed to receive session end confirmation!
Re-attaching kernel driver...
[email protected]:~/src$
Have u tried this thread?
http://forum.xda-developers.com/showthread.php?t=1457458
"To err is human, to forgive is divine"
Sent from my SGS II
Borked NAND is my guess. Possibly JTAG'able, maybe motherboard replacement.
I had the same problem a while ago with my sgs2, unfortunately i couldn't revive it, i ended up sending it to the repair center, turned out a hardware problem.
Messing with PIT is not the best solution though, but good luck anyway.
@immortalneo I have thanks
@MistahBungle That's my fear. Really wishing I'd symlinked DCIM to removable storage
@silv3rfox Glad to hear I'm not alone with this. Did it come back with fresh firmware or was your data intact?
I've managed to get in via adb shell, even though the screen is blank. There's a very limited filesystem, and all attempts to read from /dev/block/mmcblk0 eventually time out and result in the hardware rebooting and kicking me out - possibly a watchdog.
I hoped to dd /dev/block/mmcblk0p* to a microsd card as I can access external cards, but as I say it always times out and leaves a 0K length file on the card.
I'm prepared to pay up for the recovery of data from the phone, so I was wondering if there's any recommended recovery/repair centers? All I'd like is a copy of the filesystem on the flash (it sounds so simple I'll happily chuck the phone away once I have that!
Cheers
Best bet is to ask local mobile repair shops if they're capable of recovering your data, failing that contact companies that normally recover data from conventional hard drives. You may get lucky.
Many thanks. I've done just that, and have emailed Kroll and a few others.
I'll post here with the results, if there are any
Well, I had a discussion with Kroll Ontrack... apparently I've done everything their expert phone engineers would do, and the next stage is physical removal of the chip - which is something they don't do
My initial thought is to move the flash chip to a known working motherboard - so I'm about to get in touch with reworkbga.com about the task.
The PIT data - where is that stored? Is it on flash or elsewhere? Surely if reading the flash is the problem then it wouldn't be able to load the PIT? Just trying to throw some doubts into my process at the moment!
Well, just to close this one off, I got in touch with local authorised Samsung repair shop and they took it in. It ultimately went away for a new motherboard - as expected the whole thing was knackered.
Had to suffer the loss of 6 months of photos. Live and learn!
Hey all.
Sorry if this has been asked before, but I can't seem to find a proper answer on the forums. Am using Heimdall 1.4 rc1/2, on Arch Linux.
Not sure whats happened to my phone as its been flashed so many times in the past, and can't remember what might have caused this.
First time using Heimdall, as I got sick of having to keep a partition spare for XP which in the end only got used for flashing to the S2
I would really like a stock PIT file or even some feedback as to whether my partitions are correct?
Notice that the Boot partition is read only and I also have an SBL1 and an SBL2???
Please help....
HTML:
Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GANG
Flash Filename: emmc.img
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 8192
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 49152
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: Sbl.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 53248
Partition Block Count: 2560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename:
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 57344
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 73728
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 90112
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename:
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 106496
Partition Block Count: 204800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 311296
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 344064
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash Filename: factoryfs.img
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 1392640
Partition Block Count: 4194304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: data.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 5586944
Partition Block Count: 24133632
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UMS
Flash Filename:
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 1 (Read/Write)
Update Attributes: 0
Partition Block Size/Offset: 29720576
Partition Block Count: 1048576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 1 (CP)
Device Type: 1 (File/FAT)
Identifier: 9
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash Filename:
FOTA Filename:
Can someone tell me if the partitioning for a Gingerbread S2 work with a Jelly Bean ROM. I can build a PIT file off my Dads galaxy S2 which has never been touched. Not sure what it looks like yet as I need to get hold of him (and his phone).
If anyone's running JellyBean perhaps you can generate a PIT file with Heimdall and send it across to have a bash with?
Hutchism said:
Can someone tell me if the partitioning for a Gingerbread S2 work with a Jelly Bean ROM. I can build a PIT file off my Dads galaxy S2 which has never been touched. Not sure what it looks like yet as I need to get hold of him (and his phone).
If anyone's running JellyBean perhaps you can generate a PIT file with Heimdall and send it across to have a bash with?
Click to expand...
Click to collapse
Hi, one time I broke the partition information and I used the attached file to fix it.
I hope it helps.
Running stock jelly bean by the way.
Regards
JP
Thanks for digging that out for me pacmanman! I did also manage to find one for download over at Droidevelopers.com. If anyone needs pit's for future reference they have a good selection www . droidevelopers.com /f363/11722-%5Bdownload%5D-ops-pit-files.html
^Wouldn't let me post the link ^^^^
Turns out that my tables are as they should be so no cause for concern. Just a little user error on my part. Wouldn't let me write the BOOT partition, so I just left it out. To be honest I don't really understand the partitions on these things. I thought the boot partition was required, but its 0 in size. Never paid any attention to it in the past.
BIG WARNING. IF YOU DON'T KNOW WHAT YOUR DOING WITH PIT FILES THEY WILL LIKELY KILL YOUR PET RABBIT!!!!!!
Big thumbs up for Heimdall. Easy once you know how
Incidentally this was my useage:
Open 2 terminals or 1 and copy the partition lists into a text editor for reference.
"heimdall" on its own gives you the useage and options
"sudo heimdall print-pit" gives the partitions on your phone as shown in the original post.
Reference the partition names with the files in the ROM as shown below.
"sudo heimdall flash --SBL1 Sbl.bin --PARAM param.lfs --KERNEL zImage --CACHE cache.img --MODEM modem.bin --FACTORYFS factoryfs.img --HIDDEN hidden.img --verbose --no-reboot"
If anyone wants to correct me on the above please be my guest, as I just used it as surmised.
Your command looks perfect to me.
BTW. Heimdall/Samsung is using boot.bin and BOOT as names for the primary boot loader (and normally you shouldn't need to flash this), while on other systems boot-partition / boot.img is exactly that what Heimdall/Samsung is calling KERNEL / zImage
Sent from my Nexus 7 using xda app-developers app
Aaah, thank you. Excuse my ignorance, but is it reporting the block size to be 0 because it uses less than a full block for BOOT?
How do I go about writing the boot image to BOOT as I still seem to have clockworkmod on this partition and Heimdall brings up an error for this partition, assumedly because the BOOT partition is Read-Only?
SGS2 stores kernel and recovery combined in the kernel partition, i.e. the zImage (which is flashed to kernel partiyion) is for booting the rom as for launching recovery.
Sent from my GT-I9100 using xda app-developers app
I hear you there, but it seems there are actually 2 bootloaders?
i,e, there can be 2 different versions of clockworkmod installed at the same time. One is called by pressing the combination at boot. The other can be called by restarting the phone into.
After flashing the phone it restarted into a broken version of clockworkmod (similarly this same version would be called from if you have the option in android to restart in recovery mode). Switching the phone off and on again had me booting into Android, while using UP, HOME + POWER had me at the default Android recovery menu.
Quite strange....
Probably you have flashed one "new" kernels, I.e. Philz 4.93 or something like that. These have the possibility to boot different kernels depending on the buttons you are pressing when recovery is started. I didn't look very deep into that new feature yet, but as you describe your phones behaviour it must be something like that. Probably the 'second' kernel is again a kernel having CWM included so that your phone boots sometimes into one and other times into the other CWM.
Edit: no, I was wrong, it s not, that a different kernel is started, but you can define some boots scripts which will be executed on startup. Nevertheless also from here you can start CWM it provocate strange behavior.
Sent from my Nexus 7 using xda app-developers app
Read Only?
I am a noob with this but all the partitions listed on my pit file are marked as read-only and I'm curious as to whether or not these attributes can be changed to read/write so I can flash to these partitions or if that is done by flashing a different pit file and if so how do you flash just a pit file
Using heimdall on Linux mint
Hello,
My verizon samsung galaxy note 2 sch-i605 phone rebooted all of a sudden when I clicked on a text message. Since then it is stuck in a boot loop. I tried booting into clockwork recovery mode using Vol Up + Power + Home but then it shows me the 'TEAMWIN' screen and then continues bootlooping. I have tried everything for the past 4 hours and read about 30 articles. I have tried changing the recovery program to TWRP, installed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 via odin, repartitioned the phone via odin using sch-i605-16gb.pit. However, nothing changes the phone stays in bootloop. What else can I do?
salilsurendran said:
Hello,
My verizon samsung galaxy note 2 sch-i605 phone rebooted all of a sudden when I clicked on a text message. Since then it is stuck in a boot loop. I tried booting into clockwork recovery mode using Vol Up + Power + Home but then it shows me the 'TEAMWIN' screen and then continues bootlooping. I have tried everything for the past 4 hours and read about 30 articles. I have tried changing the recovery program to TWRP, installed CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 via odin, repartitioned the phone via odin using sch-i605-16gb.pit. However, nothing changes the phone stays in bootloop. What else can I do?
Click to expand...
Click to collapse
Ok..
So you are unlocked... what and where did you get that tar you are flashing..
You can try a couple things..
Find the data corruption thread..stickied in general.. flash stock recovery and do a factory reset. . Follow the directions. . See if that brings you or of the boot loop..
Flash that with the pit file in odin..
Report back here if that fixes it.. if not we'll move on
Sent from my SCH-I605 using XDA Premium 4 mobile app
lacoursiere18 said:
Ok..
flash stock recovery and do a factory reset. . Follow the directions. .
Click to expand...
Click to collapse
This is exactly what I did following the directions in http://forum.xda-developers.com/showthread.php?t=2024207 . I downloaded the Official VRALJB 4.1.1 12/9/12- http://www.androidfilehost.com/?fid=9390214368362234374 mentioned in the above page. I flashed the pit file using Odin. Nothing is getting me out of the bootloop. It is like the custom recovery etc. I am flashing has no effect at all of the phone.
I want to completely clean out the ROM including the bootloader etc. and install a new ROM. Unfortunately I am unable to connect using ADB either because my phone is not in USB debugging mode. It doesn't enter recovery mode and any of the custom recovery or ROMs I flashed to the phone is not taking effect?
I have given up. My phone is completely bricked. I installed the latest 4.3 OTA , latest firmware from Samsung and TWRP but it is as if my phone is in read only mode and nothing at all changes and the same boot loop happens again and again. Right now my only option is to take it back to Samsung but it is not under warranty since it about 1 year 5 months old. I live in the South Bay Area, California. Anywhere nearby I can take the phone to have the ROM physically replaced?
You will need to start completely over with this phone. I had the same issue.. Taking it back to stock and re rooting it did the trick. Partitions are hosed.
drarkanex said:
You will need to start completely over with this phone. I had the same issue.. Taking it back to stock and re rooting it did the trick. Partitions are hosed.
Click to expand...
Click to collapse
I have already tried taking in back to stock etc. reinstalling recovery etc. Nothing makes a difference. Odin says pass but there is no change in hte phone it goes into the same boot loop over and over again.
I had to do mine about 4 or 5 times. I thought i had bricked my phone too because mine rebooted by itself while i was in facebook. Then didnt comeback up. Make sure you run odin with admin rights on win 7
drarkanex said:
I had to do mine about 4 or 5 times. I thought i had bricked my phone too because mine rebooted by itself while i was in facebook. Then didnt comeback up. Make sure you run odin with admin rights on win 7
Click to expand...
Click to collapse
So did you not change anything during 4-5 times of flashing?
No.. No changes.. Got it back up on the stock rom. When it came back up i let it sit for 30 min to make sure it took
Also for good measure.. Redownload the stock rom again.
salilsurendran said:
I have already tried taking in back to stock etc. reinstalling recovery etc. Nothing makes a difference. Odin says pass but there is no change in hte phone it goes into the same boot loop over and over again.
Click to expand...
Click to collapse
salilsurendran said:
So did you not change anything during 4-5 times of flashing?
Click to expand...
Click to collapse
This is because your recovery partition is borked (Broken) you need to look into a program called Heimadell.. It allows you to flash img's separately .. In this case you need to flash a stock recovery.img..
lacoursiere18 said:
This is because your recovery partition is borked (Broken) you need to look into a program called Heimadell.. It allows you to flash img's separately .. In this case you need to flash a stock recovery.img..
Click to expand...
Click to collapse
I already used Heimadell. Like I said it seems that my phone is in read only mode. Is there any way I can make my sd card bootable and force my phone to boot from it rather than the rom?
Anyway to put the Verizon Samsung Galaxy Note 2 in fastboot mode?
I was able to use Heimdall suite and download the PIT file. I then flashed the stock rom using Heimdall and repartitioned it using the PIT file. I then redownloaded the PIT file and nothing changed. I then tried flashing the 4.1.2 ROM using Heimdall. Downloaded the PIT file again. There was no change at all. Heimdall and Odin seem to be able to access my system and reports 100% success when it comes to flashing the *.img files but the PIT file reports no changes. When I use ADB devices or fastboot devices command they report no devices attached. Is there any software that can let me explore the phone in download mode. Note I am not able to get to recovery or a fastboot mode(if different from download mode). Here is the PIT file from my system as reported by Heimdall:
Heimdall v1.4.0
Copyright (c) 2010-2013, 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/
Entry Count: 22
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 30797
Unknown 4: 19757
Unknown 5: 19780
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 82
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: bootloader
Flash Filename: swagBoot
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: t0.pit
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 73728
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 106496
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 122880
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 60
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 122880
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: recovery
Flash Filename: recoverThis
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139264
Partition Block Count: 180224
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 319488
Partition Block Count: 524288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 843776
Partition Block Count: 3145728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3989504
Partition Block Count: 4718592
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 8708096
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8749056
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 8765440
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
When you put your phone in Odin mode what does it display? Anything about Knox warranty? You said in one of your previous post that you tried the 4.3 ota. If the bootloader updated when you did that then using Odin to flash anything lower than 4.3 won't work.
No when I put it in Odin mode it says:
ODIN MODE
PRODUCT NAME: SCH-I605
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
I did several flashes of stock ROMs but nothing has changed in the phone. The PIT file is the exact same PIT as is supposed to be originally as mentioned in this page http://forum.xda-developers.com/showthread.php?t=2118348&page=102 as the link https://dl.dropboxusercontent.com/u/13769093/note2_i605_t0.pit