Related
The aim of this guide is to enable you to install a custom firmware on your Optimus G while being as clear, accurate and succinct as possible. This guide is intended for use by Windows users with an AT&T Optimus G (AKA LGE970).
I've presented the following sections in a specific order for a reason: you need to root to unlock, and you need to unlock to install a custom firmware. If you're currently running what the manufacturer gave you, you need to start with rooting, then unlocking, then trying other firmwares. Be careful, good luck, and have fun!
How to "root" your Optimus G
(Optional if you have another means of un-RARing) Download and install 7-zip from here. You need this to open certain types of archives (specifically .rar, but you might also want to open .tar, .bz2, or other types of archives in the future). This program is supremely awesome in its ability to open almost any archive you throw at it. It's also unobtrusive and efficient.
Download and install LG USB Drivers from here. Without these drivers, your computer won't be able to effectively communicate with your phone. This is vital for the steps we will be taking.
Enable USB debugging by going to Settings->(General)->Developer options" and checking the box next to "USB debugging." You will get warnings. You can probably ignore them. This setting will allow you to run commands on your phone from your computer (via USB). For more info on the Android Debug Bridge, click here.
Download and extract (using 7-zip (or whatever)) the root exploit from here.
Connect your phone to the computer with your USB cable.
Put the phone into "Charge Only" mode at Settings->General->PC connection->USB connection type
Open CurrentRoot.bat and follow its prompts. You will need to change from "Charge Only" to "Media sync (MTP)" mode. The setting is in the same place.
Run SuperSU (now in your apps drawer) it and make sure it works. This program allows others to gain access to superuser privileges. For more info on rooting and what kind of stuff it lets you do, click here and/or use Google.
If that didn't work for you, try following instructions from the thread where this root method came from.
How to unlock the bootloader
The bootloader is the first program your phone runs and its main job is to load the operating system. The stock bootloader is locked and will only run versions of Android that LG and AT&T want it to. Since our goal is to install and run custom firmwares, we must circumvent this locked bootloader. Luckily, thecubed and Shellnut2 have found a way to do this for us. What you want to do is buy Shelnutt's app. There are several reasons you should throw down some cash on this:
It's way easy to use
It'll make backups of your stock recovery/bootloader for you, it'll also make restoring these backups easy
The money is for a good cause
If you're still confused, visit thecubed's thread. He is the man, thank him a billion times. Then thank him again for being a nice guy.
For the convenience of those interested, here is the more laborious/error prone/manual way to unlock (NOTE: this method does NOT work if you've updated to Jelly Bean, you need to use the app):
If you haven't already, download and install 7-Zip and the LG USB drivers, and make sure you have USB Debugging turned on (see above).
Download the latest version of the bootloader unlock here (latest version has the highest version number).
Ensure that your screen is on and unlocked (I'd go to "Settings->Display->Screen timeout" and set the timeout to never to make sure the screen doesn't go off during this process). Your screen must remain on because SuperSU will ask you to grant superuser privileges to the unlock script and you want to be able to tap "Yes" when the time comes.
Connect your phone to the computer with your USB cable, and run the freegee.bat script in extracted files on your computer. Do NOT run this script as administrator. The install will fail if you do. Follow the prompts. You can ignore "No space left on the device" errors, but "adb.exe not found" or "tar: invalid magic" errors are not negligible and indicate either you skipping a step, a funky download, or something very bad.
Once the script finishes, make sure you have a populated "backups" folder in the folder where freegee.bat lives. The backups folder contains your original stock/locked bootloader, which you might want if you ever want to revert to stock.
If you're sure the script ran successfully, power off the phone. Next, hold down the power and volume up keys simultaneously to enter fastboot mode. You should see a screen that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In fastboot mode, there is a menu, but it's hidden. To navigate it, remember that volume up moves the cursor up, volume down moves it down, and power selects the currently highlighted option. The options are, in order:
Start - boot the phone normally [highlighted by default]
Restart Bootloader - reboot into bootloader
Recovery Mode - enter ClockworkMod recovery (more on this later)
Power Off - (duh)
Here is a video of thecubed showing you how to get to ClockworkMod from the bootloader (like a boss):
Using Team Win Recovery Project
Team Win Recovery Project (AKA TWRP) is a recovery, which basically allows you to install new firmwares and apply updates/modifications to already-installed firmwares (and a bunch of other things, like mounting and formatting portions of your phone's memory). It is the default recovery option when you use the Freegee app to unlock your phone (the other is Clockworkmod, which is so similar I won't be writing a separate guide on how to use it). Navigating TWRP is fairly self explanatory. Many great guides on how to use TWRP have been written and can be found via Google. Here is the first search result that came up for me. It's a pretty good guide.
One thing I will vehemently recommend is that you make a backup every time you install a new firmware. Personally, I backup apps and texts with Titanium Backup and my current firmware via TWRP (the linked guide explains how to make a backup in TWRP). Backups are a good idea and people should always make them. ALWAYS.
Installing custom firmwares
Follow the firmware author's instructions EXACTLY. These guys know what they are doing, certainly more than you or I. Check out the development threads for ROMs to try out.
Note: Be sure that if you are installing ROMs that require the Jelly Bean OTA update that you have taken that update.
There are two ways to do this: receive the update as intended (Over The Air) or use LGNPST (guide on using that under FAQ 3.a of this post) or autoprime's awesome tool, TeenyBin.
FAQs
How do I upgrade FreeGee? The easiest thing to do is simply install the new version of FreeGee the way you did the old one. It will work. Make sure you keep your original locked bootloader in a different, safe place though, just in case you ever want to revert to stock (if you try to return your phone, for example).
How do I disable that pesky OTA update notification? This comes courtesy of shawnchalfant and adfurgerson (visit ad's thread for more details): go into Titanium Backup and freeze the following programs: com.lge.lgfota.permission 4.0.4-91f513f88d AND com.lge.omadmclient 3.2.21
How can I re-lock and un-root my phone?
How to LGNPST to restore a factory image.
Obtain the following files: AutoLGNPST-tSilenzio.zip (available on IRC), and the firmware. Unzip AutoLGNPST-tSilenzio.zip and follow the instructions in "READ ME FIRST.txt" (mad props to tSilenzio for automating this process).
Here's the laborious/error prone/manual method for LGNPST-ing back to stock.
You need to obtain the following files: LGNPST-PhantomPhreak53.zip, LGNPST_ACG_2.2.3_Lab.zip, and the firmware. Follow the following steps (please note: I am less experienced with this process and find it much more tedious. Also, IMHO, I don't think the people you're returning the phone to will care if you leave some minor traces of your unlocking shenanigans. I think the process above this is more than sufficient and simpler). Credits go to Jhoopes517 for this process, he showed me how to do it in his thread.
(Install LG USB drivers)
Extract LGNPST_ACG_2.2.3_Lab.zip, run the installer. Open file explorer to C:\Program Files\LG Electronics\LGNPST and replace the current LGNPST_ACG.exe with the one in the extracted folder (if you are on a 64-bit version of windows, go to C:\Program Files (x86)\LG Electronics\LGNPST)
Extract LGNPST-PhantomPhreak53.zip and run LGNPST_GenericModels_Ver_5_0_12_0.exe and then run LGNPST_Components_Ver_5_0_20_0.exe
In file exlorer, navigate to C:\LG Electronics\LGNPST and copy over the "Models" folder from the extracted Phantom zip folder
Run cmd as administrator and execute the following
Code:
regsvr32 "C:\LG Electronics\LGNPST\Models\LGNPST_LS970.dll"
Extract LGE970AT-01-V20j-310-410-MAR-08-2013.zip and change the extension of the .tot file to .bin
Connect phone to computer, power off, and then power on, holding down the power button and both volume buttons
Run the newly replaced LGNPST_ACG.exe from step 2. Select the DLL from step 5 and the .bin from step 6.
Press Start
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release. DO NOT disconnect the cable before LGNPST is done doing its thing. Your phone may reboot. This is OK.
(If you are using Shelnutt's app, simply use the button in the app to re-lock and install the stock stuff).
Here's the laborious/error prone/manual method for re-locking the phone and installing the stock recovery/bootloader/kernel.
Remember the backups of the locked bootloader that you kept? You're going to need them. Obviously, you'll need USB Debugging enabled and LG USB drivers installed. Copy them to your phone's "Internal Storage" in a folder, in this example it's called "backups." Connect the phone to your computer via USB, open a command line (cmd) and type the following:
Code:
cd C:/some/folder/where/you/have/adb.exe/eg/your/freegee/download
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/backups/aboot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/recovery-att-backup of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot-att-backup.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd basically copies from the if= location and writes to the of= location. The first three dd steps write a bunch of zeros to the recovery, boot, and aboot partitons, the last three write the backups to aboot, recovery, and boot. If you want to know more, read all about dd here and/or Google. If you lost your backups, you can try writing mine.
Now you've restored the stock bootloader and recovery, but your phone is still rooted. To unroot it, open SuperSU, go to its settings, and tap "Full unroot." Do a factory reset (Settings->General->Backup & reset->Factory data reset) and you should be good to return the phone to AT&T (or whatever).
Be careful with these last two methods if you have removed any bloatware or installed a custom firmware, you may prefer to LGNPST back to stock (LGNPST is almost always a safe way to return to stock).
blenkows said:
Haha I wish I had seen this earlier. I had screenshots before and after so I could see exactly what was removed but I had just deleted them. From memory, it doesn't seem like too much was removed. All the AT&T apps are gone but it appears LG's apps are still here.
Click to expand...
Click to collapse
Here is a list of apps I had shortly after factory reset on stock for people to compare with theirs. I have struck out the ones I was able to remove without my phone blowing up. Let me know if you safely removed one and I'll strike it out. Also let me know if I missed any or included an app which isn't part of stock. Thanks!
AAT
Adobe Flash Player 11.1
Adobe Reader
Amazon Kindle
Android keyboard
Android live wallpapers
Android system
Aspect ratio correction
AT&T address book
AT&T code scanner
AT&T family map
AT&T hot spots
AT&T locker
AT&T messages
AT&T navigator
AT&T ready2go
AT&T smart wi-fi
Bluetooth share
Browser
Bt/wifi test
Bubbles
Calculator
Calendar
Calendar storage
Calendar widget
Camera
Car home
Certificate installer
City ID
Clock
com.android.backupconfirm
com.android.providers.partnerbookmarks
com.android.providers.settings
com.android.sharedstoragebackup
com.lge.lgdrm.permission
com.lge.lgfota.permission
com.lge.lockscreen
com.lge.omadmclient
Contacts
Contacts storage
DeviceHelp
Download manager
Downloads
DRM protected content storage
DRM service
Email
Email widget
EmailServices
Face unlock
Facebook
Favorite contacts widget
File manager
File networking
FileShare
Finance
Gallery
GestureOverlayService
Gmail
Google account manager
Google backup transport
Google calendar sync
Google contacts sync
Google partner setup
Google play books
Google play magazines
Google play movies & tv
Google play music
Google play services
Google play store
Google search
Google services framework
Google text-to-speech engine
Google+
Home
Home selector
Home theme - Biz
Home theme - cozywall
Home theme - marshmallow
HTML viewer
Key chain
Lg keyboard
Lg tag+
Lg voicecommand speechpack
Lgapduservice
Lgatcmd service
Lgsmartcard service
Lgsystemserver
Live tv
Live wallpaper picker
Local search
Lock screen settings
Maps
Marionette
Market feedback agent
Media home
Media storage
Messaging
Multi-photo live wallpaper
Music
Music
Musicfx
My uploads
MyAT&T
Network location
News
NFC service
Nfsservicemanager
Note pad
Note pad widget
On-screen phone
Package access helper
Package installer
Phone
Phone/messaging storage
Photo frame
Playready cert test
Polaris office 4.0
Power control widget
Quickmemo
Search applications provider
Settings
Setup wizard
Shutdown monitor
Sim toolkit
Smartshare
Social+
Streaming player
System ui
Talk
Task manager
Today+ widget
Tom's diner
Twitter
User dictionary
Usermode
Vidclip
Video wiz
Videos
Voice command
Voice search
Voicemail
VPN client
Vpndialogs
Wap service
Weather
Widevine keybox test
Wiper app
Wise screen
World clock widget
YouTube
Yp mobile
I can't root. What do I do?
Double check that you have followed all the steps in this guide (USB drivers, correct settings, etc.) If your software version ends in "c," you need to LGNPST to the version that ends in "o" (see the section on LGNPST in this post).
Why shouldn't I run the Nexus 4 conversion?
See this post by thecubed. Don't be impatient, a legit, safe ROM is forthcoming here. Messing with partition tables is needlessly risky.
My shiny new firmware has no APNs and I don't get mobile data! What do I do?
Use the APN settings in this post. They have always worked for me. If they don't try setting the "APN" variable to "pta" instead of "Phone."
... (ask me more questions!)
I hope you found this useful. Obviously this is a work in progress. I am way open to suggestion, please leave a comment below! If you liked this post, hit the thanks button and/or rate this thread so that others know this guide is legit. Thanks!
Very nice, man. This is great for people who don't want to have to hop between threads for all the different information.
I recommend we sticky it.
this is definitely appreciated. i was looking for a guide when i first rooted and unlocked, just to read along with making sure i was doing it right. more just to double check my process than actually needing it.
This is the best root/ROM guide I've ever seen. Excellent job.
Sent from my LG Optimus G
anyone try this on E97110d
should it work?
cpus456 said:
anyone try this on E97110d
should it work?
Click to expand...
Click to collapse
I haven't so I can't recommend trying it.
Awesome work! someone please sticky
all worked great!
can you please also post a guide on how to lock back the device and unroot.
and also how to update to a new version of freegee if it comes out.
Please
?
Thank you.
karelson said:
can you please also post a guide on how to lock back the device and unroot.
and also how to update to a new version of freegee if it comes out.
Please
?
Thank you.
Click to expand...
Click to collapse
Both of those requests are covered in the OP. Specifically, look at FAQ #2...If you can't understand that, I can't help you.
Carrett can u do a guide for going back to stock? Flashing a stock Rom....got the files I need just have no clue what to do. .need to return my phone.thanx
Sent from my LG-E970 using xda premium
martyotaku said:
Carrett can u do a guide for going back to stock? Flashing a stock Rom....got the files I need just have no clue what to do. .need to return my phone.thanx
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
What files do you have exactly? The easiest way to do it, in my opinion, is to follow the steps in FAQ #2.
i have the stock rom(i deleted some bloat) and i went on thecubed's irc and got some dlls and and a lg program but no clue what to do
Is there a way to restore? I totally messed up. My phone won't turn on at all. Help would be appreciated thanks.
i need a step by step for LGNPST back to stock if possible please
martyotaku said:
i need a step by step for LGNPST back to stock if possible please
Click to expand...
Click to collapse
I have never LGNPST-d my way back to stock, nor do I plan on doing it. If you are already unlocked, my advice to you is to obtain APKs of any bloat you removed, reinstall them, and follow my method for relocking and unrooting. That being said, you may be able to find someone willing to walk you through LGNPST-ing in IRC. I will try to figure out how to do it and if I feel confident I'll write a how-to. If someone wants to supply me with a howto, I'd be happy to include it in the OP and credit them (assuming their how-to makes sense and I can easily follow it).
Honestly though, it seems like a pointless exercise when you have CWM and su.
Sorry I can't be more accommodating.
carrett said:
I have never LGNPST-d my way back to stock, nor do I plan on doing it. If you are already unlocked, my advice to you is to obtain APKs of any bloat you removed, reinstall them, and follow my method for relocking and unrooting. That being said, you may be able to find someone willing to walk you through LGNPST-ing in IRC. I will try to figure out how to do it and if I feel confident I'll write a how-to. If someone wants to supply me with a howto, I'd be happy to include it in the OP and credit them (assuming their how-to makes sense and I can easily follow it).
Honestly though, it seems like a pointless exercise when you have CWM and su.
Sorry I can't be more accommodating.
Click to expand...
Click to collapse
I kinda need LGNPST. Somewhere during rooting, my phone just wouldn't turn back on. It did that screen flicker thing and the buttons flicker, but it stayed there for about 10+ minutes. So i figured, i wanted to start fresh with factory settings again. When i try to run LGNPST, it goes to 67% then the phone leaves download mode and then LGNPST says it's been disconnected and that i should restart my phone and then it can continue. Problem is that the phone can't even boot up at all.
I even tried the unbrick guide from the other optimus g forum but i can't get ahold of the .KDZ file. I'm not even sure if that process can work on an AT&T optimus g. Spoke to people on IRC and said that it sounds like a hardware issue. If i can't get this thing to boot, i'm going back to BestBuy to exchange for another one.
aznracer62 said:
I kinda need LGNPST. Somewhere during rooting, my phone just wouldn't turn back on. It did that screen flicker thing and the buttons flicker, but it stayed there for about 10+ minutes. So i figured, i wanted to start fresh with factory settings again. When i try to run LGNPST, it goes to 67% then the phone leaves download mode and then LGNPST says it's been disconnected and that i should restart my phone and then it can continue. Problem is that the phone can't even boot up at all.
I even tried the unbrick guide from the other optimus g forum but i can't get ahold of the .KDZ file. I'm not even sure if that process can work on an AT&T optimus g. Spoke to people on IRC and said that it sounds like a hardware issue. If i can't get this thing to boot, i'm going back to BestBuy to exchange for another one.
Click to expand...
Click to collapse
The folks in IRC know much more about lgnpst than I do. There's no secret that's being withheld, and unfortunately my best guess is that the lgnpst experts in IRC are right and it is a hardware issue. The good news is that you don't have to tell Best Buy the events leading up to your phone's demise and they probably won't be able to tell what they were either (we're talking about Best Buy employees here; most don't give two craps about their job).
Found a how to for a different lg phone here. Not certain that it will work for ours but it's worth a try. If it works for you, let me know and I'll add it the OP for others.
carrett said:
Found a how to for a different lg phone here. Not certain that it will work for ours but it's worth a try. If it works for you, let me know and I'll add it the OP for others.
Click to expand...
Click to collapse
I've tried something similar to that. Basically that's just an older version of LGNPST but when you use it, it says verizon wireless on it, well the one i downloaded at least. And you're right, took it to best buy and they didn't ask about it. I have up to January 24 to exchange it again in case it happens again. If the guys on IRC say it's hardware after explaining exactly what i did, it's the hardware. Gotta admit, i'm new to LG. I came from a line of Samsungs. Usually if anything goes wrong id just reflash with Odin or Heimedall and everything's back to normal again. LGNPST does the same function? From what i've read it serves the same purpose.
Anyway, take 2 on this guide. Deleting everything LG from my computer and starting fresh. One thing that i did notice when rooting, cmd gave me an error saying i'm missing backup_restore.apk (or something of similar name).
grizzlayleslay presents:The Complete Guide on Tinkering with your
Motorola Milestone X2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings and Welcome!
If you're here, you have a Motorola Milestone X2. You have 2.3.6 Gingerbread, and you probably hate the Blur stuff forced upon you in 2.3.6. We know. This is a dual-core phone and it feels like you're not getting the full potential out of it. Thanks to the courage and hard work of many members, we CAN get more out of this phone. Believe the impossible.
What follows is the most thorough guide on XDA for tinkering with your Milestone X2. There are many parts to this guide, and I recommend reading through all of it if you plan on tinkering with your Milestone X2.
Before going forward, I must repeat: This guide is for, and only for, Gingerbread 2.3.6 running on your Motorola Milestone X2.
I'm sure some parts of the guide can be utilized for the Droid X2 but considering that us Milestone X2 users are lumped into the Droid X2 forum and must frequently scavenge several topics before getting the documentation we need, this guide is written under the assumption that you have a Milestone X2 and that you're modifying it.
This guide is not for Android 2.3.4, 2.3.5, 2.3.batman, or anything NOT called 2.3.6. The Milestone X2 was shipped with 2.3.6 so this guide is written FOR 2.3.6, and will not be revised for any other version of 2.3. If you're not running 2.3.6 on the Milestone X2 and you choose to follow the guide anyway, that's your choice and I hold no responsibility for your gallivanting ways.
With that, let's go forward.
==================================================================
Table of Contents
Part 1: Back up the Personal Essentials
Part 2: Factory Reset Time
Part 3: Install and Update the Bare Essentials
Part 4: Rooting the Milestone X2 with 2.3.6
Part 5: Creating the Nandroid/BSR Backup
Part 6: Nandroid Restore Procedure
Part 7: Custom ROM Installation with DZK's CMOD10 2.9999999 Alpha
Part 8: Performance gains with CM10 and the MX2
Part 9: Performing an SBF Restoration on the MX2
==================================================================
REQUIREMENTS:
It is assumed that you have the following utilities handy before going forward:
A computer running Windows XP/Vista/7/8
A computer ALSO running Linux
A Motorola Milestone X2 with the USB cable that it came with when you bought it.
A Wall Charger for your Milestone X2
It is also assumed that you understand the following principles of Android tinkering:
Your mileage may vary.
I take no responsibility what you do to your Milestone X2.
I take no responsibility if you use a different phone NOT called the Milestone X2 and end up breaking it.
==================================================================
REFERENCES:
Part 4: Guide adopted from user clcrawl here: http://forum.xda-developers.com/showthread.php?t=1405077
Part 4: How to tell if your phone is rooted: http://www.androidcentral.com/is-my-phone-rooted
Part 5: Guide adopted from Moon Shadow here: http://forum.xda-developers.com/showthread.php?t=1318083
Part 7: DZK's original Thread: http://forum.xda-developers.com/showthread.php?t=1912280
Part 7: Lrs121's modification Thread: http://forum.xda-developers.com/showthread.php?t=1914238
Part 8: sbf_flash on Linux: http://forum.xda-developers.com/showthread.php?t=1321061
==================================================================
CREDITS:
This guide would simply not exist without the help & efforts of the following XDA users:
DragonZKiller (creator of the original CM10 mod for the Droid X2)
Lrs121 (creator of the port of dragonzkiller's port of CM10 for the Milestone X2, hoster of the nTelos sbf file we use)
clcrawl (creator of the original 2.3.6 Root thread for the MX2)
Moon Shadow - NM (creator of the Nandroid thread for the DX2/MX2)
imchairmanm (creator of the sbf_flash thread for the MX2)
Booga Booga (fellow MX2 user and all-around badass resource for creating this guide)
Part 1: Back up the Personal Essentials
If you have Contacts, back them up.
If you have files on your MX2 or SD card, back them up.
As always, before doing ANYTHING with your MX2, back up the important things you need regardless. If you don't back up your personal files, you risk losing them. So back them up. Put the files on a USB drive, CD, external hard drive, whatever. Keep it away from your MX2 where it can't fall in the crossfire of your modding.
Part 2: Factory Reset Time
Before going forward with any custom ROM's, it is absolutely imperative that you have a place to go back to should something go wrong, or if you want to revert back to the stock OS of your MX2. The best way to do this is to have the freshest, cleanest version of the stock OS on your MX2. Doing a factory reset gets you that freshest, cleanest version.
1) Go to your App Drawer, go to "Settings".
2) In Settings, go to "Privacy Settings".
3) Under "Personal Data" at the bottom, select "Factory Data Reset".
4) You'll be prompted with a message explaining all the important stuff about the Factory Data Reset. There are two checkboxes for erasing Internal and SD storage, this is not mandatory as it only wipes apps & media files but it's up to you if you want to do that. When ready, select "Reset Phone".
This process takes a varying amount of time, but eventually it will complete.
5) You're done!
Part 3: Install and Update the Bare Essentials
Now that the MX2's been reset, you'll have the opportunity to add your Google Account, and update apps. But wait! We want as barebones of a Gingerbread install as possible, so just update & install these apps:
1) Google Play Store
2) Stock Apps
3) Superuser (for Part 4)
4) Android Terminal Emulator (for Part 4)
5) You're done!
Part 4: Rooting the Milestone X2 with 2.3.6
Let's review before rooting:
You've backed up the bare essentials
You've Factory Reset your MX2
You've updated the Google Play store & the stock apps, AND installed Superuser AND a Terminal app.
Okay, let's go forward.
1) Install the Motorola Device Manager for Windows, here: http://www.motorola.com/consumers/v...009a0210VgnVCM1000008806b00aRCRD&pubid=987654
2) Restart your computer. Maybe you don't think you need to, but I will. Never hurts to be safe.
3) While your computer reboots, enable USB Debugging on your MX2. Here's how you do it:
Go to your "App Drawer", select "Settings", go to "Applications", select "Development", and select the checkbox for "USB debugging".
4) Plug your MX2 into your computer. At this point it's installing the ADB drivers, essentially allowing your computer to talk to your MX2 over USB.
5) Download this file. http://www.mediafire.com/?z8yb4acyjp08ahf
6) Extract the zip file to a location that is easy to get to, and make sure all the files are extracted to the same folder. For ease of use, I suggest making a folder called "Root" in the C: drive, and putting all the files in that “Root” folder.
7) Put your MX2 into Fastboot Mode. Here's how you do it:
Unplug the MX2 from the computer.
Shut the MX2 off.
Hold down the Volume Down Button while pressing the Power Button.
After the MX2 turns on you should see "Fastboot" at the top of the screen.
Press the Volume Up Button to enter Fastboot mode. Your computer may need to install drivers if this is the first time you entered Fastboot mode, so let this happen BEFORE proceeding.
8) Start a command prompt on your computer.
9) Type the following commands:
cd \<DIRECTORY> where <DIRECTORY> is the folder you created. If you created the Root folder in C:\ it would be cd \root.
moto-fastboot flash preinstall preinstall.img
moto-fastboot reboot
10) Wait for the MX2 to reboot.
11) After it reboots, execute the following commands (in the command prompt you should still have open):
adb shell
/preinstall/su
12) On your MX2 you should see a prompt to Allow or Deny Superuser access, select Allow.
13) Execute the following commands (in the command prompt you should still have open)
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
14) If you haven't yet, install a Terminal app on your MX2. I recommend "Android Terminal Emulator": https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
15) Open the Terminal app.
16) You'll be faced with a text entry prompt in the form of a $ symbol. execute the following command:
su
17) You'll be prompted with SuperUser asking for permission. Select "allow".
18) If the prompt changes from $ to #, it means you're rooted.
19) You're done!
Part 5: Creating the Nandroid/BSR Backup
Now that we're rooted, it's time to make a backup of the MX2 for future recovery. This will come in handy if at any point, you decide to roll back to Gingerbread or if something weird/bad goes wrong.
If you're confused by the term "BSR", it's because the Nandroid backup process on the MX2 hijacks the Charge animation screen when you're charging your MX2 from a wall outlet. Technically it's known as the Boot Strap Recovery, but this is what we do to get a Nandroid backup of our MX2's.
Here's how we make a Nandroid Recovery:
1) Install the BusyBox app from Google Play: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
2) Run the BusyBox app and grant it SuperUser permissions.
3) Download the "Droid X2 Recovery APK" here (yes, it will work for the MX2): http://www.markhm1972.com/MotorolaDroidX2/MOTODX2_Bootstrap_signed.rar
4) Using an archive utility like 7zip, extract the .apk file from the archive.
5) Plug the MX2 into your computer, and enter it in USB Storage Mode from the dropdown.
6) Copy the .apk file to your MX2.
7) Open a File Explorer application (or install one if you don't have it).
8) Navigate to the folder where you copied the .apk file and select it to install it. If you're warned that your phone isn't set to install non-Market applications, it will allow you to go into the Settings, where you can select the checkbox for “Unknown Sources”.
9) If it doesn't launch immediately, you can find it in the App Drawer as an app called "System Recovery".
10) Once System Recovery has been launched, select "Install Recovery".
11) Select "Allow"? when Superuser asks for permission.
12) Wait about 5 seconds to ensure the Recovery Install has completed successfully.
13) Unplug your MX2 from the computer, completely. Make absolutely sure that your MX2 is NOT plugged into a USB port on your computer or in a USB hub.
14) Plug your MX2 into a Wall Charger. Plug the Wall Charger into a nearby electrical outlet.
15) Be absolutely certain you have followed Steps 13 and 14 to the letter. Your MX2 should NOT, for any reason whatsoever in the known universe, be connected in any way/shape/form to your computer right now.
16) I am incredibly serious, make sure you have followed Steps 13 and 14 EXACTLY!
17) Double-check time. If you've followed Steps 13 and 14 like a good owner, you may skip to Step 18. Even so, it doesn't hurt to read the entire checklist again:
DOUBLE CHECK THE FOLLOWING!
Take the Motorola factory USB cable and unplug it from everything. The computer, the wall charging block, the MX2, EVERYTHING!
Plug the micro USB end into the MX2.
Plug the male USB-A end into the wall charging block.
Plug the wall charging block into the wall.
Make sure the MX2 is plugged into the wall charger and plugged into the wall. NOT a USB hub, not a USB port on a computer, Not anything but the wall charger, and the wall charger is plugged into the wall.
18) Select "Recovery Mode". In 3-5 seconds the MX2 will appear to reboot. What it is actually doing is performing the hijack of the Power Off Charge Mode of the MX2. The MX2 actually powers off, but because the BSR hijacks the Charge Animation screen (the battery with the fuel level showing the amount of charge), it will look like it is booting up. In a sense, it is, but it will boot into the Bootstrap Recovery. The battery will continue to charge as well.
If you followed the previous steps correctly, the MX2 will reboot into a screen saying "Droid X2 Recovery GFAN.COM".
19) Press the VOLUME DOWN BUTTON 6 times. This should highlight the option to "Backup & Restore".
20) Tap the power button. This selects the Backup & restore option.
21) Use the VOLUME UP or VOLUME DOWN buttons to select the memory location you would like to store the backup on. If you have not enabled the SD Card flip, or you don’t know what the SD Card flip is, store the backup on the External SD Card. I highly recommend backing up to an external SD Card.
Internal SD Card = the 8GB internal, non-removable memory. (The Internal SD Card has a little over 6.4GB of usable storage space.)
External SD Card = your removable MicroSD card.
22) Once you have highlighted your selection, tap the power button.
23) On the next screen, tap the power button again, since the Backup option is already selected.
24) Now, wait, the backup takes about 10 minutes to complete. Once it is complete, you should be back at the "Droid X2 Recovery GFAN.COM" screen, with a message at the bottom of the screen saying “Backup complete!”
25) Now press the power key since the menu selection is already on Reboot system now.
26) You have successfully made a bootstrap recovery backup of your Milestone X2.
Note: The bootstrap recovery backup does not erase old backups. You must do that yourself from within your preferred file explorer. The backups are located in /mnt/sdcard/clockworkmod/backup/YYYY-MM-DD.HH.mm.ss.
YYYY = the 4 digit year. 2011 for example.
MM = the 2 digit month. Such as 10 for October.
DD = the 2 digit day. Such as 24 for the 24th day of October.
HH = the hour in 24 hour time. Such as 14 for 2PM.
mm = the 2 digit minute of the hour. Such as 34 for 34 minutes
after 2PM, or 2:34PM.
ss = the 2 digit seconds the backup was created. Such as 17 seconds, or 2:34:17PM
Note: DO NOT add SPACES to any of the folder or backup names as this will BREAK your recovery!
27) You're done!
Part 6: Nandroid Restore Procedure
If you find that you need to restore a Nandroid backup, here's how you do it:
1) Make sure the MX2 is plugged into the wall charger and plugged into the wall. NOT a USB hub, not a USB port on a computer, Not anything but the wall charger, and the wall charger is plugged into the wall.
2) Now, power off the MX2. The MX2 will power down, then power back up and boot into the "Droid X2 Recovery GFAN.COM" screen.
3) Once in the recovery menu, press the VOLUME DOWN BUTTON 6 times. This should highlight the option to Backup & Restore.
4) Tap the power button. This choses the Backup & Restore option.
5) Use the VOLUME UP or VOLUME DOWN buttons to select the memory location (internal or external SD Card) you have your backup stored on.
6) Once you have highlighted your selection, tap the power button.
7) On the next screen, press the VOLUME DOWN BUTTON once to highlight the Restore option.
8) Now, tap the power button. This selects the Restore option.
9) Use the VOLUME UP or VOLUME DOWN buttons to select the folder that contains the backup you would like to restore. For example,2011-10-24.12.35.09/. Your folder will have a different name! Please keep this in mind.
10) Tap the power button. This choses the folder you have selected and offers a new menu.
11) Using the VOLUME UP or VOLUME DOWN buttons, select "Yes Restore".
12) Again, tap the power button.
13) Now, wait, the restore takes about 10 minutes to complete. Once it is complete, you should be back at the "Droid X2 Recovery GFAN.COM" screen.
14) Now press the power key since the menu selection is already on Reboot system now.
15) You have successfully restored a bootstrap recovery backup from your MX2.
16) You're done!
Part 7: Custom ROM Installation with DZK's CMOD10 2.9999999 Alpha
Now we delve into the nitty-gritty of getting the most of the MX2, all thanks to the XDA user dragonzkiller, whom has spent countless hours working on a port of CyanogenMod 10 (aka Android 4.1) to work on the Droid & Milestone X2.
BEFORE DOING ANYTHING ELSE, I HIGHLY RECOMMEND COPYING THAT NANDROID BACKUP FROM YOUR MILESTONE X2 TO A LOCATION NOT ON OR NEAR THE MILESTONE X2. Whether this is a USB Drive, CD/DVD, external drive, Dropbox, Google Drive, whatever. Put a copy there. Put copies in different places.
Now that you've copied your backup into one-or-more-but-preferably-more places, it's time to get the most out of our little Milestone X2.
First of all, again I give thanks to DragonzKiller for his work on this port of CyanogenMod 10. Without dragonzkiller, we wouldn't be here.
I must point out that us MX2 users have to use a port of DZK's port of CM10, by user Lrs121. DZK's port of CM10 includes a kernel_check during installation that will NOT work on the MX2, because it requires 2.3.4 in order to flash it. As the MX2 only comes shipped with 2.3.6, the only option is to bypass the kernel_check requirement.
User Lrs121 provides us with a port that bypasses this kernel check, allowing us to run DZK's port on our MX2.
So thank you, Lrs121, for providing us with this port.
Also, as an MX2 user you will HAVE to install the WiFi patch, or your Wifi will not work. Period.
So, here we go:
1) Download the following files:
The JellyBean 4.1.x "gapps" file: http://goo.im/gapps
The "cm10-20130112-unofficial-mx2.zip" file on Lrs121's Google Drive: https://docs.google.com/file/d/0BzuX6WLejxQwakVXcHVSV1R2c3c/edit
The WiFi Patch for the Milestone X2: http://www.mediafire.com/?e7cbyc9lmdj3p7g
2) Place these files on your MX2, preferably on an external SD Card. For convenience sake, I placed them in a folder called “cm10” on my external SD card.
3) Go back to Part 5 of this guide, Step 17. Run the double check. Unplug your MX2 from your computer. The MX2 MUST be plugged into a wall charger and plugged into an outlet.
4) Go to your App Drawer, select "System Recovery" and select "Recovery Mode". The MX2 will reboot into a screen saying "Droid X2 Recovery GFAN.COM".
5) Press the Volume Down button 5 times, highlighting “Install zip from SD Card” (this is your external SD Card). Press the Power button to select it. Press the Volume Down button once to select “choose from sd card”, and press the power button to select it. Navigate to your custom folder and select the cm10 zip file. Press the power button again. You'll be taken to a “Confirm install? THIS CAN NOT BE UNDONE” prompt. Press the Down Volume button 7 times to highlight the “Yes – Install cm10.zip” file, and press the Power button. Wait for it to complete installation. When it's done, it'll declare "Install from sdcard complete".
6) Repeat Step 5, this time installing the "gapps.zip" file. Wait for it to complete installation. When it's done, it'll declare "Install from sdcard complete".
7) Repeat Step 5, this time installing the "MX2_CM9_WIFI.zip" file. Wait for it to complete installation. When it's done, it'll declare "Install from sdcard complete".
8) Press the Down Volume button 5 times to select "Go Back". Press the power button to select it. Now, press the Down Volume button 3 times to select "Wipe DATA/Factory reset", and press the power button. Press the Down Volume button 7 times to select "Yes", and press the power button. Now, press the Down Volume button to select "Wipe CACHE partition". Press the Down Volume button 7 times to select "Yes", and press the power button.
9) You should be back at the main GFAN.com screen at this point, with the selection highlighted on "Reboot system now".
10) Press the power button to reboot your MX2.
11) WAIT. If you followed the steps correctly, the loading screen for CyanogenMod will appear. Soon enough, you'll be able to configure your MX2 and add apps.
12) You're done!
Part 8: Performance gains with CM10 and the MX2
The RAM in the MX2 is a bit limited, so we do have to keep in mind that while Android 4.1.2 gives us performance gains, this is no Nexus 4.
As user Booga Booga can attest to, less apps can mean greater performance. Here's what you can do to get even more out of your MX2.
1) Open the App Drawer, and go to Settings.
2) Go to Developer Options.
3) Scroll down to the "Drawing" heading.
4) Turn "Window Animation Scale" to OFF.
5) Turn "Transition Animation Scale" to OFF.
6) Turn "Animator Duration Scale" to OFF.
7) Reboot your MX2 (just because).
8) You're done!
Part 9: Performing an SBF Restoration on the MX2
If you're utilizing this part of the guide, that means you're either:
itching to go back to Gingerbread
you dun goofed (it's okay, we all do)
testing various builds of roms and wanting to start over
The SBF process is basically a reversal of installing your custom rom, where we revert to a stock version of Android. From there, we can then use a Nandroid backup to restore our MX2 to its former glory before we started tinkering. SBF-ing is a beautiful, metaphorical reset button.
For this guide, we'll be using the "sbf_flash" program and a Linux operating system.
Before going forward, I'm going to make this very obvious.
DO NOT USE RSD LITE UNDER ANY CIRCUMSTANCES WHATSOEVER.
I MEAN IT.
RSD LITE CAN REWRITE THE BASEBAND OF YOUR MX2, PERMANENTLY BRICKING IT FROM WORKING WITH YOUR CARRIER. THE BEST THING THAT CAN COME FROM USING RSD LITE IS THAT YOU'LL HAVE TO TAKE YOUR MX2 TO YOUR CARRIER'S HEADQUARTERS TO BE REFLASHED, WITH A SMALL CHANCE THAT IT WILL ACTUALLY BE RESTORED.
DO NOT MAKE THE SAME MISTAKE I DID.
DO NOT USE RSD LITE UNDER ANY CIRCUMSTANCES WHATSOEVER.
For SBF restoration on the MX2, it is imperative that we use "sbf_flash" for Linux. Yes, this means if you don't have Linux, you'll have to get yourself a copy of Linux. Any distro of Linux will probably work but for this guide I will recommend you use either Wubi or Ubuntu.
1) Acquire this SBF file from user Lrs121: https://docs.google.com/folder/d/0BzuX6WLejxQwWUJXQjBFUG1sZUU/edit?docId=0BzuX6WLejxQwMXlvYUswblVIZzg
2) Download Linux if you haven't already, and run it.
3) Download the sbf_flash program here: http://blog.opticaldelusion.org/
4) Put sbf_flash and the SBF file on your Linux install.
5) Open a terminal in the directory where you have the sbf file and sbf_flash program. Type "chmod +x sbf_flash". This will make the sbf_flash file executable.
6) Turn off your MX2.
7) Hold down the Power Button and the Volume Down button until the MX2 displays "Fastboot" above the normal Motorola start-up screen.
8) Press the Volume Down button until it reads "RSD". Press the Volume Up button to select.
9) Plug your MX2 into the computer using the usb cord. Wait a few seconds to allow your computer to recognize the device.
10) In the terminal (still opened in the same directory as the sbf_flash program and the .sbf file), type "sudo ./sbf_flash nameOfSbfFile.sbf" (obviously you're going to want to change the last part to the actual name of the sbf file you have on your computer) and enter your password when prompted.
11) Allow the program to work. It'll take several minutes and your MX2 will reboot at the end.
12) At this point you'll have reverted back to 2.3.6 Android under nTelos. Refer to Parts 3-6 for re-rooting your MX2, and restoring from the Nandroid backup that you kept safely hidden somewhere (but obviously don't do all of Part 5, no need to backup again).
13) You're done!
GOING FORWARD:
First of all I want to point out that this guide belongs to all of us. You'll find no ego trip here. All I've done is compile everything into one simple resource for us MX2 users to utilize and tested it out to make sure it worked. Everyone credited in the OP are the true trailblazers, as without their hard work I'd have nothing to compile together into a guide in the first place.
Even so, the most important principle of this guide is that it's comprehensive, easy to read, and easy to reference. Any and all additions/modifications must keep this in mind. A clean guide is a happy guide!
Anyway...
Critiques & Reviews
All critiques & reviews of the guide are welcome.
If you find a spelling/grammatical/formatting error, kindly point it out so that I can fix it.
If you would like to add other custom Rom's for the MX2 like CM7 or CM9, let's talk about it!
I've been contemplating this, as many of the parts to the guide require downloading files.
Would anyone else find it beneficial if I compiled these files into timestamped .zip's and uploaded them somewhere based on Parts of the guide? Think files like "Part4.zip" that would include all the files needed for rooting.
If so, where would be a good place to host them?
grizzlayleslay said:
I've been contemplating this, as many of the parts to the guide require downloading files.
Would anyone else find it beneficial if I compiled these files into timestamped .zip's and uploaded them somewhere based on Parts of the guide? Think files like "Part4.zip" that would include all the files needed for rooting.
If so, where would be a good place to host them?
Click to expand...
Click to collapse
Bayfiles, mediafire, Google drive, a private server. Any where really. Also what you said about rsd lite isn't technically true, it isn't that the base band gets overwritten just that there are specific files meant for each different carrier aka prl, eri, ect that get overwritten by rsd lite when. Flashed with the ntelos sbf. Also you may think of adding on the secondary way of rooting involving the scripts I wrote giving people multiple ways to do one thing. Plus I get the bounus of having people try it out and find ways I can possibly improve the process.
Sent from my Nexus 7 using XDA Premium HD app
Lrs121 said:
Bayfiles, mediafire, Google drive, a private server. Any where really. Also what you said about rsd lite isn't technically true, it isn't that the base band gets overwritten just that there are specific files meant for each different carrier aka prl, eri, ect that get overwritten by rsd lite when. Flashed with the ntelos sbf. Also you may think of adding on the secondary way of rooting involving the scripts I wrote giving people multiple ways to do one thing. Plus I get the bounus of having people try it out and find ways I can possibly improve the process.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes the scripts Lrs121 wrote are very, very helpful also as secondary ways of rooting. Worked for me like a charm, Saved time, I understood the process as I went through it and I became more knowledgeable of my device as a more-learned newly rooted owner. helped me appreciate the process more.
Sent from my Milestone X2 using xda premium
Recommended sticky!
I can't make it a sticky, as you don't have your own forum.
Sorry.
Can't you sticky it to this forum?
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
eagleeyetom said:
I can't make it a sticky, as you don't have your own forum.
Sorry.
Click to expand...
Click to collapse
Could you please elaborate on what this means? If it's due to the fact that the guide is for the Milestone X2 and not the Droid X2, please keep in mind that the phones are essentially the same with incredibly minor differences (along with carrier preferences).
The exploits and methods used in this guide are very similar to the Droid X2, but I wrote it for the Milestone X2. When it comes to talking about our phone, mods tell us to post in the Motorola Droid X2 forum, ergo here we are :/
grizzlayleslay said:
Could you please elaborate on what this means? If it's due to the fact that the guide is for the Milestone X2 and not the Droid X2, please keep in mind that the phones are essentially the same with incredibly minor differences (along with carrier preferences).
The exploits and methods used in this guide are very similar to the Droid X2, but I wrote it for the Milestone X2. When it comes to talking about our phone, mods tell us to post in the Motorola Droid X2 forum, ergo here we are :/
Click to expand...
Click to collapse
The Milestone X2 doesn't have it's own dedicated forum. That's the reason for it not being able to be made a sticky (or atleast the way I understand it). Rules are rules. But ya never know unless ya ask
tallyforeman said:
The Milestone X2 doesn't have it's own dedicated forum. That's the reason for it not being able to be made a sticky (or atleast the way I understand it). Rules are rules. But ya never know unless ya ask
Click to expand...
Click to collapse
Thanks, that does explain it. Obviously I disagree with it since
The MX2 doesn't, and will likely never have, its own forum since it's so similar to DX2
MX2 users are directed to the Motorola Droid X2 forum for help
The guide is meant to stop MX2 users from searching everywhere for help
Maybe someone will reconsider and sticky it. Maybe they won't. At least the guide exists to help people, and that's my main concern more than anything.
HOX+ Tutorial for Unlocking, Rooting & installing a custom ROM [BEGINNERS FRIENDLY ]
[SIZE="+2"]-- Step-by-Step Tutorial for Unlocking, Rooting and Installing a Custom Rom for your HTC ONE X+ --[/SIZE]
Here is my beginner friendly manual method for Unlocking, installing an alternative Recovery, Rooting and installing a custom ROM for HTC ONE X+
Why should you do it manually?
At first glance, an all in one tool to do the work for us seems a good idea, but what happens if a step fails? Do you know how to use the right tools to recover? Does your computer have the basics prerequisites installed to allow you to recover your device? In performing this task manually all the basic tools will be installed and in the event that some bugs occurs, at least you will have the certainty of having all the tools in hand to fix it. It is an easy task to obtain if you follow this step-by-step tutorial rigorously. All you need is in this thread, no need to search to find that file or that app, all you need is 30-60 minutes of attentive reading and performing the described procedure. If something goes wrong, read again and simply perform the procedure another time. Remember, you decided to root and customize your phone, no one can be held responsible for your action. If something goes wrong we are here to help, but if you have the ability to read, you should be able to perform this without a swear.
Be aware that the HTC ONE X+ comes in two versions, one version called INTERNATIONAL (ENRC2B) that come WHITOUT the so-called LTE technology.
Then the North American version for AT&T and TELUS (EVITARE_UL) version that comes WITH so-called LTE technology.
LTE is an initialism of Long-Term Evolution. To determine which version your phone is you can simply download an application called CID Getter from the Google Play store available HERE Simply open the program once installed and navigate to the line named [ro.aa.project]:[your version model]
ENRC2B is INTERNATIONAL
EVITARE_UL is AT&T / TELUS
Now that you know which version is your phone lets start with the installation of your SDK tool folder. ADB is a versatile command line tool that lets you communicate with your Android device. This tool is MANDATORY and will serve you very often. Let's do this.
-- Screenshots for the visual ones --
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Unlocking your Bootloader --[/SIZE]
This step is mandatory since there is no other solution yet to unlock the bootloader on the ONE X+. !! PLEASE BE ADVISED TO BACKUP ALL YOUR DATA FROM YOUR PHONE'S USB MEDIA, THIS PROCEDURE WILL TOTALLY AND FULLY WIPE YOUR PHONE. ALSO, BE ADVISED THAT YOUR WARRANTY IS MOSTLY VOID !!
Before doing this you can visualize what is an unlocking procedure HERE. Or you can watch this video HERE
Ready?
To unlock your bootloader go to HTCDev create your account with a valid email address, then select on the right field : All Others Supported Devices and click on Begin Unlock Bootloader (If you followed this tutorial to the letter, your SDK tool/adb command should work flawlessly for this procedure.)
Follow the on screen instructions to get your Token ID.
To submit your Token ID you need to highlight everything between the two spades ♠< < < < <Identifier Token Start> > > > > ....token ID string.... < < < < <Identifier Token End > > > > >♠
Now simply right click and Copy/Paste in the correspondent field to submit.
You will received your unlocking code in your email account (almost instantly, check in your SPAM folder if it take more than 5 minutes) you registered with on HTCDev.
Complete the unlocking procedure and wait for your phone to reboot.
Congrats! The Unlocking process is successful!
____________________________________________
[SIZE="+1"]-- Recovery installation --[/SIZE]
Let's install your new recovery now. !! Be advised that installing CWM Recovery on this device is NOT RECOMMENDED, this recovery is untested, unreliable, unsupported and outdated. The ONLY recovery you should use on your HTC ONE X+ is TWRP Recovery !!
Download this TWRP Recovery for the International version (ENRC2B) : HERE MD5:0a708f4c27d69d2d1505ce7832d4b3be
Download this TWRP Recovery for the AT&T/TELUS version (EVITARE_UL) : HERE MD5:6e24a6686bc4840043a57cb61b63f22c
Once downloaded to simplify the operation rename your file like this : TWRPrecovery.img
Take this TWRPrecovery.img file and Copy/Paste it in the platform-tool of your SDK folder.
TIP : Since your are in the platform-tool folder you can create a batch file to open a command window right from your Desktop.
Do this directly into the platform-tools folder.
Right click on an empty space and select Create New text document
In the new text paste this : c:\windows\system32\cmd.exe
Save it with this name StartADB.bat (important to save it with .bat extension and overwrite the warning)
Now right click again on your new .bat file, and create a shortcut to your Desktop.
Now try to : adb devices your phone via your new Start ADB batch file directly form your Desktop shortcut with your phone plugged on your USB cable.
If you have a serial number as confimation you have done it right!
This a ONE TIME OPERATION TO DO, IT WILL WORK AS LONG AS THE SHORTCUT WILL BE ON YOUR DESKTOP.
Time to plug your phone on your USB cable if it is not already plugged.
Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
Confirmation of the serial.
At the prompt type >adb reboot-bootloader (Enter)
The phone will reboot in bootloader mode.
Make sure the FASTBOOT USB is highlighted.
At the prompt type >fastboot flash recovery TWRPrecovery.img (Enter)
If Success is achieved, type again at the prompt >fastboot erase cache (Enter)
You now have TWRP Recovery installed.
Unplug your USB cable and hit Power button one time.
Select Recovery with your Volume rocker.
Hit Power button one time.
Your phone should reboot in Recovery
Familiarize yourself with it.
Click on BACKUP and perform a full backup of your actual ROM.
Once done REBOOT System.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Time to install the root --[/SIZE]
This is fast to obtain, simply download this SuperSU.zip file and transfer this at the root of your USB media (SD card).
You can now click on your Start SDK batch file from your Desktop to start a command window while your phone is still plug on the USB cable.
Type at the prompt > adb devices (Enter)
Then again at the prompt (if serial confirmation is positive) >adb reboot-bootloader (Enter)
Phone will reboot in Bootloader
Unplugged the USB cable
Hit Power button once
Select Recovery in the menu with the Volume rocker
Hit Power once to reboot in Recovery
Select Install
In the Select Zip to Install menu located your SuperSU.zip file
Click on it and in the new menu simply Swipe to Confirm Flash
Reboot system
You are done rooting your phone.
____________________________________________
[SIZE="+1"]-- Custom ROM installation --[/SIZE]
So far all is good and the above instructions were all successful as we expected now you want that wonderful ROM from that thread, right? This procedure is very simple, but one rule applied here : ALWAYS BACKUP YOUR ACTUAL ROM BEFORE FLASHING ANYTHING! Do transfer it on your computer and keep this file in a safe place follow this path to locate the TWRP folder. At the root of your SD card locate TWRP -> Backups -> your_One X+_serial_number -> You should have one file stamped with date and time. This is your backup you can rename it. Copy/Paste it and put it in a safe place in your computer.
Now the fun part begin!
Once you have selected the ROM for your model version INTERNATIONAL OR AT&T/TELUS, simply download it.
Take also the correspondent boot.img that need to be flashed just before or just after (doesn't really matter) the ROM installation.
Transfer your ROM.zip at the root of your internal storage of the HTC ONE X+ via your USB cable.
While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
Leave your phone plugged to your USB cable
Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
Confirmation of the serial.
At the prompt type >adb reboot-bootloader (Enter)
The phone will reboot in bootloader mode.
Make sure the FASTBOOT USB is highlighted.
At the prompt type >fastboot flash boot insert_your_boot_image_name_here.img (Enter)
If Success is achieved, type again at the prompt >fastboot erase cache (Enter)
You now have a customized boot.img installed.
Unplug your USB cable and hit Power button one time.
Select Recovery with your Volume rocker.
Hit Power button one time.
Your phone should reboot in Recovery
(!! The following instruction are with TWRP Recovery installed !!)
Select Wipe menu, then select Factory reset (swipe), select System (swipe)
Go back to the Install menu and select it.
Locate your ROM.zip and select it.
Swipe to confirm.
Probably Aroma installer will start, simply follow the on-screen instructions and complete the installation.
!! Confirm the Rebooting option ONLY IF YOU FLASHED THE BOOT.IMG BEFORE ROM INSTALLATION !!
Otherwise select the Reboot Bootloader and perform the 4 to 8 steps
Reboot the phone.
-- Screenshots for the visual ones --
Your phone should Reboot with your new ROM, put your phone aside for ~10 minutes to let the new installation performing all it's task. Then you can customize your phone at your desire. Don't forget to reboot your phone when done.
Enjoy!
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Lucky Thirteen said:
you should be able to perform this without a swear.
Click to expand...
Click to collapse
I don't do anything without swearing, but thanks for a great, thorough tutorial. Mods - please sticky this!
sup, i have been using your guide to root and i have been getting trouble getting through the "adb device" part, no matter how many htc drivers i download i end up with the same error, it says devices but mine is never shown. but i guess its all good now as is followed it through the htcdev site...... but anyways would like to know how i can add these roms cause i am really confused about there kernels and stuff would be appreciated if you could explain how it works and whats a good rom to start with.
Hi decoy,
Can you specified at which portion of the tutorial you are stuck at?
i was getting stuck at lets try all this---> AndroidSDK\platform-tools> type this -> adb devices. over here when i type this my device does not show up i have tried updating my drivers several times still no success.
Are you with stock OS on your phone?
Have you tried another USB port? USB 3.0 ports are known to create issues. Also make sure your USB cable is not on a USB hub. If you have Enable USB debugging and you have followed the procedure to the letter, obviously there is a little thing missing.
Please try to describe your computer type and Windows version, where your USB cable is plugged in your computer, is Java installed correctly. Do describe at the most of your knowledge your situation. If it's really not working we can try to arrange a TeamViewer session to have a deeper look at it.
Yo its cool now cause I already rooted it, I guess the problem was the device connection on adb, as it was not being shown even though my computer recognized it, but when I went through the steps on Htcdev it worked cause I was able to unlock and install the recovery..... And I was using it on a usb 3 hub on windows 7. And yes at the moment I am running the stock Rom. I have An other question if you don't mind.... When you install the international recovey how does the back up work and how can you use it?
Sent from my HTC One X+ using xda app-developers app
You simply reboot in recovery and you will see menus, from there it is easy simply pick your choice and swipe to confirm.
Once you will be in Recovery you will see how simple it is, it is very intuitive.
New to android and new to rooting, thanks so much for this guide, unlocked, rooted and custom rom installed. I had no issues with this guide and it was a clean and new experience
Thanks! Successful completion with a few questions
First off, thank you very much for the thorough and easy to follow guide. This was my first attempt at installing a custom ROM on my phone and it went without a hitch.
I do have a few questions for you. First, I decided to install the Elagancia rom. It was a somewhat arbitrary decision, but is there any place that lists the pros and cons about various roms so it can be easier to decide which is right for my phone?
I was hoping to find a 4.2.2 based rom that was pretty much stock without sense, but I couldn't find one for the AT&T HTC One X+, is there one out there that I'm missing?
When I went through the install, it asked me various questions about install options. I didn't know what many of the options did, so I was wondering if there was a guide somewhere about the rom which describes the tweaks I could install. And I also wanted to know if there's a way to go back and change my options without wiping the phone clean and doing a fresh install again.
And again, thanks!
BlueWRXPride said:
First off, thank you very much for the thorough and easy to follow guide. This was my first attempt at installing a custom ROM on my phone and it went without a hitch.
Click to expand...
Click to collapse
Glad if it helped you! Please take the time to rate this thread, it will help to reference it. Take the time also to read this FAQ, you will probably learn a trick or two about your phone.
BlueWRXPride said:
I do have a few questions for you. First, I decided to install the Elagancia rom. It was a somewhat arbitrary decision, but is there any place that lists the pros and cons about various roms so it can be easier to decide which is right for my phone?
Click to expand...
Click to collapse
No, there's not a specific thread for that usage, but in each ROM thread there are Changelog and Screenshots that describing what you should expect from that specific ROM. It's not perfect but generally it's a good... appetizer!
BlueWRXPride said:
I was hoping to find a 4.2.2 based rom that was pretty much stock without sense, but I couldn't find one for the AT&T HTC One X+, is there one out there that I'm missing?
Click to expand...
Click to collapse
Unfortunately, not yet, at least, not that I know of.
BlueWRXPride said:
When I went through the install, it asked me various questions about install options. I didn't know what many of the options did, so I was wondering if there was a guide somewhere about the rom which describes the tweaks I could install. And I also wanted to know if there's a way to go back and change my options without wiping the phone clean and doing a fresh install again.
Click to expand...
Click to collapse
Again, in each Changelog and Add-on section of the intend ROM should have a brief description of tweaks and options available in Aroma Installer, but you can perform a search or ask for a description if you don't find an satisfying answer about a given option.
If you flash over the same ROM, all your settings, apps and data will be preserved, only the system will be updated, so simply flash over to change some options. The vital thing is to have a perfect backup done and saved just in case something goes bad with one flash or update.
BlueWRXPride said:
And again, thanks!
Click to expand...
Click to collapse
You are welcome!
I have a more general question about different roms. First, I'm assuming while it's easy to load a different ROM on the phone, there's no way to put it on there and try it out without wiping your phone clean. That makes the process of trying our different roms to find what you like pretty lengthy. Am I missing anything there?
Second, am I right to assume that most roms that are based of Sense 4+ will more or less look the same, and that the variations from rom to rom will mostly be behind the scenes?
BlueWRXPride said:
I have a more general question about different roms. First, I'm assuming while it's easy to load a different ROM on the phone, there's no way to put it on there and try it out without wiping your phone clean. That makes the process of trying our different roms to find what you like pretty lengthy. Am I missing anything there?
Click to expand...
Click to collapse
Well there is some way to migrate your apps & DATA from one ROM to another with applications like Titanium Backup or My Backup Pro. What I usually do is a full backup of my everyday ROM just before trying another ROM, than I can full wipe (this mean a factory reset and system format) and install the intend ROM I wanna try on my phone without setting everything at the first boot, I play with it and check for options, fluidity, speed, customization,etc. If I find the ROM worth installing my thing, I go on and start the processus to migrate my personal preferences, apps and DATA. This process can take two,three,four days to set the ROM like I want. I simply full backup the unready installed ROM and simply restore my everyday ROM until the other will be completely up and running. Then I suddenly have two perfect ROM to play with only by restoring them at my desire.
BlueWRXPride said:
Second, am I right to assume that most roms that are based of Sense 4+ will more or less look the same, and that the variations from rom to rom will mostly be behind the scenes?
Click to expand...
Click to collapse
Even if the base is the same, the developers do magnificent work to customize, personalize them very differently. Options and tweaks are very different from one dev to another. They all have their personal strength and usually the ROM reflects that talent.
Again, you have to try some at first, then you will see the personality of each ROM. You will learn also if you like a strongly customized ROM or maybe you will prefer a more Vanilla ROM (close as stock as possible) it is all yours to discover.
Lucky Thirteen said:
Well there is some way to migrate your apps & DATA from one ROM to another with applications like Titanium Backup or My Backup Pro. What I usually do is a full backup of my everyday ROM just before trying another ROM, than I can full wipe (this mean a factory reset and system format) and install the intend ROM I wanna try on my phone without setting everything at the first boot, I play with it and check for options, fluidity, speed, customization,etc. If I find the ROM worth installing my thing, I go on and start the processus to migrate my personal preferences, apps and DATA. This process can take two,three,four days to set the ROM like I want. I simply full backup the unready installed ROM and simply restore my everyday ROM until the other will be completely up and running. Then I suddenly have two perfect ROM to play with only by restoring them at my desire.
Click to expand...
Click to collapse
Thanks, that makes sense. Are you able to change between roms without hooking up to the computer and using adb? In your instructions you talk about how you have to flash the boot.ini file that is specifically for the rom you want so is there a way to take care of that without your computer?
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
golmar88 said:
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
Click to expand...
Click to collapse
Start SDK refers to the cmd file you created on your desktop in the -- Creating of script file for a fast access -- section
Mr. Thirteen, do you think you could offer me a little more help? Please refer to the post below.
http://forum.xda-developers.com/showthread.php?t=2226031
golmar88 said:
I am having trouble here:
•While the ROM is transferring on your phone, simply extract the boot.img that match your ROM, rename it for an easier recognition (i.e. Viperboot.img, Eleganciaboot.img, ARHDboot.img, etc) Copy/Paste it in your platform-tool folder (SDK)
•Leave your phone plugged to your USB cable
1.Click on Start SDK, in the command window type at the prompt > adb devices (Enter)
2.Confirmation of the serial.
3.At the prompt type >adb reboot-bootloader (Enter)
Where do I click on start sdk?
Click to expand...
Click to collapse
BlueWRXPride said:
Start SDK refers to the cmd file you created on your desktop in the -- Creating of script file for a fast access -- section
Click to expand...
Click to collapse
Probably you just missed a section like BlueWRXPride told you.
trouble with file Start SDK.bat
Lucky Thirteen said:
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Click to expand...
Click to collapse
Hey lucky thriteen ive been doing everything step by step but im having trouble making the note and copying and pasting c:\windows\system32\cmd.exe once i create the shortcut and open it its nothing like how you show it in the example any idea what it could be?? thanks
---------- Post added at 04:47 PM ---------- Previous post was at 04:41 PM ----------
Lucky Thirteen said:
If you found something hard to understand, let me know, I will do my best to rearrange this tutorial.
Also let me know by PM all the orthographic errors you found, I will fix this ASAP.
If this helped you in anyway please take the time to rate this thread.
Happy flashing!
Click to expand...
Click to collapse
hey lucky thirteen ive been having trouble with the step where you have to create a note in the platform-tools file once i save the note and create the shortcut its not like the example that you post it only shows c:\windows\system32\cmd.exe any idea on what i did wrong?? thanks
How to for n00bs:
Beaups Moonshine S-OFF for the Droid DNA
(Note: This guide will assume that you are complete noob with android and linux, BUT that you are not too dense to google basic things and infer basic differences between PC setups)
YOU WILL NEED:
1 Laptop or Desktop with internet access
1 32bit Linux (Ubuntu or Mint preferred, Mint to be used in this guide) liveUSB or liveCD (liveCD preferred, and what will be covered in this guide)
1 Stock Droid DNA with the 2.06 firmware update (2.04 is reported to work, but more success seems to be had with the updated firmware) WITH AT LEAST 80% BATTERY LIFE
1 Factory HTC/Droid micro-usb (Or any cable you know will work with ADB)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Prepping your computer:
1: Burn a liveCD of your linux distro of choice. Mint is my choice due to having great out of the box compatibility with hardware.
2: Insert liveCD into your PC, turn it on (or reboot), and enter boot menu (typically esc, f8, or f12 pressed during start up) and select “Boot from CD Drive”.
3: Allow liveCD to boot, it may take some time depending on the speed of your hardware. This is good time to prepare your phone for shining.
Prepping your phone:
1: Update to the 2.06 firmware update, if you have not already. If you cannot OTA, you can find guides to flash said firmware update elsewhere on XDA
a: If you are unsure what firmware you are on, go to “Settings”, “About”, and “Software Information” and it will have your firmware listed.
2: Disable any sort of screen lock. Image lock, facelock, pin lock, doesn't matter, it MUST BE DISABLED FOR THIS TO WORK
3: Disable “Fastboot”. “Settings”, “Battery”, UNCHECK “Fastboot”
4: Enable USB Debugging. “Settings”, “Developer Options”, “USB Debugging”
5: Boot into fastboot (turn off phone, reboot holding down POWER button and VOLUME DOWN button simultaneously). Select “Factory reset”. Allow phone to reset and reboot. Go back into settings, repeat sets 2 and 3 if necessary.
Downloading, unpacking, and excecuting moonshine.
1: On your live linux session, that is connected to the internet, go to www.moonshine.io
2: READ EVERYTHING
3: READ EVERYTHING AGAIN
4: Download the .tgz file relevant to your device (for most of us this will be the Verizon DNA file “moonshine_dlx_2.06.605.1.tgz”
5: Go to the folder your .tgz was just downloaded to. This should be your “downloads directory”
6: Right click anywhere in your download directory and select “Open in Terminal”
7: Extract the moonshine .tgz by typing out the following command into terminal “tar -zxf moonshine_<device>_<version>.tgz” For the Verizon DNA this will be “tar -zxf moonshine_dlx_2.06.605.1.tgz”
Your download directory should look like this when done
(Unfortunately, after this, the iPhone I was using to take pictures died, so there are no more pictures after this, but everything is very straightforward)
At this time plug your phone (which has been factory reset, rebooted, and all things listed in the “phone prep section” have been double checked) into your PC via your HTC/Android USB cable.
8: Execute the “Distiller” by typing the following command into terminal “sudo ./distiller”
9: Agree to the onscreen prompts, sit back, relax, DO NOT F**K WITH YOUR PHONE, and let the shine do its magic. This should take five to fifteen minutes and your phone will reboot several times.
10: Enjoy S-OFF and root.
ALL CREDIT GOES TO BEAUPS AND THE MOONSHINE DEV TEAM, this is simply a shoddy step by step guide by a n00b for n00bs to (hopefully) get more comfortable with the idea. This may be reproduced, altered, or edited in anyway as long as credit is given to me (DWC2134) for the original text and pictures and to the DEVS who brought us this awesome utility. In fact, PLEASE edit, improve, and revise this as you see fit for use by new android and linux users. Any changes suggested in this thread will be taken into account and incorporated into the OP.
Toubleshooting:
1: If you are experiencing the "temproot failed" problem, first try a hard reboot, then a factory reset + hard reboot if the reboot alone does not solve the problem.
2: There is some chatter of questionable validity that VZW is trying to push an update to stop SOFF. If you are having trouble, turn off your radios and/or put your phone in airplane mode while attempting moonshine. While most, myself included, doubt the validity of this claim it is better safe then sorry.
Beaups original moonshine thread
Moderators, if this is in the wrong section, or out of line, etc etc, please move, edit, delete, or do as needed.
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
DaPitt84 said:
Does it have to be the 32 bit version? If so I just have to redo my live usb.
sent from my droid DNA with xda premium
Click to expand...
Click to collapse
Yes or the exploit will give an error saying there aren't enough 32 bit libraries. I tried on a 64 bit and got that error. I re did my live cd to use 32 bit ran the exploit and it worked flawlessly.
Sent from my HTC6435LVW using xda premium
Nice howto I did the s-off yesterday worked great. I'm on windows 7 64 bit and installed 32 bit mint.
For people doing this like op said install and use 32 bit just easier and if you're on a 64 bit system doesn't matter 32 bit installs fine.
Sent from my HTC6435LVW using xda premium
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
OK, fingered it out. This may just be of some help to others here. ubuntu-13.04-desktop-i386.iso wouldn't get into "terminal" BUT, linuxmint-15-cinnamon-dvd-32bit.iso does.
Does anyone know if it absolutely necessary to "Factory Reset" DNA with this Mooshine S-OFF method?
dfa7 said:
Very nice "How To' for us Windows PC peeps dwc2134...thank you.
I have a couple of questions if anyone can answer:
1) I haven't seen any other procedure where "Factory Reset" is called upon. Is there a specific reason?
2) I have a burned image of "Ubuntu-13.04-desktop-i386.iso" on USB Stick that runs v/smoothly on my laptop w/Vista Ultimate, but I can't seem to get to terminal screen. I do however see all of the Moonshine flies in download folder when in Ubuntu and "moonshine_dlx_2.06.605.1.tgz"
Please forgive the noobish Q's
Thx in advance
Click to expand...
Click to collapse
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious.
AndroM31 said:
First of all, thank you dwc2134 for providing this guide! I am very new to this scene (Android rooting) and this guide helps out TREMENDOUSLY since I have no knowledge about terminal/command prompts.
However, after re-reading this guide and the instructions at moonshine.io, I have some questions in my head that are preventing me from going further (If anyone here can answer any of my questions, it would be most appreciated!)
1. At the Instructions page on moonshine.io, Step 8 says "Use the matchingStockRUU..", I have no idea what this, is this something I should worry about? I have not modified my Droid DNA in anyway whatsoever ever since I got the device. I only did the 2 OTA updates (2.04 and 2.06) and that's it.
2. In this guide (dwc2134's) on Step 8 where it says to execute the "Distiller", do I type it into the same terminal window I extracted the Moonshine.tgz file?
3. Once the whole process finishes, and I go back to the fastboot screen to see the glorious text that reads: "S-Off", does this mean my phone is rooted and I can install apps like SetCPU off the bat? Or do I have to flash a custom ROM and if so, can anyone recommend a "tried-and-true" ROM?
Once again, if anyone can answer my queries, it would be very helpful. Thank you in advance!
Click to expand...
Click to collapse
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
dwc2134 said:
1: While not ENTIRELY necessary for a successful moonshining, performing the factory reset and hard reboot seems to solve the "temproot failed" problem several users (myself included) have expierenced.
2: Mint is my go to, so it may be slightly different in ubuntu. You can also open terminal by pressing ctrl-alt-T or by going to your applications menu (or the search in the dash) and searching for "Terminal" and then inputting "cd ~/downloads". This will, for lack of better words, open your download directory in terminal so that the commands you input specifically look for, and effect, the files there. You may have to alter the "~/downloads" portion slightly to get you to the correct directory, but looking at the filepath on your computer it should be pretty obvious
Click to expand...
Click to collapse
Thanks for clarrification. I decided to Mint and all is perfect! Ubuntu was a challenge considering I'm not an Apple guy and Linux is greek to me. As for the "Factory Reset", I'll gamble only 'cause I'm configured to my liking and not in mood yet to spend a day getting everything back. Thx again!
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Sent from my HTC6435LVW using xda app-developers app
dwc2134 said:
1: If you have not modified your phone in anyway, and have received the OTAs, then that is irrelevant to you.
2: Yes. Or in another terminal window opened in your "downloads" directory, though opening a second window seems kind of pointless.
3: Moonshine installs superuser to your device, so YES YOU CAN install custom apps like SetCPU right off the bat. I would recommend first installing a custom recovery (I am using CWMs new touch version) and making a nandroid backup before doing anything else, personally. I would also highly recommend installing a custom rom instead of putting in too much time with the stock sense rom. There are so many fantastic roms out for this phone, it would almost be a waste not to. A lot of folks swear by the ViperROM. I'm currently using it and love it.
Click to expand...
Click to collapse
Thank you so much for clearing away my doubts! Once I get the "S-Off" message, I'll look into your suggestions mentioned here.
dwc2134 said:
All's well that ends well. If you end up having the temp root problem, try a hard reboot first and then a factory reset.
Click to expand...
Click to collapse
dwc2134 - thanks for your help, patience and interset with some of us and this project! It does seem easier than revone.
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
HellRayzer said:
Where do I find the Linux file to put on usb? I don't have any blank cd's either...will it work from usb stick?
Click to expand...
Click to collapse
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Error When Trying To Download - 'This file reached max downloads limit"
Followed the guide...booted from USB Ubuntu. No problems. Connected to moonshine.io, clicked next, next, but when I selected the DNA version, I get the error:
"This file reached max downloads limit"
...and no download.
Any ideas? I see another person has posted this in the developers section. Is there a link problem?
Thanks.
dwc2134 said:
You can find the .iso image for any distro you want online. I prefer Linux Mint, though Ubuntu is another crowd favorite. You can make a bootable USB, but I find it easier to make and use liveCD/DVDs. A pack of burnable DVDs is $2.89 at CVS. Google is your friend for the rest of this, it is all VERY self explanatory and most distro sites put step by step instructions right on their website.
http://www.linuxmint.com/download.php
http://www.linuxmint.com/documentation/user-guide/english_15.0.pdf
Click to expand...
Click to collapse
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Max download limit reached.
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
FUBAR'd
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
CharliesTheMan said:
This is spot on. I did my first live cd related to rescuing crucial data on a government computer with a corrupt OS a few weeks ago. I googled "How to make a bootable live cd USB drive" and literally in five minutes I was booted into my Ubuntu distro.
One thing I did learn is with Ubuntu there's a lot of alternative distros on their main site with all the links. After not having the option to boot without making any changes I went to my google-found guide again and realized only ubuntu distros with "desktop" in the filename would give me the live boot option I needed for the task at hand.
One of those small details I overlooked, that was solved by a quick recheck with google.
EXCELLENT GUIDE, I'm really impressed.
Click to expand...
Click to collapse
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
UntamedDarkness said:
I am having the same issue it says that the maxium download limit has been reached.:crying:
I can't donate if I can't download!
Click to expand...
Click to collapse
ejohanss said:
Link looks to be FUBAR'd. Maybe Verizon got pizzzed and did a bit of hacking themselves...
Several people now reporting the issues in multiple threads. I just rechecked...same error.
Out of curiosity, are you using Verizon Mobile Hotspot on your phone to connect to the internet via computer? I am.
Click to expand...
Click to collapse
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Sounds like there is trouble with the download limit counter. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
dwc2134 said:
Yep, google has most any answer you could ever need if you search enough. The only reason I promote liveCDs over liveUSBs is that I think they are a touch easier to make and use. For some reason I have always had a hard time getting liveUSBs to work.
Thank you! I'm really glad it seems to have helped some folks out!
I doubt it is Verizon, most likely a bandwidth issue or hosting service issue. Seems to be common with everyone trying to download moonshine right now. Hopefully beaups will be able to set up some new downloads or someone else will be willing to host the files for him. I knew I should have kept a backup copy of the .tgz
No, when I tether I use one of the free solutions. I got bumped off of unlimited, so I tend to use more wifi then phone data. You NEED an internet connection that is not reliant on your phone for this to work. Moonshine actively connects to the internet during the ./distiller program.
Click to expand...
Click to collapse
I just checked it's a host download limit it's ABSOLUTELY not related to verizon.
I successfully installed Android Revolution 9.3 recently so thought I'd give some details for reference to anyone else it might help as I made a mistake (on purpose of course, just to make things interesting!) and encountered a few road blocks that made things a little tricky. I've not posted here many times and wouldn't claim to be an expert but have quite a bit of experience with Android (Kindle Fire was my first device to which was an uphill struggle all the way) and other tech experience with PC's and some Linux OS.
If you have a device with different specifications please be very careful when it comes to downloading and using software on your device. Doing so with the incorrect software (eg. software for a different device, wrong CID number...) can be disastrous so please be careful - soft-bricking is one thing but a hard-brick is always possible if you don't pay careful attention.
If anything here doesn't make sense or there are processes you don't understand, step back and re-consider before doing anything. You carry out these procedures at your own risk and I accept no liability. Think, think and think again, it's worth taking the time.
First things first, I have an HTC One m7 that I rooted and custom ROM'd almost as soon as I got it, so Root access is a pre-requisite for these procedures and everything described here is done with a Windows operating system.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
If you don't know what “Root Access” is or need help with it, here's a great guide and there is an abundance of other information on XDA for just about any question you might have.
I originally flashed TWRP 2.6.0.1 Custom Recovery and installed Trickdroid 11.0.0, an excellent, customisable ROM that gave me almost no problems apart from APEX Launcher not working, NOVA Launcher works brilliantly though. I haven't found any direct upgrades (please correct me if I'm wrong) but as it stands it's still a very smooth and stable ROM. My other interest was to improve my phone through firmware upgrades, which is a different process from those described here and require S-OFF (Security Off) unless you're using OTA (Over The Air) Updates, which requires a locked bootloader!
Initial Upgrade Problems
I'm quite fastidious when it comes to these things, researching, collecting and organising everything I need before hand so I was pretty annoyed that I missed the note towards the bottom of the Android Revolution HD (ARHD) page where it states that TWRP 2.6.3.3 or newer is required - I can confirm this is indeed the case! I also did a data wipe in TWRP before starting the AROMA installer - not sure this was problematic but it probably didn't help and certainly wasn't necessary so I would advise against doing that.
Whilst the AROMA installer completed apparently successfully (apart from one “error” message - set_perm: some changes failed), it became very clear it was not successful when the phone failed to boot normally and instead simply booted into Recovery every time. I was quite worried I was in dire straits because I didn't have any back up or alternative ROM on the SD card at the time, and was about to discover the joys Windows 8.1 brings to certain processes - more on that later.
So I was faced with a semi-useless phone that allowed me to get into the bootloader and Recovery but not much else, however it's a credit to TeamWin because TWRP continued to function flawlessly, despite my best efforts to screw everything up! No variation or combination of wiping outside of or in AROMA and re-installing ARHD achieved anything new - the partitions weren't mounting or being read correctly (the usb partition in particular “could not be mounted” according to TWRP), so it was clear I was sufficiently over the edge and needed to back up before I did any permanent damage.
Solutions
All of the steps I took may not be absolutely necessary, but because it was quite screwed up I was very keen to wipe the slate and get everything back to a point I was happy everything was fully functional.
The first problem was that fastboot was not working from the bootloader, by which I mean I was unable to use fastboot commands from Windows, and the phone wasn't recognized by the Device Manager, regardless of driver's installed, which I knew were correct - this was a Windows 8.1 quirk, however while the phone was in Recovery I was able to communicate via adb.
So connected to the computer, I opened a command prompt: simplest way to do this is opening the folder where adb is on your computer, which is usually your main hard drive eg. C:, where an adb folder will have been created during the installation of the tools, right-clicking in that folder with the SHIFT key held down, then selecting “Open command window here”:
C:\adb>adb push Trickdroid.zip /sd/
[If you don't follow that method, you simply have to open a standard Command window and navigate to the location of your adb folder eg. C:\>cd adb]
NOTE: the "/sd/" command at the end here is important as it tells adb the location for the file to go on your phone (the internal SD card). I've seen this push command in other tutorials without this part and the operation has failed.
You'll get a few lines in the command prompt window confirming the process starting and completing.
Then I followed the usual installation procedure for a custom ROM through TWRP (Install> Select Trickdroid .zip) - I used this ROM because I had it to hand and knew it worked.
Once the install was completed I had a functional phone again and could start to rebuild the shattered pieces of my pride. As mentioned before, I didn't have a backup on the phone - this was because I lost my original stock backup thanks to a self-destructing hard-drive (avoid Seagate hard drive's), so I started to hunt around. Thanks to the wonderful contributor's of XDA I found some excellent resources, but which you use depends on your preferred approach, and what you want to achieve but here are a few.
MIKE1986's STOCK ROM's
RUU Collection's
Nandroid Collection's
HTC Guru's Reset
Keep in mind - each of these resources have very important and specific processes that go along with each of them, so be very careful when it comes to using them.
Windows 8.1 Quirks
Windows 8.1 (originally) had some difficulty talking to attached Android devices through fastboot, and whilst having the correct HTC drivers is vital, I found a thread relating to a Windows Registry issue, requiring a Windows Update (which you may have already received) and an update to the Windows Registry (which is crucial).
Installing HTC Sync will give you the relevant drivers, but the program itself can interfere with many processes, plus it's a bit rubbish so if you uninstall it (just HTC Sync Manager) from the “Uninstall Programs” application in the Windows Control Panel, you'll just be left with the drivers and no unnecessary bloatware on your computer.
There's a simple download and instructions on how to apply the relevant changes to the Windows Registry which can be found here. If you haven't done anything like this before it can look quite intimidating but rest assured, follow these instructions to the letter and you'll be fine, maybe don't try screwing around with the other registry files though!
Recovery - Refresh and Upgrade
Whilst trying to get the phone to boot (in it's semi-disabled condition) I played around with the backup functions in Recovery, which unsurprisingly didn't work. I also deleted some of the folders within the TWRP “Backups” folder, thinking they might be confusing or causing some conflict.
So, to start afresh, I flashed a stock recovery, which can be found here.
Your phone needs to be in fastboot mode and attached to your computer - power off, then hold the volume down button and power button until the bootloader opens. Your recovery image needs to be in the adb folder, preferably named “recovery.img”. Open the Command Prompt for adb (right click in the adb folder whilst holding the SHIFT key) and flash the .img file over to the phone.
C:\adb>fastboot flash recovery recovery.img
Again you'll see a few lines in the command prompt window confirming the process starting and completing, once it's done shutdown and reboot the phone.
Of course the stock recovery isn't much use in terms functionality, and this process effects the ROM, essentially re-setting it - your SD will be fine but if you had eg. text messages, they'll be deleted so back anything like that up before doing this.
I shut down and re-booted once more just to be sure everything was ok, and then flashed the custom recovery in the same way as the stock, but now was the time to jump to a more up to date TWRP (or recovery of your choice) - I went with 3.0.0 in this case. Delete the stock recovery from the adb folder, then save the new custom recovery .img file (again re-naming it to “recovery.img”) in the same folder before fastboot flashing with the command prompt window:
C:\adb>fastboot flash recovery recovery.img
Sweet, now we've got a lovely new TWRP that looks a little different than the old version but with the same wonderful UI and functionality, and a few extras. The first time I booted into Recovery it asked me if I would like TWRP to be able to write onto the phone, or remain as “read only”. Whilst you might want to do this, there's no real reason and it kind of defeats the purpose of the recovery, plus you're not going to be able to do a backup or install files so just agree to that and you're good to go.
TWRP Information & Resources
System/ROM
Now running smoothly I was ready to upgrade, but to ensure there were no unpleasant ghosts in the system I went back to a stock ROM first. There's a variety of options as mentioned earlier, including any backup you may have saved yourself, but I went with a stock ROM provided by mike1986 this time which can be found here, whose incredible work and contributions can't be underestimated.
[NOTE: This *STOCK* ROM is NOT the same as the “out of the box” system my phone originally came with, which was 4.1.2 “Jellybean”, HTC Sense 5.0, however it served the purpose of wiping the phone slate clean to a stock system.]
I used the deodexed 6.09.401.12 - basically the difference between odexed and deodexed is the .apk structure - it's most specifically related to modifications and avoiding conflicts in the ROM. Here's a thread if you want to learn a bit more about it.
So just like any other ROM, copy the .zip file onto the SD card - simplest way to do this is having your phone connected to your computer, open up the browser window and navigate to your SD card, selecting a suitable location, just make sure you know where it is! (You can push it over via adb but it's really not necessary.) Then boot into Recovery, click Install, navigate to the .zip file location and select One_6.09.401.12_deodexed.zip (or whichever one you're using), then swipe to install.
The AROMA installer will kick in so just follow the on-screen instructions, reading each step carefully and soon you'll have the ROM installed with the usual Root access.
Don't forget the first boot after an install like this takes some time - that's completely normal, including an “Optimizing Apps” window before you get to the home screen so just be patient.
If you want to stop here then obviously that's your choice, however if you wanted to get/use OTA updates you'd need to follow some other steps to be totally stock, including locking your Bootloader, and there's a wealth of information here if that's your aim.
Custom ROM
Onto the Custom ROM of your choice - I recommend you do some research and check out reviews to find what you like the look of, but I've gone with mike1986's Android Revolution HD this time round. Download the ROM .zip and just like before, move it to your phone's SD card (no point in keeping the Stock ROM on the phone as well so delete that first to free up space, though you might want to keep it on just in case until the upgrade has completed successfully).
Reboot into Recovery via the bootloader, click Install and navigate to the .zip file, select Android_Revolution_HD-One_93.0_ef29f7.zip and swipe to install, carefully following the steps in AROMA and installing according to your preferences.
Once again after completion, reboot and be patient whilst the first boot runs its course and you're all set!
Don't forget you'll need to install the Xposed Framework to take full advantage of the Sense Toolbox within ARHD, without it simply won't work fully - it will work at a basic level but you'll get a warning/notification that you don't have full functionality. You can find lots of detailed information about this here - read it carefully because again, the correct software for your phone is very important - basically you need the latest installer, which is an .apk, and the relevant .zip files for your device.
For my phone (HTC One m7 - Quad-core 1.7 Ghz Snapdragon (Krait) 600 CPU, ARMv7 Soc (2Gb RAM) ARM CPU), one of the packages wouldn't install, claiming it wasn't correct for my device. Why exactly I'm not sure (because I absolutely, positively got the right packages!) so I'll update this when I know more, however the Xposed Framework software has worked fine since then, I'm not getting any error messages, it's all up to date and working fine.
That's it! Explore you're new ROM and enjoy. I hope this is helpful, if you've got any questions feel free to ask and I'll do my best to help. Much credit and thanks go to the people I've looked to for advice, and who have done incredible work compiling, modding and hosting the files used for these processes.
Thank and donate whatever you can to them so they can continue the sterling work.
Particular thanks to:
Mike1986
crushalot
matt95
sToRm1nG
… and anyone else in the XDA-Developers community I haven't named specifically but have been exceptionally helpful in sharing their knowledge and resources.