For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.
manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.
Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.
manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.
Related
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
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
jayreed1 said:
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
Click to expand...
Click to collapse
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
tabp0le said:
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
Click to expand...
Click to collapse
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
jayreed1 said:
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
Click to expand...
Click to collapse
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
andybones said:
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
Click to expand...
Click to collapse
I read the entire post as you recommended, and I believe I now know how to proceed.
Unfortunately, I've ran myself clear out of free time.
I'll give this a go and report back as soon as I get a few free hours again--probably Friday or so.
Thanks a million!
You guys are very welcome.
Please proceed at your own risk (as with any flashing).
I've tried to make the guide I used as clear as possible and will certainly help if anything is unclear, but keep in mind nougat wasn't out at the time it was created. I don't foresee any issues as really the main thing that is making it boot was anyone that had flashed the us unlocked firmware at any point in time, and I believe people are still converting, The guide is really flashing the us unlocked firmware then back to your (Sprint) RUU.
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
jayreed1 said:
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
Click to expand...
Click to collapse
Nice! Great to finally see some feedback from a sprint user. Wanted to try this myself before I upgrade to nougat firmware. Only thing I'm confused about is you having to erase modem 1&2. What does that mean?
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
jayreed1 said:
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
Click to expand...
Click to collapse
Awesome thanks! Sprint released Nougat OTA yesterday and OMJ extracted firmware that we can flash. Sprint Nougat RUU isn't out yet though waiting for it on HTC's site. Check it out on Sprint HTC 10 XDA dev page. If you flash the firmware and everything still works fine please let me know. Should be trying this if I have time tonight. Have a lot of homework :silly:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
andybones said:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
Click to expand...
Click to collapse
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
Click to expand...
Click to collapse
Very welcome, least I can do.
Nice work on finding the difference. Will certainly save alot of trouble for many!
guys right now what i have to do?
* i updated my htc 10 sprint till the last MM ota, i didn´t make nougat update
* i unlocked my bootloader and install unoficial twrp that i found here
* i have last viper rom
what should i do so i can install other custom roms because right now i can´t pass the boot logo
i´m s off
---------- Post added at 05:27 AM ---------- Previous post was at 05:19 AM ----------
i just need to flash this?
Attached Files
File Type: zip rfg_3.imgs.zip - [Click for QR Code] (1.91 MB, 12 views)
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Click to expand...
Click to collapse
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
beastlymonkey said:
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
Click to expand...
Click to collapse
Are you flashing it while in Download mode or bootloader?
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Are you flashing it while in Download mode or bootloader?
Click to expand...
Click to collapse
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
beastlymonkey said:
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
Click to expand...
Click to collapse
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Click to expand...
Click to collapse
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
beastlymonkey said:
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
Click to expand...
Click to collapse
Yeah I know TWRP is flashed from Download mode, but some stuff apparently still use the bootloader.
Sent from my Sprint HTC 10 using Tapatalk
Hello,
Got an HTC one M9 today. Since it has the stock rom on it, I wanted to go directly to the current version and flash all the old data out (if thats possible). So I visited the HTC-Support ROM download page which's link I cant post because I'm a too new user to this board.
There, I downloaded this (Under the "Unlocked/Developer" category): "HTC One M9 4.23.617.1".
When I start this, it recognizes my phone right and has a button "Update" for me, where I'm already wondering why is that. I want to flash my Phone with the current version, why should I bother updating anything? If you can point me where I could rather get the tools and instructions to do that (flashing with current version), I would be grateful.
However I tried Updating, and after a quick reboot the Updateprogram tells me "Error 132: Signature-Error".
It says I should get the right Update-Utility and try again. How is that not the right one?
Please help.
Greetings,
Ravior
RaviorMetal said:
Hello,
Got an HTC one M9 today. Since it has the stock rom on it, I wanted to go directly to the current version and flash all the old data out (if thats possible). So I visited the HTC-Support ROM download page which's link I cant post because I'm a too new user to this board.
There, I downloaded this (Under the "Unlocked/Developer" category): "HTC One M9 4.23.617.1".
When I start this, it recognizes my phone right and has a button "Update" for me, where I'm already wondering why is that. I want to flash my Phone with the current version, why should I bother updating anything? If you can point me where I could rather get the tools and instructions to do that (flashing with current version), I would be grateful.
However I tried Updating, and after a quick reboot the Updateprogram tells me "Error 132: Signature-Error".
It says I should get the right Update-Utility and try again. How is that not the right one?
Please help.
Greetings,
Ravior
Click to expand...
Click to collapse
Check out the readme thread, specifically the section on RUUs.
As for doing OTA updates versus RUU, the advantage of OTA updates is that your phone settings and data are preserved. RUU installs wipe and reset your phone to factory default.
computerslayer said:
Check out the readme thread, specifically the section on RUUs.
As for doing OTA updates versus RUU, the advantage of OTA updates is that your phone settings and data are preserved. RUU installs wipe and reset your phone to factory default.
Click to expand...
Click to collapse
Thank you for pointing me there. After going through much of the information stated there (In the readme thread) I was able to combine the things that happened and why they did so.
In my case, I was trying to use a RUU for 4.x versions on a phone with 3.x installed, which simply isnt supported.
So this means I have to update all the way to 4.x to install the most up to date ruu and then I can flash the device on that version.
I hope they have good reason for not letting us simply flash the current version, since its very troublesome to update all the way through but well...
Thank you!
RaviorMetal said:
I hope they have good reason for not letting us simply flash the current version, since its very troublesome to update all the way through but well...
Thank you!
Click to expand...
Click to collapse
its called "security".. But to hell with that eh!..
Beamed in by telepathy.
shivadow said:
its called "security".. But to hell with that eh!..
Beamed in by telepathy.
Click to expand...
Click to collapse
Please tell me about the security aspects of the mechanic that forces you to update step by step rather than installing full images of the current version. Just look at computer operating systems. Do you always install f.e. Windows XP and then upgrade through vista and windows 7 to windows 10?
RaviorMetal said:
Please tell me about the security aspects of the mechanic that forces you to update step by step rather than installing full images of the current version. Just look at computer operating systems. Do you always install f.e. Windows XP and then upgrade through vista and windows 7 to windows 10?
Click to expand...
Click to collapse
Well, since you didn't install anything but bought the phone with a pre-installed OS that metaphora doesn't suit at all. Compare it with a computer that you buy and that has windows 8 pre-installed. Are you able to directly install the latest windows 10 version with all current KB-updates installed? No, you aren't. You need to install windows 10 and then to install all missing KBs via the windows update function.
Since you seem to like them, here's another metaphora: Do you keep your flat's/house's lock and keys if you know that thiefs own a copy of the key? No, you probably change the lock and the key. That's what HTC did with the encryption keys.
And no one said that you need to flash every OTA up to the latest firmware of your SKU. Depending on your current firmware, you might be able to directly install the needed 4.x OTA and then you can flash a 4.x RUU (which might not even be needed since not every SKU received more than one 4.x firmware iteration, yet). And even if you aren't on the latest 3.x firmware for your SKU you only need to flash one RUU more (the one for the latest 3.x firmware of your SKU). All in all the whole flashing/installing won't take longer than one hour. A RUU gets flashed within less than 5 minutes. And the longest OTA installation that I faced with the M9 took half an hour and that was the update from Android L to Android M.
You see, there is absolutely no reason to get het up that much. So please, calm down a little. XDA isn't the place for public rants. That's what you can use facebook, twitter, G+ or reddit for.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Well, since you didn't install anything but bought the phone with a pre-installed OS that metaphora doesn't suit at all. Compare it with a computer that you buy and that has windows 8 pre-installed. Are you able to directly install the latest windows 10 version with all current KB-updates installed? No, you aren't. You need to install windows 10 and then to install all missing KBs via the windows update function.
Click to expand...
Click to collapse
Sorry, but I dont think that smartphones are that different from pcs. I think being forced to install as many tools and getting to know all the matter shouldnt be that much; it could be much easier. I think most of the stuff is just that complicated because this way its better to make money than having it in a simple and easy way, like one ROM for every country in the world. For example, I can easily create my custom windows 7 installation media with any updates and additions I would like and install it on every pc in the world thats not too old.
You see, there is absolutely no reason to get het up that much. So please, calm down a little. XDA isn't the place for public rants. That's what you can use facebook, twitter, G+ or reddit for.
Click to expand...
Click to collapse
Sorry I was just mumbling that, I didnt want to seem het up. Also, I dont use Facebook and such.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
And now I would like to ask you me how you type such long texts on your smartphone
Android/Linux is not Windows. If you believe it or not, you can't compare a PC with a smartphone.
And there are custom made firmware packs for this phone, as well.
In addition, HTC won't read what you're writing here so complaining about their decisions on xda is completely useless. If you still think that it's necessary then do so on one of the websites I mentioned in my last post.
Sent from my HTC One M9 using XDA Labs
Ok so in the last thread I started I learned how flashing ROMS works, with the matching firmware, CID's, and other stuff, but now I have another issue... The ROM that I was able to flash was the TeamVenom Viper One ROM for Android L (Lolipop)....The ROM version I used was Viper 3.5.0, but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x).... I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev) and I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link... I don't think I can update Viper because it says "Flashing the new Android M firmware is a must, else your phone won’t boot!!" (trust me it doesn't boot, I've tried)... But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)... What would I need to do from here, how would I A)fix HTC installer, or B) does anybody have a WORKING flashable stock android zip to update from Lollipop to Marshmallow...
Thanks in advanced!
Forum N00b,
qwsderter
qwsderter said:
but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x)
Click to expand...
Click to collapse
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
qwsderter said:
I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev)
Click to expand...
Click to collapse
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
qwsderter said:
I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link
Click to expand...
Click to collapse
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
qwsderter said:
But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)
Click to expand...
Click to collapse
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Flippy498 said:
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Click to expand...
Click to collapse
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash.... Any other ideas, you are the master at this Flippy, there must be another way...
qwsderter said:
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash....
Click to expand...
Click to collapse
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Flippy498 said:
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Click to expand...
Click to collapse
Ah gotcha... So I used the decryption tool to make a SD flashable zip, and what do you know, TWRP crashes when I swipe to flash... How come I can flash other ROMs but I can't flash stock roms without it crashing (Device turns off)
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok thank you "again" I have officially read your ENTIRE guide 3 times now, Not trying to offend you or make shame of your work, but the problem is I "THINK" that I am following your work.... I download the RUU for my phone (in this case SKU: 502 - CID: CWS__001 VERSION 2.11.502 (I have also tried 3.38.502.41 to no avail)) and everything is going as planned, I have verified that BOTH the CID and MID are matching that of my phone.... But when I plug SD card into Phone in download mode I get no such asked if I want to flash the file (as your guide says to do).... Ok so if I try to flash through TWRP it crashes, and if I try to Fastboot Flash the file I get what is seen in the picture attachment, and then nothing happens, except the bootloader page says "Under flash" and adds another line saying Under flash everytime I press the power button... My phone is S-OFF, is there another possible way to do this.... I swear to go I have read your ReadMe thread and I'm not just being arrogant, but my phone WILL not flash to ANY STOCK ROM downloaded anywhere from the Internet... @Flippy498 I promise there has to be something I missed in your ReadMe (I HAVE NO IDEA HOW I COULD) or i'm getting damaged ROMs... I'm sorry that you have to put up with me and help me thus far, and let me say the XDA community deserves people like you, and less people like me who think they know what they are doing until something breaks...
EDIT: It seems the phone is missing a located at /dev/fastboot_download_j in the CMD screenshot. Should that be said issue how would I go about fixing that...
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Flippy498 said:
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Click to expand...
Click to collapse
Once again Thank you for helping me out, the htc_flashboot command was what I needed, I was able to flash the stock rom through the command.... May I just say, you sir know what you are doing, and I wish you continue to help other people on this forms just like you've helped me.... I Installed the 2.x rom, but the OTA update didn't work for some reason... so I'm gonna flash the 4.x and then install ViperOne again...
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place...
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death...
Thanks again,
qwsderter
qwsderter said:
I Installed the 2.x rom, but the OTA update didn't work for some reason
Click to expand...
Click to collapse
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
qwsderter said:
so I'm gonna flash the 4.x and then install ViperOne again
Click to expand...
Click to collapse
Don't forget that you need to flash one of Sneakyghost's firmware packs if you want to be able to flash 4.x RUUs. (Keyword: encryption keys)
qwsderter said:
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place
Click to expand...
Click to collapse
That's actually the difference between my ReadMe thread and most of the RUU collections on other websites. The files only get linked if they're known to be working whereas other sites link every RUU they can find. There are a lot more RUUs for the M9 out there than the ones I listed. However, these RUUs either aren't able to get flashed successfully or their roms aren't able to receive any OTAs - e.g. there's a second RUU for firmware 1.32.401.15 than the one that is linked in my thread and if you flash that other RUU you're stuck on its firmware version until you flash a different RUU.
qwsderter said:
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death
Click to expand...
Click to collapse
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Flippy498 said:
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
Click to expand...
Click to collapse
Funny, I thought the same thing, until I realized it was ATT who I am paying every month to rip my girlfriend and I off. Well oh well, I know you are in Germany (From your profile) but if you ever come to the United States, I will say from my personal experience (my opinion, not facts) ATT has seemed to have the broadest coverage, but also is the (2nd) most constrictive (Verizon seems very constraining), to me ATT feels premium but they are also (in my opinion) the most likely to royally screw up... Oh well, no OTA time to flash!!!
Flippy498 said:
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Click to expand...
Click to collapse
Trust me, when I tried the SD card in the phone I thought, "That is a little odd", then both of my ASUS MemoPads didn't detect it either EVEN THOUGH THEY WERE RUNNING, I just assumed that they didn't work because MemoPads are the most budget friendly tablets ever and something broke, so I go to my Nexus 7 and realize it doesn't have an SD card slot so I couldn't test, so I popped the card in our Camera... Low and behold it doesnt detect.... Now the true question, why did my desktop detect it, eh whatever not worth my time.... The gods were looking down on me, they broke my $10 microSD and not my more than 10$ phone.....
Once again thank you for the help Flippy, you have no idea how much it hurt using my iPhone 5 for 2 days, I felt so inferior
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: