Develop Bugs

Desire restart after 15 minutes if intense use

I am not sure this is the place to post this but I certainly hope so.
I have researched the matter a little before posting.
I got my Desire from a friend. He has been using it for over a year.
Seems he didn't modify anything and it still has the original system but am not sure. If someone can tell me where to find this info...
If I leave the phone on without using it it stays on but if I use it, like browsing or gps or any other program, even just downloading stuff from MArket, the phone restarts after 15 minutes and if I don't take out the battery for a few minutes it loops restarts.
Once the battery is removed for a few minutes the phone restarts normally.
from what I read it may be a problem with the board heating?
Is there a way to test that? to diagnose a phone?
Thanks for any help

Hey mate,
If you're running on a stock rom there's something wrong with the hardware. Unless you've got all the spare parts you can fix the phone yourself, otherwise it has to be repaired. Soz

How do I know if it is a stock Rom

ymkx said:
How do I know if it is a stock Rom
Click to expand...
Click to collapse
-___- How do you not know if you've rooted the phone and flashed custom software?

You should ask your friend if he has bought the phone from a store or if he has rooted it before. Otherwise you have to hand it in to the repair centre

ymkx said:
How do I know if it is a stock Rom
Click to expand...
Click to collapse
Generally you can tell by going to settings/about phone and looking at the software number and kernel version. If you see any strange names in these areas, like Nova-lite, Grim Reaper ver 1, etc, it is generally a modified rom.
Also, you can look in your apps for an app called Superuser. This is a sign of a rooted phone.
Additionally, if you power down the device, you should be able to boot into Recovery (if it is installed), by holding Vol- and Pwr. If you get into the boot, and select the "recovery" option, and you get a display with options like Install zip from SD, Wipes, Formats, etc, then this is a custom recovery.
My guess, would be, if the device is stock, Run an RUU Rom, and see if it will install a fresh OS. This may fix your issue. Corruption in the OS can definately cause the issue you describe.

The best sign should actually be to boot into bootloader (power off - HOLD volume down + power until white screen pops up) In the left upper corner it should say like:
"BRAVO PVT1 SHIP S-ON". If it says "S-OFF" your phone has probably been rooted before

chippey5 said:
The best sign should actually be to boot into bootloader (power off - HOLD volume down + power until white screen pops up) In the left upper corner it should say like:
"BRAVO PVT1 SHIP S-ON". If it says "S-OFF" your phone has probably been rooted before
Click to expand...
Click to collapse
I'd bet money that most Rooted Bravo's are still S-On...not reliable.
OP, do you have the "Super User" or "SU" app installed? If yes your phone is rooted and likely running a custom ROM.
Sent from my GT-I9100 using xda premium

rete said:
I'd bet money that most Rooted Bravo's are still S-On...not reliable.
OP, do you have the "Super User" or "SU" app installed? If yes your phone is rooted and likely running a custom ROM.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
True true, back to S-ON is possible. If the phone has been rooted or not before can be hard. Anyone can tidy up a phone but I suggest he roots his phone, flashes gingerbread RUU and then try again. One moment, I'm going to find a link for you m8
Sent from my HTC Desire

rete said:
I'd bet money that most Rooted Bravo's are still S-On...not reliable.
OP, do you have the "Super User" or "SU" app installed? If yes your phone is rooted and likely running a custom ROM.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Also, don't throw your money away, alpharev are one of the first bravo HBOOT flashers. This is taken from their site: [/QUOTE] HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security. Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
AlphaRev has patched HBOOT images for several phones, whereas the HTC Desire (GSM) was our first victim. [/QUOTE]
I recommend he flashes through HTC themselves
Sent from my HTC Desire using xda premium

ymkx said:
I am not sure this is the place to post this but I certainly hope so.
I have researched the matter a little before posting.
I got my Desire from a friend. He has been using it for over a year.
Seems he didn't modify anything and it still has the original system but am not sure. If someone can tell me where to find this info...
If I leave the phone on without using it it stays on but if I use it, like browsing or gps or any other program, even just downloading stuff from MArket, the phone restarts after 15 minutes and if I don't take out the battery for a few minutes it loops restarts.
Once the battery is removed for a few minutes the phone restarts normally.
from what I read it may be a problem with the board heating?
Is there a way to test that? to diagnose a phone?
Thanks for any help
Click to expand...
Click to collapse
Go to settings -> about phone and tell me what android version you have ( 2.1 / 2.2 / 2.3 ). I will give you a link as soon as the HTC developer site is back online. The tool I will get for you will flash your phone with Gingerbread (2.3) legit
Sent from my HTC Desire

chippey5 said:
I recommend he flashes through HTC themselves
Click to expand...
Click to collapse
NEVER do that, or you'll have to downgrade later.
I had similar problems with my stock desire, update fixed it. So it might not be hardware related. Try rooting and using a custom rom and see if it persists. If so, it ist hardware related and you'll have to send it in (unroot before), if not, it's software and you can just keep your custom rom.
And, before you ask, there are ca. 100 threads on what the best rom might be. Just try any one from the Desire Index (sticky in dev section).

As you said, it might not be hardware related but what does it matter? If the official update doesnt help and he has to root it, it won't matter since he's able to flash stock roms then...
Sent from my HTC Desire

He will certainly not brick it with the official update and it's a lot easier to skip the rooting part if you're not common with it
Sent from my HTC Desire

If you want to flash the official gingerbread rom from HTC click here: http://www.htcdev.com/process/legal_download/152 . This will surely NOT brick your phone. It's the latest official for desire too.

Sure it's not a particular app that's causing it? Also, perhaps underclock the CPU and see if that improves stability. If it's anything like desktop processors, they can degrade over time and cause instability (usually more noticable when the CPU is heavily overclocked, but it still happens regardless)

Ah well,i thought you meant unlocking the bootloader through the htc tool. For that is definitely not recommended. RUU should be no problem.
Btw, there is a reason for an edit function.
Gesendet von meinem HTC Desire

muellersmattes said:
Ah well,i thought you meant unlocking the bootloader through the htc tool. For that is definitely not recommended. RUU should be no problem.
Btw, there is a reason for an edit function.
Gesendet von meinem HTC Desire
Click to expand...
Click to collapse
I agree with you about that. I would use unrevoked in that case

[Q] Why is my HTC One x (PROTOTYPE) stuck on ICS?

Why is my HTC One x (PROTOTYPE) stuck on ICS?
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Rad io_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just check the attachments. It has all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and I Thank you for it, I hope you can help me!

all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140

I did that
nogotaclue said:
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop

so you have a stock recovery now? and receive ota notifications?

Yes
nogotaclue said:
so you have a stock recovery now? and receive ota notifications?
Click to expand...
Click to collapse
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:

sN_iPower said:
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
Click to expand...
Click to collapse
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there

alright
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
alright im going to try that now, I will get back to you once I done it

nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS

sN_iPower said:
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
Click to expand...
Click to collapse
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor

sN_iPower said:
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
Click to expand...
Click to collapse
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
Click to expand...
Click to collapse
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan

Thant said:
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
Click to expand...
Click to collapse
sN_iPower said:
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Click to expand...
Click to collapse
Actually @Thant replied also, try what he suggests at the bottom of his post to update your hboot, it's a different one to the one you tried, then try a higher ruu

I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
Maybe you are right he must to prepear and know the chance to broke his OneX is big because is prototype.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
That had crossed my mind actually, but he is receiving ota notifications and the results he posted from "getvar all" indicate everything is as it should be, same model number even.
I have come across an early prototype before and the only 2 differences were the casing and slightly larger headphone jack socket. AFAIK the hardware was the same. Unfortunately, the one I saw wasn't working so I don't know what version of android it had

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 androidruu/?developer=Endeavor
Click to expand...
Click to collapse
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app

xb2 said:
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.

Thant said:
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Click to expand...
Click to collapse
Ah, I see. Manual flashing stock rom is still ok anyway.
Thanks for the info, Thant
Sent from my HTC One X using xda app-developers app

Welcome... this had been discussed...
http://forum.xda-developers.com/showthread.php?t=2232063

I have Htc one x Prototype only ics no custom recovery no jb
hi, i have a htc one x protoype(engineer model) i have tried many times to install custom recovery and jb ruu but result is always same. bootloop and black screen. is someone can help. i know only xda members can help. so plz

Invalid Version info in HBOOT

Hi,
Having gone into hboot for the first time i notice that both radio and OpenDSP have "INVALID-VER-INFO" beside them.
Is this correct on an unmodified phone.
I've done a quick search but couldnt find anything.
I have hboot version 3.16.0.000

I have this also,
I'm using a stock htc one m8 from Vodafone.
The os is: os-1.54.161.5. Boot dated Mar 22 2014,00:08:55.0
EtA

Ethel the Aardvark said:
I have this also,
I'm using a stock htc one m8 from Vodafone.
The os is: os-1.54.161.5. Boot dated Mar 22 2014,00:08:55.0
EtA
Click to expand...
Click to collapse
also have this gonna try rolling back roms thru twrp backup to see if anything related to latest rom flashed will report back

Any updates on this topic? I just bought this phone and been using it for about 2 weeks. I went into the HBOOT to see what differences there were from my previous phone and noticed the invalid version on the radio and opendsp. Again, completely stock unmodified phone.

That is the TWRP recovery bug..are u all install the twrp recovery or not?
Edit: I read it again,so u all using stock rom,Idk what caused it now
Sent from my HTC One_M8 using Tapatalk

hdorius said:
That is the TWRP recovery bug..are u all install the twrp recovery or not?
Edit: I read it again,so u all using stock rom,Idk what caused it now
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I just went into recovery for the first time on my new m8 stock and unmodified. I see the same thing. I'm in T-Mobile

Same thing here. Happened after 4.4.3 update. Stock international M8. I wonder if it has anything to do with the battery drain introduced with the update - I barely get 12 hours of usage hence, instead of 18.

shirreer said:
Same thing here. Happened after 4.4.3 update. Stock international M8. I wonder if it has anything to do with the battery drain introduced with the update - I barely get 12 hours of usage hence, instead of 18.
Click to expand...
Click to collapse
same for me here

I noticed this on my phone today too. My phone is a completely stock verizon one m8.
My phone is not yet a week old.

Hi Guys,
which firmwares do you have. I'm running 2.22.401.4 in bottloader the hboot entries are the following:
CID-HTC__102
HBoot-3.18.0.0000
Radio-1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
Even after performing s-off they didn't change
________________________________________________________________________________________________________
HTCOne M8 Gunmetal: Sunshine S-Off, firmware stock 2.22.401.4, rooted with Chainfire SuperSu, CID HTC__102
HTCOne M8 Silver: HTCDev Unlock, S-On, ARHD/ViperOne (M8) (ever switchin'), firmware 1.54.401.10, CID HTC__102

Same here i am rooted and using TWRP recovery also have the invalid message like the OP so is this normal or something gone wrong somewhere ?

wakers said:
Same here i am rooted and using TWRP recovery also have the invalid message like the OP so is this normal or something gone wrong somewhere ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54669689&postcount=11

tonnytech said:
http://forum.xda-developers.com/showpost.php?p=54669689&postcount=11
Click to expand...
Click to collapse
Thanks i also went S-Off over the weekend (sunshine) but hadn't noticed the radio and stuff had changed

hi guys,
first off, thanks to everyone contributing to this forum, I've been able to find some truly useful help in here
Has anyone found a solution to this thread? My m8 has just changed for no apparent reason to "invalid-ver-info". I don't know how important the RADIO AND OpenDSP info is when it comes to un/re-rooting.
As it happens, I did take a photo of this info the day before it happened with my M7 ..will that be of any use to me?
Also, what information from the boot or software info, should NOT be shown on the internet E.G due to privacy/security reasons.
Thanks
TW

tw10 said:
hi guys,
first off, thanks to everyone contributing to this forum, I've been able to find some truly useful help in here
Has anyone found a solution to this thread? My m8 has just changed for no apparent reason to "invalid-ver-info". I don't know how important the RADIO AND OpenDSP info is when it comes to un/re-rooting.
As it happens, I did take a photo of this info the day before it happened with my M7 ..will that be of any use to me?
Also, what information from the boot or software info, should NOT be shown on the internet E.G due to privacy/security reasons.
Thanks
TW
Click to expand...
Click to collapse
you can post fastboot getvar all (minus your Serial no. and IMEI)
nothing on the bootloader is secret

as said above. You need to provide more information to solve your issue.

ok, well here's what I have for you..if you need anything else, please tell me(see attached).
I was thinking about setting this back to stock rom, but I can't seem to find in here...do I have any possibilities?
thanks

tw10 said:
ok, well here's what I have for you..if you need anything else, please tell me(see attached).
I was thinking about setting this back to stock rom, but I can't seem to find in here...do I have any possibilities?
thanks
Click to expand...
Click to collapse
Does the phone work ? do you have stock recovery ? Have you do a normal factory reset ?

yes the phone works but not the top speaker(for what ever reason) Hence I want to send it in for repair(if possible, still 18 months guaranty).
I don't believe I have a stock recovery(I'm too new to this game to really know), there is a twrp backup, but whether it's the original or not(I doubt it) because nothing changed as far as the boot or software/firmware version is concerned when I executed the recovery(only the basic content) and the date of the backup is just one week prior to when I purchased it!?!? which makes me believe that the original was overwritten.
no I haven't, the reset was apparently done by the seller.

tw10 said:
yes the phone works but not the top speaker(for what ever reason) Hence I want to send it in for repair(if possible, still 18 months guaranty).
I don't believe I have a stock recovery(I'm too new to this game to really know), there is a twrp backup, but whether it's the original or not(I doubt it) because nothing changed as far as the boot or software/firmware version is concerned when I executed the recovery(only the basic content) and the date of the backup is just one week prior to when I purchased it!?!? which makes me believe that the original was overwritten.
no I haven't, the reset was apparently done by the seller.
Click to expand...
Click to collapse
Well if you have TWRP you can try a format data, But this will completely wipe the phone all your data and the system will be gone.
you would then flash a stock Rom back to the phone from the ext_sd card
To find the correct stock rom you need your phones basic info from fastboot getvar all
you can post the results here but exclude your serial no. and IMEI

AT&T no boot animation after flashing ViperOne

I am unlocked, rooted, s-off and running 4.3 on my AT&T m8. I recently flashed Viper One, which was my first ROM on this phone, and I no longer have a boot animation, for a while I thought I was stuck on the boot screen but it turns out that I have no boot animation. When I restart my phone all I get is the red text screen, lasts for maybe 3-4 minutes and then the screen turns off when the phone has booted. I asked in the Venom IRC and no one seemed to know what the problem was, so I just thought I would ask here. If anyone has any ideas I would appreciate it, thanks!

Fallen Advocate said:
I am unlocked, rooted, s-off and running 4.3 on my AT&T m8. I recently flashed Viper One, which was my first ROM on this phone, and I no longer have a boot animation, for a while I thought I was stuck on the boot screen but it turns out that I have no boot animation. When I restart my phone all I get is the red text screen, lasts for maybe 3-4 minutes and then the screen turns off when the phone has booted. I asked in the Venom IRC and no one seemed to know what the problem was, so I just thought I would ask here. If anyone has any ideas I would appreciate it, thanks!
Click to expand...
Click to collapse
Question I really read a lot.
As the ROM thread of Viper One states it is designed for FW 2.22.401.x Did you flash the newest FW? If yes you should have a boot animation.
Hit "Thanks" if I was if any help
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
Question I really read a lot.
As the ROM thread of Viper One states it is designed for FW 2.22.401.x Did you flash the newest FW? If yes you should have a boot animation.
Hit "Thanks" if I was if any help
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yes I am on 2.22.401.4, that seemed to be what the people in the IRC seemed to think as well. I have considered going to 2.22.1540.3 and trying again but haven't had time to do so yet.

Fallen Advocate said:
Yes I am on 2.22.401.4, that seemed to be what the people in the IRC seemed to think as well. I have considered going to 2.22.1540.3 and trying again but haven't had time to do so yet.
Click to expand...
Click to collapse
Would be with a try.
Sent from my HTC One_M8 using XDA Free mobile app

Please don't posts multiple threads asking the same question. I answered your question and attempted to help you here: http://forum.xda-developers.com/att-htc-one-m8/help/boot-animation-restarting-installing-t2849818
Did you manually flash firmware with fastboot? If not, you are not on the new 2.22 firmware. Also check your hboot, if on the new firmware, it will be 3.18.
Otherwise, 2.22.1540 firmware is recommended for US users, so flash it.

Dev edition update to 5.1

When will the Dev edition get updated to 5.1? I thought the dev edition gets updated faster than the carrier editions.

http://forum.xda-developers.com/showpost.php?p=61670999&postcount=879

SWEEET!
SO after updating the Dev Edtion, i can be on the latest ARHD and Maximus ROMS with no issues with reboots and stuff?

Quadrider10 said:
When will the Dev edition get updated to 5.1? I thought the dev edition gets updated faster than the carrier editions.
Click to expand...
Click to collapse
New update now in the process. Almost 800mb. Software 2.6.651.11

I'm downloading the new OTA update now on my Dev. Edition 2.6.651.11
Sent from my HTC One M9 using Tapatalk

scoot0073 said:
I'm downloading the new OTA update now on my Dev. Edition 2.6.651.11
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Do you have to unroot to allow OTA´s on DevEd? Thanks in advance.

It's not up on the HTC website....

Quadrider10 said:
It's not up on the HTC website....
Click to expand...
Click to collapse
No the RUU is not up yet
Just flash the 1.32 RUU and check for updates. It worked fine today
Sent from my HTC One M9 using Tapatalk

I did same, flashed the most recent RUU and did the OTA.

Is there any reason to not accept this update? I haven't modified mine yet, but I want to root and go to CM later on.

Slusho said:
Is there any reason to not accept this update? I haven't modified mine yet, but I want to root and go to CM later on.
Click to expand...
Click to collapse
I would S-off before updating just to be sure you have it
Sent from my HTC One M9 using Tapatalk

rickylambert said:
Do you have to unroot to allow OTA´s on DevEd? Thanks in advance.
Click to expand...
Click to collapse
Yea you need to flash to stock to update via OTA
---------- Post added at 06:16 AM ---------- Previous post was at 06:15 AM ----------
Slusho said:
Is there any reason to not accept this update? I haven't modified mine yet, but I want to root and go to CM later on.
Click to expand...
Click to collapse
i would say yes update ur phone, camera improvement is kinda big tho in low light its still crappy. overall its getting better

I'm not noticing camera improvements but I am noticing a big increase in performance. However, here's a fun bug: I keep waking up to it charging to only 78% or so. When I unplug and plug it back in, it starts charging higher. I've never seen a bug like this before, and it could make this unusable for me.
Also, I thought s-off just unlocked the bootloader, which is the whole point of the Dev Edition. So shouldn't that be unnecessary?

Slusho said:
I'm not noticing camera improvements but I am noticing a big increase in performance. However, here's a fun bug: I keep waking up to it charging to only 78% or so. When I unplug and plug it back in, it starts charging higher. I've never seen a bug like this before, and it could make this unusable for me.
Click to expand...
Click to collapse
What charger are you using? I found that with an older charger that worked fine on my M8, I had weird charging issues since upgrading to 1.40 firmware. Updating to 2.7, and now 2.8, firmware fixed these for the most part, but still don't get a good full charge on that old charger. On the charger that came with the M9 seems to work just fine.
Slusho said:
Also, I thought s-off just unlocked the bootloader, which is the whole point of the Dev Edition. So shouldn't that be unnecessary?
Click to expand...
Click to collapse
Those are two separate things...unlocked bootloader lets you flash custom recovery (TWRP) and therefore root and install custom ROMs, provided they work with your device's current firmware.
S-Off lets you flash new firmware as soon as it's released rather than wait for your specific carrier to release an OTA. S-Off also lets you change your device's CID and MID, so you can convert your device to developer edition, international, etc. Also with S-Off you can do other things like change your software status in bootloader back to "Official" after it gets changed to "Modified".

jollywhitefoot said:
What charger are you using?
Click to expand...
Click to collapse
I'm using the iClever charger from here: http://amazon.com/gp/product/B00J94OAG8
jollywhitefoot said:
S-Off lets you flash new firmware as soon as it's released rather than wait for your specific carrier to release an OTA. S-Off also lets you change your device's CID and MID, so you can convert your device to developer edition, international, etc. Also with S-Off you can do other things like change your software status in bootloader back to "Official" after it gets changed to "Modified".
Click to expand...
Click to collapse
It sounds like there's no reason to get S-Off on the Dev Edition then, since I'm not going to want to flash a a carrier-specific firmware, and I don't need to change the status since HTC isn't going to deny warranty service because of modified software.

Slusho said:
I'm using the iClever charger from here: http://amazon.com/gp/product/B00J94OAG8
It sounds like there's no reason to get S-Off on the Dev Edition then, since I'm not going to want to flash a a carrier-specific firmware, and I don't need to change the status since HTC isn't going to deny warranty service because of modified software.
Click to expand...
Click to collapse
When I had the issue changing to the stock charger worked for me.
With S-Off you could have flashed the leaked 2.7 firmware a couple of weeks before the official 2.8 was released. You can also change your device status in bootloader back to "Official" from "Modified".
Other than that, if you're capable of returning your device to stock system image so that you can get OTA updates, there's not much of an advantage.
Other advantages of S-Off include the ability to return the device to 100% stock and the ability to use this method (http://forum.xda-developers.com/one-m9/general/sim-unlock-method-t3143333) to sim unlock.

So what's easier: getting S-Off or returning to the stock system image?

Slusho said:
So what's easier: getting S-Off or returning to the stock system image?
Click to expand...
Click to collapse
I've never returned to to stock using the system image. I always just run an RUU because i don't keep much data on my internal storage.
S-Off is pretty simple. Just root, download the sunshine apk and run it. after a few reboots, you're good to go.
So, having said that, I would tend to think they're about the same degree of difficulty.