Develop Bugs

Flashing to stock rom,One X is this correct?

I've done my google searching, i really have. So I hope i didn't miss out on a sticky or anything else because i did check, if i didn't find it i must be blind. However,most guides I found to flash to stock rom were not on XDA. And just to be sure I've decided to come back over here and ask if this process is correct:
Also I am coming from ARHD 2.05.. so is a downgrade to 1.26 possible, do i need any kernels? Anyways here is how i'd proceed
1. Download stock recovery.img, put it in c:\fastboot
2. download the stock ruu for your specific phone
3. Boot phone into fastboot
4. open up cmd, in cmd type "cd\"
5. type "cd fastboot"
6. type in"fastboot flash recovery recovery.img"
7. type "fastboot oem lock"
(phone restarts in this case)
8. back in fastboot
9. open up stock RUU for your phone:
Agree to terms and just "next"(basically follow on-screen instructions)
... bla bla bla... and we have stock?
Is this processs correct?
Am I missing on anything, as i would be coming from ARHD.
Once again I apologize if this has been posted or if there's a guide on XDA, i've really done my searching, i just can't risk ruining this baby
Thanks in advance

This is roughly right yes. If you were on 1.26 before flashing a custom rom then you can flash the 1.26 RUU, and any higher version firmware (1.28, 1.29). if you were on 1.28 or 1.29 firmware then you cannot downgrade to 1.26, you will need to flash your current firmware version or higher. also with cmd, if you saved your fastboot file to c:\Android\fastboot then the command to get to that folder will be "cd c:\Android\fastboot"

teky said:
This is roughly right yes. If you were on 1.26 before flashing a custom rom then you can flash the 1.26 RUU, and any higher version firmware (1.28, 1.29). if you were on 1.28 or 1.29 firmware then you cannot downgrade to 1.26, you will need to flash your current firmware version or higher. also with cmd, if you saved your fastboot file to c:\Android\fastboot then the command to get to that folder will be "cd c:\Android\fastboot"
Click to expand...
Click to collapse
Does that mean I cannot get back to stock as of now? I found the 1.26 RUU and it's around 566.2 mb.
But before flashing I was on 1.29...

shadehh said:
Does that mean I cannot get back to stock as of now? I found the 1.26 RUU and it's around 566.2 mb.
But before flashing I was on 1.29...
Click to expand...
Click to collapse
you will need to find the 1.29 RUU for your phone then. have a search in HERE for the right RUU

teky said:
you will need to find the 1.29 RUU for your phone then. have a search in HERE for the right RUU
Click to expand...
Click to collapse
It's not released yet it seems. Okay, here my final question:
My final question:
So basically even though i am on ARHD 7.1.0 and have the latest firmware
I had 1.29 before flashing
I am only able to get back to stock if i have the 1.29 Ruu OR a NEWER version?(i know currently no newer official version present but assuming there is)
edit: me silly, i reread your first post and that's exactly what you stated. haha! Thank you anyway >_> guess i gotta wait for a RUU to be released

[Q] Unable to reset to stock

I've been trying to reset my HOX to stock for OTA JB update, but it keeps going into boot loops in which the only solution is to hold down the vol_down to go into bootloader.
I've been following vladnosferatu's method 2:
Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)
Extract boot.img, system.img, signed_recovery.img from rom.zip
Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot erase cache
-fastboot oem lock
Power on the phone
Run the RUU exe file (of your CID) and upgrade your phone
Click to expand...
Click to collapse
the bootloops start after oem lock.
I tried ClydeB1's noob-friendly method first, but it won't work since I'm already on 2.xxxxxxxx, and it refuses to downgrade to 1.xxxxxxxx
and I was on Renovate rom before this.
I have reset to Stock from Renovate once before, but now I can't seem to do it again. I have adb, fastboot and RUU(and extracted rom.zip)
What should I do? I've considered re-flashing CWM, flashing a Renovate again and restart the entire process, but I would like to confirm whether it would work first.
Thanks in advance for all responses!
UPDATE: I have just realised that there are 2.14 and 2.17 RUUs for my .707. I am now downloading those and trying if re-applying the steps using the updated RUUs will work.

Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!

if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.

donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
Because I have done this before perfectly fine, so I didn't expect anything to go wrong. I'd be sure to do it next time.
Seelendrache said:
if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.
Click to expand...
Click to collapse
My hboot is 2.x, but it's not even the JB hboot of 3.x. I have been able to flash ROMs just fine on 2.x, so why can't I revert to stock? The 2.x hboot is obtained from stock OTA in the first place, too.

Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
---------- Post added at 11:16 PM ---------- Previous post was at 11:15 PM ----------
donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
What are you doing here, Don ? Change phone ?

ckpv5 said:
Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
Click to expand...
Click to collapse
Hi ckpv5, I have also noticed that the 3.14.707 and 3.17.707 RUU has been uploaded. Can I just RUU the 3.17.707, skipping the manual 2.17.707? Because the only reason why I'm reverting to stock, is to update my hboot to 3.x, so that I can flash JB ROMs. Bypassing the 2.17-3.17 OTA would save quite some time.

Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.

-- question deleted cause I saw some numbers wrongly that caused confusion =/ --

Hehe no ....just got bored from the one v forums ...nothing new happening :thumbdown:

ckpv5 said:
Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Unfortunately this doesn't seem to work. The 3.14 gives me an error saying something about finding the right RUU for my device. Now downloading 2.17.707. Man htcruu downloads keep timing out halfway and I have to restart over and over :crying:
UPDATE: Yeah so it seems I had to RUU 2.17, and manually get 3.14 from OTA in order to upgrade. Can't skip that step.

HTC one X mainver 4.78.61.6 ICS.. HELP!!!!!!!!!!!!!!!!

I have an HTC one x that i bought has been rooted, on aftermarket software. Mainver is 4.78.61.6.. i am trying to return to stock.
I cant install RUU as the RUU available is ICS and can not downgrade as mainver is too high, nor can i obtain a JB RUU as a telecom nz JB ruu does not exist.
I have tried everything and searched fourms for months.
flashing ruu / firmware.zip or rom.zip always comes back with an error, signature error or mainver error. from what i can tell this mainver does not exist anywhere in the world it is FAR too high to even upgrade to any existing JB stock software.
i tried extracting rom.zip from telecom nz ics firmware and matching the mainver to be the same is the only way to return to stock using customRUU or ruu flash tool... BUT when it updates to the 4th or 5th update (system update just bofore the JB update) it freezes on boot, and does lots of weird things suck as booting into recovery / ruu / fastboot.
i have tried flashing telnz001 nandroid backup of ICS (JB not available)
everything is returned to factory spec when i do this, relocked, stock recovery etc
its on an older version of hboot (the one included in stock telnz001)
Cant upgrade hboot.
tried misc tool to change mainver to 1.00.00.0 BUT IT DOESNT WORK.
ALL that will run on it is a aftermarket rom.
IS there any other way to change the mainver?
would a nandroid backup of JB on telnz001 work?
why would it fail or play up on upgrades OTA ( mainver is NEWER than the OTA updates )
really need to return to stock and upgrade to JB
thanks

I don't seem to recognize that main version, can you check and tell me what your bootloader says. The top 3-4 lines .....

it
Mr Hofs said:
I don't seem to recognize that main version, can you check and tell me what your bootloader says. The top 3-4 lines .....
Click to expand...
Click to collapse
It says
***Unlocked***
ENDEAVORU PVT SHIP S-ON RL
HBOOD-1.12.0000
CPLD-None
MICROP-None
RADIO 0-5. 1204. 163r. 30
(is that what you wanted ?

Hmm i don't see a ruu with that number anywhere, and also no "new" stock nandroid backup
What's your exact cid
Fastboot oem readcid

Mr Hofs said:
Hmm i don't see a ruu with that number anywhere, and also no "new" stock nandroid backup
What's your exact cid
Fastboot oem readcid
Click to expand...
Click to collapse
TELNZ001

I think you are out of luck.....i can't find any useful info on your main version. Sorry mate..... Like you said, no ruu no matching firmware....

Mr Hofs said:
I think you are out of luck.....i can't find any useful info on your main version. Sorry mate..... Like you said, no ruu no matching firmware....
Click to expand...
Click to collapse
The Main version is reading 3.27.000.0 now after installing latest carbon 4.2.2 if this helps any

You need the main version that comes out with fastboot command.
Fastboot getvar version-main
The main number on a custom rom doesn't say anything. When you flash a wwe rom it will change to something like 3.14.401 or 2.17.401 for example.
You need the main version that is embedded in the hboot version.
Do the fastboot command and check if its the same number as stated in the opening post. If its different it might be useful

Mr Hofs said:
You need the main version that comes out with fastboot command.
Fastboot getvar version-main
The main number on a custom rom doesn't say anything. When you flash a wwe rom it will change to something like 3.14.401 or 2.17.401 for example.
You need the main version that is embedded in the hboot version.
Do the fastboot command and check if its the same number as stated in the opening post. If its different it might be useful
Click to expand...
Click to collapse
Have and Mainversion now reads 3.27.000.0 and HBOOT is still 1.12.0000

So its not the one from the OP. But still i haven't seen this number around either

Mr Hofs said:
So its not the one from the OP. But still i haven't seen this number around either
Click to expand...
Click to collapse
Yeh I have looked and cannot find anything either any ruu I use gets to around 80% then crashes with wrong boot error , they are the Telecom ones.Frustrating as well .

Mainver is higher than any mainver that exists for htc one.
I found out the androidinfo.txt in a zip file was updated in attempt to roll back software to ICS.
so basically i have two questions,
Is there ANY possible way to downgrade mainver. I have tried misc tool and cannot get it to work.
My other question is does anyone have a nandroid backup of JB for CID TELNZ001
and if i can get the backup all i need to do is upgrade the hboot. which i have also tried and have not been able to achieve.
Could someone please upload a backup image for cwm of JB TELNZ001 with updates included. and hboot file.
Or a firmware.zip with JB system, hboot, boot and recovery for TELNZ001.
thanks =]

im afraid there is nothing you can do...
if your hboot doesn't support JB you're out of luck
except hope that when sense 5 arrives it, comes with a higher main ver

misterr.mann said:
Mainver is higher than any mainver that exists for htc one.
I found out the androidinfo.txt in a zip file was updated in attempt to roll back software to ICS.
so basically i have two questions,
Is there ANY possible way to downgrade mainver. I have tried misc tool and cannot get it to work.
My other question is does anyone have a nandroid backup of JB for CID TELNZ001
and if i can get the backup all i need to do is upgrade the hboot. which i have also tried and have not been able to achieve.
Could someone please upload a backup image for cwm of JB TELNZ001 with updates included. and hboot file.
Or a firmware.zip with JB system, hboot, boot and recovery for TELNZ001.
thanks =]
Click to expand...
Click to collapse
thing is Telecom have brought out JB 4.1.2 and I cannot even get that to load back , stock was 4.1.1 any suggestions would help

Thing is. . I can update hboot.i have telnz001 hboot 1.39 i think. from memory. i just need to flash it. but i need the nandroid backup

You have hboot 1.12 that's a ics hboot, not a JB hboot.
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
aluria2012 said:
It says
***Unlocked***
ENDEAVORU PVT SHIP S-ON RL
HBOOD-1.12.0000
CPLD-None
MICROP-None
RADIO 0-5. 1204. 163r. 30
(is that what you wanted ?
Click to expand...
Click to collapse
Look this is what you wrote

Mr Hofs said:
You have hboot 1.12 that's a ics hboot, not a JB hboot.
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Look this is what you wrote
Click to expand...
Click to collapse
i like how thats from a different username.. i didnt write that lol
my username is misterr.mann
I wrote that i had a ics hboot im not denying that, the part you missed was i have the 1.39 hboot for jb, which i can flash and am flashing right this second, although its not going to help me as it fails on OTA update, so what im saying is once im on hboot 1.39 ill still have that EXACT same issue, as my main ver is higher than any one that exists it wont ota update. so once hboot 1.39 is on all i will need is nandroid backup of JB telnz001, literally all i asked for was this nandroid backup rom.zip or firmware.zip

My mistake :thumbdown:

Okay so my HTC one is reverted completly back to stock (used custom ruu with system.img boot.img androiinfo.text etc)
I had to edit android txt file to MATCH my existing mainver.
After 2.17 update phone boots, gets to o lock ring, and reboots. does this constantly... non stop. my main ver is still higher then cicomming update mainver is still 3.78
i have a file for OTA update zip
file name:
OTA_ENDEAVOR_U_JB_45_S_Telecom_NZ_WWE_3.17.781.2-2.17.781.3_release_304681lsq8o9k2p8n4minf.zip
now there is no RUU for JB
My question is how can i install this update, i still have hboot for ics 1.12.0000
contents in OTA_ENDEAVOR_U_JB_45_S_Telecom_NZ_WWE_3.17.781.2-2.17.781.3_release_304681lsq8o9k2p8n4minf
contains firmware.zip with hboot 1.39
so i can extract hboot file
i can fully extract the entire firmware.zip contained in the OTA update.
But am having issues flashing through fastboot, and in RUU mode it comes back 99 unknown error
Im stuck between a rock and a hard place as both options for update fail
i tried creating a firmware.zip containing android txt file with my current mainver hboot 1.39 boot.img and recovery.img
yet this update fails.
any help would be appreicated thanks

Returning to Stock from JB Maximus

Hi, I'm heading back to stock JB Sense from the original JB Maximus rom (which worked very well). I relocked in fastboot and went to flash original RUU (3.14.401.31) and I got the error message to use the correct RUU. My cid is HTC__001, it's from Clove UK. Do I need to change the HBOOT? It's from the first Maximus JB rom. It's just booting to the bootloader now. Thanks for any help!

Do this:
fastboot getvar version-main
and post the result here...

vin4yak said:
Do this:
fastboot getvar version-main
and post the result here...
Click to expand...
Click to collapse
3.09.401.100
Thanks very much!

Firs you need to update your firmware to 3.14.401.31 with Hboot 1.39..
Download (firmware): http://www.androidrevolution.nl/downloader/download.php?file=3.14.401.31.zip
And then run this RUU:
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/

Hi, thanks very much, that was the RUU I used but I'll try with that firmware and report back. Cheers for the prompt help!!

Hi, I've downloaded the firmware a few times but when I try to flash it I'm getting "cannot determine image filename for 'firmware.zip'
I moved the firmware download to my fastboot folder and renamed it firmware.zip. Then I did "fastboot flash firmware.zip" < EDIT YEP THAT was the problem
Thanks again!

Honestly at this point I'd just even go back to Maximus 4.1 at this point, but those threads all disappeared.
EDIT: I got the firmware updated, now going for the RUU

Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.

Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger

Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Click to expand...
Click to collapse
That's what I got the first time I tried to run the RUU, before flashing the new firmware. You may need firmware with a higher HBOOT to use this JB RUU. Once I flashed the firmware above, the RUU in this thread worked fine. I'm having some flashing now but heck, I had that when my phone was stock when I first got it, heh. I remember that issue now!

otarinz said:
Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.
Click to expand...
Click to collapse
Glad you sorted it out mate!
if you had just gone to stock to update... Then I will recommend you to use a custom sense rom if your attached to sense that much!
Use ViperX... It needs Hboot 1.31 at least..
Steps for flashing are the same as any other rom...
1. Wipe Data..Wipe Cache...Wipe Dalvic Cache... Or use Super Wipe Script(Recommended) : https://www.dropbox.com/s/0y31poo1kiaif4y/Super wipe script.zip
2. Flash rom. Flash Patch. (Check ViperX Thread)
3. Reboot.
Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger
Click to expand...
Click to collapse
You first have to update your firmware... Download this : http://goo.gl/M0hLq
and then run the ruu...

Hey there,
it sounds as if the HBOOT is in fact my problem. Quick question: How exactly did you flash the firmware, especially the HBOOT? I flashed the boot.img and recovery.img via command since I have no SD card access, but this doesn't seem to have changed the HBOOT.
Thanks again
Froschfinger

Relock the bootloader:
"fastboot oem lock"
Reboot RUU:
"fastboot oem rebootRUU"
Flash the firmware:
fastboot flash zip firmware.zip
You might get an error the first time you do it... try again until you get a successful message.
After successful flashing...
Go to fastboot again,,,
Now if you want to install a custom rom, you need to flash custom recovery by unlocking the bootloader... or if you want to go full stock then run the RUU...

Hey vin4yak,
that was the missing piece in the puzzle. Flashing the whole .zip file. Finally I got it working - thank you so much!!!!
All the best
Froscher

RUU update problem

Hi I have T mobile HTC one m8 which is running on firmware 4.20.531.5 .
Firmware 6.20.531.5 is out for T-mob so I donloaded RUU and before that RELOCKED the bootloader.
On fastboot screen it says RELOCKED.
So I went ahead with RUU installation ( downloaded from htc support website) and ran it.
I get error[155} unknown error with my phone displaying htc logo in white.
This error is due to bootloader not locked but mine is relocked.
I am pretty sure the RUU is correct and I can just go to bootloader screen only.
what should I do now?
Please help.

rahulsethi said:
Hi I have T mobile HTC one m8 which is running on firmware 4.20.531.5 .
Firmware 6.20.531.5 is out for T-mob so I donloaded RUU and before that RELOCKED the bootloader.
On fastboot screen it says RELOCKED.
So I went ahead with RUU installation ( downloaded from htc support website) and ran it.
I get error[155} unknown error with my phone displaying htc logo in white.
This error is due to bootloader not locked but mine is relocked.
I am pretty sure the RUU is correct and I can just go to bootloader screen only.
what should I do now?
Please help.
Click to expand...
Click to collapse
to bring it to top

rahulsethi said:
I get error[155} unknown error
Click to expand...
Click to collapse
This is a common problem for folks trying to go from LP to MM by RUU.
You'll need to find or extract the 6.20.531.5 firmware.zip, and flash it in fastboot RUU mode. Then the RUU should install properly.

Are you unable to get OTAs? If the RUU doesn't work, you can just keep updating the phone through OTAs. The function is found in Settings > About > Software Updates.

redpoint73 said:
This is a common problem for folks trying to go from LP to MM by RUU.
You'll need to find or extract the 6.20.531.5 firmware.zip, and flash it in fastboot RUU mode. Then the RUU should install properly.
Click to expand...
Click to collapse
How could I extract this firmware from exe file ? or do I have to find signed zip of this firmware ?
And should I flash it in adb by fastboot flash firmware firmware.zip ?

use this method to flash firmware T-Mobile first
download FW here
copy FW to folder adb fastboot
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip **frimware name.zip**
fastboot flash zip **frimware name.zip** - yes, 2 times
fastboot reboot-bootloader
atter that, you can flash RUU.exe

md07 said:
use this method to flash firmware T-Mobile first
download FW here
Click to expand...
Click to collapse
Yes, to the OP that is what you want (the full stock firmware if you are s-on . . . I believe that one is signed).
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
rahulsethi said:
How could I extract this firmware from exe file ? or do I have to find signed zip of this firmware ?
Click to expand...
Click to collapse
If you are s-on, it needs to be signed in order to flash it.
When you run the exe, it will make a ROM.zip in the WIndows temp folder, which is a zip version of the full RUU. You can extract firmware.zip from ROM.zip, but I don't know if its signed anymore after you extract it that way.

It worked
md07 you are the freaking man
redpoint73 said:
Yes, to the OP that is what you want (the full stock firmware if you are s-on . . . I believe that one is signed).
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
If you are s-on, it needs to be signed in order to flash it.
When you run the exe, it will make a ROM.zip in the WIndows temp folder, which is a zip version of the full RUU. You can extract firmware.zip from ROM.zip, but I don't know if its signed anymore after you extract it that way.
Click to expand...
Click to collapse

md07 said:
use this method to flash firmware T-Mobile first
download FW here
copy FW to folder adb fastboot
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip **frimware name.zip**
fastboot flash zip **frimware name.zip** - yes, 2 times
fastboot reboot-bootloader
atter that, you can flash RUU.exe
Click to expand...
Click to collapse
redpoint73 said:
Yes, to the OP that is what you want (the full stock firmware if you are s-on . . . I believe that one is signed).
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
If you are s-on, it needs to be signed in order to flash it.
When you run the exe, it will make a ROM.zip in the WIndows temp folder, which is a zip version of the full RUU. You can extract firmware.zip from ROM.zip, but I don't know if its signed anymore after you extract it that way.
Click to expand...
Click to collapse
Thanks guys! Finally had a chance to flash my firmware. However I flashed signed MM firmware from a thread by @ckpv5 instead of one you gave me @md07 as I was S-on
Thanks a lot @redpoint and @md07

Help please!
rahulsethi said:
Thanks guys! Finally had a chance to flash my firmware. However I flashed signed MM firmware from a thread by @ckpv5 instead of one you gave me @md07 as I was S-on
Thanks a lot @redpoint and @md07
Click to expand...
Click to collapse
I bought a htc one m8, its unlocked and now I just s-Off , but when i try to run the .exe RUU say the error [151] , the info of my device its:
***Software status: Modified***
***UNLOCKED***
CID-BS_US001
i just want the oficial developer edition 6.0 marshmallow, can someone help me?

seangtz said:
I bought a htc one m8, its unlocked and now I just s-Off , but when i try to run the .exe RUU say the error [151] , the info of my device its:
***Software status: Modified***
***UNLOCKED***
CID-BS_US001
i just want the oficial developer edition 6.0 marshmallow, can someone help me?
Click to expand...
Click to collapse
If updating to MM from LP (or KK for that matter) you need to first flash the MM firmware with the same number as the RUU. Its a peculiarity with US Marshmallow RUUs.