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]

[Q] Galaxy Note bricked when used "u1_02_20110310_emmc_EXT4.pit" in Odin

Okay. Some history to start with...
I got Chinese version of Galaxy Note which runs i9220 ROM and been trying to flash with HK/EU ROM last several days but out of luck so far. (And whenever failed, I re-loaded stock ROM found from Samsung-updates.com site for i9220. It then worked fine but still with original problem unsolved.
I then tried one last method that I saw someone succeed flashing Chinese ROM via use of PIT file came from one of the other downloads.. yeah, I didn't check the source PIT came from before try... which is my bad.
Without confirming it, I instantly located "u1_02_20110310_emmc_EXT4.pit" that's packaged with odin 1.85 and carelessly gave a try.
And now... my precious GalaxyNote became the most expense brick in my house and am looking for professional help from you guys.
Steps I did before bricking and tried:
1. Load GalaxyNote in Download mode (volume down + home + power)
2. Launch Odin 1.85 and no change to default setting. (Check mark on #Auto Reboot & #F.Reset Time, uncheck on #Re-Partition & #Flash Lock)
3. Set PIT to "u1_02_20110310_emmc_EXT4.pit"
4. Set PDA to "N7000XXKL7_N7000OXAKL7_N7000XXKL7_HOME"
5. Click #Start
Soon after around 5%, it failed.
I then attempted to restore factory ROM via usual way - doing same as above except no PIT this time and choosing original stock ROM for i9220.
It failed! OMG...
I then tried again (#1 ~ 5 above) but this time, check on #Re-partition for luck. Still no luck!
I then downloaded Heimdall1.3.1 and tried to extract PIT file but the tool fails as well and gives "ERROR: Failed to access device. libusb error: -12".
At all times, GalaxyNote screen shows android icon with 'Downloading... Do not turn off target!!'. And the device can also be seen from odin.
Soon as turn off galaxynote and disconnect from computer, it shows 'Software Update Fail' message.
How I can restore to original factory setting? And if possible, how I can restore to EU or Hong Kong ROM?
My Chinese friend has the same device as mine. In this case, will Heimdall tool help extracting PLT from it and help restoring my device via odin?
Your professional help is sincerely appreciated!!!!

Resolved
Using "Q1_20110914_16GB.pit" and re-partition check from odin while flashing to original stock rom has resolved an issue.
Referred from following thread.
http://forum.xda-developers.com/showthread.php?t=1533214

Never use pit and do not tick repartion when flashing.

bootloader?
U are fine. It is a recovery issue and not a bootloader. Install custom recovery and flash stock firmware w odin. Oh yea, and profit.

Toolmighty said:
U are fine. It is a recovery issue and not a bootloader. Install custom recovery and flash stock firmware w odin. Oh yea, and profit.
Click to expand...
Click to collapse
Why do you revive an old thread? The user has resolved it the day after his problem.

[Q] newbie - HELP PLS - bricked?

Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty

strangermyself said:
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
First you should t have flash abyss through odin since now you are not rooted and do t have the warranty too, the counter of flashes increased to 1 (look at the download mode small text), for rooting you can use chainfire's tool (in the cf-root kernel thread look for it in devolepment section) next get a stock rooted kernel and flash using the tool (read instructions).
For now use pc odin 1.87 and get a firmware 2.3.6 use the pc odin select the file on PDA and flash it, make sure phone is charged 100% and press start, if it doesn't work then uninstall drivers, reboot machine, reinstall them and kill kies process if present in task manager and then goto download mode connect USB and open pc odin wait for the port to be ready aka green and select file then start.... you should be fine its a soft brick afterall.
Sent from my GT-N7000 using Tapatalk 2

Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.

strangermyself said:
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
Click to expand...
Click to collapse
When connected to charger make sure phone is off the battery meter will show as soon as you connect, case it doesnt leave it for like 3 hours is fine... next about that ROM redownload. The package cleanup you temp directories in PC and try again if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2

REVERSiN said:
... if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?

strangermyself said:
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444

Whiskeyjack4855 said:
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Click to expand...
Click to collapse
Dude its a GB rom not superbrick bug in it and he didn't mention LPY yet.
Sent from my GT-N7000 using Tapatalk 2

strangermyself said:
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
Click to expand...
Click to collapse
Sorry for tea doubled post its a dumb app X's
You wipe using the CWM file in the Iss root section, and a normal recovery wipe would do too (aka restore defaults)
Sent from my GT-N7000 using Tapatalk 2

Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help

strangermyself said:
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
Click to expand...
Click to collapse
If you have the stock recovery, restore default wipes everything.
If you have stock re every and want CWM temporary just to wipe goto n7000 devolepment and check how to root by dr.ketan and get files there
If you have CWM then wipe data, wipe cache, wipe dalvik.... and try. Old download another firmware like kk5.... something else not the new LC1 LX1 releases.... (Latest GB) get an old one to get root easly
Sent from my GT-N7000 using Tapatalk 2

[Q] [Please Help] can noch access the recovery mode

Hi Guys,
i have the problem that i can not access the recovery mode.
i have try so many thinks, but every PDA i flash via ODIN failed, also the 3 parts GB
i can only enter the Download Mode for Odin.
i have also try to flash the CM10.1, but its still the same, the factory.fs fails, and if if enter the recovery mode i see the droid picture, and a process bar from 0-50% and than it makes a reboot.
thats all.
i have also a 8GB eMMC brick, but i have this a long time ago, and i have also the correkt PIT file (i use it 6 month ago)
have anyone a idea how i can enter CWM from this situation ?

How did you try to flash a cm 10.1?

Try to flash philz kernel.tar using pc Odin
Sent from my GT-N7000 using Tapatalk 2

So, you bricked your device already and fixed it with the repartition workaround one time?
And now you do have the error at factoryfs.img in PC Odin again?
Maybe you bricked your device a second time?!?
Please check with hg42 method for errors again (because you did the repair before you should know how to do this).
And if the errors are in different sectors than before you might loose more GB (resulting in 5 GB or so).
But maybe you only have to use the check and a fitting pit again.

nokiamodeln91 said:
How did you try to flash a cm 10.1?
Click to expand...
Click to collapse
On the computer (Heimdall ) , open a terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage --no-reboot
Try to flash philz kernel.tar using pc Odin
Click to expand...
Click to collapse
i will try it again
So, you bricked your device already and fixed it with the repartition workaround one time?
And now you do have the error at factoryfs.img in PC Odin again?
Maybe you bricked your device a second time?!?
Please check with hg42 method for errors again (because you did the repair before you should know how to do this).
And if the errors are in different sectors than before you might loose more GB (resulting in 5 GB or so).
But maybe you only have to use the check and a fitting pit again.
Click to expand...
Click to collapse
Fu** is this possible ?
it the first time i heard that the device can brick a second time
i will search for the hg42 method.

Slider-Override said:
Fu** is this possible ?
it the first time i heard that the device can brick a second time
i will search for the hg42 method.
Click to expand...
Click to collapse
It's possible if the member makes the same mistake a second time.
But as I said try to apply the repartition workaround again. Maybe it's not the second time but only the first one with "removed" repartition by using a normal pit file.