Related
Hi,
I almost bricked my daughter's ChaCha. Half a year ago I unlocked the bootloader to be able to install and run Link2sd to increase performance of the phone and have my daughter have all the apps on it she wants. But a week or so ago the phone started to act up and I decided to take a look.
End of the story is that the phone, when turned on, boots into fastboot automatically but the volume and power keys do not work at all. So I can't select reboot or recovery or anything. I have to remove the battery to switch it off...
Apparently system and recovery are gone cause when I issue 'fastboot oem boot' the response is '(bootloader) [ERR] Boot/Recovery image does not exist!!!'. That can't be good...
The bootloader got relocked in the process of trying to fix it which complicates the problem. Now I can't re-unlock it because the volume and power keys don't work. I can get fastboot in unlock mode but can't select 'yes' and continue because the keys do not work...
I tried re-installing stock rom via RUU with various results. Version 1.33 complains about a customer id (error 131), version 1.13 thinks it's a signature error (error 132) and version 1.18 (I must be desperate) doesn't like the bootloader version (error 140).
I tried creating an old school goldcard to get the phone to accept RUU 1.33 but obviously that failed too. Since I can't get into the phone over adb (only fastboot) I can't get the phone's CID. Also, system is reported to be nonexistent so trying to extract the CID is a dead end anyway.
I think I've tried everything and I'm about to give up. But I thought, before I do that, I better check with the experts here to see if anybody else has a brilliant idea to solve my problem. I'm considering buying the XTC clip but I'm not sure if that will work since the phone is so far gone already. Maybe someone here knows the answer to that?
Below is what 'fastboot getvar all' gives me. Hopefully that helps in answering my question: Is this phone bricked or is there still hope?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.10.0000
(bootloader) version-baseband: 7.51.35.19
(bootloader) version-cpld: None
(bootloader) version-microp: 0557
(bootloader) version-main: 1.57.0.0
(bootloader) serialno: HT16GV409974
(bootloader) imei: 355746042148642
(bootloader) product: chacha
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PH0611000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d86ac222
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
It doesn't look like it's anything you've done. If the bootloader is now locked, I would take advantage of that and send it back to the shop to get it repaired. (obviously, don't mention that you tampered with it). That shouldn't happen, I've got link2SD, and so has my partner and we've never had any problems like that, so I think it must be something wrong with your phone :/
Progress
Thanks for your reply. I thought about returning it the phone to have it repaired but it's apparent the phone has been unlocked and re-locked again. That will probably void warranty.
I don't think Link2sd caused this problem. Something else must have happened but I doubt it's a hardware problem.
I've made a bit of progress in the meantime. Somehow (I don't know how) the phone got in to recovery. The screen was black though but I could get into it with adb shell! So I got my CID and created a goldkey. I hoped that was all I needed but I still can't flash a stock rom over RUU because now they all complain about my hboot version which is 1.10
I think I need a RUU rom (exe) that supports hboot 1.10. Or, a way to downgrade to 1.07 or 1.05. Or a way to flash or push something onto the phone while in recovery.
Any help will be appreciated...
NoLimit64 said:
Hi,
...when turned on, boots into fastboot
Click to expand...
Click to collapse
Well if you are able to boot into fastboot maybe you can try this method. I used this to revive my friend's chacha.
Download this tool (it is, I believe, adlx's small fastboot tool). Extract it and navigate to it with cmd (I did this on windows). But before that download a RUU for your chacha (I used 1.3.3 version since it was the only one I could find), run RUU but don't flash it and don't exit the application as well. Then locate your temp folder (%temp%) and find somewhere in one of the folders a zip named Rom.zip (use the search function if you prefer). Copy the Rom.zip anywhere you like and extract system.img, boot.img and recovery.img and place them in the same folder where you extracted fastboot tools. And now enter these commands in cmd (don't forget to navigate to the folder you placed all the files):
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
When it is finished, reboot your phone (you will probably need to do this by pulling the battery out) and hopefully you will have the stock rom installed.
Hope that this will help you.
Regards
didije said:
Well if you are able to boot into fastboot maybe you can try this method. I used this to revive my friend's chacha.
Download this tool (it is, I believe, adlx's small fastboot tool). Extract it and navigate to it with cmd (I did this on windows). But before that download a RUU for your chacha (I used 1.3.3 version since it was the only one I could find), run RUU but don't flash it and don't exit the application as well. Then locate your temp folder (%temp%) and find somewhere in one of the folders a zip named Rom.zip (use the search function if you prefer). Copy the Rom.zip anywhere you like and extract system.img, boot.img and recovery.img and place them in the same folder where you extracted fastboot tools. And now enter this commands in cmd (don't forget to navigate to the folder you placed all the files):
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
When it is finished, reboot your phone (you will probably need to do this by pulling the battery out) and hopefully you will have the stock rom installed.
Hope that this will help you.
Regards
Click to expand...
Click to collapse
I had an issue with flashing an RUU because of HBOOT version, but as didje said, the 1.33 RUU version works with that HBOOT version
ethancottier said:
I had an issue with flashing an RUU because of HBOOT version, but as didje said, the 1.33 RUU version works with that HBOOT version
Click to expand...
Click to collapse
I always have issues flashing RUUs. Error this, error that, really annoying, so I don't flash them anymore. Now, I just flash manually those three files and I have no worries.
didije said:
I always have issues flashing RUUs. Error this, error that, really annoying, so I don't flash them anymore. Now, I just flash manually those three files and I have no worries.
Click to expand...
Click to collapse
Sorry, no luck....
C:\Fastboot\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3172 KB)... OKAY [ 2.480s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Fastboot\Fastboot>fastboot flash system system.img
sending 'system' (259524 KB)... OKAY [ 62.605s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Fastboot\Fastboot>fastboot flash boot boot.img
sending 'boot' (2572 KB)... OKAY [ 2.282s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
As I mentioned. bootloader is relocked (my bad) so flashing the individual files will not work. Unlocking the bootloader won't work either because for some reason the volume and power keys do not work while in bootloader
Running the 1.33 RUU (RUU_Chacha_HTC_Europe_1.33.401.1_Radio_47.17.35.3033H_7.48.35.14_2_release_204385_signed.exe) returns error 140 Bootloader version error when run with goldkey inserted. Without the goldkey it returns error 131 customer id error... At least the goldkey seems to work but my phone does not accept this version but I can't figure out why.
Strang thing though, the RUU says I currently have version 1.57 which means I'm downgrading to 1.33.
I'm going to try this method: http://forum.xda-developers.com/showthread.php?t=1320392
Thanks so far!!
Ah, bootloader is re-locked.. I missed that part. Bummer... Hope you will find a way. It is really strange that vol. keys do not work.
didije said:
Ah, bootloader is re-locked.. I missed that part. Bummer... Hope you will find a way. It is really strange that vol. keys do not work.
Click to expand...
Click to collapse
Did you disable fastboot in the settings? (Not sure in which part it is... Thought apps)...
If you uncheck the marker, you should be able to enter recovery, etc, again... Worked for me when I had this problem... It wasn't the bootloader that was locked, just me using the fastboot.
When you press vol down+pwr when Fastboot is enabled, you won't see your bootloader screen, it just boots fast...
Maybe worth a try...
Bunnybugs_007 said:
Did you disable fastboot in the settings? (Not sure in which part it is... Thought apps)...
If you uncheck the marker, you should be able to enter recovery, etc, again... Worked for me when I had this problem... It wasn't the bootloader that was locked, just me using the fastboot.
When you press vol down+pwr when Fastboot is enabled, you won't see your bootloader screen, it just boots fast...
Maybe worth a try...
Click to expand...
Click to collapse
Oh my, you must have misunderstood us. He CAN enter the bootloader menu, but he cannot do anything because the bootloader got re-locked (opposite to HTC Dev unlocking - when you enter hboot, bootloader menu or what is called you can see on the top "locked", "unlocked" or in my case "re-locked" - I relocked mine to take it to the service but I didn't thought that it will say RE-locked ) so he cannot flash anything unless he finds a way to unlock it again or s-off the device. That is the problem.
didije said:
... in my case "re-locked" - I relocked mine...
Click to expand...
Click to collapse
I got the same HTC chacha CID: HTC_E11, its something like "Nederlanden" version.
Re-locked don't undo Lock - just simply lock "bootloader".
You will never go back
You should Unlock by "htcdev . com/bootloader/unlock-instructions/page-3"
Then You'll be able to flash via fastboot ,sysem.img, boot.img, recovery.img
i have same problem
NoLimit64 said:
Hi,
I almost bricked my daughter's ChaCha. Half a year ago I unlocked the bootloader to be able to install and run Link2sd to increase performance of the phone and have my daughter have all the apps on it she wants. But a week or so ago the phone started to act up and I decided to take a look.
End of the story is that the phone, when turned on, boots into fastboot automatically but the volume and power keys do not work at all. So I can't select reboot or recovery or anything. I have to remove the battery to switch it off...
Apparently system and recovery are gone cause when I issue 'fastboot oem boot' the response is '(bootloader) [ERR] Boot/Recovery image does not exist!!!'. That can't be good...
The bootloader got relocked in the process of trying to fix it which complicates the problem. Now I can't re-unlock it because the volume and power keys don't work. I can get fastboot in unlock mode but can't select 'yes' and continue because the keys do not work...
I tried re-installing stock rom via RUU with various results. Version 1.33 complains about a customer id (error 131), version 1.13 thinks it's a signature error (error 132) and version 1.18 (I must be desperate) doesn't like the bootloader version (error 140).
I tried creating an old school goldcard to get the phone to accept RUU 1.33 but obviously that failed too. Since I can't get into the phone over adb (only fastboot) I can't get the phone's CID. Also, system is reported to be nonexistent so trying to extract the CID is a dead end anyway.
I think I've tried everything and I'm about to give up. But I thought, before I do that, I better check with the experts here to see if anybody else has a brilliant idea to solve my problem. I'm considering buying the XTC clip but I'm not sure if that will work since the phone is so far gone already. Maybe someone here knows the answer to that?
Below is what 'fastboot getvar all' gives me. Hopefully that helps in answering my question: Is this phone bricked or is there still hope?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.10.0000
(bootloader) version-baseband: 7.51.35.19
(bootloader) version-cpld: None
(bootloader) version-microp: 0557
(bootloader) version-main: 1.57.0.0
(bootloader) serialno: HT16GV409974
(bootloader) imei: 355746042148642
(bootloader) product: chacha
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PH0611000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d86ac222
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
i tried to relock my htc chacha and baaamm. now hboot is locked and dead because no work any volume or power keys in hboot menu. i cant select any option. doesnt work vol+ or vol- or power here. also android os doesnt start normally if i restart to this phone directly opening hboot menu (also doesnt see any device on pc). but only way to access my phone via command. my way is:
1. shutdown phone (only way is remove your battery this status )
2. plug in usb cable your pc and phone
3. dont push to start button only wait until led is on
4. push to red(end call) button
5. now your phone is detected by the pc
6. you can use (phone is power off status still) fasboot commads
7.i use fastboot reboot command and start the phone.
anyway phone is accessible still . i have relocked phone using a nonsafe software i think hboot data damaged. QUESTION IS THAT: HOW CAN WE REPAIR HBOOT ON LOCKED STATUS WITHOUT USING ANY HARDWARE (JTAG OR XTCLIP).
Hi guys I' ve a problem with my oneplus one. I've the 38r version of cyanogenmod on my opo and I want to flash another ROM on my device.
The problem is that 1 week ago I ve unlocked bootloader and rooted it, but unfortunately with an app I've deleted root and relocked boot loader on my device (I'm a disaster I Know). Now I can' t reboot it into recovery, to reset my 1+1, because It's disappeared and it's stuck on 1+1 logo
In fastboot when I type in oem device-info I got this message:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false.
I've tried to relock 1+1 from fastboot but the device is stucked on 1+1 logo and I can only reboot with fastboot reboot. I can use it normally but I'd like to restore it.
Someone can helps me?? Thanks in advance.
Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off
SpeziesTR said:
Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off
Click to expand...
Click to collapse
You flash which version of firmware? A9 original version of what? now you can into bootloader mode?
Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...
SpeziesTR said:
Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...
Click to expand...
Click to collapse
When you at the "dark screen with htc logo" . enter cmd command "fastboot reboot-bootloader" can you into bootloader mode?
Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...
SpeziesTR said:
Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...
Click to expand...
Click to collapse
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Now unable into bootloader mode is the biggest problem.
@ nenebear: Thanks for your help so far!
Has anyone else a clue how to start into bootloader?
i have almost the same problem. my screen is black all the way but all the buttons work and i can hear it boot but the screen does not turn on
I managed to get into bootloader and from there into recovery. I had to press vol up + vol down + power so the device would boot into bootloader. Very strange as this is not the normal combination. I restored my previous image, it will boot but is somehow slow and sluggish.
Nevertheless I did flash
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
but I'm still not able to go to download mode. Furthermore beeing in bootloader reading basic information is not possible. For example:
...\HTC One A9\mini-sdk>fastboot devices
HT******** fastboot
...\HTC One A9\mini-sdk>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x29b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT********
all:
finished. total time: 0.080s
...\HTC One A9\mini-sdk>fastboot oem readcid
...
FAILED (remote: unknown command)
finished. total time: 0.004s
...\HTC One A9\mini-sdk>fastboot oem readmid
...
FAILED (remote: unknown command)
finished. total time: 0.011s
Anyone a clue how to fix my A9 completely?
Hi,
i just tried to flash system.img (which I decrypted from 1.56.401.70 ROM.zip) but unfortunately got the following error.
Code:
fastboot flash system system.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
htc_fastboot finished. total time: 134.464s
Flashing Boot.img, aboot.img etc. is working....
Has someone a clue?
I fixed the problem. I flashed firmware and rom from 1.27.401.5. After that download mode was working again and I could flash 1.56.401.70 without a problem.
Now I'm on Icanas ROM and my A9 is working better than ever...
I did the same flashed a bad firmware. I can access bootloader but not download mode. I have restored a backup I had in twrp so I am running a rooted stock rom but I still can't update my phone thru RUU or Download mode. I have tried flashing the 2p9qimg ( firmware img/ zip ) thru fastboot thru bootloader but no go. All I want to do is flash the correct file so I can access download mode
S-Off
At&T converted to Unlocked
CID & MID changed
nenebear said:
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Click to expand...
Click to collapse
which img files do I need to flash if I'm on 1.12.617.6 S- off US Unlocked converted from S-On At&t. I can't get into download mode, it turns off after the HTC logo with black background. Bootloader, recovery and my phone work though.
Nevermind figured it out! =)
Good day guys,
This is my first post in xda, and i'm a little bit nervous. and please bear with my english and i am a noob to some terms too. anyway, my unit is htc one a9. it was sent to me by my brother here in philippines. it is a sprint htc and i think it is a cdma with a sim slot and memory on the side. after reading some of your topics in some forums, i manage to unlock the the network. i can make outgoing and incoming calls and sms. but GPRS is disconnected. i then found another topic by jianC on how to Convert Sprint/Boost HTC One A9 to Dev Unlock. for it says that it can solve No mobile data (but have voice/sms) on sprint firmware after sim unlock. i followed the instructions but unfortunately it brick my phone. i flashed the 2PQ9IMG_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6_signed.zip, to my phone. My old firmware was 2PQ9IMG_HIA_AERO[email protected]51002_15.00_F_CNV_CNV_HIAE_SPCS_1.15_003_release_453002_signed.zip. Now my problem is that i can get in to bootloader mode by pressing power+vol up+vol down together which is awkward.......but i cannot get in to download mode and recovery mode. the phone can still display the htc logo but 15 seconds later it shutsdown. i tried your advice to type fastboot erase system but it says FAILED<remote:device is locked. cannot erase. But my phone is Bootloader Unlocked and S-Off from sunshine. CID/MID (SPCS_001/2PQ93000) before. I change it to (11111111/2PQ912000) after. Then i tried to flash. I really don't know where to start until i found this forum. I hope somebody could help me in this problem i have.
Thanks and sincerely yours,
kramned
Hello,
One month ago, I installed the last version of weekly ROM from xiaomi.eu, this version : miui 8.3 by xiaomi.eu - 7.4.6.
I have several bugs and I would like to install the stable ROM.
So I try to boot in Recovery Mode and the phone blocks on the "MI" logo with black font.
I go to Fastboot Mode and I install the last TWRP Recovery, no problem but the phone blocks always on the MI logo.
I tried TWRP 3.1.0, 3.0.2. and also the Recovery from superluminal (TS 3.0.2-0) but always the same problem.
What can I do to have a recovery ?
Thanks a lot for your answers !
Do you have an unlocked bootloader?
Trimis de pe al meu Mi-4c folosind Tapatalk
Yes, the command C:\adb>fastboot oem device-info says that :
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I finally find a solution !
I tried to install my ROM in fastboot, I erase all the data then I tried to install the ROM but it didn't work (error message "No android-version.txt" or something like that).
My phone was totally block, because I had no Recovery and no ROM...
I remembered the guide to unlock the bootloader with the tools MiFlash. I install an old package (6.1.7) and it worked.
Then I installed the last version of TWRP and then the last stable version from xiaomi.eu
Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.
mackenzie121 said:
Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.
Click to expand...
Click to collapse
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...
paulpier007 said:
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...
Click to expand...
Click to collapse
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s
mackenzie121 said:
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s
Click to expand...
Click to collapse
Did you try running a RUU
thicklizard said:
Did you try running a RUU
Click to expand...
Click to collapse
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9
You can find RUU files here(in thread search):
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
mackenzie121 said:
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9
Click to expand...
Click to collapse
i had same problem,
start unlocking your bootloader on htcdev website and take new token: (fastboot oem get_identifier_token) until you save NEW "Unlock_code.bin” in fastboot directory then : (fastboot flash unlocktoken Unlock_code.bin)
just start all from the beginning and everything should go right
Or
copy RUU to your external sd card and rename to 2PZCIMG (leave the .zip extension untouched); reboot to download mode and it will ask you (in yellow) to choose UP to start the RUU flash (previously copied to the External SD card) or DOWN to cancel flash and make a normal boot.