Database Develop

with a soft-brick do you RUU or do a PH398DIAG.zip to recover

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

Unable to get S-off - HBOOT 1.54 - rumrunner

Hey I was hoping that someone here would be able to help.
Ive been trying for get s-off on my device, I have tried everything but it dosent wnat to work. I am probably missing something basic.
I have a GPE HTC one that I until recently used with RevolutionHD 30 (Sense version).
Now that 4.4 is out I want to flash that, but every rom seems to require s-off.
Being that my Hboot version is 1.54, i understand that my only option to s-off is using rumrunner.
I have tried to rumrunner a number of times:
Using a windows machine
Using a Linux machine
I have tried both wirh the following roms: CM 10.2, CM 11, ADR 30
But I cant seem to have any luck. On both machines I alwasy get stuck at the same place:
HTML:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
I dont know if it helps but "fastboot getvar mainver" alwasy rettuns blank.
I tried to log onto the rumrunner irc, but it looks to be empty.
Is their anything that I can do?

Please tell me your cid and your model id and I 'll guide you
Sent from my HTC One using Tapatalk

Thanks,
Cid num: GOOGL001
Model id: PN0712000
Just in case fastboot getvar all output:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36JW913072
(bootloader) imei: *******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4313mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

AmirH said:
Hey I was hoping that someone here would be able to help.
Ive been trying for get s-off on my device, I have tried everything but it dosent wnat to work. I am probably missing something basic.
I have a GPE HTC one that I until recently used with RevolutionHD 30 (Sense version).
Now that 4.4 is out I want to flash that, but every rom seems to require s-off.
Being that my Hboot version is 1.54, i understand that my only option to s-off is using rumrunner.
I have tried to rumrunner a number of times:
Using a windows machine
Using a Linux machine
I have tried both wirh the following roms: CM 10.2, CM 11, ADR 30
But I cant seem to have any luck. On both machines I alwasy get stuck at the same place:
HTML:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
I dont know if it helps but "fastboot getvar mainver" alwasy rettuns blank.
I tried to log onto the rumrunner irc, but it looks to be empty.
Is their anything that I can do?
Click to expand...
Click to collapse
Since your hboot is 1.54 use Guru Reset: 2.24.xxx.x, such as: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ (if this doesnt work try a different 2.24 version)
in installer, select ROOT, and unselect "stock recovery", then give rumrunner a chance

nkk71 said:
Since your hboot is 1.54 use Guru Reset: 2.24.xxx.x, such as: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ (if this doesnt work try a different 2.24 version)
in installer, select ROOT, and unselect "stock recovery", then give rumrunner a chance
Click to expand...
Click to collapse
Although not mentiond I also tried with "Guru Reset M7 3.63.707.4" maybe the version number that I tried wasnt good.
The download is on the way and I will try it then.
This wont cause any problems with the touch issues correct? I dont not have a OTG cable.

Or follow this guide http://forum.xda-developers.com/showthread.php?t=2358781 to flash the 4.4 Google edition RUU and be completely stock. Then your main version won't be blank, and can try to get s-off
Sent from my HTC One using Tapatalk

Ivanovic said:
Or follow this guide http://forum.xda-developers.com/showthread.php?t=2358781 to flash the 4.4 Google edition RUU and be completely stock. Then your main version won't be blank, and can try to get s-off
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
That was one of the posts that I was looking at but then i saw this
HTML:
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Should I not be worried about that?

I thought about that but you already have the correct CID and MID. I believe it will flash just fine
Sent from my HTC One using Tapatalk

Sounds reasonable ... I will update once finished.

AmirH said:
Sounds reasonable ... I will update once finished.
Click to expand...
Click to collapse
why not try s-off with 2.24 rom, and if that doesnt work you can always try the second method. once you upgrade you can no longer downgrade with S-On.

nkk71 said:
why not try s-off with 2.24 rom, and if that doesnt work you can always try the second method. once you upgrade you can no longer downgrade with S-On.
Click to expand...
Click to collapse
Thats what I plan to do.. Im downloading both roms at the same time.
Once they are finished and I have gotten a chance to play around with them, I will update.
I do hope that one of the methods work.

OK so both methods failed, maybe I'm doing something wrong...
First:
The real reason that I wanted s-off was because I wanted to install 4.4 so i decided to try with the RUU.
I tried with a locked and unlocked boot loader. the errors i got were;
1. FAILED (remote: 12 signature verify fail)
2. FAILED (remote: 99 unknown fail)
Then I went with the GURU method...
I installed the Rom, flashed stock recovery, and added root (Bootloader still unlocked).
1. Setup my HTC
2. Allowed USB debugging
3. turned fast boot off
4. Tried to run the rumrunner again (Am I missing a step here?!?)
Still get the rumrunner error.
Im not sure if its relevent, but I get this when trying to lock and unlock the bootloader:
HTML:
fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.189s
And
HTML:
fastboot oem unlock
...
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 10.802s
Does this tell you guys anything?

Check your drivers.. ? or install HTC Naked drivers.

SaHiLzZ said:
Check your drivers.. ? or install HTC Naked drivers.
Click to expand...
Click to collapse
Based on what part are you saying that?
Should I update the drivers and try to install RUU
or install and try to lock/unlock the bootloader.
ADB and fastboot do work just fine.
As for the rumrunner it was ran on a Unix machine. So the drivers shouldn't be an issue.

As an added suggestion, perhaps the drivers are not interacting properly to give those messages. Haven't seen those before. http://forum.xda-developers.com/showthread.php?t=2139767
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.

AmirH said:
OK so both methods failed, maybe I'm doing something wrong...
First:
The real reason that I wanted s-off was because I wanted to install 4.4 so i decided to try with the RUU.
I tried with a locked and unlocked boot loader. the errors i got were;
1. FAILED (remote: 12 signature verify fail)
2. FAILED (remote: 99 unknown fail)
Then I went with the GURU method...
I installed the Rom, flashed stock recovery, and added root (Bootloader still unlocked).
1. Setup my HTC
2. Allowed USB debugging
3. turned fast boot off
4. Tried to run the rumrunner again (Am I missing a step here?!?)
Still get the rumrunner error.
Im not sure if its relevent, but I get this when trying to lock and unlock the bootloader:
HTML:
fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.189s
And
HTML:
fastboot oem unlock
...
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 10.802s
Does this tell you guys anything?
Click to expand...
Click to collapse
I didnt know that "fastboot oem unlock" works with the M7, but maybe it does with the GPe
have you checked the rumrunner thread? recommend you head over there and see if you get some help. i'm not familiar enough with GPe to be able to guide you properly. sorry

I cant believe I cant get this too work... after a little investigation, I'm starting to think that it might have something to do with the fact that
"fastboot getvar mainver" returns "mainver: "
I cant even flash a stock RUU
Edit:
Updated my mainver using this tool:
http://forum.xda-developers.com/showthread.php?t=2344671
still no help

Softbricked, no OS, twrp recovery, S on. SOLVED!!!!

Hey everyone, (((((SOLVED)))))
so here is the situation.
-HTC One Bell Canada
-S on
-Twrp Recovery newest version
-No OS or backup (I accidentally deleted it)
-Windows 7 64bit
-I have fastboot files, adb files/sdk and the 3.23.666.1 Bell mobility RUU zip with no exe
I just want to get my phone back to stock then after i'll reroot and create a backup of stock so I won't have this happen again.
here is what's on my bootloader screen
Tampered
unlocked
hboot 1.55
I have tried a lot of the similar situation fixes on google and here but I couldn't find anything that has put me in a better place.
when I fastboot with
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
I tried to sideload with twerp and advanced then adb sideload and all I get is error/cannot flash zip.
Also tried installing rumrunner to get my s off but luck either.
I have also tried 4 other RUUs from htcdev and a few other places.
If there is any info you need please ask, thank you in advance.
You guys are my last hope....

christianpencz said:
Hey everyone,
so here is the situation.
-HTC One Bell Canada
-S on
-Twrp Recovery newest version
-No OS or backup (I accidentally deleted it)
-Windows 7 64bit
-I have fastboot files, adb files/sdk and the 3.23.666.1 Bell mobility RUU zip with no exe
I just want to get my phone back to stock then after i'll reroot and create a backup of stock so I won't have this happen again.
here is what's on my bootloader screen
Tampered
unlocked
hboot 1.55
I have tried a lot of the similar situation fixes on google and here but I couldn't find anything that has put me in a better place.
when I fastboot with
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
I tried to sideload with twerp and advanced then adb sideload and all I get is error/cannot flash zip.
Also tried installing rumrunner to get my s off but luck either.
I have also tried 4 other RUUs from htcdev and a few other places.
If there is any info you need please ask, thank you in advance.
You guys are my last hope....
Click to expand...
Click to collapse
Don't panic my friend, you just forgot to relock your bootloader first
Code:
fastboot oem lock

Why don't you just adb push a custom rom to your phone and flash that
Sent from my iPad using Tapatalk

Uxepro said:
Don't panic my friend, you just forgot to relock your bootloader first
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thanks Uxepro, but I have tried to flash with and without the bootloader unlocked. I get 2 different error messages, which I posted originally (12 signature verify and the 24 parsing android info fail).
If there is a step i'm missing could you tell me the step by step just in case I did something stupid.

christianpencz said:
Thanks Uxepro, but I have tried to flash with and without the bootloader unlocked. I get 2 different error messages, which I posted originally (12 signature verify and the 24 parsing android info fail).
If there is a step i'm missing could you tell me the step by step just in case I did something stupid.
Click to expand...
Click to collapse
To flash ruu with s-on you need 2 things:
Locked or relocked bootloader
Signed ruu (not decrypted)
Sent from my HTC One using xda app-developers app

christianpencz said:
I have .... the 3.23.666.1 Bell mobility RUU zip with no exe
Click to expand...
Click to collapse
1- Where did you get that from, link please
christianpencz said:
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
Click to expand...
Click to collapse
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning

nateboi81 said:
Why don't you just adb push a custom rom to your phone and flash that
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.

christianpencz said:
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.
Click to expand...
Click to collapse
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/showthread.php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you

Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/stock-nandroid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.

alray said:
To flash ruu with s-on you need 2 things:
Locked or relocked bootloader
Signed ruu (not decrypted)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you nobody said it clear to me like that. So is that why it says signature fail, caused it not a signed ruu?
Quote:
Originally Posted by christianpencz View Post
I have .... the 3.23.666.1 Bell mobility RUU zip with no exe
1- Where did you get that from, link please
Click to expand...
Click to collapse
1. http://www.htc1guru.com/dld/ota_m7_ul_jb43_sense50_mr_bm_3-23-666-1-1-29-666-17_r_release-zip/
Quote:
Originally Posted by christianpencz View Post
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning
Click to expand...
Click to collapse
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
Quote:
Originally Posted by christianpencz View Post
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/show....php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you
Click to expand...
Click to collapse
I'll try that in the meantime. Thank you (I have to use my htc one s till I get my one back up and running lol great phone just not the same at all haha.)
Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/st...oid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.
Click to expand...
Click to collapse
I got mine from there too. But mine didn't work....can you give me the steps with the codes, maybe I missed something....I'm very new at this.
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.

nkk71 said:
1- Where did you get that from, link please
1. http://www.htc1guru.com/dld/ota_m7_ul_jb43_sense50_mr_bm_3-23-666-1-1-29-666-17_r_release-zip/
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning
Click to expand...
Click to collapse
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
nkk71 said:
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/showthread.php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you
Click to expand...
Click to collapse
I'll try that in the meantime. Thank you (I have to use my htc one s till I get my one back up and running lol great phone just not the same at all haha.)
Emhalwis said:
Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/stock-nandroid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.
Click to expand...
Click to collapse
I got mine from there too. But mine didn't work....can you give me the steps with the codes, maybe I missed something....I'm very new at this.
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.

christianpencz said:
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.
Click to expand...
Click to collapse
First off the file your using is not a RUU it's an OTA
OTA M7 UL JB43 SENSE50 MR BM 3.23.666.1-1.29.666.17 R Release
their not the same thing OTA is flashed with a stock recovery on a Stock phone.
The nandroid backup / restore is your best bet at this point

clsA said:
First off the file your using is not a RUU it's an OTA
OTA M7 UL JB43 SENSE50 MR BM 3.23.666.1-1.29.666.17 R Release
their not the same thing OTA is flashed with a stock recovery on a Stock phone.
The nandroid backup / restore is your best bet at this point
Click to expand...
Click to collapse
so should I do exactly the same thing and steps just use the nandroid file instead?

christianpencz said:
so should I do exactly the same thing and steps just use the nandroid file instead?
Click to expand...
Click to collapse
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
C:\fastboot>adb devices
List of devices attached
HT343******* recovery
C:\fastboot>adb push backup /data/media/0/TWRP/BACKUPS/HT343*******/backup
push: backup/firmware_3.62.401.1.zip -> /data/media/0/TWRP/BACKUPS/HT343******/
backup/firmware_3.62.401.1.zip
1 file pushed. 0 files skipped.
3881 KB/s (28795564 bytes in 7.245s)
Click to expand...
Click to collapse
I just used one file as an example .. you'll have many files in your backup

clsA said:
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
I just used one file as an example .. you'll have many files in your backup
Click to expand...
Click to collapse
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup

alray said:
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup
Click to expand...
Click to collapse
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed

clsA said:
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed
Click to expand...
Click to collapse
ok nmv I was a little confused and didnt read your previous post correctly

