Database Develop

[Q] questions about rooting, flashing, ...

I've been reading posts on this forum for about 2-3 hours now and I still have some questions.
I have a galaxy s advance with android version 2.3.6 and baseband version XXLK2
i48.tinypic.com/2rz78sm.png
I was planning on rooting my phone and then maybe installing a custom ROM on it.
But I couldn't find a rooted firmware for my region (BELGIUM). And I also couldn't find the stock firmware for my region.
Neither on sammobile.com and neither on samsung-updates.com
My first question is: can I use rooted firmware that's for another region or will this cause problems for me?
My second question is: can I use rooted firmware with another baseband version than XXLK2?
Third question: if the answer on the first two questions is no, how am i supposed to root my phone then?
fourth and for now the last question: what is twrp recovery, and what is it used for, do I need it to root my phone or flash roms?
Thanks in advance!

ahmett75 said:
I've been reading posts on this forum for about 2-3 hours now and I still have some questions.
I have a galaxy s advance with android version 2.3.6 and baseband version XXLK2
i48.tinypic.com/2rz78sm.png
I was planning on rooting my phone and then maybe installing a custom ROM on it.
But I couldn't find a rooted firmware for my region (BELGIUM). And I also couldn't find the stock firmware for my region.
Neither on sammobile.com and neither on samsung-updates.com
My first question is: can I use rooted firmware that's for another region or will this cause problems for me?
My second question is: can I use rooted firmware with another baseband version than XXLK2?
Third question: if the answer on the first two questions is no, how am i supposed to root my phone then?
fourth and for now the last question: what is twrp recovery, and what is it used for, do I need it to root my phone or flash roms?
Thanks in advance!
Click to expand...
Click to collapse
do you want to stay with gingerbread, or upgrade to jellybean?
because rooting and flashing is much tougher in gb than in JB! tell me that i can help you.

Hi,
I got the same phone / baseband version in Austria. Downloaded XXLK2 firmware from sammobile.com, used simg2img to extract system.img, add su binary (=rooted), made a new system.img with make_ext4fs and flashed with heimdall. Meanwhile I used the same procedure to root and flash the jelly bean firmware XXLPY released for the russian market. Therefore I guess you can also flash a different version of gingerbread.
tom

Brainiac.shri said:
do you want to stay with gingerbread, or upgrade to jellybean?
because rooting and flashing is much tougher in gb than in JB! tell me that i can help you.
Click to expand...
Click to collapse
First i want to root my phone and then i want to install custom roms.
Sent from my GT-I9070 using xda app-developers app

RealBorg said:
Hi,
I got the same phone / baseband version in Austria. Downloaded XXLK2 firmware from sammobile.com, used simg2img to extract system.img, add su binary (=rooted), made a new system.img with make_ext4fs and flashed with heimdall. Meanwhile I used the same procedure to root and flash the jelly bean firmware XXLPY released for the russian market. Therefore I guess you can also flash a different version of gingerbread.
tom
Click to expand...
Click to collapse
But i'm from belgium and i couldnt find one for belgium. So you live in austria and downloaded the firmware for austria?
Sent from my GT-I9070 using xda app-developers app

ahmett75 said:
First i want to root my phone and then i want to install custom roms.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
if u upgrade to JB, root is a one step, 5 min process after which it takes a few more minutes to start flashing roms after flashing a new kernel with Clockworkmod. if u wanna start with jellybean, go here.http://forum.xda-developers.com/showthread.php?t=2094318(make sure u install the stock samsung rom first , then root then install recovery, then flash a custom rom) this WILL NOT void ur warranty
on the other hand rooting gingerbread is incredibly complex. if u wanna do that go to this thread http://forum.xda-developers.com/showthread.php?t=1985199
its totally safe to flash anither country firmware using odin.then root the supported firmware. also this will void your warranty,
then to install a new kernel with TWRP recovery , go here : http://forum.xda-developers.com/showthread.php?t=1873119
then finally choose the custom rom u want Jetmod or supressed and flash using TWRP(assuming you know how to atleast nter download and recovery mode!)
do all this in the same order.

Brainiac.shri said:
if u upgrade to JB, root is a one step, 5 min process after which it takes a few more minutes to start flashing roms after flashing a new kernel with Clockworkmod. if u wanna start with jellybean, go here.http://forum.xda-developers.com/showthread.php?t=2094318(make sure u install the stock samsung rom first , then root then install recovery, then flash a custom rom) this WILL NOT void ur warranty
on the other hand rooting gingerbread is incredibly complex. if u wanna do that go to this thread http://forum.xda-developers.com/showthread.php?t=1985199
its totally safe to flash anither country firmware using odin.then root the supported firmware. also this will void your warranty,
then to install a new kernel with TWRP recovery , go here : http://forum.xda-developers.com/showthread.php?t=1873119
then finally choose the custom rom u want Jetmod or supressed and flash using TWRP(assuming you know how to atleast nter download and recovery mode!)
do all this in the same order.
Click to expand...
Click to collapse
So what i'm going to do is:
1. download JB and install it
2. Root
3. then install twrp recovery
4. Flash a kernel with clockworkmod (which kernel do you suggest?)
5. Flash custom roms
Is this the correct order or am i wrong?

ahmett75 said:
So what i'm going to do is:
1. download JB and install it
2. Root
3. then install twrp recovery
4. Flash a kernel with clockworkmod (which kernel do you suggest?)
5. Flash custom roms
Is this the correct order or am i wrong?
Click to expand...
Click to collapse
You can't install any recovery by itself. It comes with kernel. Only kernel with permanent recovery - CWM is ThunderZap now.
1. Download JB, flash it with Odin. - go again to recovery - do factory reset.
2. Root with root.zip from stock recovery
3. Install kernel with CWM (ThunderZap) with dd command in terminal editor
4. Flash custom ROM from CWM recovery.

shut_down said:
You can't install any recovery by itself. It comes with kernel. Only kernel with permanent recovery - CWM is ThunderZap now.
1. Download JB, flash it with Odin. - go again to recovery - do factory reset.
2. Root with root.zip from stock recovery
3. Install kernel with CWM (ThunderZap) with dd command in terminal editor
4. Flash custom ROM from CWM recovery.
Click to expand...
Click to collapse
i'm going to give it a try, waiting for the download to finish

UPDATE: went in to recovery mode, plugged the usb and started the flash got this message:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Одг: [Q] questions about rooting, flashing, ...
ahmett75 said:
UPDATE: went in to recovery mode, plugged the usb and started the flash got this message:
Added!!
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Not recovry, in download mode. Did you unpack file. It should be around 700MB, not 400.
In recovery after flsshing, to do factory reset.
Sent from Galaxy S Advance

exchange exprsee
shut_down said:
Not recovry, in download mode. Did you unpack file. It should be around 700MB, not 400.
In recovery after flsshing, to do factory reset.
Sent from Galaxy S Advance
Click to expand...
Click to collapse
ok, so now i've runned odin as admin, loaded the firmware and i get this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
then i go into download mode and connect my phone and i get this.
<ID:0/003> Added!!
i've read that something has to turn yellow, or isn't that necessary?
EDIT: i just pressed start and it is installing i think

Одг: [Q] questions about rooting, flashing, ...
ahmett75 said:
ok, so now i've runned odin as admin, loaded the firmware and i get this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
then i go into download mode and connect my phone and i get this.
<ID:0/003> Added!!
i've read that something has to turn yellow, or isn't that necessary?
EDIT: i just pressed start and it is installing i think
Click to expand...
Click to collapse
Search google "samsung download mode" and you should see image of it. When you power your phone with vol.down+home+power you get question do you want to continue. You press volume up to confirm. And after that with your phone connected and file in PDA hit start.
Sent from Galaxy S Advance

ahmett75 said:
UPDATE: went in to recovery mode, plugged the usb and started the flash got this message:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I have a similar issue. In Odin/Download mode I tried flashing Jelly Bean. Here is what I get from Odin:
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> power_management.bin.md5
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In red on the screen is "CUSTOM PWR MGT BINARY !!"
Did a factory reset. Same issue. Turned on Settings -> Applications -> Development -> USB Debugging + Allow mock locations. Same issue.
Any ideas?

JBAdvXDA said:
I have a similar issue. In Odin/Download mode I tried flashing Jelly Bean. Here is what I get from Odin:
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_I9070XXLPY_I9070SERLPY_660490_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> power_management.bin.md5
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In red on the screen is "CUSTOM PWR MGT BINARY !!"
Did a factory reset. Same issue. Turned on Settings -> Applications -> Development -> USB Debugging + Allow mock locations. Same issue.
Any ideas?
Click to expand...
Click to collapse
How much time does this take? Maybe try to redownload firmware file.

shut_down said:
How much time does this take? Maybe try to redownload firmware file.
Click to expand...
Click to collapse
Maybe 10seconds.
I downloaded Odin3.07 (Was using Odin3v1.7). From: http://forum.xda-developers.com/showthread.php?t=2086965
It is still showing in red "CUSTOM *** BINARY !!!!" but is now progressing to other components.
Will report back.

JBAdvXDA said:
Maybe 10seconds.
I downloaded Odin3.07 (Was using Odin3v1.7). From: http://forum.xda-developers.com/showthread.php?t=2086965
It is still showing in red "CUSTOM *** BINARY !!!!" but is now progressing to other components.
Will report back.
Click to expand...
Click to collapse
It should last couple minutes. Something is wrong at start. I am not saying redownload Odin, whole firmware file. But you did unpack it from zip, it should be noticable that it is corrupted when you did that on pc.

shut_down said:
It should last couple minutes. Something is wrong at start. I am not saying redownload Odin, whole firmware file. But you did unpack it from zip, it should be noticable that it is corrupted when you did that on pc.
Click to expand...
Click to collapse
Thanks.
Used Odin3v3.07 to install JB and it boots! Now the baseband version is "Unknown" and I have no service.

JBAdvXDA said:
Thanks.
Used Odin3v3.07 to install JB and it boots! Now the baseband version is "Unknown" and I have no service.
Click to expand...
Click to collapse
Try wiping cache reset in stock recovery and problem solve

I've succesfully upgraded to JB, rooted and flashed kernel.
Any suggestions about ROMS for i9070 ?

[Q] Need

Currently using my first android device! Samsung galaxy note 3 for att and I decided to root it. I am currently running 4.3 but want to update to 4.4 in hopes of fixing some gps issues i've been having. I tried to use ODIN to load up the stock 4.3 firmware but have been encountering some errors. My phone no longer turns on, when it does it says "firmware upgrade encountered an issue" please select recovery mode in kies and try again. I have downloaded keys 3 and tried to recover it using that but no luck. Am willing to post screens or answer any questions you guys may have!.

Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?

reply
Face_Plant said:
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
Click to expand...
Click to collapse
Im on 4.3. I've only tried using Odin and kies which have both failed me. what im about to try is "androidrootz.com/2013/10/how-to-unrootunbrick-at-galaxy-note-3.html".. can you link to your suggestion?

I'm not sure how to copy/paste links with Tapatalk, but if you go to the general sub form for the AT&T Note 3 on this website it should be on the first page. Look for a thread titled "MJ5 restore and optionally provides root" or something along those lines. It's a somewhat long process that can be intimidating at first, but if you read the directions and follow them exactly you should be good to go.

replyy
Face_Plant said:
Are you on 4.4.2 or 4.3? If you're on 4.3, have you tried the MJ5 restore posted in the general section?
Click to expand...
Click to collapse
Face_Plant said:
I'm not sure how to copy/paste links with Tapatalk, but if you go to the general sub form for the AT&T Note 3 on this website it should be on the first page. Look for a thread titled "MJ5 restore and optionally provides root" or something along those lines. It's a somewhat long process that can be intimidating at first, but if you read the directions and follow them exactly you should be good to go.
Click to expand...
Click to collapse
:/
Was gonna try this "forum.xda-developers.com/showthread.php?t=2559715" was what you said. But alot of the links to the downloads were broken. and i didnt see any reposted :/

I thought only the mi9 firmware was available at kies?

dbartdog said:
:/
Was gonna try this "forum.xda-developers.com/showthread.php?t=2559715" was what you said. But alot of the links to the downloads were broken. and i didnt see any reposted :/
Click to expand...
Click to collapse
Just to show people what all im working with..
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 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 and try again.
Edit:
What happens when i use ODIN3 v3.07 to load the original .tar file (AP_N900AUCUBMI1_1562818_REV03_user_low_ship_MULTI_CERT.tar.md5)
I connect my phone
Odin detects it fine.
Place it in the PDA, Press start.
Only things checked are Auto reboot and F. Reset time
Wait about 5 mins for it to work.
Fails at the end. With this msg.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900AUCUBMI1_1562818_REV03_user_low_ship_MULTI_CERT.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
When trying to use Kies 3.
Start up kies with phone plugged in, in odin mode.
-the connected device is not supported by kies 3.
-confirm
so i go to tools>Firmware upgrade and initializ.
Enter model SM-N900A
Followed by S/N
Device can be initialaized to its original settings.
<ok>
Prepare for firmware upgrade
<start upgrade>
Downloads file for firmware emergence recovery of note 3 from server.
waits...
Failed to upgrade firmware due to an unexpected error.

In the restore to MJ5 thread the link to mega is no good(it was all the files in one dl, at one time)
Also I had to disable the antivirus on my computer for the sec_csc to download dont forget to turn it back on

frome901 said:
In the restore to MJ5 thread the link to mega is no good(it was all the files in one dl, at one time)
Also I had to disable the antivirus on my computer for the sec_csc to download dont forget to turn it back on
Click to expand...
Click to collapse
So I got my phone back up and working! WOOT.
But not im back to 4.3 android and am wanting to update to KitKat 4.4 I go to settings and go to software update but it says there is none available. what do?

dbartdog said:
So I got my phone back up and working! WOOT.
But not im back to 4.3 android and am wanting to update to KitKat 4.4 I go to settings and go to software update but it says there is none available. what do?
Click to expand...
Click to collapse
Do you really want to be stuck on KitKat 4.4 the offical is a locked up rom for now. try searching for the "NB4 update" thread? theres also a leaked 4.4 one click too

What ^ this guy said.

[Q] Stuck in Odin Mode and have tried everything

Hello,
Ok so I have an issue and have been searching and trying different options all day. I was rooted on MI9 with safestrap installed booted into Rom slot1 with Xnote flashed. For some reason I don't understand, I reset both stock rom and rom slot 1 (wiped data). After I restarted the phone, it was stuck with the Galaxy Note 3 logo and Custom padlock. After researching, I tried to flash stock MI9 using odin. This is the message I kept getting:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900AUCUBMI9_1625098_REV03_user_low_ship_MULTI_CERT.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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when I restart the phone, it goes to Odin mode where it says to use Kies to fix the firmware issue. Of Course, Kies didn't recognize it. It will boot into downloader mode but not recovery mode. I now uninstalled Kies and tied to flash stock many times using just the AP button. The whole time getting the same message. I can't think of anything else to try. All I want to do is go to a firmware (I don't care what) stock and unrooted.
I see this popping up on the threads but have not been able to get back to normal. This sucks! Cann anyone please help me?

I have tried MI9 one click and it says "MD5 hash value is invalid"...Now when I do get into download mode it says:
ODIN MODE
PRODUCT NAME: SM-N900A
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: Enable
<android icon>
Downloading...
Do not turn off target.
When it is in normal mode, it shows the above but asks to hook up to Kies for a firmware issue.

Arty Dodger said:
I have tried MI9 one click and it says "MD5 hash value is invalid"...Now when I do get into download mode it says:
ODIN MODE
PRODUCT NAME: SM-N900A
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: Enable
<android icon>
Downloading...
Do not turn off target.
When it is in normal mode, it shows the above but asks to hook up to Kies for a firmware issue.
Click to expand...
Click to collapse
Are you sure you're on mi9? Looks like youre on mj5 already looking at your dl mode. If you are on mj5 you cant use kies to load up mi9 we cant downgrade bootloader.

This may or may not help you.
I recently worked on a friends AT&T S4 (locked bootloader like our Note 3). It was doing the same thing you describe. Once it got to System.img it seemed stuck. Then would fail. I was then on the screen that said use Kies. I tried 3 times to flash without luck but I noticed that each time it made a little more progress. I changed usb cables the 4th or 5th flash and it finally went through and completed the Odin flash. So I would say keep trying to flash, change USB and see if it gets a little farther each time.
Good luck

Haitian said:
This may or may not help you.
I recently worked on a friends AT&T S4 (locked bootloader like our Note 3). It was doing the same thing you describe. Once it got to System.img it seemed stuck. Then would fail. I was then on the screen that said use Kies. I tried 3 times to flash without luck but I noticed that each time it made a little more progress. I changed usb cables the 4th or 5th flash and it finally went through and completed the Odin flash. So I would say keep trying to flash, change USB and see if it gets a little farther each time.
Good luck
Click to expand...
Click to collapse
I was able to get it fixed by following http://forum.xda-developers.com/showthread.php?t=2559715. I was on MJ5, but I thought I was on MI9. I felt pretty dumb when I figured it out. I freaked out all day and when I got home, tried that and it worked, but you have to complete all the steps. If you just leave it at Flashing MJ5 it will be very buggy and will not work that great.
I feel so much better now! Thanks guys!

[Q] Can't Flash S3 (GT-I9305)

Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.

Unkiejay said:
Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.
Click to expand...
Click to collapse
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?

Wood Man said:
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?
Click to expand...
Click to collapse
i am facing the same exact same probelm. i tried with different usb ports and cable results are the same . please someone help
:crying:

Tried to root 5.0.2 with 5.1.1 guide - softbricked it [SOLVED]

Hello!
Ok, I'll admit I didn't read closely enough in my haste to root my new phone, and now it's softbricked. My phone was brand new and still on the 5.0.2 firmware, and I tried to follow the guide at link here on XDA before updating to 5.1.1. After flashing the sboot.bin, it rebooted, but stuck at the Samsung logo screen with some green text at the top of the screen:
ASV TBL VER = 15
ASV TBL VER2 = 1285
ASV big:10 LITTLE:10 630:11 MIF:10 INT:10 CAM_DISP:10 (I think that's right, it's very tiny!)
I've been stuck there ever since! I can get into download mode, but that's it.
I'm not sure what to do now. I've tried reflashing the sboot.bin file, and I've tried flashing the 5.1.1 stock (COF8) ROM (which fails!)
Am I correct in thinking that the sboot.bin file will only boot 5.1.1 roms? If so, how do I get the ROM flashed if ODIN won't do it?
Any help will be greatly appreciated!

I've been thinking about this problem, and I've come up with two options. Either flash back to the original boot loader, kernel, etc. Or somehow get a stock 5.1 ROM to flash.
Any thoughts?
Sent from my (old) SGH-M919 using XDA Free mobile app

More info...
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.

SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
.
Click to expand...
Click to collapse
You are a lifesaver. More specifically a $579 saver.

Lovetoflyguy said:
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
Click to expand...
Click to collapse
Scratch that. I used PeaZip instead of WinRar or 7Zip. I didn't name it tar.md5, flashed and it's booting up now. We'll see if it works.
How did you get the new tarball file you made to pass the MD5 check? I can't get past that check when I make a new .tar file or tar.md5.

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....
Click to expand...
Click to collapse
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode

vegeta_badman said:
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode
Click to expand...
Click to collapse
Always!!!! flash Odin files in Download mode.

i did everything as u said it...But i can not flash the STOCK (COF6) in odin it fails..plz help:crying:

Lovetoflyguy said:
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.
Click to expand...
Click to collapse
how did you flash the firmware back to stock because i cant enter download mode:crying: