https://support.t-mobile.com/docs/DOC-27648
Android Security Updates
Phone Samsung GALAXY Note3
Model SM-N900T
PDA Version N900TUVSFPL1
CSC Version N900TTMBFPL1
PHONE Version N900TUVSFPL1
Region TMB
Country USA (T-Mobile)
Build Date 12.12.2016
Changelist 6005498
OS Lollipop
OS Version 5.0
If anyone tried using CF-root successfully, leave a confirmation below.
I'm interested too if anyone flashes please report back asap. Doesn't seem like much seeing as the rom is still 5.0 not 5.1 or 6 so more than likely its just 300 mb of "security updates".
Just an update: the new PL1 firmware can be rooted by CF-auto-root.
One more update: the android security patch level is still 2016-09-01, the same as the SPH3 firmware. Don't know why they say this is an "android security update"in the description.
I thought the android security patch level should be 2016-12-01 since it was built on 2016-12-12.
i couldnt ge the cf-root to work on mine. it says theres a dev error. is there a newer version to use?
bb031577 said:
i couldnt ge the cf-root to work on mine. it says theres a dev error. is there a newer version to use?
Click to expand...
Click to collapse
Odin flash the cf-root tar file.
googlephone said:
Odin flash the cf-root tar file.
Click to expand...
Click to collapse
I did that 3times and it keeps giving me the same error message. I think I'm using the wrong tar file. I'm using the one for n900TTMBFOB6. Is there a different one for N900TTMBFPL1?
bb031577 said:
I did that 3times and it keeps giving me the same error message. I think I'm using the wrong tar file. I'm using the one for n900TTMBFOB6. Is there a different one for N900TTMBFPL1?
Click to expand...
Click to collapse
Should be the same.
I downloaded here:https://download.chainfire.eu/354/CF-Root
Unzip the file and Odin flash the tar.md5 file only, not the zip file.
THANK YOU VERY MUCH IT WORKED PERFECTLY. It must have been the file i downloaded from before.
Baseband not updaing
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Did anyone try flashing roms through TWRP? if so what do you guys use?
macster2075 said:
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Click to expand...
Click to collapse
The baseband should be PL1 but the android security patch level should still be 2016-09-01.
macster2075 said:
Hi guys..
I have upgraded to the N900TUVSFPL1 update.. but I noticed the baseband still says N900TUVSFPH3 and the Android Security Patch Level says 2016-09-01... is this normal?
the Build number does say N900TUVSFPL1.
Click to expand...
Click to collapse
I think that you have to power off the phone and boot into download mode from the power off state. Otherwise, the bootloader and baseband won't update.
frequentc said:
I think that you have to power off the phone and boot into download mode from the power off state. Otherwise, the bootloader and baseband won't update.
Click to expand...
Click to collapse
In order to install the update, I had to get into download mode.
macster2075 said:
In order to install the update, I had to get into download mode.
Click to expand...
Click to collapse
Right.. but it makes a difference if you reboot into download mode (while the phone's still on) or have the phone turned off and then boot directly into download mode (volume-down + home + power).
frequentc said:
Right.. but it makes a difference if you reboot into download mode (while the phone's still on) or have to phone turned off and then boot directly into download mode (volume-down + home + power).
Click to expand...
Click to collapse
Yes.. I had to do that in order to re-root using CF-Root and also to flash the recovery.
Is this ROM based on Android 5.1.1 like others are speculating? If this is just 5.0, I'm saying "Screw Touchwiz", and staying on my AOSP Nougat...
AndroidHacker99 said:
Is this ROM based on Android 5.1.1 like others are speculating? If this is just 5.0, I'm saying "Screw Touchwiz", and staying on my AOSP Nougat...
Click to expand...
Click to collapse
Still 5.0
Is it possible to take only the most update modem (CP) from this?
I am looking to flash the latest modem for Tmo US Note 3.
Maybe flashing via Odin in the CP button?
elyranon said:
Did anyone try flashing roms through TWRP? if so what do you guys use?
Click to expand...
Click to collapse
FlashFIre. Many older posts talk MOP, TWRP, etc. At least with this hardware and firmware, FlashFire is all I use. (Much gratitude to Chainfire.)
hapa8o8 said:
Is it possible to take only the most update modem (CP) from this?
I am looking to flash the latest modem for Tmo US Note 3.
Maybe flashing via Odin in the CP button?
Click to expand...
Click to collapse
Code:
# Install Heimdall and print pit
sudo apt install heimdall
heimdall detect
heimdall print-pit --no-reboot > pit.txt
# Extract binaries from firmware package
head -z -n -1 N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar.md5 > N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar
tar -xvf N900TUVSFPL1_N900TTMBFPL1_N900TUVSFPL1_HOME.tar
Lastly, review the pit file and pick the partitions/files you want to flash. Use the tool you're most comfortable with to do the job.
Many posts refer to the necessity of bootloaders and modems being compatible. So I have not (and would not) flash just the modem. Er, that is unless someone else already did it and reported success.
(PS. Wish *I* could walk out my door and do the Haiku Stairs, a bucket list item.)
Related
You are flashing the below at YOUR OWN RISK
This is only for the Euro version, at&t version, T-mobile version or any other GSM version of the Tab. this is NOT for any CDMA version.
This is a new Tab firmware that just leaked out (P1000XXJM6)
So far the know pros are:
1) THE BROWSER IF FINALLY FIXED! it is very smooth even with flash. i am very impressed.
2) Users are reporting new widgets.
3) The drop down drawer is smoother.
4) New readers hub
5) tweaked email client
6) better camera focus?
7) ROM feels very smooth.
Update 11/29/2010
This is an updated package which should be safer to flash via Odin.
All credits are going to Richthofen who compiled this package for us.
As it seems that original package posted in this thread was not intended to be flashed via Odin.
Samsung has introduced a new FW programming method which also supports the upcoming phones. I don´t know if it is already supported by the newest Kies version.
The new format is basically the same as Odin only smarter with a few tricks and more stable.
Richthofen has prepared a new package for us that is flashable via Odin and should work much better with less problems.
Below are the download links and instructions for everything you need to flash P1000XXJM6.
1) Download the the file HERE and extract the it
2) Inside the ZIP you will find Odin 1.7 + PIT file + PDA +Modem + CSC files.
3) Open Odin, select the PIT file + PDA + Modem + CSC into their respective places.
4) Make sure repartition is CHECKED.
5) put the phone in download mode and connect it to your computer. start flashing.
6) The device will reboot. If you are getting tons of FC's on boot, reboot into recovery and do a factory reset.
Done.
** You can root using SuperOneClick method. Other methods do not work at this time.
**If you are on at&t and using the at&t model, please reflash the Bell modem to gain 850Mhz back.
clubtech said:
Please be advised that i have not yet tested this firmware so i don't know if it works and i am not responsible if it bricks your Tab!!!
The brave ones are welcome to try and report back.
It was originally labeled as P1000XXJM9 on the Samsung FUS server however it looks like it is P1000XXJM6.
Download: http://www.multiupload.com/OO6CWYBQYN
Release date: 11/25/2010
Flash: latest Odin with no repartition (as this does not look like it is a full flash). No PIT file needed as it is not a full flash.
Click to expand...
Click to collapse
Taking one for the team here, flash failed, Tab totally unresponsive.
Sorry it failed.
can u detail the below please:
- what is your tab model?
- are u still able to into download mode to flash to a working firmware ?
- are u sure you did not select repartition when flashing?
clubtech said:
Sorry it failed.
can u detail the below please:
- what is your tab model?
Bell Tab running P1000XXJK5
- are u still able to into download mode to flash to a working firmware ?
Unable to boot, access recovery or download mode, screen black, computer and Odin do not recognize cable connection.
- are u sure you did not select repartition when flashing?
Click to expand...
Click to collapse
Did not repartition.
just flashed, browser MUCH better , smooth scrolling on engadget .
You need to flash dbdata from this post:
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
Can u detail exactly how you flashed this?
Which Odin version ?
Repartirion or not?
Which tab model do you have ?
also new widgets, new notes in browser
flashed with odin 1.7 , no repartition. After flash tab reboot in download mode again.
Flashed again but only dbdata .
cezarc1 said:
flashed with odin 1.7 , no repartition. After flash tab reboot in download mode again.
Flashed again but only dbdata .
Click to expand...
Click to collapse
Thanks.
I wonder why user above you bricked then.
Which version of the tab are u using? The euro one or something else?
euro version
Gonna try flashing this firmware
So just to confirm, it's only partial yes?
Thanks
risq said:
Gonna try flashing this firmware
So just to confirm, it's only partial yes?
Thanks
Click to expand...
Click to collapse
Correct. Let us know the resutls and exactly how you flashed and Odin version used and your tab version.
cezarc1 said:
just flashed, browser MUCH better , smooth scrolling on engadget .
You need to flash dbdata from this post:
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
Click to expand...
Click to collapse
can you run acid3 test, is the result still 93/100? Thanks.
http://acid3.acidtests.org/
Sent from my GT-P1000 using Tapatalk
Ok,
Got the latest version installed by flashing the latest update with odin, then flashing dbdata.rfs afterwards....
only thing is, it's now causing launcherpro and other apps to force close, so I'm going to re-flash JJ4 / JK5 clean then re-apply this update.
antz88c said:
can you run acid3 test, is the result still 93/100? Thanks.
http://acid3.acidtests.org/
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Still 93/100
im guessing its not from samfirmware?
JM is kinda weird since on samsung code JM means J = 2010 and M = 13th month which is ......
K is november and L should be the latest one >.< (december)
where did you get this one anyway?
Ok - got it back to life....re-flashing now
cezarc1 said:
Still 93/100
Click to expand...
Click to collapse
But is the browser really smoother ? Even after you restored all your apps?
clubtech said:
It was originally labeled as P1000XXJM9 on the Samsung FUS server however it looks like it is P1000XXJM6.
Click to expand...
Click to collapse
Check this post for more info about recent releases:
http://forum.xda-developers.com/showpost.php?p=9422970&postcount=4
"JM" is weird...the dates don't make sense.
risq said:
Ok - got it back to life....re-flashing now
Click to expand...
Click to collapse
How did you get it back to life?
Sent from my SGH-T849 using XDA App
Stock 4.4.4 FNI3 Galaxy S4 M919N/JflteMetroPCS
Stock
Rooted
BusyBox
Knoxless
CIQLess
Deodexed
ArchiInit'd support
(software level init'd support. Doesnt conflict with kernel level support found in custom kernels)
ro.secure.storage set to false
Everything else completely untouched.
DOWNLOAD HERE
Stock FNI3 kernel set to permissive
DOWNLOAD HERE
Modems
Modem.bin
NON-HLOS.bin
Modem.bin And NON-HLOS.bin
Stock Firmware
HERE
Odin 3.09
HERE
Issues
Shouldn't be any.
XDA:DevDB Information
MetroPCS 4.4.4 FNI3 Galaxy S4 Rooted_Deodex'd_Knoxless, ROM for the T-Mobile Samsung Galaxy S 4
Contributors
ShinySide
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2014-10-19
Last Updated 2014-10-19
No first's. ???
Pp.
Is the "Mobile hotspot" and "data" on the Notification panel (when you swipe your finger from the top of the phone) ???
Or is it the same as the Tmobile version, Mobile hotspot is on a separate app in the app drawer, and mobile data can only be accessed under settings menu?
Thanks
xdm9mm said:
Is the "Mobile hotspot" and "data" on the Notification panel (when you swipe your finger from the top of the phone) ???
Or is it the same as the Tmobile version, Mobile hotspot is on a separate app in the app drawer, and mobile data can only be accessed under settings menu?
Thanks
Click to expand...
Click to collapse
No. But can be easily added to both.
Much thanks!!!That was fast!
http://www.youtube.com/watch?v=4e-TXWIf_DE
Now how about you upload HispAsian v4?
ShinySide said:
No. But can be easily added to both.
Click to expand...
Click to collapse
thanks.. will try it later
everything seemed to work, but after flashing the Modem.bin And NON-HLOS.bin I no longer have any sound. Anyone else having a similar issue? I think it was really the non-hlos.bin that screwed things up. Any way to undo what it did? Any help would be appreciated, thanks.
arocker said:
Much thanks!!!That was fast!
http://www.youtube.com/watch?v=4e-TXWIf_DE
Now how about you upload HispAsian v4?
Click to expand...
Click to collapse
Haha tomorrow or Saturday. Drove 400 and something miles today for work and last thing I'm doing is sitting down and messing with Android stuff
Caloba said:
everything seemed to work, but after flashing the Modem.bin And NON-HLOS.bin I no longer have any sound. Anyone else having a similar issue? I think it was really the non-hlos.bin that screwed things up. Any way to undo what it did? Any help would be appreciated, thanks.
Click to expand...
Click to collapse
The nonhlos.bin version must match the bootloader version. For example, if you have the NB7 bootloader, you need to have the NB7 nonhlos.bin. Flash the proper nonhlos.bin.
arocker said:
The nonhlos.bin version must match the bootloader version. For example, if you have the NB7 bootloader, you need to have the NB7 nonhlos.bin. Flash the proper nonhlos.bin.
Click to expand...
Click to collapse
Thanks for the reply. How can I find out what bootloader I have? I pretty much had rooted my MetroPCS S4 shortly after I bought it back in July of 2013. It was still using Jelly bean 4.2.2. with older firmware M919NUVUAMF2. I hope that info helps. Would I need to find a different nonhlos.bin file or update/upgrade my bootloader? I'm really SOL right now cuz I can't make phone calls. At least I can still recieve texts. Thanks again for any help?
Caloba said:
Thanks for the reply. How can I find out what bootloader I have? I pretty much had rooted my MetroPCS S4 shortly after I bought it back in July of 2013. It was still using Jelly bean 4.2.2. with older firmware M919NUVUAMF2. I hope that info helps. Would I need to find a different nonhlos.bin file or update/upgrade my bootloader? I'm really SOL right now cuz I can't make phone calls. At least I can still recieve texts. Thanks again for any help?
Click to expand...
Click to collapse
July of 2013 means your warranty is up so tripping knox would be no issue. I'd completely update with the firmware then you can not worry about stupid mix match problems
ShinySide said:
July of 2013 means your warranty is up so tripping knox would be no issue. I'd completely update with the firmware then you can not worry about stupid mix match problems
Click to expand...
Click to collapse
One last question. I just download the huge M919NUVUFNI3_M919NTMBFNI3_M919NUVUFNI3_HOME.tar.md5 stock firmware file. In which slot do I put that in? I'm using Odin 3.09. The slots are labled: PIT, BL, AP, CP and CSC. Thanks again.
Caloba said:
One last question. I just download the huge M919NUVUFNI3_M919NTMBFNI3_M919NUVUFNI3_HOME.tar.md5 stock firmware file. In which slot do I put that in? I'm using Odin 3.09. The slots are labled: PIT, BL, AP, CP and CSC. Thanks again.
Click to expand...
Click to collapse
AP. Uncheck auto reboot, flash it, when done pull battery, back to download mode and flash it again and reboot. Just to be 100. Sometimes bootloader and/or modems have a issue writing to the device.
Caloba said:
Thanks for the reply. How can I find out what bootloader I have? I pretty much had rooted my MetroPCS S4 shortly after I bought it back in July of 2013. It was still using Jelly bean 4.2.2. with older firmware M919NUVUAMF2. I hope that info helps. Would I need to find a different nonhlos.bin file or update/upgrade my bootloader? I'm really SOL right now cuz I can't make phone calls. At least I can still recieve texts. Thanks again for any help?
Click to expand...
Click to collapse
Edit: Looks like you're flashing the firmware...good choice.
If you've never flashed a different firmware then you would need the nonhlos.bin from the MF2 firmware. You can find that firmware at this link, under firmware...
http://androidforums.com/metropcs-g...cial-metropcs-s4-root-information-thread.html
Alternately you could just flash the new NI3 firmware like shiny suggested. It would be easier altogether. Your manufacturer warranty has expired so updating the bootloader is no longer an issue.
arocker said:
Edit: Looks like your flashing the firmware...good choice.
If you've never flashed a different firmware then you would need the nonhlos.bin from the MF2 firmware. You can find that firmware at this link, under firmware...
http://androidforums.com/metropcs-g...cial-metropcs-s4-root-information-thread.html
Alternately you could just flash the new NI3 firmware like shiny suggested. It would be easier altogether. Your manufacturer warranty has expired so updating the bootloader is no longer an issue.
Click to expand...
Click to collapse
Everything went off smoothly, thanks guys. I'm now on the latest stock MetroPCS 4.4.4 firmware.
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
arocker said:
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
Click to expand...
Click to collapse
Thanks again Arocker, worked like a charm, I'm rooted.
You are welcome
WWould I be able to use Mobil Odin pro to flash this....
laseroxstar said:
WWould I be able to use Mobil Odin pro to flash this....
Click to expand...
Click to collapse
The firmware? No. Mobile odin doesn't flash bootloaders.
Modems should be able to yet I've never used it
Here's the update.zip for the newest 5.1.1 leak build number D0F8...
https://mega.co.nz/#!iIFSRA5C!Q9KWmi3vdNc_lRN2c4RKA8GFzOsT0L8FYgl1yMg7-L8
http://pasteboard.co/1AOfi4By.png
You can sideload this file via the stock recovery
Code:
adb sideload update.zip
you must use lastest adb binary or it will fail.
Aaaaannd if you find any bugs you can downgrade back to CF6 5.1.1 no problem. I fully tested it Sorry Aou 100%
So, you're saying that the update will only be available for OCG users, not OF6? So, then, it's only an update for OCG -> OF8 ?
Weird.
Edit: NVM, I see what you're doing here. You're taking advantage of the idea that the phone will unpack this update.zip if it's already expecting to try to unpack and install the update.zip for OF6... clever.
Edit2: I'm thinking, perhaps we could create an OCG downgrade TWRP-flashable .zip that forcefully writes the OCG system & kernel to the device. It should be able to to, but I'm not sure that the OCG software would boot on the new OF6 bootloader...
Edit3: @Sunderwear - have you heard anything whether or not this leak includes a new sboot.bin (bootloader) ?
Edit4: Assuming the update.zip is signed properly, is there any reason we couldn't attempt to flash it using the factory/stock "e3" recovery?
Aou said:
So, you're saying that the update will only be available for OCG users, not OF6? So, then, it's only an update for OCG -> OF8 ?
Weird.
Edit: NVM, I see what you're doing here. You're taking advantage of the idea that the phone will unpack this update.zip if it's already expecting to try to unpack and install the update.zip for OF6... clever.
Edit2: I'm thinking, perhaps we could create an OCG downgrade TWRP-flashable .zip that forcefully writes the OCG system & kernel to the device. It should be able to to, but I'm not sure that the OCG software would boot on the new OF6 bootloader...
Edit3: @Sunderwear - have you heard anything whether or not this leak includes a new sboot.bin (bootloader) ?
Edit4: Assuming the update.zip is signed properly, is there any reason we couldn't attempt to flash it using the factory/stock "e3" recovery?
Click to expand...
Click to collapse
yes it comes with a new sboot.bin. and it wont flash the way it is right now because needs to be unpacked first.
here's a link for for what i was able to extract however is not the full thing .
https://mega.co.nz/#!HQlUyaBT!lwlFTQAQzmLZZN1ous8Q6vjoABBb5vMSeTdZx7HmcNg
Sunderwear said:
yes it comes with a new sboot.bin. and it wont flash the way it is right now because needs to be unpacked first.
here's a link for for what i was able to extract however is not the full thing .
https://mega.co.nz/#!HQlUyaBT!lwlFTQAQzmLZZN1ous8Q6vjoABBb5vMSeTdZx7HmcNg
Click to expand...
Click to collapse
Awesome. I took a look at the updater-script.
Best I can tell, it does update the bootloader (bot BOTA0 and BOTA1 with sboot.bin and cm.bin respectively). But it doesn't look like they're updating the revision number, because at the end, they update the system to SYSMAGIC002:
Code:
write_string_partition("/dev/block/platform/15570000.ufs/by-name/SYSTEM", 2000, "SYSMAGIC002", 11) || abort("fail to write secure_sysmgic in system.");
Noteworthy that this appeas to be exclusively an update from OF6 -> OF8, according to the stuff at the top.
Code:
abort("Package expects build fingerprint of samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2COF6:user/release-keys or samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2DOF8:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Edit: The sboot.bin seems to also saying stuff about SYSMAGIC002. And, for the heck of it, I tried to adb-sideload the update.zip from OF6 3e recovery. It fails the signature check.
Aou said:
Awesome. I took a look at the updater-script.
Best I can tell, it does update the bootloader (bot BOTA0 and BOTA1 with sboot.bin and cm.bin respectively). But it doesn't look like they're updating the revision number, because at the end, they update the system to SYSMAGIC002:
Code:
write_string_partition("/dev/block/platform/15570000.ufs/by-name/SYSTEM", 2000, "SYSMAGIC002", 11) || abort("fail to write secure_sysmgic in system.");
Noteworthy that this appeas to be exclusively an update from OF6 -> OF8, according to the stuff at the top.
Code:
abort("Package expects build fingerprint of samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2COF6:user/release-keys or samsung/zeroltetmo/zeroltetmo:5.1.1/LMY47X/G925TUVU2DOF8:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Edit: The sboot.bin seems to also saying stuff about SYSMAGIC002. And, for the heck of it, I tried to adb-sideload the update.zip from OF6 3e recovery. It fails the signature check.
Click to expand...
Click to collapse
yes...need someone with 5.0.2 to try to unpack it..maybe i'll get one by the shop tomorrow.
Sunderwear said:
yes...need someone with 5.0.2 to try to unpack it..maybe i'll get one by the shop tomorrow.
Click to expand...
Click to collapse
Cool, let us know!
- Also, for what it's worth, I created an "OCG downgrade" .zip, which does write the partitions just fine... But the device sticks on the boot logo. Kinda figured it wouldn't work.
Aou said:
Cool, let us know!
- Also, for what it's worth, I created an "OCG downgrade" .zip, which does write the partitions just fine... But the device sticks on the boot logo. Kinda figured it wouldn't work.
Click to expand...
Click to collapse
I got a s6 edge today and yes my trick worked..uploading unpacked update.zip right now..
Sunderwear said:
I got a s6 edge today and yes my trick worked..uploading unpacked update.zip right now..
Click to expand...
Click to collapse
What its new? any change?
fabioplata said:
What its new? any change?
Click to expand...
Click to collapse
you can find out for yourself later.. stability fixes etc..issues with the first 5.1.1 update.
Sunderwear said:
you can find out for yourself later.. stability fixes etc..issues with the first 5.1.1 update.
Click to expand...
Click to collapse
Is multiuser back ?for some reason they removed it from the offical from the last leak
And also is the ram isuue for multasking finally fixed?
frr1 said:
Is multiuser back ?for some reason they removed it from the offical from the last leak
And also is the ram isuue for multasking finally fixed?
Click to expand...
Click to collapse
I just upgraded the phone so cant fully judge..Multi user is still disabled but it's something that can be enabled with any CSC feature changer.
http://pasteboard.co/1AOfi4By.png
Sunderwear said:
I just upgraded the phone so cant fully judge..Multi user is still disabled but it's something that can be enabled with any CSC feature changer.
http://pasteboard.co/1AOfi4By.png
Click to expand...
Click to collapse
Oh ok let us know of mutitaking is better with the new update
Also where do i find a CSC changer?
The screen shot shows DOF8, but the thread title is COF8...?
flarbear said:
The screen shot shows DOF8, but the thread title is COF8...?
Click to expand...
Click to collapse
fixed. Typo...10chars
Raw support in oem camera app?
Sent from my SM-G925T using Tapatalk
@Sunderwear is it a coincidence you always manage to get edge leaks but something bad happens when it comes to the flat
mikeyinid said:
@Sunderwear is it a coincidence you always manage to get edge leaks but something bad happens when it comes to the flat
Click to expand...
Click to collapse
Lol
Sent from my SM-G925T using XDA Free mobile app
mikeyinid said:
@Sunderwear is it a coincidence you always manage to get edge leaks but something bad happens when it comes to the flat
Click to expand...
Click to collapse
Because this time i was prepared..same thing happened with the regular s6 lol .
I'm currently working on a TWRP-flashable OF8 ROM.
I won't bother with the Kernel right away, though. Until the source for OF8 shows up on Samsung's website we won't have root on OF8.
Aou said:
I'm currently working on a TWRP-flashable OF8 ROM.
I won't bother with the Kernel right away, though. Until the source for OF8 shows up on Samsung's website we won't have root on OF8.
Click to expand...
Click to collapse
I havent tested but it should boot with the current custom kernels.
This firmware is for Sprint Galaxy S6 [G920P] phones ONLY
This will not damage any of your stored files or app settings
WARNING! Do not unplug your phone once you have started
Samsung Sprint Galaxy S6 BOL1 Android 5.1.1 Stock Rom
Download Firmware
https://www.dropbox.com/s/n0p0rmi2d873h1d/G920PVPU3BOL1_SPT3BOL1_SPR_Sprint_USA_5.1.1.zip?dl=0
Alternate Firmware Download Mirror
https://www.androidfilehost.com/?fid=24052804347838029
Alternate Firmware Download Mirror
https://www.androidfilehost.com/?fid=24345424848486725
Download Odin
http://odindownload.com/SamsungOdin/#.Vr3P1_IrKJI
1. Put your phone in download mode by turning it off,
Press and hold Volume Down+Power+Home Button
And then pressing Volume Up: Continue
Phone should then say Downloading...
Do not turn off target
2. Unzip Odin.exe to your desktop
Open Odin
After connecting your phone while in download mode to your desktop
Odin should say Added!
Leave the options alone
*DO NOT SELECT REPARTITION!
3. Unzip the G920PVP firmware
Using Odin click AP and select the firmware .tar file
Click Start
Wait a few moments until Odin says SUCCESS!:highfive:
DONE! Then your phone should reboot and you'll see the Android icon/Boot Logo sequence
Check your phone for any updates while you are on this fresh new install to be on the latest firmware
BONUS! In case you get stuck in download mode
Hold Volume Up+Down Home+Power buttons
Your phone should exit and reboot
Thank you for this! Very much appreciated.
You're welcome, new firmware mirror up
Thanks for this thread. I have MM stock, but the hotspot now requires a reboot to get it working. Can I use this method to flash back to Lollipop? I saw a thread saying you cannot flash anything older than 5.1.1. That was an older thread, and basically he was told he can't flash 5.0.2 back on his S6 because he already had 5.1.1.
badkarmah187 said:
Thanks for this thread. I have MM stock, but the hotspot now requires a reboot to get it working. Can I use this method to flash back to Lollipop? I saw a thread saying you cannot flash anything older than 5.1.1. That was an older thread, and basically he was told he can't flash 5.0.2 back on his S6 because he already had 5.1.1.
Click to expand...
Click to collapse
Hotspot should be fixed in my next ROM
badkarmah187 said:
Thanks for this thread. I have MM stock, but the hotspot now requires a reboot to get it working. Can I use this method to flash back to Lollipop? I saw a thread saying you cannot flash anything older than 5.1.1. That was an older thread, and basically he was told he can't flash 5.0.2 back on his S6 because he already had 5.1.1.
Click to expand...
Click to collapse
Well, I flashed my stock Note 5 rom over to the MM leak and now I'm stuck with it till the official release is out and I can flash back to stock and receive the latest official updates as they come out.
What happened was I wiped the drive and then flashed the lower # official roms and all it did was bootloop or just wouldn't flash the version at all and would just give me an error while trying to flash.
probleme
mykehdoom said:
Thank you for this! Very much appreciated.
Click to expand...
Click to collapse
my phone stiil blocked on recovery mode after mm 8.0 download with dm-verity verification failed. Chek drk first i can try this ?
I flashed backed to 5.1.1, I left my phone sitting with wifi enabled, sprint downloaded the 6.0.1 update and gave me no choice but to install it again. I had no way to back out of it. I put 5.1.1 on my phone twice today and it keeps sending me to MM. Is there a way to flash back to 5.1.1 and disable OTA without rooting the phone..? if not then you really can't go back because Sprint will force the update to your phone.
i guess there should be an option in setting/update for you to uncheck the "update".
racimrl said:
my phone stiil blocked on recovery mode after mm 8.0 download with dm-verity verification failed. Chek drk first i can try this ?
Click to expand...
Click to collapse
The DRK error means that someone changed your phone's IMEI but did it improperly. Now the phone will not even turn on past the Samsung screen. I run phone a business and offer a service to fix it - PM me if interested
MindTrix said:
I flashed backed to 5.1.1, I left my phone sitting with wifi enabled, sprint downloaded the 6.0.1 update and gave me no choice but to install it again. I had no way to back out of it. I put 5.1.1 on my phone twice today and it keeps sending me to MM. Is there a way to flash back to 5.1.1 and disable OTA without rooting the phone..? if not then you really can't go back because Sprint will force the update to your phone.
Click to expand...
Click to collapse
wait a minute... you can roll back a stock unrooted rom without having to root??
I need tether. I have to have tether. They forced the Marshmallow update without my permission. Complete BS. Now I have no tether.
jerry43812 said:
wait a minute... you can roll back a stock unrooted rom without having to root??
I need tether. I have to have tether. They forced the Marshmallow update without my permission. Complete BS. Now I have no tether.
Click to expand...
Click to collapse
Rolling back is as simple as using ODIN and flash the stock rom, I rooted 6.0.1 and its starting to grow on me but I can flash back to stock 5.1.1 even if I was not rooted, I only root because like you I need tether and so far this was the only way on 6.0.1 MM
Man oh man, I thought I broke my charging port the day after I rooted. I was about to cry myself to sleep for the next 2 months.
Going to MM
Should I use this to go back to stock and then take the OTA to get to the latest firmware? Or would it be a better idea to download the current firmware from Sammobile?
guitarpager said:
Should I use this to go back to stock and then take the OTA to get to the latest firmware? Or would it be a better idea to download the current firmware from Sammobile?
Click to expand...
Click to collapse
Don't go the SAMMOBILE page, I have linked to a much faster site: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
hey guys i am from india and i have been using unlocked sprint s6 from a month and everything was perfect till i flashed the marshmallow firmware , i have lost the sim signal ,, need help plz.. anybody know how to get back the signal....
dksahil said:
hey guys i am from india and i have been using unlocked sprint s6 from a month and everything was perfect till i flashed the marshmallow firmware , i have lost the sim signal ,, need help plz.. anybody know how to get back the signal....
Click to expand...
Click to collapse
This guide should help you: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
I can't say if it actually works as I live in the US and my phone is not unlocked, but it seems to have helped others.
Here a link for the latest stock TAR files: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Tried to use this file and it says "SW REV CHECK FAIL. DEVICE 4 BINARY 3"
Xabring said:
Tried to use this file and it says "SW REV CHECK FAIL. DEVICE 4 BINARY 3"
Click to expand...
Click to collapse
This is a very old thread. That error means that your phone has updated to a software version of 6 or 7 and you can't revert back to 5.
Xabring said:
Tried to use this file and it says "SW REV CHECK FAIL. DEVICE 4 BINARY 3"
Click to expand...
Click to collapse
koop1955 said:
This is a very old thread. That error means that your phone has updated to a software version of 6 or 7 and you can't revert back to 5.
Click to expand...
Click to collapse
More accurately, it means that your bootloader version is 4, and you can't flash anything lower.
But no, you can't go back to Android 5
Some people just post info and never post links . I had firmware for sometime already but i was waiting for other guy to post it. I know we all looking for full Odin files so here they are :
AP_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship_meta.tar
CSC_ATT_N920AATT4EQC6_CL10809541_QB12921033_REV00_use r_low_ship.tar
CP_N920AUCU4EQC6_CP6021124_CL10809541_QB12921033_REV 00_user_low_ship.tar
BL_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship.tar
Download Link of :
Nougat_N920AUCU4EQC6_Odin_Files
All this files are in one zip. Unzip and put this in appropriate windows in ODIN.
Here are Odin 3.12.3
Good Luck.
Of course, this will wipe my device again, even though I do not select the CSC?
If you allow it to flash a new system and user data image then yes.
You basically need a wipe anyways going from MM to Nougat.
Sent from my Galaxy Note5 using XDA Labs
I'm already on Nougat N920AUCU4EQC5. I'm just trying to avoid having to wipe my phone
When i use this. It passes Odin then when the phone tries to reboot and install the update it says deleting then im back to 6.0.1. Any idea why?
norbarb said:
Some people just post info and never post links . I had firmware for sometime already but i was waiting for other guy to post it. I know we all looking for full Odin files so here they are :
AP_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship_meta.tar
CSC_ATT_N920AATT4EQC6_CL10809541_QB12921033_REV00_use r_low_ship.tar
CP_N920AUCU4EQC6_CP6021124_CL10809541_QB12921033_REV 00_user_low_ship.tar
BL_N920AUCU4EQC6_CL10809541_QB12921033_REV00_user_lo w_ship.tar
Download Link of :
Nougat_N920AUCU4EQC6_Odin_Files
All this files are in one zip. Unzip and put this in appropriate windows in ODIN.
Good Luck.
Click to expand...
Click to collapse
thank you very much for the link, bro.. i'm already Nougated now. experiencing some blue screen, but when i'm using newest odin.. all fixed.. thx again, man, you are the best.
DuganNash said:
When i use this. It passes Odin then when the phone tries to reboot and install the update it says deleting then im back to 6.0.1. Any idea why?
Click to expand...
Click to collapse
You may use wrong odin, some security installed on your phone, What build are you on?
norbarb said:
You may use wrong odin, some security installed on your phone, What build are you on?
Click to expand...
Click to collapse
It is Odin 3.12 run as admin. it gives me the green pass, then bootloader rolls back to MM
I am on build QB2 as of now.
DuganNash said:
It is Odin 3.12 run as admin. it gives me the green pass, then bootloader rolls back to MM
I am on build QB2 as of now.
Click to expand...
Click to collapse
Can you post your about phone screen ?
norbarb said:
Can you post your about phone screen ?
Click to expand...
Click to collapse
here you go, thank you
DuganNash said:
here you go, thank you
Click to expand...
Click to collapse
Thanks. Ok. Do you have any security like any kind encryption installed on your phone ?
I update first post with newest ODIN. Are you unzipping file you download and put tar files in correct windows? Are you in Download mode when using ODIN ?
norbarb said:
Thanks. Ok. Do you have any security like any kind encryption installed on your phone ?
I update first post with newest ODIN. Are you unzipping file you download and put tar files in correct windows? Are you in Download mode when using ODIN ?
Click to expand...
Click to collapse
I'm not sure about security . It was a stock at note 5 until I tried updated to qb2. All dev factors are turned on, and the rar files are all unzipped and loaded through odin in download mode. It passes then the android update screen (the little robot ) says erasing upon revoot and I boot into mm again
DuganNash said:
I'm not sure about security . It was a stock at note 5 until I tried updated to qb2. All dev factors are turned on, and the rar files are all unzipped and loaded through odin in download mode. It passes then the android update screen (the little robot ) says erasing upon revoot and I boot into mm again
Click to expand...
Click to collapse
OK. Try this , After you unzip from one zip to 4 files , unzip all 4 files to tar.md5 and try ODIN again. Check for any encryption installed on your phone preventing bootloader from overwriting files.
norbarb said:
OK. Try this , After you unzip from one zip to 4 files , unzip all 4 files to tar.md5 and try ODIN again. Check for any encryption installed on your phone preventing bootloader from overwriting files.
Click to expand...
Click to collapse
i tried this after making sure the phone was not encrypted under the security setting. Same result unfortunately. am looking for alternatives
You're the man !! just the files Odin I was looking for. I want to marry with you ... make me a son jajaja
DuganNash said:
i tried this after making sure the phone was not encrypted under the security setting. Same result unfortunately. am looking for alternatives
Click to expand...
Click to collapse
You have to necessarily erase the security lock fingerprints, you also have to remove the password lock, you have not any type of security lock, then you have to enable developer options and type USB debugging(This last one I do not know if it is strictly necessary, but just in case)If you have some security lock on your phone, even if you pray, you will not be able to!
After update installation it is sayin(device didn't have DRK,please install DRK first)
Please help me
Thanks
TaimooR Khawaja said:
After update installation it is sayin(device didn't have DRK,please install DRK first)
Please help me
Thanks
Click to expand...
Click to collapse
What did you flash before this stock firmware?
DRK=device root key
Clicking from Edge of Galaxy
Just a thought, can you Odin flash any other version of the official AT&T firmware? Maybe try another version to see if the phone is truly screwed.
Also, have you tried a factory reset on the phone first. Maybe something (anything) loaded on the phone is preventing the Odin flash. I know this shouldn't matter but it's worth a try.
mattern1974 said:
Just a thought, can you Odin flash any other version of the official AT&T firmware? Maybe try another version to see if the phone is truly screwed.
Also, have you tried a factory reset on the phone first. Maybe something (anything) loaded on the phone is preventing the Odin flash. I know this shouldn't matter but it's worth a try.
Click to expand...
Click to collapse
Same here.. i try to flash it via odin v3.12 it showing pass message..
After reboot my phone still on MM 6.0.1