[Q]Installed Google Play Edition from RUU, now stuck at Fastboot? - One (M8) Q&A, Help & Troubleshooting

Hi,
So after fighting for hours, I managed to successfully use fastboot flash zip command to RUU the google play edition rom to my phone. However, the tutorial I followed didn't say I needed to match my CID and MID, so now I am stuck at the GPE fastboot bootloader. I can flash a custom recovery (I put TWRP on after the RUU was finished). However, since my phone is stuck at fastboot, I can't transfer any files to it using adb.
What I have: Fastboot, and TWRP recovery. Booting normally brings up Fastboot. Booting to recovery brings up TWRP.
My goal: Change my CID and MID so I can properly RUU the GPE rom to my phone. I think I can change the CID from fastboot but I don't think I can change MID from there.
What do you think? Am I going in the right direction? Did I make a wrong assumption?

In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589

hellhawk741 said:
In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Well I changed my CID and MID according to the thread (I edited the android-info.txt). However when I ran fastboot flash zip it failed with
FAILED (remote: not allowed)
Any ideas? It worked before, which confuses me as to why it's not working now.
EDIT: Nevermind I am an idiot. FAILED (remote: not allowed) means you need to reboot into RUU mode by using fastboot oem rebootRUU. However now I am back to where I started.
I successfully RUUed the Google Play rom, but now my phone only boots to the bootloader and fastboot.

I'm confused by flashing the RUU, if you have an ext SD card you can copy the image there rename it, boot and it will install itself. There is a rooted image available in the Android Development forum by GrafxNYC. I followed his instructions there and it worked perfectly.

Assuming the RUU file is not an exe file, move it to your SD card and rename it to match your MID exactly and reboot into bootloader. It should flash without a problem.

Ive been wrestling with this since last Saturday but I've finally got the GPE rom working. I couldn't tell you what I did, because I've gotten sidetracked and backtracked a bazillion times. I need to make a new thread though, the GPE rom is *extremely* unstable and crashes very frequently

Related

HTC One - stuck in bootloader/fastboot and no recovery

