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
New to the forums here so I'm hoping this is the 'general' thread where everyone keeps telling everyone to post their rooting problems/questions.
I have an HTC inspire that I'm trying to root, and after I unzipped the hack kit to C: (for simplicity) I get to the first step in attn1's hack kit (after making the goldcard) which is to check for temp root. So I go type in the command and it gives me this:
C:\Documents and Settings\Saulk>C:\hackerize-ace setup-downgrade
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Starting add shell to test temp root, please be patient...
if you see a '#' prompt, okay to proceed
if you get a '$' prompt, temproot failed
type exit at the prompt to continue
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
C:\Documents and Settings\Saulk>_
I'm not sure how to proceed at this point.
Oh, I'm using XP home SP3 with .Net frameworks 1-4
I also have a couple questions about those whole process:
1. Do I need to have my goldcard in my phone at all times AFTER the rooting is finished? Or is it just for the rooting process?
2. I've been looking at roms to flash and there are sometimes other things to flash on with it. Do I just put the files on the SD card and flash them (in the appropriate order, of course) or is there a specific procedure for different types of say like kernels and roms and boot images?
I think that's it for now. I'm sure I might have other questions down the line so stay tuned!
Thanks in advance and I await your replies!
Sent from my mind using my amazing mind powers
Anyone?
Sent from my mind using my amazing mind powers
Hey everybody,
When I follow the guide by LIV2 i get stuck at the part when you install the programs like gdm3 and gnome, while your chrooted into the install. Get this error back at me. Here's the copy of the command line
Package initramfs-tools is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Unable to locate package xserver-xorg-video-fbdev
Unable to locate package xserver-xorg-input-evdev
Unable to locate package gdm3
Unable to locate package gnome
Package 'initramfs-tools' has no installation candidate
Unable to locate package wpa-supplicant
Is there a way for me to fix this?
Thanks
@rayman84
Yes, this is in the wrong forum. But im a 'noob' and I cannot post/reply in the dev sections just yet. Please move this thread to the relevant section.
Or better yet, add it as a reply to this thread: http://forum.xda-developers.com/showthread.php?t=1290503&page=1
First, some history:
The SBKDetect binary can be used in a 32bit Linux environment to grab some useful information for our brainy dev's.
In this instance, the dev team are asking for people who own Asus TF101/TF101G with serials beginning with B70 or B80 to run this binary while their tablet is in APX mode and copy/paste the results in the thread.
To run the binary in a 64bit enviro all you need to do is install ia32-libs
User 'thorntree' was experiencing problems running this binary in his 64bit Ubuntu enviro and was receiving the error
Code:
./sbkcheck: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory
My TF101G has a serial beginning with B90. I dont think there are any other users with a B90 that have run sbkcheck, so im very keen to run it. As im sure the devs are keen to get the results from this B90 TF101G.
---
Now the juicy bit:
(Disclaimer: I am by no meaNow the juicy bit:ns a Linux expert, so the process I went through below may be incorrect, but I seem to have made *some* headway, hopefully someone else can clean up and finish it off)
I was also experiencing this error on my 64bit Ubuntu (BackTrack5, actually) enviro.
- lsusb confirmed that my device is in APX mode.
- Using Aptitude I reinstalled libusb-1.0 and ia32-libs, this isnt the issue
- A find revealed that libusb-1.0.so.0 can be found in /lib and /usr/lib
- a 'strings sbkcheck' shows:
Code:
/lib/ld-linux.so.2
libusb-1.0.so.0
- So I assume that the binary is looking for the lib in /usr/lib32 as it doesnt specify an absolute path, sure enough, the file doesnt exist in /usr/lib32
- 'ln -s libusb-1.0.so.0 /usr/lib32/libusb-1.0.so.0' gives me error:
Code:
./sbkcheck: error while loading shared libraries: libusb-1.0.so.0: wrong ELF class: ELFCLASS64
(We are on the right track!)
- ls of /usr/lib32 shows a similar file 'libusb-0.1.so.4', so I removed the previous link and did a 'ln -s libusb-0.1.so.4 libusb-1.0.so.0'
- Now the error we get is:
Code:
./sbkcheck: symbol lookup error: ./sbkcheck: undefined symbol: libusb_init
- A strings of sbkcheck and libusb-0.1.so.4 shows that sbkcheck uses 'libusb_init' and libusb-0.1.so.4 uses 'usb_init'
- Changing either file above causes a 'Segmentation fault'
This is where I am stuck... Like I said, im not Linux expert or coder, but im guessing sbkcheck needs to be modified and recompiled so that is uses 'usb_init' instead of 'libusb_init' and it should work.
Hope the above helps...
Can one of you wonderful moderators please move this thread to where it belongs? Thanks!
I think you should get the 32 bit package, extract its contents, and manually copy the libusb.ko (the correct one), to /usr/lib32. The package you are looking for should be this one: http://packages.ubuntu.com/lucid/libusb-1.0-0, just get the i386 version and copy/link over. Should work.
The ELF class error is because you are trying to load a 64 bit library into/from a 32 bit application, which won't work. The other error is because that's not the library it's looking for, and thus it doesn't find what it needs.
Hope that helps
Hi guys,
I am trying to build the lineage os for the Samsung galaxy s7 on a Linux mint O/S. Each time I try and build the ROM I get an error saying I don't have the right manifests for the herolte device. So I then have downloaded the official version from here and have extracted the system image as instructed in the lineage build instructions.
The next step is to move to the device folder in the repo, in my case ~/android/lineage/device/samsung/herolte/, and then import the blobs across using "./extract-files.sh -d ~/android/system_dump/" from the already mounted system.img.
Each time I do this I get a file not found error, "bash: ./extract-files.sh: No such file or directory" and I am unsure what mistake I am making. I have checked that ADB works from the folder, which it does.
Anyone able to point me in the right direction here?
Bump
@Fevax do you have any ideas? I've tried searching through all lineage FAQ and google but by all accounts I'm doing this right. Have even purged the android build folder and re repo'ed everything?
The file extract-files.sh is located in ~/android/lineage/device/samsung/hero-common.
So, the correct command should be: ".~/android/lineage/device/samsung/hero-common/extract-files.sh -d ~/android/system_dump/"
Happy coding!