I rooted the phone and installed the super user file, but I've been having issues installing the latest stable version. I ended up installing the latest nightly version but I think it has been affecting the mic somehow. I was just wondering if anyone could clarify why I may be having issues. I placed both the latest and the second latest zip files on my SD card, but when I run the Clockwork mod, it says for both the installation is aborted.
I'm not sure why your installs would abort but if you're running cm7 and having mic issues go to Settings - Device Settings - Sound Settings and disable hi-fi recording.
Sent from my Nexus S 4G
Thanks, that seemed to have fixed the problem. I'm still not sure why the stable version isn't working but this nightly version I have seems to be working well so maybe I'll just stick with it for now.
You should flash another ROM and check whether the issue still exists steer clear or CM7 based ROMS
What would you suggest? I'm not phone illiterate or anything, but this is my first experience rooting & installing ROMs.
HurtMeSole said:
What would you suggest? I'm not phone illiterate or anything, but this is my first experience rooting & installing ROMs.
Click to expand...
Click to collapse
Heres the link to one of my fav ROMS Oxygen http://download.oxygen.im/roms/update-oxygen-2.3.2-NS-signed.zip
Instructions:
Boot into recovery
do factory reset wipe cache/dalvik/
install the ROM
For whatever reason I'm getting the same error when I tried to install the stable CM7 ROM. I also tried using the ROM Manager as well and didn't have any luck either. Could there be a problem with my ClockWork Mod?
HurtMeSole said:
For whatever reason I'm getting the same error when I tried to install the stable CM7 ROM. I also tried using the ROM Manager as well and didn't have any luck either. Could there be a problem with my ClockWork Mod?
Click to expand...
Click to collapse
Which version are you using. Try to have the latest version.
-- Installing: /sdcard/update-oxygen-2.3.2-NS-signed.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/update-oxygen-2.3.2-NS-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-oxygen-2.3.2-NS-signed.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update-oxygen-2.3.2-NS-signed.zip")
There is the error message.
HurtMeSole said:
For whatever reason I'm getting the same error when I tried to install the stable CM7 ROM. I also tried using the ROM Manager as well and didn't have any luck either. Could there be a problem with my ClockWork Mod?
Click to expand...
Click to collapse
You can reinstall CWM within ROM-manager
Yeah I did. Still no luck.
Are you on nexus s or nexus s 4G? I am not sure if there's different recovery but yours would seem to be for nexus s I believe.
Sent from my Nexus S 4G running CM7/franco.Kernel
I have the 4G. I went to the CyanogenMod site and downloaded the latest version for the 4G but I get that exact same error message I posted earlier.
Now I can't even get it to boot into recovery. It just freezes.
HurtMeSole said:
-- Installing: /sdcard/update-oxygen-2.3.2-NS-signed.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/update-oxygen-2.3.2-NS-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-oxygen-2.3.2-NS-signed.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update-oxygen-2.3.2-NS-signed.zip")
There is the error message.
Click to expand...
Click to collapse
This is for the NEXUS S, You should install the NS4G version. You try to install a NS rom to a 4G, It wont install.
Yeah I see that now. But the CyanogenMod still wouldn't install and I'm sure I was using the 4G version for that. & now I am having an issue even getting into the Clockwork recovery.
Use fastboot to flash recovery again to your phone. Then Redownload the CM7 rom from here
http://forum.cyanogenmod.com/topic/32476-cyanogenmod-7-for-the-nexus-s-4g-v7101-11-oct-2011/
and try flashing. Check whether the MD5 sum of the ROM on the site matches with the file you downloaded.
Can you get into bootloader and then you select recovery but it doesn't load? If so you could try flashing recovery from your computer using fastboot.
Sent from my Nexus S 4G running CM7/franco.Kernel
Yeah what he said! My thoughts exactly.
Sent from my Nexus S 4G running CM7/franco.Kernel
I just kept flashing the Clockwork until it allowed me to get into the recovery mode. I installed the CM7 for the 4G and it worked but there was no Market app so no way to get my backup on to the phone.
Hello everyone,
I saw a lot of people facing errors in CWM recovery while installing ROMs, themes, etc. So I decided to make a simple, short and clean thread to post some solutions which might help you in overcoming the errors.
Status 0 Error:
This error occurs due to some error in updater-binary. Replace the updater-binary from some other same type of zip you are flashing and it will work.
Click to expand...
Click to collapse
Status 1 Error:
Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you dont have correct permissions set. Use correct perms in updater-script and done
Click to expand...
Click to collapse
Status 6 Error:
The status 6 error mostly occurs when we edit an updater-script in windows text editor. This is because the windows text editor at the end of the updater-script creates a windows styled end of line which causes the error. The easiest solution is to write the updater-script in such a way that this error doesn't occurs. Try notepad++, change the end of line to unix style, unix style eol and this error won't occur
Click to expand...
Click to collapse
Status 7 Error:
The most common error that most of the people face is this one.
Following are the reasons for it:
1. Something wrong in updater-script.
2. Corrupt zip.
3. Zip not made for device or couldn't recognize the device.
To overcome the first error, the only solution is to manually edit the updater-script and search for error or post your updater-script to some forum or thread or make new thread specifying your complete error.
To overcome the second error, the only solution is to re-download the whole zip.
To overcome the third error, just delete the first three lines from your updater-script stating something related to your device. Here's the lines related to my device, i.e., Sony Ericsson Xperia Mini Pro, SK17i/a :
Code:
assert(getprop("ro.product.device") == "SK17i" || getprop("ro.build.product") == "SK17i" ||
getprop("ro.product.device") == "SK17a" || getprop("ro.build.product") == "SK17a" ||
getprop("ro.product.device") == "mango" || getprop("ro.build.product") == "mango");
Similar kind would be for your device too. And if not then the zip is simply not meant for your device.
Click to expand...
Click to collapse
Great thread,
Btw in status 6, we have to select eol as unix in npp, not just use it right
Added about status 1 error also
Cheers,
AJ
When there's 0,1 and then 6 and 7. Logic tells that there is 2-5, anybody ever heard of it?
Regards
N
Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.
DarthRecca said:
Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.
Click to expand...
Click to collapse
Make sure you zipped all the folders with meta-inf and not zipped the parent fodder
Cheers,
AJ
To whom got status 1 error
I had this problem(cwm status 1 error) while flashing my xxxxxx.zip ,so i got a twrp ,in its advanced options ,got to the file manager ,head to the / directory (all of the thing where there) ,tapped on select button,and chmod 755. Then with cwm i could flash my zip.
don't mount my ext sd card
I'm install cwm recovery in galaxy s dous 2 s7582 but cwm cannot mount my SD card for selecting any update from storage.................
Hi there,
I'm just trying to install TWRP and Cyanogenmod 12.1 (cm-12.1-20151230-NIGHTLY-taoshan / open_gapps-arm-5.1-nano-20151225), and having some problems.
Sorry for the long mail, at the end I have put a short summary of the current status of my Xperia L (C3105).
I succeeded to unlock the bootloader, afterwards I installed the stock rom (C2105_15.3.A.1.17_1272-2171 R2B_Generic DE). So far, so good.
However, all attempts to install TWRP and/or Cyanogenmod have failed so far.
At first I tried to install TWRP (latest version) via the app method (TWRP manager app form Google app store). The app reported a successful flash, but somehow I could not get to recovery when I rebooted while rocking the vol up/down buttons. Also the notification light does not any more turn purple when booting up.
Afterwards I flashed the above stock rom again because it was not clear for me whether the phone was stucked in a boot loop. I guess that this also re-installed the stock recovery again? Anyhow, since then and up to now even when I reboot and constantly press the volume buttons (both) while the phone is booting up, it still boots into android and not into the recovery.
So I guess that the recovery is not correctly installed at the moment.
I tried also with the XDA recovery-installer-taoshan-1.3.apk to install another version of TWRP (an older one), but this did not work as well, with a very similar behaviour, but afterwards I was not either to boot anything, neither the recovery nor the android system, but was possible to boot into fastboot mode so that I could re-flash the stock rom.
Now, even when I neglect the recovery and try to install cynogenmod with the command "adb sideload update.zip" (obviously with exact file name instead of update.zip), it always says the following:
ADB server didn't ACK
* failed to start daemon *
adb server is out of date. killing...
*daemon started successfully *
error: closed
I have to say that after flashing the stock rom and connecting the phone to the computer, I denied to re-install the PC companion software, because from my perspective all drivers etc should be installed. But I do not want to exclude that this could also be an issue here.
I just tried to install the universal ADB drivers, seleted repair drivers, but still the ADB connection seems to not work properly.
My device manager reports for the driver "Sony so0103 ADB Interface Driver".
Just to summarize:
- I have rooted the phone successfully (also re-rooted after flashing the stock rom)
- the bootloader is unlocked (confirmed via service menu)
- recovery does not work
- above mentioned stock rom is installed
- stock rom is booting fine
Does anyone have a suggestion of how to solve the problems and what the next steps should be? I would also very much appreciate any hint on what I have possibly done wrong in order to learn from it.
Many thanks in advance and my best regards,
Henning
Just a note:
If I remember well, I'm not sure if the ADB drivers were successfully installed. The last time when I used ADB successfully, it was with linux, and this time I tried with windows, because the flashtool seems to work only with windows (or I just do not know how to operate it in linux on the shell).
Should I just try to re-install TWRP with the app method, and without rebooting flash cyanogenmod using the "adb sideload update.zip" command? Or is there any other command which would be preferred?
I have also busybox and a terminal emulator installed, could also direclty flash it from the phone ...
Thanks in advance!
Cheers,
Henning
While using the app, when it reboots, open the app again and click TWRP again.. it'll work.. or it may be an incomplete download. delete twrp.tar from the internal SD and try again
Hi,
I hope someone could help me quickly:
I again installed TWRP 2.8.7.0 via the TWRP manager app method.
Afterwards I flashed with Flashtool the extracted boot.img from the CM-12.1 zip file.
This time I finally could boot into the recovery!
But now my problem is that the CM zip file will not be installed by TWRP.
Before the install, I wiped cache, dalvik cache, system, data (made a backup also).
Any suggestions? Is my TWRP 2.8.7.0 buggy, or the CM zip file, or is there anything I could have missed?
Many thanks in advance and sorry to bother you again!
Cheers,
Henning
Here is the log that I get from TWRP:
Installing '/sdcard/.....'
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E:Error executing updater binary in zip '/sdcard......'
Error flashing zip '/sdcard/......'
Updating partition details...
...done
xleng said:
Here is the log that I get from TWRP:
Installing '/sdcard/.....'
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E:Error executing updater binary in zip '/sdcard......'
Error flashing zip '/sdcard/......'
Updating partition details...
...done
Click to expand...
Click to collapse
obviously twrp manager app is ****ty
either use corphishs app to get my twrp versions or do the following:
1. in twrp go to
advanced->terminal command->ok
there enter :
setprop ro.build.product taoshan
setprop ro.product.name taoshan
2. flash the rom you want
3. get the app and a better twrp ;-P
Sent from my Xperia T using XDA Free mobile app
Many thanks for the quick reply!
I will try in a minute and report the results.
One question, I think that I may have already wiped system before I took the backup in TWRP.
In case I would reboot or switch off now (e.g. in order to put the SDCARD into the computer and put another version of TWRP and/or CM on it), would I be able to boot into the recovery again or would I hard-brick the device then?
I just tried to modify the update file on the computer and re-load it via sideload, but for some reason sideload could not be activated ... I will try now with your suggestion
Thanks in advance!
Still the same error .... (
I also tried to set other variables, like:
setprop ro.product.model taoshan
setprop ro.product.brand taoshan
setprop ro.product.name taoshan
setprop ro.product.device taoshan
setprop ro.product.board taoshan
setprop ro.product.manufacturer taoshan
Does not work ... it seems that the device recognized is still empty / ""
It's really weird. when I execute the shell command "getprop ro.product.name" I get "taoshan", but the updater-script does not recognize this for any reason. Probably it's the TWRP which is faulty as you indicated.
Now i just rebooted the device and connect via flashboot in order to flash the stock FTF again via flashtool.
Now I'm on stock rom again and lucky that the device is not broken (though we still have another xperia L around here from my wife, before she got a windows phone ) - hope that sooner or later I could use one of them as a debugging / experimental device though
Well, it's late for today, I will resume most likely tomorrow evening and would like to thank you once more for your very valuable hints!
Tomorrow i will try to install your version of TWRP - it is this one, correct? :
http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915
I guess this is the TWRP that you've installed as well on your device?
By the way, while I'm getting used to the process of flashing stock roms, rooting, installer recoveries etc, do you have any recommendations on certain custom ROM / GAPPS combination?
May I ask what you're using at the moment?
Just thinking about whether I will continue with CM or might switch to RR or something else ...
Cheers,
Henning
I'm just thinking if the updater-script itself has a bug:
In the first line I have:
Code:
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "C2105" || getprop("ro.product.device") == "C2104" || getprop("ro.build.product") == "C2104" || getprop("ro.product.device") == "c2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "" || getprop("ro.build.product") == "" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "taoshan" || abort("This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is " + getprop("ro.product.device") + "."););
I'm just wondering if the problem is because the abort() command is part of the assert() function, but I#m not sure about the syntax.
Cheers,
Henning
xleng said:
I'm just thinking if the updater-script itself has a bug:
In the first line I have:
Code:
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "C2105" || getprop("ro.product.device") == "C2104" || getprop("ro.build.product") == "C2104" || getprop("ro.product.device") == "c2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "" || getprop("ro.build.product") == "" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "taoshan" || abort("This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is " + getprop("ro.product.device") + "."););
I'm just wondering if the problem is because the abort() command is part of the assert() function, but I#m not sure about the syntax.
Cheers,
Henning
Click to expand...
Click to collapse
no thats all ok...
i dont know why the terminal command didnt work for you... you must have done it wrong!
yes the twrp is the one from me... and no i dont use it because i have no longer XL since my is broken...
Sent from my Xperia T using XDA Free mobile app
Hi,
I have downloaded and installed your app, as well as the latest CM-12.1 version (2016-01-19) with the corresponding GAPPS nano package.
I applied the following procedure:
1) flashed TWRP
2) rebooted to fastboot mode, extracted and flashed the boot.img from the CM-package
3) rebooted to recovery, then I recognized that probably the boot.img has overwritten the TWRP recovery, since it was the CM recovery that started
4) tried to flash CM-12.1, which failed after the verification, with the message that it can't be installed on top of incompatible data; what I've noticed was that the CM recovery did not allow me to wipe the system, don't know if that could have caused the problem.
Trying further ....
Cheers,
Henning
Hi,
I repeated the same steps just without flashing the boot.img file, when rebooting to recovery TWRP was there, and was able to flash the latest CM-12.1 which is currently booting!
Many thanks to all contributors of this ROM and to SdtBarbarossa for advice!!!
Cheers,
Henning
PS: Probably I will comment on something later ...
I installed both CM and GAPPS directly after each other, e.g. without an intermediate boot into android.
Now I have messages telling me that the google apps have been closed after each start-up.
I think I probably need to re-flash CM, then reboot, and then flash GAPPS again, right?
Even the google app store was not working, and I could also not install the TWRP with the apk file because it didn't recognize the device.
Installing stock rom again for tonight, tomorrow I will flash CM again ...
Even if the app doesn't recognize your device, flash it.. It works 100% .. and after flashing gapps you should try factory resetting .. It might work..
Good point with the favtory Reset! Thanks!
Hi,
CM-12.1 works now very well (I noticed the flashlight bug which I believe has been reported several times already, but that's not really troubling me) ...
Overall, it's really an awesome ROM! Very fast and responsive (much much faster UI feeling than with the initial SONY stock ROM), and really great to see a recent android version running that smoothly on this little device!
Many thanks again to all contributors of this ROM! Really a great piece of work!
Cheers
Henning
xleng said:
Hi,
I have downloaded and installed your app, as well as the latest CM-12.1 version (2016-01-19) with the corresponding GAPPS nano package.
I applied the following procedure:
1) flashed TWRP
2) rebooted to fastboot mode, extracted and flashed the boot.img from the CM-package
3) rebooted to recovery, then I recognized that probably the boot.img has overwritten the TWRP recovery, since it was the CM recovery that started
4) tried to flash CM-12.1, which failed after the verification, with the message that it can't be installed on top of incompatible data; what I've noticed was that the CM recovery did not allow me to wipe the system, don't know if that could have caused the problem.
Trying further ....
Cheers,
Henning
Click to expand...
Click to collapse
I'm facing the same issue not able to flash.
Can you give step by step instructions?
Hi, what is your device status at the moment? What did you do so far?