[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.
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
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

OK. It seems that you have a corrupt mdt layout.
The only thing left, is to re-flash your device from fastboot.
Find an appropriate ruu (matching your version nr) and re-flash to stock.
If your version nr is to high, we can always "downgrade" it to a lower version nr.

If you use fastboot commander ver. 1.51 from my signature, and copy-paste the device info and post it here, i can help you find the right ruu for you.

ScriptJunkie said:

Thanks and sorry for the redundant question.

Where can I get the 1.33.0013d SPL?

No worries, I found the post you were talking about. But 1.33.0013d does not take the S-OFF, it just allows to use one fastboot command. Is there a way that I can get full fastboot control with 2.2.1 update?

Is there a fast ROM that you would recommend for this set up?

SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013d (SAPP30000)
CLPD-10
RADIO-2.22.27.08

Thanks, you are the most helpful person I have found in this forum.

Click to expand...

Click to collapse

tony yayo said:

Figured it was key to being rooted. Ok, so how do I run app that requires super user?

Click to expand...

Click to collapse

ScriptJunkie said:

A easy quick check (to see if you are properly rooted) is to download a terminal in your phone and type su. If the $ changes to # you are set.

You have to allow root privileges to the terminal for this to work. But this comes from the root app. So if you say is not there I don't know.

I rooted with SuperOneClick and I had to reboot for the root app to work.

Click to expand...

Click to collapse

tony yayo said:

Think i might try a factory reset and start over.

Click to expand...

Click to collapse

Ok... to clarify SU and super user app:

SU = Super User.
It's a special binary with only one purpose, to give you root access (root = super user = i can what the f*** i want to do).
Some devices has the binary already, but you can only use it if you are root.. so its like chicken and eggs.. you need one for the other to work and vice versa.

What does rooting app / scripts / programs do then ?
Well, the only thing they do is to make sure you have su-binary in your system, and that EVERYBODY can call it... that's why you can get root permission by simply calling: su...
That's when your terminal marker changes from $ (normal user) to # (root)...

What does super user app do then ?
Well, the problem is that EVERYBODY can call su and get root permissions... so if you have other apps in your device, they can get root permissions and mess your system up if they want... super user app creates a wall around su-binary, so you have to get through the app to get root permissions. This way, you (the user) have control over WHO and WHAT get access to root permissions.

Summary: Super user app is nice to have, but it is NOT a necessity. If the su-binary is there and you can call it, then you are ROOTED ( have root permissions).
Simple test is to call su inside a terminal app... if you marker changes to # then you have root (no matter if super user app is there or not)...
You could also start a shell from adb, then call su.. if the marker changes.. you are rooted.

I hope this helps the confusion around su / root / super user ap / rooting.

To answer the following: "But 1.33.0013d does not take the S-OFF, it just allows to use one fastboot command. Is there a way that I can get full fastboot control with 2.2.1 update?"
You can always flash eng spl (1.33.2010) through custom recovery to get full fastboot controll.. once you are done doing the stuff you need to do, you NEED to flash back the 1.33.0013d spl for the android system to work...

Or you could hex-edit the 1.33.0013d spl making it discard all s-on flags and thereby become s-off (good luck :0)

Check out the second post.
All the info is there..
Don't forget to hit that thanks button :0)