Develop Bugs

HTC One X G-sensors not working all of a sudden!

Hey guys... My friend bought an HTC One X second hand. It is rooted with what seems to be stock 4.0.3 Sense 4.0. The phone is also S-OFF and everything.. I will post pictures of it.
So here's the deal:
My friend was watching a movie but suddenly he felt as if the screen wasn't rotating... Now (According to AndroSensor App) the magnetic field, orientation, gyroscope, accelerometer etc... In short.. All of the GRAVITY SENSORS and the orientation sensors aren't working.. They are DETECTED by the app but say "Waiting for event"
tried hard resetting and everything. I have put many Custom ROMs in phones before. So i can flash ROMs etc if i have to
I have attached the pictures about everything and need help.. Alot appreciated thanks.
Sent from my Nexus 4 using XDA Premium 4 mobile app

I noticed i forgot to upload all the attachments.. I also have noticed that people have this problem on Sense 5. This one is sense 4 o.o
Can anyone help me in this. Also the phone has its bootloader LOCKED. I have to unlock it now?
Sent from my Nexus

WasifSal said:
View attachment 2362068I noticed i forgot to upload all the attachments.. I also have noticed that people have this problem on Sense 5. This one is sense 4 o.o
Can anyone help me in this. Also the phone has its bootloader LOCKED. I have to unlock it now?
Sent from my Nexus
Click to expand...
Click to collapse
take it to the shop, it is under warranty till may 2014

nogotaclue said:
take it to the shop, it is under warranty till may 2014
Click to expand...
Click to collapse
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
My question is that "CAN I FLASH A SENSE 5 (4.2.2) ROM ON THIS BAD BOY BY JUST FLASHING VIA RECOVERY?"
I'll then check the other powering off and stuff i read till i get my hands on my frnd's HOX. Cuz im a bit busy waiting for the Nexus 5 launch o.o

WasifSal said:
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
My question is that "CAN I FLASH A SENSE 5 (4.2.2) ROM ON THIS BAD BOY BY JUST FLASHING VIA RECOVERY?"
I'll then check the other powering off and stuff i read till i get my hands on my frnd's HOX. Cuz im a bit busy waiting for the Nexus 5 launch o.o
Click to expand...
Click to collapse
you should update it first, that is a very old version, you should have updates available. as it is s-off you can flash anything you want but I think you will need to update the hboot first, once that is done you have a lot of options available to you

nogotaclue said:
you should update it first, that is a very old version, you should have updates available. as it is s-off you can flash anything you want but I think you will need to update the hboot first, once that is done you have a lot of options available to you
Click to expand...
Click to collapse
Ermm... So i just update it via OTA? or flash a ROM of Sense 5 or. Something?

WasifSal said:
Ermm... So i just update it via OTA? or flash a ROM of Sense 5 or. Something?
Click to expand...
Click to collapse
well with such a low version there must be quite a few OTA's waiting

nogotaclue said:
well with such a low version there must be quite a few OTA's waiting
Click to expand...
Click to collapse
Yeah you might be right... So what you are suggesting is I do a ROM flashing? Seeing the phone is already s-offed and everything
Anyways can you please list me a step by step procedure? Seeing this is my friend's phone so not doing this on my own :x

Bump?
Sent from my Nexus 4 using XDA Premium 4 mobile app

Go to settings and check for an update. What we all recommend is that you send it to HTC, all untampered One Xs should still be in warranty, so send it to them, if it can't be fixed they'll send you a One X or a One X+, or sometimes they could send a HTC One if you're lucky :/
Sent from my HTC One X using Tapatalk

humzaahmed155 said:
Go to settings and check for an update. What we all recommend is that you send it to HTC, all untampered One Xs should still be in warranty, so send it to them, if it can't be fixed they'll send you a One X or a One X+, or sometimes they could send a HTC One if you're lucky :/
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
Nay i live in Pakistan :/ if this was in warranty even they wouldn't have accepted it :/ or requested a cost for it... Either way thanks for your reply... So doing an OTA update won't create problems on an S-OFFed device right?

WasifSal said:
Nay i live in Pakistan :/ if this was in warranty even they wouldn't have accepted it :/ or requested a cost for it... Either way thanks for your reply... So doing an OTA update won't create problems on an S-OFFed device right?
Click to expand...
Click to collapse
OTA need relocked or locked device , stock recovery and stock ROM
and if you still have a problem with your g-sensor , check my signature , there is an alternative way to fix it

HTC Venom said:
OTA need relocked or locked device , stock recovery and stock ROM
and if you still have a problem with your g-sensor , check my signature , there is an alternative way to fix it
Click to expand...
Click to collapse
bootloader doesn't need to be locked or relocked for ota, only stock rom, stock boot.img and stock recovery

nogotaclue said:
bootloader doesn't need to be locked or relocked for ota, only stock rom, stock boot.img and stock recovery
Click to expand...
Click to collapse
Oh alright! Btw if i flash a recovery via fastboot, then i am able to flash (say) a custom ROM Sense 5, 4.2.2 right? Just asking for it i will update it by OTA (provided there isnt a custom recovery... Since i didnt check that) :/

HTC Venom said:
OTA need relocked or locked device , stock recovery and stock ROM
and if you still have a problem with your g-sensor , check my signature , there is an alternative way to fix it
Click to expand...
Click to collapse
Oh i'll get right on it when i get my hands on the device can i request you to stay put to this thread? Cuz i will report back here

if you flash a custom recovery you can do anything you want, ie flash a rom, sense or no sense, or flash back to stock and because you are s-off you can even change your cid to install an update from a different region.
this can go on and on and people are starting to repeat themselves and you have had all the information you need to move forward. so what you need to do, as you say you cannot fix under warranty, is :- let the phone update via ota, this will update everything including the rom, the version of sense and the hboot. then once it is finished with all ota's available you can install a custom recovery( I recommend philz touch recovery or the latest twrp) and then you can flash all the rom's or mods you like.
and if you find you still have a problem with sensors check @HTC Venom signature for a possible solution

nogotaclue said:
if you flash a custom recovery you can do anything you want, ie flash a rom, sense or no sense, or flash back to stock and because you are s-off you can even change your cid to install an update from a different region.
this can go on and on and people are starting to repeat themselves and you have had all the information you need to move forward. so what you need to do, as you say you cannot fix under warranty, is :- let the phone update via ota, this will update everything including the rom, the version of sense and the hboot. then once it is finished with all ota's available you can install a custom recovery( I recommend philz touch recovery or the latest twrp) and then you can flash all the rom's or mods you like.
and if you find you still have a problem with sensors check @HTC Venom signature for a possible solution
Click to expand...
Click to collapse
Woah thanks for that reply man! Keep in touch bro i'll update it with the details when my friend lends me his One X once again thanks!

same issue
WasifSal said:
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
same thing happened to my one x also, bought it from olx, and it was new (somewhat)...g sensor not working...i did hard reset...and it started working, but again after few days its not working, and now i have done even factory reset, but not working
what should i do
Click to expand...
Click to collapse

bilalzahid29 said:
WasifSal said:
Since i bought it second hand he told me "i gave you the phone when it was working. Even you checked it here in the shop. Not my fault.".... Thats the last time i ever buy a 2nd hand phone -.-
And he ain't wrong himself either... Anyways a helpful suggestion will be alot appreciated...
same thing happened to my one x also, bought it from olx, and it was new (somewhat)...g sensor not working...i did hard reset...and it started working, but again after few days its not working, and now i have done even factory reset, but not working
what should i do
Click to expand...
Click to collapse
Try to do the hard reset after couple of days. Once you feel your device is warm enough. Chances to get them back gets better with time
Sent from my HTC Sensation Z715e using xda app-developers app
Click to expand...
Click to collapse

i got them back except for temperature sensor....althought i did this thing several times, but once it worked out...i restarted the phone by long pressing the power button, even after the TURN OFF menu appears...on the start screen pressed volume down button to go in safe mode, all sensors started working, then i restarted mobile to come in normal mode.
working fine uptil now, i dont have restarted or powered off after that. so dont know if they will keep working after restart or again same problem will occur
all the people having same problem, just keep on trying restarts, safe mode, factory reset etc etc most probably they will start working. its just hit and trial

[Q] converted vzw M8 to Tmo, but can't update firmware

Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant

Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.

xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?

Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.

xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?

Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.

xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help

Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.

xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up

Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?

possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery

Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.

where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do

xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.

nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.

Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.

xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?

SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.

Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:

Yeah and the guy from Germany doesn't have the time to look into this anyway...

[Q] updating firmware on a rooted att M8?

Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters..... also i flashed twrp cause there was no OTA att update found (checked twice)

Dragonmaster0430 said:
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters.....
Click to expand...
Click to collapse
1) Mods won't like you posting a question in the Dev thread... there are specific sections (general, firmware, etc) where you can post it...
2)Considering that your phone is practically new, if you only rooted it and haven't installed a custom recovery, you will be able to update your firmare (OTA) through the built in upgrade process on your phone. Once, that is done, root your phone and install a custom recovery like TWRP.
good luck

Deathsting_50cal said:
1) Mods won't like you posting a question in the Dev thread... there are specific sections (general, firmware, etc) where you can post it...
2)Considering that your phone is practically new, if you only rooted it and haven't installed a custom recovery, you will be able to update your firmare (OTA) through the built in upgrade process on your phone. Once, that is done, root your phone and install a custom recovery like TWRP.
good luck
Click to expand...
Click to collapse
1. SH!t sorry! I didn't realize ?
2. ...i already flashed TWRP,cause i checked twice for a OTA before hand and therr was no update found

Anyone got any ideas?

Dragonmaster0430 said:
Please forgive me if this has been answered elsewhere, i searched but what little i found didnt seem to helpful (maybe im just confused) i want to flash the new Viper rom but it says i need 4.4.4 firmware, my rooted htc only has 4.4.2. How do i update it? I am scared of bricking my new phone so could someone please explain it to me like i am stupid? I used the all_in_one_toolkit (wonderful program!) If it matters..... also i flashed twrp cause there was no OTA att update found (checked twice)
Click to expand...
Click to collapse
Yes, I sure do.
First of all, if you want the newest ViperOne, you'll want 5.0.1 firmware, at least.
Hook up to you PC. Get into ADB/fastboot, and issue the command fastboot getvar all.
Post the readout here, and I, or someone else, will point you in the proper direction to update your firmware.
Please make sure to delete the serial# and IMEI from the readout. Never post those in a public forum.

xunholyx said:
Yes, I sure do.
First of all, if you want the newest ViperOne, you'll want 5.0.1 firmware, at least.
Hook up to you PC. Get into ADB/fastboot, and issue the command fastboot getvar all.
Post the readout here, and I, or someone else, will point you in the proper direction to update your firmware.
Please make sure to delete the serial# and IMEI from the readout. Never post those in a public forum.
Click to expand...
Click to collapse
Ok sure!....how do I issue a command?

Dragonmaster0430 said:
Ok sure!....how do I issue a command?
Click to expand...
Click to collapse
Have you never used ADB or fastboot before?
Okay. This will update your firmware. Backup anything important to you, because this will wipe your phone.
Go here: http://www.htc.com/us/support/htc-one-att/news/
Scroll down to where it says "Manual system update instructions". Read what it says, then click the download link at the bottom.

xunholyx said:
Have you never used ADB or fastboot before?
Okay. This will update your firmware. Backup anything important to you, because this will wipe your phone.
Go here: http://www.htc.com/us/support/htc-one-att/news/
Scroll down to where it says "Manual system update instructions". Read what it says, then click the download link at the bottom.
Click to expand...
Click to collapse
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?

Dragonmaster0430 said:
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Click to expand...
Click to collapse
Yes, but that's easy. Unlock your bootloader, flash TWRP, and flash a rooted ROM, such as ViperOne.
Also, I recommend not using one click toolkit methods. They often cause problems, plus doing it manually is easy and gives you an introduction to ADB and fastboot, making it less intimidating.

I don't know how to do it manually =( last time I tried I hard bricked my m7

Dragonmaster0430 said:
Not by itself, i dont think so anyways... I just followed a youtube vid on how to use the all-in-one-tool kit program... I figured less room for error risk?
Thank you for the link! Will have to reroot and unlock it after the update and stuff like that?
Click to expand...
Click to collapse
I get this when running the RUU from the link you sent...

Dragonmaster0430 said:
I get this when running the RUU from the link you sent...
Click to expand...
Click to collapse
what should i do now?

Dragonmaster0430 said:
I get this when running the RUU from the link you sent...
Click to expand...
Click to collapse
You need to re-lock your bootloader first if you are not S-Off.
Get back into fastboot and do fastboot oem lock, then leave your phone connected, and run the RUU again.

xunholyx said:
You need to re-lock your bootloader first if you are not S-Off.
Get back into fastboot and do fastboot oem lock, then leave your phone connected, and run the RUU again.
Click to expand...
Click to collapse
ok I did that my bootloader now shows
"*** TAMPERED***
*** RELOCKED ***
and i still am get the same error message that I posted the screenshot of before

Dragonmaster0430 said:
ok I did that my bootloader now shows
"*** TAMPERED***
*** RELOCKED ***
and i still am get the same error message that I posted the screenshot of before
Click to expand...
Click to collapse
You have an AT&T phone, right? That's what it says in the title. And that download link I gave you is from HTC's official website for the latest AT&T RUU.

xunholyx said:
You have an AT&T phone, right? That's what it says in the title. And that download link I gave you is from HTC's official website for the latest AT&T RUU.
Click to expand...
Click to collapse
Yup It is at&t

Dragonmaster0430 said:
Yup It is at&t
Click to expand...
Click to collapse
I don't know.
Maybe you don't have the drivers installed on your PC.
Go to Device Manager with your phone connected. You should see that your M8 is connected.
If you don't see it in Device Manager, download HTC Sync Manager and run it to install the drivers. After that, uninstall HTC Sync. It doesn't play nice with ADB and fastboot. The drivers will remain.
Then go to Device Manager and confirm that your phone is listed there when connected..

xunholyx said:
I don't know.
Maybe you don't have the drivers installed on your PC.
Go to Device Manager with your phone connected. You should see that your M8 is connected.
If you don't see it in Device Manager, download HTC Sync Manager and run it to install the drivers. After that, uninstall HTC Sync. It doesn't play nice with ADB and fastboot. The drivers will remain.
Then go to Device Manager and confirm that your phone is listed there when connected..
Click to expand...
Click to collapse
mine shows up under device manager as "MTP"

Dragonmaster0430 said:
mine shows up under device manager as "MTP"
Click to expand...
Click to collapse
I really don't know what's going on here.
I do know that if you were to go S-Off, updating your firmware is a piece of cake. You just need to find the firmware.zip and flash it.

xunholyx said:
I really don't know what's going on here.
I do know that if you were to go S-Off, updating your firmware is a piece of cake. You just need to find the firmware.zip and flash it.
Click to expand...
Click to collapse
how do i do all that?

need some help returning my phone to default

So i would like to put a stock Rom, unroot it and lock the bootloader.
The thing is i don't want to mess up my phone and Google has failed me in searching for a guide, so i'm asking here.
Anybody have a bit of time to help me out with this?

Foulgrin said:
So i would like to put a stock Rom, unroot it and lock the bootloader.
The thing is i don't want to mess up my phone and Google has failed me in searching for a guide, so i'm asking here.
Anybody have a bit of time to help me out with this?
Click to expand...
Click to collapse
What is your phone model, details

Hi, I'm having the same issue. I have a HTC Desire 820 Dual Sim bought in Australia and I unlocked the bootloader without rooting, but now I have received the interim update for Android 6.0 and cannot apply it because of my unlocked bootloader. Can somebody help?

Foolsfoolsfools said:
Hi, I'm having the same issue. I have a HTC Desire 820 Dual Sim bought in Australia and I unlocked the bootloader without rooting, but now I have received the interim update for Android 6.0 and cannot apply it because of my unlocked bootloader. Can somebody help?
Click to expand...
Click to collapse
1. What is now installed on the phone Stock recovery or twrp? 2. unlocked bootloader does not interfere with the update installation 3. This way you can lock the bootloader https://yadi.sk/d/C5ZYzOL-k4dco 4. http://forum.xda-developers.com/des...p-2-8-7-0-64bit-a51ul-a51tuhl-europe-t3287214

vuk1963 said:
1. What is now installed on the phone Stock recovery or twrp? 2. unlocked bootloader does not interfere with the update installation 3. This way you can lock the bootloader https://yadi.sk/d/C5ZYzOL-k4dco 4. http://forum.xda-developers.com/des...p-2-8-7-0-64bit-a51ul-a51tuhl-europe-t3287214
Click to expand...
Click to collapse
I suspect I have a broken TWRP for Android 4.4.4, the stock firmware of the phone. I downloaded the most popular one (http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064) and didn't realise it wouldn't work with Lollipop. Since then, I have not been able to use HBOOT on bootloader or boot in Recovery mode. And just tonight I attempted to flash the linked TWRP but it didn't work. It just did what it always does when I hit Recovery - boots into Fastboot. Can you help?

Foolsfoolsfools said:
I suspect I have a broken TWRP for Android 4.4.4, the stock firmware of the phone. I downloaded the most popular one (http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064) and didn't realise it wouldn't work with Lollipop. Since then, I have not been able to use HBOOT on bootloader or boot in Recovery mode. And just tonight I attempted to flash the linked TWRP but it didn't work. It just did what it always does when I hit Recovery - boots into Fastboot. Can you help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/desire-820/general/official-ruu-htc-desire-d820u-a51dtul-t3359709

vuk1963 said:
http://forum.xda-developers.com/desire-820/general/official-ruu-htc-desire-d820u-a51dtul-t3359709
Click to expand...
Click to collapse
Can you help me relock my bootloader? Thanks for the article, I hope it works!

Foolsfoolsfools said:
Can you help me relock my bootloader? Thanks for the article, I hope it works!
Click to expand...
Click to collapse
To update, install necessary to install Stock recovery your phone model,This is a tool for this, you need to find the download and insert into the tool and flash Stock recovery for your phone model https://yadi.sk/d/w9smMOkzseBNc

vuk1963 said:
To update, install necessary to install Stock recovery your phone model,This is a tool for this, you need to find the download and insert into the tool and flash Stock recovery for your phone model https://yadi.sk/d/w9smMOkzseBNc
Click to expand...
Click to collapse
I need to know how to lock my bootloader. Will this do it?

Foolsfoolsfools said:
I need to know how to lock my bootloader. Will this do it?
Click to expand...
Click to collapse
This program is blocking bootloader. https://yadi.sk/d/C5ZYzOL-k4dco

vuk1963 said:
What is your phone model, details
Click to expand...
Click to collapse
Hi,
Sorry for the late reply but for some reason the email alert went straight to spam and i didn't know anyone replied to my post.
The phone is a HTC Desire 820, single sim, Android version 5.0.2. I made the dumbass decision to root it and after trying to update android and almost bricking it, I would like to return it to stock. I have TWRP 2.8 i believe... I am in over my head here tbh...

Foulgrin said:
Hi,
Sorry for the late reply but for some reason the email alert went straight to spam and i didn't know anyone replied to my post.
The phone is a HTC Desire 820, single sim, Android version 5.0.2. I made the dumbass decision to root it and after trying to update android and almost bricking it, I would like to return it to stock. I have TWRP 2.8 i believe... I am in over my head here tbh...
Click to expand...
Click to collapse
I'm with you - I've followed all his instructions and pretty much have your problem and I'm actually certain I just made it worse...

Foulgrin said:
Hi,
Sorry for the late reply but for some reason the email alert went straight to spam and i didn't know anyone replied to my post.
The phone is a HTC Desire 820, single sim, Android version 5.0.2. I made the dumbass decision to root it and after trying to update android and almost bricking it, I would like to return it to stock. I have TWRP 2.8 i believe... I am in over my head here tbh...
Click to expand...
Click to collapse
Carefully read my post!, everything is written, http://forum.xda-developers.com/desire-820/help/update-modified-5-0-2-euro-firmware-t3376130

vuk1963 said:
Carefully read my post!, everything is written, http://forum.xda-developers.com/desire-820/help/update-modified-5-0-2-euro-firmware-t3376130
Click to expand...
Click to collapse
Thanks, I'll try it in a couple of days and get back to you

Foulgrin said:
Thanks, I'll try it in a couple of days and get back to you
Click to expand...
Click to collapse
Okay

[SOLVED] Can't get download mode working

Okay, I'm giving up, I need someone to help me.
I was given my neighbours HTC One M9. It was working just fine. After he gave it to me, first thing I did was a factory reset because he didn't delete anything.
After that, the problems began. When I boot up the phone, even directly after resetting and even before the setup, I get an error "Google App stopped working". And after that, all couple of seconds another "com.google.process.gapps stopped working".
I tried several of the fixes out there on the web, but it didn't go away. I did another factory reset, and again even when I setup the phone I get those errors.
There is still Android 6.0 on the phone, so I wanted to update to 7.1
During install, I got the red triangle screen, on both attemps. Well, f*ck.
So, I went on to install a new OS. Never did this before, so I though this is a good chance to learn some more about Android.
It just got even more strange. When I'm in the bootloader, I saw
***Software status: Modified***
S-ON
LOCKED
***Security Warning***
Especially the modified software was very strange, since my neighbour has neither a clue nor any interested of fiddling with phones.
When I tried to go into Download Mode, it said "failed to boot into download mode".
Recovery mode worked just fine.
Therefore, I couldn't do anything to install a new OS.
Next I bought the Sunshine App and S-OFFd my phone, which worked just fine.
Now I'm S-OFF, unlocked and the Security Warning has gone. The software is apparently still modified.
But when I go into download mode, I get the black screen with the silver logo and red text for a while, then the phone proceeds to boot normally.
What the f*uck? I'm just out of idead what to do now. Please don't let it be a dead nand... it's such a nice phone, and apart from the google app errors, it works perfectly. I used it for some surfing around today and it works really well. I can't imagine it being broken.
Thanks for your help!

What variant do you have? Firmware version?

side_flip15 said:
What variant do you have? Firmware version?
Click to expand...
Click to collapse
Firmware is 3.35.166.12
I don't know exactly about the variant, this is what the IMEI checker says:
SKU , VF , German , CHE , HTC , CH , Swisscom , Bootloader Lock , Dark Gunmetal/Dark Gunmetal , w/o SIM Lock , HIMA#UHL-D1
I have a bug report of the gapps-Error. Would that be helpful?

I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.

@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.

It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.

Flippy498 said:
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
Click to expand...
Click to collapse
Flippy498 said:
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
I didn't have to revive it, except that Google-error it works beautifully. That' broken download mode the only symptom I have. The phone is (meanwhile after Sunshine) S-OFF
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Click to expand...
Click to collapse
Well, there are two things that leave me hoping it's not a dead nand.
• Apart from that com.google.process.gapps-error, it works like a charm. No crashes, no sudden reboots. I really can't imagine a broken part of a motherboard making no trouble, wouldn't that render the part
useless? And is that Google-App Error really relatable?
• After letting the Sunshine App do its job, I don't get an error message in the download mode (well, it just boots normally after a while), the security warning has gone as well. Only the modified software is
suspicious.
side_flip15 said:
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
Click to expand...
Click to collapse
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?

Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue.
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue. Great, thanks!
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
Click to expand...
Click to collapse
Yes, I know. Maybe I just don't want to accept that fact to keep my motivation to try to save the phone...
So what my optimism suspects is that somewhere deep in the firmware there is something corrupted. That leaves the System modified and the Google app confused.
After all, recovery mode works just fine. If you check what other people experience with a dead nand, it's got to do with sudden reboots, bootloops, failed download AND recovery modes et cetera.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Click to expand...
Click to collapse
A little more hope rised in me...

sechsgangschakter said:
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Click to expand...
Click to collapse
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.

SAME HERE PROBLEM PLEASE HELP
I HAVE HTC ONE M9 OPJA100 JUST GO ON LOCKED SCREEN WHEN REBOOT TO BOOTLOADER ITS RESTART AGAIN EVEN NOT GO DOWNLOAD MODE OR RECOVERY MODE.
I WAS JUST MAKE ROOT THEN ITS STUCK ON LOGO
NOT GO FASTBOOT MODE TO CHECK CID OR FIRMWARE
WHAT I DO ?????
ITS LOCKED
S-ON ALSO

side_flip15 said:
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
Click to expand...
Click to collapse
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!

sechsgangschakter said:
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
Click to expand...
Click to collapse
Glad I helped you:highfive:

side_flip15 said:
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Click to expand...
Click to collapse
Just for the record, that's not my thread. It's owned by Sneakyghost.
@sechsgangchakter: I'm glad to hear that your phone is working, again.

Flippy498 said:
Just for the record, that's not my thread. It's owned by Sneakyghost.
Click to expand...
Click to collapse
Oh god! Sorry
Credits to @Sneakyghost :highfive:

Hello, I am having a very similar issue. I am looking for the hosd.img file for Verizon. I dont see it at https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml. Please help. Thanks

You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.

Flippy498 said:
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Click to expand...
Click to collapse
So no one knows of one available for Verizon m9? What would happen if I used a GSM one?

You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs

Flippy498 said:
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Good idea, ill give that a try. Thanks