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.
Related
Hi all,
Over on Android Forums a thread has posted claiming Keis/OTA is downloading a new version of the Stock ROM. Version NJ3? Has anyone here seen this?
Yes my wife got it last week.
Any benefit seen? Or is it more a bloatware update?
She hasn't noticed anything. Hard for her to tell really not knowing anything lol
Has anyone had a chance to grab this updated tar? I am on full CM11, I will give it a go via Keis for PC if it would still attempt to download. I know it won't actually work not being stock.
vsanch24 said:
Has anyone had a chance to grab this updated tar? I am on full CM11, I will give it a go via Keis for PC if it would still attempt to download. I know it won't actually work not being stock.
Click to expand...
Click to collapse
im checking this link out http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sph-l710
6th_Hokage said:
im checking this link out http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sph-l710
Click to expand...
Click to collapse
Interesting, I downloaded the NJ3 (in the middle of the list) but not sure how at apply it. Do you have any ideas? Or do we just change the .zip to a .tar and ODIN will work its' magic?
vsanch24 said:
Interesting, I downloaded the NJ3 (in the middle of the list) but not sure how at apply it. Do you have any ideas? Or do we just change the .zip to a .tar and ODIN will work its' magic?
Click to expand...
Click to collapse
i just checked it out.....it's not the actual update unfortunately open the zip and you'll see what i mean
That's the source code for the updated kernel. It doesn't contain any platform binaries
CNexus said:
That's the source code for the updated kernel. It doesn't contain any platform binaries
Click to expand...
Click to collapse
it has a folder in it called platform tho but when you read the Platform_read_me.txt file thing it says it's for making modules but that you have to download the module stuff separately...
You won't get anything from that file in terms of getting a rom going, trust me.
The most you could do is build the kernel zImage, but you're even limited in that because you'd need the updated boot.img for repacking your compiled zImage.
CNexus said:
You won't get anything from that file in terms of getting a rom going, trust me.
The most you could do is build the kernel zImage, but you're even limited in that because you'd need the updated boot.img for repacking your compiled zImage.
Click to expand...
Click to collapse
i see thats good info thank you
Anyone have luck grabbing the full updated rom? I tried with kies but this happened: (from a post I did on Android Forums)
... I think something has changed as now there is a small program that downloads into the temp folder. Once that finishes it asks for elevated permissions and then starts a new direct download to the phone while it is attached. I am guessing they got wind of these instructions and changed their kies upgrade method.....
My phone says that there's a patch for "Stagefright" available (under "Update Samsung Software"), and that it's been downloaded and verified (58.1 MB). I tap "Restart & install", it says "Rebooting now..." but nothing happens.
Sprint says that the patch is L710SPTBMK5 http://support.sprint.com/support/a...ServiceAdvisory_542_GKB49847-dvc6430001prd#!/
I was thinking of trying to flash it manually, but I couldn't find the file on my phone and haven't found a place to download it from.
Any suggestions?
I thought mk5 was jellybean. But I guess I was wrong. Nj2 was the latest update, until a couple days ago, not sure what the new one is. Oh1 maybe. But is your phone rooted? Custom recovery? Then don't try to install an update zip, it won't work. You can't do it manually even with stock recovery, unless you know how to adb sideload. Better off waiting until the full .tar is posted then using odin to install it.
If you're not rooted it should have installed fine. Try rebooting, if that doesn't work, and you are not rooted, use kies.
Also the update zip is in /cache, but you can only see it if you're rooted.
madbat99 said:
I thought mk5 was jellybean. But I guess I was wrong.
Click to expand...
Click to collapse
You might've been thinking of L710VPUCMK3
madbat99 said:
Nj2 was the latest update, until a couple days ago, not sure what the new one is. Oh1 maybe. But is your phone rooted? Custom recovery?
Click to expand...
Click to collapse
Yes
madbat99 said:
Then don't try to install an update zip, it won't work. You can't do it manually even with stock recovery, unless you know how to adb sideload. Better off waiting until the full .tar is posted then using odin to install it.
Click to expand...
Click to collapse
OK, I'll be patient
madbat99 said:
Also the update zip is in /cache, but you can only see it if you're rooted.
Click to expand...
Click to collapse
Yeah, checked there (and everywhere else I could think of) - nothing.
If it wasn't in cache then it probably didn't download.
If you do download it, it can have the updater script edited to be flashed in twrp. If you know how to edit updater scripts. Its not that hard.
madbat99 said:
If it wasn't in cache then it probably didn't download.
Click to expand...
Click to collapse
That's what I'm thinking too, except the phone says it was - https://goo.gl/photos/9oz9Vw3GmFkPPCGv6
Could it be that it got downloaded, but not saved, because the phone is rooted?
Mk5 is out of sequence, it has to be greater than n
avd said:
Mk5 is out of sequence, it has to be greater than n
Click to expand...
Click to collapse
What are you implying? That the Sprint website is wrong?
Not wrong, just confused.
Is this for the triband? Because mk5 on the standard s3 is indeed jellybean.
has anyone pulled the zip file? L710SPTBMK5?
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.)
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
Is this ok to install on the US variants?
Sent from my iPhone using Tapatalk
From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?
What version is this from?
hey bro did you have the flashligt icon and gesture in the new update?
Anyone flashed this with flash fire?
How to install on rooted devices???
sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
You didn't tell us what variant of the phone you have
How to install???
zimplemeh said:
Is this ok to install on the US variants?
Click to expand...
Click to collapse
No this is not recommended to install on US variant
saqlainrattansi said:
From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?
Click to expand...
Click to collapse
Yes you got it right
olive23 said:
What version is this from?
Click to expand...
Click to collapse
It's from build number *67
Jayesh Nirve said:
How to install???
Click to expand...
Click to collapse
Either use stock recovery or use Flashfire
zeft64 said:
You didn't tell us what variant of the phone you have
Click to expand...
Click to collapse
Indian Variant
Flash fire ain't working phone just reboots with no changes
can i install on retbr?
I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.
Pls tell me how u went back to 15 plsss
Aredhelelen said:
I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.
Click to expand...
Click to collapse
Exactly what I have been trying to tell. There is a fingerprint mismatch that happens. On a side note how did you manage to take yourself back from .35 to .15 and then update to .67. I get the last part, but downgrading with a higher bootloader; and where did you get the .15 build
You can simply install one of the stock versions already posted here in the forum, I just downloaded the .15 and installed it again via fastboot with the command lines (also explained in that post, in comments) like any other stock rom. Then, after starting the phone you must activate USB debbuging mode to be able to use ADB commands, so you can restart the phone in stock recovery and activate the push ota update via ADB.
Anyway, if this sounds complicated I think there is already a flashable .zip to apply ota, you can give it a try.
Hi there can anybody give me a link to a flashable zip of the stock frimware. I tried to flash the md5 file through odin and it keeps failing. I tried diffrent versions of odin and on Windows 7 and Windows 10 and still no luck
Will appreciate it thanks.
Billabomb75 said:
Hi there can anybody give me a link to a flashable zip of the stock frimware. I tried to flash the md5 file through odin and it keeps failing. I tried diffrent versions of odin and on Windows 7 and Windows 10 and still no luck
Will appreciate it thanks.
Click to expand...
Click to collapse
I don't know where there is a flasheable zip off hand, but you can make your own, there are several tutorials online, search for something like "Convert stock rom to flashable zip"
IronRoo said:
I don't know where there is a flasheable zip off hand, but you can make your own, there are several tutorials online, search for something like "Convert stock rom to flashable zip"
Click to expand...
Click to collapse
I dont have astock rom anymore
Billabomb75 said:
I dont have astock rom anymore
Click to expand...
Click to collapse
You can get stock rom from sammobile.com
https://www.sammobile.com/firmwares/galaxy-s4-mini/GT-I9190/
Billabomb75 said:
.....through odin and it keeps failing.
Click to expand...
Click to collapse
When you say failing, what do you mean? what is the error that you are getting on the phone?
i ask because i am having similar issues. am currently on lineage 7.1.1 and i found a single post out there that mentioned that when i flashed up to 7.1.1 that it triggered a fuse in the flash memory, that cannot be reversed. The error message i get seems to indicate that this is correct. fused2 > binary 1 - meaning that my handset is fused to 2 but the one i am flashing is only a 1.
i have a fully working phone on 7.1.1 but i want to revert to stock and am unable to do so
mrtim123 said:
When you say failing, what do you mean? what is the error that you are getting on the phone?
i ask because i am having similar issues. am currently on lineage 7.1.1 and i found a single post out there that mentioned that when i flashed up to 7.1.1 that it triggered a fuse in the flash memory, that cannot be reversed. The error message i get seems to indicate that this is correct. fused2 > binary 1 - meaning that my handset is fused to 2 but the one i am flashing is only a 1.
i have a fully working phone on 7.1.1 but i want to revert to stock and am unable to do so
Click to expand...
Click to collapse
I get a system write fail on system.ext4... So now i use the carbon 4.4.4 rom
Want to go back to stock
Billabomb75 said:
I get a system write fail on system.ext4... So now i use the carbon 4.4.4 rom
Want to go back to stock
Click to expand...
Click to collapse
ah right. same wants but different issue by the sound of it.
sorry i cant help!