Dear XDA developers, professionals and programmers:
Recently I came across a good deal (HTC M8 in mint condition) and bought it. It was running Android 4.4.4 and I was happy with it till I read that it could be updated to Marshmallow. I followed a few links and after some time discovered that it was originally bought from the USA and locked to AT&T even though the installed rom was WWE. Stupidly I downloaded Marshmallow update for AT&T (RUU) from the HTC website and ran the installer. The installer completed successfully and the phone now runs Marshmallow with Sense7.
Since the rom was filled to brim with useless AT&T crap that does not work outside AT&T network I decided to switch to developer WWE rom but the RUU refused to install on the phone (I have S-Off)
After doing a bit more reading I discovered it was because my new rom has a software number 6.20.502.5 while the RUU I would like to install has a software number of 6.12.1540.4
I googled and googled and searched and searched but could not find a single tutorial to explain how I can replace my current rom with the WWE version which has less bloatware and takes it easy on the RAM.
Can someone kindly explain (or redirect me to a link) of how to downgrade HTC M8 from image version 6.20.502.5 to image version 6.12.1540.4 or in layman's terms how to replace AT&T rom with Developer rom? BTW both roms are Marshmallow. I do not wish to install TWRP or CM so if there is a way besides this I'd be grateful. If not then I don't see any other options and I'd still be grateful
Awaiting your generous replies
What you want is not really a "downgrade" per se. While the AT&T version number is "larger" than the Dev Ed (6.20 versus 6.12), that is mostly just because it came later due to AT&T's slowness in approving the software. I don't think there is much (if anything) that is actually "newer" or "updated" in the AT&T stock ROM (versus Dev Ed). It just has (as you know) all the AT&T branding and bloatware crap.
What is keeping you from flashing the Dev Ed RUU 6.12.1540 is that your carrier ID (CID) needs to match the RUU (even with s-off). Therefore, you need to change your CID to that of the Dev Edition (or alternately SuperCID), which is easy since you already have s-off. You will however need root to do this, so either flash TWRP and SuperSU/Magisk to root, or you can run adb shell with run while booted to TWRP. Either way, you will need to install TWRP: https://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
No need to change the Model ID (MID) since the AT&T version and Dev Edition have the same MID.
After that, you should be able to run the Dev Ed RUU.
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Simply reboot to bootloader/fastboot then run command
To Dev Ed CID
fastboot oem writecid BS_US001
To SuperCID
fastboot oem writecid 11111111
Can't remember if this only can be done on unlocked bootloader. If can't, try this command first
fastboot oem rebootRUU
the follow by the above.
If still can't then need a unlocked bootloader to proceed.
ckpv5 said:
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Click to expand...
Click to collapse
Ah yes, obviously I was mixing up my methods to change CID versus MID.
Thanks for clarifying, yet again.
Thank you
Many thanks to you gentlemen for your generous assistance and helpful instructions. I really appreciate it. All the best
Update
Good day all:
Sorry to bother again but it failed again! I downloaded fastboot adb and followed the procedure, put the phone in fastboot mode and the CID was already 11111111 and still it refused to accept the RUU. Please find attached a photo of my fastboot screen, hope it can help determine where the problem is on my phone. [ The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!] Site refused to allow me to attach the photo link so I'll just write everything here
*****Software Status - Official******
******LOCKED******** (Even though I can use a non AT&T sim normally)
MS_UL_CA PVT SHIP S-OFF
CID~11111111
HBOOT - 3.19.0.0000
Radio - [email protected](long number)
OPENDSP - v56.2.2. (loooooooong number)
OS-6.20.502.5
eMMC Boot - 2048MB
*end of pic*
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Can any of you good gentlemen help me out a bit more? I'm willing to answer any questions to further clear the picture of my predicament.
Thank you again
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
ckpv5 said:
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
Click to expand...
Click to collapse
Thank you for your reply:
the RUU I'm trying to install is the developer RUU that I downloaded off the HTC official website. It is the same website I downloaded the AT&T RUU from which installed fine, upgrading the phone's OS from Android 4.4.4 to Android 6.0.
I have several laptops each running a different OS (Windows 7 which I use mostly and have been using for this process) Windows 10, Linux and Solaris.
I did download and install HTC Sync but disabled it's auto run when I noticed every time I plug my phone in it pops up. So that's disabled not uninstalled, but it didn't interfere in the RUU installation of the ATT update and it doesn't pop up when I try to install the developer update.
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Sir Lucifer said:
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Click to expand...
Click to collapse
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
Sir Lucifer said:
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Click to expand...
Click to collapse
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Have tried it 5 times already, results are the same. I'm downloading the RUU again, maybe my download was corrupt. Will get back to you later with any results. Thank you for your patience and time. Much appreciated
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Maybe my downloaded RUU is corrupt, I'll download another time and if it gives me the same problem I'll look for another source. I will keep you posted, thank you very much good man.
RUU Broken on HTC's website
Dear all:
After downloading the developer RUU for the second time and trying to install it again (Marshmallow for those of you who have just joined us) off the HTC support site I failed miserably at changing my firmware using that RUU. After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Sorry for wasting all your time gentlemen. I am very grateful (and very lucky) having assistance from good people like yourselves who have taken from their time to help a complete stranger. Much obliged gentlemen. And thank you all again
Cannot be the RUU is broken.
Another way to do this :
1. Install Dev Edition firmware. You can get the fw_6.12.1540.4.zip from - https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2. Instead of using RUU exe, you can use RUU zip (rom.zip) to install RUU. I remember long time ago someone had same problem like you. Asked him to use zip format RUU and it was successful.
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
You can get your own RUU.zip which is actually rom.zip yourself. Just run RUU.exe (no need to connect phone). Once it opens the agreement page, go to %temp% thru your search/run windows menu.
It's better to clear your temp directory first so easy to find 2 newly created folder when you run RUU.exe
The rom.zip is inside one of the folder. Copy that to your desktop.
Then follow this on how to install - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
There are 3 methods but I prefer the htc_fastboot because easily can see any error if any.
So step 1 firmware & step 2 RUU (rom.zip)
Sir Lucifer said:
Dear all:
After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Click to expand...
Click to collapse
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Downloaded Again
redpoint73 said:
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
ckpv5 said:
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
Click to expand...
Click to collapse
redpoint73 said:
You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
Sir Lucifer said:
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
Click to expand...
Click to collapse
I have the RUU.zip
You can download it from here :good:
Sir Lucifer said:
I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
Click to expand...
Click to collapse
That is the T-Mobile RUU. MetroPCS merged with T-Mobile, so it's a bit one and the same. But most everyone will call that RUU/version T-Mobile. It will change band support (as flashing any other RUU will). So if it was working before on the AT&T RUU(or Dev ED will support the same bands) I would not mess with random RUUs, unless we suggest them specifically.
Related
I've been having a hell of a time trying to unroot my HTC One M8... It was an AT&T one I converted to Skydragon GPE, S-off. All the resources I try to use keep on failing somehow—anyone have suggestions? There's a million different tutorials on how to do it and none of them seem to work for me, getting really frustrated...
(I would link the below guides I've been trying to follow but I'm too new a user so it won't let me):
- The Unlockr guide: The Hassoon toolkit no longer exists.
- DroidViews guide: Everything's good until I try to restore the RUU image, then the executable fails with no explanation. Same when flashing the RUU from HTC's website.
- Restoring from a Nandroid backup in TWRP: Also never makes it through the entire process, I'd have to rerun it to see what the particular error was.
Ughhh is there any definitive set of steps I can take to actually restore to default settings? Preferably with the tampered flags not tripped, but honestly I don't even care at this point... Do I need to flash some stock AT&T HTC One M8 firmware or something before doing this all? Where might I be going wrong? I know it's vague but I'd love a solid walkthrough.
Thanks everyone
The simplest way would be to get an RUU from htc.com for AT&T, putting your phone in fastboot mode (power off, then pressing power+volume down, and selecting "fastboot"), and then simply launching the ruu. It should restore your phone to nearly being stock, except for your CID number and s-off. There are tutorials on how to change your cidnumber, however i am not sure how to turn s-off back to s-on.
http://www.htc.com/us/support/rom-downloads.html here you can find appropriate downloads
Ok, firstly, you might check out this thread: http://forum.xda-developers.com/showthread.php?t=2733523
None of the instructions require the use of anything beyond fastboot/adb. Also, make sure you put your CID/MID back if you changed them to run GPE. That isn't required to run Skydragon, but if you have altered them, put them back. Then rerun the RUU. Finally, since you are S-off, you can trivially fix any flags, so don't worry about that. (Running the RUU successfully will clear the modified flag anyway)
jshamlet said:
Ok, firstly, you might check out this thread: http://forum.xda-developers.com/showthread.php?t=2733523
None of the instructions require the use of anything beyond fastboot/adb. Also, make sure you put your CID/MID back if you changed them to run GPE. That isn't required to run Skydragon, but if you have altered them, put them back. Then rerun the RUU. Finally, since you are S-off, you can trivially fix any flags, so don't worry about that. (Running the RUU successfully will clear the modified flag anyway)
Click to expand...
Click to collapse
So I did this, starting from the Skydragon Sense 7 ROM:
made nandroid backup
flash 1.54.401.5 firmware
set cid to CWS__001
run RUU for the latest AT&T one. It says it will update from 1.54.401.5 to 2.6.502.16.
Result? Error 155 "Unknown Error", no other information.
Any ideas?
osdiab said:
I've been having a hell of a time trying to unroot my HTC One M8... It was an AT&T one I converted to Skydragon GPE, S-off.
Click to expand...
Click to collapse
Did you actually "fully convert" to GPE, or just flash Skydragon GPE?
What color is your hboot screen?
What hboot number, radio number?
osdiab said:
- The Unlockr guide: The Hassoon toolkit no longer exists.
Click to expand...
Click to collapse
The toolkit still exists. But it hasn't been updated in a very long time, and will therefore cause many many issues. So don't use the toolkit!
osdiab said:
- DroidViews guide: Everything's good until I try to restore the RUU image, then the executable fails with no explanation. Same when flashing the RUU from HTC's website.
Click to expand...
Click to collapse
Don't know what guide that is, or what RUU it tells you to use; but be aware that there are many RUU versions for the M8, and the RUU needs to be the proper one for your CID and MID. Also, Win7 or 8.1 is recommended (Win8 and especially Win10 will cause the RUU to fail).
redpoint73 said:
Did you actually "fully convert" to GPE, or just flash Skydragon GPE?
What color is your hboot screen?
What hboot number, radio number?
The toolkit still exists. But it hasn't been updated in a very long time, and will therefore cause many many issues. So don't use the toolkit!
Don't know what guide that is, or what RUU it tells you to use; but be aware that there are many RUU versions for the M8, and the RUU needs to be the proper one for your CID and MID. Also, Win7 or 8.1 is recommended (Win8 and especially Win10 will cause the RUU to fail).
Click to expand...
Click to collapse
hboot screen is white. hboot number is 3.19.0.0000. radio number is [email protected] I was using windows 8.1, though the computer I was using only has USB 3.0 ports (Apparently people say 2.0 is better?)
This is on the firmware that I was using for Skydragon, I can reflash the other firmware I had used for the failed RUU upgrade if that would be useful.
osdiab said:
hboot screen is white. hboot number is 3.19.0.0000. radio number is [email protected]
This is on the firmware that I was using for Skydragon, I can reflash the other firmware I had used for the failed RUU upgrade if that would be useful.
Click to expand...
Click to collapse
I'd leave it alone, and just try running the RUU.
osdiab said:
I was using windows 8.1, though the computer I was using only has USB 3.0 ports (Apparently people say 2.0 is better?)
Click to expand...
Click to collapse
Yes, folks have reported issues with RUU and USB 3.0. You can always try, the worst that will happen is the PC won't be able to talk to the phone.
Another user mentioned you can "disable" USB 3.0 in settings, but I'm not familiar with that.
redpoint73 said:
I'd leave it alone, and just try running the RUU.
Yes, folks have reported issues with RUU and USB 3.0. You can always try, the worst that will happen is the PC won't be able to talk to the phone.
Another user mentioned you can "disable" USB 3.0 in settings, but I'm not familiar with that.
Click to expand...
Click to collapse
OK, I've tried doing it on a computer that has USB 2.0 ports and once again, no go.
Trying to run the Developer/Unlocked RUU on HTC's website, it's stuck forever at 0/7 sending.
Trying to run the AT&T one, it errors out with a 155: Unknown Error message as soon as it boots to RUU mode.
Any other thoughts?
osdiab said:
Trying to run the AT&T one, it errors out with a 155: Unknown Error message as soon as it boots to RUU mode.
Click to expand...
Click to collapse
I think this means you need to relock your bootloader (required to RUU with s-on).
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
Thanks for your reply man, but im extremely lost here. Could you please guide me step by step? I've downloaded the firmware. Where do I put it? I've tried the adb folder. But it show error: can not locate firmware.zip.
Edit: Another question. Is that firmware applicable for my device?
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
ckpv5 said:
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
Click to expand...
Click to collapse
That would be very kind of you, thanks. Though, i think I've already messed up my phone. I finally got to update with the firmware in the link. The RUU was going on smoothly as well, until it reached 38% when Error 155 showed up again. The phone then went on to the bootloader screen with no options for fastboot, restore or such. I restarted it and entered the bootloader. My firmware is being shown as 6.20.502.5 but when rebooting the phone it won't go past the screen with the HTC logo. I'd be extremely grateful if you could help me out of this mess.
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Big-Bonsai said:
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Click to expand...
Click to collapse
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Uninstall HTC Sync Manager but leave HTC USB drivers then try again to run RUU after you put the device on bootloader/fastboot mode.
ckpv5 said:
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Click to expand...
Click to collapse
Yeah I did. I re-installed it later to see if it would show any information.
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
So I'm gonna try the RUU again. I'll keep you updated. You've been a big help. Thanks a lot!!
Big-Bonsai said:
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
Click to expand...
Click to collapse
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Jongla said:
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Click to expand...
Click to collapse
Hey man, thanks for replying here. I sent you a pm. Could you please check?
ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
Hello there. I kind of made it work. What I did was take the rom.zip from the ruu file and flash it via htc fastboot special. And it worked well. The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help. Do you have any suggestions for me?
Big-Bonsai said:
\The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help.
Click to expand...
Click to collapse
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Jongla said:
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Click to expand...
Click to collapse
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Click to expand...
Click to collapse
redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
Click to expand...
Click to collapse
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
redpoint73 said:
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
Click to expand...
Click to collapse
Man I searched EVERYWHERE. People dont seem to have any problems like this. What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?). Can you tell me if I did anything wrong?
Big-Bonsai said:
What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?).
Click to expand...
Click to collapse
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
redpoint73 said:
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
Click to expand...
Click to collapse
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps. I don't know if it's asking too much of you. Thanks anyways.
Big-Bonsai said:
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps.
Click to expand...
Click to collapse
Which version do you want to "convert" to?
Dev Ed is easy, it shares the same model ID (MID) as AT&T, and you already have SuperCID. So all you would need to do is run the MM Dev Ed RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Euro is a bit more steps, you would need to change to the Euro MID: http://forum.xda-developers.com/showthread.php?t=2708581
Then run Euro MM RUU, noting that relocking bootloader is not needed for you (since you have s-off): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
when i turn on my htc m9 it goes to bootloader and i have access to download mode and recovery mode (rooted TWRP) and i tried with so many RUU but always i get error 131 (RUU not matched with your CID )
my phone is UNLOCKED and S-ON i cant get it to S-OFF and change the cid :/
kernel: lk
product: htc_himawhl
version: 1.0
imei:
version-main: 2.11.651.19
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: SPCS_001
any solution ? or RUU for my MID and CID ?
Have you identified your MID & CID? This will be key in finding the correct RUU. The best resource is the SKU/CID/MID list by Sneakyghost & Behold_this (url below). Yes, we could look it up for you, but it's best to learn firsthand and will take just a minute or two.
Once you know your carrier and model, we can start searching for the matching. From your information, it looks like you're currently on Lollipop firmware, so we're talking about moving you to Marshmallow if it's available. This will get you the latest firmware and enable you to run the latest custom ROMs, if you should choose to do so.
Useful links for modding your HTC M9
Flippy498's Google Sheet
- the end-all, be-all resource for HTC M9 restoration
SKU-, CID- and MID-List by Sneakyghost and Behold_this
- a spreadsheet for using your CID & MID to identify your phone
HTC Sync Manager
- installs the necessary drivers & ADB tools for the HTC M9
Instructions for obtaining your CID, MID & software version on Windows:
a. Install HTC Sync Manager (this will install the necessary drivers & ADB tools)
b. Boot your phone into download mode (from a powered off state, turn on by holding the POWER+DOWNVOL)
c. Connect your phone to your PC
d. Open a command prompt window
e. Navigate to the ADB tools folder, typically C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
- assuming the path is correct, you can cut & paste this command into your terminal: cd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
f. Execute the following command in a terminal (command prompt): fastboot getvar all
g. Copy the lines that mention product, version-main, mid, and cid.
@computerslayer: It's actually easier to look at the line with "OS" at the beginning which can be found in download mode (it states the same information as version-main from getvar all) and to search for a RUU that corresponds to that firmware version. There is no need for finding out the device's CID or MID.
Edit: Besides of that all the needed information can already be found in the OP.
@djope47: Visit HTC's US website. They provide RUUs for US carriers. The search function of your browser and your version-main will probably lead you to the correct RUU. Newer versions with the same SKU (the numbers behind the second dot in the firmware version and before the third dot) should be fine, too.
Edit2: Or you look at the RUU collections which are linked in my thread (located in the general section).
Sent from my HTC One M9 using XDA Labs
i got my firmware from HTC site (sprint) and in the begging of flashing (0%) it gives me error-155 (same result with unlocked/relocked bootloader and S-ON) and when i try with zip file it tells me i dont have the correct CID
Flippy498 said:
@computerslayer: It's actually easier to look at the line with "OS" at the beginning which can be found in download mode (it states the same information as version-main from getvar all) and to search for a RUU that corresponds to that firmware version. There is no need for finding out the device's CID or MID.
Edit: Besides of that all the needed information can already be found in the OP.
Click to expand...
Click to collapse
Thanks Flippy! I appreciate the chance to learn more about the M9.
djope47 said:
i got my firmware from HTC site (sprint) and in the begging of flashing (0%) it gives me error-155 (same result with unlocked/relocked bootloader and S-ON) and when i try with zip file it tells me i dont have the correct CID
Click to expand...
Click to collapse
So you tried the M9 x.xxx.651.xx RUU from HTCs website while your phone was relocked and booted to download mode? Your phone definitely has the correct Sprint CID therefore it's not normal that you face that error. How did you try to flash the *.zip from stifilz's collection (or did you extract the *.zip from the *.exe by yourself - if so: what have been your exact steps?)? Did you use fastboot or have you tried the SD card method described in my google sheet?
I personally don't like the *.exe files or the fastboot method (which actually work the same way). They fail so many times due to little mistakes a user can make. The SD card method on the other hand doesn't rely on working USB cables, drivers, the correct USB port, and a relocked bootloader (so you can use it with an unlocked bootloader, too) or in some cases the correct windows version (some people have problems with win 10 whereas the same setup with win 7 doesn't produce a single error for them).
ive tried the sd card method (go to download mode then press volume up button ) and i got the failed msg ,i tried it with different x.xxx.651.xx RUUs all gives the same result
Is it possible to install ruu from the US developer version to HTC One m9 bought from other country ? (Dubai version )
i found this https://www.youtube.com/watch?v=xWmnHwkDrKk ,its the same problem that i have but its for htc one ,ist safe if i try it on htc m9 ?
djope47 said:
i found this https://www.youtube.com/watch?v=xWmnHwkDrKk ,its the same problem that i have but its for htc one ,ist safe if i try it on htc m9 ?
Click to expand...
Click to collapse
I didn't watch the video, but I can tell you that he is using an HTC One M7 and that I wouldn't follow instructions for anything other than your phone model (HTC One M9).
i noticed that all RUU.zip files that i downloaded are corrupted i cant extract them ,and the size of zip file is more than 2GB but the total size of the files inside it is like 70MB is this normal ? ive downloaded several RUUs and they are all with the same problem
They're encrypted and not meant to be unzipped. Therefore many programs can't handle those archives. If you use 7-zip and the #-method then you're able to unzip a RUU. However there is absolutely no reason why you should do that since they get flashed as a zip.
Sent from my HTC One S using XDA Labs
so what should i do ive tried what u said and didnt work out ! should i try this method https://www.youtube.com/watch?v=xWmnHwkDrKk ?? and in those RUUs they have the same CIDnum with my phone but the MIDnum mine is 0PJA10000 and the sprint RUUs have 0PJA20000
any solution ?
Oh yeah, I totally missed that. The MID with the 2 is the correct one for sprint. Did you buy your phone second hand? It looks like someone set is S-OFF, changed the MID and set it S-ON, again. Maybe that person flashed a RUU that's not compatible with that phone, too. You should try to find out the Serialnumber of the phone and contact HTC for finding out whether it really is a sprint phone or whether someone borked an international M9 (your current MID is the international one). GSM firmware and CDMA hardware are not compatible and vice versa. In the worst case it's unrecoverable.
If we know it's original firmware we might be able to fix the phone with a RUU. However I can't guarantee anything.
Btw, instructions how to flash RUU.zip files can be found in my google sheet, too.
Sent from my HTC One S using XDA Labs
all what you said i was the one who done that ! i bought it with s-off and with TWRP and i was trying to get it back to stock so i followed a guide that told me to change my MID to 0PJA10000 (its was 0PJA20000 at first )then i flashed a wrong RUU that was in the guide and i set it S-ON again ! i contacted htc they told me its sprint
any solution now ?
Flippy498 said:
Oh yeah, I totally missed that. The MID with the 2 is the correct one for sprint. Did you buy your phone second hand? It looks like someone set is S-OFF, changed the MID and set it S-ON, again. Maybe that person flashed a RUU that's not compatible with that phone, too. You should try to find out the Serialnumber of the phone and contact HTC for finding out whether it really is a sprint phone or whether someone borked an international M9 (your current MID is the international one). GSM firmware and CDMA hardware are not compatible and vice versa. In the worst case it's unrecoverable.
If we know it's original firmware we might be able to fix the phone with a RUU. However I can't guarantee anything.
Btw, instructions how to flash RUU.zip files can be found in my google sheet, too.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
all what you said i was the one who done that ! i bought it with s-off and with TWRP and i was trying to get it back to stock so i followed a guide that told me to change my MID to 0PJA10000 (its was 0PJA20000 at first )then i flashed a wrong RUU that was in the guide and i set it S-ON again ! i contacted htc they told me its sprint
any solution now ?
I guess you're talking about the "100%" guide here in the general forum. The problem is that it only applies to the international version of the M9. Since many users don't know that there is a dedicated forum for every US branded version of the M9 mistakes like yours may occur.
If possible flash a custom rom that is compatible with your current firmware and based on sense (like an old viper version for example). Then get the sunshine app and try to re-S-OFF your phone. If you're lucky and the previous owner used sunshine, too, you won't have to pay. If not you need to invest 25 bucks to recover your phone. After you got S-OFF you change the MID back to its original state. Afterwards you should be able to use the RUU.zip as described in my sheet.
Sent from my HTC One S using XDA Labs
Flippy498 said:
I guess you're talking about the "100%" guide here in the general forum. The problem is that it only applies to the international version of the M9. Since many users don't know that there is a dedicated forum for every US branded version of the M9 mistakes like yours may occur.
If possible flash a custom rom that is compatible with your current firmware and based on sense (like an old viper version for example). Then get the sunshine app and try to re-S-OFF your phone. If you're lucky and the previous owner used sunshine, too, you won't have to pay. If not you need to invest 25 bucks to recover your phone. After you got S-OFF you change the MID back to its original state. Afterwards you should be able to use the RUU.zip as described in my sheet.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
where can i find that custom rom ?or which one is the right one for my phone ? can you give me a link to it ? help me please im a noob
Being a noob is not an excuse for not using the xda search or google. The rom is even linked in my signature.
Link to Team Venoms Website
I guess version 3.5 should work fine for you.
Flippy498 said:
Being a noob is not an excuse for not using the xda search or google. The rom is even linked in my signature.
Link to Team Venoms Website
I guess version 3.5 should work fine for you.
Click to expand...
Click to collapse
damn man it worked thanks a lot
I recently got my hands on a One M9 but I'm having trouble updating anything on it. I check for updates and it says there aren't any available. However, my software version is 1.14.531.1, which is older than anything I've seen in any threads anywhere.
Here's the readout from fastboot getvar all:
kernel: lk
product: htc_himaul
version: 1.0
vzwisLTE:
vzwmid: HTC
max-download-size: 800000000
imei:
battery-status: good
version-main: 1.14.531.1
boot-mode: download
version-bootloader: 1.0.0.0000
mid: 0PJA12000
cid: 11111111
It doesn't say it here, but the phone is s-off.
I started by following the instructions at Cyanogenmod: unlocked, installed TWRP, installed ROM. However, it wouldn't install the ROM. It failed at the point where it tries to verify the device. I changed the recovery to the Cyanogenmod recovery and tried again, but that didn't work either. After a bit of reading, I thought that perhaps I needed to update the bootloader and that a RUU update might do the trick. I got the most recent one from HTC and ran it. It stalled where it says "sending" at 0%. I put the ROM.zip on the SD card to try it that way. That also failed. I relocked the bootloader and tried the RUU again with the same result.
I've wondered if I need to update the firmware per this thread http://forum.xda-developers.com/one-m9/development/firmware-t3068243 but I'm still new to the HTC world and not sure if that's it or if I'm just guessing. The firmware files I found there are much smaller than I expected, so I'm not sure what exactly they will update or if they'll fix the problem or just make it worse.
Can anyone tell me where to go from here, or at least point me in the right direction?
You can't flash offical firmwares unless your phone is stock. I think you should be ok flashing unsigned zips though. I couldn't tell you if htc do incremental or if you can just flash the latest. Flippy's thread might shine a light on something.. Your Cid is supercid.
Beamed in by telepathy.
So, are you saying that if I go back to the stock recovery that I should be able to use the RUU to update everything? There are a bunch of stock recoveries here, but none of them match my phone. The oldest ones there are several versions newer than mine and none match my CID. Can I still use one of them or do I need to find one that matches my phone exactly?
When I got the phone there was an SD card in it with a 0PJAIMG.zip file and a text file with a very long name with the software version (1.14.531.1) in it. Fortunately I saved them. I put those files back on and tried flashing that 0PJAIMG file and this time it worked. It seems to have removed the recovery I put on it and now it looks completely stock, with a locked bootloader and everything. Updating with the latest RUU still doesn't seem to work, however. It's still stalled at "sending" and 0%.
I would like to try a different RUU that's a smaller jump, but I haven't had any luck finding one yet.
OTA updates are incremental. A RUU on the other hand contains the whole firmware that has been distributed for its SKU until the point that RUU got released. Besides it contains the whole system. That's why RUUs are so big.
Sneakyghost's files lack some parts of the official firmware packs since they're not meant to get flashed if you want to get back to stock. They're meant to get flashed if you want to update your phone's firmware without reverting it's system back to stock since this way is less time consuming if you want to flash a new custom rom afterwards. That's why they're so much smaller than a RUU. Besides, they're unsigned and you won't be able to use them without S-OFF.
I personally don't like the *.exe versions of RUUs since they use fastboot and many users aren't able to set up their adb/fastboot environment correctly. Therefore, I neither support flashing RUU.exe files nor fastboot flashing of RUU.zip files. However if you extract the RUU.zip from the latest x.xx.531.x RUU.exe you could flash it via a SD card. I don't have a direct link to a guide for the extraction at the moment but there should be several here on xda which you should be able to find via google. It doesn't matter if they're written for an older HTC phone since the steps you need to do are always the same. Instructions for flashing a RUU via SD card can be found in my google sheet (which is linked in my signature).
And one last thing: The SCID prevents the M9 from installing OTAs. Therefore, you should revert it back to its original CID if you want to install any OTA.
Personal opinion: Since you can't use RUUs with a different MID than the one of your phone although you use the SCID (that was possible on older HTC phones) and you aren't able to install OTAs if you use it (that was possible on older phones, too) I personally don't think that there is any benefit left in using it.
Edit: I forgot to mention that there is a dedicated forum for the T-Mobile US M9 here on xda which can be found with the xda search function. You might find the files you need over there. Due to that other forum the T-Mobile US variant of the M9 isn't that much supported here in the forum for the international variant.
Sent from my HTC One S using XDA Labs
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
drfarmkid said:
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
Click to expand...
Click to collapse
I would say the phone is modified. As far as I know, test units don't need S-OFF or the SCID since they simply use different firmware versions than normal units. You can change every version of the M9 into a test unit by applying for HTCs beta program.
What was the error that got shown when the SD card method failed? Did you try to flash the correct RUU.zip for your phone? As mentioned before your MID needs to match even if the phone has the SCID. Therefore, you can only use x.xx.531.x RUUs.
Edit: I forgot to mention that every S-OFFed device runs that reporting software you mentioned if that device is running the stock rom. That Software gets triggered by the S-OFF flag.
Sent from my HTC One S using XDA Labs
Well, I managed to find the 1.32.531.33 RUU in the forum for the T-mobile variant (thanks flippy498 for bringing it to my attention) and that ran just fine. Once that was done I tried running the RUU I downloaded earlier from HTC (3.39.531.31) and it worked fine. It seems the problem was indeed that I just needed something that was a smaller jump. I've seen no mention of any software version earlier than 1.32 anywhere in this forum, so I wonder if my phone was an early test unit or something that the version 1.14 mine had was an earlier pre-release version or something and that is why I had the problems I did.
Thanks for the info regarding the reporting software running on all s-off phones. I saw something about red text in other threads and wondered if that's what it referred to. Now I know.
Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG10000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery (latest TWRP installed when download mode still working) or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)
jhon222 said:
Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG1000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)
Click to expand...
Click to collapse
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.) If you can't find a suitable RUU you'll need to contact Llabtoofer's RUU Service.
Flippy498 said:
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.)
Click to expand...
Click to collapse
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.
jhon222 said:
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.
Click to expand...
Click to collapse
Your phone seems to have a mediatek processor. Those devices need to get handled a bit different than snapdragon devices. However, I absolutely have no experiences with mediatek devices. If I were you I'd contact the service I linked in my earlier post...