[Q] unable to flash anyrom after kitkat port - Optimus One, P500, V Q&A, Help & Troubleshooting

Hi there,
I flashed a KitKat port to test it. However, I decided to go back to Cyanogenmod since it didn't work very well.
However, any ROM that I try to flash appears this error:
format() expects 5 args, got 3
E: Error in /storage/sdcard0/cm-7.2.0-p500.zip
(Status 7)
Installation aborted
what can I do to fix this? thanks

Athosbr99 said:
Hi there,
I flashed a KitKat port to test it. However, I decided to go back to Cyanogenmod since it didn't work very well.
However, any ROM that I try to flash appears this error:
format() expects 5 args, got 3
E: Error in /storage/sdcard0/cm-7.2.0-p500.zip
(Status 7)
Installation aborted
what can I do to fix this? thanks
Click to expand...
Click to collapse
To flash that KitKat, you had to place a newer CWM or TWRP recovery version.
To flash cm-7.2, you need to go back to the older recovery!

For KitKat ROMs a recovery equivalent to 6.0.4.5 or newer is required to flash. The newer recoveries are capable of flashing CM 10.2 to CM11. All older Android versions will require the use of an older recovery, pre 6.0.4.5, such as CWM 5.0.2.7 Touch by vivekkalady.

Dovidhalevi said:
To flash that KitKat, you had to place a newer CWM or TWRP recovery version.
To flash cm-7.2, you need to go back to the older recovery!
Click to expand...
Click to collapse
shinobisoft said:
For KitKat ROMs a recovery equivalent to 6.0.4.5 or newer is required to flash. The newer recoveries are capable of flashing CM 10.2 to CM11. All older Android versions will require the use of an older recovery, pre 6.0.4.5, such as CWM 5.0.2.7 Touch by vivekkalady.
Click to expand...
Click to collapse
nice to know that. I will try later
In other subject, I tried other kitkat roms and they gave me that same error. the only one that worked was Omega. is there any reason to that?

Athosbr99 said:
nice to know that. I will try later
In other subject, I tried other kitkat roms and they gave me that same error. the only one that worked was Omega. is there any reason to that?
Click to expand...
Click to collapse
Sorry, I honestly can't say. I no longer use this device so I've been out of the loop for some time now.

Also having same problem
Can't Flash anyother rom after kitkat port.
plz help me.
Thanks

DevG said:
Can't Flash anyother rom after kitkat port.
plz help me.
Thanks
Click to expand...
Click to collapse
Have you installed any custom kernel?
I am also faced this problem and solved by flashing stock rom with KDZ

Related

CM11 Installation - Status 7

Installation keeps aborting (Status 7) every time I try to install the latest CM11 nighties on my TF700. I am using CWM v6.0.3.1 (I believe the latest one). I've also tried previous versions of CM11 and they also won't flash, CM10.2 seems to work fine.
Any help would be great!
Thanks!
Update Recovery
mangcool said:
Installation keeps aborting (Status 7) every time I try to install the latest CM11 nighties on my TF700. I am using CWM v6.0.3.1 (I believe the latest one). I've also tried previous versions of CM11 and they also won't flash, CM10.2 seems to work fine.
Any help would be great!
Thanks!
Click to expand...
Click to collapse
You need to update your recovery to 6.0.4.6 recovery.
foothill17 said:
You need to update your recovery to 6.0.4.6 recovery.
Click to expand...
Click to collapse
Got it! Thanks!
Didn't know that's the latest one that supports KK.
Switched back to CM 10.2, though. CM11 is a little laggy and unresposive at times on the TF700.
Thanks for your help!

Can't flash any ROM!

I have tried different recoveries and ROMS and they all fail telling me that I have the wrong ROM for the device. CM11 (P51xx) and the Omni ROM are just 2 that I have tried. I have the WiFi (5113) and have managed to get the MK3 (4.2.2 build) back via Odin and rooted but that's as far as I can get. Any ideas?
Have you tried to flash a custom ROM with CWM with different versions?
Mord Fustang said:
Have you tried to flash a custom ROM with CWM with different versions?
Click to expand...
Click to collapse
Yup
Make sure you are using the correct recovery for your device.
To flash KitKat Roms you need at least CWM 6.0.4.4 or newer, same for CWM based recoverys.
Latest PhilZ Touch will work too to flash KitKat too.
Else try TWRP 2.6.3.4.
Some recoverys in my thread, link in my signature.
CWM Swipe will get an update later or tomorrow to 6.0.4.7 Swipe
Android-Andi said:
Make sure you are using the correct recovery for your device.
To flash KitKat Roms you need at least CWM 6.0.4.4 or newer, same for CWM based recoverys.
Latest PhilZ Touch will work too to flash KitKat too.
Else try TWRP 2.6.3.4.
Some recoverys in my thread, link in my signature.
CWM Swipe will get an update later or tomorrow to 6.0.4.7 Swipe
Click to expand...
Click to collapse
That did it!! Thanks much!

[RESOLVED] Updating HBoot

Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
zodac01 said:
Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
Click to expand...
Click to collapse
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
ayyu3m said:
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
Click to expand...
Click to collapse
Ha, a nice strong "no". Thank you for that - good thing I came here to check first then.
Ok, first things first, I've tried updating using the OTA, but it doesn't install. I'm using TWRP v2.6. I could get the error code, but I think I read somewhere that you can't (or shouldn't) install OTA with custom bootloaders? I was hoping to use CM if possible anyway, so hopefully shouldn't have to worry about that (unless that's the way to update the HBoot...)
As for the other info, my HBoot is v1.13 and my CID is O2___01.
807 94346552
Anyone with any information?
zodac01 said:
Anyone with any information?
Click to expand...
Click to collapse
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
rosswhite said:
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
Click to expand...
Click to collapse
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
zodac01 said:
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
Click to expand...
Click to collapse
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
rosswhite said:
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
Click to expand...
Click to collapse
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
zodac01 said:
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
Click to expand...
Click to collapse
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
zodac01 said:
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
Click to expand...
Click to collapse
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
rosswhite said:
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
Click to expand...
Click to collapse
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
zodac01 said:
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
Click to expand...
Click to collapse
No problem at all, glad you got it sorted.
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
c1aran said:
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
Click to expand...
Click to collapse
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Sent from nowhere over the air...
Rapier said:
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
LINK REMOVED
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hi,
I got a bit frustrated last night and must have missed that information in the CM11 thread. I had a look at that link and it has fixed my issues. Thank you very much!

[Q] stuck on TWRP 2.5.0.0 + cannot install cm11

lets get down to business,
I'm currently running CM10.2.0 with TWRP 2.5.0.0 as recovery, I recently tried updating to latest CM11 M4 snapshot but received the following error:
"error executing updater binary"
I read that i need to update recovery (2.6.3.0 latest) but encountered a roadblock.
I downloaded the .img to internal memory in root directory and used the terminal emulator as per TWRP instructions, rebooted into recovery but it still showed 2.5.0.0. I then tried using ADB but ran into the same issue
I've thought about using CWM but when I install ROM toolbox it says only tf200 is officially supported.
lastly tried Goomanager but it gave me an error saying recovery not found.
any thoughts on this?
any ideas would be appreciated
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
n00b1c1d3 said:
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
Click to expand...
Click to collapse
What is your bootloader version is it 10.1.6.27.x
The last digit really does not matter...
If so you need this recovery here http://forum.xda-developers.com/showthread.php?t=2691886
Let me know if I can help you with anything else..
Thx Josh
ended up using that method and all went well.
thanks

philz 4.0 cant update

i flashed my p5110 with the files philz_touch_5.00.5-p5100.tar (through odin) and philz_touch_5.00.5-p5100 from the recovery menu.
everytime i try to install a new rom i always get status 7 error
the roms i tried are:
lineage-11-20171126-1223-UNOFFICIAL-espresso3g
Slim-p5110-4.4.4.build.9.0-OFFICIAL-8287
DhollmenK-4.4.4_p5110-20150619
any ideas what to do???:crying::crying::crying:
hombregr said:
i flashed my p5110 with the files philz_touch_5.00.5-p5100.tar (through odin) and philz_touch_5.00.5-p5100 from the recovery menu.
everytime i try to install a new rom i always get status 7 error
the roms i tried are:
lineage-11-20171126-1223-UNOFFICIAL-espresso3g
Slim-p5110-4.4.4.build.9.0-OFFICIAL-8287
DhollmenK-4.4.4_p5110-20150619
any ideas what to do???:crying::crying::crying:
Click to expand...
Click to collapse
Use the latest espresso-common twrp by Andi.
Also keep in mind that you should never flash your device with incompatible recoveries or roms because it could get bricked. Don't flash stuff for a p5100 to your p5110; they are different devices.
Thank you... I changed the twrp and it worked like a charm..

Categories

Resources