i just rooted my nexus s using clockwork mod herring and i installed the fix for recovery mod and the latest su.(2.3.6.3 efgh signed) i had this problem wiht the orignal su i rooted with 2.3.6.1 ef sgined i was previously running gingerbread 2.3.4 now when i try to install any ( i have tried a few) custom roms it keeps aborting saying status 7 this happens when i used rom manager and when i adb push the file to the sd card any one have a fix for this ?
Which version of CWM that you installed? Also what is your phone model?
Related
What i have: Nexus S i9023
What i had: Blandroid 2.3.7
What i did today: flashed .zip from sdcard to stock 2.3.6 found on xda
then flashed .zip from sdcard stock 4.0.3 found on xda
now my bootloader (i press vol up and power button) says unlocked but if i try to go into recovery it breaks down. superuser is insalled on my phone. but i don't have access to rom manger (says i need root).
what can i do? is my phone still rooted or not? how can i root it again? will i lose my data from my sd card?
greets!
There was a problem with su and official ics but here is what I did: I went back to official 2.3.3 downloaded from xda, phone notified me of an update, jumped straight to 4.0.3 ( update was 160 mb so it might be both 2.3.6 and 4.0.3) then I followed this
http://forum.xda-developers.com/showthread.php?t=1396913
Installed rom manager, updated my cwm then I went to su website and downloaded today's fix now my su is working and notifies me if any app needs permission.
Hope this helps
I was running nexus s 4.0.3 on my phone i downloaded the kernel to overclock my nexus s but the kernel was of nexus s gingerbread i suppose
So my phone hanged and didnt boot up ....at that time i forgot to make bacup of my current rom so i ve downloaded a older ics(not official pre realse one) i flashed with it and it started everything worket except wifi and the problem of status 7 has begun i couldnt fix it so i went to samsung guys and they installed the 2.3.3 on my phone ... and now the main problem start
My nexus s is not able to accept any kind of update say it as a system update of i9023 2.3.6 or custom rom with status 7 error . I googled it a lot they say its a problem with the signature it download a proper signed file still it doesn't help it installs but not working properly even after doing wipe cache , dalvik cache so i googled more it says make no changes in phone and return it with stock system apps i did it again same problem while system update (screen hangs with android exclamatiory sign in a triangle) i then downloaded a stock rom of 2.3.3 for nexus s i9023 while installing it with the clockworld mod recovery 5.0.2(latest as far as i know) it starts install then says status 7 error.
To overclock my phone i have installed netarchy kernel for overclocking to 1.4 ghz....is it because of my kernel changed i am not able to install andy custom rom or system ota update from google
And theres one more thing i have changed the bootloader version accidently thinking it may work to i9020xxka3 i think which is the same for i 9023 and my baseband version is i9020xxkb3.
I have tried to install many signed versions of rom for my phone including 2.3.3 ,2.3.6 and ics 4.0.3 all stock downloaded from different websites but still not able to install any rom through clockworld mod recovery and any of the system update .
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Download latest recovery from http://forum.xda-developers.com/nexus-s/development/crespo-philz-touch-t2284670
Then try to flash the ROM. It seems your recovery is very old.
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
@smit.sanghavi is right.
You need KitKat compatible Recovery. Update your recovery and then try to flash the ROM.
K guys, wanted to try all you said, but there's another problem.
I discovered my nexus isn't rooted. Bootloader unlocked, but any root checker says its unrooted (of course it was before...). So I'm trying to reroot it but when im connecting my phone via usb in bootloader windows 7 doesn't recognize the device. When the phone is connected in recovery or in normal usb debugging mode it recognizes it as adb android, looks good to me. I go back to booloader and i get "Windows has stopped this device because it has reported problems. (Code 43)" in Devices.
Installed the drivers on few different ways.
So.... what now ?
UPDATE: solved
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Sounds like you flashed the wrong recovery, possible that you installed the p3100 recovery.
Try reflashing the recovery.
miksol said:
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Click to expand...
Click to collapse
Flashing KK ROMs on outdated recovery will get you a status 7 error. Grab the latest (I'd go with TWRP as CWM support will be ending soon) version from here...http://forum.xda-developers.com/showthread.php?t=2548257 update to the latest one you like (CWM is 6.0.5.0) Load up a ROM and give it a go. I put all my ROMs on an external card to be safe. Maybe do that and then just install from such.
p,s. CM installer never works, I dont think our tabs are compatible with it. At least I've never got it to work.But, you dont need it anyways.
So last night I went about installing a new custom ROM on my HTC One S, proceeded to unlock via the official app, and completed that step.
Upon attempting to install the custom ROM (that I got from the official CM site, the ROM being CM12, made sure it's for my device), I also deleted the backup I made of the system and now I am stuck with a bricked phone.
The problem is : I have a ROM and a custom recovery, BUT whenever I try to install the ROM, I keep getting this error message
E:Error executing updater binary in zip
Error flashing zip
The phone has been flashed before to android 4.4 with HTC Sense 6, if that information helps.
As I said, the custom ROM is from the official site, stable version, and the phone is bootloader unlocked.
Solution
Solved, had to install a ROM that complied to the HBOOT version (i.e. 2.16.0)