Develop Bugs

4.3 downgrade to 4.1.1 Brick, please help.

I downloaded 4.1.1 from Samsung-Updates.com and then extracted it and tried to flash it in Odin but the program is saying,
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Odin is recognizing the phone and the drivers are installed. The phone, AT&T GS3 I747, is currently running Android 4.3 w/root and custom recovery. The phone is stock otherwise but it is failing for some reason.
***UPDATE*** I just found out from another thread that when you try to downgrade from 4.3 to 4.1.X it WILL BRICK. Dang you Samsung!! >=(
***UPDATE-2*** I would like to know if there's a fix or recovery method for this issue: can't flash ROMs, can't flash with Odin, stuck at AT&T logo, nandroid restore doesn't fix issues.
What I did to cause this issue:
1. Installed 4.3 OTA
2. flashed desamsungnizer knox removal
3. Try to flash 4.1.1 with Odin(failed)
4. reboot phone, stuck at AT&T logo.
5. restore nandroid, reboot, stuck at AT&T logo.

Nabbu said:
I downloaded 4.1.1 from Samsung-Updates.com and then extracted it and tried to flash it in Odin but the program is saying,
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Odin is recognizing the phone and the drivers are installed. The phone, AT&T GS3 I747, is currently running Android 4.3 w/root and custom recovery. The phone is stock otherwise but it is failing for some reason. I'm trying to send it in for warranty for defective volume rockers and headphone jack so I need it stock asap any help is appreciated.
I just found out from another thread that when you try to downgrade from 4.3 to 4.1.X it WILL BRICK. Dang you Samsung!! >=(
Click to expand...
Click to collapse
did yu get it fixed cuz sammy is pulling alot of [email protected] with this 4.3 update for the S3

winosxbuntu said:
did yu get it fixed cuz sammy is pulling alot of [email protected] with this 4.3 update for the S3
Click to expand...
Click to collapse
Unfortunately I haven't found a fix for it and no one else seems to notice it except for the thread in General that says [WARNING].
I would like to know myself if someone knows why the phone boots up but is stuck at the AT&T logo and cannot flash ROMs or Odin files and that Nandroid restores don't fix the "damage".

Nabbu said:
Unfortunately I haven't found a fix for it and no one else seems to notice it except for the thread in General that says [WARNING].
I would like to know myself if someone knows why the phone boots up but is stuck at the AT&T logo and cannot flash ROMs or Odin files and that Nandroid restores don't fix the "damage".
Click to expand...
Click to collapse
if you can access to download mode, follow this link to downgrade to 4.1.2 http://www.androidpit.com/how-to-downgrade-galaxy-s3
or wipe everything and reboot see if that works before downgrading
or WIPE everything 1st get to download mode, flash 4.3 with odin instead since you are on stock and pretty much you are safe to go.....

winosxbuntu said:
if you can access to download mode, follow this link to downgrade to 4.1.2 http://www.androidpit.com/how-to-downgrade-galaxy-s3
or wipe everything and reboot see if that works before downgrading
or WIPE everything 1st get to download mode, flash 4.3 with odin instead since you are on stock and pretty much you are safe to go.....
Click to expand...
Click to collapse
I'll give it a shot and get back with you if my phone is revived. Thanks!

winosxbuntu said:
if you can access to download mode, follow this link to downgrade to 4.1.2 http://www.androidpit.com/how-to-downgrade-galaxy-s3
or wipe everything and reboot see if that works before downgrading
or WIPE everything 1st get to download mode, flash 4.3 with odin instead since you are on stock and pretty much you are safe to go.....
Click to expand...
Click to collapse
You still cannot downgrade from 4.3 and you cannot flash 4.3 because the official software is not yet available, only the OTA patch.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
You still cannot downgrade from 4.3 and you cannot flash 4.3 because the official software is not yet available, only the OTA patch.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Yeah I just figured that out but I was thinking of flashing a 4.3 custom rom or even 4.4 to see if it revives the phone.
I'm trying it today I'll update if it works.

Was able to restore 4.3 from SamMobile with Odin 3.09
I foolishly tried to downgrade from 4.3 OTA to 4.1.1 using Odin and bricked the device. After much testing, I was able to use Odin 3.09 and the 4.3 firmware posted on SamMobile (in my case the Rogers version). All other attempts with other versions led to the "Fail auth" in Odin.
Hope that helps some people who have bricked inadvertently.

sabrinaela said:
I foolishly tried to downgrade from 4.3 OTA to 4.1.1 using Odin and bricked the device. After much testing, I was able to use Odin 3.09 and the 4.3 firmware posted on SamMobile (in my case the Rogers version). All other attempts with other versions led to the "Fail auth" in Odin.
Hope that helps some people who have bricked inadvertently.
Click to expand...
Click to collapse
***UPDATE*** I just realized that if you running the stock 4.3 recovery it wont boot. You have to flash TWRP for it to boot because the stock says to do an emergency firmware recovery in Kies.
Here is where I figured it out how to fix it: http://forum.xda-developers.com/showthread.php?t=2539313
The files I used in this walk through below are in the link above.
I just unbricked my phone, finally, after flashing Slim ROM and Slim Gapps then flashing UCUEMJ2 in Odin 3.07.
Here's how:
1. Download/open Odin 3.07
2. Flash TWRP.tar
3. Download Slim ROM and Slim Gapps and transfer to micro SD card, might need a micro SD card adapter.
4. reboot to recovery and wipe then install Slim ROM/Gapps
5. If successful then good, keep slim rom if you want, if not I suggest you try another 4.3-4.4 ROM and when successful in flashing continue.
6. Open Odin then click PDA and flash UCUEMJ2.md5
7. It will flash everything but aboot.mbn and will say FAIL! (Auth) but it will boot up into stock 4.3.
Here is what the Odin Message box said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img.ext4
<ID:0/012> NON-HLOS.bin
<ID:0/012> persist.img.ext4
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
After this I'm sending it in for warranty and a software reinstall from Samsung so it can be like brand new.
I hope this helps someone.

Nabbu said:
***UPDATE*** I just realized that if you running the stock 4.3 recovery it wont boot. You have to flash TWRP for it to boot because the stock says to do an emergency firmware recovery in Kies.
Here is where I figured it out how to fix it: http://forum.xda-developers.com/showthread.php?t=2539313
The files I used in this walk through below are in the link above.
I just unbricked my phone, finally, after flashing Slim ROM and Slim Gapps then flashing UCUEMJ2 in Odin 3.07.
Here's how:
1. Download/open Odin 3.07
2. Flash TWRP.tar
3. Download Slim ROM and Slim Gapps and transfer to micro SD card, might need a micro SD card adapter.
4. reboot to recovery and wipe then install Slim ROM/Gapps
5. If successful then good, keep slim rom if you want, if not I suggest you try another 4.3-4.4 ROM and when successful in flashing continue.
6. Open Odin then click PDA and flash UCUEMJ2.md5
7. It will flash everything but aboot.mbn and will say FAIL! (Auth) but it will boot up into stock 4.3.
Here is what the Odin Message box said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img.ext4
<ID:0/012> NON-HLOS.bin
<ID:0/012> persist.img.ext4
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
After this I'm sending it in for warranty and a software reinstall from Samsung so it can be like brand new.
I hope this helps someone.
Click to expand...
Click to collapse
Thanks for the log and instructions, this is helpful for anyone that has bricked their phones
Again thanks

Same issue, but my Note hasn't root
Nabbu said:
***UPDATE*** I just realized that if you running the stock 4.3 recovery it wont boot. You have to flash TWRP for it to boot because the stock says to do an emergency firmware recovery in Kies.
Here is where I figured it out how to fix it:
The files I used in this walk through below are in the link above.
I just unbricked my phone, finally, after flashing Slim ROM and Slim Gapps then flashing UCUEMJ2 in Odin 3.07.
Here's how:
1. Download/open Odin 3.07
2. Flash TWRP.tar
3. Download Slim ROM and Slim Gapps and transfer to micro SD card, might need a micro SD card adapter.
4. reboot to recovery and wipe then install Slim ROM/Gapps
5. If successful then good, keep slim rom if you want, if not I suggest you try another 4.3-4.4 ROM and when successful in flashing continue.
6. Open Odin then click PDA and flash UCUEMJ2.md5
7. It will flash everything but aboot.mbn and will say FAIL! (Auth) but it will boot up into stock 4.3.
Here is what the Odin Message box said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> cache.img.ext4
<ID:0/012> NON-HLOS.bin
<ID:0/012> persist.img.ext4
<ID:0/012> recovery.img
<ID:0/012> system.img.ext4
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
After this I'm sending it in for warranty and a software reinstall from Samsung so it can be like brand new.
I hope this helps someone.
Click to expand...
Click to collapse
Same issue, bricked my Note II after trying downgrade. Problem is that my Note wasn't rooted. So i guess trying to install TWRP will not work, right? Any ideas???

mikrax said:
Same issue, bricked my Note II after trying downgrade. Problem is that my Note wasn't rooted. So i guess trying to install TWRP will not work, right? Any ideas???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2549068

Thanks! Unbrick done!
BCSC said:
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
Thanks i just fix my phone installing original firmware 4.3 from sammobile trough Odin. And it worked!

can't flash stock rom on Odin, stacked !! help!!!

Hi all, so I installed the cyanogenmod's new update, I used its in the system update, thought it will be pretty safe just like a stock android update, but then my phone stuck at boot screen. and I really don't have time to mingle with the system right now. I need the phone like 3 hours ago!! i downloaded the stock rom and try to use odin to flash it. then it gives me this error message.
I tried, change the cable, change usb port, change odin version, but nothing works so far. (((
Please help !!
<ID:0/008> 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/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>
<ID:0/008> Complete(Write) operation failed.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.

audit13 said:
You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.
Click to expand...
Click to collapse
Is there a 4.3 rom we can flash with odin? I attempted (stupidly) to flash stock after a CM11 nightly caused a bootloop and would not allow me to enter recovery. All I can do for the moment is enter download mode. Every rom I try to flash I get the same error along with the error on my phone reading:
SW REV CHECK FAIL : Fused 2 > Binary 0
Is there anything I can do?
EDIT: Finally found a fix. I flashed a rom from this thread.
http://forum.xda-developers.com/showthread.php?t=1980683
Just go to their website and download the file for your specific model. After flashing my phone booted up in CM11 (what I previously had installed) but it crashed upon loading the lockscreen. Luckily I could enter recovery mode and do a factory reset. This fixed everything!

[Q] Internal Storage 0MB. Can't flash anything via Odin

Hey everyone.
I'm helping fix my friend's GS3 (SGH-i747). He said that he ran out of battery, and then went into a bootloop. He's running on one of the CM Nightlies from a while back.
We've tried to wipe cache, dalvik cache, factory reset, etc, but nothing works because internal storage fails to mount. I've tried flashing stock via Odin, but with no success. When I flash a recovery however, it says it was successful but when I boot into the phone, I still have the old recovery.
The phone is on TWRP. When I go into "mount", internal storage is shown having 0mb. I cannot click on anything else (data, cache, etc) except system and external sd card (when it is present).
I've tried flashing the CM zip that was on the external SD card but had no success either.
No idea what to do from here. Any help would be appreciated. Thanks!

What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?

!
audit13 said:
What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?
Click to expand...
Click to collapse
I get "NAND WRITE START!!" and then FAIL. It shows that the phone is connected to my PC. I've tried flashing CWM. It says it's successful, but when I boot into recovery, the recovery is still TWRP.

I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097

audit13 said:
I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097
Click to expand...
Click to collapse
I kinda figured that too. I tried flashing a pit file for the sgh-i747 16gb alongside a stock ROM but nothing happened. How should I go about finding one for the phone?
Btw, the internal storage was already at 0mb before I tried flashing a pit file.

Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068

audit13 said:
Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I'd try it but I don't have access to a 16GB or higher SD card. How do I go about getting a pit file for the phone?

Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2

audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Thanks for the link. To be sure, I flash this along with a stock rom right? Is there a specific stock rom that I have to use? I got one from Sam Mobile.

audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Here's the log in Odin:
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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!
<OSM> All threads completed. (succeed 0 / failed 1)
That's what I usually get.

Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.

audit13 said:
Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.
Click to expand...
Click to collapse
Should I flash stock 4.3 then? Unless this phone has Kit Kat (I think the CM version my friend was using is Kit Kat)

The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.

audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Pretty sure that I had put Stock 4.3 at one point. Thanks for the info, I'll try finding a stock 4.3 for Odin and report back.

audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Okay so I tried flashing stock 4.3 and Odin fails at system.img.ext4
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
I got the stock 4.3 from here: http://www.androidayos.com/samsung-galaxy-s3-stock-firmware/
I tried the .pit file included in that as well as the .pit file from the other thread you linked.
Also, the phone was on CM11 4.4.2 before all of this happened. No idea if that makes a difference, but if I recall correctly, the phone did have stock 4.3 at one point.

If you manage to get the thing booted then you might want to run a memory test to see if all the nand is still good

Did you check re-partition?

audit13 said:
Did you check re-partition?
Click to expand...
Click to collapse
Yep

I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660

audit13 said:
I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660
Click to expand...
Click to collapse
Yep, I downloaded that exact one and I get the error. What should I do now?

[Q] Soft Brick Issue

So, I had flashed CM12 and was unable to send text messages.
> Wiped Data / Everything
> Opened ODIN
> Flashed Stock Note 4 Rom
> Fail right away.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any reason why ODIN would be failing to flash back to Stock?
My battery should be at least 60%+, I can enter download mode etc.
I'm just confused on whats going wrong.
Any help would be appreciated it.
Thank you.

Sorry but most likely you can't go back to KitKat. What is your current bootloader version?
You can still restore your CM backup or flash back and check it with Galaxy Tools or Phone Info in Google Play.
If bootloader is OE1 or higher, you might just as well Odin the OJ6 stock tar, wiping as you did, power down, pull battery minimum 30 seconds. Odin with latest 3.10.7 using default options.
BTW, there's usually a messaging fix posted in OP or nearby post by OP in CM threads.
Sent from my SM-N910P using Tapatalk

Not going back to KitKat is fine.
I have seen the fix for sending SMS now for CM12.1, its a shame that it resets itself after a reboot.
I may still stay with CM12.1 for a bit then.
I was able to Flash TWRP Recovery and restore CM12.1 however.
My Bootloader according to Phone Info is: N910PVPU4V0J6
Though, when I leave CM12.1, I am still unsure how to flash back to Stock from here.
I was trying to flash OJ6 Stock before, which was the .tar that was failing to flash.
Thanks your input!

Rooness said:
Not going back to KitKat is fine.
I have seen the fix for sending SMS now for CM12.1, its a shame that it resets itself after a reboot.
I may still stay with CM12.1 for a bit then.
I was able to Flash TWRP Recovery and restore CM12.1 however.
My Bootloader according to Phone Info is: N910PVPU4V0J6
Though, when I leave CM12.1, I am still unsure how to flash back to Stock from here.
I was trying to flash OJ6 Stock before, which was the .tar that was failing to flash.
Thanks your input!
Click to expand...
Click to collapse
I saw ANIE in the fail log you posted. That was the original Sprint Note 4 tar from KitKat.
Do you have the OJ6 full tar?
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
That tar should flash; wipe everything but extSdCard, power down, pull battery 30 seconds and boot into download mode using latest Odin defaults should do it.
Sent from my SM-N910P using Tapatalk

Oh thank you for noticing that!
Swore I was using the proper one.
That is probably why it was failing in the first place.
Downloading now and I'll try in the morning!
Thanks once again, I really appreciate the help.

NP. Verify the md5 against the zip and you should be fine.
Sent from my SM-N910P using Tapatalk

HELP! Galaxy S6 (SM-G920P) (SOLVED)

I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
UPDATE
Was able to flash stock 5.1.1. Even stock firmware, still rebooted every minute even in safe mode.
Ended up flashing stock 5.1.1 and run the same root and also flash twrp to the device. Nonetheless It still reboots every minute, even in safe mode. Below is the recovery.txt and also attached is a photo of where it's stuck because of rebooting. I swear it's something with the cellular...
recovery.txt
Where it stuck due to rebooting every minute
Update 2
The reboot does not occur in twrp or download mode
Update 3
Following Koops second method
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
Click to expand...
Click to collapse
After the stock flash, booting up hangs on the sprint loading screen, dims, then restarts (only first time star. then ting up after flash) goes through setup, but again reboots every minute. The bars at the top sometime show up and sometime don't show up.
Also every reboot, i turned on voice assistant and "system update" is said every time.
At this point im open to any suggestions. If it's not fixed today ill most likely have to go buy an s5 off of amazon.
UPDATE
Got the phone through setup. Baseband and software version is unknown and notification of "Checking device status" is constant. Even after flashing stock 5.1.1. After about a minute, the device status becomes official.
Might try this:
technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
UPDATE
forum.hovatek.com/thread-116.html
Tried using these methods to fix the baseband issue yet still havent fixed it.
UPDATE Finale
For some reason Koops stock firmware didn't work with my phone. I'e uploaded the firmware that did in case others run into the same issue.
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Thank you everyone who helped!
Pictures of device info added below for specific info
Also if it helps I had flashed twrp before anything. I forget specifically if I did anything in twrp that may have helped or not.
http://imgur.com/vUmjfbX
http://imgur.com/CXql8Li
http://imgur.com/2dUJ1om

x1xmadex1x said:
I recently rooted my device. I had uninstalled superSU on accident. I reinstalled and it said it couldn't update the binary. I then prompted to try to run the root again. It failed and reboot except this time my phone now reboots in maybe 1-2 minutes and it seems the cell service wont start either. I tried safe mode and the same issue. It would reboot in 1-3 minutes. I factory reset and wiped the cache several times. Currently downloading stock firmware to try to flash via odin. Any suggestions on fixing it?
Click to expand...
Click to collapse
Flash back to stock via Odin and install twrp then flash THIS version of SuperSU. Unlike the normal version, this one will not install in the system thus lowering the risk of breaking your device(s)

Flash failed
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess

Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.

Still rebooting
I flashed the newest one, the one linked and yet it still reboots after about a minute...cant get past the "Optimizing app" part now...it reboots before it can finish.
It seems like it reboots when trying to get signal....my bars come up but no reception..then just reboots...

Helpful info?
If it helps, I used this to root it:
autoroot.chainfire.eu
samsung SM-G920P zerofltespr zerofltespr universal7420 exynos5 LMY47X.G920PVPU3BOJ7 5.1.1
Like i said i uninstalled super su, reinstalled, than ran that through odin again and it crashed.

x1xmadex1x said:
I tried flashing stock:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
on phone: SW REV. Check Fail Device: 3,Binary: 1
Any input?
Edit Only had "AP" selected in odin...fairly new to droid...how would I go about fixing this hodgepodge of a mess
Click to expand...
Click to collapse
What do you have ticked under options?

1619415 said:
What do you have ticked under options?
Click to expand...
Click to collapse
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked

x1xmadex1x said:
It successfully flashed the samsung Official
sm-G920P
I checked the "AP" and used the latest 5.1.1 previously linked and in options I had auto-reboot and F-Reset Time ticked
Click to expand...
Click to collapse
Try doing it this time without rooting

1619415 said:
Try doing it this time without rooting
Click to expand...
Click to collapse
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on

koop1955 said:
Try this TAR, it is the latest:
https://www.androidfilehost.com/?fid=24343351889231947
OCF, which failed for for, is 5.02 from May. The one above is 5.11 from December.
Click to expand...
Click to collapse
Correct tar and successful, but doesnt solve my problem...still rebooting a minute to being turned on even in safe mode

Updated main

Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...

1619415 said:
Does it do this while in download mode and TWRP (not plugged in)? To me it sounds like maybe the battery is bad...
Click to expand...
Click to collapse
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago

I am having a very similar issue, can't seem to figure out how to fix it.

x1xmadex1x said:
No, it does not happen in twrp or download mode (plugged in or not plugged in)...I just got the galaxy s6 less than a month ago
Click to expand...
Click to collapse
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.

1619415 said:
When I first got mine, it had a battery problem and I brought it to Sprint and they gave me a new one right there for free.... Mine would power off every hour because it couldn't hold a charge.
Click to expand...
Click to collapse
My knox counter is tripped and the galaxy s6 doesnt have a removeable battery...it says it has a charge..i dont think the battery is the issue...

x1xmadex1x said:
Second time flashing stock 5.1.1 which was previously linked thanks to koop1955.
G920PVPU3BOL1_G920PSPT3BOL1_G920PVPU3BOL1_HOME.tar.MD5
-First time was successful but nonetheless have the same issue; Continuous reboot after about a minute being on.
-Second time flashing the 5.1.1 stock with "AP" checked and in options "Auto-reboot" and "F. Reset Time" checked.
Log from odin below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Yet I am still getting the same issue: rebooting about every minute to being turned on
Click to expand...
Click to collapse
After it flashes, boot to STOCK recovery and perform a data wipe/factory reset. My guesses are you have stale leftovers from previous ROM/build and the system can't find what it is looking for and terminates.

Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.

koop1955 said:
Last hope if everything else has failed:
1) Return to Stock via TAR.
2) Reboot to recovery (Stock) and do a factory reset.
See if that fixes it. If not -
1) Return to Stock via TAR.
2) Install TWRP via Odin.
3) From TRWP do an Advanced Wipe - Dalvik Cache, Cache, Data and Internal Storage. (That is as complete a wipe as I know how to do.)
4) Go back to Stock via TAR.
DO NOT USE THE CHAINFIRE SUPERSU ANYMORE. That seems to have caused problems.
Click to expand...
Click to collapse
Thank you, will try that in a little.
What about a "PIT" file?