Database Info

Root for my HTC magic from roger!!!

Hi,
I try to update to root hofo image.
i copy the update file to sdcard
in recovery utility i run apply sdcard:update.zip
e:No signature (553 files)
E:Verifycation failed
Installation aborted
can you help me root my htc roger?
SAPPHIRE PVT32A SHIP S-on H
HBOOT-1.33.0010 (SAPP5000)
CPLD-12
RADIO-3.22.20.17

doronb said:
Hi,
I try to update to root hofo image.
i copy the update file to sdcard
in recovery utility i run apply sdcard:update.zip
e:No signature (553 files)
E:Verifycation failed
Installation aborted
can you help me root my htc roger?
SAPPHIRE PVT32A SHIP S-on H
HBOOT-1.33.0010 (SAPP5000)
CPLD-12
RADIO-3.22.20.17
Click to expand...
Click to collapse
You have to update the SPL
http://forum.xda-developers.com/showthread.php?t=529019

This should be in General. But here you go.
Fallow This guide and you'll be fine.
Clinton

fastboot mode
ClintonH said:
This should be in General. But here you go.
Fallow This guide and you'll be fine.
Clinton
Click to expand...
Click to collapse
in fastboot mode this what i get
C:\android-sdk-windows-1.5_r2\tools>fastboot boot recovery.img
downloading 'boot.img'...
and i n the mobile nothing...!
C:\android-sdk-windows-1.5_r2\tools>fastboot boot recovery-RAv1.2.0H.img
downloading 'boot.img'... FAILED (remote: not allow)

doronb said:
in fastboot mode this what i get
C:\android-sdk-windows-1.5_r2\tools>fastboot boot recovery.img
downloading 'boot.img'...
and i n the mobile nothing...!
C:\android-sdk-windows-1.5_r2\tools>fastboot boot recovery-RAv1.2.0H.img
downloading 'boot.img'... FAILED (remote: not allow)
Click to expand...
Click to collapse
Make sure you have your drivers installed correctly. When adb devices does it list your phone or no. I'm guessing it does not and your drivers need to be installed correctly. Just fallow the guide I gave you to the letter and it will work perfectly, has for 2 of my phones for numerous ROM flashes.
Clinton

Just reread this, you have the new HBOOT-1.33.0010 (SAPP5000) SPL, sorry didn't realize that. You'll have to downgrade to a flashable SPL. The instruction should be on the forum just do a search. Did you phone come with that SPL or did you do the update from Rogers?
Found it knew I ran across it before. http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/
Clinton

ClintonH said:
Just reread this, you have the new HBOOT-1.33.0010 (SAPP5000) SPL, sorry didn't realize that. You'll have to downgrade to a flashable SPL. The instruction should be on the forum just do a search. Did you phone come with that SPL or did you do the update from Rogers?
Found it knew I ran across it before. http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/
Clinton
Click to expand...
Click to collapse
i have the updated htc rogers 32a same spl as this and i successfully followed the unlockr 1 click root guide.. running hero rom now and my spl is still 1.33.0010 sapp 50000

Howler62 said:
i have the updated htc rogers 32a same spl as this and i successfully followed the unlockr 1 click root guide.. running hero rom now and my spl is still 1.33.0010 sapp 50000
Click to expand...
Click to collapse
Yeah sorry meant to edit that out. You don't have to downgrade just different steps on rooting. I don't have this SPL so I've never had to do anything different than the guide in my first post just happened by the info a few weeks ago.
Clinton

Thank you for the support
ClintonH said:
Just reread this, you have the new HBOOT-1.33.0010 (SAPP5000) SPL, sorry didn't realize that. You'll have to downgrade to a flashable SPL. The instruction should be on the forum just do a search. Did you phone come with that SPL or did you do the update from Rogers?
Found it knew I ran across it before. http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/
Clinton
Click to expand...
Click to collapse
Hi,
This link help me to upload the JACHERO
The only problem i heave with this jacohero rom, is the connect to Bluetooth device! i found the 520Plantronics and paired.
The device status "Connected to phone audio"
but if i do a call the voice is in the mobile phone!
is it a bug?

Yeah if you search the forum you'll find that all Hero builds have the BT issue. Until the source is released it cannot be fixed. If you need working BT you'll have to go with a different ROM.
Clinton

[HELP!] CM5 on 32A

I'm having trouble flashing CM5. I'm coming from Sense hero Capy v0.3.
Using recovery RA-hero-v1.6.2, I'm seeing the following while attempting to flash update-cm-5.0.7-DS-test1-signed.zip:
assert failed: getprop("ro.product.device") == "trout" || getprop("ro.bE:unknown command [uild.product")]
getprop("ro.product.device") == "sapphire" || getprop("ro.build.E:unknown command [product")]
E:Error in /sdcard/update-cm-5.0.7-DS-test1-signed.zip
(Status 7)
Do I need to go back to a Magic recovery? What are my next steps? Don't wanna screw this up.
Thanks.

What rom did you actually grab? If you grabed it from one of the few threads on here tonight, thats not for 32ANR, those were for MyTouch3G LE/1.2
So can you specify?
If you grabed the rom from http://forum.cyanogenmod.com/index....gic-would-you-like-a-pony-v507-test1-04292010 , make sure you also flashed their 32A/EBI1 port.

you should flash a cm5.0-32a port.

kbeezie said:
What rom did you actually grab? If you grabed it from one of the few threads on here tonight, thats not for 32ANR, those were for MyTouch3G LE/1.2
So can you specify?
If you grabed the rom from http://forum.cyanogenmod.com/index....gic-would-you-like-a-pony-v507-test1-04292010 , make sure you also flashed their 32A/EBI1 port.
Click to expand...
Click to collapse
Oh damn! I assumed I could flash update-cm-5.0.7-DS-test1-signed.zip, then bcrook's bc-5.0.7-t1-ebi1_R2-signed.zip. Guess we still need to wait? Little over anxious I guess.

gleonard3 said:
Oh damn! I assumed I could flash update-cm-5.0.7-DS-test1-signed.zip, then bcrook's bc-5.0.7-t1-ebi1_R2-signed.zip. Guess we still need to wait? Little over anxious I guess.
Click to expand...
Click to collapse
Wait, now I'm confusing myself... I grabbed
http://kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-test1-signed.zip
and
http://briancrook.ca/android/cm-ports/bc-5.0.7-t1-ebi1_R2-signed.zip
That seems right to me. But when I try to flash I get the error in the OP.

You need to revert back to your old radio (3.22) / Engg. SPL. (1.3x) Also revert to the sapphire recovery.
Then flash, in this order:
1. http://kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-test1-signed.zip
2. http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
2. http://briancrook.ca/android/cm-ports/bc-5.0.7-t1-ebi1_R2-signed.zip
CM 5.0.7 works wonderfully on my 32A (not 1.2/LE). It flies!
gleonard3 said:
Wait, now I'm confusing myself... I grabbed
http://kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-test1-signed.zip
and
http://briancrook.ca/android/cm-ports/bc-5.0.7-t1-ebi1_R2-signed.zip
That seems right to me. But when I try to flash I get the error in the OP.
Click to expand...
Click to collapse

pix27 said:
You need to revert back to your old radio (3.22) / Engg. SPL. (1.3x) Also revert to the sapphire recovery.
Then flash, in this order:
1. http://kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-test1-signed.zip
2. http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
2. http://briancrook.ca/android/cm-ports/bc-5.0.7-t1-ebi1_R2-signed.zip
CM 5.0.7 works wonderfully on my 32A (not 1.2/LE). It flies!
Click to expand...
Click to collapse
Will do. Thanks!

gleonard3 said:
Wait, now I'm confusing myself... I grabbed
http://kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-test1-signed.zip
and
http://briancrook.ca/android/cm-ports/bc-5.0.7-t1-ebi1_R2-signed.zip
That seems right to me. But when I try to flash I get the error in the OP.
Click to expand...
Click to collapse
First you flash the CM-5.0.7 rom, then you flash the ebi1 patch.
You may have to wipe first, and also re-download the zips if you think they might have gotten corupted.
Also based on the error, its possible you may not even have the correct hardware, if you're not using a dream or sapphire device, then its not gona want to install. (though your sig seems to suggest you have a sapphire device)

If that fails, I think you'll find that you have the Hero version of Amon_RA/Cyanogen's recovery on your phone, whereas you'll actually need the Sapphire/Magic version

pix27 said:
You need to revert back to your old radio (3.22) / Engg. SPL. (1.3x) Also revert to the sapphire recovery.
Then flash, in this order:
1. http://kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-test1-signed.zip
2. http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
2. http://briancrook.ca/android/cm-ports/bc-5.0.7-t1-ebi1_R2-signed.zip
CM 5.0.7 works wonderfully on my 32A (not 1.2/LE). It flies!
Click to expand...
Click to collapse
O,,I got the same problem, Is CM5 works with old radio,spl and sapphire recovery but not the new radio,spl and hero recovery?
Ths for help

i AM GETTING THE SAME ERROR ON
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005
CPLD-12
RADIO-3.22.20.16
CLOCKWORK RECOVERY

Yes. you need the OLD radio.
exe127 said:
O,,I got the same problem, Is CM5 works with old radio,spl and sapphire recovery but not the new radio,spl and hero recovery?
Ths for help
Click to expand...
Click to collapse

Try with the RA sapphire recovery.
dwayne08 said:
i AM GETTING THE SAME ERROR ON
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005
CPLD-12
RADIO-3.22.20.16
CLOCKWORK RECOVERY
Click to expand...
Click to collapse

Anyone have an idea of how hard would it be for somebody to come up with a port for new radio?

exe127 said:
O,,I got the same problem, Is CM5 works with old radio,spl and sapphire recovery but not the new radio,spl and hero recovery?
Ths for help
Click to expand...
Click to collapse
Confirm, I was flash backward to old radio & spl then follow above order to flash CM5. It's rebooting now~~~ waiting~~~

Yes, you have to revert to old SPL and Radio.
I tried with new SPL and didn't work. With old SPL and RADIO it is working fine up to now.
Regards,
Mauro

You may have only downloaded a part o the files. If you got them lastnight when the servers were slammed, Then you only got pieces of the files.

exe127 said:
O,,I got the same problem, Is CM5 works with old radio,spl and sapphire recovery but not the new radio,spl and hero recovery?
Ths for help
Click to expand...
Click to collapse
yes it does work on old radio but not sure about the new radio..........i'm using cm5 on old radio only................

My Magic already came with new radio (6.35.07.29) when I bought it. Is safe to downgrade to old radio? I really want to test this rom . If it's safe, wich version of radio should I pick?

nevermind.....

32B downgrade to cupcake (1.5)

hi all,
ive got created a gold card yes i did it
but now the next problem.
ive got the LATEST original vodafone rom.
i put the sappimg.nbh from cupcake 1.5 in my root in the sd sappimg.nbh.
but now when i want to update it still gives the error: Main version is older
Please can someone explain me what i need to do???
//Nick

aw common someone should know this??
what do i have to do to downgrade? when i already used the goldcard methodit didnt worked man
//Nick

How about this:
[How-To] Fix perfected SPL (fastboot remote: not allow)
forum.xda-developers. com/ showthread.php?t=548218

Mods, please delete....duplicate post

Hee tnx man. Bureau isnt that thread for rooted users already?
Andere of i want to root, do i really need tot downgrade tot 1.5 first?
//Nick

nickislauw said:
Hee tnx man. Bureau isnt that thread for rooted users already?
Andere of i want to root, do i really need tot downgrade tot 1.5 first?
//Nick
Click to expand...
Click to collapse
DO NOT USE ehb224 post. It is for Magics 32A
32B users must use CyanogenWiki manual
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
Note: in cyanogenwiki used cyanogen recovery, but all can use AMon_RA recovery or Clockworks recovery
Another thing: After getting recovery all can flash other 32B ROMs, not only CyanogenMod

5[Strogino] said:
DO NOT USE ehb224 post. It is for Magics 32A
32B users must use CyanogenWiki manual
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
Note: in cyanogenwiki used cyanogen recovery, but all can use AMon_RA recovery or Clockworks recovery
Another thing: After getting recovery all can flash other 32B ROMs, not only CyanogenMod
Click to expand...
Click to collapse
lol DID used that on my 32b and it just works perfectly lol
//Nick

5[Strogino] said:
DO NOT USE ehb224 post. It is for Magics 32A
Click to expand...
Click to collapse
According to the info in the thread (and Amon_RA) it is for either 32A or 32B boards.
If you read through the thread it does say that a 32B board does need to have a 32B radio flashed after.

Sapphire 32A 32B SPL 1.33.2013 & SPL 1.33.0013 for T-MOBILE 2.2 FROYO update

Hi all,
I just made a New modified SPL for new T-Mobile 2.2.1 FROYO update
The following SPL "should" work on PVT 32A and PVT 32B boards :
Crios SPL 1.33.2013 ENG
or
WARNING !!!! This is PREFECT SPL !!!
Original SPL 1.33.0013 SHIP
WARNING !!!! This is PREFECT SPL !!!
How to Flash
after you can try to install
FROYO 2.2 OTA modified - no check
or try the following original updates:
FROYO 2.2 OTA or
FROYO 2.2 OTA FRG83 from DMD64
Remember:
This SPL is 1.33.2005 HexEdited
Crios
Buy me a FROYO

