Related
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
• Your custom ROM will be: http://goo.im/devs/teameos/roms/nightlies/wingray/
• Your GOOGLE APPs (GAPPs) would be: gapps-ics-20120429-signed.zip http://goo.im/gapps
Full thread in details can be found here: http://forum.xda-developers.com/showthread.php?p=20479464
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html • Recovery Image: http://goo.im/devs/teameos/recoverie...ecovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to:
Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Advice: purchase Startup Manager from the market. Remove unwanted user programs from the startup. That will boost the boot time of your xoom. and don't remove superuser or superSU.
To have better battery life, from the market buy JuiceDefender ultimate. configure it as aggressive. don't worry, it is ok. This will give you around 2 hours of extra battery life than the promised 10 hours. Keep that in the startup.
You may need after that to install terminal emulator from the market if not already installed by the ROM to check if you have root permissions. Just type "su -" you will be prompted with superuser check. Click allow. and then type "id" You will see your id is root.
Should you require further details or assistance, please let me know. And enjoy the best rom customized ever for your device
Best Thanks to TEAM EOS for the great ROMs they provide.
After you are done with all that, let me know and will explain to you how to work with the pre-installed gooManager in the new ROM. It will make your life much easier to upgrade to future releases of your ROM.
Note: if you are coming from eos rom, there is no need to wipe data. Wipe cache and dalvik are enough.
If you are coming from another rom other than eos roms, or rooting for the first time, wipe data is needed as well. Enjoy...
Sent from my MZ601 using Tapatalk 2
Great guide! I was waiting for someone (I was too lazy myself) to create a guide that skipped right to the good stuff: Custom Roms.
One thing though: After "fastboot flash recovery eos-recovery-r6.img" aren't you supposed to reboot, and then immediately go into recovery, just so that the system doesn't bring back the old one? Or am a dreaming things (again)?
Hi yosterwp. My pleasure to be part of xda community mate.
Well, after flashing recovery, within adb, I am asking to reboot fastboot and and rebooting recovery. Then rebooting system is mentioned there. That is why I am asking to use the volume button and power button combinations to prevent it from going to old rom and directly go to recovery to flash eos rom
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Hi yosterwp. My pleasure to be part of xda community mate.
Well, after flashing recovery, within adb, I am asking to reboot fastboot and and rebooting recovery. Then rebooting system is mentioned there. That is why I am asking to use the volume button and power button combinations to prevent it from going to old rom and directly go to recovery to flash eos rom
Sent from my MZ601 using Tapatalk 2
Click to expand...
Click to collapse
Ahh, efficient and direct for the noob in all of us! I expected nothing less from you; great job!
At step 1 of "To flash the other ROM downloaded above", I get this:
http://i.imgur.com/lsItx.jpg
What am I doing wrong?
EDIT: If it helps, when I flash the recovery image, I get this:
http://i.imgur.com/BdZRM.jpg
Is that right?
Also, when I try to enter recovery, I get this:
http://i.imgur.com/pWUZS.jpg
(and before I get that I get the same Android outline with 2 spinning cogs inside, then it changes to that)
I don't actually get into recovery (first image I posted) until I press the Vol Up and power buttons at the same time.
EDIT 2: Disregard all that!
I got it all working using this, and XxLordxX's Lord AIO Tool.
Installed the ROM and GAPPS from this though.
ICS looks so damn nice on this I LOVE ANDROID!
Hey. I am happy you got all that working
For the previous images you posted, it seems boatloader was not unlocked and that is a pre-requisite for Recovery installation.
Now that it is working, Enjoyyyyyyy ICS
wesamothman said:
Hey. I am happy you got all that working
For the previous images you posted, it seems boatloader was not unlocked and that is a pre-requisite for Recovery installation.
Now that it is working, Enjoyyyyyyy ICS
Click to expand...
Click to collapse
Hmm. I ran through the bootloader unlocking on the device, changing the option with the arrow keys then it said
"Formatting UDA" then said it was finished..
Anyway, it's working now, and CWM works (obviously, as I now have the custom ROM installed).
Sent from my HTC One X using Tapatalk 2
EDIT -- never mind got it figured out!
ok i did these two steps
adb reboot bootloader
fastboot oem unlock
and the device rebooted back into HC like it was when i took it out of the box
now when i run adb devices it doesnt see it and if i do adb reboot bootloader it says device not found
dodgefan67 said:
EDIT -- never mind got it figured out!
ok i did these two steps
adb reboot bootloader
fastboot oem unlock
and the device rebooted back into HC like it was when i took it out of the box
now when i run adb devices it doesnt see it and if i do adb reboot bootloader it says device not found
Click to expand...
Click to collapse
Cool. Now ICS is ON?
wesamothman said:
Cool. Now ICS is ON?
Click to expand...
Click to collapse
yeah i found the thread to put the US rom on it, got the official HC from motodev and updated it OTA to ICS 4.0.4!! patiently waiting for JB now
Spanish Xoom?
Hi.
I have an Spanish Xoom Wifi, and I'm concerned about if this ROM (wingray):
- will work in my european/spanish XOOM?
- will allow me to change language and keyboard layout to Spanish?
- can this "english" ROM "brick" my device ? (I don't know if flashing an US or NON-Spanish rom in my Spanish device can brick it).
Thanks.
NoP_Compiler said:
Hi.
I have an Spanish Xoom Wifi, and I'm concerned about if this ROM (wingray):
- will work in my european/spanish XOOM?
- will allow me to change language and keyboard layout to Spanish?
- can this "english" ROM "brick" my device ? (I don't know if flashing an US or NON-Spanish rom in my Spanish device can brick it).
Thanks.
Click to expand...
Click to collapse
Yup. It works well on your device.
For spanish keyboard, get smartkeyboard and spanish addon. Enjoy.
Sent from my MZ601 using Tapatalk 2
Device Not found
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
---------- Post added 13th July 2012 at 12:20 AM ---------- Previous post was 12th July 2012 at 11:44 PM ----------
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
What does adb devices say? Use another USB port and use the USB cable it came with
Hahleq said:
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
---------- Post added 13th July 2012 at 12:20 AM ---------- Previous post was 12th July 2012 at 11:44 PM ----------
I've installed the SDK and Motorola USB drivers as instructed.
When I attach the Xoom, I hear the device connect chime. I even saw the fastboot driver message say "complete" with the happy green checkmark.
However, when I run:
adb reboot bootloader
I get error: device not found.
I tried the LIAOT tool and it also hangs up looking for the device.
Thx for any advice.
Click to expand...
Click to collapse
You need to make sure that usb debugging check box is checked under settings.
Sent from my Xoom using Tapatalk 2
rooted, flashed
Hi everyone.
I would like to thank you for all the developers here, for the information on how to do it. Without you guys I would stuck with stock honeycombe 3.2 here in the UK. I have been waiting for an official update OTA ics 4.0 for months, but still no sign if other Xoom users will ever get it.
Did it first time rooted, flashed, now running team eos wingray 4.0.4 ics, on my xoom mz604, what a huge improvement.
Thank you again for all of you!
We are here one community to help out. By the way jellybean is out for your device if you are interested.
Sent from my Xoom using Tapatalk 2
wesamothman said:
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
• Your custom ROM will be: http://goo.im/devs/teameos/roms/nightlies/wingray/
• Your GOOGLE APPs (GAPPs) would be: gapps-ics-20120429-signed.zip http://goo.im/gapps
Full thread in details can be found here: http://forum.xda-developers.com/showthread.php?p=20479464
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html • Recovery Image: http://goo.im/devs/teameos/recoverie...ecovery-r6.img
• GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
• ROM: http://goo.im/devs/teameos/roms/nightlies/wingray/
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to:
Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 40 - 50 seconds).
Advice: purchase Startup Manager from the market. Remove unwanted user programs from the startup. That will boost the boot time of your xoom. and don't remove superuser or superSU.
To have better battery life, from the market buy JuiceDefender ultimate. configure it as aggressive. don't worry, it is ok. This will give you around 2 hours of extra battery life than the promised 10 hours. Keep that in the startup.
You may need after that to install terminal emulator from the market if not already installed by the ROM to check if you have root permissions. Just type "su -" you will be prompted with superuser check. Click allow. and then type "id" You will see your id is root.
Should you require further details or assistance, please let me know. And enjoy the best rom customized ever for your device
Best Thanks to TEAM EOS for the great ROMs they provide.
After you are done with all that, let me know and will explain to you how to work with the pre-installed gooManager in the new ROM. It will make your life much easier to upgrade to future releases of your ROM.
Click to expand...
Click to collapse
AFTER adb reboot bootloader shows me adb not found in command prompt
some archive txt tells me that adb si moved and i need to donwload platforms tools via sdkmanager....is this correct?
thanks for the guide! i need some help with this!
MARIANOTE said:
AFTER adb reboot bootloader shows me adb not found in command prompt
some archive txt tells me that adb si moved and i need to donwload platforms tools via sdkmanager....is this correct?
thanks for the guide! i need some help with this!
Click to expand...
Click to collapse
Check step 4. Your Cmd have to be in SDK/tools, wherever that us, example, c:/SDK/tools/
Sent from my MZ601 using Tapatalk 2
Information: If you're experienced with ADB/Fastboot or Manual Android Rooting, you could read this thread and see if you find something that seems wrong and report to me, thanks!
IntroductionHello there!
I decided to create a new Nexus 7 Rooting Guide, I know that there are some guides already, but I have a few reasons to make this guide.
Unlike many rooting guides, this one doesn't use an automated program (a.k.a Toolkit) and it works for both Nexus 7 Wi-Fi and Nexus 7 3G.
This guide has been tested with a Nexus 7 3G Edition, running Android 4.2.1/4.2.2.
Last Topic Update: Never
Last Minor Topic Update: Check thread edit date!
Requirements:
Nexus 7 (Wi-Fi or 3G Edition)
Android SDK
ADB/Fastboot Drivers
Unlocked Bootloader
If you don't have ADB/Fastboot drivers installed, please check out this thread:
http://forum.xda-developers.com/showthread.php?t=1907796
See Basic Knowledge and Driver Installation parts.
If you have Android SDK and ADB/Fastboot drivers installed and working, you can continue reading.
Make sure you have USB Debugging enabled in your Nexus 7.
Don't forget to unlock the bootloader!
Warning: You're the only one responsible if something bad happens to your device!
Nothing bad is going to happen, but there is always a small risk.
Personally, I recommend having +60% of Battery during ROM Changes (Flashing and etc).
I also recommend you to learn how to do a Factory Image Restore (Flash Stock ROM) before attempting to root...
Rooting your Nexus 7
To root our device, we're simply going to put in our tablet a small program called "SuperSU", you might want to download it now to your PC:
SuperSU v1.04
Basically, we´re going to put SuperSU in /system partition, the file you downloaded is a "Flashable ZIP".
We're going to use TWRP (Team Win Recovery Project) to flash the Flashable ZIP (In this case, SuperSU), after flashing SuperSU you get root privileges!
Now, go to your Android SDK Folder where Fastboot (fastboot.exe) is located (platform-tools), open a command prompt and change directories to your Fastboot location, if you need help just search on Google.
Now, you have CMD (Command Prompt) open with the Android SDK Directory, and we need to reboot your device into Fastboot mode, to do that just type the following:
adb reboot-bootloader
Click to expand...
Click to collapse
You're now in Fastboot Mode (a.k.a Bootloader), type the following to make sure you're in Fastboot Mode:
fastboot devices
Click to expand...
Click to collapse
You should see something like this:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Type "fastboot reboot" to reboot the device, then copy the SuperSU.zip you downloaded to your Nexus 7.
I also forgot to tell you to download TWRP, if you have the Nexus 7 Wi-Fi Edition, your board codename is Grouper, if you have the 3G Edition, your board codename is Tilapia.
TWRP for Nexus 7 [grouper]
TWRP for Nexus 7 3G [tilapia]
Copy the correct TWRP Edition to your Nexus 7, then boot into the bootloader.
Temporarily boot TWRP using the following command:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Replace "TWRP.img" with the correct file name.
You can also flash TWRP instead of temporarily booting.
Inside TWRP click "Install" and select the SuperSU ZIP File, then Confirm Flash.
After flashing, reboot your device and you should have SuperSU installed. (Open SuperSU just to test)
Congratulations! You now have a Rooted Device!
To make sure you have rooted, download "Root Checker" from Google Play.
ConclusionAs you can see, this tutorial is a little different from others, I explained what we were going to do and also explained the commands instead of giving you directly the commands.
This tutorial was written to teach the basics of ADB/Fastboot, I hope you rooted your device without problems and learnt/learned something, have a good day!
Feel free to give suggestions or corrections!
This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.
Just for newbies wondering what this really means:
1. install and boot into TWRP/CWM recovery means you boot up a 'mini' linux which can do whatever it wants(as root) to any of the partition on the device(including the /system one)
2. the supersu package contains 2 files(an APK and the more importantly 'su') plus some update scripts that (1) would run and copy them to the appropriate places(mainly the 'su' which is the only file that is critical)
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
bftb0 said:
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
Click to expand...
Click to collapse
Hello!
Thanks for your answer, I completely forgot about the "Unlocking Bootloader" part, tomorrow when I get some time I will edit the thread...
Have a good day/night.
Edit: Added "Unlocked Bootloader" to the requisites list and a small note after "Make sure you have USB Debugging enabled in your Nexus 7", tomorrow I may edit the thread again.
Edit 2: I think the essential part is written, and because I'm a little busy, I will leave (temporarily) this thread. You're free to enhance this guide and re-publish it following Creative Commons Attribution-NonCommercial 3.0 Unported License.
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!
There doesn't seem to be a comprehensive guide on this, so I thought I would provide one.
READ THIS FIRST
DO NOT TAKE ANY OTA UPDATES!!!
Please consider the following:
Ask yourself these two questions: "Why do I want to unlock my bootloader? Why do I need root access?" If the answer to either one of those is "I don't know," don't do it. Both of these actions weaken the security of your phone, and there's no reason to do that if you're not sure why.
This guide is for the Droid Turbo, model XT1254. It is not for the Droid Turbo 2, and it is not for any phone that is not named Droid Turbo.
Standard XDA rules apply. I'm not responsible for anything you do, and neither is anyone else other than you.
I'm assuming that you are running a Windows PC. If you have a Mac, I can't help you. If you're running Linux, you shouldn't need help.
This method is not free. It costs $25 (USD). If that's not okay with you, don't do this.
Once your bootloader is unlocked, you CANNOT safely re-lock and unlock it again. See this thread for what happens when you try to do that: http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081#post65095391
Still here? Cool.
Section 0: Installing Firmware Version MCG24.251-5
1. Go to Settings -> About phone -> Build number. If it says SU4TL-44, SU4TL-49 or MCG24.251-5, skip to section 1 of this guide. If it says MCG24.251-5-5, you need to take an extra step to unlock your bootloader. I'll explain later. For now, just skip to section 1 of this guide. If it says anything else, keep reading.
Flashing MCG24.251-5 using this method will erase all of your data. Back up any important files/information before proceeding.
2. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
4. Download the MCG24.251-5 firmware package from here: https://www.androidfilehost.com/?fid=889764386195901169
5. Extract the contents of the MCG24.251-5 firmware package to the installation directory of Minimal ADB and Fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot on any 64-bit installation of Windows).
6. Power off your phone.
7. Hold down the volume down button and power on your phone. Release the volume down button when you see that the phone has booted into bootloader mode. You'll see a dead green android.
8. Plug the phone into your computer.
9. Open the Minimal ADB and Fastboot shortcut on your desktop. This will open a command prompt.
10. Type "fastboot devices" and press enter. If it displays your device's serial number, you're ready to go. If it displays nothing, your computer is not recognizing your device properly.
11. Navigate to the installation directory of Minimal ADB and Fastboot and double click on FlashAll.bat. This will flash MCG24.251-5 to your device and erase all of your data.
12. Use the power button to select Start in the bootloader menu to boot normally.
13. Set up your phone at least to the point where you can install apps if you want to.
For now, just try to ask someone nicely to help you out with this. I'll try to get this done before the end of the day.
Section 1: Unlocking the Bootloader
1. Download Sunshine from here: http://theroot.ninja/download.html
2. Move the apk file to a convenient location on your phone. If you downloaded it with your phone, it's in your downloads folder already, so leave it there.
3. Use any file browser on your phone to navigate to the folder that contains the Sunshine apk file. Tap on it to install it.
4. If a message comes up and says that you need to enable installation of apps from unknown sources, follow the instructions on that message to enable it.
5. Enable Wi-Fi on your phone if it is disabled. Even if you aren't connected to a Wi-Fi network, it still needs to be on.
6. !!!DO THIS STEP ONLY IF YOU'RE ON MCG24.251-5-5!!! Follow the instructions here to obtain temporary root: https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/. DO NOT perform the uninstall step.
7. Open your app drawer and start Sunshine.
8. Follow the instructions.
9. !!!FOR MCG24.251-5-5 ONLY!!! Sunshine will reboot your phone automatically, and it will go into a bootloop. This is normal. Don't panic. Hold down the volume down button until the phone goes into bootloader mode. Plug your phone into the computer, start Minimal ADB and Fastboot (see Section 0 for link if you didn't have to install it before this point), and enter the command fastboot oem config fsg-id "". This will disable the temporary root exploit. Reboot your phone normally, and everything should be happy again.
10. If, when your phone reboots, you see a "Warning: The bootloader is unlocked" message, you have successfully unlocked your bootloader. If you do not see this message, open Sunshine again and follow the directions again. If you're on MCG24.251-5-5, you'll have to gain and uninstall temproot again at the appropriate times.
Section 2: Installing TWRP
Team Win Recovery Project is arguably the most important tool to have on a bootloader-unlocked phone. This is how you install it:
1. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790. If you already did this in section 0, you don't have to do it again.
2. Download the latest TWRP .img file from here: https://www.androidfilehost.com/?w=files&flid=39562
NOTE: The TWRP file that you download should have a .img extension. Make sure you can see this. If you don't see .img at the end of the filename, Google how to make file extensions visible on your version of Windows and do it. If you do not do this, you may run into trouble later.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481. If you already did this in section 0, you don't have to do it again.
3. Rename the file that you downloaded in step 2 to TWRP.img
4. Copy TWRP.img to the directory that you installed Minimal ADB and Fastboot to. The default location on an installation of 64-bit Windows is C:\Program Files (x86)\Minimal ADB and Fastboot.
5. Turn off your phone.
6. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Poor little guy...
7. Plug your phone into your PC.
8. Double click on the Minimal ADB and Fastboot shortcut that's on your desktop. It will open a command prompt.
9. Type "fastboot devices" without quotes and press enter. If it gives you your phone's serial number, you're good to go. If it gives you nothing, your device is not detected. This can happen for several reasons, and I won't discuss them here. However, if you followed these directions and all of your hardware is functioning properly, you should be good to go.
10. Type "fastboot flash recovery TWRP.img" without quotes and press enter. It should tell you that the flash was successful. You might see some "not found" errors. These are normal and can be ignored.
11. Highlight "Recovery mode" on your phone using the volume up and down buttons.
12. Press the power button to boot into TWRP.
13. TWRP will boot, and it will ask you if you want to allow write access to the system partition. IT IS VERY IMPORTANT THAT YOU ALLOW THIS. Check the box that says to never ask this question again.
14. Select Reboot, followed by System to boot the phone normally.
Section 3: Gaining Root Access
If you intend to install a custom rom, these steps are not necessary. Custom roms almost always come with root access built in. Refer to the thread of your custom rom of choice for installation instructions.
If you do not want a custom rom, and you simply want root access on the stock Droid Turbo rom, continue reading.
1. If you are on the stock marshmallow rom, build MCG24.251-5 or higher, download the latest version of both Magisk and Magisk Manager to your phone: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
NOTE: You need to be on marshmallow to use Magisk to root your phone. The Magisk thread says it supports lollipop and higher, but it only supports lollipop for some stock Samsung roms. This does not apply to you. If you want to root your phone on lollipop, you'll need to use SuperSU. I won't go into that here because I don't think there is a lot of demand for it, but if you need help with that, reach out to someone here. It's not difficult.
2. Install Magisk Manager the same way you installed Sunshine.
3. Turn off your phone.
4. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Andy, what have they done to you?
5. Use the volume up and down buttons to highlight "Recovery mode."
6. Press the power button to select Recovery mode.
7. Select Install from the TWRP main menu.
8. Select the most recent version of Magisk (the .zip file, NOT the Magisk Manager .apk file) that you downloaded.
9. Swipe the bar at the bottom of the screen to flash this zip file.
10. When it finishes, select Wipe Cache/Dalvik and swipe the bar at the bottom of the screen.
11. Select Reboot System
Section 4: Passing Safetynet using Stock, Unrooted Marshmallow
If you are running stock marshmallow with an unlocked bootloader, you will fail safetynet verification (and be unable to use Android Pay). Installing Magisk is the only recommended method, as of this writing, to bypass this limitation. If you completed Section 3, you shouldn't have any trouble. Understand, however, that there is a constant game of cat and mouse going on between Google and Magisk's developer, so sometimes Google will update safetynet to beat Magisk. If that happens, wait for Magisk Manager to tell you that a new version of Magisk is available, and it will install the new version for you. That's your best bet for passing safetynet again.
If you really want to pass safetynet, but you really don't want to be rooted, you can disable root (Superuser access) in the Magisk Manager settings.
Section 5: Miscellaneous
Here are some links to stuff you can flash now that your bootloader is unlocked:
Official LineageOS 12.1 (Android 5.1.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3260253
Official LineageOS 13.0 (Android 6.0.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3353298
AOSPExtended (Android 7.X): https://forum.xda-developers.com/moto-maxx/general/rom-aospextended-rom-v3-1-t3555361
Unofficial LineageOS 14.1 (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-t3494646
crDroid (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-crdroid-android-t3491257
Android Open Kang Project (Android 7.X): http://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Resurrection Remix (a great LineageOS-based rom, Android 5.1.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-5-5-5-t3197643
Resurrection Remix (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232
Resurrection Remix (Android 7.X): https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109
Computerfreek274's optimized stock rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
MoKee Open Source Project (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-mokee-opensource-project-t3188936
Bliss Rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-bliss-rom-6-4-team-bliss-t3422937
Android Open Kang Project (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-android-kang-project-t3422456
Android Open Kang Project (Android 7.X): https://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Change the splash screen (the bootloader unlocked warning message) that you see when you first start your phone: http://forum.xda-developers.com/dro...custom-boot-logos-accepting-requests-t3262873
Xposed framework and installer (make sure to use the sdk22-arm version if you're running a lollipop rom, sdk23-arm if you're running marshmallow. Not available for nougat yet.): http://forum.xda-developers.com/showthread.php?t=3034811
Alternative Material Design Xposed Installer that provides additional features: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Pon-3 Audio Mod (modified and improved Viper4Android. It makes your phone sound better.): http://forum.xda-developers.com/showthread.php?t=2530976
Other modded Viper4Android versions that are better than PON-3: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Theme your TWRP with different colors: http://forum.xda-developers.com/android/themes/theme-twrp-3-0-0-0-dark-stock-colors-t3310235
More TWRP themes: http://forum.xda-developers.com/showpost.php?p=66276401&postcount=2889
Android N Emojis: http://android.wonderhowto.com/how-to/get-android-nougats-all-new-emojis-right-now-0170328/
Section 6: Troubleshooting
Issue: When you try to boot TWRP, you see a screen that says "no command." TWRP does not boot.
Solution: The screen you are seeing is the stock Droid Turbo recovery menu (the menu that you're trying to replace with TWRP). If you see this after flashing TWRP, one of two things happened:
-You did not boot into the recovery menu immediately after flashing TWRP, and it was therefore replaced by the stock recovery menu.
-When you flashed TWRP, the process did not complete successfully.
The solution to both of these problems is to repeat section 2 and follow the instructions more carefully.
Issue: When TWRP asked you if you wanted to allow write access to the system partition, you selected no. Now you cannot flash anything.
Solution: At the main TWRP menu, select Mount. Uncheck the box that says "Mount system partition as read-only."
Issue: Fastboot says "cannot load TWRP.img" when you try to flash it.
Solution: This error indicates that Fastboot cannot find TWRP.img. The most common source of this problem is that you did not make your file extensions visible, and so when you renamed the TWRP file to TWRP.img, you actually renamed it to TWRP.img.img (including the hidden .img file extension that you didn't realize was there). Google how to enable file extensions on your version of Windows, follow those instructions, and if this is the issue you will see it.
nice write up - will follow these when I get my phone tomorrow.
worked!
Just tried this. Worked amazingly, and exactly as you described! Thanks!!
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk
SpyderPride said:
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Nope, no matter what I do, it stays on that screen. I have to reboot and then it returns to normal. I've followed all of the steps twice now and got the same results each time. I do have the phone still plugged into the computer charging.
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before
5.1
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?
CatMan8 said:
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?
Click to expand...
Click to collapse
if u want an unlocked bootloader then take the OTA
22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
The screen that you're seeing is the stock Droid Turbo recovery menu, which means that TWRP is not getting flashed. What result does it give you after section 2, step 10?
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Yeah, I did the exact same thing. The MDK bootloader is golden. I broke my phone once and almost cried. Luckily, I was able to get another MDK on Swappa. The seller wasn't even charging extra for it! He/she must not have known what they had.
As for Viper4Android, I've added a link to section 4 that you might want to look at.
iceblitz4 said:
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before
Click to expand...
Click to collapse
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.
s4shield said:
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.
Click to expand...
Click to collapse
Such is life. Sometimes if you want the wubz, you gotta take the brony.
TheSt33v said:
Such is life. Sometimes if you want the wubz, you gotta take the brony.
Click to expand...
Click to collapse
Ha ha ha!
successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.
Awesome post. It definitely will come in handy. One question, at what point should I create a backup image via twrp? Is it before section 3 step 7?
s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Download the file www.viperforandroid.com install goto menu set as expert ui under ui setting open viper4android check on click box click appropriate sound changer so it sounds right to u I suggest doing on headphones than use thoose settings as base settings for phone bt ect.. The the real good sound comes in under conolover files you must download impulse response files or. Irs files dfx_pro_surround_2.irs, Dolby,, dfx ect. After u download you unzip and using a file manager find unzipped file and goto sd card u will see viper4android folder inside that folder you will see 2 other folders one being kernel place irs files in kernel folder. Now when you click impulse response you will have the audio producing files. Like Dolby digital cinema, stereo, HD. Ect there are hundreds I'll post my walk though install video
can you help me sir
my friend have verizon moto droid ultra xt1254 and he already give it to me
and i got this phone with google account privacy and he forgot last email in this device, so i cant finished setup wizard and go to home screen
this device locked bootloader so i cant do something to
what should i can do?
jco23 said:
successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.
Click to expand...
Click to collapse
Thanks for the help.
After I got stuck, I downloaded and installed KingRoot. It successfully rooted my phone. I downloaded two different root checkers and they confirmed. Everything works correctly within Rom Toolbox Pro now, I can remove apps (stupid NFL mobile, Amazon, etc). My software status says "Modified". I did not need to format or anything like that. Is that normal? My only issues are with XBlast Tools and SuperSU, when I change a setting in XBlast, it does NOT get updated. Even after a reboot. In SuperSU cannot update binaries for some reason.
I cannot post outside links for screen shots yet.
Hi,
picking an os for daily driver: Look what is currently the newest android (android 11) and pick the last or pre last version, so android 9 or android 10 (and scroll a bit through the most viewed threads if someone has problems or is giving review by saying that it runs smooth; in the end most roms are based on lineageos and although some say they are more performant, hear this: If there were a really good tweak with no bad side effects than lineageos would have already implemented it. So a lineageos rom will do, but better be looking through some threads). This products will have pretty new features but have (nearly) all bugs fixed. E.g. you choose this one: https://forum.xda-developers.com/t/rom-10-0-official-crdroid-v6-12-osprey.4075505/ .
There you will see an instruction list, which is good, BUT: You first have to install twrp recovery. Coming from an Samsung Smartphone this was new for me on moto, because now you have to use fastboot to install twrp and go through an unlocking process.
( 0) backup )
1) install drivers
2) get adb and fastboot tools
3) unlock your phone
4) install twrp
0) Backup your data, they may be lost during unlocking
1) Go to https://support.motorola.com/us/en/drivers and download and install the drivers. They are important for windows to speak to your phone.
2) The tools adb and fastboot are part of a larger android sdk which you probably don't want to completley install. But you will also probably want to have an official download link. So the best thing for you will be probably https://developer.android.com/studio/releases/platform-tools . Downlaod the plattform tools and extract them somewhere.
3) Now you have to go to the official unlocking process and have to create an motrola account for that (just use and 10 minute mail). See this: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and for further help look at this video:
. You will get some code which you will send to motrola which will send you an unlock code.
4) And after you did the whole stuff including enabling devloper mode and debugging and unlocking in that developers settings and have unlocked your phone, you can use
"./adb.exe reboot bootloader" and " ./fastboot flash recovery twrp-3.4.0-1-osprey.img" to reboot to booloader and install twrp.
Now you can do the steps which are e.g. shown in the above rom thread.
Hope this helps somebody, i first had to get used to that stuff and frist had errors (validation fail and whatever things) in my console with adb and fastboot, but after correctly unlocking and so on it worked.
Greets an thanks for all devlopers empowering such and old phone.