Database Info

[GUIDE] Root and Unlock Canadian i337M without tripping Knox

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.

HELP! SM-G920i TWRP Issue

Hi Guys,
I've got an S6 Australian SM-G920i version. Done the root option and done the twrp recover flash in odin however i keep getting stuck at Samsung Logo. Tried root first and then flash twrp that didn't work, tried twrp first then tried to boot to recovery to root from twrp and still no go. teamwin says it compaitible with SM-G920i version tried TWRP 2.8.6.0 and TWRP 2.8.6.2 still no go.
Please help if any of you know of a work around.
Thanks in advance

Hello hoglak
I have a 920I and was also having the same problem.
I solved the problem flashing the latest version of the rom from SamMobile site.
After flashing the rom your TWRP should work.

Tbnitz said:
Hello hoglak
I have a 920I and was also having the same problem.
I solved the problem flashing the latest version of the rom from SamMobile site.
After flashing the rom your TWRP should work.
Click to expand...
Click to collapse
Can you tell me which specific rom you tried i downloaded latest I can find for Aus rom but still having the same issue. Any chance give a step by step guide on what you did exactly.
Thanks in advance

I just used the New Zealand firmware.

I am from Brazil and with the orginal rom the same thing happened, im flashed the generic one and worked.
This one seems to be the general rom to Australia
http://www.sammobile.com/firmwares/database/SM-G920I/XSA/
But i used the zto version from Brazil

hoglak said:
Hi Guys,
I've got an S6 Australian SM-G920i version. Done the root option and done the twrp recover flash in odin however i keep getting stuck at Samsung Logo. Tried root first and then flash twrp that didn't work, tried twrp first then tried to boot to recovery to root from twrp and still no go. teamwin says it compaitible with SM-G920i version tried TWRP 2.8.6.0 and TWRP 2.8.6.2 still no go.
Please help if any of you know of a work around.
Thanks in advance
Click to expand...
Click to collapse
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.

d2d2d2d2 said:
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.
Click to expand...
Click to collapse
I'll give this a go tonight hopefully it will work.
Thanks mate

d2d2d2d2 said:
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.[/QUO
Thanks mate that worked perfectly.
Click to expand...
Click to collapse

OTA OC3

If I use Odin to flash this(which should be last OTA) can I then root with PingPong?
ALL_VZW_G920VVRU1AOC3_G920VVZW1AOC3_CL4318389_QB4424773_REV02_user_low_ship.zip
Also is there just an update file I can flash instead?

I just rooted OE2 with ping-pong so your all good!

And now you can't flash an update file

You can't flash an update when rooted, but the Verizon Update Assistant software, or Samsung's neW KIES replacement software (can't remember the name) you can flash a new update and wipe phone like new, so you lose nothing by rooting!
I was rooted in Stock firmware and now I'm on the latest firmware and rooted!

Bricked the S6 SM-920I. I'm at wits' end.

I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:

Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.

Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!

ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.

ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin

1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?

Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq

ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.

Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:

1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.

Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.

ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.

Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!

ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good:

Flashing Stock 6.01 (PG1) from sammobile, the device wont boot post install

Hello everyone, I need some help here.
I downloaded the latest from sammobile
G900PVPU3CPG1_G900PSPT3CPG1_G900PVPU3CPG1_HOME.tar .md5
and ODIN v3.12.3
I placed the tar file in the AP slot, installed everything, I receive the final okay and the phone reboots to the stock samsung boot animation, and just sits.
Does anyone have any idea why I can't seem to get past the boot animation?
I can pull the battery and install TWRP, and boot to recover fine, but no matter how long the device will NOT get past the boot animation.
Is it possible that I have a bad download? Can I "downgrade" to PE2, without risk of bricking the device somehow?
thanks

Before clicking Start on odin, did you uncheck everything else (autoreboot, f-reset time, re-partition)? I followed all the steps here for that same firmware. It worked for me on first try. Also, did you download the appropriate version for your phone? From what I can see there are 4 versions on sammobile, VMU, SPR, XAS, and BST. I have a Virgin mobile phone, so i got the one with product code VMU.

welp I went back to old tried and true V3.09 and used PE2, and then let it boot after a LONG TIME. Then I upgraded to PG1 using the update feature in "about device".
Not sure why I could not use the latest PG1 tar file, direct from sammobile.
Curious though, has anyone been able to "downgrade back to lollipop, just in case? Or has Samsung locked it down.
I tried to go back to OA6, and also OK4 and I got a fail (red) in ODIN using both sammobile stock files.

Amd4life said:
welp I went back to old tried and true V3.09 and used PE2, and then let it boot after a LONG TIME. Then I upgraded to PG1 using the update feature in "about device".
Not sure why I could not use the latest PG1 tar file, direct from sammobile.
Curious though, has anyone been able to "downgrade back to lollipop, just in case? Or has Samsung locked it down.
I tried to go back to OA6, and also OK4 and I got a fail (red) in ODIN using both sammobile stock files.
Click to expand...
Click to collapse
You may have to boot into recovery and factory reset once ODIN has successfully flashed. Should boot after that.
Sent from my SM-G900P using XDA-Developers mobile app