Develop Bugs

4.3 to 4.1.1 fails, Firmware encountered an issue...

I was trying to flash my s3 back to 4.1.1. It failed when I was using odin. Now, I get the message Firmware encountered an issue..
I downloaded kies 3 but my phone will not connect to it.
Iv tried many different things and odin keeps failing after a couple lines.
What can I do?

b_rad_1983 said:
I was trying to flash my s3 back to 4.1.1. It failed when I was using odin. Now, I get the message Firmware encountered an issue..
I downloaded kies 3 but my phone will not connect to it.
Iv tried many different things and odin keeps failing after a couple lines.
What can I do?
Click to expand...
Click to collapse
Does your phone still boot? or do you have a Brick?
If it still boots Leave it alone. you can flash any rom you want to as long as there is no bootloader in it.
If you already bricked it, is it a soft brick or hard brick?

theramsey3 said:
Does your phone still boot? or do you have a Brick?
If it still boots Leave it alone. you can flash any rom you want to as long as there is no bootloader in it.
If you already bricked it, is it a soft brick or hard brick?
Click to expand...
Click to collapse
When I insert the battery and power on it has a message saying " firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
above that in the top left it says
odin mode
product name :sgh-1747m
custom binary download: yes (1count)
current binary: samsung official
system status: official
qualcomm secure boot: enable
warranty bit: 0
bootloader rp swrev: 1
This is all it does. I can get into download mode. But everytime I try to flash it says failed.

This is 4.3 touchwiz? or 4.3 custom rom?
If custom, I encountered a similar issue where going back to Odin failed. Trying to turn on the phone and going into recovery mode let "Firmware encountered and issue". I had also encountered the problem of Kies not connecting. It would say "connecting" but nothing would happen.
Can your phone boot in download mode?
If yes, you should be able to recover the firmware with Kies.
You may need to use the previous version of Kies and not Kies 3, as I think Kies 3 is only for 4.3 android touchwiz versions. If you had touchwiz 4.3 from the OTA, you may be stuck as I think people have had problems trying to go back to 4.1.
In Kies go in Firmware Upgrade and Initialisation. You will need to know your phone's model and serial number. They can be found behind the battery.
Follow the steps and you should be able to go back to 4.1.1.

chemicalseb said:
This is 4.3 touchwiz? or 4.3 custom rom?
If custom, I encountered a similar issue where going back to Odin failed. Trying to turn on the phone and going into recovery mode let "Firmware encountered and issue". I had also encountered the problem of Kies not connecting. It would say "connecting" but nothing would happen.
Can your phone boot in download mode?
If yes, you should be able to recover the firmware with Kies.
You may need to use the previous version of Kies and not Kies 3, as I think Kies 3 is only for 4.3 android touchwiz versions. If you had touchwiz 4.3 from the OTA, you may be stuck as I think people have had problems trying to go back to 4.1.
In Kies go in Firmware Upgrade and Initialisation. You will need to know your phone's model and serial number. They can be found behind the battery.
Follow the steps and you should be able to go back to 4.1.1.
Click to expand...
Click to collapse
Its 4.3 touchwiz ota last week.
I will try kies instead of kies 3. With kies 3 it just says connecting, wont connect. When I do the Firmware Upgrade and Initialisation. I type in my model and it just closes.
Im downloading kies right now...

Oh also, I had encountered the closing problem when in Windows.
I was able to not have the random closing problem when using Kies on a Mac.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

b_rad_1983 said:
Its 4.3 touchwiz ota last week.
I will try kies instead of kies 3. With kies 3 it just says connecting, wont connect. When I do the Firmware Upgrade and Initialisation. I type in my model and it just closes.
Im downloading kies right now...
Click to expand...
Click to collapse
Kies has be installed and when I click on tools- Firmware Upgrade...
I type in the model and it says "Please check the model name and enter it". I click ok and it goes back to the main screen, nothing happens.

when i open kies and plug in the phone it says "connecting".... 5mins has passed..same thing..

Hm, yeah it's odd.
I had the same issue with the main screen saying connecting forever, which didn't matter for upgrading the firmware.
Do you have the att version?
I'm assuming you put SGH-I747 for model?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

My fix
I'm not an expert but I had the same problem due to the 4.3 release. You can't go back to an earlier release because the new boot loader is
locked. Nothing worked until I googled and located the exact .pit file and flashed it in Odin. I was rather desperate by then as I had a two day old
phone, lol. Kies doesn't have the newer release so I don't think you can use it. I used cwm mod recovery and flashed to a rooted stock 4.3 rom.
Hope this helps or someone can help more.

chemicalseb said:
Hm, yeah it's odd.
I had the same issue with the main screen saying connecting forever, which didn't matter for upgrading the firmware.
Do you have the att version?
I'm assuming you put SGH-I747 for model?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Rogers
SGH-I747M

Im currently looking for the stock 4.3 rogers file

I cant find what I need as im not 100% sure what im looking for..
im currently downloading
SGH-I747M_RWC_I747MVLDMF1_I747MOYADMF1_Original.zip

b_rad_1983 said:
I cant find what I need as im not 100% sure what im looking for..
im currently downloading
SGH-I747M_RWC_I747MVLDMF1_I747MOYADMF1_Original.zip
Click to expand...
Click to collapse
I reached the download limit..cant download it

Which Odin are you using? If you arent using it try Odin 3.09.

theramsey3 said:
Which Odin are you using? If you arent using it try Odin 3.09.
Click to expand...
Click to collapse
3.07 is what i used.

b_rad_1983 said:
3.07 is what i used.
Click to expand...
Click to collapse
I just thought about it you have to go back with the 4.3 because if you do succesfully flash anything older you will Hard brick your phone, right now you should be able to recover with the 4.3 odin file.

theramsey3 said:
I just thought about it you have to go back with the 4.3 because if you do succesfully flash anything older you will Hard brick your phone, right now you should be able to recover with the 4.3 odin file.
Click to expand...
Click to collapse
Where can i get the 4.3 odin file?

Check sammobile.com

b_rad_1983 said:
Where can i get the 4.3 odin file?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
You have to register for their site to be able to download. in the search bar about 1/3 page down on right type in SGH-I747M then find your carrier and download the appropriate file.
After that if you still dont like 4.3 you can flash whatever rom you want in CWM or TWRP or atleast thats whats been rumored. I have no clue I like 4.3 and havent had any issues with the rom I had a hard brick that I caused and recovered.

CM nightly did something to my dad's phone

I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!

Nobody? =\

Razor1973 said:
I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!
Click to expand...
Click to collapse
First of all, I'd say (from my experience) screw Kies. Go straight to flashing the STOCK ROOTED S3 files. Do NOT load any custom bootloaders or anything. This is step one, using Odin to get back to stock root. Here is a link to a tutorial (in case you need it, it has the files too): Click Here
Now once you finish that, go ahead and use Odin to flash the latest CWM or TWRP (up to your preference, I use TWRP). To get the latest TWRP for Odin, go HERE.
After you have the custom recovery, you should make a Nandroid backup in TWRP. Also, at this step, for the love of your sanity teach your dad how to make a backup. This might save you down the road
Now that you have a backup and are rooted, you can start flashing the roms. Make sure that you do NOT flash any bootloader OR modem unless they are the I747UCDMG2 ones. IF you flash those you will be fine.
Hope this helps!

Well, I had no choice by to use Kies because ODIN would always fail or crash. Only after I flashed using Kies could I use ODIN successfully. So I just flashed using Kies again, which allowed me to ODIN (3.07) the AT&T file in that thread you gave me. However, ODIN fails a few seconds into the flash with the following error. Any other ideas? Thank you for the help.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
By the way, phone won't boot up and ODIN will crash or any other attempt, as you can see in my second screenshot (same condition I was describing in my OP). It looks like it goes past the boot flash, but crashes on cache. So I need to flash via Kies again. It's been the only way I can start all this over.
In case it makes a difference, before the first ODIN attempt, the download mode read "CURRENT BINARY: SAMSUNG" and after it failed, download mode read "CURRENT BINARY: CUSTOM".

Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

