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"
Related
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.
xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.
xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery
Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:
Yeah and the guy from Germany doesn't have the time to look into this anyway...
Hey Folks
I have a slight issue, I had a rooted HTC 10(UK EE) phone running firmware 1.80.91.1, which I wanted to update so I flashed a back-up from TWRP to restore OTA functionality, however, this backup was corrupted and the phone got stuck in a boot loop with no OS, hurrah!
I've sorted that however, by locating a TWRP backup of 1.21.91.4, which was the only one I could find for the CID EVE__001, this file was just a boot and sys.img no recovery, now I still can't get OTA updates as I'm getting the file system is corrupted error when trying to download the updates.
So I've hunted and hunted either to find a full back-up, recovery or RUU that will work with my CID as I'm S-on, I have had no luck, so I can no longer get updates for the phone.
So, does anyone have a stock recovery they could upload for either 1.21.91.4, or even better a full back-up of any of the x.xx.91.x firmware? I've been tearing my hair out trying to find anything above 1.21.91.4 and even that was just a partially back up.
Any help is muchly appreciated.
Hi, I am om EE uk but my CID is HTC__001.
I HAVE A FULL BACKUP DONE IN TWRP, WHICH YOU CAN HAVE. I WILL SORT IT OUT AND SEND YOU A LINK. DONT KNOW IF IT WILL WORK BECAUSE OF DIFFERENT CID, BUT YOU CAN GIVE IT A GO.
GIVE ME A DAY OR SO.
Sorry to resurrect the thread, @si86 I've having trouble restoring radio signal on my HTC 10 after flashing an incorrect ROM, I'm on EE also- I'd really appreciate a copy of your TWRP backup to try on my handset if you are able to supply, would be very appreciated! I'm able to change the CID to match, having been through them all recently! My bootloader is unlocked and I'm S-Off. Thanks.
@Tuesg Were you able to rectify your situation?
SailorJerry01 said:
Sorry to resurrect the thread, @si86 I've having trouble restoring radio signal on my HTC 10 after flashing an incorrect ROM, I'm on EE also- I'd really appreciate a copy of your TWRP backup to try on my handset if you are able to supply, would be very appreciated! I'm able to change the CID to match, having been through them all recently! My bootloader is unlocked and I'm S-Off. Thanks.
@Tuesg Were you able to rectify your situation?
Click to expand...
Click to collapse
I am uploading the copy to my g_drive now. It is around 6.5Gb. Sent me your email so I can give you access to the folder so you can download it.
Sent from my HTC 10 using XDA-Developers Legacy app
you legend. will pm you now. Thanks.
SailorJerry01 said:
you legend. will pm you now. Thanks.
Click to expand...
Click to collapse
I've just hunted high and low to try and figure out why nothing will flash successfully to my HTC 10.
turns out to be this same issue, I'm showing as CID - EVE_001 on an MID 2PS62000
Any chance you could send me that link as well so that I can at least try and get the phone back to a usable state instead of being stuck in either bootloader, download or recovery.
My phone is Bootloader unlocked, but still S-On as I hadn't got that far yet.
Will i need to flash a stock recovery? and lock the bootloader again to get this to install properly?
It's really proving tricky as hell.
I got caught out a bit here as I was half way to using sunshine to s_off, and then I accidentally triggered an OTA update to Nougat 7.0.......
It never restarted properly after that and i've been unable to get it back to 6 or any other ROM at all as they all fail.
I managed to fix it, but only by switching to s-off and installing the EU edition software, I'm a tad concerned now though as I've yet to get the roll out of the 7.0 update, not sure if that's because of installing a different firmware or whether it hasn't been rolled out yet.
@si86 Many thanks for your assistance and sharing the files, I was unable to fix my phone after trying various avenues (100+hrs) so I swallowed my pride and went the insurance route, not worth spending more time on getting to work and I now have a rather nice device, yet unusable call/texts wise to play with alongside my nice shiny new one running 2.41.91.3 - I've rooted and S-off with sunshine, just trying to decide whether i'm going to play with some more custom ROMS again! Of course I am!
@Tuesg Kudos on fixing your issue!
guys can you please help me, my HTC 10 is EVE_001 i want to unroot how do i do that? i bought it off gumtree and cant get banking app to work due it being rooted.
faceman123 said:
guys can you please help me, my HTC 10 is EVE_001 i want to unroot how do i do that? i bought it off gumtree and cant get banking app to work due it being rooted.
Click to expand...
Click to collapse
You can usually do it straight from the SuperSU app itself.
silegeek said:
You can usually do it straight from the SuperSU app itself.
Click to expand...
Click to collapse
how can i do that, im really noob to this, thanks
faceman123 said:
how can i do that, im really noob to this, thanks
Click to expand...
Click to collapse
Along with superuser usually comes with an app for configuring it, depending on how it was rooted. SuperSU is usually the most common although I much prefer magisk.
It will be obvious what it's called, either superuser, SuperSU, etc. SuperSU contains within it the ability to fully unroot.
If there's no app, and if it is a stock rom, and not a custom one, a factory reset will remove it. If not, you will probably need to either do some adb commands to remove it, or remove it using the recovery.
silegeek said:
Along with superuser usually comes with an app for configuring it, depending on how it was rooted. SuperSU is usually the most common although I much prefer magisk.
It will be obvious what it's called, either superuser, SuperSU, etc. SuperSU contains within it the ability to fully unroot.
If there's no app, and if it is a stock rom, and not a custom one, a factory reset will remove it. If not, you will probably need to either do some adb commands to remove it, or remove it using the recovery.
Click to expand...
Click to collapse
you sir are my hero, i will try when i get home !!
silegeek said:
Along with superuser usually comes with an app for configuring it, depending on how it was rooted. SuperSU is usually the most common although I much prefer magisk.
It will be obvious what it's called, either superuser, SuperSU, etc. SuperSU contains within it the ability to fully unroot.
If there's no app, and if it is a stock rom, and not a custom one, a factory reset will remove it. If not, you will probably need to either do some adb commands to remove it, or remove it using the recovery.
Click to expand...
Click to collapse
In short terms, yes that might work for banking apps but it won't work for future Android updates. You need a completely stock (untouched) system and SU changes that even if you choose to unroot via the application.
hi when i i tried that super user unoot it goes to Twrp bootloader and nothing in there says unroot or uninstall twrp bootloader
Hey guys Google pay still doesn't work says phone has been modified I am eve_001 software number 1.80.401.1 what can I do to make phone stock again
faceman123 said:
Hey guys Google pay still doesn't work says phone has been modified I am eve_001 software number 1.80.401.1 what can I do to make phone stock again
Click to expand...
Click to collapse
I've had that issue with both Viper and Maximus. Removing root doesnt seem to totally remove it, and certain apps still pick up ... something.
Going back to total stock condition is a huge pain in the unmentionables. Because quite a lot of phones don't actually have an RUU for thier CID (for instance mine, H3G__001) has no RUU. So complete stock, even from TWRP backup was never an option for me. Even though ROOT wasnt an issue, things like OTA problems persisted no matter what.
I had to S-OFF (worth it in general tbh) in order to go back to a complete stock condition using the HTC WWE version (HTC__001). In the end I just decided to stick with the ROM I have now, LeeDroid. It has the option to be installed without root from the get go, but these days I just use Magisk. It is so simple to hide from banking apps and even things like pokemon go, that it doesnt do any harm having root there.
si86 said:
Hi, I am om EE uk but my CID is HTC__001.
I HAVE A FULL BACKUP DONE IN TWRP, WHICH YOU CAN HAVE. I WILL SORT IT OUT AND SEND YOU A LINK. DONT KNOW IF IT WILL WORK BECAUSE OF DIFFERENT CID, BUT YOU CAN GIVE IT A GO.
GIVE ME A DAY OR SO.
Click to expand...
Click to collapse
Hey si86,
wondering if I can get a link to your backup too!!
Thanks man!
PM me your email and I will send you a link.
Sent from my HTC 10 using XDA-Developers Legacy app
---------- Post added at 09:44 PM ---------- Previous post was at 09:40 PM ----------
Jon Olita said:
Hey si86,
wondering if I can get a link to your backup too!!
Thanks man!
Click to expand...
Click to collapse
Send me your email, and I will send you a link
Sent from my HTC 10 using XDA-Developers Legacy app
si86 said:
Hi, I am om EE uk but my CID is HTC__001.
I HAVE A FULL BACKUP DONE IN TWRP, WHICH YOU CAN HAVE. I WILL SORT IT OUT AND SEND YOU A LINK. DONT KNOW IF IT WILL WORK BECAUSE OF DIFFERENT CID, BUT YOU CAN GIVE IT A GO.
GIVE ME A DAY OR SO.
Click to expand...
Click to collapse
Hi there,
I'm in the exact same spot as the guy above. I restored the backup he mentioned, but don't have the Recovery. Therefore my phone is telling me I need to enter decryption password and won't boot past it.
Would you be able to give me that backup too?
Thanks.
After successfully converted to US Unlocked, Nougat, I tried to revert back by flashing firmware.zip and TWRP backup. But after the first time flashing the firmware.zip, I tried to reboot to download mode to complete the 2nd flashing but the phone just shut down. Now I cannot turn it on anymore and it does not even register charge from the charger. Have I bricked it? My is Japan variant, S-Off, bootloader relocked
nerodarknight said:
After successfully converted to US Unlocked, Nougat, I tried to revert back by flashing firmware.zip and TWRP backup. But after the first time flashing the firmware.zip, I tried to reboot to download mode to complete the 2nd flashing but the phone just shut down. Now I cannot turn it on anymore and it does not even register charge from the charger. Have I bricked it? My is Japan variant, S-Off, bootloader relocked
Click to expand...
Click to collapse
The correct way to revert would be to change the CID back then flashing the corresponding firmware etc. If you tried flashing the firmware for Japan but still had the CID set to us unlocked then yes you possibly bricked the phone.
I changed the cid back to Japan variant already, if the CID was not correct it wouldn't flash anyway. The problem is that the phone isn't receiving charge from the charger. I believe the phone would still hold a charge even if brick.
nerodarknight said:
I changed the cid back to Japan variant already, if the CID was not correct it wouldn't flash anyway. The problem is that the phone isn't receiving charge from the charger. I believe the phone would still hold a charge even if brick.
Click to expand...
Click to collapse
Sounds like a big hairy nasty brick alright.
comstockload said:
Sounds like a big hairy nasty brick alright.
Click to expand...
Click to collapse
Gonna bring it to the carrier, gonna see what they are going to do, hopefully can have it replaced
Same happened to me. Had to replace using insurance
nerodarknight said:
Gonna bring it to the carrier, gonna see what they are going to do, hopefully can have it replaced
Click to expand...
Click to collapse
may I ask what firmware you flashed to revert back?
If you flash an incremental one it will brick. need to flash a full/combined firmware from @Sneakyghosts thread
Same thing happened to me this morning, went to flash a FW and boom, brick. Not sure what I did wrong but will not do it anymore lol.
I've sent it away to HTC for repair. Has anyone else went this route and know what to expect?
I'm worried they will get it back on and see that it's S-OFF and a different CID than what it should be. I have a Sprint variant.
FlowingAway said:
Same thing happened to me this morning, went to flash a FW and boom, brick. Not sure what I did wrong but will not do it anymore lol.
I've sent it away to HTC for repair. Has anyone else went this route and know what to expect?
I'm worried they will get it back on and see that it's S-OFF and a different CID than what it should be. I have a Sprint variant.
Click to expand...
Click to collapse
theres no sprint nougat firmware, so you flashed an GSM firmware on your CDMA sprint? Not good.
This is why I take as few risks as possible when flashing. I'm still on a MM rom and will be until we get an official TWRP. And I only flash firmware/roms made for my device. Just my $0.02. Keep the change.
.
j to the 4n said:
theres no sprint nougat firmware, so you flashed an GSM firmware on your CDMA sprint? Not good.
Click to expand...
Click to collapse
I did it once before. I removed all radio img files and any other img files that the Sprint firmware doesn't contain. I think what did me in was flashing it while on an official Sprint Marshmallow ROM. The other time I did it I was already on a Nougat ROM. Might've been Viper or CM 14 a few days ago.
Learned my lessons haha. One question tho, what if I were to flash a RUU, matching CID and MID, would it be ok?
nerodarknight said:
Learned my lessons haha. One question tho, what if I were to flash a RUU, matching CID and MID, would it be ok?
Click to expand...
Click to collapse
I am only going to tell you the safest way because I don't want you to brick another phone. Assuming you're already on a custom rom:
1. Download the N ruu.exe for your device from HTC. Right now all they have is N for the US unlocked. The rest should be available in Jan. It won't kill anyone to wait that long.
2. Run the executable on your computer and follow the easy prompts. This will perfectly install the stock N rom.
3. Flash the official TWRP via fastboot command.
4. Use TWRP to format your data partition then flash the custom N rom of your choice. SuperSu should be included with the rom.
Finished. Yes, there are all kinds of things you can do instead. I use my phone for work too so I ain't going there.
Hi guys. I'm having a bit of a problem. I want to preface this by saying I know almost nothing about modding Android.
A while back I bought a used HTC M8, and I guess it had a bunch of modifications to it because it was rooted and boots into a weird screen (says something about being for developers only?) before booting into a screen that it waits on for about 5 (says ROM: Internal) and then boots the OS.
Well recently I had an issue where Maps wouldn't work and would lockup my phone when I launched it. So I decided to do a factory reset. After the reset was complete it was impossible for me to log into my Google account as the app would crash every time I tried to log in. Not logging in = unable to use the play store, etc. I tried factory resetting twice more and kept having the same problem.
So I decided maybe the phone had some weird custom OS installed that caused the phone to act weirdly. I decided I'd go to the HTC website and download their ROM and install it. However the phone doesn't seem to accept the ROM since the installation encounters an error and crashes at the beginning of the install.
So I decided I might as well try to flash a custom ROM since the phone had already had all the modifications done. It had some TeamWin recovery thing installed, S-ON enabled, and the bootloader unlocked. I downloaded the latest nightly of CyanogenMod and tried to flash it in recovery mode. It seems to complete okay as it says "success" after flashing. But when I try to boot the device it just boots directly into recovery mode and I can't seem to figure out what I've done wrong?
Any help would be super appreciated.
post the result of fastboot getvar all after removing serialno and imei
ahmed.ismael said:
post the result of fastboot getvar all after removing serialno and imei
Click to expand...
Click to collapse
Sorry, could you please be a bit more detailed on how exactly I'd do that?
Edit: Seemed to have fixed it by flashing the latest version of TWRP and then flashing Cyanogen mod again. Thanks!
Firepower01 said:
I decided I'd go to the HTC website and download their ROM and install it. However the phone doesn't seem to accept the ROM since the installation encounters an error and crashes at the beginning of the install.
Click to expand...
Click to collapse
Just for your knowledge, you can't just install just any RUU. It has to match your phone's carrier version (CID), which is one of the reasons ahmed asked for your getvar data (and those details of the phone can also affect what TWRP version to use, what ROMs you can install, etc.). Plus, you need to relock the bootloader to RUU, unless the phone is s-off.
The process of doing fastboot getvar all, has been described on this forum too many times to count. So its not his responsibility to describe that process to you; when you can easily find it by searching and learning for a few minutes.
I'm actually out of town now so I don't really have any way of knowing of the ROM I used is compatible with my carrier. My phone is unlocked so I wonder if that matters?
Regardless, I'll look into posting my getvar all when I get home. Thanks.
Firepower01 said:
I'm actually out of town now so I don't really have any way of knowing of the ROM I used is compatible with my carrier. My phone is unlocked so I wonder if that matters?
Click to expand...
Click to collapse
I'm not talking necessarily about your carrier or if the SIM is unlocked. The official RUUs will only run, if they match the CID of the phone.
We may be able to determine the version direct from the device, if you have an OS number listed on the bootloader screen. Is there an OS number listed there, and if so, what is it?
I couldn't install the HTC ROM, so I installed CyanogenMod.
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