Related
This is the situation:
Windows XP 32bit
Galaxy Note with LA4
Odin V1.85
KIES latest version
Latest Android SDK
I tried today to downgrade to a directly rootable stock ROM. It failed?
My Note stucks on the bootscreen.
I can put the Note in the downloadmode. When I start Odin, I see a yellow box under ID:COM with 0:[COM7], so my computer sees the Note. I want to flash the rootable stock ROM as described in many threads, especially following Dr. Ketans Guide
But it fails, it stucks at Initialzation..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
I tried the LA4 stock ROM, same problem.
After this I have putted the Note in recovery mode and this is what I see:
"E:failed to mount /sdcard (Unknown error: 0)"
"E:install_application_for_customer:Can't mount /sdcard"
" your storage not prepared yet. please use UI menu for format and reboot actions."
"copy application failed"
In the recovery mode I tried Factory reset and Wipe cache...no effect.
Since 4pm I have tried many things, read threads and posts, but nothing has solved my problem. By the way I have not seen a problem as described above no where. Is there a genius who can solve this/my problem?
Or is my Note bricked?
The only thing i can see is that it can't mount the SD. Other than that, i don't know. And you know i had my own problems yesterday, so i'm not in the position to know what might be wrong. But one thing is sure, it's not bricked since you can enter download mode.
I know it's frustrating, but you'll have to wait for somebody that knows some things about Odin. I used it myself for the first time yesterday since the Note is my first Samsung device.
Sent from my iPad GT-N7000 using xda premium
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps
I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
As you can read I did trie data factory reset, after flash with Odin it didn't work. Thanks for your help.
gee2012 said:
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps
Click to expand...
Click to collapse
As you can read I can't ENABLE USB DEBUGGING, because I can't start my Note up normally. Thanks for your help.
Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Thanks, but no effect.
dr.ketan said:
I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)
Click to expand...
Click to collapse
With the pit-file it showed PASS!:
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/006> Added!!
At my screen the following:
Firmware upgrade encountered an isseu.
Please select recovery mode in Kies & try again
If I open Kies to select recevory mode it asks for a recovery code. I tried some codes like 0000,1234 and others, but no good...
Then, I entered the download mode of the Note and tried a flash with KK9 (one file) it shows PASS:
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan
Note not bricked.
Problem solved.
And the problem was?
Sent from my GT-N7000 using xda premium
Read my first post...
got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks
Caesarea038 said:
With the pit-file it showed PASS!:
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan
Click to expand...
Click to collapse
Really glad to hear.
It is really painful when some one say bricked lovely device.
its ok now, congratulation.
it is advisable once you format internal SD card. Not in hurry, but at least before next update.
Sent from my GT-N7000 using xda premium
shaharda said:
got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
...........................
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks
Click to expand...
Click to collapse
Can you tell me exactly the problem and what you did step by step?
Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Today I figured something out:
If you encounter problems with rooting/flashing try another or original USB cable, maybe a different USB port....
My problem as described in my first post was a combination of a fail USB cable and a software problem.
thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).
now the battary won't charge. need to send it to the Lab.
thanks anyway. (i'll as them what they did)
shaharda said:
thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).
Click to expand...
Click to collapse
Can you enter DOWNLOAD MODE?
I was trying to root my galaxy note, I download the rooted stock rom (N7000DXLC2) from here http://forum.xda-developers.com/showthread.php?t=1535025
but the odin failed and showing this
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000DXLC2.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000OLBLC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then my phone can't boot anymore, it jus stuck at the samsung n7000 screen,
i tried to download stock rom and flash again, but it failed like above,
and when i go try to flash the kernel, it success to go to the recovery mode,
but it showing error like
E:Error in /cache/recovery/sec_csc.zip (status 7)
And i maybe forgot to enable usb debugging before i root, is this the cause? how i enable it now?
what can i do now? I tried to change port, change pc, uninstall kies, reinstall driver, close antivirus, and all doesn't work, please help...
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and setting it in the options anyway.
bioweb said:
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and set it in the options anyway.
Click to expand...
Click to collapse
I tried that, and I uninstalled the kies,
but the odin still showing the same error.
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
17n337 said:
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
Click to expand...
Click to collapse
CAUTION : Just dont go on blindly flashing the PIT file. Its a repartitioning file. To be used only when your partition is corrupted.
Galaxy Note stuck
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
vinay28761 said:
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
...
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but
...
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
...
Can anyone explain my current situation...???
Click to expand...
Click to collapse
First: this thread is marked as solved since april. Chances are very low for a reaction (but at least I did)
Second: Make a new one in Q&A
Third: What do you mean with "Took the TB"? Especially when you flash a new Stock Rom after
Fourth: Did you put the tar-file under "Phone"? Should be "PDA".
Fifth: Read a lot in the stickies here - good start for handling Odin is Dr. Ketan's thread
Sixth: your current situation might result from not reading enough. I hope you didn't brick your device and can restore a running Rom with the instructions from the stickies. Good Luck
how exactly did you reach this situation?
Did you resolve this ?
vinay28761 said:
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
Click to expand...
Click to collapse
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
dannyogolo said:
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
Click to expand...
Click to collapse
Yes, i resolved it. I just followed dr. ketan's guide to flash through ODIN properly and exactly as described. I would request you to do the same.
Hope it solves your error too. If not, please post your screenshots.
could you jst give me details about dis nand write fail problem?i m having same problem in my gt n7000
Does anyone know where i can download PIT file for samsung gts6802 and a bootloader?
It woulb be very helpful. Thank You
Hmm this is odd..
Flashed this GB Stock via PC Odin many times and competes without issue, Tried it today and I am currently stuck at Get PIT for Mapping... It;s a single file ROM I am trying and no I have not selected to use a PIT file or repartition or anything...
Everything is the same as normal,
Phone just shows in Download mode but with no activity...
Any ideas? Am I safe to do a battery pull / disconnect it at this point? Do I wait? Its been like this for half hour or soo..
Very strange..
This is where I'm stuck -
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
From the above - it has not started any "Push" activity yet and there's nothing showing (Progress bar or anything) on the phone so I assume it's cool to pull the cable.. Just wondering if anyone else had this issue...
Fix Info
If you're like me and a little worried about things like this then it's best to ask - As i stated, from my understanding here, ODIN had NOT started any NAND write.
This was resolved by unplugging the USB > ODIN immediately turned to "Failed" > Rebooted phone > Rebooted PC > Success..
I DO NOT recommend unplugging USB from ODIN without either A} Knowledge or B) Advice
If it HAS started to write and you're stuck somewhere other than this (Factory_FS / Data IMG etc), seek advice.. and most of all 'Search before asking....'
Thanks all
replied to PM
Here a SS
Cheers Dr. K
Was looking for just that kind of assurance
I pulled the cable and all is well, Probably something rogue running on my PC as I've used the image to flash before loads of times..
Oh well, I'll wait until I finish work and try again
Yeah this is common, nothing serious.
pit mapping starts everytime, even you dont select pit.
cheers !
dr.ketan said:
Yeah this is common, nothing serious.
pit mapping starts everytime, even you dont select pit.
cheers !
Click to expand...
Click to collapse
Well I spoke too soon!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.bin
<ID:0/005> modem.bin
<ID:0/005> Sbl.bin
<ID:0/005> cache.img
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
Stuck here for an age now...FFS
So......
I've not got an expensive paperweight it would seem?
Any ideas guys, I've offered alot in the past and this is purely trying to flash a GB Stock ROM i've used a thousand times in PC Odin....
Could it be a comms error? My laptop is ****e...
Flash Pre rooted ROM from my signature.
Phew All sorted...
My advice is don't do **** on a HP laptop hahaha
Nah - i think I lost connection once or twice - AzzleDazzle on his IIRC was a saviour - cheers for the replies - I'm back - I'm Stock - and I am updating...
So in effect - this was a massive PC issue....
As I said - Dr. You're always as asset to have on hand and sorry if I spammed ya PM's - was just having a heart attack there for a few..
Without succes
Do have the same problem on my Note 2 and tried to fix it as shown, but withoiut succes. Hope Dr. Ketan, you or another Android cardiologist may help me, Please.
CJSlim79 said:
Hmm this is odd..
Flashed this GB Stock via PC Odin many times and competes without issue, Tried it today and I am currently stuck at Get PIT for Mapping... It;s a single file ROM I am trying and no I have not selected to use a PIT file or repartition or anything...
Everything is the same as normal,
Phone just shows in Download mode but with no activity...
Any ideas? Am I safe to do a battery pull / disconnect it at this point? Do I wait? Its been like this for half hour or soo..
Very strange..
This is where I'm stuck -
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
From the above - it has not started any "Push" activity yet and there's nothing showing (Progress bar or anything) on the phone so I assume it's cool to pull the cable.. Just wondering if anyone else had this issue...
Fix Info
If you're like me and a little worried about things like this then it's best to ask - As i stated, from my understanding here, ODIN had NOT started any NAND write.
This was resolved by unplugging the USB > ODIN immediately turned to "Failed" > Rebooted phone > Rebooted PC > Success..
I DO NOT recommend unplugging USB from ODIN without either A} Knowledge or B) Advice
If it HAS started to write and you're stuck somewhere other than this (Factory_FS / Data IMG etc), seek advice.. and most of all 'Search before asking....'
Thanks all
Click to expand...
Click to collapse
i am stuck there too.
i just wanted to ask....
WHEN IM STUCK THERE...I NEED TO UNPLUG REBOOT THE TAB AND GET BACK TO DOWNLOAD MODE AND RECONNECT WHILE ODIN IS STILL RUNNING ON PC....right?
but odin doesnt recognize the device again...
please help.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
CJSlim79 said:
Hmm this is odd..
Flashed this GB Stock via PC Odin many times and competes without issue, Tried it today and I am currently stuck at Get PIT for Mapping... It;s a single file ROM I am trying and no I have not selected to use a PIT file or repartition or anything...
Everything is the same as normal,
Phone just shows in Download mode but with no activity...
Any ideas? Am I safe to do a battery pull / disconnect it at this point? Do I wait? Its been like this for half hour or soo..
Very strange..
This is where I'm stuck -
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
From the above - it has not started any "Push" activity yet and there's nothing showing (Progress bar or anything) on the phone so I assume it's cool to pull the cable.. Just wondering if anyone else had this issue...
Fix Info
If you're like me and a little worried about things like this then it's best to ask - As i stated, from my understanding here, ODIN had NOT started any NAND write.
This was resolved by unplugging the USB > ODIN immediately turned to "Failed" > Rebooted phone > Rebooted PC > Success..
I DO NOT recommend unplugging USB from ODIN without either A} Knowledge or B) Advice
If it HAS started to write and you're stuck somewhere other than this (Factory_FS / Data IMG etc), seek advice.. and most of all 'Search before asking....'
Thanks all
Click to expand...
Click to collapse
i am stuck there too.
i just wanted to ask....
WHEN IM STUCK THERE...I NEED TO UNPLUG REBOOT THE TAB AND GET BACK TO DOWNLOAD MODE AND RECONNECT WHILE ODIN IS STILL RUNNING ON PC....right?
but odin doesnt recognize the device again...
please help.
You need to restart both the phone in download mode and close odin and then restart odin
Sent from my GT-N7000 using xda app-developers app
Get PIT for mapping..
(Get PIT for mapping..)
You need to check cable or to replace cable some samsung needs original cable.. thats it
CJSlim79 said:
Phew All sorted...
My advice is don't do **** on a HP laptop hahaha
Nah - i think I lost connection once or twice - AzzleDazzle on his IIRC was a saviour - cheers for the replies - I'm back - I'm Stock - and I am updating...
So in effect - this was a massive PC issue....
Click to expand...
Click to collapse
:good: Thanks a lot! Stuck for days on end trying to root my Galaxy S3 t999 when I ran across this. I switched from my HP laptop over to my Dell desktop setup and everything ran perfectly on the first try! I was pulling my hair out trying to figure out why Odin kept failing and I couldn't root. Don't know what's up with those HPs.
Solution
You need change other cable. This will change problem
i tried and OK !
delete
Error odin invalid ext4 image firmware italy to germany(BTU)
Hello i have the simil problem with my galaxy note 4 (SM-N910F) (I'm italian), i try to flash firmware italy in my phone because i have the germany firmware (BTU) but odin screen error invalid ext4 image, i have read tha t the problem is the pit or the partition in my phone. what should i do for flash my firmware in my phone thanks a lot.
Post odin log
Sent from my SM-N910G using xda premium
Odin: invalid ext4 image and the odin in desktop on my computer write fail and the smartphone don't reboot
Sent from my SM-N910F using XDA Free mobile app
Copy paste full error log from odin
Sent from my SM-N910G using xda premium
Hi there, I'm trying to flash my Galaxy S3 mini GT-I18190 with an official ROM which was downloaded from SAMMOBILE. My phone isn't carrier locked or anything like that. I have installed the drivers necessary and I'm using the original USB Cable. The Error I'm getting is as follows:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMC1_I8190OJVAMC3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.img
<ID:0/015> NAND Write Start!!
<ID:0/015> recovery.img
<ID:0/015> STE_boot1.img
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
On my device screen it says: "CUSTOM STEboot1 BINARY !!
What can I do to solve my issue?
ROM: I8190XXAMC1_I8190OJVAMC3_HOME.tar.md5
ODIN: I tried Odin3_v3.04, Odin_v3.09, Odin3_v3.11.1
Thanks in advanced.
bump
Hello,
I faced this problem last night when trying to flash an official S3 rom via Odin, I used Samsmobile to download the firmware. I kept getting the same error as you with the dreadful red 'FAIL' notification. However, I managed to overcome this issue by using Odin v 3.10 with the right firmware (stupidly, I had downloaded the firmware for the wrong variant, the i8190 as opposed to the i8190n). Furthermore, I also flashed the appropriate PIT file to my device along with the firmware (the only reason I did this was because it was mentioned as a possible solution in many threads). Also, I made sure there was no trace of Kies on my computer before connecting my device and flashing.
Pinda007 said:
Hello,
I faced this problem last night when trying to flash an official S3 rom via Odin, I used Samsmobile to download the firmware. I kept getting the same error as you with the dreadful red 'FAIL' notification. However, I managed to overcome this issue by using Odin v 3.10 with the right firmware (stupidly, I had downloaded the firmware for the wrong variant, the i8190 as opposed to the i8190n). Furthermore, I also flashed the appropriate PIT file to my device along with the firmware (the only reason I did this was because it was mentioned as a possible solution in many threads). Also, I made sure there was no trace of Kies on my computer before connecting my device and flashing.
Click to expand...
Click to collapse
Hi there, If you don't mind can you please send me links to the files you used (the firmware and the PIT file)?
1337x said:
Hi there, If you don't mind can you please send me links to the files you used (the firmware and the PIT file)?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/database/GT-I8190N/EVR/
That's where I downloaded the firmware, the first one (I8190NXXAMB1). Note that it's for the N variant in my country (UK) and my network provider (EE), I downloaded the PIT file off XDA on a thread I found, I cannot for the life of me remember where it is now. However, it's on my computer at home, so if possible, I'll upload it to this thread when I get back. Keep me updated on how you get on pal.
note 5 N920T
Successfully flashed Sick/Flu ROM about 2-weeks ago and it was (is) excellent. It was like getting an entirely new phone in battery life and speed. Long story short, tried to add fingerprint scans and bricked it--only to find out this was the one caveat to the ROM. So proceeded to reflash ROM while talking with family during Thanksgiving--I had really prepared the first time and felt pretty comfortable doing it again--but not being focused I ended up deleting the wrong information and soft bricking it.
At this juncture the only item still visible on the internal drive is TWRP. I AM able to boot into ODIN mode and the software does recognize my phone and I am also able to boot into TWRP. Other than that I do not have any OS on the phone at this time. I've downloaded the original firmware, but multiple attempts at flashing it have failed. Hours and hours of reading it seems that I may be missing a PIT file (?), but I haven't been able to confirm that is the actual problem or locate the specific N920T PIT file anyways. Seems like many of the discussion strings died in 2015
I can provide more details about the failure messages I read on ODIN and my phone during reflash attempts if anyone has the patience and time to help me. I spent essentially 13 hours straight all over the internet with no success and am reaching the point of throwing it into a fire
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success
Wyattthomas said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success
Click to expand...
Click to collapse
If you need the PIT file you can get it here but you'll have to create an account in order to see the download links.
http://www.sammobile.com/forum/showthread.php?t=30106
By the way don't use an old firmware, you have to use the very last firmware you were using before ever doing anything to it.
I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.
Wyattthomas said:
I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.
Click to expand...
Click to collapse
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.
MrMike2182 said:
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.
Click to expand...
Click to collapse
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.
Wyattthomas said:
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.
Click to expand...
Click to collapse
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.
MrMike2182 said:
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.
Click to expand...
Click to collapse
First thing I did. I've since backed it up about 3 more times...never again will I make that fatal error.