i am using the ruu evita 1.73.502.1 zip and my image version is 1.88.707.2 and it gives me an error 155 unknown error.
can it be because its a lower version
lorijuan1024 said:
i am using the ruu evita 1.73.502.1 zip and my image version is 1.88.707.2 and it gives me an error 155 unknown error.
can it be because its a lower version
Click to expand...
Click to collapse
yes it is
you can downgrade using this method:
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
jags_the1 said:
yes it is
you can downgrade using this method:
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
Click to expand...
Click to collapse
Hmm just yesterday I flashed the 1.73 Ruu on top of a rooted 1.85 no hacks needed other than relocking the bootloader
Related
XDA can't find a way to overcome wrong CID issue with HTC One V
Ok, this is device specific to the HTC One V, but the One V community at xda is tiny and I've posted there with zero replies after 24 hrs. Maybe someone else familiar with HTC can help me out here.
I'm trying to flash the HTC EU ROM onto my Asia market HTC One V (unlocked bl, rooted, cwm recovery). The two ROMs are compatible as they are both for the same part number (PK7610000). In the android-info.txt inside both ROM.zips the only difference is the rotten CID.
I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Tried MMC0 and MMC2 (GoldCard generator got errors with MMC1). Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?
CafeKampuchia said:
Ok, this is device specific to the HTC One V, but the One V community at xda is tiny and I've posted there with zero replies after 24 hrs. Maybe someone else familiar with HTC can help me out here.
I'm trying to flash the HTC EU ROM onto my Asia market HTC One V (unlocked bl, rooted, cwm recovery). The two ROMs are compatible as they are both for the same part number (PK7610000). In the android-info.txt inside both ROM.zips the only difference is the rotten CID.
I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?
Click to expand...
Click to collapse
Off hand I would say that whatever tool/method you used to create the goldcard used the wrong mmc value. That is very common with the newer HTC devices. Try to find a tool that supports MMC0/MMC1 and possibly MMC2
Thanks, I'll give that a try this evening.
Any other suggestions?
tpbklake said:
Off hand I would say that whatever tool/method you used to create the goldcard used the wrong mmc value. That is very common with the newer HTC devices. Try to find a tool that supports MMC0/MMC1 and possibly MMC2
Click to expand...
Click to collapse
MMC1 didn't work. SimpleGoldCard.exe reported errors.
MMC2 produced a different CID and successfully generated a GoldCard, but the install failed again: "CID incorrect! Update Fail!"
Any more ideas? It can't be impossible to do this!
DELETE
Persistence
Last bump before conceding defeat.
I htcdev unlocked my phone with the all in one Htc one x program. It all worked fine but i accidentally flashed an htc one x kernel on my sensation! Ive seen people say to just install a new one but when i do that it says an error about the boot.img. Help please!! SON btw
Reatret said:
I htcdev unlocked my phone with the all in one Htc one x program. It all worked fine but i accidentally flashed an htc one x kernel on my sensation! Ive seen people say to just install a new one but when i do that it says an error about the boot.img. Help please!! SON btw
Click to expand...
Click to collapse
Download a ROM, extract its boot.img then use fastboot command:
fastboot flash boot boot.img
Oh and p.s dont use tools designed for other phones in future - why you needed one to htcdev unlock is beyond me though, the instructions are perfectly clear on the htcdev.com website
Jonny said:
Download a ROM, extract its boot.img then use fastboot command:
fastboot flash boot boot.img
Oh and p.s dont use tools designed for other phones in future - why you needed one to htcdev unlock is beyond me though, the instructions are perfectly clear on the htcdev.com website
Click to expand...
Click to collapse
Its a lot easier that way, I found. Anyways, could you pleaselink me to a stable working rom? I dont trust myself on finding one. and what do you mean by "use fastboot command: fastboot flash boot boot.img"
Reatret said:
Its a lot easier that way, I found. Anyways, could you pleaselink me to a stable working rom? I dont trust myself on finding one. and what do you mean by "use fastboot command: fastboot flash boot boot.img"
Click to expand...
Click to collapse
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Jonny said:
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Click to expand...
Click to collapse
Is there a way to get the adb/fastboot files on a bricked phone? :C
lefiese wilful
Jonny said:
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Click to expand...
Click to collapse
Oh nevermind! I got it down, I am downloading ViperS Rom, i understand all your instructions now!! I am very confident this will work, ill reply with results.
Jonny said:
You need the adb/fastboot files to use the fastboot command, there is a link either in the "flashing ROM's with S-ON" guide or in the "Guide to S-OFF, custom recovery and SuperCID" thread - sorry, Im on my phone so cant link it.
Then put the files in C:\adb and open command prompt and type:
cd C:\adb
then press enter
Next you need to extract the boot.img from a Sense ROM zip file - any from the dev thread will do as long as its a Sense ROM - and place boot.img in the C:\adb folder then put phone into bootloader, connect to computer and select "fastboot USB" from the phones bootloader menu and then type the following command into command prompt:
fastboot flash boot boot.img
hit enter then type:
fastboot reboot
press enter and all done
Click to expand...
Click to collapse
By the way, the exact error is 'assert failed: write_raw_image("/tmp/newboot.img","boot")'
Reatret said:
By the way, the exact error is 'assert failed: write_raw_image("/tmp/newboot.img","boot")'
Click to expand...
Click to collapse
Yep, because you are S-ON, the script cant write to the boot partition which is why the fastboot flash boot boot.img workaround is needed
Jonny said:
Yep, because you are S-ON, the script cant write to the boot partition which is why the fastboot flash boot boot.img workaround is needed
Click to expand...
Click to collapse
Do you know where the boot.img is located? I downloaded CoreDrod Sensation and cant seem to find it.
boot.img is located
try to explore or double click the ROM you download ROMname.rar boot.img must in the archive.
Reatret said:
Do you know where the boot.img is located? I downloaded CoreDrod Sensation and cant seem to find it.
Click to expand...
Click to collapse
I dont know where its located in every ROM, just a few. My Sense 3.6 ROM boot.img is located in Extras/Kernel/ but most are just in the root of the file - I do things a little different because of the way my customizations in Aroma Installer work
I have a HTC Cha Cha from my friend. This Cha Cha is originally sold in Hong Kong (I checked it with the phone's IMEI), however when I would like to restore this phone to shipped rom, after I relocked it, I have tried so many different RUU but FAILED. All RUU occured the "Error 131 : Customer ID Error"
I checked the CID of my phone and it appeared as HTC_622.
Here are the RUU I have tried:
1. ruu_chacha_htc_asia_wwe_1.57.707.2_radio_47.23.35.3033h_7.51.35.19_release_228383_signed.exe
2. RUU_Chacha_hTC_Asia_WWE_1.21.707.2_Radio_47.14.35.3030H_7.47.35.17_release_197518_signed.exe
3. RUU_Chacha_hTC_Asia_TW_1.25.709.1_Radio_47.17.35.3033H_7.48.35.14_2_release_199798_signed.exe
4. RUU_Chacha_hTC_Asia_India_1.20.720.1_Radio_47.14.35.3030H_7.47.35.17_release_196443_signed.exe
Actually which RUU can be suitable to restore to stock in my ChaCha with CID HTC_622?
Don't know about the apropriate RUU, but if you have custom recovery you cannot flash any of them. You first need to flash stock recovery before you flash RUU. Here is how I restored my phone a while back via fastboot. I have extracted from RUU rom.zip, and from that zip extracted system.img, boot.img and recovery.img. Then I formated my phone (wipe, format system etc.), connected it in fastboot mode and flashed first recovery.img then boot.img and system.img at the end. Reboot and you will have the stock rom flashed. After that I relocked the bootloader. You can try to extract and flash only recovery.img and then try to run RUU. Hope that this helps.
Regards
didije said:
Don't know about the apropriate RUU, but if you have custom recovery you cannot flash any of them. You first need to flash stock recovery before you flash RUU. Here is how I restored my phone a while back via fastboot. I have extracted from RUU rom.zip, and from that zip extracted system.img, boot.img and recovery.img. Then I formated my phone (wipe, format system etc.), connected it in fastboot mode and flashed first recovery.img then boot.img and system.img at the end. Reboot and you will have the stock rom flashed. After that I relocked the bootloader. You can try to extract and flash only recovery.img and then try to run RUU. Hope that this helps.
Regards
Click to expand...
Click to collapse
would you mind to give me a link for HTC chacha's original firmware (RUU) in zip format? I wanna flash my phone to original firmware. tnx be4
You can find some RUUs here:
http://www.androidruu.com/?developer=Chacha
The easiest way to extract rom.zip from RUU is to run RUU, wait for the setup to start but do not click next and do not close the window. Search the temporary folder (you can find it by entering %temp% into the run command) and you will find rom.zip inside one of the folders located in this temporary folder. Copy rom.zip somewhere you can find easily for future use and then close the RUU window.
Regards.
Hi, after flashing an incorrect version of gapps onto a CM10.1 nightly rom I have worked myself into a very tight corner.
The phone is s-on, wont boot into android and also I am unable to enter any kind of recovery. I have tried fastboot flash recovery and fastboot boot recovery with CWM and TWRP and flashing a stock recovery extracted from an RUU. All I get when trying to enter recovery is a reboot then HTC white screen then boot loop. I am under the impression all I can possibly do at this stage is to flash a stock RUU yet I can only find one RUU that matches my ORANG_001 cid and that gives me the error of "44 hboot version check fail". So I then tried to flash a more recent RUU but they all have different cid numbers. If I attempt to modify the android-info.txt to add my cid I corrupt the zip and get a sign verification failure. I've attempted to make a new zip and then resign it with AutoSign.zip but again I get a "12 signature verify fail."
If anyone could shine any light on altering cid inside RUU or possibly a way of me getting back into recovery it would be greatly appreciated.
guymalpass said:
Hi, after flashing an incorrect version of gapps onto a CM10.1 nightly rom I have worked myself into a very tight corner.
The phone is s-on, wont boot into android and also I am unable to enter any kind of recovery. I have tried fastboot flash recovery and fastboot boot recovery with CWM and TWRP and flashing a stock recovery extracted from an RUU. All I get when trying to enter recovery is a reboot then HTC white screen then boot loop. I am under the impression all I can possibly do at this stage is to flash a stock RUU yet I can only find one RUU that matches my ORANG_001 cid and that gives me the error of "44 hboot version check fail". So I then tried to flash a more recent RUU but they all have different cid numbers. If I attempt to modify the android-info.txt to add my cid I corrupt the zip and get a sign verification failure. I've attempted to make a new zip and then resign it with AutoSign.zip but again I get a "12 signature verify fail."
If anyone could shine any light on altering cid inside RUU or possibly a way of me getting back into recovery it would be greatly appreciated.
Click to expand...
Click to collapse
try to gain s-off.
you can install every ruu then and chaning cid will be much easier then.
guymalpass said:
Hi, after flashing an incorrect version of gapps onto a CM10.1 nightly rom I have worked myself into a very tight corner.
The phone is s-on, wont boot into android and also I am unable to enter any kind of recovery. I have tried fastboot flash recovery and fastboot boot recovery with CWM and TWRP and flashing a stock recovery extracted from an RUU. All I get when trying to enter recovery is a reboot then HTC white screen then boot loop. I am under the impression all I can possibly do at this stage is to flash a stock RUU yet I can only find one RUU that matches my ORANG_001 cid and that gives me the error of "44 hboot version check fail". So I then tried to flash a more recent RUU but they all have different cid numbers. If I attempt to modify the android-info.txt to add my cid I corrupt the zip and get a sign verification failure. I've attempted to make a new zip and then resign it with AutoSign.zip but again I get a "12 signature verify fail."
If anyone could shine any light on altering cid inside RUU or possibly a way of me getting back into recovery it would be greatly appreciated.
Click to expand...
Click to collapse
To run the latest cm hou have to have a hboot of 2.15. What's your current version?
Did you btw flash the boot.img seperatly?
If s-on you have to.
Flash a RUU (cant flash a RUU with a lower hboot than that you already have)
Than do otas till your on jb. Then go back to custom roms.
Verstuurd van mijn HTC One S met Tapatalk
Thanks for the replies, is it possible to s-off when I can only access bootloader though? My hboot is 2.15.0000 and yes I had flashed the boot.img separately, the rom worked perfectly until I flashed the wrong gapps. I would love to flash an RUU but I can only find one that is compatible with my cid and it won't install.
guymalpass said:
[...] and also I am unable to enter any kind of recovery. I have tried fastboot flash recovery and fastboot boot recovery with CWM and TWRP and flashing a stock recovery extracted from an RUU. All I get when trying to enter recovery is a reboot then HTC white screen then boot loop.
Click to expand...
Click to collapse
fastboot erase cache
^-- this often / sometimes / maybe fixes the situation where recovery fails to boot.
guymalpass said:
Hi, after flashing an incorrect version of gapps onto a CM10.1 nightly rom I have worked myself into a very tight corner.
The phone is s-on, wont boot into android and also I am unable to enter any kind of recovery. I have tried fastboot flash recovery and fastboot boot recovery with CWM and TWRP and flashing a stock recovery extracted from an RUU. All I get when trying to enter recovery is a reboot then HTC white screen then boot loop. I am under the impression all I can possibly do at this stage is to flash a stock RUU yet I can only find one RUU that matches my ORANG_001 cid and that gives me the error of "44 hboot version check fail". So I then tried to flash a more recent RUU but they all have different cid numbers. If I attempt to modify the android-info.txt to add my cid I corrupt the zip and get a sign verification failure. I've attempted to make a new zip and then resign it with AutoSign.zip but again I get a "12 signature verify fail."
If anyone could shine any light on altering cid inside RUU or possibly a way of me getting back into recovery it would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using Hansoons All-in-one toolkit to flash a recovery?
It all started yesterday where i was trying to update (InsertCoin) which for some reason made my phone shut down mid-way through the installation process...
I had to reboot my phone back into recovery to wipe system/cache/data to reinstall...For some reason this wiped/damaged everything but the bootloader ofc.
(Bye go all my pictures, whatsapp conversations etc...)
This made me not being able to boot into my recovery aswell
I still can't get back into my recovery, and i've tried flashing the recovery over and over again via fastboot flash recovery twrp.img
When i try to flash the recovery, it succeeds but when i try to boot into it, it blinks the splash screen with odd intervals, i dont know if this means that its trying over and over again...I'm sort of desperate here...any help?
sidenote here: I'm in linux
you should've updated firmware to hboot 2.22 needed for IC, then you need to install the latest recovery 2.7.1.1 from twrp website
twrp here: http://techerrata.com/browse/twrp2/m4ul
new firmware here :http://forum.xda-developers.com/showthread.php?t=2759131
I have not updated it, will go and do that now,
Code:
[email protected]:/media/leon/*censor*/Android/ROMS/Millium$ sudo fastboot flash zip firmware.zip
[sudo] password for leon:
target reported max download size of 800227328 bytes
sending 'zip' (19549 KB)...
OKAY [ 2.466s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 4.305s
Right.....!?
I really don't want to reboot to bootloader at the moment...since the update failed...
Apparently i am S-ON and therefor need to obtain s-off, but i don't have an android system installed..how
s-off required to flash firmware or if s-on, bootloader needs to be re-locked, sorry i assumed you knew that! maybe create a signature giving details of your device for future, it does help.
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
Click to expand...
Click to collapse
not work ?? ok, then you will need to s-off the device, unlock first,you need SUPERCID also
Braddison said:
not work ?? ok, then you will need to s-off the device, unlock first
Click to expand...
Click to collapse
It did, sorry, didnt edit the post quick enough
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
Click to expand...
Click to collapse
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Braddison said:
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
well you've done everything that i done when i tried out Insertcoin rom for a few days and never had any of your issues. so not sure whats going on.
- unlocked bootloader
- get s-off
- get supercid
- update firmware
- get latest twrp recoverry
- install Insert Coin
use the fix miniwhooper posted on her firmware thread ....Flash stock recovery and factory reset from boot loader. It will fix you /data partition.. then flash custom recovery and it should be fixed
`leon said:
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
Click to expand...
Click to collapse
Make sure you are in the folder your rom zip is located.
Run the command...
adb push filename.zip /sdcard
Wait around 10 minutes as it will not give you progress
go back to TWRP main page and install, choose SDcard and the zip file you just uploaded should be there.
hello @AnGrY sCoTsMaN
i have the exact same problem but i flashed cm.12.1 cant boot in recovery or flash anything using adb
hboot os 2.22 it says unlocked but it seems not
can you please help me out
Edit: problem solved without doing anything