Might be a stupid question... but my co worker wants me to root his Note 3 and I see chainfire's auto root is for lollipop OA6... His Note 3 is on OH1 - will this work without bricking his device? or is there another root method out there for the Note 3?
Thanks ahead of time!
bosswick said:
Might be a stupid question... but my co worker wants me to root his Note 3 and I see chainfire's auto root is for lollipop OA6... His Note 3 is on OH1 - will this work without bricking his device? or is there another root method out there for the Note 3?
Thanks ahead of time!
Click to expand...
Click to collapse
I believe that firmware (OH1) is for the Glalaxy S3 not the Sprint Note 3.
Go here http://forum.xda-developers.com/galaxy-s3-sprint to get what you need
Good luck
actually, OH1 is for sprint galaxy note 3, as of August 3rd, 2015.
http://www.sammobile.com/firmwares/download/52971/N900PVPUEOH1_N900PSPTEOH1_SPR/
to bosswick, i used Odin 3.10 to flash my note 3 to stock using the above firmware.
then i rebooted back into download mode, and flashed the .IMG file for TWRP recovery through Odin.
then i rebooted into recovery, and from within TWRP, i flashed the latest SuperSU 2.4.6. i had root upon my first bootup... not sure if this will work for you.
im bumping this in hopes that someone responds... will any new roms be cooked based on this update?
pocholo36 said:
im bumping this in hopes that someone responds... will any new roms be cooked based on this update?
Click to expand...
Click to collapse
OH1 is a security update for the Stagefright app you can find info here http://support.sprint.com/support/a...ServiceAdvisory_542_GKB59201-dvc7770003prd#!/ as for new roms it depends on what base is used, the security issue showed up in Lollipop 5.0, but was not a problem in KK NK4. I don't think it is worth updating to OH1 as it only fixes half the problem, as already determined in this thread by JoHnNYBlaZE716 http://forum.xda-developers.com/note-3-sprint/general/stagefright-fix-t3180092
I did OE1. Rooted via odin the regular way to root, then twrp via odin, wiped, and tried the pac man rom. It was cool but spen didnt work
jimzweb1 said:
OH1 is a security update for the Stagefright app you can find info here http://support.sprint.com/support/a...ServiceAdvisory_542_GKB59201-dvc7770003prd#!/ as for new roms it depends on what base is used, the security issue showed up in Lollipop 5.0, but was not a problem in KK NK4. I don't think it is worth updating to OH1 as it only fixes half the problem, as already determined in this thread by JoHnNYBlaZE716 http://forum.xda-developers.com/note-3-sprint/general/stagefright-fix-t3180092
Click to expand...
Click to collapse
oooohhh yeeaaaah... now i remember reading about that, thanks jimzweb1.... i thought a modem update would be worth it but i guess not, oh well... im on OH1 baseband now with latest CM nightly...
djhulk2 said:
I did OE1. Rooted via odin the regular way to root, then twrp via odin, wiped, and tried the pac man rom. It was cool but spen didnt work
Click to expand...
Click to collapse
You need to download Spen Buddy from the play store. It will allow for the Spen to work with CM based ROMs.
Related
Feeling like a Noob... Tried to downgrade from MJ4 to MI5 but now I'm stuck in download mode....
Guessing my only way out at this point is to flash TWRP then flash freeza MJ4 rom ?????
MasterZen88 said:
Feeling like a Noob... Tried to downgrade from MJ4 to MI5 but now I'm stuck in download mode....
Guessing my only way out at this point is to flash TWRP then flash freeza MJ4 rom ?????
Click to expand...
Click to collapse
yep, that's the way out. I had exaclty the same issue after trying to use CF-autoroot on stock MJ4 update. FYI after using odin to get TWRP back i also could not flash freeza's MJ4 as I had wiped system, data, davlik and cache also I had to restore a nandroid then factory reset in order to flash MJ4. One bug with freeza's MJ4 is your wifi passwords won't stick. However MI5 works fine with MJ4 firmware and does not have the wifi password issue. Probably more than you wanted to know but that's it in a nutshell.
ifly4vamerica said:
yep, that's the way out. I had exaclty the same issue after trying to use CF-autoroot on stock MJ4 update. FYI after using odin to get TWRP back i also could not flash freeza's MJ4 as I had wiped system, data, davlik and cache also I had to restore a nandroid then factory reset in order to flash MJ4. One bug with freeza's MJ4 is your wifi passwords won't stick. However MI5 works fine with MJ4 firmware and does not have the wifi password issue. Probably more than you wanted to know but that's it in a nutshell.
Click to expand...
Click to collapse
Thanks for the advice. So after I installed TWRP everything came back online. Currently working on a new rom for this device. Hoping I can bring Bonsai to our SN3...
I was able to use Knox de la vega method to downgrade from MJ4 to MI3. I used odin to flash both the AP file and the CSC file for the sprint MI3 and it worked like a charm but did flip my knox counter
MasterZen88 said:
Thanks for the advice. So after I installed TWRP everything came back online. Currently working on a new rom for this device. Hoping I can bring Bonsai to our SN3...
Click to expand...
Click to collapse
girron said:
I was able to use Knox de la vega method to downgrade from MJ4 to MI3. I used odin to flash both the AP file and the CSC file for the sprint MI3 and it worked like a charm but did flip my knox counter
Click to expand...
Click to collapse
You cant downgrade the mj4 firmware
Sent from my SM-N900P using Tapatalk
insane209 said:
You cant downgrade the mj4 firmware
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did but it screwed everything up. The baseband was still MJ4 but the build number was MI3 and I kept getting pen input errors and everything slowed down so much that it was pretty much not usable. I finally took it into another sprint store and was able to get it swapped out with a new one after adding insurance to it. This time I made sure not to upgrade yet to MJ4 to prevent screwing up my phone again. For some reason I was able to use both the MD5 and CSC files for MI3 to flash that in Odin but again it royally screwed it up.
Solution to WiFi password problem: http://forum.xda-developers.com/showthread.php?p=47358736
girron said:
I did but it screwed everything up. The baseband was still MJ4 but the build number was MI3 and I kept getting pen input errors and everything slowed down so much that it was pretty much not usable. I finally took it into another sprint store and was able to get it swapped out with a new one after adding insurance to it. This time I made sure not to upgrade yet to MJ4 to prevent screwing up my phone again. For some reason I was able to use both the MD5 and CSC files for MI3 to flash that in Odin but again it royally screwed it up.
Click to expand...
Click to collapse
They released the mj4 tar firmware now...flash it with odin
Sent from my SM-N900P using Tapatalk
Question about a firmware upgrade that is available. Now I just bought my Note 3 this past Wednesday and immediately got notification of a software update for the firmware. Knowing the issues taking a software update can sometimes cause, I haven't taken it. The phone is MI5. so should I not touch the update or what? I haven't rooted because I haven't had a chance, still figuring out the right steps and what, if anything, may be needed. Help with that would be welcomed as well.
squick said:
Question about a firmware upgrade that is available. Now I just bought my Note 3 this past Wednesday and immediately got notification of a software update for the firmware. Knowing the issues taking a software update can sometimes cause, I haven't taken it. The phone is MI5. so should I not touch the update or what? I haven't rooted because I haven't had a chance, still figuring out the right steps and what, if anything, may be needed. Help with that would be welcomed as well.
Click to expand...
Click to collapse
No its always good to take the ota update...rooting is eazy
Sent from Sprint Galaxy Note 3 using Tapatalk
squick said:
Question about a firmware upgrade that is available. Now I just bought my Note 3 this past Wednesday and immediately got notification of a software update for the firmware. Knowing the issues taking a software update can sometimes cause, I haven't taken it. The phone is MI5. so should I not touch the update or what? I haven't rooted because I haven't had a chance, still figuring out the right steps and what, if anything, may be needed. Help with that would be welcomed as well.
Click to expand...
Click to collapse
insane209 said:
No its always good to take the ota update...rooting is eazy
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
The quote by insane209 is exactly that.
OTA can update the bootloader making rooting without tripping KNOX impossible.
klau1 said:
The quote by insane209 is exactly that.
OTA can update the bootloader making rooting without tripping KNOX impossible.
Click to expand...
Click to collapse
Well if ur worried about knox then thats on u....but they update devices for a reason...and that is to fix various bugs..
Sent from Sprint Galaxy Note 3 using Tapatalk
insane209 said:
Well if ur worried about knox then thats on u....but they update devices for a reason...and that is to fix various bugs..
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
Who said you can't have both?
If you were smart enough, you would have responded with URDLV to patch the ROM and root without KNOX and MobileODIN to further upgrade the ROM without changing the old bootloader (which doesn't have anything to do with bugs)
But no.
klau1 said:
Who said you can't have both?
If you were smart enough, you would have responded with URDLV to patch the ROM and root without KNOX and MobileODIN to further upgrade the ROM without changing the old bootloader (which doesn't have anything to do with bugs)
But no.
Click to expand...
Click to collapse
No i just franky give a **** about warrenty...i got a bad esn phone lol
And as for bugs yea this phone still gots em...other than that owell
Sent from Sprint Galaxy Note 3 using Tapatalk
insane209 said:
No its always good to take the ota update...rooting is eazy
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
klau1 said:
The quote by insane209 is exactly that.
OTA can update the bootloader making rooting without tripping KNOX impossible.
Click to expand...
Click to collapse
Ok, thanks for the input. Just wanted to ask to make sure.
http://www.droid-life.com/2014/10/1...date-with-knox-2-0-connectivity-improvements/
...Sigh. When will vzw pull their heads out of their..
Surge1223 said:
...Sigh. When will vzw pull their heads out of their..
Click to expand...
Click to collapse
Until they realize they are not doing their customers any favors, never.
I knew better. Got an MDK device, rooted it immediately and have been running CM ever since. [emoji41]
If you guys are talking about Knox 2.0...get used to it. Knox is being incorporated by Google in Android "L".
Remember, with all the hackers out there, the average Joe and Joan want their privacy secured...all the banking that is done from the phones now?
And also Verizon is the largest carrier for military and commercial contracts...to keep them and get more the phones have to be as secure as possible.
Anyone try to see if Towelroot works with this build?
I think they need to find another root method. Towelroot only works on kernels june 3 and below. I have no idea if it will work if you used it
I'm not upgrading. All flashaholics like me will DEFINITELY just wait for a possible exploit for NC5 than hope for the almost nonexistent chance there will be an unlock in the new firmware. Just my $0.02
Sent from an S4 Lost in the Echoe
SolidSnakeUS said:
Anyone try to see if Towelroot works with this build?
Click to expand...
Click to collapse
We have been able to use towelroot on the latest updates for the att S4, S5, and Vz S5 by flashing back the previous kernel, rooting, then reflashing the new unexploitable kernel. Vz S4 users will likely be able to do the same on NG6.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Least they could have done was give us 4.4.4 at the same time.
Sent from my SCH-I545 using XDA Free mobile app
Anyone get this yet. What android version is it still 4.4.2
Does towelroot work on this update? I want to know before I take the plunge...
Sent from my SCH-I545 using Tapatalk
Downloading now. I don't care if I lose root. I'll test towelroot after the update.
MedleHed said:
Downloading now. I don't care if I lose root. I'll test towelroot after the update.
Click to expand...
Click to collapse
Towelroot is guaranteed not to work. A better option is to grab the update from your cache/fota folder and post so that we can make a workaround to keep root.
Yep id give it to muniz.
Theres no way im going through the drama we had last time.
Surge1223 said:
Yep id give it to muniz.
Theres no way im going through the drama we had last time.
Click to expand...
Click to collapse
Lol, I remember and don't blame you at all.
It's confirmed that towelroot doesn't work. The version is still 4.4.2. The first thing I noticed was the GPS toggle in the notification area is now a Location toggle.
Any method of rooting?
Now that Towelroot is out, is there any way of rooting on the latest version? Downgrading, flashing an image in Odin, etc? Or are we pretty much screwed until a work around is found?
asalkowskineo said:
Now that Towelroot is out, is there any way of rooting on the latest version? Downgrading, flashing an image in Odin, etc? Or are we pretty much screwed until a work around is found?
Click to expand...
Click to collapse
There is a very good chance that the kernel swap method will work on this latest build.
Someone just needs to grab the ota from their device. We'll take the kernel from the new update and package it into an Odin flashable .tar. You'll then flash the old NC5 kernel after taking the update, re-boot and root using towelroot, then reflash the new kernel. No guarantees but this method has been working on all of the latest Sammy updates.
muniz_ri said:
There is a very good chance that the kernel swap method will work on this latest build.
Someone just needs to grab the ota from their device. We'll take the kernel from the new update and package it into an Odin flashable .tar. You'll then flash the old NC5 kernel after taking the update, re-boot and root using towelroot, then reflash the new kernel. No guarantees but this method has been working on all of the latest Sammy updates.
Click to expand...
Click to collapse
I could give you guys the OTA if you tell me how to do it. I'm by no means an expert at rooting, but I've had a few years experience. So basically you'll modify the new kernel to allow downgrading to NC5, root, then update again? I had Towelroot before I updated, had OTA survival mode enabled in SuperSU, and had it installed as a system app, but I still lost root on this latest update. :crying:
muniz_ri said:
There is a very good chance that the kernel swap method will work on this latest build.
Someone just needs to grab the ota from their device. We'll take the kernel from the new update and package it into an Odin flashable .tar. You'll then flash the old NC5 kernel after taking the update, re-boot and root using towelroot, then reflash the new kernel. No guarantees but this method has been working on all of the latest Sammy updates.
Click to expand...
Click to collapse
When they finally block us from doing this, it will be a dark day lol.
I have the note edge, still on kit Kat, it's rooted. But it's got a stock rom. I was thinking about upgrading to lollipop, but read I'd have to unroot kitkat, install the official lollipop, then root lollipop?
Are there step by step instructions, or maybe even an easier way out there?
I miss the days when we could just flash radio updates and any rom we wanted without doing anything else. Ha.
http://forum.xda-developers.com/showthread.php?t=2943993
primo523 said:
http://forum.xda-developers.com/showthread.php?t=2943993
Click to expand...
Click to collapse
Thanks but that thread is for T-mobile?
You have to Odin back to stock firmware. .. Let the OTA take place then re-root ..
Werd.
primo523 said:
You have to Odin back to stock firmware. .. Let the OTA take place then re-root ..
Click to expand...
Click to collapse
I assume that this hasn't changed at all?
OK2 isn't rooted yet, so flash the OG1 stock rom for lollipop and root that one. Don't take the OTA though cause you'll lose root.
Sent from my SM-N915P using Tapatalk
DevXen said:
I have the note edge, still on kit Kat, it's rooted. But it's got a stock rom. I was thinking about upgrading to lollipop, but read I'd have to unroot kitkat, install the official lollipop, then root lollipop?
Are there step by step instructions, or maybe even an easier way out there?
I miss the days when we could just flash radio updates and any rom we wanted without doing anything else. Ha.
Click to expand...
Click to collapse
Would you happen to have a nandroid of your KitKat have a friend who's battery can hardly last the day due to the constatnt drain issue on 5.1.1
cRiMiNaL_Genius said:
Would you happen to have a nandroid of your KitKat have a friend who's battery can hardly last the day due to the constatnt drain issue on 5.1.1
Click to expand...
Click to collapse
I'm sure I do somewhere. But it isn't a fresh install. It has my hacks and my own settings and my everything including any personal info they it stores? I. E. Google wallet info and lte encryption keys.
Thats no problem if you're still on KitKat make a new backup excluding the data and cache partitions, hopefully thas not too much for a friendly request lol
UPDATE: SOLVED, as of 07 FEB 2016; I needed to find an .MD5-compiled ROM with an NC5 bootloader; my last working bootloader was NC5 and using Odin to flash ROMs with other bootloaders had failed.
My phone has been rooted for over 2 years now and I've run a handful of ROMs, with Hyperdrive probably the most stable of the lot. Last fall I was losing some functionality (bad microphone) and I figured I might as well try a new ROM in case that helped. I install CM 12 and life was okay. I set it to download updates (mistake) and it upgraded me from CM 12 to CM 13. Much as I like the new Marshmallow features, my S4 steadily degraded in function over time, to the point where I stopped making or receiving phone calls.
Last week half of my installed apps disappeared, and attempting to install anything through the Google Play store failed. No clue how that might happen, but I knew it was time to flash a new ROM.
That was when I discovered I could no longer boot into TWRP; it hung on the TEAMWIN logo screen. Then I started getting the Verizon screen claiming it had detected unauthorized software.
Since I could no longer operate the phone, I went ahead and put it into download mode and ran Odin3 v3.10.7 and used that to flash an OC1 ROM, the only one I had that was in .MD5 format.
Now I can't get past a bootloop that leaves me hanging at the Verizon logo screen.
Any thoughts?
What is your bootloader right now? And/or what was it while on Hyperdrive?
Edit: wait....I see where u Odin'd oc1...was it the stock image? If so u may have flashed the oc1 boot.img. If that's the case, I suggest you download FlashFire and read up on it. Because if u were on nc5 or anything before you should be able to ODIN back down. But if u have an oc1 bootloader you're permalocked.
Huh. I tried to respond to this hours ago. Didn't upload, apparently.
Anyhow, thanks for responding. I have not been able to get an .MD5 version of the stock image to flash. The only complete .MD5 I've successfully downloaded is called "I545VRUGOC1_Neutered_Full_Odin.tar.md5". The last ROM running on this device was CyanogenMod 13, which is Android 6 with NC5 kernel.
I'm currently attempting to download "VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5" but it is slow going.
As for FlashFire, how could I install it to my phone? I cannot get past the bootloop. Odin seems to be my only option for flashing at this point, right?
Have you tried going to recovery after flashing OC1? maybe there are some leftovers of previous process, if your phone can go into recovery you should try to do some wipes
Edgardo_Uchiha said:
Have you tried going to recovery after flashing OC1? maybe there are some leftovers of previous process, if your phone can go into recovery you should try to do some wipes
Click to expand...
Click to collapse
Great suggestion; unfortunately, TWRP is blocked by the Verizon notice now (the one that tells you Verizon's identified unauthorized software on the phone).
Okay, I'm going to try an NC5.MD5 that I was able to download. Here's hoping it moves this process forward....
I can help you! I have everything! PM me here, or send me a message on hangouts!
Sent from my SCH-I545 using Tapatalk
Cincinnatux said:
Huh. I tried to respond to this hours ago. Didn't upload, apparently.
Anyhow, thanks for responding. I have not been able to get an .MD5 version of the stock image to flash. The only complete .MD5 I've successfully downloaded is called "I545VRUGOC1_Neutered_Full_Odin.tar.md5". The last ROM running on this device was CyanogenMod 13, which is Android 6 with NC5 kernel.
I'm currently attempting to download "VRUFNC5 Full-Wipe Verizon SCH-I545 4.2.2 562219 Stock Restore.tar.md5" but it is slow going.
As for FlashFire, how could I install it to my phone? I cannot get past the bootloop. Odin seems to be my only option for flashing at this point, right?
Click to expand...
Click to collapse
You're on the right path. ODIN the nc5 full wipe. And from there you can use Safestrap to flash whatever. But I'm wondering if you've locked the bootloader to oc1 or of1. If that's the case, you can go to sammobile.com and register and sign-in and download any factory image flashable thru ODIN.
The nc5.md5 worked! It's not particularly stable (yet), but at least the phone boots up and seems to work.Thanks to those who took the time to read over the issue and offer suggestions!
May i ask how you had cm13 running on nc5? @Cincinnatux
klabit87 said:
May i ask how you had cm13 running on nc5? @Cincinnatux
Click to expand...
Click to collapse
Yeah me too?!...I was confused throughout this whole post, but I'm glad he took the advice and got nc5 full wipe. Does the trick everytime (on a downgradeable bootloader of course).
ATGkompressor said:
Yeah me too?!...I was confused throughout this whole post, but I'm glad he took the advice and got nc5 full wipe. Does the trick everytime (on a downgradeable bootloader of course).
Click to expand...
Click to collapse
Perhaps I am mistaken. I had NC5 the last time I had checked, which was when I installed CM12. Sometime around December or so CM12 upgraded itself to CM13. The only thing I remember having to change was GAPPS, moving that from 5.1 to 6.0.
Cincinnatux said:
Perhaps I am mistaken. I had NC5 the last time I had checked, which was when I installed CM12. Sometime around December or so CM12 upgraded itself to CM13. The only thing I remember having to change was GAPPS, moving that from 5.1 to 6.0.
Click to expand...
Click to collapse
Regardless of whether it was CM12 or CM13, I would still like to know how you did it and where you got the files from.
Thanks.
klabit87 said:
Regardless of whether it was CM12 or CM13, I would still like to know how you did it and where you got the files from.
Thanks.
Click to expand...
Click to collapse
While I used to troll XDA for ROMs, for CM I'm sure I went to their website and downloaded whatever was current at the time, which was a Lollipop ROM. I used TWRP to install, but I no longer have any of my notes for that install so I couldn't verify any of this, really.
Cincinnatux said:
While I used to troll XDA for ROMs, for CM I'm sure I went to their website and downloaded whatever was current at the time, which was a Lollipop ROM. I used TWRP to install, but I no longer have any of my notes for that install so I couldn't verify any of this, really.
Click to expand...
Click to collapse
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
klabit87 said:
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
Click to expand...
Click to collapse
That's what I was assuming as well. When I had the s3, I was able to install a cm Rom thru Safestrap. Actually the other thread we were in by mohammad.afaneh, he was a dev on the Safestrap for s3 and got it to support a cm Rom, but it didn't have working data signal or Wi-Fi.
ATGkompressor said:
That's what I was assuming as well. When I had the s3, I was able to install a cm Rom thru Safestrap. Actually the other thread we were in by mohammad.afaneh, he was a dev on the Safestrap for s3 and got it to support a cm Rom, but it didn't have working data signal or Wi-Fi.
Click to expand...
Click to collapse
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
klabit87 said:
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
Click to expand...
Click to collapse
I don't think it was kexec. But go to the s3 forums and/or search his afh. We could probably modify it, or figure out exactly what he changed and incorporate it into the SS we have. Depending on what he changed, it may be possible to implement nc5flasher, gain support for AOSP bases (aka get them to boot). But in order to have a fully functional modem/firmware, the kernel would need to be built from source. I do know there is a thread (I think in s4 unified development) on a proof of concept project that will enable insecure modules on locked bootloaders. I could be wrong about the actual forum it's in and exactly what's involved. I believe it can be done, it's just gonna take many minds focused on a common goal with positive intent.
PS. There's a bounty and it would be nice if we could do it.
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
SORRY FOR HIJACKING YOUR POST @Cincinnatux!!!!!
klabit87 said:
So he got kexec working? That would be nice.
Maybe he can provide some insight on this.
I know many others that would love to use cm based roms.
Would be even better if he could get safestrap to work on oc1/of1 bootloaders
Click to expand...
Click to collapse
No, he modded CM enough to work with SS...
klabit87 said:
If that's the case then you actually had the mdk bootloader. There is no way to have any cm based rom on nc5.
Click to expand...
Click to collapse
Just to reduce my ignorance a little, maybe one of you can point out the error in my thinking/memory. I thought NC5 vs MDK vs OC1 was whatever was listed in About Phone as the Baseband Version, right? While my phone was MDK at the time of purchase (July 2013), I changed the baseband a few times while upgrading to newer flavors of Android. My current baseband is I545VRUFNC5, which is what I remember it being last fall as well. Where am I mistaken? Thanks!
Cincinnatux said:
Just to reduce my ignorance a little, maybe one of you can point out the error in my thinking/memory. I thought NC5 vs MDK vs OC1 was whatever was listed in About Phone as the Baseband Version, right? While my phone was MDK at the time of purchase (July 2013), I changed the baseband a few times while upgrading to newer flavors of Android. My current baseband is I545VRUFNC5, which is what I remember it being last fall as well. Where am I mistaken? Thanks!
Click to expand...
Click to collapse
Baseband does not equal bootloader.
You can update the baseband no problem but can't update the bootloader without being able to go back.
There is an app that you could use to check your bootloader called samsung phone info I believe our something like that.
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