Related
You CAN Root the new Hboot, and you don't need s-off. (strictly for those who don't know and need help)
thanks to the cwm team for there beautiful recovery, and chainsDD for SU
1. head over to htc dev
http://www.htcdev.com/bootloader/
2. create a account or sign in (you must use your real email address)
3. go to unlock bootloader
4.Select "all other supported Models"
5.Follow the directions and install all the software provided and you will end up with a unlocked bootloader with s-on
6. enter FASTBOOT again on your phone
7.open the command prompt again on your pc
8.Download this recovery from the CWM TEAM and place it in the same folder as fastboot (where you put unlock_code.bin)
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.2-supersonic.img
9. for simplicity's sake rename the above file to recovery.img
10.in your command prompt navigate to the folder containing your fastboot files and recovery.img
11.enter the following in the command prompt:
fastboot flash recovery recovery.img
12. Once that completes navigate to recovery on your phone and pres power to select it
13.once CWM recovery boots on your phone use the volume up and down to pick Mounts and storage press power to select it
14.select Mount usb storage
15.take this zip and drag it to the root of your SD card
http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip
16. on your phone press power to un mount your usb storage
17. select go back
18.select install zip from sd card
19.choose zip from sd card
20.select the su-bin-3.0.3.2-efghi-signed.zip file we just downloaded and press power to flash
21. reboot the phone
22.once your phone is booted go to the market and search superuser
23.download and install superuser
24. search busy
25. use one of the busybox installers and install busybox (hit allow on the su notification)
26.enter superuser, press the menu buton on your phone, select preferences, then scroll down to su-binary
27.hit update, and allow the prompt, if all the output is in green then you have full root congrats!!!
For Those who wish to take it one step further and achieve s-off revolutionary or unrevoked
I give credit to Captain_Throwback over at themikmik.com for this...
this process will format your phone I recommend running a program like titanium backup and syncing your contacts to google before you go any further
28.reboot your phone, and enable usb debugging
29. place these 2 files, unziped on the root of your sd card
http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
30.set your phone to charge only
31.open the command prompt on your pc and navigate to the same folder as your fastboot files in the step above
for example: cd c:\android-sdk\platform-tools\
32. type the following into the command prompt pressing the enter key at the end of each line:
Code:
adb shell
you should get a dollar sign
Code:
su
you should now get a pound sign
Code:
cat /sdcard/flash_image > /data/flash_image
Code:
chmod 755 /data/flash_image
Code:
/data/flash_image misc /sdcard/mtd-eng.img
33.now set your phone to disk drive mode and place this zip on the root of your sd card (do not unzip)
http://www.4shared.com/zip/Cf3g-3lV/PC36IMG_SuperSonic_S_Sprint_WW.html
34.rename the above file to PC36IMG
35. set your phone to charge only
36.at this step you have 2 options you can pull the battery of your phone and put it back in then hold volume down and pres power to enter the bootloader or you can go back to your command prompt and type the following:
Code:
exit
Code:
adb reboot bootloader
37.when your bootloader is done loading press volume up to flash the PC36IMG.zip
38 your phone will reboot the bootloader once durring this process, dont be alarmed just wait for it to finish, when done it will ask you to press power to restart the phone
39 when done remove the PC36IMG file from your sd card
40. congratulations you are now back to stock 2.2 froyo evo 4g
41. you may now root and get s-off using the Unrevoked method found here:
http://unrevoked.com/
42. If you would rather use the revolutionary method run this ruu on your pc:
http://goo-inside.me/supersonic/ruu...15.00.05.02_NV_2.15_release_199233_signed.zip
43.now you can use the revolutionary method
revolutionary.io
Note original post for s-off found here:
http://themikmik.com/showthread.php...18-HBOOT-with-HTCDev-com-No-More-Watermark!-"
note if you get stuck with a locked oww Hboot and it wont flash the PC36IMG you may use taco root to gain temp root then use steps 29-39 to unlock your bootloader to flash the PC36IMG
http://www.acsyndicate.net/taco-root-for-htc-phones-gives-perma-root-for-all-htc-phones/
Dude,this is great for those who have the new version of Hboot.Good looking out.
This is great, man.
There is a way to get S-Off with this frightful HBOOT, however
I suggest you check here on the MikMik. The great part is that you is that you achieve S-Off with Unrevoked, so you have a permanent S-Off compared to Revolutionary's!
Nice guide, but you should really encourage flashing of RA recovery instead of CWM. It's just way more reliable on the EVO 4G.
So will this work for the updated 2.3.5 android??
Steek34 said:
So will this work for the updated 2.3.5 android??
Click to expand...
Click to collapse
This is how you root the updated 2.3.5
Sent from my PC36100 using XDA App
Is working for me
After several hours searching on the Net for Root update 2.3.5. And trying any possible recomendations.
This one really work for me.
Thanks XDADev and THC Butterz to make it possible.
Officiall and Proud Nobb
Later!...
Captain_Throwback said:
Nice guide, but you should really encourage flashing of RA recovery instead of CWM. It's just way more reliable on the EVO 4G.
Click to expand...
Click to collapse
+100
Most the issues I've seen on this forum over the last year were solved by switching to AmonRa recovery. Let's get people started with a leg up.
Good guide.
Sent from my PC36100 using xda premium
Anyone getting issues with HTCdev? I am getting Error Code: 173. Error Reason: Check Rule Fail with exception.
Its it still possible to brick with this root. Can't you only permanently brick when flashing radios? Can you do that if you have s-on?
Sent from my PC36100 using xda premium
Hanging on parse
I used
Unlocking EVO 4G via HTCDEV.mp4 on youtube.com via Thedoctadro
I'll try to keep this brief,
I too had spent many hours trying to find the most up to date and seemingly easiest way to begin rooting my hboot 2.18.
I had updated my phone and then read a post about how the evo has been exempt from the Ice Cream Sandwich update.
The video told me to download the htc supertools file. I did not use the tools specified in dev, but still followed the same procedure.
File found here on goo inside .me - htcsupertoolv3.rar
It was on a wiki site with all the listings for the supertools and I chose the latest one that was available.
It is unlocked but when it scans my pc36img, it hangs.
I've read about formatting the sd card and putting another pc36img on and then reinstalling but unsure as to where to find the right one. My phone is fully updated with current updates. Any help would be appreciated if there is any to give seeing as how early into development this process is.
Sidenote: I didn't use the software on the dev instructions because I wanted to follow to a T exactly the instructions in the video. Thanks again.
pendelum said:
I used
Unlocking EVO 4G via HTCDEV.mp4 on youtube.com via Thedoctadro
I'll try to keep this brief,
I too had spent many hours trying to find the most up to date and seemingly easiest way to begin rooting my hboot 2.18.
I had updated my phone and then read a post about how the evo has been exempt from the Ice Cream Sandwich update.
The video told me to download the htc supertools file. I did not use the tools specified in dev, but still followed the same procedure.
File found here on goo inside .me - htcsupertoolv3.rar
It was on a wiki site with all the listings for the supertools and I chose the latest one that was available.
It is unlocked but when it scans my pc36img, it hangs.
I've read about formatting the sd card and putting another pc36img on and then reinstalling but unsure as to where to find the right one. My phone is fully updated with current updates. Any help would be appreciated if there is any to give seeing as how early into development this process is.
Sidenote: I didn't use the software on the dev instructions because I wanted to follow to a T exactly the instructions in the video. Thanks again.
Click to expand...
Click to collapse
If you're unlocked using the HTCDev method, you should be using a custom recovery to flash updates, not the bootloader method. The bootloader method will only work if specific criteria are met, since your device is still "S-ON". Do you have a custom recovery (RA-supersonic, preferably) installed?
Re: Hangs on parse.
Thanks! The instructions were to unlock the hboot, and then after the reboot, flash a custom recovery but because it's hanging, I can't get into fastboot usb to flash the custom recovery. Hind sight, I should have waited till there was a full walk through with links to the files needed for the rooting process and only trusted these forums. About a year ago, I rooted an old evo I had through these forums and these are the only ones I will trust. Any help would be much appreciated.
I got thru this one. Ive rooted using the revolutionary method & done it this way. Good tutorial, helps out those who dont know how to root with this ota update.
pendelum said:
Thanks! The instructions were to unlock the hboot, and then after the reboot, flash a custom recovery but because it's hanging, I can't get into fastboot usb to flash the custom recovery. Hind sight, I should have waited till there was a full walk through with links to the files needed for the rooting process and only trusted these forums. About a year ago, I rooted an old evo I had through these forums and these are the only ones I will trust. Any help would be much appreciated.
Click to expand...
Click to collapse
If you can confirm your bootloader says you're unlocked, you can try removing whatever PC36IMG.zip file you have on your sd card, and put the one I'm attaching to this post there instead. It should get picked up by the bootloader. It's for RA-supersonic v2.3.
A big thanks again. Worked like a charm. Love this site.
yah, i updated the op today and added some more info
Oh perfect...this is my first time rooting my phone so im trying to take in all the information i can.
Worked like a charm, thanks a bunch!
Also, I had a bad NAND recently and was not able to update via Revolutionary. This worked.
A sort of simple ?
If I choose to only to do the unlock bootloader with custom recovery but leave it at s-on, I understand that there is a way that I can still flash rom's to the the Evo......however I want to know if I would still be able to use any streamlines apps anymore such as Boot Manager or Boot Loader? say if I still want to have like 5 different Rom's on my Sd card how can I switch between them?
Is there a way to reset the Internal Memory of the N4 without the phone? I try to turn my phone on and it's a lit black screen. I accidentally dragged a file named "Recovery.img" onto the memory and I'm guessing that's what the problem is...
12Fully said:
Is there a way to reset the Internal Memory of the N4 without the phone? I try to turn my phone on and it's a lit black screen. I accidentally dragged a file named "Recovery.img" onto the memory and I'm guessing that's what the problem is...
Click to expand...
Click to collapse
Where did you drag it to? Do you have CWM or TWRP recovery, and can you boot to it? If so just adb push a rom zip and flash it.
Can you boot to BL? Have you tried flashing the stock, or other, recovery image yet? Anyways usually a good idea to provide more detail if possible, any steps you've taken already, blah, blah.
Anyways worse case scenario you can back up YOUR apps and the user partition of the SD card via adb:
Code:
adb backup -all -nosystem -shared -apk
If your BL is already unlocked, then flashing the factory images via fastboot won't result in you having to unlock your BL and potentially lose your junk. If you do have to unlock your BL and it wipes your data off the sdcard:
Code:
adb restore backup.ab
adb back up guide: http://forum.xda-developers.com/showthread.php?t=1420351
flash factory images: http://forum.xda-developers.com/showthread.php?t=2010312
I dragged it onto the main directory of the phone. I unlocked my bootloader, installed CWM via fastboot, and now it won't let me start up my phone. I CAN boot into bootloader.
12Fully said:
I dragged it onto the main directory of the phone. I unlocked my bootloader, installed CWM via fastboot, and now it won't let me start up my phone. I CAN boot into bootloader.
Click to expand...
Click to collapse
Try
Code:
fastboot erase cache
and see if you can boot then.
I still can't reboot.
*Edit
Resolved. Wug's Nexus Root Toolkit did the trick.
I am a noob at android--just putting that out there. But trying...
I just received my new nexus 7 2013. I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it, and then the plan was to root it. Something happened in the process--can't say for certain what, but at some point the tool brought up TWRP on the nexus and a file that the tool said was supposed to be there, wasn't. The end result now is that my nexus is stuck on the bootloader. None of the buttons seem to work, other than restart bootloader. Turn off DOES turn off the nexus, but then when pressed again, goes right back to the bootloader. The recovery one flashes the screen quickly, then goes back to the bootloader. The Start option makes it so the screen shows the "Google" icon indefinitely with the unlocked lock icon. I need to note that the option to get into the bootloader (power + vol up and vol down) did not work for me—the only way I was able to go into the bootloader was the power and vol down. Currently though, pressing the power button makes the nexus go directly into the bootloader.
When plugged into computer via the usb cord, windows xp currently doesn't recognize anything is plugged in, although I do have the latest USB drivers installed.
I downloaded and ran SDK and went through the various fastboot commands from within a cmd window. The fastboot devices command does bring up a device number, so it is recognized by fastboot.
Here's where others will start to shake their heads in bewilderment...in my haste to try and get this up and working and out of the endless bootloader menu, I *could* have flashed it with the nexus 7 2012 recovery image, because when using fastboot to do so, at end says something about grouper and my device says flo (although nothing changed with the nexus—as in there are no obvious changes as still in bootloader). I am aware that the official flo factory image is not yet available, although at this point, I don’t have much confidence in that doing anything.
If I open up Wugfresh’s Toolkit, I can’t do anything with it, as it says that ADB doesn’t work or something and to enable USB debugging, which I can’t do because I’m stuck on the bootloader.
I don't know where to go from here--I don't know if the device is salvageable or if it is completely toast and I should just return it and get another one...I see that in the day since I downloaded Wugfresh’s Toolkit, he has released two more versions—not sure if the new version can do anything—haven’t tried yet. Can anyone with more knowledge than myself give me a hand or some advice? Thanks in advance.
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Username invalid said:
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Click to expand...
Click to collapse
it is unlocked. I am able to use the fastboot commands to unlock and lock. it currently is unlocked.
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Username invalid said:
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Click to expand...
Click to collapse
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
busdonic said:
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
Click to expand...
Click to collapse
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Username invalid said:
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Click to expand...
Click to collapse
Yeah, I see that....not sure why I did it myself actually, cuz now that you mentioned it, does seem pretty stupid--I guess that explains why I'm here asking for advice
I'm assuming that the one click restore will work. If it doesn't, I think I found a non-official flo factory image. I think (?) if I flash that to the tablet in fastboot, that will restore it, or at least get it past either the bootloader menu or past the Google icon shown at startup.
Geodude074 said:
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
Click to expand...
Click to collapse
this worked--thanks much. Am much relieved to be up and running again....
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!
Ladies & Gents, please buckle up for liftoff.
Code:
[COLOR="Red"][B]/* Disclaimer
* You are choosing to test this software as-is & accept full responsibility in case
* it will not work as expected. Or for WW3. Or dead kittens, whichever is worse.
*/[/B][/COLOR]
Instructions 1/2 = Bootloader Unlock:
Code:
[b]1: DOWNLOAD[/b] the [URL="https://drive.google.com/file/d/0B8rpJsF4EG0YUHh4UEo5ZExHWjg"]> prerequisites <[/URL]
[b]2: UNZIP[/b]
You will have 3 folders for zs550kl, zs570kl & zs570klpro containing:
UL-Z016-WW-4.12.40.9999-user.zip -> unlock-capable firmware update
UL-Z016_1-WW-4.12.40.9999-user.zip -> unlock-capable firmware update for the zs570kl PRO variant (in its own folder)
UnlockTool.apk -> unlock app, needed for the actual operation
PDF with Instructions in CN & EN (for zs570kl/pro only)
- bootroot.img - rooted boot image (bootrootn.img for ZS550KL Nougat)
- bootstock.img - stock boot image, if you want to return to stock or if something went wrong (bootstockn.img for ZS550KL Nougat)
- Superuser.apk - superuser app
[b]3: FACTORY RESET[/b] via Settings -> Backup & Reset
This usually solves the issue with not being able to unlock due to a "missing PIN"
Do through initial setup - no need to configure anything as the following factory reset will erase everything again.
Just click through the options to access the app drawer asap.
[b]4: COPY Files:[/b]
ZS570KL - Copy UL-Z016-WW-4.12.40.9999-user.zip to your internal storage
ZS570KLpro - Copy UL-Z016_1-WW-4.12.40.9999-user.zip to your internal storage
[COLOR="DarkOrchid"]ZS550KL - no files needed at this stage. Just ensure you are on the latest firmware: (Marshmallow: v12.40.108.29; Nougat: v22.40.26.43); update otherwise.
[URL="http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z018-WW-12.40.108.29-user.zip"]> latest MM firmware <[/URL] put it in the root of your internal storage.
[URL="http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z018-WW-22.40.26.43-user.zip"]> latest N firmware <[/URL] put it in the root of your internal storage.[/COLOR]
Copy & install UnlockTool.apk
[b]5: REBOOT[/b]; You should have a notification about a new firmware.
No notification for ZS550KL if you were already on the latest firmware.
Install & reboot again.
[b]6: Run the UNLOCK[/b] App
It should do another factory reset on success.
Instructions 2/2 = ROOTING:
Code:
[b]7:[/b] Copy/install Superuser.apk
[b]9:REBOOT into BOOTLOADER[/b]; either holding volume up + power from a powered down state or typing the following in a console (assuming you have ADB enabled in developer options)
adb reboot bootloader
[b]9: FLASH[/b] bootroot.img via fastboot
fastboot flash boot bootroot.img (you can also do a fastboot boot bootroot.img without flashing to check if the boot image works for you)
fastboot reboot
note: change the filename to bootrootn.img if you want to test the ZS550KL Nougat version.
[b]10:[/b] Check for root via adb shell; su or via any app requiring root, on device (terminal, titanium backup, etc...)
- in case something goes wrong, flash the stock boot via fastboot.
- report success/failure in this thread.
[b]11:[/b] BUSYBOX (Optional):
I've bundled busybox with the boot image; follow the commands below to install (in an adb shell or terminal session):
mount -o remount,rw /system
busybox --install -s /system/xbin/
[b]12: RECOVERY[/b] (Optional):
[URL="https://drive.google.com/file/d/0B8rpJsF4EG0YZ1FQSkUxRW9TdWs"]> stock dump <[/URL]
> twrp < / WIP
What it does mean to us? Can someone create some tutorial?
Wysłane z mojego ASUS_Z016D przy użyciu Tapatalka
squo_85 said:
What it does mean to us? Can someone create some tutorial?
Wysłane z mojego ASUS_Z016D przy użyciu Tapatalka
Click to expand...
Click to collapse
It means we have the bootloader unlock.
The tutorial/instructions are contained in a PDF in the zip.
English instructions at the end of the PDF.
Three is one more question?
Hot to root it?
Like for 520kl with changed according to 570kl files
Spoiler
https://youtu.be/hg77b8o8Jk4
Or just use universal tool e.g. Autoroot tool?
Spoiler
https://youtu.be/UYTCRhg0SCw
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Chaosruler said:
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Click to expand...
Click to collapse
Thanks for testing ;]
Were you thus able to achieve root from within an app on the system?
adwinp said:
Thanks for testing ;]
Were you thus able to achieve root from within an app on the system?
Click to expand...
Click to collapse
yeah, Titanium Backup (PRO)
thank you very much for your hard work, let the custom android era begin!
Chaosruler said:
yeah, Titanium Backup (PRO)
thank you very much for your hard work, let the custom android era begin!
Click to expand...
Click to collapse
Great, thank you for the confirmation & enjoy ;]
Let the fun begin ^^
Do you think I can flash with fastboot flash instead of running it with fastboot boot? The latter let's me have root until I restart my device( temp root)...
Maybe fastboot flash will perma root it
Chaosruler said:
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Click to expand...
Click to collapse
Hey there,
How did you achieve root? How did you achieve unlocking bootloader. I have followed the instructions and all I have was my data erasing. How can I confirm if my bootloader is unlocked and what did you do to get root. OneClickRoot stated my phone could not be rooted.
I have the zs570kl/256gb phone too.
jmoricone said:
Hey there,
How did you achieve root? How did you achieve unlocking bootloader. I have followed the instructions and all I have was my data erasing. How can I confirm if my bootloader is unlocked and what did you do to get root. OneClickRoot stated my phone could not be rooted.
I have the zs570kl/256gb phone too.
Click to expand...
Click to collapse
bootloader unlock is not root... its what is required to root... to confirm your bootloader is unlocked use adb to get device info, it will say if its unlocked there
What I did to root is run fastboot boot bootroot.img to temporarily use the ops boot image
Chaosruler said:
bootloader unlock is not root... its what is required to root... to confirm your bootloader is unlocked use adb to get device info, it will say if its unlocked there
What I did to root is run fastboot boot bootroot.img to temporarily use the ops boot image
Click to expand...
Click to collapse
Wow, i guess i am a newbie here.. I have heard adb but dont remember what where or how i got it fo rmy zen2. can you provide instructions how how to check, access, use adb to confirm unlocked bootloader. Also can you provide instructions on to to run the boot image for rooting.
thanks
For some reason, i can't get to fastboot, i was able to get it before unlocking this device, now after unlocking, i can't get to fastboot, unless i'm missing something here. I can get to recover mode, but that all.
EDIT: Ok i got into boot loader, which my fastboot was able to detect the device, but the commands are unknown, search it up saying it;s locked, but i just did the installment above for updating it to make it unlock, am i missing something here? (I might do this over again later on tonight)
We may need screenshots of making sure to see the oem unlocking.
Darkdragontc said:
For some reason, i can't get to fastboot, i was able to get it before unlocking this device, now after unlocking, i can't get to fastboot, unless i'm missing something here. I can get to recover mode, but that all.
EDIT: Ok i got into boot loader, which my fastboot was able to detect the device, but the commands are unknown, search it up saying it;s locked, but i just did the installment above for updating it to make it unlock, am i missing something here? (I might do this over again later on tonight)
We may need screenshots of making sure to see the oem unlocking.
Click to expand...
Click to collapse
I updated post #1 with step by step instructions.
Follow.
I also went through the process myself, as described in OP & everything went fine.
Confirmed working.
adwinp said:
I updated post #1 with step by step instructions.
Follow.
I also went through the process myself, as described in OP & everything went fine.
Confirmed working.
Click to expand...
Click to collapse
Yup Confirmed Working, no more problems. Thank you! Now i hope we can make some custom roms and get twrp on here when we can. (820 that what i have)
Just to be clear, on the SD821 variant is this a permanent root or just a temp root?
ultramag69 said:
Just to be clear, on the SD821 variant is this a permanent root or just a temp root?
Click to expand...
Click to collapse
temp root if you use fastboot boot command
Perma root of you use fastboot flash boot command
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
pacattack81 said:
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
Click to expand...
Click to collapse
I can confirm it with my device...
pacattack81 said:
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
Click to expand...
Click to collapse
I used a SD820 boot image as base & don't have a SD821 variant to test on thus didn't want to mislead the community.
But @Chaosruler tested & it seems to work.