Develop Bugs

[Q] HTC Boot Screen Freeze

Google brings back a lot of people who have this problem but no-one seems knowledgeable enough to have a fix for it hence my post here. Since I followed the How to downgrade, Easy S-Off and the tried and tested radio.img flash guides and flashed Leedroid (13/01 epic stable build) I've had an infrequent (i don't reboot much) problem with my DHD freezing on the HTC screen during boot. I've solved this in the past by reflashing (as I can still enter the bootloader and Clockwork Mod) from an SD card but this is getting annoying.
The people on Google who are having this problem have said they've returned their phones however If I were to do that I would have to go straight to HTC as I got mine from eBay, are HTC going to helpful in this situation?
So Is there a known fix for this that I'm missing? Maybe the latest Leedroid?
On a side note if there is no fix is it even possible revert my DHD to level of stock such that HTC won't know I've been mucking around with it? I took to easy S-Off route that apparently can be reversed and I didn't SIM Unlock it but due to my over confidence I can't be sure I kept all the backups of the stock stuff that I should have kept.
Anyway, thanks guys. I'll just hang out here with no phone for a bit hoping there is a way to get it to boot because I'd really hate to lose some of the MMS message I've been sent .

You should do a full wipe and try a new rom, for example the newest LeeDroid or Android Revolution HD.
It is possible to revert to stock so that HTC will never know, just follow the S-ON instructions in my Radio Tool thread.

jkoljo said:
You should do a full wipe and try a new rom, for example the newest LeeDroid or Android Revolution HD.
It is possible to revert to stock so that HTC will never know, just follow the S-ON instructions in my Radio Tool thread.
Click to expand...
Click to collapse
Many thanks for the reply. I did a ClockworkMod wipe and went for the new Leedroid (I've no idea if its the best but it was the first I spotted after rooting my phone), guess I'll have to wait and see if it happens again but touch wood no problems so far.
I've just been looking through the Revolution thread and spotted your wipe tool so if it does happen again I'll try that. I'd also like to say many thanks for your s-off thread, its very well written and easy to understand, and your work supporting the DHD is outstanding.

[Q] stock update S-OFF phone

I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,

Kokuyo said:
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Click to expand...
Click to collapse
Why did you root your phone? There is no need to update your phone to the latest OTA update if you are wanting to install custom ROMs.

Because I was testing custom mods and wanted to go back to stock?

Kokuyo said:
Because I was testing custom mods and wanted to go back to stock?
Click to expand...
Click to collapse
ahhh, I thought you had just rooted it. I updated the day after I received my new phone. I had problems with bluetooth (music wouldn't resume after ending phone calls) and wound up here on the XDA forums looking for answers. I ended up rooting my phone, installing CM6 and now CM7 and never looked back. There is no bluetooth switching problems using CM builds so I'm happy.

Found this:
http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock

Thanks, that looks interesting. Now the only question: Do I need my original CID? And if so, how do I find it now that the CID has been changed by gfree?

That link is about a procedure to restore the stock G2 ROM. Since you seem to have a DZ ROM, I'm not sure if you want to flash a G2 ROM (though the other bits might be useful).
The 1.72 OTA update has been rootable for some time now, so you can safely accept the update if you want. But it might be easier just to flash the 1.72 ROM in its entireity (you can get it from the dev forum).
With SuperCID and S-OFF you should have no problems flashing 1.72.

steviewevie said:
With SuperCID and S-OFF you should have no problems flashing 1.72.
Click to expand...
Click to collapse
Really? Then I don't quite understand the stickied warning thread that says to never, ever attempt that.
Anyhow, I gave the Virtuous mod another go. Since it has sense and 1.72 I'm thinking of testing this one out a bit more, before I go flashing stock.
Thanks for the replies, though.

Unable to find/install stock RUU on hboot 1.57

I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.

don't boots said:
I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.
Click to expand...
Click to collapse
Well i dont have a CDMA one v but i know that the RUU for hboot greater than v1.17 had not been released.. So the best method to recover stock ROM is using a stock ROM backup with the same hboot and radio version , if anyone bought a one v recently he should be on the latest hboot and radio version , you can get a stock backup from such a person or search on xda for such a backup..

There isn't a RUU for the Hboot 1.57 and the newest radio. Sorry to give the bad news. You will either have to use a nandroid backup or install one of the custom roms such as RhythmicRom, e3remeSense or myOneV. Good luck on your rooting journey!

Thanks. I ended up successfully installing Rhythmic, but I can't get x3reme Sense (my preferred ROM) to work, for some reason (which is sort of ironic - I know Rhythmic incorporates a fix to allow for compatibility, but I thought one of the OTA updates was supposed to prevent installing anything not based on Sense). Oh, well.

If you'll use this kernel, then x3reme Sense will boot. I tried it for a while, but for a sense based rom I prefer myOne. If you want to try it, Cyanprimo will boot and run fine with the RhythmicRom v1.2 kernel. That is my daily driver(at least for now).
http://forum.xda-developers.com/showthread.php?t=2261819

S-Off affect performance?

I went ahead and did the whole S-Off process recently. Before I did it, Viper Rom ran smooth as butter. not a complaint in the world, then I saw the update and thought I read that I may need to upgrade my firmware, which is a PITA if you aren't S-Off. I didn't read the fine print that it was international (I have the Sprint Variant) and went S-Off. Now everything feels a bit laggy. I've done 3 fresh flashes, reverted to my stock backup image, and went back to the old version of Viper I was on prior to the s-off.
My question is, now that the device knows it is s-off, does it impact the performance? Is it creating logs now for HTC? I feel like if I undo the s-off, I will have wasted the money I just dropped into it. Is there a way to toggle between the 2? Or am I a crazy person? I was going to go ahead and do an RUU as a final attempt to get back the snappiness, but wanted to see if anyone else had some input on the matter.

southernstyle said:
I went ahead and did the whole S-Off process recently. Before I did it, Viper Rom ran smooth as butter. not a complaint in the world, then I saw the update and thought I read that I may need to upgrade my firmware, which is a PITA if you aren't S-Off. I didn't read the fine print that it was international (I have the Sprint Variant) and went S-Off. Now everything feels a bit laggy. I've done 3 fresh flashes, reverted to my stock backup image, and went back to the old version of Viper I was on prior to the s-off.
My question is, now that the device knows it is s-off, does it impact the performance? Is it creating logs now for HTC? I feel like if I undo the s-off, I will have wasted the money I just dropped into it. Is there a way to toggle between the 2? Or am I a crazy person? I was going to go ahead and do an RUU as a final attempt to get back the snappiness, but wanted to see if anyone else had some input on the matter.
Click to expand...
Click to collapse
No S-Offing has absolutely nothing to do with performance. S-Offing just allows you full access to the phone. If anything it sounds like the firmware you flashed might be causing the lag if it wasn't specifically for your model. What I would do is find the correct latest firmware or RUU & start from scratch. I would go the RUU route since it would wipe the phone clean period and install the latest firmware. Not 100% sure if RUUing will undo the S-Off, I don't think so but again not 100% sure.

Robert's PDA said:
No S-Offing has absolutely nothing to do with performance. S-Offing just allows you full access to the phone. If anything it sounds like the firmware you flashed might be causing the lag if it wasn't specifically for your model. What I would do is find the correct latest firmware or RUU & start from scratch. I would go the RUU route since it would wipe the phone clean period and install the latest firmware. Not 100% sure if RUUing will undo the S-Off, I don't think so but again not 100% sure.
Click to expand...
Click to collapse
Running a RUU will not affect S-off status.

Robert's PDA said:
No S-Offing has absolutely nothing to do with performance. S-Offing just allows you full access to the phone. If anything it sounds like the firmware you flashed might be causing the lag if it wasn't specifically for your model. What I would do is find the correct latest firmware or RUU & start from scratch. I would go the RUU route since it would wipe the phone clean period and install the latest firmware. Not 100% sure if RUUing will undo the S-Off, I don't think so but again not 100% sure.
Click to expand...
Click to collapse
Magnum_Enforcer said:
Running a RUU will not affect S-off status.
Click to expand...
Click to collapse
Thanks for the quick replies. I never flashed the firmware, but it might be worth trying to flash it. I'm trying another rom to see if maybe it was just that. I'll try it out for a day and if that doesn't work then I'll go with the ruu. Appreciate the response guys.
Coming back to HTC, I somehow got talked into a Samsung last year. Worst decision ever. So I'm remember how to customize my phone again lol

I would most definitely update the firmware for the device. It's always a good idea to keep your firmware up to date. Being S-off this is pretty easy to do, but you can also run the latest RUU, as well, and start from scratch with a clean install.

With a stock phone, with S-Off you will get a message in "Usage & Error Reporting" that your device is a test device & that regardless of what is selected, reports will still be sent to HTC.

omar302 said:
With a stock phone, with S-Off you will get a message in "Usage & Error Reporting" that your device is a test device & that regardless of what is selected, reports will still be sent to HTC.
Click to expand...
Click to collapse
that is udove.apk. delete it from system and factory reset and that will be gone.
delete it from the rom zip your using before installing is better but if your completely stock (not flashing a rom .zip), the first option is what to do

Thanks for the replies. I did flash firmware and a new rom, and everything feels a lot better. Also swapped kernel. Thanks for all the info

My experience is that 1.80.xxx.1 and .3 is laggier then 1.30
this has to do with kernel changes from HTC in the official firmware.
I noticed this in the setup - in the first screen where you change language the background moves. On 1.30 it flows fluidly for as long as you bother to look but on 1.80 it laggs and stutter alot more and this is without doing anything.
HTC must have adjusted the official kernel to save power and thuss, it's more laggy (everywhere).

re-exploring rooting, flashing, and so on

Just wanted to make a post about re-exploring the whole rooting and custom ROM nature of Android.
I used to be fairly active when I was using my Desire HD back in the day (which remains one of my all time favorite devices). I was making splash screens, boot animations, discovering my own tweaks and stuff, which are probably around here in the Desire HD section somewhere, inclusing a bootloader, splash flash, radio flasher and all sorts.
And then it seemed to me that most of the reasons people were rooting for, were starting to becoming irrelevant, as more of those features were being built in etc. For my phones after the HD, I used a custom recovery at most, but never bothered to root, or install a different rom. Not to mention one of the more important banking apps I used refuses to work with root. Even now, I find my self exploring, tweaking, and then removing root. It seems to leave things as I set them whilst letting me run the phone normally.
I've been on the HTC10 for a few weeks now and a few issues with it have forced me to consider alternative ROMS as a way of fixing these or getting more out of the phone than is already possible. I unlocked the bootloader fine, but I dont think I will bother with S-OFF.
Last time I tried to install a custom rom to a phone with S-ON, you had to install the ROM first, and then go back into the bootloader and flash the roms boot.img seperatley. Apparently that step isnt necessary anymore, it takes care of it all during the installation process.
I'm glad I started to get into it all again, and I will be keeping an eye on new or interesting roms and seeing what becomes of them. Open to suggestions too

S-off isn't as much of a necessity as it used to be with some of the older HTC phones. It still has its usefulness, though. As far as ROM flashing goes, you can flash a ROM on the 10 without having to flash the boot.img separately, as you stated.
Sent from my HTC 10

The process is how I remember it on my old Desire HD, which I dug out recently. For whatever reason it cannot be changed to ENG-HBOOT or S-OFF (I think the bootloader is too recent or it was when HTC decided to start locking bootloaders, or something along those lines) it is bootloader unlocked, but S-ON RL (not sure what the RL means ... re-locked?) I updated the recovery to 4EXT since apparently no one seems to like CWM/Rom Manager these days, and I reflashed a more stable rom to it, which needed the boot.img flashed in fastboot.
S-OFF and ENG-HBOOT was fun for things like custom splash screens and so on, buts its nice that it isnt necessary for ROM flashing.

I was debating whether to bother with S-OFF, but in the end I'm glad I did if only to have the latest radio firmware. A bit terrifying to be a big step closer to bricking, though.
Everyone seems to be using TWRP recovery now, by the way.
Also, might want to give LeeDroid ROM a shot. Have been very impressed with how many kinks he's worked out.
The only finance app I know of that won't run on a rooted device is Android Pay. There's a workaround for this, though: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 Can't imagine not having root!

pixelvisions said:
I was debating whether to bother with S-OFF, but in the end I'm glad I did if only to have the latest radio firmware. A bit terrifying to be a big step closer to bricking, though.
Everyone seems to be using TWRP recovery now, by the way.
Also, might want to give LeeDroid ROM a shot. Have been very impressed with how many kinks he's worked out.
The only finance app I know of that won't run on a rooted device is Android Pay. There's a workaround for this, though: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 Can't imagine not having root!
Click to expand...
Click to collapse
Yeah I know it's opens up a lot of avenues for things, the app is Barclays, I'm in the UK so it may differ from what you have if you're elsewhere. They did ALOT of work to make it pretty unusable if you're rooted, and it won't even load at all with xposed and root cloak installed. A few do work, such as Nationwide.
I am on Maximus HD (LlabTooFeRs ROM), which is easier because OTA updates etc. I used to use LeeDroid a lot back on my Desire HD. I'll try a variety of roms when I can find the time.
HTC10 is pretty stable for now though. My main problem (just for fun really) is figuring out how to radio s-off and eng s-off my old desire HD. The cid is ORANG001, but the phone itself accepts any sim as it's been unlocked. Beyond that, I cannot downgrade the bootloader, the phone is rooted, bootloader unlocked, the sd card for it is a gold card, although I may try another. It just seems to not want to do anything.

silegeek said:
Yeah I know it's opens up a lot of avenues for things, the app is Barclays, I'm in the UK so it may differ from what you have if you're elsewhere.
Click to expand...
Click to collapse
Ah, I see -- a lot of frustration with that app on these forums!

pixelvisions said:
Ah, I see -- a lot of frustration with that app on these forums!
Click to expand...
Click to collapse
Yeah I noticed that! :laugh:

silegeek said:
Yeah I noticed that! :laugh:
Click to expand...
Click to collapse
Hey there. Just something to try out, if you want a bunch of tweaks build into the ROM, would be Viper10. It's really amazing and comes with OTA updates as well.
S-OFF would be needed in case you'll leave your HTC 10 on a custom ROM instead of reverting to stock, to be able to flash the latest no wipe firmware zips if need occurs as a result of incompatibility with your Custom ROM's base.
Sent from my HTC 10 using XDA Labs