Related
Thanks to @spyke555 for his backup copy of the Rogers version of the SGH-I257M firmware. I managed to root it with vroot, so there is a chinese version of SU on there but it works. I also stuck busy box on it and tried to get rid of most of Rogers apps.
Now to use this, you must stick it into your backup folder (i.e: clockworkmod/backup) it is NOT a flashable rom, it is a backup. If anyone wants to turn it into a flash rom, or create custom roms out of it, please do. Need to see some I257M roms popping up.
Dropbox
Box.com
G Drive
We also have @dsavard copy of the stock firmware from Koodo, which you can flash with Odin
Dropbox
Mirror 1
And here we have all of the STOCK and UNROOTED firmware for the Canadian I257M over at Sammobile
All vroot does is give root access without changing the rom. It uses the chinese program Superuser 1.0.4. You can get rid of this by following these steps:
Go to play store and install SuperSU.
Start SuperSU and you will be asked for permission by Superuser 1.0.4, choose 允许(means allow). (Should be the right side option.)
SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
Now, freeze Superuser 1.0.4 in titanium backup, just in case you need it again.
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
After that, you are rooted with SuperSU and Superuser 1.0.4 will not be there anymore.
Once you do that, SuperSU will be the default and will be in english.
Good to see this here. I just picked up my S4 Mini today. I'm from Canada so I'm assuming it's a slightly different version than the other models? Cause mine in an SGH-1257M. Is it a different process to root it?
I'm not too familiar with vroot. My last phone was an HTC Evo 3D.
Skyty said:
Good to see this here. I just picked up my S4 Mini today. I'm from Canada so I'm assuming it's a slightly different version than the other models? Cause mine in an SGH-1257M. Is it a different process to root it?
I'm not too familiar with vroot. My last phone was an HTC Evo 3D.
Click to expand...
Click to collapse
vroot is like SRS or any other one touch root program, but it's in chinese. Easy to use and has a high success rate for most phones. the I257M is slightly different from what we can tell from the other models; different features. As far as I can tell there isn't a different way to root this but I'm not to sure how the others were rooted. I also don't know if there is anything different between the Bell, Rogers, Fido, etc. versions besides their own bloatware. I hope I can get all the different versions uploaded.
Omega2513 said:
vroot is like SRS or any other one touch root program, but it's in chinese. Easy to use and has a high success rate for most phones. the I257M is slightly different from what we can tell from the other models; different features. As far as I can tell there isn't a different way to root this but I'm not to sure how the others were rooted. I also don't know if there is anything different between the Bell, Rogers, Fido, etc. versions besides their own bloatware. I hope I can get all the different versions uploaded.
Click to expand...
Click to collapse
Yeah, I have a Rogers phone. Just got it yesterday.
Is there a guide on here how to root with vroot? I'm not too good at rooting and whatnot. I've only done it once on my Evo 3D and that was more than a year a go haha!
Just google it. The vroot forum has step by step with pictures
Sent from my SGH-I257M disguised as a GT-I9195
hey can someone help me?
i have a telus version and i would like to back mine up and post an image for you guys. we can then update the first post with the different carrier versions if we ever need to go back to stock for warranty purposes. i'd also like to see if there are different files from the carriers.
Omega2513 said:
Just google it. The vroot forum has step by step with pictures
Sent from my SGH-I257M disguised as a GT-I9195
Click to expand...
Click to collapse
Will do!
Edit: So I found this post:
http://forum.xda-developers.com/showthread.php?t=2455822
It mentions select the drivers for your phone? Is the S4 Mini supported?
infamouskid said:
hey can someone help me?
i have a telus version and i would like to back mine up and post an image for you guys. we can then update the first post with the different carrier versions if we ever need to go back to stock for warranty purposes. i'd also like to see if there are different files from the carriers.
Click to expand...
Click to collapse
There are forums here on how to temporarily give root and install CMW to make a backup.
Well, I just rooted my phone using VROOT. It is still recognized as an SGH-I257M. However, when any of my apps update it's all in Mandarin (I think?). Would I simply use the backup you posted? Would that solve that issue?
Will the I9195 roms work with phone even though I didn't root it as a I9195?
Skyty said:
Well, I just rooted my phone using VROOT. It is still recognized as an SGH-I257M. However, when any of my apps update it's all in Mandarin (I think?). Would I simply use the backup you posted? Would that solve that issue?
Will the I9195 roms work with phone even though I didn't root it as a I9195?
Click to expand...
Click to collapse
All vroot does is give root access without changing the rom. It uses the chinese program Superuser 1.0.4. You can get rid of this by following these steps:
Go to play store and install SuperSU.
Start SuperSU and you will be asked for permission by Superuser 1.0.4, choose 允许(means allow). (Should be the right side option.)
SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
Now, freeze Superuser 1.0.4 in titanium backup, just in case you need it again.
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
After that, you are rooted with SuperSU and Superuser 1.0.4 will not be there anymore.
Once you do that, SuperSU will be the default and will be in english.
You can use the backup that I posted but it would be the same as your stock rom. The backup is just for those who don't want to root their own rom, doesn't trust the program, etc. The I9195 roms will still work, but when you flash them, your phone will recognize itself as a GT-I9195 instead of SGH-I257M
Sorry for bumping this, but I wanted to ask, did you have any trouble installing CWM after you rooted with VROOT?
It keeps telling me that SGH-I257M is unsupported.
What I did was use the I9195 rooting method to get CWM installed then switch back with I257M backup. It turns your phone back to I257M but CWM stays installed. You could also try installing twrp
Sent from my SGH-I257M disguised as a GT-I9195
Omega2513 said:
What I did was use the I9195 rooting method to get CWM installed then switch back with I257M backup. It turns your phone back to I257M but CWM stays installed. You could also try installing twrp
Sent from my SGH-I257M disguised as a GT-I9195
Click to expand...
Click to collapse
Ah... that's why I'm having issues. I'll look into TWRP.
Edit: Just tried TWRP. No luck.
It wouldn't backup my ROM. Just booted me into recovery with no option of backing up.
Edit #2:
Slowly figuring this out. I unrooted my phone and re-rooted with the I9195 method. I now have CWM.
What I think it is, the I9195 method unlocks the bootloader where just rooting the I257M doesn't do that
Sent from my SGH-I257M disguised as a GT-I9195
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
dsavard said:
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
Click to expand...
Click to collapse
Hmm... good to know... thanks!
I unrooted my phone and re-rooted via the I9195 so I could get CWM. Hopefully it removed anything that VROOT left.
dsavard said:
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
Click to expand...
Click to collapse
Thanks for the info. I didn't realize that was possible
@Omega2513 As a safer alternative, why not install the S4Mini_RootKit_v1.zip from arco68 (http://forum.xda-developers.com/showthread.php?t=2364980) from CWM Recovery ? It is the same for all s4 mini (I9190, I9192 and I9195), so I suppose it will work for the SGH-I257M too.
It's possible it could work. Never tried it, but since it does the other models, I don't see why not.
Sent from my SGH-I257M disguised as a GT-I9195
I've got a backup of the latest Koodo SGH-I257M stock firmware [MK5 (KDO)]) by following this recipe:
http://forum.xda-developers.com/showthread.php?p=23188887
I've uploaded it online for anyone who could need it :
[EDIT: Download not available anymore. Anyway the firmware is now available on Sammobile.]
It seems to be in the same format than firmwares found on the sammobile web site. So, it could be useful for those who wish to revert to stock with Odin... and know how to do it.
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app
Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk
Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.
i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot
re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app
Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.
cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2
Hello.
I have a towel rooted VZW Note 3. I'm trying to install the update but it keeps giving me a error message. Currently I have used the super Su and selected full unroot. And it still has the saresults. Any help would be great.
Chris
[email protected]
I'm in the same boat.. initially did towel root to get CM installed but my laptop wouldn't run Heimdall due to a dll issue I couldn't work out, so I never used root access. The update notification has been super pushy and obnoxious for several weeks now. I didn't realize SU had an unroot option but it looks to be moot?
EDIT: I went into SU and tried the unroot option. It gave a message about some kernals possibly rooting on their own again on boot so after SU closed I chose to start the software update now thinking it would go and do it's thing before the kernals could.... and it worked to upgrade it to 4.4.4
Maybe this needs some testing before I'd recommend it safely as I don't have an understanding of these things like I used to... I didn't even try to make a backup FFS
I'll give that a try thx
Sent from my SM-N900V using XDA Free mobile app
Before I start, my current setup is
Model # Z012DC, Buildnumber: 20.20.1703.38-201704010(Latest update) and rooted successfully using https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926. (I have 3-1-0 TWRP instead of 3-0-2, and used lazy flasher instead of no verify). Bootloader was unlocked via official bootloader unlocker.
Some apps do not work for some reason post root. For example, I use root explorer but when it loads, it just shows blank and after a short while it says it's not responding and I have to close it. The apps I have is genuine and purchased from google play.
Quite a few apps that read/write files in certain scenarios seem to freeze/crash the app after the app is opened.
I have done factory reset to make sure there weren't any other unknown variables.
Coincidentally, if I run root explorer or any other app I have problems with right after a factory reset(pre-root) the app loads up successfully and works just fine(though it shows that certain sections can't be accessed because it needs to be rooted but this is normal.) but it stops working after the root.
I'm trying to figure out if there's something wrong with the actual root process itself, or if there's some issues in regards to the latest firmware or something else entirely.
Any suggestions/inputs are welcome.
I had the same issue with root explorer, but I corrected it by factory resetting and re-installing root from this thread https://forum.xda-developers.com/showthread.php?t=3569926. Maybe it has to do with you using lazy flasher and not following the guide. Worth a shot?
Edit: I jinxed it, latest update caused the same issue again. You're probably right, we need a root v2 method
Install BusyBox and it works again. I installed it from the thread but it didn't work until I installed it from an app on the market
Confirmed. Installing busybox from app store fixed it. For reference the busybox version is 1.26.2.
Thanks!
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
Wasn't it much easier if you install TWRP first, then root it using magisk?
Thank you for thatsuggestion. I didnt know that I can install TWRP before rooting the phone first
I had trouble rooting with CF auto root on my SM-N910F, not exactly the same problem as you.
Then I did some reading into other root alternatives and basically found out that SuperSU, which CF autoroot uses, was sold to a Chinese company called Coding Code Mobile Technlogy sometime around 2015. As it's closed source and Chinese firms particularly have been known not to respect user privacy, I would go with Magisk instead as it's open source, plus I have had zero problems with it so far.
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
hgroth said:
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
Click to expand...
Click to collapse
I'm no expert myself, in fact I'm new to it! but I'll share with you what I know.
I basically flashed TWRP to the phone using Samsung Odin (Loads of videos Youtube showing the process) Then I used Android Debug Bridge to push the Magisk flashable .zip file over to the phone (I think I could have actually just copied it into /sdcard - Androids name for internal storage bizarrely - through windows just like any other external device) before booting into TWRP on the phone, and simply selecting "install", selecting the Magisk .zip and flashing it from there. Then I just booted into Android and I seem to remember either the Magisk manager app will now be in your app draw, or alternatively there is an app placeholder there which allows you to download the full manager app, I can't remember which it is but small difference. Here is a link to the official Magisk thread on XDA which you can use find the download links you need. Take note that right at the top it states...
"Magisk does NOT have a website. Do NOT download Magisk from unofficial sites"
When I did it I downloaded Magisk from one of the top websites that appears when you search "Magisk" in Duckduckgo (they look very official) however after I read the notice above in the official thread I wiped the phone and did the process over again just to be safe! I hope that is helpful. :good:
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
did you remove battery after the flash?
Thanks for your help. Yes I tried that after the 2nd attempt when I set Odin not to auto reboot, I removed the battery
and then booted the phone after inserting the battery with the same result, not root. I am wondering why it says
boot image not found, aborting....... since I loaded the CF Auto Root which should be the correct boot image