Related
Tested on my Canadian i337M S4 (4.4.2 MVLUFNI2 firmware). Knox was not tripped.
This may work on other S4.
Summary of the Steps:
- Downgrade to special Kernel from W0lfdroid
- Root with TowelRoot
- Flash back 4.4.2 Kernel
- Downgrade to 4.2.2 Modem
- Unlock with RegionLock Away v1.3
- Flash back 4.4.2 Modem
Detailed Steps:
-=FILES REQUIRERD=-
Download these ROMs from SamMobile:
4.2.2 rom for your phone
- Use 7zip to extract MODEM.BIN from it
4.4.2 rom for your phone
- Use 7zip to extract MODEM.BIN from it
- Also use 7zip to extract BOOT.IMG (this is the Kernel), and archive it as a tar file.
-=ROOT=-
Follow this method:
http://www.w0lfdroid.com/2014/09/To...4-S5-and-Note3-Android-4.4.2-NF-or-Later.html
Important: for flashing back the Kernel, the 4.4.2 file from that site may not work properly (causes wifi to behave weird). You need to use the boot.img tar you made earlier.
-=UNLOCK=-
1. Put S4 into download mode by holding Volume Down and Home Button on startup, then press Volume Up
2. Attach Phone using USB cable
3. Start Odin
4. under the Files [Download] section 3rd button (Phone) point to the 4.2.2 modem.bin
5. click on start
6. --- After phone reboots, check it installed correctly by verifying the baseband version is the same as the one you just flashed
7. Once successful run RegionLockAway
8. Next you must install proper modem back using Odin
9. Start Odin
10. under the Files [Download] section 3rd button (Phone) point to the 4.4.2 modem.bin
11. click on start
12. --- After phone reboots, check it installed correctly by verifying the baseband is the same as the one you just flashed
Using Heimdall on Linux to flash stock ROM and getting everything back to original tripped KNOX for me.
Everything was done properly and ROM worked perfect. Oh well.
Tip: (lol)
When flashing stock firmware back to device stick to Windows stock ROM flashing methods. (Odin)
Wish I would of found this info a few weeks ago. niCCe!
ngold thanks
I have a phone from a guy at work it is a Rogers phone KNOX is already tripped the phone is rooted and on 4.4.2 MVLUFNI2 firmware can I still use your unlock method?
And if so which 4.2.2 firmware did you use on Sammobile I don't see any Canadian firmware listed for 4.2.2.
Do you have a link to the RegionLockAway is it just the 1.3 version I'm finding for the Note 3?
stdly said:
ngold thanks
I have a phone from a guy at work it is a Rogers phone KNOX is already tripped the phone is rooted and on 4.4.2 MVLUFNI2 firmware can I still use your unlock method?
And if so which 4.2.2 firmware did you use on Sammobile I don't see any Canadian firmware listed for 4.2.2.
Do you have a link to the RegionLockAway is it just the 1.3 version I'm finding for the Note 3?
Click to expand...
Click to collapse
Yeah you can use this method if KNOX is already tripped. (or you can just use CF-Autoroot as it saves some hassle)
To unlock, the firmware I used was VLUAMDJ . On Sammobile, you'll see it if you filter by Canada (Rogers).
For Regionlock Away 1.3, yes you can use the one posted in the Note 3 forum - http://forum.xda-developers.com/showthread.php?t=2470551
ngold said:
Yeah you can use this method if KNOX is already tripped. (or you can just use CF-Autoroot as it saves some hassle)
Click to expand...
Click to collapse
Thanks ngold,
Will CF-Autoroot unlock the phone it is already rooted?
stdly said:
Thanks ngold,
Will CF-Autoroot unlock the phone it is already rooted?
Click to expand...
Click to collapse
No CF-Autoroot only roots the phone. It trips the Knox, but it's easier. So if you already tripped Knox, that's the best method to root.
ngold said:
No CF-Autoroot only roots the phone. It trips the Knox, but it's easier. So if you already tripped Knox, that's the best method to root.
Click to expand...
Click to collapse
Thanks dude it worked I was worried because I didn't have a working sim card in it but no problems.
I can't flash the modem, bootloader locked?
download what roms? links?
If the phone has a 4.3 or newer bootloader, the phone can't be rooted without tripping knox as far as I know.
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
cd2xtac said:
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
Click to expand...
Click to collapse
On OK3 the bootloader is locked. You cannot downgrade to 4.4.2 or 4.4.4 or any other previous version. You also cannot install custom recoveries like ClockworkMod or TWRP. You are relegated to Safestrap or FlashFire as discussed in jrkruse's threads.
You can ONLY use SafeStrap. TWRP and Clockworkmod cannot load because we have a locked bootloader.
You must flash a kitkat kernel to boot into safestrap, which I gather you didn't do. Then when you're done in Safestrap, flash a safestrap-flashable lollipop kernel BEFORE EXITING SAFESTRAP to boot back into your ROM.
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
cd2xtac said:
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
Click to expand...
Click to collapse
You will remain tied to OK3
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Dudash said:
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Click to expand...
Click to collapse
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
jrkruse said:
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
Click to expand...
Click to collapse
Thanks for clarifying
What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?
GoodLooks550 said:
What is the most stable stock android version? Kitkat or Lollipop?
My phone is currently on NE9 and want to optimize my phone to be the best with what's out now, especially since development will be dwindling. It seems that Lollipop does not run too well (high battery usage?), according to what I see on the threads. Without any input, I would update to NK2 and then towelroot. However, would anyone recommend me updating to BOK3 or BPB1?
Click to expand...
Click to collapse
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.
painiac said:
They're both stable, but we do see a lot of complaints about lollipop battery life.
Try it for yourself. Just stick with jrkruse's stock lollipop images that don't update the bootloader past BOD5, or any ROM that specifically does not update the bootloader. Then you can easily downgrade back to kitkat if you decide you don't like it.
Click to expand...
Click to collapse
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?
GoodLooks550 said:
Thanks, painiac! I used your guide to get up to date with the S5, btw--things are very different from what I remember in the S4 world.
Click to expand...
Click to collapse
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
GoodLooks550 said:
Anyway, after rooting and installing safestrap, if i were to flash jrkruse’s BPB1 Rom (http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029), I would install the rom, safestrap fix, patch (optional), and BPB1_Firmware_No_Bootloaders.zip. Anything else to add?
This set up would allow me to go back to kit kat by installing a jrkruse kit kat rom and related firmware w/o bootloader?
Click to expand...
Click to collapse
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.
painiac said:
Glad I could be of service. I came here just a few months ago from an S3. Imagine my disgust and shock... That was actually the impetus for writing that guide, because there's so much to have to learn and I'd just finished researching the crap out of it all for myself in a short amount of time.
Click to expand...
Click to collapse
I was lucky to have my an S4 MDK (unlocked bl), so things were much simpler back then--had an S3, as well. In the process of getting my S5 running the way I wanted, the use of safestrap was completely new to me. Thankfully, some heavy browsing of the forums got me through. I did not use flashfire, which would have been something else to learn!
painiac said:
Nothing else to add, I think you got it. That no bootloaders firmware file you selected is the important one.
jrkruse says you can still run kitkat ROMs even if you're stuck with Lollipop, but I haven't tried it yet. Staying with the BOD5 or earlier bootloader actually allows you to flash KitKat stock image files with Odin, which you cannot do without bricking if you've updated your bootloader to BOE1 or later. I like this because the KitKat root process is a lot less problematic than the new Lollipop root method; but more importantly, you can freely upgrade to Lollipop with BOD5 bootloader (modified) stock Odin images, and then you can freely downgrade with stock KitKat Odin images.
Click to expand...
Click to collapse
Thank you--your replies and guide were gold in terms of figuring it all out.
For onlookers of this thread, once you get to lollipop, it's hard to go back to kitkat. A lot of the small details really add up to an improved user experience. Also, having an s7 edge, the PB1 build on the S5 has 90% of the same functionality of the S7e--excluding edge-related features, of course.
To summarize my upgrade experience:
Root from any kitkat rom: Flash the NCG kernel in odin (AP/PDA), reboot and root with towelroot apk, and then install and update supersu; and lastly re-flash the NE9 kernel.
Install Hashcode's version of Safestrap: Install busybox apk. Install safestrap apk (version 3.75). Make sure to use a microsd card for installation, as recommended.
Install PB1 rom: (source: http://forum.xda-developers.com/verizon-galaxy-s5/development/vzwstock-based-tw-rom-3-4-16-t3329029). Reboot into SS. Flash G900V_Fix Safestrap.zip. Reboot into SS. Flash:
VZW_BPB1_ODEX_DEODEX_V9.zip,
Extra_toggles.zip (optional),
BPB1_Firmware_No_Bootloaders.zip , and
G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip.
Flash all in a single queue. Reboot into download mode and flash G900V_OD5_Bootloader.tar.md5 in odin. Reboot. Wait. (NOTE: for more customization, before installing rom, unzip rom. Edit the options.prop in text editor to your likeing. Rezip original contents with updated options.prop. Flash this zip as the rom file)
To get back into safestrap/recovery: Make sure hashcode's version of safestrap is installed. A lollipop safestrap will be installed--don't use it. Also, install NI2Flasher.apk (this flashes a kitkat kernel, which will allow you to get back into the kitkat safestrap). Reboot into safestrap. IMPORTANT: When complete with whatever is being done in SS, flash G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip to get back into lollipop rom.
Install xpose modules: This allows the essential greenify app (HIGHLY RECOMMENDED) to run to maximum potential. Gather following files:
1. APK: Xposed Installer 3.0 alpha4 (comes with some roms)
2. Flash in SS: Framework: xposed-v75-sdk21-arm-arter97-snapdragon.zip
3. Flash in SS: Uninstaller: xposed-uninstaller-arter97.zip
Since the rom I installed did not come with xposed installed. I flashed the framework in SS (look above to properly access and leave SS). Reboot. Install the APK. Reboot. Highly recommend installing Wanam's modules for lollipop--tons of modifications.
Unbrick: Get into download mode and flash: Full Wipe G900V_Downgrade_to_NCG.tar . (This helped me a ton until I realized that safestrap for the S5 does not work with rom-slots. Use the stock slot to do all flashing)
I gathered all this information from various threads, and hope this helps (highly recommend reviewing painiac's guide before starting anything - http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848). I am no expert, but this is what worked for me--please correct me if I'm wrong at any step. I believe the way I set this up, I should be able to get back to a kitkat rom, if I ever wanted to (easiest way to do this would be to flash the unbrick file). I hope this can help at least one person, since I know I'm not the only person to recently get an S5 due to someone else in the family upgrading to the S7.
Need some guidance in setting up root and Rom on my s5. Never done this before on a Verizon phone so if anyone can help I'd appreciate it
I have just bought an S6, finally moving from LG G3 (where things were simpler to root).
I have spent a few hours reading about the possibilities of rooting, flashing whilst not tripping Knox and have a few queries regarding some of the procedures.
I am lucky enough to be on 5.0.2 (G920FXXU1AOCV) which is supported by PingPong root method and Kingroot. I would like to upgrade to Marshmallow without tripping Knox and therefore keeping my warranty.
I am just querying the steps required to do this, I am of the understanding that these are the steps:
1. Root with PingPong
2. Flash TWRP via Odin/Flashfire
3. Flash whichever marshmallow related rom, kernel, mods, xposed framework etc I desire through TWRP (or is Odin/flashfire the only method that doesn't trip Knox)?
Will root remain after flashing marshmallow?
Will I need to change the bootloader at all?
before flashing a marshmallow rom, you have to get the latest bootloader. i don't know if there is another way than flashing it through odin. using this method you lose your root.
also, if you install a different kernel, it's most likely to lose root too.
and with xposed, you need a deodexed firmware at the moment. it's recommended to install a deodexed rom with a clean install. i think, you'll lose root, too.
If you flash TWRP or custom kernel via any method (TWRP, Flashfire, Odin vs), knox will be tripped.
There's NO way to use 6.0.1&root without tripping Knox.
Please forgive if i'm posting incorrectly, have been a lurker for a while
I have a Samsung s6 G920F variant, locked onto o2 (UK network) I believe the bootloader is locked also.
I was on Lollipop (with pingpong root) and recently upgraded to Marshmallow 6.1, so my root is obviously gone, and it doesn't seem that there's root right now that works.
I really want to try out the XtreStoLite rom, theoretically could i flash this rom via odin, since its TW based, would it load on without root, and with locked bootloader? I don't really care about Xnox tripping, but I definitely don't want to brick the phone... I'm not sure if the XtreStoLite rom would count as 'stock based' therefore being recognized by the phone as an official operating system? If that sounds correct.
http://download.chainfire.eu/supersu
Link to root your phone correctly.
And Yes you can flash xtrastolite with a custom recovery and without root .
Agreed. ROM has root already. Since you're already on MM, don't flash BL and modem, just ROM & optionally addon. Note that if you replace the stock kernel, you'll probably lose root.
Sent from my SM-G920W8 using Tapatalk
If you lose it, just flash the zip below again
hasnunl said:
If you lose it, just flash the zip below again
Click to expand...
Click to collapse
Thanks!