Develop Bugs

Soft Brick problem URGENT

Hello fellow xda members!
Im having issues with my soft bricked samsung galaxy s3 AT&T. I tried flashing stock rom after using CM10 nightlies for a while. I totally forgot to fully whipe all data. So i went ahead and tried to flash stock rom using odin. I believe my problem lies in what i did in odin when i was flashing the rom. I followed the HOW TO UNROOT & FACTORY RESET YOUR SGSIII video in the ALL IN ONE NOOBS VIDEO GUIDES post ( http://forum.xda-developers.com/showthread.php?t=1728824&highlight=heimdall ). In the video he told me to make sure i have F. Reset Time dissabled before i flash. I think that this might be the problem.
Also as an attempt to fix this issue, i attempted to follow the how-to on fixing a soft brick (which is what i believe is the problem) on this post ( http://forum.xda-developers.com/showthread.php?t=1840030 ). Odin gives me a nice big FAIL when i attempt to flash the VRALEC bootchain. I followed the guide (so far) to the exact letter, and what i should do if i have problems flashing those files.
One more thing i forgot to mention, the only thing that i can do is boot into download mode. I cant boot into recovery T_T.
Thanks in advance!
ps: let me know if there is anything i have missed to help find the solution!

bump

I rooted my friends GS3 yesterday and he was on Verizon. We had to flash the unlocked VRALEC bootchain. We never do that for AT&T as it's not locked.
Not sure what else I can say, but just make sure you didn't flash anything from the Verizon S3...
EDIT: Yeah man that second thread you linked to is Verizon. They are completely different phones...
Just download the Odin files, put your phone into download mode and make sure you have Samsung USB drivers installed and Windows 7 (mine doesn't work on Win8) and put the odin files into the PDA section and flash.

geoldr said:
I rooted my friends GS3 yesterday and he was on Verizon. We had to flash the unlocked VRALEC bootchain. We never do that for AT&T as it's not locked.
Not sure what else I can say, but just make sure you didn't flash anything from the Verizon S3...
EDIT: Yeah man that second thread you linked to is Verizon. They are completely different phones...
Just download the Odin files, put your phone into download mode and make sure you have Samsung USB drivers installed and Windows 7 (mine doesn't work on Win8) and put the odin files into the PDA section and flash.
Click to expand...
Click to collapse
Thanks brother, i guess i missed that it was Verizon (duh!) i feel stupid. Il try it again, and update.

All you have to do after you flash the stock ROM is go into recovery by powering off the phone and holing the volume up +power + home button and select wipe data/factory reset and it will boot. Hope you didn't do more damage by flashing something from your second link.
Sent from my SGH-I747 using xda premium

GalaxyMaster said:
All you have to do after you flash the stock ROM is go into recovery by powering off the phone and holing the volume up +power + home button and select wipe data/factory reset and it will boot. Hope you didn't do more damage by flashing something from your second link.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I think he should be Okay because Odin said 'failed'. But I think it would be a good idea to Odin back to stock because that will re-partition your phone and I think it would be better overall to just start fresh.

happened to me a few times lol
what you do is
get a stock rom for your phone
go to recovery, wipe everything(data, dalvik, cache)
go to download mode
flash stock rom through odin
done.

pcshano said:
happened to me a few times lol
what you do is
get a stock rom for your phone
go to recovery, wipe everything(data, dalvik, cache)
go to download mode
flash stock rom through odin
done.
Click to expand...
Click to collapse
You see, that would be a great idea, but i cant get into recovery

lemonbox said:
You see, that would be a great idea, but i cant get into recovery
Click to expand...
Click to collapse
You don't need recovery for Odin. It will completely wipe your phone for you.
Here is a link to the AT&T Odin file for the latest release.
http://hotfile.com/dl/182224582/7ad...I747_ATT_1_20121116120521_7p9l4qgqoh.zip.html
Got it from here:
http://forum.xda-developers.com/showthread.php?t=1968625

geoldr said:
You don't need recovery for Odin. It will completely wipe your phone for you.
Click to expand...
Click to collapse
Oh sorry, i thought you wanted me to get into recovery and wipe data first before i flash?

Don't worry about recovery just Odin back to stock. This process will already wipe everything. After successful flash in Odin if it bootloops, then do a factory reset in stock recovery
Sent from my SGH-I747M using xda app-developers app

jbradbury said:
Don't worry about recovery just Odin back to stock. This process will already wipe everything. After successful flash in Odin if it bootloops, then do a factory reset in stock recovery
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thank you !! Hope this will solve my problem.

lemonbox said:
Oh sorry, i thought you wanted me to get into recovery and wipe data first before i flash?
Click to expand...
Click to collapse
jbradbury said:
Don't worry about recovery just Odin back to stock. This process will already wipe everything. After successful flash in Odin if it bootloops, then do a factory reset in stock recovery
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
I never said to go into recovery, somebody else did And yes just Odin back to stock. And just like jbradbury said. If you are still getting a bootloop after you Odin to stock, to a factory reset in the samsung 3e recovery. The stock Samsung 3E recovery will be flashed when you Odin.

*sigh* no luck, i download the stock rom, put my phone into download mode, loaded the rom and flashed it, and maybe 3 seconds later i got FAIL again. Any other suggestions anyone? Also i noticed SECURE CHECK FAIL : aboot in red at the top left of download mode screen.
This is what odins message box told me if it helps:
<ID:0/004> Added!!
<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/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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

lemonbox said:
*sigh* no luck, i download the stock rom, put my phone into download mode, loaded the rom and flashed it, and maybe 3 seconds later i got FAIL again. Any other suggestions anyone?
This is what odins message box told me if it helps:
<ID:0/004> Added!!
<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/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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
flash an ICS rom

Danvdh said:
flash an ICS rom
Click to expand...
Click to collapse
Il give it a shot. I found an ICS based rom here ( http://forum.xda-developers.com/showthread.php?p=29119632#post29119632 ). Before i download and flash, just wanted to make sure i got the right one ^.^ Would that be fine?

question: did you run it as admin?
but it seems to me that the authorization failed
try restore IMEI and flash again

pcshano said:
question: did you run it as admin?
but it seems to me that the authorization failed
try restore IMEI and flash again
Click to expand...
Click to collapse
I just ran odin as administrator and nothing . Also, how does one restore IMEI?

I have successfully unbricked my phone :3 The problem was the rom. Im with virgin mobile aka Bell and from this experience i learned that the I747 does not equal I747M
Thank you all for the help!!!! Seriously.

lemonbox said:
I have successfully unbricked my phone :3 The problem was the rom. Im with virgin mobile aka Bell and from this experience i learned that the I747 does not equal I747M
Thank you all for the help!!!! Seriously.
Click to expand...
Click to collapse
Yes they are different phones. I'm glad you got it figured out.

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

[Q] [Help] Flashed stock ROM via ODIN, hangs at T-Mobile splash screen

Need to warranty my Note 3 due to hardware camera problem. I unlocked my factory 4.3 bootloader, installed TWRP, and went to W03 Slim 8.5. I have never ran the official 4.4.2 update which I believe implies my bootloader is still the 4.3 version.
I launched ODIN 3.07, and flashed the N900TUVUBMI7 rom from this page: AndroidRootz
Everything appears to have ran in ODIN successfully:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone boots up with no warnings on the Samsung splash and then gets to the white T-Mobile 4G LTE splash and just hangs there. I've tried reflashing the firmware from ODIN with the same result.
What should I do? Should I flash up to the 4.4.2 version? The phone is going back regardless so I don't care about anything other than getting this to boot up so I can exchange it.

Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.

negativefx said:
Tried from ODIN 3.09 with the same result. I have the 4.4.2 firmware but I am hesitant to flash it until someone can shed some light on this issue.
Click to expand...
Click to collapse
Try wiping /data or a factory reset in recovery.

Have you tried re-downloading the 4.3 firmware. Sometimes this can happen from a bad download.

Shawn said:
Try wiping /data or a factory reset in recovery.
Click to expand...
Click to collapse
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!

happened to almost everyone, I had to odin v3.09 and run 2 times... the 1st time it said it was successful, but stuck at the Samsung screen, the 2nd time booted up just fine..
on my link I have odin and the new firmware, old firmware my stock not rooted roms... all u need for my stock not rooted is chainfire superuser app, then download busybox, your done,
look on my signature for any files needed, also uploading the Samsung driver.. no kies needed.

negativefx said:
You read my mind... Just read that an ODIN firmware flash doesn't wipe. Booted to recovery, did a wipe data from recovery and rebooted. Works like a champ. Thanks!
Click to expand...
Click to collapse
No problem, I used to forget to wipe when I put my phones back to stock with Odin.

I'm currently running an AOSP rom 4.4.2...what are the steps to flash the 4.3 stock rom touchwiz??

4.4.2 is out? newest firmware available atm is nk3 4.4.2
anyway
1. d/l firmware file from sammobile.com
2. boot to download mode
3. run odin and plug phone into pc(if you have a mac your on your own from here as i have a pc and not a mac)
4. load file you just d/led(in tar.md5 format) into the pda slot(i'm assuming you have odin 3.07)
5. click start and wait to profit.
you can also d/l 4.3 firmware from same site if you really want it.
good luck

I meant I have a AOSP custom rom its regular google not touchwiz
Sent from my SM-N900T

right. thats how you restore stock touchwiz though. it's pretty simple.

will I lose root?..so if I have this current baseband which is MI7..does that mean that I still have 4.3 bootloader?
Sent from my SM-N900T

yeah you will lose root. but you can reroot it afterwards. and yes if you flash the 4.3 firmware it'll keep the 4.3 bootloader or should anyway. might want to wait on someone else to chime in here on the bootloader and baseband though as i am not really sure. i just upgraded from a note 2 to my note 3. and i run nk3 on my note 3. it's fine with all the roms i have tryed so far though. no issues at all.

I'll wait a lil bit cause someone just told me that since I'm on 4.4.2 custom aosp rom I won't be able to revert back to 4.3 Touch wiz
Sent from my SM-N900T

i'd just go with the nk3 firmware. it's 4.4.2 stock touchwiz. works great. but thats me. hehe

this is my android version and that is my baseband..im soo confused
View attachment 3079890
Sent from my SM-N900T

ok. your baseband and bootloader are 4.3, but your custom rom is a 4.4.2 rom. if you install the nk3 firmware. you'll have stock touchwiz 4.4.2 with the nk3 baseband and bootloader along with the csc file. and a bunch of otherstuff. it will all be upgraded. instead of having a custom 4.4.2 rom you'll be on the newest stock touchwiz version which is nk3.
nk3 can be rooted. you can install a custom recovery and still reinstall custom roms.
if that makes sense.

that's wat I was looking for, thanks dude..this is my version of ODIN that I have..this is what I used to root the phone when I first got it last year
View attachment 3079899
Sent from my SM-N900T

1.8.5 will work. been so long since i seen that version. just add the tar.md5 file to the pda slot. click start and profit

is it better to upgrade ODIN to tge latest version or just stick with 1.85?
Sent from my SM-N900T

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

[Q] Can't install a rom

Okay. So I flashed a rom onto my Galaxy S3 (actually a friend's but whatever) and the camera bugged out entirely, far worse than I expected. Okay, no biggy, so I tried to restore the backup I made. That wont work for some odd reason. I get stuck at the white AT&T screen. So I figured it was safe to assume that I needed a new rom. Factory reset yields the same result. I'm okay with going back to stock rom, I don't really care. I just want it to work again.
I tried flashing a stock rom with odin, which yields this:
<ID:0/004> Added!!
<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/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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And I cannot figure out how to access the phone in my computer.
I can get into download mode and I have a relatively recent version of TWRP recovery installed. If I can either a) get a flashable rom or b) get into the phone I should be able to fix it.
Any advice appreciated!
EDIT: May have figured out why odin wont flash. Was not aware of the locked bootloader that prevents downgrading. The only stock rom I could find was for 4.1.1, and honestly assumed it was fine. Searching for a new stock rom now and trying that.

Don't flash a stock ROM with Odin. It's failing because the ROM is trying to downgrade your bootloader. Attempts to downgrade the bootloader could brick your phone.
The bootloader is not locked on the s3.
You need to find out which bootloader is on your phone in order to flash the right files.

audit13 said:
Don't flash a stock ROM with Odin. It's failing because the ROM is trying to downgrade your bootloader. Attempts to downgrade the bootloader could brick your phone.
The bootloader is not locked on the s3.
You need to find out which bootloader is on your phone in order to flash the right files.
Click to expand...
Click to collapse
Okay, assume I'm a total moron. What would you suggest?
Before this, it was running stock 4.4.2, if that helps determine the bootloader.

tylerrex96 said:
Okay, assume I'm a total moron. What would you suggest?
Before this, it was running stock 4.4.2, if that helps determine the bootloader.
Click to expand...
Click to collapse
Boot into TWRP. Then go into Advanced -> Terminal Command. You'll have to select a folder. It doesn't matter what you pick, just select one. A less sensitive area like sdcard might be safer than say /, but you won't be entering any commands that alter anything.
To check your bootloader enter:
Code:
getprop ro.bootloader
Knowing that will help with what to do next.

jason2678 said:
Boot into TWRP. Then go into Advanced -> Terminal Command. You'll have to select a folder. It doesn't matter what you pick, just select one. A less sensitive area like sdcard might be safer than say /, but you won't be entering any commands that alter anything.
To check your bootloader enter:
Code:
getprop ro.bootloader
Knowing that will help with what to do next.
Click to expand...
Click to collapse
I don't have the phone on me, just about to go work on it. However, if I could access the SD card and place a rom of some sort on it, would it be safe to flash? I was just thinking. I'll let you know of the results of that in a few minutes.

From custom recovery flashing ROMs is relatively safe because the zips packaged to be flashed from custom recovery don't typically mess with your bootloader. Messing with the bootloader seems to be the most common way to brick an at&t gs3.
Odin is another story. Odin tars often will flash firmware, especially the"return to stock" variety, and from mjb forward the bootloader on the i747 can't be downgraded.
I'd still verify what firmware you're on before flashing anything else.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

jason2678 said:
From custom recovery flashing ROMs is relatively safe because the zips packaged to be flashed from custom recovery don't typically mess with your bootloader. Messing with the bootloader seems to be the most common way to brick an at&t gs3.
Odin is another story. Odin tars often will flash firmware, especially the"return to stock" variety, and from mjb forward the bootloader on the i747 can't be downgraded.
I'd still verify what firmware you're on before flashing anything else.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

I realized that I am in fact a total moron. The original rom (CM12 5.0.1 or w/e) that had the huge problem with the camera was still on the phone. I reflashed that so the phone would show in My Computer, and then just downloaded/flashed a different rom.
Thanks for the help anyway guys! I don't intend to mess with phones that aren't mine anymore haha, getting the recovery to stick was hard enough alone.