alray said:
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup
Click to expand...
Click to collapse
clsA said:
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed
Click to expand...
Click to collapse
clsA said:
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
I just used one file as an example .. you'll have many files in your backup
Click to expand...
Click to collapse
I sort of understand what you guys mean.....if I change the name of zip file to like nanbackup does that matter?
I know almost nothing about this process, can you do it in code form and a bit simpler.....sorry I'm a bit noobish

christianpencz said:
I sort of understand what you guys mean.....if I change the name of zip file to like nanbackup does that matter?
I know almost nothing about this process, can you do it in code form and a bit simpler.....sorry I'm a bit noobish
Click to expand...
Click to collapse
if you extract the zip to a folder named "nanbackup'' and you move that folder in your adb/fastboot folder then i think the right command should be:
Code:
adb push nanbackup /data/media/0/TWRP/BACKUPS/HT********/nanbackup/
note the space between nanbackup and /data/......
and you should be able to see the backup in twrp after the push is completed
Maybe @CiSa can confirm that before you proceed...

alray said:
if you extract the zip to a folder named "nanbackup'' and you move that folder in your adb/fastboot folder then i think the right command should be:
Code:
adb push nanbackup /data/media/0/TWRP/BACKUPS/HT********/nanbackup/
note the space between /nanbackup and /data/......
and you should be able to see the backup in twrp after the push is completed
Maybe @CiSa can confirm that before you proceed...
Click to expand...
Click to collapse
thank you, so before I try this...what do i actually type where it says HT******
or how can I find out what to put?

Help flashing firmware.

I have been trying to update a firmware to I can run the new lp rom. It says the new firmware is required. His phone is s-on and I used the new twrp..
E:\greg\lollipop>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.150s
E:\greg\lollipop>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3

budeone said:
I have been trying to update a firmware to I can run the new lp rom. It says the new firmware is required. His phone is s-on and I used the new twrp..
E:\greg\lollipop>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.150s
E:\greg\lollipop>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
Click to expand...
Click to collapse
Is there a question in there somewhere?

BD619 said:
Is there a question in there somewhere?
Click to expand...
Click to collapse
ROFLMAO
Yeah.. sorry.. it keeps failing.. I have tried to do a RUU after locking it back up.. I have tried everything I can think of.. just wont let me update.

budeone said:
ROFLMAO
Yeah.. sorry.. it keeps failing.. I have tried to do a RUU after locking it back up.. I have tried everything I can think of.. just wont let me update.
Click to expand...
Click to collapse
What errors are you getting?

BD619 said:
What errors are you getting?
Click to expand...
Click to collapse
FAILED (status read failed (Too many links))

budeone said:
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
You got that error when you re-locked right?
If so that's normal...does bootloader say RELOCKED?

BD619 said:
You got that error when you re-locked right?
If so that's normal...does bootloader say RELOCKED?
Click to expand...
Click to collapse
I relocked and get that message. Nothing changed in the phone I am still on the 1.0 version of firmware. Then I have no recovery unless I unlock again. I am starting to wounder if I cant go from the very first firmware to the latest?

budeone said:
I relocked and get that message. Nothing changed in the phone I am still on the 1.0 version of firmware. Then I have no recovery unless I unlock again. I am starting to wounder if I cant go from the very first firmware to the latest?
Click to expand...
Click to collapse
In theory you should be able to go right to the latest.

BD619 said:
In theory you should be able to go right to the latest.
Click to expand...
Click to collapse
I know if I were s-off I would not be having these issues. I am not paying $25.00 bucks for someone else phone.

Todd what's up when did you get an m8?

FrozenRiff said:
Todd what's up when did you get an m8?
Click to expand...
Click to collapse
Its my boss's phone. I have tried everything and I cant get it to work.. I even tried buying him shunshine and that wont work.

Boot loop, can't enter recovery

Hi All,
Just wondering if anyone might have any other ideas for me, as I've reached the limit of my very limited skills.
I have an HTC one International, Australian Optus version.
It is running 7.21.980.5.
I don't know the history of this phone, but it came to me in a bootloop.
Phone was S-ON and untamptered.
I can boot into fastboot and RUU mode so can clear cache, flash zips etc.
I have now unlocked the bootloader and tried flashing every custom recovery version under the sun (and stock), as well as clearing cache everywhere and flashing stock boot.img
There does not seem to be an RUU available for this carrier (which would in theory get me out of this situation) and I can't get S-OFF to write superCID as the phone won't boot so can't use Firewater (it has HBOOT 1.66). The only full zips I can find are from nandroid backups, or Guru restores that require flashing the zip through recovery.
When I flash a recovery, it succeeds every time, but when I reboot for recovery, it has the white screen with 'entering recovery' for a few seconds, but then it reboots and tries to boot into normal mode again.
Anybody been able to get out of a similar situation, without flashing an RUU?

kamold said:
Hi All,
Just wondering if anyone might have any other ideas for me, as I've reached the limit of my very limited skills.
I have an HTC one International, Australian Optus version.
It is running 7.21.980.5.
I don't know the history of this phone, but it came to me in a bootloop.
Phone was S-ON and untamptered.
I can boot into fastboot and RUU mode so can clear cache, flash zips etc.
I have now unlocked the bootloader and tried flashing every custom recovery version under the sun (and stock), as well as clearing cache everywhere and flashing stock boot.img
There does not seem to be an RUU available for this carrier (which would in theory get me out of this situation)
Click to expand...
Click to collapse
Yes there is one but its only available at ir-file.com. File name is PN07IMG_M7_UL_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_425296_signed.zip
You'll need an account to download from this website which cost 15$, it take approx 1 day for your account to be active after payment. (I'm not affiliated with them btw). If you download the ruu please re-upoad on a free file hosting site like androidfilehost.com and share the link please so we can add it to the collection in the general section and help future user.
I can't get S-OFF to write superCID as the phone won't boot so can't use Firewater.
Click to expand...
Click to collapse
Anyway Firewater doesn't exist anymore, only way to s-off now in Sunshine S-OFF which cost 25 and still need the device to be booted anyway.
The only full zips I can find are from nandroid backups, or Guru restores that require flashing the zip through recovery.
When I flash a recovery, it succeeds every time, but when I reboot for recovery, it has the white screen with 'entering recovery' for a few seconds, but then it reboots and tries to boot into normal mode again.
Click to expand...
Click to collapse
Try unofficial twrp recovery by MDMower if it still doesn't work then you'll have to download that ruu from ir-file.com

Thanks very much for your reply @alray, I appreciate it!
Tried that TWRP, still the same issue. So I'll try and get hold of that RUU that you've posted and get back to you.

OK so I got the RUU, relocked the bootloader and tried to load it but I can't flash it. I get a 'could not allocate x bytes'.
I also can't do a fastboot erase userdata or internal (failed remote:not allowed).
I have a feeling that maybe the internal flash memory chip might be faulty.
unless anyone else has any other ideas?

kamold said:
OK so I got the RUU, relocked the bootloader and tried to load it but I can't flash it. I get a 'could not allocate x bytes'.
Click to expand...
Click to collapse
Can you post a screenshot of your command window, want to see everything from the beginning when you are trying to flash the RUU.

C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.191s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot flash zip PN07IMG_M7_UL
_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_
425296_signed.zip
load_file: could not allocate 1639602889 bytes

kamold said:
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.191s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot flash zip PN07IMG_M7_UL
_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_
425296_signed.zip
load_file: could not allocate 1639602889 bytes
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash 7.xx.xxx.x RUU, get rid of this toolkit and use fastboot/adb directly from a command window.
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_425296_signed.zip
htc_fastboot reboot

alray said:
You must use htc_fastboot.exe to flash 7.xx.xxx.x RUU, get rid of this toolkit and use fastboot/adb directly from a command window.
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_425296_signed.zip
htc_fastboot reboot
Click to expand...
Click to collapse
You sir are a gentleman and a scholar!
RUU loaded successfully.
Phone still bootloops though
Oh well.

kamold said:
You sir are a gentleman and a scholar!
RUU loaded successfully.
Phone still bootloops though
Oh well.
Click to expand...
Click to collapse
Is it bootlooping or stuck at htc white splash screen? First boot can take up to 10-15 minute and phone will stay at htc spash screen for that time.
Unfortunately if it still doesn't boot after flashing the ruu, its maybe an hardware problem.

Yeah I think it's hardware unfortunately. Starts and then reboots after about 20 seconds. Rinse and repeat.
I'll use the screen and housing and try and resurrect another phone.
Sent from my HTC One_M8 using Tapatalk

kamold said:
Yeah I think it's hardware unfortunately. Starts and then reboots after about 20 seconds. Rinse and repeat.
I'll use the screen and housing and try and resurrect another phone.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
would you mind sharing the ruu file. please...

rajivshahi said:
would you mind sharing the ruu file. please...
Click to expand...
Click to collapse
All the RUUs are here:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

kamold said:
All the RUUs are here:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
thanks a lot really appreciated.:good: