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

DISCONTINUED noobs guide to unlocking/locking bootloader, rooting, returning to stock

DISCONTIUED PLEASE READ THE END POST!
FIRST THINGS FIRST I TAKE NO RESPONSABILITY FOR YOU BRAKEING OR BRICKING YOU HARDWARE OF ANY KIND! THIS IS A noob's GUIDE
TO UNLOCKING/LOCKING YOUR XOOM'S BOOTLOADER, ROOTING AND ALSO A GUIDE TO GOING BACK TO STOCK. ALL WHAT I HAVE WROTE HERE
IS THANKS TO ALOT OF PEOPLE ON XDA AND VERIOUS OTHER XOOM FORUMS. THERE IS ALOT OF THREADS OUT THERE WHAT ARE VERY CONFUSING
AND THE IS A SIMPLE GUIDE AND I CHOSE TO WRITE IS TO HELP PEOPLE THAT ARNT USED TO THIS KIND OF ANDROID DEV. THIS IS A WAY FOR
WINDOWS OLY AS I DONT AND WONT HAVE A MAC SORRY
THESE STEPS ARE VERY SIMPLE FOR PEOPLE THAT KNOW HOW TO FIND THINGS ON WINDOWS AND I KNOW IT ISNT VERY EASY BUT IT EXPLAINS ALOT
IN A LOT LESS WAY AS THE OTHERS SO ITS SIMPLE.
(<> = SPACE NOT TO CONFUSE PEOPLE)
NEEDED - MOTODEV DRIVES
TIAMAT UNIVERSAL ROOT
TIAMAT 2.2.2 ROM
ORRIGINAL XOOM 3.0 FILES
THANKS TO EVERYONE - okantomi (ORIGINAL HEL FROM HIS GUIDE)
TIAMAT (FOR ALL THE FILS ROOT, ROMS, ETC)
+ EVERYONE ELSE WHO HAS HELPED
LETS GET TO IT THEN
UNLOCKING/LOCKING MOTOROLA ZOOM BOOTLODER:
1. open files from c:/USER/ android or what ever its under for android SDK/AVD (mine was in programfiles x86)
2. open command prompt
3. copy the adress of platformtools.OR.tools from SDK
4. type in cd<>the paste address
5. then type adb + enter
6. then type fastboot<>oem<>unlock or (lock to re-lock the bootloader)
7. should boot into protocal to ask if u accept all the t&c's
8. accept it all (WARNING THIS WILL FACTORY RESET AND ALL DATA WILL BE LOST)
9. it should reboot with bootloader unlocked!
10. then root!
ROOTING:
A. BEFORE WE START DO NOT FLASH A .ZIP FILE THROUGH COMMAND PROMPT AS THIS WILL CAUSE PROBLEMS!
B. GET THE UNIVERSAL ROOT FILE FROM THE TIAMAT FORUM (http://forum.xda-developers.com/show....php?t=1242241)
c. MAKE SURE U HAVE THE TABLET ON CHARGE!
d. copy the tiamat recovery to your tool files
1. open command prompt as before
2. type fastboot<>reboot<> bootloader
i. when in fastboot you may need to unplug and plug the usb back in
3. type fastboot<>flash<>recovery<>then the name of the file wich is either the name it was of download or i suggest
rename it as 3.2 root.img
4. after this is done the device can be re-started and there you have a rooted motorola xoom
RETURNING TO STOCK:
A. BEFORE WE START YOU WILL NEED THE ORRIGINAL FILES FROM THE MOTODEV SITE
(http://developer.motorola.com/products/software/)(COPY THESE TO THE TOOLS OR PROGRAM TOOLS WICH EVER YOU DIRECTED FROM
ORRIGINALY!)
1. open command prompt and navagate to the tools.or.program tools as before
2. TYPE FASTBOOT<>FLASH<>BOOT<>BOOT.IMG
3. TYPE FASTBOOT<>FLASH<>SYSTEM<>SYSTEM.IMG
4. TYPE FASTBOOT<>FLASH<>RECOVERY<>RECOVERY.IMG
5. TYPE FASTBOOT<>FLASH<>USERDATA<>USERDATA.IMG
6. TYPE FASTBOOT<>ERASE<>CACHE
7. TYPE FASTBOOT<>OEM<>LOCK
THIS WILL ONLY GIVE YOU ANDROID 3.0.1 YOU WILL HAVE TO UPDATE MANUALY AS I HAD TO IT ISNT VERY HAD EVEN THO IS TOOK ME A WHILE
TO LEARN IT.... THIS GUIDE IS FOR noob's AS IT SAYS COZ THERE ARE ALOT OF GUIDES OUR THERE WHAT ARE VERY DIFFRENT AND THIS WAY
WORKED FOR ME SO HOPE IT HELPS
if anyone needs more info just get in touch
EDIT: this has not been updated due to the fact i dont have a XOOM anymore! still pease feel free to contact me via PM if you need any help and i will try my best to help! thanks all

Thanks you for this.

I like it...I'll refer peeps to it.
Edit: Yeah, well, reading it over with the questions from scsa20 especially, who I know is very experienced, leads me to see that perhaps this guide needs a bit more work. But I really like that you wanted to share what you have learned and I agree that there are some big holes in all of the available guides. Maybe you could address the issues and incorporate scsa20's recommendations...then you'd have a really useful guide and help a lot of people.

Thanks for this, but you have to fix some links, as the are now they don't work

RETURNING TO STOCK:
A. BEFORE WE START YOU WILL NEED THE ORRIGINAL FILES FROM THE MOTODEV SITE
(http://developer.motorola.com/products/software/)(COPY THESE TO THE TOOLS OR PROGRAM TOOLS WICH EVER YOU DIRECTED FROM
ORRIGINALY!)
1. open command prompt and navagate to the tools.or.program tools as before
2. TYPE FASTBOOT<>FLASH<>BOOT<>BOOT.IMG
3. TYPE FASTBOOT<>FLASH<>SYSTEM<>SYSTEM.IMG
4. TYPE FASTBOOT<>FLASH<>RECOVERY<>RECOVERY.IMG
5. TYPE FASTBOOT<>FLASH<>USERDATA<>USERDATA.IMG
6. TYPE FASTBOOT<>ERASE<>CACHE
7. TYPE FASTBOOT<>OEM<>LOCK
THIS WILL ONLY GIVE YOU ANDROID 3.0.1 YOU WILL HAVE TO UPDATE MANUALY AS I HAD TO IT ISNT VERY HAD EVEN THO IS TOOK ME A WHILE
TO LEARN IT.... THIS GUIDE IS FOR noob's AS IT SAYS COZ THERE ARE ALOT OF GUIDES OUR THERE WHAT ARE VERY DIFFRENT AND THIS WAY
WORKED FOR ME SO HOPE IT HELPS
Click to expand...
Click to collapse
Will these steps flash back stock kernel ? I using tiamat custom kernel such as Odachi. relock bootloader with a custom kernel will make xoom bricked so these step would flash back stock kernel ???

How about turning off caps lock? Oh, and learning how to spell "break"

I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
TIAMAT 2.2.2 ROM
Click to expand...
Click to collapse
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
UNLOCKING/LOCKING MOTOROLA ZOOM BOOTLODER
Click to expand...
Click to collapse
I think you mean "XOOM" and not "ZOOM"
1. open files from c:/USER/ android or what ever its under for android SDK/AVD (mine was in programfiles x86)
Click to expand...
Click to collapse
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
4. type in cd<>the paste address
Click to expand...
Click to collapse
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
5. then type adb + enter
Click to expand...
Click to collapse
What exactly are you trying to have us achieve here?
6. then type fastboot<>oem<>unlock or (lock to re-lock the bootloader)
Click to expand...
Click to collapse
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
7. should boot into protocal to ask if u accept all the t&c's
8. accept it all (WARNING THIS WILL FACTORY RESET AND ALL DATA WILL BE LOST)
9. it should reboot with bootloader unlocked!
Click to expand...
Click to collapse
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
1. open command prompt as before
Click to expand...
Click to collapse
You should already be in a command prompt, if not, reopen.
2. type fastboot<>reboot<> bootloader
Click to expand...
Click to collapse
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
i. when in fastboot you may need to unplug and plug the usb back in
Click to expand...
Click to collapse
I have yet to see anyone having to do this tbh
3. type fastboot<>flash<>recovery<>then the name of the file wich is either the name it was of download or i suggest
rename it as 3.2 root.img
4. after this is done the device can be re-started and there you have a rooted motorola xoom
Click to expand...
Click to collapse
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.

All of this.... AND you can flash HLK75D and save yourself about three hours of manual slow updates!!
Which is available on Motodev, you shouldnt need the link to that by now. Also... no one post after me cause this thread should go buhbye.
scsa20 said:
I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
I think you mean "XOOM" and not "ZOOM"
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
What exactly are you trying to have us achieve here?
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
You should already be in a command prompt, if not, reopen.
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
I have yet to see anyone having to do this tbh
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.
Click to expand...
Click to collapse

Have you guys seen the movie "Super 8"?
Yeah, in that movie there is a train wreck a little bit smaller than this guide.

graymulligan said:
Have you guys seen the movie "Super 8"?
Yeah, in that movie there is a train wreck a little bit smaller than this guide.
Click to expand...
Click to collapse
OK, stop piling on...at least he tried to give back...more than I've seen with a lot of people.

Hi guys thanks for all the comment al try help u all with what worked for me as not alot did work for me I'll answer all your questions one by one after each other so bare with me and thanks again for your posative feed back
Sent from my MZ604 using xda premium

luyenbichta said:
Will these steps flash back stock kernel ? I using tiamat custom kernel such as Odachi. relock bootloader with a custom kernel will make xoom bricked so these step would flash back stock kernel ???
Click to expand...
Click to collapse
This wont brick it I have recently returned to stock as I want a ics rom or official software. As fare as im aware you can flash all models with the stock files and it is is quite easy as it says just tips the command from the original folder and DONT type adb
Sent from my MZ604 using xda premium

scsa20 said:
I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
I think you mean "XOOM" and not "ZOOM"
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
What exactly are you trying to have us achieve here?
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
You should already be in a command prompt, if not, reopen.
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
I have yet to see anyone having to do this tbh
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.
Click to expand...
Click to collapse
I didn't really want to explain how to flash a rom as that way you quoted didn't work for me. I no I have ****ty grammer and spelling but I did type up quick and step by step ifor noobs as this is very new to me. I have experiance with galaxy s and s2 but not in bootloaders and flashing with command prompt. Thanks anyway and I am gunna edit it shortly. But as I say I am happy to explain more to people
Sent from my MZ604 using xda premium

Tto be hoist all the people that have complain I don't no if its my english which yeah im english but I thinks its pritty straight forward that it how to unlock your bootloader, root your device and return to stock its pritty simple. I didn't add how to flash a custom rom as all the guides I found and used I flashed mine from internal memory not on and sd card. But like I say thanks for the possative comments quys
Sent from my MZ604 using xda premium

Out of curiosity, when you go from root back to stock, does the bootloader automatically lock back, or is that done seperately?
Sent from my ADR6300 using Tapatalk

300k said:
Out of curiosity, when you go from root back to stock, does the bootloader automatically lock back, or is that done seperately?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
If you tips all the commands in u will need to accept it all again. Well that's what did anyway
Sent from my MZ604 using xda premium

I still can not make this model the root someone help me? Xoom 2 media edition MZ607 wifi 32gb.

Ok I've followed 2 guides which very much the same. I'm having a lot of trouble with this, I'm trying to hard reset my xoom because someone (I don't know who) decided to put on a password lock.
When I type "fastboot oem unlock" it fails.... Please view the images below and please please please help!
Cmd prompt
{
"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"
}
Xoom display
Sent from my CM9 Flashed GT - I9100 XDA app-developers app

Bump
Sent from my CM9 Flashed GT - I9100 XDA app-developers app

Orkane1989 said:
Bump
Sent from my CM9 Flashed GT - I9100 XDA app-developers app
Click to expand...
Click to collapse
hey sorry for no reply as i havnt got a xoom anymore if you need any help feel free to inbox me if you need any help op will be updated!

[HOWTO] Easy Root Instructions (Sprint or T-Mobile) [Updated 24 June 2012]

First off, let me say that I did not develop this schtuff and all thanks should go to those that did. Special thanks to noobnl (his thread here), mskip and TeamEpic for all their work.
A note about these instructions:
They're long and may seem a little daunting to those that aren't experienced. Please don't let that deter you as they've been written to be as simple and easy to follow as is reasonably possible assuming you can work a Windows PC and extract a zip file.
==> If you encounter problems with these instructions, please check the FAQ in the post following this one. <==
For video instructions (courtesy of qbking77) scroll to the bottom of this post.
General Disclaimer:
Use these tools and this guide at your own risk. Doing these things wrong/improperly/etc. has the ability to completely ruin your device and YOU assume all risk and responsibility if that happens.
Also note that rooting WILL violate the manufacturers warranty on the device making it ineligible for warranty repair. If you have insurance on the device however, they MAY still replace it for the cost of your deductible.
Click to expand...
Click to collapse
Non-ADB Root instructions (Windows Only):
First, the non-dangerous, standard user stuff:
Download and install the Samsung USB drivers from Samsung's website: http://downloadcenter.samsung.com/c...nt_L710_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Turn on Debugging on your Phone
Open Settings
Select "Developer options" in the System section
Check the box for "USB Debugging"
Press "OK" to confirm.
Plug you phone up to your computer using the USB cable and allow the drivers to install.
Download CMW_SuperUser_v3.07.zip from the bottom of this post
I recommend making yourself a nice little GS3 folder in your downloads folder for all this stuff so it's easy to find
DO NOT UNZIP!!
Copy CMW_SuperUser_v3.07.zip on to the Root of your GS3s INTERNAL storage (if you put it into a folder, you may have a hard time finding it later, but that's on you).
DO NOT UNZIP!!
Unplug your phone
Power off your phone
Now, this is the part that can BRICK your phone so follow ALL instructions CAREFULLY!!
Download Odin3-v3.04 from the bottom of this post
Extract Odin3-v3.04 into it's own folder somewhere where you can easily find it.
Download clockworkmod.tar from the bottom of this post to somewhere you can easily find it.
Reboot your phone into download mode
Hold down Volume Down, Home and then the Power button until the Warning!! message is displayed
Press Volume Up to continue.
Your phone should now be in download mode, displaying a green Android and say Downloading. If it is not, power off your phone by holding down the power button and then try to get into Download mode again. Do NOT progress until you have done so.
Go into the folder you extracted Odin3 into and run Odin3 v3.04.exe (you may have to Right-Clik => Run as Administrator)
Connect your phone to your computer via USB. Drivers may install again; if this happens, allow them to finish before progressing.
In Odin, the COM box all the way to the left should turn blue and it should say Added!! in the Message area.
Click on PDA and in the Open window that pops up navigate to and open the clockworkmod.TAR file you downloaded earlier
Verify that Auto Reboot and F. Reset Time are checked
Click Start. Once the process is completed you device should automatically reboot and there will be a green PASS! box in the upper left of the window. You can then close Odin.
Power off your device and boot into Recovery mode
To boot into Recovery mode: Hold down Volume Up, Home and then the Power button until the device begins to power on then release all 3.
You'll know you're in recover mode when it says "CWM-based Recovery" at the top of the screen
Install CMW_SuperUser_v3.07.zip that you copied onto your internal memory
Navigating ClockWorkMod Recovery: Use the Volume Up and Down rocker to change the highlighted option and the Home button to select an option. The Back softkey works, but will not be lit and will take you back one screen.
Installing a zip:
Select "Install zip from sdcard" (Yes, I know it's on the internal storage.)
Select "Choose zip from sdcard"
Select the zip you want to install; in this case CWM_SuperUser_v3.0.7.zip
Select "Yes" to begin installing
Once the process has completed use the Back arrow to get back to the main recovery screen (Remember: it works, but it's not lit) and select "reboot system now." Once your device boots up you should now be 'Rooted,' but there's still a few more things to be done
Install BusyBox. There are actually several ways to do this, but the BusyBox app in the Google Play Market is quick and easy.
Install BusyBox (this is a link to the online verison of the Google Play store. You can actually follow this link and install it from there and it will get pushed to your phone. Alternatively, just search for BusyBox in the Google Play store and it should be the first app in the search results from author Stephen (Stericson))
Open BusyBox Free from your App Drawer
Allow it Root access when it prompts you
Tap the red "X" to close the dialog window that pops up
Allow BusyBox to scan you phone
Tap "Install" to install BusyBox and make the necessary file changes.
Update your Binaries.
Open the Superuser App from the App Drawer
Get into settings (the wrench icon in the upper right of the screen)
Select Su binary under the General section towards the bottom of the list
Select Update
Your device is now rooted and all set.
How to video (YouTube): http://www.youtube.com/watch?v=7Soapch0c5U
Thanks again to qbking77 for the instructions video!
P.S. If you are a developer or I have used some of your material and/or you feel you should be credited, please let me know and I will update this post.

Frequently Asked Questions
This FAQ is in the works as more questions roll in so I'll do my best to keep it updated.
Q: Odin failed! What do I do!?
A: Try plugging your USB cable into a different USB port on your computer and/or try a different USB cable (Odin's picky about the cable). The drivers may install again; if so, wait for them to finish. After that, verify that the device shows as Added in Odin again and click start again. If that still fails, try unchecking F. Reset Time box and removing any MicroSD card you have in the device, plug the device into (yet another) USB port and try again.
Q: Will these instructions work for other US (LTE) versions of the GS3?
A: I have not personally tested this method on any other versions of the GS3 but uoY_redruM and carrrnuttt (and others) have confirmed that this method works for the T-Mobile version as well. It should in theory also work for the AT&T and Verizon versions, though that's unconfirmed at this point.
Q: Ok, so I've got Root. What now?
A: That's entirely up to you. Root allows a near endless amount of customizatoin, but some of the most commonly sought after benefits of Root are these:
Root Only applications. These allow you to simply do more with your phone or tweak the way it functions. Some that I personally recommend are:
Titanium Backup and its Pro Key => For making backups of your apps, app data and system data and uninstalling or freezing Bloatware.
Quick Boot => For booting drectily to recovery or Download Mode (listed as Bootloader in the App)
Removing Bloatware => I recommend Titanium Backup for this
Loading custom ROMs. There aren't many floating around just yet, but I expect that'll change soon as the ball gets rolling.

Excellent write-up. Thanks. Now can we install custom roms from other forums or do we have to specifically wait for any to come up here.

Great write up! very easy and simple

daniel06gt said:
Excellent write-up. Thanks. Now can we install custom roms from other forums or do we have to specifically wait for any to come up here.
Click to expand...
Click to collapse
You should wait for any specific Sprint Galaxy S3 ROMs that get posted if you want to ROM your phone. I'm sure some will be popping up by the end of the weekend so I wouldn't expect that you'll have to wait too long

Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.

Very nice work... I'll get a how to video going very soon!

(repost, sorry)

Great write-up! Thanks for taking the time to do this.

Thanks for writing this up!

teh roxxorz said:
Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.
Click to expand...
Click to collapse
Yes, this and noobl's method are pretty much the same, the main reason for this post is to put the method into an easy-to-read step-by-step format that's easy for beginners to follow. Remember, we were all beginners at some point

I come from HTC so Odin is new to me, this guide is little more friendly than noobl's method. Although either would suffice this is just pretty clearly laid out.
Look forward to root.

Very nice and simple
Thank you. Now let the games begin....

cypher_zero said:
[...]Remember, we were all beginners at some point
Click to expand...
Click to collapse
While I expect a fair amount of carry-overs from Sprint Epic's and Epic Touch's, I also expect a large influx of excited users who haven't used a Galaxy S phone before.
:highfive:

How to video is done! Just have to compile and upload it

qbking77 said:
How to video is done! Just have to compile and upload it
Click to expand...
Click to collapse
Always on the ball qbking77 gotta add galaxy s 3 to your signature now =)

teh roxxorz said:
Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.
Click to expand...
Click to collapse
I hate adb that shiit is tedious LOL

tj.iscool said:
I hate adb that shiit is tedious LOL
Click to expand...
Click to collapse
You can always script a bat file or two, saves always rewriting commands.

tj.iscool said:
I hate adb that shiit is tedious LOL
Click to expand...
Click to collapse
I actually prefer adb over one click roots.
Something about seeing what your doing and sense of accomplishment lol

cypher_zero said:
Yes, this and noobl's method are pretty much the same, the main reason for this post is to put the method into an easy-to-read step-by-step format that's easy for beginners to follow. Remember, we were all beginners at some point
Click to expand...
Click to collapse
No qualms there, just making sure I didn't miss anything. Though you are right, it may be hard for a beginner to follow noob's more experienced cut throat guide. Kudos.

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.

Explain like I'm a three year old, I beg of you.

I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.

Allmystical1 said:
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Click to expand...
Click to collapse
No problem, we are all new at this once, right?
First Step: Downloads!
TWRP:
http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.8.4-for_odin.tar.md5
ROM:
Here is a matter of preference. If you want the latest *working* version, you can upgrade to 5.0, but you lose the camera. I presume you want the camera to work, so I suggest Bubor's CM11 for KitKat. There are other good roms too, like PAC and SediRom, but we will start with Bubor's CM11.
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip.md5sum
ODIN:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
Second Step: Prepare.
I am presuming that you are using a Windows computer. If you are using a Linux computer, I can tell you what to do also, but these instructions are for Windows. I am also presuming that you have an external SD card in your phone, if you do not, go buy one and put it in your phone.
Unzip the Odin304.zip by right clicking on it and say unzip/extract, etc. If your Windows does not have this option, you need to download a program like winzip or 7zip so you can unzip this file. If you need those programs, they can be googled and downloaded.
Third step: Further preparation.
Turn on your phone and plug it into a usb cord and plug the usb cord into your computer. If you are using Windows, it will try to find drivers for the phone. It should be automatic and just work. If it does not, then you need the drivers, which are here:
http://www.mediafire.com/download/0up21ccc9gajwjv/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
*If you downloaded this file, just double click it like a program, it should open and install drivers for your phone. Do not do this unless your computer cannot find drivers for your phone!
Fourth step: Charge your phone.
Plug in your phone and FULLY charge it. ALL the way to 100% CHARGED. No exceptions. No shortcuts. Do it. Then UNPLUG YOUR PHONE AND TURN IT OFF.
Fifth step: Put TWRP on your phone.
a. Your phone should now be unplugged and off. Open the ODIN folder that you unzipped earlier and double click on ODIN to open the program.
b. Click on the PDA button ( you and I both know that your phone is not a PDA, this is not a typo ) and it will open a browser. Find the twrp-2.8.4-for_odin.tar.md5 file and select it. It should now fill in the blank line next to PDA with this info.
c. WHILE HOLDING THE UP VOLUME BUTTON ON YOUR PHONE, press and hold the power button. When you see "SAMSUNG" you can release the power button, but KEEP HOLDING THE UP BUTTON, untill you see a yellow triangle and warning notice. If you hold too long, that is okay as it will take you straight to the download mode with the green android that says "ODIN" at the top and "Downloading" in the middle. If you got stopped at the yellow warning/triangle, press up again to go to download mode.
d. Plug your phone into the usb, and the usb into your computer.
e. In the Odin program, press start.
You should now see a serries of verbage going by on the left, at the top a green bar may fill in, and hopefully, in the end it says "success" or "pass". Your phone should reboot all by itself. If ODIN says fail, ask for further instructions. If passed, close Odin.
Sixth step: Put your CM11 files on your phone.
Your phone should have rebooted and looks just like it did before, now powered on, and in your stock Ice Cream Sandwich firmware. As with any file transfer, plug your USB into the phone and computer. Drag the CM11 files to the phone. Anywhere will do, but if you have an external SD card in your phone, I recommend you put it there.
Seventh Step: Boot into TWRP.
a. Turn off your phone.
b. Unplug the USB.
c. HOLD THE DOWN VOLUME BUTTON and press the POWER BUTTON. When you see "Samsung" release the POWER BUTTON, but keep holding the VOLUME DOWN BUTTON. At the top of the screen, white letters should say something like "entering recovery".
d. When you see "Team Win Recovery Project" release the down volume button.
Eighth step: Make a backup!
a. Press "Backup" button on screen.
b. Check all checkboxes (system, cache, data, boot, Android Secure)
c. Press "Storage: sdcard (xxxx mb)" bar.
d. Select "External_sd" to choose to backup to your external sd card.
e. Slide the swipe bar to the right to backup. This will take a few minutes, with progress bar.
NOTE: if the screen dims, when you touch it, you will see a TWRP lock icon, swipe right to unlock it.
f. When backup is completed, it will say "reboot system", do not click that. Click the "home" icon in the lower left corner.
g. Click the "Wipe" button.
h. Swipe right to factory reset.
i. Click the "home" icon in the lower left corner.
j. Click the "install" button.
k. At the top, click on the "Storage: sdcard (xxxx mb)" bar.
l. Select "External_sd"
m. choose the cm-11-20160126-UNOFFICIAL-i927.zip
n. When that is done, click on the "reboot system" button.
The system will reboot. You should now see CM11's boot screen. The first boot takes a bit of time.
Ninth step: Thank Bubor.
a. Log into XDA.
b. Go to http://forum.xda-developers.com/captivate-glide/development/dev-cm-11-0-t2802184
c. Slap every thanks button that is for a post by Bubor untill it tells you that you cannot slap any more thanks buttons (that is only 8 thanks per day).
Tenth step: Enjoy your phone!
....I think you know how to do that.....
If you have ANY questions, please just post them here and we will see if we can answer them.

I am thanking you so very much! Also... I do apologize for such a time lapse in my reply. Life happened.

I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.

tr3sie7e said:
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
Click to expand...
Click to collapse
Great question, and an interesting problem!
First, I am really glad that you followed the instructions and made a backup! It is good to know that you can always go back to the way it was.
I recommend that you download another rom from the developer section here, such as Sedi-rom, omni-rom, etc., and try flashing that. If you flash one of those roms, does your IMEI stay for those roms?
Try this one: http://forum.xda-developers.com/showthread.php?t=2789727
You can do steps 7 through 10 with any of the roms in the developer thread. If this other rom works, you can use it, or download others and try them. If the SediRom does not work also, then we will need to sit down and figure this out.

I really appreciate the fact that you're here to help.
I downloaded and installed SediRom 2.1.2 and my IMEI still shows as "Unknown." However this time I should add there is a serial number, which I don't believe was present in CM11 or in the stock ROM, although I'm not sure if that's at all significant. I made an external backup of the efs file from the stock ROM, is there some way I could just reinstall CM11 and replace/overwrite the efs to give it an IMEI number? I'd really like to use CM11 if possible, I was enamored by how good it looked and how functional it was, especially since the last time I tried CM a long time ago I didn't have such a good opinion of it. Plus the bootloader is friggin sweet !
I recently got the phone unlocked off eBay, so I don't know its past history but I was able to access the network when I had the SIM card in prior to initially installing CM11 but not afterwards. I'm trying to use a T-Mobile SIM but like I said I was able to successfully access the network prior to installing CM11. But the IMEI doesn't show at all regardless if the SIM is in at all.
Is there some kind of different hardware/firmware like in a newer slightly different version of the phone that came out resulting in compatibility issues? I'm not the most experienced but I've dipped by toes in this before, so I would be willing to go the extra mile if it meant I could get CM11 to work, because honestly it looked like everything I could ever want from this phone with a good looking theme too...

Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs

xdajog said:
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?

tr3sie7e said:
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
Click to expand...
Click to collapse
Well restoring efs have to be done in recovery only! Do not try to do this while android is running!!
To be honest the absolute best way is having a dd partition dump of the whole partition. When you have followed the mentioned guide do you have used also dd like this?
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
I don't know if copying the efs folder alone would work.. better is restoring the whole partition if possible. Do you have such kind of backup?
Sent from my LG-H815 using XDA Labs

Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew

azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.

azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
Redownload. Maybe the file you had downloaded gets corrupted or is incomplete ..
.
Sent from my LG-H815 using XDA Labs

bubor said:
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
Click to expand...
Click to collapse
Many thanks bubor! Renaming worked like a charm.
FYI, I tried re-downloading it, but that didn't seem to work yesterday.
I really appreciate all of your work, everything is working great.
Thanks for the quick responses.
All the best!

So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...

tr3sie7e said:
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
Click to expand...
Click to collapse
Check my faq here:
http://forum.xda-developers.com/showthread.php?t=2789727&p=54075993
Scroll down to restore efs.
.

Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...

tr3sie7e said:
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
Click to expand...
Click to collapse
Please paste the output of the results. Doing this in twrp is the correct way.