Related
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
How do you have fastboot when fastboot comands are done from download mode? Dont you have a stock system image that you made?
He means bootloader mode, the white screen. I think OP is SOL. That's why it's important to make backups, especially for exotic devices. I'm not sure if it's possible, but since he's s-off his best bet would be to convert to an unlocked or Verizon device if at all possible just to get the device working again and wait for either an ruu or backup.
If he is soffed he can flash an international ruu
Sent from my HTC 10 using XDA-Developers mobile app
Android The Greek said:
If he is soffed he can flash an international ruu
Click to expand...
Click to collapse
Cid and mid still needs to match
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
I remembered the case of failure to entering Download Mode in M9 which solution is flashing the hosd image (extract from firmware), you can give it a try
androg said:
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
Click to expand...
Click to collapse
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Many domo's, DarkRazorZ!
I read that twrp-3.0.2-6-pme.img is the one to go for - that what you used?
Good you had no grief from HTC Japan. I actually sent back my M7 for the purple camera issue a few years back and did very little to disguise the fact it was unlocked and S-Offed. I think they are all fellow modders there and don't give a damn what we do. One reason why HTC is awesome.
I am now waiting for Nougat on the HTC10 (they (AU) just did a press release that it will be pushed soon), and as soon as that is on my phone, I shall be going the Sunshine route and installing aforementioned TWRP and so on. Getting fidgety, though... Xposed, Amplify, ad blocking... lemme at 'em.
DarkRazorZ said:
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Click to expand...
Click to collapse
Hey I was wondering if you could help me on how to get a replacement device, I ran into the same problem as you did. Thanks
Hello DarkRazorZ.
I'm curious about your attempt to convert HTV32 to international.
It couldn't be done because of hardware compatibility issue among HTV32 and international?
Or because of just your own mistake in the process?
Did you try a method like this?
http://forum.xda-developers.com/htc-10/help/convert-htc-10-to-unlocked-t3384460
I'm in Japan and considering to buy HTV32, and I want to use it with international firmware.
I know this is your thread, but I can't find any information about this on web.
So could you share me your knowledge. Thanks.
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Quadrider10 said:
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Click to expand...
Click to collapse
No, I'm considering to buy HTV32(= HTC10 for Japan region), not other.
Well I'll make a new thread about this issue.
Thanks for replying Quadrider10, and sorry for disturbing DarkRazorZ.
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. , which I believe you need in order to flash a stock or RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
DarkRazorZ said:
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
Click to expand...
Click to collapse
hii can u help me how to unlock bootloader on HTC 10 AU version
aSSikn said:
hii can u help me how to unlock bootloader on HTC 10 AU version
Click to expand...
Click to collapse
follow this tut:
https://www.htcdev.com/bootloader/
s2kaka said:
follow this tut:
htcdev
Click to expand...
Click to collapse
i already follow that tutor yesterday.. but when i insert token number the site always says error 170 "CID not allowed"
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.
Hi everyone, first thread in xda!
So, my friend has a m9 that bought on April of 2016 in Germany, worked just fine until these days, it has already marshmallow, he was on exchange but now he's back to Paraguay.
Yesterday we tried to update, because there were updates available (3.35.401.32), so we downloaded from the phone settings.
Downloaded just fine, and when trying to install, just installed until 25% and then the red triangle appeared. I've been looking for some info, and just found that happened to some people too, but no answer or positive help.
Then I downloaded the Nougat OTA to just flash it via recovery (sideload); once in Recovery mode, headed to ADB install, renamed the OTA zip (to be accurate OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip) just to "ota.zip" cuz i'm so lame to write the whole name.
The flashing went well until @ ±40% and then Error Status 7 appeared, saying "This Package is for 'htc_himaulatt' devices; this is a 'htc_himauhl.'"
I think that the error might be in the regional versions, but I searched for HIMAUHL and there is NOTHING, NOWHERE.
Anyways, then I just downloaded the RUU from HTC's page, and still with no positive results, still on marshmallow and no possibilities to upgrade.
Any help?
martynssimpson said:
Hi everyone, first thread in xda!
So, my friend has a m9 that bought on April of 2016 in Germany, worked just fine until these days, it has already marshmallow, he was on exchange but now he's back to Paraguay.
Yesterday we tried to update, because there were updates available (3.35.401.32), so we downloaded from the phone settings.
Downloaded just fine, and when trying to install, just installed until 25% and then the red triangle appeared. I've been looking for some info, and just found that happened to some people too, but no answer or positive help.
Then I downloaded the Nougat OTA to just flash it via recovery (sideload); once in Recovery mode, headed to ADB install, renamed the OTA zip (to be accurate OTA_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6_R-3.35.617.31_release_490897lkj8xif5v3eoiykd.zip) just to "ota.zip" cuz i'm so lame to write the whole name.
The flashing went well until @ ±40% and then Error Status 7 appeared, saying "This Package is for 'htc_himaulatt' devices; this is a 'htc_himauhl.'"
I think that the error might be in the regional versions, but I searched for HIMAUHL and there is NOTHING, NOWHERE.
Anyways, then I just downloaded the RUU from HTC's page, and still with no positive results, still on marshmallow and no possibilities to upgrade.
Any help?
Click to expand...
Click to collapse
So what is the device SKU? It sounds like your phone did exactly what it was supposed to do - reject an incompatible RUU.
There is a possibility that the device is rooted, you cannot update unless the phone is stock. You need to put the phone in download mode, connect to a pc via usb cable and in cmd type: fastboot getvar all
Then you tried to flash an att firmware on a wwe international device so it rejected it, which is normal.
I can safely tell you that you'll be lucky to recover the phone from its current state. You must now do a lot of reading. Starting with flippys thread in the general section of the m9 forum.
Lucky for you I have the same device with a stock backup (except the stock recovery) at the same firmware you had before you started should you need it, I think you will. It is linked in flippy's thread.
Beamed in by telepathy.
computerslayer said:
So what is the device SKU? It sounds like your phone did exactly what it was supposed to do - reject an incompatible RUU.
Click to expand...
Click to collapse
Yes, the SKU is HIMA_UHL, european version I guess (?)
shivadow said:
There is a possibility that the device is rooted, you cannot update unless the phone is stock. You need to put the phone in download mode, connect to a pc via usb cable and in cmd type: fastboot getvar all
Then you tried to flash an att firmware on a wwe international device so it rejected it, which is normal.
I can safely tell you that you'll be lucky to recover the phone from its current state. You must now do a lot of reading. Starting with flippys thread in the general section of the m9 forum.
Lucky for you I have the same device with a stock backup (except the stock recovery) at the same firmware you had before you started should you need it, I think you will. It is linked in flippy's thread.
Beamed in by telepathy.
Click to expand...
Click to collapse
Okay m8, thanks! I'll be reading.
It's funny cuz my friend doesn't know **** about rooting and stuff like that, but i'll give a try.
Sent from my Andromax AD687G using XDA Free mobile app
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
Okay, I'm giving up, I need someone to help me.
I was given my neighbours HTC One M9. It was working just fine. After he gave it to me, first thing I did was a factory reset because he didn't delete anything.
After that, the problems began. When I boot up the phone, even directly after resetting and even before the setup, I get an error "Google App stopped working". And after that, all couple of seconds another "com.google.process.gapps stopped working".
I tried several of the fixes out there on the web, but it didn't go away. I did another factory reset, and again even when I setup the phone I get those errors.
There is still Android 6.0 on the phone, so I wanted to update to 7.1
During install, I got the red triangle screen, on both attemps. Well, f*ck.
So, I went on to install a new OS. Never did this before, so I though this is a good chance to learn some more about Android.
It just got even more strange. When I'm in the bootloader, I saw
***Software status: Modified***
S-ON
LOCKED
***Security Warning***
Especially the modified software was very strange, since my neighbour has neither a clue nor any interested of fiddling with phones.
When I tried to go into Download Mode, it said "failed to boot into download mode".
Recovery mode worked just fine.
Therefore, I couldn't do anything to install a new OS.
Next I bought the Sunshine App and S-OFFd my phone, which worked just fine.
Now I'm S-OFF, unlocked and the Security Warning has gone. The software is apparently still modified.
But when I go into download mode, I get the black screen with the silver logo and red text for a while, then the phone proceeds to boot normally.
What the f*uck? I'm just out of idead what to do now. Please don't let it be a dead nand... it's such a nice phone, and apart from the google app errors, it works perfectly. I used it for some surfing around today and it works really well. I can't imagine it being broken.
Thanks for your help!
What variant do you have? Firmware version?
side_flip15 said:
What variant do you have? Firmware version?
Click to expand...
Click to collapse
Firmware is 3.35.166.12
I don't know exactly about the variant, this is what the IMEI checker says:
SKU , VF , German , CHE , HTC , CH , Swisscom , Bootloader Lock , Dark Gunmetal/Dark Gunmetal , w/o SIM Lock , HIMA#UHL-D1
I have a bug report of the gapps-Error. Would that be helpful?
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Flippy498 said:
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
Click to expand...
Click to collapse
Flippy498 said:
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
I didn't have to revive it, except that Google-error it works beautifully. That' broken download mode the only symptom I have. The phone is (meanwhile after Sunshine) S-OFF
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Click to expand...
Click to collapse
Well, there are two things that leave me hoping it's not a dead nand.
• Apart from that com.google.process.gapps-error, it works like a charm. No crashes, no sudden reboots. I really can't imagine a broken part of a motherboard making no trouble, wouldn't that render the part
useless? And is that Google-App Error really relatable?
• After letting the Sunshine App do its job, I don't get an error message in the download mode (well, it just boots normally after a while), the security warning has gone as well. Only the modified software is
suspicious.
side_flip15 said:
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
Click to expand...
Click to collapse
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue.
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue. Great, thanks!
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
Click to expand...
Click to collapse
Yes, I know. Maybe I just don't want to accept that fact to keep my motivation to try to save the phone...
So what my optimism suspects is that somewhere deep in the firmware there is something corrupted. That leaves the System modified and the Google app confused.
After all, recovery mode works just fine. If you check what other people experience with a dead nand, it's got to do with sudden reboots, bootloops, failed download AND recovery modes et cetera.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Click to expand...
Click to collapse
A little more hope rised in me...
sechsgangschakter said:
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Click to expand...
Click to collapse
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
SAME HERE PROBLEM PLEASE HELP
I HAVE HTC ONE M9 OPJA100 JUST GO ON LOCKED SCREEN WHEN REBOOT TO BOOTLOADER ITS RESTART AGAIN EVEN NOT GO DOWNLOAD MODE OR RECOVERY MODE.
I WAS JUST MAKE ROOT THEN ITS STUCK ON LOGO
NOT GO FASTBOOT MODE TO CHECK CID OR FIRMWARE
WHAT I DO ?????
ITS LOCKED
S-ON ALSO
side_flip15 said:
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
Click to expand...
Click to collapse
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
sechsgangschakter said:
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
Click to expand...
Click to collapse
Glad I helped you:highfive:
side_flip15 said:
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Click to expand...
Click to collapse
Just for the record, that's not my thread. It's owned by Sneakyghost.
@sechsgangchakter: I'm glad to hear that your phone is working, again.
Flippy498 said:
Just for the record, that's not my thread. It's owned by Sneakyghost.
Click to expand...
Click to collapse
Oh god! Sorry
Credits to @Sneakyghost :highfive:
Hello, I am having a very similar issue. I am looking for the hosd.img file for Verizon. I dont see it at https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml. Please help. Thanks
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Flippy498 said:
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Click to expand...
Click to collapse
So no one knows of one available for Verizon m9? What would happen if I used a GSM one?
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Flippy498 said:
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Good idea, ill give that a try. Thanks