PSA Sprint Gingerbread root - Galaxy Tab General

psneuter & rageagainstthecage only work for Froyo and below.
gingerbreak only works for 2.3.2 and below.
Sprint update EF17 is 2.3.4
That means none of those exploits will work. That means you can't just boot up SuperOneClick and expect it to root the new ROM.
With that in mind, could everyone please stop posting about their failed one-click rooting attempts.
I know, it's well intentioned, but it's not helping.
Now, there is no known exploit readily available, so there are two options:
1) Compile & flash a ROM already patched with root/superuser.apk
2) Build an update.zip file that that does the patching and run it from recovery.
Both of these have been done plenty of times in the past on other phones, and there is nothing to stop them from working. Expect to see one or the other from someone who knows how (not me) in the near future.
Till then, don't even bother with the one-clicks.

Good Post! I, myself, read all the information regarding the upgrade, and realized from the awesome Devs that root would not work until they get a chance to have it in hand, and see if there is an available exploit.
If people would just relax a little, and give some of these Guys/Gals a chance to take a look at the code, and see what they can do, it would make the forums a wee bit happier..

that's right, i personally went through all the existing methods but no luck
this makes me wanna go into android system dev. now im staying on android app dev but it seems that it is not enough. hopefully i can have more time to learn system tweaking after i finish my current project.
until then, it's all on you guys good luck. for all the devs out there, thank you for your great works, saving us from this unrooted system BS

Related

Does anyone know of an ongoing effort to root the Cliq?

I'd like to toss my hat in the ring if anybody needs a guinea pig.
I've tried asroot2 and some of the other Behold2/etc. rooting guides, but when I run this:
./data/local/try3 /system/bin/sh
I get this:
[1] Killed ./data/local/try3 /system/bin/sh
And nothing seems to work.
thats the same thing we get on the droid with this. Might want to check other forums, as most people that get the cliq are not gonna check xda, at least i wouldnt think they would. The owners of the Droid have our own forums now, as well as a couple Google waves on the subject of rooting our device and an irc channel.
fallingup said:
thats the same thing we get on the droid with this. Might want to check other forums, as most people that get the cliq are not gonna check xda, at least i wouldnt think they would. The owners of the Droid have our own forums now, as well as a couple Google waves on the subject of rooting our device and an irc channel.
Click to expand...
Click to collapse
sigh... if only XDA could have become the home of Android (heck all of their other forums are empty!)
suffice to say - I am working on building a ROM for cliq using the source
but to begin to do any testing, I need root lol
Where are the forums you guys use?
wesgarner said:
sigh... if only XDA could have become the home of Android (heck all of their other forums are empty!)
suffice to say - I am working on building a ROM for cliq using the source
but to begin to do any testing, I need root lol
Where are the forums you guys use?
Click to expand...
Click to collapse
was going to start a thread to put the link for the source code, but since you already have it, i'll put the link here for other people to stumble across.
https://opensource.motorola.com/sf/frs/do/viewSummary/projects.cliqdext/frs
I'm not to familiar with linux or source codes and such. But someone had mentioned in another forum I came across that the source code may have a clue about gaining root. Maybe its in how the programing would interact with the SPL? Does the O/S need some kind of permission from the SPL to run with the hardware? It is the SPL that is blocking/locking down root right? So if the OS needs ROOT to be able to run, then shouldn't there be some code in the source that ask's the SPL for permission for root? And if so, once we have that lil' bit o' code, it can be ran via a script and/or ADB? Like trick the SPL into thinking its the O/S asking for ROOT?
Many of us do have the CLIQ. I would be more than happy to be both a guinea pig as well, and donate $ to whomever can figure this out. The extra RAM on the CLIQ and the glass screen make it so much nicer than the G1 + MyTouch, pending it ever gets rooted...
http://droidle.org/?p=208
I've been trying to follow the CLIQ root as closely as possible.
Drew
im so with this guy i need apps to sd on my click lol i think we all do my internal memory is [email protected]!!!! im excited to read on !
state of the root address, AFAIK
A guy has an image the equivalent of the dreamimg.nbh used to root g1s recovery mode looks for this file and will apply it if found automaticly.
He said its rooted and ready to run, the difference is with the g1 we had the developer keyset which we replaced the original one on that came with our phones so they would ignore OTA updates (since the keys don't match) and so they would take updates that are signed with the PUBICLY available keyset the OTA keyset we don't have...
So to get to the problem, the rooted update can't be applied unless the "moto keyset" gets leaked or a developers keyset exists and it is possible to change it with the secured version of fastboot, which it seems is also the reason goldcard exploits (and others) didn't work.
Does Moto offer a "developers" cliq? Id assume not or we would have the keyset, but I dunno if the keyset is unavailable or if there is a problem in using the key to sign the package?
Anyway that's how I see it with all the searching I've done about this topic, I would also give up all the blurbloat for a stock cyanogen googglyfone.
Bhang
Cliq root website
cliq-development.com
or the new one:
demoshadow.com!
we are getting close! its an entire website devoted to rooting the cliq!
It's been done!
http://modmymoto.com/forums/showthread.php?t=526469
jiktheworm said:
It's been done!
http://modmymoto.com/forums/showthread.php?t=526469
Click to expand...
Click to collapse
I've run into two people who have rooted thier cliqs using this guild. one attempted to unroot to enable OTA for the 2.1 release, the other rooted and tried to update the radio via the moto update.zip
both involved the moto update.zip
reroot your cliq, defang the moto update.zip by removing recovery.img and boot.img from the zip file before flashing, all worries should be gone.
new radio witch addresses the clock conflict and keeps your cliq rooted with recovery
NuroSlam said:
I've run into two people who have rooted thier cliqs using this guild. one attempted to unroot to enable OTA for the 2.1 release, the other rooted and tried to update the radio via the moto update.zip
both involved the moto update.zip
reroot your cliq, defang the moto update.zip by removing recovery.img and boot.img from the zip file before flashing, all worries should be gone.
new radio witch addresses the clock conflict and keeps your cliq rooted with recovery
Click to expand...
Click to collapse
and yes i do believe this was an intentional bricking of all rooted phones by motorola

Problems with the root!

Hi, my phone now is working and all ( the is it bricked post) Thanks guys
Here is the new problem...I would like to go to 2.2.1 ( the passimg.zip is 2.2) is there a way to update without unlocking bootloader.
I tried Androot and superoneclick....Androot gives me the Fugu message and SuperOneClick says its Rooted...but when I go to rom manager or other apps that need superuser...
I get this message : An error occured while attemting to run privileged commands!
So basically Root isn't working.
Also, when trying to install Cyan cm6...Rom manager reboots...but I get the Triangle with the exclamation point with the green man next to it...
Is it still possible to have my cake and eat it? ( locked phone, with root access so I can install modded roms)
Again...can someone help me with this
Thanks!
You didn't have to make a duplicate post. I already answered one of your questions in the other thread.
Dont make another post next time...
I rooted FRG83D with superoneclick root, But if its not working for ya you will have to unlock the bootloader via fastboot. Then push a custom recovery. With the recovery you can install the su binaries.
Manual root:
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Ok i'll only answer here now for this question:
I don't want to loose my warranty. Hence the softroot way.
I thought of something dunno if its possible:
is there a stock FRG83 image like the FRG33 I just installed....maybe 2.2.1 will be compatible with androot or superoneclick
Thanks
You need to do a few things before you go any further. There are key steps you are leaving out that are just a recipe for disaster. I'll detail them below, in the specific order you should follow them. There shall be no deviation from this list.
1 - Put your phone down. Seriously, stop messing with it. Just quit.
2 - Read the Wiki that you've been linked to, in both threads, several times.
2a - Now that you've read the Wiki, really read the Wiki. Yeah, you skimmed it the first time, I know you did.
2b - Now go read it again. I'm sure you'll notice something new this time.
2c - Now go read the links in the Wiki. Explore those threads.
2d - Those threads that the Wiki links to? They have links in them. Go read those.
3 - Rinse and repeat all steps from 2a to 2d for, oh, about 4 days. During this time you are allowed:
To post general chit chat on the forum. No technical stuff, no help threads, no questions. Just read. If you have questions, you need to read some more.
No more than 3 app installs per day, from the market. Thou shalt not download and install any APKs from any source that is not the Android Market.
To tweak settings on your phone, provided those settings are all done via the touchscreen on your phone. You shall forget the acronym "ADB".
Once you've done that, you'll root your phone in no time, and you won't be worried that you've bricked it. Then, and only then, can you start asking questions.
Why? Because all of your questions right now are answered. You're jumping the gun, and it's obvious you haven't done much research at all. Seriously, go read.
I hate to be mean, but if you want to understand stuff, you need to try and understand it on your own first. You're here looking for solutions (that are already spelled out) to problems that you created (because you didn't read anything). Quit looking for the easy way out. If you want to enjoy your phone and the features of what you're trying to accomplish...put some work in yourself, and stop expecting everyone else to fix everything and spell it out. People here are more than happy to help, but you gotta start helping yourself.
@Soberguy: Thumbs up to you. Couldn't have said it any better.
musashiken said:
@Soberguy: Thumbs up to you. Couldn't have said it any better.
Click to expand...
Click to collapse
Thanks, mate. Didn't mean to quote the guy above me, just noticed I did that. Fixed it.
I'm amazed at the patience some folks have. Maybe it was my rough 3 day weekend that's left me a bit short... Appreciate the thanks, all the same.
Ok, I do go a bit fast.
I'll read...it just that I tried the cm7 mod ( i know its experimental) and the phone
would'nt boot.
With the help of the great people on the board, I got my phone working again but on FRG33 (2.2)
My last question was if it was possible ( or someone knows of because Ive checked the net) to root without unlocking ( androot and superoneclick that i know of) if I have FRG33 ( Because Ive been getting permission errors)
Finally, I wanted to know if a FRG83 stock image was available so that I could recover to it without unlocking bootloader. (or any other stock that lets me root without unlock)
I'll unlock the phone as a last option...I'm sorry...And if anyone is pissed at my posts ...well sorry I just taught some of you experts could help.
pooky2010 said:
Ok, I do go a bit fast.
I'll unlock the phone as a last option...I'm sorry...And if anyone is pissed at my posts ...well sorry I just taught some of you experts could help.
Click to expand...
Click to collapse
See? Looking for the easy way out again.
It's not about anyone being pissed or short on patience. Look at how frustrated you are with the situation. You're frustrated. Why? Cause you did it wrong. Why? Cause you didn't read enough first. Even after several suggestions, you still want it done, with help, right now, or you'll sulk about someone pissed and how no one held your hand through it.
Is it possible to do what you want? Absolutely! Pretty easy, too. But if you read and help yourself, you'll better understand how to update in the future, as well as how to root the future update. Or, you'll learn how to root what you have, and flash a pre-rooted stock ROM (yes, those are here as well).
So call me an ass, cool. You did in your mind, that's fine. But really, I'm trying to let you know what will help you the most, and that's having a better understanding of how to prevent a boot loop in the future, or at least how to fix it if it happens. Best of luck, man.
Sent from my Sexy Nexy, courtesy of the fine developers of Tapatalk
Here's the deal.
I did a one click root without unlocking the bootloader. Then I installed rom manager and flashed clockwork recovery. Then I did a backup ( both done in rom manager) then I went back into rom manager and installed cyanogenmod 7 and my nexus is now haxored gingerbread. Make sure you do a full wipe before flashing new roms and it'll always work.
I didn't update my radio, my hboot or anything like that. And it all just works and is dead simple. I would suggest trying z4root or universal androot and then downloading rom manager from the market.
How you managed to **** up something so simple is pretty funny dude.
I'm using an at&t band n1 with an smiled. Not the one with super LCD. I heard a rumor that the super LCD n1s have problems with certain mods. You might want to figure out what type of screen you have too.
The cyanogenmod wiki at cyanogenmod.com might help you too.
Sent from my Nexus One using Tapatalk
OP, you have to learn the hard way. Stop using "newbie" as an excuse.
I was also a "newbie" when I first got my Nexus One in February. Everything about android was new and alien to me. It actually took me a couple of months of lurking in xda and reading up on tutorials before I took the plunge to rooting my phone. And I did not bother anyone on that. I made sure I understood the steps and triple checked every move I made in following instructions even though I did not understand them.
I also was worried about warranty and actually did the manual way of rooting my phone without unlocking the bootloader using some method that involved cutting a piece of plastic from my battery. That was nerve wrecking and no where as simple as the superoneclick thingy you have now. Yet I survived and I did it on my own.
I must admit that you have to be a little bit confident in using computers and have some basic knowledge of typing commands in cmd. But everyone has to start from somewhere.
Seriously if it's too much trouble or too complicated, maybe staying stock or going Iphone is a more comfortable alternative.
I'm actually pretty good with computers...
Also, I have bricked 4 phones (the provider took them back) fooling around...
I could brought this one back ( they didnt check). But I want to learn...I'm pretty impulsif...Anyway so far
With FRG33 z4root works (read thanks)
Now I trying to flash clockwork...( when I download cyan 6 +google apps) it reboots but I get the triangle thingy...I click power volume up ( read that thanks) I get a blue menu...I kinda scared to click an option so I rebooted...I'm trying to use rom manager for updates because its really simple ...anyway
Thats it for tonight All of you guys are nice dudes and I'll learn and will try to help im my own way...I know I'm a newbie that likes short cuts (hell I read all day at my day job...lol) This is fun ( playing with male toys)
Thanks guys!

[Q] A Request and Warning from Evo owner

First I am coming across product threads to request some information. As stated in my post, "I" am an Evo owner and are pretty well versed in rooting procedures flashing etc. It is my second hobby having rooted eight Evo's and de-facto maintaining them for friends and co-workers. I'm somewhat a flashaholic. However, my wife owns an Epic and recently has asked me to root her phone. Being so involved in the Evo community I really haven't had the time (or desire) to get immersed in a whole new system. So because of my procrastination, I would like to ask two simple questions and I will figure out the rest. For the Epic:
1. What is the quickest, most fool proof way to root and get permanent "S-on"?
2. What are a few of the most popular ROMs/kernals in use?
(I have a full evening to read and get this done, but reading through all the post will take a week so pointing me in the right direction would be a great help. Plus I don't want the OTA pushed to her phone and be locked out for weeks until a new exploit is found).
Now for the warning. I see many asking "what if I accept the OTA and I am rooted"? A warning from what happened with the Froyo update for the Evo. Those who accepted the OTA for the Evo were without root for nearly a month because a new exploit had to be discovered. The first root procedures were long and difficult (no one click roots here, the learning curve was pretty steep). Eventually easier exploits were found and posted but in the long run, accepting the OTA simply was not worth it. The funny thing is I had the official Sprint OTA (rooted) running five hours after it was released! So hold your horses if you are rooted but just itching to accept the OTA. You WILL lose root and it may be a while before you get it back. One of the manufacturers goals is to patch the root exploits and make it as difficult as they can to root it again. A rooted version of the OTA almost always pops up within 12 hours after release.
Thanks in advance for any replies and good luck, congratulations for the long overdue update!
There are only a few ROM choices at the moment as most chefs/devs were waiting for Froyo and source before developing for the Epic.
Samsung uses a proprietary RFS file system. If you plan on flashing one of the RFS based ROMs, use this One-click to install CWM and root-
http://forum.xda-developers.com/showthread.php?t=770388
If you plan on going with ext4 file system, use this One-click root and CWM installer-
http://forum.xda-developers.com/showthread.php?t=897612
Bonsai is a very nice/popular ext4 ROM.
Also, I suggest you familiarize yourself with Odin(Samsung flashing utility), as you might need it if something gets borked along the way.
aburgthing said:
First I am coming across product threads to request some information. As stated in my post, "I" am an Evo owner and are pretty well versed in rooting procedures flashing etc. It is my second hobby having rooted eight Evo's and de-facto maintaining them for friends and co-workers. I'm somewhat a flashaholic. However, my wife owns an Epic and recently has asked me to root her phone. Being so involved in the Evo community I really haven't had the time (or desire) to get immersed in a whole new system. So because of my procrastination, I would like to ask two simple questions and I will figure out the rest. For the Epic:
1. What is the quickest, most fool proof way to root and get permanent "S-on"?
2. What are a few of the most popular ROMs/kernals in use?
(I have a full evening to read and get this done, but reading through all the post will take a week so pointing me in the right direction would be a great help. Plus I don't want the OTA pushed to her phone and be locked out for weeks until a new exploit is found).
Now for the warning. I see many asking "what if I accept the OTA and I am rooted"? A warning from what happened with the Froyo update for the Evo. Those who accepted the OTA for the Evo were without root for nearly a month because a new exploit had to be discovered. The first root procedures were long and difficult (no one click roots here, the learning curve was pretty steep). Eventually easier exploits were found and posted but in the long run, accepting the OTA simply was not worth it. The funny thing is I had the official Sprint OTA (rooted) running five hours after it was released! So hold your horses if you are rooted but just itching to accept the OTA. You WILL lose root and it may be a while before you get it back. One of the manufacturers goals is to patch the root exploits and make it as difficult as they can to root it again. A rooted version of the OTA almost always pops up within 12 hours after release.
Thanks in advance for any replies and good luck, congratulations for the long overdue update!
Click to expand...
Click to collapse
One-click root as linked above is the fastest way. It's also stickied at the top of the forum. The one titled " Samsung Epic 4G Wiki - CLICK HERE AND USE THIS BEFORE POSTING".
We've been running leaked FroYo for months, and root was not an issue. Kernels compiled from the OTA source have not had root issues either.
I too am an Evo owner and was flashaholic until I found myn's Z with the SBC kernel and DT's a2sd with Davlik running on SD. With that said, I also own a Epic and have switched back and forth due to the GPS bug and no DT a2sd. I've finally settled on something that works though. I've used Superoneclick universal root since it's extremely easy, tried all of the roms until I settled on Truly Epic Rebirth 1.5 with EXT4 support since it's the only one that gave me consistent GPS (I use GPS alot being in Medical sales) and then I used the one click odexer tool to speed it up and reduce my Dalvik cache footprint. No DT a2sd but I have offered tkirton $50 to port his app over so I can use it on my epic (Just waiting on him when he has time).
I am new to android as the Epic is my first android phone. The easiest root option I have seen is the one click 2.5.5 in dev section. For roms I can't offer a suggestion but would wait until 2.2 drops. And for the warning all of the leaks were rooted with the same one click method. So unless they did something drastic rooting will not be an issue after the update. Plus I am sure the devs will have prerooted roms out within a few hours of the release.
Sent from my SPH-D700 using XDA App
I have an Evo and an Epic. Everyone here seemed to answer your question already but I wanted to inform you there is no "S-OFF" with the Galaxy S series. That security feature is only apart of HTC Android phones as far as I know. A simple "OneClickRoot" is sufficient for full access to the system.
Thanks for all your replies. I guess it's time to get busy!

[Q] Root for US OTA 2.0

So I'm going to go out on a limb and say that there is no solution to root a TP that's already applied the 2.0 update?
I've tried the root methods already obtainable on here and they don't work. I'm guessing (more hoping) that someone is working on finding a solution.
Makes me sad. A co-worker updated it for me because "it said it needed to update it so I did it for you"... *sigh*
OTA2 removed the exploit unless you were already rooted and used Voodoo Rootkeeper to maintain root during the update. I haven't heard the outcome with regards to 2.5. I don't want to risk root so won't be updating unless it's safe.
2.5 is out ? which your version of tablet ?
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Either people like us find a way to downgrade or wait until a new exploit is found. The former seems easier but my knowledge of these things isn't very high...
Yeah, I'm not sure how to either. I'm good at following directions but when a "friend" upgrades your device for you...
As for downgrading, I don't think that'll be an option until someone finds a Lenovo rom flash utility.
byersbw said:
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Click to expand...
Click to collapse
2. 5 was not available to US last week. How did you get it? Supposedly it's still going through certification. 0086_US is 2.0. What version are you?
Oh hell.... I've been reading too many posts on the Lenovo forums. My apologies, I am running OTA 2.0 NOT 2.5. I will correct my first post and title.
I'm running ThinkPadTablet_A310_02_0039_0086_US.
Okay. Thanks. No worries, but was scratching my head, looking puzzled.
Haha! I can understand. I have that look a lot sadly. I appreciate you telling me as I had no clue as to what exactly I was saying.
Now, if anyone knows someone on the inside at Lenovo that could get the flash utility...
LOL If only.
And now we wait. Did NOT expect CM9 to come out so fast and be working so didn't care much for root otherwise. Oh well, that was my fault and I knew I'd lose root for the time being. Now I wait patiently, since the primary work of the developers now is making CM9 to work properly so w/e.
Why isn't there a way to downgrade the rom to 075? The tab has a recovery boot. If it could be downgraded, it could then be rooted , then updated.
No way to downgrade, unless you know something the rest of us are unaware of. There's a bunch of folks that either can't root at all, or took OTA2 before getting root/without preserving root. We've been told that there's nothing to be done for the time being.
I don't know how to do it, but I know that's how other tabs got around the problem. I only say it in case someone does.
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Thanks. Noob enough that I couldn't explain it, just knew it doesn't work.
YassinTP said:
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Click to expand...
Click to collapse
I wonder what it takes to defeat the check? There must be an update script that performs that check. Editing elements of the update script has been the key to other "can't be done" situations.
http://forum.xda-developers.com/showthread.php?p=22918839[WIP][4.0.3]ICS CM9 ThinkPad Tablet PORT
I'm going to keep putting forth suggestions instead of claiming something can't be done. Afterall, the point of this entire forum is to work togther to overcome obstacles.
While I don't know a lot about these things, if it could be done, it would have been. This forum is overflowing with posts from owners of all kinds devices asking how to downgrade their respective device so they can take root. It's not an uncommon request, and one that I have researched for another device, only to find the same answer. Hey if you find out how to do it, you'll make a fortune.
Two other tablets, the Flyer and the View downgrade to gingerbread, then unlock bootloader, then root, then update to honeycomb, then custom roms are applied. They got the idea from another tab, the Iconia, who got it from the Transformer . . .
I'm just trying to push good and bad ideas to someone with the skills. It's about not taking 'no' as an answer.
Here's the thread for Flyer/View:
http://forum.xda-developers.com/showthread.php?p=21028879[Procedure]No HTC unlock downgrade HC-GB for official OTA

[One Stop Shop] How to root the Moto X - Let's end the confusion.

This thread is to help people figure out what root method is for them and where to go to find out how.
Please simply direct members to this thread or the individual threads for each method.....there's no need to repeat this stuff in thread after thread. A quick link and good luck message keeps XDA clean.
Please send a thanks (with that little thanks button thingy) to these dedicated members who worked hard at these guides and methods.
***A WORD of WARNING!!!*** No matter the model, dev edition....locked bootloader, unlocked bootloader.... Doesn't matter....NO MOTO X can be safely downgraded from 4.4.2 or higher. Not without GREAT risk. (4.4 can be downgraded to 4.2.2 POST camera update for SlapmyMoto root method...but NOT to 4.2.2 PRE camera update.....that will equal a guaranteed brick.) Got it? Good!
Further, due to security features of the phone, the parts which past root/disable write-protection processes exploit, will fail to downgrade, so for those with locked bootloaders you couldn't use the processes for previous versions anyway.
Unlocked Bootloaders (Any Android Version)
Note: See Post 70 for Bootloader Unlocking info.
So, you got a Dev Edition or another model that can have its bootloader unlocked.....awesome! You got it made! Doesn't matter what Android version you're on, the procedure is the same.
Too root, see this awesome GUIDE . There's a section on "How to Unlock your Bootloader.". And a section on "Rooting Unlocked Bootloader." OR after you unlock your bootloader you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 Please be sure to use the latest TWRP fastboot IMG file and Installable ZIP of SuperSU
Easy! Done!
Don't know if your bootloader can be unlocked? See Post 70
Locked Bootloaders on 4.4 or lower ONLY (At&T, Verizon and Republic Wireless...and those who just don't want to unlock their bootloader, due to warranty or whatever.)
Now it gets tricky!!!
For devices still on 4.4 or lower you can root AND disable write protection! Awesome!! But....to stay this way...you can never upgrade your android version past 4.4. As it stands today anyway.
Again, see this great GUIDE and read the section on "Rooting Locked Bootloader.". This is quite involved and takes some work. Read read read....and proceed carefully.
(Thanks to @jcase for creating the methods used to achieve this. ��)
If you're already on 4.4.2 or higher....sorry, this will NOT work for you. And no, you can't downgrade from 4.4.2.... Not without great risk!!! Whoever says otherwise....is just plain wrong.
If you have a LOCKED Bootloader and are on 4.4.2 or lower, You could try JCASE's SUNSHINE tool. It will check if your phone is compatible first, if it is and you want to proceed, you will be charged about $25 USD. If it works on your phone it will Unlock the bootloader without destroying data and without needing a code from Moto or the former China Middleman option. For more, please see -> http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 and/or -> http://forum.xda-developers.com/showthread.php?t=2792487 Once your bootloader is unlocked via Sunshine, you then root the same way developer edition or other unlocked bootloader users root (flash TWRP, boot into it, and let it root, or flash SUperSU).
Locked Bootloaders on 4.4.3 and 4.4.2 (Tho, for 4.4 or lower, the method above will give you write protection disabled....a big plus!!)
Well, you can achieve root, but unfortunately, write protection will still be enabled. Meaning...no writing to the system partition, and any changes you make, root wise, will reset after a power down or hard reboot. So some root apps will work fine....and some may not.
This app by @iKrYpToNiTe combines towelroot with pie and is very simple to use. Works up to Android 4.4.3 Check out this thread for his TowelPieRoot for the Moto X app!
Locked bootloaders on Android 4.4.4
Unfortunately, there is no root method for you guys as of today. And again....no....you can't downgrade. Not without significant risk., and even if you could downgrade, due to security features of the phone, the parts which past root/disable write-protection processes exploit, will fail to downgrade, so you can't use those old processes anyway.
Update: There is a VERY RISKY method to root for Verizon and ATT 4.4.4 users that have a LOCKED bootloader. See -> Moto X Root AT&T/VZW [KXA21.12-L1.26] You are required to be on a particular firmware level, it does NOT disable write protection, it only roots. It is risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Locked bootloaders on Android 5.1
Again....no....you can't downgrade. Not without significant risk.
There is a VERY RISKY method to root for Verizon and ATT 5.1 users that have a LOCKED bootloader. See -> Root for Moto X ATT XT1058 5.1 [LPA23.12-21.1] You are required to be on a particular firmware level, it does NOT disable write protection, it only roots. It is risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
There is no option yet for other models with Locked bootloader, like Verizon or Republic Wireless, because as of this edit, 5.1 has not been released for for them.
I'd like to list all the threads I linked and credit the members who created these great guides.
For lots of Moto X info and help, there's this great Guide by @dray_jr
[REF]The Complete Moto X Guides/Information Thread
@iKrYpToNiTes app TowelPieRoot for the Moto X automates the towelroot/pie setup.
A great outside link here by @KidJoe , the Motorola Moto X How To page (The only outside link here......cause it's really good!)
And let's not forget my friend @Perseus71 for this great Moto X resource thread!!! [INDEX][REF][GUIDE][TUTORIAL][RESOURCE] Welcome to your Motorola Moto X - Resource
And a special thanks to our Moto X support Gurus. These guys bust their humps helping the Moto X community and can help with almost any issue!! Just post an issue anywhere in the Moto X section and they are sure to show up!
@samwathegreat and @KidJoe
If these guys tell you something....I can assure you its very solid advice!
I hope this clears up the confusion with rooting your Moto X. Follow the links based on your situation.... And read, read and read again....then do!!!
You can ask questions here if you wish and hopefully the community can assist you....but you would probably be better served asking in the links to your root method.
Happy Rooting!!
Additional option for having root with write protection enabled......
From @iKrYpToNiTe :
Okay for any user who is on 4.4 and lower they can root and disable write protection. Then they can install safestrap and flash any stock based rom to the stock slot. They then need to boot into the bootloader to flash the new stock kernel and baseband via fastboot, then reboot and enjoy
my old stock based 4.4.2 rom is here http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/
Remember to thank the man if you visit his thread.
Thanks ikryptonite for the addition. ?
Reserved again
This is great. Thanks for taking the time to put this together dude.
@iKrYpToNiTe
I would love for you to write up something and pm me about your ROM method and exactly who it can apply to? Short, sweet and a link to your thread. And I'll add it to the opening post.
I've always been unlocked.... I don't know enough about your method.
Also similar roms that work the same? If you don't mind. ?
you can pm me and I'll add it in.
Thanks my friend! (You don't have to of course.... Just thought your ROM and similar are options too)
sivarticus85 said:
This is great. Thanks for taking the time to put this together dude.
Click to expand...
Click to collapse
I hope it gets read! Lol. The guys that made those threads put a lot of work into them. Yet new root threads pop up daily.
Let's stop repeating root steps and start pointing to the info already available guys.
KJ said:
I hope it gets read! Lol. The guys that made those threads put a lot of work into them. Yet new root threads pop up daily.
Let's stop repeating root steps and start pointing to the info already available guys.
Click to expand...
Click to collapse
+1 !!!!!!!!!
I might suggest a few things to clear up the 4.4.2 and Pie, and.... on LOCKED bootloaders.
KJ said:
....
Locked Bootloaders on 4.4.2 and lower.
Well, you can achieve root, but unfortunately, write protection will still be enabled. Meaning...no writing to the system partition, and any changes you make, root wise, will reset after a power down or hard reboot. So some root a apps will work fine....and some may not.
Click to expand...
Click to collapse
I would remove "and lower" as while that statement applies to 4.4.2, "lower" would then mean 4.4.0 which SlapMyMoto and MotoWpNoMo still work to root and disable write protection.
Something else I would re-consider... While I agree this thread -> http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 is great and contains a lot of useful information, it seems to me that many newbies don't understand it, or overlook the information they seek which is why they are asking questions.
For rooting with an unlocked bootloader, might I suggest telling people to get the latest TWRP, SuperSU, and mFastboot, then use -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 does not include how to setup and configure ADB and mFastboot, put them in your path, etc. Something like this -> http://mark.cdmaforums.com/ADB.htm. It is needed unless someone uses a "tool kit" to root, and many new users don't have a clue about Platform Tools, ADB, or mFastboot.
Heyo there! Looks great so far. Just needs a little formatting and this could be really helpful! I'm humbled by having my name linked in the same thread as jcase and geohot. I do believe @iKrYpToNiTe made an app which makes the Pie+Towelroot easier making my version obsolete.
dier325 said:
Heyo there! Looks great so far. Just needs a little formatting and this could be really helpful! I'm humbled by having my name linked in the same thread as jcase and geohot. I do believe @iKrYpToNiTe made an app which makes the Pie+Towelroot easier making my version obsolete.
Click to expand...
Click to collapse
That will be coming. No way I'm attempting any of that on my mobile browser. Lol. Makes me wanna step on the phone.
As soon as I get time on my family laptop....it'll get a facelift!
You're guide is well laid out for sure....that's why its here. ?
Alternative threads may be added....but only if they have differences. (for different results or methods) Won't be adding basically the same info repeated....just choices. Just in case anyone wonders later.
KJ said:
That will be coming. No way I'm attempting any of that on my mobile browser. Lol. Makes me wanna step on the phone.
As soon as I get time on my family laptop....it'll get a facelift!
You're guide is well laid out for sure....that's why its here. ?
Alternative threads may be added....but only if they have differences. (for different results or methods) Won't be adding basically the same info repeated....just choices. Just in case anyone wonders later.
Click to expand...
Click to collapse
I have updated my own thread to link to @iKrYpToNiTe 's app, so users can get to it from there.
It's also interesting that you mention formatting on mobile browsers. I did most of the writing of that thread on my Moto X while testing everything. It took awhile but it was a relief switching to my PC to respond and edit.
KidJoe said:
I might suggest a few things to clear up the 4.4.2 and Pie, and.... on LOCKED bootloaders.
I would remove "and lower" as while that statement applies to 4.4.2, "lower" would then mean 4.4.0 which SlapMyMoto and MotoWpNoMo still work to root and disable write protection.
Something else I would re-consider... While I agree this thread -> http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 is great and contains a lot of useful information, it seems to me that many newbies don't understand it, or overlook the information they seek which is why they are asking questions.
For rooting with an unlocked bootloader, might I suggest telling people to get the latest TWRP, SuperSU, and mFastboot, then use -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 does not include how to setup and configure ADB and mFastboot, put them in your path, etc. Something like this -> http://mark.cdmaforums.com/ADB.htm. It is needed unless someone uses a "tool kit" to root, and many new users don't have a clue about Platform Tools, ADB, or mFastboot.
Click to expand...
Click to collapse
Hello my friend!!
I'll tackle each point you made.
You are right about it making more sense to NOT use Pie on 4.4 and lower....but....as I said in post above....it is an alternative. Some may be scared off by the slapmymoto method, it is pretty involved. Or they might not care about write protection and just want to use a few root apps, so Pie may be their choice. I'll clarify that tho for sure!! Good point. ?
I disagree about the Complete Guide thread on one part, I find its easy to find the section you're looking for. But, I think many just ignore long guides cause they are overwhelmed or simply want a quicker answer. It does cover A LOT tho. And when I use it to link, I always mention the heading they should look for.
I will find a good ADB guide as you said tho....I just realized it was not included. I haven't "used" the guide myself. Lol. But no, I can't use the links you suggested, as that's a thread by a banned member (multiple bans on multiple accounts to be clear) and I would never link to anything by a banned member. Just my preference.
And here is a challenge for you I hope you accept.......
I tend to mostly only link to XDA threads, as XDA is my home for this hobby. If I may make a suggestion....why not take some of the excellent things from your webpage (yes, I've seen it....its awesome!) And translate them into XDA guides? The things that XDA is lacking anyway. No need to write guides where guides already exist. If an existing guide is lacking anything....suggesting to the creator to edit it is a good alternative also. Also, as this is going to be the thread linked to on XDA's new Root Directory for all devices....again, I feel it should point members only to XDA information, not outside sites. Even tho your page is great. ?
If you start with the ADB guide, I'll link it here for sure! ? Otherwise I may use an N5 guide I know....and just point out any differences.... Tho there isn't many.
And for rooting unlocked bootloaders, yes....it could be done a little "slower".... So the newest member could even follow it. So there's another guide that could be made.
Again, I didn't make this thread to list procedures......I made it to point to info already created by others. The X section is extremely confusing to newcomers..... We needed a clear "map" to help those new members find what they need.
Hopefully the "how to root" threads may slow down. Also, hopefully quick links to this, or the individual threads within this, will help guys like us and a few others from repeating the info day in and day out.
Thanks for the input...I seriously appreciate it. I'll make a few of those changes/clarifications you suggested tomorrow evening. Its late here now.
dier325 said:
I have updated my own thread to link to @iKrYpToNiTe 's app, so users can get to it from there.
It's also interesting that you mention formatting on mobile browsers. I did most of the writing of that thread on my Moto X while testing everything. It took awhile but it was a relief switching to my PC to respond and edit.
Click to expand...
Click to collapse
Lol. You have more patience than me. I hate using the mobile browsers for almost anything.....especially things like editing colors and what not.
I will get to it very soon on my laptop tho.
I felt this should be put up sooner than later, as every day I see 2 or more "how to root MY device with my situation" threads.
I don't blame them.....its been a long standing issue that the X is confusing, and I think more than anything, a lot of the confused members just want confirmation that they're on the right track.
There's perfectly great info on it all in the threads.....but finding it and what suits your circumstance is another story. Its all over. Lol
KJ said:
Lol. You have more patience than me. I hate using the mobile browsers for almost anything.....especially things like editing colors and what not.
I will get to it very soon on my laptop tho.
I felt this should be put up sooner than later, as every day I see 2 or more "how to root MY device with my situation" threads.
I don't blame them.....its been a long standing issue that the X is confusing, and I think more than anything, a lot of the confused members just want confirmation that they're on the right track.
There's perfectly great info on it all in the threads.....but finding it and what suits your circumstance is another story. Its all over. Lol
Click to expand...
Click to collapse
Phew! The sheer thought of writing up one-third of what you have on your mobile device exhausts me. I tend to take my laptop -everywhere-, and use the phone for well....phone things LOL and for a substitute when I just can't have my laptop with me. Wow! I wouldn't have thought for one second you'd be patient enough to write all of this up on your phone. KUDOS, bro. You have far more patience than I.
Thanks again for the new thread. I know it will be just awesome (aesthetically) by the time you are finished with it. :good:
KJ said:
And here is a challenge for you I hope you accept.......
I tend to mostly only link to XDA threads, as XDA is my home for this hobby. If I may make a suggestion....why not take some of the excellent things from your webpage (yes, I've seen it....its awesome!) And translate them into XDA guides? The things that XDA is lacking anyway. No need to write guides where guides already exist. If an existing guide is lacking anything....suggesting to the creator to edit it is a good alternative also.
Click to expand...
Click to collapse
I have tried suggesting edits to the OP on some threads. They've been ignored.
I would love to have all the stuff here, so people can stay on one site. But my finally typing the stuff on my web pages rather than the forums has been due to several reasons....
I tried writing some of this stuff either as a new thread, or as a post in a thread created by someone (i.e as a helper).. Two examples. 1. Taking an OTA and Returning to Stock started as this thread -> http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735 and Bootloader Unlock FAQ started THIS POST in this thread -> http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651 and was linked in the OP. I pasted links to it in the "China Middleman Back???" thread. And I posted links to the OTA thread when relevant. Unfortunately, they were ignored, and the same questions asked.
I'm not as well versed and comfortable with layout and formatting, in the forums. Its easier for me to do on my PC with an HTML editor. It makes doing it via web page faster and easier for me.
Doing it as web pages, posting to my site, I could work on them offline, as time permitted, easily formatting them they way I want, etc. then upload after they are ready. Its easy to include pictures if I want, bold, colors, sizes, etc. Putting them in a post is more time consuming, I have to get it right and complete immediately, format it, etc. before I save/post it. Its more difficult to go back and edit a forum post, update it, etc. Again, editing must be done online, and in its entirety. I can't start editing, save, and finish editing tomorrow, otherwise the post wont make sense.
its how I've always done it, even back in the day on HowardForums, especially when we really needed to test most of the processes FIRST before making them available to the public. I could make the page, and only those I gave the link to could see it until I was ready to go live with it.
As for an ADB guide, or rooting an unlocked bootloader X, I could make make them. I would want them to be illustrated so newer people can follow along. Sure us "more experienced members" don't need that much detail, but we aren't the ones asking the questions. :silly: Unfortunately for me, that would be easier to do via web page.
I agree that there needs to be a comprehensive repository for rooting the X, the info is scattered, has changed, etc. There is just so much, so many places to start, so many "conditions" and caveats, I wouldn't know where to start. SO I do commend you on this undertaking!
I wouldn't mind taking this discussion to PM if you have ideas or suggestions on how to quickly/easily take some of my pages and convert them to posts.. rather than clutter this thread up any more.
KidJoe said:
I have tried suggesting edits to the OP on some threads. They've been ignored.
I would love to have all the stuff here, so people can stay on one site. But my finally typing the stuff on my web pages rather than the forums has been due to several reasons....
I tried writing some of this stuff either as a new thread, or as a post in a thread created by someone (i.e as a helper).. Two examples. 1. Taking an OTA and Returning to Stock started as this thread -> http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735 and Bootloader Unlock FAQ started THIS POST in this thread -> http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651 and was linked in the OP. I pasted links to it in the "China Middleman Back???" thread. And I posted links to the OTA thread when relevant. Unfortunately, they were ignored, and the same questions asked.
I'm not as well versed and comfortable with layout and formatting, in the forums. Its easier for me to do on my PC with an HTML editor. It makes doing it via web page faster and easier for me.
Doing it as web pages, posting to my site, I could work on them offline, as time permitted, easily formatting them they way I want, etc. then upload after they are ready. Its easy to include pictures if I want, bold, colors, sizes, etc. Putting them in a post is more time consuming, I have to get it right and complete immediately, format it, etc. before I save/post it. Its more difficult to go back and edit a forum post, update it, etc. Again, editing must be done online, and in its entirety. I can't start editing, save, and finish editing tomorrow, otherwise the post wont make sense.
its how I've always done it, even back in the day on HowardForums, especially when we really needed to test most of the processes FIRST before making them available to the public. I could make the page, and only those I gave the link to could see it until I was ready to go live with it.
As for an ADB guide, or rooting an unlocked bootloader X, I could make make them. I would want them to be illustrated so newer people can follow along. Sure us "more experienced members" don't need that much detail, but we aren't the ones asking the questions. :silly: Unfortunately for me, that would be easier to do via web page.
I agree that there needs to be a comprehensive repository for rooting the X, the info is scattered, has changed, etc. There is just so much, so many places to start, so many "conditions" and caveats, I wouldn't know where to start. SO I do commend you on this undertaking!
I wouldn't mind taking this discussion to PM if you have ideas or suggestions on how to quickly/easily take some of my pages and convert them to posts.. rather than clutter this thread up any more.
Click to expand...
Click to collapse
I hear ya!!!
I don't know much about formatting any page, web or XDA. Lol. I throw in a little color and bold type and underlines...that's about all I know. Lol
I will add your page at the credits area at the end of the OP with the other links. Its definitely worth it for people needing help. . (Tonight....hate editing on my phone).
As far as cluttering this thread...I'm not sure if its allowed, but I may ask it to be cleaned after a bit and the OP has been discussed enough and tweaked. Would take a moderator a bit of time....but would be worth it to remove all out discussion that is not directly about rooting. If its not possible....this will all disappear back in the pages eventually.
Hopefully more of the actual root related posts will go in the appropriate threads anyway. Aside from pointing out the way to anyone still unsure which applies to them. Shouldn't be actual troubleshooting here tho. ?
Thanks for your suggestions! If you've noticed I did make some adjustments based on your comments.
This thread is to help people figure out what root method is for them and where to go to find out how to root their device. It's a one stop shop for Moto X rooting, since there's many methods based on each devices condition.
I made this also so the Moto X can have ONE single root link on XDA's new root directory, created and maintained by a friend and mentor of mine, @PG101 .
So let's get straight to the current different root methods for the Moto X, as it seems there is confusion about this everyday and new threads started by confused members.
Please simply direct members to this thread or the individual threads for each method.....there's no need to repeat this stuff in thread after thread. A quick link and good luck message keeps XDA clean.
I'm not going to write out root methods....instead I'm going to explain what scenario means what and link to current threads by members who took the time to make guides, how to's and so on.
Please send a thanks (with that little thanks button thingy) to these dedicated members who worked hard at these guides and methods.
Warning!
No matter the model, dev edition....locked bootloader, unlocked bootloader.... Doesn't matter....NO MOTO X can be safely downgraded from 4.4.2 or higher. Not without GREAT risk.
Unlocked Bootloaders
You got it made! Doesn't matter what Android version you're on, the procedure is the same.
See this awesome guide. There's a section on "How to Unlock your Bootloader.". And a section on "Rooting Unlocked Bootloader."
Locked Bootloaders on 4.4 or lower ONLY
For devices still on 4.4 or lower you can root AND disable write protection! Awesome! But to stay rooted, you cannot upgrade past 4.4.
Again, see this great guide and read the section on "Rooting Locked Bootloader.". This is quite involved and takes some work. Read and proceed carefully.
This will NOT work on 4.4.2 or higher!
Locked Bootloaders on 4.4.2
Well, you can achieve root, but unfortunately, write protection will still be enabled. Meaning...no writing to the system partition, and any changes you make, root wise, will reset after a power down or hard reboot. So some root apps will work fine....and some may not.
There are two methods: PIE and Towelroot. Both of these can help you achieve root. PIE is a tethered root while Towelroot runs off an app on the device.
You can also combine these methods using TowelPIERoot made be @iKrYpToNiTe in a very easy and efficient app.
Locked bootloaders in Android 4.4.3 or higher
Unfortunately, there is no root method for you guys as of today. And again, you cannot downgrade without SIGNIFICANT risk.
Warning about using these exploits
Myself or anyone that has helped develop this are not responsible for anything that occurs to your phone by using this method.
I hope this clears up the confusion with rooting your Moto X. Follow the links based on your situation and read the guides! Multiple times!
You can ask questions here if you wish and hopefully the community can assist you....but you would probably be better served asking in the links to your root method.
Credits:
Guide by @dray_jr
>*Moto X*>*Moto X General*>*[REF]The Complete Moto X Guides/Information Thread
PIE for 4.4.2 by @jcase
>*Moto X*>*Moto X Original Android Development*>*[Root 4.4.X] Pie for Motorola devices
Towelroot by @geohot
>*Verizon Samsung Galaxy S 5*>*Verizon Galaxy S 5 General*>*I'm throwing a party and you should come **GS5 ROOT THREAD**. (It works on all devices, see website)
PIE with Towelroot for more functionality by @dier325
>*Moto X*>*Moto X General*>*Towelroot Discussion Thread (good information about the process, but pretty much replaced by @iKrYpToNiTe 's new app....mentioned next)
TowelPieRoot by @iKrYpToNiTe
>*Moto X*>*Moto X Themes and Apps*> *[Root][APP]TowelPieRoot for the Moto X
And let's not forget my friend @Perseus71 for this great Moto X resource thread!
>*Moto X*>*Moto X General*>*[INDEX][REF][GUIDE][TUTORIAL][RESOURCE] Welcome to your Motorola Moto X - Resource
And a special thanks to our Moto X support Gurus. These guys bust their butts helping the Moto X community and can help with almost any issue. Just post an issue anywhere in the Moto X section and they are sure to show up!
Be sure to keep a lookout for @samwathegreat and @KidJoe, they are both very knowledgeable and give good advice.
Hopefully this has cleared up any confusion there is in the Moto X rooting community.
Happy Rooting!
I welcome any feedback here! Please fill me in on anything I'm missing or any mistakes....or any other constructive criticism or suggestions.
Click to expand...
Click to collapse
Went ahead and cleaned everything up, hope you don't mind. Just had to remove some smiley faces and clean up some grammar ^_^
I'm not sure if it's just me but I can only get exposed to work with Jcases pie root. I have tried both towel root and towel pie but it won't work for me. Not sure if it's even pertinent to this thread but thought I'd throw it out there. I'm on att 4.4.2
Sent from my XT1058 using Tapatalk
superp32 said:
I'm not sure if it's just me but I can only get exposed to work with Jcases pie root. I have tried both towel root and towel pie but it won't work for me. Not sure if it's even pertinent to this thread but thought I'd throw it out there. I'm on att 4.4.2
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
I'd use @iKrYpToNiTe 's app. And look through his thread or ask there about xposed. Chances are its been brought up in the thread already, but maybe not.
Link is near end of first post!
Excellent thread, though.
For me, getting to the Motorola's Android environment was kind of tricky, specially coming from a Galaxy S3 Mini, which was my first Android device (coming from iOS and Blackberry) and rooting it was a piece of cake.
Fortunately I got a SIM-unlocked XT1053, which could and was bootloader unlocked by me. So rooting was easier than some other variants are.
I see that there are info everywhere but spread on XDA and other forums. It's nice to see that there is one root-specific thread now, where all possible options are covered.
Keep it going!

Categories

Resources