Hello everyone!
I've been looking for a custom recovery for my HTC Rhyme (Bliss) and I've tried EVERYTHING!
Clockworkmod recovery, 4ExtRecover, Amon Ra Recovery, etc. There is no option in ROM Manager Pro and there are no custom ROMS for my phone. Even if there was a ROM for my phone, I can't flash any ROMS!!! So, I'm desperately waiting for someone to help me or maybe a developer who knows how to build a recovery. Please help me. I've been emailing developers and seeking out options all over the web.
If you can help, thanks.
Bump
Can someone please help me...
I don't think there'll be much development for the Rhyme. It isn't as popular as the other HTC phones, mainly because of it's niche consumer target. It's mostly meant for women, and most of the devs on XDA are guys. Also the phone hasn't become so widespread that they might take interest in developing for it. That's the reason there isn't even a forum for HTC Rhyme in XDA, alongside all the other devices. So I guess you're at a dead end and stuck with stock. :-\ Maybe something will come up if you're lucky!
Hopefully something comes up because I can't even flash a kernel or anythign...thanks!
It may be a girls phone, but the boys have to maintain them. Also the Sense 3.5 must make it an interesting test bed? Vote for a forum.
Post a request here: http://forum.xda-developers.com/show....php?t=1301121
http://forum.xda-developers.com/showthread.php?t=1416406
Sorry, I put a bad link above. This one works.
Hello everyone !
I've got good news : after a lot of search, I found a chinese site which explains how to flash an unofficial ClockworkMod 5.0.2.7 on the HTC Rhyme.
I don't understand chinese, and so a guy helped me on phonandroid.com (a French forum) : he found the PI46IMG.zip file on MediaFire.
Here is the url (I'm not allowed to post links) : http :// www . mediafire . com/?xu8o6ppiu00e76z
The bootloader autoflash method (puting the file in the microSD's root) didn't worked for me (incorrect CID), but a fastboot flash did !
Here are informations (got with fastboot) about my phone, on which it worked :
Code:
> fastboot getvar all
version: 0.5
version-bootloader: 1.30.0004
version-baseband: 3822.09.00.08_M
version-cpld: None
version-microp: None
version-main: 1.29.401.11
product: bliss
platform: HBOOT-7630
modelid: PI4610000
cidnum: HTC__203
partition-layout: Generic
security: on
build-mode: SHIP
commitno-bootloader: 693a31ef
hbootpreupdate: 12
gencheckpt: 0
So to flash the unofficial CWM 5.0.2.7, someone must :
- Unlock the bootloader
- Download the PI46IMG.zip file (4.17MB)
- Unzip the file on the hard drive
- Reboot into fastboot (via
Code:
adb reboot bootloader
for example)
- Flash the recovery.img :
Code:
fastboot flash recovery recovery.img
Enjoy !
PS: Sorry if my English isn't very good, I'm French.
I'm really unsure of what you mean by unzip the file on the hard drive...do you mean on the phone like I'm flashing a radio? and then what do I do after that and thanks btw!!
Tried this several times. It's not working for me. In fact, I've tried everything I could find about rooting the Rhyme and NOTHING has panned out. The only thing that I've been able to do successfully is unlock/relock the bootloader. I've tried flashing numerous recoveries and even an RUU mod. I have no success using methods that others have used and they worked for them. ZergRush is what most have used but I get nowhere with it. Now, I can't even get the stock recovery to boot.
This is my wife's phone and I really want to root it so that she can have the benefit of being able to completely backup everything, in addition to all the other great perks that come with root.
Any help would be great.
Thanks.
@rankelvin: by "unzip the file on the hard drive" I mean on your computer, as the only way to flash a recovery or a boot image on the Rhyme is with the fastboot command and an unlocked bootloader.
@RuLEoF2: ZergRush almost worked for me, but not permanently. I think the best way to have a real root for the Rhyme is to flash an already rooted ROM, like the one I published (you can search here for "Aurore Rhyme 1.0"), but you need a recovery to do that... I thought the fastboot method would work for everyone, it's weird it doesn't... What does the phone do when you try to boot on the recovery ?
It goes to the white HTC screen for a few seconds, then to a black screen with an image of a phone and a tiny caption saying something about updating. That only lasts about a second where it then goes to the infamous red triangle screen.
I have to hold down the power button for about 10 seconds to get it to power down from there.
I've tried flashing with fastboot from my PC (no joke) at least 20 times with several different recovery downloads. No good. It never takes.
---------- Post added at 02:10 PM ---------- Previous post was at 01:31 PM ----------
Here's what I got with a recovery a just tried to flash. The recovery image was extracted from an RUU.
C:\android>fastboot flash recovery recovery_signed.img
sending 'recovery' (4018 KB)...
OKAY [ 2.656s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.328s
The infamous red triangle screen is normal with stock recovery. You have to press the power button while holding the volume up button to enter in the recovery from there.
About the "signature verify fail", is the bootloader really unlocked ? There is no signature verification on my phone when I flash something with fastboot...
Ok... I am able to get to the recovery that way.
The bootloader may have been locked on that flash attempt. I've been bouncing back and forth, trying different processes. I unlocked it again a little while ago and flashed a boot.img which worked fine.
As an experiment, I just tried flashing Amon Ra for Rezound, It said that it installed "okay" but it wouldn't load. No surprise there. So I re-flashed the recovery image from earlier and it installed "okay" and that one loaded just fine. The main thing that I wanted to know from this was I even able to flash a recovery at all and it appears so.
That recovery image is the only one I have and it looks like it's the stock "Android system recovery <3a>". I haven't been able to find any custom recoveries as of yet.
The only one custom recovery made for the Rhyme I found after a long search is the one on MediaFire I linked before. I don't know if there is any other which could work... :/
I tried that one before and again just now. It fails saying "Model ID incorrect!".
I am able to extract the files with 7zip. Is there something I can do to modify the txt file?
Which files are you able to extract with 7zip ?
And what does this fastboot command return ?
Code:
fastboot getvar modelid
I am able to extract the recovery.img and the android-info.txt files. The txt file contains the following...
"ModelID: PI4610***
ModelID: PI4610000
CIDNUM: 1111111
MainVer: 2.0.0.134076
DelUserData:0"
When I use the fastboot "getvar modelid" command, I get "modelid: PI4611000".
I tried flashing the recovery.img by itself manually with fastboot and it didn't work. It said "okay" but wouldn't boot past the white HTC screen.
OK, so you have better to flash the stock recovery again...
I'll try to find a recovery for your ModelID but it will be difficult. :/
Ok. I did and the stock recovery is working.
Thank you very much. I really do appreciate your help.
So the problem is that the recovery is for the bliss and yours is a blissc.
I found a way to build an official CWM from a stock recovery, but I need informations about your phone to check if the partitions table is the same on the two models.
The informations I need are the return of the following commands, that must be executed on the phone (via adb shell) :
Code:
cat /proc/emmc
mount
If the partitions table is the same, this recovery should work, I just build it from a BlissC RUU's recovery with the official CWM builder :
http://android.4urore.net/blissc/recovery.img
Related
Okay, a little background here:
HTC Evo 4G LTE
Android Version: 2.3.3
Baseband Version: 2.15.00.11.19
Kernel Version 2.6.37.4-cyanogenmod
Mod Version: 7.0.3.1-supersonic
Okay so i acquired this phone in a trade (upgrading from a Evo 4G) and have attempted to activate it with my sprint number. Every time I get to the step where I have to press ##etc... the phone will not cooperate. From what I understand, this is due to the lack of sense.
I have clockwork recovery premium installed and am familiar with the procedure for flashing a rom. I just need someone to point me in the right direction of which rom I need to install/do other things to get this phone activated.
Any help would be greatly appreciated! If any additional info is needed, please let me know! Thanks!
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
om4 said:
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
Click to expand...
Click to collapse
Thank you for the fast response.
Well, I may have already messed up. I saw the check for updates button in clockwork recovery and downloaded the newest cyanogen mod that it recommended ( 7.2. something I think, I can't remember). I flashed it and it is now stuck on the boot logo.
Could I apply the fastboot thing you are talking about to this situation? If so, how do I do that on windows 7? Sorry for my ignorance.
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
http://db.tt/zyPbGmtO
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
om4 said:
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
Click to expand...
Click to collapse
okay i did the steps to the best of my understanding and i got this response in cmd.
recovery-twrp-2.2.2.0-jewel.i
sending 'recovery' (7356 KB).
OKAY [ 1.901s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.902s
Any suggestions?
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
om4 said:
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
Click to expand...
Click to collapse
I can still access my clockwork recovery. Could I just put the mean rom on an sd card and flash it through clockwork? Thanks for your help.
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
om4 said:
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
Click to expand...
Click to collapse
Okay, so I attempted to flash through clockwork recovery and got this message
"Error in /sdcard/MeanROM-ICS-V47-jewel-ltevo.zip
(Status 0)
Installation aborted."
I guess the installer is dependant on twrp, I'm not that familiar with cwm though
om4 said:
I guess the installer is dependant on twrp
Click to expand...
Click to collapse
Okay, well is there any way I can just completely wipe it and get it back to stock? Or anything? Sorry, I am just kind of freaking out a little right now...
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
om4 said:
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
Click to expand...
Click to collapse
Well it identifies it using the fastboot devices cmd. I tried to flash it again on another computer ending in the same error.
Is there any way that the recovery package you linked to could be faulty or something?
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
om4 said:
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0001
(bootloader) version-baseband: 2.15.00.11.19
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 3.26.651.6
(bootloader) serialno: HT08THL01989
(bootloader) imei: 355195000000017
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3655mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3b95cc40
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
om4 said:
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
Click to expand...
Click to collapse
No, every time I try to reboot into cm10 it will hang on the boot logo except one time when it booted into recovery. Could you link me a good guide to relock the bootloader and run ruu?
Is there any where else I can post this to get some additional input?
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
om4 said:
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
Click to expand...
Click to collapse
Well I can't get the phone to do anything now...its just showing a black screen (no backlight or anything). I was going to try to do the zip.
Have I messed up? Now I am getting worried
You can't get into bootloader at all? Have you tried holding power to reboot phone?
Hi Everyone / Anyone,
I've got and HTC One X+ (64GB) not AT&T. Since a week my phone was being slow and doing crazy things so I managed to reinstall the mod I had (Android Revolution HD 6.2).
First of all I made a backup of all my datas (including SD card) and then I restarted the phone in recovery mode. From there I made a wipe dalvik cache and format of SD card FROM the CWM recovery ... (an old one, didn't remember witch version). Things got harder from this moment because my SD Card isn't recognize at all since the moment I formated it from the CWM, I can't even mount it from the recovery. So I managed to reinstall a newer version of the CWM to see if it works and ... It failed.
Now I'm stuck on the bootloader, I don't have any rom installed because I formated everything into the recovery, the recovery isn't working (when I choose recovery I see the "HTC" logo and the phone shutdown or stay stuck on it.
It's been 7 hours I'm reading all the forums and threads out there to find a solution but nothing seems to work.
I tried to install the lastest CWM Recovery (recovery-clockwork-5.8.4.0-endeavoru) but it didn't worked, previous version didn't worked neither (6.0.3.2 or 6.0.2.8).
I also tried the TOOL (JBFTOOL21) found on this forum but I got the same issue with recovery : still not working.
So I've got two main issues to manage and that's why I really need your help, first I need to figure out why I can't even access the recovery : if someone can help me get it back it could be great!
Here's the informations about the phone :
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.30.0000
CPLD : None
MICROP : None
RADIO : None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Oct 17 2012, 22:00:29
Run fastboot getvar all and some info are:
INFOversion: 0.5a
version-bootloader: 1.30.0000
version-baseband: None
version-cpld: None
version-microp: None
version-main: 1.14.401.16
product: enrc2b_u
platform: HBOOT-T30S
modelid: PM3511000
cidnum: HTC__203
battery-status: good
battery-voltage: 3647mV
devpower: 8
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
I really need your help!
Pou007a said:
Hi Everyone / Anyone,
I tried to install the lastest CWM Recovery (recovery-clockwork-5.8.4.0-endeavoru) but it didn't worked, previous version didn't worked neither (6.0.3.2 or 6.0.2.8).
I really need your help!
Click to expand...
Click to collapse
endeavoru = HTC One X
ENRC2B = HTC One X+
U were trying to flash the recovery for the HTC One X on HTC One X+....
Try the CWM recovery from this thread
try flashing this recovery from fastboot and erase the cache....
Then get into CWM recovery and "adb push" the ROM to ur SDCARD
For the Tutorial on adb commands refer to this tutorial
[email protected] said:
endeavoru = HTC One X
ENRC2B = HTC One X+
U were trying to flash the recovery for the HTC One X on HTC One X+....
Try the CWM recovery from this thread
try flashing this recovery from fastboot and erase the cache....
Then get into CWM recovery and "adb push" the ROM to ur SDCARD
For the Tutorial on adb commands refer to this tutorial
Click to expand...
Click to collapse
Thanks a lot, my recovery is now working! But I still have a major problem : my SDCard isn't recognize anymore in the phone since I tried to format it from the CWM Recovery, I can't mount it, I can't format, I can't push anything anymore ... I've been searching again for this but it seems I have no luck.
Into the bootloader when I try to place the HBOOT on it says :
"SD checking...
Failed to open usb master mode
[Preload] Failed to open usb master mode
Loading PM35IMG.zip image...
Failed to open usb master mode
Please plug off usb"
I also get these error into the recovery when trying to mount :
"E:unknown volume for path [/sd-ext]"
But I can access it through the "Install zip" of CWM. It remains impossible anyway to place any ROM onto it, I also tried the "install zip from sideload" but adb doesn't recognize the phone as plugged-in. ADB devices returns an empty list of devices connected ...
Can you help me ... again ?
YES!!!
Finally it was successfull, my phone is reinstalled and working again using your advices, here's the steps I did to make it work :
I reinstalled the good CWM recovery you gave to me, then I tried to access the SDCARD via the recovery but it didn't worked as well so I tried again with ADB (following the link you gave). In fact I had an old version of ADB that's why my phone wasn't recognized. When I used the lastest version and cheking with "adb devices" my phone appears.
I went to the "Install ZIP" section in CWM, and used the "Sideload", just after I checked again via ADB devices which said my phone was in sideload mode, all I had to do is to "adb sideload rom.zip" and here we go, it was installing!
Thank you a hundred times [email protected]! I feel so much better now! It was a real challenge anyway!
Thanks again for you precious help!
Pou007a said:
YES!!!
Finally it was successfull, my phone is reinstalled and working again using your advices, here's the steps I did to make it work :
I reinstalled the good CWM recovery you gave to me, then I tried to access the SDCARD via the recovery but it didn't worked as well so I tried again with ADB (following the link you gave). In fact I had an old version of ADB that's why my phone wasn't recognized. When I used the lastest version and cheking with "adb devices" my phone appears.
I went to the "Install ZIP" section in CWM, and used the "Sideload", just after I checked again via ADB devices which said my phone was in sideload mode, all I had to do is to "adb sideload rom.zip" and here we go, it was installing!
Thank you a hundred times [email protected]! I feel so much better now! It was a real challenge anyway!
Thanks again for you precious help!
Click to expand...
Click to collapse
I m sorry I was AFK till now.....Glad u got sorted by ur owm.....Cool
cant find ruu for my model will costom rom get me out of boot loop
ca""
[email protected] said:
endeavoru = HTC One X
ENRC2B = HTC One X+
U were trying to flash the recovery for the HTC One X on HTC One X+....
Try the CWM recovery from this thread
try flashing this recovery from fastboot and erase the cache....
Then get into CWM recovery and "adb push" the ROM to ur SDCARD
For the Tutorial on adb commands refer to this tutorial
Click to expand...
Click to collapse
""
please!!!1 can someone help me i dont think my problem may be too bad but im very confused by all the slight variations in instructions im seeing.
my hox+ is in a boot loop where it gets to the home sceen i even see notifications coming in then it says process com.android.phone has stopped,
this happened after i foolishly replaced the telephony.db file with one from my hox(not plus) international version.
the phone is rooted but i relocked the bootloader iin preparation to flash ruu but now im realisiing that non of the Ruu's im seeing are for my model.(i have the original telephony.db file)
can install a costom rom from the bootloader screen even though i didnt do a twrp back up( i only downloaded the latest twrp img file usinf rom installer)
hi [email protected] i have the path its /data/data/com.android.providers.telephony/databases/telephony.db but how do i put the file back on that part from the screen, can you give me step by step direcrtions ive been at this 12hrs straight now just trying to get correct information as there seems to be so many slight variations, it will be greatly appreciated...
crasha1 said:
""""
please!!!1 can someone help me i dont think my problem may be too bad but im very confused by all the slight variations in instructions im seeing.
my hox+ is in a boot loop where it gets to the home sceen i even see notifications coming in then it says process com.android.phone has stopped,
this happened after i foolishly replaced the telephony.db file with one from my hox(not plus) international version.
the phone is rooted but i relocked the bootloader iin preparation to flash ruu but now im realisiing that non of the Ruu's im seeing are for my model.(i have the original telephony.db file)
can install a costom rom from the bootloader screen even though i didnt do a twrp back up( i only downloaded the latest twrp img file usinf rom installer)
Click to expand...
Click to collapse
Do u know the path of the telephony.db file in ur phone........??????
U can put ur phone on recovery mode and connect to PC
Since u have the original telephony.db of ur phone u can try putting that back on that path........and reboot and see whether that works.....
if that doesnot work u can try this RUU
[email protected] said:
endeavoru = HTC One X
ENRC2B = HTC One X+
U were trying to flash the recovery for the HTC One X on HTC One X+....
Try the CWM recovery from this thread
try flashing this recovery from fastboot and erase the cache....
Then get into CWM recovery and "adb push" the ROM to ur SDCARD
For the Tutorial on adb commands refer to this tutorial
Click to expand...
Click to collapse
I accidentally flashed recovery to boot portion:crying:. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
now i cant boot into recovery, when i try to it just shows twrp logo nothing else!
please help....
Unlocked bootloader
HBOOT: 1.12.0000
RADIO : 2.1204.135.20
Can u go to fastboot mode by combine hardware buttons? Then u can flash recovery again, then go to recovery at fastboot mode and copy custom rom or stock rom via adb push then etc.
[SOLVED]
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
EDIT :
My actual bootloader :
Code:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OPENDSP-v33.1.0.45.1128
eMMC-boot
Aug 22 2013, 11:48:30:-1
I tried to check my version for RUU reset
Code:
c:\Fastboot>fastboot getvar version-main
version-main: 5.08.163.2
finished. total time: 0.003s
Couldnt find any .exe RUU to help.
Thanks !
Bruwno said:
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
Click to expand...
Click to collapse
Are you using the latest CM 4.4 nightlies ? If yes these rom wont install using TWRP , you need to install either Lloir or Philz CMW recovery to flash them. This is clearly mentioned on Lloir's Post.Again make sure you are Using the enrc2b version of the phone..
http://forum.xda-developers.com/showthread.php?t=2510836
ethanon said:
Are you using the latest CM 4.4 nightlies ? If yes these rom wont install using TWRP , you need to install either Lloir or Philz CMW recovery to flash them. This is clearly mentioned on Lloir's Post.Again make sure you are Using the enrc2b version of the phone..
http://forum.xda-developers.com/showthread.php?t=2510836
Click to expand...
Click to collapse
Thank You for your answer, but i've been using stable cm-10.2.1-enrc2b. So i'm not sure that is the problem, because i've been having the same signature verify fail with other custom roms...
EDIT : Apparently i can't send anything to the /sdcard , i tried to send the right original OTA RUU, for flashing it from the original recovery, still getting this verify signature failed
Bruwno said:
Hi,
I just unlocked my phone using HTCdev/bootloader, and installed TWRP 2.6.3.0 recovery flashing it from HTC ONE X + toolkit .( I first flashed it from fastboot cmd, but it wasnt loading on the recovery when i was selecting it on my bootloader, then it worked just fine from the toolkit ).
After this operations, i tried to flash the last CM custom rom, following their wiki, but when i flash the rom, i get this error :
Code:
c:\Fastboot>fastboot flash /sdcard cm-10.2.1-enrc2b.zip
sending '/sdcard' (208390 KB)... OKAY [ 15.600s]
writing '/sdcard'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 36.999s
I tried to flash the boot.img first, by extracting it appart and using command
Code:
fastboot flash boot boot.img
, then flashing the zip file, but it still doesn't work.
Last thing but not the coolest, I'm now, totally unable to boot on my previous rom.
I can use fastboot/bootloader and recovery perfectly though. Every single file i'm trying to flash into the /sdcard is failing due to signature verification. Please can someone help me ?
Thank you.
( sorry for my bad english writing )
EDIT :
My actual bootloader :
Code:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OPENDSP-v33.1.0.45.1128
eMMC-boot
Aug 22 2013, 11:48:30:-1
I tried to check my version for RUU reset
Code:
c:\Fastboot>fastboot getvar version-main
version-main: 5.08.163.2
finished. total time: 0.003s]/code]
Couldnt find any .exe RUU to help.
Thanks ![/QUOTE]
[QUOTE="Bruwno, post: 50774443, member: 5754687"]Thank You for your answer, but i've been using stable cm-10.2.1-enrc2b. So i'm not sure that is the problem, because i've been having the same signature verify fail with other custom roms...
EDIT : Apparently i can't send anything to the /sdcard , i tried to send the right original OTA RUU, for flashing it from the original recovery, still getting this verify signature failed[/QUOTE]
Sorry Missed that the phone that you are using is EVITA (TelUs vesion of the phone ) and not the enrc2b (International version), Since you are trying to install the cm-10.2.1-enrc2b (International) version of the ROM it is failing .. enrc2b and EVITA are two different phones internally .They have different roms so try installing ROMS meant for EVITA(At&t) and not enrc2b .. This is kinda risky ... might just brick your phone ..
You can try this CM version on your phone
http://forum.xda-developers.com/showthread.php?t=2547118
Click to expand...
Click to collapse
ethanon said:
Sorry Missed that the phone that you are using is EVITA (TelUs vesion of the phone ) and not the enrc2b (International version), Since you are trying to install the cm-10.2.1-enrc2b (International) version of the ROM it is failing .. enrc2b and EVITA are two different phones internally .They have different roms so try installing ROMS meant for EVITA(At&t) and not enrc2b .. This is kinda risky ... might just brick your phone ..
You can try this CM version on your phone
http://forum.xda-developers.com/showthread.php?t=2547118
Click to expand...
Click to collapse
Nope, still nothing able to be uploaded got this verify signature failed error again and again...
Bruwno said:
Nope, still nothing able to be uploaded got this verify signature failed error again and again...
Click to expand...
Click to collapse
which ROM are you installing? also try installing the correct Recovery which is meant for EVITA (HOX) version and try installing the correct rom again. TRY HOX ROMS NOT HOX+ ROMS.
ethanon said:
which ROM are you installing? also try installing the correct Recovery which is meant for EVITA (At&t) version and try installing the correct rom again.
Click to expand...
Click to collapse
Well well well, i see progress down there !
I just tried something. I used the TWRP mount option to mount the sdcard, as it poped on my computer i was able to paste directly the ROMS which was unable to transfer before. I'll try EVITA CM first, after wyping data/cache. I'll let you know. This is pretty encouraging. Thanks for the reading, the ideas !
Bruwno said:
Well well well, i see progress down there !
I just tried something. I used the TWRP mount option to mount the sdcard, as it poped on my computer i was able to paste directly the ROMS which was unable to transfer before. I'll try EVITA CM first, after wyping data/cache. I'll let you know. This is pretty encouraging. Thanks for the reading, the ideas !
Click to expand...
Click to collapse
Make sure you download the HOX Roms from Cyanogenmod website and also my bad I gave you a wrong link in the previous post..
SOLVED
ethanon said:
Make sure you download the HOX Roms from Cyanogenmod website and also my bad I gave you a wrong link in the previous post..
Click to expand...
Click to collapse
After fighting hours to solve the problem, i was able to use a custom recovery to mount the sdcard and transfert it from a graphic interface. Then install it from recovery on the phone.
I still doesn't know why it wasnt transfering before, and why i got the failed verify signature using flash command in fastboot.
I'll run some simulation in order to found out why it's going this way and try to find a solution. I saw a lot of post mentionning this problem but still no solutions.
Thank you though, everything is ok now.
Bruwno said:
After fighting hours to solve the problem, i was able to use a custom recovery to mount the sdcard and transfert it from a graphic interface. Then install it from recovery on the phone.
I still doesn't know why it wasnt transfering before, and why i got the failed verify signature using flash command in fastboot.
I'll run some simulation in order to found out why it's going this way and try to find a solution. I saw a lot of post mentionning this problem but still no solutions.
Thank you though, everything is ok now.
Click to expand...
Click to collapse
For your case in particular I think it has to do with the wrong ROM selection . as you were trying to install enrc2b ROM and Recovery meant for enrc2b.
Good Day community, I have a question to see if you can help me or someone who has already done.
I have my M8 (CID CWS_001 was originally AT & T) and I have SuperCID, I'm s-off, I have unlocked the bootloader, I installed the firmware 2.22.401.5 and TWRM 2.7.1 rom with 7.1 HD Maximus, good now my question is: I want to make the official Developer Edition version of HTC (CID BS_US002 and firmware 2.22.1540.3) the idea is to stick with OTA updates and all could help me with what I want? thank you very much to all.
the idea is that it looks as if you had bought the developer edition version and not the at & t
greetings,
the easiest way would be to run the dev edition RUU, thats what i did, just be sure to change the cid to match.
chizler said:
the easiest way would be to run the dev edition RUU, thats what i did, just be sure to change the cid to match.
Click to expand...
Click to collapse
and where I downloaded the developer edition of RUU friend?
Enviado desde mi HTC One_M8 mediante Tapatalk
the htc dev website, http://www.htcdev.com/devcenter/downloads/P00. just select what you need.
chizler said:
the htc dev website, http://www.htcdev.com/devcenter/downloads/P00. just select what you need.
Click to expand...
Click to collapse
The only file for the Developer Edition that I could find is the MR1 file, but no RUU. I have an AT&T branded M8, fully converted to GPe. Is there a way to run the MR1 to convert my current setup to the Developer Edition?
https://www.dropbox.com/s/txz5sv2r3...31A.4145.02L_release_372510_signed_2.exe?dl=0
That should be the link to it in my dropbox. just give it a min to upload.
Thanks for posting the RUU! I changed my phone's CID to BS_US002 and ran the RUU, only to get the dreaded 159 error. I find myself missing Sense, but I really don't want to revert to AT&T's bloatware-infested version and deal with their constant update delays.
I wonder If the error has something to do with the HBOOT version on the 4.4.4 GPe firmware?
Pretty sure you have to convert back to sense before you run the RUU.
Believe you are [email protected]
jsaldarriaga said:
Good Day community, I have a question to see if you can help me or someone who has already done.
I have my M8 (CID CWS_001 was originally AT & T) and I have SuperCID, I'm s-off, I have unlocked the bootloader, I installed the firmware 2.22.401.5 and TWRM 2.7.1 rom with 7.1 HD Maximus, good now my question is: I want to make the official Developer Edition version of HTC (CID BS_US002 and firmware 2.22.1540.3) the idea is to stick with OTA updates and all could help me with what I want? thank you very much to all.
the idea is that it looks as if you had bought the developer edition version and not the at & t
greetings,
Click to expand...
Click to collapse
I converted my AT&T One M8 to US unlocked version (CID: BS_US001) using the directions in the thread below:
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
This assumes you have S-OFF, and unlocked bootloader and i started with an AT&T stock rom with no root. I am not sure if that is a requirement. For this i did the AT&T RUU by installing an older stock recovery. (AT&T 4.4.3 RUU)
1. Change CID to BS_US001 - open command prompt on your computer and navigate to your fastboot folder; alternatively open the fastboot folder and hold down shift and rightclick, and select open command prompt here. turn USB debugging ON on your phone and connect it to your computer in fastboot mode (turn your phone off and while holding the VOL down button press the power button, the phone goes to bootloader mode, select the fastboot [first option] and press power button, connect the phone to computer and it should say fastboot-usb), verify connection by typing fastboot devices in cmd prompt, it should give your device code. after confirming you are connected via fastboot, type "fastboot oem writecid BS_US001" Reboot bootloader and confirm CID change by typing "fastboot getvar all" and your CID should read "BS_US001".
2. Restore developer nand - for this you will need a custom recovery like TWRP or CWM. If you already have TWRP, then please proceed. To install custom recovery, download TWRP from here. save the twrp recovery image file to your fastboot folder. put your phone in fastboot mode and connect to computer and open cmd prompt from your fastboot folder and type "fastboot flash recovery recoveryname.img", recoveryname should be exactly what the same as TWRP recovery filename. Verify TWRP installation by typing "fastboot reboot-bootloader" and selecting recovery. TWRP recovery should load. Download BS-US001 stock nand from here. At this point boot your phone normally and connect to computer. The navigate to the TWRP folder and backup folder, and paste the BS_US001 nand zip file here. Reboot to TWRP recovery and select restore and select the BS_US001 file you just copied.
3. Install Unlocked version (BS_US001) firmware which includes stock recovery - Download the unlocked version firmware from here. For installing firmware i used this thread. There are two methods however, i used the following method and is my favorite. For this it is recommended that the HT sync manager be uninstalled leaving just the HTC drivers. Place the firmware zip in the fastboot folder. Put your phone in fastboot mode and connect to computer. Open cmd prompt in your fastboot folder. Type "fastboot oem rebootRUU", phone will turnoff and a dark screen with only HTC will appear (this is the RUU mode), now type "fastboot flash zip firmware.zip" replace firmware with the actual filename of the firmware zip. You will see a green progress bar while the firmware is being flashed. I read somewhere that the flash will fail the first time so reflash the firmware a second time by typing "fastboot flash zip firmware.zip". It did fail for me the first time and installed the firmware a second time and it worked. type "fastboot reboot-bootloader" from here select option to reboot your phone normally. Once booted and connected to the internet, you will receive an OTA update notification for 4.4.3. After installing that, another OTA for GPS improvements will appear.
This worked for me. If you are stuck at some point, please read through the original threads. Especially the firware installation thread has a nice FAQ. Goodluck. Please remember, you can not install an OTA while you have a custom recovery. Please wait until you install the firmware zip for accepting the OTA. If the firmware does not install fro some reason, you can pull the stock recovery from the firmware zip and install this recovery using fastboot. Then you can accept the OTAs.
Let me know how it goes.
Converting back to Sense from GPe prior to running the RUU is what I was afraid of. Oh well, I guess I'll have to set aside a couple of hours this weekend. Thanks for the clarification, guys!
here is a link to show you how to do it, once you have all the files it doesnt take 10 mins. i have done it at least 3 times without a problem.
http://forum.xda-developers.com/showthread.php?t=2733523
chizler said:
here is a link to show you how to do it, once you have all the files it doesnt take 10 mins. i have done it at least 3 times without a problem.
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
It worked like a charm. I'm now running a full DevEd. Thanks for all your help!
Glad it worked for you.
This was my first full day running the phone since I converted to DevEd and the first thing I've noticed is that the battery life is through the roof. With moderately heavy usage, I currently have about 40% of battery life left. The phone would have been dead by 6 pm when I was running GPe.
Some Help Please!
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
lsv-1 said:
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
Click to expand...
Click to collapse
I'm having the same problem. I want to convert to Developer edition using a RUU, but none of the Windows 7 machines I can find will run the exe file properly. It's so incredibly frustrating for me! All I need is a working ZIP that doesn't give me the 32 header error
lsv-1 said:
Hello guys, I converted a BS_US001 to gpe, but I want to go back to stock sense. Yesterday I followed this youtube video http://youtu.be/BLbJaSMfFks to restore the newest stock nandroid backup available 2.22....4, I was able to copy the files and restore everything but for some reason after restoring the boot up of the OS was extremely slow it was taking 5 mins or so to fully boot, I think that my mistake was not doing a "Full custom wipe" in TWRP or a compatibility problem I do not know. I ended up re-installing the GPE RUU.
Today I want to start fresh, could you guys please help me with a few simple steps?
I think this is the order I have to follow:
1. Change CID to 11111111
2. Flash 1.54.401.5
3. Boot into stock recovery to Factory reset
4. Install custom recovery TWRP
5. perform a full custom wipe formating system partition
6. reboot into fastboot and change CID to BS_US001
7. Reboot Fastboot and run RUU (or do I have to have a backup restored first?)
I am missing something? Thank you.
Note: I was able to find this RUU_M8_UL_K44_SENSE60_SECURITY_BrightstarUS_WWE_1.54.1540.10_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_372510_signed_2.exe
*UPDATE: I've messing around with this RUU to avoid the error 59 previously described and I found a great tutorial to extract the RUU zip from the .exe, unfortunately the zip appears to be invalid and cannot be opened (someone mentioned that Zip Repair Pro does the trick but that sounds kinda messy) I tried to flash the 0P6BIMG.zip and the error I get is this:
sending 'zip' (633306 KB)...
OKAY [ 38.593s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 40.025s
Could you guys please share the BrightstarUS RUU again just to confirm if the RUU that I downloaded is corrupted or not?
Thank you again!
Click to expand...
Click to collapse
If you are GPe converted then to need to follow the instructions here to go back to Sense.
http://forum.xda-developers.com/showthread.php?t=2733523
Sent from my HTC One_M8 using Tapatalk
I upgraded my OnePlus X today with the community build OxygenOS 3.1.0 using TWRP. There was an error saying that my device was not "OnePlus" but "ONE". So I edited the updater-script and replaced the word "OnePlus" by "ONE" in getprop line and successfully installed the ROM.
Then I connected my phone to PC, enabled OEM unlock and USB debugging, booted into fastboot and typed -
Code:
fastboot oem unlock
It said Okay, done...but there was not action on the phone screen. It stayed in Fastboot mode. I rebooted the phone and it was the same as before. I thought it was okay and continued with the process by booting into fastboot again and flashing TWRP with the command -
Code:
fastboot flash recovery twrp-3.0.2-0-onyx.img
It was successful. Then something weird happened when I typed -
Code:
fastboot boot twrp-3.0.2-0-onyx.img
The output was downloading image, okay. Then booting and the error FAILED(remote: dtb not found).
I tried manually entering the recovery mode, first by volume down + power button and then by advanced reboot menu -> recovery. All that happens is that it stays stuck in Oneplus Logo screen with powered by android written at bottom. I am able to boot into the OS.
I am sure that the image file is not corrupted as I have used the same before a couple of times. Still I tried flashing Stock recovery and a few other image files of the same version of TWRP. The same error comes up every time. Flashing is successful but booting is not. What should I do?
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is my recovery or bootloader corrupt?
I tried this code -
Code:
fastboot oem device-info
Output was -
...
(bootloader) Device tampered : false
(bootloader) Device unlocked : true
(bootloader) Charger screen enabled : false
(bootloader) Display panel :
(bootloader) console_enabled : 0
(bootloader) exec_console_unconsole : 0
OKAY [0.017s]
finished. total time : 0.018s
The problem is when I type -
Code:
fastboot oem unlock
Nothing pops up on my phone.
Maybe the reason is that I had a rooted version of OxygenOS 2.2.2 with TWRP but when I flashed the community build of OxygenOS 3.1.0 somehow TWRP was missing...
What should I do now? I am back at 2.2.2 now as the beta build didn't suit me. This error still persists. The first link above was stock recovery which did work. But I need TWRP back...
....................
Sorry to bother. Issue solved. It was already unlocked and this time flashing and booting in the image worked idk why...
arunmohan16 said:
flash this recovery https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img. If it didn't help, try this http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Thank you dude, i have been looking for this all day
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
tirlibibi said:
I got exactly the same problem, i tested lot of recovery without any luck.
I installed the one from the dropbox, now i got the stock recovery, but, i can do anything, from SDCard or Sideload, the installation of CM13 or Oxygen 3 failed.
Any suggestions ? 4h i tested everything i got in mind to try to fix it.
Thanks
Click to expand...
Click to collapse
This guide will help you. http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 Use this mini tool, http://forum.xda-developers.com/showpost.php?p=64344611&postcount=4