Develop Bugs

[Official] ICS rom for captivate glide release Sep 7

Hey guys the official rom is out
http://blogs.att.net/consumerblog/story/a7783602
you have to update your device over kies.
Cheers

Got the message just now
" AT&T Free Msg: Samsung Captivate Glide upgrade to Android 4.0 Ice Cream Sandwich is now available! The OS update supports enhanced performance, user interface and other device improvements. Open the link from your PC (not your phone), and follow the instructions: www.samsung.com/us/attcaptivateglide/update "
Sent from my SAMSUNG-SGH-I927 using xda app-developers app

page was working about an hour and now page not found. Maybe they pulled the update? I haven't tried it yet because of the keyboard backlight issue from other posts...and I have no desire to do any rooting/CWM stuff.

Page worked for me just now. It basically just says download kies and let it upgrade.
Does the official rom have the same version number as the leaked one?
Sent from my SAMSUNG-SGH-I927 using xda app-developers app

strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.

There are no bugs, samsung has fixed it all

Does the official version have CarrierIQ?

Nevermind.

R3D X said:
There are no bugs, samsung has fixed it all
Click to expand...
Click to collapse
Oh? That's not what others have reported - the keyboard backlight is supposedly still broken, unsure about tethering or the other problems.

gnahc79 said:
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
Click to expand...
Click to collapse
No backlight on my wife's Glide... She's pissed...

Then root and install the zip

I actually passed on this phone because I was worried it might not get ICS. I'm glad it did all the same. I miss having a hard keyboard.

Sengfeng said:
No backlight on my wife's Glide... She's pissed...
Click to expand...
Click to collapse
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.

gnahc79 said:
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
Click to expand...
Click to collapse
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.

bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own

bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .

gnahc79 said:
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
Click to expand...
Click to collapse
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
Anh56 said:
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
Click to expand...
Click to collapse
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
bakageta said:
To fix the keyboard backlight bug, you'll need the following:
Odin 1.85
Clockworkmod Recovery
The Keyboard Backlight fix The one labeled LH2 is for the official, the one labeled CWM is for the leak. If you're not sure what you're on, go to About Phone, and check the Baseband Version, if it ends in LH2 you're on the official, if it ends in LG9 it's the leak.
Optionally, SuperUser 3.2 RC3 if you'd like root.
First, make sure you have Kies installed, so that you have the correct USB drivers. Download the 4.0.4 .exe file from here. Power off your phone, hold Volume Up and Power to turn it back on. Keep holding them until you get a screen warning you about custom software, and release, then press volume up again to enter download mode. Hook the phone up to your pc and run Odin 1.85. Uncheck "F. Reset Time" and make sure that the only box checked is Auto Reboot, you shouldn't need to change anything else. Click on the PDA button, and load the clockworkmod .md5 file you downloaded, then press the start button and wait for the device to reboot.
This time you'll reboot into recovery. Power the phone off, hold the volume down and power button to turn the phone one. Keep holding them until you see text about entering recovery in the top left, and release. Use the volume keys to navigate and power to select, and go to Install zip from sdcard. Select the keyboard backlight fix zip. Once that's finished, if you'd like to be rooted, repeat the process to flash a zip, and this time select Choose zip from sdcard, selecting the superuser zip you downloaded earlier. Select Yes, and wait for superuser to flash. If you plan on keeping Clockwork Mod Recovery, you should make a backup now. To do so, select Backup and restore, and backup. This will take a bit, just be patient. When you're finished, select reboot system now, and you should be set.
From here, if you rooted you can install something like Titanium Backup, which will use root access to let you remove the various AT&T bloatware.
Click to expand...
Click to collapse

Yeah backlight isn't working sorry, someone on a blog had said so. Very unprofessional of samsung. A rom cooked with cm9 willl have to include the backlight fix

bakageta said:
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
Click to expand...
Click to collapse
:good:
Cool, thanks for the info. Good to know root is not required. I'll still hold off on the update but I'm sure others will apply ICS+backlight fix.

I updated last night, and I can report that after ending any call the phone app reports a hard stop rather than just going away, and that resets your cell connection. And I imagine the keyboard backlight will be fixed very soon. But did these issues exist on the leaked rom in its first release and then programmers modified to get them back?
-Ara
Sent from my SGH-I927 using xda app-developers app

[Q] Blue LED and no screen :(

tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?

Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app

CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?

I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app

Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.

topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?

Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?

Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2

Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings

CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!

Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible

CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.

[Q] Video recording not working in 5.0.1 - force reboots phone

I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!

jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
My stock rom I made doesn't have that problem, my wife records my kidz all the time, no issues... try wiping if you left your data, I always wipe all data before upgrading to any rom...
check my signature or in the Tmobile development thread.. completely stock...

jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
Same issue, searching for it since many days, I hope its not a hardware issue.
I tried custom roms as well as stock roms, but nothing worked. Pls help.

chetancc said:
Same issue, searching for it since many days, I hope its not a hardware issue.
I tried custom roms as well as stock roms, but nothing worked. Pls help.
Click to expand...
Click to collapse
I have the same issue. Wiped the entire phone including internal sdcard, went back to stock firmware but nothing worked. Taking pictures works but as soon as press the record button it freezes and a few seconds later the phone will reboot.

Just to let you guy know what I am sure is going on, this video recording damage has been caused by none other than aosp! if you all have previously installed liquid smooth like I did in 3 separate devices
1.tmo s4
And 2 note 3's (one is tmo and one is sprint) I think it is any asop although each person having this damage to their device should answer if they previously installed aosp and specifically liquid smooth.
I was going to assume this damage was only going to happen on tmo note 3, so I tested it on 2 other phones and sure enough they must be forced to remain running asop (the s4 has candy 5) the sprint note 3 currently has the ever so bugging liquid smooth. I also have tried every clean Odin delete everything known to us layman's on the planet and now I am looking for a NV restore. I already tried so sort of a NV item restore Using the dialer *#9090# then pressing Q and then pressing 0000 then option 2,1,2,3 then all with no change. I read somewhere in the xda's grapevine lol about a flash able zip called "Brick_Loop_FIX_afterRestoringBackup" that starts an built in feature that restores or rebuilds the modem then upon boot restores the NV items. I am assuming they are the same thing. Although, with no thought it will fix anything I will flash the zip tomorrow and let you know. I got a couple things to back up incase whatever may happen capin, unless one of you guys try it first, let me know

Haven't heard from the grapevine what protocol, ims or a static rebuild even does except if your imei is all zeros and your don't have any network or stuck in a boot loop after a nandroiid restore I erpose this will fix those couple thing I have read. Although I assume the dialer hidden menu NV rebuild does not really NV rebuild all like it says it does or the all its referring to is really just the first 2 options that are just a couple basic stuffs or it would have fixed my aosp camera damage. Well never listen to anyone who says aosp is all the rave and how you should try it out lol its blackmail to get you to stay on a bugged out ROM forever! LOL

jidainight said:
I installed the official T-Mobile 5.0.1 update N900TUVUFOB6 via Samsung Kies and rooted via Chainfire. I can take pictures okay but when I try to record videos through the stock Camera app, it freezes then reboots the phone, which happens every time! I've tried to install other camera apps from the Play Store but none of them work for video recording. I suspect it's an api issue. Has anyone run into this or know what the problem is? I've even wiped cache and did a factory reset through Recovery but still the same problem. I really need to be able to record videos on my phone, so if anyone has a solution I would be so grateful!
Click to expand...
Click to collapse
I had this same exact problem and i fixed it finally after hours of research and trial and error. I noticed that my baseband and bootloader was Nb4 even tho i had flashed lollipop, so i ended up flashing stock lollipop using odin from http://forum.xda-developers.com/note-3-tmobile/general/5-0-n900tuvufob6-extracted-stock-t3047672 then after flashing i downloaded the lollipop bootloader and used odin 3.09 to flash that bootloader in BL, and the modem in ap, video camera works now and youtube has been fixed also.

How does one find the bootloader version? I checked and noticed the baseband is in fact Nb4, although looking for the bootloader version I just seen the build is Ob6.

revized said:
How does one find the bootloader version? I checked and noticed the baseband is in fact Nb4, although looking for the bootloader version I just seen the build is Ob6.
Click to expand...
Click to collapse
Try https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
it tells everything including bootloader version

OK thank you, I will check it out. what does the baseband and bootloader need to be? I mean what does yours read so I know what files to search for and load using version 3.09?
BL and AP, what do they need to show exactly?
Thanks a lot for the help, if this fixes the video recorder I will post many places that you fixed the problem and link back to this thread. =)
After looking at my current setup it does make sense according to what you are saying if the current firmware is 0b4
And both the baseband and bootloader are Nb4.
Should they all 3 be ob4?
- never mind my son said I am sweating over nothing, just to make sure they are all ob4. If this works I am going to be able to use my camera again! Thanks again!

