Hi,
I was having bad experiences with stock OTA Lollipop 5.0.1 that ended up resulting in a bootloop. Long story short I decided to flash back to KitKat. Now I flashed back to the stock Verizon firmware G900VVZW1ANK2 using Odin. I went ahead and tried using towelroot, but apparently I guess the Kernel exploit is patched in that Dec build of KitKat, and it will not work (I tried other modstrings no dice).
From reading the following article it seems like the latest version of Kit Kat you can apply towelroot to is the NHA build from August 2014.
http://www.droidviews.com/update-verizon-galaxy-s5-to-android-4-4-4-kitkat-ni2-and-root-it/
http://www.w0lfdroid.com/2014/09/TowelRoot-Samsung-Galaxy-S4-S5-and-Note3-Android-4.4.2-NF-or-Later.html
Can someone please tell me if I am understanding this right? These article talks about rooting an older version of KitKat (NHA), then flashing a higher version of just the rooted kernel (which I assume is not the whole 2 GB Android OS). I assume in order to flash a custom rooted kernel, you need to have root in the first place, so is that why it is done?
So basically should I flash back to NHA, apply towelroot, then flash to NK2 firmware (OTA or by file?), and then flash rooted w0lf kernel? I thought when you flash back to stock firmware it unroots your device?
Or do I need to flash back down to NCG, apply towelroot, then flash to NK2 firmware (OTA or by file?), and then flash rooted w0lf kernel? Has anyone used these custom w0lf kernels, can they be trusted?
Or should I just flash my phone to the NHA build, root it, and leave it there?
For reference:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Booyaah82 said:
Hi,
I was having bad experiences with stock OTA Lollipop 5.0.1 that ended up resulting in a bootloop. Long story short I decided to flash back to KitKat. Now I flashed back to the stock Verizon firmware G900VVZW1ANK2 using Odin. I went ahead and tried using towelroot, but apparently I guess the Kernel exploit is patched in that Dec build of KitKat, and it will not work (I tried other modstrings no dice).
From reading the following article it seems like the latest version of Kit Kat you can apply towelroot to is the NHA build from August 2014.
http://www.droidviews.com/update-verizon-galaxy-s5-to-android-4-4-4-kitkat-ni2-and-root-it/
http://www.w0lfdroid.com/2014/09/To...4-S5-and-Note3-Android-4.4.2-NF-or-Later.html
Can someone please tell me if I am understanding this right? These article talks about rooting an older version of KitKat (NHA), then flashing a higher version of just the rooted kernel (which I assume is not the whole 2 GB Android OS). I assume in order to flash a custom rooted kernel, you need to have root in the first place, so is that why it is done?
So basically should I flash back to NHA, apply towelroot, then flash to NK2 firmware (OTA or by file?), and then flash rooted w0lf kernel? I thought when you flash back to stock firmware it unroots your device?
Or do I need to flash back down to NCG, apply towelroot, then flash to NK2 firmware (OTA or by file?), and then flash rooted w0lf kernel? Has anyone used these custom w0lf kernels, can they be trusted?
Or should I just flash my phone to the NHA build, root it, and leave it there?
For reference:
Click to expand...
Click to collapse
First of all, you don't need root to flash kernels or even entire ROMs, since sometimes the best way to achieve rooting is by flashing (cf-root, but not Verizon apparently) for Samsung devices.
I don't understand your problem with lollipop why did you downgrade? What caused the bootloop?
Towelroot vulnerability was patched right before the last relases of Android 4, so it is possibile.
So:
-In order to eventually flash even just the kernel (I can't see the point, you would still be pretty outdated), no, you don't need root, but you do need Odin or custom recovery.
-You may just flash NK2 and root it, which is what's explained in the guide. Again, if you really need that version of android.
-I've never used these w0lf kernels you are talking about, but at this point I would say they are not necessary.
-You could also just keep NHA, your choice, if that's a matter of security updates you are failing anyway, since lollipop is the most advanced. It depends on what you are looking for.
But before you proceed with anything, Verizon stuff is strange. It seriously took bug bounties to root that phone, and I suggest you follow the guide you linked. Anyway, I found evidence of towelroof working for all kitkat versions of Verizon up to Nk2, I guess that the main problem is actually flashing another firmware if required at this point.
Ciuffy said:
First of all, you don't need root to flash kernels or even entire ROMs, since sometimes the best way to achieve rooting is by flashing (cf-root, but not Verizon apparently) for Samsung devices.
I don't understand your problem with lollipop why did you downgrade? What caused the bootloop?
Towelroot vulnerability was patched right before the last relases of Android 4, so it is possibile.
So:
-In order to eventually flash even just the kernel (I can't see the point, you would still be pretty outdated), no, you don't need root, but you do need Odin or custom recovery.
-You may just flash NK2 and root it, which is what's explained in the guide. Again, if you really need that version of android.
Click to expand...
Click to collapse
There is a bug with the VZW version of Lollipop 5.0.1 right now that randomly affects phones. A VZW employee told me they are trying to get their build of Lollipop 5.10 fixed by September. The bootloop thing wasn't instant after I OTA updated to Lollipop, it was a gradual thing, along with my decreased battery life and back of my phone staying constantly warm. Since I have flashed back to Kit Kat I am no longer having those problems. A few weeks ago I noticed my S5 started randomly rebooting. This started happening more and more until it literally was falling into a bootloop. I tried factory reset+wipe partition cache, but that did not fix it...so that is why I ultimately got rid of Lollipop, just too many problems for me personally.
I have NK2 and towelroot does not work:
yes I tried different modstrings, yes I will stay away from VZW in the future
At this point, if nothing I suggested worked, my best guess is to flash NHA and use towelroot on it. I don't know about those w0lf kernels, you may try and report the results.
Related
So, I've been too scared to update my unbranded S4 (still on 4.2.2 stock) but it looks like this Towelroot changes the game somewhat.
So, from my understanding, if I wanted to install say, the GPE rom, this would be the process:
1) Install towelroot and root phone
2) Install a custom recovery such as TWRP
3) Install GPE rom
Does towelroot come with a recovery or do I have to install one manually (flashing via Odin?) Is Towelroot compatible with 4.2.2 or would I need to update my phone with the official OTAs? Am I right in assuming updating via the OTA installs the bootloader which comes with KNOX?
Thank you
Crosshash said:
So, I've been too scared to update my unbranded S4 (still on 4.2.2 stock) but it looks like this Towelroot changes the game somewhat.
So, from my understanding, if I wanted to install say, the GPE rom, this would be the process:
1) Install towelroot and root phone
2) Install a custom recovery such as TWRP
3) Install GPE rom
Does towelroot come with a recovery or do I have to install one manually (flashing via Odin?) Is Towelroot compatible with 4.2.2 or would I need to update my phone with the official OTAs? Am I right in assuming updating via the OTA installs the bootloader which comes with KNOX?
Thank you
Click to expand...
Click to collapse
Hi,
the steps describe are right , you need to root your phone ( step 1) , you need to install a custom recovery ( step 2 , not included in step 1) at this point your warranty will be void if you have a knox enable bootloader and finally install custom rom ( step 3)
As mention by geohot
Definitely invited: AT&T GS5, Verizon GS5, GS4 Active, Nexus 5
May have some troubles at the door but invited: AT&T/Verizon Note 3
Possibly invited: Every Android phone with a kernel build date < Jun 3
what model S4 you have , I know for sure all I9500 4.2.2 have the old bootloader so as long as you do not update the bootloader you can use any method you want to root and have no problem with knox. Confirm this for your phone and DO NOT UPDATE THE BOOTLOADER
MAX 404 said:
Hi,
the steps describe are right , you need to root your phone ( step 1) , you need to install a custom recovery ( step 2 , not included in step 1) at this point your warranty will be void if you have a knox enable bootloader and finally install custom rom ( step 3)
As mention by geohot
Definitely invited: AT&T GS5, Verizon GS5, GS4 Active, Nexus 5
May have some troubles at the door but invited: AT&T/Verizon Note 3
Possibly invited: Every Android phone with a kernel build date < Jun 3
what model S4 you have , I know for sure all I9500 4.2.2 have the old bootloader so as long as you do not update the bootloader you can use any method you want to root and have no problem with knox. Confirm this for your phone and DO NOT UPDATE THE BOOTLOADER
Click to expand...
Click to collapse
Ah sorry, here are the details for my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, apart from installing the official OTA Galaxy S4 update, is it unlikely I'll end up updating the Bootloader?
Thank you
Crosshash said:
Ah sorry, here are the details for my phone:
So, apart from installing the official OTA Galaxy S4 update, is it unlikely I'll end up updating the Bootloader?
Thank you
Click to expand...
Click to collapse
Hi ,
I am 100% sure all 4.2.2 are old bootloader ( if you want to make sure go to download mode and see if there is any knox related text)
As long as you do not do any official OTA or flashing with Odin any >4.2.2 stock rom you are knox free .
MAX 404 said:
Hi ,
I am 100% sure all 4.2.2 are old bootloader ( if you want to make sure go to download mode and see if there is any knox related text)
As long as you do not do any official OTA or flashing with Odin any >4.2.2 stock rom you are knox free .
Click to expand...
Click to collapse
Fantastic, thank you. I checked and there was nothing related to KNOX on the Download Mode screen. Guess I'll be flashing GPE now.
Thanks again
I bought a s4 from someone on Craig's list. phone looked and powered up so I paid him for it when I went to Best buy to update my account to having a S4 and not an iPhone we tried to get wifi to come on it would go lite green then turn gray same for the bluetooth. I tried find the guy I got my phone from his phone # is disconnected. long story short I found he had rooted it them wiped it back to stock. I have tried a lot of thing I searched. I tried all the file I could find. Now I have the phone rooted with saferoot with knox disabler and installed safestrap ran jfltatt-mk3-modules.zip. my baceband is NC1 but my buil is MK2. PLEASE HELP.
Thank you,
Treydawg
You could first try flashing the MK2 modem.
If the above doesnt work, download and flash using Odin the full MK2 firmware from http://forum.xda-developers.com/showthread.php?t=2616221
My Baseband is NC1 but my build number is MK2 do I flash MK2 modem or NC1 modem
I have safestrap on the phone now flash it with safestrap or odem.
sorry for all the questions
jmjoyas said:
You could first try flashing the MK2 modem.
If the above doesnt work, download and flash using Odin the full MK2 firmware from http://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
treydawg said:
My Baseband is NC1 but my build number is MK2 do I flash MK2 modem or NC1 modem
I have safestrap on the phone now flash it with safestrap or odem.
sorry for all the questions
Click to expand...
Click to collapse
On stock rom, all firmware components have the same version. So, one could say their firmware version by looking at the baseband. But, actually, the baseband is the modem. Since you build is MK2, you should flash the MK2 modem to make everything compatible.
If the file is in ".tar" or ".tar.md5" format, you flash using Odin. If the file is in zip format, then you flash it using recovery.
As per the All things ATT thread, the modems are flashable via recovery.
jmjoyas said:
On stock rom, all firmware components have the same version. So, one could say their firmware version by looking at the baseband. But, actually, the baseband is the modem. Since you build is MK2, you should flash the MK2 modem to make everything compatible.
If the file is in ".tar" or ".tar.md5" format, you flash using Odin. If the file is in zip format, then you flash it using recovery.
As per the All things ATT thread, the modems are flashable via recovery.
Click to expand...
Click to collapse
It was a zip file but didn't help. Im about to think the phone is bad and give up. I was think of doing the 4.4.2 upgrade with the wifi fix and see if that helped. whats your thoughts on my next move?
treydawg said:
It was a zip file but didn't help. Im about to think the phone is bad and give up. I was think of doing the 4.4.2 upgrade with the wifi fix and see if that helped. whats your thoughts on my next move?
Click to expand...
Click to collapse
I would flash the nb1 tar file in Odin and see if that works. If it doesn't you probably have a hardware issue.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would flash the nb1 tar file in Odin and see if that works. If it doesn't you probably have a hardware issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You will love this one. I upgrade my Rom and the phone worked (not wifi or Bluetooth) for a little bit I went to load BL, AP, CL with Oden like it told me to. Oden locked up on BL and my phone locked up saying upgrade fail connect to kies to recover something like that. I had to down grade back to MK2 reload a rom I had. But now the build is MK2 but the baseband is MLD. I was able to root it with SafeRoot but I can't load SafeStrap on it. Plus still no WiFi or Bluetooth. Don't know where to go from here. Help please!
Flash the NB1 firmware from the http://forum.xda-developers.com/showthread.php?t=2616221 thread under return to stock section. There is one version which is rootable with towelroot.
can you post your screengrab on here?
I've noticed that lately, there has been more clones that has the same issues.
Either the person who had the phone before you either attempted to flash modem and failed or it may be a clone with older firmware and newer baseband.
Also, upon the bootup, if you see the android icon instead of that Samsung logo, it might be a fake or has custom roms.
Oh, and I also encounter this same issues. You're better off flashing NB1, then updating to NC1 for root method. But if you're still on MK1, try reflashing it or try letting kies do a recovery on your phone.
Also, check the imei on swappa.com and verify that your phone isn't on the blacklist.
Ziken said:
can you post your screengrab on here?
I've noticed that lately, there has been more clones that has the same issues.
Either the person who had the phone before you either attempted to flash modem and failed or it may be a clone with older firmware and newer baseband.
Also, upon the bootup, if you see the android icon instead of that Samsung logo, it might be a fake or has custom roms.
Oh, and I also encounter this same issues. You're better off flashing NB1, then updating to NC1 for root method. But if you're still on MK1, try reflashing it or try letting kies do a recovery on your phone.
Also, check the imei on swappa.com and verify that your phone isn't on the blacklist.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since I don't have wifi and I put my sims cards in another phone I had to take a pic of the screen
I flashed the NB1 to the phone after 30 mins the wifi started working (about 2 hours) but when I was setting up my tv on watchon the wifi stopped working and has not worked since.
I checked on Swappa.com not black listed
Hey everyone. I've rooted my phone with towel root as described here. http://forum.xda-developers.com/gal...to-root-i337ucufnj4-4-4-4-11-13-2014-t2939553
I was thinking about cyanogenmod, or pure nexus. Any thoughts? I want to have a nearly pure android experience but still look good without bloatware.
Pure Nexus looked like it fit the description but the method of flashing looked like it might limit my future options.
Thoughts?
androidcortex said:
Hey everyone. I've rooted my phone with towel root as described here. http://forum.xda-developers.com/gal...to-root-i337ucufnj4-4-4-4-11-13-2014-t2939553
I was thinking about cyanogenmod, or pure nexus. Any thoughts? I want to have a nearly pure android experience but still look good without bloatware.
Pure Nexus looked like it fit the description but the method of flashing looked like it might limit my future options.
Thoughts?
Click to expand...
Click to collapse
Well you won't be able to flash cm. Pure nexus is great but yes also limited with not having a stable Dev for the ROM anymore. I actually flashed GoldFinger shortly after the pn Dev switched phones and I like it a lot. Tons of room for customization since it still has Samsung features (coming from a person that doesn't favor touchwiz). Here's a preview
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It even gets updates
Interesting, why exactly is cm not an option now? I'll look into goldeneye.
androidcortex said:
Interesting, why exactly is cm not an option now? I'll look into goldeneye.
Click to expand...
Click to collapse
Cm requires cwm/twrp. These recoveries are only accessible for using of the MDL boot loader, which is the original s4. Upgrades after that are stuck with safe strap and we can't downgrade that far. [emoji24]
Oh wow. So they have an Apple-like situation going on? So I should only look at safestrap roms?
androidcortex said:
Oh wow. So they have an Apple-like situation going on? So I should only look at safestrap roms?
Click to expand...
Click to collapse
Yep yep. All compatible Roms for us will be in the all things general thread.
So at this point I am wondering is there any roms highly favored over the rest? I'm going to look them all over but I want to hear some thoughts in here.
Also after following that rooting guide, can I simply install safestrap from my phone or do I need to flash the nc1 kernel and reroot again?
@iB4STiD is a pretty favored Dev around here it seems so all of his Roms are a pretty good bet. I haven't tried GoldenEye but I love GoldFinger because it has the touchwiz of s5. Older versions I cant hang with. @Joe-Tech is also great but he has an s5 now but I saw that he's still trying to put out builds, mainly for pure nexus so there's still some hope for that ROM.
And how about safestrap? Can it be installed on rooted nj4 or do you need to install it on nc1 first?
So while on nj4, if thats the base youre on, you'll need to be using the nc1 kernel (flashed with Odin 3.09). Which I assume you're on since you're rooted. While still on the nc1 kernel you'll flash safe strap, v3.75 b01. All of these files are in the Odin to stock thread in general in the spoiler under nj4 rooted with ss. After you have ss installed then you Odin the nj4 kernel back onto the phone.
Is that kernel ver correct?
Hmm I'm not sure. What method did you do for upgrading?
Flashed with odin
Okay if you don't recall flashing the nj4 kernel after successfully rooting on the nc1 kernel, you should still be on it. So download busy box from the play store, and install it from within the app. After make sure you have the ss 3.72 b01 apk on your phone then install that. Then you can put the nj4 kernel back on your phone with Odin. If you don't remember, flash the nc1 kernel anyway in Odin.
After all that you can flash Roms in ss. Make sure you have the nj4 modules and a download of SuperSU (to make sure you dont lose root) on your phone to flash. Only use the stock slot.
Oh and if the ss app disappears from your drawer, just install the app again from your phone.
The guide has you flash back to nj4 after you towelroot in nc1, I'm guessing I need to flash back to nc1 then install that?
androidcortex said:
The guide has you flash back to nj4 after you towelroot in nc1, I'm guessing I need to flash back to nc1 then install that?
Click to expand...
Click to collapse
No the guide is for if you're on nc1. If you were on nc1 and used Odin to get to nj4, it only sounds like you didn't complete the rest of the steps.
The Odin method has you flash the nj4 ROM and then the nc1 kernel because the nj4 kernel can't be rooted. That's why after you successfully root and get ss, you can flash the nj4 kernel. But before that you have to install SuperSU to make sure you keep root.
I followed the steps to a t and got root with the method I linked to in the original post.
Bootloader readout.
So if you're only without safe strap, get busy box from the play store and install fully. Then the correct version of safe strap just because its stable, and you should be in business to flash compatible Roms.
Hi,
I'm a new Samsung Galaxy S5 user, I have a S5 SM-G900F model running Lollipop stock rom with G900FXXU1BNL9 baseband version, LRX21T.G900FXXU1BNL9 build number and Knox 2.3, i want to know how to root and flash a custom rom without tripping Knox counter (0X0).
Help please...
No method yet, only downgrading to KK
I don't believe there is a way right now. Towelroot will usually do it but your build date is most likely too new. You can wait till its updated to work with your phone or trip the counter ?
Although I could be wrong.
Sent from my SM-G900W8 using Tapatalk
Towelroot only works with KK builds, and they have to be dated prior to June 2014 iirc
The dev of Towelroot "Geohot" works for Google now too, so.... updating it, maybe not
Thx guys for your replies...so the only way is to downgrade to KK, right? How to do that?
Grab a stock KK ROM for your model S5 from sammobile, flash using ODIN
Instructions are on the ROM download page and scattered around XDA in most threads
*Detection* said:
Grab a stock KK ROM for your model S5 from sammobile, flash using ODIN
Instructions are on the ROM download page and scattered around XDA in most threads
Click to expand...
Click to collapse
So...i only have to download a rom from SamMobile and flash thru Odin? How to know which the correct one to download?
You enter your phone make, model and country/region into the search panels
For example, this is for mine:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloading the stock 4.4.2 rom for my model, after i flash the rom thru Odin, can i root with towelroot app and supersu? And after root can i flash a custom rom without trigger knox?
Flashing Stock ROM = KNOX 0x0
Flashing Custom ROM / Recovery = KNOX 0x1
You can root with Towelroot if the ROM you are flashing is from before June 2014 iirc
Then yes you can install SuperSU
*Detection* said:
Flashing Stock ROM = KNOX 0x0
Flashing Custom ROM / Recovery = KNOX 0x1
You can flash with Towelroot if the ROM you are flashing is from before June 2014 iirc
Then yes you can install SuperSU
Click to expand...
Click to collapse
Nope is from September...
Then towelroot won't work
You either need a build from before that date, or flash the kernel of a build from before that date, root, then flash back your original kernel
Don't know where to get those files from, but plenty of threads with people posting links kicking about, if I find any I`ll post them - but you'll likely need to request the specific version for your ROM
*Detection* said:
Then towelroot won't work
You either need a build from before that date, or flash the kernel of a build from before that date, root, then flash back your original kernel
Don't know where to get those files from, but plenty of threads with people posting links kicking about, if I find any I`ll post them - but you'll likely need to request the specific version for your ROM
Click to expand...
Click to collapse
But if I flash a rom from June?
hXc71 said:
But if I flash a rom from June?
Click to expand...
Click to collapse
I ask the same question. [emoji14]
hXc71 said:
But if I flash a rom from June?
Click to expand...
Click to collapse
Then you should be able to root with towelroot fine without flashing any other kernels - it's ROMs built after then that is the issue
hXc71 said:
But if I flash a rom from June?
Click to expand...
Click to collapse
Sorry for the late reply, but you may flash the latest kitkat fw, than an older kernel compatible with towelroot, than root, than reflash the current kernel and you're done!
Knox 0x0 and root enabled
downgrading to kitkat didnt helped < july
I tried all the things but didnt worked
flashed earlier build of kernal and tried
flashed whole rom (early build. First KK rom)
None of them worked for me
well i am a G900H user. I dun think theres exception for exynos varients.
There seems to be some disagreement over what I am about to type.......but this is what I've read about several times........
Downgrading from Lollipop back to KitKat *may* not work........
The Lollipop builds seem to include enhanced security (in the bootloader or kernel.....or somewhere like that) which remains in place even if the phone is flashed back to KitKat. This enhanced security 'patches' the exploit that Towelroot took advantage of, rendering the app ineffective for rooting EVEN IF the compatible kernel or firmware is flashed. Basically, once Lollipop is on your phone, Towelroot won't work no matter what you do to try to get around it.......
As I said, this is only information that I've read, and I *might* have misunderstood......but there it is.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I stumbled across this file on the net and thought I would give it a spin.
I was on Firmware N910VVRU2CPF3 dated June 2016
I flashed the "Combination file" using Odin 3.10.7
COMBINATION_VZW_FA44_N910VVRU2APB1_VZW2APB1_2932719_REV00_user_mid_noship_MULTI_CERT.tar.md5
I then flashed N910VVRU2BPA1 firmware from here
It worked and now I am on 5.1.1
I wanted to go lower but, because of the Binary being fused at 2, I was unable.
Perhaps someone can find a way to get back to 4.4.4 with this so we can root with CF Auto Root.
For those that might be confused on how to use this..
1. Place your phone in Download mode
2. Open Odin on your PC, select the AP button, and then select the combination file that you just downloaded..
3. After install the phone will reboot and it will be in a Factory repair or test mode.. feel free to tinker and explore.
4. Power off your phone and go back to download mode.
5. Go back into Odin and flash your desired firmware which would be 5.1.1 and above.
captaingowa said:
I stumbled across this file on the net and thought I would give it a spin.
I was on Firmware N910VVRU2CPF3 dated June 2016
I flashed the "Combination file" using Odin 3.10.7
COMBINATION_VZW_FA44_N910VVRU2APB1_VZW2APB1_2932719_REV00_user_mid_noship_MULTI_CERT.tar.md5
I then flashed N910VVRU2BPA1 firmware from here
It worked and now I am on 5.1.1
I wanted to go lower but, because of the Binary being fused at 2, I was unable.
Perhaps someone can find a way to get back to 4.4.4 with this so we can root with CF Auto Root.
For those that might be confused on how to use this..
1. Place your phone in Download mode
2. Open Odin on your PC, select the AP button, and then select the combination file that you just downloaded..
3. After install the phone will reboot and it will be in a Factory repair or test mode.. feel free to tinker and explore.
4. Power off your phone and go back to download mode.
5. Go back into Odin and flash your desired firmware which would be 5.1.1 and above.
Click to expand...
Click to collapse
I'm pretty sure you can just use the BPA1 firmware to downgrade without flashing the "Combination file".
weard1212 said:
I'm pretty sure you can just use the BPA1 firmware to downgrade without flashing the "Combination file".
Click to expand...
Click to collapse
Perhaps ?
I have seen several warnings not to take any updates past a certain date on Android 6.0.1, otherwise you cannot go back, as the newer firmware prevents any downgrading in lieu of "security patch".
The Combination file enables you to install any firmware or newer than its specific binary.
In running this you will notice a bare bones KitKat 4.4.4 AOSP UI.
The Binary is fused for loading only firmware that includes KNOX, as it was first introduced as of 5.1.1 for the SM-N910V
Which is my belief why it is such a secret to go back.
captaingowa said:
Perhaps ?
I have seen several warnings not to take any updates past a certain date on Android 6.0.1, otherwise you cannot go back, as the newer firmware prevents any downgrading in lieu of "security patch".
The Combination file enables you to install any firmware or newer than its specific binary.
In running this you will notice a bare bones KitKat 4.4.4 AOSP UI.
The Binary is fused for loading only firmware that includes KNOX, as it was first introduced as of 5.1.1 for the SM-N910V
Which is my belief why it is such a secret to go back.
Click to expand...
Click to collapse
unnecessary ! you can flash back to lollipop(5.1.1 bpa1) with Odin without the need of this binary and Knox hit the scene on jellybean final bud (4.3)
@mojoswagger1980
Please show me 4.3 firmware for the SM-N910V
The Verizon Note 4 Jumped from 4.4.4 to 5.0.1 then to 5.1.1
Per Samsung the update from 5.0.1 to 5.1.1 installed Knox on the SM-N910V.
This Binary is very useful ..
But glad to know you don't like that I posted it.
Lol the sm 900v (note3) premiered on 4.3 essentially the same phone seriously. For the record you said Knox kept us from downgrading as of lolipop I then corrected that statement with mine . device model firmware doesn't apply given that Knox was universaly added to all android devices at that time
I downgraded successfully using BPA1 from the newest firmware just this last week. No issues or conflicts and rerooted/bootloader unlocked...easypeasy
please elaborate
Oh_wow said:
I downgraded successfully using BPA1 from the newest firmware just this last week. No issues or conflicts and rerooted/bootloader unlocked...easypeasy
Click to expand...
Click to collapse
can you list details of how you did this and what version you were on before downgrade, thanx
i have followed the instructions but it keeps failing. any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
drsuse said:
i have followed the instructions but it keeps failing. any ideas?
Click to expand...
Click to collapse
Check to make sure you are not using a USB3 port. I always have issues with USB3.
Those of you that have downgraded back to 5.1.1. I have a question for you.
While on 6.0.1, did you have problems with your GPS with it losing signal? IF SO, did downgrading back to 5.1.1 solve this problem?
I've been having problems with my GPS for quite awhile now and I can't figure out if the problem is related to 6.0.1, loose screws or oxidation of the contacts inside of my phone.
Know what? I think all my laptop usb are usb3. I'll try my older laptop and let you know
i needed a pit file for the note 4 vzw i added that and erased the partition via odin and now im flashing 5.1.1 no errors this time
Anyone try this with build number: MMB29M.N910VVRS2CQB2 ????
Balian67 said:
Anyone try this with build number: MMB29M.N910VVRS2CQB2 ????
Click to expand...
Click to collapse
I need to know this tooo
thegiant_2 said:
I need to know this tooo
Click to expand...
Click to collapse
I got it to work. Don't go doing anything just yet. I plan to make a new topic about it.
Balian67 said:
I got it to work. Don't go doing anything just yet. I plan to make a new topic about it.
Click to expand...
Click to collapse
So, this method won't work???
thegiant_2 said:
So, this method won't work???
Click to expand...
Click to collapse
yes it worked for the build number I was on. Which is up in my other comment. Be careful, follow the directions closely
JOSHSKORN said:
, did you have problems with your GPS with it losing signal? IF SO, did downgrading back to 5.1.1 solve this problem?
I've been having problems with my GPS for quite awhile now and I can't figure out if the problem is related to 6.0.1, loose screws or oxidation of the contacts inside of my phone.
Click to expand...
Click to collapse
GPS Signal I believe is hardware related and I have that problem as well..
This appears to be the most feasible approach to fixing it and I will be attempting this shortly as it is not the same phone model but possibly the same cause for the issue.
https://forum.xda-developers.com/showthread.php?t=1973727
Trying to downgrade as well and having the same issues.... cannot flash anything without it failing. The only firmware that worked was the combination one and nothing else. Please help! Thanks!