Database Users

[Guide][ALL DEVICES]ROOT + flash custom recovery + fix perfected spl [27 JAN 2012]

I added a DONATE button... my HTC Magic device was stolen.. i need a new one for testing...
Once i have enough for it i will remove the donate button :0)
Root your sapphire/magic device the easy way.
This guide is confirmed to work with Rogers 2.1 update!
It will not work with the 2.2.1 update...
Instead, use this tool for root and continue from step 5..
WANT ROOT ONLY:
try to install "universal androot" from market and just do step 4.
--OR--
Only do the blue steps in this guide!
The recovery is optional!
The spl is a luxury and only needed if you have some specific use for it!
Remember spl = hboot ( the names are interchangeable)
READ EVERYTHING BEFORE YOU DO ANYTHING.
I'M NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE.
This guide is made for NOOBS with windows, but the steps can be made on any OS.
The RootTools-package have the tools + images needed for windows, linux and mac!
You don't even need the android sdk :0)
No need for goldcard!
Step 0) -Only do this step if your going to flash custom recovery + spl(optional)
Reboot your system into fastboot (hold power-button and back-button together)
Write down EVERYTHING YOU SEE ON YOUR SCREEN.
Reboot into your system again.
Step 1)
Download and extract the contents of RootTools to C:\roottools
Step 2)
start a command promt (cmd)
type:
cd c:\roottools\windows
Step 3)
Make sure that your device has usb debugging turned on by doing:
push "menu" -> Settings -> Applications -> Development -> make sure that "USB debugging" IS CHECKED.
now install the app that will root your system by typing:
adb install C:\roottools\App\UniversalAndroot_1.6.1.apk
Step 4)
Start the app from your device... it's called universal androot.
The app will automatically check your system version.
But, just to sure - verify it then push "root "
Wait for it to finish..
if it fails, then try again... if it still fails try to choose:
"Do not install Super user" and then push "root "
If all goes well then you have ROOT :0)
If it did not go well, then ask for help in this thread!
You can now do what ever you want...
But i recommend to continue with the recovery part.
The eng spl is optional, and you dont need it unless you have enough experience with fastboot and terminal commands! Roms are flashed using custom recovery...
Step 5) RECOVERY
Now we use the info you wrote down earlier...
---------------
If your radio starts with 3.22:
adb push C:\roottools\3.22Radio\recovery-RA-sapphire-v1.7.0H.img /sdcard
----OR---
If your radio starts with 2.22:
adb push C:\roottools\3.22Radio\recovery-RA-sapphire-v1.7.0G.img /sdcard
----OR---
If your radio starts with 6.35 type:
adb push C:\roottools\6.35Radio\Recovery-RA-hero-v1.6.2.img /sdcard
------------
Step 6) OPTIONAL
If you would like a eng(Engineer) spl/hboot then do this:
--------------
If your radio starts with 3.22 or less type:
adb push C:\roottools\3.22Radio\hboot_2010_signed.zip /sdcard
(If you have the 3.5mm jack use the above, but only if you have something important that needs eng spl.
Using this spl will cut your ram in half and make the 3.5mm jack useless!
You can always revert back to stock spl when your done doing the "important" stuff :0)
----OR---
If your radio starts with 6.35 type:
adb push C:\roottools\6.35Radio\hboot_2007_signed.zip /sdcard
Step 7)
Now we are going to flash custom recovery.
type:
adb shell
su
(Now look at your device. If the superuser app is asking for permissions, then just push "allow" and make sure that the "remember" option is checked.)
cd /system/bin
ls
(now make sure that you see a file called "flash_image". If you do not, then make step 9 and forget the rest of THIS step)
./flash_image recovery /sdcard/_________ (where the "_________" are replaced by the name of the recovery image you pushed in step 5)
( An example:
./flash_image recovery /sdcard/Recovery-RA-hero-v1.6.2.img
---OR---
./flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0H.img)
Remember, if you get no response, or the command it self is repeated, then you are good to go. In Linux (and thereby also Android) no errors means success!
Now you should have a custom recovery.. you can read in the forum what that can do for you...:0)
I recommend you to stop here, or you can continue if you made step 6.
If your recovery is not sticking(like it returns to stock on every boot) check out the second post!
Warning, step 8 can brick your device if done improperly!
Step 8)
Now we are going to flash eng spl/hboot using the custom recovery.
Turn of the device.
Start in recovery mode by holding the home-button together with power-button for min 5 sec.
(Hold the home-button first then the power-button :0)
The custom recovery should start. You navigate using the trackball.
Choose "flash zip from sdcard"
(If you get errors like those:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
Or
E:Can't mount SDCARD:
It's a small bug that shows up randomly.
It means that the custom recovery can't mount your sdcard...
To fix it try this:
Select "usb-ms toggle".... waiting 5 sec...then push menu-button.
Some times you need to repeat it 2-3 times before you again can get access to the sdcard!
Then choose "flash zip from sdcard" from the menu.)
Choose the zip file you pushed in step 6.(should start with hboot)
Follow the instructions on the device screen. JUST DO WHAT IT TELLS YOU TO DO!!!
The device should restart a couple of times...
It's normal if you see a different recovery screen for 10-15 sec... LET IT WORK!
By all means don't interrupt it unless it has taken more then 2 min!
(IF MORE THAN 2 MIN, THEN REMOVE BATTERY)
You are done when it's back in recovery and is doing nothing for 30 sec or so.
Choose "Power off".
Restart in fastboot and check that your info has changed from what you wrote down earlier...
DONE. You now have eng spl + custom recovery + ROOT... You can now do WHAT EVER YOU WANT TO DO.. you have complete control over your device :0)
THE END!
Check out some of the tools in my signature :0)
Step 9) ONLY IF YOU DID NOT FIND flash_image IN STEP 7
type:
exit
(you should now be back to windows command promt, if not keep typing exit until you are)
type:
adb push C:\roottools\App\flash_image /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 777 ./flash_image
./flash_image recovery /sdcard/_________ (where the "_________" is replaced by the name of the recovery image you pushed in step 5)
( An example:
./flash_image recovery /sdcard/Recovery-RA-hero-v1.6.2.img
---OR---
./flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0H.img)
Remember, if you get no response, or the command it self is repeated, then you are good to go. In Linux (and thereby also Android) no errors means success!
(Now go back and read the text after step 7 which has gray+red colour)
LINK TO ROOTTOOLS:
Rapidshare
Hotfile
Depositfiles
Fileserver

Recovery issue
About the recovery issue (This is only on SOME systems!):
In /system/recovery.img there is a full copy of everything that is loaded on the recovery partition. This file is automatically flashed onto the recovery partition every time you shut down. That means two things: 1. Any changes you make directly to the recovery partition gets blown away on reboot and 2. If you want to change the recovery partition you're probably better off just sticking the image in /system/recovery.img and rebooting.
So to fix this problem you have to rename the custom recovery file to:
recovery.img
then make sure it's on /system/recovery.img.
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mv /sdcard/recovery.img /system/recovery.img
This will make sure that you have the custom recovery on every boot.
OR
you could delete the file located on: /system/etc/install-recovery.sh which is responsible for flashing the stock image
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/etc/install-recovery.sh
Others who don't have this problem, please ignore the above :0)
NB: Some of the info is borrowed from.
Source: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

Well, everything worked untill i got to step 10.
I have a MyTouch 3G. v1.2 with headphone jack.
HBOOT- 1.33.001
Radio 2.22.23.02
I tried to execute
<verbatim>mv /sdcard/flash_image /system/bin/</verbatim>
then i got
<verbatim>failed on '/sdcard/flash_image' - Cross-device link</verbatim>
Any help?

You are great! I searched for a step by step description for days!!
I will try it tommorrow with my HTC Magic 32a and tell you if it worked.

Xenstier said:
Well, everything worked untill i got to step 10.
I have a MyTouch 3G. v1.2 with headphone jack.
HBOOT- 1.33.001
Radio 2.22.23.02
I tried to execute
<verbatim>mv /sdcard/flash_image /system/bin/</verbatim>
then i got
<verbatim>failed on '/sdcard/flash_image' - Cross-device link</verbatim>
Any help?
Click to expand...
Click to collapse
Try
cp /sdcard/flash_image /system/bin
Make sure that your are working inside the shell and not on the cmd promt.
And are you sure that the flash_image is not there?
On both mine tests, the flash_image file was present!!!!

