Related
I've been away for a while and I apologize if the answer is here somewhere, I looked and couldn't find what I was looking for but maybe I wasn't looking right. Anyways I just got my S5, already tripped knox oops, but don't care. What I do care about is no more OTA updates D: so I'm not auto up on new stuff. I guess that's okay if I want root but I digress. Is there a way to update to 5.1.1 (i'm on 5.0) without nuking my phone? I get tired of the backup-update back and forth back and forth with updating. I already had a few snags with ODIN'ing the root for the phone and such. I think I'm on my 3-4 full setup and it's getting tiring.
TL;DR- Is there a way to update to 5.1.1 without having to backup/restore all of my data, like a pre-root or rootable ODIN of 5.1.1? Second, is 5.1.1 important? I heard it fixes alot of bad security problems.
Oh and I don't need a custom rom, I actually like the standard phone.
Sakuryu said:
I've been away for a while and I apologize if the answer is here somewhere, I looked and couldn't find what I was looking for but maybe I wasn't looking right. Anyways I just got my S5, already tripped knox oops, but don't care. What I do care about is no more OTA updates D: so I'm not auto up on new stuff. I guess that's okay if I want root but I digress. Is there a way to update to 5.1.1 (i'm on 5.0) without nuking my phone? I get tired of the backup-update back and forth back and forth with updating. I already had a few snags with ODIN'ing the root for the phone and such. I think I'm on my 3-4 full setup and it's getting tiring.
TL;DR- Is there a way to update to 5.1.1 without having to backup/restore all of my data, like a pre-root or rootable ODIN of 5.1.1? Second, is 5.1.1 important? I heard it fixes alot of bad security problems.
Oh and I don't need a custom rom, I actually like the standard phone.
Click to expand...
Click to collapse
So you are wanting to run stock rom with just root?
Yeah i found out how after a bit of searching. But now i have seandroid not enforcing. Warranty set kerne
Update here, I just ran the stagefright detector and it shows me as being vulnerable. I updated to FOG6 5.1.1 Deodexed/Rooted. Shouldn't it have been patched?
Sakuryu said:
Update here, I just ran the stagefright detector and it shows me as being vulnerable. I updated to FOG6 5.1.1 Deodexed/Rooted. Shouldn't it have been patched?
Click to expand...
Click to collapse
From What I heard the 5.1.1. update only fixed part of the issue, after the fix another issue was found.
Ok so bare with me here. I was on 5.1 rooted on stock rom i got a ota update for 6.0 MM. so i flashed stock rom and unroot and fastboot stock recovery so i can accept the update... yes i know there is no root for it... anyways i do the update.... it gets stuck on the tmobile logo... so i factory reset and its a no go same thing... so i think ill fastboot 5.1 boot.img recovery and system... it boots and then get stuck on android is starting apps... and gets stuck on that... thinking crap. i ruined my phone... but i remember as im not a total noob on flashing.... i just updated to 6.0 i sure it has a new kernel and radio etc... so i reroot fastboot mm twrp and flash the ported korean MM and it boots up. only problem now is the korean version port has issues such as the the freaking camera... im sure i could go back to 5.1 if i flash the 5.1 radio kernel etc.... but it worth it? and where would i find these files?
Unfortunately this phone is a mess with the OTA and all. Your best bet is probably just to wait and see what the devs come out with. I wouldn't try to rollback because I've heard some bad stuff about that. I would just stick with it and wait to see what MM options are released.
martinsavvy said:
Unfortunately this phone is a mess with the OTA and all. Your best bet is probably just to wait and see what the devs come out with. I wouldn't try to rollback because I've heard some bad stuff about that. I would just stick with it and wait to see what MM options are released.
Click to expand...
Click to collapse
Thanks martinsavvy. I'm impatient the Korean port is terrible... I flashed eliminator and got bricked cause I didn't follow the steps... Some how someway I was able to get back on to twrp after 30 minutes of fooling around with it. Wiped everything and did it again and now I have 6.0 stock running smoothly
Sent from my LG-H901 using XDA-Developers mobile app
Ok. I know the models N950U and N950U1 can swap firmware. So since Sprint had released Pie for N950U on its network, I got to thinking if that firmware can be flashed via Odin on N950U1.
The answer is Yes! I successfully flashed the N950USQU5DSC1/N950UOYN5DSC1 OS: Pie(Android 9) on my N950U1. And without the Sprint bloats.
After some discussions with @Mr. Orange 645 , I felt I needed to put some caveats in this post. So anyone attempting this should be reminded of some inherent risks.
1. There's a possibility that your OTA updates could be broken.
2. If you do get updates via OTA it will include Sprint bloats and stuff.
3. You will have to flash via Odin PIE for N950U1 when it's out.
4. Use only the files included in the Sprint PIE firmware. Do not mix with other files.
5. And something could always go wrong and you end up bricking your phone. DO NOT DO THIS IF YOUR PHONE BRICKING TOLERANCE IS LESS THAN 0.1%
6. A full factory reset is a must
This is simply really. Use the regular Odin 3.13.1 and select BL, AP, etc. But only IGNORE the Home_csc file and the User_Data file. Don't flash these.
Also, do not mix any other CSC files. Flash only the files you see in the Sprint PIE firmware.
If you do it right, your N950U1 will boot to Pie without any Sprint apps or other bloat.
Importantly Knox is not tripped. Phone status still official. In download mode Knox still reads 0x0.
OTA still works (at least it still connects to server and returns a result). However, if there is an update and you installed it, I can't say the effect it will have on the phone.
More pics
jopancy said:
This is simply really. Use the regular Odin 3.13.1 and select BL, AP, etc. But only IGNORE the Home_csc file and the User_Data file. Don't flash these.
Click to expand...
Click to collapse
Just be aware that this (only partially flashing a firmware update) will most likely break OTA updates on your device. As a consequence you will always need to use ODIN to flash future updates unless you flash the full set of files again.
Of course this won't trip Knox. It's all official firmware. And it will break OTAs, so when you want to update, you will have to use ODIN.
My suggestion is:
1. Wait for the official OTA. It should be pushed soon since the carriers have released Pie. OR
2. Follow my guide to get the Pie beta for the U1. OR
3. Just flash the full carrier firmware and deal with the bloat.
Mr. Orange 645 said:
Of course this won't trip Knox. It's all official firmware. And it will break OTAs, so when you want to update, you will have to use ODIN.
My suggestion is:
1. Wait for the official OTA. It should be pushed soon since the carriers have released Pie. OR
2. Follow my guide to get the Pie beta for the U1. OR
3. Just flash the full carrier firmware and deal with the bloat.
Click to expand...
Click to collapse
Of course some will wait for the official OTA. But for people like me who want to see what Pie has to offer NOW, this is a way of doing that. Official OTA updates can be reinstated when PIE for N950U1 is out and is flashed via Odin.
People got the unlocked version because they didn't want the bloat that comes with carrier branded firmware.
jopancy said:
Of course some will wait for the official OTA. But for people like me who want to see what Pie has to offer NOW, this is a way of doing that. Official OTA updates can be reinstated when PIE for N950U1 is out and is flashed via Odin.
People got the unlocked version because they didn't want the bloat that comes with carrier branded firmware.
Click to expand...
Click to collapse
PIE is available now for people to see what it has to offer on the U1 without mix matching firmware files and breaking things.
Yes I know why people buy the U1. I've had several of them myself since the S8+
Mr. Orange 645 said:
PIE is available now for people to see what it has to offer on the U1 without mix matching firmware files and breaking things.
Yes I know why people buy the U1. I've had several of them myself since the S8+
Click to expand...
Click to collapse
Stop writing contradictory things and creating panic where there is non. How many people got to join the Beta? Moreover the beta is now closed. N950U1 has to wait for the official PIE when most of the carriers have done their test. And that could be weeks. Like I explained if one cannot wait, this method is an option to get pie now. You agree that both N950U1 and N950U has the same Hardware, so what is to break? I could point you to older posts where some have flashed different carrier firmware on their phones without issues. I have been using Sprint PIE Firmware on N950U1 without issues, Samsung pay works, Secure folder works, not a single issue.
If you are afraid to 'break things' then you shouldn't even be on xda.
jopancy said:
Stop writing contradictory things and creating panic where there is non. How many people got to join the Beta? Moreover the beta is now closed. N950U1 has to wait for the official PIE when most of the carriers have done their test. And that could be weeks. Like I explained if one cannot wait, this method is an option to get pie now. You agree that both N950U1 and N950U has the same Hardware, so what is to break? I could point you to older posts where some have flashed different carrier firmware on their phones without issues. I have been using Sprint PIE Firmware on N950U1 without issues, Samsung pay works, Secure folder works, not a single issue.
If you are afraid to 'break things' then you shouldn't even be on xda.
Click to expand...
Click to collapse
I don't think you know what the word contradictory means. I never said anything contradictory, nor am I creating panic. I believe I have a little more experience at this than you do. And I'm trying to help you out as well as others. Have you even read my guide?
Mr. Orange 645 said:
I don't think you know what the word contradictory means. I never said anything contradictory, nor am I creating panic. I believe I have a little more experience at this than you do. And I'm trying to help you out as well as others. Have you even read my guide?
Click to expand...
Click to collapse
Yes I have read your guide. In fact, it is one of the reasons I felt what I did could work. I only posted the results of following your guide. So I am confused at why you are so critical.
N950U1 is supposed to work on ANY carrier. Including Sprint. So it should follow that Sprint firmware could be flashed on N950U1.
For all it's worth, you should see my post as a confirmation of your guide.
And OTA isn't broken. I tested it and it works. See pics.
jopancy said:
Yes I have read your guide. In fact, it is one of the reasons I felt what I did could work. I only posted the results of following your guide. So I am confused at why you are so critical.
N950U1 is supposed to work on ANY carrier. Including Sprint. So it should follow that Sprint firmware could be flashed on N950U1.
For all it's worth, you should see my post as a confirmation of your guide.
And OTA isn't broken. I tested it and it works. See pics.
Click to expand...
Click to collapse
I'm confused as to why you are determined to take what I'm saying so personal. I'm not being critical.
And again, yes, the devices are identical hardware-wise and you can cross flash carrier firmware on the U1 and U1 firmware on the carrier models. That's not the question.
I was merely pointing out that mixing firmware files (using some from U1 and using some from U) can break things, including OTAs. That's not being critical, that's letting you and everyone else know the downside. The only person who's been critical is you, telling me I shouldn't even be on XDA, merely because I dared to tell you a con to mixing firmwares.
By the way, your screenshot proves nothing. That just means you CHECKED for an OTA. When I say OTAs will be broken, I mean even if your phone recognizes there's an update available, it won't be able to apply it, as the OTA update checks to make sure you're on a specific firmware version.
As I said before, I personally helped someone do EXACTLY what you did through PM, and he went back to regular firmware because his OTAs were broken and he didn't want to have to use ODIN each time he wanted to update.
New Root Method For Note 8 SM-N950U/U1 V7 Bootloaders
Rooted Nougat RomThis is last nougat rom made for note 8 it is prerooted with flashfire and safestrap preinstalled. It has CSC stuff for all carriers added. Its debloated slightly with knox removed. Some stuff may not work but im not sure as I cannot test but this stuff may include fingerprint and or face recognition. If stuff doesnt work it probably related to using pie modems and non-hlos on a nougat rom which you have no choice.
Downloads
Rooted_N950USQS3BRB4.rar
BL_N950_NOUGAT_V7.tar.7z
Includes Fingerprint and Face Unlock fix for above nougat rom. Just flash in BL slot in odin after everything else
Safestrap-4.10-B03-GREATQLTE-PIE.zip Will boot straight to safestrap only for pie roms
Safestrap-4.10-B03-GREATQLTE-NOUGAT.zip Will Give you the safestrap splash screen on boot
Directions
Safestrap Method
1. Extract system.img from the Rooted_N950USQS3BRB4.rar and copy to phone reboot to safestarp and flash system image reboot to download and flash BL_N950_NOUGAT_V7.tar.md5 in odin
Good luck testers.
tested and confirmed working!
Now bring to n960u :cyclops:
jrkruse said:
tested and confirmed working!
Click to expand...
Click to collapse
Wow that is amazing. Good work on getting this going!!!
pbedard said:
Now bring to n960u :cyclops:
Click to expand...
Click to collapse
Already did one test with an unmodified system in edl and it failed like all the other times i tried it lol
@jrkruse Was there a particular reason RJ1 was chosen as the base combo instead of RG2?
The only difference I heard of was that RG2 actually was the DRK repair, where RJ1 did most of the other stuff.
Delgoth said:
@jrkruse Was there a particular reason RJ1 was chosen as the base combo instead of RG2?
The only difference I heard of was that RG2 actually was the DRK repair, where RJ1 did most of the other stuff.
Click to expand...
Click to collapse
it doesnt matter what v5 combo I am only using bootloaders on rooted rom and you just flash full combo system to be able to reboot to edl mode. The goal was to get root so safestrap can be used on Pie and thats been achieved.
This is excellent! Thanks guys!
Sent from my SM-N950U using Tapatalk
I have been waiting for this for quite some time. Thank you!
c
echo ¦¢ Galaxy S8 Plus USA Flash System Program
mode
Click to expand...
Click to collapse
can we add note 8 to description in batch file?
When flashing "COMBINATION_FA71_N950USQU5ARJ1_CL13942288_QB203914 89_REV00_user_mid_noship_MULTI_CERT.tar.md5 "
should I press BL+AP+others or just BL?
similar question, when flashing COMBINATION_FA71_N950USQU5ARJ1_BOOTLOADERS.tar should i select BL only or AP?
My baseband version is N950U1UEU1AQ15 build number NMF26X.N950USQU1AQ15 but I see different versions from romreactor below, am I still ok to flash?
One main question, which V5 firmware version is best for this root method, as I am still on firmware N950USQU2BQLA.
The V5 firmwares range from android 8.0 Oreo to 9.0 Pie and thus my question is out of all the V5 bootloader versions below which one is best for this root method for me to update to from my current version.
N950USQU5CRG7,
N950USQU5CRIA,
N950USQU5DSC1,
N950USQU5DSD3,
Also, couple newbie questions, 1. pre rooted firmware means Android Pie or Oreo with root access enabled right?
2. Does this root method allow you to flash custom roms of pie?
Ok, so I have been out of the rooting game for a couple of years now due to needing an engineering kernel and then losing 20% battery capacity. With this I am interested as I am running 5DSF6 currently. With this, are we only able to do the initial rooted ROM and have root access and customize from there or can we load different ROMS? Also, are kernels still out of the question with this method as well?
Also, congrats on getting this to work.
Romreactor said:
One main question, which V5 firmware version is best for this root method, as I am still on firmware N950USQU2BQLA.
The V5 firmwares range from android 8.0 Oreo to 9.0 Pie and thus my question is out of all the V5 bootloader versions below which one is best for this root method for me to update to from my current version.
N950USQU5CRG7,
N950USQU5CRIA,
N950USQU5DSC1,
N950USQU5DSD3,
Also, couple newbie questions, 1. pre rooted firmware means Android Pie or Oreo with root access enabled right?
2. Does this root method allow you to flash custom roms of pie?
Click to expand...
Click to collapse
There is only root available for nougat. The whole reason for all of this was to get people a pie rom that has the ability to boot to safestrap. Now this isn’t root but in safestrap you can flash zips just like you can with twrp or flashfire you can backup data or delete apps or modify system files and most everything you do you will still pass safetynet . Of course you can run a prerooted nougat rom or make your own but you would have to run the combo bootloader and boot img so your stuck with those limitations. Nothing has changed since this phone was first rooted with samfail method.
Sent using some kind of device I modified
People on v3 v2.5 or v2 or v1 bootloaders there is really no reason to stay on those older bootloaders since this method works for v5 if you choose to use this method you will be updated to v5 bootloaders
Sent using some kind of device I modified
jrkruse said:
There is only root available for nougat. The whole reason for all of this was to get people a pie rom that has the ability to boot to safestrap. Now this isn’t root but in safestrap you can flash zips just like you can with twrp or flashfire you can backup data or delete apps or modify system files and most everything you do you will still pass safetynet . Of course you can run a prerooted nougat rom or make your own but you would have to run the combo bootloader and boot img so your stuck with those limitations. Nothing has changed since this phone was first rooted with samfail method.
Sent using some kind of device I modified
Click to expand...
Click to collapse
Ah ok... so to be clear and for those who may be seeking the same question:
Is the battery still stuck at 80%? (Unless one charges to 100% in DL mode.)
jrkruse said:
People on v3 v2.5 or v2 or v1 bootloaders there is really no reason to stay on those older bootloaders since this method works for v5 if you choose to use this method you will be updated to v5 bootloaders
Sent using some kind of device I modified
Click to expand...
Click to collapse
Also to add, for those who are on 7.1.1 Nougat like me and several others who want to preserve the BL, just know that once you roll up you can not roll back. I think it's important to emphasize this..
iunlock said:
Ah ok... so to be clear and for those who may be seeking the same question:
Is the battery still stuck at 80%? (Unless one charges to 100% in DL mode.)
Also to add, for those who are on 7.1.1 Nougat like me and several others who want to preserve the BL, just know that once you roll up you can not roll back. I think it's important to emphasize this..
Click to expand...
Click to collapse
Just curious whats your reason for not updating bootloader to v5 now that you can root it as well
Sent using some kind of device I modified
jrkruse said:
Just curious whats your reason for not updating bootloader to v5 now that you can root it as well
Sent using some kind of device I modified
Click to expand...
Click to collapse
Because newer isn't always necessarily better. I'm of the minority and there are others like me who prefer to stay on the earlier firmwares.
The hopes of getting a full root early on was another reason, where had we blindly rolled up to the latest, it could have locked us out from taking advantage of a possible working root on an earlier BL. One rule of thumb is to never just jump on updates. We call them lock outs...and we kind of saw this with the original samfail root where those who updated could not roll back; but of course now it's possible which is great. Thanks again for making this happen and saving those who jumped early that never thought they would see a form of root.
There of course other reasons I like to stay put on earlier firmware versions, but that's for another conversation. @butchieboy, @KennyG123 and I go way back and they know.... We enjoy our Note 3's on 4.3, Note 4's on KK 4.4, Note 5 on MM etc...
iunlock said:
Because newer isn't always necessarily better. I'm of the minority and there are others like me who prefer to stay on the earlier firmwares.
The hopes of getting a full root early on was another reason, where had we blindly rolled up to the latest, it could have locked us out from taking advantage of a possible working root on an earlier BL. We kind of saw this with the original samfail root where those who updated could not roll back; but of course now it's possible which is great. Thanks again for making this happen and saving those who jumped early that never thought they would see a form of root.
There of course other reasons I like to stay put on earlier firmware versions, but that's for another conversation. @butchieboy, @KennyG123 and I go way back and they know.... We enjoy our Note 3's on 4.3, Note 4's on KK 4.4, Note 5 on MM etc...
Click to expand...
Click to collapse
Each too their own im always just curious why people refuse to update and not fully utilize the potential of their phone but like you said newer isn’t always better
Sent using some kind of device I modified
@jrkruse
You are a true rock star. And I too thank you for bringing this to us[emoji106][emoji106]
Sent from my SM-N960U using Tapatalk
Hello im using a SM-G965U1 and im currently running Baseband Version: G965U1UES4CSD4 Security Patch April 1, 2019
Ever since my S9+ started running Android 9 ive found it very user unfriendly, ugly, bloated, laggy, and more strictly governed.
I need help from some of the smart minds on XDA to help me compile a build that lets me flash Android 8 without tripping a
binary flash error/rollback prevention. I AM 100% willing to Brick my S9+ if it means i have any minute chance of getting back
my beloved android 8.0.
I also own a limited license to Samsung Knox if this would help with this project.
Update: If it increases any chance of getting my phone back to Oreo i will be offering a reward to anyone who is successful
Thanks in advanced
NitricWave said:
Hello im using a SM-G965U1 and im currently running Baseband Version: G965U1UES4CSD4 Security Patch April 1, 2019
Ever since my S9+ started running Android 9 ive found it very user unfriendly, ugly, bloated, laggy, and more strictly governed.
I need help from some of the smart minds on XDA to help me compile a build that lets me flash Android 8 without tripping a
binary flash error/rollback prevention. I AM 100% willing to Brick my S9+ if it means i have any minute chance of getting back
my beloved android 8.0.
I also own a limited license to Samsung Knox if this would help with this project.
Thanks in advanced
Click to expand...
Click to collapse
You can't go back due to the higher "4" Bootloader. Bootloader with oreo was XX2. Maybe there is a chance to flash a Oreo rum with twrp. But for that you'd need root.
Jogg3r said:
You can't go back due to the higher "4" Bootloader. Bootloader with oreo was XX2. Maybe there is a chance to flash a Oreo rum with twrp. But for that you'd need root.
Click to expand...
Click to collapse
Yeah i understand that i thought i explained that. What i thought would be possible is to package bootloader 4 to run with Android Oreo.
Nothing is impossible. If humanity figured out how to land a man on the moon we can figure how to trick a S9 to run Android Oreo.
If it increases any chance of getting my phone back to Oreo i will be offering a reward to anyone who is successful
NitricWave said:
Yeah i understand that i thought i explained that. What i thought would be possible is to package bootloader 4 to run with Android Oreo.
Nothing is impossible. If humanity figured out how to land a man on the moon we can figure how to trick a S9 to run Android Oreo.
If it increases any chance of getting my phone back to Oreo i will be offering a reward to anyone who is successful
Click to expand...
Click to collapse
Looks like humanity would likely go even to Mars. But some people just need to read and understand more.
NitricWave said:
Yeah i understand that i thought i explained that. What i thought would be possible is to package bootloader 4 to run with Android Oreo.
Nothing is impossible. If humanity figured out how to land a man on the moon we can figure how to trick a S9 to run Android Oreo.
If it increases any chance of getting my phone back to Oreo i will be offering a reward to anyone who is successful
Click to expand...
Click to collapse
We never went to the Moon so yes, your request is impossible
I'm assuming you're just a troll with nothing else better to do. Go get a job like the rest of us, thanks:good:
w41ru5 said:
Looks like humanity would likely go even to Mars. But some people just need to read and understand more.
Click to expand...
Click to collapse
I don't understand how this could apply here, do you even understand how hardware integrated security works such as Common Criteria Mode? Everything is dictated to be either on or off. Software is never unbreakable even when integrated with hardware. It just so happens to be that samsung's knox is extremely good at minimizing vulnerabilities.