Database Info

[Q] HELLUP! Firmware upgrade encountered an issue. Please seclect recovery mode in Ki

Firmware Upgrade encountered an issue. Please select recovery mode in Kies & Try again.
I have this problem with my Samsung Galaxy Tab 7.7 wifi
Saw several site and I also use Odin 3 v1.85 but I can nog fix it.
Does anyone has a solution PLEASE??.

Hi,
If u hv made a nand backup... restore it from cwm.
If not, get yr original ROM and reinstall thru odin.
Then reroot and reinstall CWM & install yr prefered ROM/kernel.
Hope it helps.

skycruzer said:
Hi,
If u hv made a nand backup... restore it from cwm.
If not, get yr original ROM and reinstall thru odin.
Then reroot and reinstall CWM & install yr prefered ROM/kernel.
Hope it helps.
Click to expand...
Click to collapse
Hi,
It look like it doesn't get connected to the device.
I need the orgibnal Rom for the device I found a lot on the internet but nothing works though Odin.
Where can I find the orginal Rom.
Regards,
P. Derksen

plsderksen said:
Hi,
It look like it doesn't get connected to the device.
I need the orgibnal Rom for the device I found a lot on the internet but nothing works though Odin.
Where can I find the orginal Rom.
Regards,
P. Derksen
Click to expand...
Click to collapse
Try sammobile...

I have this problem with my Samsung Galaxy Tab 7.7 P6800. I've never tried to flash any custom rom. I was trying to upgrade from HC to ICS official firmware P6800XXLQ2/P6800OXALQ2/P6800XXLPW/P6800XXLQ2. I've tryied several times with odin3 v1.85 and always fail. I've tried again the original HC P6800XXLA4_CSC_TPH and still fail. And always in the end.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800OXALQ2_P6800XXLQ2_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..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> cache.img
<ID:0/006> NAND Write Start!!
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> recovery.img
<ID:0/006> Sbl.bin
<ID:0/006> zImage
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched along the forum and found no more solutions. Can anybody help me? Are there some more instructions to use in odin, another odin version or another program?
Thanks in advance.
I've solved the problem.
Used a wrong pit. Saw the solution not in Galaxy Tab 7.7 Q&A, Help & Troubleshooting but in general.
So thanks again for the magnific forum.

[Q] Root attempt gone wrong

Hi All,
I've attempted to root my SM-900, using Odin 3.09 and followed all the usual steps.
Suddenly I got different coloured horizontal lines on screen and that probably means my attemp didn't go that well...
I've read I should go back to the original firmware using kies, and then try again.
So how do I restore the original firmware?
I have an image (.img) and understand I need samsung Kies.
Question: Do I use Kies or the new KIES3?
How to go from there?
Or is there another way to restore the firmware?
Thanks in advance!

I figured it out already....
I un-tar-red the recovery file. Leaving it as .tar solved the issue.

bricked
my tablet is stuck,tried different usb ports,different odins,different cables .gets stuck on set up connection,now all i get on screen is FIRMWARE UPGRADE ENCOUNTERED AN ISSUE

wolverinex66 said:
my tablet is stuck,tried different usb ports,different odins,different cables .gets stuck on set up connection,now all i get on screen is FIRMWARE UPGRADE ENCOUNTERED AN ISSUE
Click to expand...
Click to collapse
Please describe what is showing on tab's screen
Sent from my GT-S7562 using XDA Premium 4 mobile app

fixed
I was able to flash the stock recovery thanks

Had the same issues. Solved it by reinstalling the USB drivers. Via Kies 3, under the Tools menu. Worked perfectly after that. (Edit. ...for CFautoroot)
Sent from my SM-P900 using Tapatalk

Man that's gotta be a scary moment...
Sent from my SM-P900 using Tapatalk

Need advice
Frank_H said:
I figured it out already....
I un-tar-red the recovery file. Leaving it as .tar solved the issue.
Click to expand...
Click to collapse
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank you

wilsto said:
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank
Since the recovery image was downloaded as aan .tar file, which is a container file like .zip or.7z, I thought that I needed to unzip it.
You can mount the .tar file in Odin as it is, without unzipping it first.
You can find the recovery download location in the CF-root thread.
Click to expand...
Click to collapse

wilsto said:
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank you
Click to expand...
Click to collapse
Mine did that after flashing a different firmware and trying to root. I solved it by first flashing the stock recovery in chainfires thread then rooting.
Sent from my SCH-I605 using XDA Premium 4 mobile app

Duly.noted said:
Mine did that after flashing a different firmware and trying to root. I solved it by first flashing the stock recovery in chainfires thread then rooting.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep me too..

I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.

Install Kies 3, then go into the Tools menu and reinstall the USB drivers. Reboot. Try auto root again. Should work on the first try.
Sent from my SM-P900 using Tapatalk

dodo99x said:
Install Kies 3, then go into the Tools menu and reinstall the USB drivers. Reboot. Try auto root again. Should work on the first try.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?
---------- Post added at 08:39 AM ---------- Previous post was at 08:35 AM ----------
heldc said:
I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.
Click to expand...
Click to collapse
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?

paulskerr said:
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?
Click to expand...
Click to collapse
I did. I did the uninstaller for the USB drivers several times, with no luck. So finally I just deleted the Samsung folders in program files and program files x86. I did not reinstall Kies, just the USB drivers from samsung.com. I used odin 3.09, and it went flawlessly. Well, mostly-wifi took a *long* time to reconnect the first time after boot, but I'd also installed the update just before rooting, so dunno if it was the rooting or the update.

heldc said:
I did. I did the uninstaller for the USB drivers several times, with no luck. So finally I just deleted the Samsung folders in program files and program files x86. I did not reinstall Kies, just the USB drivers from samsung.com. I used odin 3.09, and it went flawlessly. Well, mostly-wifi took a *long* time to reconnect the first time after boot, but I'd also installed the update just before rooting, so dunno if it was the rooting or the update.
Click to expand...
Click to collapse
I finally go also. I did exactly what you did. Thank you

Frank_H said:
Hi All,
I have an image (.img) and understand I need samsung Kies.
Click to expand...
Click to collapse
Where do I get this image?

How many are remembering to unhide developer options and then select usb debugging? The moment I did that everything worked

Whwre did you find the USB drivers on samsung.com? When selecting the SM-P900 it does not offer any for download.

heldc said:
I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.
Click to expand...
Click to collapse
So this happened to me, and this is my first time rooting. I have the tar file for recovery. How do I proceed? I haven't unplugged my note pro, can I just put in the new file in the pda and start, or do I need to restart odin? Really kind of worried...

[Q] bricked device

i was trying to install a recovery with mobile odin than the device got into a boot loop showing only Samsung boot screen i cant get into a recovery mode i can into download mode, but i do that and connect my device to the computer to odin every thing seems normal except that when i try to flash any thing with odin it takes forever and nothing happens till the device runs out of battery. any advice please

come on guys n one can help me here

Mr.Doc said:
come on guys n one can help me here
Click to expand...
Click to collapse
When that happened to me I did a hard reset and then flashed the firmware. Don't know if that helps, a year has passed since I did that.

Mr.Doc said:
i was trying to install a recovery with mobile odin than the device got into a boot loop showing only Samsung boot screen i cant get into a recovery mode i can into download mode, but i do that and connect my device to the computer to odin every thing seems normal except that when i try to flash any thing with odin it takes forever and nothing happens till the device runs out of battery. any advice please
Click to expand...
Click to collapse
What happend that caused your note to get into boot loop? Did it went loop after flashing or something ? When u get into recovery which recovery does it show ? And at the end what are u now trying to flash can u please paste odin message which it shows in the left pain ?

:highfive: it worked finally ive downloaded a new rom from from sammobile 4.4.2 and tried it and it worked like a charm I dnt what happened but it worked and my note is doing fine now thank u guys :good:

Mr.Doc said:
:highfive: it worked finally ive downloaded a new rom from from sammobile 4.4.2 and tried it and it worked like a charm I dnt what happened but it worked and my note is doing fine now thank u guys :good:
Click to expand...
Click to collapse
Good to hear :victory:

Mr.Doc said:
:highfive: it worked finally ive downloaded a new rom from from sammobile 4.4.2 and tried it and it worked like a charm I dnt what happened but it worked and my note is doing fine now thank u guys :good:
Click to expand...
Click to collapse
Glad ur saved..

