Related
Hi there,
I just came up to Android with an Orange branded HTC Desire. Until now, I was using a HTC Diamond 2 with WM and tried some cooked ROM. But it was really easy with WM. Now, I need to understand more or less how my Android phone works to be able to play with it the same way I played with my Diamond 2.
As I'm a bit lost with some Android terms and concepts and I would like to purpose a kind of glossary for newbies like me. The goal is to explain common concepts with a functional and a technical point of view. I try to give example based on Nexus One and Desire based on personal experiments.
I'll start with what I've understood last few days and believe to be right. I'll ask you to correct my mistakes and to complete this FAQ. I'll keep this post updated.
For the moment following lines may contain big mistakes. I will try to flag validated information.
ROM
A ROM contains the OS on your phone. It can be installed like Windows or Linux on your desktop PC. A ROM contains the kernel and a pack of applications already installed for you. You can find a lot of cooked ROM (ROMs made by great people who would like to share with you optimizations they've done on their phone) on Internet. Normally, Android phones only accept ROM which are signed by the reseller. So you can only put Orange ROM on Orange branded phone.
Moreover, installing a new ROM is a way to update your phone. However, Android phone include an internal updating system (it's just a program like Windows update) so you can receive updates without installing a new ROM. It's called OTA (On The Air) update. OTA update is the way for basic customers to receive update for their phone.
Functionally :
Install a ROM is as easy as execute an exe on you Windows PC. It very easy and fast. You can also install a ROM by using the Recovery Menu.
GoldCard
A GoldCard is a modified SDCard which allows you to put the original unbranded ROM on a career branded phone (installing the original HTC Desire ROM on an Orange HTC Desire). Normally, if you try to execute a HTC ROM updater with a Orange phone, you'll be stuck after 4 or 5 clicks on next. With a Goldcard in your phone, you can archive the process.
You can't install a ROM built for an other device just using a GoldCard (installing a Nexus One ROM on a Desire is not possible).
GoldCard is only needed if you have a carrier-branded Desire, even for rooting process. Unbranded phones never need it.
Be sure to keep your GoldCard because it will be needed for each ROM modifications. You can use a GoldCard as a normal SDCard without problem. However, if you create new partitions for app2sd, your GoldCard will ruined.
Functionally :
Create a GoldCard is easy. It will take you 30 minutes. Not all SDCards work to create a GoldCard. Mine (SanDisk 4Go) included in my Orange package worked perfectly.
Instructions can be found here or here.
Technically :
If I'm right, while you are installing a ROM from the executable on your desktop PC, the phone checks if the ROM you're trying to install match a hard coded key on the phone. With a GoldCard, you make the phone believe signature is good.
CID
The serial number of your SDCard. You'll need to retrieve it with ADB Shell to create your GoldCard.
Functionally :
In ADB Shell (see ADB section), following command line give you your CID :
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
Fastboot
It's like the BIOS on your desktop PC. You can access the fastboot with a keyboard combo while starting your phone. It give you access to some function like Recovery Mode or SIM Unlock. With fastboot, you can also install a new ROM using a zip placed on your SDCard.
Use can easily unlock Fastboot on the Nexus One using a ADB shell command.
Fastboot give you access to the recovery mode. In this mode, you can gain write permission in the /system partition which is not possible in Disk Drive mode, event with USB Debugging enabled. With this access, you can easily remove applications which are included in the ROM (like FriendStream in HTC ROMs).
Functionally :
To reach Fastboot on Desire : Hold down back button while pressing power.
Technically :
When you connect the phone to your PC in Fastboot, you will establish a special connection with the device. It uses "Android Bootloaded Interface" driver.
Fastboot unlock
An operation to unlock Fastboot. It's the first step to root your phone. It's easily done for the Nexus One via ADB (see here). It much more difficult with the Desire (possible thanks to Paul).
HBoot
An other boot menu.
Functionally :
To reach HBoot on Desire : Hold down volume down button while pressing power.
ADB
ADB means Android Debug Bridge. You can read this. When you connect your phone to your PC, you can choose different modes :
Charge only : No interaction with your PC
Internet tethering (only if you have a HTC standard ROM, Orange & Co disable this option) : Your PC will see your phone like a modem.
HTC Sync (if you have a HTC standard ROM) : Use to synchronize you data with HTC Sync software
Disk drive : Your PC will see your phone as a USB key allowing you to access to your SDCard
If you're in Disk Drive mode (or even if you're in Charge only mode), you can activate USB debugging (setting > applications > development on your phone). In this mode, your PC will use a ADB driver to establish a special connection. With ADB drivers, you have access to ADB Shell.
With ADB Shell, you can list every file on device and deploy your own application.
Functionally :
Activate USB debugging on your phone to play with ADB Shell.
ADB Shell is accessible from Windows or Linux.
For people who don't use to play with command line, on windows, you must either open a cmd.exe and move in the "tools" folder (with cd command) of your unzipped ADB package or add this repository to your path (instructions here[URL].
Then you can check that everything is alright with following command :
Code:
adb devices
You should see :
Code:
List of devices attached
HTxxxxxxxx device
Then you can type "adb shell" to enter the shell. All Unix basics commands are available and you can do whatever your want... almost nothing since you're not root.
Rooting
Rooting a device is a process to become root on its OS. It allows you to install very nice apps like app2sd (to install application on SDCard), SetCPU app (to overclock or downclock your device) or OpenVPN. This kind of apps can not run if your device is not rooted.
With a rooted device, you can install apps which are not yet validated for your phone on the market by modifying the ID of your device (like the user-agent of your browser). It's easier than downloading the apk file from somebody who extracted the application on a device accepted by the market for this application.
Finally, with a rooted device, you can install ROM from an other device (installing a Nexus One ROM on a Desire).
Functionally :
On Desire, become root is now possible thanks to Paul from Modaco. On Nexus One, it much more easy.
Process is easy if you follow guides step by step. Warning, it will remove all data and configuration on your phone. However, your SD card won't be modified.
If you follow the guide to root the Desire, one of the first steps is to put a big zip file on your SDCard (often rootedupdate.zip). In fact, this zip file contains the ROM you'll have on your phone at the end of the process. Guides generally provide an almost generic ROM. The only modification made to this ROM is the addition of the Superuser Permissions app (the Ninja icon) which will help you to grant root access to applications asking for permission. Installing this ROM is the easier solution. However, you can use every ROM you want (you will find some very interesting ROM on this forum). Just put the file on your SDCard at the beginning of the process and point to the good zip file in the last step. Warning, if you want to install a ROM with app2sd in it, you must know that this application requires a special partition on your SDCard, so you must format your SDCard before the first boot of your new ROM. To do this, just after installing the ROM zip file (the last step of the rooting process), you have to stay in the Recovery Menu and use the good option to create partitions on your SDCard. Of course, your SDCard will be formated.
Technically :
I have no idea what are tricks to become root. You have to find a hole in the phone software. It's not easy.
The process itself requires several steps :
The first step is to unlock the bootloader. This step is easy on Nexus One. On Desire, this step is archived by installing a kind of ROM from Fastboot on your phone.
Unlocking bootloader will give you access to the Recovery Menu and will make your phone accept non-HTC-signed updates (for Desire).
Then, you have to connect your device in HBoot mode to your PC in order to write some files on the phone. These files are used to launch the Recovery Menu. From this menu, you can wipe all data and some caches (I don't know differences between all caches)
Finally you can install a new ROM on your device using a zip file on your SDCard.
Recovery Mode
The Recovery Mode is a special mode accessible from HBoot. You'll need to access this mode to push files needed for the Recovery Menu. It's an important step in the rooting process.
Functionally :
When your phone is in Recovery Mode, you'll see a little red triangle on your screen.
Technically :
Recovery Mode is a special provided by Android to do special operations. In fact, I don't know what's the real usage of this mode.
Recovery Menu
The Recovery Menu is a small tool accessible from Recovery Mode. It purposes some options such as wipe your data, format your SDCard and the most important option : deploy ROM or files from a zip file previously dropped at the root of your SDCard.
Functionally :
The Recovery Menu is a green menu you have to use in the root process.
Technically :
On the Desire, Recovery Menu is the only way to write files on /system. Put a zip file on the root of your SDCard and the Recovery Menu will unzip the package and deploy files on your phone for you. You will have to use this menu to install OpenVPN because this application requires to put some file in /system partition. In the last step of the rooting process, Recovery Menu will deploy your ROM (which is nothing more than just a bunch of files) on your phone.
SIM Unlock
SIM Unlock in a process different from all others. If I'm right, you'll have to use Fastboot, put some files on your SDCard and press SIMUnlock. Required files can be provided by your operator. This process works with all ROMs and don't required a root access.
Nandroid Backup
The Nandroid backup process creates binary images (.img) of the boot, data and system partitions (and ext also, if you choose nand+ext). Needless to say you need root in order to be able to perform this kind of backup.
Later, you can use those image files to restore those partitions, in a very similar way you restore a hard-disk partition from a ghost created image. Practically the restore process erases all their content and replaces it with the data saved in the img files, thus reverting the phone's software to the state it was when you performed backup.
Nandroid backup doesn't include the radio image; you can only change (or revert) the radio by flashing it again.
If you want to go back to stock software, you need to use a RUU, which overwrites all the modifications you made into the phone's software (and of course removes the root access as well).
APK
This is the file format for applications. Each application is packaged in an APK file. When you install an application from the market, you're just downlading an APK file which is then automatically installed on your phone.
You can also find APK files on Internet, put them on your SDCard (or directly download them from your phone) and install them.
Deodexed
Technically :
By default, applications are odexed. This allows Android to preload some parts of an application to optimize its launch time. Unfortunately it makes application resources be dispatched outside the APK. Deodexing is a process of gathering all resources inside the application.
Functionally :
Some applications apply a theme on other applications. You need a deodexed version of the targeted application to use this. However, deodexing applications is not a process you should take care of. You'll find some custom ROMs in which all applications have been deodexed for you.
That's all for now. I really want to complete technical information on above lines. It will be great if somebody could explain why you can not install a Nexus One ROM on a HTC Desire using only a GoldCard. Moreover I would like to know how works Fastboot with SDCard. It seems that SDCard plays a really important role (used to update ROM, SIM unlock and GoldCard).
PS : English is not my native language, please be indulgent.
Many thanks to The Professor and silvake for some precisions.
Matco.
Great topic idea, thank you!
Great idea!
Just found out that you need to be in recovery mode in order to have write permissions to the /system partitition (Disk Drive with USB debugging enabled won't work).
More details in the link below, if you want to include them:
http://forum.xda-developers.com/showpost.php?p=6347071&postcount=2
(credits go to emdzej)
Thank your for your support. I just updated the post with your details.
I would like to add some links but I don't have enough rights to add the url tag in my posts.
CID register - serial number of your sd card
Perhaps time to move the info to the wiki ?
Greetings from a vastloper
This should deffinatley get a sticky + be added to the wiki. Great info, so many new terms to learn now that i'm experimenting with android on my blackstone and seriously considering a Desire
Thank you for your replies. I just made some improvements.
It will be ready for the Wiki as soon as someone will confirm informations and help me to complete blanks.
I would really like to have more technical informations. Feel free to share what you know !
For moderators, is it possible to allow me to add URL ?
Matco said:
Thank you for your replies. I just made some improvements.
It will be ready for the Wiki as soon as someone will confirm informations and help me to complete blanks.
I would really like to have more technical informations. Feel free to share what you know !
For moderators, is it possible to allow me to add URL ?
Click to expand...
Click to collapse
matco my desire was not branded by any network.. does this mean to root I should just go ahead with the root process ignoring the goldcard step?? thanks
Yes, you're right (check [Guide] Rooting in this forum, page 4 post 39). GoldCard is only needed for branded phone.
Anyway, the website which generated the .img has been disabled. So you can't create easily a GoldCard right now...
Negative, it's back online:
http://psas.revskills.de/?q=goldcard
guys stuck on the red exclamation mark.. using vista, i ran recovery bat but the recovery mode is not going green. what other files hould be in the same folder as recovery bat?
Everything that was in the original pushfiles.zip along with adb-nilezon. Not sure if they're still there, but if they are, here's where you should be able to find them.
I just updated the FAQ as I successfully rooted my Desire. Rooting process helps me to understand what are Fastboot and HBoot for.
It would be nice if someone can tell me if you can put any zip you want on your SD Card for the last step of the rooting process or if you have to use special ROM included in the file package (rootedupdate.zip).
Thanks by advance.
You can put any full ROM on as the last step, it doesn't have to be rootedupdate.zip. That one will be exactly stock + root, though - so for people who like the phone as is but want root, that's the ROM they want.
You can download anybody else's ROM and throw it on for the final step if that's your cup of tea, though. May want to mention that if they're picking a ROM with A2SD in it, that they need to perform the SD setup before booting, or they may run into trouble with that.
Thank your for your reply.
I will add a warning for people who want to install a ROM with app2SD in it (if I'm right they can use the little "green" menu just before installing the zip file to create partitions on SD Card).
As you seem to have a good understanding of the rooting process, could you explain me what is the goal of the first step (installing a fresh ROM from RUU Installer with phone in Fastboot Mode)? And what are pushed files for ? Is it for green menu?
You need to partition the SD card (using the partition options in the recovery (green) menu) after your ROM and A2SD are installed - if you partition beforehand, you'll lose the zip files you need to flash.
The first step unlocks the bootloader so it'll allow low-level access and recovery mode and so the phone will accept non-HTC-signed updates, I believe. The pushfiles in the second step are forcing the recovery menu (the green menu you mention) onto the device - but since we can't have write access to /system while the device is outside of recovery mode, we have to push the files every time.
very helpful for winmo converts thanks
it took me some time to figure that out
I've done some updates thanks to The Professor.
Great thread, thank you
Please refer to this post before upgrading Your DHD
http://forum.xda-developers.com/showthread.php?t=879525
If You update to latest version You will NOT be able to boot custom HBOOT!!!
Here is guide how to downgrade Your DHD if You updated to latest version by mistake
http://forum.xda-developers.com/showthread.php?t=905003
This is complete guide for all HTC Desire HD owners who want's to root their devices and install custom recovery image.
FLASH THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
I have collected and summarize few guides on this forum in order to collect all informations on one place.
Check following threads for additional informations.
Please post all bug's and issues related to DHD scripts to sfjuocekr thread below.
http://forum.xda-developers.com/showthread.php?t=835746
http://forum.xda-developers.com/showthread.php?p=9183483
Summary:
1) Download Paul's Visionary+ tool (I have used version r12) (google removed this app from market) so You will have to download it from Paul's website.
This tools enables root and removes new HTC protection.
2) Install engineering version of HBOOT to get S-Off (HTC bootloader, something like BIOS for Your PC)
This step is optional and it's not required in order to flash custom ROM's on Your DHD but gives You more freedom with Your device.
3) Install custom recovery image (recovery is special program which is invoked from HBOOT
in order to flash ROM onto Your device.
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/h...722/10-nov-r12-test-visionary-one-click-root/ or download it from here http://forum.xda-developers.com/attachment.php?attachmentid=447543&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Time for next step!
2) Install engineering version of HBOOT to get S-Off
2.1) Download sfjuocekr DHD script for flashing HBOOT from here
http://forum.xda-developers.com/showthread.php?t=835746
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory. Rename DHD-smart folder on Your SDCARD to DHD.
2.3) Run Terminal Emulator
2.4) Type su
2.5) Type "sh /sdcard/DHD/check
(Please be aware that You have to type "sh" in front of command)
2.6) If everything went OK type
sh /sdcard/DHD/backup
2.7) If this also went OK proceed with
sh /sdcard/DHD/hboot
This command will install engineering hboot which have S-Off turned off.
3) Install custom recovery image
3.1) Since ROM manager now officially support's Desire HD, we will use it to download and install custom clockwork image.
3.2) Run android market app on Your DHD and download and install ROM Manager app from market.
3.3) Download and install ROM manager.
3.4) Run ROM manager and select first option (Flash ClockWorkMod Recovery).
3.5) Wait until ROM Manager say's that installation went successfully (Current version of ClockWorkMod is 2.5.1.3)
3.6) After installation tap in Rom manager option Reboot into Recovery to test that everything went well.
3.7) DHD should reboot in clockwork recovery manager.
Enjoy.
This afternoon I've done what you describe in your guide and can say that everything works fine on my DHD !
Another Desire HD free from chains
Alright this probably sounds disgustingly noob but my phone isn't going into bootloader mode x_x. I've rooted the phone and followed the S-OFF procedure and no luck... Any ideas?
EDIT: Don't worry issue resolved. I had to end up using adb shell reboot bootloader. It's still a bit weird though, as to why I can't do this without adb...
Did You manage to install clockwork successfully?
zexbig said:
This is complete guide for all HTC Desire HD owners who want's to root their devices and install custom recovery image.
(I hade run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
Enjoy.
Click to expand...
Click to collapse
known issue : can't remember the app, double-twist I think, it auto mounts SD card. Do you have that? Deselect or uninstall.
Yup looks like it. It's saying ClockworkMod Recovery v2.5.1.2. The only issue is, I can't select any of the options lol
EDIT: don't worry also solved that
Just another question though, using NANDROID am I able to backup my current ROM? I'm with Vodafone australia and I want to be able to restore this ROM (for warranty purposes).
crypticc said:
known issue : can't remember the app, double-twist I think, it auto mounts SD card. Do you have that? Deselect or uninstall.
Click to expand...
Click to collapse
Hmm probably something which come with original HTC ROM, I didn't install anything similar to that. But will double check..
Sylpher said:
Yup looks like it. It's saying ClockworkMod Recovery v2.5.1.2. The only issue is, I can't select any of the options lol
EDIT: don't worry also solved that
Just another question though, using NANDROID am I able to backup my current ROM? I'm with Vodafone australia and I want to be able to restore this ROM (for warranty purposes).
Click to expand...
Click to collapse
Backing up current ROM and restoring is primary function of nanodroid
zexbig said:
Backing up current ROM and restoring is primary function of nanodroid
Click to expand...
Click to collapse
Haha just making sure . I didn't want to lose my current ROM because Vodafone doesn't honour warranties on phones that have been modified in this manner.
Also I forgot altogether to say thanks lol! Thanks for the simple and straightforward guide
Hi, Does anyone have 10/Nov r12 test: VISIONary + one click root and can send it to me? I can't seem to be able to download it anywhere! Pages are down
clockwork installed can't select
HUGE thanks for writing these instructions. They worked perfectly.
rolphez said:
Hi, Does anyone have 10/Nov r12 test: VISIONary + one click root and can send it to me? I can't seem to be able to download it anywhere! Pages are down
Click to expand...
Click to collapse
Here you have the VISIONary r13, I've rootet successfully with this version.
just followed the guide and im backing up my phone now. Thanks very much.
help
3.5) Download test clockwork image from
and put it in C:\android-sdk-windows\tools\ directory.
3.6) Reboot Your phone into bootloader (Turn off phone, and press VOLUME DOWN and HOLD IT, and it the same time PRESS POWER and hold it until You get bootloader screen.
Then scroll with Volume down button on to fastboot and press power, connect USB cable and wait until android fastboot interface is installed.
3.7) Run cmd and cd to C:\android-sdk-windows\tools\
3.8) type
fastboot flash recovery clockwork.img
3.9) If everything went OK You will get following message:
C:\android-sdk-windows\tools>fastboot.exe flash recovery clockwork.img
sending 'recovery' (4914 KB)... OKAY
writing 'recovery'... OKAY
3.10)This means that You are almost finished. Type
C:\android-sdk-windows\tools\fastboot.exe reboot-bootloader
to reboot Your phone in bootloader mode.
When You are back in bootloader mode select recovery and phone will reboot in Clockwork recovery mode, since DHD does not have optical trackball just scroll 3 times trough menu (just press volume down button until You get message "back menu button enabled".
Enjoy.[/QUOTE]
hi
thanks for the guide.
done all the steps upto 2 everything good
cant get the step 3 , can you explain more deeply.
downloaded all the files , kept on my pc . do i need to move andriod -sk folder to sd and then rebot my phone . as you said to boot in bootloader but wen i press and hold power and volume down nothing happens
need help plz
another question how can i keep my original rom backed up , with which app?
I also cant get into the bootloader by pressing volume down when powering on. Also tried through shell (I think?, is the commands 'su' and then 'reboot bootloader'?) and got a 'not permitted'.
solved
I had to end up using adb shell reboot bootloader
its backing up my phone now
than everybody
where the backup will be saved , name of the files , so i can save them . and i f anything go wrong how to restore the original files?
help
after doing step one can i remove Visionary+ from phone?
any pros of keeping it?
You can remove visionary, only cons is that visionary have unroot option if You want to revert back this maybe usefull.
Sent from my Desire HD using Tapatalk
OP
please help me out here:
i always get this from cmd:fastboot not recognized as an internal or external command and nothing happens! any ideas please.
thank you
**NOTE** I just copied this over from www.rootmydroid.co.uk where i published it first. It is here for ease of access **NOTE**
So, recently i have found myself having to root a couple of HD's for friends..
Subsequently i discovered that the information on the topic is pretty ambiguous, so in this guide i aim to make everything that you need to know clear and put all the files you need all in one location.
So here goes..
**This is a risky process. I nor anyone on the rootmydroid team will accept any responsibility for anything that may happen to your device.**
**It is also worth keeping a "safety net" just in case. I advise heading over to www.shipped-roms.com and under the alias "ACE" find the RUU that matches your current software number, i.e 1.32.xxxxxx**
**To make life easier, download the following apps from the market:**
* conectbot
* ES File Explorer
* ROM Manager
1) Make sure that your software version is 1.32.xxxxx or you will not be able to root!
It contains a new version of HBOOT that breaks root and standard S-OFF.
2) Download [email protected]'s visionary root tool
(download at the end of post)
3) Install it on your HD
Plug your HD in to your PC and select "Mount as disk drive". It should then appear on your PC and you can proceed to drag and drop the "visionary.apk" onto the root of your SD card (not in any folders). Alternatively, you can do it OTA via dropbox.
4) Run it and enable "Set system r/w after boot" Then click "Temproot Now" and wait until it is finished.
5) Once it has finished click "Permroot Now"
Your DHD will automatically reboot, do not worry.
To determine whether this worked or not, open up connectbot and on the drop-down menu on the bottom left corner select "local" login as a whatever you like, for example "rootmydroid" and then type "su" then hit enter. If a "#" comes up, then the rooting process was successful.
Right next up, install the "Engineering version of HBOOT" (hacked).
**WARNING** This process is inherently risky. Ensure that you follow these instructions TO THE LETTER, or you will end up with a fancy paperweight. **WARNING**
1) Download sfjuocekr 's DHD script for flashing HBOOT from the end of the post
2) Unzip it and copy it to your SD card. Ensure it is on the root of your SD (not in any folders) Note that it will come in two folders "DHD-Smart" and "DHD-Dumb" from my experience, rename the "DHD-Smart" folder to "DHD".
3) (After unplugging your device) Run connectbot in local mode just like earlier, and type:
* su (then hit enter)
* sh /sdcard/DHD/check (ensure that you type "sh")
* (Provided everything went ok) sh /sdcard/DHD/backup
* (If this also went ok) sh /sdcard/DHD/hboot
The script should then install the engineering version of HBOOT and achieve S-OFF.
Woop, everything risky is pretty much done for now. Now we can sit back and not be too tense whilst we install a custom recovery image. Luckily this is made easy via ROM manager (which you should already have installed if you followed my instruction).
1) Run ROM manager and select the first option "Flash ClockworkMod Recovery"
2) Wait until ROM manager says that the process is complete (Somewhere along the way a superuser request may pop up asking for permission. This is fine, just click allow.)
3) After installation select the option "Reboot into recovery" to ensure that everything went ok (From my experience this does not actually take you directly to recovery. From the screen it takes you to use the volume keys to scroll and select "Recovery" then use the power button to select.)
4) Your DHD should then reboot into ClockworkMod recovery
Next up is installing a custom ROM. To do this find the ROM that you like the most from www.xda-developers.com . I recommend either LeeDroid or AndroidRevolutionHD.
1) Download the ROM of your choice and place it on the root of your SD card.
2) Reboot into recovery
3) Go to "Nandroid" and perform a backup
4) Once the backup has completed select "wipe data/factory reset" then "wipe cache partition"
5) Go to "Install ZIP from SDCARD" and select your ROM from the list
6) Wait for it to finish installing
7) Once completed, go back and select "Reboot" at the top of the list (Note that the first boot may take up to 20 minutes, so do not be alarmed. Whatever you do, do not panic and pull the battery half way through the boot or you WILL brick.)
Voila! You are fully rooted, have S-OFF and have flashed a custom ROM!
If at any point you need help please come to our live help at: http://bit.ly/g776Yz
Or feel free to contact me at: [email protected]
Android001
Links for files needed:
Visionary
HBOOT Script
Props to [email protected] for his awesome "visionary" app and sfjouecker for his equally awesome script.
3 topics below yours... check my sig
These guides just pop up like mushrooms in a rainy season It is better for new users to have one or two alternative methods, but too much is too much.
Sent from my Desire HD using Tapatalk
wid0w said:
3 topics below yours... check my sig
Click to expand...
Click to collapse
Not to mention the sticky at the top of the thread
Like the work you do for us with little Android experiance jkoljo.
After one year use of HD2 I went to DHD and realy like Android
Regarding this: "3) Go to "Nandroid" and perform a backup"
Is Nandroid a part of Rom Mangaer boot meny or do I have to install it separate?
audiavant said:
Like the work you do for us with little Android experiance jkoljo.
After one year use of HD2 I went to DHD and realy like Android
Regarding this: "3) Go to "Nandroid" and perform a backup"
Is Nandroid a part of Rom Mangaer boot meny or do I have to install it separate?
Click to expand...
Click to collapse
It may appear as either "Nandroid" or "Backup and Restore" i was unsure which it was, as i was not looking at the recovery as i wrote the post.
Sorry mate. Have to close this thread as there is more than one guide floating around.
On of them being this one
http://forum.xda-developers.com/showthread.php?p=11557769
Thanks for the effort.
Regards,
M_T_M
5/12/2011 : Thread marked depreciated due to the recent movement to get the 3.1 Honeycomb update installed. While parts of this tutorial may remain valid, the overall synopsis is not. For those of you that have used this guide I can vouch for the procedure in the thread linked below as a viable option to install the 3.1 update.
Thread to 3.1 Android Update
This tutorial was written for the NooB’s among us (like me) that are new to this stuff and are having a hard time “piecing together” all of the steps. While I am actually a not quite a beginner, NONE of these steps/methods/files have been developed by me. I have simply compiled the procedure in a document that I hope will be useful. With this in mind all the credit belongs to the many individuals that contribute in the XDA Developers forum. I have reviewed many posts by many people and have used all of the information along the way. I have intentionally chosen NOT to mention any specific names for fear that I will leave someone out. If you see anything herein that reminds you of something you posted then it probably is true and you are respectfully THANKED!!!
THIS TUTORIAL WAS CREATED AND TESTED ON THE US WIFI ZOOM. THE PC WAS RUNNING VISTA 32BIT
As a courtesy I will attempt to keep this post up to date with links to revised files. Bear in mind that I performed my upgrade using the original information/links and it was successful. I suggest that since this tutorial is for beginners that you follow the ORIGINAL links to complete the guide. Once you get that far you should have a better understanding of the procedures and be ready to "experiment" by flashing new kernals, recoveries, rom's, etc., using directions found in the corresponding section(s) of the development forum. After-all that is the real reason for most of this stuff anyway. As an example.... there is a 5/3 update below which adds links to newer versions of the Tiamat Kernel and Clockwork Mod. While you could probably just download and use the updated versions of these files in conjunction with this tutorial, I have NOT personally verified this to work. If anyone does try, or if the Dev's want to chime in, please post so that I can update accordingly. Thanks.
5/3/2011 --- UPDATE: Added Links to updated Tiamat Kernel (1.4.1) & Clockwork Mod (3.0.2.8) and added links to discussion threads.
5/11/2011 --- NOTICE: If you are wanting to upgrade to the recently released 3.1 Honeycomb Update than I suggest you re-consider following this guide. The upgrade procedure requires that the device be stock or the update will fail. Furthermore there has not been a Kernel Developed yet that works with 3.1 and some users were complaining about issues with ClockWork Recovery after applying 3.1. See the development section for more information
A) Installing ADB
ADB stands for Android Debug Bridge and simplistically stated will be used to send commands to your XOOM using the keyboard on your PC. In essence your PC will be acting like a terminal. ADB is included in a package known as the Android SDK. The following steps should be taken to insure a successful install of the SDK, therefore giving you access to ADB.1. Install Java JDK : http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.htmla. Download appropriate Java SE Development Kit (JDK) from link above
b. Double click to Install JDK
c. Accept Setup Defaults2. Install SDK Starter Package: http://developer.android.com/sdk/index.htmla. Download SDK Starter Package from link above. There are versions available for Microsoft Windows, Linux and Mac OS X. In case of Windows, both an installer and a zip file are available but there isn’t any need to use the installer as a formal installation is not required. Download the ZIP file.
b. Once you have downloaded the SDK, simply extract the compressed file to a location on your computer. In our case, we have extracted it to the root of our C drive and that makes [FONT="]C:\android-sdk-windows[/FONT] the installation location of the SDK. From here onwards, we shall be referring to this location as the ‘SDK folder’.3. Download the SDK Platform Tools using the SDK Mamager.a. Browse to the SDK folder and launch SDK Manager.
b. When launching it for the first time, it will present you with a window to choose packages to install. The first option begins with ‘Android SDK Platform-tools’. Make sure it is checked, and uncheck all the other packages for now. You can check/uncheck a package by simply double clicking on the package. Again, the only package you want to install is the Android SDK Platform-Tools.
c. Once the process is done, you will have a ‘platform-tools’ folder inside your SDK folder. That folder will include ADB and all its dependencies.
d. Make a copy of the File “fastboot.exe” which is in the “tools” directory and place it in the “platform-tools” directory.B) Install XOOM USB Driver
Just to be sure your XOOM is recognized by your PC it is recommended that you install the latest USB drivers for your system.1. Install MotoHelper : http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Driversa. Download the Driver with MotoHelper from the Link above
b. Double Click downloaded file and follow on-screen instructions to install.C) Unlock Bootloader
Unlocking the bootloader gives you full control over the device so you can flash new Recovery’s, kernels, ROM’s, ETC. THIS STEP WILL DELETE ALL DATA AND SETTINGS ON YOUR XOOM.1. Put XOOM in Debug modea. On the device, go to home screen, press [FONT="]Apps[/FONT] > >Settings>>Applications>>[FONT="]Development[/FONT], and enable [FONT="]USB Debugging[/FONT].
b. Now connect your XOOM to the PC via USB. New hardware installation should begin and it will start looking for and installing the drivers.
c. A prompt should appear that states the drivers were installed successfully. On my PC the AutoPlay Device Options also appeared. I clicked “Open Device to View Files” and saw the device Storage with 27.8 GB free of 28.7 GB.2. Execute ADB Commandsa. Open a command prompt by navigating to the ‘SDK Folder’, Holding the shift key, right clicking on the “platform-tools” folder and selecting “Open Command Window Here” from the popup menu.
b. In the new command window type: adb reboot bootloader and press enter.
c. Wait for the Dual Core screen with “Starting Fastboot protocol support” in the upper left corner to appear and then type: fastboot oem unlock in the command window and press enter. You should see: “To continue, follow instructions on the device’s display…”.
d. Read the WARNING on you XOOM and either Continue Below or Cancel following the on-screen instructions.
e. If you decided to continue then on the XOOM Push Volume Down Button to change the selection from “Cancel” to “I accept” and then press the Volume Up to select that choice.
f. You will be questioned again so Push Volume Down then Volume Up to confirm you want to UNLOCK your device. You will see “Device Unlock operation in progress…” “Formatting UDA”
g. When the operation completes the device will read”Device unlock operation done – rebooting…” and the device will reboot. The windows new hardware “gong” will sound a couple of times during this procedure. After this step when my XOOM rebooted I also saw an “MTP Device” driver Install dialog box on my PC. Unplug the device, and quickly perform the initial set-up. You can “Skip” any steps that will allow you to (like WiFi setup). Just get back to the home screen and continue below:
h. Verify that USB debugging is still enabled and if not re-enable it as outlined above.
i. Re-connect your XOOM to the PC and close any AutoPlay dialog.D) Install Custom Recovery
A custom recovery allows you to flash files created by community developers such as ROM’s, Radios, Kernels, Themes, ETC. It also allows you to perform special tasks such as system backup’s, partitioning, cache wiping, ETC. As of 4/28/2011 the generally accepted custom recovery for the XOOM is ClockworkMod Recovery v3.0.2.5. Clockwork Discussion Threada. Download Clockwork Mod from here: ClockworkMod 3.0.2.5
3.0.2.8 ClockworkMod
b. Place the File “recovery.img” that you just downloaded in the “platform-tools” directory
c. In the previously open command window (if you closed it then re-open as described above) type: adb reboot bootloader and press enter.
d. The device will reboot into bootloader mode (as described above) and when this completes type: fastboot flash recovery recovery.img
e. Check the screen of your XOOM and see: “Flashing StorMgr partition recovery STATUS: - done!
f. Type: fastboot reboot in the command window and press enter.
g. Your XOOM should now boot with no noticeable changes.
h. In your command window type: adb reboot recovery
i. Your XOOM will reboot and an unfamiliar screen will appear. This is the “recovery” program and at this time you should simply verify that you see a reference to ClockworkMod Recovery in the upper left corner of the XOOM. This indicates that our efforts have been successful.
j. When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog.
k. Navigate in ClockworkMod Recovery by using the volume up/down to “move” and the power button to “select”. Look for reboot system, highlight it and hit the power button. Your zoom will reboot normally.
OPTIONAL STEPS
l. At some time later (AFTER YOU ARE ROOTED) to avoid the need to execute ADB commands to enter recovery, I suggest you look for a free application called “Quick Boot”, by Sirius Applications from the market.
m. Once Quick Boot is installed run it and simply select “Recovery” to boot into ClockworkMod. E) Install Custom (Tiamat)Kernel to your XOOM
The Tiamat Kernel we have chosen includes many advantages over the “stock” kernel most notably being support for the SD Card slot which as of this writing has still not been released by Moto. Tiamat Discussion Threada. Download the file “Tiamat_Xoom-v1.4.0.zip” from here: Tiamat Kernel 1.4.0
Tiamat Kernel 1.4.1 A big Thanks to Cam3era who acted as a gunia pig for this....Apparently you are better off flashing the 1.4.0 Kernal first and then flashing the 1.4.1. Details are in the Tiamat Thread
b. Make sure you have an SD Card in your XOOM. Some people are having issues with the system reporting the wrong size of the SD card and it has been suggested that you format your card in another android device prior to using it with your XOOM. Another “trick” was to use a small capacity card. Apparently this may still be a current issue so I recommend you format you card prior to use. I personally had a 1GB Micro SD that I formatted in my Android Phone.
c. Enter Recovery via adb by typing: adb reboot recovery in your terminal window and press enter.
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the Tiamat kernel zip you downloaded above onto the SD Card.
iv. "Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the zip file and select it.
vi. Navigate to “Yes – Install Tiamat_Xoom-v1.4.0.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.e. After the XOOM reboots (this could take a while) check to insure that USB debug mode is still enabled. If not, re-enable it as described above.F) Root the XOOM and Install Superuser APK
Root access is similar to “administrator” privileges and gives you the power to run specially developed programs that take advantage of these additional rights. An example would be a program called titanium backup which coupled with the “super user” privileges can perform backup duties not available in “non-root” environments. The following file was obtained and discussed here: Link
a. Download the file Root_Xoom.zip from here: http://forum.xda-developers.com/attachment.php?attachmentid=579548&d=1303896724
b. Connect your XOOM to the PC (again be sure Debug mode is enabled) and close any AutoPlay dialog boxes that pop up.
c. In the same command window used previously type: adb reboot recovery
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the “Root_Xoom.zip” file you downloaded above onto the SD Card.
iv. Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the “Root_Xoom.zip” file and select it.
vi. Navigate to “Yes – Root_Xoom.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.e. After the XOOM re-boots check to see that you have a new App in the Drawer called “Superuser”.G) CLEANUP
As you become more at ease with using Clockwork Recovery you will use it more and more. There are many more features than can be described here and after all, that is beyond the scope of this tutorial. I highly recommend that you seek out more information about this tool so you can put it to good use. One term you will see used a lot is “wiping”. Wiping does exactly that to a specific partition(s) and/or file(s) thereby insuring that a new installation is “clean” and no “remnants” of prior information exist. The upside to this “cleaning” is that there is less chance of corruption from using older (or incompatible) versions of files or data and the downside is that this “data” may contain useful information such as high scores, completed game levels or even previously remembered passwords. You should learn how to back-up this data using Titanium Backup or another backup application and manually reload it after your upgrade is considered “stable”. This allows you to wipe and thereby insure that any “issues” you experience are not related to “remnants”. So, with this all said, I recommend that you now Wipe your User Data and Cache. Again, if you have not backed up, this will erase and reset things that you may not want erased or reset. Proceed with caution!!!!
a. Enter Recovery via quickboot or adb as described above.
b. Using the Volume and Power Buttons as described above navigate to “wipe data/factory reset” and select it.
c. Navigate to “Yes – delete all user data” and select it. Wait until it says “Data wipe complete”.
d. Navigate to “wipe cache partition” and select it.
e. Navigate to “Yes – Wipe Cache” and select it. Wait until it says “Cache wipe complete”.
f. Navigate to “reboot system now” and select it.
g. Set up your rooted, custom recovery, custom Kernel XOOM!! ENJOY
I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.
Thanks for the kind words!
One step at a time my friend. This was my first attempt at creating a tutorial and I tried to handle the "pictures" with very detailed wording. Embedding screenies into future efforts is on my to do list.
The bottom line regarding this is..... I created the tutorial before I even took my XOOM out of the box and then followed it to see if it worked. While I had some minor issues with the original draft, I believe they have all been taken care of in this final.
I expect that if any issues are encountered, it will involve the SD Card size which seemed to be a common issue for some. I had NO problems with mine.
And, while I'm at it....... I was a little hesitant to include the information on "quick boot". Some members (and I'm taking this off the top of my head right now) had issues using clockwork when it wasn't initiated using the adb reboot recovery command. I seem to recall that there was a difference in this regard between the WiFi and 3G versions. In any case if Clockwork does not seem to be working for you then stick with starting up recovery using adb and NOT Quick Boot. Having Quick Boot available in your app drawer is recommended however in case you ever experience issues mounting the device to your PC.
tritran18518 said:
I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.
Click to expand...
Click to collapse
Thanks
This is exceptionally well done. A tremendous resource. I hope you will keep it up to date. I will refer to it often. Thank you!
I hope this works.....With this it is time to root. Thank you for a great step by step instructions.
This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk
See this tread: Stock Image
I have NOT done this procedure but will follow that thread to see how it turns out.
Someone DID apparently re-lock the device but I don't know if that procedure removes all indications that the device was un-locked in the first place.
cam30era said:
This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
I didn't put this "guide" in the development section because I didn't actually develop anything. Perhaps I should have?
This is an awesome step by step instruction! Good Work! Thanks a lot!
Land Master said:
Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
Click to expand...
Click to collapse
Ran through it yesterday on my father in law's new Xoom, worked great!!!
I was holding out for HTC flyer with pen, or Transformer with keyboard...
But, was impressed and may be going with Xoom now myself.
Thanks so much for the guide, it worked very well and he's happily tethered to adhoc wifi on his droid now, so very thankful as well.
Sent from my SCH-I500 using XDA App
Awesome tutorial! Now I have a place to point new users to when they hijack my thread
bigrushdog said:
Awesome tutorial! Now I have a place to point new users to when they hijack my thread
Click to expand...
Click to collapse
Thanks BRD for everything you do. I added links to the 5/1 files but also a disclaimer. Your thoughts on this would be appreciated.
Feedback
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point?
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?
cam30era said:
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point? Corrected This THANKS!
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?
Click to expand...
Click to collapse
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.
Land Master said:
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.
Click to expand...
Click to collapse
I'll try flashing 1.4.0 and then back to 1.4.1 and let you know. Thanks for the suggestions.
OK. I just tried to flash 1.4.0 from CWM. Got following error message:
E:Error in /sdcard/tiamat_xoom-v1.4.0.zip
(status 0)
Installation aborted.
I'm getting help now on the Tiamat thread. I'll keep you posted on how this gets resolved.
Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.
cam30era said:
Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.
Click to expand...
Click to collapse
Very glad you got it sorted. I added your suggestion to the OP.
mbowe said:
It worked very well and he's happily tethered to adhoc wifi on his droid now.
Click to expand...
Click to collapse
Ad-hoc? A stock xoom doesn't support this but a rooted one can now? Didn't realize that had been enabled.
hi,
can i install the kernel and the custom recovery without root ?
i thought i need to have root first....
=========================================================================================
=== Device: GT-P5100 (Galaxy Tab 2, 10.1", 3G model)
=== Description: Safe stock ODIN image, recovery and root
=== Packaged by: cheatman ( xda - http://forum.xda-developers.com/member.php?u=490310 )
=== Stock ROM version: P5100XWALD7
=== Build date: 07 June 2012
=========================================================================================
Disclaimer: I am not responsible and assume no liability on how this information is used. This package is provided "as is" without any warranty and does not guarantee any fitness for any purpose.
ONLY FOR GT-P5100 (3G model)!!! Do not flash on any other Galaxy Tab 2!!!
Download the ZIP (large, about 600MB) from here:
=> DOWNLOAD FROM HERE (HotFile)
How to use: Read the readme.txt file or this post here.
On to the safe stock restore process:
1. Make sure you have the Samsung device drivers installed before you begin. If you don't, install them from here:
- 64bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
- 32bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
2. Make sure your tablet's battery is at least 30% charged up before you begin.
3. Make sure you have an external microSD inserted in the device, if you also plan on rooting afterwards. Nothing will be erased from the microSD, there is no need to worry about that.
4. Run procedure to flash back the stock ROM from Samsung (Ice Cream Sandwitch 4.0.3 - P5100XWALD7) from the folder "Step1-Stock". STOP HERE FOR PURE STOCK!!!
5. Run procedure to enable ClockworkMod recovery from the folder "Step2-Recovery". This step is OPTIONAL (only if you want a custom recovery). STOP HERE IF YOU DON'T WANT ROOT!!!
6. Run procedure to enable "root" access from the folder "Step3-Root".
7. Done! Enjoy! Profit!
===============================================================
========== Step 1 - Flashing Stock P5100XWALD7 ================
===============================================================
1. Download the file from the link above.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "PLATFORM_P5100XWALD7_482645_REV02_user_low_ship.tar.md5" file.
8. Press "PHONE" button and select the "MODEM_P5100XXLD7_REV_01_CL1128355.tar.md5" file.
9. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
10. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA", "PHONE". DO NOT CHECK RE-PARTITION!!! NEVER!!!
11. Click the big "Start" button and WAIT. Be patient!!! The process takes about 3-4 minutes but can take longer.
12. Do not power down the tablet while this takes place. Do not shut down your PC. Do not touch anything! Just wait! Get a coffee or something...
13. After full flash the tablet will reset automatically.
14. Congratulations you are now safely back to stock P5100XXALD6.
15. There is no need to flash the bootloader and CSC. Do so at your own risk.
===================================================================
========== Step 2 - Flashing ClockworkMod Recovery ================
===================================================================
1. Download the attached recovery file "p5100-recovery.tar.md5.zip" and extract it.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "p5100-recovery.tar.md5" file.
8. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
9. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA". DO NOT CHECK RE-PARTITION!!! NEVER!!!
10. Click the big "Start" button and wait a few seconds. Flashing recovery.img is super-fast!
11. After recovery flash, the tablet will reset automatically.
12. Congratulations you are now running recovery for your tablet.
13. Note: Internal SD is not working with this recovery, you must use external microSD cards to load up ZIPs.
14. You can also download and extract the kernel and flash it also on "PDA" if you want a rooted Kernel
=========================================================
========== Step 3 - Enabling root access ================
=========================================================
1. Download the attached file "CWM-root-P5100-v1.zip".
2. Copy the "CWM-root-P5100-v1.zip" file to the external microSD card.
3. Shut down your tab.
4. Insert the microSD in the tablet.
5. Hold "Power+Volume DOWN" physical buttons on your tablet to initiate recovery mode. It takes a while to start up recovery (10-15 seconds) so be patient. Try not to press too hard on the buttons as it does not help at all (takes same amount of time :-D)
6. Use the "Volume UP" and "Volume DOWN" buttons to navigate (select options) and the "Power" button to select. Don't HOLD the buttons, just press them (like a click or something).
7. Select the option to install ZIP from sdcard.
8. Navigate to where you copied the "CWM-root-P5100-v1.zip" file and select it.
9. Wait for the operation to complete.
10. Navigate back and select option to "Reboot system"
11. Congratulations you have a fresh stock ROM with CWM and root ready to go!
12. Enjoy
=======================================================================================
Thanks and greetings go to:
- Galaxian-Soup
- nycbjr
- All others who help and bring value to the XDA comunity!
Peace and have fun!
C.
Reserved!
Looking for mirrors. This is a very large file!
Thanks.
Ah damnit lol this was almost what i was looking for. I need the one for the wifi version.
Do you think the recovery would be the same? Thats the only part i really need lol.
Nvmind i see its all in one file lol
Recovery is in an independent folder, you don't flash the initial zip lol.
Anyway, the recovery and root steps should apply to p5110 as well.
Cheers,
C.
Thank you for all the hard work. I'm sure my Willy nilly ways will require me to use this
Sent from a note on fire in the middle of the sea
Hi,
I see that in your instructions for flashin stock do not use file "BOOTLOADER_P5100XXALD6_365113_REV02_user_low_ship. tar.md5" which is otherwise included in the package, does that mean that it did not necessarily use one?
When it is necessary to use that file?
Thanks.
Updating the bootloader is not required.
Playing with bootloaders is very risky and dangerous in general (can permanently brick tab).
Bootloader is responsible for the download mode. If you can access it and flash using odin, there is no need to mess with it. Upgrading it may result in a locked boot mode, meaning you can't flash custom stuff anymore.
I included only the required files and steps so you guys don't have to look for the right combination.
Peace,
C.
Thank you for the file sir oh sir.
Rapidshare mirror
Sized at 492.65MB, i recompressed the file using 7-zip to cut off the size a bit. It is below 500MB, meaning it's Dev Host friendly.
Code:
stock-safe-p5100-4.0.3-v1.zip 2E5566F2311BAD666A8CFD9674AEE0A5
stock-safe-p5100-4.0.3-v1.7z 946AAC1EDE408FFCA48BAF592AC3F92C
Step1-Stock
MODEM_P5100XXLD6_REV_01_CL1128355.tar.md5 07EFC235DC6989D50C9321076EDCDFC1
PLATFORM_P5100XXALD6_365113_REV02_user_low_ship.tar.md5 8186B1660ED2D4C1752336014ED047FD
Step2-Recovery
recovery.tar.md5 16AFDD2FEDBD8476521D9C144C823023
Step3-Root
CWM-root-P5100-v1 4D2E472F0C0A640F4170B9500F39FCAC
Can someone please confirm the hashs?
I rooted my Galaxy Tab 2 10.1 WiFi GT-P5110 using the manual and it works fine!
Thanks for the manual
Sent from my r00t3d GT- P5110 using XDA Premium App
Updated new version of the stock image.
Thanks for this find go to our friend "zi0m3k" (cheers, mate!)
C.
How did you capture the stock recovery from the device? I would like to do the same from my GT-P5113, but (of course) one has to flash CWM first to get access, and that overwrites the recovery.
Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.
cheatman said:
Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.
Click to expand...
Click to collapse
I know that the final goal is to overwrite the recovery to get the benefits of CWM (e.g.). But if you want to save the *stock* recovery first, you need to capture/dump it from the device somehow before flashing (correct me if my logic here is incorrect).
Also, yes, I know a good way to dump it is with "dd", but one needs root to do that (I tried for the hell of it, to see if there was non-root read access, but alas, no).
I think you have hit upon my question regarding root: did you root the tab without flashing CWM? If so that will allow "dd" to capture the stock recovery, yes. If you used CWM, that you overwrote the recovery, and you would not have been able to save the stock recovery in that case.
I have not found a rooting method for the GT-P5113 that does not involve flashing CWM, so I cannot figure out how to same my stock recovery, which I would like to do before flashing CWM (and thereby losing the stock recovery forever).
I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.
cheatman said:
I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.
Click to expand...
Click to collapse
Hi, yes, that's exactly right - I wanted to know how you got elevated rights in order to use dd for this.
I really want the recovery image from *my* stock tablet - not one off the net.
Could you private message me, if you are uncomfortable talking about it here. I am well-versed in Linux (I've done kernel development, I'm part of the Gentoo Linux dev team, etc.), so I am no stranger to Linux. I know there are exploits now and then, but they are not usually trivial. If you found a new one for the current kernel, then I'm impressed, and please do tell. If you found the exploit somewhere on the net, can you send me a link?
Thanks, Joe
Well, I must admit I actually took my time thinking whether I should actually write a reply :-D
However, my main concern is having to write a lot to explain stuff, but considering you are a kernel dev, this should be easy peasy. In short, I didn't force my way in, I just *convinced* the system to let me in. It's an inherent problem of Android, in fact:
1. Extracted the boot.img and unpacked it.
2. Replaced the adbd binary in the ramdisk with an unsecure one.
3. Repackaged and flashed using ODIN.
4. Used adb root to get into the system, the *regular* way. Once adbd lets
5. Installed su and superuser.apk.
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists). Any and all Android devices that use this layout (boot.img) can be rooted this way. Sorry to disappoint you about the exploit, but I am no *real* dev. I just know my way around :-D
PS: You can get the latest boot.img I did for this purpose here
Hope it helps with your recovery dump,
C.
cheatman said:
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists).
Click to expand...
Click to collapse
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.
LavaJoe said:
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.
Click to expand...
Click to collapse
I would be eternally grateful if you could post the stock rom for the 5113 (including stock recovery) if you can. I would settle for just the stock recovery in flashable form via odin etc.
A read through Samsung's kernel source reveals that the governors are already coded into the kernel (install voltage control and you can switch between governors and schedulers at will).
It looks like the set stock speed on the 10.1 5113 is 1008MHz.
Does anyone know how/where in the kernel overclocking is programmed?
The source also looks pretty comprehensive for the tablet and apparently is very similar to that of the 7" tab. I imagine it wouldn't be too hard for a veteran coder to fix this up for the 10" users.
I haven't coded in years and I'm not familiar enough with Android to do anything but attempt to compile the source from Samsung.
Hi,
Does this work on P5100XXLD6 ?
Android version 4.0.3
Thanks