Yes, I am unlocked and rooted. Running carbon 4/1 nightly atm and using KTK but whenever I try to flash a new kernel I get an error. In TWRP it says "Error flashing update binary" and in CWM I get Status Error 7. Both are latest versions and the kernels are for my version of Android as well and the downloads did download successfully. Just got no clue what is happening.
U can use SU to update ur binary. I also recommend to have the latest twrp (2.6.3.1. I read that 7.0 ppl having trouble with backups) or cwm recovery
Sent from my SCH-I535 using Tapatalk
Updated my SU binary and still getting the same error. "Error executing updater binary"
I guess I can try CWM
Sent from my SCH-I535 using xda app-developers app
Tried it in CWM. Got status error 7.
Sent from my SCH-I535 using xda app-developers app
Do a clean install. Factory reset format. Then flash rom and different kernel
Sent from my SCH-I535 using Tapatalk
DubleJayJ said:
Yes, I am unlocked and rooted. Running carbon 4/1 nightly atm and using KTK but whenever I try to flash a new kernel I get an error. In TWRP it says "Error flashing update binary" and in CWM I get Status Error 7. Both are latest versions and the kernels are for my version of Android as well and the downloads did download successfully. Just got no clue what is happening.
Click to expand...
Click to collapse
Status 7 error indicates you need to update your recovery
Answer should be stickied
ShapesBlue said:
Status 7 error indicates you need to update your recovery
Click to expand...
Click to collapse
Thanks, finally a proper response!!! :good::good::good:
Related
I am working with Skyrocket I727R (the rogers phone), and have installed LiquidSmooth 4.1.2 which I must say works very well. I just wanted to try another rom and update to JB 4.2.2.
I thought when I could not flash JellyBeer and Paranoid Android getting error 7 that it was due to the Assert line in the updater-script. But after removing the Assert Line, it still would not flash. I also found out I cannot flash any of the Roms. I am using TWRP 2440. which I had to install through Odin as the TWRP.zip file would not flash properly with CWM recovery. It said it completed successfully but on reboot nothng would happen, so I had to install the TWRP.tar through ODIN. Could it be my SD card, or a problem with recovery? Should I try a different version of TWRP?
Thanks for any help.
The twrp version you're using is very old. New roms won't flash on it. The latest is 2.5.x.x
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
WARRENFRALEIGH said:
I am working with Skyrocket I727R (the rogers phone), and have installed LiquidSmooth 4.1.2 which I must say works very well. I just wanted to try another rom and update to JB 4.2.2.
I thought when I could not flash JellyBeer and Paranoid Android getting error 7 that it was due to the Assert line in the updater-script. But after removing the Assert Line, it still would not flash. I also found out I cannot flash any of the Roms. I am using TWRP 2440. which I had to install through Odin as the TWRP.zip file would not flash properly with CWM recovery. It said it completed successfully but on reboot nothng would happen, so I had to install the TWRP.tar through ODIN. Could it be my SD card, or a problem with recovery? Should I try a different version of TWRP?
Thanks for any help.
Click to expand...
Click to collapse
Use the goo manager app to install twrp. Yours is old as dirt.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
xcrazydx said:
Use the goo manager app to install twrp. Yours is old as dirt.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I updated TWRP using Goo manager as suggested. I tried installing Revolt which does not have an assert line. It failed. Error with updater-binary.
Tried installing Beanstalk (newest version). Also had error with update-binary. Then I edited the updater-script removing the assert line. Eureka, it worked.
WARRENFRALEIGH said:
I updated TWRP using Goo manager as suggested. I tried installing Revolt which does not have an assert line. It failed. Error with updater-binary.
Tried installing Beanstalk (newest version). Also had error with update-binary. Then I edited the updater-script removing the assert line. Eureka, it worked.
Click to expand...
Click to collapse
Sweet!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
I was just trying to flash the alpha build 2 of KitKat 4.4 on my nexus s when suddenly in between it failed and said No file_ contexts set_ metadata rexursive_ some changes failed.. Something like that and failed to flash.. I have the latest version of recovery. Wiped data, cache, dalvik cache, system but it is still like this..
Sent from my Nexus S using xda app-developers app
Problem occured flashing 4.4 KitKat
Did you you use the latest CWM recovery which is ver. 6.0.4.3? Atm that's the only one able to flash aosp kitkat 4.4.
Hi guys. My problem is different from the OP's.
After flashing the alpha 2 I can no longer boot into Recovery. Now when I am in the bootloader and select Recovery the phone reboots normally into Android.
Also SU is requesting to update binaries, but the update fails from the app. Was thinking about flashing it again but without getting to Recovery it is not possible..
Cheers
filipeglfw said:
Hi guys. My problem is different from the OP's.
After flashing the alpha 2 I can no longer boot into Recovery. Now when I am in the bootloader and select Recovery the phone reboots normally into Android.
Also SU is requesting to update binaries, but the update fails from the app. Was thinking about flashing it again but without getting to Recovery it is not possible..
Cheers
Click to expand...
Click to collapse
Do you still have superuser function? Outdated is fine if your phone will grant su requests.. If you have su get the CWM app and have it update your recovery..
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
...get the CWM app and have it update your recovery..
Click to expand...
Click to collapse
Actually ROM Manager downgraded the CWM to the non-touch version from the touch one that I had downloaded from their site.
It is working well now though... I can live with the non-touch version
Thanks a lot!
filipeglfw said:
Actually ROM Manager downgraded the CWM to the non-touch version from the touch one that I had downloaded from their site.
It is working well now though... I can live with the non-touch version
Thanks a lot!
Click to expand...
Click to collapse
Now that your recovery is back, reflash the touch version..
Sent from my Nexus S using XDA Premium 4 mobile app
I am trying to use flash paranoid android and flashing this version of gapps along with it: pa_gapps-stock-4.4.2-20140412-signed. When I go to flash the ROM, it succeeds without issue, but when I go to flash gapps it says that it cant open the zip fie of gapps and than in parenthesis it says (bad). and than it says installation aborted. Please help.
maxell505 said:
I am trying to use flash paranoid android and flashing this version of gapps along with it: pa_gapps-stock-4.4.2-20140412-signed. When I go to flash the ROM, it succeeds without issue, but when I go to flash gapps it says that it cant open the zip fie of gapps and than in parenthesis it says (bad). and than it says installation aborted. Please help.
Click to expand...
Click to collapse
Maybe it was a bad download?
Sent from my Nexus 7 using xda app-developers app
Kreateablaze said:
Maybe it was a bad download?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have downloaded it about 3 times and tried to flash it. Previously I tried to do this with OmniROM but than I just gave up and restored my system back to stock. Now I am trying it with Paranoid Android and the same thing is happening.
maxell505 said:
I have downloaded it about 3 times and tried to flash it. Previously I tried to do this with OmniROM but than I just gave up and restored my system back to stock. Now I am trying it with Paranoid Android and the same thing is happening.
Click to expand...
Click to collapse
Are you checking the md5sum of the download? Do that to make sure it's a good download
Sent from my SAMSUNG-SGH-I727
I wanted to try a KitKat ROM so i downloaded a couple on PC and transferred to SD card. I did a backup (which really saved me lol) and then, as instructed , formatted system, data, and cache. Wiped Dalvik and flashed ROM (Paranoid Android 4.0). It started but after the "installing update" message I got a error message " error /location of zip/name of zip (status0)". I thought it meant that the zip was corrupted so i downloaded on PC again. Transferred to SD and tried to install following the same stepsand got the error again. After that I tried to install another ROM(Validus 5.1) and still got the error. Decided to restore and see if i could get help before trying again. Any ideas what is wrong? Thanks in advance for any help
EDIT can dev please move I thought i was posting in troubleshooting section. Sorry
explicitKC said:
I wanted to try a KitKat ROM so i downloaded a couple on PC and transferred to SD card. I did a backup (which really saved me lol) and then, as instructed , formatted system, data, and cache. Wiped Dalvik and flashed ROM (Paranoid Android 4.0). It started but after the "installing update" message I got a error message " error /location of zip/name of zip (status0)". I thought it meant that the zip was corrupted so i downloaded on PC again. Transferred to SD and tried to install following the same stepsand got the error again. After that I tried to install another ROM(Validus 5.1) and still got the error. Decided to restore and see if i could get help before trying again. Any ideas what is wrong? Thanks in advance for any help
EDIT can dev please move I thought i was posting in troubleshooting section. Sorry
Click to expand...
Click to collapse
Are you using the most recent version of TWRP, CWM, or Philz recovery? Are you currently running a custom ROM?
EDIT: Thread reported to mod as "Thread needs moving or maintenance."
Sent from my SGH-T989 using Tapatalk
jrc2 said:
Are you using the most recent version of TWRP, CWM, or Philz recovery? Are you currently running a custom ROM?
EDIT: Thread reported to mod as "Thread needs moving or maintenance."
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I'm using a custom ROM right now, I don't know if the Philz I have is the most recent. Would that cause errors? How would i know what version I have installed.
explicitKC said:
I'm using a custom ROM right now, I don't know if the Philz I have is the most recent. Would that cause errors? How would i know what version I have installed.
Click to expand...
Click to collapse
If the version of Philz you are using is from JB then that could cause the errors.
Sent from my SGH-T989 using Tapatalk
jrc2 said:
If the version of Philz you are using is from JB then that could cause the errors.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ok I installed CWM recovery v6.0.1.2. I tried installing Paranoid Android again and after it got to Installing Update I got a message
set_metadata_recursive: some changes failed
E:Error in /external_sd/zips/pa_p3113-4.3-BETA4-20140513.zip
(Status 7)
Installation aborted.
explicitKC said:
ok I installed CWM recovery v6.0.1.2. I tried installing Paranoid Android again and after it got to Installing Update I got a message
set_metadata_recursive: some changes failed
E:Error in /external_sd/zips/pa_p3113-4.3-BETA4-20140513.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Status 7 means that your recovery is out of date. I am running AOSPA Beta4 on my p3113 and installed it using the latest TWRP from the below thread. The version of cwm in that thread should also work.
Latest recoveries: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989 using Tapatalk
jrc2 said:
Status 7 means that your recovery is out of date. I am running AOSPA Beta4 on my p3113 and installed it using the latest TWRP from the below thread. The version of cwm in that thread should also work.
Latest recoveries: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
TY i'll download and try, Is there a recommended recovery? Or is it just personal preference?
explicitKC said:
TY i'll download and try, Is there a recommended recovery? Or is it just personal preference?
Click to expand...
Click to collapse
I am currently using TWRP, but I have used PhilzTouch in the past. They both work pretty well. TWRP has bigger buttons that are spaced out better and has an easier interface to use. PhilzTouch has some other features but isn't as polished. It is just a matter of personal preference. Some Roms will have a recommended recovery listed, though.
Also, to make sure that the zip you download isn't corrupted, check the md5 of the zip you download against the md5 on the download page.
Sent from my SGH-T989 using Tapatalk
Biggest advantage of using Phillz touch is that it can detect OTG cable,so you can flash ROMs from USB device as well;on the other hand, TWRP allows you to flash 10 zips at the same time,it will release the overhead of selecting Zip one after another manually. So choose your options wisely.
Edit:-
One more thing I would like to add,Phillz touch blackhawk supports dual-booting through next kernel
lokesh.3440 said:
Biggest advantage of using Phillz touch is that it can detect OTG cable,so you can flash ROMs from USB device as well;on the other hand, TWRP allows you to flash 10 zips at the same time,it will release the overhead of selecting Zip one after another manually. So choose your options wisely.
Click to expand...
Click to collapse
The version of TWRP I linked to also supports otg.
Sent from my SGH-T989 using Tapatalk
jrc2 said:
The version of TWRP I linked to also supports otg.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
really,which one are you referring to ? TWRP 2.7.0.3 ?
lokesh.3440 said:
really,which one are you referring to ? TWRP 2.7.0.3 ?
Click to expand...
Click to collapse
I am currently using 2.7.0.1 but 2.7.0.3 also has it. The one that I linked to was compiled by Android-Andi
Sent from my SGH-T989 using XDA mobile app
jrc2 said:
Status 7 means that your recovery is out of date. I am running AOSPA Beta4 on my p3113 and installed it using the latest TWRP from the below thread. The version of cwm in that thread should also work.
Latest recoveries: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Just wanted to say thanks again to jrc2. I went with TWRP because backup to sd card was not working on CWM and Philz. Backup would start and in the middle of backing up data or system tab would just reboot. But TWRP looks ok and flashed with no problems.
Hi guys. I read alot those days about everything and now i'm trying to instal CARBON ROM to my nexus 5.
When i'm in TWRP, i get this error when i try to instal the ROM:
Installing ' /sdcard/CARBON-KK-NIGHTLY-20141002-0125-hammerhead.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file fould
Verifying zip signature...
assert failure: getprop("ro.bootloader") == "HHZ11k"
E:Error exeuting updater binary in zip ' /sdcard/CARBON-KKNIGHTLY-20141002-0125-hammerhead.zip'
Error flashing zip ' /sdcard/CARBON-KKNIGHTLY-20141002-0125-hammerhead.zip'
Updating partition details...
I updated the bootloader and still it gets the error.
The steps i use when i try to flash the rom are:
1. wipe: For TWRP- wipe system partition, data, cache and dalvik
2. get to install..
Hope you know this problem because i'm sick of it I tried to install a custom kermel, and bom, the error apears again.
Thank you!
p.s: sorry for my bad english.
Could be a bad download. Try again. Or perhaps you can ask in the Rom thread?
I get this error every time, i tried with kernel also. I cant ask there because i'm newbie.
Oh, you need 10 posts to post there. Look around and join discussions with some constructive posts, when you have 10 you can post in the Rom thread.
Or, simply try another Rom.
Probably a bad download. But in a terminal emulator on your phone what do you get when you type:
su
getprop ro.bootloader
Sent from my Nexus 5 using XDA Free mobile app
i tried another rom, still the same
in the terminal i get a response: HHZ11k
p.s: i have the stock rom now, i guess its not a problem.
PaulTodinca said:
i tried another rom, still the same
in the terminal i get a response: HHZ11k
Click to expand...
Click to collapse
what bootloader are you using? i believe youll need the HHZ11d bootloader to flash anything over 4.4.2
PaulTodinca said:
i tried another rom, still the same
in the terminal i get a response: HHZ11k
p.s: i have the stock rom now, i guess its not a problem.
Click to expand...
Click to collapse
You have the right bootloader then. It's a bad download
Sent from my Nexus 5 using XDA Free mobile app
@jd1639 all the roms i try to install are bad downloads? :-s
@simms22 are you sure? could you give me a link or something to test it ?
PaulTodinca said:
@jd1639 all the roms i try to install are bad downloads? :-s
@simms22 are you sure? could you give me a link or something to test it ?
Click to expand...
Click to collapse
I don't know, but you have the right bootloader. You shouldn't be getting the assert error.
Sent from my Nexus 5 using XDA Free mobile app
Try philz recovery. ?
Are you sure that its the right version for the nexus?
Sent from my Nexus 5 using XDA Free mobile app
yes, i'm sure.
This is my phone, i checked on, and its corect.
Version: 4.4.4
Build: KTU84P
Bootloader: HHZ11k
Baseband: 2.0.50.1.16
PaulTodinca said:
yes, i'm sure.
This is my phone, i checked on, and its corect.
Version: 4.4.4
Build: KTU84P
Bootloader: HHZ11k
Baseband: 2.0.50.1.16
Click to expand...
Click to collapse
What version of twrp are you on. If an older version update it
Sent from my Nexus 5 using XDA Free mobile app
TWRP version: v2.8.0.1
I have to ask you, after i rooted the phone i never made any changes into the TWRP Manager. I backed / restored up trough recovery mode and
I see bunch of stuff there: Install, classic backup and i am concerned to see install TWRP, but its installed :-s . Is there a problem?
PaulTodinca said:
TWRP version: v2.8.0.1
I have to ask you, after i rooted the phone i never made any changes into the TWRP Manager. I backed / restored up trough recovery mode and
I see bunch of stuff there: Install, classic backup and i am concerned to see install TWRP, but its installed :-s . Is there a problem?
Click to expand...
Click to collapse
Shouldn't be a problem. But I'd delete twrp manager. Once you have twrp installed do everything through it, not twrp manager
Sent from my Nexus 5 using XDA Free mobile app
im still using twrp version 2.6 something, so twrp 2.8.0.1 is fine. but yea, do it through the recovery, not twrp manager.
Two things....Try philz....lol. Yes twrp should work, but try philz to see what happens.
And is your device encrypted?
Finnaly!!!! i downloaded 10 times the rom and it works... and it was a thing to mark under the install button and i deselected that.
Thank you guys! Love you all! :laugh::victory:
PaulTodinca said:
Finnaly!!!! i downloaded 10 times the rom and it works... and it was a thing to mark under the install button and i deselected that.
Thank you guys! Love you all! :laugh::victory:
Click to expand...
Click to collapse
What do you mean, a thing to mark under the install button?
Sent from my Nexus 5 using XDA Free mobile app