Related
HTC just released over the air update for the one x....check it out
Sent from my HTC One X using XDA
Yeah
1.28.401.9
I'm installing it just now as it completes download.
Mines unbranded with a Orange UK sim.
See if any changes.
already in General
Thx to you sir!!! Downnnloooaaddinnggg HTC love.
EddyOS said:
already in General
Click to expand...
Click to collapse
i don't think anyone is worried about dupe threads here. i started one about the audio chip, then another one showed up and went on 3 pages after i asked why it was needed.
brent8577 said:
i don't think anyone is worried about dupe threads here. i started one about the audio chip, then another one showed up and went on 3 pages after i asked why it was needed.
Click to expand...
Click to collapse
LOL
As far as I heard back from people already using 1.28, it seems to have some battery draining issues and other problems occurring, so I guess I'll skip this and will wait for ROMs to adapt the best out of this OTA update.
If more positive comments are posted here, however, I might still think about giving it a shot
What's the kernel version for 1.28? And can somebody verify if the nvcplsvc.apk in the correct place? Thanks.
Sent from my HTC One X using Tapatalk 2
Not heard of 128 being run till today,heard of 126 or 117,116, I'm UK and was on 126,unlocked one X
Sent from my HTC One X using XDA
Nothing here yet - I'm on 1.26 on Voda in the UK - are they rolling it out, or should it be available everywhere?
available in Belgium
Available on O2 in the UK
I've click installed and its been stuck on the black screen with the two green arrows and phone for around 10 minutes?
Does anyone whose flashed the update know how long it will take?
Thanks!
Exciting update but i already rooted my device and installed CWM. And now i have no idea what i should do because i want to try the new OTA update (no idea what OTA actually mean lol) but with the CWM i getting some ugly error messages after downloading the update and restarting the phone for applying it.
Should i wait for Revolution ROM build on 1.28 or look for How to get rid off CWM and lock the device again for OTA update?
And also please give me link or a guide what should i do if i want to RELOCK the device again, havent find anything in my briefly look on HTCdev web, there are just info how to unlock it.
bigbamboo5 said:
Nothing here yet - I'm on 1.26 on Voda in the UK - are they rolling it out, or should it be available everywhere?
Click to expand...
Click to collapse
It depends on your provider...alot of people seem to have gotten the update. I'm on Three and don't have it yet though.
OTA = Over The Air
I got OTA update today too! 1.28.401.9
nothing in india yet :| tried twice today.. unbranded.. anyone in india got update ?
madik_ said:
Exciting update but i already rooted my device and installed CWM. And now i have no idea what i should do because i want to try the new OTA update (no idea what OTA actually mean lol) but with the CWM i getting some ugly error messages after downloading the update and restarting the phone for applying it.
Should i wait for Revolution ROM build on 1.28 or look for How to get rid off CWM and lock the device again for OTA update?
And also please give me link or a guide what should i do if i want to RELOCK the device again, havent find anything in my briefly look on HTCdev web, there are just info how to unlock it.
Click to expand...
Click to collapse
Wait for ARHD update, mike already said it would be out today, so not long to wait.
To re-lock - fastboot oem lock
Update
Im on O2 and im still waiting lol
Kernel version
the kernel version is still 2.6, to be exact 2.6.39.4-g86aa4d. I don't think anything changed here... nVidia should work harder on getting 3.0 to work :\
If anyone cares: baseband is 1.1204.103.14.
I don't have any battery draining issues so far, it seems to me the banding actually got a little better, so they may have fixed at least some of the rendering related problems. GPU can still not be enabled, though.
P.S: I'm on an unbranded device. I might get Zen Pinball later, to see if that was fixed...
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
Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
domt91 said:
Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
Click to expand...
Click to collapse
You need a stock recovery to flash the OTA.
domt91 said:
Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
Click to expand...
Click to collapse
Easiest way to get it back to stock is just flash the Sprint H/K RUU. You can download it from HERE. Just run it and connect your phone when prompted and follow the instructions (I'd probably change your CID back to the Sprint one first to be on the safe side but as you're S-OFF it shouldn't be needed). You might also need HTC Sync Manager installed. If so, you can get it HERE
This process will wipe the phone completely so back up any data first but other than that you'll at least be back to stock and then troubleshoot any issues from there
Thanks
Many thanks to everyone.
Any chances of loosing the SIM UNLOCK when going back to stock completely?
Nope, that shouldn't be touched but as I've not had a SIM-locked device in years I can't say for certain
EddyOS said:
Nope, that shouldn't be touched but as I've not had a SIM-locked device in years I can't say for certain
Click to expand...
Click to collapse
OK, many thanks!
:good:
domt91 said:
:good:
Click to expand...
Click to collapse
Mine did the same this morning just flash twrp recovery and boot into it and you should be fine I don't know why it did this since I'm used to it popping up with a screen asking if I want to unlock boot loader but if it told you it was good then push twrp and you're good
tjeeeeee said:
Mine did the same this morning just flash twrp recovery and boot into it and you should be fine I don't know why it did this since I'm used to it popping up with a screen asking if I want to unlock boot loader but if it told you it was good then push twrp and you're good
Click to expand...
Click to collapse
Yeah, I just did that, no problems at all.
Tried to delete the previous post, but you got ahead of me
Let's see if I can get the mobile data to work without flaws.
domt91 said:
Yeah, I just did that, no problems at all.
Tried to delete the previous post, but you got ahead of me
Let's see if I can get the mobile data to work without flaws.
Click to expand...
Click to collapse
Are you trying to run any specific roms? I know with Sprint it's a bit limited
tjeeeeee said:
Are you trying to run any specific roms? I know with Sprint it's a bit limited
Click to expand...
Click to collapse
I want to try ARHD v22
domt91 said:
I want to try ARHD v22
Click to expand...
Click to collapse
Why not 34? Lol Sprint is up to date on its software you could just update to the lollipop firmware, and I could pull some of the files I've got to see if I can help you get it running, I'm on Leedroid right now so the process should be the same for ARHD.
tjeeeeee said:
Why not 34? Lol Sprint is up to date on its software you could just update to the lollipop firmware, and I could pull some of the files I've got to see if I can help you get it running, I'm on Leedroid right now so the process should be the same for ARHD.
Click to expand...
Click to collapse
Sorry if some of my questions are a bit dum, I just got from a long trip and have been out of this all rooting busines for a while...
Do i need to install a new stock firmware from Sprint with Lolipop to get the 34 runing?
I have been told v34 won't be working with this software I have right now on the phone.
domt91 said:
Sorry if some of my questions are a bit dum, I just got from a long trip and have been out of this all rooting busines for a while...
Do i need to install a new stock firmware from Sprint with Lolipop to get the 34 runing?
I have been told v34 won't be working with this software I have right now on the phone.
Click to expand...
Click to collapse
You can or you can go to the Sprint android development and flash the updated recovery since you are s-off and it'll permit you to flash lollipop roms without many issues but there is still the files that need to be modified for ARHD to work correctly like the boot.img and a few others.
tjeeeeee said:
You can or you can go to the Sprint android development and flash the updated recovery since you are s-off and it'll permit you to flash lollipop roms without many issues but there is still the files that need to be modified for ARHD to work correctly like the boot.img and a few others.
Click to expand...
Click to collapse
I just installed ARHD, everything went well and when it rebooted, the phone won't turn on... just black screen.
Any ideas??
domt91 said:
I just installed ARHD, everything went well and when it rebooted, the phone won't turn on... just black screen.
Any ideas??
Click to expand...
Click to collapse
Power+vol up for about 15 seconds then power+vol down to get into recovery. You cant flash it unless you swap out Sprint specific files otherwise you'll get what just happened or boot directly into boot loader.
Like I mentioned I can pull the files together and see if I can get it working for Sprint tonight when I get home but until then flash either fluent Rom or stock if you want lollipop or just flash bad boyz if you don't mind kitkat
tjeeeeee said:
Power+vol up for about 15 seconds then power+vol down to get into recovery. You cant flash it unless you swap out Sprint specific files otherwise you'll get what just happened or boot directly into boot loader.
Like I mentioned I can pull the files together and see if I can get it working for Sprint tonight when I get home but until then flash either fluent Rom or stock if you want lollipop or just flash bad boyz if you don't mind kitkat
Click to expand...
Click to collapse
I will go with installation of
Sprint_HTC_One_M8_non-HK_4.20.651.2_RUU
Sounds good?
domt91 said:
I will go with installation of
Sprint_HTC_One_M8_non-HK_4.20.651.2_RUU
Sounds good?
Click to expand...
Click to collapse
Yes and ill put the Sprint ARHD together tonight and test
tjeeeeee said:
Yes and ill put the Sprint ARHD together tonight and test
Click to expand...
Click to collapse
Many thanks!
For me, the biggest issue is the mobile data breakdowns... I know I read somewhere a while ago it was an issue with some Sprint M8 models. I would like to get everything working w/o problems since it is GSM unlocked, and via QPST I unlocked all the bands.
domt91 said:
Many thanks!
For me, the biggest issue is the mobile data breakdowns... I know I read somewhere a while ago it was an issue with some Sprint M8 models. I would like to get everything working w/o problems since it is GSM unlocked, and via QPST I unlocked all the bands.
Click to expand...
Click to collapse
Also, I just found some official EU RUU's with different radio's as far as I can tell from the filename.
Maybe that could be the final solution to all the problems?
old m9 ended up kicking the bucket sorta (usb died, so no way to charge the phone) so i bought a used one from swappa. it came with the latest ruu flashed, but i decided to reflash again to make sure it was totally clean (RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.12.exe). it went fine and so i began the process of unlocking it and flashing recovery (twrp 3.0.2.0) and flashing a rom (arhd 20 which is marshmallow) and titanium backuping back into shape. it unlocked and flashed recovery fine, however when i flashed the rom and did the first boot, i noticed i had no signal even though the stock rom had 4 bars of lte. it was also very laggy and had issues with crashing apps and for some reason still had at&t bloatware even though i did a dalvik/cache/system/data wipe beforehand and then a data wipe during the install and was missing inbuilt htc apps like internet. in the settings it shows that the imei, baseband, and other things related are all "unknown". i researched and came across a fix where you flash back your stock boot image, and it worked, except it would fail to boot after the first reboot. so that was useless.
i decided to try flashing arhd 14 (lollipop) because its what my old m9 had since forever and never gave me an issue. surprisingly, it actually installed and ran just fine even though the phone is on marshmallow firmware, as well as much quicker and smoother than arhd 20. however, i have the same issue. no signal, and imei and stuff "unknown". it does show my imei in download mode so i know the phone itself didnt forget it somehow. i have no idea what is going on here because ive literally never had this problem with any phone, even with my old m9 and i absolutely refuse to use a stock rom and have to manually deal with all of the bloatware especially with selinux making anything remotely "dangerous" an excessive hassle. can someone help me figure out this unnecessary pita?
this is what is shown in the download mode screen:
*** UNLOCKED ***
HTC_HIMAULATT PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440801_96.01.51207A_F
OPENDSP-15.6.1.00522.8994_1026
OS-3.38.502.12
Did You Get Any Solutions ? :crying:
nope.
daktah said:
nope.
Click to expand...
Click to collapse
Can you please give me the link of stock img which helped you to get signal at first boot ? i am running on viper marshmallow rom.advance thanks to you
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
and yes exact same problem is also happening with me It shows imei in fastboot,but In the settings and phone info,Imei shows unknown and no cell signals .I Just Bought THe phone 2 Days ago Happened after flashing the Ar Hd Rom
i used the boot from the nandroid i made of the stock ruu image before i tried to install arhd
I know I sound stupid, but actually I did'nt take any backup before flashing would you please upload it to somewhere and give me a link. It would mean a lot to me, thanks
daktah said:
i used the boot from the nandroid i made of the stock ruu image before i tried to install arhd
Click to expand...
Click to collapse
Are you S-OFF? if so, are you sure that you used the correct firmware. Never had this issue myself, but am remembering from the days on the M9 that such an issue could occur if a wrong firmware is flashed.
Another chance could be the following one: if your RUU didn't download correctly it might be damaged and thus have caused the problem. This may be the case as you're missing stock Apps after flash. Have you checked if the md5 of the downloaded file is correct.
Edit: report back if it helped.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Are you S-OFF? if so, are you sure that you used the correct firmware. Never had this issue myself, but am remembering from the days on the M9 that such an issue could occur if a wrong firmware is flashed.
Another chance could be the following one: if your RUU didn't download correctly it might be damaged and thus have caused the problem. This may be the case as you're missing stock Apps after flash. Have you checked if the md5 of the downloaded file is correct.
Edit: report back if it helped.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Yeah turns out the latest arhd is made for 3.35 and I'm on 3.38, so that's why it's all jacked up. And of course there is no way to "downgrade" (see: upgrade) to a lower firmware without $25 s off. Pretty ridiculous I have to pay just to s off so I can put my phone on an older software that works better because of "security" (see: money).
daktah said:
Yeah turns out the latest arhd is made for 3.35 and I'm on 3.38, so that's why it's all jacked up. And of course there is no way to "downgrade" (see: upgrade) to a lower firmware without $25 s off. Pretty ridiculous I have to pay just to s off so I can put my phone on an older software that works better because of "security" (see: money).
Click to expand...
Click to collapse
I still think something went wrong when flashing RUU. A 3.35 based ROM shouldn't jack up anything, as long as your firmware is even a later one than the ROM base. Btw 25 bucks are well invested regarding all the work they do, but it's the wrong place to discuss. Did you check if the RUU downloaded correctly and the md5 after download still is the same as given in the dl link. Missing stock Apps after flashing an RUU are a major indicator for a bad download, and if firmware parts where missing in this download as well, you'll end up just as you'd described in your opening post.
Sent from my htc_pmeuhl using XDA Labs
I used the ruu 2 or 3 times and it worked fine every time and the stock rom runs just fine. It's when trying to flash the rom it doesn't work, and I used one I downloaded from my computer, from my phone, and one I already had on my SD and they all ended up with the same result.
5m4r7ph0n36uru said:
A 3.35 based ROM shouldn't jack up anything, as long as your firmware is even a later one than the ROM base.
Click to expand...
Click to collapse
It actually does. That's why thicklizard made his custom kernel. The 3.3x firmware versions for SKUs which skipped the 3.35 version are not compatible with 3.35 roms unless that kernel gets flashed.
Edit: I just read that the mono-revisited kernel is only for AOSP roms. I'm sorry but it seems like I don't have a solution for sense roms.
5m4r7ph0n36uru said:
Missing stock Apps after flashing an RUU are a major indicator for a bad download, and if firmware parts where missing in this download as well, you'll end up just as you'd described in your opening post.
Click to expand...
Click to collapse
Doesn't daktah say in the OP that he was missing those apps after flashing ARHD20? I never used that rom but it sounds like they got uninstalled during the installation. Does ARHD have an aroma installer like the Viper rom does where you can select which apps to install or not to install?
Sent from my HTC One S using XDA Labs
Flippy498 said:
Doesn't daktah say in the OP that he was missing those apps after flashing ARHD20? I never used that rom but it sounds like they got uninstalled during the installation. Does ARHD have an aroma installer like the Viper rom does where you can select which apps to install or not to install?
Click to expand...
Click to collapse
Thanks for the clarification mate.
Didn't remember this one.. guess it's already to long since I used my M9. I'm not sure if he tried to state exactly what I quoted from your post, cause he jumps from RUUing right to the flash of ARHD. never used it myself, this I don't know if it comes with an Aroma Installer at all. Either way it would be interesting to know what happens if he just boots into his stock ROM, to make sure the cause isn't a bad download of the RUU. Feel free to correct me if I'm mistaken
Sent from my htc_pmeuhl using XDA Labs
In theory you're right but I guess we both missed the post located directly above mine.
Sent from my HTC One S using XDA Labs
We did indeed. Blind I've become, as Yoda would state now.
Sent from my htc_pmeuhl using XDA Labs
So I managed to fix it... By replacing the USB/aux board in my phone. Only cost 10 bucks for a new one . However now i have a problem where my phone will not charge at full speed and will actually give me the "using too much power to charge" message when doing a titanium backup even on the stock charger. The battery was at dead flat 0 for like 5 days before I fixed it, so do I need to replace it or is there something else I can do to fix it? When it's full it holds a charge for as long as it did before, just charging is not working correctly it seems.
i have nandroid backup of 3.38.841.6 let me know if i can be any help, i"ll upload it on mediafire and give you link,
btw i had the same problem yesterday, i flashed my nandroid backup and things went smooth
i got no imei no network after flash AEHD20, so i flash back boot img from backup, everything fine but without root. i down load twrp backup from http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698, select the correct CID match your phone. my CID is HTC__044 with 3.42.708.3. After download backup unzip the file, done once backup boot file, copy the file from download overwrite your backup, then restore the file from backup. good luck. don't wipe!!!!!!
17/09/16
I install Viber one still no imei, restore back up boot, imei back but no root, install super su 2.65 everything fine got root and imei.
Install twrp 2.8.5.0 first then update to twrp 3.0.2.0
Hey arcslt18,
arcslt18 said:
i have nandroid backup of 3.38.841.6 let me know if i can be any help, i"ll upload it on mediafire and give you link,
btw i had the same problem yesterday, i flashed my nandroid backup and things went smooth
Click to expand...
Click to collapse
Do you still have that nandroid backup handy?
I think i do, Currently at work. i'll contact you as soon as i get my hands on it.
I've had this quite a lot of times but flashing a different kernel usually sorts of out right away
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
So i checked on a friends stock m9 and indeed it has the 4.47 update.
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
SO LONG FOR GOOD ADVICE FROM XDA.
BOOOO.
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
myphonesbetter said:
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
Click to expand...
Click to collapse
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
myphonesbetter said:
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Click to expand...
Click to collapse
HTC is a bit lazy in regard to updating their webpage. You're always only able to download the latest RUU. However, you don't mention which variant you own. There is more than just one non-dev edition variant. Nevermind, you mentioned it in one if your following posts.
myphonesbetter said:
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
Click to expand...
Click to collapse
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
myphonesbetter said:
So i checked on a friends stock m9 and indeed it has the 4.47 update.
Click to expand...
Click to collapse
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant.
myphonesbetter said:
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
Click to expand...
Click to collapse
It's possible to break the OTA-update function by modifying the system via a root file explorer, as well.
myphonesbetter said:
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
Click to expand...
Click to collapse
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
myphonesbetter said:
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
Click to expand...
Click to collapse
The "database" is still stickied (in not only one but two subforums of the M9 section - the general and the q&a section). Therefore, I'm a bit surprised that you weren't able to find what you're looking for. In addition the thread I'm talking about is not only a database, it even contains all information you would have needed for solving your issues, already.
myphonesbetter said:
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Click to expand...
Click to collapse
If the RUU is older than your current firmware then you won't be able to use it.
myphonesbetter said:
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
Click to expand...
Click to collapse
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down up and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
myphonesbetter said:
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
Click to expand...
Click to collapse
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Flippy498 said:
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
Click to expand...
Click to collapse
Yah. I get it. Was kind of just shouting to get some attention.
Ive noticed that not just this forum but many other forums that i used to use have lossed a lot of popularity.
I think because facbook groups and things like reddit that cover all subjects.
The problem with those places is that they are so unorganized.
Maybe thats also part of why its become so unorganized here. just what people are used to.
I honestly wasnt expecting actual info. Thank you.
Flippy498 said:
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
Click to expand...
Click to collapse
Well i was afraid to brick it so i figured out (accidentally) how to update.
Flippy498 said:
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant It's possible to break the OTA-update function by modifying the system via a root file explorer, as well..
Click to expand...
Click to collapse
Yes that was. it is 4.27.
I could not find any older ruu's on their site. Or anywhere for that matter. none with active links at least.
Flippy498 said:
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
Click to expand...
Click to collapse
Yes 132. I did not realize that. Do you mean i would need to update via ota? by searching for updates.
Flippy498 said:
If the RUU is older than your current firmware then you won't be able to use it.
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
Click to expand...
Click to collapse
So i was originally trying to flash the latest frimware 4.27.xxx but i kept getting error 132.
And on the htc website it has 2 sections for ruu's m9 ans m9 developer. So i just figured it was the wrong one.
So i figured i would try the last ruu that i flashed before installing the rom that i ran for almost 2 years (lee droid)
when i flashed that, it got halfway through and gave me error 155. but left my phone in the middle of an update. Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
Well i could not reboot the phone so i just started the recover process. This rebooted my phone a few times then just started flashing the rom. To my surprise it worked.
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Took about 4 hours and 7 updates or so. probably 5 gigs on the data plan but finally it finshed with a 1.1 gig update to 4.27.
Im not sure why the first flash failed or why it worked, but eventually it did work.
Flippy498 said:
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWRP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Click to expand...
Click to collapse
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
I was using the last ruu that i had used. but i also flashed a rom and it was a long time in between.
Also i installed the old version of lee droid on 4.27.xxx and it seemed to work fine. I did this on accident though. Flashed the wrong zip. Re-flashed the latest 4.0 and it seems to be working great. Noticing a couple little lags. Might go to the stock rom just rooted and debloated. It seemed to run a little smoother than leedroid for the time i was using it. but i felt like they were trying to extract my stem cells via confusing TOS agreements.
myphonesbetter said:
Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
[...]
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
Click to expand...
Click to collapse
The power button isn't disabled. As said in my last post, you need to press the power button and the volume down button for 30 seconds. It's always been like that on the M9 since HTC already changed that on the M7 or M8 (can't tell you which one exactly it was).
Relocking was only needed on HTC phones that are older than the M9. HTC changed that with the M9. And as said in my last post, re-locking the M9 if you don't have a RUU at hand that you already used successfully is more than dangerous due to Google's FRP. You might end with a non-booting non-unlockable phone.
In addition, a relocked dootloader doesn't change the fact, that your phone is missing the needed encryption keys. That's why the 4.x RUU still failed.
However, it's nice to hear that you could solve your problems now. ?
Sent from my HTC One M9 using XDA Labs
Ah, I made a mistake while writing my posts. It's power and volume up. Not power and volume down. :silly: