Related
Hi guys. I published a step by step guide for all the newbies (I had a tough time the first time. Slightly different combination but it works! Also flashed the custom recovery image!
http://ilikemygooglephone.com/2010/...-and-root-google-nexus-one-mac-windows-linux/
This tutorial on rooting and flashing the RA recovery rom is THE BOMB!
Followed all the steps and now I too have gone to the dark side, and eaten some cookies....
Nice work.
Great! Love it!
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Does it have to be 2.0.0? or can it be any of the RA recoveries above 2.0.0?
bahathir said:
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Click to expand...
Click to collapse
A question for you, if it's possible to simply just change the permission of the su file on the phone, why do most auto root zip's come with an su file of their own?
Could they not just run the script above?
this whole procedure thing ... do stock users like myself lose anything? Like, does it wipe data or does it simply root and nothing at all changes?
You can never tell with these procedures... half wipe the phone...
I haven't tested it, but from the steps listed above (by bahathir) you won't lose any data.
All he's doing is getting you to boot into fastboot mode (power on the phone while pressing the trackball), and then loading the custom recover into temporary memory.
Then, the system folder is mounted and the required permissions are applied to the su file. Once that's done, you reboot your phone and nothing else changes.
The question that I had above though, is that I've not seen this method used before. Most one-click root methond replace the su file (requiring you to flash a zip file from custom recovery).
ahh too bad it doesn't work. maybe a 2.3.3 thing, but I just tried unlocking my bootloader and it says I'm missing AdbWinApi.dll from my PC ... but it's clearly there.
I have the most up-to-date Android SDK packages. I've used them before to root my nexus without a hitch...
SU should be present on the system, and the method above takes it for granted. Thus it's for RErooting. Rooting methods bring the SU - they don't care if there's one on the system, assuming that there isn't.
On the other hand, I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader. If it's the case - this is the most overlooked and bulletproof rooting method for Nexus. But I doubt it's the case.
Here's a n00b question. I have an unlocked boot loader and had previously rooted my phone using superoneclick. I wiped all the data before moving to stock gingerbread since I was on CM7 nightlies before. So there is no "su" in my phone. I get the obvious error:
c:\android-sdk-windows\platform-tools>adb shell 'chmod 4755 /system/bin/su'
/sbin/sh: chmod 4755 /system/bin/su: not found
when I try to run the steps listed here. Any ideas how to get the 'su' on my phone?
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Jack_R1 said:
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Click to expand...
Click to collapse
Thanks Jack! Can you point me to an su package that I can safely flash with gingerbread?
Sent from my Nexus One using XDA App
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
aliezad said:
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
Click to expand...
Click to collapse
I don't think that zip would work.
I rooted by applying the su.zip provide by dsixda here: http://forum.xda-developers.com/showthread.php?t=968396 (attachment, bottom of first post)
You would need to flash this from custom recovery (I used Amon RA 2+).
Thanks Brownbay! Worked like a charm!
Jack_R1 said:
...I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader.
Click to expand...
Click to collapse
Unfortunately this won't work on a locked bootloader (at least, not on mine!), so if you've used 'super one click' to root your N1 without unlocking it (like me), this method won't work for you.
I already have had my bootloader unlocked. I'm wondering if this rooting method alone will wipe my phone?
No, it won't wipe your phone.
I was attempting to root my 6.2.1 and successfully had superuser installed and rooted. When I tried moving the Android Marketplace into the /system/apps/ folder it wouldn't appear so I checked all the write permissions and still no luck. I reverted back but must have deselected all of the permissions because now in my /systems/ folder the /app permissions are d---------.
The result is the Fire is stuck on the "Kindle Fire" boot screen and will go no further. When I try all of the fixes it prevents me from going into the adb shell as root, with either a "Stopped (signal)" or "Segmentation fault" error when I type in "su" or "su -".
None of the other tools such as zergRush work because they can't write to the file system and can't elevate to shell root in order to do so. This thread: http://forum.xda-developers.com/showthread.php?t=1356257 doesn't work either because in order to gain temp root, it requires zergRush. Any help on gaining shell root would be appreciated and any additional details can be provided.
Did you try the lastest KF utility v.7? Your not alone with this problem...
I'm in the same boat as you. I tried for 2 days to fix it to no avail and finally decided I was SOL without one of of these "factory cables". The other day I did a support chat with amazon and they are sending me a new kindle. My main gripe with the kindle is there is no way to easily factory reset because of the lack of hardware buttons. Think I'm gonna wait for a cyanogenmod 9 rom before I mess with the replacement... Good luck.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Had this problem last night
Already trying to hack your Christmas present?
I had this problem last night. Stuck on boot screen and powering down and up didnt fix. This is what what fixed it for me.
Go into CMD and type this, with the kindle connect via usb,
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Used KF Utility 6
I haven't had success with v7 yet, but will try when I get back. I had trouble with KF Util on Windows 7 so went back to XP. Will try Ubuntu next because it's easier to navigate the command line. Is there any difference between v6 and 7 with respect to elevating shell privileges?
Yeah follow the command... I think we are stuck on fastboot!
Well at least I'm not the only one who did this. Same issue... Tried to copy the marketplace APK and it wouldn't appear. Changed permissions and am now stuck at boot splash. Executing "fastboot -i 0x1949 oem idme bootmode 4000" simply hangs at "<waiting for device>".
No shell root, no progress
I've tried unrooting with KF utility v7 to no avail. One problem could be that I had Burrito Root on the Fire prior to the bricking, but how I can remove it at this point is beyond me. I can't run the fastboot commands without being in shell root, and KFUtilityv7 doesn't work without those credentials.
Some errors: "(idme) Invalid permission"; "reboot: Operation not permitted". These are seen when I try to put it in recovery mode. FYI, my ADB status is online and my computer sees it, the ADB Rooted status says "No" and I'm in Boot Status 4000 (Normal).
When I try running BurritoRoot it goes through a process, says "Elevating the Shell" and then errors out with "adbd cannot run as root in production builds"
Then below this it says "Root Activated" and "The Kindle is successfully in root mode."
Here is the output from my attempts at installing Permanent Root with KFUtility v7:
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
2114 KB/s (843503 bytes in 0.389s)
Error: Could not access the Package Manager. Is the system running?
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
It is HIGHLY recommended you have TWRP installed before using root.
****************************************************
At this point you can see the mount operations were not successful because you cannot gain root in the shell with su. I am going to try this through my Ubuntu build and see if I can gain privileges through Linux.
Hi. Same problem here. Changed the /system/app permissions by mistake and the Fire won´t pass the loading screen.
I think the only hope we have is that someone finds a way to root from adb.
According to GregDDC:
GregDDC said:
I had the same issue and fixed it with a recovery cable.
The process was simple, just short the 1st and 4th pins on a microUSB cable and boot into recovery/fastboot. You can find all the information here (link) and here (http://forum.xda-developers.com/showthread.php?t=1392693&page=3). I accomplished everything using Kindle Fire Tools.7 I hope this helps.
Click to expand...
Click to collapse
I just don't have the dexterity to fashion my own cable.
Sent from my SPH-D710 using XDA App
Sent from my SPH-D710 using XDA App
I have the same problem. I get the boot-loop with the kindle fire logo. I can access the file system, but most commands give me a seg or permission error. ZergRush doesn't work so fast boot won't work.
I'm trying to get a factory programming cable off here or make my own. That should bypass the whole root issue and put you directly into fast boot so you can load a kindle rom or cm7 or whatever.
Think I'll wait for my wife to go to work tomorrow so I can spend the day working on a cable without distraction. ;-)
Sent from my SPH-D710 using XDA App
Seriously, you most likely don't need the Factory cable to fix your problems. Just do some more reading. There are more than enough threads on these issues to provide you with a clue on how to get out of or into what you are trying to do.
Care to give us a clue on the solution then? I have scoured both this and other threads.
Sent from my SPH-D710 using XDA App
If you cant boot into the OS, you cant get root again.
If you cant boot into TWRP, you cant get it fixed.
If you were romping around with root, with no recovery installed, its likely bricked.
Get a factory cable, or send it back. Learn from the mistake and install a recovery.
Exactly correct (unfortunately) Vasheypooh. At the crossroads of waiting for another temp root through adb our practice my soldering skills.
Sent from my SPH-D710 using XDA App
Factory cable will be the solution for me i'm from canada.
Vashypooh said:
If you cant boot into the OS, you cant get root again.
If you cant boot into TWRP, you cant get it fixed.
If you were romping around with root, with no recovery installed, its likely bricked.
Get a factory cable, or send it back. Learn from the mistake and install a recovery.
Click to expand...
Click to collapse
i've come to the same conclusion unfortunately. this is only my second attempt at rooting an android device and it's wildly different from the process for the previous device i was working with, so since the instructions i was using didn't mention installing a recovery, i failed to do that myself. my kindle is going to the "Your kindle had detected a problem and must clear App storage" on every boot and all attempts to communicate with it have failed. looks like a cable or a new device are my only options at this point. i will definitely be using a recovery of some kind from now on!
rcabls said:
I was attempting to root my 6.2.1 and successfully had superuser installed and rooted. When I tried moving the Android Marketplace into the /system/apps/ folder it wouldn't appear so I checked all the write permissions and still no luck. I reverted back but must have deselected all of the permissions because now in my /systems/ folder the /app permissions are d---------.
The result is the Fire is stuck on the "Kindle Fire" boot screen and will go no further. When I try all of the fixes it prevents me from going into the adb shell as root, with either a "Stopped (signal)" or "Segmentation fault" error when I type in "su" or "su -".
None of the other tools such as zergRush work because they can't write to the file system and can't elevate to shell root in order to do so. This thread: http://forum.xda-developers.com/showthread.php?t=1356257 doesn't work either because in order to gain temp root, it requires zergRush. Any help on gaining shell root would be appreciated and any additional details can be provided.
Click to expand...
Click to collapse
I have exact same issue. Can someone help. I can't get rooted using any of the tools available today.
HELP!
This is because you changed the properties on all the files in /system.
Why would you do that?
su no longer has permissions to run.
If you can't get into recovery, you likely need a factory cable to fix.
This is for windows but it should be adaptable to other operating systems.
Here is a quick "how to" restore your su on stock if you dont have a backup, when you have lost it for what ever reason.
To confirm you have have lost su from your system, connect your device, open up a cmd window and type or copy and paste the following one at a time:
Code:
adb shell
Code:
su
If su "#" isnt retured then do the following:
Download the LATEST OTA update zip from here-
https://ouyafw.skumler.net/
and place in your adb folder for ease of use.
Connect a wired USB keyboard to the OUYA.
Boot into recovery using -
Code:
adb reboot recovery
Upon reboot, you will likely be presented with a black screen and an Ouya icon with "!". Press the home button on your keyboard.
Using the keyboard, navigate using "up","down" and "enter" to select update from adb.
When prompted, open a cmd and enter the following-
Code:
adb sideload RC-OUYA-1.0.346-r1_ota.zip
Replace the file name above as appropriate.
Upon completion reboot system and you will have regained su.:fingers-crossed:
NOTE: When sideloading the OTA firmware the build dates are compared to one another. If you try to sideload an older version you will receive a fail. Use the same build version or above.
F.A.Q.
Q. I recieve an error stating device not found in recovery.
A. You need to install the drivers for the recovery as you did for adb.
Q. I receive an error due to build.prop
A. When sideloading the OTA firmware the build dates are compared to one another. If you try to sideload an older version you will receive a fail. Use the same build version or above.
This is tried and tested on my device.
Thanks to
@rayman for the firmware link.
Timothy Graupmann for Youtube video.
Thank you, as i have a lost su and i don't want to wait for the next OTA update i will follow this method.
tonyeltriton said:
Thank you, as i have a lost su and i don't want to wait for the next OTA update i will follow this method.
Click to expand...
Click to collapse
No problem.
Did you lose su with the ouya toolbox or via something else.
dully79 said:
No problem.
Did you lose su with the ouya toolbox or via something else.
Click to expand...
Click to collapse
Well i think i have messed up with adb commands, after that i tried ouya toolbox with luck because the program said that my ouya should be rooted but it wasn't. I will restore lost su and then try again ouya toolbox.
Adb reboot recovery takes me to a black screen with ouya logo and " ! " under it.
tonyeltriton said:
Adb reboot recovery takes me to a black screen with ouya logo and " ! " under it.
Click to expand...
Click to collapse
Thats where you press "Home" on your attached usb wired keyboard to enter the options.
dully79 said:
No problem.
Did you lose su with the ouya toolbox or via something else.
Click to expand...
Click to collapse
Lol i did and this would have came in handy if I found it earlier but I figured it out and install the proper su file
I can confirm these instructions work perfectly. I factory defaulted my Ouya after rooting it and lost access to su in the shell even. These steps fixed my Ouya!
Sent from my Nexus 10 using Tapatalk 4 Beta
Edit:
[Procedure] http://forum.xda-developers.com/showpost.php?p=64841837&postcount=27
Edit/
I am creating this thread dedicated for me and other beginners "noobs".
Where should I begin as a beginner?
I am looking to unlock and root with latest MM that motorola supplies.
Things you should know about me:
I have no idea how to use adb.
I have no idea how to unlock & root or even if I should but I don't like ads.
I have no idea which firmware to use.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am completely lost.
I have not gotten my phone yet, I ordered it this morning and will be here Friday. I am just trying to compile sources and info.
Thanks a bunch guys, I really need help with this.
One piece of advice for starters just since you used the word noob. Never mod your phone on a low battery. You can mess a phone up enough to break offline charging, and without a removable battery that you can swap out or charge in a cradle that could get awkward in a hurry on this phone. I always make sure I'm >75% just in case. You can fastboot your way out of all kinds of trouble; but not if your battery is dead and your phone is so screwed up it is not offline charging.
Your phone will probably show up with Android 5.1.1 installed, at least I got mine about 3 weeks ago and it did. Once it is through initial setup it should want to apply an OTA to Android 6.0 right away; if not check for it in Settings -> About -> System updates and it should find one. Just let it update before you do any setup or app downloading.
Once you're on MM, before you do any setup you have to unlock your bootloader if you intend to root. You'll get all the warnings about voiding warranty and here there be dragons, so be prepared for that. Also, unlocking the bootloader will wipe your internal storage, so don't bother with any setup or app downloading before you do it.
Start with Heisenberg's thread. It is a great guide on how to setup your computer for adb and fastboot as well as all the syntax you need for unlocking the bootloader and installing a custom recovery. Make sure to get the 2.8.7.1 version of TWRP that is patched to work with the MM bootloader.
When you boot to TWRP recovery for the first time it will ask if you want to keep system read only. Keep system read only and make a backup immediately. I usually make one backup of boot, system, and data, and a separate one of just efs; don't worry if you don't understand, you'll figure it out when you get there. TWRP is all touch based and pretty intuitive. This way you have good, untouched system backup to fall back on just in case.
When it comes to rooting MM, don't use the old system install method. Flash a SuperSU from this experimental systemless root thread (I used this instead of the ivcarlos method linked to the Heisenberg thread because it is more automated and easier). I can vouch for the 2.62-20151210170034 version of SuperSU. I've used it to root stock MM on this phone 3 or 4x as I've restored backups and changed kernels. I've heard the 2.64 and above SuperSU versions are not working with this phone on MM, and the older traditional system root methods like the v2.49 version that is linked to the Heisenberg thread are causing bootloops on MM. Don't panic on first boot after the systemless root; it appears to bootloop once but comes up normally the second time.
One other thing, TWRP doesn't seem to be able to detect the systemless rooting method, and it really wants your phone to be rooted. If/when TWRP offers to automatically install SuperSU, don't let it - ever - it will keep asking. It must use the old method that causes bootloops on MM, not the new systemless method linked above.
Once you're all rooted and settled in, if you get sick of the unlocked bootloader warning you can fix it by reading up in this thread. Just be sure to read carefully and get the MM logo and not the LP logo.
Wow, thank you so much for the long type up.
Duly noted and this is a great start. May I continue here if I run into any problems?
I think ima have fun with this phone
I am into tinkering with devices, "sometimes linux" etc, like my PC OS win7x64 is modified big time, so I probably will catch on with unlocking rooting etc very quickly.
I got chillz and cannot wait!
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Hitti2 said:
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Click to expand...
Click to collapse
Good luck :good:
I just noticed one thing that might not be entirely clear in the Heisenberg thread. It says to enable adb in the Settings -> Developer Options menu, but by default you won't have a Developer Options menu.
To get one, go into Settings -> About Phone, scroll all the way to the bottom, and tap on build number about 8 or 10 times. Your phone will say something to the effect of congratulations now you're a developer, and you'll have the menu.
Edit: i just noticed it says how to enable developer options further down the page
ty, I will need it lol.
Dev options were on my S5 too. My pops showed me how to on the S5, kinda hoping it was the same way to enable them, turned out to be. Cool.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
^^^This^^^
and remember what XDA is really for ...http://forum.xda-developers.com/showpost.php?p=2031989
with that, enjoy all the reading, and do not be afraid to look at other sites too, there are even videos around that can help guide you...
and there are fellow members here to help...but most questions have already been asked and answered, so search first! Cheers! :highfive:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
1) Be sure to get the newest TWRP that has been patched for M.
Click to expand...
Click to collapse
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Hitti2 said:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Click to expand...
Click to collapse
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
[Q] Where should I begin as a beginner?
At the beginning, of course.
Sorry couldn't resist...
Naddict said:
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
Click to expand...
Click to collapse
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Hitti2 said:
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Click to expand...
Click to collapse
after you unlock and install custom recovery, you use TWRP (the custom recovery) to create the backup...
as you are on MM, you cannot use the "all in one" application that I provided in the link...so you will have to manually install/flash your rom
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Hitti2 said:
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Click to expand...
Click to collapse
Clearly you are impatient (not trying to be rude here), - XDA truly is not a place to pay for someone to do it for you, XDA is about learning and development, there are several places that a search will get you what you need. Many members have also posted links above to vast amount of information (specifically this post and this entire thread here http://forum.xda-developers.com/showpost.php?p=64183396&postcount=151 and here too http://forum.xda-developers.com/showpost.php?p=64311581&postcount=171) that you should take time to read and then, as you move through these things then you ask questions.
Offering to pay to have someone do it for you is really not what this site is about.
Read, do google searches...it has been done a hundred time already mate, take the time to learn what it is you are doing before actually doing it.
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Hitti2 said:
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989
Hitti2 said:
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Click to expand...
Click to collapse
Looks to me like several folks in there offered suggestions on how to successfully get root ...and again, as my last helpful post here...you really need to read Heisenberg's thread, that guide works, and from what I can tell, you have to use systemless root.
Ok, I will follow
Intro
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Prerequisites:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
1. How To Unlock Your Bootloader
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
3. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Click to expand...
Click to collapse
& I will follow
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/show...35&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps...ellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Click to expand...
Click to collapse
I still think its going to brick but uhwell.
So far so good, I've got it unlocked.
I apologize for my ignorance. I am gonna take it a step at a time.
Doing step one "unlocking" was scary but it went good.
Wish me luck!
Hello everyone,
I've wasted my Christmas days to - unsuccessfully - re-root a Shield (16GB; 2015) after upgrading to Software 7.2.1. I need to use more than one USB mass storage device and to be able to copy from one to another, so I want to re-enable Stickmount.
The device was rooted before (which means the bootloader was already unlocked, too), and enabling USB debug, finding the device on my PC via "adb devices" was no problem, either. Issuing "adb reboot bootloader" went fine, too, the device could now be seen via "fastboot devices".
So, I flashed the TWRP image (I actually tried three different versions, 3.0.2, 3.1.1, and the most recent 3.2.3). All seemed to load fine (it spewed out two time values followed by OKAY, took about one second), but the reboot that follows only shows the NVIDIA logo forever without anything else happening (the longest I waited was 20 minutes) - according to the docs I could find (and had used before), TWRP should appear after about 15 seconds.
So, I'm stuck. I cannot get TWRP to start which prevents me from sideloading SuperSU, which means I can't use Stickmount.
Is there anything I did wrong? Is there any other way to get Stickmount installed onto my Shield? Any help is appreciated.
Cheers, Pit.
You'll need to wait until TWRP gets updated to get around the new android security measures. So keep checking TWRP website periodically to see when a new version is released.
You could have found this out if you went to Nvidia Shields Android TV forum and read some posts.
I was reading here, as well as at the nvidiashieldzone, where the tutorials are up, plus I was googling for the errors I was getting to no avail. Sorry for not finding every post on every forum on the internet, and thanks for giving the right pointer.
That means there is currently no way whatsoever to get the Shield rooted on 7.2.1., right?
Not just now, there's a guide to root 7.2 - using a developer image, and there's a chance of bricking - best to wait until TWRP is updated - also you don't need to root to use stickmount.
You only need to do something like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb shell
pm install -i "com.android.vending" -r /sdcard/Download/stickmount.apk
adb reboot
That way you can use your apk without being rooted - and your device will still be secure, and you can use widevine etc for netflix and other apps that check to see if your device is rooted.
Or you can just push the driver files stickmount uses like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb push hosts /system/etc/hosts (example file)
adb shell "chmod -R 644 /system/etc/hosts"
adb reboot
Thanks for the info - if I understand this correctly, I can install apks with root-like permissions using TWRP without rooting the whole device, right?
I will try that out once TWRP is working again.