Related
i have my phone updated to 2.1 and rooted. Want to overclock it now but not sure what im supposed to do with the kernel-overclock-update-v3.zip. I have the original PB00IMG.zip i updated and rooted my phone with, am i supposed to use it somehow?? New to this would appreciate any help.
Just use this, Flash it and it will make ur life easyier.
http://forum.xda-developers.com/showthread.php?t=685581
so phone will be stock again right? have to re dload apps and sync contacts and **** again right?
hmm... or u can try to flash the kernel-overclock-update-v3.zip to the one you have
be sure to nand backup first
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
did you flash recovery?
duckingzebra said:
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
Click to expand...
Click to collapse
Hey man,
When you rooted did you flash the Amon-Ra recovery image? If so put the update zip on the root of your sd. Power down your handset. hold the volume UP and the power on will bring you to the recovery menu. Here you have options for back up,flash from zip etc...once there you can select whatever rom/update you want to flash. Remember nandroid is your friend always back up. Also as far as apps etc...check out Titanium back up or one of the other free back up apps in market. I hope this helps you out.
volume up + end button = Recovery
ok, im following the steps to III: Flashing a Custom Recovery. and when i get to the step :adb push recovery.img /sdcard it says :cannot start recovery.img: No such file or directory...is the recovery.img also supposed to gon on the root of my sd card? or just the tools folder, cause its there?
yes its suppose to be on the root of the sdcard too
still says cannot stat 'recovery.img': no such fire or directory
am i supposed to replace /sdcard with /J (which is what my phone comes up as in my computer) -tried that still didn't work...
can u link me to the tut u are using?
http://forum.xda-developers.com/showthread.php?t=647707
QUOTE=TopazAaron]
duckingzebra said:
did you see the tutorial i linked? still cant figure it out.
Click to expand...
Click to collapse
ok
put the Recovery image in the tools/ in the sdk
after that plug ur phone into the comp
now being there in cmd navigate to the /tools/ folder
then type or copy and paste
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
---
now if you still have issues, let me know, sorry i didnt reply, i got busy with other things.
thanks for ur pm tho[/QUOTE]
ok now instead of saying :cannot start recovery.img: No such file or directory
it says error: device not found, when i open my computer my sdcard in my phone shows up and i can open it...
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
TopazAaron said:
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sorry newser here, irc??
Is your phone actually rooted? To check, turn on your phone, then turn on USB debugging through Settings/Applications/Development/USB debugging. Plug your phone into the computer via the USB cable.
In the run box of your computer, type cmd, then enter.
When the command window shows up, changed you your SDK tools directory. On my system it would be:
cd c:\android-sdk-windows\tools
Then run the following command
adb shell
You're rooted if it comes back with
#
If it comes back with
$
try the typing
SU
if it does not change from $ to # then you might want to try rooting again, and be sure to install the Amon_RA recovery
typing exit multiple times will back you out of adb, and the cmd window.
Hope that helps.
Edit: Of course that works for 2.1 leak 3 users as well.
Easier way for you tho, if you boot to hboot with the send and end buttons, you should see hboot with S off if you're rooted. If it's S On you're not.
NOTE: For those of you that are looking to root thier Inc and already have the latest 2.2+ OTA released in November, these steps will not work. Changes have been made to the ROM so until a new root application has been developed by the unrEVOked team, I am afraid you are left with a stock phone. Sorry. If new updates come out, I will try to post them here.
NOTE: I have uploaded the 2.1 and 2.2 RUUs to Rapidshare and updated the links.
First, let me say that I did not come up with this nor did I create any of the tools. I am passing all this on in a single thread to let people know how update thier Droid Incredible to the OTA 2.2 and have root access if they have it in any of the following conditions:
1. Stock 2.1 without root or unrEVOked Forever
2. Stock 2.1 with root and no unrEVOked Forever
3. Stock 2.1 with root and unrEVOked Forever
4. Stock 2.2 without root and with unrEVOked Forever
5. Stock 2.2 without root and no unrEVOked Forever
6. Custom ROM with root and S-OFF
7. Getting free WiFi Tethering on 2.2
8. Removing unwanted preloaded applications.
NOTE: This may work with custom ROMs, but I have not verified it.
NOTE: SOME PEOPLE, INCLUDING ME HAVE HAD THE PROBLEM OF BEING STUCK IN HBOOT AFTER LOADING A ROM IMAGE. IF THIS HAPPENS TO YOU AFTER LOADING THE 2.1 OR 2.2 ROM, DO NOT PANIC, JUST REAPPLY THE ROM AND ALL WILL BE FINE. FOR SOME REASON THE ROM DOES NOT LOAD CORRECTLY ON THE FIRST TRY BUT DOES ON THE SECOND.
I am passing this on because I loaded the OTA 2.2 without unrEVOked forever loaded on my phone. What a mess. I tried everything (I thought) to try and downgrade it back to stock 2.1 but with no luck. If you do not know, unrEVOked3 cannot currently root a 2.2 updated Droid Incredable and if you have not used unrEVOked forever, you can not get clockworkmod recovery to reload on the phone. I tried the 2.1 RUU to downgrade, but never could get it to connect to the phone. I then tried to use the 2.1 PB31IMG.zip to load and the HBoot loader would just tell me that it was an older image and not load it. I thought I was hosed until the unrEVOked team breaks the code on the 2.2 HBoot loader until I got pointed in the right direction (sort of).
TNS201 pointed me to the following thread: http://forum.xda-developers.com/showthread.php?t=768295
I gave this a try and still could not downgrade my phone. I searched around and after much trial and error, I was able to put together the correct steps to downgrade my phone and then applied unrEVOked3, unrEVOked forever, the OTA 2.2 update, and then reroot the phone. Anyway, here is what I have come up with:
** NOTE: THIS WILL TOTALY WIPE YOUR PHONE CLEAN!!! BACKUP ANYTHING YOU WANT BACK ON THE PHONE!!! **
Condition 1
1. Go to the following link and follow the instructions: http://forum.xda-developers.com/showthread.php?t=709220 Only do the steps for getting ADB loaded on your computer!
This will get ADB loaded on your computer which you will need when doing customizations to the phone. It will also walk you through rooting your phone and doing a lot of other things. Good thread for us noobs.
2. Download unrEVOked Forever from here: http://unrevoked.com/rootwiki/doku.php/public/forever
3. Copy the file to the root of your sdcard.
4. Reboot your phone into clockworkmod recovery and load the unrEVOked Forever zip file. This will turn S to off and allow unsigned images to be loaded.
When you reboot your phone, you will have a fully rooted and S-OFF stock 2.1 Droid Incredible.
NOTE: If you are having troubles downloading the OTA 2.2 RUU, use this link to download the ROM. Just delete the "_2.2" from the file name and go straight to step 12. http://rapidshare.com/files/418523008/PB31IMG_2.2.zip
To load 2.2, do the following:
5. Download the OTA 2.2 RUU from here: http://rapidshare.com/files/418527589/RUU_Incredible_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_1433.exe
6. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
7. Run the RUU and update your phone to 2.2. If the RUU updates your phone, go on to step 15. If the RUU will not connect to your phone Go to step 8.
8. Start the RUU.
9. Go to your computers temp directory and locate the folder that contains the file rom.zip.
10. Once you locate this file, copy it to any folder (or your desktop).
11. Rename rom.zip to PB31IMG.zip
12. Copy PB31IMG.zip to the root of your phones sdcard.
13. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip. This will take a while, so be patient.
14. Follow the instructions to have HBoot install PB31IMG.zip.
Whether you used the RUU or HBoot and PB31IMG.zip, at this point, you should have 2.2 loaded on your phone, but you will no longer have root. You will have S-OFF.
To regain root access, do the following:
15. Download clockworkmod recovery from here: http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
16. Download the payload update from here: http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
17. Download superuser from here: http://dl.dropbox.com/u/6408470/su-releases/su-2.3.4-ef-signed.zip
18. Copy all three files to the root of the phones sdcard.
19. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip.
20. Follow the instructions to have HBoot install PB31IMG.zip. Since the phone is still S-OFF, this will reload clockworkmod recovery on the phone.
21. Boot the phone into recovery and load the two zip files downloaded in steps 16 and 17. This will root the phone and reload superuser.
If all went well, when the phone reboots, it should now be loaded with 2.2 and have full root and S-OFF. Enjoy.
Condition 2
1. Do steps 2 through 21 under Condition 1.
Condition 3
1. Do steps 5 through 21 under Condition 1.
Condition 4
** NOTE: THIS ONE DOES NOT WIPE YOUR PHONE!! **
1. Do steps 15 through 21 under Condition 1.
Condition 5
This is a tuffer one and requires the phone to be downgraded to 2.1 before upgrading it back to 2.2. Anyway, here are the steps:
NOTE: YOU MUST USE THE 2.1 RUU I HAVE LINKED AND THE MTD0.IMG FILE I HAVE ATTACHED OR THIS MAY NOT WORK!!!
NOTE: If you are having troubles downloading the 2.1 RUU, use this link to download the ROM. Just delete the "_2.1" from the file name and go straight to step 5 after completing step 1 and 2 (skip step 3 and 4). http://rapidshare.com/files/418141003/PB31IMG_2.1.zip.html
1. Do steps 1 and 2 under Condition 1.
2. Download the attached zip file. It contains the files I had a hard time finding.
3. Download the 2.1 RUU file from here: http://rapidshare.com/files/418525132/RUU_Incredible_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_.exe
4. Follow steps 8 through 11 under condition 1 to get a good copy of the 2.1 ROM.
5. Copy the 2.1 ROM to the c:\android-sdk-windows\tools folder.
6. Unzip the files downloaded in step 2 to the c:\android-sdk-windows\tools folder.
7. Copy the unrevoked-forever.zip to the c:\android-sdk-windows\tools folder.
Note: At this point, you should have the following files copied to your c:\android-sdk-windows\tools folder:
PB31IMG.zip (this is the 2.1 ROM)
unrevoked-forever.zip (will set S-OFF)
rageagainstthecage-arm5.bin (this is a root exploit - gives you temperary root)
mtd0.img (need to research this one)
flash_image (this flashes images)
7. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
8. Open a command promt window and change to the c:\android-sdk-windows\tools folder.
9. Enter adb push unrevoked-forever.zip /sdcard/ and then press enter.
10. Enter adb push flash_image /data/local/ and then press enter.
11. Enter adb push rageagainstthecage-arm5.bin /data/local/tmp/ and then press enter.
12. Enter adb push mtd0.img /sdcard/ and then press enter.
13. Enter adb push PB31IMG.zip /sdcard/ and then press enter.
14. Enter adb shell and then press enter.
15. Enter cd /data/local/tmp/ and then press enter.
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
17. Enter cd /data/local/ and then press enter.
18. Enter chmod 777 /data/local/flash_image and then press enter.
19. Enter cd /data/local/tmp/ and then press enter.
20. Enter ./rageagainstthecage-arm5.bin and then press enter. You will now see some text on your cmd prompt screen explaining the exploit. Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
21. Enter adb shell and then press enter. You will see you now have a # instead of a $ prompt.
22. Enter cd /data/local and then press enter.
23. Enter ./flash_image misc /sdcard/mtd0.img and then press enter. This will flash your misc partition with Toast's mtd-eng.img and should return you to a # prompt.
24. Enter reboot bootloader and press enter.
25. HBoot will load. Select bootloader and HBoot will then load PB31IMG.zip.
26. Follow the instructions to have HBoot install PB31IMG.zip.
Once it is finished, select restart. You now are on the stock 2.1 build of Android. Now you can follow steps 3 through 21 under condition 1 and get your phone loaded back with 2.2 and have root and S-OFF.
Condition 6
1. Do steps 5 through 21 under Condition 1.
Condition 7
The following steps will allow you to use the 3G Mobile Hotspot that comes with the OTA 2.2 update and not have Verizon charge you for using it:
1. On your phone, bring up the dialer and dial ##778. This will load EPST.
2. Select EDIT.
3. Enter 000000 for the password.
4. Select SECURITY.
5. Select the username that has [email protected].
6. Edit the username to read [email protected] (delete "dun.").
7. Click the back button to return to the list.
8. Select M.IP DEFAULT PROFILE.
9. Repeat steps 5 and 6.
10. Click on MENU and select COMMIT.
At this point, your phone will reboot and you will be able to use the 3G Mobile Hotspot application to get free WiFi tethering. Enjoy.
Condition 8
I have so far found three options for removing the preloaded apps. They all require the phone to be rooted. Here they are:
1. The first way is to get Titanium Backup. You will also need to donate (as little as $3.99) to get full functionality of Titanium Backup, but it is well worth it. If you do not want to physically remove the application, you can use the FREEZE function and the application will be removed from the app list, but physically will still be on the phone. If you really want to get it off, you can uninstall and then deleted from the phone. All of this through a user interface that is pretty easy to use. By the way, it also does backups of apps and data.
2. Another option is to get Root Explorer. You have to pay for this one. It will let you mount the system folders on the phone as read/write and allow you to move and/or delete apps from the apps folder on the phone. This is a good app and worth having even if you do not use it to remove apps.
3. The final way is to use ADB and the command prompt to remove or move any application you do not want. This is tried and true, but combersome. You do not have to buy it, but there is no GUI to help you out.
My thanks to all the folks here on XDA that made it possible for us to release the possibilities of the Droid Incredable. As I stated above, I did not create the apps or the steps, I just put them together for others to use. I wish I could thank all the individuals that made this possible, but I did not get thier IDs, so in lew of an individual thank you, I am posting this group THANK YOU. Keep up the good work!
Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?
Scblacksunshine said:
Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?
Click to expand...
Click to collapse
No, in the case of having 2.2 already loaded and S-OFF, you are correct, the phone will not get wiped. The steps will root the phone and load superuser back on.
confirmation
Can anyone confirm option 4 working??
RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
Those are steps I used to get root back on my phone after I update to 2.2. As I stated, I messed up the first time and did not load unrEVOked forever and could not root the phone, so I had to downgrade to 2.1 first and then go through the rooting process. That time I made sure to load unrEVOKED forever. After that, all went well.
Sent from my HTC Incredible.
RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.
Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?
also Im running Ubuntu 10.04 if that makes a difference
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked
PimpShit420 said:
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked
Click to expand...
Click to collapse
I tried this and it did not work for me. It looked as if it did. It gave me the proper prompt, but on reboot, no root access. I had to use chmod 777 instead of chmod 0755.
PimpShit420 said:
Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?
Click to expand...
Click to collapse
I made a mistake, the line should have had 777 after chmod, not 0755. I have updated the instructions. If other individuals that use 0755 instead of 777 get the above to work, let me know. I do not know what the difference is. All I know is 0755 did not work for me. I had to use 777. I think I will do some research on chmod.
Hope other individuals find this helpful.
well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots
I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue
PimpShit420 said:
well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots
Click to expand...
Click to collapse
This is the problem I had. Try 777 instead of 0755 after each of the chmod commands. That is what worked for me.
you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail
chmod 0755 vs chmod 777
PimpShit420 said:
I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue
Click to expand...
Click to collapse
Well, I looked the chmod 777 and chmod 0755 commands up. Both commands change the read/write state for a file. 0755 changes the permissions for a specific group and user. 777 changes the permissions for everyone. You can find an explanation here: http://ss64.com/bash/chmod.html
0755 did not work for me, but 777 did. I am going to keep the instructions as they are unless I get feedback that 0755 is working for other people. If I do, I will add them as an alternative.
PimpShit420 said:
you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail
Click to expand...
Click to collapse
Are you using 777 for each chmod command?
Also, I was reading through the steps and found an error with step 16. It said the following:
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
It should have said this:
16. Enter chmod 777 /data/local/rageagainstthecage-arm5.bin and then press enter.
I have updated the steps on post 1.
Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!
BNG303 said:
Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!
Click to expand...
Click to collapse
Your welcome. I am glad it helped.
bagery77 said:
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.
Click to expand...
Click to collapse
Glad this helped. I wanted to give everyone a one stop shop for updating and root for 2.2. Also hoped everyone would not have to go though all that I did.
One thing I've noticed is there isn't a lot of documentation for getting set up and unlocking your bootloader on a Linux OS. Setting up your machine to get adb and fastboot to recognize your device takes a tiny bit of extra work on a Linux operating system, but what exactly needs to be done may not be clear to everyone. Whether it's because you're new to the Android SDK/adb, somewhat new to Linux, or can't simply can't seem to find the Vendor Code for the Nexus S. (For those who are looking specifically for this, it's '18d1', and I assume will be the same on all Nexus devices to come; If this means nothing to you right now, read on.)
Disclaimer: I take no responsibility if something goes wrong (if it does, it should be fixable though), Unlocking your bootloader voids your warranty (but you can lock it back), Unlocking the bootloader will wipe your entire phone, including USB Storage; so make a copy of all those family photos and other files you may have put onto the USB storage if you want to keep them.
For the sake of sanity, this guide assumes you are using Ubuntu. If you're using something else (or different applications), there are terminal commands offered, and you probably have an idea on how to adapt the given instructions to your Linux OS.
Preparation: Installing the Android SDK, ADB, Fastboot & Setting Up Your Nexus S to be Recognized
1. Download the Android SDK for Linux: http://dl.google.com/android/android-sdk_r08-linux_86.tgz
2. Save it in a folder of your choice. I chose to keep it in my Downloads folder, myself. If you'd like, you can rename it to the simpler name of 'AndroidSDK.tgz'. The rest of the guide will assume that you did, because I'm lazy, and it makes things simpler; it will also assume you saved it in Downloads. If you feel that you have the intuition to rename and edit the path names based on your own choices, then fine; but if you're utterly lost here, just stick with what I'm doing; download to 'Downloads', rename to 'AndroidSDK.tgz'.
3. Now that you have it, navigate to the folder you downloaded it to, right-click, and click 'Extract' to unzip it. If for some reason you cannot do this, open up a terminal and try this command:
Code:
tar zxvf /home/<your-user-name>/Downloads/AndroidSDK.tgz
You may have to adjust the command if you didn't save it under Downloads or didn't rename the file to AndroidSDK.tgz.
4. Now, we'll install adb and some other software packages by starting up the Android SDK and AVD Manager. Start it either by:
- Navigating to your AndroidSDK folder, going to the 'tools' folder and double-clicking the file called 'android'; if a popup opens asking you what you want to do with it click 'Run'.
- Using this command:
Code:
/home/<your-user-name>/Downloads/AndroidSDK/tools/android
5. In Android SDK and AVD Manager, click on "Available packages". Check the box next to "Android SDK Tools, revision 8" and "Android SDK Platform-tools", and click on "Install Selected" then "Install". When prompted click "Yes" to restart ADB.
6.You should now have a folder in /home/<your-user-name>/Downloads/AndroidSDK/ called "platform-tools".
7. Download fastboot here: http://developer.htc.com/adp.html
- Save it to the aforementioned platform-tools folder.
- Now, navigate to the file, right click it, click 'Properties', go to the 'Permissions' Tab and check 'Allow executing file as program'. Alternatively, run this command:
Code:
chmod +x /home/<your-user-name>/Downloads/AndroidSDK/platform-tools/fastboot
8. Now to set things up so adb and fastboot recognize your Nexus.
- Type this command into a terminal:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
- Paste this into the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
- Click save and close.
- Then, type the following terminal command:
Code:
sudo restart udev
9. Almost done with preparations! Run this command:
Code:
gedit .bashrc
And add this line to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Then save the file and close.
10. Download this file and save it to /home/<your-user-name>/Downloads/AndroidSDK/platform-tools: http://www.mediafire.com/?4pe5y906zr67nfh
10.We're ready to go!
Unlocking the Bootloader on your Nexus S and Rooting
Once again, unlocking your bootloader wipes everything on your device, including USB storage. Make a backup of any files you want to keep.
1. On your Nexus S, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
2. Power off the phone, and then hold down the Volume Up button and the Power button simultaneously to get into Bootloader/Fastboot mode. Connect your Nexus to the computer via USB.
3. Run this command to unlock your bootloader: (Once again WIPES EVERYTHING!)
Code:
fastboot oem unlock
Hit Enter and on your phone you will be prompted to confirm the action. (Use Volume +/- buttons to choose, power button to confirm choice) Confirm. At this point you will have an unlocked bootloader.
4. Copy/paste the following into the Terminal window:
Code:
fastboot flash recovery /home/<your-user-name>/AndroidSDK/platform-tools/recovery-clockwork-herring.img
5. Use the Volume +/- buttons to choose the Recovery option, then press the power button.
6. In Recovery, go to 'mounts and storage' and choose 'mount USB storage'.
7. Go to this page: http://forum.xda-developers.com/showthread.php?t=682828
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Link As..." Save that file to your desktop and then copy it to the main directory of your mounted phone.
8. Click 'Unmount'. Go back to 'mounts and storage' and choose 'mount /system'. Then Go Back and choose 'install zip from sdcard'>'choose zip from sdcard'>su-2.3.6.1-ef-signed.zip
9. When it's finshed installing, reboot. You are now rooted.
Special Thanks
Amin Sabet; I used your Mac guide as a reference and copy/pasted some things for convenience.
Koush; For first posting the unlocking information, developing ClockworkMod Recovery, and ROM Manager. You should probably hook him up with a donation. https://www.paypal.com/us/cgi-bin/w...63663d3faee8d9384d85353843a619606282818e091d0
Michael.B.; for suggesting adding the platform-tools folder to the .bashrc file.
Linus Torvalds; Without which we'd have neither Android nor Ubuntu.
Feel free to leave your comments on the guide below.
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ and platform-tools directories to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Click to expand...
Click to collapse
Be sure to update your username above.
Thanks a lot man, great guide. I didn't get my NS yet but this is gonna be very useful soon
ps: someone please stick this
Michael.B. said:
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
Be sure to update your username above.
Click to expand...
Click to collapse
Thanks for the tip. I added your tip and instructions for marking fastboot as executable.
Stuck due to the thread's usefulness
I forgot to ask: will this work for 64 bit systems?
nicholasbgr said:
I forgot to ask: will this work for 64 bit systems?
Click to expand...
Click to collapse
It should work just fine.
Thanks, got me rooted nice and quickly.
BlackOtaku said:
It should work just fine.
Click to expand...
Click to collapse
Yes but don't forget to install 32 libs.
Thanks for guide
Useful !
I'm waiting for cyanogen ROM so i'll able to install
Cheers
To confirm, yes it works on 64bit. I am running that
Thanks for the confirmation, guys
Good stuff, much appreciated.
I'm working on a simple shell script that should automate some of the more menial tasks while holding the user's hand through the process. I should have it up later today.
UPDATE: It's up! Link on the first page.
Sent from my Nexus S using XDA App
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
confiq said:
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
Click to expand...
Click to collapse
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
confiq said:
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
Click to expand...
Click to collapse
You shouldn't flash the recovery in the boot partition, I think that will cause problems with the phone period. :S
If you flash a custom boot.img (which this guide doesn't cover, though the script will flash Superboot) or kernel like Paul's Superboot, Supercurio's Voodoo Kernel, or Koush's insecure boot.img, OTA updates will fail to install. OTA updates will also reflash your recovery back to stock. One of the devs around here will probably start modifying them so they don't check the boot.img or reflash the recovery though.
Thanks for this! Worked perfectly
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
matroska said:
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
Click to expand...
Click to collapse
To fix the problem, before selecting zip file, you have to select mount /system. Then go to apply update.zip and proceed as usual.
Thanks
ok im stock
with this part fastboot oem unlock ware i put this code in my terminal of my pc ,,i put the cell in fasboot , i intall everiting if i put that code in my terminal
bash: /home/toshiba/.bashrc: line 2: syntax error near unexpected token `('
bash: /home/toshiba/.bashrc: line 2: `export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools# ~/.bashrc: executed by bash(1) for non-login shells.'
[email protected]:~$ fastboot oem unlock
fastboot: command not found
[email protected]:~$
what can i do or im doing wrong
I decided to put together a nice, straightforward tutorial on how to root and unlock your device. I have recently joined the Android scene myself, and the XDA forums have been invaluable to my learning process. I did hit a few brick walls in the process (and nearly bricked my phone as well) before I finally achieved a 100% working, rooted, unlocked ROM installation. So, I just wanted to put together a short, easy to follow guide on rooting and unlocking, which will (hopefully) avoid you extra time / headache.
Note: It is quite possible (though not certain) that you may lose your current data after the unlock process, so make sure to make a backup before you proceed.
Pre-Requisites:
- Atrix 4G (AT&T)
- Any firmware up to 4.5.91 (which is currently the latest official - as of 8/4/11)
- A Windows PC
- Current Motorola drivers for your device installed on your PC
Required Files:
Android Root and Unlock (2011-08-04).zip
This archive contains Fastboot, ADB, Tenfar's ClockWorkMod, Pudding (v2), and RSD Lite 5.3.1 (which is all you'll need). I put it together into one package to save you a bit of time, but all the credit goes to the original devs / creators.
Step 1 - Unlock the Bootloader
Extract the provided archive into a folder on your PC. Let's assume this is "C:\Atrix\".
Install RSD Lite 5.3.1 program on your Windows machine.
Make sure the latest Motorola USB drivers for your Atrix are installed on your PC.
Run the RSD Lite program on your PC.
Power down your Atrix and connect to your PC via USB.
Power on your Atrix, and immediately hold the Volume Down button until you see a menu pop up. This will be a text menu which will appear at the top of your screen, and the first option you'll see will be "Fastboot". Cycle the menu by pressing the Volume Down button until you get to the "RSD" menu option. Press the Volume Up button to launch the RSD support on your Atrix.
You should now see the phone appear in the RSD Lite program interface on your PC (in the bottom menu). Click on it. You should see some data about your Atrix appear in the Device Properties pane.
Hit the "..." button in the RSD Lite program to bring up the file menu and select the "4547-fix-try2.sbf" (included in the archive above). This is Pudding. It will unlock your Atrix in just a moment.
Hit the "Start" button. RSD Lite will flash your phone. This process will be fairly quick, and your Atrix will reboot once or twice. After your Atrix boots back into Android, power down your phone and close the RSD Lite program on your PC (ignore the warning... the process is complete... if it wasn't complete, you would not be able to boot up into Android).
Power down your Atrix once again. Leave it connected to your PC via USB. Power it on again and hold the Volume Down key to get to the boot menu (as before). This time, select the "Fastboot" option by pressing the Volume Up button.
Open up the Command Prompt on your PC (Run 'cmd', or browse for it in your 'Accessories' application menu) and go to C:\Atrix\ (or the directory where you extracted the provided archive).
Type in the following command:
fastboot oem unlock
You will see a message pop up with a warning about unlocking your device. Assuming you are here, you don't care about this, so just make note of the device id that the message provides.
Type in the command again, this time with the device id:
fastboot oem unlock ### ,
where ### is the device id you noted above.
Type:
fastboot reboot
That's it! Your device now has an unlocked bootloader.
Step 2 - Flash the ClockWorkMod
ClockWorkMod ("CWM") will allow you to make backups of your current system, as well as install mods and ROMs.
Reboot your Atrix.
Hold the Volume Down button as the device powers up to get to the boot menu. (You should be familiar with this by now.)
Select the "Fastboot" option from the menu by pushing the Volume Up button.
Type the following command from the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or the directory where you extracted the provided archive):
fastboot flash recovery recovery-en-goapk-0630-1029.img
Type into the command prompt:
fastboot reboot
You're done. You will now be able to launch CWM from the boot menu by selecting the "Android Recovery" option. Again, the boot menu cycles with the Volume Down key, and you make a selection with the Volume Up key. If you selected the wrong option, just pull your battery and try again.
Step 3 - Root Your Device
Rooting will give you the "Superuser" program in Android and allow you to provide superuser permissions to apps.
Reboot your device. As it powers on, hold the Volume Down button to get into the boot menu. Select the "Fastboot" menu option using the Volume Up key.
Type the following commands into the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or where you extracted the provided archive):
fastboot flash preinstall preinstall.img
fastboot reboot
Wait until your device boots fully into Android.
On the command prompt on your PC, type in the following commands, sequentially (executing each one-by-one, i.e., hitting the enter key after each):
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Done! You should now see the "Superuser" program as one of your Android's apps.
You are now unlocked, rooted and have CWM installed! You are ready to mod / ROM your Atrix.
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
antoniolcrd said:
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
Click to expand...
Click to collapse
Keep typing commands. It'll look like an error but keep going.
Sent from my MB860 using XDA App
Maybe out of luck...
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
This is one of the most n00b friendly guides I ever read. I can picture each step in my head as I read the instructions.
EDIT: This can go either way. I find it easier just to flash a ROM that's pre-rooted after unlocking the BL and installing CWM when it comes to step 3.
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
antoniolcrd said:
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
Click to expand...
Click to collapse
No way.
Nickel3ack said:
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
Click to expand...
Click to collapse
I´ve tried this command also. Pls check:
C:\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount/system -o remount,rw
/bin/mount/system -o remount,rw
bash: /bin/mount/system: Not a directory
[email protected]:/# cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: cannot create '/system/bin/su': Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Holy Crap I Think I'm Bricked
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Don't Panic
sonnyjame5902 said:
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Click to expand...
Click to collapse
No... don't worry. It's not a brick. Worst case you can restore the stock ROM.
1st Thing to try:
Basically, just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Before it can go to RSD, press the Volume Down key to get to Fastboot. Press Volume Up to get into Fastboot. Continue with steps 11-15. If this unlocks the bootrom, your error should disappear and you'll have your fully functional Android back.
2nd thing to try:
Just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Let the phone go into RSD. Go back to the RSD Lite program on your PC and repeat the Unlock process. Hopefully this time it will work.
3rd thing to try:
If not.... go to the Firmwares Superthread here on XDA and download the ROM appropriate for your carrier. Flash it onto your device via RSD (same method for flashing as above, except select the SBF you downloaded from the thread). This will get your device back into operation at least (you will lose all your data tho, so I'd try the other 2 methods first).
Friggin Cheers Mate! Got it all set up with option 2, and now I'm rooted and SU! And they said it couldn't be done after the Gingerbread OTA update! Bollocks!
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Dell2 said:
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Click to expand...
Click to collapse
The method for CWM described here is to flash the CWM directly to your recovery partition. All it needs is for the device to have an unlocked bootloader. You don't need to be rooted for this. Rooting only affects the way your Android OS permissions apps. You'll definitely need to be rooted to install CWM via ROM Manager or Titanium Backup. This is not that method.
can i just root with step 3 or do i have to unlock first?
Just out of curiosity I see in the OP that this should not affect data - what evidence is there of this being the case with 4.5.91 OTA?
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Nickel3ack said:
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Click to expand...
Click to collapse
This is just the first time I've read about being able to work on 4.5.91 without wiping the user data, so I was curious how this method differed from the others that were out there (mrramirezusa and the original pudding). Thanks for the info.
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
im getting error when i click start button it gives error of failed flashing
jeffhwitz said:
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
Click to expand...
Click to collapse
For RSD, none.
EDIT
Now having done this I can say it doesn't make any difference because this is all done outside of the Android Operating System.
Well, I did it and I did irritatingly lose everything in my /data. Luckily I've got everything backed up. Came from the 4.5.91 OTA and other than rooted was totally stock. Did give me a failed to boot 0x1000, pulled batt, restarted and did fastboot, did the unlock successfully (i.e. didn't flash any additional files so per the posts no reason I should have lost everything but I still did).
So, it does seem like more often than not doing this from the real actual unmodified OTA will cause a loss of user data as has been stated even though sometimes it doesn't seem to.
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. Download https://drive.google.com/file/d/0B6...drivesdk&resourcekey=0-W0btfSuQS9kq5iNNsCuWgQ and copy command file to cache/recovery folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this reboot to recovery and automaticly instal ww rom
This is fantastic, and smart move making a new thread...
Thanks,
sutekh137
And if you're not bricked, but can't update from the old software version. Copy and paste the commands in terminal emulator to force the update. Worked out great. Thanks for the tip.
slayeralive said:
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this your device will reboot to recovery and automaticly instal ww rom
Click to expand...
Click to collapse
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
bravesoul said:
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
Click to expand...
Click to collapse
I would assume root of the device itself as the next step is to put update.zip in /data
(Get me in on the fun. I helped. )
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tablet's memory root. Do I put it after mnt or before (I,m using root browser v2.3)? Like in the real root of everything? Another question. Must I use the zip inside another zip of the asus ww rom, or just the unzipped zip file. (LOL, confusing, i know).
(I dunno JerBear, they're very peculiar about what/who they blow)!!
bravesoul said:
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tab memory's root. Do I put it after mnt or before?
Click to expand...
Click to collapse
They should be symlinked to the same thing. Let me check...
Well. I only have the data folder that's in the root. Peculiar.
As for the zip file question, go for trial and error. Worst case scenario recovery rejects it.
(We'll work around it )
This is what I get in terminal emulator:
Me176c
bravesoul said:
This is what I get in terminal emulator:
Click to expand...
Click to collapse
You need that command only when you are using ADB over PC
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Me176c
bravesoul said:
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Click to expand...
Click to collapse
Use zip inside original.
slayeralive said:
Use zip inside original.
Click to expand...
Click to collapse
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Me176c
bravesoul said:
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Click to expand...
Click to collapse
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
slayeralive said:
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
Click to expand...
Click to collapse
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
bravesoul said:
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
Click to expand...
Click to collapse
Have fun with your "reward"
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Try again you did somethin wrong
Folow the steps download->extract->rename to update.zip->copy to /data folder->type in terminal
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
If you missd or typed wrong one character in terminal it wont work. Try again.
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
From the top, you must be rooted and you must know what that is.
I used the file from inside the download. I believe it has user in the name.
Rename this file to be update.zip.
Place update.zip into the data folder in the root directory, ie. root/data/update.zip.
Back out of that when it's finished and find the original post with the instructions, touch it and touch the message symbol like you are going to reply.
Copy all of the commands from after su, to the end.
Open terminal emulator, Type su and give root permission at the prompt, touch and paste, you should see what you copied, if you don't, do it again. If you do, touch enter and the process will begin.
Do not do anything until the device reboots COMPLETELY. It will go through several reboots, just wait.
Viola, you will be updated.