xSharpi said:
Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Click to expand...
Click to collapse
These are flashabe through recovery, not ODIN. Both bootloader and ROM files are ZIP's and ODIN expects TAR, MD5, SMD, GZ or TGZ in the PDA section.
As I had mentioned, I cannot flash anything through a custom recovery (and I've tried several, including TWRP and CWM) because the recovery complains that the ROM is for a d2att and my device isn't. My device *is* a d2att, only that CM nightly flashed something to it that makes it identify itself as something different, it sounds like.
I really am stuck. So far, the only ROM I have been able to flash is stock 4.1.2 using Kies and nothing after that.
Any other ideas please???

Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4

A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

xXshur1kenXx said:
Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Click to expand...
Click to collapse
I just used Kies to flash to stock 4.1.2 successfully (which has always been the case) and then the S3 Toolkit 7.5 to root (screenshots). After the last step, the phone doesn't boot up (same thing always happens when I try to root), so I can't install GooManager or ROM Manager. However, I am able to get into stock recovery, so I will try to follow steps RockRatt recommends and report again. Thank you.

RockRatt said:
A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Click to expand...
Click to collapse
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.

Razor1973 said:
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.
Click to expand...
Click to collapse
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

xXshur1kenXx said:
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Click to expand...
Click to collapse
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).

Razor1973 said:
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).
Click to expand...
Click to collapse
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

xXshur1kenXx said:
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Click to expand...
Click to collapse
It's my dad's phone. LOL

RockRatt said:
Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Click to expand...
Click to collapse
What are you apologizing for??? God, no. It was me who bricked the phone, not you!
I'm about to leave the house and go to this really good cellular repair shop very close to me to see if they do JTAG repairs. I was going anyways to take my original Nexus 7 for a screen replacement. I tried to do it and screwed it up too. hahahaha

Razor1973 said:
It's my dad's phone. LOL
Click to expand...
Click to collapse
My mistake. Meant to say if he could haha. Sorry i couldn't help more. Hope the JTAG works!
Sent from my SAMSUNG-SGH-I747 using Tapatalk

You have been very helpful. Guy doesn't do JTAG repairs. I will keep calling shops in town. If none does, I will ship it. Thanks!

For JTAG repair, have you checked this site? You still have to send the phone in, though.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii/

Flash stock rom on SCH-i925 with odin.

Hello, I have a bricked SCH-i925 Verizon. I'm trying to update the rom from odin. It uploaded the file to the device, but what keeps happening is when it gets to write nand it fails. I'm doing it from the odin menu (power+vol down). What might I try to get it to work? I'm using win7 and odin 3.07. I go the majority of them and tried them all, but all do the same. I'm flashing I925VRAMK1_I925VZWAMK1.

tauntt said:
Hello, I have a bricked SCH-i925 Verizon. I'm trying to update the rom from odin. It uploaded the file to the device, but what keeps happening is when it gets to write nand it fails. I'm doing it from the odin menu (power+vol down). What might I try to get it to work? I'm using win7 and odin 3.07. I go the majority of them and tried them all, but all do the same. I'm flashing I925VRAMK1_I925VZWAMK1.
Click to expand...
Click to collapse
Were you able to return the tablet to its original state?

Ura535 said:
Were you able to return the tablet to its original state?
Click to expand...
Click to collapse
Nope she's bricked. Even with the stock rom Odin fails to flash. I think it's the locked bootloader that's why it won't work. Verizon is a useless company.

[Q] Won't boot after return to stock via ODIN attempt

Was trying to get the phone back to stock so I can upgrade. I followed the instructions on the How to Return a Device Back to Stock thread, downloaded the stock TAR, rebooted and tried to boot into recovery but it would not let me. I then tried to boot into the device as normal and now I have a screen with the message Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again. Any suggestions? I downloaded and tried but cannot connect via Kies 2.6.. I can still get into the device via ODIN. Suggestions?

What firmware did you use to flash? Flash NH7 if you haven't

A little back-story and a possible solution.
demonr6 said:
Was trying to get the phone back to stock so I can upgrade. I followed the instructions on the How to Return a Device Back to Stock thread, downloaded the stock TAR, rebooted and tried to boot into recovery but it would not let me. I then tried to boot into the device as normal and now I have a screen with the message Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again. Any suggestions? I downloaded and tried but cannot connect via Kies 2.6.. I can still get into the device via ODIN. Suggestions?
Click to expand...
Click to collapse
I've never updated my S4 past the MDL firmware. I encountered this problem a few months back when I wanted to revert back to 100% stock MDL. I had updated my baseband/modem though to NB4, yet still obviously had the MDL bootloader. I was scared to death that I had bricked my phone because nothing I did would let me boot past that screen. I couldn't get to recovery, normal boot, nothing... the phone would just automatically go to that screen: Firmware upgrade encountered an issue.
What I did was simply revert my baseband/modem back to MDL. Once that was done successfully I was able to flash the MDL firmware again and booted right up. If this might be your issue, you will have to know which baseband/modem you were using and which bootloader version you were running before you attempted to flash stock. It should go without saying that the main idea here is to have your baseband and bootloader versions match before flashing the firmware in Odin.
Seems a little odd to me as the stock Odin-flashable firmware includes the modems and all... I'm just passing along what worked for me when I had that problem.

