Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[RESOLVED] Updating HBoot

OP zodac01

16th March 2014, 12:36 AM   |  #11  
OP Junior Member
Thanks Meter: 2
 
29 posts
Join Date:Joined: Sep 2011
Quote:
Originally Posted by rosswhite

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/show...38&postcount=1

Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville

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.
16th March 2014, 12:42 AM   |  #12  
rosswhite's Avatar
Senior Member
Thanks Meter: 87
 
270 posts
Join Date:Joined: May 2011
Quote:
Originally Posted by zodac01

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.

No problem at all, glad you got it sorted.
The Following User Says Thank You to rosswhite For This Useful Post: [ View ]
5th May 2014, 12:04 AM   |  #13  
Junior Member
Thanks Meter: 2
 
12 posts
Join Date:Joined: Feb 2012
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/show....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/show....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/show....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/show...74317537341266)
*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!
5th May 2014, 09:31 AM   |  #14  
Rapier's Avatar
Recognized Contributor
Flag Bucharest
Thanks Meter: 1,880
 
3,959 posts
Join Date:Joined: Jun 2008
Donate to Me
More
Quote:
Originally Posted by c1aran

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/show....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/show....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/show....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/show...74317537341266)
*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!

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...
Last edited by Rapier; 5th May 2014 at 09:36 AM.
5th May 2014, 03:53 PM   |  #15  
Junior Member
Thanks Meter: 2
 
12 posts
Join Date:Joined: Feb 2012
Quote:
Originally Posted by Rapier

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...

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!
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes