Database Develop

Can't downgrade from XXLB2?

Hi, i tried to downgrade from XXLB2 to KJ1 with Odin, but it didn't work. NAND write error. Now i am stuck. What can i do?

Hi, where is download link of your new Rom ?
facepalms

Blackflip said:
Hi, i tried to downgrade from XXLB2 to KJ1 with Odin, but it didn't work. NAND write error. Now i am stuck. What can i do?
Click to expand...
Click to collapse
you can start by posting in the correct place... this should go in Q and A not development...
Here this may help you
http://forum.xda-developers.com/showthread.php?t=1318423
or maybe this might
http://forum.xda-developers.com/showthread.php?t=1321268

Moved To Q&A​
Please post all questions in the Q&A section​

sorry for posting in the wrong forum.
So i have tried everything:
- downloaded and tried flashing 2 different stock ROM's from Switzerland XXKK5 and XXLA4 with odin. no avail:
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried installing the AbyssNotekernel42CWTouchOriginalLogo.tar
got into the menu and installed Superuser-3.0.6-efgh-signed.zip
but my SGN still won't boot.
Can someone PLEASE tell me what i am doing wrong?
I just want to go back to stock ROM now since this has been a rotten experience for me.
I know that my SGN is only Soft-bricked, i can still go into Download mode, but Odin will just not take any ROM that i throw at it.
Thank you for your help!

Would be really great if someone could help! Please!

anyone here?

I'm kinda having a similar issue. If i find a way around it I'll tell you.

Blackflip said:
sorry for posting in the wrong forum.
So i have tried everything:
- downloaded and tried flashing 2 different stock ROM's from Switzerland XXKK5 and XXLA4 with odin. no avail:
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried installing the AbyssNotekernel42CWTouchOriginalLogo.tar
got into the menu and installed Superuser-3.0.6-efgh-signed.zip
but my SGN still won't boot.
Can someone PLEASE tell me what i am doing wrong?
I just want to go back to stock ROM now since this has been a rotten experience for me.
I know that my SGN is only Soft-bricked, i can still go into Download mode, but Odin will just not take any ROM that i throw at it.
Thank you for your help!
Click to expand...
Click to collapse
Right click odin and run as administrator
Sent from my GT-N7000 using xda premium

I finally found a way... I downloaded the 3 Part KJ1 Firmware (N7000OXAKJ1)
then i put into Odin (run as Admin of course)
- KERNEL_N7000XXKJ1_CL627135_REV02_eng_mid_ship.tar.md5
into the "Bootloader"
- MODEM_N7000XXKJ1_REV_05_CL1067428.tar.md5
into the "Phone"
- GT-N7000-MULTI-CSC-OXAKJ1.tar.md5
into "CSC"
and flashed my SGN.
Then i did it again but this time i also put the
- CODE_N7000XXKJ1_CL627135_REV02_user_low_ship.tar.md5
or the
- N7000XXKKA_N7000OXXKK5_N7000XXKK5_HOME.tar.md5
into "PDA"
finally my phone booted up again.
after that it was pretty straightforward with updating to ICS Stunner.

N7000 xxlb2 problem
how to root n7000 xxlb2? SuperUser will not install at all.
Can man say what or how to do it? i'll be pleased to hear from you guys.
Thx a lot.

[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 ?

S4 Active Softbricked when trying to go from NC9 to ML2

I have two rooted s4 actives on stock rooted 4.4.2. Had no problems until recently it's been every day I get a nagging message about an ota being available. I can't seem to disable the ota check or Knox on kit Kat. The ota is for my firmware, apparently I'm a version behind but the phones work fine so I really don't want to fix what isn't broken. Any way to block these messages and the forced reboots? The updates fail every time but it's really annoying.
Sent from my SAMSUNG-SGH-I537 using Tapatalk

SebringTech said:
I have two rooted s4 actives on stock rooted 4.2.2. Had no problems until recently it's been every day I get a nagging message about an ota being available. I can't seem to disable the ota check or Knox on kit Kat. The ota is for my firmware, apparently I'm a version behind but the phones work fine so I really don't want to fix what isn't broken. Any way to block these messages and the forced reboots? The updates fail every time but it's really annoying.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
I think you mean you're on 4.4.2, maybe the NC9 firmware? If you are you have 2 options:
Delete, freeze, or rename wssyncmldm.apk and wssyncmldm.odex to disable OTA updates
Update to NE3 using the ML2 firmware and the NE3 OTA. You can re-root afterwards with towelroot, but make sure you back stuff up with Titanium Backup because the process will completely wipe your phone.

Yeah 4.4.2 typo fail. I'll check again but last time with my root file Explorer I could only find the .odex file.
Sent from my SAMSUNG-SGH-I537 using Tapatalk

Devo7v said:
I think you mean you're on 4.4.2, maybe the NC9 firmware? If you are you have 2 options:
Delete, freeze, or rename wssyncmldm.apk and wssyncmldm.odex to disable OTA updates
Update to NE3 using the ML2 firmware and the NE3 OTA. You can re-root afterwards with towelroot, but make sure you back stuff up with Titanium Backup because the process will completely wipe your phone.
Click to expand...
Click to collapse
I admit I'm fairly new to this phone. I know how to flash the ML2 firmware via ODIN. Now once that is sent to the phone, I leave it stock, if I go to settings -> More -> About Device -> Click "Software Update" Will that download the NE3 OTA? Both my phones are currently on NC9 firmware, I have no issues but my wife has some odd problems with her phone. So if I have to go to stock unrooted and reroot that's fine I'll do what I have to - I just want to make sure I know what I need to do before I start.

When trying to flash ML2 files ODIN fails every time. Is it possible to go from NC9 to ML2? I've installed the drivers from Samsung, it detects the phone in ODIN but it can't write to it.
Readout from ODIN 3.04:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I537ATTBML2_2244695_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Now when my phone boots I get "Fimrware upgrade encountered an issue. Please select Recovery Mode in Kies and try again" making it a paperweight...

Also tried on another desktop same results. At this point I'm a bit desperate as it's my only phone.

SebringTech said:
Also tried on another desktop same results. At this point I'm a bit desperate as it's my only phone.
Click to expand...
Click to collapse
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.

Devo7v said:
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Click to expand...
Click to collapse
Phone successfully restored to ML2. I'm now in the process of downloading the ML2 to NE3 OTA File. Hoping that the update goes smoothly. I thank you very much for pointing out my error!

SebringTech said:
Phone successfully restored to ML2. I'm now in the process of downloading the ML2 to NE3 OTA File. Hoping that the update goes smoothly....
Click to expand...
Click to collapse
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.

xdafly said:
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
Click to expand...
Click to collapse
I think he said it was the bootloader.
Devo7v said:
Flash everything but the bootloader and you'll be fine. Since you're on 4.4.2, you can't downgrade the bootloader back to 4.3, that's why it's failing.
Click to expand...
Click to collapse
SebringTech said:
I thank you very much for pointing out my error!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app

xdafly said:
if you don't mind posting, what was the hangup at your first attempt ? Too many files for Odin at first or something else ?
am trying to help out someone who appears to have the same problem as you did.
Click to expand...
Click to collapse
It was the bootloader. When the phone is upgraded to 4.4.2 it's boot loader can't go down from that. So the bootloader from ML2 is incompatible. When I flashed the other three files it worked just fine! Then I applied the patch to get the phone to the latest firmware. It's a .cfg file you rename it to update.zip and put it on the sd card. boot into the stock recovery and install the update. I must admit a few glitches I was having are gone now since upgrading to the latest greatest, and Towelroot made it stupid easy to root.

Ok, good to know, will pass on the information, thank you.

Errors with ATT S5 Active

I recently screwed up my S5 active and am desperate for help.
I only ever really occasionally screw with the OS, and I did a poor job of documenting what I did with this phone, so I will do my best to recollect exactly the state.
The phone is an AT&T Samsung Galaxy S5 active, model G870A
The recovery was some kind of robot icon that would show for maybe ~10 seconds at the start of boot (not a regular android, more square). I've tried searching for it to, as yet, no avail.
I'm fairly certain that the image I put on the device was KoolKit_S5_Active_V1.1.0.
I cannot recall if I used safestrap, towelroot, twrp, or some combination of these in order to get the above on the device. I have copies of each sitting in a folder I created for the phone.
The other day, SuperSU said it needed the binary updated. Me, being dumb, wanting the notification to go away, decided to appease it. It asked if I wanted to do so using recovery. I figured this would be easier, so I clicked "yes". And then my life got a lot more stressful.
When the phone boots now, it goes into ODIN mode and displays the message "android could not do normal boot. ODIN MODE".
I cannot get it to any other screen. Recovery, download mode, whatever. (I'm pretty sure this is download mode, but I cannot initiate any mode, it just goes into this).
I've been poking around on these forums. The first suggestion I thought might work was to use ODIN to (re?) flash towelroot. Or TWRP. I forget which one I tried, but it wound up resulting in a failure in ODIN, and a message on the screen stating something along the lines of "sys rev check fail no version".
I am very confused about what I need to be flashing using ODIN, but I have managed to cobble together that it has to be through ODIN.
I don't necessarily need links, I can find those, and I may already have the files. I'd really like to know which files it is that I need.
Do I need a firmware? What is the file format for that? tar.md5? etc.
Ideally I'd just like to get back to a regular run mode where my worst problem was a wonky USB port. I would deeply appreciate it if anyone could get me in that direction.
Thank you

It's working.
I plugged it in, tried to flash a PIT file. That failed. Apparently one does not flash those alone.
The screen said something like "check failed : PIT" ...
I went here:
http://forum.xda-developers.com/showthread.php?t=2799754
Followed the instructions. Got a failure. (This was, stupidly and fortunately, without restarting phone after pit failure).
Phone rebooted like nothing was ever wrong.
ODIN log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
P.S.: Previously unidentified robot was safestrap:
http://img.wonderhowto.com/img/96/6...hwiz-launcher-your-samsung-galaxy-s5.w654.jpg

Im glad you could fix it.
I also have a problem with a AT&T S5 active, the phone has horrible screen lag (even the booting screen is slow)
I tried doing a factory reset and also doing a downgrade to kit-kat using Odin, but the problem persists

Cannot flash anything through Odin

So here's my problem. I bought my Note 4 (SM-N910T3) with 5.1.1 and rooted. As soon as 6.0.1 released, I downloaded and flashed and then rooted a little later. I started having some small issues because of the root so I did some research and found a systemless root method on XDA that was a possible solution. At some point, probably from flashing MM, my Baseband and Bootloader got updated to the newest at the time. That was fine at the time but I starting missing some of the features of 5.1.1 that got removed in the update. So now I'm looking at iB4STiD's Rapture ROM which is build upon stock 5.1.1 but I've hit a pretty major wall. No matter what I try, how many times, I cannot flash anything through Odin, besides 6.0.1 that I haven't tried. iB4STiD provides the Baseband and Bootloader files to flash with his ROM which are for my specific model.
Now, I've read in a couple places that you can't downgrade your bootloader but that sounds weird to me so maybe someone can explain more if that's correct. Now for some info:
Download Mode Text:
Code:
[COLOR="Red"]ODIN MODE (HIGH SPEED)[/COLOR]
PRODUCT NAME: SM-N910T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (2)
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, R1, A2, P1[/COLOR]
[COLOR="Blue"]SECURE DOWNLOAD: ENABLE[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
Now this is what comes up when I attempt to flash:
Odin:
Code:
<ID:0/008> 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/008> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download Mode:
Code:
[COLOR="Red"]SECURE CHECK FAIL: aboot
[1]eMMC write fail: ABOOT[/COLOR]
I am at the end here and mentally exhausted so if anybody can give some guidance or advice then that would be awesome. Let me know if you need more info!

It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk

nano303 said:
It's silly. But I remember trying to unroot my nte 4 by going back to stock, odin kept failing until I s
Used the official USB cable of the note 4. I had to borrow my step dad's USB to successfully get the thing back working.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.

squiglybob13 said:
Yep I tried 4 different cables and different ports, including 2 OEM samsung cables that came from my Note 4 and an older phone. Nothing.
Click to expand...
Click to collapse
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.

pvsgh said:
You can't downgrade T3 via ODIN once you upgrade to MM. So basically you are stuck with latest bootloader.
Click to expand...
Click to collapse
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.

squiglybob13 said:
Yea that's what I was afraid of. My next issue though is I can't seem to flash ANYTHING via Odin. I even tried a stock rom that matched my current bootloader and it gave me the same error.
Click to expand...
Click to collapse
Use PhoneInfo application from Playstor to check your exact bootloader version and post it here. The error from your 1st post shows only when you try to downgrade.

I believe I've got the same problem (N910T, I tried to downgrade to 5.1.1 so that I can install Rapture v8.2), except in Odin it stops at system.img.ext4 then fails. I tried restoring with my backup through TWRP but now it's giving me this:
extractTarFork() process ended with ERROR=255
Basically I'm stuck with Odin and TWRP, I have the 5.1.1 firmware which doesn't work, and I'm currently downloading the 6.0.1 firmware and hopefully I'll be able to get it working again after this 2.2GB file finishes downloading with my 10mb/s internet -.-