How big of a risk is it to flash this?

Crios said:
Hi all,
I just made a New modified SPL for new T-Mobile 2.2.1 FROYO update
SPL 1.33.2013
How to Flash
after you can install FROYO 2.2 OTA
Remember:
This SPL is 1.33.2005 HexEdited for 32B.
Crios
Buy me a FROYO
Click to expand...
Click to collapse
Why did you create a separate thread for this?

oj0043 said:
How big of a risk is it to flash this?
Click to expand...
Click to collapse
Minimum
It is full 1.33.2005 classic ENG SPL
Crios
Buy me a FROYO

So you just edited 1.33.2005 to make it look like the 1.33.2013?

eyegor said:
So you just edited 1.33.2005 to make it look like the 1.33.2013?
Click to expand...
Click to collapse
In a simple way....YES

Crios said:
In a simple way....YES
Click to expand...
Click to collapse
Alright, I'll test it on the 32A.

Works just fine on my 32A Magic!

This does indeed flash and show the new version info, but the OTA fails to flash. Sounds like the OTA requires s-ON

dasunsrule32 said:
This does indeed flash and show the new version info, but the OTA fails to flash. Sounds like the OTA requires s-ON
Click to expand...
Click to collapse
The OTA requires a correct SPL version.
Can you show us the error and the details of your phone?

Crios said:
Can you show us the error and the details of your phone?
Click to expand...
Click to collapse
32b, your new spl
E: Failed to verify whole-file signature
E: signature verification failed. Installation aborted.
In Clockwork, disable verification:
assert failed: getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire"
E:Error in /sdcard/e059adc603a3.signed-opal-ota-60506.e059adc6.zip
(Status 7)
Installation aborted.
I have root, let me try to nix that and see if it will work.

dasunsrule32 said:
32b, your new spl
E: Failed to verify whole-file signature
E: signature verification failed. Installation aborted.
In Clockwork, disable verification:
assert failed: getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire"
E:Error in /sdcard/e059adc603a3.signed-opal-ota-60506.e059adc6.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Simple:
Check your /System/build.prop file
ro.product.device and ro.build.product must be = sapphire

Crios said:
Simple:
Check your /System/build.prop file
ro.product.device and ro.build.product must be = sapphire
Click to expand...
Click to collapse
It is, it was a stock build.

dasunsrule32 said:
It is, it was a stock build.
Click to expand...
Click to collapse
It's a strange error with stock build.
Try to wipe and retry.

Crios said:
It's a strange error with stock build.
Try to wipe and retry.
Click to expand...
Click to collapse
I did wipe, same issue. Others are reporting the same issue. I am wiping and returning to a complete stock 1.6 and will root flash the spl and try again.

I think that the problem is in the rom signature. because I can flash another roms with this SPL but the 2.2 original rom gives me the same error.

Enigma87 said:
I think that the problem is in the rom signature. because I can flash another roms with this SPL but the 2.2 original rom gives me the same error.
Click to expand...
Click to collapse
It's not a problem with the rom, it's an old SPL trying to fool a newer update. Don't believe this method will work properly. *fingers crossed*

dasunsrule32 said:
It's not a problem with the rom, it's an old SPL trying to fool a newer update. Don't believe this method will work properly. *fingers crossed*
Click to expand...
Click to collapse
Probably the problem is:
check_prereq 1285103450
and
assert(!less_than_int(1285103450, getprop("ro.build.date.utc")));

A bit of success... sort of
After I flashed the SPL, I booted into stock 1.6 and almost immediately received notice of the second OTA update. So I reflashed the stock recovery (non-custom) and was able to flash the update.
However it hung up on the splash screen after reboot (I let it sit there for 30 min).
Hope that sheds some light on the problem.

The SPL is the incorrect version number: 1.33.0013 is the correct version. Not sure if this will affect the update or not.

[GUIDE] Rooting your Perfected SPL Magic!

You're probably thinking why this idiot has posted a short rooting guide with no pics for the HTC "G2"/32B/Sapphire. I know there are others out there, but they are too long and take too much time compared to this method.
Well, with this method, you DO NOT need to DOWNGRADE to 1.5/1.6 from the OTA Froyo and is COMPLETELY friendly with non-data users, like me. This method WILL give you su and superuser access on the OTA Froyo update.
Instructions:​0) (As a pre-requisite, backup your sdcard on your computer, just in case, because the apk is known to erase/format the sdcard in the phone; It never happened to me, but it is better to play it safe)
1) Download gingerbreak from this thread (Yes, I know it says gingerbreak but it works on froyo also)
2) Install the .apk, run the apk
3) Phone will reboot, if successful
4) You are rooted! Superuser will be installed.
5) Continue below if you desire to continue to flash a custom rom
Click to expand...
Click to collapse
Credits: Chainfire (Infinite thanks!)
Click to expand...
Click to collapse
It is tested working by me on a T-Mobile Magic 32B that was unrooted with Perfected (S-ON) SPL and 2.22.28.25 radio. I used Gingerbreak 1.20.
Click to expand...
Click to collapse
EDIT: Please test and confirm it is working. If this method works, goldcards will not be needed to root devices with S-ON

Now you have root, now what?
Download the 'busybox installer' by Stericson.
Click to expand...
Click to collapse
After installing busybox and rebooting, you need to flash recovery.
Instructions​1) Download this binary (flash_image) as the OTA Froyo does not have it.
2) Download the recovery image from this thread: AMON_RA Recovery
3) Unzip, and copy the binary to sdcard and rename the recovery image you just downloaded to 'recovery.img' for simplicity
4) Now, I hope you have Android SDK installed as the next steps would be much easier with it (You can do it via terminal app on phone also)
Code:
adb shell
su *NOTE(You may need to press "allow" if the superuser prompt pops up)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin *NOTE (You cannot 'adb remount' or push any files to system/bin, that is why cp is used)
flash_image recovery /sdcard/recovery.img
5) Recovery should now be installed, and you can update your spl so you can install other roms, radios, hboot, etc...
Click to expand...
Click to collapse

Can this method be used to achieve S-OFF on a 32A Device, running Rogers 2.1 Sense rom with new 1.76.2007 ENG SPL and new radio?

Godzi said:
Can this method be used to achieve S-OFF on a 32A Device, running Rogers 2.1 Sense rom with new 1.76.2007 ENG SPL and new radio?
Click to expand...
Click to collapse
I think you can try this method, but make sure you flash a matching recovery. Maybe RA-1.7.0.1 or Bladyle's RA-2.2.0. After that you can flash S-OFF in recovery. What's your current SPL and Radio?

Godzi said:
Can this method be used to achieve S-OFF on a 32A Device, running Rogers 2.1 Sense rom with new 1.76.2007 ENG SPL and new radio?
Click to expand...
Click to collapse
This guide seems to be aimed at 32b devices running stock froyo
And (on 32b at least), eng spl=s-off...

Unkjcr said:
I think you can try this method, but make sure you flash a matching recovery. Maybe RA-1.7.0.1 or Bladyle's RA-2.2.0. After that you can flash S-OFF in recovery. What's your current SPL and Radio?
Click to expand...
Click to collapse
The thing is that the phone currently has RA 1.7.0 recovery installed and the latest radio + 1.76.2007 ENG SPL, but I have the S-ON and I want it OFF since I want to downgrade to the old radio and SPL.

Godzi said:
The thing is that the phone currently has RA 1.7.0 recovery installed and the latest radio + 1.76.2007 ENG SPL, but I have the S-ON and I want it OFF since I want to downgrade to the old radio and SPL.
Click to expand...
Click to collapse
I don't see how you could have s-on with an Eng spl... flash a different spl?

Godzi said:
The thing is that the phone currently has RA 1.7.0 recovery installed and the latest radio + 1.76.2007 ENG SPL, but I have the S-ON and I want it OFF since I want to downgrade to the old radio and SPL.
Click to expand...
Click to collapse
Was your SPL always S-ON or did it change back to S-ON after being S-OFF?

Unkjcr said:
Was your SPL always S-ON or did it change back to S-ON after being S-OFF?
Click to expand...
Click to collapse
I had not noticed it till now, but I think that it has always been S-ON.

Godzi said:
I had not noticed it till now, but I think that it has always been S-ON.
Click to expand...
Click to collapse
I asked this because the 1.76.0007 ENG SPL should have S-OFF. Try this command in fastboot mode: fastboot oem eraseconfig. After this check if the security of your SPL changed back to S-OFF.

It is only tested working on a 32B device with 1.33.0013 S-ON perfected spl (that came with the Froyo OTA update, if I'm not wrong).

Unkjcr said:
I asked this because the 1.76.0007 ENG SPL should have S-OFF. Try this command in fastboot mode: fastboot oem eraseconfig. After this check if the security of your SPL changed back to S-OFF.
Click to expand...
Click to collapse
Thanks. That did it.

Why does the title say 1.33.2013?
The only 2013 spl i know of is a edited 2005 spl that was used to trick updates... and its s-off

There, fixed it. I mean the *Perfected SPL* that comes with the Froyo OTA 32B Update. Sorry for confusion.

Mytouch 3g 1.2, used gingerbreak to root, phone rebooted verifyed root access, RESULT= PASS . It did not install superuser.apk rebooted phone after gingerbreak result= FAIL.
Any1 know why its not allowing me to install busybody?
That's the messaged I received
Sent from my MB525 using XDA Premium App

Is there a certain version of android I must have in order to root? Should I flash downgraded rom in order to root? I currently have 2.2.1 should I downgrade to make root easier?
Sent from my MB525 using XDA Premium App

ATXiceman512 said:
Is there a certain version of android I must have in order to root? Should I flash downgraded rom in order to root? I currently have 2.2.1 should I downgrade to make root easier?
Sent from my MB525 using XDA Premium App
Click to expand...
Click to collapse
You don't NEED to downgrade, but I find rooting 1.6 is the easiest way.
If this guide didn't work you might want to do the rooting manually. Go to c-skills.blogspot.com (hopefully thats right. Going by memory) and download the gingerbreak or killinginthenameof binary (gingerbreak is made with gingerbread as its main target, killinginthenameof was gonna be gingebreak but Google made some changes that prevented it from working. They both should work but if one doesn't, try the other) and run that in a terminal or adb. then push superuser.apk and su to their proper places (/system/app and /system/xbin I think). I can be more detailed if needed.

tvall said:
You don't NEED to downgrade, but I find rooting 1.6 is the easiest way.
If this guide didn't work you might want to do the rooting manually. Go to c-skills.blogspot.com (hopefully thats right. Going by memory) and download the gingerbreak or killinginthenameof binary (gingerbreak is made with gingerbread as its main target, killinginthenameof was gonna be gingebreak but Google made some changes that prevented it from working. They both should work but if one doesn't, try the other) and run that in a terminal or adb. then push superuser.apk and su to their proper places (/system/app and /system/xbin I think). I can be more detailed if needed.
Click to expand...
Click to collapse
Thank you for the prompt reply, I tried rooting with gingerbreak V1.20. The phone rebooted, I then ran a root checker to verify root it says "phone is rooted." But, don't think it is..... MY MAIN GOAL IS TO INSTALL CYANOGENMOD7 ON MY FIANCEE'S MYTOUCH 3G 1.2(HYBRID) If you could be make a short detailed guide that would be most helpful, I appreciate everything. If you could alsogo a little more Indepth about pushing applications and such.. thanks again. =)
Sent from my MB525 using XDA Premium App

ATXiceman512 said:
Thank you for the prompt reply, I tried rooting with gingerbreak V1.20. The phone rebooted, I then ran a root checker to verify root it says "phone is rooted." But, don't think it is..... MY MAIN GOAL IS TO INSTALL CYANOGENMOD7 ON MY FIANCEE'S MYTOUCH 3G 1.2(HYBRID) If you could be make a short detailed guide that would be most helpful, I appreciate everything. If you could alsogo a little more Indepth about pushing applications and such.. thanks again. =)
Sent from my MB525 using XDA Premium App
Click to expand...
Click to collapse
Okay.
Install rom manager from the market ad try to flash clockworkmod recovery. If it works, you had root and can now flash roms. If it doesn't.. post that and ill give better rooting instructions

So I rooted with super one click method and have a working super user (I think) it let's me use titanium and set cpu...so can I just skip the first post and start at the second post right?..and if so I was wondering if anybody knows if I can just start flashing away after the second post instructions or do I HAVE to flash a new spl..currently ship s-on .33.0013 I have the ota update radio as well...I'm not a noob to android as I have a cm7 nightly powered s-off tmobile g2,but a noob to my wifes mytouch, when I rooted the g2 (the way I did), is I rooted it then entered commands into terminal to get s-off, flashed cwm, and then it was game on...so is flashing a new spl the same as getting s-off in a way?? And if I have to, can somebody give me a link to a recomended spl?? Any info is appreciated..ty.
Sent from my HTC Vision using XDA Premium App