lordcheeto03 said:
I've never updated my S4 past the MDL firmware. I encountered this problem a few months back when I wanted to revert back to 100% stock MDL. I had updated my baseband/modem though to NB4, yet still obviously had the MDL bootloader. I was scared to death that I had bricked my phone because nothing I did would let me boot past that screen. I couldn't get to recovery, normal boot, nothing... the phone would just automatically go to that screen: Firmware upgrade encountered an issue.
What I did was simply revert my baseband/modem back to MDL. Once that was done successfully I was able to flash the MDL firmware again and booted right up. If this might be your issue, you will have to know which baseband/modem you were using and which bootloader version you were running before you attempted to flash stock. It should go without saying that the main idea here is to have your baseband and bootloader versions match before flashing the firmware in Odin.
Seems a little odd to me as the stock Odin-flashable firmware includes the modems and all... I'm just passing along what worked for me when I had that problem.
Click to expand...
Click to collapse
I'll repost from another hoping this explains it as it is the only thing I can think of.. but it worked.
TLDR: installed stock TAR not stock TMO TAR, updated (stupid me) to 4.3, wrong baseband and recovery did not go back to stock using the stock TAR and the Philz Touch recovery would not have flown to return the phone. I figured it out with some help though!
Thank you, that was it. I returned it to stock after following the instructions in the how-to thread but something happened and it boned the recovery where it would reboot into the device every time. Being they need to inspect the phone and in my case they wiped it in front of me when I turned it in it had to be fixed. The device received the updates from TMO and stupid of me I installed them so it was now 4.3 hence the reason I could not install the stock 4.2 anymore. I found the stock firmware you mentioned above and installed it and it fixed it but tripped the counter. I installed the updates from TMO and it was enough to pass inspection. I was able to go into recovery at the store, show the clerk while he was dicking around with the paperwork for the Note I was about to buy. I reached over, showed him "look here it is in recovery and here is wipe data factory reset okay?" and wiped it. He muttered okay thanks or something like that and we were golden. Heck if he could have read the counter anyways it is so flipping tiny.
Thanks for the suggestions!

[Q] ODIN Fail on Unroot and Restore Stock Attempt

I am trying to unroot and restore stock ROM so that I can sell my Note 2014 10.1.
I am using ODIN 3.09 and P600UEUCNK1_P600XARCNK1_HOME.tar.md5
ODIN keeps giving me a FAIL. Looks like "Cant Open Serial Port". I have attached a screen shot from ODIN.
Any ideas as to what I can do here?
Thanks

You need to extract the zip file, and edit .md5 off the end, leaving a .tar file to flash. Make sure you unroot via superuser, then factory reset, then download mode.....Will take 7-9 minutes. Wait for reboot, and removed to show in ODIN. Just did this myself, and device shows official, and recovery is stock, without even the Knox splash showing recovery bit! Easy breezy. I flashed on top of 4.4.4 bootloader the 4.4.2 .tar, and let it update OTA. T-Mobile P607-T Gluck!

Worked like a charm my friend...Thanks so much
Sent from my SM-N900P using Tapatalk

I followed these steps. Flashed same tar file, and successful install. Although i cant update software because says my version has been modified. Anyway to still get updates and be totally stock?

Flash updates from Kies instead OTA is never going to work again.
Sent from my SM-P600 using XDA Free mobile app

Please could anyone had the steps ... the same issue is faced with Note 10.1 Gt-8000
I' m using N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar with ODIN 3.07 which is detecting the com 3 or com 6 with it, and failing always and the device is stopped at either ODIN MODE if I used the volume down plus power or at Firmware upgrade encountered an issue. please select recovery mode in kies and try again... it would never enter to the recovery mode or Bootloader, please advise... thanks in advanced.