Brick city!
sbdanish911 said:
Glad ur saved..
Click to expand...
Click to collapse
I have a situation where my VZW LTE SCH-i925 can only access download mode; this was the result of a failed attempt to root/update ROM. I have tried flashing the stock firmware with the below results. I have sourced a PIT; however, when flashed it to fails. I have searched the forums for quite some time and I cant seem to locate anything solid that works. Did you flash KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5 succesfully or is there another ROM on sammobile that I missed?
I have located the following files for the SCH-i925:
recovery1.tar.md5
sboot.bin
SCHI925.PIT
These files were found at http://forum.xda-developers.com/showthread.php?t=2252630
I have also downloaded stock firmware from http://www.sammobile.com/firmwares/3/?download=24285
KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.tar.md5
I also have:
KIES_HOME_I925UVXAMD1_I925UUSCAMD1_1098858_REV00_user_low_ship.tar.md5
Nothing I do seems to work. I see a progress bar but invariably NAND write fails at some point. Can anyone give some guidance? I know search is my friend but apparently I am very lost. Please help, thanks!
Below is the Odin error I receive when flashing the stock firmware from sammobile.com:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I925VRAMK1_I925VZWAMK1_1481643_REV00_user_low_ship.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..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Hello everyone! My case is the following: I bought very cheap bricked Galaxy Note with the help I’ll manage to fix it, but as far my attempt are not successful.
The first thing is that I don’t know the exact model of the tablet. On its back it’s written GT-N8000, but when I boot it in Odin download mode it’s says GT-N8020. Which of them should I believe? Is it possible that it is indeed GT-N8000 but someone tried to flash it with the wrong ROM?
As for the tablet it goes through the “Samsung Galaxy Note 10.1” logo and the proceeds with the “Samsung” boot image and that’s all, it never loads the Android OS.
It doesn’t also boot in recovery mode, but only in download mode – the Odin.
When I try to flash any TWRP for the model (both for GT-N8000 and GT-N8020) it’s unsuccessful, the same is with the stock ROMs for the both models. I tried different ROM files, different TWRP versions, different USB ports, different laptops – the result is the same. I didn’t try different USB cables because I have only one, but the same cable works flawlessly for file transfers with my other GT-P5100. I also tried with the PIT files, but the result again is the same. And here is the log file when I try to flash with TWRP with Odin.
<ID:0/028> Added!!
<ID:0/028> Odin engine v(ID:3.1401)..
<ID:0/028> File analysis..
<ID:0/028> Total Binary size: 7 M
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> NAND Write Start!!
<ID:0/028> SingleDownload.
<ID:0/028> recovery.img
<ID:0/028> FAIL!
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Impossible to understand your multiple posts .
Bricked , modem .bin . nand write .
Reads as Nand failed throw it in the bin .

Can't restore note 5 to stock

I am trying to restore my phone to stock because only stock modified rom works with VR, but doesn't play nice with android wear.
So back to stock I go, however when I put it in download mode load up AP with the file, and hit start it says "FAIL!" I have team win installed and that is how I get to download mode. I only had Auto Reboot and F. Reset time selected as well.
Can anyone advise me on what I may be doing wrong?
Here is the log:
<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 Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Download the stock firmware again the one you're using might be corrupt, also make sure drivers are installed

I have the drivers installed, also tried 2 firmwares, trying one more now.
Was following this guide:
http://www.droidviews.com/restore-t-mobile-galaxy-note-5-sm-n920t-to-stock-5-1-1-lollipop-firmware/

no firmware seems to be working. I also tried a new cable and a few ports. No change.

tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.

Are you using 3.10.7?

I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.

Drachnem said:
tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.
Click to expand...
Click to collapse
How are you entering download mode?
Sent from my SM-N920T using Tapatalk

I've done it by using teamwin, also by holding pwr + home + volume down

guaneet said:
Are you using 3.10.7?
Click to expand...
Click to collapse
tried two...3.10.6, and 3.10.7

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
You have to pay 10.00 to download the files

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
Last time I checked you donated if you wanted, not forced to

Drachnem said:
Last time I checked you donated if you wanted, not forced to
Click to expand...
Click to collapse
Donated to try this fix, hope it works...

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
As I recollect the fee is for the latest PAC, the others are free.

So it got further with the files and the pit file, but it didn't seem to fully work and I want to understand what may be wrong. It said failed in the first box but continued then the next box said pass.
The phone is now booted in setup mode but I wanted to understand what i may run into with this error or if I am fine...
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_N920TUVS2COKC_N920TTMB2COKC_CL5966591_QB7480468_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/004> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:1/004> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:1/004> File analysis..
<ID:1/004> SetupConnection..
<ID:0/005> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Set PIT file..
<ID:1/004> DO NOT TURN OFF TARGET!!
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> SingleDownload.
<ID:1/004> sboot.bin
<ID:1/004> NAND Write Start!!
<ID:1/004> param.bin
<ID:1/004> cm.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img
<ID:0/005> Can't open the serial(COM) port.
<ID:1/004> modem.bin
<ID:1/004> cache.img
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
I don't often have an answer, but after being the benefactor of the knowledge and kindness of others through the years, I'm glad to help when I can.

Drachnem said:
I've done it by using teamwin, also by holding pwr + home + volume down
Click to expand...
Click to collapse
That's the problem you are using twrp enter download mode by volume up+pwr+home
Sent from my SM-N920T using Tapatalk

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
Are you able to post the files here (if that doesn't violate an XDA rule)? Trying to get the old ones and they seems to be gone and really don't want to have to pay, but I guess I will if I have to.

Hey Guys,
Having an issue getting one of my Galaxy Note 5 (SM-N920T) back to stock. I am able to flash stock firmware in Odin 3.10.7 but the phone is bricked. When I flash any stock firmware the phone reboots and is stuck at the Note 5 Splash Screen. If i reboot into recovery and try to do the factory wipe it tells me it can't find "E:" and fails. Only way I can get the phone to boot is if I flash a rooted kernel. Then I noticed it says the Baseband is unknown in settings. I was going to try flashing through ADB but it tells me ADB is disabled, same with flashing from external storage. I cant even get it to reboot into bootloader. I am starting to think the phone needs IMEI repair..

Phone only boots to download mode after failed ODIN installation.

So I was running Ressurection Remix ROM and I was on OG1 but I wanted to upgrade from OG1 to OK4 so I downloaded the .tar for OK4. Went to install it through ODIN and I got this message.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU3BOK4_G900PSPT3BOK4_G900PVPU3BOK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I also tried odin flashing og1 but it does not work I also try to recover through kies but it says device is unsuppported even though it shows me on the phone screen to use the recovery feature in kies.

forget kies, use Odin. Im betting its a bad tar.md5 (same as the thread before this one in this forum). Id get a fresh copy of the next to newest tar.md5 and flash it in Odin, and while youre at it, get a new copy of odin (the one i use is 3.10) and ive been getting all my tarballs from idoneapps.com for a few mos now and theyve been solid as a rock. Give that a whirl and see whatcha got. Also, i think your culprit is a bad bootloader, S5s booting to download mode after a factory image flash is usually caused by the bootloader

youdoofus said:
forget kies, use Odin. Im betting its a bad tar.md5 (same as the thread before this one in this forum). Id get a fresh copy of the next to newest tar.md5 and flash it in Odin, and while youre at it, get a new copy of odin (the one i use is 3.10) and ive been getting all my tarballs from idoneapps.com for a few mos now and theyve been solid as a rock. Give that a whirl and see whatcha got. Also, i think your culprit is a bad bootloader, S5s booting to download mode after a factory image flash is usually caused by the bootloader
Click to expand...
Click to collapse
Got it to work I had redownloaded the tar file and got the latest odin. But still didn't work. I went to go eat and tried it again and then suddenly it worked -.- Odin is unstable compared to HTC's RUU. I am just glad I got it to work
Sent from my SM-G900P using XDA-Developers mobile app

svz235 said:
Got it to work I had redownloaded the tar file and got the latest odin. But still didn't work. I went to go eat and tried it again and then suddenly it worked -.- Odin is unstable compared to HTC's RUU. I am just glad I got it to work
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
Unstable? How so? I can tell you this about Odin, it can take a while for it to load a file of the size of S5 restore tar.md5s. The root files you flash in Odin are small, so Odin only takes about 5 seconds to load them(if that), but a 1.5 GB file can take about 4 to 5 min on slower processors. My desktop (benchmarks at 5700) loads those files in about 90 seconds and almost instantaneously for the root and recovery files
Sent from my SM-G900P using XDA Free mobile app