Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
Odin Mode
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWREV: A2
Click to expand...
Click to collapse
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUENE4_I9305H3GENE1_I9305NEUEML2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Centrumgsm said:
Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
Click to expand...
Click to collapse
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed
klemen241 said:
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed
Click to expand...
Click to collapse
I did. As far as I can tell, I did everything according to the guides.
[edit] I also managed to flash a different I9305 without problem, so I'm sure it's not driver or flash file related. There is something with this specific phone that prevents flashing.
I've seen a "rescue firmware" for the I9300 with separate PDA, MODEM and CSC (+.pit) files for when the regular stock firmware wouldn't flash, and I was wondering if such a thing exists for the I9305 or if there is a guide on how I could make one.
Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.
daedric said:
Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.
Click to expand...
Click to collapse
Can't brick the device much more than it already is, right? I tried it, but it just gets stuck here:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
I got bored after 15 minutes, turned off the target, turned on the target, no change, still the same error when flashing.
Thought about the Knox bootloader preventing me from updating it, but that usually gives me some kind of error message right on the flash screen. Plus I'm using the latest images, and the other I9305 also says "SWREV A2", so that shouldn't be a problem.
This looks more and more like a motherboard replacement...
All i have to say is, good luck. Things don't look good.
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9305/
daedric said:
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
Click to expand...
Click to collapse
Tried it, no go. Same error, still won't boot into recovery. On the upside, it didn't trip Knox either
Ok, just for good measure, let's get down to the basics.
Questions:
1. What type of USB cable are you using? Can you try another?
2. Is the USB cable connected directly to the computer , or via HUB / Front ports ?
3. Have you tried cleaning the usb port on the device ?
I've covered all the basics, even tried another computer. Same results.
I couldn't find a solution, ended up sending the phone for a motherboard replacement. Thanks for the suggestions, everyone!
Related
Hey all,
I've softbricked my Captivate and back to download mode using a JIG. It took me awhile to get it there as well. Anyhow, my phone is connected to the PC and is recognized by the OS and Odin3 3 Button Fix v1.81. It is not detected by Odin 1 click. When I attempt to flash back to stock, Odin REALLY enjoys to "setupconnection" with my phone. So much so it stays there for 10+ mins. I've heard people say that the PDA check box causes this issue. I've flashed to stock before and it hasn't been an issue until now. I was wondering if I can leave out the PDA.zip just to get back to stock 2.1. Would there be many ill effects? Especially if I'm just going to flash to a custom ROM?
I was on CM7 Nightly build 14. I attempted to recover back to Phoenix Ultimate using CWM. It failed when installing something that had to do with boot. Should I also add a bootloader file to the Odin install?
Thanks!
Just restart your PC and try one click odin...if Odin 1.8 is detecting then one click odin should also detect IMO...
I am not 100% sure but you do need PDA to flash to stock...try Icezar's package, its safest way to flash to stock..
Not really an answer to your question, but did you have repartition checked when you used odin? To return stock?
Sent from my GT-I9000 using XDA App
I did have re-partition clicked. I got the same results with and without it clicked. I had it showing up in Odin 1 click, but that got stuck with file analysis or the like. Now I have the Phone ! PC screen and I'm not sure how to proceed.
EDIT: Sorry for lying, back in download.
EDIT: Using Icezar's Package
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Enter CS for MD5..
<ID:0/003> Check MD5.. Do not unplug the cable..
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So, Odin was flashing and the battery fell out. /cry
JIG now opens Phone ! PC screen and the Odin won't recognize it. I've had Odin opened first and loaded all information before hand. No luck so far.
Any tips?
EDIT: New Captivate coming from ATT. Thanks for the help everyone!
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?
hi all,
i was on KL3, rooted, then KIES kept bothering me so i thought i'd upgrade to the new LA3 i think....
then the thing crashed and now all i get is the Firmware upgrade encounted an issue. PLease recovery mode in Kies and try again.
problem is, i cant get it to go into recovery mode?!??!?! (volume up, power?)
nothng works, KIes cant detect it, and cant upgrade anything, i am a total noob, and can only get into ODin mode..
HELP please?!?!?
what do i need to do, please step by step, what to download, what to press and whether i need to get a micro sd to install some firmware?
thankyou - urgent help needed!
First of all, relax
You said you can get into "Odin Mode"? I suppose that's download mode. Just go to this thread and everything is explained here. No need to worry
http://forum.xda-developers.com/showthread.php?t=1424997
Just flash another firmware (why not the latest) and everything will be just fine.
P.S. Once rooted, you should probably stay away from stock upgrades...
Press thanks if it helped
Recovery : vol up + home + power
If you get into recovery just wipe cache n wipe data
If error still there
Go to download :
vol dwn + home + power
Reflash new rom
Sent from my GT-N7000 using xda premium
this is all i get and gets stuck???
i chose this one: N7000XXLC1---------2.3.6-------2012 March----------N7000OXXLB3-----------France------------------------------------Download
went to bed for 2 hours and it didnt move...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXXLB3_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
confirm you have close antivirus if running
Dont put ROM file too deep, better keep on Root folder e.g. C:/Folder/***.tar.md5
Dont use USB extension, attach USB cable direct to slot on PC, try using different slot (preferably back side PC)
N dont forget to put device in download mode.
Thankyou Dr.Ketan and eug3n91
worked after i switched to the onboard USB.
i guess thats probably why Kies failed too....
this site is fantastic, been a lurker for a while, but never needed to post until today and its proven to be very succesful with both of you helping out so quick.
cant thankyou enough!
Dr.Ketan I am facing the same problem and did exactly the same but this is all i get
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK3_N7000ODDKK1_N7000DDKJ3_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> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.bin
<ID:0/015> cache.img
<ID:0/015> factoryfs.img
same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893
ow1166 said:
same problem here. flashed ROCKET ROM but now i can just go into download mode and CWM. ICS roms stuck on NAND WRITE START and GB roms on FACTORYFS.IMG
I tried everything ever mentioned i guess:
-Tried fix it with KIES but it doesn't even find my device
-use different USB port
-install USB drivers new
-flash Q1_20110914_16GB.pit
-flash other kernel "CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5"
-flash "N7000_XXKL8" where i have to flash three files with odin v1.85
-took the battery out for a longer time
-Flashed different Stock Roms (wipa and without wipe)
-flashed the Abyss Kernel 4.2 again
-flashed "Criskelo's Rom" with CMW
-Tried on different PC with Windows XP
Please there must be a way to help me and khok3893
Click to expand...
Click to collapse
I'm afraid this has to do with corrupted memory partitions. It's what devs called 'superbricks' if I'm not mistaking...
You could try a ROM with a PIT file, hoping that would repartition any bad sectors.
Again, I could be mistaken. Try to read some other threads around here. A lot of.others have also encountered this problem
khok3893 said:
<ID:0/015> factoryfs.img
Click to expand...
Click to collapse
When you stuck at factoryfs.img = system partition corrupted
I tried with PIT file (Q1_20110914_16GB.pit) and ICS LYP Rom and it stucks on "NAND WRITE START" that comes after "factoryfs.img" I even uses "re-partition" in Odin. Nothing works.....
So lots of bad things have happened while trying to install a rom to my note 3. I had it rooted, with the safestrap bootloader installed, but then I tried to upload the Dynamic Kat rom but it when it went to boot it just had a blue flashing light. I then tried to restore through download mode and now it is saying
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION ENABLE
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So I went through Odinv 3.09 and tried to flash back to stock using N900AUCUBMI9, but I keep getting failed messages through that. I also downloaded another program that was a one-click odin based restore but that also gave the same fail message. I eventually tried to go through Kies 3 & Kies but both said my device was not compatible with it. I am at a loss.
When trying to use odin I get this.
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
tomdrumtomthumb said:
So lots of bad things have happened while trying to install a rom to my note 3. I had it rooted, with the safestrap bootloader installed, but then I tried to upload the Dynamic Kat rom but it when it went to boot it just had a blue flashing light. I then tried to restore through download mode and now it is saying
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION ENABLE
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So I went through Odinv 3.09 and tried to flash back to stock using N900AUCUBMI9, but I keep getting failed messages through that. I also downloaded another program that was a one-click odin based restore but that also gave the same fail message. I eventually tried to go through Kies 3 & Kies but both said my device was not compatible with it. I am at a loss.
When trying to use odin I get this.
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> One Click Downloader Mode
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
UPDATE:
Through Odin, I have flashed just the .pit file. This allowed me to boot back into the stock OS. However, the stock OS is very buggy (Direct Pen Input has stopped x10) and various other problems.
The problem is now, that I still can't flash the stock OS through Odin. I just keep getting fails. Any idea why?
What baseband version does your device show in Settings/General/About Device?
andygev35 said:
What baseband version does your device show in Settings/General/About Device?
Click to expand...
Click to collapse
I don't know, because now its stuck in a bootloop.... it should be the baseband version for the stock firmware at 4.3 though. So it should've been N900AUCUBMI9.
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. (NOT 4.4.4) Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Use the four-file restore method and use the download links I provided in the OP.
andygev35 said:
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Click to expand...
Click to collapse
I did flash to dynamic kat from 4.3 which resulted where I couldn't boot. But then I restored to 4.3. (It was broken as I said, something about the pen not working and lots of lag). The note 3 was on 4.3 to begin with. Right now I'm trying to get my 4.3 to work but Odin just gives me fail messages for when I try to flash 4.3. Flashing the BL and AP end in errors. Flashing everything else gives a pass.
The only thing I know to try is to update to NC2 (4.4.2) via Odin. Maybe someone else knows how to restore to JB.
andygev35 said:
I could be wrong here, but isn't DynamicKat based on kitkat? That would make it incompatible with 4.3. You may need to just Odin to stock kitkat 4.4.2. (NOT 4.4.4) Then you can use safestrap 3.75 and load DynamicKat.
http://forum.xda-developers.com/showthread.php?t=2703006
Use the four-file restore method and use the download links I provided in the OP.
Click to expand...
Click to collapse
Alright, I did this and it worked! Its on kitkat now! Thank you!
Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!
master-i said:
Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!
Click to expand...
Click to collapse
If you have TWRP installed, you can just ADB the file over. Easy.
If you only rooted and want to preserve your KNOX flag, you need to ODIN back to stock and then re-root. It's not destructive, so it's not nearly as bad as it sounds
I don't have twrp for now but can i Install it on download mode ? I just tried to install it and it stop on Start upload (on odin)
Follow these instructions. Download ODIN from that link too
http://forum.xda-developers.com/tmo...irmware-sm-g920t-firmware-odin-guide-t3077706
Do i lose my data? and where Can I find the [Unified Driver Installer] on step 2?
No you won't lose your data at all, you will lose root, but all you need to do is re-root the phone.
http://developer.samsung.com/technical-doc/view.do?v=T000000117
I think it's easier to flash only the build.prop no? is it possible?
Thanx to help me bro!
No at this point, IMO, this is the easiest way to get you back to where you were. I assume you're on the stock ROM just rooted.
Yes, I were on the stock room just rooted by PingPong. Hope it will not make my phone slower or make it crash more often... :/
Yeah just ODIN back to stock, then re-root using PingPong, it's really not as bad as it sounds. All of your apps and user data including all settings will still be there.
@se1000
Please look this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Have you had your phone in download mode for a while? If so, try rebooting the phone
se1000 said:
Have you had your phone in download mode for a while? If so, try rebooting the phone
Click to expand...
Click to collapse
Of course I just retried again same error... I can't understand because I see the 0:COM3 on Odin...
Are you using the ODIN from the link? I had problems with other versions
se1000 said:
Are you using the ODIN from the link? I had problems with other versions
Click to expand...
Click to collapse
Yes the V3.10
Were you trying to run ADB earlier? Try rebooting the PC
I closed and reopen Ondin on Administrator and now it's blocked with: <ID:0/003> SetupConnection..
Try a different USB cable or different USB port. Seems ODIN can get a bit finicky
I rebooted PC and my Phone and unplugged and still the same
maybe it's because i tried to install twrp?
Shouldn't matter, as long as you're in download mode and ODIN shows light blue it should work