Related
So far, this is going to be a guide for noobs. Please read through this, and ask any questions that you have. This has been compiled from different guides around XDA, and information has been stripped that does not relate to our phones. More will be put up here when I find it, and all credit will be provided. This will be from 'duh' to 'didn't know that'. The idea is to provide a beginning to end explanation: Stock Incredible to Rooted with custom Rom.
Topics so far - ADB, Rooting (reflash), Unrooting, Nandroid, Remove/Install Apps, roms, kernels...
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE DOING ANY OF THIS.... REGARDLESS OF WHY. Yadda, yadda, yadda...
**********At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done).**********
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Now, we get USB drivers to work. Some use HTC Sync for drivers, however HTC Sync does not like to play nice with the reflash tool (later on this), so we will use the generic google USB drivers.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.
============================================================
2) Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
============================================================
3) Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in:
cd C:\**your sdk name**\tools (Press Enter)
adb devices (Enter) You should see your device listed
adb shell (Enter) you should see $ in the next line
**After you obtain root**
su (Enter) you should see # in the next line if you are already rooted
**you may need to allow adb shell to run as root. Look at the phone and see if Superuser.apk is asking for your permission to allow adb root access. Click on "Remeber my selection" and select yes.
Now you are all set to run adb commands as root or as a regular user
**Note: for a list of commands that you can type using adb type "adb" in cmd
All Credit for Topics 1 - 3 go to user XDA member nephron. I mostly copied all of his guide, but updated some information on it to make sense for our phones. Also, removed some stuff I didn't see necessary. Please go to the original thread for the G1: http://forum.xda-developers.com/showthread.php?t=532719&highlight=nandroid+guide for a list of further Credits, and for information I've left out. If you like this thread, please donate to HIM
============================================================
4) Rooting your phone - READ THIS WHOLE SECTION BEFORE GOING TO ANY EXTERNAL LINKS PLEASE. At this point, running the UnrEVOked reflash3 tool will root your phone and install a custom recovery. To try to make it really easy to understand, recovery allows you to access your phone to make PERMANENT changes (something we can't do while booted yet), flash custom roms, and save your sorry little @$$ if you do something that you weren't supposed to
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it), and that you have the Google USB drivers installed (i.e. you read at least some of this post). The first thing we're going to do is:
1) Read this: http://forum.xda-developers.com/showpost.php?p=6875912&postcount=1
2) If you read #1, you already went here: http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
and downloaded the MODIFIED (i.e. changed, not the same, DON'T SKIP THIS STEP) driver and installed it
3) If you read #1, you already downloaded the reflash tool executable
4) If you read #1, you've already done #2, and 3, and this is just a worthless step of me explaining how important it is that you did #1
5) Lets do this. #1,2,3 and 4 were "get ready" steps. By now, you installed the modified driver, went to the webpage and downloaded the UnrEVOked3 reflash tool. HTC sync is also uninstalled. Plug in your phone (normally booted) to your pc and select "Charge Only" when asked how to connect to PC, and click on "remember my selection". Click Done.
6) Unplug Phone from PC.
6a) If you have double twist installed, at this time open the task manager on your pc, and kill doubletwist.devicehelpder....
7) Run the "reflash_package" executable that you just downloaded. Notice the path that it lists and click "install". This will unzip "reflash.exe" and a bunch of other stuff that is needed to the directory that you just noted. Go to this directory (usually the same one where the executable you just ran is) and run "reflash.exe"
8) Plug in your phone.
9) When the program is finished, you should see koush's clockworkmod recovery on your phone's screen and reflash will say that it's done. Congrats, you have root and a new recovery.
If something went wrong, and you're not on koush's recovery and reflash says it's done, don't worry, just re-run reflash. You can run it as many times as necessary. It will not hurt anything AT THIS TIME (this may change later)
10) Koush's recover works a little differently:
a) Vol+ and - scroll up / down
b) the Power button work as a "Back" button, and will turn off screen if you're at the root of the menu. If your screen goes blank, don't read, just hit Power again
c) To make a selection, click the optical trackpad
11) Reboot your phone by highlighting the selection and choosing it
For the most part, these instructions were written from memory, but all credit goes to UnrEVOked, Shadowmite, and anyone that they've given credit to in original links.
============================================================
5) Unrooting - I didn't want to re-invent the wheel, so I'm posting an external link:
http://androidforums.com/all-things...ideo-howto-unroot-incredible-downgrading.html
Just follow the instructions. Credit goes to the OP. If this link ever goes to a 404, pm me and I will find another link with instructions and update this. Also, if you don't understand something, just ask in this thread, someone will answer (maybe even me ).
============================================================
6) Whats is a Nandroid Backup?
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
Nandroid Backup is a tool allowing your Incredible that has koush ClokworkMod Recovery to create a full system backup and restore it, which, when flashing and testing different roms can be very useful.
A) Creating a Backup using Nandroid
Boot up your phone in recovery (Turn off, then turn on while holding Vol- and Power. Press Vol- once to highlight recovery, hit Power once to go into it)
You will now see your new koush recovery
Scroll down (Vol -) to "nandroid" and select it (press the optical button in)
"Backup" will be highlighted. select it
Let it work, it might take a while for a full system backup
Once its done, your backup is complete and is saved on your sdcard in the "clockworkmod" folder. Normally it's stored in the "nandroid" folder, however our Recovery does things a little differently.
B) Recovering to Your Nandroid Backup
Make sure u made a backup and its in the clockworkmod folder on your sdcard
Boot up your phone in recovery (Explained Above)
Go into "nandroid" in the recovery (also explained above)
Select "restore backup" and select from the backups you have (if you have multiple) that you want to restore; this will do a simple, "restore all" of your latest nandroid backup
:OR:
Select "Advanced Restore", choose from the backups that you have on your SD card, and then what you want to restore. You can individually restore "system", "data", "cache", etc....
In "Advanced Restore", i have not seen a way to restore multiple options (cashe AND system, etc...) Koush, am I missing something?
Let it work
Once its done, restore more options through the Advanced Restore menu, or reboot your phone and your selections will now be restored!
============================================================
7) Remove Apps
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Go into Clockworkmod Recovery (With phone turned off, Vol - + Power, then Vol - to select recovery, then hit Power)
2) Select "partitions" from menu, then select "mount sytem" You can also "mount sdcard" if you want to back apps up to sdcard
3) Connect Phone to PC
3a) Open a command prompt and navigate to your sdk\tools directory
3b) Type: adb remount (it shoud return successful)
4) Open Adb Shell on your pc (Type: adb shell)
It should automatically show #, otherwise type "su"
Type:
cd /system/app (enter)
5)Type ls (this will show you all of the stuff in the /system/app directory)
6) To "delete" apps, type the following:
/system/bin/mv Your_APP.apk Your_APP.apk.bak (i.e. CityID.apk CityID.apk.bak). If you want to clear up space on your internal storage for whatever reason, you can replace Your_APP.apk.bak with /sdcard/Your_APP.apk.bak (this will move the app to the root of your SD Card instead of just change it's name)
If you don't get errors, you're done.
*This does not delete apps, but changes their file type so they will not show up as an app, in case you want to get them back at any time later you still have them and don't have to frantically post threads on XDA asking for them.
============================================================
8) Install Apps to /system/app
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Place your app you want to install into the root of your sd card (this is easiest)
2) Go into Clockworkmod Recovery (Explained in 7)
3) Mount system and sdcard under partitions (Explained in 7)
4) Connect Phone to PC
4a) adb remount in command prompt (should sow successful) (again, in 7)
5) Open Adb Shell on your PC
6)
IF NOT at #, type "su" to go from $ to #.
Type:
/system/bin/mv /sdcard/Your_App_Name.apk /system/app/Your_App_Name.apk
7) If you don't get errors, you're done. You can unplug phone, and reboot
============================================================
9) Flashing Custom Roms
Download a ROM that you want to try. One of the roms from here are a good starting point: http://inc.sodpit.com/. They are mostly stable might get a few random reboots.
Steps:
1. Download Rom of your choice
1a. Right now, there might be two ROM types, a nandroid backup and an update.zip type file. For right now, I recommend sticking with the update.zip kind. These instructions are meant for it, but I just want you to make sure you know which type it is before you try to flash it.
2. Copy and Paste the downloaded file onto sdcard. Make sure it is not in any directory's of SD card, just on the sdcard (the "root" of it).
3. Verify it's there using Astro or some other File Manager just to be safe.
4. Download and Run Titanium Backup from the Market if you haven't already. (If you don't have it, get it, it's must have for root users.)
a. Select Menu, Batch, Backup user apps. (in Titanium Backup)
b. let it run, this will take some time.
5. When that's done open your command prompt, navigate to your sdk\tools directory, and type "adb reboot recovery" (Not within adb shell, but in command prompt in that directory. I'm not going to explain how to do this because it's already explained above. Also, if you're flashing roms then you're already familiar with it, or maybe you shouldn't be flashing roms ).
6. Do "Wipe data/factory reset" and "wipe cache partition" in Recovery **This WILL WIPE your phone**
7. Select "install zip from sdcard", then select "choose zip from sdcard", then select the name of the zip you want to install.
8. When that's done reboot your phone, once your done setting up all the settings, download titanium backup from the market again, and set that up.
9. In Titanium, Select Menu, Batch, Restore User apps.
After that's done you'll have all your apps that you had before, data included, with a fresh new rom to try out. Hope this helps!!
All credit for these instructions goes to tcbert2010, they were suggested to me, and I liked them. I modified them a BIT, so they make more sense to me and hopefully to you. See post #2 in Original Thread = http://forum.xda-developers.com/showthread.php?p=6953608#post6953608
============================================================
10) Installing custom kernels
I'm only mentioning Hydra's kernels. I'm running the Undervolted, NOT overclocked kernel with wireless N to preserve my battery to get more life out of it
**Taken from website's FAQ**
Q: So how do I install the kernel?
A: First step is to either download the kernel zip file straight to your phone, or download it onto your computer and put it on the sdcard of your phone. Next you turn the phone off hold volume down and power at the same time. When the phone is in HBOOT wait a few seconds for it to initialize then hit volume down once and then power to boot into Clockwork recovery. Once in clockwork recovery you want to select "Install zip from sdcard", then "Choose zip from sdcard". You will now see a listing of files on your sdcard select the kernel zip you downloaded, or if you downloaded strait to your phone go to the Downloads folder and select the kernel zip file. The kernel will now install to the phone and once it's done it will say install complete. Now you can hit the power button once to return to main menu and select "reboot system now" . Your phone will now reboot with the new kernel.
***
Go to: http://hydrakernel.net/ to download the kernels
Please read: http://hydrakernel.net/faq.htm to educate yourself. It's worth it.
Credit to EJHEART for the wonderful kernels! Where are my 2.2 kernels EJ ?
============================================================
Again, if you have suggestions, requests, or whatever please post or PM me.
PM Me if I missed giving someone credit. PLEASE!!!
reserved
reserved for future.
Reserved
reserved for future
Great thread topic... reserved for future use
Updated
Updated with Reflash instructions.
dreamersipaq said:
Help I'm stuck at waiting for system to settle
check these common issues:
- You switched your driver to the one from this post? It's NOT identical to the SDK one.
- You don't have any usb applications that might be taking focus while we are working with the phone right?
- Is the SD card present in the device?
- You did give su permenent access when you allowed it in superuser right?
More to come...
Click to expand...
Click to collapse
Good start, iPaq! I just want to plug Linux AGAIN. I had zero problems using reflash for linux and using Gparted in Ubuntu/Debian/Linux Mint mint means one can do all kinds of things that will become helpful very soon if not already (e.g., manipulate ext and swap partitions on the sdacard!). Aside from linux being Android's native file system, using a Linux distro just makes 110% good sense if you plan to do any developing for the DI/Android. Why poeple struggle so much with Windows when Linux is free is beyond me
2 cents deposited!
Additional items to add
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Great topic
Sent from my ADR6300 using XDA App
...
jdmba said:
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Click to expand...
Click to collapse
1) - Will update soon
2) - I BELIEVE that this works:
1) Go into Clockworkmod Recovery
2) Mount Internal Storage under partitions
3) Connect Phone to PC
4) Open Adb Shell on your pc
Type:
su (will change to #)
cd /system/app
mv CityID.apk CityID.apk.bak
you're done.
Not in front of my phone at this sec, but if mv does not work, try
busybox mv CityID.apk CityID.apk.bak or
/system/bin/mv CityID.apk CityID.apk.bak
*This does not delete it, but changes the file type so it will not show up as an add, in case you want to get it back at any time later.
If I'm wrong please correct me.
3) The easiest way to update recovery at this time is through Koush's Rom Manager. However, at this time I've read somewhere that it's not persistent. Let's give this a few days.
Updated
First Post Updated.
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
qwho said:
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
Click to expand...
Click to collapse
Take this opportunity to flash up to HBOOT 79, wipe, and re-root. Start fresh. Re-reflash w/unrevoked2. Alles in Ordnung! At least, that solved all of my problems. Start with the big headache to avoid later headaches. Once you have a nandroid of a "proper" root, you'll never have to do the annoying initial root again.
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
qwho said:
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
Click to expand...
Click to collapse
Exactly. Doing will wipe out all userdata, everything not stored online, on your card, or on internal disk. It's really the best way to go, to start fresh and remove all the little variable piecemeal rooting has placed in your path to date.
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
qwho said:
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
Click to expand...
Click to collapse
Just down this, run it in Windoze, and before it tries to flash (you don't need your DI connected!), go into your AppData/temp directory, find the ~142mb rom.zip file, rename it to PB31IMG.zip, put it on /sdcard root directory, boot into bootloader, let the card/file get picked up while holding down-volume, ok the flash, no need to ok the reboot, then boot into to recovery and proceed with adb shell/rooting process one
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
sanchagrins said:
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
Click to expand...
Click to collapse
Not sure what you mean. Go into Hboot, and select recovery. When Koush's recovery loads, use Vol- to highlight "nandroid". Click the optical button in, and you'll enter another menu. Select the first option, which should be highlighted by default, which should be "Create Backup" or "Backup Device" or something like that.
Let me know if that works.
When I go into recovery the only options I get are:
Reboot System now
Apply sdcard: update.zip
Wipe data/factory reset
Wipe Cache partition
----------------------------------
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
sanchagrins said:
When I go into recovery the only options I get are:
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
Click to expand...
Click to collapse
You can't install anything to recovery that will stick until you get root via procedure 1, then reflash with unrevoked 2. Sounds to me like you've gotten ahead of yourself
I have put together some steps to take your fresh KA6 2.2 Official update and add Root and ClockworkMod Recovery. It may look hard, but should only take a couple minutes.
This is without ODIN or ROMS.
Steps:
0. Have yourself a T-Mobile Vibrant and PC Running Windows.
1. Use SuperOneClick (latest) to root phone. When you run the application, click the first button on the left and wait for the process to complete. Details will be scrolling in the middle window.(http://forum.xda-developers.com/showthread.php?t=803682)
2. Use a file manager (ROOT EXPLORER) or adb with root access to mount /system/ and remove bloatware (SLACKERRADIO and AMAZONMP3 and such) from /system/app/
2a. TOTAL NOOBS: Get SUPER MANAGER from the market (FREE). Then grant it root by going into SUPER MANAGER and selecting File Manager > [Menu BUTTON] > Setup > Enable ROOT function. Then go up levels, the top button on the file manager which will take you up a directory, until you get to / and scroll to the bottom and select [system]. Then select [app]. Then click [Menu BUTTON] > Switch System to R/W and press R/W. Scroll down and long press the slackerradio.apk to delete. You can do this too amazon market to delete and other useless apps.
3. YOU NEED STEP 2 TO DO THIS STEP! Install Busybox from Market and run Busybox Installer to ensure its properly working and the latest is installed.
4. Run SuperOneClick again to place phone into shell root ADB (Second button from the left). Allow the process to run and then a pop up will say something about rebooting the phone. DO NOT DO THIS, continue on to the next step.
5. While in shell root from the previous step, run (3e) to (2e) modified recovery script. The instructions are simple. Download, unzip, and run the batch file found inside. This is ran from the COMPUTER NOT YOUR PHONE. Use the menu system to complete and then reboot as recommended. (http://forum.xda-developers.com/showthread.php?t=833423).
5a. NOT NOOBS: you can copy over the recovery yourself to /system/bin as mentioned by some commenters. If you do not know what this is, then ignore it.
6. Remove any update.zip files from /sdcard/ and also remove any ClockworkMod directories using your favorite file manager or by mounting to a computer with a wire and activating the drive for My Computer. This is the internal one, not external.
7. Use ROM MANAGER from market to install ClockworkMod Recovery and reboot. This is free to download. When you launch, select the top item to install the recovery and then a menu will pop up to choose the phone you have. Happily select Vibrant. Once that's done, select reboot into recover right below that.
8. Re-install packages and it should reboot. You can navigate the menu using VOL UP AND DOWN and power to select.
9. Re-install packages again and it should boot into Clockwork Recovery. It should change form BLUE TO GREEN
ALL DONE.
That should do it for ya! Let me know if it worked out. Please follow all steps and don't cut corners.
Should you need to get back to ClockworkMod Recovery, you can use "adb reboot recovery" and re-install packages, or reboot into recovery with ROM MANAGER.
Edit Rev.a: added a step (6) Made the instructions more precise and added additional steps to clear up some confusion.(1-22-11)
Edit Rev.b: Added step 2a from request. root explorer is not free so use super, that works too. (1-24-11)
Edit Rev.c: Added more detail to the steps and added supplemental info for replacing the recovery with the modified one. (1-27-11)
Edit Rev.d: Super1Click has updated, so latest? works.
Side note: I do step 4 because from my experience, I had trouble getting the modified 3e script to get root. Figured might as well just give it root to begin with.
Side note: Yes I am aware that there are other methods and different ways. This was the noob way for me to convey it to the masses. I still do appreciate all feedback regardless of what it is. Thanks!
jmcghee1973:
***For kicks you can do your 2.2 KA6 update the download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.
***For kicks you can do your 2.2 KA6 update then download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.
Not to hijack your thread...
Yea I know, but I wanted to find a way without ODIN.
added ur blurp
Reinstalling packages does not seem to work for me. Every time I click it and it reboots it keeps going into the samsung recovery menu... Help?
Does it give an error for signing or just looks like its working then reboots?
Looks like it works and then reboots
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/
Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card changed directories with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager
Nothingness00 said:
Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card stopped working with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager
Click to expand...
Click to collapse
Tried that, still can't get into clockwork recovery...
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/
I would highly suggest doing that step. The system is full to begin with. Use Root Explorer and grant access, then mount system into r/w and remove the stupid stuff. You should do this to get Busybox on (AS IN BEFORE YOU INSTALL BUSYBOX)
What does busybox do?
jmoreau10 said:
What does busybox do?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/BusyBox
ITS ESSENTIAL
Got it working man, thanks.
Awesome! Good to hear. This is my first tutorial and I'm stoked that its working well for others.
I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.
dsilver981 said:
I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.
Click to expand...
Click to collapse
4. Run SuperOneClick again to place phone into root shell ADB
For this step, run SuperOneClick from before, the same you used to root. The second button says "Shell Root". Click that Wait for it to say you have shell root until you reset.
5. Run (3e) to (2e) modified recovery script (http://forum.xda-developers.com/showthread.php?t=833423)
Just download the attachment in the first post and follow instructions. Its fairly simple process. Keep in mind, this may not work unless your phone is shell root from step 4
Thank you Nothingness. Cleared it right up. Worked perfectly.
dsilver981 said:
Thank you Nothingness. Cleared it right up. Worked perfectly.
Click to expand...
Click to collapse
Awesome! Great to hear it! Love them thanks
im a total noob, but im about to try this, wish me luck haha
thoetherguy said:
im a total noob, but im about to try this, wish me luck haha
Click to expand...
Click to collapse
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.
Nothingness00 said:
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.
Click to expand...
Click to collapse
haha, yeah it was easy , thanks...
i chose to start this thread as an educational and informative way of answering simple question so new questions arent repeatedly asked.
first off try to use the search window as much as possible before you post a question, chances aer your question has been asked before, so you will find the answer somewhere.when you do have to post a question be patient, the answer will come either in the form of an informative response or with a link to an informative response.
in every thread or be it for a rom ,a mod a theme etc. there are instructions. follow them to the letter and you shouldnt have any problem.
most importantly, be grateful to the devs or members which might assist you , at least say thank you and hit the thanks button, and donate if you can. these individuals work very hard at what they do here to provide you with the information and freedom you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
Root your HTC HERO200 CDMA...
there are many different methods of rooting your device, it depends on your particular device.
they all work you simply have to find the one that works for you. for instance myself i use the regawmod one click method. (thanks regaw) when
i tried to use it on an associates device it didnt work...you have to find the method that works for your device.
youll find the files and programs you need to perform whatever procedure you choose to try on the developers page.
make sure you read the instruction completly before you begin. when you do begin follow the instruction to the letter and you shouldnt have any problem.once again, dont get piussed at the dev because it didnt work, its not that the procedure doesnt work, it just didnt work for you...simply search for another method and try again.and you will succeed.
i was going to post some of the methods but dont have permission from the devs to do so, so for now youll have to search for the precedures yourself. if or when i do get permission ill edit this thread or post the link in order to help yo on your way,,,ehhh for now itll be good practice for using the search window.
method 1.
hhttp://www.gadgetsdna.com/how-to-root-htc-hero-cdma-stock-android-2-1/3628/
The HTC Hero 2.1 exploit is based on the EVO rooting method. Rooting HTC Hero Android phone provides full access to its system files allowing you to modify the phone’s firmware and install third party apps, themes and custom ROMs. You can then spruce up your HTC Hero handset with number of third party applications.
How to Root Sprint’s 2.27.651.5 Release for CDMA Hero (Stock Android 2.1)
Note: If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK.
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.33 here. Run the installer, and reboot your computer when it is finished. Skip to step 4 once rebooted.
Step 4: Download the hero-root.zip. This zip contains everything you need to root your Hero.
(md5: c6e5058ed14f71c68fb099e10be142fb)
Step 5: Extract the 3 files inside hero-root.zip to the C:\android-sdk-windows\tools folder on your computer.
Step 6: Make sure USB Debugging is ON (checked) on your Hero. Navigate to Settings > Applications > Development > and make sure it is checked
Step 7: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is “Charge Only”, not “Disk Drive” or else this won’t work. You may restart your comuter when prompted to do so.
Step 8: Open a Command Prompt window by clicking the Start button and typing cmd into the search box and pressing enter. Alternatively, navigate to Start Menu > All Programs > Accessories > Command Prompt
Step 9: You enter the commands followed by pressing ENTER, one code at a time.
1 cd C:\android-sdk-windows\tools
You should now see C:\android-sdk-windows\tools>
Now type
adb devices
You will now notice your HTC Hero phone’s serial number. If you get “device not found” error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging on your phone. Continue on once you get the proper phone serial output.
You will now push the files needed to gain root to your sdcard in your phone with these following commands one by one:
adb push unrevoked /sdcard
adb push recovery.img /sdcard
adb push boot-patched.zip /sdcard
Now we run the exploit. Be patient, this may take up to 40 seconds.
adb shell
sh /sdcard/unrevoked
You should now see output that says this:
UNREVOKED
============================================================ unrEVOked: root for HTC evo and hero (http://unrevoked.com)
Now, on your phone, go to your app tray, and you will see that the Superuser Permissions app is in it, which is only possible on rooted devices.
Open the Superuser Permissions app. You will see a blank screen.
In the Command Prompt on your computer, type:
A prompt will appear on your Hero asking you to give /system/bin/sh privileges. Click Allow.
Go back to your command prompt, and you should see
$ su su #
Now Type
flash_image recovery /sdcard/recovery.img
Flashing the recovery may take many seconds to complete. Wait until the # symbol returns to proceed.
You should now see
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
#
This means it was a successful flash.
Now type
reboot recovery
Your phone will now boot to the custom recovery image you just flashed. In the Recovery Menu on your phone, choose the option:
Flash zip from sdcard
Then Select
boot-patched.zip
and press the Home button to apply. Once Recovery says “Install from sdcard complete” select “Reboot system now” from the menu.
Voila!! You now have full root access on HTC Hero 2.1!
Thanks to the guys at xda-developers and gadgetsdna
or, you can try regaw's one click root method. you can find it here on Xda, just use the search window,,,it's easy
both of these methods have worked well for me in the past, im sure one of them WILL work for you
-----------------------------------------------------------------------------
Flashing a ROM (from clockworkMod)
this is the method i use and i "never" have any problems
download the ROM of your choosing and move to the root of your sdcard
follow the devs instruction for installation which should be something like this;
1. do a nandroid backup
2. reboot into recovery
3. wipe data
4. wipe cashe
5. choose advanced, wipe dalvik
***OPTIONAL***
6. choose mounts and storage
7. format system
8. format data
9. formatcashe
10. go back. and choose install zip from sd card
11. choose, choose zip from sd card
12. find the rom you want to flash and choose yes
13. when its through flashing choose install zip from sd card
14. find the gapps you want to flash and choose yes
when its through with the flash the screen will return to the main menu and choose reboot system
the first boot will take a little longer than usual this is normal. setup your google s#@ts as usual and enjoy your new ROM.
follow these instructions and you shouldnt have any problems, if you do, go back to the thread you downloaded from post a reply to report it to the dev so they know theres a problem and they can determine if its a problem with the rom, a problem with the way you flashed or a problem with your system.
15. "ONCE AGAIN" most importantly, be grateful to the devs, at least say thank you and hit the thanks button, and donate if you can.
these individuals work very hard at what they do here to provide you with the information you need to do what you want to do with your HEROC.
say thanks,,,its not that difficult.
-----------------------------------------------------------------------------
themeing your new ROM
1. make sure the theme you choose is compatable with the rom you have flashed
2. since alot of the themes have a different procedure for installation,"READ AND FOLLOW THE DEVS INSTRUCTIONS"(sorry for the caps)
they are there for a reason.
-----------------------------------------------------------------------------
boot animations
1. Put the zip file in your tools folder from the android-sdk-windows
2. Load up Command Prompt (cmd) and go to your tools directory inside the android-sdk-windows folder
3. Load up your phone into recovery and mount /system
4. Type in command prompt
adb remount
adb push bootanimation.zip /system/media
adb reboot
or (compliments of user7618)
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----------------------------------------------------------------------------
Flashing a different recovery image
cd C:\android-sdk-windows\tools...got
cd C:\android-sdk-windows\tools>adb devices...got
(recognized phone)>>>>>
cd C:\android-sdk-windows\tools>adb shell
#flash_recovery image /sdcard/recovery-clockwork-4.0.0.2-heroc-20110611.img (enter)
mtd: successfully bla bla bla
#reboot....
or,,,
[edit] Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Copy the recovery.img to root of the SD card.
3.Boot the phone into recovery.
4.Open command prompt, cd to the Android SDK directory & type the following commands:
adb shell
mount /sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method II
Flash recovery using: RomManager
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.On the SD card, go to /clockworkmod/download/koush.tandtgaming.com/recoveries.
3.Rename the old image there named recovery-clockwork-2.5.0.1-heroc.img to recovery-clockwork-2.5.0.1-xxx.img.
4.Move, then rename, the recovery.img you downloaded to recovery-clockwork-2.5.0.1-heroc.img.
5.Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
[edit] Method III
Flash recovery using: Terminal Emulator Note: Requires s-off, otherwise you'll recieve "out of memory" errors.
1.Download the ClockworkMod Recovery: HeroC Download Optimus V Download.
2.Move recovery.img to root of the SD card.
3.Open the Terminal Emulator on the phone & type the following commands:
4.:
su
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
5.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
[edit] Method IV
Flash recovery using: H-Boot/S-Off Only HeroC Only
See S-Off for CDMA Hero if you are unsure what S-OFF is.
1.Download HERCIMG.zip
Newest Download: (version 3.0.5) HERCIMG.zip <--Updated 01212011
md5: 6dcd265a51cc7090824d7f9f889b370b
Alternate Download: (version 2.5.0.7) HERCIMG_clockwork-2.5.0.7 <--Updated 02-07-2011
md5: 0a367eb1d4445c72f8022769f7edc9dd
2.Move HERCIMG.zip to root of the SD card. Make sure the file is named HERCIMG.zip or H-Boot will not recognize it.
3.Power off the phone.
4.Hold the Volume Down & Power' button until the phone boots into the bootloader.
5.Wait for bootloader to scan and find HERCIMG.zip.
6.Press action to install.
7.The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Retrieved from "http://romrepo.info/wiki/index.php?title=Flash_the_ClockworkMod_Recovery"
-----------------------------------------------------------------------------
Change sprint insignia (ON AOSP) to whatever you want
1. Download eri.zip
2. Unzip the file to wherever you please.
3. Right click on eri.xml and choose "Open with Notepad"
4. Once you open the file you will see "Sprint" in the 5th line.
5. Delete Sprint and place whatever you would like in it's place. I believe you have up to 16 spaces to work with if need be.
6. Save the file with an .xml extension. Important: Make sure it is eri.xml and not eri.xml.txt. This will cause issues.
7. Place the eri.xml in your /androidsdk/tools directory.
8. Pull up your Command Promt/Terminal/Etc
9. CD to your /androidsdk/tools directory and:
adb remount
adb push eri.xml /data/eri.xml
adb reboot
or, (thanks to user 7618 )
I threw together a simple app to change the Carrier Name in the status bar/lockscreen to whatever you want since my alot of people seem to ask how to change it. Feel free to use it. Tested on Incredible and Eris. Dev's feel free to thow it your roms if you want. No ads and free just a simple tool to change the text. Thanks to the great Eris community.
Currently only works for AOSP roms such as cyanogenmod.
V1.3
While trouble shooting some radio issues on a rom I realized there's no need to reboot the phone to apply the new carrier name. I only needed to cycle the radio so I changed the app to toggle airplane mode on and then back off after you input your text so the change should take place immediately. This should make it a little easier to test and try different things or just change it more often.
I also added some shortcut buttons at the bottom to quickly add the text for the ", < and > signs so you don't have to type it all out. Only tested this with cm7 but should still work with any rom's it worked with before. Again thanks to Psiphon for pointing these symbol fixes out.
http://www.multiupload.com/RO6RZUUL16
V1.2
Fix for phones that don't already have an eri.xml file there
Added version number to bottom of screen so people can be sure what version they are running.
http://www.androidphiles.com/files/g.../ccname1.2.apk
V1.1
Fixed force closes when using symbols.
You can now use symbols except for double quotes. Apostrophe (single quote) seems to work fine.
Some usefull info if you want to use quotes....
Originally Posted by Psiphon
You can use special characters like the quotation marks and greater/less than signs by using entity references (either using an entity name or number):
" (quotation mark) use "
< (less than sign) use either < or <
> (greater than sign) use either > or >
I hope this helps!
Added Toast popup to let you know the name has been set.
If reboot button does not reboot phone just reboot the phone manually
http://www.androidphiles.com/files/g.../ccname1.1.apk
This app does one thing. It takes the input text you type and creates and eri.xml file and puts it in data/ folder on your phone. Then you can reboot for change to take effect. You can uninstall the app after you change it if you want or you can leave it on there(it's pretty small) in case you like to switch it every now and then. If you flash a new rom you will have to rerun the app.
-----------------------------------------------------------------------------
hopefully there will be more info in the future to add to this thread that will make things easier for everyone all around.
-----------------------------------------------------------------------------
***TO ALL DEVS AND OTHER MEMBERS*** i myself cant thank you enough for the help and advice ive recieved in the past, if you might hace any information you feel would be helpful to this thread please feel free to PM it to me and ill see that i edit this post with your procedures. and ofcourse your names will be added to a list of thanks at the bottom of the post,,,Thanks again,
THANX FOR THEIR HELP TO ME IN THE PAST;
flipz
coffeehandle
MattCrystal
laie1472
user7618
PMGRANDS
kushdeck
bierce22
conap
psiphon
kifno(aspentree)
-----------------------------------------------------------------------------
all of the information i have provided here has been compiled from Devs and other membes in order to assist new memberslike myself , and to help the devs and senior members so they dont have to keep answering the same questions again and again.
*** i f you want to thank someone, thank them for passing on their knowlege to me as im passing it on to you***
enjoy,,,
please dont double post
Nice beginners guide.
-----
3vo. That is all that needs be said.
Nice beginners guide.
Also, an easier way to change the carrier banner:
http://forum.xda-developers.com/showthread.php?t=960099
Instead of all that goofy crap with files and whatnot.
Boot animations are easier to change by sliding the .zip into /system/media or /data/local. That way, there is no need for adb commands, just a file explorer like root explorer. Make sure that it is named bootanimation.zip.
-----
3vo. That is all that needs be said.
Thanks man ill keerp adding, i really hope this helps some folks
Kudos. Good guide.
#Root/Hack-Mod_Always*
Also we dont talk about "he who must not be named" around here so you might want to take that out of the credits.
lai and user know who im talking about lol.
Uhhhhh,,,Ooops. My bad....sorry bout that guys.
ha lol i was just kidding but seriously that guy went bannanas and had a severe case of schizophrenia lmao.
lol, i hear ya man, i feel credits given where credits due, but on the other hand,,,,aw well you know what i was gonna say
Yeah, dude was crackers, but if he helped you, then he helped you. I'd leave him in there, personally.
-----
3vo. That is all that needs be said.
Yup agreed. A if he helped he helped that's just how it is. Like the guy or not.
#Root/Hack-Mod_Always*
cool guys i do feel the same way, but dont wanna stir any bees nests either, ill put it back in but we'll just overlook it. thanx for understanding
I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
failed to copy recovery.img permission denied
Click to expand...
Click to collapse
Thanks for any help, I'm hoping it's just a small little step I missed.
mikeeey said:
I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
Thanks for any help, I'm hoping it's just a small little step I missed.
Click to expand...
Click to collapse
This is covered in the cwm thread in development section you need to use a file explorer that has root access and change permissions to the /data folder. You can use es file explorer, its free. Open it go into settings then browse as root... not really sure exact steps but they are in the came thread.
O my such a small step I missed! Thank you! Ill try this later today.
Permissions of /data are set to R/W but I still get the same error..
I'm starting to wonder if the cause of this is because I tried using Rom Manager to flash clockwork, THEN tried the adb method. Maybe it already being there is causing the permission denied?
edit: so it looks like it was as simple as me looking over the permissions and thinking I saw everything was checked, but really the two checks from the left under "other" were grayed out lol, checking those fixed it.
This HOW-TO is meant for individuals who like to do things manually and see each process as they occur, versus using a toolkit. I prefer manually unlocking/rooting as I can confirm each step visually and I believe it makes for a more educational experience. Familiarity and confidence with fastboot/adb can be beneficial later on for restoring/troubleshooting/flashing etc down the road.
Unknown at this point if OTA updates will install after flashing CWM. There may be a check file in the OTA that could prevent installation if modified file structure is detected. I’ll edit when I confirm. At any rate, not really an issue as you can flash the OTA yourself as someone on XDA will most likely post it up, or you could re-flash the stock recovery using fastboot which you will now be comfortable with after using this guide! Additionally, if an OTA causes you to lose root you can revisit the appropriate steps to flash SuperSU again.
There are several ways to do these procedures, and I’ve certainly taken the long way on some of them. So by no means am I claiming this to the best or most efficient method, but my hopes are to make things a little more clear and simple based off some of the questions and challenges I’ve seen in a few threads.
This how-to was written for Windows and uses adb and fastboot for installation.
Please let me know of any corrections, additions or errors. Many thanks to the members and devs who made these files available.
1. Download all of the following files and place them in the same directory. I will note whether you need to extract them or not.
Download and extract platform-tools-v16.zip from here: (thanks to efrant)
http://forum.xda-developers.com/showthread.php?t=1626895
Download and extract [ADB/FB/APX Driver] Universal Naked Driver 0.72 from here:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Download SuperSU from here: (look for UPDATE-SuperSU-v1.25.zip or current version)
http://forum.xda-developers.com/showthread.php?t=1538053
Download ClockworkMod from here: (look for Galaxy Nexus 7, Download Recovery 6.0.3.1 or current version – Recommend non-Touch as of ver 6.0.10, some reported issues with the Touch version)
http://www.clockworkmod.com/rommanager/
2. Now we will install the drivers and verify they are working. If you cannot verify drivers are functioning in both normal boot and recovery you need to stop and figure out what you are doing wrong. Proceeding further would be pointless. If you are having trouble, visit the Naked Driver thread listed above or here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
a. Make sure you have USB debugging enabled on your Nexus: setttings ->develop options ->USB Debugging.
b. USB connect your Nexus to your Windows pc. If you get a notification for unknown/driver not found, look in Device Manager for the exclamation point, and right click for update driver software, then browse my computer, then point to where you saved and extracted the Universal Naked Driver folder. If you get a warning from Windows complaining the driver is not signed, hit ‘Install driver anyway’. After the driver installs, you should now have ‘Nexus 7’ listed under ‘Portable Devices’ with no exclamation point.
Now we will verify using adb. You will need to launch a command prompt from the directory you saved all the files from step 1 to. Easiest way is to navigate to the directory via file explorer, then hold down shift and the RIGHT mouse button, and select “Open command window from here”.
In the cmd prompt, type:
adb devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again. You should see something like:
List of devices attached
945d3339495 device
if instead you see:
List of devices attached
945d3339495 offline
then most likely you need to look on your nexus for a notice to allow the connected computer permissions to use usb debugging. If you don't see a notice, disable/enable usb debugging in "Settings -> Developer options" and then you should get the prompt. You should select 'remember this computer', if not you will have to do it again upon reboot.
c. Now we need to reboot into the bootloader and load the drivers again. So type:
adb reboot bootloader
and your Nexus should reboot into the bootloader. My laptop found the driver on its own, note that in Device Manager it is now listed as ‘Android Device’ instead of under ‘Portable Devices’. If your system does not find the driver, follow the same steps as above to update your driver after you located the exclamation point in Device Manager.
Now we will verify that the driver is installed correctly while in the bootloader. Again from a command prompt opened from the directory where you saved all the files from step 1, type:
fastboot devices
You should get a response with your Nexus serial number. If not, stop. Drivers are not loaded, re-read above and visit threads mentioned, try again.
3. Perform device unlock. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! Please backup accordingly.
Your Nexus should still be in the bootloader. Type:
fastboot oem unlock
Your Nexus will prompt you to accept. NOTE: !!!THIS WILL ERASE ALL YOUR USER DATA!!! After a short moment, the device should report unlocked under “lock state”. Reboot device by typing:
fastboot reboot
After rebooting, sign in, etc.
4. Copy over SuperSU . In windows explorer locate the UPDATE-SuperSU-v1.25.zip and copy it to your Nexus internal storage area. Don’t put it any of the folders, just dump it in there. Now reboot into the bootloader again by typing:
adb reboot bootloader
5. Flash CWM. Once in the bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
after you get ‘finished’ from the command window, reboot your Nexus into CWM recovery by navigating with the volume buttons to ‘recovery mode’, then press power button.
6. Root Nexus. Using the volume keys, navigate to ‘install zip from sdcard’ and hit the power button. Now select ‘choose zip from sdcard’ and hit the power button. Navigate down to UPDATE-SuperSU-v1.25.zip’ and hit the power button. Select ‘Yes’, hit power. Once done select ‘go back’, then ‘reboot system now’.
Congrats, you’ve unlocked and rooted your Nexus!
Now at this point CWM recovery may or may not still be present on your device. There have been mixed reports on whether it will ‘stick’ the first time you flash it. The stock ROM has a check file that will replace CWM with the stock recovery upon reboot. To determine if CWM is still present simply reboot into recovery and see if it is there. Type:
adb reboot recovery
Obviously if you see the droid with exclamation point CWM did not stick. If you have no need for CWM, and simply wanted root you could stop now. Wait a few minutes and your device will reboot on its own and you are all done.
However, if you desire CWM then proceed on.
7. Rename recovery-from-boot.p to prevent stock recovery re-installation. Your Nexus should be booted normally at this point.
a. Go to the Play store and install ES File Explorer File Manager. Under settings enable ‘up to root’, ‘root explorer’, and ’mount file system’.
b. Navigate to /system and rename:
recovery-from-boot.p
to
recovery-from-boot.bak
by long pressing and selecting ‘rename’. Note: Be careful while navigating your device with these options enabled, a typo or slip-up could cripple your device and require a restore. I suggest once this rename is competed to disable the above options to avoid any mistakes in future exploring.
8. Flash CWM again.
a. Reboot into bootloader by typing:
adb reboot bootloader
b. once in bootloader type:
fastboot flash recovery recovery-clockwork-6.0.3.1-grouper.img
c. reboot device by typing:
fastboot reboot
d. verify CWM stuck by rebooting into recovery:
adb reboot recovery
And that should be it!
Some additional notes: CWM does make notice on rebooting with a message ”ROM may flash stock recovery on reboot. Fix? This can not be undone”. I don’t know what CWM will do there, so I prefer to rename the recovery-from-boot file so that I could easily restore it if I wanted. But perhaps that is what CWM does, although the message persists even after I renamed the file. Maybe someone could clarify this.
Hope this helps some people out in enjoying this great device even more, thanks for reading.
4.1.2 and 4.2.1 updates...
Thought I would revisit the thread as we've had two updates since I wrote the above. I installed 4.1.2 OTA with no problems but as expected, I lost root and CWM.
Because I'm lazy, I didn't worry over it much and then 4.2.1 shows up and also installed perfectly. Finally got around to getting root back and here are the steps I used.
Notes:
* Need to make sure drivers are correctly installed. See first post.
* I never really used CWM so I elected not to permanently install it this time.
* This update is a brief synopsis of how I got root back. If the steps are not clear, review the first post as the procedure is very similar.
1.) Ensure USB debugging is still enabled. On 4.2.1 "Developers options" are hidden by default. To enable simply tap "Settings > About tablet > Build number" 7 times. Back out and "Developers options" should now be available. In my case USB debugging was still enabled.
2.) Download SuperSU v0.99 and CWM 6.0.1.9 from links in first post. I used non-touch version of CWM.
3.) Transfer SuperSU over to internal storage of your Nexus. Be sure you know where you dumped it.
4.) Reboot into bootloader: adb reboot bootloader
5.) Temporarily boot or permanently install CWM so we can install SuperSU zip.
for temp boot type: fastboot boot recovery-clockwork-6.0.1.9-grouper.img
for perm install type: fastboot flash recovery recovery-clockwork-6.0.1.9-grouper.img
6.) Once in CWM select:
a. install zip from sdcard
b. choose zip from sdcard
c. navigate to /0/ then wherever you put SuperSU
7.) Once finished back out and reboot system now. I selected "No" on allowing CWM to disable stock recovery. If you are only temp booting CWM then this likely won't matter either choice you make. If you perm flashed CWM then you may wish to choose 'Yes".
That should cover it. Thanks for reading, any questions or corrections be sure to let me know.
I have a question about this:
I rooted and installed CWM on my 4.2 N7, but now, then I try to install the 4.2.1 OTA update, I get this error:
Code:
assert failed: apply_patch_check("/system/lib/libweb rtc_audio_preprocessing.so", "bin_number", "big_number""),
E: error in /cache/jop40d-from-jop40c.zip
(Status 7)
It's wise to apply this if I already have a rooted+CWM N7?
Some root procedures, or third party apps like Titanium Pro can make changes to certain system files that will cause an official update to fail. In your case, it appears at least "rtc_audio_preprocessing.so" located in "/system/lib/libweb" has been altered.
The easiest solution is to flash the current factory image then root. You can find them here: https://developers.google.com/android/nexus/images#nakasi.
However, you will lose your data. So back up accordingly.
If that's not an option, you can try:
a.) figure out which app you have that caused the change, and see if it has a 'revert' option or if uninstalling will put the file(s) back to stock.
b.) find the unmodified contents of /system/app and /system/lib and replace yours. Needs to be from 4.2 in your case.
c.) find a modified manual update patch (either zip for CWM or .img for fastboot) that has been altered to ignore the integrity check.
Curious, just went looking for "rtc_audio_preprocessing.so" in a factory 4.2 system.img and can not locate it, or the lib/libweb directory. Perhaps a third party app made these additions and thus the integrity check is failing as the files are unknown/unaccounted for?
At any rate, I went ahead and sourced a 4.2 system.img and extracted the /app and /lib directories in case this helps you or anyone else searching along.
Extracted from: nakasi-jop40c-factory-6aabb391.tgz
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip
https://dl.dropbox.com/u/34704640/sys_apps_dir.zip.md5
https://dl.dropbox.com/u/34704640/sys_lib_dir.zip.md5
so I factory-reseted my N7, but it didn't helped. I found the file /system/lib/libwebrtc_audio_preprocessing.so so I tried to replace it with the file you posted (thanks btw!), but while using a console (su, then cp file.so file.so.backup) I get the error saying it's a read-only system, so I can't replace that file
any other idea?
EDIT: So I was playing around with the N7 (although I can really remember, I think I formated /system ?):
So, yeah, I actually formated /system for some unknown reason and there is no OS to boot, so I'm downloading at 25 KBps (yes...I know) and I'll be installing the JOP40D version for the N7.
ah, so the file is actually:
/lib/libwebrtc_audio_preprocessing.so
not
/lib/libweb/rtc_audio_preprocessing.so
That makes a little more sense. On cp over the original file, as you discovered the /system partition needs to be remounted as writable before you would be able to make changes. You could easily accomplish this with one of the root file explorers from the market. I use "ES File Explorer" as its free. Then simply copy over your file.
Or if you prefer adb: mount -o remount rw /system
Regardless, you are starting over from scratch so no worries. One of the things I love about this device is the option to start fresh-from-factory with minimal fuss.
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
cub0ne said:
igot a question. im currently running or 4.2.1 (rooted/unlocked). i used wugsfresh to root and unlock my device. wugfresh uses TWR and i want to try CWM and remove the TWR, would it be possible? i want to try different roms like cyanogen and i think CWM would be a good option.TIA
Click to expand...
Click to collapse
I am also on 4.2.1 unlocked and rooted with wugfresh toolkit. I downloaded CWM from the play store, the app can download the latest CWM recovery and flash it for you. That is what I did, All I have used CWM for is a nandroid backup, but have booted into recovery and wiped cache and fixed permission
Has anyone had issue is SuperSU and CWM running Fix Permissions in the CWM app? I get an error...
Thank you!
Thank you very much for the excellent guide, your explanations were very clear!
It was a lot of fun following it, and I am very happy for choosing this guide over the 'one-click' toolkits.
I'll give it a try
After trying a "all in one toolbox" to unlock and root I think I'll give this a shot. I got stuck at not being able to root and like your OP said, doing it manually would help with the learning curve.
Quick questions that has popped up is.
Do I lock my bootloader back to use your guide?
I've noticed drivers I have in device manager have different names. Does this mean there are dif drivers that do the same thing? Should i delete them and use the ones in the OP?
Late response, but I'll answer for future users following this thread...
Once your bootloader is unlocked by any means, no need to relock in order to follow this guide. We simply have to have it unlocked so we can gain root
Drivers are probably the most common issues people have in any instance of trying to interact with their device. While its not imperative that the names are the same, what is most important is that you can communicate with the device. There really isn't the right or wrong driver name, just that the driver works! Having said that, if you are wondering whether you have the correct drivers installed, simply follow the steps and attempt a "adb devices" or "fastboot devices" command depending on your device status as is outlined in the tutorial. If you do not have the appropriate response, then you need to stop and determine the issue.
Update after OTA 4.2.2
Lost root as expected, and followed procedure in post #2 to gain root back. Also updated OP file versions to current as of this post as they all worked successfully.
Only thing I would note: If you get a "offline" notice after trying 'adb devices', be sure to check your nexus for a notification to allow the connected computer access for USB debugging. If you don't see one, go to "Settings -> Developer options" and disable/enable USB debugging and it should pop up. I don't remember this behavior when I first wrote the tutorial, so it may be something new for 4.2.2. After reboot it will require approval again, so you may wish to select 'remember this computer'. I added this note in the OP as well in the appropriate step.