IT SHOULD/WOULD WORK...
I took mine perfectly working and rooted device and flashed both RUU updates...
The lastest one with sense and the one before that...
Applied the same steps and it worked like a charm...
What i like about this methode is:
No need for goldcard
No need for download and setup of sdk
No multiple links to follow, only 1 download
Works for all os
The download have all the tools and images you would need :0)

Good job mumi

mumilover said:
Try
cp /sdcard/flash_image /system/bin
Make sure that your are working inside the shell and not on the cmd promt.
And are you sure that the flash_image is not there?
On both mine tests, the flash_image file was present!!!!
Click to expand...
Click to collapse
When i tried cp
# cp /sdcard/flash_image /system/bin/
cp /sdcard/flash_image /system/bin/
cp: not found

Xenstier said:
When i tried cp
# cp /sdcard/flash_image /system/bin/
cp /sdcard/flash_image /system/bin/
cp: not found
Click to expand...
Click to collapse
OK...
1) are you sure that you are inside the system and not inside the recovery?
2) inside the shell type:
cd /system/bin
ls
post here all what you get on your screen... write it down or take a picture or something....
3) you can install buzybox and try step 9 again.
buzybox will install all common executables/commands for you.. like cp(copy), mv(move) and which(looks up if a command like cp is found or not).

I made some changes to the guide:
1) some step nr ref that was wronge.. ups
2) updated the info regarding devices with 3.5mm jack
3) older radio is also taken care of :0)

will it work if i have a official htc rom, 1.91.xxx.xx (vodafone italy) with spl 1.33.0007 (perfect spl)?
no need of goldcard? i can follow this guide? thanks

Are the first four steps hazardous? No, so why don't you just try it and you tell us if it worked.

eyegor said:
Are the first four steps hazardous? No, so why don't you just try it and you tell us if it worked.
Click to expand...
Click to collapse
i'm noot a noob, i had 5 android devices till december 2008, all rooted and hacked.
now i have an issue on girlfriend's magic 32b, it seems that i cant have acces anymore to the recovery partition.
the only solution i've found is to flash a original htc rom wich has 1.33.0007. my magic has still the non perfect spl 1.33.0004.
so mine is only a question, if for you was a stupid question, i'm sorry

daniele8Dj said:
will it work if i have a official htc rom, 1.91.xxx.xx (vodafone italy) with spl 1.33.0007 (perfect spl)?
no need of goldcard? i can follow this guide? thanks
Click to expand...
Click to collapse
Try it... it should work..
The app uses a special exploit to give you root...
If you want root then only do the blue steps (1-4).
if you want more continue with the guide :0)

Xenstier said:
Well, everything worked untill i got to step 10.
I have a MyTouch 3G. v1.2 with headphone jack.
HBOOT- 1.33.001
Radio 2.22.23.02
I tried to execute
<verbatim>mv /sdcard/flash_image /system/bin/</verbatim>
then i got
<verbatim>failed on '/sdcard/flash_image' - Cross-device link</verbatim>
Any help?
Click to expand...
Click to collapse
Done..
I changed the guide..
You should have no problems now :0)
If you do, i have changed the link/roottools to include busybox...
I can make changes again to the guide if you have no luck with the new guide...
NB: i have only changed a small part... YOU in particular only need to read step 9(old step 10) again... just a trick to avoid using cp or mv...
we push the file directly to /system/bin hihihihi.

Made some changes to the guide for better success chances

Updated the guide with more info regarding the 1.2 version magic (with 3.5mm jack).

Updated the guide with more info regarding the 1.2 version magic (with 3.5mm jack).

Doh can you host the RootTools somewhere else? RapidShare doesn't like me and says I've reached the max amount of download. Dunno.
Also. My phone is already rooted and I have a perfect SPL ending in 0006. Do you think it would be OK for me just to do Step 6? Or maybe I should just follow another guide?
Also, why do some guides for fixing perfect SPLs say you have to have a goldcard and then others don't?
Thanks!

Step 5 is more importent then step 6...
Recovery is safer to mess with...
Spl is win or lose... if it goes bad your in trouble...
if recovery goes bad, no harm at all :0)
But yes, if you allready have root, then just pick up at step 5!
Regarding the goldcard:
The app is using a special exploit in the linux/android system to give you root..
So you dont need the goldcard...
The goldcard is something HTC related.. to fool the hardware/software to do something is not supposed to do.
That's why some guides need goldcard while others don't :0)
You want other download links?
Say the magic word... and it's not doh!

[Q] Rooted w/ Unrevoked, .apk files still read-only

I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?

BR3W CITY said:
I used Unrevoked to root my desire earlier today. It went through all the steps fine, saying at the end that it was "victorious" and done. I re-booted, and got into the ClockwordMod, so I assume it worked as intended.
I'm trying to delete the stock bloatware off of my device (USCC Desire), but when I used the CMD line to remove some of the .apk files, it tells me they are read only. Does this mean I didn't get Root?
I noticed 3 things after using unrevoked.
1. My boot screen still shows that S-ON, and I was under the impression that Unrevoked turned this off.
2. I can get into clockwordmod, unlike before
3. I have the superuser app showing up on my app's list.
Am I missing something obvious?
Click to expand...
Click to collapse
To test that you are infact rooted, please do the following:
1. Open command prompt/shell
2. cd into your AndroidSDK directory
3. Issue the command:: adb shell (if you see the # mark, then you are rooted -- otherwise type, su.)
To answer your questions:
1. When your phone says its "read-only file system"; this means that you need to issue the adb remount command; this will remount the system as RW (read/write), at which point you can go on deleting any apps you no longer want.
2. If you still have S-ON, that means you did not run the Unrevoked FOREVER file. You've only ran the Unrevoked 3 file. Notice when going to the Unrevoked site, that there are two different downloads.
3. Clockworkmod/superuser will exist because you are rooted and the process was successful.

alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.

n/m, didn't read previous post properly

BR3W CITY said:
alright.
So, I use adb shell, and get the $, type SU and it gives me the #. From there I go to do the remount, but it seems that all I get is "adb not found" I can do the list just fine from this point, but any adb commands result in not found.
I have also done the same commands (remount, remount with a specific directory) and it says "remount not found"
I can get the app list as mentioned, and have attempted to uninstall/remove a stock app, but get the "read-only" file system error. So it sound like the problem comes in either mounting the folder, or getting it to switch to read/write.
Click to expand...
Click to collapse
What kind of phone? Some phones won't reliably mount the system partition read-write while running in normal mode. You should be able to do it from the clockwork recovery system though.

htc desire on 2.1, from USCC. I have not yet tried to do it from clockwork yet. I will try that later
Thanks!

Thanks for the help, putting her into ClockwordMod and using it to Mount /system solved the problem. Stock crap is gone yay!

NS 4G - Need radio image dump

Looking for anyone with a new NS4G to dump a copy of the radio. I messed up and flashed a rom that had a gsm radio attached. rendering my phone useless as far as phones go.

root
post a good root method and how to do the dump. I can have it hotlinked in 1 hour

i used http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
worked just fine.

Once you're rooted, do
Code:
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
Then upload that ns-cdma-radio.img somewhere ;D

?
ok thanks, i will link it when finished
the dumped file will be in my phone memory, correct?

ryandoubleu said:
ok thanks, i will link it when finished
the dumped file will be in my phone memory, correct?
Click to expand...
Click to collapse
It will be on your internal storage that you can mount as a drive on your pc, yes.

may take...
may take longer than an hour as I am doing the SDK install

ryandoubleu said:
may take longer than an hour as I am doing the SDK install
Click to expand...
Click to collapse
You don't need the platform api, just the SDK tools/platform-tools , that'll save you a lot of download time.

yes i should have mentioned that. i didn't install the SDK either just the tools.
just like http://forum.xda-developers.com/showthread.php?t=878786

hmm
fastboot command wont work? troubleshooting as we speak

ryandoubleu said:
fastboot command wont work?
Click to expand...
Click to collapse
instal drivers?
look to the 2nd rooting method i posted. the 2nd file you download are the drivers. you would install it when your phone is in fastboot mode then go to device manager and upgrade the driver

unzip the rar file and make sure to select x86 or x64 driver for your pc.
you should be able to type "fastboot devices" hit enter and it will return your phone if you have the drivers installed

Also the simplest method to get the drivers might be to put phone into fastboot mode, plug USB to computer, then install PDA Net (which automatically installs the phone drivers). I personally could not get the drivers to install manually on Windows 7, had to use the PDA Net method.

CMD is giving my a Permission Denied with this command
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040

ryandoubleu said:
CMD is giving my a Permission Denied with this command
adb shell dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
Click to expand...
Click to collapse
Try this: (I am assuming you've already finished rooting and installed superuser)
run adb shell
that should give you a "$" prompt in your command window (you've just shelled into your phone)
then type "su" (without the quotes)
On your phone, a superuser request should pop up on the screen, hit Allow
Your command prompt should change to a #
then type
dd if=/dev/mtd/mtd5 of=/sdcard/ns-cdma-radio.img count=12583040
*EDIT: made a typo in the original writeup of this post and left out the count parameter*
(no adb shell required before the dd command this time since you're already shelled into the phone)

here it is
http://www.megaupload.com/?d=H3Z7RQLZ radio image for you
Also, from the first root method I cant find this file and move forward
4. Tap on the gray box that says Mount R/W
5. Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
6. Once renamed, download and install the app called ROM Manager from Android Market
7. Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.

ryandoubleu said:
http://www.megaupload.com/?d=H3Z7RQLZ radio image for you
Also, from the first root method I cant find this file and move forward
4. Tap on the gray box that says Mount R/W
5. Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
6. Once renamed, download and install the app called ROM Manager from Android Market
7. Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.

joebags said:
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
Click to expand...
Click to collapse
Actually the point of renaming that script is to prevent clockwork from being overwritten by the stock recovery.
The default stock rom is set up to re-flash the stock recovery from cache on bootup if it detects that it's been changed (which is very annoying if you *want* clockwork recovery).

thank you very much for uploading that for me
now correct me if i'm wrong netarchy but i would use fastboot to flash the img file?
I just want to double check before i mess up once again. i'm pretty smart and a quick learner but not a pro like yourself

worked?
joebags said:
i didn't do that i just ran ROM manager and flashed the latest Clockwork. you're backing up the old recovery. in that step, good idea, sure. needed, not really.
Click to expand...
Click to collapse
the radio.img got you working?

[Q] ADB push permission denied while trying to temp root on HTC Glacier via Windows

Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks

thepaperescape said:
Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks
Click to expand...
Click to collapse
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
How ever their are much easier methods. This being one of them. Makes sure to go to page two.

neidlinger said:
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
Click to expand...
Click to collapse
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.

thepaperescape said:
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.
Click to expand...
Click to collapse
okay.
I've seen alot of people try this method and very little come out okay.
you need SU access to push objects to the phone. The phone is seeing it as a foreign object and is wanting to prevent it from being pushed. The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.

Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App

Nicgraner said:
Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
SU was actually Switch User but Super User is used ATM due to the confusion it created to the newbies a decade ago who didn't understand how permission base structure on *nix worked. Which always required chmod and whole rwx thing even made it more confusing so they preallocated it with [email protected] with UiD:0 as default permission.
Now what I like to know is why are you using that howto? As neidlinger stated just run VISIONary+ to get TempROOT and then do root.sh to obtain PermROOT. If you need to unlock the CiD just call TMo and get the code free as no need to risk it. But if you still want Radio S=OFF then just do the simple gfree step and you will have it.

You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?

UsrBkp said:
Now what I like to know is why are you using that howto?
Click to expand...
Click to collapse
Well for one, I chose that guide because my goal is to install cyanogen and that is found directly off their site regarding my phone. My expectation is that a group of developers so renowned for their contributions should be able to correctly explain how to get to the point of install. Still I know it's a wiki, and things are constantly changing (generally faster than the wiki). For instance, I did notice that the wiki was incorrect about the location of the google usb drivers post download. I assume that is due to the newer version of the sdk i installed. And the jdk r25 is pretty new and I believe that to be one of the other things causing me problems, but I don't know for sure.
neidlinger said:
The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.
Click to expand...
Click to collapse
I tried doing this for those two files (su and superuser) that are supposed to be pushed onto the sd root and i thought it worked. cmd allowed me to push the other three files into /data/... no problem. chmod to 0755 even seemed to work (it neither explicitly approved or denied). but then when I got to step 8, terminal on the phone said i did not have access to run that command.
shuka325 said:
You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?
Click to expand...
Click to collapse
That's what I figured based off of the guide (since it's a guide on GETTING TO temproot, but what do I know... i'm supernoob. I've attached an image to see if you can see ANYTHING wrong with what I'm trying to do.
Thanks for everything guys!

I would give up that guide and use VISIONary to gain Temp Root & Root.sh to obtain perm Root. Then install the latest rom manager and make sure CWM sticks. Then you can flash CM7, or any other ROM for that matter.

Is there any guide you all think stands above the rest?!?!

thepaperescape said:
Is there any guide you all think stands above the rest?!?!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=13989736&postcount=6

1st time attempt to root, stuck at visionary+

Hi all,
I appreciate this forum is cram packed with info, but for me as a newb...I can't see the woods for the trees :-(
I have a stock Orange D-HD ( A2.3.3 with sense 2.1 ) and basically just want to unlock it to use an O2 sim.
I have previously flashed WM6 cooked roms onto Kaisers / Hermes & Himyies so do understand the basic principle. And I grasp the basic point about rooting as I have flashed a Superpad device too.
http://forum.xda-developers.com/showthread.php?t=964996
So I started to follow the above tutorial thread and downloaded Visionary+ and S-OFF etc.
But even though I set USB root debugging, when I run Visionary+ to temp-root, my DHD just runs the triange message a few seconds and then just goes blank.
Is there an alternative way to root instead of visionary+ ???
Someone pls help me get past the first hurdle and root my device
Thanks

I got stuck too but...
Did u try ticking the 'root on startup or reboot' option? then restart. it may take a few goes, u'll probably notice Superuser has been installed then Temproot should happen next reboot. Permroot's the same, may take a few times to stick. To test if ur root has worked try installing Titanium Backup from market, u'll need it once ur rooted.

If you have a Stock HTC with Android 2.3.3 you need to downgrade the software version first before you can use visionary.
[GUIDE] How to downgrade 1.7x/1.8x/2.x to 1.32.405.6

ahh ok, will do.
None of this was mentioned in the guide link I mentioned in the original post. It would be worthwhile for that guide to be modded to reflect the fact a downgrade is needed.
"Open up a cmd and go to Downgrade folder"...is this done on the PC or the phone??? don't understand...

hey, have you created a goldcard mentioned in section 1 of the tutorial?

ermm,, nope
I wasn't sure I needed to as it seemed to be related to branded phones. Mine is locked to orange at present....but it doesn't have an orange splash screen or any orange logo on the phone casing. Thought if my 'build' number had '405' in the middle...that this meant I didn't need a goldcard creating...
wrong or right peeps??

ebod said:
None of this was mentioned in the guide link I mentioned in the original post.
Click to expand...
Click to collapse
Ehem......
wid0w said:
If your Desire HD is running stock firmware 1.7x, please check this guide in order to downgrade:
http://forum.xda-developers.com/showthread.php?t=905003
Click to expand...
Click to collapse
and
wid0w said:
Basic Setup
...
- Desire HD with lower than 1.7x stock ROM
...
Click to expand...
Click to collapse
I think the guide captures every detail.

for3st said:
Ehem......
and
I think the guide captures every detail.
Click to expand...
Click to collapse
All very well if you understand what a rom is. My software page is full of 2.50 , 2.6 type numbers and nothing below 1.7....hence my comment.
Also, I've made a goldcard out of a spare 1gb sd, and copied PD98img.zip to it. So for the next bit....do I now put that goldcard in my HTC and connect to the PC whilst set in USB debugging enabled mode.
Then do I put this lot below into the win-xp pc 'run' box line by line or one whole lump?:-
adb push misc_version /data/local/tmp
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
./data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF

ebod said:
All very well if you understand what a rom is. My software page is full of 2.50 , 2.6 type numbers and nothing below 1.7....hence my comment.
Also, I've made a goldcard out of a spare 1gb sd, and copied PD98img.zip to it. So for the next bit....do I now put that goldcard in my HTC and connect to the PC whilst set in USB debugging enabled mode.
Then do I put this lot below into the win-xp pc 'run' box line by line or one whole lump?:-
adb push misc_version /data/local/tmp
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
./data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
Click to expand...
Click to collapse
one by one......

I dont use Visionary+ , it just dont work in my phone,end me up using manual method. Plus S-off and Engineering S-off.
First of all, DOWNGRADE UR PHONE TO 1.32
Gaining Radio S-OFF:
This method will get you the Radio S-OFF flag while SIM-unlocking it and setting up SuperCID, which means
1. This method will root your phone for the process if it isn’t already rooted. If you just want to permanently root your phone
2. Make sure you have ADB installed on your computer. Also, if you have previously installed VISIONary on your phone in order to root it, uninstall it first before proceeding.
3. Download Desire HD S-OFF Toolkit and unzip its contents to your computer. Put it in your adb folder
4. Enable USB Debugging on your phone from Settings > Applications > Development.
5. Connect your phone to your computer via USB.
6. Launch a Command Prompt/Terminal window on your computer, navigate to the folder where you extracted the files in Step 3 and enter the following commandsne by one , press enter after each line
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 push gfree /data/local
adb shell chmod 0755 /data/local/tmp/*
adb shell chmod 777 /data/local/gfree
7. Install Terminal Emulator app on your phone from the Android Market and launch it.
8. Enter the following command in Terminal Emulator on your phone:
/data/local/tmp/rage
9. In a while, you will see the output “Forked #### childs”. Now press ‘Menu’ and tap ‘Reset Term’ to exit Terminal Emulator.
10. Launch Terminal Emulator again. You will notice that it force-closes. Don’t worry and just launch it again, and you should have a root shell indicated by the # prompt instead of $.
11. Now enter the following commands in Terminal Emulator:
/data/local/gfree -f
sync
/data/local/tmp/root
sync
If you get a ‘mkdir: /system/xbin already exists’ error during the process, ignore it and proceed.
12. Wait patiently while the process finishes. Once it is complete, reboot your phone.
You should now have Radio S-OFF, SIM-unlock and SuperCID all set on your phone. If you just want to install ClockworkMod recovery and custom ROMs etc., you are all good to go and do not need to gain Engineering S-OFF. You may simply install ClockworkMod Recovery, find a custom ROM of your choice and flash it to your phone from recovery.
Gaining Engineering S-OFF:
You should attempt to gain Engineering S-OFF if and only if you want to gain absolute access to your Desire HD including the ability to flash a radio or edit all your phone’s partitions the way you want. If you are not absolutely sure what you are about to do, we recommend that you do NOT proceed.
1. Make sure you have already gained radio S-OFF by following the above-mentioned steps.
2. Download the Engineering HBoot for HTC Desire HD and extract the contents of the zip files.put in adb folder
3. Enable USB debugging (if not already enabled) and connect your phone to the computer.
4. On your computer, launch Command Prompt/Terminal, navigate to the folder where you extracted the files in Step 2 and enter these commands:
adb push hboot-eng.img /data/local
5. Finally, launch Terminal Emulator on your phone and enter these commands, being EXTREMELY careful not to make any mistake here:
su
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Make sure to allow when Super User access is requested. Wait till the process is finished and you’re done!
You now have the Engineering S-OFF HBoot installed and with this, you have absolute control over your HTC Desire HD. You can now flash radios of your choice to your phone and have access to modify all its partitions as well as unbrick it in certain circumstances where no other method would revive your device.
Click to expand...
Click to collapse

rohithksaj said:
one by one......
Click to expand...
Click to collapse
...but I get lost here : "•Open up a cmd and go to Downgrade folder, execute commands:"i.e. I don't understand a 'cmd' is an where I open it from..
EDIT : okay finally at 1.32 & rooted ( yey!)
wanting to check whether the S-OFF info is right but having a mare trying to get bootloader screen to stop from tripping to HBOOT and running the PD98IMG ( even though I took out the goldcard ).
Is there some specific combination to hold vol-down and power for a set number of seconds? I've tried 10+ times and can't stop it going onto the HBOOT update thingy :-(

Ok folks...back to my painful rooting excercise
I'm still in this thread
http://forum.xda-developers.com/showthread.php?t=964996
..trying to eastablish whether or not my S-OFF info is correct before proceeding further. The thread says :-
"Testing Eng S-off and Radio S-OFF
1. Power Down Your Device
2. Go to Bootloader
3. If it says Ace PVT ENG S-OFF your phone is ENG S-OFF.
4. use Volume down to get to system info and tap power button to select
5. check CID for CID-11111111 (if you have this all is done 100%)
6. Reboot
"
how can I check my "CID-11111111" info ? where is it displayed?

DOH STUPID STUPID STUPID!!!!!
Before I made my goldcard I put a copy of pd98img.zip on my SD card....and although I took out the goldcard...when I put the normal SD back in, I neglected to recall it had a copy of pd98img.zip still sat on it.
Thats why I couldn't access bootloader.
Anyways, I have the right S-OFF info so its now onwards the next step