Database Info

[Q] Switch from 4EXT to CWM ? / Flashing boot.img ? (CM10-alpha)

Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU

1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img

Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.

FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM

For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card

pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S

amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !

FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.

Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.

c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.

[Q] don't know where to start

hi guys, as the title says...
a client booked in a HTC Sensation that's stuck on the start up screen. as far as i can tell, they've tried to load some or other software to it.
i don't know if it's been rooted or anything like that, but i'd like to restore to to it's previos state. if you could be of assistance, it would be greatly appreciated
i've added a few pics to show exactly what i'm dealing with here

First way: wipe data (factory reset), wipe cache, advanced - wipe dalvik cache
then reboot. This start up may take 5-10 minutes. if not loading again:
Second way - flashing any rom, but I doubt how - because the phone is s-on and there is cwm not 4ext recovery on it. So maybe try wire trick to get s-off: http://unlimited.io/juopunutbear.htm

Can you get the CID and flash a compatible RUU?

this is what you need
http://forum.xda-developers.com/showthread.php?t=1631861
in a few steps:
flash 4ext recovery(step 2)
put the rom in the root of sdcard
enable smartflash from recovery
flash the rom
done and enjoy

olegat0r said:
First way: wipe data (factory reset), wipe cache, advanced - wipe dalvik cache
then reboot. This start up may take 5-10 minutes. if not loading again:
Second way - flashing any rom, but I doubt how - because the phone is s-on and there is cwm not 4ext recovery on it. So maybe try wire trick to get s-off: http://unlimited.io/juopunutbear.htm
Click to expand...
Click to collapse
did this, everything's still the same

rzr86 said:
this is what you need
http://forum.xda-developers.com/showthread.php?t=1631861
in a few steps:
flash 4ext recovery(step 2)
put the rom in the root of sdcard
enable smartflash from recovery
flash the rom
done and enjoy
Click to expand...
Click to collapse
going to give this a squizz now, wish me luck...

Thanks a lot guys, the phone is working again, minor touch screen issues, but hey, it's dialing out and everything!

[Q] Questions regarding liquidsmooth

Hi all,
Over the past few days I have been using this splendid ROM, however something went wrong during the flashing of the ROM or I missed something, because all of my apps keep crashing and my stock browser app crashes everytime I use it. And I also get random reboots. I think it's the boot.img, but i'm tired of trying
I installed this rom in the Following order:
1. Wipe cache
2. Factory reset
3. Wipe dalvik cache
4. Flash the ROM
5. Rebooted into fastboot
6. Fasboot flash boot boot.img
And I also tried it in this order:
1. Fasboot flash boot boot.img
2. Wipe cache
3. Factory reset
4. Wipe dalvik cache
5. Flash the ROM
6. Reboot
What am I doing wrong here?
----------------------------------------------------------------
Adding some extra info just incase:
I came from stock sense 4.1+ android 4.1.1
Current device info:
UNLOCKED
S-ON
Hboot version 2.15.0000
Radio 1.11.50.05.28
I also tried redownloading the zip, but got the same result
At last i'm wondering if there are any specific kernels available for this ROM, and which 1 you guys recommend.
Thanks in advance!

In TWRP you want to factory reset then wipe system and then flash the rom and see if that works for you.

Darknites said:
In TWRP you want to factory reset then wipe system and then flash the rom and see if that works for you.
Click to expand...
Click to collapse
Ok ty, will try and see if that will sort it all out

Sadly, same story... :crying::crying::crying::crying: Is installation of the rom supposed to happen in 30 seconds?

Boyyoka said:
Sadly, same story... :crying::crying::crying::crying: Is installation of the rom supposed to happen in 30 seconds?
Click to expand...
Click to collapse
Em not sure but sounds a bit to quick. Get yourself 2.3.3.0 of TWRP and try with that and if its still being quick then do the wipes like I said but reboot but back into the recovery then flash the rom.

nevermind cheered too early... Seriously something is corrupting my phone

Maybe you have a bad download, try redownloading and flash.

[Q] How to root HTC one mini (At&T)?

Can someone help me root my HTC one mini at&t version, it's up to date on the latest firmwire 4.4.2. I tried rooting it before using this tutorial right here htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux
Got as far as installing custom recovery but when I install SuperUser it shuts off constantly, so I had to revert it back. The bootloader shows Unlocked "tampered" and S-On. So could anyone help? I'm using cricket on this phone and hoping to root it so I can switch roms (thinking that'll solve the MMS problem)

AzrielAx said:
Can someone help me root my HTC one mini at&t version, it's up to date on the latest firmwire 4.4.2. I tried rooting it before using this tutorial right here htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux
Got as far as installing custom recovery but when I install SuperUser it shuts off constantly, so I had to revert it back. The bootloader shows Unlocked "tampered" and S-On. So could anyone help? I'm using cricket on this phone and hoping to root it so I can switch roms (thinking that'll solve the MMS problem)
Click to expand...
Click to collapse
You don't need to root it to install a custom ROM. YOU only need to unlock it (through HTC Dev) and install a custom recovery (TWRP). If you reboot to bootloader and post the hboot version you're on, I can point you to the correct files.

jollywhitefoot said:
You don't need to root it to install a custom ROM. YOU only need to unlock it (through HTC Dev) and install a custom recovery (TWRP). If you reboot to bootloader and post the hboot version you're on, I can point you to the correct files.
Click to expand...
Click to collapse
M4_UL PVT Ship S-ON RL
The Hboot version is 2.22.0000
Shows Tampered in black and unlocked in pink
I have team win recovery Project v2.7.1.1 installed just when I tried installing SuperUser on it it kept turning off so I had to restore it from a backup before I installed Superuser

AzrielAx said:
M4_UL PVT Ship S-ON RL
The Hboot version is 2.22.0000
Shows Tampered in black and unlocked in pink
I have team win recovery Project v2.7.1.1 installed just when I tried installing SuperUser on it it kept turning off so I had to restore it from a backup before I installed Superuser
Click to expand...
Click to collapse
So do you want to root your existing ROM or flash a custom one? Most custom ROM's come rooted already.
The best custom sense ROM is Insert Coin. (IMO) You can download it from the Android Development section.
Before you flash:
1) Download Insert Coin rom and copy it to your device
2) Make a backup in twrp and test it (it sounds like you already have a good backup)
3) copy the backup folder to your computer just in case you wipe out your SDCard...in fact, I'd backup everything you don't want to lose, including the backup. Nothing you do should wipe your sdcard, but better safe than sorry.
To flash:
1) Boot to recovery (TWRP)
2) Go to Wipe
3) Go to Advanced Wipe
4) Wipe the following: Davlik Cache, System, Cache & Data (DO NOT WIPE INTERNAL STORAGE-this is your sdcard)
5) Back out the the TWRP homescreen
6) Go to Install
7) Find the Insert Coin rom, select it, and swipe to start the install
8) Follow the onscreen menus for install options (since you already wiped everything, you can select the option to NOT wipe prior to install)
Notes on Insert Coin - if you use handsfree bluetooth calling, you need to download one of the 4.4.2 versions of the ROM (3.0.7 or 3.0.8). I usually use 3.0.7, personally. 3.0.8 had some issues with paid apps not installing properly and 3.0.7 is pretty much bugfree imo. If handsfree bluetooth isn't important, then the latest 4.x.x version will be fine.
I hope this helps you.

jollywhitefoot said:
So do you want to root your existing ROM or flash a custom one? Most custom ROM's come rooted already.
The best custom sense ROM is Insert Coin. (IMO) You can download it from the Android Development section.
Before you flash:
1) Download Insert Coin rom and copy it to your device
2) Make a backup in twrp and test it (it sounds like you already have a good backup)
3) copy the backup folder to your computer just in case you wipe out your SDCard...in fact, I'd backup everything you don't want to lose, including the backup. Nothing you do should wipe your sdcard, but better safe than sorry.
To flash:
1) Boot to recovery (TWRP)
2) Go to Wipe
3) Go to Advanced Wipe
4) Wipe the following: Davlik Cache, System, Cache & Data (DO NOT WIPE INTERNAL STORAGE-this is your sdcard)
5) Back out the the TWRP homescreen
6) Go to Install
7) Find the Insert Coin rom, select it, and swipe to start the install
8) Follow the onscreen menus for install options (since you already wiped everything, you can select the option to NOT wipe prior to install)
Notes on Insert Coin - if you use handsfree bluetooth calling, you need to download one of the 4.4.2 versions of the ROM (3.0.7 or 3.0.8). I usually use 3.0.7, personally. 3.0.8 had some issues with paid apps not installing properly and 3.0.7 is pretty much bugfree imo. If handsfree bluetooth isn't important, then the latest 4.x.x version will be fine.
I hope this helps you.
Click to expand...
Click to collapse
'
It did I successfully installed a custom rom on it thank you!

Having trouble fixing softbrick after attempting to root A9

On an HTC One A9 updated to 1.55.617.4 via OTA. CID = BS_US001. I unlocked the phone (i still have S-Off), installed TWRP, and then tried to root it. Like a fool, I didn't back up first. Something went wrong and I can't boot, I just get stuck at the HTC logo bootsplash. I have tried using the RUU tool to reset the phone to version 1.12.617.6 (both unlocked and relocked) without success. I tried to restore a TWRP backup from this thread but TWRP doesn't see it on my SD card.
Am I missing something? Do I need S-Off? Are there stock images somewhere I can use? I'm striking out so far and I could really use some help.

cornercase said:
On an HTC One A9 updated to 1.55.617.4 via OTA. CID = BS_US001. I unlocked the phone (i still have S-Off), installed TWRP, and then tried to root it. Like a fool, I didn't back up first. Something went wrong and I can't boot, I just get stuck at the HTC logo bootsplash. I have tried using the RUU tool to reset the phone to version 1.12.617.6 (both unlocked and relocked) without success. I tried to restore a TWRP backup from this thread but TWRP doesn't see it on my SD card.
Am I missing something? Do I need S-Off? Are there stock images somewhere I can use? I'm striking out so far and I could really use some help.
Click to expand...
Click to collapse
Had some trouble myself but this is how I solved it.
•Get the 1.12.617.6 ruu.exe and flash that.
http://www.htc.com/us/support/rom-downloads.html#unlocked
•After you boot up and set-up, take the system update to 6.0.1 and then flash twrp.
• Boot into twrp and then factory reset your device.
•Download the latest SuperSU beta from it's respected thread and flash that.
http://forum.xda-developers.com/apps/supersu
•(optional) Download the latest open gapps pico for 6.0 arm64 (if you like less bloat)
http://opengapps.org/
•(optional) Install the stock marshmallow boot animation (make sure to get the 1080p flashable zip)
http://forum.xda-developers.com/android/themes/bootanimation-android-marshmallow-t3180984
---------- Post added at 10:45 AM ---------- Previous post was at 10:18 AM ----------
My bad. Just read that you already used the ruu program. Is your mid correct?(2PQ912000) and you are in fact S-Off?
If that doesn't work maybe try using htc fastboot with the extracted zip for BS_US001 from the ruu thread.

AnierinB said:
My bad. Just read that you already used the ruu program. Is your mid correct?(2PQ912000) and you are in fact S-Off?
If that doesn't work maybe try using htc fastboot with the extracted zip for BS_US001 from the ruu thread.
Click to expand...
Click to collapse
I misspoke, I'm S-On. Is the RUU supposed to be able to overwrite a newer version (ie overwrite 1.55 with 1.12)? I have been trying to flash using RUU with USB passthrough to a windows virtual machine, but I guess I should try with a native install and see if that works.
If I'm S-On, will flashing with htc_fastboot still work?

cornercase said:
On an HTC One A9 updated to 1.55.617.4 via OTA. CID = BS_US001. I unlocked the phone (i still have S-Off), installed TWRP, and then tried to root it. Like a fool, I didn't back up first. Something went wrong and I can't boot, I just get stuck at the HTC logo bootsplash. I have tried using the RUU tool to reset the phone to version 1.12.617.6 (both unlocked and relocked) without success. I tried to restore a TWRP backup from this thread but TWRP doesn't see it on my SD card.
Am I missing something? Do I need S-Off? Are there stock images somewhere I can use? I'm striking out so far and I could really use some help.
Click to expand...
Click to collapse
Try flashing the 1.55.617.4 stock rooted ROM I posted here in TWRP. Make sure you wipe everything prior to flashing.

You can't RUU with S-On unless you have the stock recovery flashed. Head over to the resource page and flash the stock recovery via fastboot.
Then you can RUU.
Can't say this enough around here, S-Off/Unlock the bootloader should be the first thing people do that are going to fool around with ROMS. Sunshine is worth the $25.
You can RUU all day/night with S-Off, you don't need to relock bootloader or anything, any recovery can be installed, the RUU will always get you back to ground zero again.
After that, if you want to go up to 6.0.1, there are a few things mentioned above you need to do.
You either have to do a basic setup after the 6.0.0 RUU, take the 6.0.1 1.55 update. You can boot and do a basic setup, but you need to TWRP recovery, Format Data, then Run/Install SU Beta 2.65 from TWRP, then reboot again and start your setup over from scratch since Data is gone, plus no more encryption on your phone.
Really it is a matter of just a few steps to re-root the phone...but you have to be S-Off to make it easy.

techlogik said:
You can't RUU with S-On unless you have the stock recovery flashed. Head over to the resource page and flash the stock recovery via fastboot.
Then you can RUU.
Can't say this enough around here, S-Off/Unlock the bootloader should be the first thing people do that are going to fool around with ROMS. Sunshine is worth the $25.
You can RUU all day/night with S-Off, you don't need to relock bootloader or anything, any recovery can be installed, the RUU will always get you back to ground zero again.
After that, if you want to go up to 6.0.1, there are a few things mentioned above you need to do.
You either have to do a basic setup after the 6.0.0 RUU, take the 6.0.1 1.55 update. You can boot and do a basic setup, but you need to TWRP recovery, Format Data, then Run/Install SU Beta 2.65 from TWRP, then reboot again and start your setup over from scratch since Data is gone, plus no more encryption on your phone.
Really it is a matter of just a few steps to re-root the phone...but you have to be S-Off to make it easy.
Click to expand...
Click to collapse
RUU wipes whatever recovery you have and replaces it with stock, so no, you don't have to be on stock recovery to run an RUU.
The user has already updated to 1.55 via OTA, which means, because the user is S-ON, that they CANNOT RUU back down to 1.12, because the OS version is older.
The one thing you did state correctly is that S-OFF with SunShine would make all of this much easier. However if a corrupt system or boot is the only issue, flashing the ROM I linked is a simple and easy solution to get back up and running.

I'll try flashing the system image tonight to see if I can get it working. Next time, I'm not going to forget to S-Off and Nandroid backup first. And yes, to confirm through my own experience, I cannot use RUU since I upgraded OTA to a newer version that the RUU has regardless of recovery version.

cornercase said:
I'll try flashing the system image tonight to see if I can get it working. Next time, I'm not going to forget to S-Off and Nandroid backup first. And yes, to confirm through my own experience, I cannot use RUU since I upgraded OTA to a newer version that the RUU has regardless of recovery version.
Click to expand...
Click to collapse
You're not going to try the ROM I posted?

Captain_Throwback said:
You're not going to try the ROM I posted?
Click to expand...
Click to collapse
Sorry, that's what I meant. I don't do a lot of phone mods so I'm probably misusing some vocab (not to mention, I'm only now beginning to understand the many terms). I am going to try the ROM you posted. Just to clarify the process, I should do the following, correct?
1. Reunlock Device
2. Reflash TWRP recovery
3. run "fastboot erase system"
4. run "fastboot erase boot"
5. Drop the zip file on my SD card without extracting
6. Flash the ROM from the SD card via http colonslashslash highonandroid.com/android-roms/how-to-install-custom-rom-using-twrp-recovery-failproof-method/ (sorry, forum won't let me post links yet)
Questions
1. Do I have to use htc_fastboot for any part of this process? I've been loading TWRP with the regular fastboot since I usually run on a Mac.
2. Are there other partitions that need formatting?

cornercase said:
Sorry, that's what I meant. I don't do a lot of phone mods so I'm probably misusing some vocab (not to mention, I'm only now beginning to understand the many terms). I am going to try the ROM you posted. Just to clarify the process, I should do the following, correct?
1. Reunlock Device
2. Reflash TWRP recovery
3. run "fastboot erase system"
4. run "fastboot erase boot"
5. Drop the zip file on my SD card without extracting
6. Flash the ROM from the SD card via http colonslashslash highonandroid.com/android-roms/how-to-install-custom-rom-using-twrp-recovery-failproof-method/ (sorry, forum won't let me post links yet)
Questions
1. Do I have to use htc_fastboot for any part of this process? I've been loading TWRP with the regular fastboot since I usually run on a Mac.
2. Are there other partitions that need formatting?
Click to expand...
Click to collapse
Regarding your steps:
1. yes
2. yes
3. no - But running "fastboot erase cache" might be a good idea
4. no - But you should boot into TWRP at this point
5. yes - You can copy the files directly to the device over USB via MTP or UMS (mass storage mode)
5.5. In TWRP, Wipe Menu -> Format Data -> type "yes" to confirm, and then reboot recovery using the reboot menu in TWRP.
6. I don't know what that link is, but once you boot back into TWRP, you just navigate to the zip and swipe to install it.
7. Reboot system
8. ?????
9. Profit!
Regarding your questions:
1. No
2. See 5.5 above. You can also go to the Advanced Wipe Menu (Wipe -> Advanced Wipe) in TWRP and check the boxes to wipe Cache and System.

Captain_Throwback said:
Regarding your steps:
1. yes
2. yes
3. no - But running "fastboot erase cache" might be a good idea
4. no - But you should boot into TWRP at this point
5. yes - You can copy the files directly to the device over USB via MTP or UMS (mass storage mode)
5.5. In TWRP, Wipe Menu -> Format Data -> type "yes" to confirm, and then reboot recovery using the reboot menu in TWRP.
6. I don't know what that link is, but once you boot back into TWRP, you just navigate to the zip and swipe to install it.
7. Reboot system
8. ?????
9. Profit!
Regarding your questions:
1. No
2. See 5.5 above. You can also go to the Advanced Wipe Menu (Wipe -> Advanced Wipe) in TWRP and check the boxes to wipe Cache and System.
Click to expand...
Click to collapse
Great, I'll report back this evening.

Captain_Throwback said:
Regarding your steps:
1. yes
2. yes
3. no - But running "fastboot erase cache" might be a good idea
4. no - But you should boot into TWRP at this point
5. yes - You can copy the files directly to the device over USB via MTP or UMS (mass storage mode)
5.5. In TWRP, Wipe Menu -> Format Data -> type "yes" to confirm, and then reboot recovery using the reboot menu in TWRP.
6. I don't know what that link is, but once you boot back into TWRP, you just navigate to the zip and swipe to install it.
7. Reboot system
8. ?????
9. Profit!
Regarding your questions:
1. No
2. See 5.5 above. You can also go to the Advanced Wipe Menu (Wipe -> Advanced Wipe) in TWRP and check the boxes to wipe Cache and System.
Click to expand...
Click to collapse
Looks like your fix worked. Thanks for your help, this saved me a lot of trouble with HTC.