Develop Bugs

[GUIDE] Turkeys' Ultimate Guide to Root Desire v42.1.1 "Misc Errors are History"

[GUIDE] Turkeys' Ultimate Guide to Root Desire v42.1.1 "Misc Errors are History"
Turkeys' ULTIMATE Guide to Rooting v42.1.1
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot (Adding Now)
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me you can do so below
GBP
EUR
USD

Root Guide - Pt. 1 - Info
So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...

Root Guide - Pt. 2 - UnrEVOked
So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...

Root Guide - Pt. 3 - Flashing Your First ROM
Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF

Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!

Apps2SD
A2SD
First, we need to get S-OFF to flash Amon-RA Recovery. You can use clockworkmod/ROM Manager to do this although it is very error prone so don't!
Now, I'll be honest, I really cba to write and provide support for people S-OFFing, so I'll link to someone elses instead.
But you can still post on this thread with questions, post there if the S-OFF doesn't work.
S Me OFF!
Download the AmonRA recovery image here before continuing. (Make sure you save it in the adb folder inside. the other stuff file below)
1) Make sure USB Debugging is on and make sure you downloaded the 'Other Stuff' file in post 2 and have extracted it to somewhere you can get to easily. (I always reccommend C:\root)
Next we need to flash Amon RA recovery. We will do this via the command line using fastboot. Your phone needs to be in booted Android mode for this next step.
2) Open a command prompt (Start > Run > cmd) and type the following: (you will need to replace some bits if you extracted the other stuff file to a different location.
Code:
cd \
cd root
cd adb
adb-windows reboot bootloader *let your phone reboot into fastboot before continuing*
fastboot-windows flash recovery what-you-called-amonra-recovery.img
fastboot-windows reboot
Next we are going to reboot into your newly flashed recovery image and repartition your SD card. This will format your SD card so please BACKUP your SD Card before continuing.
3) Open the Quick Boot app you downloaded in Pt. 4 and tap Recovery to reboot into recovery mode. Once you are in Recovery scroll down to and select Partition SD Card then select Partition SD. Now use the TRACKBALL to scroll up and down until you get the partition size you want and press trackball to continue. Now select 0 swap unless your ROM supports it and you know what it is. Then set the rest of the SD Card to FAT32 and press the TRACKBALL followed by the HOME BUTTON to confirm and start partitioning!
Note: If you want to use an ext3 or ext4 partition and your ROM supports it, select the SD:ext2 to ext3 option to upgrade to ext3 and the other one to upgrade to ext4. However, I would advise against doing this as you will wear out your SD Card faster.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.

Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Bravo. Now, you need to recall what version of Android you were on before you rooted. If you were on 2.1, you need to choose one of the RUUs which say 1.21.xxx.x. If you were on FroYo, you need to choose one that says 2.xx.xxx.x. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.

Fixing the annoying unrEVOked misc errors
Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse

Reserved for when I think of some awesome idea I just have to put here. #2

just say WOW! really Great!

Please don't forget radio info.

What a super great guide I really appreciate it, I think we all will

Nice one turkey, I just want to hug you so hard!
{
"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"
}

gascanieto said:
Please don't forget radio info.
Click to expand...
Click to collapse
Whoops forgot that, I'll add it in now
EDIT: Added quickly from an old guide, rewrite soon

Brilliant post
Really Really useful for nooblits

Great, easy guide. wish I had this when I rooted my desire ages ago.

There needs to be more stuff written in plain english - like this guide.
Very easy to read. I'm sure it will find its way into the sticky threads soon enough!
V42 beta....hehe
Anyway, good work! I love it.
Josh.

Can I make a suggestion and ask for a quick guide on updating your recovery image? I have clockwork recovery mod from the first unrevoked tool and thought ROM Manager updated it (it says I am using 2.5.0.7) however whenever I flash a ROM it always says I am on 2.5.0.1. Not sure on how to update it and if I should rather apply the rule if it aint broke dont fix it .

Real nice, one flaw: you use volume keys to navigate in Clockwork (which is default for unrevoked) and trackball in amonra IIRC
Sent from my HDfied HTC Desire

Actually, Clockwork uses the trackball too
Sent from my HTC Desire using XDA App

[Q] need help rooting dinc2 please

so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[

simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder

In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.

im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes

Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk

nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally

drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.

how did you get it too work???

simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....

the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!

yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod

ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2

I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.

nothing is working out for me this is not fun

same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.

yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that

[Guide] -The Ultimate Stock to Custom ROM Awesomeness thread - Noob friendly

Hi there and Welcome to my Ultimate Stock to Custom ROM Awesomeness Thread!
-----
There are still many of people out there who are thinking about Unlocking their Bootloaders, Rooting and installing a custom ROM onto their HTC One X.
I recently did so myself and although I've been a member on XDA for a while now and I rooted my old HTC Sensation I found the process to vary with my HOX.
Now there are many amazing Guides and "How-To's" already out there on XDA but I thought that I'd compile a lot of what's already in those threads and turn all of the yummyness that's already out there on XDA and write this from a first timers perspective.
Disclaimer:- Please note that I'm no expert when it comes to this stuff and I'm not amazing at trouble shooting, if you follow this guide it should turn out fine but if not then this is no fault of my own, you do all of this at your own risk! As I say, it should be fine and you should get through this guide fine. There may be better ways of doing what I'm showing you in this guide but this is how I did it and it worked out okay for me. If you know of a better way the please feel free to state so in the following thread.
-NOTE-
THIS GUIDE IS FOR ICS ROMS ONLY, NOT JB ROMS.
So after that disclaimer relax, read, re-read and take your time and hopefully by the end of this guide you'll have a Custom Rom running on your HOX and without too much panicking and worrying. It's a bit wordy and a bit lengthy but it's an in depth guide.
BEFORE WE START! Go to your HTC One X, Settings, Developer Options and make sure that you've got USB debugging checked! I also always have Fast boot checked in the Power options as well, it's not really important for this guide but I like to know that when I turn my HTC One X off that it is truly off!
Also if you wish you can pop into security and check on 'Allow installation of non-Market apps in Unknown Sources. Again, not really important for this guide but always good to have checked!
---NOTE---
In this guide I talk about using ARHD 9.2, this is because it's the latest version that's been released at the time of writing. Naturally ARHD will be updated but the guide will still be okay to follow.
Lets Get Started!
---
Installing HTC Sync and the Android SDK onto your PC:-
Before we start anything I personally think that it's a good idea to get these two steps out of the way as we're going to need to use these tools a bit later on.
HTC Sync
To install HTC Sync the best way to do this is to follow this LINK and click on the Download link on the right hand side. Follow the Set-Up wizard and get HTC Sync installed onto your PC. Now I'm sure that I don't have to talk you through this step so we'll leave this part now and move onto getting the Android SDK.
Thanks to EddyOS for this recommendation:
EddyOS said:
Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download
Click to expand...
Click to collapse
So feel free to download either HTC Sync (It's the only version I've personally used), or download HTC Sync Manager as it's designed specifically for the One Series.
Android SDK
Now that you've gotten HTC Sync set-up onto your machine we'll start with the Android SDK, you can find the installation files here: Android SDK For Windows, Click on the "Download the SDK For Windows link.". Let it download the Run the file.
Now to make life a bit easier for us later, when you get to the menu for choosing the Destination of the program we'll alter this for ease of use later. When I'm in set-up it automatically sets the location to
C:\Documents and Settings\James\Local Settings\Application Data\Android\android-sdk
Click to expand...
Click to collapse
We'll change this to:
C:\Android\android-sdk
Click to expand...
Click to collapse
Continue with the install.
Once installed the SDK 'should' open itself, if not then open it from the start menu.
You'll be shown a screen that has a load of options on it and a button at the bottom that says 'Install [X] Packages', Make sure that you have Android SDK and Android SDK Platform Tools checked (See Image).
{
"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"
}
The program will automatically select numerous other options, it's fine to leave these checked. the installation may take some time depending on your PC etc...
Now that's all finished we can move onto something a little more productive!
Backing Up Your Data:-
When I went to Unlock My Bootloader I read that I'd loose my data and I wasn't too happy about this, I came across this thread '[GUIDE] Full Phone Backup without Unlock or Root', which was a life saver, I'll talk you through some of it just so that we can get a backup made but if you want more concise instructions then make the jump to the thread and have a look!
Now, to backup!
Open your Command Prompt, for those of you who don't know how to do this it's Start > Run... > CMD > Okay. Now that you've got your Command Prompt open we'll need to find adb.exe, which should be at this location
C:\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
as this is where we chose the Android SDK to be located when we installed it earlier!
So to find this in the command prompt type in
cd \Android\android-sdk\platform-tools
Click to expand...
Click to collapse
This will take you to that location. (See Image)
Now that we're in the platform-tools part of your PC in command prompt, it's the perfect time to plug in your HOX via USB to your PC, just choose 'Charge Only' for now.
Now back in CMD (command prompt) enter these values:
adb backup -apk -shared -all -f C:\backup\backup20111230.ab
Click to expand...
Click to collapse
Please note that this will create a folder in your C:\ called 'backup', this is where your backup will exist, also please not that you can call your backup whatever you like, it doesn't have to be 'backup20111230.ab' but I prefer to choose the days date, so mine today would be 'backup20082012.ab', 20th August 2012. Once you've typed this into CMD you'll be prompted to unlock your phones screen and continue backup (See Image)
So unlock your phone screen, choose a password (write this down somewhere as you'll need to to replace the backup onto your phone after we've put a custom ROM onto it) let it start to backup!
Now there is a common issue with the backup's freezing at
com.android.sharedstoragebackup
Click to expand...
Click to collapse
If this is the case for you, just unplug the phone, exit out of CMD, plug the phone back in, get back into cd \Android\android-sdk\platform-tools in the CMD and this time alter the backup command so that it reads:
adb backup -apk -noshared -all -f C:\backup\backup20111230.ab
Click to expand...
Click to collapse
All you've done now is change -shared to -noshared, let the backup continue, hopefully it'll complete!
Now that you've got your backup all safely stowed away on your PC it's time to get down to business! Unlocking your Bootloader!
---
Unlock the Bootloader:-
Did you install HTC Sync at the start? As now you're going to need it!
Navigate your web browser to www.htcdev.com/bootloader and click register at the top, complete the registration process, making sure that you use an email address that you have access to.
Once registered make your way back to www.htcdev.com/bootloader and sign-in.
Once signed-in at the supported devices drop down select 'All Other Supported Models' and click on Begin Unlock Bootloader.
Now before we move onto anything else we're going to want the Fastboot Files, which Cursed4Eva is kindly hosting here: Fastboot Files
Once downloaded, on your PC go to the folder C:\Android and inside that folder create a new folder called fastboot, so you'll have
C:\Android\fastboot
Click to expand...
Click to collapse
Now the fastboot files that I linked to earlier come in a Zip file, unzip it to C:\Android\fastboot, this makes it easier to find it in CMD.
Now back @ htcdev, you've registered and signed in? Good, you've chosen All Other Supported Models and clicked Begin Unlock Bootloader, it'll ask you if you wish to continue, click yes, then the Legal Terms will pop up, just click that you acknowledge both terms and continue with 'Proceed to Unlock Instructions'.
Now click through the instructions until Step 8, ignore everything else.
Now turn off your HOX, now we'll turn on the HOX into the Bootloader, so press and hold down the Volume Down Button and whilst pressing the Power Button, continue to hold this down, the phone may vibrate and bleep a bit but continue to hold it down until you are greeted with a screen that has some options on it, Fastboot, Recovery etc... Now the touch screen wont work so we navigate using the volume buttons & Power Button, press down on the Power Button wile you have Fastboot selected, you'll enter Fastboot Mode with the options HBoot, Reboot, Reboot Bootloader & Power Down. You'll see above these options it'll have Fastboot written and highlighted in Red, leave the phone as it is, just plug it into the PC via USB and that highlighted 'Fastboot' will become 'Fastboot USB'.
Now open CMD, enter
cd \Android\fastboot
Click to expand...
Click to collapse
This will access the fastboot folder in your C:
Now in CMD once you're in the fastboot folder enter this command:
fastboot oem get_identifier_token
Click to expand...
Click to collapse
Now it'll bring up the Identifier Token. (see Image)
Now using your mouse, right click in CMD where it says
<<<< Identifier Token Start >>>>
Click to expand...
Click to collapse
Highlight it to where it says
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
Now on your keyboard, once you've highlighted the Identifier Token press 'Ctrl + C' to copy the Identifier Token.
Now back at the HTC Dev website, scroll down to after Step 10, where it says My Device Identifier Token:, Click in that field and either press Ctrl + V or right click and paste your Identifier Token into that field.
Now Click Submit.
You'll now be taken to a page where you'll be informed to check your emails.
Open up your emails and you'll have an email from HTC and in that email will be an attachment, this will be called Unlock_code.bin.
Download it and place it in your fastboot folder at C:\Android\fastboot.
There will also be a link in the email which will say like "Continue with Bootloader Unlock Procedure" or something like that, Click it.
Back in CMD, you should still be at C:\Android\fastboot, now type in
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Please note the Capital 'U' in Unlock_token.bin, press Enter.
Now look back to your HTC One X screen, it'll have two options on it.
1. YES Unlock Bootloader
2. NO Do not Unlock Bootloader
Select Yes with the volume keys and press the power button, the phone will turn itself off and reboot,
CONGRATULATIONS YOU'VE UNLOCKED YOUR BOOTLOADER!
---
Installing a Custom Recovery (Clockwork Mod) and Superuser Access, ROOTING YOUR HTC ONE X:-
Now that we've unlocked the bootloader we're really close to finishing the whole procedure and getting a custom ROM onto our HTC One seX!
Please note that there will be no images or screenshots from here on as a majority of this is all done on the phone handset bar the flashing of the recovery.img onto the handset.
Follow these links:
SuperSU for Super User Access, download the CWM installable ZIP: http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip courtesy of ChainFire, Please donate to this guy so he can buy some beers
Clockworkmod Touch Recovery Thread: Download the latest Official Recovery
Again, please donate to broncogr and buy this guy a beer or at least hit Thanks.
So now that you've downloaded both files;
The CWM-SuperSU-v0.94.Zip file and the recovery-clockwork-touch-5.8.4.0-endeavoru.img
Right click on the recovery-clockwork-touch-5.8.4.0-endeavoru.img file and rename it to recovery.img, this makes it easier to work with later.
Connect your HTC One X to your USB cable and then to the PC, choose Disk Drive, next, copy and paste the CWM-SuperSU-v0.94.Zip file onto the root of the SD card for your HOX. Once that's on there, change the phones USB connection to charge only.
Open CMD, now get back into the fastboot folder in CMD, do you remember how to do this? It's C:\Android\fastboot then press Enter.
Now start the phone back up into the Bootloader, press and hold Vol Down and press Power Button, once in the Bootloader, once again, select Fastboot and then leave the phone as it is, running in Fastboot USB.
Back to CMD, type in this command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Press Enter. You've just flashed a custom recovery onto your HOX, Once that's finished, type 'exit' into CMD to close the CMD panel.
Back on your HTC One X, using the Volume buttons navigate down to Power Down, once the phone is off, with it still connected to the PC via USB, start it up again into the Bootloader (Vol Down + Power). Once in the Bootloader select Recovery, hit Power. You'll then load up into Clockwork Mod Recovery.
Now you can use either the touch screen or the volume buttons. Navigate to 'Install ZIP from SD Card', hit the Power Button, next select 'Choose ZIP from SD Card'. Now you'll need to scroll right to the bottom of the list to the CWM-SuperSU-v0.94.Zip you placed on the phone earlier.
Click it and it'll ask you if you want to install, select yes install, and let it do it's thing, Then select 'Go Back', Reboot System Now.
Once the phone has shut itself down and restarted, go to the Play Store / Google Market and Install Titanium Backup: Titanium Backup Root. Let it install, once that's finished, start the App on your HTC One X and it'll ask you for Super User Access, grant/accept it.
With the older versions of TiBu (Titanium Backup) You had to go to the problems section and install BusyBox but i believe that it does it automatically now (At least it did for me) So when you start up TiBu You'll see this on screen:
Root Access: OK
Click to expand...
Click to collapse
CONGRATULATIONS YOU'VE ROOTED YOUR HTC ONE X!
---
Making a Nandroid Backup:-
Now that you're rooted and have a custom recovery we'll make a Nandroid Backup, this is EXTREMELY IMPORTANT as it'll act as your fail safe if flashing the custom ROM goes 'Tits-Up'.
Nandroid:To backup the current running rom.
Click to expand...
Click to collapse
When you make a Nandroid backup you are essentially making a carbon copy of how the phone is at that point in time. It doesn't matter if it's a stock rom or a custom rom.
If you are flashing a custom rom onto a phone and it goes wrong or has bugs in it or you don't like it you can restore the Nandroid backup and turn back the clock so that the phone will be as it was when you made the Nandroid backup, as you can see, it's important to do this.
To make a Nandroid backup, turn off your handset, power up into the bootloader, go to recovery, once in recovery there will be the option Backup/Restore, choose backup, let the phone perform the backup - this may take a little time. Once it's finished, just choose restart/reboot phone.
There you have it your very first Nandroid backup!
If it makes you feel a little easier, before flashing a custom rom onto your phone you can transfer the Nandroid backup onto a PC.
Just connect your handset to a PC via USB cable, Disk Drive, then once you can get into the phone on the PC, enter the Clockworkmod folder and make a copy onto the PC of the 'backup' folder.
To restore a Nandroid backup, providing you have the Clockworkmod\backup folder on your phones SD card, enter recovery, and in the option Backup/Restore, just choose 'restore' and off it goes, you've restored the Nandroid backup.
Many people make Nandroid backups before the flash a custom rom onto their phone, even seasoned veterans do this as it's your one fail safe against a disastrous occurrence... messing your HOX up! Some people make them Monthly, Weekly and even a few make them daily!
-NB-
BEFORE PERFORMING A NANDROID RESTORE, PLEASE PLEASE PLEASE READ THIS POST!!!
http://forum.xda-developers.com/showpost.php?p=32084184&postcount=138
Now onto flashing ARHD!!!
---
Installing Android Revolution HD 9.2:-
We're so close to having a Custom ROM on our HTC One X, not far to go now!
Make sure you have at least 35% Battery when you do this! Preferably more, I cannot stress this enough!!!
Pop on over to Mike1986's ARHD Thread here: ARHD Thread Donate to Mike1986 if you like or Thank him as his work is brilliant!
Scroll down to the DOWNLOADS section and download Android Revolution 9.2, boot.img for 9.0.x and Super Wipe.
Next connect your phone to your PC and select Disk Drive, now copy the SuperWipe file and the ARHD 9.2 ROM onto your phones SD card at Root, no need to go any deeper.
Next take the boot.img for 9.0.x file (it's named Flash_boot_9.0.x.rar) and copy it to C:\Android, once the file is there, right click and Extract Here.
Now boot your HOX up into the Bootloader (Vol Down + Power) and then go into fastboot, connect your HOX to the PC to get Fastboot USB.
Now that you're connected, go back to C:\Android and click on the file called
install-boot-windows
Click to expand...
Click to collapse
In the CMD panel it'll ask you to hit any key, so just press Spacebar or whatever, it'll do it's thing, it might ask you to press any key again or it'll just finish.
Back over to your handset, Press the power button to get back into HBoot and then select Recovery.
Once Clockworkmod Touch Recovery has started once again choose the option 'Install ZIP from SD Card', then 'Choose ZIP from SD Card', now scroll down to the Superwipe ZIP, make sure you choose this and not the ARHD ROM, Anyway, choose the Superwipe script and select Yes when it asks you if you want to Wipe.
Once it's performed the wipe, select Go Back and now repeat 'Install ZIP from SD Card', then 'Choose ZIP from SD Card', this time select the ARHD ROM file.
The setup for ARHD will begin, on your handset select next, then select Agree, then next again.
You'll come across a screen that has two check boxes on it, one will say
Wipe Data Partition
Click to expand...
Click to collapse
Select this.
Tweeks: You'll be presented with a screen of Tweeks that can be included into the flashing of the ROM, I personally choose
Improve EXT4 Performance, Force GPU2, Improve Multitasking, Experimental Tweeks and the last option, I can't remember what it is
Click to expand...
Click to collapse
Click Install, It'll finish, then Reboot.
Now don't panic, the first reboot can take up to 5 Minutes to complete, this is why it's imperative to have over 35% battery life as a shut down now can be disastrous!
Once it's rebooted you just have to setup your phone like you would do if it was fresh from the box.
Restore data backup:-
Now all that's left is to restore your data that you backed up at the beginning!
Open CMD, enter
cd \Android\android-sdk\platform-tools
Click to expand...
Click to collapse
Now do you remember where you saved your backup? Good!
Now in CMD enter the location and file name of your backup
adb restore C:\backup\backup20082012.ab
Click to expand...
Click to collapse
Remember mine was todays date! On your HOX screen you'll be asked to enter your password that you chose when making the backup, it'll do it's thing Et Voila!
You've restored all your lovely data, remember, the stuff you had on the phone when it was stock? Nice!
CONGRATULATIONS!!!
YOU'VE MADE A DATA BACKUP, UNLOCKED YOUR BOOTLOADER, ROOTED & INSTALLED A CUSTOM ROM AND REINSTALLED YOUR DATA ONTO YOUR HTC ONE X!!!
I hope that you find this guide useful and that you've managed to fumble your way through it without too much trouble or many hiccups.
If you have any questions or hit any problems please feel free to ask, I'll try to help you if I can.
If this guide has helped you at all then please hit Thanks
GLHF!!!
The-Last-Hylian
---DISCLAIMER---
If I've said anything wrong or given out the wrong info, then please PM me and I'll make amendments.
Also, instead of donating to me or whatever, instead I'd just like to place a link to my site here: Tuffphones - The home of tough, rugged and waterproof mobile phones. (If I'm not allowed this link here please PM me and I'll remove it)

Reserved

nicely written. once my hox is replaced and finally working, i think i shall have to refer back to this

Would it be worth sticky-ing this thread to the top of General?

Great thread mate. I sincerely believe that it deserves to be stickies for everyone to see, because you did a very thorough and detailed Jacob that will surely be helpful to newcomers. You deserve your own praise too. I'm one of those holding back on unlocking my HOX since I'm waiting for an unofficial unlock method and contemplating if it's even worth holding on a HTC device and not just going back to my iPhone which was easier to hack and modify (imo).
Sent from my HTC One X using Tapatalk 2

Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download

Yes
Well done on this! Super site

Check back to this thread soon!
I'm going to write into my reserved #2 post about how to get the best out of your HOX for gaming!

EddyOS said:
Better to recommend HTC Sync Manager as that's for the One Series phones...
http://www.htc.com/www/help/htc-one-x/#download
Click to expand...
Click to collapse
I mainly choose HTC Sync as it's the only one I've used and I thought I'd only write about what I know so that way I know it's reasonably accurate.
Thanks for the tip + link EddyOS, I'll add that into the OP as an alternative.

Good one! Explained everything required. N00b friendly xD

death__machine said:
Good one! Explained everything required. N00b friendly xD
Click to expand...
Click to collapse
Thanks that was what I was aiming for
I figure that even if something is really complicated to do (which granted not much of what I wrote about is), if you write the instructions with proper and correct grammatical English then people will understand it a lot better.

Hi the last hylians, i currently new with hox, mine previous was sgs. It looks difficult to install custom rom with hox rather than sgs. First i want to know, mine software is 1.29.707.11, can i install all the custom rom or just a particular one with the same software. Thanks
Sent from my HTC One X using xda app-developers app

neoandresk said:
Hi the last hylians, i currently new with hox, mine previous was sgs. It looks difficult to install custom rom with hox rather than sgs. First i want to know, mine software is 1.29.707.11, can i install all the custom rom or just a particular one with the same software. Thanks
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi there,
As long as you have a decent grasp of the English language and can follow instructions reasonably well then installing a custom ROM isn't too difficult, I'm sure you could muddle through
.707 is that Malaysia/Indonesia?
I believe that you could install a custom ROM that would be x.xx.401.xx as you'd be unlocking the bootloader so theoretically can install any OS on the phone that you like, the region for the OTA therefore wouldn't need apply as you wouldn't get FOTA's afterwards anyway.
It might be worth asking on the Android Revolution HD thread and posting a link to this thread so that way you can get a 2nd opinion.
Afaik you'd be fine however.
T-L-H

This isn't knocking the guide, as it's good, BUT everything you have here is already available online if people were bothered to search for it - especially the bootloader unlocking as HTC have a detailed guide on their own website
You should also highlight the importance of downloading the RUU for your phone before unlocking. If it's not available add a note to proceed with caution
Still, good work

EddyOS said:
This isn't knocking the guide, as it's good, BUT everything you have here is already available online if people were bothered to search for it - especially the bootloader unlocking as HTC have a detailed guide on their own website
You should also highlight the importance of downloading the RUU for your phone before unlocking. If it's not available add a note to proceed with caution
Still, good work
Click to expand...
Click to collapse
Thanks for that, I should mention about downloading the RUU for the phone in case you want to revert back, I was going to add that into the reserved #2 post at a later date, 'How to revert back to Stock'
Yeah I'm aware that there is a lot of info out here on XDA already but like I said at the start of my OP, it's all in different places, some of it is difficult to understand and it's quite fragmented in parts and there isn't really a 'Start-to-Finish' guide out there, or at least not one that I've seen. Even then, people can still find what they need, have access to all the relevant tools but still not be able to proceed, either due to lack of English skills or understanding, intelligence etc... So I thought I'd write it up in real 'laymans terms'.
But as you say, the info's already here for those who've learnt to use the search button

Thanks for repyling, fyi mine is indonesia.
Sent from my HTC One X using xda app-developers app

neoandresk said:
Thanks for repyling, fyi mine is indonesia.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
How did you get on?

Hi mate! at first, thanks for this "noob" tuturial! i think i'm going to try it later.. i have some questions i would like to know before i continue as i don't root/flash roms since my htc hero.. would be thankful if you cared to help me
i have just installed the ruu on mine with 4.0.4 and senses 4.1.
- Will i be able to make a complete rom backup of my actual rom (exactly as it is, with my configs, apps, etc. i user to do it everytime when i was flashing a new rom on my hero so i could revert if anything went wrong or i didn't like the new rom).
- if not, is there a way to reinstall the ruu or the official rom later if i decide for it so i can receive official updates? In other words, can i revert to an "original" state?
And finaly, is there anything that is not working on revolution rom?
thanks a lot!

Hey Porsche. V,
The answer to both of your questions is essentially 'Yes'.
You'll find in my OP one section called 'Backing up your data', depending on which instructions you decide to enter will depend on what gets backed up, take a look at that section and the forum thread that I linked to from that, that'll give you an idea on what to enter into CMD.
It'll be something like
Code:
adb backup -apk -shared -all -f C:\backup\backup21082012.ab
There's a good list of the factory ROMs here, download the relevant one for your handset, RUU etc... then put the phone in fastboot USB and enter into cmd from cd \Android\fastboot
Code:
fastboot oem lock
That'll relock the bootloader, I think that's correct anyway, never done it myself, I know many others have however but yes you can revert back to how the phone is stock, bar the Bootloader saying 'Relocked' instead of 'Locked'.
You can also make a Nandroid backup (always recommended, I should add that into my guide) before flashing any new ROMs, especially when coming from stock
Read these;
1:- http://forum.xda-developers.com/showthread.php?t=1660807
2:- http://forum.xda-developers.com/showthread.php?t=1543604
3:- DEFINITELY READ THIS http://forum.xda-developers.com/wiki/HTC_One_X#Total_recovery_-_flashing_a_RUU_to_completely_restore_your_phone
The ARHD ROM is the most stable ROM there is, everything works, it's the best!
Porsche.V said:
Hi mate! at first, thanks for this "noob" tuturial! i think i'm going to try it later.. i have some questions i would like to know before i continue as i don't root/flash roms since my htc hero.. would be thankful if you cared to help me
i have just installed the ruu on mine with 4.0.4 and senses 4.1.
- Will i be able to make a complete rom backup of my actual rom (exactly as it is, with my configs, apps, etc. i user to do it everytime when i was flashing a new rom on my hero so i could revert if anything went wrong or i didn't like the new rom).
- if not, is there a way to reinstall the ruu or the official rom later if i decide for it so i can receive official updates? In other words, can i revert to an "original" state?
thanks a lot!
Click to expand...
Click to collapse

instaling Revolution rom now! thanks for the tuturial!

f*cked up phone

first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks

CrankyPants said:
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
Click to expand...
Click to collapse
Restore you stock ROM nandroid. Look for it in here COLLECTION of Stock backup's seeing as you really didn't bother to provide us with the relevant and more important information such as the CID and Main software version you were on before you decided to mess your phone up and I doubt you made a backup of your device before doing it.

Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.

I guess I will be the "bad guy" but why are you messing with your phone when you have no clue what you are doing?

Everyone starts somewhere. Im sure we all learned a lot of what we know now by making lots of stupid mistakes. This logic rings true for life... not just phones.

lucas.scott said:
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
Click to expand...
Click to collapse
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?

CrankyPants said:
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
Click to expand...
Click to collapse
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.

Jyotirdeb said:
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Click to expand...
Click to collapse
How to install a custom recovery via adb and what is adb?
sorry I don't know anything

CrankyPants said:
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
Click to expand...
Click to collapse
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.

I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.

leongwengheng said:
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
Click to expand...
Click to collapse
Good choice on the videos, these days reading is a bit to tedious for most people. Heck, they don't even read "STOP" on the STOP signs anymore, just drive straight past

I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app

leongwengheng said:
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck at school then and later on in your job

Lucky boy having such a commited community here. You could've quite easily ended up with a £600 paper weight. Might want to show some appreciation to everyone holding your hand through a process that you should've read about before doing anything. Must admit, I did like the 'I just kept hitting next without knowing what I was doing', that's probably the best thing I've read lol lol.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

BerndM14 said:
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
Click to expand...
Click to collapse
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?

CrankyPants said:
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
Click to expand...
Click to collapse
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.

BerndM14 said:
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
Click to expand...
Click to collapse
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.

CrankyPants said:
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
Click to expand...
Click to collapse
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?

BerndM14 said:
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
Click to expand...
Click to collapse
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.

Jyotirdeb said:
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Click to expand...
Click to collapse
To get getvar all you'll need fastboot commands, will fastboot commands even work if he MIGHT not have enabled USB Debugging or for that matter haven't accepted the RSA key?
That's why I asked about the recovery as well though. I saw that on hasoon's toolkit the flashing of a custom recovery was like the next step on the process which means that this guy should at least have a custom recovery already installed.

Bricked Phone After Magisk Install

Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James

Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.

jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."

Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk

Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....

Make sure you are trying to open from the correct location, and put .\fastboot

EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?

simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?

Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.

Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...

simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!

Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.

Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!