Root [VZW] M7 stuck in ruu mode

[Eric Do]

I have an HTC One M7 stuck in RUU mode. It's a Verizon phone and I've moved to Tmo, and I was attempting to flash a Tmo ROM as described at http://htc-one.wonderhowto.com/how-to/get-your-htc-one-m7-ready-for-different-mobile-carrier-0151867.

First time through, the install failed, and I went back to recovery and restored my previous Verizon-supplied ROM. Second time through, I also entered the command "fastboot erase cache" as that was recommended, but it still didn't succeed with the install/boot. Now, I cannot get out of RUU mode and I can't flash a ROM successfully (both the one in the above link as well as Android Revolution HD for M7 fail).

I've also tried "fastboot reboot-bootloader" but that reboots me right back into RUU mode. Here's the output of "fastboot getvar all":

C:\Users\edocktor\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA425S904587
(bootloader) imei: 990004283555773
(bootloader) meid: 99000428355577
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3926mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.105s​

Any suggestions?

 

[Unforgiven]

I spun your post to its own thread in the M7 Verizon ATR section. I asked a couple of smart folks to have a look. Good luck.

 

[Eric Do]

Thanks. I'm racking my brain on this and I think there are two ways out of this mess, but I can't get either to work. One would be to get back into recovery mode, since I do have a valid backup. The other is to get this ROM to install. But every time I try, it ends with:

FAILED (remote: 51 partition update fail)
finished. total time: 303.409s
​

Any/all ideas welcome.

 

[scotty85]

you have,unfortunately been terribly mislead. that guide should be taken down,as running gsm RUUs on vzw or sprint cdma world phones is plain and simply a BAD idea. while in some cases the ruu may install correctly,things will not work correctly,and the phone is still only going to recieve the same vzw bands. running the t mobile ruu will NOT let you recieve t mobiles LTE or old skool 4g in non-refarmed areas.

your vzw device will work on t mobile's network just fine with the stock firmware.

my advice would be,if you have changed the MID allready:
1)change cid to 11111111 ( fastboot oem writecid 11111111 )
2)run a verizon RUU. be aware that the "failed: please flush again imediately" is typical,and you simply need to run the ruu again for it to complete
3)once youre back to a working phone,change cid and mid back to vzw

at any rate,you will be stuck in ruu mode until you flash something. in a worse case,you can pack up your recovery image and flash that in ruu mode,and it should let you out when its finished.

edit:
heres a vzw ruu: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442

 

[Eric Do]

Thanks Scotty85, makes sense. Unfortunately I'm still stuck. For one, my recovery image is on the device so I can't go that route until I can get back into recovery mode.

And the RUU route also seems to be blocked because I followed the instructions on that other page and changed the MID to a Tmo HTC One MID using something I installed and ran in TWRP. Now, any Verizon RUU seems to fail to install due to the bad MID. Is there a way to change the MID from the command line in Fastboot? I changed the CID, but it looks like I have to change the MID too before installing a Verizon RUU (or find one that doesn't validate the MID).

 

[scotty85]

Thanks Scotty85, makes sense. Unfortunately I'm still stuck. For one, my recovery image is on the device so I can't go that route until I can get back into recovery mode.

actually,what i meant was your recovery itself(twrp or whatever),not a backup. the recovery can be packed up with an android info document and installed via ruu mode. a recovery ruu,of sorts. usually it will let you out of ruu mode after a successful flash of something,but ive seen some cases where partition damage keeps you still stuck there. its worth a shot if the ruu fails.

And the RUU route also seems to be blocked because I followed the instructions on that other page and changed the MID to a Tmo HTC One MID using something I installed and ran in TWRP. Now, any Verizon RUU seems to fail to install due to the bad MID. Is there a way to change the MID from the command line in Fastboot? I changed the CID, but it looks like I have to change the MID too before installing a Verizon RUU (or find one that doesn't validate the MID).

there isnt a way to change your mid in your current state,thats why i recomended changing the cid to supercid(11111111) as that will also eliminate the model id check. im fairly certain that you can change your cid from ruu mode,as it is a part of fastboot,and most fastboot commands will still work.

failing that,as long as youre s off,we can modify the android info document in a rom.zip so that it will jive with your current variables. if this turns out to be the case,we will need to track you down a decrypted ruu so that it can be modified.

 

[Eric Do]

I am s-off. I successfully set the CID to 11111111 in fastboot, and then worked on this option:

we can modify the android info document in a rom.zip so that it will jive with your current variables

I was not able to find the android-info file in the vzw ROM linked earlier in this thread, but I found this one, downloaded it, unzipped it, changed the MID in android-info to match my MID, re-zipped it, and then tried to install it via fastboot:

http://forum.xda-developers.com/ver...tkat4-4-3-sense-6-s-off-t2867643/post55245618

All seemed to go well, but it looks like fastboot no longer likes the file format of the android-info file. Perhaps this is because I edited it in windoze.

target reported max download size of 1528414208 bytes
sending 'zip' (1466348 KB)...
OKAY [ 56.746s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 57.056s​

Thanks for the ideas/support so far. I feel like we're close to getting this device back.

 

[scotty85]

I am s-off. I successfully set the CID to 11111111 in fastboot, and then worked on this option:



I was not able to find the android-info file in the vzw ROM linked earlier in this thread, but I found this one, downloaded it, unzipped it, changed the MID in android-info to match my MID, re-zipped it, and then tried to install it via fastboot:

http://forum.xda-developers.com/ver...tkat4-4-3-sense-6-s-off-t2867643/post55245618

All seemed to go well, but it looks like fastboot no longer likes the file format of the android-info file. Perhaps this is because I edited it in windoze.

target reported max download size of 1528414208 bytes
sending 'zip' (1466348 KB)...
OKAY [ 56.746s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 57.056s​

Thanks for the ideas/support so far. I feel like we're close to getting this device back.

If you have successfully changed the Cid, then we should not have to modify the Android info document. Did you try and run the ruu that I linked above?

Or try the one that you downloaded, without modifying the document?

 

[Eric Do]

Even with supercid and s-off, it seems like it still performs the model # check:

target reported max download size of 1528414208 bytes
sending 'zip' (1445964 KB)...
OKAY [ 55.791s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 56.264s​

 

[scotty85]

Even with supercid and s-off, it seems like it still performs the model # check:

target reported max download size of 1528414208 bytes
sending 'zip' (1445964 KB)...
OKAY [ 55.791s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 56.264s​

hmmm thats not good. search the t mobile forum,and find a "firmware.zip" for a t mobile device. steal that android info document,and just swap the whole thing into your decrypted ruu. when editing the document,sometimes very small things can throw it off so the phone doesnt recognize it.