Ok...so I've been reading almost every post in here all day long...and I wanted to upgrade my Stock Android 4.1.2 phone to one of the cool roms on here. One rom (I can't remember which one)...said I needed MJ9 firmware...so I flashed it. Then I successfully rooted. I then tried to install a new recovery so I could flash the new shiny rom. As soon as I rebooted...got the Verizon Brick Message from hell. Ok...then I searched how to get rid of that. I found a post saying to flash back to stock MJ9 which gave me Android 4.3. Now that means I can't unlock my bootloader so I could root and install the roms...correct?
I guess my question is. Can I use ODIN to flash back to 4.1.2 and have a chance at an unlocked bootloader...or am I skrewed? I should just accept the OTA kitkat and be done with it?
I
Well if you flashed stock 4.3 you most likely locked up your boot loader and there is no known exploit to unlock that boot loader atm. I think there's still a way to root 4.3 but I'm not 100% sure how. Hopefully someone else can chime in on that.
Sent from my SCH-I605 using Tapatalk
@gallogj
Unfortunately, your bootloader is locked now, so trying to ODIN to 4.1.2 won't unlock it. There's not an easy way to unlock it now (search the threads and you'll see that Mobile Tech videos can downgrade for a price... and someone else reported that they used an "unbricker" method to downgrade... but others don't appear to have had as much success).
If you stay on 4.3 MJ9, you can still get root, run root apps/ Xposed, etc... And with 4.3 MJ9, you can also use Safestrap to run custom Touchwiz ROM's.
If you take the OTA to kit kat, there's not a root method currently for our Note 2's, so you'll be running pure stock.
It's totally up to you, but if you want root (at least for now), you'll want to stay with 4.3 MJ9.
--------------------------------
Edit: You can check out Safestrap at this link: http://forum.xda-developers.com/showthread.php?t=2704992
Here's a link to the saferoot method for 4.3 MJ9: http://forum.xda-developers.com/showthread.php?t=2565758
I just picked up the Galaxy Note 3, I didn't want a spark enabled phone as I want to use hotspot + voice at the same time.
I am coming from an LG G3 that I still have but will not use until sprint rolls out VoLTE and before that I had a Galaxy S4.
My phone is stock at NAB and I am not sure what is the best way to get root and run the latest version of the firmware. Will towelroot or CF-AutoRoot work and is there a way for me to not trip knox but still run a firmware version higher then NAB?
I've read a few topics in this forum and did a search for NAB and none of them have been clear as how to root the firmware version of NAB and update it to the latest hopefully without triggering knox. I don't really care if knox is tripped but if I can keep my warranty why not right? If there is no other way i'll just update to NH7 and use SuperSU or CF-AutoRoot root method that I read about.
mikeownage said:
I just picked up the Galaxy Note 3, I didn't want a spark enabled phone as I want to use hotspot + voice at the same time.
I am coming from an LG G3 that I still have but will not use until sprint rolls out VoLTE and before that I had a Galaxy S4.
My phone is stock at NAB and I am not sure what is the best way to get root and run the latest version of the firmware. Will towelroot or CF-AutoRoot work and is there a way for me to not trip knox but still run a firmware version higher then NAB?
I've read a few topics in this forum and did a search for NAB and none of them have been clear as how to root the firmware version of NAB and update it to the latest hopefully without triggering knox. I don't really care if knox is tripped but if I can keep my warranty why not right? If there is no other way i'll just update to NH7 and use SuperSU or CF-AutoRoot root method that I read about.
Click to expand...
Click to collapse
If you want to run the latest, then you'll need to trip Knox.
Any major changes between NAB and NH7? Such as a major performance increase or significantly better battery life? If not I can just use towelroot right?
From what i can find the changes for NC5
Enhancements/Fixes
Wi-Fi Calling
NH7
Enhancements/Fixes
Android 4.4.4
HD Voice Icon support
International WiFi Calling support
Google Security Patches
KNOX 2.0
Kids Mode (Added within app tray instead of just a widget)
mikeownage said:
Any major changes between NAB and NH7? Such as a major performance increase or significantly better battery life? If not I can just use towelroot right?
From what i can find the changes for NC5
Enhancements/Fixes
Wi-Fi Calling
NH7
Enhancements/Fixes
Android 4.4.4
HD Voice Icon support
International WiFi Calling support
Google Security Patches
KNOX 2.0
Kids Mode (Added within app tray instead of just a widget)
Click to expand...
Click to collapse
Definitely battery improvements, I really can't speak to NAB to NH7 performance changes. My phone came with NC5 as I got it from Sprint last Feb.
mikeownage said:
I just picked up the Galaxy Note 3, I didn't want a spark enabled phone as I want to use hotspot + voice at the same time.
I am coming from an LG G3 that I still have but will not use until sprint rolls out VoLTE and before that I had a Galaxy S4.
My phone is stock at NAB and I am not sure what is the best way to get root and run the latest version of the firmware. Will towelroot or CF-AutoRoot work and is there a way for me to not trip knox but still run a firmware version higher then NAB?
I've read a few topics in this forum and did a search for NAB and none of them have been clear as how to root the firmware version of NAB and update it to the latest hopefully without triggering knox. I don't really care if knox is tripped but if I can keep my warranty why not right? If there is no other way i'll just update to NH7 and use SuperSU or CF-AutoRoot root method that I read about.
Click to expand...
Click to collapse
If you don't want to trip KNOX, and don't need Kids Mode then you can still update to NC5 and root with Towel Root. Here is a link for more info http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Thanks
I am now running NC5 rooted with towel root and it works very well. I just need to find a permanent way to disable firmware update notifications next.
[Q&A] Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or
Q&A for Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or other
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or other. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Mega 2 as well.
KingRoot did work for me. I am looking for a custom ROM now, but there is like NO support from anywhere for this device. I hope we can get a developer onboard and get something built for these devices.
have a thread on android forums for this as well, you can do a search for Mega 2 and its the only thread on the mega 2 forum, screenname on there is Matt Cajon as well.
Maybe we can make something happen
Custom Recovery?
Any luck with a working custom recovery?
running backup before running the app.
Thank you shockazulu for your post on the mega2 root.
I'm new to this and have been looking and searching for the best way to do it and most have refurred the king root app.I do have a questions .
Do I still need to do a backup of the phone before running the app.?
Is this a preferment root as I noted your phone reverting back to it's original state?
Noticed there is a newer version of the king root app now 4.5 and would it be better to run that app ?
Thanks Again and I'm sure I'll have another question before I get into doing this !
Chris
I manage to root the galaxy mega 2 on the newer baseband G750AUCU3AOFA. Since for some reason you can't root it on that build. but with the modem flash it worked
Matt Cajon said:
KingRoot did work for me. I am looking for a custom ROM now, but there is like NO support from anywhere for this device. I hope we can get a developer onboard and get something built for these devices.
have a thread on android forums for this as well, you can do a search for Mega 2 and its the only thread on the mega 2 forum, screenname on there is Matt Cajon as well.
Maybe we can make something happen
Click to expand...
Click to collapse
The problem with the att version of the mega 2 is that the bootloader is locked. So there is no way to use a custom bootloader like Clockwork. Without a custom bootloader we can't load/flash roms.
But what we can do is........
We can use a program called Flashfire. Flashfire is a way to flash things on our phone without having to use the bootloader.
We can also use exposed launcher and wanam exposed. This is the tools we can use to make customise our stock rom.
One of us could customize a rom and create a step by step for how they created it. If it is a stable setup then instead of others flashing that custom ROM, they would fallow the steps to create the same custom ROM.
whats with the vague answer ...
if you rooted it on OFA how did you do it?!?!
WHAT MODEM?! please elaborate I need to know asap..
Any of you had luck on installing a custom recovery for it? i am trying to help another forum member who have this S750A .
I recently ported a custom TWRP for my device which is a SM-J105B. Found out that TWRP was easier to port/works better on it than CWM for instance. Maybe this is the case for you guys device, i want to help out.
i know this is a 1 year old post but if any were successful please share the knowledge cheers from Brasil!
Pindroid is trying to help me i have a samsung galaxy mega 2 sm-g750a also it said "unlocked" on the ad when i got it but anyways we are looking for the original 4.4.4 kitkat firmware and can't seem to find it anywhere but the one we did find that has repair in its title has never worked as far as flashing with it goes. I have lollipop right now and it works fine but it hasn't solved the problem im having with my IMEI so we are trying a downgrade to see if that helps. Anyways thanks for any help
I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops then I gotta reflash 5.1.1 firmware via Odin ...I've looked and looked just the run around on how to root this device,I really wanna root this phone love the screen and it's my go to phone for work ,if anyone could figure this out that would be awesome
I get the same thing...Boot looping after root..Firmware is 5.1.1..Anyone have thoughts?Thanks.
Surgeman said:
I get the same thing...Boot looping after root..Firmware is 5.1.1..Anyone have thoughts?Thanks.
Click to expand...
Click to collapse
Thoughts on how to root or how to fix the bootloop?
Piridroid said:
Thoughts on how to root or how to fix the bootloop?
Click to expand...
Click to collapse
The root is no problem..It's the boot loop is the biggest problem.And factory wiping it doesn't fix the issue.
Surgeman said:
The root is no problem..It's the boot loop is the biggest problem.And factory wiping it doesn't fix the issue.
Click to expand...
Click to collapse
As mrodriguezangel said on page 1:
"I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops THEN I GOTTA REFLASH 5.1.1 FIRMWARE VIA ODIN .."
Did you manage to root Mega 2 5.1.1 without issues? To remove the bootloop you will have to reflash your stock firmware via ODIN software.
According to the official AT&T page (is yours at&t?) :
https://www.att.com/devicehowto/tut..._KB425949?make=Samsung&model=GalaxyMega2G750A
Latest Kitkat is July 7, 2015
Android version: 4.4.4
Baseband version: G750AUCU3AOFA
Kernel Version: 3.4.39-2550495 [email protected]#1
Build number: KTU84P.G750AUCU3AOFA
Latest Lollipop is September 2, 2015
Android version: 5.1.1
Baseband version: G750AUCU3BOH4
Kernel Version: 3.4.39-5559233 [email protected]#1
Build number: LMY47X.G750AUCU3BOH4
Googled "G750AUCU3BOH4" and found http://www.mediafire.com/file/hd72qrsaeoob9tl/G750AUCU3BOH4+5.1.1.rar , try to know more about it, but should work ok.
How did you root?
Piridroid said:
As mrodriguezangel said on page 1:
"I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops THEN I GOTTA REFLASH 5.1.1 FIRMWARE VIA ODIN .."
Did you manage to root Mega 2 5.1.1 without issues? To remove the bootloop you will have to reflash your stock firmware via ODIN software.
According to the official AT&T page (is yours at&t?) :
https://www.att.com/devicehowto/tut..._KB425949?make=Samsung&model=GalaxyMega2G750A
Latest Kitkat is July 7, 2015
Android version: 4.4.4
Baseband version: G750AUCU3AOFA
Kernel Version: 3.4.39-2550495 [email protected]#1
Build number: KTU84P.G750AUCU3AOFA
Latest Lollipop is September 2, 2015
Android version: 5.1.1
Baseband version: G750AUCU3BOH4
Kernel Version: 3.4.39-5559233 [email protected]#1
Build number: LMY47X.G750AUCU3BOH4
Googled "G750AUCU3BOH4" and found http://www.mediafire.com/file/hd72qrsaeoob9tl/G750AUCU3BOH4+5.1.1.rar , try to know more about it, but should work ok.
How did you root?
Click to expand...
Click to collapse
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Surgeman said:
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Click to expand...
Click to collapse
mmm Ok. How did you root with SuperSU ? CF-auto? recovery? supersu-me ?
Is there an option called "Unlock by OEM" under "Developer Options"? Enable it.
Another thing, according to this tutorial for the SG-M750F:
https://androidmtk.com/root-samsung-galaxy-mega-2-sm-g750f
This F version which should be similar is only rootable with a specific firmware. Maybe thats the case for the A version aswell.
Also, next time you have root, before you reboot you should make a backup of your EFS and Modem folders. You can do that via ADB, EFS tools or using some apks for instance.
Check dlo2000 post on first page, he had kitkat installed, rooted with Kingo and let the the phone OTA update to lollipop... somehow his IMEI number got corrupted and now he cannot use his phone to make calls. Thats why backing up your EFS partition is important, your IMEI is there.
So from what i understood, you did know stock firmware flash would remove bootloops, but you currently dont know how to root without creating a bootloop, is that correct? cheers
---------- Post added at 01:48 AM ---------- Previous post was at 01:37 AM ----------
Surgeman said:
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Click to expand...
Click to collapse
Enterprise... maybe it has extra security turned on, idk.
How do you know it has to do with KNOX, did it show some knox message? Chainfire's supersu sometimes asks to let it disable knox. Which version of supersu did you use?
Piridroid said:
mmm Ok. How did you root with SuperSU ? CF-auto? recovery? supersu-me ?
Is there an option called "Unlock by OEM" under "Developer Options"? Enable it.
Another thing, according to this tutorial for the SG-M750F:
https://androidmtk.com/root-samsung-galaxy-mega-2-sm-g750f
This F version which should be similar is only rootable with a specific firmware. Maybe thats the case for the A version aswell.
Also, next time you have root, before you reboot you should make a backup of your EFS and Modem folders. You can do that via ADB, EFS tools or using some apks for instance.
Check dlo2000 post on first page, he had kitkat installed, rooted with Kingo and let the the phone OTA update to lollipop... somehow his IMEI number got corrupted and now he cannot use his phone to make calls. Thats why backing up your EFS partition is important, your IMEI is there.
So from what i understood, you did know stock firmware flash would remove bootloops, but you currently dont know how to root without creating a bootloop, is that correct? cheers
---------- Post added at 01:48 AM ---------- Previous post was at 01:37 AM ----------
Enterprise... maybe it has extra security turned on, idk.
How do you know it has to do with KNOX, did it show some knox message? Chainfire's supersu sometimes asks to let it disable knox. Which version of supersu did you use?
Click to expand...
Click to collapse
I used Kingo the first time,and even used Super SU me to remove Kingo...AT&T devices doesn't require any unlock for cricket because AT&T owns them lock stock and barrel.You're getting the same service just bottle necked on the 4G end of it at 8 mbs and it's unlimited.I have been reading through other post in some other forums,and the SE for Android pops up about security settings and ask to reboot to restore them.Once you do..the boot loop begins.I have searched the error out also...and it pertains to knox.I have even tried to remove knox before rebooting..No go..still boot loops...Myself and another user have the same issue,and we've been trying to figure a work around and nothing yet.Some other information I have read that with the Lollipop update it adds the enterprise knox that may cause issues.But it doesn't hurt to try...Oh I forgot to mention...I made a efs backup before I started the journey but good looking out..Thanks..
Surgeman said:
I used Kingo the first time,and even used Super SU me to remove Kingo...AT&T devices doesn't require any unlock for cricket because AT&T owns them lock stock and barrel.You're getting the same service just bottle necked on the 4G end of it at 8 mbs and it's unlimited.I have been reading through other post in some other forums,and the SE for Android pops up about security settings and ask to reboot to restore them.Once you do..the boot loop begins.I have searched the error out also...and it pertains to knox.I have even tried to remove knox before rebooting..No go..still boot loops...Myself and another user have the same issue,and we've been trying to figure a work around and nothing yet.Some other information I have read that with the Lollipop update it adds the enterprise knox that may cause issues.But it doesn't hurt to try...Oh I forgot to mention...I made a efs backup before I started the journey but good looking out..Thanks..
Click to expand...
Click to collapse
OK, so it was supersu-me and the issue has to do with SElinux right.
dude i own a Galaxy J1 mini and i was the "first person" to root the B/F/M/Y versions (custom recovery method, based on an obscure version created for the H version) , this device is also a 5.1.1 android, SElinux activated from factory. The website which provided the root for the H version vanished a couple of weeks after they annouced it... lucky to find it, i just had to read easy tutorials here in XDA to learn how to properly port the TWRP for my specific model B and later on for the other J1 mini variants on ppl demand.
What i find out from my experience is, if i was going to wait for some expert to find how to root it, i would still be waiting... keep trying!
I would personally as a noob, try to find out how to disable KNOX or SElinux . There are probably commands which can be run as root user to disable them, for instance "selinux set permissive" (i know it exists, something like that, maybe). There are apps which claim to do those stuff, just search playstore for "knox" or "selinux" and you will see. In case none does the job automatically, search how to do it manually.
In my case, the TWRP+SuperSU method worked just fine, looks definitive. BUT, before i found this, the only other real option was a chinese app called 360root. None other root app works on my device so far. But its root was unstable and not compatible with all apps, thats why i searched for a permanent root.
THis 360root only worked on the older firmware (also 5.1.1, but older samsung release).
My opinion is... in case you dont mind using kitkat (android 4.4) i would flash the oldest firmware and try to root it with Kingo (which owners of variants of the MEGA 2 claim is the only tool capable, it even turns knox off in some cases). Remembering that if this worked, you would have to disable automatic firmware updates. Letting a rooted device to auto-update usually creates more trouble.
If kitkat is a no go for ya and you want to stick with lollipop, i would first try to disable the protections via apps (root ; dont reset, install app, try). Same applies to manually trying "disabling commands" via Terminal or ADB, root, try.
If that still does not work ... i would try to download a stock lolipop firmware and extract its files. I would then try to create a custom recovery (read tutorials) and also check if there were any options i could manually reprogram inside boot.img , recovery.img, system.img etc... (more tutorials lol)
Again man, im no expert, but thats what i would do! i actually downloaded that lollipop stock firmware for your device and will try to look inside it when i have time.
Piridroid said:
OK, so it was supersu-me and the issue has to do with SElinux right.
dude i own a Galaxy J1 mini and i was the "first person" to root the B/F/M/Y versions (custom recovery method, based on an obscure version created for the H version) , this device is also a 5.1.1 android, SElinux activated from factory. The website which provided the root for the H version vanished a couple of weeks after they annouced it... lucky to find it, i just had to read easy tutorials here in XDA to learn how to properly port the TWRP for my specific model B and later on for the other J1 mini variants on ppl demand.
What i find out from my experience is, if i was going to wait for some expert to find how to root it, i would still be waiting... keep trying!
I would personally as a noob, try to find out how to disable KNOX or SElinux . There are probably commands which can be run as root user to disable them, for instance "selinux set permissive" (i know it exists, something like that, maybe). There are apps which claim to do those stuff, just search playstore for "knox" or "selinux" and you will see. In case none does the job automatically, search how to do it manually.
In my case, the TWRP+SuperSU method worked just fine, looks definitive. BUT, before i found this, the only other real option was a chinese app called 360root. None other root app works on my device so far. But its root was unstable and not compatible with all apps, thats why i searched for a permanent root.
THis 360root only worked on the older firmware (also 5.1.1, but older samsung release).
My opinion is... in case you dont mind using kitkat (android 4.4) i would flash the oldest firmware and try to root it with Kingo (which owners of variants of the MEGA 2 claim is the only tool capable, it even turns knox off in some cases). Remembering that if this worked, you would have to disable automatic firmware updates. Letting a rooted device to auto-update usually creates more trouble.
If kitkat is a no go for ya and you want to stick with lollipop, i would first try to disable the protections via apps (root ; dont reset, install app, try). Same applies to manually trying "disabling commands" via Terminal or ADB, root, try.
If that still does not work ... i would try to download a stock lolipop firmware and extract its files. I would then try to create a custom recovery (read tutorials) and also check if there were any options i could manually reprogram inside boot.img , recovery.img, system.img etc... (more tutorials lol)
Again man, im no expert, but thats what i would do! i actually downloaded that lollipop stock firmware for your device and will try to look inside it when i have time.
Click to expand...
Click to collapse
Ok let me know what you find with the firmware when you get the chance.I have used 360root also in the past myself on devices when nothing else would work.I have tried several times and different ways.Disabled Knox via terminal with temp. root and still no go.It's the SELinux enforcing is the biggest problem.Kingo will install as a system app..but you won't have full root unless you run the apk to root the device again and it reboots on it's own after about 5 minutes or so.I'll keep stabbing at it..and post my findings.I assume I'm not the only one that could use this.Thanks for your time Piridroid.
Anything new on this?
is there any way to root vzw s4 5.01 of1 or it's non rootable yet?
you can not root of1, and a downgrade is not possible at the moment
Can it be rooted soon ?
Sent from my SCH-I545 using XDA Free mobile app
It's been rooted. http://forum.xda-developers.com/showthread.php?t=3254434
root available
Mahmoud Bakry said:
is there any way to root vzw s4 5.01 of1 or it's non rootable yet?
Click to expand...
Click to collapse
root by edgardo uchija and downgrade kernel in odin mode at OC1
downgrade SYSTEM COMPLETE not available, safetrap not working in android 5.0.1
try it:
http://forum.xda-developers.com/galaxy-s4-verizon/general/samsung-s4-i545-verizon-of1-root-t3254434
installation safestramp (not working for my)
http://forum.xda-developers.com/galaxy-s4-verizon/general/guide-safestrap-access-odin-t3120483
Sorry no speak english
Enjoy and Have phun
S4 root on of1
Yes you can root on OF1. I did mine just recently. Use this method: http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971.
Good luck
The last and only way to get root...
THE LAST AND ONLY WAY LEFT FOR ROOTING....VERIZON S4 LOLLIPOP...
Listen guys I think this could be the only chance of rooting s4 i545 0f1 I have tried every single root king/towel root etc etc on pc and phone too but all failed because the main reason is that when ever u try to root it verifies the build/kernel number and when it sees that it's 0f1 It stops working because the new most stable update of lollipop with the build number 0f1 doesn't comes with a unlocked boot loader so that u can install other stuffs just like. I phone specially in version and some other verient it would be a waste of time to try any other methos except this let me explain it did u know a while ago after the release of lollipop some apps were only supported by the 5.0 lollipop or higher when people lowere then lollipop like jelly bean and kitkat tried to download it from play store it said that this vision is not compatible with your devise because the play store decetected the 4.0 version just like king root does with build and kernel and stops but some geeks found the way to solve that by changing the build and krnel to latest version like 5.0 without even effecting system what if we could do the same with the build and kernel member to the previous working one like 0C1 then I think king root and other apps might get to working the reference how to change the kernel and build with out effecting the system is just go to YouTube and type ( fix "your device isn't compatible with this version" ) this will give u the reference for that location and app to change the build and kernel number I haven't tried it yet but if u r on that please reply me but hurry I think this can really work just need some one to test that but hurry... and please do inform back if it really works...c:
OR the other last and only option left would be to downgrade your version s4 i545 kernel = ..... 0F1 to 0C1 kitkat Which is now posible with Oden and then root it then turn it back to lollipop 5.0.1 kernel = .... 0F1 the most stable kernel version out there hope that helped u all .... c: Thanks