[GUIDE] STOCK (8.2.3.9/8.2.3.13/8.4.4.5) to 3.1 (PRIME! v1.4) + Overclock! - Eee Pad Transformer Android Development

This guide is for you if you currently have a STOCK EEE Pad transformer running on the 8.2.3.9, 8.2.3.13, or 8.4.4.5 update If you are already rooted and have CWM, skip to part 3 or 4 as appropriate
I rooted and upgraded to 3.1 yesterday and found the guides a bit scattered (and may be hard for Android newcomers to understand). I thought I'd write a new consolidated step-by-step guide for everyone
IF YOU WOULD LIKE A VIDEO TUTORIAL, PLEASE LET ME KNOW! IF THERE'S ENOUGH INTEREST, I'LL MAKE ONE!
SKIP TO PART 2 IF YOU ARE ALREADY ON 8.2.3.9
REQUIREMENTS:
-MicroSD card (THIS MUST BE IN YOUR TRANSFORMER AT ALL TIMES DURING THIS PROCESS!)
-Patience
-Brain
If you'd like to download all of the files first, the steps highlighted in GREEN contain files you need to download.
DISCLAIMER: As always, this guide is for information purposes only. I cannot be held responsible for any damage you may incur on your device. Proceed at your own risk!
ALSO, THIS WILL WIPE YOUR INTERNAL/EXTERNAL SD CARD SO HAVE EVERYTHING BACKED UP JUST IN CASE
PART 0: ADB and Drivers
1) Download adb from here: http://www.mediafire.com/file/vix9hcmm23ohtbc/adb.zip
and the ASUS ADB Drivers from here: http://www.mediafire.com/file/rgr9d77picbxwz3/ASUS_Android_USB_drivers_for_Windows.zip
2) Unzip the contents of adb.zip to C:\Android
3) Install the ASUS ADB drivers
4) On your transformer, go to Settings -> Applications -> Development and make sure "USB Debugging" is checked
5) Plug in your TF into your computer via USB
6) Open a command prompt (WinXP: Start -> Run -> cmd | Vista/7: Start -> type "cmd" and hit enter)
7) Type
Code:
cd C:\Android
8) To test whether ADB is working, type the following into the command prompt and hit enter
Code:
adb devices
If you've done everything correctly up to this point, you should see a bunch of numbers listed under "List of devices attached"
PART 1: Downgrading to 8.2.3.9
The 8.2.3.13 update is currently unrootable so we'll need to downgrade to 8.2.3.9 first
1) Grab the 8.2.3.9 upgrade from here (THIS IS FOR THE US SKU ONLY!): http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
If you have the WW SKU (not in the US), download this one: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_WW_epad_user_8239.zip
If you have the TW SKU, download this one: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_TW_epad_user_8239.zip
2) Open up the file you downloaded in step 1 and unzip the Asus folder onto the ROOT directory of your microSD card. Make sure you copy the entire Asus folder and not just the files inside it!! The transformer will NOT detect the update file if there is no Asus folder on the root of your SD card.
3) Insert your microSD card into your Transformer. On the bottom right hand corner in the notification area, there should be a message saying that an update has been detected. Tap that message to start the update. Let it do its thing (it'll take about 5-10 minutes and reboot once it's done)
PART 2: Rooting and installing CWM
Now we'll need to root and install Clockwork Mod Recovery
4) Download the following root package: http://www.mediafire.com/file/1otzpglspbfb9p8/TF101_ROOT.zip
5) Unzip the contents of the root package into C:\Android
6) Open a command prompt and navigate to C:\Android (type "cd c:\Android" without the quotes)
7) Type the following commands in order
Code:
adb push gingerbreakBB /data/local/
Code:
adb shell chmod 777 /data/local/gingerbreakBB
Code:
adb shell
Code:
/data/local/gingerbreakBB
This should execute the gingerbreak program which will do the dirty work for us After about 5-10 minutes, you should be presented with a "#" symbol, which means root has been acquired.
DO NOT CLOSE THIS WINDOW!!
If you get an error, type "exit" (without quotes) and hit enter. Then reboot your TF and try it again:
Code:
adb shell
Code:
/data/local/gingerbreakBB
8) Download hashmyfiles.zip from: http://www.mediafire.com/file/o1tkpx159919hp8/hashmyfiles.zip
This program calculates the MD5 checksum of a file. We need to make sure our CWM file isn't corrupted or else you can brick your Transformer.
9) Run hashmyfiles and drag CWM_BLOB_V5 from C:\Android into the window. The MD5 checksum should be 8c9ef19b726e76fd73de4632db7e4288. If this doesn't match, redownload the root package and try again.
10) Open a new command prompt window and navigate to C:\Android once again
11) Type the following in order
Code:
adb push CWM_BLOB_V5 /data/local
Code:
adb pull /data/local/CWM_BLOB_V5 cwmblob_retransfer
There should now be a file in C:\Android called "cwmblob_retransfer". Drag this file into hashmyfiles and see if the MD5 checksum is 8c9ef19b726e76fd73de4632db7e4288. If it isn't, repeat step 11 and try again.
12) Return to the shell I told you to keep open in step 7 and type
dd if=/data/local/CWM_BLOB_V5 of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
13) Your TF will reboot (if it doesn't reboot by itself, do it manually) and you will see a progress bar on the ASUS EEE Pad logo splash page.
14) Your device is now rooted with CWM installed!
PART 3 (OPTIONAL, HIGHLY RECOMMENDED): CWM3.1.0.1 mod by solarnz
This part installs a modded ClockworkModRecovery developed by solarnz. It skips /data/media (your internal storage partition) during Nandroid backups and factory wipe/resets. This way, your internal storage isn't wiped during nandroid backup/restores.
15) Download the modded CWM from here: http://dl.dropbox.com/u/13093938/XDA/Transformer/recovery-3.1.0.1-solarnz-R3-240511-1908.zip
MD5 checksum is 4470bee75f3318f07ec1eb5ddcee1f96.
16) Move the zip file (do not unzip) to the root of your microSD card and insert into your Transformer.
17) Reboot your Transformer into CWM:
Turn Transformer off
Hold down the POWER button and the VOLUME DOWN button simultaneously until you see a message on the top left portion of the screen
When you see this message, release the two buttons and immediately press VOLUME UP as the message states
18) Scroll down to "Install Zip From SD card" using the VOLUME DOWN button and hit the power button to select it
19) Scroll down to "Choose Zip form SD Card" and hit the power button
20) Select "recovery-3.1.0.1-solarnz-R3-240511-1908.zip" and flash it!
21) Reboot your Transformer!
PART 4: PRIME! v1.4
22) Download the latest build of PRIME! v1.4 from here: http://forum.xda-developers.com/showthread.php?t=1052380
23) Make sure you verify the MD5 checksum before you transfer it!
24) Copy the ROM zip file over to the root of your microSD card and reboot your Transformer into CWM
Turn Transformer off
Hold down the POWER button and the VOLUME DOWN button simultaneously until you see a message on the top left portion of the screen
When you see this message, release the two buttons and immediately press VOLUME UP as the message states
25) Repeat steps 18-20, but this time, select the PRIME! ROM zip file and flash that.
26) BAM WELCOME TO Rooted HONEYCOMB 3.1!!!
PART 5 (optional): Overclocking
In order to overclock, we will need to use a custom kernel. The only custom kernel as of this post is the Clemsyn-Blades overclocking kernel (currently on version 5). It offers up to a 1.6Ghz overclock (stock is 1Ghz)! Not all Tegra2 processors can run at this speed though so your mileage may vary!
27) Grab the latest overclocking kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1109630
28) Copy the kernel zip file to your internal SD card
29) Reboot into ClockworkMod Recovery and make a Nandroid backup by going to "Backup and Restore".
30) Install the kernel by going to "install zip from SD card" and selecting the kernel file
31) Wipe the cache by selecting "Wipe cache partition"
32) Wipe the dalvik-cache by selecting "Advanced" then "Wipe Dalvik Cache)
33) Reboot and grab CPU Master from the Market
34) Set your overclock and you're good to go If you get lockups, try reducing the overclock
FAQ/Troubleshooting:"]
Q: HELP! I closed the shell window when I wasn't supposed to! Now it just tells me "Cannot copy bootmsh. Permission denied"
A: Run the following commands in a new terminal window and start over
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
Q: CWM gives me the error: "E:can't mount /sdcard"
A: Format your SD card with your computer, and try copying the files onto the SD again.
CREDITS:
Androidroot.mobi for the original rooting guide
solarnz for the modded CWM
Roach2010 for making PRIME! v1.4
clemsyn for the Clemsyn-Blades overclocking kernel
Thanks for reading If you're feeling generous, feel free to buy me a beer

Awesome guide mate, good work.

Roach2010 said:
Awesome guide mate, good work.
Click to expand...
Click to collapse
Wouldn't be possible without your work on Primordial

PART 1: Downgrading to 8.2.3.9
The 8.2.3.13 update is currently unrootable so we'll need to downgrade to 8.2.3.9 first
2) Open up the file you downloaded in step 1 and unzip the Asus folder onto the ROOT directory of your microSD card. Make sure you copy the entire Asus folder and not just the files inside it!! The transformer will NOT detect the update file if there is no Asus folder on the root of your SD card.
3) Insert your microSD card into your Transformer. On the bottom right hand corner in the notification area, there should be a message saying that an update has been detected. Tap that message to start the update. Let it do its thing (it'll take about 5-10 minutes and reboot once it's done)
I have to downgrade from 3.1 US leaked to 8.2.3.9 WW the method that you wrote does not work (for me) I tried several times but the update stops almost instantly after reboot with an exclamation mark..
some help?

MimiK said:
PART 1: Downgrading to 8.2.3.9
The 8.2.3.13 update is currently unrootable so we'll need to downgrade to 8.2.3.9 first
2) Open up the file you downloaded in step 1 and unzip the Asus folder onto the ROOT directory of your microSD card. Make sure you copy the entire Asus folder and not just the files inside it!! The transformer will NOT detect the update file if there is no Asus folder on the root of your SD card.
3) Insert your microSD card into your Transformer. On the bottom right hand corner in the notification area, there should be a message saying that an update has been detected. Tap that message to start the update. Let it do its thing (it'll take about 5-10 minutes and reboot once it's done)
I have to downgrade from 3.1 US leaked to 8.2.3.9 WW the method that you wrote does not work (for me) I tried several times but the update stops almost instantly after reboot with an exclamation mark..
some help?
Click to expand...
Click to collapse
Did you initiate the update from the notification? Also, do you have the US or WW version (hardware-wise, not the currently installed software)

r34p3rex said:
Did you initiate the update from the notification? Also, do you have the US or WW version (hardware-wise, not the currently installed software)
Click to expand...
Click to collapse
start from the notification, my hardware is WW (italian) with 3.1 US leaked

Did you download the WW downgrade file? I just added it to the guide

r34p3rex said:
Did you download the WW downgrade file? I just added it to the guide
Click to expand...
Click to collapse
yes, but it did not work for me .. I solved it with a guide found on a French forum.
1. I renamed the file WW_epad-user-8.2.3.9.zip in EP101_SDUPDATE.zip
2. I put it in the root of microsd
3. restarted with vol down + power, then vol up
4. I waited until the end of the installation
5. I restarted with vol down + power and I did the wipe
now have 3.0.1 ww 8.2.3.9 and I'm ready to root, and primordial
thanks very much !

I'm getting to the part right after rooting and at the bottom it says:
[!] dance forever my only one
# _
when I go to type something in this window nothing happens...any advice?
UPDATE: FIXED! My cmd prompt must have frozen...Just had to run: adb shell rm /data/local/tmp/boomsh & adb shell rm /data/local/tmp/sh and start over from step #7. Have clockwork installed and am about to flash primordial 3.1.

dude.... awesome work...
But u wouldnt believe how retarded people can get.
So despite of the huge big red "do not close the shell", i closed it!
now when i start over from the beginning, i get "cannot copy boomsh. : permission denied". WAT DO I DO???

MimiK said:
yes, but it did not work for me .. I solved it with a guide found on a French forum.
1. I renamed the file WW_epad-user-8.2.3.9.zip in EP101_SDUPDATE.zip
2. I put it in the root of microsd
3. restarted with vol down + power, then vol up
4. I waited until the end of the installation
5. I restarted with vol down + power and I did the wipe
now have 3.0.1 ww 8.2.3.9 and I'm ready to root, and primordial
thanks very much !
Click to expand...
Click to collapse
Cool, good info to have

psycho2097 said:
dude.... awesome work...
But u wouldnt believe how retarded people can get.
So despite of the huge big red "do not close the shell", i closed it!
now when i start over from the beginning, i get "cannot copy boomsh. : permission denied". WAT DO I DO???
Click to expand...
Click to collapse
Run the following commands, and start over
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh

Can this be used with netformer kernal? I installed and it wouldnt boot. If it cant is there another kernal that will make it overclock.

So I got my tablet downgraded to 8.2.3.9, and when I run the gingerbreakBB from the shell, it runs for a few minutes and it shows the following...
Code:
[*] vold: 0918 idx: -0021540
[*] vold: 0918 idx: -0021539
--code break--
[*] vold: 0918 idx: -0020901
[-] Bad luch. Fixed vold?
$
So the fact that it didn't show #, I'm assuming it failed. I ran the gingerbreakBB again from that $, and got this.
Code:
$ /data/local/gingerbreakBB
/data/local/gingerbreakBB
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Detected honeycomb! Starting honeybomb mode (scale=10).
[+] Found system: 0xaff181a1 strcmp: 0xaff37b85
[+] Found PT_DYNAMIC of size 240 (30 entries)
[+] Found GOT: 0x00017368
[+] Using device /devices/platform/sdhci-tegra.2/mmc_host/mmc1
[*] vold: 0918 GOT start: 0x00017368 GOT end: 0x000175e8
Now I get a permission denied if I try typing su at the shell. What happened? What do I need to do??

mike6200 said:
Can this be used with netformer kernal? I installed and it wouldnt boot. If it cant is there another kernal that will make it overclock.
Click to expand...
Click to collapse
3.0.1 kernels can't be used with 3.1. Until ASUS releases the source of the 3.1 kernel, I'm afraid we won't have any custom kernels
tycoonbob said:
So I got my tablet downgraded to 8.2.3.9, and when I run the gingerbreakBB from the shell, it runs for a few minutes and it shows the following...
Code:
[*] vold: 0918 idx: -0021540
[*] vold: 0918 idx: -0021539
--code break--
[*] vold: 0918 idx: -0020901
[-] Bad luch. Fixed vold?
$
So the fact that it didn't show #, I'm assuming it failed. I ran the gingerbreakBB again from that $, and got this.
Code:
$ /data/local/gingerbreakBB
/data/local/gingerbreakBB
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Detected honeycomb! Starting honeybomb mode (scale=10).
[+] Found system: 0xaff181a1 strcmp: 0xaff37b85
[+] Found PT_DYNAMIC of size 240 (30 entries)
[+] Found GOT: 0x00017368
[+] Using device /devices/platform/sdhci-tegra.2/mmc_host/mmc1
[*] vold: 0918 GOT start: 0x00017368 GOT end: 0x000175e8
Now I get a permission denied if I try typing su at the shell. What happened? What do I need to do??
Click to expand...
Click to collapse
Reboot and try running gingerbreakBB again

r34p3rex said:
Reboot and try running gingerbreakBB again
Click to expand...
Click to collapse
After rebooting the tablet, rm the gingerbreakBB and recopying it to /data/local/, I re-ran the gingerbreakBB from shell, not showing any progress yet. Going to give it to 10:45 EST to report what's happened.
Thanks.

Can i just install a 3.0.1 over my 3.1
I am rooted

tycoonbob said:
After rebooting the tablet, rm the gingerbreakBB and recopying it to /data/local/, I re-ran the gingerbreakBB from shell, not showing any progress yet. Going to give it to 10:45 EST to report what's happened.
Thanks.
Click to expand...
Click to collapse
After 11 minutes, the prompt never did anything. Closed prompt, reopened and rm gingerbreakBB from shell. Turned tablet off, inserted sdcard (per instructions from http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/) says sdcard must be in at all times, which I did not have. Copied gingerbreakBB back to /data/local/, re ran the program from shell and now it's actually doing something.
Just finished, and showed #. That proves that you MUST have a MicroSD Card inserted at all times during the root process. Might want to add that to your guide. Now I will finish up, and let you know how it goes.
Thanks!

Nice guide! Wish it was out for me when i was doing this stuff to my TF the other night!

tycoonbob said:
After 11 minutes, the prompt never did anything. Closed prompt, reopened and rm gingerbreakBB from shell. Turned tablet off, inserted sdcard (per instructions from http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/) says sdcard must be in at all times, which I did not have. Copied gingerbreakBB back to /data/local/, re ran the program from shell and now it's actually doing something.
Just finished, and showed #. That proves that you MUST have a MicroSD Card inserted at all times during the root process. Might want to add that to your guide. Now I will finish up, and let you know how it goes.
Thanks!
Click to expand...
Click to collapse
Good to know! Will add it
mike6200 said:
Can i just install a 3.0.1 over my 3.1
I am rooted
Click to expand...
Click to collapse
Do you have CWM installed? Are you on official 3.1?

Related

[GUIDE] How To Root The Sprint CDMA Hero (Windows)

I have compiled this guide from the other one posted on this forum, the discussion therein, and my own knowledge. If you have any suggestions on making it better or to correct any mistakes I may have made please let me know.
This guide is intended for Windows and includes detailed instructions. It will cover the steps necessary to root, flash the new recovery image, create a full backup. This will work with software versions 1.29.651.1 and 1.56.651.2 (aka Android 1.5). If you have updated to 2.1 please following this guide here. I am not responsible for any damage done to your phone using this guide. Root at your own risk.
I have put to together a video on YouTube for you to follow along as well. The version numbers of certain files are now outdated in the video so change file names as necessary.
If you own a non-Sprint Hero, you will need to do some extra steps. Follow the guide in the How to Root Non-Sprint CDMA Hero thread.
Step 1: Download the Android SDK from http://developer.android.com/sdk/index.html The Windows file is called android-sdk_r06-windows.zip. Extract the files to your C: drive so that you now have the folder C:\android-sdk-windows
Step 2: Download the asroot2 exploit file from http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154 Extract asroot2.zip to C:\android-sdk-windows\tools folder.
Step 3: Download the Hero recovery image from http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1g Place this file in C:\android-sdk-windows\tools as well.
Step 4: Make sure USB Debugging is off by going to Settings>Applications>Development. Now connect the phone to your PC via USB cable.
Step 5: Mount your sdcard; Browse to the HTC Sync folder and install HTC Sync on your pc. After it is done installing unmount the sdcard then enable your USB debugging.
Step 6: Open a command prompt by clicking the Start button and typing cmd into the search box and pressing enter or found under All Programs>Accessories.
Step 7: You will now enter a series of commands which I will place inside code boxes to indicate the entire command. You may copy and then paste them into the command prompt window by right clicking. Only enter one command at a time.
1:
Code:
cd C:\android-sdk-windows\tools
2:
Code:
adb devices
If you've been following this guide you will see your 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 AFTER you connect the USB cable. Continue on once you get the proper phone serial output.
3:
Code:
adb push asroot2 /data/local/
4:
Code:
adb shell
5:
Code:
chmod 0755 /data/local/asroot2
6:
Code:
/data/local/asroot2 /system/bin/sh
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#​Now for a few last commands.
7:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
8:
Code:
cd /system/bin
9:
Code:
cat sh > su
10:
Code:
chmod 4755 su
You are now officially rooted. A few more steps and you will have flashed the recovery image.
11:
Code:
exit
12:
Code:
exit
13:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
15:
Code:
adb shell
16:
Code:
su
17:
Code:
cd /sdcard/
18:
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
19:
Code:
reboot recovery
Step 8: This is the last command; you may now close the cmd prompt. This will cause your phone to boot into recovery mode; it should take no longer than 30 secs. The third option on the list is "- Backup/Restore"; select it. Now, select the first option "- Nand backup". The phone will prompt you to press HOME to confirm which is want you want to do. The backup will begin. You will see the screen say, "Performing backup : .........." When done, the bottom of the screen will say "Backup complete!" and you will be given the menu options again. Go back to the main menu and select reboot system. Rebooting your phone after installing the new recovery image may take several minutes.
Step 9: Once your phone is fully booted, mount the sdcard. You will see a folder called "nandroid"; I highly recommend you copy this to your pc in case you lose your sdcard data or reformat it. Your phone is rooted, 100% backed up, and ready to install a custom rom if you wish!
wow dude,
instructions worked great on Win7
i was able to download the missing usb_drivers by running SDK Setup in C:\android-sdk-windows, and selecting the usb driver from the available packages. I was unable to download the index for the SDK Setup program until I enabled "force http://" in the settings menu.
had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
izanagi said:
wow dude,
i'm about to follow these instructions. thank's for the precise list!
(btw, about to try it on Win7.. may have to change some folder pathing but we'll see)
okay.. typo on the first command in parentheses, and I'm missing the usb_drivers folder (do you have it / can sent it to me) so am unable to install the device in win7.
Click to expand...
Click to collapse
Heh, thanks for the misspell heads up. I did my rooting from Win7 pc; it automatically installed correct drivers for me. To check go to the Control Panel>View devices and printers. You see one device named "Android Phone". Otherwise as far as Ive heard installing HTC Sync installs proper drivers.​
izanagi said:
*** edit had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
**** edit: all done.. your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
Click to expand...
Click to collapse
Thank you for taking the time help make my guide better. I'm very glad to know there are little to no hiccups.
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
detox702 said:
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
Click to expand...
Click to collapse
This guide is for the CDMA Hero not the Eris!
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no. I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip". This is done from the boot menu. Does the rom load automatically? Did I do something wrong? I got root with no problem. A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Never mind. I held down Home and Power at
the same time instead of Home THEN power! ARRGH! Loading up now as I type. Sorry.
ELIMINATED said:
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no.
I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip".This is done from the boot menu.
Does the rom load automatically? Did I do something wrong? I got root with no problem.
A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Click to expand...
Click to collapse
yuck... break up your sentences, that's alot of crap to throw on someone all at once... and the bold doesn't help it any.
check to see if you have the custom recovery installed....
-turn off phone
-hold vol down + power
-should search for some stuff then give three options
-press "home" to enter recovery image
do you see "!" and a phone.... does it just hang or do you see a green/yellow menu?
At the end of his post he says he figured it out. He wasn't holding down home key
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
awesomeindeed said:
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
Click to expand...
Click to collapse
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
thank you TS. I've been lurking xda for a couple years now when i had the mogul and tp. First time on an android device. Thank you for your time in helping me.
someone buy this man a drink!!!
Invaluable piece of work right here, helped me get it done in no time at all....real clear concise and very helpful....REQUEST THIS BE A STICKY!!!!!
fenske09 said:
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
Click to expand...
Click to collapse
That was the name of the zip file not the extracted folder.
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
newtodroid said:
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
Click to expand...
Click to collapse
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
theresthatguy said:
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
Click to expand...
Click to collapse
also make sure you have the heroc version there's a hero and heroC, i messed that up once and had similar results
new ROM
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
kristaps said:
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
Click to expand...
Click to collapse
you converted your sd card to fat32,ext2,swap and now the apps are looking for the program on your sd card,
turn off your phone
take out sd card
turn on phone
uninstall app
turn off phone
put in sd card
turn on phone
reinstall app
this should fix you

[ROOT] ~~~ HTC EVO - Auto Root ~~~ v2.5 (4/25/11)(deprecated)

This tool is now deprecated. To root your Evo 4G running Gingerbread you will need to use the Revolutionary tool that can be found at http://www.revolutionary.io.
I'm sorry to do it but due to the ridiculous amount of people who are still asking for help rooting gingerbread, I will no longer be supporting this tool what so ever. Any further emails I receive about it will be deleted.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I am proud to present the HTC EVO Auto Root script! It took me awhile but I finally got it fully automated, it probably would have been easier using VB to write it but I wanted it to be readable by everybody. I don't have working scripts for Linux or Mac yet but for older phones you should be able to follow the Alternative Method and use the code included at the end of the post with minimal changes. If you are new to rooting the Evo you should check out the Rooting Information and Common Problems thread to familiarize yourself with some of the screens you will see. At times your phone may shows ominous looking icons that look bad but really aren't, at times like that it is important that you don't panic and do anything that could damage your phone.
This will make a backup of your WiMAX partition and the RSA keys that are stored on it; backing up your RSA keys separate is not necessary. It will save it in the AutoRoot folder so be sure not to delete it.
If you run into any problems please include the following information with your post: Any methods you have previously tried to root with, what it did last plus any error messages it may have given (if you can right click, select all and copy it from the terminal), and if you are in the bootloader we need to know what the top two lines say. Running this will create a log file named: autorootlog.txt. Please post this as well.
Any feedback no matter good or bad is appreciated! Let me know how it works for you.
Randy (randyshear on youtube) has made a great video of the process if you would like to get an idea of what to expect before hand. It is important to note that, depending on your phone, the process may be slightly more involved or require more or less time.
HTC EVO 4G ** ROOT AND NAND UNLOCK ** AUTOROOT V 2.2 ** HOW TO **
This has been confirmed working with:
Software versions 1.32, 1.36, 3.29, 3.30 & 3.70
hBoot Version .76, .93, .97, 2.02 & 2.10
Thanks go to
HTC for making the phone to begin with
Sebastian Khramer for his rageagainstthecage exploit
Toastcfh for his tutorial and all of his work on improving the Evo, a lot of this is borrowed from his previous work
Amon_RA for his recoveries and for his quick work creating a recovery compatible with the new NAND blocks
Calkulin for collecting all of the radios and update images
Whosdaman, Football and Sniper911 for sharing the RUUs with us
The Unrevoked Crew for all of their hard work on the Unrevoked Forever s-off tool
amoamare and Zikronix for all of their hard work on rooting phones with the 2.02 hboot
chris1683 for his Sprint Lovers ROM
Netarchy for all of the great kernels
A huge thanks goes out to Dan0412 who took the time to debug this for version 003 2.02 phones
Schnick1 and tauzins for their help with getting ADB to act right
Props go to RyanZA and anyone else who worked on the z4root app. I wouldn't have got 3.70 rooted as fast as I did if I didn't have their app to learn from.
You Will Need:
A windows machine
HTC Sync that can be found on Sprint's website. HTC Sync 2.0.35.exe
At least 1 GB of free space on your SD card
A full or close to full battery (your phone will not charge during part of this and if it dies you will be SOL, aka Bricked)
ADB debugging enabled (Settings > Applications > Development > ADB Debugging)
Your phone connected to your computer as Charge Only and HTC's Evo drivers / HTC Sync installed.
The AutoRoot.zip File that can be found in this post
[*]I highly recommend you have the appropriate RUU, or PC36IMG, downloaded before you start. It is always good to have and if something does not go as planned it can get your phone back up and running with minimal down time.
Click to expand...
Click to collapse
IF YOU HAVE PREVIOUSLY TRIED ROOTING YOU MUST RESTORE FROM A RUU BEFORE RUNNING THIS. IT WILL NOT ROOT IT UNLESS YOU DO THIS.
Instructions:
This will try to back up your apps but it's not always able to, you will also lose all of your settings. Titanium Backup works well to save your apps however you will need to use z4root to temporarily root before you will be able to use it.
Download HTC Sync from Sprint's website here and install it. You may need to use the 'Repair' option for it to replace any old drivers.
Extract AutoRoot.zip into a folder that is easy to find and then open the folder.
Right click on 'AutoRoot.bat' and run it as Administrator.
Once it finds your phone it will start by checking out what kind of setup it uses and then attempt to get root access. If it fails usually it's from too many active apps or the phone being used, if so you will need to restart it before trying again. If you are using 3.70 it will let you know when it is running by blurring the screen.
When it is ready it will reboot your phone into the boot loader. Then, depending on your phones setup, it will either enter RUU mode and automatically flash the debugging firmware or give you instructions on how to flash it from the hBoot.
If you have to flash it manually just push Power to select "BOOTLOADER" and say Yes when it asks to flash the PC36IMG.zip. It will complain part of the way through about Boot Loader and/or radio errors and then skip them, this is normal. Once it finishes say No when asked to reboot and use the Vol Down button to highlight Recovery. Then press Power to select it.
If you are entering the Recovery your phone will show a Red Triangle with an Exclamation mark inside, at this point the script will take back over and attempt to flash Unrevoked Forever.
After it finishes flashing the engineering bootloader, or Unrevoked Forever, it will reboot into the bootloader and see if your NAND is unlocked. If so it will flash the Sprint Lovers ROM along with the Recovery and updated Radios. Afterward it may boot into the ROM and attempt to restore your Apps before finishing, try not to interrupt it until it tells you it has finished.
Once it's fully rooted and you have your phone set back up it's a good idea to make one more NANDroid with everything up to date. Then make one more backup of your WiMAX partition in case something happens to the first one.
Click to expand...
Click to collapse
If you have an older phone and don't want to flash Unrevoked Forever or Sprint Lovers w/ the radio updates you can have it skip them. It will just flash the engineering bootloader to unlock the NAND and then flash the recovery directly from there. You will need to update everything and flash a custom ROM on your own. This will only work if your phone has a version .9x hBoot.
Instructions for Quick method:
This will completely wipe your phone. If you would like to back up your apps you can use Titanium backup to save them. It also has an option to save the system files but this can result in a buggy ROM afterward.
Extract AutoRoot.zip into a folder that is easy to find.
Open a DOS prompt by running the OpenShell file.
Type 'autoroot quick' and press Enter
It will then flash the engineering bootloader and the recovery through fastboot. Once it is finished you can use the bootloader menu to boot into the recovery and make a NANDroid, flash a ROM, radios, etc.
Click to expand...
Click to collapse
Links:
Downloads
AutoRoot v2.5 - Full Root Zip (MD5: 5E1BF365F3B5479329896BD55C33678E)
AutoRoot v2.5 - Tools Only (MD5: 5DBA70A8CDD052A9908E4F43D6BBC669)
The following are the ROMs pulled out of the RUUs, you can flash them by renaming and putting it on your sd card or from your computer with fastboot using the included FlashZip script.
Sprint Evos (USA):
3.29.651.5_PC36IMG.zip (MD5: 2F5046C0FC6FE61114EBC53D5997B485)
3.30.651.2_PC36IMG.zip (MD5: 4A2CAB264244C79B2E2BE9E3CFE2B503)
3.70.651.1_PC36IMG.zip (MD5: 7056D42812AA5DF03FCC8DDDC2B64E85)
KDDI Evos (Japan):
1.05.970.1_PC36IMG.zip (MD5: 78F9E8BFEE705F34790A46C258268F02)
Sources
How to unlock Nand Protection ~ Part-2
RA-evo-v1.8.0 (a modified version is included)
RUU to restore 3.29.651.5
RUU to restore 3.30.651.2
RUU to restore 3.70.651.1 (Thanks to 911Sniper for the original mirror)
Sprint Lovers ROM (a modified version is included)
Click to expand...
Click to collapse
Changes for v2.5
Script now checks for Admin Priveledges and kills HTC Sync Services for Sync 3.05
Fixed issue recognizing build numbers
It will attempt to back up Apps now
Checks branding in order to recognize KDDI Evos
Unrevoked forever will now be retried if it doesn't get run the first try
Changed it so it will leave the phones in Fastboot mode if it fails
Recognizes ADB issues easier now
Changes for v2.4
Updated the ROM and Recovery
The working directory is now saved correctly when the path has a space in it
Fixed an error checking the firmware version that would cause the script to close
Made it more capable of recovering when the phone is in an unknown state
Fixed the SD card not being recognized with Eclair
Some parts will check for the 'daemon' error messages and will call to fix it
Made it so the MTD data is not saved unless it is recognized
The script will continue if it times out while waiting on Unrevoked Forever
The WiMAX partition is backed up through the ROM at the very beginning instead of through the Recovery
Changes for v2.3:
Updated the ROM, Recovery and Radios
The script will now recognize your phone at any point in the process and will continue where it left off
Fixed the FlashRecovery script and made it so you can choose what to flash, just put your PC36IMG of choice in the folder with it and let it do the work
Fixed the version checker so it doesn't get confused with custom ROMs anymore
Quick mode checks your hboot version from the ROM now so it won't even try if you have a new bootloader
It is much more tenacious going into the recovery, hopefully fixing the issue with ADB dropping out there
Fixed a bug where the MTD block sizes were not always being remembered correctly
Added more checks to make sure the phone is where it's supposed to be throughout the process
Made it try harder to get the recovery log so it doesn't get missed as much
Tweaked the timing some so it moves a little bit quicker and you only have to hit a button twice to exit instead of three times
Fixed the infinite loops so they are now 95% shorter
Changes for v2.2:
Updated the recovery to Amon RA's version 2.2.1
MTD information for each phone is saved in case it is restarted and unable to find out.
Fixed a bug where pre 3.xx ROMs were not being recognized correctly.
Phones are explicitly called by their serial number to prevent confusion if an emulator starts or another phone gets plugged in.
Unresponsive ADB daemons are killed to help prevent them for hanging or randomly restarting.
Changed autoroot.log to autorootlog.txt to make it easier to attach
Minor bug fixes.
Changes for v2.1:
Updated the recovery to Amon RA's version 2.2
Minor bug fixes
Changes for v2.0:
Added an app to give ADB root and keep it active in 3.70
Updated Sprint Lovers and Amon RA
Removed the two separate kernels/recoveries for new and old phones
Added a battery life check before flashing
Checks Firmware versions in both the ROM and hBoot
Checks that the Misc partition was flashed properly
Fixed all of the bugs with Quick root, it no longer flashes Sprint Lovers if you run it with S-OFF
It automatically restarts adbd where it would occasionally reset itself and get hung up
It also kills adbd when it finishes so you can move/delete it
Changed the bat that restarted adbd so it kills it instead
Added a bat to flash AmonRA through Fastboot with non-Eng hBoots
Added a bat to open a Cmd prompt already in the autoroot folder
Rewrote a good portion of the script and cleaned it up a lot
Made it more flexible so it doesn't get lost as easily
Plus more I forgot
Click to expand...
Click to collapse
Contents of v2.5 Include:
adb.exe
adb-linux
adb-mac
adbWinapi.dll
adbWinusbapi.dll
AutoRoot.bat
check.bat
fastboot.exe
fastboot-linux
fastboot-mac
FindPhone.bat
FlashZip.bat
OpenShell.bat
StartRecovery.bat
amon_ra_1.8-mod/
res/
....AutoRoot.apk
....autoroot.ini
....dump_image
....Escalate.vbs
....Escalater.bat
....EscSC.lnk
....exploid.com
....FindPhone.bat
....flash_image
....ini.cmd
....mtd-eng.img
....PC36IMG_UD.zip
....PC36IMG_AmonRA-v2.3-hausmod_revA.zip
....PC36IMG-SprintLovers-AmonRA_2.3-hausmod_revA.zip
....radios.zip
....rageagainstthecage-arm5.bin
....recovery-RA-v2.3-hausmod_revA.img
....URFSOff.zip
....URFSOn.zip
....WatchPhone.bat
Notes:
Recovery is recovery-RA-supersonic-v2.3 with Netarchy's 4.3.2 CFS NoHAVS NoSBC NoUV
radios.zip is EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003
URFSOff.zip is the Unrevoked Forever S-OFF tool
URFSOn.zip is the Unrevoked Forever S-ON tool
Click to expand...
Click to collapse
As always, this will void your warranty and may possibly damage your phone. You and you alone are responsible for anything that you do. Everything contained in this thread is for informational purposes only.
Click to expand...
Click to collapse
IMPORTANT: Everything contained in this post is meant for phones with the older bootloader. If you have hBoot version 2.02 or ROM version 3.30 you must use the above method.
Old Universal Root
(Scroll Down for Alternate Method)
You Will Need:
A windows machine and basic knowledge of DOS or a Linux/Mac box with a little bit of determination
At least 1 GB of free space on your SD card
A full or close to full battery
ADB debugging enabled (Settings > Applications > Development > ADB Debugging)
Your phone connected to your computer as Charge Only
The EVORoot.zip File that can be found in this post
Click to expand...
Click to collapse
Instructions:
Extract EVORoot.zip into a folder that is easy to find and go to that folder. Then copy the 'moveme' folder out of that one and on to your sdcard. Once it finishes copying unmount/eject the SD card through windows and change your phone back to Charge Only.
Double click on 'runexploit' and let it run. When it asks if you want to flash the hBoot push 'y' and then {enter}. If there are any errors follow the instructions given to try and resolve them. It will automatically reboot your phone once it is ready for it. If all you see is the prompt flashing press Ctrl+C or close the window to exit and re-run it as Administrator.
When the bootloader comes up push the Power button and you should see it start searching for updates. When it gets to PC36IMG.zip it will ask if you want to update with it, push Volume Up to say yes.
*DO NOT TURN OFF THE PHONE OR LET THE BATTERY DIE WHILE UPDATING*
When it's finished push the power button to select 'fastboot' and use the volume buttons to select the yellow 'reboot' button. Push power one more time to select it and reboot your phone. It should start up rooted and ready to go, however you will still need a custom Recovery so you can make NANDroid back-ups and flash an up to date ROM.
Once the phone starts back up run 'flashrecovery' through explorer. It will automatically flash and then reboot your phone into Amon_RA's recovery. When it reboots you should see green text on a black background, if you see a triangle with an exclamation mark then you still have the stock recovery and need to reboot and try again.
Use the volume buttons to select Backup/Restore then push Power to select it.
Select Nand backup and push power. This will make an exact copy of your phone as it is. If you get an error that says 'run mobile-nandroid...." make sure you have at least 3 or 400MB free on your memory card. You can use USB-MS toggle to mount your SD card if you need to make room or copy a ROM to your phone. The moveme folder can also be deleted from your SD card at this point and you can make copies or move the backup once it is complete. Just make sure you have one good backup before continuing.
The NANDroids are saved under 'nandroid/??????????/backupfolder-date-time/'. The folders need to be moved whole.
Return to previous menu, select Wipe, then have it Wipe data/factory reset, Wipe cache & Wipe dalvik-cache. If you get stuck in a bootloop try these steps again and try wiping the SD:ext partition as well.
Return, then go in Flash zip from sdcard. Once there flash the Radios. It is again very important not to interrupt or reset the phone while the radios are being flashed, although it will probably want to reboot before flashing can be finalized, just follow the instructions.
Once it is finished Return to the previous menu and select Power Off. Then hold down the vol down button while turning the phone back on.
It will boot back up into the bootloader, select No if it asks to update or reboot. From here select Recovery and it should go back to the black background with green text.
Select Flash zip from sdcard and Flash ROM-Supersonic_3.30....zip. If you have a different ROM you want to use you can flash another one instead.
Once it is finished Return to the main menu and have it Reboot system. Your phone should start up normally and ask to be set up, complete the set up like normal.
When you have it set up and are sure everything is working properly I would make one more NANDroid so you have a copy with the updated radios. At this point you can also flash another recovery and do anything else you would normally do. Just be sure to use unrevoked forever if you plan on using a different hBoot.
Click to expand...
Click to collapse
Links:
Downloads
EVORoot.zip
EVORoot.zip - No bootloader, ROM or Radio updates
eng-PC36IMG.zip mirror 1, mirror 2
The following are the ROMs pulled out of the RUUs and renamed, make sure you use the correct version for your phone but if you aren't able to find out start with the 3.29.
3.29.651.5_PC36IMG.zip
3.30.651.2_PC36IMG.zip
If you are having trouble flashing custom ROMs try using this kernel (Thanks to xxbabiboi228xx)
Stock kernel #17
Sources
How to unlock Nand Protection ~ Part-2
All EVO Radio, WiMAX, PRI & NV versions
RA-evo-v1.8.0
RUU to restore 3.29.651.5
RUU to restore 3.30.651.2
Click to expand...
Click to collapse
Contents Include:
adb.exe
adb-linux
adb-mac
adbWinapi.dll
adbWinusbapi.dll
exploid.com
flashboot.bat
flashrecovery.bat
runexploit.bat
moveme/
.....eng-PC36IMG.zip
.....evo_radios_wimax_pri_nv_3.30.zip
.....flash_image
.....mtd-eng.img
.....rageagainstthecage-arm5.bin
.....recovery-RA-evo-v1.8.0.img
.....SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip
Click to expand...
Click to collapse
Alternate method
If you already have the EVORoot.zip file you can download the scripts below without the boot/ROM/radio.
Instructions:
Extract EVORoot.zip into a folder that is easy to find such as C:\EVORoot. Then copy the 'moveme' folder out of that one and on to your sdcard.
Open up a DOS prompt and go to the EVORoot directory. eg. 'cd C:\EVORoot'.
type: runexploit {enter}
It will scroll a few lines saying that the ADB server will be reset and to run it on the desktop, this is normal. If it says Permission Denied check to make sure your phone is set to charge only and your sd card is not mounted as a hard disk.
type: adb shell {enter}
If you see '$' then type: "./data/local/tmp/rageagainstthecage-arm5.bin", without the quotation marks, and push enter. After a few seconds it should kick you out to the \> prompt.
If you see '#' then type: exit {enter}
type: flashboot {enter}
If you don't see any errors let it continue, if you do see an error push Ctrl+X to stop
Your phone will then reboot, when it comes back up the bootloader option should be highlight. Press the power button to select it. It should then search for a second and ask if you want to install the pc36img.zip, push Volume Up for Yes.
*DO NOT TURN OFF THE PHONE OR LET THE BATTERY DIE WHILE UPDATING*
When it's finished go into fastboot and select the yellow 'reboot' through the menu, it should start up rooted and ready to go however you will still need a custom Recovery so you can make NANDroid back-ups and flash an up to date ROM.
Once the phone starts up do step #4 to check for root (# prompt), if it is a '$' try typing 'su {enter}'. If that does not work use runexploit and then check again. Return to the DOS prompt once finished.
type: flashrecovery {enter}
Let it continue as long as there are no errors, otherwise Ctrl+X will stop it. If you run this more than once you can ignore the file not found errors from when it first starts. When the phone reboots you should see green text on a black background, if you see a triangle with an exclamation mark then you still have the stock recovery.
Use the volume buttons to select Backup/Restore then push Power to select it.
Select Nand backup and push power. This will make an exact copy of your phone as it is. If you get an error that says 'run mobile-nandroid...." make sure you have at least 3 or 400MB free on your memory card. You can use USB-MS toggle to mount your SD card if you need to make room or copy a ROM to your phone. The moveme folder can also be deleted from your SD card at this point and you can make copies or move the backup once it is complete. Just make sure you have one good backup before continuing.
The NANDroids are saved under 'nandroid/??????????/backupfolder-date-time/'. The folders need to be moved whole.
Return to previous menu, select Wipe, then have it Wipe data/factory reset, Wipe cache & Wipe dalvik-cache. If you get stuck in a bootloop try these steps again and try wiping the SD:ext partition as well.
Return, then go in Flash zip from sdcard. Select and Flash ROM-Supersonic_3.30....zip. If you have a different ROM you want to use you can flash that one instead.
Flash the Radios, it is again very important not to interrupt or reset the phone while the radios are being flashed. It will probably want to reboot itself afterward, just follow the instructions.
Once it is finished Return to the main menu and have it Reboot system. Your phone should start up normally and ask to be set up, complete the set up like normal.
Once you have it set up and are sure everything is working properly I would make one more NANDroid so you have a copy with the updated radios. At this point you can also flash another recovery and do anything else you would normally do. Just be sure to use unrevoked forever if you plan on using a different hBoot.
Click to expand...
Click to collapse
Links:
Downloads
EVORoot.zip
EVORoot.zip - No bootloader, ROM or Radio updates
eng-PC36IMG.zip mirror 1, mirror 2
Click to expand...
Click to collapse
Contents Include:
adb.exe
adb-linux
adb-mac
adbWinapi.dll
adbWinusbapi.dll
flashboot.bat
flashrecovery.bat
runexploit.bat
moveme/
.....eng-PC36IMG.zip
.....evo_radios_wimax_pri_nv_3.30.zip
.....flash_image
.....mtd-eng.img
.....rageagainstthecage-arm5.bin
.....recovery-RA-evo-v1.8.0.img
.....SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip
Batch Files
runexploit.bat
Code:
adb shell "cat /sdcard/moveme/rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin"
adb shell "chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin"
adb shell "./data/local/tmp/rageagainstthecage-arm5.bin"
flashboot.bat
Code:
adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image misc /sdcard/moveme/mtd-eng.img"
adb shell "mv /sdcard/moveme/eng-pc36img.zip /sdcard/pc36img.zip"
adb shell sync
adb reboot bootloader
flashrecovery.bat
Code:
adb shell "mv /sdcard/PC36IMG.zip /sdcard/moveme/eng-PC36IMG.zip"
adb shell "mv /sdcard/moveme/evo_radio_wimax_pri_nv_3.30.zip /sdcard/evo_radio_wimax_pri_nv_3.30.zip"
adb shell "mv /sdcard/moveme/SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip /sdcard/ROM-SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip"
adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image recovery /sdcard/moveme/recovery-RA-evo-v1.8.0.img"
adb shell sync
adb reboot recovery
Click to expand...
Click to collapse
This uses HTC's eng hBoot to unlock NAND protection so it is relatively safe, but, as always, this will void your warranty and may possibly damage your phone. You and you alone are responsible for anything that you do. This is for informational purposes only.
Click to expand...
Click to collapse
Here are linux and mac versions. You just need to get adb from somewhere (I don't think the packaged windows version will work).
If it's in your path, just change all of the "./adb" to "adb", or if you copy the executable to the same directory as these scripts, leave them as is.
Put them in the same directory, as the kit, and they should work.
I haven't tested, but thought I would write them up quickly to help with mutli-os support.
runexploit.sh
Code:
#!/bin/bash
./adb shell "cat /sdcard/moveme/rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin"
./adb shell "chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin"
./adb shell "./data/local/tmp/rageagainstthecage-arm5.bin"
flashboot.sh
Code:
#/bin/bash
./adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
./adb shell "chmod 755 /data/flash_image"
./adb shell "/data/flash_image misc /sdcard/moveme/mtd-eng.img"
./adb shell "mv /sdcard/moveme/eng-pc36img.zip /sdcard/pc36img.zip"
./adb shell sync
./adb reboot bootloader
flashrecovery.sh
Code:
#!/bin/bash
./adb shell "mv /sdcard/PC36IMG.zip /sdcard/moveme/eng-PC36IMG.zip"
./adb shell "mv /sdcard/moveme/evo_radio_wimax_pri_nv_3.30.zip /sdcard/evo_radio_wimax_pri_nv_3.30.zip"
./adb shell "mv /sdcard/moveme/SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip /sdcard/ROM-SuperSonic_3.30.651.2_Rooted_BB_DeOdexed_Bash_ADP_BattPrcnt.zip"
./adb shell "cat /sdcard/moveme/flash_image > /data/flash_image"
./adb shell "chmod 755 /data/flash_image"
./adb shell "/data/flash_image recovery /sdcard/moveme/recovery-RA-evo-v1.8.0.img"
./adb shell sync
./adb reboot recovery
I'm getting a permission denied when I try to runexploit
Can you post an alternate mirror for the rootkit?
jacobzamarripa said:
I'm getting a permission denied when I try to runexploit
Click to expand...
Click to collapse
Do you have debugging enabled?
MJStephens said:
Do you have debugging enabled?
Click to expand...
Click to collapse
usb debugging. yes
jacobzamarripa said:
usb debugging. yes
Click to expand...
Click to collapse
Are you running cmd.exe as admin?
Do you guys have a youtube video of step by step for this? Because i cant even get past the third step
BrashL said:
Are you running cmd.exe as admin?
Click to expand...
Click to collapse
im not quite sure how. im on windows xp
jacobzamarripa said:
im not quite sure how. im on windows xp
Click to expand...
Click to collapse
Im pretty sure he just means that your on an user name on windows that has Master rights.
Bravo, bravo. You really outdid yourself on this hauss. What a fabulous tutorial for noobs. In my spare time, I would be happy to make a Mac version of this tutorial for you. I think the Mac part jut confuses people more. Seriously, great work. I will be referring people to this. Replaces the need to do 20 commands with like 4 homemade batch scripts. Pm me or email at [email protected] and I will build a Mac tutorial (giving you full credit of course)...
Confirm?
This looks and sounds awesome. I would LOVE a mac version of this and like to donate to good work
Can I get a confirmation from someone reporting success using this method?
I'd like to use this on a friends phone today but am a bit hesitant because it's so new.
thanks!
i will confirm that all the scripts work on thier own. i have no idea if hauss's batch scripts work. all the exploits are legit though. i will download and proofread. either way, it should work. i know hauss is experianced at rooting and stuff.
wait, huge file. does someone mind sending me everything except the pc36img.zip and eng-pc36img.zip? email is [email protected]
does anyone know if it will work on parallels on mac.
adb connection will be reset. restart adb server on desktop and re-login
I keep getting error message saying "adb connection will be reset. restart adb server on desktop and re-login"
--------------------------------------------
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3316, 3316}
[*] Searching for adb ...
[+] Found adb as PID 1400
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
rukshmani said:
I keep getting error message saying "adb connection will be reset. restart adb server on desktop and re-login"
--------------------------------------------
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3316, 3316}
[*] Searching for adb ...
[+] Found adb as PID 1400
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Click to expand...
Click to collapse
Actually i kept getting this same message when i was on the adb server and was attempting to get to the recovery screeen on the phone. Do you by any chance have HBoot 2.2 on your evo?
Hi Noobe , yes unfortunately..am i SOL
rukshmani said:
i keep getting error message saying "adb connection will be reset. Restart adb server on desktop and re-login"
--------------------------------------------
[*] cve-2010-easy android local root exploit (c) 2010 by 743c
[*] checking nproc limit ...
[+] rlimit_nproc={3316, 3316}
[*] searching for adb ...
[+] found adb as pid 1400
[*] spawning children. Dont type anything and wait for reset!
[*]
[*] if you like what we are doing you can send us paypal money to
[*] [email protected] so we can compensate time, effort and hw costs.
[*] if you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 usd!
[*]
[*] adb connection will be reset. Restart adb server on desktop and re-login.
Click to expand...
Click to collapse
this is not an error message! This means it is working! Just move on to the next step. If there is nothing that says the word error, there is probably no error!

