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
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
jcr67 said:
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
Click to expand...
Click to collapse
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED?
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
tpbklake said:
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED? .
Click to expand...
Click to collapse
yep
tpbklake said:
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
Click to expand...
Click to collapse
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
jcr67 said:
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
Click to expand...
Click to collapse
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
jcr67 said:
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
Click to expand...
Click to collapse
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Drugzy said:
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Click to expand...
Click to collapse
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s
jcr67 said:
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s
Click to expand...
Click to collapse
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
tpbklake said:
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
Click to expand...
Click to collapse
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s
HBOOT now says:
*** RELOCKED ***
*** Security Warning ***
jcr67 said:
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s
Click to expand...
Click to collapse
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Reinstall the HTC ruu
Sent from my HTC Raider X710e using xda app-developers app
tpbklake said:
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Click to expand...
Click to collapse
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
jcr67 said:
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
Click to expand...
Click to collapse
Yes you should be ok.
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
yep he will be , during my downgrade i had to relock with security warning and ruu fixed it all
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
Thanks very much. The stock ICS RUU has now installed successfully. I guess when I originally tried to reinstall it, I had left out the 'RELOCK' step, which is why it failed.
So now I am back to the start (stock ICS + HBOOT 2.02 S-ON), and want to get S-OFF and install your ROM zip. ,What I originally intended to do to get S-OFF was:
1) Unlock the bootloader, flash CWM Recovery, flash SU
2) Run downgrade GB RUU
3) S-off with Revolutionary
4) Install Blackrose HBOOT
5) Install your vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But step 2) failed with an unknown error. (I then tried to install your zip, and the rest is the sad history.....).
So what caused step 2 to fail? Did I need to relock the bootloader first?
Many thanks for your help, tpbklake
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly.
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly. p
Click to expand...
Click to collapse
That's it. HBOOT is remaining at 2.02.0002 after runme.cmd
Is the device rooted?
y OR n:y
Waiting for device to connect
Device found
Pushing misc_version
2455 KB/s (367096 bytes in 0.146s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Cleaning temp files
Any ideas anyone?
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Click to expand...
Click to collapse
No, I'm unlocked and rooted
Does the stock ruu have superuser installed? If it does I'm outta ideas.
Sent from my HTC Incredible S using xda app-developers app
---------- Post added at 07:58 PM ---------- Previous post was at 07:40 PM ----------
One more thing, I would try flashing another ROM, i came from Niks Sense 4a rom, and the script worked with no issues.
Remember you will need to manually flash the boot.img of the rom as you are S-ON.
jcr67 said:
No, I'm unlocked and rooted
Click to expand...
Click to collapse
Open a command window and then type in the command:
adb shell
If you get a # prompt then your ROM is rooted correctly and the script should run. If it doesn't then the ROM isn't properly rooted and the script will fail.
Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
axel_johnson said:
Hi, about 6 months ago bought a rogers htc raider, upon receipt procedures to perform the unlock bootloader and s-off procedure, it will change back to a stock rom and I gave it to my brother, I recently comes for saying that when you turn the phone just stays on the logo screen, entering volume down menu and power, try to do a factory reset and get stuck, also download a stock rom and extracted the rom.zip file so renowned as ph39img.zip and try to run and do the updating also remains stalled, also try to lock the bootloader with fastboot oem lock and also stuck.
please i need help.
Click to expand...
Click to collapse
1. This should not be in the development section......
2. Boot to bootloader.
3. Does it say Locked, Relocked, or Unlocked?
4. Does it say S-On or S-Off?
5. Do you have v1.83 or 1.85 bootloader?
6. Select Recovery, what happens?
1. This should not be in the development section......
2. Boot to bootloader.
yes boot with volumen - and power
3. Does it say Locked, Relocked, or Unlocked?
Unlocked, i try locked again but nothing the phone still stuck, running the command fastboot oem lock.
4. Does it say S-On or S-Off?
s-off along a few months with the method juonot... with wire.
5. Do you have v1.83 or 1.85 bootloader?
show the version 1.85
6.- recovery
don't work when selected the option recovery the phone show the screen logo along 1 second and back to screen boot.
Next step would be fast boot flashing a custom recovery. I recommend wcx or twrp. Once youve done that, youll be set to properly wipe and flash the ROM of your choice
wcxjb hello and try but I can not, I get the following error.
C: \ Useful HTC One X \ WCXJB_ROOT_PACK \ WCXJB_ROOT_PACK> fastboot flash zip jb_hboot.
zip
******** sending 'zip' (379 KB) ... OKAY [0.318s]
***************** writing 'zip' ... FAILED (remote: not allowed)
finished. total time: 0.642s
please what else I can do ... I need to operate this phone.
Extract the wcxrecovery.IMG from the zip..
Fastboot flash recovery wcxrecovery.IMG
You can't fastboot flash a zip
I tried to do that and I get the following error.
C:\Utiles HTC One X\WCXJB_ROOT_PACK\WCXJB_ROOT_PACK>fastboot flash recovery wcxr
ecovery.img
sending 'recovery' (6996 KB)... OKAY [ 1.720s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 3.178s
please help me.
Is your Boot loader unlocked?
yes the bootloader is unlocked, i try locked o relocked but not possibly, the phone was stuck.
please help what steps should I follow ... I want to retrieve the phone.
axel_johnson said:
please help what steps should I follow ... I want to retrieve the phone.
Click to expand...
Click to collapse
The only things I can think of that would cause this "writing 'recovery'... FAILED (remote: image update error)" would be:
1. You got a bad download
2. Bootloader is not properly unlocked
3. Your recovery partition got borked somehow
Things I would try next:
1. Redownload the recovery image and try again
2. fastboot oem lock to lock the bootloader, then go through the unlock process again
3. fastboot oem lock, run your carrier's RUU, reunlock bootloader, fastboot flash recovery wcxrecovery.img, fastboot flash boot boot.img (from ROM), boot to recovery, wipe data, system, dalvik, and cache, and flash ROM
pleas help me my htc rider
My phone refuse to boot up to normal background it is stuck on the htc logo hv tried factry reset bt still no progress it was caused by an apps I installed phone name htc rider vrsn 4.0 pls help me
I have an HTC One developer edition (64GB), and I've flash Clockwork Recovery to it.
However, when I relock the bootloader and install the RUU, it doesn't overwrite the recovery partition.
What can I be doing wrong?
I've tried fooling around with the "HTC Fast boot" (in the Sense menu, not the sdk fastboot) but I can't seem to figure out what I'm doing wrong...
sofakng said:
I have an HTC One developer edition (64GB), and I've flash Clockwork Recovery to it.
However, when I relock the bootloader and install the RUU, it doesn't overwrite the recovery partition.
What can I be doing wrong?
I've tried fooling around with the "HTC Fast boot" (in the Sense menu, not the sdk fastboot) but I can't seem to figure out what I'm doing wrong...
Click to expand...
Click to collapse
actually what are you trying to achieve?
Well, mostly I'm just trying to learn more about how Android works. I was able to restore the RUU before and it even removed the tampered boot loader warning but now my RUU doesn't seem to restore everything. It's very inconsistent so that's why I'm trying to figure out exactly how this works and what I might be doing differently.
Maybe I have to clear the (dalvik) cache before running the RUU?
sofakng said:
Well, mostly I'm just trying to learn more about how Android works. I was able to restore the RUU before and it even removed the tampered boot loader warning but now my RUU doesn't seem to restore everything. It's very inconsistent so that's why I'm trying to figure out exactly how this works and what I might be doing differently.
Maybe I have to clear the (dalvik) cache before running the RUU?
Click to expand...
Click to collapse
it shouldn't be needed, you only need to lock your bootloader and then run the RUU and that will bring everything to stock
matt95 said:
it shouldn't be needed, you only need to lock your bootloader and then run the RUU and that will bring everything to stock
Click to expand...
Click to collapse
Ok, something is wrong then...
My boot loader says relocked and tampered but after running the RUU, recovery doesn't work (it just reboots if I try to enter recovery and shows the developer warning before rebooting)...
sofakng said:
Ok, something is wrong then...
My boot loader says relocked and tampered but after running the RUU, recovery doesn't work (it just reboots if I try to enter recovery and shows the developer warning before rebooting)...
Click to expand...
Click to collapse
it worked in your case the stock recovery always gives that symbol there's nothing wrong with it
Maybe I'm not explaining it properly, but for example, I JUST relocked my bootloader and ran the RUU.
It restored successfully.
However, if I boot into the bootloader and then recovery, it boots into clockwork recovery! That means the RUU didn't overwrite my recovery partition...
Shouldn't the RUU restore the stock recovery?!
sofakng said:
Maybe I'm not explaining it properly, but for example, I JUST relocked my bootloader and ran the RUU.
It restored successfully.
However, if I boot into the bootloader and then recovery, it boots into clockwork recovery! That means the RUU didn't overwrite my recovery partition...
Shouldn't the RUU restore the stock recovery?!
Click to expand...
Click to collapse
Try getting the .zip one and do a fastboot version. Works for me.
tozfeekum said:
I'm trying to return my HTC developer edition back to stock
and I am running the RUU via terminal:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip.
I've tried running it immediately as suggested in other threads but that hasn't worked.
Does anyone know what's going on here:
ending 'zip' (1004418 KB)...
OKAY [ 34.434s]
writing 'zip'...
(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) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 165.173s
EDIT:
I got this working by running fastboot erase cache
Click to expand...
Click to collapse
I'm not sure if you're also experiencing the recovery partition missing, like in my thread.
http://forum.xda-developers.com/showthread.php?t=2267008
Hmmmm, maybe that's my problem?
I've just flashed the ZIP, and everything looked like it worked fine... (I received the "please flush image" message and I re-ran the flash and it then completely successfully)
However, when I select [Recovery] from HBOOT, the screen flashes for a second, and then it returns to the HBOOT again. It does seem like the recovery partition is missing...?
Here is my fastboot log: http://pastebin.com/KQJjE78a
EDIT: When I unlocked my bootloader (fastboot flash unlocktoken), and then tried to enter recovery, it went back into clockwork recovery!!
The RUU/ZIP is absolutely, positively, not overwriting my recovery... (which is also why the bootloader still says "tampered" as well, because the entire stock image is not being 100% restored)
I have the same exact problem with my one dev edition.Hope someone can figure this out
Sent from my HTC One using xda premium
Glad to see I'm not the only one!
I've decrypted the RUU ZIP file and extracted the signed recovery.img, but I think decrypting the ZIP changes the checksum so when I try to flash it to the bootloader it says the signature failed.
I've been trying all kinds of things and I have gotten it to work (and the tampered warning was removed), but I have no idea what combination of commands/images I used to get it working...
Hopefully somebody can help us
sofakng said:
Glad to see I'm not the only one!
I've decrypted the RUU ZIP file and extracted the signed recovery.img, but I think decrypting the ZIP changes the checksum so when I try to flash it to the bootloader it says the signature failed.
I've been trying all kinds of things and I have gotten it to work (and the tampered warning was removed), but I have no idea what combination of commands/images I used to get it working...
Hopefully somebody can help us
Click to expand...
Click to collapse
you succeeded in installing the recovery then?
matt95 said:
you succeeded in installing the recovery then?
Click to expand...
Click to collapse
Yes, a few days ago it worked but now it's not working any more and I'm not sure what combination of events occured when it did work...
sofakng said:
Yes, a few days ago it worked but now it's not working any more and I'm not sure what combination of events occured when it did work...
Click to expand...
Click to collapse
the stock one i mean..? where did you get it? from a nandroid backup or from the RUU itself?
The only way I have fixed this is flashing stock recovery from one of Mike's post ...but I think it's from the at&t model ...not sure if that makes a difference but I do get it working then
Sent from my HTC One using xda premium
martyotaku said:
The only way I have fixed this is flashing stock recovery from one of Mike's post ...but I think it's from the at&t model ...not sure if that makes a difference but I do get it working then
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmmm, so there is a signed recovery image floating around somewhere? Any idea which post has it?
I've also been able to successfully get mine restored but it seems like it worked by some random chance.
Here's what I think I did differently:
* Turned off phone for five minutes
* Unplugged USB cable until I entered fastboot
I have no idea if that's why the RUU finally worked but I'd love to know for sure in case I need to perform this in the future.
sofakng said:
Hmmm, so there is a signed recovery image floating around somewhere? Any idea which post has it?
I've also been able to successfully get mine restored but it seems like it worked by some random chance.
Here's what I think I did differently:
* Turned off phone for five minutes
* Unplugged USB cable until I entered fastboot
I have no idea if that's why the RUU finally worked but I'd love to know for sure in case I need to perform this in the future.
Click to expand...
Click to collapse
Did you do the fastboot erase cache?
The way I got it back to stock recovery was doing this.
When I had CWM, I attempted to fastboot a different recovery using this.
http://forum.xda-developers.com/showthread.php?t=2158763&highlight=recovery+img
It installed but it never worked as the phone could not enter. Then I just fastboot the factory zip and it some how overriden the faulty recovery and it worked.
I'm not home now and hate using this app lol I'll post it when I get home ...but it's from dev mikes post
edit here is what i used from this link http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
I will get there said:
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
I will get there said:
Hi Xda
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
I will get there said:
Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
solbirn said:
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
Click to expand...
Click to collapse
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
nkk71 said:
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
Click to expand...
Click to collapse
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
loughary said:
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
Click to expand...
Click to collapse
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
I will get there said:
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
Click to expand...
Click to collapse
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
nkk71 said:
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks @nkk71
I now have an unlocked bootloader
I have also now flashed CWM 6.0.4.5 however I still do not have adb available. The difference now is fastboot is recognised in device manager as before but when I boot into CWM instead of it dissapearing, it moves to 'other devices' one (with yellow exclamation) I know it did this before because of drivers not being installed/recognised but I have htc sync manager installed which in theory has installed the drivers??!
Anything else I can try without adb?
Again many thanks for your assistance, I see you in a number of threads helping people...top bloke!
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
I will get there said:
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
Click to expand...
Click to collapse
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Ivanovic said:
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Click to expand...
Click to collapse
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
IF you re flashing a 4.4 ROM then use TWRP 2.6.3.3 or latest CWM
IF you re flashing a 4.3/4.2 ROM then use TWRP 2.6.3.0 or older CWM
Link for the RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
http://www.htc1guru.com/downloads/ruu-file-downloads/
I had to use the exe version to get it working when I had a similar issue.
Sent from my One using Tapatalk
Yes there is a fix. Install stock recovery. Go to bootloader and select factory reset. It will go to stock recovery and do it's thing and should go into a Bootloop . install custom recovery you should be good
Hi All
Just a quick note, to say all back up and running, thanks for all the respondants who helped.
I wanted add how i got it up and running, so if anyone has similar issues they can use it:
I believe the biggest culprit was the newest Firmware and TWRO 2.3.3.3 in which it did not want to load.
I downgraded by Hboot to firmware 3.xxx and then flashed TWRP 2.3.3.0 and it let me in instead of kicking me out to a bootloop.
I then had access to ADB sideload, which did not work for me in the 1st instance that led me to my problem, This i believe was due to not having the lastest SDK.(upgrade this).
Make sure the Rom you are pushing works well for that downgraded firmware i.e. a solid 4.3 based rom in my case.
Also to note I wiped my external SD card and was unable to mount this to flash, let TWRP sort this by doing a factory reset prior to flashing.
Hope this helps anyone who experienced similar symptoms to me.