So with trying to help and give back to the community I'm going to post my recent flashing experience.
So here's a little history.. I have a N900W8 from MTS. (Manitoba Telephone System).
Couple months back when the Tel Cel base came out I wanted root so I flashed using the following guide.
-- http://forum.xda-developers.com/showthread.php?t=2614772
This worked out well and the stock rom w/ root was very stable, CWM boot loader..
So now that this new build 'NB7' came out it got me itching to flash again.. LoL
I met all the requirements for 4.4.2 boot loader and such so I decided to flash xnote13 w/ civ snapkat kernel.
This setup worked well.. The rom had a few glitches but was very quick and the best of all I could change the DPI.
I didnt setup the rom 100% as I was feeling it out. After a day or so I decided to flash to stock NB7 and then flash xnote13 again so I can have the updated NB7 modem.
Oh Man.. This is where the fun begins.. So I hit up sammobile and grabbed the latest rogers rom as I noticed all the Canadian roms used the same PDA/CSC/MODEM.
-- http://www.sammobile.com/firmwares/3/?download=26660
PDA: N900W8VLUCNB7
CSC: N900W8OYACNB7
MODEM: N900W8VLUCNB7
I take this rom, flash it on my phone via Odin.. What I notice is the model# and build change to reflect NB7 but the baseband was still MJ4.
I flash 2-3x and still no change.. I'm like wtf..
At this point I'm confused as to why I cannot upgrade this baseband.
I then decided to flash the CSC from the guide I used earlier. As I had a multi-csc installed from when I had flashed Xnote13.
-- http://forum.xda-developers.com/showthread.php?t=2614772
After this I flashed the NB7 rom again via Odin and boom. The baseband reflected NB7.
I noticed my phone had a few Bell apps. When I looked into this I found out its due to the CSC. I tried the method mentioned in most posts *#272*YOURIMEI# but this wouldnt work. I would get instant error messages.
I then found this app on google play which people mentioned having success with.
-- https://play.google.com/store/apps/details?id=com.manniakk.cscselector
I used this app w/ root I was able to bring up a list of the CDN CSC codes. Whats funny is there is no list anywhere on the internet that has what CSC code belongs to which provider.
By going through sammobile and using some good guessing I was able to figure out what most of them are with some exceptions.. I couldnt find MTS...
I ended up choosing MTA and rebooted my phone but sure enough Bell apps were still there.. Tried a few more things and couldnt get past that so I just said forget it.
I decided to keep the Stock NB7 4.4.2 rom w/ root... I frooze all that Bell **** and there's no branding whats so ever.
The rom is working flawless. During this process I rooted the phone multiple times and flashed the NB7 rom multiple times via Odin. At no point did my Knox trip..
As of right now I have CWM as the bootloader and Knox is still 0x0.
Sorry for the long read.. If you have any questions lemme know.
ReDz
Can you help me with rooting my phone? There's too much guides out there for specific models so it confuses me lol. My Note 3's model is the N900W8, running on KitKat 4.4.2, kernal 3.4.0-859721, and the baseband # is N900W8VLUCNB7. I just want to root it so I can remove all the bloatware. I don't plan on adding any ROMs to it unless it's close to looking like stock because I still want the SPEN features without all the fancy stuff
Doodless said:
Can you help me with rooting my phone? There's too much guides out there for specific models so it confuses me lol. My Note 3's model is the N900W8, running on KitKat 4.4.2, kernal 3.4.0-859721, and the baseband # is N900W8VLUCNB7. I just want to root it so I can remove all the bloatware. I don't plan on adding any ROMs to it unless it's close to looking like stock because I still want the SPEN features without all the fancy stuff
Click to expand...
Click to collapse
I've replied to your other thread in Q & A, but if you just want to root, flash this file using odin. It might or it might not trip Knox on your phone. Make sure reactivation lock is off before flashing.
Doodless said:
Can you help me with rooting my phone? There's too much guides out there for specific models so it confuses me lol. My Note 3's model is the N900W8, running on KitKat 4.4.2, kernal 3.4.0-859721, and the baseband # is N900W8VLUCNB7. I just want to root it so I can remove all the bloatware. I don't plan on adding any ROMs to it unless it's close to looking like stock because I still want the SPEN features without all the fancy stuff
Click to expand...
Click to collapse
Do you try with towelroot ?
zelenko said:
Do you try with towelroot ?
Click to expand...
Click to collapse
I already have and it doesn't work
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
No man there is no blocking,its just that right now nobody developed an exploit for thta specific phone.Give it some time.
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
i just orderd samsung galaxy core prime because no one is developing any thing at all for this device.I will be making root exploit and start cooking rom for this device so just wait a bit and i will be working on it.
Waiting for rooted kernel for G360T1 or G360T
Arrowblue said:
i just orderd samsung galaxy core prime because no one is developing any thing at all for this device.I will be making root exploit and start cooking rom for this device so just wait a bit and i will be working on it.
Click to expand...
Click to collapse
There are many of us using the MetroPCS version G360T1 that will gladly try any root method you get going. Feel free to contact directly if you need some testing help. While waiting for root, I tried Package Disabler Pro 3.7 that was released September 15. It works fine on the G360T1, although it says "Custom" under "Device status" in "About Device -> Status." Haven't gone to Download Mode to see if the triangle is set or not, but I'm guessing the flash counter has been tripped. I'm not worried about it too much, and it may have been tripped with some other attempt to root the device. Still, this app was just what I needed to disable all the junkware and still have a smooth working Lollipop 5.1.1 while waiting for the real goodies.
alienwarning said:
There are many of us using the MetroPCS version G360T1 that will gladly try any root method you get going. Feel free to contact directly if you need some testing help. While waiting for root, I tried Package Disabler Pro 3.7 that was released September 15. It works fine on the G360T1, although it says "Custom" under "Device status" in "About Device -> Status." Haven't gone to Download Mode to see if the triangle is set or not, but I'm guessing the flash counter has been tripped. I'm not worried about it too much, and it may have been tripped with some other attempt to root the device. Still, this app was just what I needed to disable all the junkware and still have a smooth working Lollipop 5.1.1 while waiting for the real goodies.
Click to expand...
Click to collapse
The thing is i got g3601 and its running kitkat and no update availble on it ??? so i am porting 5.1 for it.Recovery has been patched up and working kinda fine but need to fix alot of issues.normally i dont develop for mid range mobiles but my brother got one so that is why i started with this one.my first projects are z3 + and xperia lines.I will let you know when it is completed for testing.
Hmm, I thought this was for SM-G360T and the Samsung Galaxy Core Prime that is out for T-Mobile and running Lollipop 5.x. Is the G3601 a typo or different model? The MetroPCS G360T1 will work fine with the firmware and files from T-Mobile G360T because they are the same device and even same network provider. Anyway, it looks like someone was kind enough to modify the kernel source code the Samsung posted just a week or two ago. Here is the news, but be warned that it will trip the KNOX flag:
http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522
I put my G360T1 in download mode and it still says official and no warning triangle. I mentioned that it said custom in the About Phone page after doing other terminal entries and running Package Disabler Pro 3.7. Some may want to wait to root the device until there is a deodex'd rom out there to run xposed framework. I like the slimed down stock 5.1.1 and there are a bunch of garbage programs hogging the decent entry level device resources. More news to come...
root for sm g360ti
Follow this link:
http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522
Rooting using the same files as G360t1
I have rooted the g360t using the files from this post http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522 which are for the g360t1 variant and it went well but you have to go to developer options and activate OEM unlocking for it to work and I did it with Odin version 1.85.
Rooting sm-g360t
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
I got it rooted with king root but can't fined recovery and can't turn phone off it just bootloops how you fix that
Has anyone had SUCCESS rooting a SM-G360T device?
Snlich said:
Hey everyone,
So this is pretty straight foreward, I'm attempting to root my Galaxy Core Prime (G360T, from T-Mobile in US) and I have had absolutely zero luck finding ANYTHING related that model number.
I've found plenty of stuff here, but it is all related to the G360H, G, and even the T1 (i think?) I've tried Kingo, Odin, and a few other things and I'm getting absolutely no where.
I'm wondering if anyone out here has had any luck with rooting this device in particular, or if maybe there is something I'm missing? I'm pretty new to the idea of rooting devices but I'm a proficient technically so I'm not exactly sure what is going on.
Is it T-Mobile software or something blocking the ability to root? I can't believe there is that much of a difference between my phone and say the G360H.
Thanks in advanced for the help, as I'm totally clueless at this point.
Click to expand...
Click to collapse
My specs:
Model #: SM-360T
Android Version: 5.1.1
Baseband Version: G360TUVU1AOF9
I migrated from Nokia 521 - Windows 8.1 phone to this Android device because of the litany of apps I could use for productivity. I am highly disappointed that I am unable to revoke permissions of applications to resources I think they don't need. So, I basically use phone to make calls and text. If someone has successfully rooted THIS smartphone version, please advise. I'm a little technical, too.
Try this: https://autoroot.chainfire.eu. find your model and download the file you need, unzip it then put your phone in download mode and use odin 3.7 to send it to the phone. That outta be enough. I have not rooted this particular device in a while but I have rooted plenty of others using that method and it works like a charm every time. I just did a quick look up and your model is listed there. Give it a try and post your results.
Thank you so much, Geevil!!!
Appreciate your response.
alienwarning said:
Hmm, I thought this was for SM-G360T and the Samsung Galaxy Core Prime that is out for T-Mobile and running Lollipop 5.x. Is the G3601 a typo or different model? The MetroPCS G360T1 will work fine with the firmware and files from T-Mobile G360T because they are the same device and even same network provider. Anyway, it looks like someone was kind enough to modify the kernel source code the Samsung posted just a week or two ago. Here is the news, but be warned that it will trip the KNOX flag:
http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522
I put my G360T1 in download mode and it still says official and no warning triangle. I mentioned that it said custom in the About Phone page after doing other terminal entries and running Package Disabler Pro 3.7. Some may want to wait to root the device until there is a deodex'd rom out there to run xposed framework. I like the slimed down stock 5.1.1 and there are a bunch of garbage programs hogging the decent entry level device resources. More news to come...
Click to expand...
Click to collapse
I'm running stock 5.1.1 on G360t and just got some root using this kernel so tanks for the help and all the fish
Hello how would one root the sm-g360t and get custom recovery on it ?
Sent from my SM-G360T using Tapatalk
I have the sm g360t1, though no computer to connect the phone to. I see this phone listed in the cf-auto root repository linked above- not sure if that method needs a computer. King root may have worked, though the root gone by when using w0lfdroid's
Kingroot removal/supersu installer. It worked on orher phones.
King root is such spyware. I really want to try something else...
ewokmojo said:
I have the sm g360t1, though no computer to connect the phone to. I see this phone listed in the cf-auto root repository linked above- not sure if that method needs a computer. King root may have worked, though the root gone by when using w0lfdroid's
Kingroot removal/supersu installer. It worked on orher phones.
King root is such spyware. I really want to try something else...
Click to expand...
Click to collapse
Yes King Root is bad. Pretty much like malware for your device. Don't use cf-auto-root either, as it's kind of a generic root and doesn't really function properly. I'm helping people constantly fix their devices after either tryung King or CF. Use Trapkernel to root the SM-G360T1 & SM-G360T. It's quick and easy and roots the device with no problems.
http://forum.xda-developers.com/showthread.php?p=62859013 Here is the recovery you should use too in case anyone's wondering. You flash it the same way as root.
http://forum.xda-developers.com/showthread.php?p=66266209
I recommend using version 3.0.1-0 though, as version 3.0.2-0 has had problem flashing certain roms for some reason.
Thanks bogarty, I was able to root and flash custom recovery on my phone with both links you provided here.. I have the T-Mobile version (SM-G360T) but everything went well
Dont know if ppl still trying to root this device but I just found out that you can download the rooting file trough chainfire for this model. Here´s the link: https://download.chainfire.eu/767/C...to-Root-cprimeltetmo-cprimeltetmo-smg360t.zip
Why do that when there is a root method for this device.
Follow this thread here for all your root needs for this device
http://forum.xda-developers.com/gal...should work just fine for the tmobile version
will this allow me to use a at&t sim card in my SM-G360T phone instead of T-Mobile
Model #: SCH-I535
Android Version: 4.4.2
Baseband version: I535OYUDNE1
Kernel version: 3.4.0 (May 20, 2014 KST)
Build number: KOT49H.I535VRUDNE1
SE for Android status: Enforcing SEPF_SCH-I535_4.4.2_0016
Hardware version: I535.10
So i just got this S3 for really darn cheap in great shape. I figured i wanted to root and use custom recovery and then maybe try some new roms. But it comes to my attention through like all the helpful tutorials that the bootloader is locked and there is almost zero guarentee that even the one that have done this will work without many issuses. so im just seeing if anyone thinks its worth it to try with this phone or look else where and deal with 4.4.2
Of course its always worth getting rid of all the bloatware ! I have a galaxy S3 rooted with the liquid smooth ROM and love it .
The bootloader is not locked I had to root it and remove the battery on reboot in order to pass it or it will try to reload back to default also took a few times .
I would say it is worth it to root. From there your choices are limited since you are on 4.4.2 with the NE1 bootloader.
I bought such a device in May, proceeded to root, install SafeStrap, and then flashed the SuperLiteROM.
NOTE, there are only three ROMs safe to use on an i535 with the NE1 bootloader.
DO NOT try to flash a custom recover such as CWM or TWRP.
to quote myself from another thread:
I picked up a used i535 a few months ago as a device to mod and learn. I had no intentions of using it as my daily phone - I'm on AT&T with an i747. I found it was already on the NE1 bootloader and modem, I hadn't read enough before purchasing.
I was able to root it with TowelRoot. Following that I installed BusyBox and then installed SafeStrap Recovery for devices with the NE1 bootloader, see here.
From what I have seen there are three ROMs available to this device on NE1; stock NE1, SuperLiteROM, and Paul Pizz. This thread is a good resource for all but Paul Pizz, which is here. I after installing SafeStrap I flashed SuperLiteROM to the stock slot, it seems to avoid some issues when flashed here instead of a secondary slot. Since then I have installed XPosed framework and have several mods working with no issues.
Click to expand...
Click to collapse
The XPosed module I spent the most time tinkering with was XPrivacy.
So question.. Can I use Xposed Framework on my Verizon Galaxy S III without tripping KNOX and bricking my phone or is that one of the things I can't do because I can't flash custom roms n such?
Phone is running Android 4.4.2
Model number is SCH-I535
If I can use Xposed then is there anything I should be careful about and not touch / do?
Any feedbk??
Dimmizer said:
So question.. Can I use Xposed Framework on my Verizon Galaxy S III without tripping KNOX and bricking my phone or is that one of the things I can't do because I can't flash custom roms n such?
Phone is running Android 4.4.2
Model number is SCH-I535
If I can use Xposed then is there anything I should be careful about and not touch / do?
Click to expand...
Click to collapse
I don't know much about Knox, I deleted anything that looked related to it from my phone that I Was able to, and last I checked with a program that is supposed to give you a status of knox it just throws an error that I believe means it can't tell the status.
Anyway, I have Xposed running without issue on my phone, same phone, same stock android (Although rooted and cleaned up the best I could) without issue. Running modules like APM+, EnableCallRecording, and Wanam Xposed.
I was running Xposed on my i535 with the 4.4.2 bootloader and modem installed. I bought the phone used last May with no intent of using it as a phone. I wanted it to learn more about modding. It was already on the 4.4.2 Stock ROM. At that point I started reading the i535 forums and learned of the limitations of my "new" device. After reading for a week I rooted with towelroot, installed busybox, installed safestrap and then flashed one of the two ROMs usable on this device. It worked well for four months. I lent it out to a friend and it was returned unbootable. I will probably be able to restore the device since I can get to download mode and the stock recovery.
I don't know if this changed my Knox/warranty bit status. I'm not concerned since the device is well out of warranty and I am not the original owner. It didn't change the performance or battery life of the phone. My understanding is that Knox is to run secure corporate apps to protect data, something I will not be doing. So, I wouldn't be concerned if I were you unless your worry is that it may affect resale.
Which Xposed Framework version did you use?
" I was running Xposed on my i535 with the 4.4.2 bootloader and modem installed. It was already on the 4.4.2 Stock ROM"
I have a Towelroot rooted Verizon GS3 i535 and want to install xposed framework but everything I read is 2 years old and version for Kit Kat 4.4.2 is experimental. I'm on a stock rom. So now in June 2016, which stable version should I install? My rom is touchwiz and build NE1 if that helps.
I read warnings that installing on a Samsung modified rom will result in a bootloop and that is a show stopper for me.
Also confused about version numbers. 2.7 is download file number V33. I can't find a list showing which version numbers go with which file numbers.
Many Thanks!
I've researched multiple rooting tutorials and have found a lot of guides based on the auto-root file from www(.)autoroot.chainfire(.)eu
However, I still do not know what to do with this. From my research I found out that there is a possibility that the bootloader is locked and that is the reason I am scared, if I brick this phone I will not have a phone for another 2 years. If I flash a new clear android 7.0.0 stock for the S6 without the O2 addon bloatware with the bootloader locked it will brick my phone since this is some sort of security feature.
What I want from my S6:
- VERY good security, I will be banking on it alot, using android pay, etc so I need it to basically be hack-proof etc. Im not going to install apps like lucky patcher which are not from the play store.
- A new clean stock version of Android 7.0.0 without so many O2 apps that I cannot uninstall.
- Root access to remove certain system services and increase my battery life
I am a previous root user, 1 year ago being on my rooted S3 which I rooted using KingoRoot with one click. Now I come back year later to a new phone 3 generations down with things like the locked bootloader and KNOX. Could anyone explain what I can do at this point?
Phone specification essentials:
Name: Samsung Galaxy S6 O2/EU
Model Number: SM-G920F
Build Number: G920FXXU5EQE5
Android Version: 7.0
Knox Version: 2.7.1
The device still has a simlock, and I was told that the sim lock is installed in the ROM. So if I were to flash Im assuming the simlock would be removed however I still have a pending order for the unlock code coming in 7 days.
Try with a TWRP and a Magisk' - SuperSU it's a will be less-stable for now' (Seriously who are be use at This for now?)
Addition advantage it's a doesn't Permissives of a Magisk (Still "Enforced")