Database Info

[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] [HELP] GT-N8013 - Soft Bricked(ODIN MODE ONLY)

GT-N8013
Blue/Gray
16GB Wifi Only Model
I was watching a youtube video, my tablet froze for an hour, died, then I let it charge and it rebooted into the samsung logo. After that it decided to go white screen and goes to a white screen every time it's booted. I've been trying to resolve this on my own with various resources for about a month now.
I can get to ODIN mode no problem, but I can't flash anything. I have recently bought a new OEM Samsung USB cable and tried multiple versions of ODIN on two different machines. Directly connected to the motherboard and not USB 3.0 ports.
I think the solution to my problem may be answered:
Here: http://forum.xda-developers.com/showthread.php?t=2268735
or
Here: http://forum.xda-developers.com/showthread.php?t=2713297
It is hard for me to comprehend the English used in the first link as I think Authors first language is not English. I think what he is saying is that if ODIN is not working then you have to flash the PIT file via adb and a SD card, but I cannot access Recovery, and I don't recall fully how to use ADB in Downloading Mode, if that's possible at all. He also states I may need to downgrade my bootloader version based on the last ROM that I had on my tablet. If someone could educate me on that I'd appreciate it.
The 2nd link says I need the stock firmware for my country(I live in the U.S. of A.) and to nand erase all but I feel like that should be used as a last resort. I did download both N8013UEALI3(4.0.4) & N8013UEUCMI3(4.1.2) from sammobile.com though.
When I try to flash just a Recovery/ROM, with Autoreboot checked, I get the PIT error message below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_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>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, with Auto Reboot & Re-partition checked, I get the error message:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, Re-partition checked, I get the error message:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT w/ Recovery/ROM, Re-partition Checked and Auto-Reboot checked, I get:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any assitance would be greatly appreciated, I've been without my tablet for a month now. I have any backup, I don't recall the ROM I flashed because it was so long ago, but I'm pretty sure the version was Jellybean. I know my recoevry was one of the later CWM TouchScreen Rom recoverys but I can't recall the version. Thanks for any help, please let me know what information I'm lacking or what I can do, thank you all for your time.

Update
Any assistance would be greatly appreciated. I have tried to different PIT files for the PIT mapping and they both failed. Getting pretty desperate now. I can't even NAND Erase All, I gave that a shot and it failed:
When I select NAND Erase All, stock rom(4.0.4 or 4.1.2), Pit, & Re-Partition checked, Nand Erase all Checked, I get the following in ODIN 3.07 and 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.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> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm starting to think its the ECCM and maybe I need a JTAG repair. Like I said before, I can't get into recovery, I just get a all white screen. When the tablet first died I got the Samsung logo and then it rebooted and went White, I never got the Samsung logo again. Any help please? Even if it's just recommendations for trusted JTAG repair sites, because I don't trust the ones I've found ths far. Or know PIT files that have worked for flashing on the N8013. Anything at all.

BUMP
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.

onlysafonne said:
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.
Click to expand...
Click to collapse
@onlysafonne what file fails? I see your log above

carl1961 said:
@onlysafonne what file fails?
Click to expand...
Click to collapse
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!

onlysafonne said:
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!
Click to expand...
Click to collapse
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you

Heimdall
carl1961 said:
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you
Click to expand...
Click to collapse
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.

onlysafonne said:
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.
Click to expand...
Click to collapse
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer

carl1961 said:
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Click to expand...
Click to collapse
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.

onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
if you not under warenty I would maybe buy a used one on ebay that might just have a cracked screen, you might even find a 32GB one
http://www.ebay.com/itm/Samsung-Galaxy-Note-10-1-32-GB-Wi-Fi-GT-N8013-/361155880699?pt=US_Tablets&hash=item54169166fb

onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
onlysafonne, I have the same problem. I can use Odin and get to CWM but nothing I flash will get me past the Samsung Galaxy Note 10.1 image I cannot even get it to shut off. It will go black then power right back up.
I have flashed with Nand Erase All checked only
KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_u ser_low_ship.tar
Any ideas? I have not heard of JTAG

