Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...
Lhon0901 said:
Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...
Click to expand...
Click to collapse
Uncheck the partition box. Whenever it's grayed out, it means that for one of your options you haven't met the pre-reqs. For example partition requires a PBL, SBL and a recovery file I believe. Error -12 after clicking start refers to a driver issue.
Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps
btyork said:
Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps
Click to expand...
Click to collapse
Okay, I'll try the partition part and see if it works, but I beleive it's not checked as I put no file in it... As for the second post, yes, I have found the firmware I need but it's extracted and not in tar form... That's why I need heimdall...
Maybe if somebody can point me on how to compile it to TAR again I'll just use odin...
***Added: I got my hands on a DXKM3 firmware that came with my phone here. Now if someone can help me put those files again in the TAR format I would be very glad... Getting heimdall to work would, too...
Thanks for the replies!!!
You're right!!! I failed to notice that factory.rfs is not yet extracted, and "Start" magically became selectable!!!
I feel kinda stupid... T_T
Was able to flash now... Thanks for the help guys!!!
Related
I have recently switched to Heimdall as I have been having reliability problems with Odin (V1.7 Windows7. XP3 compatibility , administrator.)
I nearly bricked a friend's phone with it when it baulked after uploading the pit (needed making the 300k resistor force download cable!). On my machine it now just wont connect ... enter Hiemdall to the rescue.
However I was forced to unpack the archive in Hiemdall and apply all the files separately as there was no apparent way to use the pit + whole tar file
Whiles this worked its a bit risky if you do it at 2am and the boxes in Heimdall could be more clearly separated.
Is there any way not shown to use the whole tar file in Hiemdall?
I say this because although i am now the proud owner of an Insanity 009 galaxy I will have to use Hiemdall to flash back to "stock" 2.3.3 rooted before i can try a different rom because of the way CM7 changed the filesystem.
tazzydemon said:
I have recently switched to Heimdall as I have been having reliability problems with Odin (V1.7 Windows7. XP3 compatibility , administrator.)
I nearly bricked a friend's phone with it when it baulked after uploading the pit (needed making the 300k resistor force download cable!). On my machine it now just wont connect ... enter Hiemdall to the rescue.
However I was forced to unpack the archive in Hiemdall and apply all the files separately as there was no apparent way to use the pit + whole tar file
Whiles this worked its a bit risky if you do it at 2am and the boxes in Heimdall could be more clearly separated.
Is there any way not shown to use the whole tar file in Hiemdall?
I say this because although i am now the proud owner of an Insanity 009 galaxy I will have to use Hiemdall to flash back to "stock" 2.3.3 rooted before i can try a different rom because of the way CM7 changed the filesystem.
Click to expand...
Click to collapse
No it's not possible to flash a tar archive with Heimdall. See here for reasoning.
Benjamin Dobell said:
No it's not possible to flash a tar archive with Heimdall. See here for reasoning.
Click to expand...
Click to collapse
A very succinct and accurate reply which I had not spotted. Yes I used Hiemdall because Odin had soft bricked one phone and refused to work on mine (it used to - dont get that). Heimdall was perfectly reliable.
It would be nice to know before pressing GO that Heimdall is actually able to connect to the phone.
Otherwise excellent work. Thank you.
Hey guys... ok i have been looking and cant seem to find how to rectify this issue... i am really stuck and would appreciate any help possible..
Ok so i had stock 2.2 on my captivate, n tried to install a gingerbread rom using mobiletechvideos easy step guide using this link
http://www.youtube.com/watch?v=UOyx5JQ_8_I
... in doing that the first step of installing the bootloaders through odin, i inserted the pda files but it freezes at setup connection... now i think its soft bricked as i can still put it in download mode.. the thing is i have tried one click odin to revert back to 2.1 or 2.2 but it stops at set pit file... and then do not turn off target... its been here for over 25 mins n nothing... i have kept trying a couple of times and sometimes it wud just say fail.. Guys again i am sorry if this in the wrong place or has been brought up before.. i tried looking and was not able to find anything..
Thanks
Well your first issue there he says flash to stock 2.1 jf6 you where on 2.2 Unless your phone is a newer build 2.1 is always better to flash then 2.2. What build is your phone?
Reboot your computer, swap usb ports to one that is in the back attached to the motherboard (if already back there swap to a different one in the back) or port #1 on a laptop. Right click odin and run as administrator.
Thanks for the responses..
Yeah i know it said do it on 2.1, i figured it cud have worked on 2.2 i guess i was wrong... n in terms of switching port, odin still recognizes the port as i get the yellow screen but it doesn't move from there...???
It doesn't matter what's on the phone 2.1, or 2.2. **** you can be in a custom rom (I made the jump from firefly). If you are using odin its the same, if it will write 2.1 over anything why wouldn't do it for 2.3.3? No Difference.. The only way 2.2 would matter is if you weren't using odin then you would have to get around 3e recovery. But download mode is underneath the firmware does not matter what is on it odin will overwrite it.
And odin can be super touchy with the usb ports. And although it sees it the flash fails if odin is on the rag and didn't take any midol.
studacris said:
It doesn't matter what's on the phone 2.1, or 2.2. **** you can be in a custom rom (I made the jump from firefly). If you are using odin its the same, if it will write 2.1 over anything why wouldn't do it for 2.3.3? No Difference.. The only way 2.2 would matter is if you weren't using odin then you would have to get around 3e recovery. But download mode is underneath the firmware does not matter what is on it odin will overwrite it.
And odin can be super touchy with the usb ports. And although it sees it the flash fails if odin is on the rag and didn't take any midol.
Click to expand...
Click to collapse
again thanks for your help studacris... so basically if odin can read it but nothing happens i am screwed... i really need to know if there is absolutely anything else i can do to fix this as this is my only means of communication.. i am lost without my cappy...
Are you sure you are using a Motherboard usb port and that you are running on Admin? If odin is being stupid you can look in to Heimdall
prbassplayer said:
Are you sure you are using a Motherboard usb port and that you are running on Admin? If odin is being stupid you can look in to Heimdall
Click to expand...
Click to collapse
yeah i am sure i am using it on the motherboard port and running it on admin.. It basically freezes on differnt areas and doesnt completely reflash to stock on odin3 one-click downloader...
So there is nothing else i cud do with odin rite??
rheanjd said:
yeah i am sure i am using it on the motherboard port and running it on admin.. It basically freezes on differnt areas and doesnt completely reflash to stock on odin3 one-click downloader...
So there is nothing else i cud do with odin rite??
Click to expand...
Click to collapse
Try a different version of odin. If that dont work then use Heimdall
You can go to samfirmware.com-US SGS download wich ever version u want (id use JF6) download and decompress. Each .md5 file you need to decompress as well and get out the individual file in them. Here is a good how too with heimdall from mobiltechvideos. Hope this helps
prbassplayer said:
You can go to samfirmware.com-US SGS download wich ever version u want (id use JF6) download and decompress. Each .md5 file you need to decompress as well and get out the individual file in them. Here is a good how too with heimdall from mobiltechvideos. Hope this helps
Click to expand...
Click to collapse
Thanks.. i was hoping odin wud have come through but i guess i will have to try heimdall...
Ok guys i have downloaded heimdall and right now trying to install the jf6 2.1 rom... the thing is i am on load package and tyring to put the firmware package... this might be a stupid question but i am inserting the zipped file but it keeps saying - Tar header contained an invalid file size... Do i need to extract the files and then do this..???
rheanjd said:
Ok guys i have downloaded heimdall and right now trying to install the jf6 2.1 rom... the thing is i am on load package and tyring to put the firmware package... this might be a stupid question but i am inserting the zipped file but it keeps saying - Tar header contained an invalid file size... Do i need to extract the files and then do this..???
Click to expand...
Click to collapse
Wich Heimdall you using? I suggest 1.1.1 in wich you choose each file u want to flash individually.
i had downlaoded 1.3.0 will try this thanks..
ok so i have inserted factory fs, kernel,param,cache,database data,modem and clicked start, it took two seconds and then stated failed to retrieve config descriptor...??
also i haven't added anything in the pit or primary and secondary and recovery files
rheanjd said:
ok so i have inserted factory fs, kernel,param,cache,database data,modem and clicked start, it took two seconds and then stated failed to retrieve config descriptor...??
also i haven't added anything in the pit or primary and secondary and recovery files
Click to expand...
Click to collapse
Im not sure about your error but the Jf6 from samfirmware has FactoryFS, Param.lfs, Cache, Database Data, Modem and Recovery(Zimage). Maybe you put a file in the wrong place?
Thanks but istn't the zimage supposed to be for the kernel... i haven't inserted anything into the recovery field...
i am rite now left clueless
No your right. Its the kernel I had a brain fart. Well I honestly Do not know whats wrong, Im assuming you ran Heimdall as Admin... Well **** man any way you have access to another machine? Im out of ideas maybe someone else can help. =/
Hey thanks i really appreciate the help ...
guys if anyone else can help me out it would be really appreciated... the phone is all i got and i really need it to work today... i am just restarting my computer and will try again hopefully it will work otherwise i am out of options...
Ok restarted and giving the same issue...
"Failed to retrieve config descriptor"
what the hell is that???
So I've downloaded the following kernels from a link here on XDA that should be swapping kernels to allow me root on my recently upgraded, stock ROGERS 2.3.3 Captivate. Odin is telling me to "Check image files !!" when I load the .tar files into the Select Intergrated Package (and yes, the one package switch is on). I opened the tar to double check it wasn't double-compressed.
What else would be giving me this problem? I'm using Odin 4.28. Curiously, it is showing my phone as detected, my phone IS in downloading mode, but Odin just says (Android) in the Title, no specific model. But it says it's found it on COM 6. <1> Added!! and Detected!!
It's when I load up the kernel tar's and try to start that it yells at me. Is this triggering anything in anyone's mind that I'm doing wrong? Or do I need to provide more info?
I am using Vista 32-bit (legit) on a Dell studioXPS. And I ran it as administrator.
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Pirateghost said:
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Click to expand...
Click to collapse
Yeah. That is def the wrong version of Odin. Download the i9000 bootloaders in my sig. Unzip it. Delete the pda.tar.md5 file. Use the included version of Odin (1.82 I think) to flash your kernel.
Alright, quick question - I accidentally flashed the phone, not the pda. I tried to flash the KH2 modem back via phone but ODIN failed. Kies is currently not detecting the phone, and so I decided to try flashing the PDA while I had it open and I would figure the modem out after. ODIN hung, so I closed it and rebooted out of downloading mode and got the Phone ! Computer error. So I figure now I have to flash back to the stock rom and start over again, but this time I would like some advice as to which step to take next. I downloaded I896UXKH2-HOMEBINARY.tar.md5 from another thread here. Can I flash this with Odin - and if so, which is the place to load it? Bootloader? PDA? Phone? CSC? I have no PIT files.
Think it goes into the pda slot. Go back to the thread t you got it from and read the first post of the thread. Also restart your computer before trying to flash again.
can someone upload the modem.zip, please thank you
Hi.
I got my beautiful Note yesterday and started tinkering right away, got really careless while following this guide:
someadress/root-and-install-clockworkmod-recovery-on-samsung-galaxy-note/
used the .pit called "u1_02_20110310_emmc_EXT4.pit" linked in the package and didn't uncheck the re-partition box. After reboot i got the yellow trianglethingy. Download mode and clockwork recovery still work but thats about it.
I dont really know what to do, downloaded N7000XXKKA_N7000OXXKK5_AUT.zip but Heimdall doesnt seem to like it. Good news is that Heimdall and Odin 1.85 both recognize the phone in download mode. Perhaps a .pit will solve my conundrum?
Have searched the forums, sorry if I'm posting in the wrong section.
comae said:
Hi.
I got my beautiful Note yesterday and started tinkering right away, got really careless while following this guide:
someadress/root-and-install-clockworkmod-recovery-on-samsung-galaxy-note/
used the .pit called "u1_02_20110310_emmc_EXT4.pit" linked in the package and didn't uncheck the re-partition box. After reboot i got the yellow trianglethingy. Download mode and clockwork recovery still work but thats about it.
I dont really know what to do, downloaded N7000XXKKA_N7000OXXKK5_AUT.zip but Heimdall doesnt seem to like it. Good news is that Heimdall and Odin 1.85 both recognize the phone in download mode. Perhaps a .pit will solve my conundrum?
Have searched the forums, sorry if I'm posting in the wrong section.
Click to expand...
Click to collapse
Get Heimdall, put your note in download mode. Go to the utility page, under "download as a file" click "save as", in the dialog put "galaxynote.pit". This will download the pit from the phone. Now you can untar the odin package (which might contain a pit too, in this case, you'd want to use that one), go to the flash tab of heimdall and select the pit you made (or got from the odin package, if it came with one), and add partitions and add the files from the odin tarball you extracted.
EDIT: This thread should be move to general. Moderator has been notified.
where does zImage go?
Thanx alot for the help so far, I've extracted the pit and loaded it in Heimdall. Ive assigned all parts of the tarball with the stock firmware (N7000XXKKA_N7000OXXKK5_AUT) I downloaded from here. It didn't come with a .pit-file. In which partition do I put zImage, its the only file left from the package?
These partitions are unassigned so far:
GANG
SBL2
KERNEL
RECOVERY
DATAFS
UMS
EFS
also, do i tick the repartition and reboot boxes? Is it possible that the .pit-file on my phone is somehow broken? Wouldn't it be safer if I could have yours?
Thank you so much for helping me, It sucks being alone and clueless after making a terrible misstake.. feels like this can be fixed after all
Got it working!
Thank you <3
hi
i have this problem too.. but when i click on download button this error appear
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
I rooted my phone and wanted to flash back to stock so I can update with the OTA and re-root, but I downloaded the zip for the AT&T tar files and everything seemed to pass MD5 checks and went okay, but as soon as I hit Start, the program just continues to say NAND Write Start for over 20 minutes, and won't flash, how do I go about re-trying this without bricking my device? It's still plugged in atm in download mode.
What version of Odin are you using? I had this problem because I had v3.10 and the s6 is not compatible with that version, you have to have v3.10.6.
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
If Odin is having trouble flashing to your phone. Here is some simply tips and tricks to try.
1. Try flashing everything except for the bootloader .
2. Try running Odin as admin.
3. Try upgrading to the newest Odin available.
4. If all else fails, open Samsung Kies, and go to emergency recovery, put your model # and serial # in, and it will flash your phone to stock for you, then you can try again.
5. Also make sure all of the correct drivers are installed for your phone, sometimes Windows can be bad about that. Try getting drivers from samsung directly.
6. Try a new USB Cable, as crazy as that is, I have had some not work, and others work fine.
7. Try a different USB Port on the PC, or restart the PC.
I hope this helps.
I tried just flashing the ROM and CSC and it flashed just fine, I left out the CP file, what is that? Everything seems fine just flashing the ROM and CSC, but do I need to flash the CP file too, for anything?
CSC is the consumer software customization and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
I hope this helps
I didnt get it. Do you mean to put each .md5 file in all sections? ? Please help me
_Dennis_ said:
Mine did that, I closed odin, reopened, put each .md5 file in right section (AP in AP, BL in BL, CSC in CSC, ect) and it worked
Click to expand...
Click to collapse
Please help me out. I am having same problem NAND WRITE stuck.
Solved
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Nand write start fail solved
I have solved using Odin3 v3.10.7 with firmware VZW-G920VVRU4BOK7-20151211140939 and Windows 7 for Galaxy S6 SM-G920V
NAND stucked
kishor1995 said:
Thanks everyone for your post. But what I did is, just downloaded the Odin v3.10.6......that worked with S6. And I guess S6 is not compatible to other earlier versions of odin. So better try with Odin v3.10.6.
Click to expand...
Click to collapse
can u tell the steps u did? to do it
Help
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
bonniegertz said:
I am having the same issue and I have done everything suggested here but still is NAND fail. Any ideas
Click to expand...
Click to collapse
Were you finally able to get it to work?
Its working!
Zoide_ said:
Were you finally able to get it to work?
Click to expand...
Click to collapse
Yes, I gave up but a friend of mine found a thread that talks about using Kies to bring it back to factory default. You need to know the serial # and IMEI # If you can find this information, you can reset it using Kies.
Had the same problem. Used Odin 3.10.6
But before all this, I connected phone with debugging enabled in windows and authorized it, the problem never resurfaced