As you can see in the picture the phone boots up to this screen. A friend of mine bought an HTC One on ebay and he found out it was rooted/unlocked so he went to put it back to stock and may have bricked the device while doing so.
EDIT: so I am able to use fastboot, but not adb because I can't get into Windows. Flashing the stock Verizon RUU I found still doesn't get me anywhere though.
Is there any hope for this device? Thanks in advance!
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
cmlusco said:
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
Click to expand...
Click to collapse
Yea I saw that after messing around with it some more. It is Windows 7 x64.
I tried the one at the bottom of the page as I can't find one anywhere else. I also used the commands at the bottom to try and flash it.
http://www.htc1guru.com/downloads/ruu-zip-downloads/
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
cmlusco said:
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
Click to expand...
Click to collapse
OK cool I will try that once it downloads. It shows "My HTC" in the device manager. Also with the fastboot devices command it does give me the device ID.
EDIT: That worked! Thanks a lot for the RUU file, as I could not find that anywhere.
Hello. A friend of mine has the same problem. She tried to flash this RUU: "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted" but the phone doesn't boot. Here is more info about the problem: http://forum.xda-developers.com/showthread.php?t=2688936
Can she flash the RUU posted here?
This is what the hboot says:
Unlocked
m7_wlv pvt ship s-off rh
cid-11111111
hboot 1.54.0000
radio 1.12.42.0906
opendsp v31.120.274.0617
os 1.10.605.10
Thank you very much.
She can, but since she is s-off, its better to flash the decrypted one. http://vzw1files.dyndns.org/RUUs/2.10.605.1/PN07IMG_M7_WL_JB_50_VZW_2.10.605.1_DECRYPT.zip
cmlusco said:
She can, but since she is s-off, its better to flash the decrypted one.
Click to expand...
Click to collapse
First, thank you very much. She changed the CID to VZW__001. That's not a problem, right?
Does the CID and MID have to be compatible with the RUU? She has this MID: PN0731000.
Downloading this RUU, will report back.
Again, thank you.
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
cmlusco said:
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
Click to expand...
Click to collapse
Hello again. Before we try to flash the RUU, I would like to ask you the steps to do it. This is what we gonna do:
1. Download RUU
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
And that's it? Nothing else is needed, right?
EDIT: we flashed the RUU. Now the phone boots always in fastboot. No matter what option we choose, the phone does nothing and goes back to fastboot. On the bottom of hboot there is a new line in red: "Active cmdline overflow! (1073 Bytes)"
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
cmlusco said:
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
Click to expand...
Click to collapse
Hello. We just did it, and still the same problem. We were reading that some people solved this by doing a downgrade to hboot 1.44. But I don't want to make this problem worse.
You can try it, its worth a shot. Just flash an older ruu. http://vzw1files.dyndns.org/RUUs/. Dont remember which one goes with 1.44
cmlusco said:
You can try it, its worth a shot. Just flash an older ruu. Dont remember which one goes with 1.44
Click to expand...
Click to collapse
You can't be more kind. We made a downgrade, and now we can use CWM again. (We did the downgrade before reading your post, so we didn't use an older RUU) Now thinking hwat should be the next step: flashing a ROM (custom or stock, mounting a pendrive) or flashing an older RUU or anything else. Again, dude, you're awesome.
I'm stuck in a similar situation and any help would be appreciated so I don't screw this up. I can get into the bootloader but not into recovery (gets to the first TWRP screen then reboots). Safe mode works fine too.
Win7 64bit
S-off
Rooted
Stock ROM
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW-001
HBOOT-1.54.0000
RADIO-1.12.42.0731
OS-1.10.605.8
I can get into ADB. Would just like to know if I need to flash a new RUU or should I flash updated TWRP first? And the proper commands so I don't botch this.
Any help would be greatly appreciated.
Thanks
I would try reflashing twrp first. http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
fastboot erase cache
fastboot flash recovery recovery.img
cmlusco said:
I would try reflashing twrp first.
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Didn't work. Got to the TWRP splash screen and back into the bootloop again.
Ok then i would do an ruu. http://vzw1files.dyndns.org/RUUs/
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip (may fail with flush error, just do the cmd again)
fastboot reboot
Hi,
Similar problem here.
This is my situation:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
CID: VZW__001
MID: PN0731000
Only fastboot. Can't access to recovey (CWM). Can't access to OS, so no adb.
Every time I try to RUU it gives the "Signature verify fail" message.
So, I tried encrypted ROMs (those at vzw1files. dyndns. org), and I could go a step forward; but the flashing hungs up after giving this messages:
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
Thanks in advance, I hope I didn't screw it up.
The problem is nicouy that you are s-on, and on the newest kk firmware. An s-on phone will not allow you to "downgrade" firmware, and we do not yet have the latest ruu available, at least to my knowledge. So your kind of screwed right now untill we get our hands on a kk ruu.

[Q] RUU failed. Now stuck on htc logo. Dead?

Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
gmdiesel05 said:
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
Click to expand...
Click to collapse
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
clsA said:
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
Click to expand...
Click to collapse
yes the second time it said device not found! In cmd window, i type adb devices and none there
This is what happens, and hangs there
C:\Users\Desktop\platform-tools>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.072s]
finished. total time: 0.073s
C:\Users\Cedrik\Desktop\platform-tools>fastboot flash zip RUU-HTC_One_M8_GPE_5.0
.1-3.11.1700.5.zip
gmdiesel05 said:
yes the second time it said device not found! In cmd window, i type adb devices and none there
Click to expand...
Click to collapse
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
clsA said:
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
Click to expand...
Click to collapse
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. now i cant flash a 2nd time
Click to expand...
Click to collapse
are you s-off ? is your phone a GSM M8 ?
Did you try the other method, just renaming the RUU to 0p6bimg.zip (<a 0 (Zero) not a capital o (O), naturally...)
What error do you get when the flashing of the RUU fails?
Like mentioned by clsA said, adb devices won't work in fastboot mode, it should be "fastboot devices" to check if it's connected
---------- Post added at 06:20 AM ---------- Previous post was at 06:18 AM ----------
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
Click to expand...
Click to collapse
You changed CID and MID I take it?
CID - GOOGL001
MID - 0P6B17000
Would have helped a bit if we had an idea what the error was.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
Yeah he said his phone is S-OFF in OP
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Click to expand...
Click to collapse
gmdiesel05 said:
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
Click to expand...
Click to collapse
just use the fastboot flash zip ruu.zip command again
clsA said:
just use the fastboot flash zip ruu.zip command again
Click to expand...
Click to collapse
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
gmdiesel05 said:
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
Click to expand...
Click to collapse
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
clsA said:
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
Click to expand...
Click to collapse
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything. Sorry you lost me here
maybe im not waiting long enough?
Click to expand...
Click to collapse
you have the file renamed just copy it to your Ext - sdcard and let the bootloader flash it
don't forget to delete or rename it on the sdcard before you reboot again or it will flash it again
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
Click to expand...
Click to collapse
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Method 1
No computer required. Everything else still required. s-off, super CID/gpe CID etc..
1. Rename the RUU zip file 0p6bimg.zip (if your hboot is looking for a different name then rename it to whatever it's looking for)
2. Place the zip on your external SD card
3. Power off your phone
4. Boot into Hboot (hold down vol down as you power on the device)
5. it will load the zip and ask you if you want to proceed
6. Say yes
7. Wait
8. Profit
Click to expand...
Click to collapse
Didn't say anything about flashing it in RUU mode.
BerndM14 said:
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Didn't say anything about flashing it in RUU mode.
Click to expand...
Click to collapse
i used
Method 2
ADB/FastBoot Method
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
you will the following message:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
Code:
fastboot reboot

Reverting to stock to sell - best method?

I bought an M8 last year, locked to vodafone UK (CID VODAP001). I have since unlocked through HTC-DEV, S-OFFed using sunshine, converted to GPE for a while, and am now using it on a developer CID (BS_US002) entirely stock in order to get the OTA lollipop update straight from HTC. I obviously have the tampered message and unlocked bootloader, I am looking to return it to stock as much as possible (apart from S-ON). I have been looking at this thread but am not sure if it will work. I was looking to keep stock lollisense. My question is do I need to change my CID/MID back to the original ones or can I leave them as is and remove the tampered message etc.
My guide will work but there are bits that aren't needed now we have the RUU. I'll post in the morning with proper steps as I'm my phone at the mo and links are a PITA on here!
EddyOS said:
My guide will work but there are bits that aren't needed now we have the RUU. I'll post in the morning with proper steps as I'm my phone at the mo and links are a PITA on here!
Click to expand...
Click to collapse
Much appreciated! I'll check back tomorrow.
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
EddyOS said:
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
Click to expand...
Click to collapse
Is there any way I can use regular fastboot instead of htc_fastboot? I'm on a mac..
Nope, the Google one doesn't work for some reason. HOWEVER, apparently there is an HTC version on the HTC Dev site, which might very well work...
https://www.htcdev.com/process/legal_fastboot_mac
Failing that you'll need to use a Windows PC
EddyOS said:
Nope, the Google one doesn't work for some reason. HOWEVER, apparently there is an HTC version on the HTC Dev site, which might very well work...
link
Failing that you'll need to use a Windows PC
Click to expand...
Click to collapse
I was getting failures with remote:32 header error when usng that fastboot, managed to get on a windows PC and all sorted now. Thanks for your help!
No worries, glad I could help. I take it all the locking/tamper removing went OK as well?
EddyOS said:
No worries, glad I could help. I take it all the locking/tamper removing went OK as well?
Click to expand...
Click to collapse
Everything went to plan, all back to stock apart from S-OFF now
EddyOS said:
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
Click to expand...
Click to collapse
Hey, just did all points but how to go back to s-on and get ride of "test device" info?
EDIT: nvm, problem solved by myself. Thanks for the tutorial

RUU.zip downgrade

downloaded 2.10.401.1.zip from flippy498 and renamed to 0PJAIMG.zip to debrand (h3g) and downgrade (cm13) my m9, booted to download mode presses vol up and it flashed, it gets right through to system.img_04 the fails with error failed: -2, 21: fail to flash via downloadzip. when i reboot i have to reflash recovery and a rom so is it done properly or do i have to keep trying to it fully completes.
Are you s-off ?
Must have that for downgrade...
Cid and Mid in the RUU must match the device...
Either change device....or unzip the RUU with 7-zip and check in the info.txt folder for the RUU cid and mid...
I personally change the device in terminal command window as I don't like unzipping files unless I have too...
Check those areas and try again....g
gregsarg said:
Are you s-off ?
Must have that for downgrade...
Cid and Mid in the RUU must match the device...
Either change device....or unzip the RUU with 7-zip and check in the info.txt folder for the RUU cid and mid...
I personally change the device in terminal command window as I don't like unzipping files unless I have too...
Check those areas and try again....g
Click to expand...
Click to collapse
thanks for the reply i have the international m9 unlocked bootloader s-off with cid__001 which goes with that file, it flashes ok till that steep then fails asks to power down and does just goes into boot loop and wont flash a rom but can flash recovery, trying a ruu.exe
all fixed must have been a bad download at the start, ruu.zip sorted it the ruu.exe kept coming back with battery under 30% even though it was at 100%.

M8 bricked, cant flash new rom neither restore backup

Hey guys,
Recently I have bought used m8 with custom rom. Seller said he sells it because after trying to do factory reset (thinking it could restore to stock) he lost any gsm signal, only wifi worked. I had some experience with flashing sony mobiles and lg few years ago, so thought it would be easy to install stock rom and use device again. Googled a bit about flashing HTC devices, then downloaded rom, after that had some dificulties with win 8 and htc drivers, so tried to put rom into sd, it was too small. Somehow managed to put rom into device, tried to flash, had some errors, tried another roms, got another fails, changed my cid and mid, played with locked/relocked things, that didn't help either. Tried to restore a nandroid backup, even if it says restore was successful, after i choose reboot, it only boots me in bootloader. Now i cant access twrp, my pc recognises phone, but none of adb commands work.
I apologise if anyone got similar problem, but tried to look for explainations on my own, and found nothing, so this is my last hope to get it working.
Any help or info will be appreciated, I also am very interested in what you guys are doing, so i could even donate for people who can help alot.
***RELOCKED***
M8_WLV PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OS-6.12.401.4 (6.12.401.4)
eMMC-boot 2048mb
If any info more needed, just write, ill add anything you ask.
iTrolis said:
***RELOCKED***
M8_WLV PVT SHIP S-OFF
CID-HTC__032
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OS-6.12.401.4 (6.12.401.4)
Click to expand...
Click to collapse
A big mistake has been made, either by you, or the previous owner. As you indicated the previous owner lost GSM signal, I would guess that person may be the culprit.
Here's what I mean: Your M8 version is Verizon, indicated by the product name M8_WLV. I can see from the OS number (6.12.401.4) that installation of Euro firmware was attempted.
The Verizon version is somewhat unique, in that its designed for use on US Verizon carrier's CDMA network (in addition to GSM, HSPA, LTE) and therefore has its own partition layout, radio firmware, etc. Trying to flash any other version's firmware to this device will not work, and may result in a permanent radio brick. Essentially, only Verizon firmware or RUUs should only be installed to this device. Unlike most other M8 versions, you cannot convert the Verizon M8 to another version by changing the CID/MID (after s-off) and flashing another version RUU.
Indeed, the OS number in parenthesis indicates a problem with the firmware. And I'll venture to guess that this line is also in red font (which also indicated a firmware problem).
Your best (and really, only) option is to try the proper Verizon RUU. A lot of times, this will fix the firmware, and get the radio to work. Although there is a possibility that its a permanent radio brick (as we've seen a number of times). Try the 6.21.605.3 RUU from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another couple mistakes that I can see:
There was never a need to relock the bootloader for what you are doing, since the device is s-off. Its not needed to do this in order to flash firmware or RUU (the main reason to relock bootloader) as this requirement is bypassed by s-off. A relocked bootloader won't interfere with the RUU I recommended. But it would hamper trying to install TWRP custom recovery.
adb won't work unless you are booted to Android OS, or in TWRP. Since neither of those are working, it is normal and expected that adb command won't work. Fastboot command should work, while booting into bootloader-fastboot mode (and only that mode). While fastboot is related to adb, there are important conditions and differences.
redpoint73 said:
Your best (and really, only) option is to try the proper Verizon RUU. A lot of times, this will fix the firmware, and get the radio to work. Although there is a possibility that its a permanent radio brick (as we've seen a number of times). Try the 6.21.605.3 RUU from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
If the latest RUU doesn't fix the radio signal, I suggest to install the lowest version 1.5x. as the lower version usually will fix the NV partition which related to radio and unbrick it. (This is what I read in VZW thread before)
ckpv5 said:
If the latest RUU doesn't fix the radio signal, I suggest to install the lowest version 1.5x. as the lowest version usually will fix the NV partition which related to radio and unbrick it. (This is what I read in VZW thread before)
Click to expand...
Click to collapse
Good to know, I wasn't aware.
I think the 1.5x files would be here: https://forum.xda-developers.com/verizon-htc-one-m8/development/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
Edited my earlier post.
Your earlier link is good ... click 4.4.4 RUU zip link, it's 3.28.605.4 RUU
The only way to reset the partition to out of the box stock is to flash your carrier's 4.4.4 firmware and the stock recovery for you device. Reboot to recovery and select factory data reset and let it do it's thing. If you watch the reset log you will see it mention resetting the NV partition.​
Source : https://forum.xda-developers.com/showpost.php?p=57453624&postcount=2
guys, thank you for help, downloaded latest .zip file, renamed it to 0P6GIMG.zip, did fastboot flash zip 0P6GIMG.zip and it shows this: target reported max download size of 1826
Invalid sparse file format at header magi
any ideas?
iTrolis said:
guys, thank you for help, downloaded latest .zip file
Click to expand...
Click to collapse
Try the 4.4.4 RUU as ckpv5 advised in his most recent post.
what if i have changed cid and mid thinking to make my device to international?
now my cid is HTC__032
and MID 0P6B12000
i have to change these to original for verizon?
iTrolis said:
what if i have changed cid and mid thinking to make my device to international?
now my cid is HTC__032
and MID 0P6B12000
i have to change these to original for verizon?
Click to expand...
Click to collapse
That's correct, you will need to change back to the Verizon CID and MID to run the RUUs, firmware. Sorry, I missed that in the details you provided.
Alternately, if you change to SuperCID (11111111) in most cases this will bypass the MID check (and save you some steps).
now got RUU mode with exclamation marks on the edges of screen..
changed cid to vzw__001, but now need to get to fastboot again, to change it to supercid and will try 6,0 ruu.exe 4,4,4ruu.exe and 6,0 .zip files i have downloaded
Edit: cid changed to supercid, still stuck on silver htc logo with 4triangles on the edges. cant find a solution...
Read this on how-to : https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your ruu.zip not the one in the guide.
At the end of the guide, you'll see there are 3 methods to install ruu.zip
tried your method and got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip rom.zip
sending 'zip'... (46028 KB) OKAY
writing 'zip'... FAILproject does not have sa key to decrypt rom
FAILED (remote: project does not have sa key to decrypt rom)
Execution time is 2(s)
already tried to do it with ARUwizard.exe and stuck on silver HTC letters with 4 triangles nad exclamation marks on the edges of the screen, cant boot to bootloader, and i dont have enough storage in SD card to put rom in it
edit: trying again with another .zip file, now got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip 1.zip
sending 'zip'... (1760932 KB) OKAY
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL24 parsing android-info fail
FAILED (remote: 24 parsing android-info fail)
Execution time is 56(s)
ckpv5 said:
Read this on how-to : https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your ruu.zip not the one in the guide.
At the end of the guide, you'll see there are 3 methods to install ruu.zip
Click to expand...
Click to collapse
another question, what should be there in that ruu.zip? downloaded few and there is one with rom.zip, adb.exe, ARUwizard.exe, alot of .dat files and bitmap images inside, others are only with boot-signed.img and android-info.txt
iTrolis said:
another question, what should be there in that ruu.zip? downloaded few and there is one with rom.zip, adb.exe, ARUwizard.exe, alot of .dat files and bitmap images inside, others are only with boot-signed.img and android-info.txt
Click to expand...
Click to collapse
What are those you downloaded ? Which link ?
In my earlier post, I specifically suggested this one : https://www.androidfilehost.com/?fid=95784891001604006
If in ruu.zip you downloaded has all those files, it means you need to extract the ruu.zip then run the ARUwizard.exe to install.
ckpv5 said:
What are those you downloaded ? Which link ?
In my earlier post, I specifically suggested this one : https://www.androidfilehost.com/?fid=95784891001604006
If in ruu.zip you downloaded has all those files, it means you need to extract the ruu.zip then run the ARUwizard.exe to install.
Click to expand...
Click to collapse
yes i have downloaded exactly this and two more, now extracted this, ran wizard and got error 171 usb connection error, tried another usb cable, another usb slot but same error, what could solve this?
Do you have latest HTC USB drivers installed ? As explained in this guide - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
where it says - first you need this ?
Also try with USB2.0, if running it with ARUwizard.exe (that also explained in the same guide in the link at the lower part).
Or take only the rom.zip then
htc_fastboot flash zip rom.zip
ckpv5 said:
Do you have latest HTC USB drivers installed ? As explained in this guide - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
where it says - first you need this ?
Also try with USB2.0, if running it with ARUwizard.exe (that also explained in the same guide in the link at the lower part).
Or take only the rom.zip then
htc_fastboot flash zip rom.zip
Click to expand...
Click to collapse
downloaded htc sync manager, uninstalled it, tried both usb cables on all three different usb ports, same 171 error, tried to flash zip, got this:
C:\Users\Vartotojas\Desktop\android-sdk-windows\platform-tools>htc_fastboot flas
h zip rom.zip
sending 'zip'... (46028 KB) OKAY
writing 'zip'... FAILproject does not have sa key to decrypt rom
FAILED (remote: project does not have sa key to decrypt rom)
Execution time is 3(s)
I downloaded the 3.28.605.4 ruu.zip to see what's going on here .. it's a signed RUU, you're not supposed to extract it. No normal zip archiver can extract it properly.
Rename the whole as ruu.zip or rom.zip then htc_fastboot it after you put the device in RUU mode
fastboot oem reboot RUU
fastboot flash zip ruu.zip (or rom.zip if you renamed it rom.zip)
fastboot reboot-bootloader
also make sure your windows extension is not hidden so it won't actually become ruu.zip.zip where you will have unable to load ruu.zip error
The whole
0P6BIMG_M8_WL_K444_SENSE60_VZW_MR_VERIZON_WWE_3.28.605.4_HSM_Radio_1.09.20.0926_NV_VZW_2.11_002_release_393779_signed_1.zip
is the rom.zip
ckpv5 said:
I downloaded the 3.28.605.4 ruu.zip to see what's going on here .. it's a signed RUU, you're not supposed to extract it. No normal zip archiver can extract it properly.
Rename the whole as ruu.zip or rom.zip then htc_fastboot it after you put the device in RUU mode
fastboot oem reboot RUU
fastboot flash zip ruu.zip (or rom.zip if you renamed it rom.zip)
also make sure your windows extension is not hidden so it won't actually become ruu.zip.zip where you will have unable to load ruu.zip error
The whole
0P6BIMG_M8_WL_K444_SENSE60_VZW_MR_VERIZON_WWE_3.28.605.4_HSM_Radio_1.09.20.0926_NV_VZW_2.11_002_release_393779_signed_1.zip
is the rom.zip
Click to expand...
Click to collapse
downloading that .zip again, but i think that RUU fail doesnt let me to work now, how can i access fastboot when im locked to that ruu fail screen? power+vol up then vol- just restarts me to that black screen with htc letters and four triangles on the corners of screen
type command
fastboot reboot-bootloader

Categories

Resources