Related
I had another thread about rooting my Bionic and I was getting help. I did have more questions and was hoping that as the process went on, I would get answers. I guess it just kinda died since no one is answering my last questions. If anyone wants to check it out, it's in this section and the only one I have posted.
Anyway, the main question I have, and I figured it would be better to start it's own topic, is about updating to JB on a rooted phone. I have read many threads and lots of people either messed up root or bricked and had to start over. I guess it's not so much a question, more like directions on doing it properly. Like I said, I have read posts with instructions and a bunch of people chime in saying they did everything but still lost root. So there could be something unclear in those instructions and I don't want to take a chance. I will tell you what I have so far and what I have done.
I rooted my phone using this method
http://droidbionicroot.com/droid-bionic-root/how-to-root-ics-on-droid-bionic-and-motorola-android/
The root process I used gave me SuperSU and didn't tell me the version for the SU binaries. I searched around and all I could find was info on SuperUser in regards to backing up root. I uninstalled SuperSU, kinda. I just told it to use a different SU cuz when I used SuperUser and updated the binaries, SuperSU wanted to update them, then I opened SuperUser and the binaries reverted back. I was worried so I just told SuperSU to use a different SU. Was that ok?
SuperSU is no longer there, just disappeared. SuperUser is still on my phone.
Got safestrap tho still not updated to 3.11, got TBU (free), got Voodoo.
I have not made a backup with TBU.
I did do protect root with Voodoo but that was a week or so ago.
I have not made any major changes. BUT, I do have Hide It Pro and the apps I have hidden appear in TBU as frozen. Well at least it is highlighted and the option defrost is there.
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Don't be afraid....
The worst that can happen is you brick your phone and have to redo EVERYTHING. And chances are that won't happen if you're considering this and have done things in the past.
I only keep one SU app on my phone, but I have heard about being careful if you do have more than one not to confuse the binaries, so maybe if you can uninstall one and just use the one you kept to do everything, I'd say do that, but again I don't know.
I would also be careful about anything frozen especially if it's a system app or bloatware in the system...
See my other thread [Trifecta] Jelly Bean Update...I had all kinds of issues and made it thru, I'm sure you could too.
Cheers.
Ok, but what exactly do I do? I haven't modded anything, just rooted and "froze" apps. I know that after reading that I should take my phone back to where I had it right after root with no changes. Like I said, my phone has no mods and nothing has really changed. So what is the best way to update and keep root? Only reason I want to keep root is because it was easy and I don't want to do it again but more complicated (don't know Linux) If someone wants to type it out, step by step, or link to instructions that you followed exactly and succeeded in updating and keeping root, please do so.
As far as the GSM hack, not sure if I really need that.
Sorry....wasn't leaving you hanging...
You can try an app called OTA RootKeeper by Voodoo, it seems to work most of the time. But from what I understand once you start the update to JB even if it fails you can't go back. So if you update and lose root...
Go HERE
Read thru it, then follow the links to all info, tools & instructions.
Cheers.
Thanks. Hopefully everything goes ok with the update. I really don't want to spend a day learning and updating programs I never used. But if the update fails I guess I have no choice. I will wait till I know I have time, probably this weekend.
CycoPuppet said:
Thanks. Hopefully everything goes ok with the update. I really don't want to spend a day learning and updating programs I never used. But if the update fails I guess I have no choice. I will wait till I know I have time, probably this weekend.
Click to expand...
Click to collapse
I was chiming in for what little help I could offer on your other thread, and then I ran into an unexpected glitch myself. You can read all about it here. Basically, if you do an FDR for any reason on the stock ROM in SafeStrap, you are probably going to run into problems. It's happening to a ton of other people.
CycoPuppet said:
I had another thread about rooting my Bionic and I was getting help. I did have more questions and was hoping that as the process went on, I would get answers. I guess it just kinda died since no one is answering my last questions. If anyone wants to check it out, it's in this section and the only one I have posted.
Anyway, the main question I have, and I figured it would be better to start it's own topic, is about updating to JB on a rooted phone. I have read many threads and lots of people either messed up root or bricked and had to start over. I guess it's not so much a question, more like directions on doing it properly. Like I said, I have read posts with instructions and a bunch of people chime in saying they did everything but still lost root. So there could be something unclear in those instructions and I don't want to take a chance. I will tell you what I have so far and what I have done.
I rooted my phone using this method
http://droidbionicroot.com/droid-bionic-root/how-to-root-ics-on-droid-bionic-and-motorola-android/
The root process I used gave me SuperSU and didn't tell me the version for the SU binaries. I searched around and all I could find was info on SuperUser in regards to backing up root. I uninstalled SuperSU, kinda. I just told it to use a different SU cuz when I used SuperUser and updated the binaries, SuperSU wanted to update them, then I opened SuperUser and the binaries reverted back. I was worried so I just told SuperSU to use a different SU. Was that ok?
SuperSU is no longer there, just disappeared. SuperUser is still on my phone.
Got safestrap tho still not updated to 3.11, got TBU (free), got Voodoo.
I have not made a backup with TBU.
I did do protect root with Voodoo but that was a week or so ago.
I have not made any major changes. BUT, I do have Hide It Pro and the apps I have hidden appear in TBU as frozen. Well at least it is highlighted and the option defrost is there.
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Click to expand...
Click to collapse
You were trying to use two different superuser apps (superuser and SuperSu) to control the su binary - each comes with its own binary, so when you used one to update su, then the other is naturally going to complain.
Clean Install
CycoPuppet said:
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Click to expand...
Click to collapse
I highly suggest that before you try anything, you make a backup of your device with TBU and then copy the TBU file to your PC.
From what i've heard the cleanest way to keep root and get to JB is to backup everything, flash the ICS fxz, root, backup root with Voodoo and then take the ota update. This should put your phone on stock rooted JB. From there you can download TBU and restore your apps and data.
This is a bit excessive but it should in theory fix any issues that could arise from having frozen apps or otherwise changed the system.
ian_mcxa said:
I highly suggest that before you try anything, you make a backup of your device with TBU and then copy the TBU file to your PC.
From what i've heard the cleanest way to keep root and get to JB is to backup everything, flash the ICS fxz, root, backup root with Voodoo and then take the ota update. This should put your phone on stock rooted JB. From there you can download TBU and restore your apps and data.
This is a bit excessive but it should in theory fix any issues that could arise from having frozen apps or otherwise changed the system.
Click to expand...
Click to collapse
DO NOT ATTEMPT TO FXZ TO 246 ICS NOW. You've already updated to JB, and you will brick your phone if you attempt to go back.
New MotoX from sprint.
android version 4.2.2
baseband msm8960pro_bp_2323.020.90.00r
kernel 3.4.42.-xline.
system version 139.14.1
build 13.9.0q2.x-116-mx-17-57-1
i did a fair amount of searching but could not find the proper instructions for obtaining root access for the moto x. Need root access or this device would be a deal breaker.
Can someone point me to a link? I would be much appreciated. Thanks Listers!!!
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
I did search the web and the forums; I'm sorry. it was a long day, i had just purchased the phone and wanted to make sure i didn't brick it. I have rooted/jailbroken several other devices but wanted to know if the latest ota update would cause a problem for that.
Again, I'm sorry for for the excess forum baggage.
I'll try again.
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
moises1204 said:
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
Click to expand...
Click to collapse
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
bullpen7979 said:
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
Click to expand...
Click to collapse
ownmoto or whatever?? um... ok... I can tell you haven't browsed the different sections for the Moto X here or you would have seen in the "Moto X Original Android Development" section that its called "PwnMyMoto"
Brokenwall gave you a way to root your sprint device, no matter what stock rom you're running... OTA updates or not. Granted unlocking your bootloader voids your warranty... and he didn't give you a 100% newbie step by step guide which it now seems you were really looking for.
Also in the Moto X Original Android Development is a thread titiled... "[Root] RockMyMoto (Yes, even the first OTA)" which is pretty obvious as to what it is for. If you took a few minutes to read it, you'd know it is what you want if you don't want to unlock your bootloader. Its not a very long thead (141 posts currently) so it wont take long to read. The original post contains everything you need, except how to make sure you have Telnet as part of your Windows install (there are posts in that thread later that say what to do to enable/install Telnet as a Windows Feature inside Add/Remove Programs).
Sorry, if I come across as harsh. I know you just want to root without screwing up your phone, and I get that. But I'm afraid if you haven't been able to look around and find this stuff, you'll likely not be able to properly follow and understand the instructions and will therefore stand a good chance of messing up your phone!!!
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Again, I'm sorry for being stuck here and having to ask the question. I would greatly appreciate the assistance of someone who can speak to my specific situation.
Thank you and regards to those who can help.
Bull
bullpen7979 said:
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
Click to expand...
Click to collapse
The steps taken in the video are exactly explained in the post.
There are a few assumptions.. 1. Your PC has telnet on it, or you know how to install it. (there is a link further in that thread which Windows users can follow. 2. You have ADB Driver and Platform tools from the AndroidSDK installed correctly on your PC, and Moto drivers installed. Again, there are threads on this already, so you'll have to find/follow them.
You could also try to follow this post -> http://forum.xda-developers.com/showthread.php?p=47067076 however, it uses puttytel.exe instead of Telnet so it will look a little different. It too assumes you've properly installed ADB Driver and Platform Toos from the Android SDK along with the Moto drivers.
Another option is the "Tool Kit" -> http://forum.xda-developers.com/showthread.php?t=2477132 which is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. Only thing would be if you want to use "Flash back to stock" you need to download the ROM file separately.
bullpen7979 said:
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Click to expand...
Click to collapse
Right now, there is the rom the phone shipped with. If you have that, you use PwnMyMoto process to root it. The "camera update" that was pushed over the air. If you have that, you use RockMyMoto. And as of yesterday, if you have Verizon X, there is KitKat which can not be rooted (unless your carrier allows you to unlock your phone's boot loader)
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. Bummed. I just want my device rooted so I can send my daughter the one I promised here.
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. I'd even accept remote assistance via logmein. Pretty bummed. I just want my device rooted so I can send my daughter the one I promised her.
I have no idea why this process has been so difficult this time around. I have rooted, downloaded & installed custom roms, etc.
http://forum.xda-developers.com/showthread.php?t=2536200
Please help. I am out of ideas.
jayboyyyy said:
http://forum.xda-developers.com/showthread.php?t=2536200
Click to expand...
Click to collapse
Isn't this just for the verizon model?
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
I have to believe it can be done, I'm just not getting it for some reason.
I'm really sorry, as I have said in multiple posts. Like I said, I would paypal you a reasonable sum if one of the more experienced people out there want to remote in via logmein and help. I know that sounds lame. I'm normally a guy who likes to research it all himself and do this.
I'm normally the guy who helps other people with this stuff, but I just can't hash this out. I've spent the last three days of my free time reading, researching, trying to get the thing to connect as a drive so I can push files to it and run them via adb.. Even went so far as considering buying a wireless adapter to put the files there wirelessly. I'd try now but I'm exhausted. If you can help, please PM me and we can work out something if you are willing. Thanks to those who have suggested methods. I do appreciate your help. I have tried them all except the last kit kat method which I thought was just for Verizon. I'm with sprint. As tired as I am, I'm afraid to brick the thing. I'm very close to asking for a method to restore the phone and take it back. I really wanted wireless tether. I need it for work and to run the ipad on occasion. Sorry this was a long post/thread.
Sorry I'm not as quick as the rest of you. Just want a rooted phone and can't seem to get it done this time on my own.
Any suggestions?
bullpen7979 said:
Isn't this just for the verizon model?
Click to expand...
Click to collapse
No. That will work for any Moto X Developer Edition or Carrier edition with an unlocked boot loader. So T-Mobile, Sprint, etc.. If you can unlock your boot loader via -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth then you can root via this process.
bullpen7979 said:
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
Click to expand...
Click to collapse
To get your phone to show up in windows as Drive Letter, needs USB Mass Storage mode. Ok, You've installed an app for that, fine... but 1. I'm not aware of that app working, and more importantly, 2. I am not aware of any root method in these forums that requires your phone to show as a "drive letter" to work. So I couldn't even begin to suggest what you are doing wrong.
What instructions are you actually trying to follow? Why not post questions on it in that particular thread, including exact details of what you've done, what you see on your phone, any/all errors or messages, etc.???
And if what you really want to do is tether with sprint, I hope you have checked out threads with suggestions on hacks/ways that work to tether on Sprint Moto X before you worry about rooting.
For example, if you want to remain non-rooted, FoxFi could possibly be an option. As I am a Verizon user and haven't used it, I can't say how well it works for Spint, and I can't say how well it works for Verizon, just that Verizon KK users say it doesn't work, but it did with the JB/4.2.2 roms..
KidJoe;
Thanks for your patience. I'm sorry about all of this. I have tried to be as clear as I can be, but I will redouble my efforts. Let me read clearly that last link and I will post back. I do want root access for all the other cool things it enables too, so I'm determined to get it right. I just want to be careful not to miss something and turn a decent phone into a paperweight.
That link you referenced is exactly what I used to unlock. When I reboot the phone, I get a white screen with a red exclamation point that says bootloader unlocked.
Fox Fi is a no go
Update. Just tried Foxfi. Does not work with current status of unlock but not rooted. I need root, but how does one copy files to the device via usb? I remember there being a setting.
I opened a new thread on this subject. http://forum.xda-developers.com/showthread.php?p=47740046#post47740046
Hope that's not against the rules. I really thing the failure is related to my inability (or ignorance of how to ) push files to the device.
Good gravy. This has eaten up WAY too much time.
Apparently its a mixed bag over at sprint. Some can some can't.
http://www.sprintusers.com/forum/showthread.php?t=234246
I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
Hi, long time lurker here. I want to start by saying how great and informative this site is. Anyway, my nexus 6 came in from the mail like 5 hours ago, did all the updates from 5.0 to 6.0 and it's now running Marshmallow mra58n. Question is should I root it immediately and if so, are there any guides I can follow? Much love to you all, I'm not exactly pro at this kind of things but I can follow instructions since I have competently rooted my past phones which were an HTC M7, M8 and a Samsung Galaxy Note 10.1 tablet.
Thank you.
Edit: Phone is also unlocked, I currently have no SIM card
start here..
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've been looking at the Nexus Root Toolkit since I am kind of confused on how to proceed with anything at all, is that ill advised since I've read that there are problems with the USB cable disconnecting during reboot?
Also, thank you for the reply.
I used the NRT without issue. Just follow the guide step by step.
Sent from my Nexus 6 using Tapatalk
and, dont touch the usb cable while the phone is processing your commands!
j/k, never even heard of the USB cable "problem"
I just used the toolkit today to unlock and root my N6.
Sent from my Nexus 6 using Tapatalk
I rooted last night initially using manual method described in the first link provided, however after some driver issues ultimately used the 2.1.0 rootkit to uninstall and reinstall all drivers. That too alone saved me tons of time and either method is simple if you can follow instructions.
Totally recommend rooting and then experimenting with custom roms, its like getting a new phone everyone you install a new rom.
Have fun!
Kristine,
In answer specifically to your question "Should I...?" my answer is "No". It really depends on what you think you'll get from it - why do you want to do it? What specific benefits do you want?
The reason that I say "no" is that I've been rooted on all my several phones for years, and I've decided that for me the annoyance of having to manually flash ROMs outweighs the benefits - particularly now that Google are releasing frequent security updates. The moment you root your device the OTA (over the air) updates no longer work.
For me the major reason for rooting was to have a firewall. The other things (wakelock detection, double tap to wake, auto-hibernation...) were great but not showstoppers. Now that there is a non-root firewall (Netguard) I'm happy to leave my phone unrooted. I haven't had an OTA to apply yet, so if I have any problems then I might change my mind, but my advice would be to think hard about why you want root before you buy yourself into a world of tinkering...
razortaz18 said:
At the least unlock the bootloader right away. Doing so will completely wipe the phone so it's the first thing I do.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Dammit, are you kidding me? I just downloaded and setup everything, figured I'd do all everything else tomorrow... Oh, well I can do it again I suppose.
Kristine-N said:
Question is should I root it immediately....
Click to expand...
Click to collapse
Because I don't want a white interface, rooting is necessary. Google forces to many things, like forced encryption, useless apps and a white interface (battery drain). When rooting was impossible I would not have bought a Nexus.
Short answer: No!
Long answer: Well, it's sill no, but you can or even should do a couple of things.
First if all, allow OEM Unlocking in development settings. There are gazillion how-tos to switch developer mode on, and tick that switch. Google has borked OTAs already, and if your phone doesn't boot, and the switch is off, then you're boned, you can send it for repair. But if you can unlock you bootloader, then you can flash a custom recovery and make your phone working again.
Second, if you do plan to root your phone in the near future, you should unlock the bootloader now, while it's still new, because it will erase everything (IMHO this would be sufficient as a security measure, the Enable OEM Unlocking is overkill).
As for the main question if you don't have any specific ideas what you want the root for, then don't root your phone. It's a clear and present security risk, and you're just one too many "Allow" taps from letting someone acquire your passwords, clone your IMEI, and download your personal stuff. My motto is, if you don't know what exactly root is, what it does, then you don't know how to prevent exploits that need it to run.
Also if you modify your phone in any way, and that includes rooting, you won't receive the monthly OTAs, and will have to flash it manually.
And finally, don't use toolkits on a Nexus. Spend another hour reading about the matter and you will find out typing adb and fastboot commands is a easy as clicking buttons on toolkits. There is nothing extra in them, they just download the images to flash, and "type" these commands for you.
Unlock bootloader and don't root it for now. After some time, if you feel like you're missing some features that you can obtain only with root, then go ahead. But for now I would strongly recommend to stay stock and see how it goes...
Today i bring you the very first rom for our device.
It's only stock, but the installer includes enough options to keep us happy for a while.
The core installation includes a stripped down system menu with Google play and contacts. I also added, by default, the WiFi fix and hotspot mod. The rest of what you install is your choice.
Aroma options:
Choose which J320 you own
Debloat (fully customizable)
Deknox
Install root
Install busybox
Install Init.d
Install Xposed
Bugs:
None
If you find any let me know, but if you do not wipe, please don't even report bugs.
Link:
Download
Installation:
Flashfire
Enjoy
-D
This uses the same base files for each room, AQG1. So even tho the highest firmware for J320AG is only AQB1 you still get the July security update (minus the new sboot)
All devices are interchangable for me, on Cricket. Depending on your carrier maybe they'll all work for you too.
I have AT&T Samsung Galaxy Express Prime GoPhone, J320A. Owned it for one week. It has been carrier-unlocked. I'm now using T-Mobile SIM. Seems to work OK. Only issue I can find is where the SIM status page does not show my phone number.
I would appreciate pointers or maybe a place to look for installation steps. I assume I'll to need to root via Kingroot then replace with SuperSU (if possible). Then install FlashFire. I have rooted and installed ROMs on other devices (Galaxy Exhibit, 2012 Nexus tablet, Moto G), but seemingly devices are more locked-down these days. I understand that TWRP is not available for this device and likely will not be.
Last year, I bought a couple of inexpensive T-Mobile phones and "rooted" them with KingRoot which is still installed on those phones. (Not really thrilled about that.) I put rooted in quotes because it doesn't quite behave like a fully-rooted phone, IMO. I'm not very expert in these things, but I know how to follow steps and have used ODIN, TWRP, et cetera.
I'm leery of working with these more locked-down phones. Am I being paranoid and/or incorrect about these matters?
BTW, thanks for the ROM! I'm surprised there aren't more replies.
Maybe this phone is not as popular as I think it should be. Maybe it's too low-spec for the tech-savvy crowd. I got mine for just $64 at Walmart online, but they've since raised the price to $79. Seems like a good deal, even at that price.
I paid $15 to carrier-unlock it. I had to flash firmware (modem file?) before unlocking, then flash another file (restored modem?) after unlocking. I was following emailed instructions after the initial unlock procedure failed.
Here's the root thread
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
There's a xposed module that does just that, never tried it tho, and of course it's not permanent.
https://forum.xda-developers.com/ga...pp-sim-changer-change-registered-sim-t2106490
I definitely like the phone and yeah, it's a good price.
Being locked does hurt it tho. No easy recovery and no roms from source. The only thing we might get will be ported. And with no kernel, porting is a pain to track down problems... but i like a challenge
My J3 was unlocked out of the box? Still don't quite get the different names for it though. Rooted with infixremix method and worked fi e until its download caused the dialer to crash whenever it was opened. Still trying to sort out the mess I made of this one.
original stock
hey do any of you guys know where I can get the original firmware to restore this device? mine is the S/W: j320aueu1ape9
on the box it says j320x UD
Odin files are posted here
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
How is this ROM working out?
Can anyone -- or DamienMc, the creator -- post a review of how this ROM is working out? Brief or long; any type of review would be appreciated.
I'm thinking of trying this ROM and I haven't rooted my phone yet.
Although I did unlock the carrier via a paid unlocker site. I'm using it on T-Mobile with no apparent issues. My phone is stock, of course, except for being carrier-unlocked. …Several questions, if I might:
Are those "extra" AT&T and Samsung accounts present? (ref. screenshot)
Are Samsung factory (i.e.: theme-able) dialer, messaging, and contacts apps installed?
Is it still possible to theme the UI with the Samsung theme installer?
Finally, which bloat icons have been purged? (ref. screenshot) I realize one's idea of bloat may vary from individual.
Any feedback or commentary is welcome. Thank you for your consideration.
could it work on J320H?
i know it's for 320A/Az but i want to try it
danny8 said:
Can anyone -- or DamienMc, the creator -- post a review of how this ROM is working out? Brief or long; any type of review would be appreciated.
Any feedback or commentary is welcome. Thank you for your consideration.
Click to expand...
Click to collapse
I'm not going to review it (someone else can)
But I used it heavily before I started work on something new.
It's as stable as stock... cause it is stock Nothing tweaked just the few add-ons to let you tweak it easier.
About the bloat.
I did notice I should have left Samsung account (and maybe billing) with the standard install. Because you can't use the theme store without them. But they're in 'bloat'.
You can always install all the debloat options and have 100% deodex stock and edit to your liking.
hamzaeid said:
could it work on J320H?
i know it's for 320A/Az but i want to try it
Click to expand...
Click to collapse
Sorry bud, different chipset
How do we flash this to our device mainly because twrp and cwm ain't a thing for the j320a. Also I'm using kingroot and I cannot go to su I've tried also flashify does not work either does flashfire how would you go about rooting with su cause I've tried the mrw method and contanstaly it would pop up kinguser has stopped working so do you have another method of rooting the J320A. I just followed the first post about rooting it.
iiFir3z said:
How do we flash this to our device mainly because twrp and cwm ain't a thing for the j320a. Also I'm using kingroot and I cannot go to su I've tried also flashify does not work either does flashfire how would you go about rooting with su cause I've tried the mrw method and contanstaly it would pop up kinguser has stopped working so do you have another method of rooting the J320A. I just followed the first post about rooting it.
Click to expand...
Click to collapse
I just rooted my phone with Kingroot and used the mrw method to remove it well keeping my root. after got Su in my terminal emulator, I deleted the kingroot apk not the app itself. then just installed SuperSu thru my play store and been working just fine for me.
gus8347 said:
I just rooted my phone with Kingroot and used the mrw method to remove it well keeping my root. after got Su in my terminal emulator, I deleted the kingroot apk not the app itself. then just installed SuperSu thru my play store and been working just fine for me.
Click to expand...
Click to collapse
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.
iiFir3z said:
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.
Click to expand...
Click to collapse
Yeah i guess i never had kinguser app or apk i had to delete. Was just kingroot apk that i downloaded and used.
iiFir3z said:
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.
Click to expand...
Click to collapse
After mrc and kinguser crashes you should have supersu. You need to run that first, let it update the files and then reboot.
If su doesn't even get installed, have the apk ready and install.
Another thing you should make sure your really rooted, reboot after king and recheck.
Also what versions of kingroot and mrw are you using?
iiFir3z said:
I'm using Kingroot and I cannot go to SU. I've tried also Flashify does not work. Either does Flashfire. How would you go about rooting with SU…
Click to expand...
Click to collapse
I followed the rooting thread OP directions carefully and had many problems. My initial Kingroot was really ugly and heated the phone. I then attempted to use SuperSU-Me Pro (paid version). It was never able to complete, even after several tries. I struggled using various techniques over many hours. (I did have root with Kingroot.) Nothing would remove Kingroot 5.0.5, and as you probably know, Kingroot won't allow for many apps such as Flashfire. Very frustrating. I probably shortened the life of my phone and battery with all the crap I tried. Many pulls of my battery were needed.
I finally wrested control from Kingroot by uninstalling version 5.0.5 and installing Kingroot 4.5 instead. Then SuperSU-Me Pro did its work. Had I used Kingroot 4.5 from the outset, would things would have gone better? I don't know. The rooting process for this phone is a one-way trip with a dubious outcome. I know the Express Prime is not costly, but if you're risk adverse think twice before trying to root. I suppose you can undo the whole thing, but I haven't tried and likely will not.
Despite the problems I had, I believe using SuperSU-Me Pro was worth the cost and ultimately saved time. I'm glad I rooted my phone, but -- damn, it was a lot of effort compared to previous phones and my tablet.
I have not tried the de-odexed ROM posted in this thread's OP, but it's on my to-do list. I'm kind of afraid of messing with my phone for the time being. I'll post a review if and when I try it out.
For what it's worth, I wasn't able to get my built-in flashlight toggle to work. I ran the fix script via flashfire with no success. Update: Fixed after installing Busybox. Thanks, DamienMc!
danny8 said:
I wasn't able to get my built-in flashlight toggle to work. I ran the fix script via flashfire with no success.
Click to expand...
Click to collapse
You need busybox installed as well
Busybox
Oh, you're very good. It works!
Help! After flashing the rom, it does not let me log in to the google account and I can not exit that screen, the message it displays is as follows:
danny8 said:
I have AT&T Samsung Galaxy Express Prime GoPhone, J320A. Owned it for one week. It has been carrier-unlocked. I'm now using T-Mobile SIM. Seems to work OK. Only issue I can find is where the SIM status page does not show my phone number.
I would appreciate pointers or maybe a place to look for installation steps. I assume I'll to need to root via Kingroot then replace with SuperSU (if possible). Then install FlashFire. I have rooted and installed ROMs on other devices (Galaxy Exhibit, 2012 Nexus tablet, Moto G), but seemingly devices are more locked-down these days. I understand that TWRP is not available for this device and likely will not be.
Last year, I bought a couple of inexpensive T-Mobile phones and "rooted" them with KingRoot which is still installed on those phones. (Not really thrilled about that.) I put rooted in quotes because it doesn't quite behave like a fully-rooted phone, IMO. I'm not very expert in these things, but I know how to follow steps and have used ODIN, TWRP, et cetera.
I'm leery of working with these more locked-down phones. Am I being paranoid and/or incorrect about these matters?
BTW, thanks for the ROM! I'm surprised there aren't more replies.
Maybe this phone is not as popular as I think it should be. Maybe it's too low-spec for the tech-savvy crowd. I got mine for just $64 at Walmart online, but they've since raised the price to $79. Seems like a good deal, even at that price.
I paid $15 to carrier-unlock it. I had to flash firmware (modem file?) before unlocking, then flash another file (restored modem?) after unlocking. I was following emailed instructions after the initial unlock procedure failed.
Click to expand...
Click to collapse
Could you please tell the name of the service/company you used to carrier-unlock it ? (I'm in the same situation) Thanks! @danny8