Database Develop

[Q] ODIN - Check image files !! Works for others though...

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

Soft bricked N7000. How to?

Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.

Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)

I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?

btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.

True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.

Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.

btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?

N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han

choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you

mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium

I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]

Need help flashing Dok2

Can someone help me out here? I am suffering from the major lagging and freezing with my Note 4 and i contacted Samsung about it. They told me to visit a local Samsung store and they can check out my phone, but i want to be back to stock before taking it in. Last night I tried to Odin back to stock Dok2 for roughly 4 hours and i couldnt get it accomplished. Am i missing something? I tried 3 different versions of Odin and downloaded 2 diffrent copies of the Dok2 firmware, but still no luck. Is there a specific processto follow? I tried factory resetting the phone before odin flashing, I even clean wiped the phone in Odin deleting internal storage as well.
Please help!

Anyone??????

Did you download Odin and DOK2 from sammobile? I was able to flash my phone with the downloads from there. I would double check and make sure you are using the stock samsung USB cable that came with your phone.
I'm having the exact same freezing and lockup issues as you are, by the way.

I dont beleive my odin and firmware came from sammobile, so i will give that a shot. I did make sure to use the samsung usb cable. I guess i need to make sure it was my usb cable and not my wife's S4 cable. Not sure if that makes a difference.

Ok. I still can't odin flash Dok2. I downloaded the new version on Odin from Sammobile and downloaded a copy od Dok2 (full) from a link to Mega. I couldn't get the sammobile link to work.
Any other suggestions?

It's possible that your DOK2 file might be corrupted or something. Try giving this one a shot, http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 to download the firmware. Input your phone model, set region to TMB, place check mark on "auto" box, and place a check mark on the "decrypt automatically" box. Click on "Check Update" and download. Don't worry about the .enc4 extension on the file name, once its done downloading and decrypting you will get a .zip file of the firmware.

I tried downloading the SamFirm program from the link you provided above, but I get an error in the program stating: "Could not load file or assembly "Microsoft.WindowsAPICodePack.Shell. Version= 1.10.0. Maybe this is because I am running Windows 10.

OK, problem solved. I downloaded Kies 3 and was able to restore to DOK2 using it.

Gjohnson7771 said:
OK, problem solved. I downloaded Kies 3 and was able to restore to DOK2 using it.
Click to expand...
Click to collapse
Can you elaborate on this Kies 3, I'm stuck I the same issue and I cant get back to Stock ROM for Note 4

Sure. Kies 3 is the Samsung software for recovery and updates. You should be able to just Google Kies 3 and download.

Gjohnson7771 said:
Sure. Kies 3 is the Samsung software for recovery and updates. You should be able to just Google Kies 3 and download.
Click to expand...
Click to collapse
So use Kies 3 as opposed to using Odin to flash the fw?

That's the only way I was able to flash Dok2 again. I tried at least 20 times in Odin and it failed everytime. I'm still having issues on Dok2, I wish I could flash back to Cod6.

Please Help

Ok so I have a note 4 that was not working properly as it would boot into Odin mode when I tried to turn it on. That being said, it sometimes would boot normally or not turn on at all. So my solution was to root it and install a custom rom (like cyanogen mod). So I got odin and the twrp file and the custom kernel and followed the steps necessary: flash twrp, flash the kernel, flash super su, etc. But the problem is that Odin says "no pit binary". So I google it and found out that I could repartition it using a stock ROM and the correct pit file. I did that and it failed as well. So I turn to keis and do the firmware and initialization thingy, that ends up failing too. So I go back to odin and try to flash stock firmware but it fails after " writing NAND " thingy or it fails saying "cannot open specified file" or "no pit file ". What can I do.[emoji27]

beelito19 said:
Ok so I have a note 4 that was not working properly as it would boot into Odin mode when I tried to turn it on. That being said, it sometimes would boot normally or not turn on at all. So my solution was to root it and install a custom rom (like cyanogen mod). So I got odin and the twrp file and the custom kernel and followed the steps necessary: flash twrp, flash the kernel, flash super su, etc. But the problem is that Odin says "no pit binary". So I google it and found out that I could repartition it using a stock ROM and the correct pit file. I did that and it failed as well. So I turn to keis and do the firmware and initialization thingy, that ends up failing too. So I go back to odin and try to flash stock firmware but it fails after " writing NAND " thingy or it fails saying "cannot open specified file" or "no pit file ". What can I do.[emoji27]
Click to expand...
Click to collapse
Hey bud. Are you trying to flash a pit file and firmware or just firmware. And is it a N910T and if so on what build of firmware..? Send a screenshot of download mode...and also try to rename the extracted firmware file from .md5 to .tar and try to flash

Its a N910T and its on 5.1.1, i read on another XDA thread that to repartition something you need stock firmware (which I have a 5.1.1 one) and the right pit file (I have the N910T one) and that in odin put the extracted firmware file and on pit put the pit file. I did that and it failed. And how would I rename the file ... Would I just rename it on the file explorer on windows?

noob4598 said:
Hey bud. Are you trying to flash a pit file and firmware or just firmware. And is it a N910T and if so on what build of firmware..? Send a screenshot of download mode...and also try to rename the extracted firmware file from .md5 to .tar and try to flash
Click to expand...
Click to collapse
First it was a pit file and firmware, but now I'm trying to unbrick it by flashing just firmware on odin since keis doesn't seem to help. And yes it is an N910T, dont know the exact build but it is 5.1.1 ( would flashing a different 5.1.1(for the n910t) build matter or not, since its still 5.1.1 ?)

Yea if your on dok2 you can't go back to anything under that. It will fail every time. What firmware build u got

noob4598 said:
Yea if your on dok2 you can't go back to anything under that. It will fail every time. What firmware build u got
Click to expand...
Click to collapse
I dont know... The latest one ( the update for stage fright was the last update I had installed on there. Since it's soft bricked ( the connect to kies message) I can't tell what the exact build was... I just know its a 5.1.1 build.)

Pretty sure i ruined my phone.

Was in the process of IMEI repair. (Just for reference.)
My phone use to be rooted and on a custom rom. It was previously reverted back to stock DOK2 5.1.1. My phone cannot be flashed anymore for some reason. I cant even flash the DOK2 file that goes in AP. I tried flashing the trlte pit file and now my phone doesn't boot past the T-Mobile logo. I think im missing some files to do a full ODIN flash.

U need to flash trltetmo pit file. Trlte is for N910F I believe and I think it's 16gb internal sd. U need to flash 100% stock dok2 with the pit file and make sure repartition is checked. If it fails....try renaming the .tar.md5 to just .tar (remove md5) for some reason I can't flash stock any other way

Karina Kapri said:
Was in the process of IMEI repair. (Just for reference.)
My phone use to be rooted and on a custom rom. It was previously reverted back to stock DOK2 5.1.1. My phone cannot be flashed anymore for some reason. I cant even flash the DOK2 file that goes in AP. I tried flashing the trlte pit file and now my phone doesn't boot past the T-Mobile logo. I think im missing some files to do a full ODIN flash.
Click to expand...
Click to collapse
I don't have a specific answer to your problem, but make sure you try and wipe the cache as well. I remember having a situation where I was trying to flash my device back to stock and it was bootlooping. The problem ended up being that I hadn't properly wiped everything from the custom ROM I had been on.