Device: HTC Flyer 32GB 3G
Firstly my Flyer is running on 3.2 (version is 3.07.xxx...)
It's unstable, a lot of Force Close (especially HTC Sense)
so I decide to flash rom into 3.10.405.1 with Paul's instruction
I found that, with my stupididty I mistype fillename in step 9.
9.Flash your device's radio with the Honeycomb radio with the fastboot command 'fastboot flash radio stock-hc-flyer-radio.img'
and I realized after step 15
15. Flash your device's recovery with the patched-to-work-with-new-hboot revolutionary recovery - 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img'
because it's show "remote signature verify fail"
I guest this is the cause of it
now my Flyer:
- Become to S-On
- Cannot turn off my Flyer. It's turned on after 5 seconds, then enter to HBOOT.
- Cannot turn on to Android system either. Always enter to HBOOT
- Cannot go to recovery. system reboot then enter HBOOT again.
- I still can use fastboot.
- Cannot use adb. device not found
- I tried to update driver http ://unrevoked .com/rootwiki/doku.php/public/windows_hboot_driver_install but still not work. 'adb devices' is show nothing
- I try to flash it with "RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed.exe" but it can't.
My HBOOT screen
-----------------------------
*** LOCKED ***
*** Security Warning ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3809.07.04.12_M
eMMC-boot
Aug 29 2010,13:32:02
HBOOT USB PLUG
<VOL UP> to previous item
<VOL Down> to next item
<POWER> to select item
FASTBOOT
RECOVREY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
-----------------------------
how can I fix it?
earthchie said:
Device: HTC Flyer 32GB 3G
Firstly my Flyer is running on 3.2 (version is 3.07.xxx...)
It's unstable, a lot of Force Close (especially HTC Sense)
so I decide to flash rom into 3.10.405.1 with Paul's instruction
I found that, with my stupididty I mistype fillename in step 9.
9.Flash your device's radio with the Honeycomb radio with the fastboot command 'fastboot flash radio stock-hc-flyer-radio.img'
and I realized after step 15
15. Flash your device's recovery with the patched-to-work-with-new-hboot revolutionary recovery - 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img'
because it's show "remote signature verify fail"
I guest this is the cause of it
now my Flyer:
- Become to S-On
- Cannot turn off my Flyer. It's turned on after 5 seconds, then enter to HBOOT.
- Cannot turn on to Android system either. Always enter to HBOOT
- Cannot go to recovery. system reboot then enter HBOOT again.
- I still can use fastboot.
- Cannot use adb. device not found
- I tried to update driver http ://unrevoked .com/rootwiki/doku.php/public/windows_hboot_driver_install but still not work. 'adb devices' is show nothing
- I try to flash it with "RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed.exe" but it can't.
My HBOOT screen
-----------------------------
*** LOCKED ***
*** Security Warning ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3809.07.04.12_M
eMMC-boot
Aug 29 2010,13:32:02
HBOOT USB PLUG
<VOL UP> to previous item
<VOL Down> to next item
<POWER> to select item
FASTBOOT
RECOVREY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
-----------------------------
how can I fix it?
Click to expand...
Click to collapse
your radio version and hboot version not fit togheter. try with goldcard (rom.zip) file from this ruu RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.08 9BU_3809.07.04.06_M_release_204108_signed
read this thread http://forum.xda-developers.com/showpost.php?p=16147471&postcount=77
viera77 said:
your radio version and hboot version not fit togheter. try with goldcard (rom.zip) file from this ruu RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.08 9BU_3809.07.04.06_M_release_204108_signed
read this thread http://forum.xda-developers.com/showpost.php?p=16147471&postcount=77
Click to expand...
Click to collapse
Thanks for your respond but since I cannot boot into android system
so I stuck in step #10
#10 Download "GoldCard Helper" from the Android Market and open it.
I also can't use adb to get cid by myself too
earthchie said:
Thanks for your respond but since I cannot boot into android system
so I stuck in step #10
#10 Download "GoldCard Helper" from the Android Market and open it.
I also can't use adb to get cid by myself too
Click to expand...
Click to collapse
Could you adb push the apk to system/app ?
Sent from my PG86100 using XDA App
steam374 said:
Could you adb push the apk to system/app ?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
No I can't.
I cannot use adb command because device is not found
I stuck in HBOOT screen and Fastboot screen
so all I can do is just fastboot command
--
More information. hope it useful
C:\android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.11.0006
INFOversion-baseband: 3809.07.04.12_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 3.07.0.1
INFOserialno: HT163T400297
INFOimei: 354672040978247
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 3957mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 60a0efb2
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.008s
maybe I can run adb command if i can enter recovery
I found that htc magic can enter to recovery by use
'fastboot boot recovery-RAv1.2.0H.img' command
how about htc flyer, where can i find recovery image for flyer which allow me to enter recovery mode.
I use recovery image from clockworkmod but it's not work
I would try to boot into RUU mode (Vol up and Power), and then just flash your original RUU.
Lucas0511 said:
I would try to boot into RUU mode (Vol up and Power), and then just flash your original RUU.
Click to expand...
Click to collapse
cannot get into RUU mode
When I press vol up and power in the same time.
Flyer boot into FASTBOOT.
earthchie said:
cannot get into RUU mode
When I press vol up and power in the same time.
Flyer boot into FASTBOOT.
Click to expand...
Click to collapse
i have read another forum, i think you can look with another android device your ext. sdcard cid (your friend`s device)
you can try it
As long as your device is S-ON you cannot flash a custom recovery. At this point I would ask Paul in his original Modaco thread for help http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
earthchie said:
maybe I can run adb command if i can enter recovery
I found that htc magic can enter to recovery by use
'fastboot boot recovery-RAv1.2.0H.img' command
how about htc flyer, where can i find recovery image for flyer which allow me to enter recovery mode.
I use recovery image from clockworkmod but it's not work
Click to expand...
Click to collapse
viera77 said:
i have read another forum, i think you can look with another android device your ext. sdcard cid (your friend`s device)
you can try it
Click to expand...
Click to collapse
Thank you, I tried and it fail because of inccorect CID (I can't remember the exactly message)
Lucas0511 said:
As long as your device is S-ON you cannot flash a custom recovery. At this point I would ask Paul in his original Modaco thread for help http://android.modaco.com/topic/345950-installing-honeycomb-on-your-flyer-the-complete-guide/
Click to expand...
Click to collapse
Okay thank you. I'll do that
okay now I already unlock bootloader following these steps:
http://www.htcdev.com/bootloader
I can turn off my Flyer now
but still cannot enter to the Android system
this is my current HBOOT screen
------------------
*** UNLOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3809.07.04.12_M
eMMC-boot
Aug 29 2011,13:32:02
HBOOT USB PLUG
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
------------------
what can I do to fix it after unlock bootloader?
OH NO! it getting worst
after i unlock bootloader
i cannot charge battery
now my flyer's battery is dead.
I charged it with wall chage for 3 hours
but no respond from flyer. just orage LED flashing all the time.
when i pressed power botton for 5 seconds, LED stop flashing and start to flahing again after 5 seconds
now i really wanna trow it away -*-
earthchie said:
OH NO! it getting worst
after i unlock bootloader
i cannot charge battery
now my flyer's battery is dead.
I charged it with wall chage for 3 hours
but no respond from flyer. just orage LED flashing all the time.
when i pressed power botton for 5 seconds, LED stop flashing and start to flahing again after 5 seconds
now i really wanna trow it away -*-
Click to expand...
Click to collapse
i am having the same problem as u but 1 day before i tryed rooting and flashing honeycomb my flyer died and when i truned it back on it would not go past the htc logo so i went in to the bootloader an did a factory reset and it was fine so i started rooting and flashing honeycomb and now it doesn't work i dont know wat to do i cant only go in to bootloader by pressing vol up and power
Hi,
did u solved?
iam in the same situation than you, but with an htc incredible s.
Did u tested with a Goldcard?
Hi all.
has a solution been found for the above problem
I am stuck with the same issue!
Related
I am trying to upgrade my UK Vodafone HTC Magic to your Cyanogen Mod Froyo OS. It's currently running Android 1.6.
The "Upgrading from CyanogenMod 4.2 to CyanogenMod 5/6" article says:
Note: it is recommended that you upgrade to Amon_Ra recovery 1.7.0 for your device. Dream or Magic
Click to expand...
Click to collapse
And links to the article "[Recovery] [32A & 32B] [16-May-2010] RA-sapphire-v1.7.0".
It seems that the easiest way to install this is via Fastboot:
Code:
Copy recovery-RA-sapphire-v1.7.0G.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img
My fastboot screen says:
Code:
SAPPHIRE PVT 32B SHIP S-ON GI
HBOOT-1.33.0004 (SAPP10000)
CPLD-10
RaDIO-2.22.19.261
Apr 9 2009,23:30:40
HBOOT
<BACK> Fastboot Mode
If I press "back" I am then presented with:
Code:
<VOL DOWN> HBoot Mode
<SEND< Reset DEvice
<ACTION> Restart to HBoot
<MENU> Power Down
I don't understand how to flash the recovery file. Can someone help me out?
Thanks,
Robin.
nottrobin said:
I am trying to upgrade my UK Vodafone HTC Magic to your Cyanogen Mod Froyo OS. It's currently running Android 1.6.
The "Upgrading from CyanogenMod 4.2 to CyanogenMod 5/6" article says:
And links to the article "[Recovery] [32A & 32B] [16-May-2010] RA-sapphire-v1.7.0".
It seems that the easiest way to install this is via Fastboot:
Code:
Copy recovery-RA-sapphire-v1.7.0G.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img
My fastboot screen says:
Code:
SAPPHIRE PVT 32B SHIP S-ON GI
HBOOT-1.33.0004 (SAPP10000)
CPLD-10
RaDIO-2.22.19.261
Apr 9 2009,23:30:40
HBOOT
<BACK> Fastboot Mode
If I press "back" I am then presented with:
Code:
<VOL DOWN> HBoot Mode
<SEND< Reset DEvice
<ACTION> Restart to HBoot
<MENU> Power Down
I don't understand how to flash the recovery file. Can someone help me out?
Thanks,
Robin.
Click to expand...
Click to collapse
The best guide I've ever received was from THIS SITE.....I'm doing that as we speak
Thanks.
According to that method I'm pretty sure I have to create a goldcard to get back to Cupcake. Which is annoying, because I don't currently have a spare SD card (as it currently errors whenever I try to flash to a new ROM). And I'm also a little worried that I might brick my phone. I was hoping I could avoid this by not needing to downgrade, by installing this Amon_RA recovery mod.
However, as it looks like I probably just have to suck it up and do the goldcard method, I'll just order one on ebay and have done with it.
Cheers.
I've got a Sprint EVO 3D I am trying to unbrick for a friend. What happens is that the phone powers on and the only thing that happens is that I get a black screen with the HTC logo and four exclamation points on the four corners of the screen. I can't get into hboot. Holding the power button and the volume down button don't do anything unless the phone is completely off, in which case, I get the previously mentioned HTC screen.
I can use fastboot commands though. The command "fastboot reboot-recovery" restarts the phone but I get exactly the same result, the black HTC screen with four exclamation points.
"fastboot getvar mainver" returns "2.17.651.5"
"fastboot getvar cid" returns "SPCS_001"
Based on that information, I consulted the Google and found "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed." That ran for a while until the RUU program on my computer then said it couldn't complete the update and returned error code 155. Googling that error produced several threads that spoke of making sure the bootloader was locked prior to running the RUU. That step was mentioned in the forum that led me to the RUU in the first place and I verified that the bootloader was locked prior to running the RUU by running "fastboot oem lock." That command returned "(bootloader) Device was already locked!" To be sure, I ran the whole process again. Verified the bootloader was locked, and received error 155 again.
When you disconnect the USB after running the RUU, the screen changes to the familiar white hboot screen and says the following
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Hboot Version is older
Update Fail!
After more searching and more Googling, I found an RUU named "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed" which is supposed to work with hboot 1.58. That one ran for much longer and a green status bar showed up on the EVO's screen. The RUU program errors out with error 132: Signature Error but the green bar on the EVO's screen keeps moving until it gets to just before the "C" in the HTC logo and stops there. I let the phone sit for nearly an hour with no change. At that point, I disconnected the USB to see if I could get the HBoot screen again and this is what it showed:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Parsing ...[download ZIP]
[1] BOOTLOADER - Bypassed
[2] BOOT - OK
[3] SBL1 - OK
[4] USERDATA - OK
[5] WIMAX - OK
[6] RECOVERY - OK
[7] SBL2 - OK
[8] SPLASH1 - OK
[9] SYSTEM - Fail-UZ
[10] SBL3 - Fail-PU
[11] TRUST_ZONE - OK
[12] ADSP - OK
[13] RPM - OK
[14] PG2FS_SPCUSTOM - Fail-UZ
[15] RADIO_V2 - Fail-UZ
Image uzipping fail!
Update Fail!
I have also tried placing a PG86IMG.zip file from another thread onto an SDCard. This doesn't do anything that I can see. At this point, I've spent two days trying to fix this phone and I am out of ideas. The rest of the fixes for a bricked EVO all start with "enter hboot" which I can't do with any method I am aware of or can find.
Any suggestions or am I just out of luck?
firesyde424 said:
I've got a Sprint EVO 3D I am trying to unbrick for a friend. What happens is that the phone powers on and the only thing that happens is that I get a black screen with the HTC logo and four exclamation points on the four corners of the screen. I can't get into hboot. Holding the power button and the volume down button don't do anything unless the phone is completely off, in which case, I get the previously mentioned HTC screen.
I can use fastboot commands though. The command "fastboot reboot-recovery" restarts the phone but I get exactly the same result, the black HTC screen with four exclamation points.
"fastboot getvar mainver" returns "2.17.651.5"
"fastboot getvar cid" returns "SPCS_001"
Based on that information, I consulted the Google and found "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed." That ran for a while until the RUU program on my computer then said it couldn't complete the update and returned error code 155. Googling that error produced several threads that spoke of making sure the bootloader was locked prior to running the RUU. That step was mentioned in the forum that led me to the RUU in the first place and I verified that the bootloader was locked prior to running the RUU by running "fastboot oem lock." That command returned "(bootloader) Device was already locked!" To be sure, I ran the whole process again. Verified the bootloader was locked, and received error 155 again.
When you disconnect the USB after running the RUU, the screen changes to the familiar white hboot screen and says the following
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Hboot Version is older
Update Fail!
After more searching and more Googling, I found an RUU named "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed" which is supposed to work with hboot 1.58. That one ran for much longer and a green status bar showed up on the EVO's screen. The RUU program errors out with error 132: Signature Error but the green bar on the EVO's screen keeps moving until it gets to just before the "C" in the HTC logo and stops there. I let the phone sit for nearly an hour with no change. At that point, I disconnected the USB to see if I could get the HBoot screen again and this is what it showed:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
RUU
Parsing ...[download ZIP]
[1] BOOTLOADER - Bypassed
[2] BOOT - OK
[3] SBL1 - OK
[4] USERDATA - OK
[5] WIMAX - OK
[6] RECOVERY - OK
[7] SBL2 - OK
[8] SPLASH1 - OK
[9] SYSTEM - Fail-UZ
[10] SBL3 - Fail-PU
[11] TRUST_ZONE - OK
[12] ADSP - OK
[13] RPM - OK
[14] PG2FS_SPCUSTOM - Fail-UZ
[15] RADIO_V2 - Fail-UZ
Image uzipping fail!
Update Fail!
I have also tried placing a PG86IMG.zip file from another thread onto an SDCard. This doesn't do anything that I can see. At this point, I've spent two days trying to fix this phone and I am out of ideas. The rest of the fixes for a bricked EVO all start with "enter hboot" which I can't do with any method I am aware of or can find.
Any suggestions or am I just out of luck?
Click to expand...
Click to collapse
in order to write a new bootloader youll need to be unlocked andsOFF...your phone says youre relocked
plus the version youre trying to install is for hboot 1.5 not 1.58...
http://goo.im/stock/shooter/ruu
go there and try to runn that RUU...its for the ICS version of android with hboot 1.58 which is what you have...and until you unlock your bootloader again and then root then gain s-off THEN you can install a different bootloader versio like 1.5 which is what is suppoed to run with version 2.17
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
further
by the way, i think i went wrong by failing to flash boot.img as i have s-on. after install of rom via cwm, flyer got in a bootloop (ended up having to bootstrap battery as it drained). since this, flyer would not boot. Entering recovery just caused a quick glimpse of recovery screen before bootlooping. Since this i now can only get to my hboot screens, attempting to boot or recovery just gives me the wgite htc screen indefinitely.
adb driver?
ok, i think my issue is with adb.
with flyer in hboot so options are
fastboot
recovery
factory reset
clear storage
simlock
image crc
when i check device manager, it is listed as ADB interface, expand that and you get 'bootloader interface'
put flyer in fastboot mode, i see
bootloader
reboot reboot bootloader
power down
and the device is gone from device manager completely.
in either mode, when in adb running command 'adb devices' i get nothing, although running commands such as 'fastboot flash boot boot.img/recovery.img i get a success message after writing. 'fastboot reboot' will successfully reboot the device but it still does not boot up or enter recovery when attempted.
am i missing an adb driver or something?
AT&T HTC one M8 was bootloader unlocked, S-OFF (i remember), rooted and loaded with MaximusHD 4.0.0. operating pretty good for weeks.
yesterday, not sure what happened, it was powered off when i pulled out from my pocket. battery was around 15% or drained maybe.
then, i had to press and hold power button for 15 seconds to get the screen on. it only goes into bootloader (cannot go to recovery, cannot do normal reboot). This is what it shows now:
***UNLOCKED***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
OS-
eMMC-boot 2048MB
Feb 27, 2014, 16:20:59.0
tried to move to the recover and boot from there, the phone vibrates and went back to bootloader screen immediately.
tried to use fastboot oem lock, no response.
tried to use fastboot flash unlocktoken unlock.bin, it says success on the remote machine but doing nothing on the phone.
tried to use fastboot flash recovery image, it says remote write error.
cannot do anything with adb command since the phone wasn't boot to anywhere at all.
Anyone had this problem? or i missed something.. thanks.
qqragoon said:
AT&T HTC one M8 was bootloader unlocked, S-OFF (i remember), rooted and loaded with MaximusHD 4.0.0. operating pretty good for weeks.
yesterday, not sure what happened, it was powered off when i pulled out from my pocket. battery was around 15% or drained maybe.
then, i had to press and hold power button for 15 seconds to get the screen on. it only goes into bootloader (cannot go to recovery, cannot do normal reboot). This is what it shows now:
***UNLOCKED***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
OS-
eMMC-boot 2048MB
Feb 27, 2014, 16:20:59.0
tried to move to the recover and boot from there, the phone vibrates and went back to bootloader screen immediately.
tried to use fastboot oem lock, no response.
tried to use fastboot flash unlocktoken unlock.bin, it says success on the remote machine but doing nothing on the phone.
tried to use fastboot flash recovery image, it says remote write error.
cannot do anything with adb command since the phone wasn't boot to anywhere at all.
Anyone had this problem? or i missed something.. thanks.
Click to expand...
Click to collapse
fastboot erase cache
fastboot flash recovery twrp.img
fastboot erase cache
then go to new recovery, let me know your outcome, make sure you grab the official 2.7.0.2 twrp IMG file from their website.
an0ther said:
fastboot erase cache
fastboot flash recovery twrp.img
fastboot erase cache
then go to new recovery, let me know your outcome, make sure you grab the official 2.7.0.2 twrp IMG file from their website.
Click to expand...
Click to collapse
That didn't work. no response from the phone at all when I run first two commands.
However, I took the phone and plug into a different charger by accident (2A current), it boots up correctly now.
Still don't know what went wrong. Hope this can help someone in the same situation.
[Q] HTC Desire 601 - Bootloader stuck on "Tampered" and "Relocked"
Can someone shed some light on what I did wrong with my HTC Desire 601 (locked to Rogers)?
ZARA_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.26.40e.00.14
OpenDSP-v18.2.0268.0925
OS-2.14.631.3
eMMC-boot 1024MB
Feb 26 2014, 12:27:49.0
Bootloader is showing *Tampered* and *Relocked*. I get an error message when I type:
fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.125s]
finished. total time: 0.125s
So I typed:
fastboot flash unlocktoken unlock_code.bin
results:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.140s
I "power vol +/up" and then "power button" to select "yes".
Phone turns off but does not boot or anything. Just black screen.
Is there any hope to recover this phone?
htcraspy said:
Can someone shed some light on what I did wrong with my HTC Desire 601 (locked to Rogers)?
ZARA_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.26.40e.00.14
OpenDSP-v18.2.0268.0925
OS-2.14.631.3
eMMC-boot 1024MB
Feb 26 2014, 12:27:49.0
Bootloader is showing *Tampered* and *Relocked*. I get an error message when I type:
fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.125s]
finished. total time: 0.125s
So I typed:
fastboot flash unlocktoken unlock_code.bin
results:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.140s
I "power vol +/up" and then "power button" to select "yes".
Phone turns off but does not boot or anything. Just black screen.
Is there any hope to recover this phone?
Click to expand...
Click to collapse
make sure you have no errors(ex have an arrow or line extra when copying from terminal to htc dev site for unlock code) I have done this before and it gives a black screen
toolhas4degrees said:
make sure you have no errors(ex have an arrow or line extra when copying from terminal to htc dev site for unlock code) I have done this before and it gives a black screen
Click to expand...
Click to collapse
Thanks for the reply. In command prompt I just highlight the area that is instructed on HTCDev and right-click to copy. When I paste it to continue I do get the message that a token was submitted successfully.
I receive the "unlock_token.bin" file and flash the phone with the "fastboot flash unlocktoken Unlock_code.bin" command but when I choose "yes" and press the "power button" it goes to a black screen.
More information on how this became a problem is that I was able to unlock the bootloader before and flashed a stock ROM with CWM/TWRP because the phone was freezing at the "HTC" logo screen.
The phone booted fine and this is the software information that I had saved:
Android version
4.4.2 (KitKat)
HTC Sense version
5.5
Software number
2.14.631.3
HTC SDK API level
5.69
Kernel version
3.4.10-g910527a
[email protected] #1
SMP PREEMPT
Baseband version
1.26.40e.00.14_10z18.40.1304L
Build number
2.14.631.3.CL315961 release-keys
Since everything was running fine at that time I decided to use the command "fastboot oem lock" which gave me the tampered and relocked flags. The phone at some point and I don't know why decided to freeze at the "HTC" logo screen again and I cannot unlock the bootloader due to the issue I had explained in the initial post.
I will try HTCDev again to get a new unlock_token.bin but is there anything else I could try?
Thanks,
htcraspy said:
Thanks for the reply. In command prompt I just highlight the area that is instructed on HTCDev and right-click to copy. When I paste it to continue I do get the message that a token was submitted successfully.
I receive the "unlock_token.bin" file and flash the phone with the "fastboot flash unlocktoken Unlock_code.bin" command but when I choose "yes" and press the "power button" it goes to a black screen.
More information on how this became a problem is that I was able to unlock the bootloader before and flashed a stock ROM with CWM/TWRP because the phone was freezing at the "HTC" logo screen.
The phone booted fine and this is the software information that I had saved:
Android version
4.4.2 (KitKat)
HTC Sense version
5.5
Software number
2.14.631.3
HTC SDK API level
5.69
Kernel version
3.4.10-g910527a
[email protected] #1
SMP PREEMPT
Baseband version
1.26.40e.00.14_10z18.40.1304L
Build number
2.14.631.3.CL315961 release-keys
Since everything was running fine at that time I decided to use the command "fastboot oem lock" which gave me the tampered and relocked flags. The phone at some point and I don't know why decided to freeze at the "HTC" logo screen again and I cannot unlock the bootloader due to the issue I had explained in the initial post.
I will try HTCDev again to get a new unlock_token.bin but is there anything else I could try?
Thanks,
Click to expand...
Click to collapse
AFAIK no, this is the only way. but like i said. if you make an error in copying the txt, htc dev won't recognize it and the .bin will go through successfully and will ask you the question on phone then go to black screen. redo the htc dev part.
toolhas4degrees said:
AFAIK no, this is the only way. but like i said. if you make an error in copying the txt, htc dev won't recognize it and the .bin will go through successfully and will ask you the question on phone then go to black screen. redo the htc dev part.
Click to expand...
Click to collapse
Thanks. I wish it was that simple. I highlighted the text and right-click to copy the portion to paste. I know what you mean about having an extra space because I tried that too and it does pass for a submission. But either way I am still stuck with the same issue. It's probably something else wrong with the phone as I can't even "factory reset" because the screen would just freeze and go no where.
*SOLVED*
htcraspy said:
Thanks. I wish it was that simple. I highlighted the text and right-click to copy the portion to paste. I know what you mean about having an extra space because I tried that too and it does pass for a submission. But either way I am still stuck with the same issue. It's probably something else wrong with the phone as I can't even "factory reset" because the screen would just freeze and go no where.
Click to expand...
Click to collapse
Well this is strange but I got the phone fixed and running again. First I called Fido (my carrier) and they suggested a 2 year renewal plan so that I could get a new phone to replace the HTC Desire 601 which was out of warranty. So I called HTC directly in hopes on getting my hands on a RUU for Rogers/Fido but they couldn't provide me a link or the file.
Okay so from the beginning, my HTC Desire 601 is on KitKat 4.4.2 with HBOOT 2.22. I unlocked the bootloader using the following the instructions on HTCDev. Then I used something called "rumrunner" to turn "S-ON" to "S-OFF" as this would explain why I got the "Tampered" flag. Then I flashed a custom recovery by TWRP (openrecovery-twrp-2.8.3.0-zaracl.img) and then flashed a file "STOCK_ODEX_ROOT_HTC_ZARA_UL_601_2.14.1401.86_v.1.0.1". I did this because originally the phone was not booting past the "HTC" white logo screen. Flashed the file "recovery_stock.img" to remove TWRP. When I confirmed that everything was working again, I changed "S-OFF" back to "S-ON" and relocked the bootloader. I forgot how I changed "S-OFF" back to "S-ON" but there is a thread in the forums explaining it.
So why I am here looking for help because my fix from before did not work this time. I was not able to unlock the bootloader which kept giving me a black screen when I chose "yes" to unlock.
THE SOLUTION:
1. Unplug any data cable, sim card, sd card from the HTC Desire 601 phone
2. Hold "vol- down" and power button to get into the bootloader
3. Presss "vol- down" to "recovery"
4. HTC logo with a white background will appear but wait a little until you see a "red triangle" but in my case I got a mobile icon device with greens arrows in a circular form above it
5. At this point I have to hold "vol+ up" and press the power button once (the screen might dim a bit but that is normal). Release "vol- up" button.
6. Wait until the recovery options appear and use "vol+ up" / "vol- down" to select "wipe cache partition"
7. Do the same thing to "reboot system now"
8. At this point I was able to unlock the bootloader and the phone decided to boot properly without having to do anything else
Strange but problem solved :victory: