Related
Its not clear to me if I need recovery my soft-bricked HTC Raider by doing a PH39DIAG.zip or running the right RUU???
With the RUU I get the following error:
"RUU, Security fail! Update fail!"
With the PH39DIAG.zip I don`t know where to get one.
Heeeeeeeeeeeeeeeeeeeeeelp!
If the RUU isn't working you probably need to flash the appropriate kernel. Were you using the all-in-one-toolkit? Try flashing back to the stock kernel, and run the RUU.
>>>If the RUU isn't working you probably need to flash the appropriate kernel.
I bought the phone soft-bricked to hboot. RUU is giving me the error I posted. I don`t know what ROM is on it so I don`t think I need to flash a kern.
Here are the things I have tried so far.
My HTC Raid (I am in Canada so don't know if this is a Bell or Rogers or who knows, I bought it white screened) is stuck in white screen with HTC logo. I took
the following steps:
Downloaded RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe
from
http://hotfile.com/dl/145619873/245....77.551061.02L_release_219561_signed.exe.html
--Ran RUU and the program noted I have image version 1.65.566.3 on my Radier
--Selected Update and tried to update to 1.65.631.1
--The Raider came up in the HTC/black backgroup and then gave the following ERROR[155] UNKNOWN ERROR.
--After exiting RUU and disconnecting the cable the phone shows along with the general hboot information on the phone "RUU, Security fail! Update fail!"
--Restarted phone with volumn down and power and it came up in hboot and showed the following error:
SD Checking
Loading...[PH39DIAG.zip]
No Image!
Loading...[PH39DIAG.nbh]
No image or wrong image!
Loading...[PH39IMG.zip]
No image!
Loading...[PH39IMG.nbh]
No image!
Loading...[PH39IMG.tar]
No image!
Loading...[PH39IMG.aes]
No image!
--I tried re-locking the bootload with "fastboot oem lock" and I get a "..." after the command and nothing else happens. Waited for 10 minutes.
--Also "adb devices" shows no devices.
--Installed HTCSync, started HTCSync, pluged in hbooted HTC Raider, Drivers Software Installation diolog box shows "My HTC" driver installed, still nothing when
I run "adb devices"
--Ran "fastboot oem lock" and get the following.
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.026s
--When I run Hasoon2000s HTC Vivid AIO Kit v1.2 Relock Bootloader I get the following.
INFOLock successfully
FAILED (status read failed (Too many links))
finished. total time: 0.022s
--With Hasoon2000s HTC Vivid AIO Kit v2.0 I get.
INFOLock successfully
FAILED (status read failed (Unknown error))
finished. total time: 0.023s
--reboot into hboot and status still "*** UNLOCKED ***"
hmmm, I haven't messed with this sort of thing of the Vivid so much, but I have on the flyer, and I've gotten the soft brick white HTC screen too, and typically what it means is the Hboot version doesn't support the firmware on there. I got no link but perhaps the developers have the Hboot version your looking for with the firmware you got.
Can you get into fastboot? If you can its just a matter of flashing the Hboot with ADB and then running the RUU
yes I can get into fastboot.
The hboot version i have is the same as my other Raider that is on rogers. On the working Raider I have 1.65.631.1 software number, 2.3.4 android version, 3.0 Sense, 2.6.35.13-gc1166ee kernel version, 1.11.1020.03_03.77.551061.02L bb, 1.65.631.1 CL175411 release-keys build number.
So the hboot is the same on both of them, they are both unlocked, and the working one has HOLIDAY PUT SHIP S-ON RL
don`t know if that helps or not.
The Reason You Are Getting That Error is because your bootloader is still unlocked, go into hboot go into fastboot and plug in via usb and it should say "Fastboot USB" in red then run the ruu.... once completed do a battery pull, go back into hboot unlock bootloader again, then install a custom recovery (i recommend WildChild's) then if you plan on using a custom rom... use a kernel supported or use the rom's kernel in the zip "Boot.img" flash that kernel put the rom on your sd card or go into wildchilds recovery go to enable usb-ms and enable internel sd card and put the rom in there disable usb-ms go to wipe clear the two caches then go into the main menu flash zip menu internel or externel sd card select the rom and install and you are good to go ! anymore help pm me i can help greatly
---------- Post added at 03:36 AM ---------- Previous post was at 03:24 AM ----------
Hmm sounds like you do not have the right htc drivers installed download the all in one tool kit and run the first few steps ! Download your ph39img.zip here http://goo.im/private/iomonster/htcvivid/roms/ics-ota/PH39IMG.zip
>>>The Reason You Are Getting That Error is because your bootloader is still unlocked
no it is *** UNLOCKED ***
>>>go into hboot go into fastboot and plug in via usb and it should say "Fastboot USB" in red
Yes
>>>then run the ruu....
times out with an error, here is my RUU
RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe
>>>Download your ph39img.zip here
what do I do with it. I put it on the sdcard and did a bootload and it gives the following errors.
SD Checking
Loading...[PH39DIAG.zip]
No Image!
Loading...[PH39DIAG.nbh]
No image or wrong image!
Loading...[PH39IMG.zip]
No image!
Loading...[PH39IMG.nbh]
No image!
Loading...[PH39IMG.tar]
No image!
Loading...[PH39IMG.aes]
No image!
Flash a proper recovery, then flash an gingerbread Vivid custom ROM and immediately flash the appropriate boot.img to go with it.
If it boots, you know you're on GB. Relock the bootloader in fastboot and run either the Telus or Bell ruu for GB. Try both before coming back.
>>>Flash a proper recovery,
I have flashed a number of proper recovery images.
From Vivid all in one kit v2.1 http://forum.xda-developers.com/showthread.php?t=1498003 I have tried to flash
recovery-cwm-vivid-5.5.0.4B2.img
wcxrecovery.img
and recovery.img from a back up by cwm on my other working Raider
"fastboot devices" gets me "HT1ALVJ03540" and when I go to fastboot on the hboot menu I get "FASTBOOT USB" in red.
I have used "fastboot flash recovery filename.img"
After all these flashes when I boot into hboot and select RECOVERY and press the power key it show a white screen with a green htc and then with in 1 sec goes back into hboot.
Prehaps is is of interest than when I run the RUU RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe it tells me I have image version 1.65.666.3 installed and wants to put 1.65.631.1 -- you can see that from the image name and the getvar all output below
Also I have extracted the rom.zip following http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/ from this RUU and renamed it PH39DIAG.zip and when it loads it hboot gives an "Wrong zipped image!" after "Checking..[PH39IMG.zip]"
Here is my fastboot getvar all info
INFOversion: 0.5
INFOversion-bootloader: 1.83.0014
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: 0360
INFOversion-main: 1.65.666.3
INFOserialno: HT1ALVJ03540
INFOimei: 358730040049371
INFOproduct: holiday
INFOplatform: HBOOT-8260
INFOmodelid: PH3915000
INFOcidnum: BM___001
INFObattery-status: good
INFObattery-voltage: 4075mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: ccb23700
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.514s
The image that is on this bricked Raider appears to be a bell ICS ROM.
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1672800
When I run RUU I get a "ERROR 155 UNKNOWN ERROR" in the RUU program and if I unplug the phone it shows RUU Security fail! Update fail!
>>>then flash an gingerbread Vivid custom ROM and immediately flash the appropriate boot.img to go with it.
I cant get a recovery to take so I am guessing I need to fix that before going on to a custom ROM?
I had a similar problem with bell ics bootloop. I flashed kozmicks r2 from fastboot, and used darkraider 1.5.4.zip from recovery. Device was s-on at the time.
@RagnarDanneskjold you have links to those two files
Kernel http://forum.xda-developers.com/showthread.php?t=1572015
Dark Raider http://forum.xda-developers.com/showthread.php?t=1586613
bobmutch2 said:
@RagnarDanneskjold you have links to those two files
Click to expand...
Click to collapse
@Maqical
Thanks.
If you are still having trouble you can PM me.
The kernel didn`t take.
>>>flash the kernel from fastboot
Here is what I get when I flash the kernel
"fastboot devices"
gets me "HT1ALVJ03540"
"fastboot flash boot Kernels/KozmiKKernel-RC2.zip"
gets me
sending 'boot' (5480KB)... OKAY [1.332s]
writing 'boot' ... FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.652s
Not exactly sure so dont depend on me for this.. but when i flash my kernels i have a "boot.img" and you put it in with the files for fastboot and i open a command window and type "fastboot flash boot boot.img, you're flashing a zip
bobmutch2 said:
The kernel didn`t take.
>>>flash the kernel from fastboot
Here is what I get when I flash the kernel
"fastboot devices"
gets me "HT1ALVJ03540"
"fastboot flash boot Kernels/KozmiKKernel-RC2.zip"
gets me
sending 'boot' (5480KB)... OKAY [1.332s]
writing 'boot' ... FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.652s
Click to expand...
Click to collapse
Refer to this link:
http://forum.xda-developers.com/showthread.php?t=1416836
Find the boot.img file for kozmicks kernel. You can download it or extract it from
darkraider.zip.
Place the boot.img file in you fastboot folder on your computer.
Run the following commands in fastboot
fastboot flash boot boot.img
fastboot reboot
Now you must flash a custom recovery. CWM, or WCX will work.
You can use all-in-one-toolkit to do this.
From recovery install darkraider from .zip.
Folllow instructions, use defaults.
@RagnarDanneskjold
In darkraider_v1.5.5.zip there is 5 kernels faux, holics, kozmikb7, kozmikrc2, and stock, they all have boot.img but kozmik b7 and rc2?
Which one would I use?
I am not sure if have read all I have posted. I cant write stuff to this device. kernels dont take, recovery images dont take, the PM39IMG.zip doesn`t take. There is some issues here more than just finding the right files to flash.
I used 1.5.4 because s-on compatibility has been dropped in newer versions, (so I understand?), so I would use that version. Take the boot.img from kozmiksrc2. Make sure you select it when installing darkraider.
A Kernel of your choice.. but for now just until you get the phone working i would use stock
bobmutch2 said:
@RagnarDanneskjold
In darkraider_v1.5.5.zip there is 5 kernels faux, holics, kozmikb7, kozmikrc2, and stock, they all have boot.img but kozmik b7 and rc2?
Which one would I use?
Click to expand...
Click to collapse
Hi XDA
I have a problem.
I was gonna upgrade my HTCDEV unlocked Incredible S with CM7 to Ice Cold Sandwich.
So i tried flashing the ICS .zip and when i rebooted it was stuck on splash screen.
I figured this was because I was on an incompatible firmware version so I decide to flash the latest ICS RUU.
I start by relocking the bootloader and after that run the RUU.
About halfway through it stops with an error message.
Now I can only boot into bootloader, pressing the recovery tab just opens fastboot menu, if I try to run the RUU again it stops immediatly with error 170 and if I try to install a recovery manualy i get the error FAILED (remote: signature verify fail)
Only thing that works is fastboot commands
How screwed am I?
frederikh said:
Hi XDA
I have a problem.
I was gonna upgrade my HTCDEV unlocked Incredible S with CM7 to Ice Cold Sandwich.
So i tried flashing the ICS .zip and when i rebooted it was stuck on splash screen.
I figured this was because I was on an incompatible firmware version so I decide to flash the latest ICS RUU.
I start by relocking the bootloader and after that run the RUU.
About halfway through it stops with an error message.
Now I can only boot into bootloader, pressing the recovery tab just opens fastboot menu, if I try to run the RUU again it stops immediatly with error 170 and if I try to install a recovery manualy i get the error FAILED (remote: signature verify fail)
Only thing that works is fastboot commands
How screwed am I?
Click to expand...
Click to collapse
The mistake you made was not manually flashing the boot.img file from the ICS ROM.zip since you had the unlocked bootloader.
Which RUU are you trying to install? You may just need to extract the ROM.zip from the RUU and copy that to your sd card and rename it PG32IMG.zip. Then when you reboot into the bootloader it will attempt to load it.
tpbklake said:
The mistake you made was not manually flashing the boot.img file from the ICS ROM.zip since you had the unlocked bootloader.
Which RUU are you trying to install? You may just need to extract the ROM.zip from the RUU and copy that to your sd card and rename it PG32IMG.zip. Then when you reboot into the bootloader it will attempt to load it.
Click to expand...
Click to collapse
RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
frederikh said:
RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
Click to expand...
Click to collapse
OK then just extract the ROM.zip from the %TEMP% directory as I previously suggested and you should be good to go.
tpbklake said:
OK then just extract the ROM.zip from the %TEMP% directory as I previously suggested and you should be good to go.
Click to expand...
Click to collapse
Well...
The RUU shots down before the rom.zip is extracted to the temp folder.
But if you think this will work, would you then mind running the RUU yourself and upload the rom.zip somewhere where I can dl it?
If you have a compatible phone that is
Thank you
frederikh said:
Well...
The RUU shots down before the rom.zip is extracted to the temp folder.
But if you think this will work, would you then mind running the RUU yourself and upload the rom.zip somewhere where I can dl it?
If you have a compatible phone that is
Thank you
Click to expand...
Click to collapse
Run the RUU without the phone connected. Just leave it sit on the first screen and then you can find the ROM.zip in the %TEMP% directory.
tpbklake said:
Run the RUU without the phone connected. Just leave it sit on the first screen and then you can find the ROM.zip in the %TEMP% directory.
Click to expand...
Click to collapse
It's working!!
Thank you very much
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
You've had an htc one for two years?
BableMan said:
You've had an htc one for two years?
Click to expand...
Click to collapse
No. Started out with my Nexus S, then moved to a Nexus 4, then gave that to my wife and got an HTC One. I love this phone so much I wish I'd had it for two years already, but no.
Do you have any idea of a new path I can try?
misterasset said:
After flashing updates regularly for over two years I do not know what I have done to mess my phone up this bad, but I did. There is no more file structure on the phone whatsoever. Nothing. At all.
Currently I can boot into Bootloader or I can boot into CWM Touch Recovery.
Whenever I go to "Install a Zip" using Recovery, there is no option to choose anything because there is no file structure.
Whenever I go to "Install a Zip from Sideload," and ROM file I send to it returns with a Status 7 error. I read online about removing the PROP comments from the update-script to fix the Status 7 error but that did not work, still got a Status 7 error.
I downloaded the RUU for the correct CID, there were two, and both of them fail with Error 155 Unknown Error.
I'm at my wit's end here and am pretty afraid I have bricked my phone. Would anybody here be willing to try to steer me out of the mess I have created?
Thank you,
Chris Williams
Click to expand...
Click to collapse
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Sent from my HTC One using Tapatalk
Delgra said:
Just to know.. Did you try to flash a RUU.exe or a RUU.zip? I had a lot of problems with the .exe files, while flashing the RUU.zip from command line usually work like a charm to me.
Click to expand...
Click to collapse
I have tried both actually. I used Hansoon2000's (I'm at work so hopefully I'm referencing that correctly) all in one toolkit to try to flash the RUU.zip file back to the device. It fails while transferring to the device every single time.
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
How do I flash the RUU.zip from the command line? I have tried using "Install zip from sideload" but I get a Status Error 7 when trying to flash ROM.zip files, and I have tried using ADB PUSH to push the ROM.zip over to the phone but since there's no file structure it doesn't really ever end up anywhere on the phone. (I'm using ROM.zip generically here for my CM ROMs, not RUU) Is there a command line or ADB function to flash the RUU.zip file that I'm not aware of?
Thanks,
Chris
misterasset said:
So next I tried to use the RUU.exe, both a newer and older version, for my CID and I get the mysterious Error 155 Unknown Error.
Thanks,
Chris
Click to expand...
Click to collapse
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
nkk71 said:
Error 155 -> you're probably on hboot 1.55+, so you need to downgrade hboot separately first, (to hboot 1.44) then you can run the RUU. download here: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then in bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot reboot-bootloader
-> confirm hboot is 1.44
and run RUU.
PS: you have to be s-off obviously.
Click to expand...
Click to collapse
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
misterasset said:
Thanks for the info. I'm actually on HBOOT 1.44 already luckily. But I am not S-Off. Is that why the RUU is not working? I tried to use the All-In-One Toolkit to achieve S-Off now, but without a file structure it didn't work.
Any direction on achieving S-Off while it's so messed up?
Thanks,
Chris
Click to expand...
Click to collapse
Please:
1- date of bootloader
2- a "fastboot getvar all" (remove IMEI and s/n)
3- link to the RUU you are trying to use.
Don't forget pressing the little thanks button for people who have helped
No offense but it sounds as if you simply aren't running an ruu.zip correctly. I'm not understanding all this hensonn2000 or toolkit talk that you have going on. You flash ruu.zip while the phone is in fastboot oem RUU mode. Not that complicated. Also the error 155 was the bootloader being unlocked if I recall correctly. You have to relock it before flashing or running the appropriate RUU. Specially if youre s-on.
Thanks guys. I ended up getting it all working. I did not have the Bootloader relocked and that was why the RUU kept failing.
Thanks again for the extra direction,
Chris
I'm sure(or at least hoping) this has been answered elsewhere, but after 6 hours of searching I'm in desperation mode. Here's where I'm at:
Brand new Sprint M8 HK edition
cid: SPCS_004
version_main: 1.54.654.13
modelid: 0P8B70000
radio: 1.05.20.0321_2
Rooted with SuperSU, TWRP 2.8.1 (2.8.3 won't work, gets stuck on loading recovery), S-ON
I thought I could flash http://forum.xda-developers.com/showthread.php?t=2706441 without being S-off, and stupidly did not make a backup. Flashing appeared to go fine, but after rebooting the phone goes straight to the bootloader. I can still access TWRP, and have tried to flash multiple ROM's/Firmware to get the phone in any working config, but no matter what I do I can't get anything to flash.
If I try to flash 1.54.654.9 Full Firmware from RUU from http://forum.xda-developers.com/showthread.php?t=2729173 I get the FAILED (remote: 99 unknown fail) error. Research said to lock the bootloader, which I did, but then I get the FAILED (remote signature verify fail).
The ultimate goal is to get stock android running on the M8(recently lost my Nexus 5 which I loved), but at this point I'd take any working OS so I can simply use the phone.
I've been using fastboot to flash as I don't have ready access to a microSD card reader.
Any help would be greatly appreciated, and met with BTC tips.
Download the ROM from the link below. Make sure you do a full wipe in recovery first. Then flash the ROM.
https://www.androidfilehost.com/?fid=23329332407590598
The full firmware you're attempting to install won't install because you're S-on and you cannot downgrade firmware while S-on. If this doesn't work you'll need to relock your bootloader and flash the latest RUU from the link you posted (software version 3.31.654.2).
Magnum_Enforcer said:
Download the ROM from the link below. Make sure you do a full wipe in recovery first. Then flash the ROM.
The full firmware you're attempting to install won't install because you're S-on and you cannot downgrade firmware while S-on. If this doesn't work you'll need to relock your bootloader and flash the latest RUU from the link you posted (software version 3.31.654.2).
Click to expand...
Click to collapse
Thanks for the reply. Downloaded the ROM you linked, got the following:
$ sudo fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49586 KB)...
OKAY [ 3.070s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 3.071s
Is that expected?
Yes, that's expected, because that's not how you flash a ROM.
Can you push the ROM to your phone and then try flashing it via recovery? You mentioned not having a microSD card reader but I presume you have a microSD card, correct? If so push the ROM to the card, do a full wipe in recovery (Dalvik cache, cache, data & system), then flash the ROM.
Magnum_Enforcer said:
Yes, that's expected, because that's not how you flash a ROM.
Can you push the ROM to your phone and then try flashing it via recovery? You mentioned not having a microSD card reader but I presume you have a microSD card, correct? If so push the ROM to the card, do a full wipe in recovery (Dalvik cache, cache, data & system), then flash the ROM.
Click to expand...
Click to collapse
Thanks for trudging along with me, still learning here. I pushed the ROM you linked to my sdcard via adb, did a full wipe, and went to install:
Installing ' /sdcard/firmware.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat " /system/build.prop": No such file or directory
E:Error executing updater binary in zip '/sdcard/firmware.zip'
Error flashing zip '/sdcard/firmware2.zip'
I was able to flash the GPe ROM successfully using this method, but my phone still reboots to bootloader...
Odd.
At any rate, you're going to need to update your firmware, otherwise you won't be able to properly run the GPE port to begin with.
Thanks again. I was able to recover to stock image with the RUU you suggested. Do you have any suggestions/links for ROMS with stock android? And do you have a BTC address?
You can take a look at the thread in the link below (the first post, actually).
http://forum.xda-developers.com/showthread.php?t=2729173
I don't have a BTC address.
Hi there,
I recently got a Sprint HTC M8(Non HK) with android version 4.4.2 and software number 1.54.651.8.
I tried to flash the firmware before flashing the RUU to update it to marshmallow(6.0). But when i tried to flash it using adb i get this error message(error: cannot load 'firmware.zip').
Also i have copied the file where my adb.exe and fastboot.exe and also renamed it to firmware.zip.
here are my cmd commands:
C:\Users\donsh.DESKTOP-BDD1FFG>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\Users\donsh.DESKTOP-BDD1FFG>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\donsh.DESKTOP-BDD1FFG>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\donsh.DESKTOP-BDD1FFG>fastboot flash zip firmware.zip
error: cannot load 'firmware.zip'
C:\Users\donsh.DESKTOP-BDD1FFG>fastboot reboot
rebooting...
finished. total time: 0.015s
C:\Users\donsh.DESKTOP-BDD1FFG>
Click to expand...
Click to collapse
any help is appreciated
thanks
Update: My device is S-OFF and boot loader locked. I have no custom recovery installed too.( I don't know if i would be needing a custom recovery to flash the firmware and if it's needed could i get a link on how to flash a custom recovery, newbie here)
Shazly M said:
Hi there,
I recently got a Sprint HTC M8(Non HK) with android version 4.4.2 and software number 1.54.651.8.
I tried to flash the firmware before flashing the RUU to update it to marshmallow(6.0). But when i tried to flash it using adb i get this error message(error: cannot load 'firmware.zip').
Also i have copied the file where my adb.exe and fastboot.exe and also renamed it to firmware.zip.
here are my cmd commands:
any help is appreciated
thanks
Update: My device is S-OFF and boot loader locked. I have no custom recovery installed too.( I don't know if i would be needing a custom recovery to flash the firmware and if it's needed could i get a link on how to flash a custom recovery, newbie here)
Click to expand...
Click to collapse
go to the windows folder settings and uncheck the option "Hide extensions of known file types". It appears that the file name is "firmware.zip.zip" at the moment if it is indeed in the same folder. after that, remove the extra .ZIP from the file name and try again.
junaidawan86 said:
go to the windows folder settings and uncheck the option "Hide extensions of known file types". It appears that the file name is "firmware.zip.zip" at the moment if it is indeed in the same folder. after that, remove the extra .ZIP from the file name and try again.
Click to expand...
Click to collapse
Well I did this method and it worked,
Installed twrp recovery
Flashed it using "fastboot flash zip firmware.zip.zip" and it got flashed but now when I try to flash the Rom I keep encountering the error "target reported max download size of 1826418688" any fixes or workarounds for this?
Shazly M said:
Well I did this method and it worked,
Installed twrp recovery
Flashed it using "fastboot flash zip firmware.zip.zip" and it got flashed but now when I try to flash the Rom I keep encountering the error "target reported max download size of 1826418688" any fixes or workarounds for this?
Click to expand...
Click to collapse
Are u using htc_fastboot.exe? If not then download and use that one instead of just fastboot.exe
junaidawan86 said:
Are u using htc_fastboot.exe? If not then download and use that one instead of just fastboot.exe
Click to expand...
Click to collapse
i tried using both exe but still no luck with, i think it has something to do with storage
As per my knowledge, this issue sometimes either happens due to incorrect firmware OR by using fastboot instead of htc_fastboot. Did u flash the firmware twice? And can you tell me what are the contents of the rom's zip file?
junaidawan86 said:
As per my knowledge, this issue sometimes either happens due to incorrect firmware OR by using fastboot instead of htc_fastboot. Did u flash the firmware twice? And can you tell me what are the contents of the rom's zip file?
Click to expand...
Click to collapse
I flashed the firmware successfully with normal fastboot.exe
(I flashed it twice since I failed at the first try) and my Rom is a full signed HTC non hk, I'm not sure if I should do a factory restore and then try it