I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks

Flying_Phil said:
I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks
Click to expand...
Click to collapse
have you tryed to odin install your firmware? usally the bootloop is caused because you need to do a factory reset to get rid of (in your case OmniRom 4.4.4) your firmware as I see is http://www.sammobile.com/firmwares/confirm/31427/N8010XXUDNE4_N8010BTUDNF1_BTU.zip/

Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or cwm recovery. But there is still twrp.
I can't open your link :-/

Flying_Phil said:
Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or can recovery. But there is still twrp.
I can't open your link :-/
Click to expand...
Click to collapse
try this N8010 recovery with the included 3.07 odin put in PDA slot and do no check re-partiton look at picture
@Flying_Phil
yes samfirmware is picky go here and search your N8010 you most likly need to signup (it's free) and as you see most odin updates or "home" which means it does not do a factory reset which is ok if your updating a stock unrooted rom so you need to do a factory reset when coming from a custom rom.

well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.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> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!

Flying_Phil said:
well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.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> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Click to expand...
Click to collapse
ok so did you try and reboot to stock recovery and do a factory reset

carl1961 said:
ok so did you try and reboot to stock recovery and do a factory reset
Click to expand...
Click to collapse
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.

Flying_Phil said:
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.
Click to expand...
Click to collapse
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB

carl1961 said:
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB
Click to expand...
Click to collapse
GT-N8010 16GB. Need more?

Galaxy tab 2 10.1 (3g + WIFI) optus net work australia, boot loop

Given one of the above to try and fix.
It is in a boot loop. turns on for 10 seconds or so then re starts.
Only download is accessible via power + vol up. Pwr + Vol down recovery is not accessible.
I have Odin 3.07. plus other versions as well
Have downloaded TWRP 2.8.5.0 and tried to install. Odin says it went well but cannot run it via pwr + Vol dwn or any other key combination.
Have also downloaded latest offical samsung rom (4.2.2) and tried to install. Odin gets halfway through and stops with fail status, failed to write.
Have a PIT file and tried re-partition. No different.
Tried nand erase all, ends with fails to write.
Have tried 2 cables, 2 computers and 4 different usb ports.
Have latest usb drivers.
odin Log
ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMK3_P5100OPSDMK1_P5100XXDMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1005)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> Sbl.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> system.img
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What else can i try to recover this or is it beyond repair?
James

sup8pdct said:
Given one of the above to try and fix.
It is in a boot loop. turns on for 10 seconds or so then re starts.
Only download is accessible via power + vol up. Pwr + Vol down recovery is not accessible.
I have Odin 3.07. plus other versions as well
Have downloaded TWRP 2.8.5.0 and tried to install. Odin says it went well but cannot run it via pwr + Vol dwn or any other key combination.
Have also downloaded latest offical samsung rom (4.2.2) and tried to install. Odin gets halfway through and stops with fail status, failed to write.
Have a PIT file and tried re-partition. No different.
Tried nand erase all, ends with fails to write.
Have tried 2 cables, 2 computers and 4 different usb ports.
Have latest usb drivers.
odin Log
ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XXDMK3_P5100OPSDMK1_P5100XXDMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1005)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> Sbl.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> system.img
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What else can i try to recover this or is it beyond repair?
James
Click to expand...
Click to collapse
Two things
1. Are you really sure that the firmware file is from a trusted source? If possible get a second copy from different trustable source.
2. The great Emmc of our tab, which is turning out to be the biggest killer of our tab. Perhaps emmc replacement.

Got it from Sammobile.. Finding another source with out broken links or getting heaps of rubbish or payimg $$$ is hard.
I found a vodafone one. same thing happens. earlier version, ditto.
Was thinking the EMMC is damaged. woundering if it is worth fixing.
billysam said:
Two things
1. Are you really sure that the firmware file is from a trusted source? If possible get a second copy from different trustable source.
2. The great Emmc of our tab, which is turning out to be the biggest killer of our tab. Perhaps emmc replacement.
Click to expand...
Click to collapse

sup8pdct said:
Got it from Sammobile.. Finding another source with out broken links or getting heaps of rubbish or payimg $$$ is hard.
I found a vodafone one. same thing happens. earlier version, ditto.
Was thinking the EMMC is damaged. woundering if it is worth fixing.
Click to expand...
Click to collapse
I can't gulp this down my throat. Why the emmc is such a pain, I can understand a hard brick, but what really is causing this? I see few cases already, It's a soft brick and you can get into download mode as well. Firmware off sammobile does work.
Changing emmc requires professional, I don't know about the cost involved but i was looking on YouTube at a emmc replacement case. The guy did changed the emmc and it was back to life again. They could charge exorbitant. But still I don't feel so sure as to just put it all on emmc, root cause must be found out.

I now have tried win XP (win 7 before) with another rom. Still the same.
Am wondering if there is a write lock happening.
What does Flash lock in odin mean?
can it be undone?
billysam said:
I can't gulp this down my throat. Why the emmc is such a pain, I can understand a hard brick, but what really is causing this? I see few cases already, It's a soft brick and you can get into download mode as well. Firmware off sammobile does work.
Changing emmc requires professional, I don't know about the cost involved but i was looking on YouTube at a emmc replacement case. The guy did changed the emmc and it was back to life again. They could charge exorbitant. But still I don't feel so sure as to just put it all on emmc, root cause must be found out.
Click to expand...
Click to collapse

sup8pdct said:
I now have tried win XP (win 7 before) with another rom. Still the same.
Am wondering if there is a write lock happening.
What does Flash lock in odin mean?
can it be undone?
Click to expand...
Click to collapse
http://www.droidforums.net/threads/guide-complete-samsung-odin-v3-xx-options-and-reference.278159/
Read this here, this checkbox wasn't needed for our device. I would not suggest you to check this box. It might work or further damage your device.
I think your device is at unbrickable mode right now, cause i have read people share this like they have flashed every bit of wrong files on their devices, which in normal case people will never try to even think of and yet are at the same situation.
I would suggest you to go through every detail you can find about the unbrickable situation.

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..

Soft Bricked GT-S7582

I am following "[Guide] Know your Device: Galaxy S Duos2 GT-S7582~Root~Odin~CWM~ROM LIST |2014.06.08|" this process to flash my device but its not working
please help
odin log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7582DDUANJ1_S7582ODDANJ1_S7582DDUANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> BcmCP.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anybody tell me the problem how can i fix it

Flash the latest firmware from Odin ..u can download it from firmwarefile.com

Muscular droid said:
Flash the latest firmware from Odin ..u can download it from firmwarefile.com
Click to expand...
Click to collapse
I have already download the latest firmware from there.
Is there any other solution available for it then please help me out

rename the .tar.md5 file to .tar, open with winrar or anything that can read .tar and tell me if it having sboot.bin in there or not?
also your phone is s7580 or s7582?

​
sandpox said:
rename the .tar.md5 file to .tar, open with winrar or anything that can read .tar and tell me if it having sboot.bin in there or not?
also your phone is s7580 or s7582?
Click to expand...
Click to collapse
no it doesn't contain sboot.bin in there
i have attached the screenshot of the files in there
and my device is s7582

kishorprabhat said:
​
no it doesn't contain sboot.bin in there
i have attached the screenshot of the files in there
and my device is s7582
Click to expand...
Click to collapse
Looks like the last stock ROM which installed on your device is too old and its bootloader doesn't accept sign of new stock ROM, try to download another ROM but lower down in the list on samfirmware

sandpox said:
Looks like the last stock ROM which installed on your device is too old and its bootloader doesn't accept sign of new stock ROM, try to download another ROM but lower down in the list on samfirmware
Click to expand...
Click to collapse
okay trying with oldest one available on samfirmware
wait for my replay because free download service of samfrimware is under maintenance till 28 Nov so unable to download rom

kishorprabhat said:
okay trying with oldest one available on samfirmware
wait for my replay because free download service of samfrimware is under maintenance till 28 Nov so unable to download rom
Click to expand...
Click to collapse
http://updato.com/firmware-archive-select-model?q=gt-s7582

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7582DDUANJ1_S7582ODDANJ1_S7582DDUANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> BcmCP.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> dt-blob
<ID:0/005> hidden.img
<ID:0/005> param.lfs
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
downloaded rom from the site you provided and it worked
thank you very much

Hello everyone.
I have a big problem i had root on my GT-S7582
On the other day the mobile phone hung up and when I went to call it it arrives the part of for the password and it restarts and it stays like this always and does not let to reset by keys somebody knows how to solve this problem? I've tried several things but it does not work.
Sorry for my english
(I'm from Portugal, Portugal phone)

SérgioVoid said:
Hello everyone.
I have a big problem i had root on my GT-S7582
On the other day the mobile phone hung up and when I went to call it it arrives the part of for the password and it restarts and it stays like this always and does not let to reset by keys somebody knows how to solve this problem? I've tried several things but it does not work.
Sorry for my english
(I'm from Portugal, Portugal phone)
Click to expand...
Click to collapse
You have to reset your phone, to do so turn it off, go to recovery(press power,home , vol up key simultaneously) then use vol key to move up down, select format or factory reset whatever is present there and then apply it.....it will fix your problem

Vishal Shrivastav said:
You have to reset your phone, to do so turn it off, go to recovery(press power,home , vol up key simultaneously) then use vol key to move up down, select format or factory reset whatever is present there and then apply it.....it will fix your problem
Click to expand...
Click to collapse
Hello.
I already did it wrong but when I go to restart it says error in big letters.

SérgioVoid said:
Hello.
I already did it wrong but when I go to restart it says error in big letters.
Click to expand...
Click to collapse
Then download odin and firmware from Google, put i in your computer, turn off your phone go to download mode(press power button,home key and volume down (not up ) key simultaneously)
Open Odin on computer select PIT/AP and locate firmware you just downloaded connect your phone through usb when it show [com 6 ] or something like that then press start, leave it till process complete, it will reboot in between the process, dont panic just wait till it say ok.....turn it on injoy, i hope you didn't installed any custom ROMs like cyanogen 12,13,14 etc. If you did, then you have to factory reset it as i mentioned earlier

Vishal Shrivastav said:
Then download odin and firmware from Google, put i in your computer, turn off your phone go to download mode(press power button,home key and volume down (not up ) key simultaneously)
Open Odin on computer select PIT/AP and locate firmware you just downloaded connect your phone through usb when it show [com 6 ] or something like that then press start, leave it till process complete, it will reboot in between the process, dont panic just wait till it say ok.....turn it on injoy, i hope you didn't installed any custom ROMs like cyanogen 12,13,14 etc. If you did, then you have to factory reset it as i mentioned earlier
Click to expand...
Click to collapse
OK thank you!
How can I find out what my original Firmaware is? And where can I find the PIT I could not find.

SérgioVoid said:
OK thank you!
How can I find out what my original Firmaware is? And where can I find the PIT I could not find.
Click to expand...
Click to collapse
http://www.samprix.com/samsung-galaxy-s-duos-2-gt-s7582-official-firmware-update/ you will find it here, just download the firmware for your contry,

Vishal Shrivastav said:
http://www.samprix.com/samsung-galaxy-s-duos-2-gt-s7582-official-firmware-update/ you will find it here, just download the firmware for your contry,
Click to expand...
Click to collapse
Did not work does not leave the part that says samsung
I do not know what else to do anymore.

Are you on stock ROM
Sent from my Intex Cloud Swift using XDA Labs
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
Muscular droid said:
Are you on stock ROM
Click to expand...
Click to collapse
Try installing TWRP recovery and flash custom ROM !!!!
Sent from my Intex Cloud Swift using XDA Labs