Develop Bugs

Have I bricked my phone :( - Experts plz help!

Guys,
!!!!! N00B Alert - I am not an expert in what I am doing. Just following instructions from experts like you. I will try to be as technically articulate as possible !!!
I had recently (about a month ago) rooted my phone to install CM 10.2. I love CM.
In an attempt to unlock my phone I wanted to get back to stock ROM. So I googled and bumped into a way to do it from Kies (not sure if it was a good idea). I followed the instructions and boom the firmware initialization failed half way through. Now when I turn my phone on I get this error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So I tried again multiple times but it won't work.
Then I thought may be there is another way and googled and found this thread - http://forum.xda-developers.com/showthread.php?t=2186967
Followed the instructions to the word, but I see the dreaded FAIL message in ODIN.
Below is the log. (I tried twice in one stretch).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Another thing is I am not able to get to recovery mode. When I try I can only get to the Firmware error screen I mentioned above.
Any help to get out of this mess would be great!

did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

andrewjae04 said:
did you make sure you had the LK3 bootloader before trying to flash stock? if so I also had Odin fail while flashing this firmware. only one that worked for me was root66 firmware. i never booted all the way in but i read that you have to uncheck "auto restart" before flashing, once it is done pull battery and boot into recovery and factory reset. if that doesn't work you can do what I did. Odin flash cwm and install a rom from your sdcard
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I didnt know I have to have the LK3 bootloader, may be I missed in the instructions.
Anyway, how do I flash Clockworkmod from Odin? if I can do that I can get back to CM 10.2 and then try paying for unlock code.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

andrewjae04 said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att/philz_touch_6.07.9-d2att.tar.md5
this is what I used but it didn't work for me without first flashing root66 firmware. i will try to find that link and post it also.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank You!
andrewjae04 said:
http://click.xda-developers.com/api...747UCDLK3.7z&jsonp=vglnk_jsonp_13911206638286
this is the link to root66 for att.
BEFORE YOU DO ANY OF THIS YOU ARE ON AT&T RIGHT?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I am on AT&T.
After I read your post about flashing CWM with ODIN I researched and found a method. I tried it and it PASSED!. Then my phone restarted and boom it booted directly into CM 10.2. Not sure how, felt a bit creepy. Then I updated to latest Nightly CM 11 build and brough back all my apps and my phone has LIFE right now. Thanks for the tip! :good:

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
I believe if you were originally on 4.1 then you still have that bootloader. I dont think OTA updates the bootloader so you should be able to downgrade with the root66 if that is the case.

audit13 said:
Make sure the bootloader that's currently on your phone is not from the 4.3 OTA update. If it is, you can't use Odin to restore a stock rom, you'll have to find a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.

mr_legolas said:
May be it is, I updated to 4.3 thru OTA and after a few days rooted and installed CM 10.2. How do I check?
Then this should be the reason that ODIN didnt work for me. Which genuine source I should look at for a AT&T 4.3 ROM based on the leaked 4.3 AT&T ROM.
Click to expand...
Click to collapse
This is why your flash to stock failed, lucky for you. The MJB bootloader is not downgradable and if 'successful' is bad news...aka brick, requiring serious hacking if not JTAG service to repair. As far as ROM's go as long they do not attempt to change the bootloader (none i've seen do, but you never know) the worst that could happen is a 'status 7' fail in recovery and no change to your firmware, pertaining to the bootloader that is. There are any number of other reasons why something could go wrong during the process. MJB has been around long enough most customs ROM's have probably adapted their updater-script to include it. If not there are ways around this I (and several others) have documented elsewhere. My advice moving forward, make sure to educated yourself thoroughly before attempting anything that can brick your device and if you are not sure, ask first flash later.

dmplus said:
when you say "find" an AT&T 4.3 rom, I wish you could give me a link. I am working with a device that was handed to me that was on 4.3 then flashed to a t999 rom. Now I cannot get it to flash ANYTHING AT&T 4.3 (and I've looked all over), neither in odin, nor in recovery, except, oddly enough it will reflash the same t999 image. The radio (modem) also no longer works.
Click to expand...
Click to collapse
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233

audit13 said:
I assume your can get into download mode. If that is the case, try flashing this in Odin: http://forum.xda-developers.com/showthread.php?t=2498233
Click to expand...
Click to collapse
I had tried to flash that via odin without success. What I was able to do to fix the issue was to flash a custom recovery via odin (TWRP). Then use the custom recovery to blind flash (no signature or md5 check) the ATT modem, and then I was able to flash the link you sent. After that it still didnt boot, so i had to reboot in TWRP, dump caches, reboot again, wait, literally like 5 minutes and it came back to life. Whew, what a day.

[Q] AT&T SGH-I747 Soft Brick Need Help!!!

I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<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/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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?

FuTuRisTiC Zo3 said:
I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<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/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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?
Click to expand...
Click to collapse
Ok I Installed Insecure Boot img via odin3 and my phone rebooted but now instead of it booting at the 1 second samsung screen it goes past it to the galaxy s 3 screen and just sits there. i also installed twrp, it let me mount everything but i cant u adb to push anything and it says i have no os installed. i dont know what moves to make anymore someone please help me out!!!

What version of Android did you have on your phone when it last worked, stock or custom ROM?

dawgdoc said:
What version of Android did you have on your phone when it last worked, stock or custom ROM?
Click to expand...
Click to collapse
its was a stock android rom i believe im not sure what version though.

Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time

lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
yes im able to go into download and recovery mode

lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
oops didnt fully read your 1st post

lemngo02 said:
oops didnt fully read your 1st post
Click to expand...
Click to collapse
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices

If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?

FuTuRisTiC Zo3 said:
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices
Click to expand...
Click to collapse
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.

dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
ok, not to jack his thread, but what if you are on the 4.3 bootloader? i didnt do what he did, but i am stuck in a similar situation. I am on the 4.3 bootloader, but i do have a custom recovery installed. problem is i get an error when i try to wipe. Ive tried flashing stock 4.3 rom via sideload in stock recovery, and modified rom though twrp. both roms install fine, but dont boot, but they do freeze in different points so i know something is being flashed. ive also tried wiping in cwm and stock. im bout ready to flash anything to this phone. oh and a nandroid restore fails after boot img flashes.

FuTuRisTiC Zo3 said:
its was a stock android rom i believe im not sure what version though.
Click to expand...
Click to collapse
From your message, you likely were on stock 4.3. Since you are able to get into recovery and download modes, you may try a restore via custom recovery. Please see the thread below on how to install custom recovery and do a stock restore ...
<http://forum.xda-developers.com/showthread.php?t=2658486>

fastludeh22 said:
ok, not to jack his thread, but what if you are on the 4.3 bootloader? I am on the 4.3 bootloader, but i do have a custom recovery installed.
Click to expand...
Click to collapse
I would then link you to the same thread Larry2999 provided.

dawgdoc said:
I would then link you to the same thread Larry2999 provided.
Click to expand...
Click to collapse
thanks. i had found that thread right after i posted. lets hope. its halfway downloaded. if that doesnt work,ill be posting a thread about the weird way i ended up here and detailed report of what i did and what ive tried...

dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
audit13 said:
If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?
Click to expand...
Click to collapse
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do

never mind folks i got it up and running my only option was to use the sd card so i found my adapter and fixed it. im on 4.1.2 now its updating software now im guessing to 4.3. thank you guys for all the help

FuTuRisTiC Zo3 said:
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do
Click to expand...
Click to collapse
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.

dawgdoc said:
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.
Click to expand...
Click to collapse
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else

FuTuRisTiC Zo3 said:
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else
Click to expand...
Click to collapse
There is a chance that being rooted will prevent you from using the OTA official update. I've seen reports of people being able to update to the official 4.3 while rooted, but I've also seen reports of people not being able to update.
Before you make that update, bear in mind that the official 4.3 bootloader, its name ends in MJB, is the one that will prevent you from ever going back to an older bootloader. Some of the devs and the more experienced on here have no problem with that. Others do consider it an issue. An alternative is to install the leaked 4.3 bootloader, it's name ends in MJ2. That bootloader will allow you to downgrade to the 4.1.1 or 4.1.2 bootloaders, or so I have read. There is information about this in the development and the general forums for our device.
To muddy the waters more; if you intend to sim unlock your device without gettings codes from your carrier you need to do it from the 4.1.1 official ROM. A point you can not return to from the official 4.3 ROM, or so I've read.

I am having a huge booting issue with my Samsung Galaxy S3. Its a brand new one and I tried rooting it but it gave me this error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can get to download mode, but not recovery nor does it boot into the Android OS. I tried putting back the stock OS and it gave me this error:
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried follow a bunch of these threads, but I can't seem to resolve my issue yet. I probably have that 4.3 bootloader which screwed everything up. Can someone help me resolve my issue? I literally got this phone today from AT&T. Thank you.

S3 keeps rebooting into recovery

So this is just a quick question. I've never had a phone reboot into recovery mode before, I've just had them either straight up hardbricked, stuck on logos, not booting, or only booting into Download Mode. From going through other threads (I used the search bar before asking this question. *shock&awe*), I'm gonna assume this is also considered a soft brick.
I'm not sure what was done to the phone because I upgraded to an S5 and passed this S3 down to my little brother who tried to flash another ROM. It was working fine on one of the stable versions of SlimKit before I got the S5 if that matters.
So my questions:
Is this considered a soft brick?
Would flashing stock everything resolve this issue? (reverting back to Stock everything, then reflashing custom ROMs)
Is there a simpler way to resolve this issue to avoid going back completely to stock?
Thanks for looking everyone.

Yes, anytime you can get to download mode or recovery its considered a soft brick. A hard brick will not boot anything at all.
Flashing stock firmware will be the best option imo. But you could just try flashing a rom. You will likely have to factory reset in either case.
If i had to guess, he probably formatted /system and then the rom failed to flash, leaving it with no OS.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

I haven't tried to do anything with it until he gets home, but best bet would be the following? Let me know if something's off or if I should do something another way:
Download stock firmware on the SD card
Factory reset
Flash stock firmware
Flash custom ROM
Reboot
At any point would the phone get unrooted? I'm gonna just make sure everything's set to go when the little bro gets home.

You cannot flash stock firmware from SD. Here is what you should do:
1) download stock firmware to your computer
2) factory reset, wipe cache and dalvik
3) flash stock firmware with Odin and make sure the device boots and works fine
4) flash custom recovery
5) flash custom ROM
6) reboot
Edit: also make sure you flash the correct firmware. For example if the device was ever updated to 4.3 then only flash that 4.3 build, any other that is lower will fail. And yes you will lose root when you flash back to stock but it doesn't mean much at all. You can gain root easily

I keep getting this issue in ODIN when I attempt to flash a stock firmware. Any ideas?
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUENC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Ate you sure you have a T999, not a T999L.
Also, if kies is on your computer, uninstall it.

It's a S3 from T-Mobile directly, so I think it's a T999. I have Kies 3 for my S5 installed, so I'll go ahead and uninstall to try again. Will report back.

Check the sticker under the battery. T-Mobile doesnt sell the T999 anymore, only the T999L. Depends on how long ago you got it.

DocHoliday77 said:
Check the sticker under the battery. T-Mobile doesnt sell the T999 anymore, only the T999L. Depends on how long ago you got it.
Click to expand...
Click to collapse
I love you. Be back after getting the right firmware.

Just fyi in case you didnt know, there is an ota available for the T999L.
After flashing your firmware, go to settings , about device, and tap software update. It should update you to the latest build. (Still just 4.3, but i imagine its a bugfix/security update).
If you are up for putting in a little extra time, i can help you pull the ota (after downloading but before flashing it). If i can get a hold of this ota i can make an easier update method available for other members since no firmware has been released for it.
If you dont want to thats perfectly fine btw. Im sure someone else would get it soon.

[Q] What is the best method to unroot my Note 4?

Stupid me, didn't read up enough to realize that rooting the Note 4 breaks OTA updates. It looks like I can pull the update down via Kies 3. But before I do that I want to make sure I'm going in the right direction.
So far I've found two options, would any of these work to allow OTA updates to work again?
1) Use Kies 3 and install the update
2) Reinstall the original ROM following the instructions on this page...
http://androidromupdate.com/2014/11/07/n910pvpu1anie-sprint-samsung-note-4-sm-n910p-stock-firmware/
3) hit the "full unroot" button in SuperSU Free
Any recommendations guys?

MeepZero said:
Stupid me, didn't read up enough to realize that rooting the Note 4 breaks OTA updates. It looks like I can pull the update down via Kies 3. But before I do that I want to make sure I'm going in the right direction.
So far I've found two options, would any of these work to allow OTA updates to work again?
1) Use Kies 3 and install the update
2) Reinstall the original ROM following the instructions on this page...
http://androidromupdate.com/2014/11/07/n910pvpu1anie-sprint-samsung-note-4-sm-n910p-stock-firmware/
3) hit the "full unroot" button in SuperSU Free
Any recommendations guys?
Click to expand...
Click to collapse
There is already an updated stock rom floating around. Do you have Odin downloaded to your computer?
---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------
cmdauria said:
There is already an updated stock rom floating around. Do you have Odin downloaded to your computer?
Click to expand...
Click to collapse
Just follow this thread and you will be golden!! Very easy thing to do.
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867

MeepZero said:
Stupid me, didn't read up enough to realize that rooting the Note 4 breaks OTA updates. It looks like I can pull the update down via Kies 3. But before I do that I want to make sure I'm going in the right direction.
So far I've found two options, would any of these work to allow OTA updates to work again?
1) Use Kies 3 and install the update
2) Reinstall the original ROM following the instructions on this page...
http://androidromupdate.com/2014/11/07/n910pvpu1anie-sprint-samsung-note-4-sm-n910p-stock-firmware/
3) hit the "full unroot" button in SuperSU Free
Any recommendations guys?
Click to expand...
Click to collapse
1. My phone was stock rooted, I upgraded using Kies and the phone status changed from custom to Official. Then I rerooted and it changed back to custom again. That leads me to believe that if you upgrade using Kies and don't re-root it will accept OTA updates again. I can't confirm that though. (The Knox flag of course remained tripped, no way to fix that as of now)
2. Don't know, but I would expect any full stock Odin would allow OTA as long as the status is Official.
3. NO, I tried the full unroot button on SuperSU and the status remains Custom, and it won't even check for OTA.
Kies was very easy for me, I didn't have to unroot and at least in my case all data and apps were retained. With Odin you will end up with a factory fresh phone and have to restore all your data and apps.

That answers my question. I'll try the kids method and re root later. Thanks for the help

MeepZero said:
That answers my question. I'll try the kids method and re root later. Thanks for the help
Click to expand...
Click to collapse
and did the OTA do anything for ya??? good or bad??

Quick reply, in case someone finds this looking for a similar solution. I removed root completely via the app and then updated via Kies, can't tell yet if I'll be able to OTA update from now on but it was a successful update.

poit said:
1. My phone was stock rooted, I upgraded using Kies and the phone status changed from custom to Official. Then I rerooted and it changed back to custom again. That leads me to believe that if you upgrade using Kies and don't re-root it will accept OTA updates again. I can't confirm that though. (The Knox flag of course remained tripped, no way to fix that as of now)
2. Don't know, but I would expect any full stock Odin would allow OTA as long as the status is Official.
3. NO, I tried the full unroot button on SuperSU and the status remains Custom, and it won't even check for OTA.
Kies was very easy for me, I didn't have to unroot and at least in my case all data and apps were retained. With Odin you will end up with a factory fresh phone and have to restore all your data and apps.
Click to expand...
Click to collapse
Let me get this straight...
You were rooted on NK2 and plugged into Kies and just installed the OB7 without having to flash to factory and update OTA and it worked good? I do have a custom rom installed though.
Once i am re-rooted on OB7 I will not be installing anything but ROMs so I do not need to worry about OTA using Kies would make this sooooooo much easier.

Note 4 sm-n910G
Hi all Android fans of the world. I own a stock rooted Kitkat Galaxy note4. I have Kies 3 and Odin installed and would like to go back to stock unrooted in order to get L-5.0.1 OTA when it finally comes. Can anyone show me a link for the firmware on Sammobile or elsewhere plz... i am a recent convert from iphone and just learning things from scratch. Thankyou in advance

