Related
Hi there,
I've got a rooted and S-off (Revolutionary) HTC Desire and I need to revert to stock ROM as the device is going for a repair.
Can I simply run the .exe RUU utility from HTC directly (htcdev.com/devcenter/downloads) to revert to stock or do I risk damaging my phone?
Many thanks.
No Expert said:
Hi there,
I've got a rooted and S-off (Revolutionary) HTC Desire and I need to revert to stock ROM as the device is going for a repair.
Can I simply run the .exe RUU utility from HTC directly (htcdev.com/devcenter/downloads) to revert to stock or do I risk damaging my phone?
Many thanks.
Click to expand...
Click to collapse
have a read of the convenient sticky post at the top of the Q&A thread
Hi, yes I did read it but I wasn't sure about something (I may just misinterpreted what I read).
The sticky says at (4):
[4]RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
Click to expand...
Click to collapse
So my question is: if I do use the official RUU on my rooted, S-off device will it:
(i) DEFINITELY fail (as described in the sticky), or
(ii) MAY fail if there is an unexpected issue.
In other words if it will definitely fail, then I will not do it and look at another option.
Thanks for your help.
No Expert said:
Hi, yes I did read it but I wasn't sure about something (I may just misinterpreted what I read).
The sticky says at (4):
So my question is: if I do use the official RUU on my rooted, S-off device will it:
(i) DEFINITELY fail (as described in the sticky), or
(ii) MAY fail if there is an unexpected issue.
In other words if it will definitely fail, then I will not do it and look at another option.
Thanks for your help.
Click to expand...
Click to collapse
It is (ii) that you may fail if there is an unexpected issue.
If you did change your hboot after you s-off, you need to flash the hboot downgrade first, so when the hboot is unlocked then it is usually safe to flash the official RUU.
I did flash official RUU two times since I have my desire and there was not problem at all for me.
Edit : flashing downgrade hboot will not harm your phone even though you may not change your hboot after s-off, it will just unlock it. When the hboot is unlock it is always safer to flash RUU
No Expert said:
Hi, yes I did read it but I wasn't sure about something (I may just misinterpreted what I read).
The sticky says at (4):
So my question is: if I do use the official RUU on my rooted, S-off device will it:
(i) DEFINITELY fail (as described in the sticky), or
(ii) MAY fail if there is an unexpected issue.
In other words if it will definitely fail, then I will not do it and look at another option.
Thanks for your help.
Click to expand...
Click to collapse
Go to alpharev.nl, download and flash the stock hboot, then the downgrader, then run the RUU
bortak, worked perfectly and was able to return device to stock for repair by HTC under warranty.
Thanks.
Hello.
For 2 days now, I have been trying to unlock a DHD,with not much luck so far. (AAHK being disabled just when I needed it.)
I am now trying to use the official HTCDev bootloader unlocker, but it doesn't seem to work either.
So far, my rom is still stock. (The phone tells me it is :
sense 3.0,android 2.3.5, ver 3.12.405.1 ,
HBOOT 2.00.0027
Radio 26.14.04.28_M )
The phone was never branded or somlocked.
It SHOULD be supported by HTCDev. However,when I run the RUU update, It asks me if I want to go from 3.12.405.1 to 3.13.000.0
I say yes.
The phone reboot to Fastboot, and then I get an error 191, saying that my rom is not supported and I should wait for an update.
Since it supposed to be supported already, there will be no update of course.
Earlier, I had tried to manually downgrade following this guide :
http://forum.xda-developers.com/showthread.php?t=1424023
I had gone to the end of the guide, having the message "your card is now gold",but couldn't seen to use it to downgrade. (Is there a specific way to use a goldcard ? I just got to bootloader and it seems to load something ... but in the end the hboot version doesn't change.)
I kept the goldcard as it was, and used another micros SD.
I did a factory reset before trying HTC dev unlocker.
Now I am a bit lost. I have tried to find what to do by reading posts, faqs, and generally searching here ot with google.
But I seem to go from outdated to incomplete guides, and / or lack the basics to understand what I read.
Does anyone know what my next step should be ? What could prevent HTCdev unlocker from working ?
kaceps said:
Hello.
For 2 days now, I have been trying to unlock a DHD,with not much luck so far. (AAHK being disabled just when I needed it.)
I am now trying to use the official HTCDev bootloader unlocker, but it doesn't seem to work either.
So far, my rom is still stock. (The phone tells me it is :
sense 3.0,android 2.3.5, ver 3.12.405.1 ,
HBOOT 2.00.0027
Radio 26.14.04.28_M )
The phone was never branded or somlocked.
It SHOULD be supported by HTCDev. However,when I run the RUU update, It asks me if I want to go from 3.12.405.1 to 3.13.000.0
I say yes.
The phone reboot to Fastboot, and then I get an error 191, saying that my rom is not supported and I should wait for an update.
Since it supposed to be supported already, there will be no update of course.
Earlier, I had tried to manually downgrade following this guide :
http://forum.xda-developers.com/showthread.php?t=1424023
I had gone to the end of the guide, having the message "your card is now gold",but couldn't seen to use it to downgrade. (Is there a specific way to use a goldcard ? I just got to bootloader and it seems to load something ... but in the end the hboot version doesn't change.)
I kept the goldcard as it was, and used another micros SD.
I did a factory reset before trying HTC dev unlocker.
Now I am a bit lost. I have tried to find what to do by reading posts, faqs, and generally searching here ot with google.
But I seem to go from outdated to incomplete guides, and / or lack the basics to understand what I read.
Does anyone know what my next step should be ? What could prevent HTCdev unlocker from working ?
Click to expand...
Click to collapse
You need to update your hboot for HTCDEV tool to work. I don't know why but the links in the site seem to have been removed thou the link is still alive.
Try to use this tool (that will guide you through the process) http://forum.xda-developers.com/showthread.php?t=2133336 or use this tool (that will unlock the bootloader, flash CWM recovery and root) http://forum.xda-developers.com/showthread.php?t=2169515
glevitan said:
You need to update your hboot for HTCDEV tool to work. I don't know why but the links in the site seem to have been removed thou the link is still alive.
Try to use this tool (that will guide you through the process) http://forum.xda-developers.com/showthread.php?t=2133336 or use this tool (that will unlock the bootloader, flash CWM recovery and root) http://forum.xda-developers.com/showthread.php?t=2169515
Click to expand...
Click to collapse
I tried both those utility, but they merely download and launch the same RUU update. It will detect a 1.00.000.00 image version, try to update to 3.13.something,and then tell me it can't due to unsuported rom.
I think the problem might be that I switched my version 1.00.000 manually when I was trying to downgrade. I'LL try reversing that, but if anyone has another idea, please ...
Edit :
Nope, still stuck.
I changed back the misc version to 2.00.0027, but the HTC dev ruu update still tells me that my rom is not supported.
Can't update hboot, can't get token, can't unlock
kaceps said:
Hello.
For 2 days now, I have been trying to unlock a DHD,with not much luck so far. (AAHK being disabled just when I needed it.)
I am now trying to use the official HTCDev bootloader unlocker, but it doesn't seem to work either.
So far, my rom is still stock. (The phone tells me it is :
sense 3.0,android 2.3.5, ver 3.12.405.1 ,
HBOOT 2.00.0027
Radio 26.14.04.28_M )
The phone was never branded or somlocked.
It SHOULD be supported by HTCDev. However,when I run the RUU update, It asks me if I want to go from 3.12.405.1 to 3.13.000.0
I say yes.
The phone reboot to Fastboot, and then I get an error 191, saying that my rom is not supported and I should wait for an update.
Since it supposed to be supported already, there will be no update of course.
Earlier, I had tried to manually downgrade following this guide :
http://forum.xda-developers.com/showthread.php?t=1424023
I had gone to the end of the guide, having the message "your card is now gold",but couldn't seen to use it to downgrade. (Is there a specific way to use a goldcard ? I just got to bootloader and it seems to load something ... but in the end the hboot version doesn't change.)
I kept the goldcard as it was, and used another micros SD.
I did a factory reset before trying HTC dev unlocker.
Now I am a bit lost. I have tried to find what to do by reading posts, faqs, and generally searching here ot with google.
But I seem to go from outdated to incomplete guides, and / or lack the basics to understand what I read.
Does anyone know what my next step should be ? What could prevent HTCdev unlocker from working ?
Click to expand...
Click to collapse
I have same issue
fahad4210 said:
I have same issue
Click to expand...
Click to collapse
I found what was wrong for me !
It came from my first try at manually downgrading. Except the misc version is not the HBOOt version, it's the rom version. Following the guide, I had set it to 1.00.000.0
I retraced the same step, except I set it to 3.12.405.1 ( the version of the rom ).
And it worked !
kaceps said:
i found what was wrong for me !
It came from my first try at manually downgrading. Except the misc version is not the hboot version, it's the rom version. Following the guide, i had set it to 1.00.000.0
i retraced the same step, except i set it to 3.12.405.1 ( the version of the rom ).
And it worked !
Click to expand...
Click to collapse
so what you did? Hwo did u manually downgrade it?
alvarado iondevi
fahad4210 said:
so what you did? Hwo did u manually downgrade it?
Click to expand...
Click to collapse
No.
After setting the rom version back to 3.12.405.1, I used the HTC unlocker to unlock my Hboot.
The automatic script ( easyUnlock and EasyAceUnlock ) didn't seem to work for me (Error while trying to get root.)
So I just installed Clockwork mod recovery. I don't really need to be root anyway. I just want some JellyBean taste.
But now I seem to be having a new problem. I tried to install a rom ( Wiping everything I can from CWM before ) but my phone won't boot. It is stuck to the green HTC logo.
I will be looking through new post from this forum to try to find a solution, while downloading other roms.
I wonder if some (or all) roms require you to be root to work.
kaceps said:
No.
After setting the rom version back to 3.12.405.1, I used the HTC unlocker to unlock my Hboot.
The automatic script ( easyUnlock and EasyAceUnlock ) didn't seem to work for me (Error while trying to get root.)
So I just installed Clockwork mod recovery. I don't really need to be root anyway. I just want some JellyBean taste.
But now I seem to be having a new problem. I tried to install a rom ( Wiping everything I can from CWM before ) but my phone won't boot. It is stuck to the green HTC logo.
I will be looking through new post from this forum to try to find a solution, while downloading other roms.
I wonder if some (or all) roms require you to be root to work.
Click to expand...
Click to collapse
You haven't flashed the boot.img in fastboot...that is a must when using an unlocked bootloader.
glevitan said:
You haven't flashed the boot.img in fastboot...that is a must when using an unlocked bootloader.
Click to expand...
Click to collapse
Indeed. Now starting the slow process of finding the right rom.
I will regret not being able to flash a radio ( since I'm not S-Off ) but at least I be able to try new roms.
Thanks !
hi,
for me works great with the HTC Easy Unlock Bootloader Tool from glevitan:good:
then i following this guide:
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
for noobs like me
works great
now i can flash all rooms they have an boot.img inside easily.
:victory::victory::victory:
Got my shiny new M8 today.
Was following Vomers excellent guide to get it ready for my custom ROM of choice however have hit some snags.
Wanted to get some advice before I get myself further into trouble...
Was able to unlock the bootloader OK via HTCDev and get root, TWRP installed per normal.
S-OFF with firewater failed, which is fine for some devices I know, so I thought I'd use Sunshine. This also failed with Viper ROM installed, so I installed MaximusHD, Sunshine also fails (incompatible ROM).
My CID is HTC__044.
HBOOT 3.16
My radio version now shows INVALID_VER_INFO
and OS is blank.
However the phone functions and I can use the mobile network OK...
Any tips as to how I can get to S-OFF so that I can install the firmware package again?
I'm pretty sure it had 1.54 before I started (I recorded it elsewhere)
Thanks
You need to restore your backup and it should then work and once S-OFF you can flash the FW package which will fill the blanks in again on the HBOOT
EddyOS said:
You need to restore your backup and it should then work and once S-OFF you can flash the FW package which will fill the blanks in again on the HBOOT
Click to expand...
Click to collapse
Of course - my 'backup'
The one I didn't make because I recklessly just jumped into rooting/SOFF given it was a new phone with none of my data on it....
I'll try the stockish package from mike1986 and see if I can get Sunshine to run. Fingers crossed
kamold said:
Of course - my 'backup'
The one I didn't make because I recklessly just jumped into rooting/SOFF given it was a new phone with none of my data on it....
I'll try the stockish package from mike1986 and see if I can get Sunshine to run. Fingers crossed
Click to expand...
Click to collapse
Mike's package is the EU unbranded phone (I think your phone is an Asian one) but it should do the job in terms of gaining S-OFF
EddyOS said:
Mike's package is the EU unbranded phone (I think your phone is an Asian one) but it should do the job in terms of gaining S-OFF
Click to expand...
Click to collapse
Yeah I know its limited CIDs and mine isn't included, I just want to be able to get Sunshine to run and then I should be back on track to super CID and S-OFF to get fw loaded properly.
It installed ok (from here in case anyone else managed to be as silly as me http://forum.xda-developers.com/showthread.php?t=2735235).
yay! Sunshine runs now. I am somewhat relieved...
Phone is now S-OFF and correctly reporting the radio and open DSP versions
delete
I made s-off after some attemps with firewater
When m8 will reboot, wait to see usb icon on screen device, than begins with shell commands
in superSU also "allow root when boot"
just so in the end it worked for me
S-Off Failed, now invalid Radio & OpenDSP, OS- (Blank)
Interesting Similar Posts_
I'm definitely not an advanced developer, but slowly learning my way around.
I have successfully unlocked and rooted my HTC One M8, and flashed only the Teamwin (TWRP) custom recovery v2.7.1.0 I have not flashed a custom rom and really do not intend to anytime soon --likely until I learn more. However, I wanted to go ahead and S-OFF. I attempted to use "Firewater", but it failed --"Welp . . . etc." During the attempts --after entering: "adb reboot" the installing htc driver process kept failing showing sometimes "MTP and debugging disconnected" and sometimes each just "failed". However, the phone shows both connected, and adb commands continue to work just fine. However, S-OFF continued to fail. Then I noticed that both HBoot lines Radio & OpenDSP showed "Invalid_Ver_INFO, and the OS- was blank.
Like one of posts; I do not have a back-up of my phone (nandroid) immediately after rooting, but as I said, I have not flashed a custom rom. Otherwise, my personal data is backed-up. Should I have flashed the custom recovery twice similarly as mentioned about flashing the stock rom instance described?
So far, I have only seen mention of "Sunshine" on XDA, and have been continuing to research first before I do anything else.
For now, my objective is to resolve the invalid notices in HBoot, and attain S-OFF. I don't really care about the "tampered" and "unlocked" flags for now --other than the hindrance of block of OTA Updates.
My pursuit of S-OFF has been pushed as I was trying to overcome the Ext SD-Card "write" block, when I noticed that Titanium uninstalls and other "write" file related actions would not remain permanent. The "app SD fixes" have not worked and the "manual fix" of permissions "Platform.xlm" file global ". . . media_ rw/" does not stay either. So subsequently, I began thinking/anticipating that the lack of S-OFF may be related to this problem. Perhaps I'm way-wrong on this point, but none-the-less I'm now pushing the resolution of my S-OFF issue also.
Guidance from anyone would certainly be appreciated. As addressed in the S-OFF post involving the mention of "Sunshine" I certainly don't mind paying the cost to gain S-OFF if it will work. I respect and appreciate the work of developers and often subsequently purchase Pro app versions simply to add donation to free versions etc. Sorry for the long post, and will be much shorter in the future!
Thanks for any help!
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.
i got a big problem!
i had root on my M8s and tried to fully unroot.
for that i used the function of the app SuperSU and fully unrooted my phone. perhaps my phone got stuck while booting and im in a bootloop. i can actually go to the fastboot but for using RUU i nead S-OFF which i dont have.. i also dont have USB-Debugging on anymore..
is there any possible way of comming out of an bootloop with s-on and without usb debugging? please help.
thanks!
S-on isn't needed to RUU, unless you mean to flash an "older" version RUU (downgrade from current OS number) or flash an RUU meant for a different CID.
Debugging is also not needed to RUU. Only fastboot is needed, which you said you have access to.
redpoint73 said:
S-on isn't needed to RUU, unless you mean to flash an "older" version RUU (downgrade from current OS number) or flash an RUU meant for a different CID.
Debugging is also not needed to RUU. Only fastboot is needed, which you said you have access to.
Click to expand...
Click to collapse
can you tell me what to do? i have no clue.
i tried putting the RUU file on my sd card and also put it in the phone and the only thing it responds me when trying to flash the image is :" parsing device halted due to large image update fail"
what should i do?
staen said:
can you tell me what to do? i have no clue.
i tried putting the RUU file on my sd card and also put it in the phone and the only thing it responds me when trying to flash the image is :" parsing device halted due to large image update fail"
what should i do?
Click to expand...
Click to collapse
Not sure how much I can help with that. I don't have the M8s (but rather the "standard" M8). So my knowledge of the "s" version is limited. What I posted before is general info, that applies to all M8 versions.
Make sure it's the proper RUU for your version. What is the exact file name or version number RUU? What OS number does it say on the bootloader screen?
Also, bootloader must be relocked, in order to RUU.
Beyond those things, I don't know what can be causing the "large image" error.