Database Users

Rooting 32B Magic 'Perfect' SPL, whilst ensuring it can be returned to stock

First, thanks for taking the time to read this. I appreciate that these forums get a lot of frustrating posts with people asking questions that have already been answered, and it is not my intention to do that. I have been lurking on these forums for a while, and have read around quite a bit of information. However, I cannot find the exact answers I am after.
To start, I am now on my 2nd HTC Magic 32B (Voda UK), after I sent my initial phone off for repair. I was running Cyanogen Mod on this phone, and flashed this rom by fastbooting in to Cyanogen's Recovery and going from there.
I was careful to take a nandroid backup before I flashed, and as such, when the time came to said the phone off for repair, I was able to restore the backup and send it off with the stock firmware running.
Unfortunately, the phone I have now received has a 'perfect' SPL, HBOOT-1.33.0007, so I cannot flash a rom using the same method.
My primary concern through all of this, is finding a way to flash roms such that I can revert everything back to normal if the need arises.
I have read around 1-click rooting, so, my proposed method at the moment would be:
1) use Flashrec to boot into Cyanogen Recovery
2) Backup using nandroid
3) using adb shell to flash Cyanogen Recovery
4) use Cyanogen Recovery to flash rom
I should now be in a position where I can a) flash back to the original recovery if needed, using the backup from nandroid, and b) flash back to the original rom if needed, using the backup from nandroid.
Would this work as I hope?
I have read about having to 'downgrade' the SPL when wishing to restore a nandroid backup, but I did not need to previously. What are the circumstances where you do need to? - I would not want to do this, since I have no way of flashing the original SPL back. I presume there is no way to backup my SPL? so I could return to it if need be?
Thanks for taking the time to read this, and I appreciate any help you may be able to give me.
Cheers.

I have a Rogers 32A that had a Perfect SPL (1.33.0010) on it and I got a rooted recovery ROM by using One Click Root. The Perfect SPL wasn't allowing me to fastboot at all (giving me a "no access" error or something). So instead I booted running the stock software, and used the one click root program to backup my ROM and then flash a recovery ROM (used the default Cyanogen Recovery 1.4). Then when I rebooted while holding down Power + Home, I came right into my rooted recovery ROM where I could install whatever .zip ROM I wanted (AFTER I BACKED UP WITH NANDROID, of course).
I didn't need to use ADB for anything, and I still ended up with root. So I guess I'm confused when you say you're going to use flashrec to boot into cyanogen recovery and then use adb shell to flash cyanogen recovery. I was under the impresion that flashrec FLASHES cyanogen recovery for you, eliminating the need to use ADB/Fastboot. Assumed "flashrec" stood for "Flash Recovery ROM".
My steps were:
1) Install/run flashrec
2) In FlashRec: Backup your current ROM
3) In FlashRec: Select a new recovery ROM to Flash (has Cyanogen's by default, can change to something on your SD Card)
4) In FlashRec: Flash the Recovery ROM
5) Exit FlashRec and reboot into Recovery Mode (Hold Home and Power)
6) You're done, you have a rooted phone. Go ahead and Nandroid a backup, wipe your data, and install a new ROM.

Thanks for your reply.
It is my understanding that flashrec does not flash the recovery rom, but just allows you to boot to it. (Similar to the fastboot boot filename.img command). I would guess that if you reboot your phone using home + power now, that it would boot to the standard recovery.
If it is the case that flashrec does flash the recovery image, then that would be handy, and presumably the backup could be restored using either nandroid or adb.
Thanks, this clarifies that my rooting procedure is along the right lines, however I am still concerned whether flashing everything back to normal will go as I expect.

Just booted into recovery, and its still CyanogenMod v1.4 + JF.
I'm trying to think if I did anything special during my rooting efforts. I don't think I did. I know that I flashrec'd twice. the First was with Amon_Ra's recovery console, and then I did it again a bit later with Cyanogen's. But I'm positive I was never able to successfully use adb's fastboot command due to my perfected SPL.
And you're right, I didn't address your concerns about unrooting at a later date. I assume that is what you're doing when you use flashrec to create a backup of the stock Recovery ROM, but i'm not positive.

Taken from:
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
EVERY TIME YOU REBOOT YOUR PHONE INTO NORMAL ANDROID IT UNDOES WHAT YOU JUST DID. Every time android boots, it reflashes the recovery partition with the default one from a file stored in your phone. For safety reasons, we are not replacing this file – just flashing the partition directly. So if you boot to recovery mode, then boot back into your normal mode, and then boot back into recovery mode – you will see a triangle with an exclamation point and only 3 options.
Click to expand...
Click to collapse
So I'm not sure what's going on.
Thanks for your input. I think I'm nearing enough confidence to go ahead and give this a try. Probably tomorrow.

Hi ParanoiaPersonified - can you post an update when you flash? I also have a new Voda Magic with the same SPL as yourself.....I got the OTA upgrade to Donut yesterday which I may have been silly about accepting.
I wasn't too impressed with the speed improvements in Donut and now want to flash something built by one of the XDA chefs, but am having problems rooting with the traditional methods - even 1 click doesn't seem to work....
Cheers.

It is my understanding that one-click-root only works on 1.5, and the exploit that it uses is patched in 1.6. I think you may need to use the 'gold card' method, radita.
I've realised that my handset has a fault (the scrollwheel does not work when scrolling to the right), so I will be unfortunately waiting for a replacement handset before taking any of the steps mentioned above.
Hopefully the replacement does come with 1.6 pre-installed!

"Gold card" method looks a little more involved....guess I don't have a choice though.
Thanks.

more fresh rom confusion

ok so i unrooted my phone to stock then used kitchen to auto root it and all worked great. then I put the recovery 1.5.3 i think it was on my root of sd card, and also had fresh 1.1 on it as update.zip
but everytime I apply it i get errors, now EVERYTHING works but I dont have service and settings force close.
should I wipe then install 1.1. or just upgrade from stock wen its rooted?
or maybe try 1.0 first with clean install or wipe?
thanks

If I were you, do this. RUU the phone to put it back to complete stock settings. Then, run the Auto-rooter in the Pre-Kitchen. This will put it to the latest recovery image. Then, just flash Fresh 1.1 to it, and then you'll be up to date.

you flash the recovery image dif then as if you were flashing a rom

wait so put recovery-RA-heroc-v1.5.2 on the root of card and change name to update and apply that, then delete that off root of card, put on fresh 1.1 rom and name it update then flash that?
can I do a clean install? or just update?

1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for).
2. Write down the filename of the recovery image EXACTLY as it is written (i.e. RA-Hero-Recovery-v1.2.2.img).
3. Put the recovery image file on the SD card (not in any folders).
4. Download Terminal from the Market if you don’t already have it and install it (there are a few different terminals in the Market ,
5. Open the Terminal program and type the following (with hitting enter at the end of each line):
su
flash_image recovery /sdcard/name-of-recovery.img
6. In the above text, replace name-of-recovery.img with the name of your recovery image (make sure the .img is on the end).
7. Phone should pause for a second and then show you a new blank line. Turn it off and back on by holding down Home and Power to ensure it flashed correctly. Done.
__________________

on another note you should change the title of this thread to user confusion has nothing to do with fresh rom ....might be confusing to some

As opposed to posting it in the FreshROM thread, had it really been a FreshROM issue.

702DROID said:
1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for).
2. Write down the filename of the recovery image EXACTLY as it is written (i.e. RA-Hero-Recovery-v1.2.2.img).
3. Put the recovery image file on the SD card (not in any folders).
4. Download Terminal from the Market if you don’t already have it and install it (there are a few different terminals in the Market ,
5. Open the Terminal program and type the following (with hitting enter at the end of each line):
su
flash_image recovery /sdcard/name-of-recovery.img
6. In the above text, replace name-of-recovery.img with the name of your recovery image (make sure the .img is on the end).
7. Phone should pause for a second and then show you a new blank line. Turn it off and back on by holding down Home and Power to ensure it flashed correctly. Done.
__________________
Click to expand...
Click to collapse
I know that you know that the auto rooter does all of that for you.
No renaming RA to update.zip or anything like that. RUU to get your phone back to stock. Then run the auto-rooter. This gives you a stock but rooted phone, with RA as your recovery image. You will then be able to install fresh rom. That's all!

edit/removed

flipzmode said:
I know that you know that the auto rooter does all of that for you.
No renaming RA to update.zip or anything like that. RUU to get your phone back to stock. Then run the auto-rooter. This gives you a stock but rooted phone, with RA as your recovery image. You will then be able to install fresh rom. That's all!
Click to expand...
Click to collapse
didnt want to confuse him anymore then he already is

ok did RUU and the kitchen and did auto rooter. running 1.5.2.
Just downloaded fresh 1.1
going to put it into the root of sdcard and rename the fresh rom to, "update"
then power down phone, power back on and ok should I wipe phone then apply update zip
or
not wipe and just apply zip?
then once I apply just then choose reboot and basically thats

You don't need to wipe. RUU puts your phone back to bone stock.
You shouldn't need to rename FreshROM to update either.

ohh, ok that was my biggest problem i think, im used to my g1 and i always renamed the rom to update.zip
so keep it fresh-cdma-hero-1.1
and apply update

unrEVOked 3.1...to full root

Hello all,
I was one of those people who used the unrEVOked root to simply obtain wireless tether. Now that I have it, I cant update to Froyo. Would anyone be able to suggest a method to obtain full root so I can just flash a Froyo ROM?
FYI, I dont have adb shell or android sdk installed. I was looking at toast's method however I am unsure, if that is the correct path to march in. I have no problem learning adb shell if necessary.
Thanks in advance and look forward to buying someone a beer.

you can try SimpleRoot 1 click (check your software version as there are two separate SimpleRoot threads, one for 1.47.651.1 and the other for the older version)

I had unrevoked as well. This is what you need to do:
Download simple root.
Click button 1 root, follow prompts. reboot.
click button 2 recovery, select ra recovery. reboot.
Download rom, radio, and wimax. Put all into SD card.
Boot into recovery. (power & vol down)
wipe data, cache, dalvik.
Select update from sd. choose select zip file (not update.zip)
select rom zip, install. reboot
Boot into recovery. (power & vol down)
install radio, then wimax(same way as rom). Pretty sure you should reboot each time. That's what I did atleast.
That's it. I updated my profile afterwards in system updates to make sure no problems w/ data occurred.

hhhmmm ill have to try that! thanks!

Can anyone else confirm this?
dlbevo

You can flash some ROMs, including netarchy's rooted stock ROMs, without a "full root". Even though Unrevoked is not a full root, the NAND is unlocked when you are in the ClockworkMod recovery.

[Q] Problems HTC MAgic 32b recovery mode

HTC Magic
SAPPHIRE PVT 32B
HBOOT-1-33.006
CPLD-10
RADIO-2.22.19.261
I have problems getting in to the recovery mode (pwr button + home) it just gives me de red vodafone screen and hangs.
I am trying to install a custom rom.
- rooted the device with universal androot. it says my device is rooted succesfully.
- i also installed rom manager and installed the default clockwork recovery.
But i cant reboot into flash recovery.
I also tried another thread with a custem flash recovery recovery-RA-sapphire-v1.7.0G.img. I followed it's instructions.
the instructions tells me on a terminal session or CMD prompt to install this custom ROM.
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
But i get no permission. I cant get root user when i type su.
so I must not have a rooted device or my permissions are incorrect on the sd-card.
Does anyone have an idea what i should do?

Did you reboot your phone after running Universal Androot?
Sent from my LG-P500 using Tapatalk

What happens if you switch off the phone and then press and hold home button while pressing the on/of button to switch on the phone.
If you are root and have installed the recovery properly, it should be shown within a few seconds after showing the red vodafon screen. From there you should be able to flash any custom rom. Meanwhile I flashed many recoveries and roms on both my tattoo and my magic 32b. Never had any problem execept those when forgetting to wipe.
And to be honest, I'm far away from beeing an expert!

I installed rom manager first and then universal androot.
also when i use adb from the android sdk i sometimes get the problem that i have no permission.
Could it be that the phone is'nt correctly rooted?
I tried all kinds of tools either on pc or mac. nithing really works
what would be the best way to root the HTC Magic correctly and what recovery image should i use. Also wich order.
I'm quite the noob when it comes to installing custom roms

Try "SuperOneClickv1.6.3-ShortFuse.zip" (available at xda).
This was very easy to use and worked like a charm.
I used it twice on my magic 32b, no problem!

I tried that also.
the rooting works. I tried an app to check if i have root access and it says I have root acces.
but when I use adb commands and su to root it will say no permission.
i think this is why installing the recovery in clockwork fails.
any suggestions?

I'll repeat myself. Have you rebooted the phone after running the root programs? Either one?

yes. I rebooted after each try but still I can't get into recovery mode. it just hangs.
also when i try to install a recovery image file i still get the no permissions errors.
the only recovery mode install that worked was the recovery from clockwork in ROM manager.

If ADB is working, goto shell (adb shell).
What do you see in prompt,
is it '$' or '#'?
If it's '$' try "su".
What is the output of "id"?
If you're root you should see something like "uid=0(root) gid=0(root)"

I See a $ and my id is shell instead of root.
if I type su it will give me a no permission error.
however I did download a terminal tool for android
from there I can su and it will make me root.
is there anyway i can use the terminal to install a recovery image so that if i boot my phone with home+power I will get into the recovery?

Try something like this:
http://forum.xda-developers.com/showpost.php?p=4056530&postcount=6
Replace the recovery image in the post by for example recovery-RA-sapphire-v1.7.0G.img.
I did it almost the same way.

I was also having a recovery problem (Tmobile) after trying to flash_image RA-1.7.0G into recovery in rooted 2.2.1 OTA (obviously not the way to go). I downloaded the Clockwork Rom Manager from the Market and it was able to flash both Clockwork or Amon RA recovery with no problem and then reboot it into recovery.

sickbox said:
I was also having a recovery problem (Tmobile) after trying to flash_image RA-1.7.0G into recovery in rooted 2.2.1 OTA (obviously not the way to go). I downloaded the Clockwork Rom Manager from the Market and it was able to flash both Clockwork or Amon RA recovery with no problem and then reboot it into recovery.
Click to expand...
Click to collapse
When you reboot and go into recovery, does it load amon_RA or clockworkmod?
I had problems with that from the 2.2.1 OTA.
I was rooted for a long time, and then had to try the t-mo 2.2.1 so I unrooted and ran that for a while after their ota update. It was sluggish and I didn't much like it so I thought I would try using z4root and superoneclick to root it and put setcpu and overclock it a bit to see if it improved. Z4root didn 't work and superoneclick appeared to work. If you went into terminal it would give you # and seem to be rooted. I could install and run set cpu and it would work. However no matter what recovery I tried to install, it would disappear and return to stock recovery upon reboot with the 2.2.1 OTA.
You could get rom manager to load, or seemingly so , clockworkmod recovery. You could also have rom manager load into clockworkmod from within rom manager. Buit as soon as you reboot, it goes back to the default stock recovery.
I eventually gave up with that and decided to reroot old school and rooted it manuallyl. I went back to the sappimg.nbh file, installing the old cyanogen 1.4 recovery, the 1.33.2005 SPL. I then put clockwork mod 2.5.0.7 recovery on and then the t-mo 2.22.23.02. I was running cm6.1 for a while and now Yoshi's ginger rom.
And so, after this wandering tale, lol, I am wondering if you had more success that I did with the 2.2.1 and getting a recovery to load.

cyberstoic said:
When you reboot and go into recovery, does it load amon_RA or clockworkmod?
I had problems with that from the 2.2.1 OTA.
I was rooted for a long time, and then had to try the t-mo 2.2.1 so I unrooted and ran that for a while after their ota update. It was sluggish and I didn't much like it so I thought I would try using z4root and superoneclick to root it and put setcpu and overclock it a bit to see if it improved. Z4root didn 't work and superoneclick appeared to work. If you went into terminal it would give you # and seem to be rooted. I could install and run set cpu and it would work. However no matter what recovery I tried to install, it would disappear and return to stock recovery upon reboot with the 2.2.1 OTA.
You could get rom manager to load, or seemingly so , clockworkmod recovery. You could also have rom manager load into clockworkmod from within rom manager. Buit as soon as you reboot, it goes back to the default stock recovery.
I eventually gave up with that and decided to reroot old school and rooted it manuallyl. I went back to the sappimg.nbh file, installing the old cyanogen 1.4 recovery, the 1.33.2005 SPL. I then put clockwork mod 2.5.0.7 recovery on and then the t-mo 2.22.23.02. I was running cm6.1 for a while and now Yoshi's ginger rom.
And so, after this wandering tale, lol, I am wondering if you had more success that I did with the 2.2.1 and getting a recovery to load.
Click to expand...
Click to collapse
You could have just got booted into recovery once, flashed the engineering SPL only (there's a ZIP you can flash from recovery to do this), which would only change the SPL, from recovery, then erase/reflash the recovery from fastboot, and finally change the SPL back.

DonJuan692006 said:
You could have just got booted into recovery once, flashed the engineering SPL only (there's a ZIP you can flash from recovery to do this), which would only change the SPL, from recovery, then erase/reflash the recovery from fastboot, and finally change the SPL back.
Click to expand...
Click to collapse
Thanks; that is very useful , and I didn't even think of that at the time. I think I was so frustrated that the recovery would not stay I just had a "I will make it work moment" and I knew what I was doing would work.
But thanks, I will definitely remember that if I have to do that again

Just here to help ;D
Sent from my LG-P500 using Tapatalk

Can't root after XTC Clip S-OFF

Hi, I was on hboot 1.01.0001 so I finally got S-OFFed today. I flashed Ruu 1.37 and now I am on hboot 0.80.0007 and S-OFF.
However, I can't root with Unrevoked (tried 3.21, 3.22 and 3.32 Windows and Ubuntu versions, where I could root the same ROM time ago).
I also can't flash a Clockworkmod recovery from the recovery I have now (stock one) for failed signature verification and I don't know what to do... Now i get Bakcup CID missing in Unrevoked too...
Please any help. It must be a little thing, but I don't know.
EDIT: I finally got it with a test version of Unrevoked. Posted in the 4th post of this thread.
Thanks

How to install recovery
antonio1475 said:
Hi, I was on hboot 1.01.0001 so I finally got S-OFFed today. I flashed Ruu 1.37 and now I am on hboot 0.80.0007 and S-OFF.
However, I can't root with Unrevoked (tried 3.21, 3.22 and 3.32 Windows and Ubuntu versions, where I could root the same ROM time ago).
I also can't flash a Clockworkmod recovery from the recovery I have now (stock one) for failed signature verification and I don't know what to do... Now i get Bakcup CID missing in Unrevoked too...
Please any help. It must be a little thing, but I don't know.
Thanks
Click to expand...
Click to collapse
Same here. Got S-OFF and superuser is working now. Unrevoked says Can't root is you firmware to new.
Rom Manager says it installs Clockwork recovery but recovery is not working??
Anyone?

eduardb said:
Same here. Got S-OFF and superuser is working now. Unrevoked says Can't root is you firmware to new.
Rom Manager says it installs Clockwork recovery but recovery is not working??
Anyone?
Click to expand...
Click to collapse
But are you still on hboot 1.01.0001? Because if Unrevoked says Can't root is you firmware to new that may be. Or have you flashed an older RUU?
How have you got superuser???

eduardb said:
Same here. Got S-OFF and superuser is working now. Unrevoked says Can't root is you firmware to new.
Rom Manager says it installs Clockwork recovery but recovery is not working??
Anyone?
Click to expand...
Click to collapse
Hey! If you are in hboot 0.80 (Flash 1.37 RUU), I finally found a test version of Unrevoked here that installed Clockworkmod recovery!!!
http://rootmydroid.co.uk/guides/howto-fix-the-backup-cid-missing-error-on-unrevoked/
Option 1--> downlod the file, is the Unrevoked test version. Run it, it works!!
I hope if it useful to somebody.

Do you guys even know what's the purpose of having S-OFF?!
If you phone's NAND is unlocked, just get temp root and flash the recovery

Kwen said:
Do you guys even know what's the purpose of having S-OFF?!
If you phone's NAND is unlocked, just get temp root and flash the recovery
Click to expand...
Click to collapse
Hey I am sorry! I did what I could. I tried Unrevoked and didn't work so I eventually got an Unrevoked version that did the trick.
Excuse me if I can't do another way without having the steps to follow.

I had the same problem first i set s-off, then flashed and older RUU, then unrevoked 3.14 and that worked for me......so good and easy and fast!

hans3103 said:
I had the same problem but i use unrevoked 3.14 to root the wildfire.....all without any problems I think newer is not always better for things like this.
Click to expand...
Click to collapse
Yeah, the test version I posted was 3.22. I ll note myself that 3.14 works for the next time. Thanks

strange...newer is not always better ........lol

If you get the error-message concerning the cid in Unrevoked - just adb into the phone, run the __unrevoked__ script in /system and flash the clockwork-mod after that. From there you can install rooted images like you want ..

sammy98 said:
If you get the error-message concerning the cid in Unrevoked - just adb into the phone, run the __unrevoked__ script in /system and flash the clockwork-mod after that. From there you can install rooted images like you want ..
Click to expand...
Click to collapse
Thank you! I will keep that in mind.

Just fix your .misc file, as descriped in this post ( http://forum.xda-developers.com/showthread.php?t=824396 ) - when done, then re-run unrevoked

Birthe88 said:
Just fix your .misc file, as descriped in this post ( http://forum.xda-developers.com/showthread.php?t=824396 ) - when done, then re-run unrevoked
Click to expand...
Click to collapse
I read a post about this file but I found it hard and risky. Decided to use a test version of Unrevoked as said before.
Thanks for the ost anyway. Will be useful.
Sent from my HTC Wildfire using XDA App

xtc clip s-off
I got the same error message but got rooted with and older version of unrevoked...then the problem was solved. Much more easy and more safe i guess . I dont know if this work for every one but for me it did.

Rooting after S-OFF
Hi guys,
I`ll share here my experience.
There are mainly two different methods (with some variations) of obtaining ROOT after S-OFF (with XTC Clip).
1-st (and likely undesirable to me) is exactly: downgrading > Unrevoked > upgrading.
- And why so?
There have some disadvantages:
- downgrading is additional flashing of the device and is unnecessary at all (you`ll see later).
- need of connection to computer.
2-nd (very desirable metnod) is to install CWM Recovery right away S-OFF. Even this procedure is not a must, but makes your life easier. Then You can flash right from SD card whichever ROM you like.
- And what advantage gives this to me?
- Only 1 flash procedure, no need of downgrades. Flashing with already rooted ROM (any custom or rooted stock) gives you ROOT access with only 1 step.
- There is no Unrevoked procedure, thats mean no need of computer connection at all.
The most painless and secure algorithm is:
1. S-OFF (by XTC Clip)
2. Install ClockWorkMod (CWM) Recovery - Here you`ll find recovery .img and .zip for all supported models.
How to install CWM Recovery?
As example I`ll give Wildfire aka Buzz:
- You`ll need to upload PC49IMG.zip (last CWM 3.0.0.6) on top of your sdcard ( NOT in any folder).
- Boot the smart in bootloader (holding VOLUME DOWN then POWER). You will be asked to install the ZIP file (Yes is right answer). Recovery will then install automatic, DO NOT press any buttons before finishing of process.
3. Backup/Restore Your current ROM:
- Starting Recovery: in bootloader navigate (with VOLUM DOWN) to "recovery", then POWER to enter in CWM Recovery menu.
- Navigation: TRACKPAD or VOLUME button to navigate trough menus, to select them press TRACKPAD button. Use BACK touch button to back in menus.
- Backup: you`ll find "Backup" menu under "backup and restore" main menu - When pressing "Backup" then CWM will perform backup of current state of the device. If succeed you'll see "Backup complete" message.
- Restore: you`ll see this menu as "Restore" right under "Backup". The menu gives you a list of available backups to restore. There have to be at least 1 backup to perform restore operation.
4. Wipe ONLY cache/dalvik when performing next step (5.) (if you want to save all data and settings, else do data/factory reset also which is recommended before flashing any custom ROM):
- just "wipe cache partition" in main menu and under "advanced" perform "Wipe Dalvik Cache".
- "wipe data/factory reset" - perform this action, ONLY if want to flash custom ROMs. This action will RESET smart to its factory settings (you`ll lose all data and settings except those saved on sdcard).
5.(optional) Install su binary with Superuser rootpack:
- download Eclair-Froyo-Gingerbread rootpack
- place the file as is on sdcard or in some folder on sdcard (there is no need to be on top of sdcard)
- boot in recovery and go to "install zip from sdcard" menu, then "choose zip from sdcard" submenu - here you can browse through sdcard folders and install su-2.3.6.1-ef-signed.zip (or your ROM or any update, e.g. radio, kernel etc.).
6.(optional) Make backup of Rooted ROM - see (3. : Backup)
7.(optional) Install some backup application like Titanium Backup (or PRO) or MyBackupRoot (or PRO) - this is optional but recommended. When backing up your Applications+Data you can restore them even after flashing custom ROM (which is performed after data/factory reset, and all applications and data will be wiped).
8. Install any custom or stock ROM:
- for stock ROM see 5.
- for custom ROM perform 4. (including "wipe data/factory reset"), then 5.
9.(optional) Restore Your applications and data - when Custom ROM is installed there is need to perform data/factory reset. Any backup of applications and data performed in step (7.) could be restored in freshly flashed Custom ROM.
NOTE: Later on I`ll add some additional stuff here - useful links and more deep explanation of mentioned algorithm if needed.
Happy Rooting!
XTC Clip in Bulgaria

dailor said:
Hi guys,
I`ll share here my experience.
There are mainly two different methods (with some variations) of obtaining ROOT after S-OFF (with XTC Clip).
1-st (and likely undesirable to me) is exactly: downgrading > Unrevoked > upgrading.
- And why so?
There have some disadvantages:
- downgrading is additional flashing of the device and is unnecessary at all (you`ll see later).
- need of connection to computer.
2-nd (very desirable metnod) is to install CWM Recovery right away S-OFF. Even this procedure is not a must, but makes your life easier. Then You can flash right from SD card whichever ROM you like, and that includes Stock Rooted ROM.
- And what advantage gives this to me?
- Only 1 flash procedure, no need of downgrades. Flashing with already rooted ROM (any custom or rooted stock) gives you ROOT access with only 1 step.
- There is no Unrevoked procedure, thats mean no need of computer connection at all.
When flashing with rooted Stock ROM, there is no need of data/factory reset procedure (wipe only caches - cache partition and dalvik). That`s mean exactly after flashing You will be Booted & Rooted with all settings and data saved.
The most painless and secure algorithm is:
1. S-OFF (by XTC Clip)
2. Install ClockWorkMod (CWM) Recovery
3. Backup Your current ROM
4. Wipe cache/dalvik ONLY when performing next step (5.) (if you want to save all data and settings, else do data/factory reset also which is recommended before flashing any custom ROM).
5.(optional) Install Stock Rooted ROM
6.(optional) Make backup of Rooted ROM
7.(optional) Install some backup application like Titanium Backup or MyBackup (PRO)
8. Install any custom or stock ROM.
9.(optional) Recover Your applications and data - when Custom ROM is installed there is need to perform data/factory reset. Any backup of applications and data performed in step (7.) could be restored in freshly flashed Custom ROM.
NOTE: Later on I`ll add some additional stuff here - useful links and more deep explanation of mentioned algorithm if needed.
Happy Rooting!
Click to expand...
Click to collapse
Great explanation! It will sure be useful for someone

Ok.. how do I install clockwork after getting s-off with xtc clip??

pyroblazer said:
Ok.. how do I install clockwork after getting s-off with xtc clip??
Click to expand...
Click to collapse
Check the 4th post of this thread http://forum.xda-developers.com/showpost.php?p=12093356&postcount=4
easy

antonio1475 said:
Check the 4th post of this thread http://forum.xda-developers.com/showpost.php?p=12093356&postcount=4
easy
Click to expand...
Click to collapse
thnx....mate... gonna get s-off on monday... that is if i can afford it rightnow..

pyroblazer said:
thnx....mate... gonna get s-off on monday... that is if i can afford it rightnow..
Click to expand...
Click to collapse
But someone is going to make it to you for some $ or you bought the XTC Clip?
Because for the price of XTC Clip, you can get a new phone...