LightspeeDLee said:
Hi all Android fans of the world. I own a stock rooted Kitkat Galaxy note4. I have Kies 3 and Odin installed and would like to go back to stock unrooted in order to get L-5.0.1 OTA when it finally comes. Can anyone show me a link for the firmware on Sammobile or elsewhere plz... i am a recent convert from iphone and just learning things from scratch. Thankyou in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3056478
Sent from my SPH-L710 using xda app-developers app

unroot failed
so i finally managed to find a download for my note 4 that wasnt just jargon. Loaded to ODIN hit the start button all looked good and then i get a fail at the end.
no stuck on the downloading screen with a message:
Volume size is too big
ODIN: Invalid ext4.img
This is what is in the ODIN message if this helps you at all :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1BOC5_N910FEUR1BOD2_N910FXXU1BOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

technophobe321 said:
so i finally managed to find a download for my note 4 that wasnt just jargon. Loaded to ODIN hit the start button all looked good and then i get a fail at the end.
no stuck on the downloading screen with a message:
Volume size is too big
ODIN: Invalid ext4.img
This is what is in the ODIN message if this helps you at all :
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910FXXU1BOC5_N910FEUR1BOD2_N910FXXU1BOC4_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
RQT_CLOSE !!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Removed!!
Click to expand...
Click to collapse
Is your phone SM-N910P or SM-N910F?
You posted in SPRINT Q&A FORUM.
If phone truly is SM-N910F, please post in correct forum.
SM-N910P? Download tar from this post below, the md5 is 68EC06027A3ECFE8471263256B139257
http://forum.xda-developers.com/showpost.php?p=62230599&postcount=1
I'd suggest that one for faster download but only for SM-N910P.
Edit: never mind; try KIES instead.
Sent from my SM-N910P using Tapatalk

sorry my bad
its a SM910F btw still no luck but have put in my original message which is what i thought i was in already...

technophobe321 said:
its a SM910F btw still no luck but have put in my original message which is what i thought i was in already...
Click to expand...
Click to collapse
Got it. So it was rooted at one point with another firmware on it? Did KIES emergency recovery do anything for it?
So I'm guessing it has stock recovery but won't flash or boot at this point. If so, boot into recovery, factory reset, reboot recovery and factory reset again. Power down, remove battery, wait 30 seconds and boot into download mode and flash the stock tar with auto reboot disabled (preferably one that has a md5 checked against downloaded zip, then drag the tar.md5 image out of opened archive with 7zip). You'd only have F. Reset Time enabled in Odin options.
Pass or fail, power down, pull battery, wait 30 seconds, boot into download mode and flash stock tar with auto reboot enabled plus the F. Reset Time enabled. Close Odin with each flash attempt.
One other thing that has worked in the past is considering the suggestions given, use your imagination to try similar things with custom recovery or flashing parts of the stock tar like extracted bootloader and kernel and (emergency) recovering with KIES. Or even flash CWM recovery, write everything, reboot recovery, wipe again, flash a rooted SM-N910F ROM, un-root it and wipe everything, power down, pull battery and flash stock tar. Take notes of attempt to avoid trying the same thing twice until you succeed. I think you will eventually get it. If so report, the steps that you think were primarily responsible for success.
Best wishes for success and return of the phone.
Sent from my SM-N910P using Tapatalk

thanks
thanks for the info it seems the main problem i have is getting the valid file. everyone i try fails with 2 mb left or a 1.7gb file turns into 3.2gb i have paid for sammobile super download and also rapid transfer but both are either corrupted files or just jargon. The one from rapid transfer almost worked until it got near the end and as the file was 3.2 gb it was too large.
i need the correct file for an SM910F unlocked from a reliable source and the genuine file everywhere i try fails or is a virus.