Huawei Ideos Super FAQ

This is an FAQ for the Huawei Ideos as there have been many questions on how to do the same things. Hopefully this should help. There are other FAQs but this one tries to compile as many as it can into one FAQ.
Feel free to reply to this if there are any questions or if you want me to make any additions. The FAQ won't be complete to begin with but I will add as I get time.
One thing I will say is that I WON'T TAKE RESPONSIBITY IF YOU DAMAGE YOUR PHONE. I AM PROVIDING THE INFORMATION AND WILL TRY TO HELP YOU IF SOMETHING BAD HAPPENS BUT I CAN'T TAKE ANY RESPONSIBILITY
1. How to root the IDEOS
This can be done quite simply by adapting what quail wrote:
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from here (WORKS)
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me. (HAVEN'T CHECKED)
c) My preferred method: (HAVEN'T CHECKED)
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy​
2. How to flash the Ultrakiller Recovery Image
Now this has been covered many times but there have been a lot of problems with the BSOD on the IDEOS. A few days ago Ultrakiller came up with a solution that works regardless of the LCD type. Now this was distributed as an IMG file so many people were confused so here is a link to one with everything you need included. All I did was remove the amon'ra image and copied the Ultrakiller recovery IMG to the folder and edited the scripts to point to the new file.
After you download the file:
* Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys (Yes, bootloader is just the IDEOS logo) WHILE YOUR DEVICE IS PLUGGED IN
* WINDOWS - double click 'install-recovery-windows.bat'
* MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
* LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'​
See Q3 if you have Windows and the prompt hangs on "Waiting for Device"
3. How to solve problems with drivers on Windows in bootloader mode?
1. Unplug your phone
2. Download and install PDANet from here - at the end of the setup it will tell you to plug in your phone - do that
3. Put the phone into bootloader (See Q2 above)
4. Go to device manager and right click on "Android 1.0" and click "Update drivers"
5. Click "No, not this time" and Next
6. When it asks you where to look for drivers point it to PDANet's install location
7. Hopefully it should find the driver and prompt you to install it - it will take some time
8. You can now access your device in bootloader!​
Thanks to the following people:
Quail for the base of the guide and the ROM I'm using - it's amazing BTW
Ultrakiller for the recovery image
Changelog:
21/01/2010: Initial writeup
22/01/2010: Added Q3 and made some minor changes​
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Hi - the Ultrakiller recovery IMG in the ZIP from the Link above is "Ultrakiller.img.img". Dunno if it didnt work cause of this - sry didnt test, just downloaded new Ultrakillers "UltraJack-Recovery_v4.6.2.img", saved into that folder and changed the .bat to "fastboot-windows.exe flash recovery UltraJack-Recovery_v4.6.2.img" and it worked for me Even superuser.apk didnt work for usb-root but z4root does it perfect and DroidExplorer showing files now .
Thanks so far to all investing their time here
P.S.: the HUAWEI background of Ultrakillers recovery is very delicious
General guide to Flash ROM
Can you please provide a detailed guide for flashing Huawei Ideos. Because it is super guide. So it must contain this topic also.
I want to flash official ROM on following link:
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
Waiting for your response
yrnehukuht said:
i unfortunately deleted a system app and upon restarting my phone it wont boot.....it keeps hanging at the startup and reboots.. help me how to system restore...
Click to expand...
Click to collapse
Dear have u find out the solution of this problem?? COZ im also suffering from this if u find it then plz tell me [email protected]
I have downloaded a rom from xda-developers wiki from this link
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS
then updated my device software by going in to update mode(press vol up + end key + power button) .
This step returned me my original recovery.
But I am not going to recommend it bcoz i am facing problems like my cd drive which is automatically displayed has become inaccessible.
I am having problem to copy files to sd card.
My upgrade mode is not working now.
all these things were working immediately after the above mentioned process but I am now stuck with these things.
I think it is because i have flashed lower version number of rom on phone.
If you want to recover recovery mode only then I have successfully flashed UltraJack-Recovery 5.2.1 from this link
http://forum.xda-developers.com/showthread.php?t=860189&page=24
Inform about your progress
Thanx. Very useful
Hi guys. I am in a lot of trouble with my ideos.
Tried installing a custom ROm using ROM manager and it failed, although the original ROM is still there and its booting up and working perfectly.
However, when i try to boot into recovery, only the lit blackscreen shows.
I have tried everything from running ULTRAjack recovery on windows(which only shows 'waiting for device' on cmd, with the pdanet drivers installed) to ubuntu(which shows 'waiting for device' on Amon-ra recovery and permission denied on ULTRAjack).
Could it be i didnt root the device properly since i used z4 root?
Any more ideas?
900/2100 or 850/1700/1900/2100
Hello, How do I tell which sub-model my U8150 is please? Either HSDPA 900 / 2100 / AWS or HSDPA 850 / 1900 / 2100 / 1700. baseband = 22201003; build no.= U8150V100R001C183B825; IMEC = 355093040562676; IMEC-SV = 39.
Check out your fcc id suffix. I have heard there is a b version and a d version.
hi do flashing many roms affects my ideos mobile?
netskink said:
Check out your fcc id suffix. I have heard there is a b version and a d version.
Click to expand...
Click to collapse
All I got is a U8510-1, no letter... any thoughts?
Unlock u8150
Hello.
i have a T-Mobile Ideos u8150, also known as Comet.
it is locked to T-Mobile and requests a pin code when using another sim card.
is there a way to unlock the phone?
please help me...
thank you.
Enable USB Debugging & One Click Root with Unlock Root Tool

[GUIDE] Telus Desire HD - Rooting and Flashing

DISCLAIMER: This guide and package are provided as-is. I do not accept any responsibility for damage caused by following the guide or using the programs. This process was used by myself for rooting, unlocking and installing ROMs on my own Telus Desire HD. Please read through the entire guide ahead of time and make sure you understand where all the files in the package are.
Introduction
I noticed there was a good deal of confusion about the forums as to what to do with the Telus Desire HD and whether it was closer to the European DHD or the Inspire 4G. Turns out its closer to the Inspire 4G. jkoljo helped figure out what needed to be done to successfully flash this phone, so don't forget to thank him!
By the way, don't order a SIM unlock code if you need to unlock the phone so you can use it on another network. This procedure allows you to SIM unlock you phone without an unlock code. (Refer to step 22 in Section B.d).
Feel free to let me know if theres anything wrong or missing or if you have any questions.
Enjoy rooting and ROMing!
-AlexDP
-------------------------
Note: All the files needed for this process are included in this package. The folders for each section are located under folders with corresponding names (i.e. the files for Preparation are in the "Preparation" folder).
Download the package here:
-Full version, includes the PD98IMG.zip stock downgrade ROM file.
-Lighter version with no PD98IMG.zip file. You can get the necessary PD98IMG.zip file from here and use it when needed as per the guide.
A. Preparation Notes:
-Install HTC Sync (from the "Step 1 - HTC Sync" folder")
-Set your phone to allow usb debugging by going to Settings->Applications->Development and checking off USB debugging.
-Make sure you have the same SIM card if you've logged into Android Market before.
-Leave your Desire HD plugged in to your PC. Choose Charging only when prompted (unless you need to copy files to your SD, in which case switch to Mount drive).
-At the end of the process, once your all done rooting, save a copy of the following files from your SD card just in case:
hboot_check.nb0
hboot_eng.nb0
part7backup-SomeNumbersHere.img
hboot_original.bin
-Create a Gold Card:
Install GoldCard Helper from the Android Market,
Run it and make note of the value listed after Card:mmc2, Reverse CID. It should be a long series of numbers and letters. (make sure to use mmc2, the default copy to clipboard copies mmc1 ..)
Visit this page (http://psas.revskills.de/?q=goldcard), enter the new copied number and create your goldcard image, which will be e-mailed to you.
Save the file attached in the email to your PC.
Install HxD Hex Editor on your computer, from the "Step 4 - Gold Card" folder.
Run HxD Hex Editor. ("Run as Administrator" under Vista and Windows 7).
Go to the Extra menu and select Open Disk. Under physical disk, select Removable Disk (your microSD card), uncheck Open as Read only and click OK. Note that you should select physical disk NOT the logical disk. This is important!
Go to the Extra menu again and select Open Disk Image. Open the goldcard image that you received by email.
Press OK when prompted for Sector Size (selecting 512 (Hard disks/Floppy disks)) and click OK.
You should now have two tabs - one is your removable disk, the other is your goldcard image.
Click on the goldcard image tab. Go to the Edit menu, choose Select All then select the Edit menu again and select Copy.
Click on the Removable Disk tab. Highlight offset (line) 00000000 to offset (line) 00000170 (including the 00000170 line), then click on the Edit menu and select Paste Write.
Click on the File menu and select Save, accepting the warning.
Your Gold Card SD card is completed.
----
B. Rooting (Do this if you just want to root, or if you want to install a custom rom, do this first):
B.a Downgrade Process
1- Copy the PD98IMG.zip file from the "Step 1 - PD98IMG" folder and put it on the root of your SD card (i.e. not in any folders). Do NOT rename this file.
2- Go to the "Common files" folder and double click Start Here.
3- Copy the files in "Step 3 - Downgrade" to the "Common files" folder.
4- In the new command window that opens, type the following commands (you shouldn't get any errors. hit enter after each):
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
Code:
/data/local/tmp/misc_version -s 1.31.405.3
exit
Note: If you get an error while running the step before exit, try using 1.31.405.6 instead of .3.
5- Type adb reboot bootloader and hit enter. Your phone will be switched into the white bootloader screen. Wait for the bootloader screen.
6- Hit the power button to select bootloader from the options. It'll automatically find the PD98IMG.zip and start examining it. You'll see a blue progress bar at the top right. Once it finishes it'll ask you to hit volume up if you want to install. Do so. Don't worry if some items are marked "Bypassed" during install.
7- Once its done, it'll ask you to hit the power button to restart. Android should boot up.
8- Set the usb debugging option again. (Refer to Preparation step 2).
B.b Temp Root
Note: As an alternative to this section, you can download and install Visionary on your phone and have it do the temproot, by tapping the Temproot Now option. If you do this, jump straight to section B.d once you're done. If you have trouble doing this, or Visionary shows "rooting" then gets stuck or get a black screen, reboot your phone and follow this section fo the guide.
9- Make sure your SIM card is in when signing in to the Android Market for the next steps, otherwise it'll give you an error saying it can't access the Google server (!?! wtf, btw...)
10- Copy the files from the "Step 10 - Temp Root" folder to the "Common files" folder.
11- Go to the "Common files" folder and double click Start Here.
12- In the new command window that opens, type the following commands (you shouldn't get any errors. hit enter after each):
Code:
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push rage /data/local/tmp/rage
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/*
13- On the HTC Desire HD, install the Android Terminal Emulator (by Jack Palevich) app from the Android Market.
14- Launch the Terminal Emulator, and run the following command: /data/local/tmp/rage
15- After a minute or so, you will see the following message on the phone Forked #### childs. Press the Menu button & select Reset Term. The Terminal Emulator will exit out.(If you don't see this after a few minutes, something is wrong. Retrace your steps).
16- Launch Terminal Emulator. It will force close. Launch it a second time, and you'll have a root shell (i.e. you'll see a # sign instead of the $ sign in the console).
B.c Permanent Root
Note: It turns out this section (B.c) is actually unnecessary as its taken care of later in the process already. You can safely skip this section and go straight to section B.d.
17- Copy the files from the "Step 17 - Permanent Root" folder to the "Common files" folder.
18- Go to the "Common files" folder and double click Start Here.
19- In the new command window that opens, type the following commands (you shouldn't get any errors. hit enter after each):
Code:
adb push gfree /data/local
adb shell chmod 777 /data/local/gfree
20- Launch the Terminal Emulator on your phone and run the following commands:
Code:
/data/local/gfree -f
sync
/data/local/tmp/root
NOTE: You may see an error that states mkdir: /system/xbin already exists, if you do, simply ignore and continue on.
Code:
sync
21- Wait for this to finish. Once done, restart the HTC Desire HD.
B.d Unlock phone for flashing ROMs and carrier unlocking
Note: The order of these steps has been changed, but the folder names haven't been updated. Please pay good attention to the instructions here.
22- Run Easy Radio Tool (in the "Step 23 - Easy Radio Tool" folder), select the first option (especially if you want to SIM unlock, if not the Radio S-OFF option is sufficient). Follow the directions in the program. Make sure to accept the SuperUser request on the phone when it pops up (keep your phone unlocked so you see it). It may fail at one point and your phone will restart. If it does, thats ok just run it again and it'll finish successfully this time.
23- Run EasyS-OFF (in the "Step 24 - EasyS-OFF" folder) and follow the instructions.
B.e Flash ClockworksMod Recovery
24- Download and run ROM Manager from the Android Market and have it install ClockworksMod Recovery.
24.I If you're not flashing a Gingerbread-based ROM (like CM7), please choose the last option in the list "All ClockworkMod Recoveries" then choose 2.5.1.3.
24.II If your installing a CyanogenMod or any other Gingerbread-based ROM you must have ClockworkMod Recovery 3.0 and above, so just choose the first option in the list, "Flash ClockworkMod Recovery".
If this fails with a message about permissions, it means you haven't rooted correctly, retrace your steps.
----
C. Flashing a new ROM:
1- Download the ROM of your choice (I recommend Android Revolution HD, available here: http://forum.xda-developers.com/showthread.php?t=840040, but feel free to chose any). Copy the zip for the ROM to your SD card. Inside ROM Manager, click Install ROM from SD Card and select the ROM that you put on your SD card. Select wipe data and cache and optionally the backup checkbox. Let it finish installing and rebooting your device.
Note: If you are flashing to a ROM other than a stock Telus ROM (Raidroid Stockify is a stock Telus ROM), you will have to enter your APN settings manually. If you're using your phone on a different network than Telus, you will have to enter your APN settings.
Note:If you want CyanogenMod, it's available inside ROM Manager and you dont need to do this part and you can skip to the very last step. If you want to install CyanogenMod 7 or any Gingerbread-based ROM, you must first update your ClockworkMod Recovery to 3.0 and above. Please note that you can't restore from a backup or install a non-Gingerbread ROM from ClockworkMod Recovery 3.0 and above. If you need to restore from backup or downgrade, install ClockworkMod Recovery 2.5.1.3 (ROM Manager -> All ClockworkMod Recoveries -> 2.5.1.3) then proceed to flash or restore as needed.
2- Copy Telus Kernel.zip to your SD card from the "Step 2 - Telus Kernel" folder.
3- Run Kernel Update Utility (in the "Step 3 - Kernel Update Utility" folder) and click "Select a cwm zip", then click next, then click Go to fastboot, wait for the white bootloader screen on your phone, then click Flash. Once it's done, it'll reboot back into Android.
4- Once that's done click next, wait for the USB connection and USB debugging mode notification.
5- Click flash button in Kernel Update Utility and once that's done click finish.
Your done! Sound works perfectly and so does Wi-Fi!
--------------------------
Guide Credits:
This guide and package was pieced together from various other guides and packages after exploring the various posts and methods on the topic, mostly from Xda-Developers. I've listed them here:
Gold Card Guide: http://www.droid-den.com/android-guides/android-guide-how-to-create-a-gold-card
CyanogenMod Downgrade and Rooting guide: http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide#Downgrade_to_1.32.405.6
How to downgrade: http://forum.xda-developers.com/showthread.php?t=905003
One click Radio S-OFF tool: http://forum.xda-developers.com/showthread.php?t=857537
One click ENG S-OFF: http://forum.xda-developers.com/showthread.php?t=855403
Desire HD, no sound thread (thanks jkoljo): http://forum.xda-developers.com/showthread.php?t=949909&page=10
Thanks to everyone who wrote those guides and these programs and made it possible for us to flash the Telus Desire HD, specifically jkoljo, who put his own time into it.
Instead of gfree and rage, you can just use Visionary and Radio S-OFF Tool, saves a lot of time
Sent from my Desire HD using Tapatalk
True. I was personally having some trouble with Visionary though... after hitting temproot now or temproot on boot it'd show the rooting screen, then hang there and turn black. The whole phone would get slow too.
I'll probably add that as alternative steps tomorrow morning when I wake though. Thanks for the feedback!
Sent from my Desire HD using XDA App
Alex, thanks so much. I don't yet have the device, but was looking for a fool-proof rooting/sound-maintaining guide before purchasing. I knew it would come in good time
I also had tons of trouble using Visionary to temp/perm root my Desire Z. I would definitely shy away from that method, especially if you're comfortable with ADB. Your method, while it may take longer, works great.
Does this also provide a SIM Unlock like it does the G2?
Does flashing the Telus Kernel from the Kernel Update Utility yield a different result than flashing it from Clockwork?
Thanks Guys. Guide worked Perfect!
You should remove the gfree part of your guide, Easy Radio Tool does exactly the same, but in one click. In the current form, you are Radio S-OFFing two times.
Gfree does not give you permanent root.
jkoljo said:
You should remove the gfree part of your guide, Easy Radio Tool does exactly the same, but in one click. In the current form, you are Radio S-OFFing two times.
Gfree does not give you permanent root.
Click to expand...
Click to collapse
So you mean the entire part B.c, right? Thanks again for your feedback!
Yes, entire B.c section, and flashing ClockworkMod should be the last step of all.
jkoljo said:
Yes, entire B.c section, and flashing ClockworkMod should be the last step of all.
Click to expand...
Click to collapse
Thanks, updated as such.
I'm getting this error:
mmap<> failed. Operation not permitted
On section B a -4 on the command
adb shell /data/local/tmp/psneuter adb shell
Anyone know what's causing it?
Hey guys, has anyone been successful in getting sound on the cm7 nightly ROM?
omegacell said:
I'm getting this error:
mmap<> failed. Operation not permitted
On section B a -4 on the command
adb shell /data/local/tmp/psneuter adb shell
Anyone know what's causing it?
Click to expand...
Click to collapse
I'm sorry, there was a mistake. It should be:
adb shell /data/local/tmp/psneuter
<hit enter>
adb shell
<hit enter>
Instead of:
adb shell /data/local/tmp/psneuter adb shell
I've updated the guide to reflect that.
sound and other stuff
plasticdarlow said:
Hey guys, has anyone been successful in getting sound on the cm7 nightly ROM?
Click to expand...
Click to collapse
Nope I cant get any sound and if youflash the telus zip I just get stuck at htc logo, funny thing is I can get sound through fm radio only, i get sound oon fm radio through headset and through speaker but not on anything else.
I'm getting stuck during root process....any ideas???
C:\Documents and Settings\waycoy\Desktop\Telus Desire HD\Common files>adb push psneuter /data/local/tmp
2490 KB/s (0 bytes in 557962.000s)
C:\Documents and Settings\waycoy\Desktop\Telus Desire HD\Common files>adb push misc_version /data/local/tmp
15 KB/s (0 bytes in 15837.001s)
C:\Documents and Settings\waycoy\Desktop\Telus Desire HD\Common files>adb shell chmod 777 /data/local/tmp/psneuter
C:\Documents and Settings\waycoy\Desktop\Telus Desire HD\Common files>adb shell chmod 777 /data/local/tmp/misc_version
C:\Documents and Settings\waycoy\Desktop\Telus Desire HD\Common files>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
C:\Documents and Settings\waycoy\Desktop\Telus Desire HD\Common files>
I loaded cm 6 and got no sound at all either. Which roms are people having good luck with?
Sent from my Nexus One using XDA App
Step Ba6 when applying PD98IMG.zip I recieve a "Model ID incorrect!" and "Update Fail!". Any suggestions? There were no errors up to that point. My scree is currently sitting at Press POWER to reboot. Not wanting to brick - am I ok to POWER. Model on the packing box shows A9192 if that means anything.
dr_pepper said:
Step Ba6 when applying PD98IMG.zip I recieve a "Model ID incorrect!" and "Update Fail!". Any suggestions? There were no errors up to that point. My scree is currently sitting at Press POWER to reboot. Not wanting to brick - am I ok to POWER. Model on the packing box shows A9192 if that means anything.
Click to expand...
Click to collapse
you can reboot my phone had the same problem i was unable to downgrade i was stuck at that point for a while. i dont know if there is a fix for this yet.
Bummer. Thanks for the reply
gold card
Did you guys use a gold card. Did you follow everything from the start down. I did it last night and had no problems. The only problem you will have if you get it done is with roms. At this point it is probably best just to get root and wait for some roms that use the right kernel, some roms sound tinny, some just don't work. CM7 doesn't work with sound at all and if you apply the TELUS kernel it locks up at HTC boot screen.

[REF] Axioo Picopad QGN (Root, Busybox, CWR, etc)

Axioo PICOPAD QGN
Android OS, v2.2 Frozen Yogurt
Qualcomm MSM7227 (App: ARM11 600MHz)
This wont work on PICOPAD 9
This is a very unpopular device from Indonesia. Although it is very easy to Root using "Superoneclick". As more people got hold of this free set(via Singapore old Starhub Internet plans), more people are also starting to ask about the steps on rooting this device. I thought I should start a guide here where I've followed from different places, piece them together here.
Feel free to comment and share if there are other ways to root, flash and install custom roms or android version. More importantly over clocked kernels. (remember seeing a link at kwbr's thread)
There are similar sets "CSL Spice Mi700 DroidPad", "Viewpad 7", etc
Alternatively you could research more by heading on to Viewpad 7's thread as I found out that device is very much similar and more developers are active there. I've also tried flashing kwbr's rom and it works for me.
Well if you are going to follow this thread to root, then read on...
WARNING! You warranty is now VOID & I will not be responsible if you brick your device.
Click to expand...
Click to collapse
Sections:
1. Rooting your device (wiki)
2. Installing Clockwork recovery (wiki)
3. Setting up ADB (optional)
4. Setting up partition on SDcard to free up device main space (WIP)
1. ROOT & Busybox (comes in a package)
Use these steps to root with "SuperOneClick". (Thanks to SuperOneClick)
Download and install "SuperOneClick"
Alternatively, download older version (some say works better) 1.6.5 1.7.0
Make sure you have .NET Framework v2.0 for Windows XP(win update)
On picopad, Unmount your SD card. From settings -> sd card -> unmount
Enable USB debugging, Setting -> Applications -> Development -> tick USB Debugging
Connect picopad to Pc via usb, ignore pctools if popup.
Goto Windows Explorer, Picopad will appear as "CD-ROM", explore CD-ROM and run SETUP.exe, ignore pctools
Open "SuperOneClick"
Change the option from "psneute" to "rageagainstthecage"
Click Root.
Rooted , Superuser & Busybox installed
Mount back your SDcard if u wish and reboot your device at least twice.
Congrats! Your device is rooted!
If you are satisfy with only root and superuser access, then you can stop here.
If you would like to install(flash) Clockworkmod recovery so you can backup your device(nandroid) and flash rom/kernel/stuff easier, proceed to step 2. (Highly Recommended)
If you want to set up ADB proceed to step 3 (optional, may come in handy and good for other android devices.)
2. ClockworkMod Recovery 5.0.2.6
2a. Preparing to installing CWR
Download CWR 5.0.2.6 and Flash_Image
Unzip, then copy "flash_image" and "cwm5026.img" to the root of your sdcard. (if you don't know how.. take your SDcard out and use a card reader)
Power on the device and install a terminal app so you could type commands in, try Android Terminal or Terminal Emulator
Once installed, open the app and start typing:
Gain superuser access type
su (once in superuser, you will see "#")
Click to expand...
Click to collapse
copy flash_image to system/bin
cp /sdcard/flash_image /system/bin
Click to expand...
Click to collapse
Install the flash_image
chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
Backup your original Recovery
cat /dev/mtd/mtd3 > /sdcard/orirecovery.img
Click to expand...
Click to collapse
And if you ever want to restore back for warranty issues
flash_image recovery /sdcard/orirecovery.img
Click to expand...
Click to collapse
2b installing ClockworkMod Recovery 5.0.2.6
The previous ver 2XXX is pretty outdated, thanks to mb-14 for sharing 5026.
Now you are ready to flash ClockworkMod Recovery
Assuming the file name that you download from CWR is "cwm5026.img" Type
flash_image recovery /sdcard/cwm5026.img
Click to expand...
Click to collapse
Done!
Now to run Clockwork Recovery:
First, turn off your device.
Now, hold down both volume button and press the power button at the same time, when you see recover on the corner of the screen, you can let go as you will boot up in Clockworkmod Recovery.
How to use 5.0.2.6 CWR?
Use the device vol+ and [/b]vol- to move up and down or the soft keys menu for "down", home for "up"
Select options by pressing the power button or , use the soft keys search for "enter"
back is for "back".
When you load into CWR, you could do many stuff, some simple info on the main options,
Wiping data is resetting your device to factory default, but CWR remains as long as you do not flash a stock recovery or a rom with a different recovery inside.
You could do stuff like formatting and partitioning SDcard to prepare for Apps to be install in SDcard to save space in device. Other than that, you could do a Backup for your entire device which is also known as nandroid backup, but it doesn't backup the bootloader and radio, so take note if you are going to flash custom radio or bootloader.
If you have a backup, you could restore back to that backup, this is good if you accidentally flash something bad or dislike a rom
Fixing permission is good if you always have FC.
You can mount SDcard to your pc from here and manage files with from your PC.
You could use ADB to push / pull files in and out of your device from PC.
you could install other roms, kernel and files using the "install zip" option.
If you want to set up ADB proceed to step 3 (optional, may come in handy and good for other android devices.)
3. Installing ADB on your windows
Download and install Latest JAVA SE Development kit "JDK" and Android SDK.
Follow the steps here on installing ADB, Android Debug Bridge.
3a. SET PATH for ADB: Check if you had set the path to sdk platform tools folder, this is to run adb command from any path. Steps for Windows XP:
Right-click ‘My Computer’ and click ‘Properties’.
In the ‘System Properties’ window, click the ‘Environment Variables’ button on the ‘Advanced’ tab.
Find ‘Path’ in the ‘System variables’ section and double-click it to edit it.
Make sure NOT to delete the existing entry in ‘Variable value’.
Just add the following string to the end of it, including the semi-colons:
;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools;C:\Program Files\Android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
Start ADB shell to command picopad from your pc:
Make sure Picopad is connected to pc via USB and sdcard is mounted.
From PC, Goto command prompt (Start -> Run type "CMD")
Type "ADB devices" from command prompt ( to see if path is set and picopad is connected, you should see 1 device attached, not more, not less)
C:\Documents and Settings\tish>adb devices
List of devices attached
FM88888888888 device
Click to expand...
Click to collapse
Troubleshooting:
If you can't get the adb command to work, probably you didn't set the path correctly, refer back to SET PATH or go to your adb actual folder to type the command which should be here C:\android-sdk-windows\platform-tools\
3b. Using ADB
At recovery or booted up device, on Pc Type:
adb shell (you will see "$")
Click to expand...
Click to collapse
now access superuser type
su (allow superuser access from Picopad and you will see "#")
Click to expand...
Click to collapse
Here you can copy files using (push/pull), I recommend you google for ADB commands to have a better understanding.
4. More sections to come eg: The space problem on the device, so alternative is partitioning sdcard to install apps as to free up space in device........
You could buy me a beer if you really appreciate my work here.
Updates from Fri the 21th April 2012
Reorganizing error section
Adding missed out steps here and there
Placing direct link for faster downloads
Added 2 older ver. SuperOneclick which works better
Removed CWR 2.5.1.2 details since it's outdated.
Added some details on 5.0.2.6 CWR
Updates from Fri the 13th Jan 2012
Added CWM 5.0.2.6 and soft keys steps.
Added possibility to explore Viewpad 7's dev forum.
Included some wiki info on root and CWR(Clockworkmod Recover)
Added troubleshoot for Set path to android sdk adb folder.
Included ADB set and using step
I first rooted my Picopad using guides from hucqim80, however they are not meant for Picopad and I've gather the info and posted them here.
Original recovery image provided by jax79sg here
This is to recover original recovery and replace clockworkmod recover.
This step is done because you need to send your set for warranty repair probably.
Remember to do a factory reset first before replace with original recover.
tishfire said:
Wonder if anyone had backup their Picopad's original recovery? "orirecovery.img" Accidentally erased mine thinking I had already backup in my pc.
Hope you could put up for me to download thanks .
Click to expand...
Click to collapse
I will upload mine somewhere after i try your steps above.
sure, thanks
axioo picopad.
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
did u go to cd-rom folder and execute setup.exe before u click superoneclick?
No , I did not run the setup.exe from the cdrom drive cos when i plugin the device it automatically ask me to do the PC syncing. Actually i tried that before but that din work either.
I ran both PC running win7 and winXP, both also stuck at Running psneuter ...
Hi,
I ran into this error which puzzles me greatly.
# flash_image recovery /sdcard/cwrecovery.img
flash_image recovery /sdcard/cwrecovery.img
flash_image: permission denied
Do you know how to resolve this?
Thanks in advance.
Warmest Regards
eagleen said:
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
Click to expand...
Click to collapse
same with me....anybody can give another tips ?
try to turn on picopad usb first. then try to ru he setup in picopad identified as " cd-rom" try again
Sent via Picopad
is there any custom ROM compatible for this device ?
help
Please help me when i type cp /sdcard/flash_image /system/bin and press enter i got something like this : cp /sdcard/flash_image /system/bin: not found
I'm a wrong.?
can this Stock ROM modified for support with App2sd by Trkton ?
Vuska said:
can this Stock ROM modified for support with App2sd by Trkton ?
Click to expand...
Click to collapse
It supports without any modification in the first place.
Roms, probably the MI700's custom rom will work, get to hucqim80's signature, the link is there.
nhasir said:
Please help me when i type cp /sdcard/flash_image /system/bin and press enter i got something like this : cp /sdcard/flash_image /system/bin: not found
I'm a wrong.?
Click to expand...
Click to collapse
probably ur file is not in that directory for this error message to appear.
eagleen said:
Hi tishfire , thanks for the guide, i got the same device as yours but when it always stuck at the below lines , can anyone help ? thanks in advance.
[/I]Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
677 KB/s (585731 bytes in 0.843s)
OK
chmod psneuter...
OK
Running psneuter...[/I]
Click to expand...
Click to collapse
Okay, i know your problem... just change the option in superoneclick from psneuter to rageagainstthecage... and then root it...
when the superoneclick start to not responding, just re root it using the same method....
then to enable your superuser, install z4root to your device
I managed to root the picopad and flashed as stated.
When i boot up pressing both power and vol button, i was brought into this FTM mode. And from there i can't do anything...... the screen looks as follows.
Hmm....the cwrecovery didn't get flashed?
SWVer=3.240
MODEL: FM6-0001
HWVer:106
Power on with pressing VOLUME_DOWN keys to leave Auto FTM.
[Resolved]
Try holding both up and down volume buttons instead of just one of them
tishfire said:
Wonder if anyone had backup their Picopad's original recovery? "orirecovery.img" Accidentally erased mine thinking I had already backup in my pc.
Hope you could put up for me to download thanks .
Click to expand...
Click to collapse
This is many months late, here's the stuff if anyone needs it.
http://www.megaupload.com/?d=PKMW1ODU
jax79sg said:
This is many months late, here's the stuff if anyone needs it.
http://www.megaupload.com/?d=PKMW1ODU
Click to expand...
Click to collapse
Im still using my picopad.
Thanks!
Sent from my Nexus S using XDA App
can anyone help me with original backup for the splash and welcome screen axioo pico pad?
my pico pad splash and welcome screen change to viewsonic because i install viewpad 7 ROM in to my pico pad.....
somebody....help me please !!!
thankyou

Categories

Resources