revized said:
OK thank you, I will check it out. what does the baseband and bootloader need to be? I mean what does yours read so I know what files to search for and load using version 3.09?
BL and AP, what do they need to show exactly?
Thanks a lot for the help, if this fixes the video recorder I will post many places that you fixed the problem and link back to this thread. =)
After looking at my current setup it does make sense according to what you are saying if the current firmware is 0b4
And both the baseband and bootloader are Nb4.
Should they all 3 be ob4?
- never mind my son said I am sweating over nothing, just to make sure they are all ob4. If this works I am going to be able to use my camera again! Thanks again!
Click to expand...
Click to collapse
yeah cool let me know please if it helps!! this was the main reason i had flashed back to kitkat so many times.

Post Chainfire Root Issues 5.1.1

I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.

Maybe flashing unikernel will help, it can be found here: https://www.androidfilehost.com/?fid=24269982087012055
Just flash it in Odin, if that does not work you may want to try bringing it to where you bought it for warranty.

No luck, unfortunately.

offthatwall said:
No luck, unfortunately.
Click to expand...
Click to collapse
Idk, @koop1955 any suggestions?

1619415 said:
Idk, @koop1955 any suggestions?
Click to expand...
Click to collapse
Posted this in the other thread: http://forum.xda-developers.com/showpost.php?p=64735692&postcount=19
That is all that I have for you.

offthatwall said:
I attempted to root my phone using the Chainfire Auto-root method today and somehow managed to use the 925p edge MD5 file instead of 920p. This caused a few issues, the X-axis was inverted, no service, and a continual automatic reboot after about 30-60 seconds of the phone being on. In an attempt to fix it, I have tried a few things. in many combinations. I have reflashed the stock tar file, cleared cache, factory reset, and flashed the PIT file found in post 12 of this thread http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325/page3. Unfortunately all attempts have been for fruitless. Obviously the first issue to be tackled is the constant rebooting. Any help would be appreciated.
Click to expand...
Click to collapse
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!

x1xmadex1x said:
Koop's stock firmware didn't fix mine for some reason either...heres the stock version that fixed mine
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Hope it helps!
Click to expand...
Click to collapse
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?

koop1955 said:
The firmware posted above is OJ7, which seems to be an earlier version than the OL1 firmware. I have no idea why OJ7 would work for you when OL1 wouldn't. (Unless you got a bad download of OL1, which is why I recommend checking MD5.)
If you are still on OJ7, can you try system update and see if that takes you to OL1?
Click to expand...
Click to collapse
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed

x1xmadex1x said:
I have already re-rooted my device and installed twrp...it wont let me install a system update due to custom and not official...Also I downloaded the OL1 three occasions..and MD5 passed[/Q
Im have the constant reboot now. Im gonna try another pb6 6.0.1 tar file only one ive tried was the sprint worker one said revo in in it. That didnt not fix my constant rebooting issue. So far any rom even after odin stock still rebooting every 2 minutes.
Click to expand...
Click to collapse

will get that logcat
Saafir said:
Note the time and grab a logcat.
Ok i left the phone at home but i did look at the log cat about the first ten lines all had emmc in them im not quite sure. Well I cant read it lol. when i get home il flash twrp and restore a back up let reboot a few times get a log cat and post it will twrps log cat work? If im lucky i might get a app installed to do it. I no longer got adb and fastboot on my computer but will download if needed.
im waiting for a replacement to get to the sprint store. i flashed stock and took it in rebooting sprint guy tried factory resetting it and clearing cache which got it stuck in the pre load starting or optimizing apps before itd finish it it would reboot and if i kept going id beable get to start up settings thats it. now i can flash twrp still it does restores my back ups and after that itl boot the system i can uninstall or install something or what not maybe 1 min after im able to get into it it reboot. only wifi connects though.
Again i had about all roms we got on sprint forum on that phone worked awesome loved it til the time i restored the efs on 6.0.1 with a twrp thats a unofficial build modded to work on 920p.
Click to expand...
Click to collapse

Sounds good thanks man.

Seems as maybe a somewhat common issue unfortunately thats happening for s6 as well as sprint note 5 as there are a few threads regarding the same issue. Theres a thread for s6 on this issue and on 2nd page appears as if someone found a fix having something to do with letting it die completely etc.. http://forum.xda-developers.com/sprint-galaxy-s6/help/constant-rebooting-t3287213

I figured my rebooting issue was corrupted data becausr i was transferring from phone to pc to phone and no md5 check. Though now i will use it. Good luck

N910P - Please Help - Tried to root and failed No Bootloader found?

I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.

JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!

Once you get phone back on stock. I'll show how to root!

Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.

SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!

I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.

JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.

Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.

meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light