technophobe321 said:
thanks for the info it seems the main problem i have is getting the valid file. everyone i try fails with 2 mb left or a 1.7gb file turns into 3.2gb i have paid for sammobile super download and also rapid transfer but both are either corrupted files or just jargon. The one from rapid transfer almost worked until it got near the end and as the file was 3.2 gb it was too large.
i need the correct file for an SM910F unlocked from a reliable source and the genuine file everywhere i try fails or is a virus.
Click to expand...
Click to collapse
These should also be trusted sources for SM-N910F.
http://forum.xda-developers.com/showpost.php?p=58814028&postcount=1
I think your ISP may be contributing to bad downloads. You may have to download from another location.
SMH; the other suggestions stemmed from previous difficulties with other users after crashing Odin with wrong stock tar. Hopefully your case is as simple as getting a good download for the SM-910F.
Sent from my SM-N910P using Tapatalk

SAMSUNG NOTE 4 SM-N910P SPRINT USA:
I am getting an error while downloading the update to marshmallow when i just clicked on the software update it says "The operator system in your phone is modified through unauthorized way please try to install update through smart switch or visit a customer service" is anyone can help me to figure out this issue i needs to update my phone as soon as it possible. I did check as well my phone has not rooted so far but still is giving an error mentioned above.

need to reprogram as the phone stuck at Samsung Galaxy S III

My phone got crashed which can't bootup. The phone always stayed with Official release, never rooted. I am not sure which version has been upgraded to, now it stuck with Galaxy S 3 screen, only thing I know it has the SecureLinux enabled, so it must be either 4.3 or 4.4. I wanted to reprogram to the official firmware, but not sure if I reprogram to the wrong version, would that causes any problem?
Please help.

additional infomation:
at download mode:
PRODUCT nAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE

Does this download menu look like 4.2?
Or it is 4.3 , I dont see warrenty flag.
Thanks.

No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.

audit13 said:
No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.
Click to expand...
Click to collapse
The phone is T999 for T-mobile, but seems there is one time only that it had official release of 4.2.1 or 4.2.2 available. I am not sure if I should flash the 4.1.2 or 4.2.1 back. But I seem can't find the 4.2.1 or 4.2.2 firmware on line anymore.
Question is that if I try to flash 4.1.2 to the phone, would it cause any problem if it was in 4.2.1?
Thanks all, I know this probably an old issue.

Flashing 4.1.1 or 4.1.2 should be fine.

audit13 said:
Flashing 4.1.1 or 4.1.2 should be fine.
Click to expand...
Click to collapse
###Right now I can't go to recovery mode, so I am trying to program the stock recovery, but failed. When I tried to odin the stock 4.1.2 it failed too. Here is the error during flashing stock recovery.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried different USB cables? Different USB ports? The rom cam from sammobile.com?

audit13 said:
Tried different USB cables? Different USB ports? The rom cam from sammobile.com?
Click to expand...
Click to collapse
Here is the error msg:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)

It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.

audit13 said:
It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.
Click to expand...
Click to collapse
thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3?

You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.

thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3? All I want is just get the phone back. I tried to load 4.3 bootloader, but it failed.

audit13 said:
You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
There is possibility that the pit is wrong, I tried to load the downloaded T999-16Gb pit from download site, maybe that file is not right? Since I can flash the stock boot.img by using Odin for version 4.1.2, the bootloader must be right???, Don't know what aboot.mbn would be affected by anything else.
I am wondering if someone can provide the T999 regular 16GB pit file, the early version of T999, Thanks.

A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.

audit13 said:
A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.
Click to expand...
Click to collapse
is it possible that the phone is upgrading from 4.1.2 to 4.3 and got crashed. but the bootloader is still showing 4.1.2?
what other possible reason that I can't flash aboot.mbn?

Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.

audit13 said:
Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.
Click to expand...
Click to collapse
Reboot to download mode, it is saying the same.
I am trying to flash stock recovery, modem, bootloader, all stock version 4.1.2 Only it can flash 4.1.2 bootloader, the recovery and modem always fails. Also the stock rom got failed.
With the same setting I can flash my other S3 recovery without problem, so the Odin, USB cable should not be an issue.
Thanks.

Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.

audit13 said:
Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.
Click to expand...
Click to collapse
the only problem is that my other working phone is running 4.3. I don't know what is the procedure to program it to 4.3 if my crashed one is in 4.1.2