Database Info

Help for S-Off XTC Clip User

Hi,
As you can see from my signature, I'm still using all the firmware which originally came with my phone back in June.
As I needed root for a particular application, I got S-off through the XTC Clip method. For various reasons, I would like the latest (rooted) official ROM. Having read through the guides, I think to get up-to-date I need to do the following:
1. Get a custom recovery (ext4 seems the most popular);
2. Do a backup using the custom recovery;
3. Follow the instructions in this thread to get the latest hboot and radio: http://forum.xda-developers.com/showthread.php?t=1240266
4. Backup key data to be restored using Titanium backup;
5. Do backup again using custom recovery;
6. Install ROM from developers site following instructions. I should use either of the following to get the latest official Rom:
http://forum.xda-developers.com/showthread.php?t=1230029
http://forum.xda-developers.com/showthread.php?t=1287797
Is the above roughly the right process to follow? Not totally sure what I am doing but hopefully I am on the right lines.
Many thanks,
Damian

damian35 said:
Hi,
As you can see from my signature, I'm still using all the firmware which originally came with my phone back in June.
As I needed root for a particular application, I got S-off through the XTC Clip method. For various reasons, I would like the latest (rooted) official ROM. Having read through the guides, I think to get up-to-date I need to do the following:
1. Get a custom recovery (ext4 seems the most popular);
2. Do a backup using the custom recovery;
3. Follow the instructions in this thread to get the latest hboot and radio: http://forum.xda-developers.com/showthread.php?t=1240266
4. Backup key data to be restored using Titanium backup;
5. Do backup again using custom recovery;
6. Install ROM from developers site following instructions. I should use either of the following to get the latest official Rom:
http://forum.xda-developers.com/showthread.php?t=1230029
http://forum.xda-developers.com/showthread.php?t=1287797
Is the above roughly the right process to follow? Not totally sure what I am doing but hopefully I am on the right lines.
Many thanks,
Damian
Click to expand...
Click to collapse
Looks good I just would do this:
Backup key data to be restored using Titanium backup;
as first step not at fourth.
And would insert a factory reset (wipe /data, /cache and /dalvik cache)
before 6 and a wipe of /cache and/dalvik cache before step 1 and 3.
The wipes are not really necessary, but to stay on the safe side I would recommend it.
Swyped from my Desire S

Hi,
Thanks for the quick response - I think I am getting somewhere here.
A couple of other points:
Is 4ext recovery the best custom recovery? I'm guessing a custom recovery is essential.
The link to the hboot for xtc-clip contains an old radio, so I will need to include another step to further update the radio.
when I download the hboot for xtc-clip file, do I need to do something to validate that the file is complete (this md5 thing)? Is it easy to validate.
Going to give the above ago this evening, so hopefully it will go ok!!
Thanks again,
Damian

damian35 said:
Hi,
Thanks for the quick response - I think I am getting somewhere here.
A couple of other points:
Is 4ext recovery the best custom recovery? I'm guessing a custom recovery is essential.
The link to the hboot for xtc-clip contains an old radio, so I will need to include another step to further update the radio.
when I download the hboot for xtc-clip file, do I need to do something to validate that the file is complete (this md5 thing)? Is it easy to validate.
Going to give the above ago this evening, so hopefully it will go ok!!
Thanks again,
Damian
Click to expand...
Click to collapse
1) As much as I know it's the best for our device, it's based on cwm and adds a few helpful features to it
2) You could put the radio inside my signature, it's not the latest, but it's up to date and within the latest there is a report about bigger battery consumption with wifi
The steps to get it working are described within the thread where you get it from, anyway the procedure is more or less similar to the one for hboot
3) Would be a good idea, but cause there is no md5 sum to compare with it doesn't make much sense, but you could ask if someone can post it, and then generate the md5 of yours within Linux (I don't know if you're an windows our Linux user) or within the adb shell and compare it
Here is an md5 howto:
http://linux.byexamples.com/archives/198/md5-checksum-how-to/
(only the first step is needed by you, just compare the output with the posted md5sum)
To get adb working just take a look at the guide for newcomers
Swyped from my Desire S

[Q] stock rom with s-off ? what i need to do?

hello and sorry for the same questions asked over the same issue...
its my first time and im afraid to brick my phone
anyway now im with custom rom and want to go back to stock to receive ota updates.
my phone is rooted and s-off i want to stay s-off with stock rom.
1. is it possible ?
2. will i need to wipe data before the flash?
3. backup needed ?
4. will i get ota updates with stock rom s-off?
5. the ruu is europe 1.47 do i need it to match to my software/radio/hboot?
my phone:
SAGA PVT SHIP S-off RL
HBOOT -0.98.0002
RADIO-3805.06.02.03_M
EMMC-boot

@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.

foX2delta said:
@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.
Click to expand...
Click to collapse
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped

thanks
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!

yonigo870 said:
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!
Click to expand...
Click to collapse
here is a few guides to help with that question i don't know anything about rom manager sorry i use 4ext touch recovery
Custom ROMS:
Custom roms can be found in this thread: http://forum.xda-developers.com/show....php?t=1146601 or head to the development section.
(Most of these ROMs are pre-rooted, which means that you don't need to root your phone after flashing one of the custom ROM.)
How To: Flash Custom ROMs using Recovery (Method 1)
(You can use your default recovery from Revolutionary tool but I recommend using 4EXTRecovery)
1. Copy your custom ROM "zip" file to your SD card (Root directory).
2. Turn off your phone.
3. Turn on your phone by holding the power button and the volume down button together.
4. Once you see the white screen, choose "Recovery"
5. Make a full wipe/format and clear all cache.
6. Choose "install from sdcard/zip file" and then choose your Custom ROM zip file from your SD card to flash your Custom ROM.
Optional: If you want to use 4EXTRecovery, just flash it like you are flashing your custom ROM(Step 6). Just do it before you flash your new ROM.
How To: Flash Custom ROMs using ROM Manager (Method 2)
(This method might be easier for flashing ROM updates or add-ons)
1. Go to ROM Manager (You can install this software from the Android Market.)
2. If you want to use 4EXTRecovery, please follow steps below, and if you're not using 4EXTRecovery, please skip to step 6)
3. Press your phone's option's button and choose Manual Flash Override.
4. Press OK and choose your phone model.
5. Choose ClockworkMod 3.x (After these steps, your ROM Manager won't ask you to flash new recovery again when flashing new a ROM)
6. Reboot into Recovery and make a full wipe/format and clear all cache then reboot.
7. Now, from your ROM Manager, choose Install ROM from SD Card.
Note: Flashing ROMs can be vary, some custom ROMs may require you to flash some of their own file first. Eg, The LBC Mod ROM requires you to flash "WIPE zip file" before flashing the ROM. Read their instructions carefully to know more.
NOTE: I am not responsible for any faulty or bricked devices after S-OFF or flashing new ROMs. Do it at your own risk.
How To: Flash a ROM in a "Perfect" Way (Method 3 - Recommended)
A great guide from vampire36 for people who encounter the following problems:
1. The ROM you flashed gets stuck on HTC screen (bootloop) while the same ROM works right for others
2. You get the same kernel and radio yet you find your cell to have more battery drain than others
3. Finally some strange force closes and restarts but works perfect for others
So this is basically one of the most perfect way to flash a custom ROM and is a way to help people who face such issues.
Please head to : http://forum.xda-developers.com/show....php?t=1257731 to see full instructions and discussions.

Blush91 said:
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped
Click to expand...
Click to collapse
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root afterwards and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!

Saipro said:
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!
Click to expand...
Click to collapse
yes i've flashed many roms also and have never encountered a boot-loop the only time i got a boot-loop was when i flashed the wrong RUU in the past 48 hours i've changed roms about 20 times

flashing pre rooted stock rom
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager

yonigo870 said:
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager
Click to expand...
Click to collapse
Loooool don't worry that's what's xda is for were all here to help
Sent from my HTC Desire S using XDA

no wifi
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
the phone updates himself ??? i see it updates programs from the market without me doing anything
* do i need to reboot the phone after flashing rom ??? and how ?

yonigo870 said:
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
Click to expand...
Click to collapse
I don't know much about titanium I use app extractor try this ROM http://db.tt/Wnl7ZrKa
App extractor restores your apps contacts wifi settings SMS from your nandroid(backup)
Sent from my HTC Desire S using XDA

many thanks for the help !!!!
do i need to reboot after flashing ?

Yeah reboot I hope you made a full wipe before flashing sorry should have told you earlier
Sent from my HTC Desire S using XDA

yeah i did full wipe
after flashing rom the phone made updates from the market by himself, and now im restoring via titanium and seems like everything is ok...
after that titanium asked me to reboot, and so i did.
again thanks a lot for the support and for the help !!!!!!!!

problem !!! the rosie utility stopped unexpectedly...
htc widgets (like clock and weather) not working after restoring with titanium!
maybe its since the backup was on sense 2.1 and now its 3.0
how can make the htc widgets work ???

reboot back into recovery and fix permissions i dont know if you can do that in titanium

solved !!!
all was needed is to clear data from the htc sense

Virtuous ROM: SuperCID and Firmware upgrade NOT needed?

The thread [GUIDE] A must read for those noobs who want to enjoy ICS states that ALL ICS roms need a firmware upgrade.
However, the installation instructions for the Virtuous ROM doesn't say anything at all about upgrading the firmware: http://www.virtuousrom.com/p/documentation.html
Which one is right?
Also, just to be on the safe side, is SuperCID needed?

The documentation page you linked is installation instructions for all Virtuous ROMs, so it's pretty generic. If you look at the description page for Virtuous Inquisition, which is ICS-based, the page does mention firmware. That ROM is based on the most recent 3.32 firmware, which is probably what you want to use. AFAIK, all ICS ROMs require firmware version of 3.12 or greater.
As for SuperCID, I think there are firmware downloads on the forums now that don't require it but it's also pretty easy to do.

pyrilium said:
The documentation page you linked is installation instructions for all Virtuous ROMs
Click to expand...
Click to collapse
Ahhh. Ok. That was the missing link. Thanks.
I have a rooted S-OFF Sensation 4G with the stock ROM and ClockWork. So all I need to do is:
Flash the Firmware that doesn't require SuperCID
Nandroid Backup / Wipe
And then I can flash Virtuous.
Is that correct?
Also, does flashing Firmware alone cause a wipe?

That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.

pyrilium said:
That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.
Click to expand...
Click to collapse
Wow, this is extremely helpful, thank you. One other thing: does it matter what version of ClockWork I'm using? (I rooted/did S-Off a loooooong time ago.)

Glad I can help!
I don't know whether the version of CWM matters. I doubt it would, other than maybe making a nandroid backup in a format other than current, but it's not that hard to update the recovery either.
I actually started using 4ext recovery recently, and I like it a fair bit better than CWM. It's something like $2.00 on the market, but includes a userspace application that lets you do things like set up a series of recovery operations (i.e. make backup, wipe, flash a set of zips) and then reboot into recovery to run them.

Perfect, thanks. I'll give this a shot.
Every few weeks I look up how to move to ICS but then lose my enthusiasm once I see all the things I'd have to do to switch haha. But today I noticed that Virtuous doesn't need some of those steps

One more question: SuperWIPE is unnecessary for Virtuous Inquisition correct? I see that it is necessary for Android Revolution, but I just wanted to make sure.

I've always seen superwipe recommended as part of the upgrade process from GB to ICS. It might not be required for Virtuous, but I don't see why you'd want to avoid it. The flashing process *will* wipe your phone - you want to use something like Titanium Backup to backup/restore app states if that's a problem - and performing the superwipe takes almost no time.

Woohoo! Successfully upgraded from stock Gingerbread (rooted & S-Off) to Virtuous Inquisition ICS! I wrote down what I did, so if anyone is interested, below is how I did it. It took about 15 minutes in total (not including the backups). Hopefully it helps someone else out there!
Titanium Backup all apps
Nandroid Backup via ClockWork Recovery (1434 MB)
Get CID Version:
Download ADB/Fastboot files from attachment from Post #1 of the [Firmware][Mar 12] thread
Connect phone to PC -> adb reboot bootloader -> Then in bootloader:
fastboot getvar cid: T-MOB010
fastboot getvar mid: PG5810000
fastboot reboot
Download the appropriate Firmware from above thread (CTRL+F for T-MOB010/PG5810000) and the Virtuous ROM from Virtous Website
Copy both files to sdcard, check md5 on both
Flash Firmware:
Turn phone off -> Hold Volume-Down + Power to enter bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once completed successfully and asks you to reboot, pull the battery out. (Gingerbread & firmware are incompatible, causes bootloops)
With phone off and plugged into PC, do adb reboot recovery (Thanks pyrilium!)
Mount USB storage
Use PC to delete firmware file from sdcard
Wipe all data and cache -> Flash Virtuous -> Reboot
(Note that YES, flashing firmware causes bootloops -- as I found out! So firmware and ROM must both be flashed together.)
And thanks pyrilium for the note about using "adb reboot recovery" while the phone is off! I would have never figured that you could issue adb commands with your phone off. That tip isn't even in any of the guides, so thanks for that! Extremely helpful.
Anyway, hope that helps others out there. And thanks for helping me!

[Q] Uber noob stuck and scared

So I've been reading these forums for days on end now before I touch my phone again. Is my order of things to do correct? (HTC One XL (AT&T))
1. Root
2. Supercid
3. Unlock bootloader
---Currently here---
4. Install CWM/make a backup
5. Relock bootloader
6. Flash a RUU (1.88?)
7. Unlock bootloader
8. Flash a rom
9. Enjoy
As shown above, I rooted, have su on my screen and I can get into the bootloader by vol down+power. I had a scare trying to install RUU 1.85 but I think it failed because my bootloader is unlocked?
Basically everything I do on my phone scares me now. I opened my bootloader today so I can see what stock recovery looked like. I got some weird icons that scared me. I cannot stay where I am because I cannot get OTA updates, and I cannot flash updates myself. HELP!
Thanks, people on this forum are awesome, but you all know too much to be able to write a proper noobs guide.

Valitri said:
So I've been reading these forums for days on end now before I touch my phone again. Is my order of things to do correct? (HTC One XL (AT&T))
1. Root
2. Supercid
3. Unlock bootloader
---Currently here---
4. Install CWM/make a backup
5. Relock bootloader
6. Flash a RUU (1.88?)
7. Unlock bootloader
8. Flash a rom
9. Enjoy
As shown above, I rooted, have su on my screen and I can get into the bootloader by vol down+power. I had a scare trying to install RUU 1.85 but I think it failed because my bootloader is unlocked?
Basically everything I do on my phone scares me now. I opened my bootloader today so I can see what stock recovery looked like. I got some weird icons that scared me. I cannot stay where I am because I cannot get OTA updates, and I cannot flash updates myself. HELP!
Thanks, people on this forum are awesome, but you all know too much to be able to write a proper noobs guide.
Click to expand...
Click to collapse
Those steps are correct EXCEPT for 5, 6 and 7. You don't need those if you're flashing a custom rom, only if you're staying official and using an RUU. We can flash insecure boot.img files now which allow us to jump around firmware versions without blowing up. Just make sure you do a factory reset from recovery before flashing a new custom rom to prevent any weird bugs (you can use Titanium Backup to backup all your apps). Also, I would personally recommend flashing TWRP over CWM. It's a little more friendly in terms of UI and has a bit more functionality baked in.
Edit: And just FYI, the RUU did fail because your bootloader was unlocked. And now you know.

Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.

stnguyen09 said:
Those steps are correct EXCEPT for 5, 6 and 7. You don't need those if you're flashing a custom rom, only if you're staying official and using an RUU. We can flash insecure boot.img files now which allow us to jump around firmware versions without blowing up. Just make sure you do a factory reset from recovery before flashing a new custom rom to prevent any weird bugs (you can use Titanium Backup to backup all your apps). Also, I would personally recommend flashing TWRP over CWM. It's a little more friendly in terms of UI and has a bit more functionality baked in.
Edit: And just FYI, the RUU did fail because your bootloader was unlocked. And now you know.
Click to expand...
Click to collapse
Thanks for confirming why the RUU failed. I was scared because it never said it failed or errored. I let it run for 90+ minutes and finally did a hard reset on my phone.
I downloaded Titanium but I don't understand where the backups go. How to save them or how to use them for recovery. I also don't understand how people talk about this phone having an SD card when it doesn't.
I saw TWRP and it looked like the better option but I thought a lot of the roms needed CWM to flash from. I guess I really don't fully understand how to flash a rom then.
This is so weird because I jailbroke my iPhone 3g, and tried multiple roms on my cousins Droid X a long time ago.
Easy question. If you stick with roms, any reason to ever relock the bootloader?
Thanks

Lilshaun said:
Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.
Click to expand...
Click to collapse
I'm on 1.73
As the previous poster said, if I want custom roms I shouldn't even bother with the RUU? Is the RUU just a way to get the most updated factory settings because of root? Also do RUUs cancel root?

Valitri said:
Thanks for confirming why the RUU failed. I was scared because it never said it failed or errored. I let it run for 90+ minutes and finally did a hard reset on my phone.
I downloaded Titanium but I don't understand where the backups go. How to save them or how to use them for recovery. I also don't understand how people talk about this phone having an SD card when it doesn't.
I saw TWRP and it looked like the better option but I thought a lot of the roms needed CWM to flash from. I guess I really don't fully understand how to flash a rom then.
This is so weird because I jailbroke my iPhone 3g, and tried multiple roms on my cousins Droid X a long time ago.
Easy question. If you stick with roms, any reason to ever relock the bootloader?
Thanks
Click to expand...
Click to collapse
1. You never need to relock the bl unless you're RUU'ing
2. TWRP and CWM do the same thing, what you can do with one you can pretty much assume you can do with the other
3. Titanium Backup (I refer to it as TiBu) stores the backup files on your phone in a Titanium Backup folder on your sd card. You use the TiBu app itself to batch restore your apps. So this mean you're gonna have to redownload it manually from the Play Store after a factory wipe. You also have the option or restoring your apps with data and also restoring system data. In my experience, restoring system data is always a bad idea and will cause weird behavior. Restoring app data also sometimes has weird consequences, depending on the app, so I usually just restore my apps without data and individually restore data to apps I know will have no issue and are a pain to set up again.
4. We refer to it as an sd card because it technically still is one, just soldered onto the board.
5. Yes, RUU will get rid of root. It returns your phone to its factory state (except it doesn't touch your user data)
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
Lilshaun said:
Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.
Click to expand...
Click to collapse
Upgrading to 1.85 isn't necessary since we can flash boot.img and jump between versions

Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.

Valitri said:
Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.
Click to expand...
Click to collapse
You can have TiBu sync to a Dropbox, Google Drive, or Box account too. The scheduling feature is real nice. I have mine running the 2 default scheduled backup tasks every morning at 6am and then automatically uploading to Google Drive provided that I am plugged in and on WiFi.
I have it run every morning just in case I do something stupid during the day.
Oh and make sure to watch your internal storage space. CWM/TWRP backups take up A LOT of space, around 1GB (that's off the top of my head, I know it's around there somewhere). Manage your backups carefully, deleting ones you don't need.

you dont need to bootloader unlock before you upgrade to 1.85. just get the unlock code and then, with a locked bootloader, update RUU to 1.85. then afterwards unlock bootloader with unlock code.bin.

Valitri said:
Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.
Click to expand...
Click to collapse
Titanium is just for backing up apps not the entire phone. Sorry if you knew that, it just sounded like you didn't.
You need to flash TWRP and do a backup with it. This will backup your entire phone. In case you ever run into issues you know that you have a backup of your phone from when it was fully functional. This stays on your phone and if you ever need to restore it you do so from within TWRP.

pside15 said:
Titanium is just for backing up apps not the entire phone. Sorry if you knew that, it just sounded like you didn't.
You need to flash TWRP and do a backup with it. This will backup your entire phone. In case you ever run into issues you know that you have a backup of your phone from when it was fully functional. This stays on your phone and if you ever need to restore it you do so from within TWRP.
Click to expand...
Click to collapse
Right, think of a TWRP/CWM backup as the equivalent of a Windows System Restore Point or a Mac Time Machine Backup. It's pretty much a snapshot of your system that you can jump back to in order to revert anything you did that screwed things up.

[Q] 1.85 rooted to scottsrom JB rooted

Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...

Megadave123 said:
Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...
Click to expand...
Click to collapse
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything except sd card. Wipe cache,dalvik, system, factory reset.
Flash Rom.
If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app

31ken31 said:
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything but sd card, cache,dalvik, system, factory reset.
Flash Rom. If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Regarding unlocking - can I do it with supercid set, or do I need to change to all 2's ?
Should I do s-off?
I'm on whatever versions of everything are stock for a device shipped with 1.85 - ok, the bootloader screen says hboot is 1.09.0000
I'll search around but are there docs on the specific steps for flashing roms?
BTW, thanks for the quick reply...

Hit install from recovery pick Rom and flash.. don't worry about s-off being on hboot 1.09 u can flash whatever from recovery. Htcdev has 1111111 blocked I think if it is use all 2's
Sent from my HTC One X using xda app-developers app

FWIW supercid seemed to work for unlock just fine...

31ken31 said:
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Click to expand...
Click to collapse
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..

Megadave123 said:
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..
Click to expand...
Click to collapse
It's says bugs fixed but it's not fixed.. I don't recommend cwm for this device. Go to twrp website and download 2.3.3.1 and flash it
Sent from my HTC One X using xda app-developers app