Related
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
My Nexus 6 has finally shipped! It should be here Friday!
This is my first Nexus and I have never rooted, unlocked, flashed, etc. any of my previous phones.
I have been doing a lot of research and have been considering running CM12.
My question is, should I run my Nexus 6 with stock android for a few weeks and then try CM12? Or should I just root, unlock, and flash CM12 as soon as I get it?
I know that if I wait then I will need to back up all my data because it will factory data reset but I am not worried about that... I understand it is easier to do it right out of the box because you don't have to worry about loosing anything but I can just back my info/apps up so that isn't a big deal.
Also, would you guys suggest something over CM12? Right now I am planning on using CM12 and just getting it setup how I like it then leaving it. I don't plan on always flashing and making changes but I might get sucked into it lol
Thanks everyone!
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
DebianDog said:
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Good point! I don't know if CM is on 5.1 yet. I just assumed it was but I will look into it. This is all new to me so thanks for pointing that out, didn't even think about that!
I won't know what version is on the phone until Friday. But even if it is on 5.0 I am sure it will notify me that 5.1 is ready to download as soon as I boot up the phone.
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
DebianDog said:
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Okay, thanks for the info!
Since I ordered my phone directly from Google, do I need to debloat? Or is that just for carrier versions?
mlin said:
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
Click to expand...
Click to collapse
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
CFrance said:
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Click to expand...
Click to collapse
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
gee2012 said:
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
Click to expand...
Click to collapse
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
DebianDog said:
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
My two cents. I don't think you've dealt with enough newbies. on another forum it was me and a group of others that would help people get their phones out of boot loops and soft bricks. I have literally helped hundreds of people get their phone back.
even if you look here on XDA you'll see people trying to flash the wrong files download files that are not even for their phone, are following a dated instruction or don't really understand how directories work.
Sent from my Google N6 on VZ
DebianDog said:
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
Click to expand...
Click to collapse
Thanks for the info! I actually had just downloaded this program over the weekend and was planning on using it once I do decide to root... which I am thinking will be as soon as I get the phone. lol other than that I think I am going to run it on stock for a while at first and wait until CM is on 5.1 for a while....
mlin said:
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Click to expand...
Click to collapse
Thanks! I am planning on rooting and unlocking right away for TB and maybe a couple other little things like lightflow just for fun. Being the nerd that I am, I have a feeling that once I start playing with the whole rooting, unlocking, and flashing stuff I am going to really enjoy it.
gee2012 said:
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the reply! I see what you are saying, I had already come across Wug's toolkit over the weekend and was planning on using that because it seemed so simple.
However, seeing how I still have two and a half days until my phone will be here, maybe I will look into the manual way a little more to decide which route I want to go.... Any suggestions on where to start? Threads, videos, etc?
Thanks!
Boot into download mode, Unlock bootloader, reboot, boot back into download mode, fastboot twrp recovery, boot into recovery, reboot via recovery and install su when prompted. When you boot into android you will be prompted to update su. You now are rooted. Only other thing I would think about when you first get your device is if you want forced encryption. You will be required to wipe SD data if you decide to go with non forced encryption.
I loved cm on my previous touchwiz devices because I like stock/asop style. I find cm has bugs in early os update releases. I would only install cm if i took advantage of themes which I don't.
CFrance said:
Any suggestions on where to start? Threads, videos, etc?
Thanks!
Click to expand...
Click to collapse
You can waste a lot of time while you're waiting for your phone in this thread http://forum.xda-developers.com/showthread.php?t=2992769
ROM Reviews (5.1) + Nexus 6 Hacking: NRT · Apps · Utilities [3.22.15]
Sent from my Google N6 on VZ
Ok, so my old Nexus 6 fell 40' down a pipe chase while I was soldering some 4" copper water mains at work. Needless to say it was destroyed.
Got the replacement phone from insurance, went to plug it in to the computer to unlock and root it, but the computer won't recognize it, even though it had no problem recognizing the old phone. I checked, and device manager says unknown device with the little yellow triangle on it.
Android sdk tools are installed, as are the latest Google drivers.
I followed the instructions in the All-In-One thread for getting the computer to recognize the device, but it doesn't seem to be working.
Should I uninstall the sdk tools and the drivers, and redo them all?
Or does anyone else have any other suggestions?
Thanks.
the Nexus Root Toolkit can help you set up drivers, I'd give that a shot.
i was always told to not use toolkits...
i went ahead and deleted both the sdk and the google drivers, and reinstalled them, and everything is working now. unlocked and got twrp back, making a backup now, then on to root.
any idea if we can get regular root on mmb29v? i don't think i want systemless root... or do i? is there a link that i can read to learn the difference between the two and why one is better than the other?
People on this site recommend not using NRT for *rooting*, but NRT is more than just a rooting tool. It's a fantastically-well-programmed kit which helps with all parts of the process - as you've just discovered yourself (or did you not use NRT?). I've questioned (what I perceive to be) the kneejerk antagonism towards toolkits, but I think that the more experienced members recognise and admit that toolkits have their place once people take the time and trouble to understand what the toolkits are doing so that when they go wrong people don't plague the forums with questions that have been answered dozens of times already.
Yes, you certainly do want systemless root. It makes things like Google Pay (or whatever it's called - I wouldn't touch it myself) work, and it potentially makes OTA upgrades work. There is no benefit that I know of that would make system root better than systemless, though I'm just an uninformed end-user of other people's expertise...
(P.S. As an aside, unrelated to this query, can I ask generally that people don't respond including the entire original message unless the thread is so fantastically busy that the reply would make no sense? I wade through dozens of posts which repeat again and again the post I've just read directly above the reply. It's a waste of space, processing power and my time to have to look for the reply following the 50 lines of repeated comment above it. If you're responding to a specific point, copy and paste that particular point into your reply, not the entire 200 lines... You get me...?)
no, i didn't use nrt. i did the fastboot flash of the oem unlock and recovery.
as for the systemless root helping with ota, i had systemless root on my old nexus 6 and it wouldn't allow me to do ota's. i also don't use google pay.
it also seems easier to flash custom rom's when you have system root as opposed to systemless root, but maybe i am wrong?
Yes, I think that even Chainfire accepts that his systemless root won't work with OTAs unless you use the built-in unroot function before trying the upgrade. I mentioned it only because I was rooted with v2.68 and the N preview installed regardless, which surprised me. I dont think that the same happy event occurs with ordinary security OTAs.
I don't believe installing a custom ROM is affected in any way by the root method, since you lose it anyway.
And I'm sure you've gladdened many hearts tonight with your comment "i didn't use nrt. i did the fastboot flash of the oem unlock and recovery."...
i know for installing purenexus, there is a difference between system root and systemless root. nathanchance gives a description for updating purenexus with systemless root, but not for installing it fresh.
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
you can downgrade and then you can root
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os. Is it required to side load?
Ubuntu_noobi said:
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os.
Click to expand...
Click to collapse
Wrong procedure. See forum index for details, in particular the first two posts in this thread.
Ubuntu_noobi said:
Is it required to side load?
Click to expand...
Click to collapse
Yes.
So glad I found this post. Researching the same thing. Trying it out now
Sent from my iPhone using Tapatalk
yungskeeme01 said:
So glad I found this post. Researching the same thing. Trying it out now
Click to expand...
Click to collapse
Any new info to share? I still haven't been able to figure it out
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
What exactly are you trying to "figure out"? Responded a few days ago with downgrade/rollback links which includes a step-by-step video.
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
I downgraded to 5.3.1. Rooted the fire and am now running CM 12.1. Very smooth!. Took me a awhile to get since I have a Mac but got it working. Used Rootjunky's YouTube video on how to restore. That's how I downgraded. Then used his Supertool for Mac and rooted. I then installed Flashfire and put CM12 on the tablet.
Sent from my iPhone using Tapatalk
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
Davey126 already answered it here.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
amerkiller1995 said:
I used KingRoot directly and decided not to replace it with SuperSu.
Click to expand...
Click to collapse
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
amerkiller1995 said:
Davey126 already answered it here.
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
Click to expand...
Click to collapse
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Davey126 said:
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
Click to expand...
Click to collapse
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
yungskeeme01 said:
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
amerkiller1995 said:
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
Click to expand...
Click to collapse
Sorry if I misread it. I used the version included and KingRoot so I replaced it in Supertool and re-rooted using SuperTool and it removed it no issues. Whatever though, it got rooted one way or another!
Sent from my iPhone using Tapatalk
Awesome I will try again tonight
Solved!!! Finally!!!
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
TL;DR: THERE IS NO "One click" OPTION THAT WORKS. I DOWNLOADED ALL OF THEM. IVE TRIED EVERY DAMN ONE OF THEM. STOP SEARCHING. You MUST side load the system with the code necessary to make it capable to root. Downgrading to 5.3.1 was the secret, instead of trying to root on 5.3.2. I made a glossary of the confusing terminology, made a step by step walk through for noobs
SO, having felt encouraged by the response by people on this forum, last night I decided it was worth another try.
I finally figured out what I was missing. IF YOU CURRENTLY HAVE FIREOS VERSION 5.3.1, YOU MUST ROLL IT BACK THRU SIDE LOADING see here: SIDELOAD TUTORIAL
I tried to load straight onto the system disk and caused all kinds of problems. Once I followed that step by step, which TBH, was a lot of pausing and rewinding. I am not familiar with many terms so I made this...
Android Common Terms:
Boot: A sequence of commands written into the underlying software that tells the device what order to operate in
Bootloader: See Previous (this is the sequence I referenced previously)
Locked Bootloader: Think of trying to edit a PDF you did not create... Exactly.
ADB Fastboot: THIS IS A PROGRAM... NOT A FUNCTION. I still get this confused, thinking that it is a quicker version of the boot sequence... IT IS NOT. ADB Fastboot is a program that gives access to the base software code making it reachable to use certain sections of to "edit the PDF".
Custom Recovery: It is the new version of Windows 10 you were updating to when your crappy laptop you JUST bought came with Windows 8.1. Essentially.
Root: Remember the PDF? Well, if you work somewhere that has Adobe Reader, and you see the window on the right pop up with the ability to login to Adobe Online or whatever? Well, rooting is having login credentials to ACTUALLY edit that damn PDF.
Flash: Download from the internet, and install on your hard drive, or SD Card. It actually means you erase whatever is there completely first, then install. It's two steps, which is why they don't just call it installing... I think.
Partition: Have you ever worked in an office with cubicles? Exactly. A partition is a wall that you put up to segregate files, or programs, or whatever.
SuperTool: Based in your computer. RootJunky Went through and basically made one tool that has everything you need for rooting. PROBLEM IS THAT HE TELLS YOU TO DOWNLOAD ADB FASTBOOT AND DRIVERS AND A BUNCH OF STUFF, then says, or you can just download the SuperTool, which means, I now HAVE TWO OF ALL OF IT, and then I spend the next three hours trying to figure out if its the "custom rom that I sideload into the TWRP, or if the Flashed version of the bootloader gets added to the recovery image, but not before the drivers are flashed into the fastboot."
While this doesn't cover a lot, I hope that people in this community understand what it is like for someone unversed in the lingo to grasp exactly what is going on. I don't think we should speak like idiots and elementary students, but I also think we lose a ton of people that may have something to offer one day because they got frustrated with the terminology and gave up. Luckily, I stuck it out and gave it one last chance and I got it.
So, once I downgraded from 5.3.2 to 5.3.1, I went about trying to root the device, which was also a little confusing.
Step 1: Downgrade if you have 5.3.2 to 5.3.1
Step 2: Enable ADB and Debug in the Settings
Step 3: Hold down the Power and Volume Down button, release the power button once the device starts to reboot and a menu will popup
Step 4: Use the volume keys to access the first selection. This is how you access the "sideloading".
Step 5: Open the SuperTool, click on the batch file which should say Auto... because calling it SuperTool would be confusing
Step 6: follow the super easy instructions. Honestly.
It will walk you through the process and get you to the part about Kingroot and FlashFire and eventually root the device.
I honestly hope this helps someone. God knows it would have saved me from spending approximately 30 hours trying to figure this out.
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