Related
[Q] Flash any ROM = "android.process.acore has stopped" missing recovery/update.zip?
Former evo (power) user, running (almost) all the nightlies and then RC of CM6. (usb power port broke. Chose Epic rather than waiting a month for the (out of stock) evo. So far, I like the hardware much better on Epic).
I Rooted/Clockworked via the linux thread in the forums. (http://forum.xda-developers.com/showthread.php?t=792058)
SuperUser info: Superuser v2.3.6.1 - Added clear log to menu in log
Database version 5
Su binary v original (sometimes shows Su binary v%s)
ROM manager info:
Current Recovery: CWM 2.5.1.0
No Alternate Recovery available
Reboot into Recovery takes me to (blue) Samsung recovery page (exclamation point in triangle)
E:Failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
(click home button -- reboots phone).
Using QuickBoot, Recovery sends me to the Samsung blue screen (not clockwork) and BootLoader just reboots back to phone).
However, Power off. Camera + Vol Down + Power takes me to clockwork.
Successfully made (and restored) backup.
Yesterday I flashed Tha Boss. About a minute in, I get the following error: "android.process.acore has stopped unexpectedly. Please try again. - Force close".
Successfully restored to my backup (of stock)
This morning I flashed Bubby's Magic AOSP. Same deal. About a minute in, I get the following error: "android.process.acore has stopped unexpectedly. Please try again. - Force close".
Again, successfully restored to my backup (of stock).
I've "replaced" blur on my stock with widget locker, ADW and beautiful widgets, but am having terrible battery issues. I do not care for any of the samsung/sprint stuff.
Obviously I am missing something here. Am I missing some recovery file? update.zip?
Thanks for any help/suggestions.
Drew
I was encountering issues like this as well. I went back to the start and did it all from scratch.
Used odin to get back to stock no root no custom recovery.
Once stock I let the phone prompt me for the di07 update ( probably not necessary as there is now a .tar with the di07 update so u can use that in odin)
I installed root using the one click busybox 2.2.4
Then I used the clockworkmod 2.5.1.0 flasher in the Permanent Method! Thread
I then installed the premium rom manager and when I did a backup from it I noticed something different ... it went through some stuff that said "replacing stock recovery with custom" or something to that extent. In the past doing that from rom manager would just take me to the stock rec. Now I can even boot into custom rec from rom manager and since then I've had no fcs of that sort when installing backups or new roms.
Sent from my SPH-D700 using XDA App
From my understanding of this error, so far at least, it has something to do with contact sync. I'm working on developing a ROM right now and I'm experiencing the same issue.
If anyone has any insight into this "acore" error message, I'd like to know what I might be able to do to fix this for myself as well.
rmartinez2 said:
I was encountering issues like this as well. I went back to the start and did it all from scratch.
Used odin to get back to stock no root no custom recovery.
Once stock I let the phone prompt me for the di07 update ( probably not necessary as there is now a .tar with the di07 update so u can use that in odin)
I installed root using the one click busybox 2.2.4
Then I used the clockworkmod 2.5.1.0 flasher in the Permanent Method! Thread
I then installed the premium rom manager and when I did a backup from it I noticed something different ... it went through some stuff that said "replacing stock recovery with custom" or something to that extent. In the past doing that from rom manager would just take me to the stock rec. Now I can even boot into custom rec from rom manager and since then I've had no fcs of that sort when installing backups or new roms.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
So, should I use Whosdaman's DIO7 tar (http://forum.xda-developers.com/showthread.php?t=794138) instead of the DG27?
Also, does that pit file (Aridon's 'How to return to stock' (http://forum.xda-developers.com/showthread.php?t=773032) work with DIO7?
Thanks for this info, btw
I need that DIO7 file but Megaupload isn't working, would one of you be nice enough to upload it to Mediafire for me?
if your running adw launcher, go into adwsettings > system preferences and make sure that you have wallpaper hack unchecked, this was causing the acore force close issue on my phone
for your clockwork issue, make sure your running a kernel that supports it and also after flashing clockwork recovery (the final version) an update.zip file should have gotten installed on your sd card, dont remove it has it is needed.
the only way to reboot into clockwork recovery is to do it through rom manager, every other way will send you back to the stock recovery.
hope that helps
aim1126 said:
if your running adw launcher, go into adwsettings > system preferences and make sure that you have wallpaper hack unchecked, this was causing the acore force close issue on my phone
for your clockwork issue, make sure your running a kernel that supports it and also after flashing clockwork recovery (the final version) an update.zip file should have gotten installed on your sd card, dont remove it has it is needed.
the only way to reboot into clockwork recovery is to do it through rom manager, every other way will send you back to the stock recovery.
hope that helps
Click to expand...
Click to collapse
Odin'd back to stock. Rerooted using 1-click. Rom Manager (paid version) still takes me to that blue samsung.
Don't seem to have update.zip from root, tho i *do* have root.
Still getting the
E:Failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
message, including the update.zip file not found...
****Goes away for 30 mins****
Ok. I re-re-odined. Then tried noobini's permanent method (http://forum.xda-developers.com/showthread.php?t=782300)
Try-first would not run. Try-last did not give me su permissions.
What am I missing here?
Maybe I should just re-root the 1-click? If I do, where can I pick up the update.zip and flash it manually?
Thanks,
Drew
SwimDrewid said:
Odin'd back to stock. Rerooted using 1-click. Rom Manager (paid version) still takes me to that blue samsung.
Don't seem to have update.zip from root, tho i *do* have root.
Still getting the
E:Failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
message, including the update.zip file not found...
****Goes away for 30 mins****
Ok. I re-re-odined. Then tried noobini's permanent method (http://forum.xda-developers.com/showthread.php?t=782300)
Try-first would not run. Try-last did not give me su permissions.
What am I missing here?
Maybe I should just re-root the 1-click? If I do, where can I pick up the update.zip and flash it manually?
Thanks,
Drew
Click to expand...
Click to collapse
Ran the Noobini permanent method over the linux 1-click -- still unsure what I'm missing in way of CWM.
No update.zip on sd card (not in any's the one-click zips i've seen either.
Still can't get to recovery via Rom Manager -- only via Vol Down + Camera + Power,
So, to reiterate, I'm rooted, ROM Manager shows 2.5.0.2, but Flash Alternate Recovery is unavailable.
Back Up Current Rom takes me to the blue samsung recovery (not cwm recovery) with following messages/errors:
--Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Hit the home screen to fastboot back to phone.
Power off
Vol Down + Camera + Power,
make a back up that way
So. Anybody want to lend me their update.zip??
Thx,
Drew.
Looks like I *do* have update.zip on sd card. I copied to my desktop and was able to extract it (meaning the compression didnt get corrupted).
It has all the nandroid files in /sbin.
Just thought of something. This is the same sd card i had in the evo -- has a bunch'a stuff on it (including old cwm backups)
Maybe tomorrow I'll (backup then) format card, odin, reroot?
Have you tried wiping cache and data on each ROM Install? Sometimes crap is left over and you end up with old application data/caches that interfere with the way they interact. Backup what you need, then wipe data/cache. Then install Zip from sdcard, after it finishes, wipe data/cache once more and reboot into Android.
Hope this fixes your issues.
schizopunk said:
I need that DIO7 file but Megaupload isn't working, would one of you be nice enough to upload it to Mediafire for me?
Click to expand...
Click to collapse
It's been uploaded 2 other mirrors now. Check the thread again.
http://forum.xda-developers.com/showthread.php?t=794138
Yeah. Always. Didn't have the clockwork kernel. Do now and everything is clockworked willy.
Thanks to all you xda people!
Sent from my (rooted) SPH-D700 using XDA App
Just an fyi on this acore issue. I was having the same problem after flashing tha boss. went back to andromeda and same thing. Aosp and same thing. Flashed the Andromeda kernel and the problem was solved. During it all clockwork was still working so I'm thinking that aim1126 was right earlier when he said that the kernel must support clockwork.
I sell and activate these phones and i had the acore force close on freshly activated epic the other day
One thing I found is that if you remove the TouchWiz launcher from any ROM then you will get this.
schizopunk said:
One thing I found is that if you remove the TouchWiz launcher from any ROM then you will get this.
Click to expand...
Click to collapse
I just installed LauncherPro on Apophis, removed the TouchWiz launcher and deleted it's folder in /data/data/. It's only been about a minute, but I haven't seen any errors yet. Is there any specific way to trigger it?
schizopunk said:
One thing I found is that if you remove the TouchWiz launcher from any ROM then you will get this.
Click to expand...
Click to collapse
Same thing happened to me every time I deleted TW but then I didn't delete its folder from /data/data so I don't know?
Sent from my SPH-D700 using XDA App
illogic6 said:
I just installed LauncherPro on Apophis, removed the TouchWiz launcher and deleted it's folder in /data/data/. It's only been about a minute, but I haven't seen any errors yet. Is there any specific way to trigger it?
Click to expand...
Click to collapse
Try syncing your contacts with TouchWiz's facebook feature... it most likely won't sync.
smoothone said:
Same thing happened to me every time I deleted TW but then I didn't delete its folder from /data/data so I don't know?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I just delete that folder because I'm OCD about unneeded files.
Here's how I setup my phone.
1) Odin to DI18
2) Flash clockwork recovery with this method: http://forum.xda-developers.com/showthread.php?t=782300 (Don't worry about rooting. This runs an exploit that gives you temp root and flashes clockwork.)
3) Power off, reboot into clockwork recovery
4) Wipe data
5) Flash ROM (Try my ROM if all else fails. I haven't seen one acore force close.)
6) Flash kernel if needed
That method SHOULD eliminate any possible variation between installs. I'm running the most recent version of Apophis, Phoenix kernel, no TouchWiz, still no errors. If you follow this method and get acore force closes, I will be baffled.
schizopunk said:
Try syncing your contacts with TouchWiz's facebook feature... it most likely won't sync.
Click to expand...
Click to collapse
Ah, that might be it. I don't use facebook.
EDIT: I just created a dummy account, opened the contacts app and signed in. It synced without force close. Might be due to a lack of friends. Any other ideas?
Hi
I have recently had my HTC Wildfire rooted after the fantastic AlpharevX contribution.
I've played around with different ROMs, and since I experienced problems with GPS in CM 7.1 RC1, I decided to go for a Radio update.
I have CWM recovery 3.2.0.0, which according to this general Wildfire thread is not compatible with flashing the current radio versions.
I therefore downloaded the Radio zip-file, copied it to my SD root dir and started ROM Manager and selected update ROM from SD card.
I checked "Backup current ROM" and "Wipe Dalvik cache" and pressed OK to the different dialog boxes.
It then rebooted to a black screen with the little green Android and a warning sign with an exclamation mark in it.
It has just stayed there for more than 10 minutes now.
I read somewhere that flashing radio can be riscy, and also that one must have patience and not interrupt anything. Therefore I haven't dared touching it without seeking advice...
What should I do? Am I supposed to press anything to continue, or should I try to turn it off (either using power button or by battery removal)?
Kind regards, Martin
UPDATE: I lost patience and decided to click on the different buttons. By clicking the power button, it displayed that I had entered CWM Recovery 3.2.0.0 and the log states:
Finding update package...
Opening update package...
Verifying update package...
E: failed to seek in /cache/update.zip (Invalid argument)
E: signature verification failed
Installation aborted.
I have just rebooted for now... Is it somehow possible to have two different CWM Recovery versions installed, such that I can boot directly into 3.2.0.0 and maybe enter 2.5.x.x. from ROM Manager?
you must flash clockworkmod recovery in rom manager then click run in recovery mode (second option) in rom manager then phone will reboot and got temporary CWM 2.5.0.7 and you can flash radio in this version
ziemjak said:
you must flash clockworkmod recovery in rom manager then click run in recovery mode (second option) in rom manager then phone will reboot and got temporary CWM 2.5.0.7 and you can flash radio in this version
Click to expand...
Click to collapse
Thanks a lot...
I just updated the radio.
Now I also now how to flash Froyo custom ROMS. CWM 3.2 only allowed me to flash Gingerbread ROMs.
moderator pls close thread problem solved
Hi since we are at it, I also have a question about radios...
My Bluetooth used to work just fine on my htc stock ROM before switching to CM 7.0.3, I could both send and receive files from my mac.... well the thing is I can only receive them now, I can't get my wildfire to send anything to my mac! (already tried the app from the market, I think it's called Bluetooth File Transfer)
Anyway do you think a radio upgrade or in my case downgrade could fix this? I currently have 13.55.55.24H_3.35.20.10.
Heeelp....
Hi, i root my wildfire with sucess but i can´t instal any rom, and i tried to fix permissions with "root tool.apk". Restart the phone and its freeze on logo in a white background.
I already try recovery, wipe factory and nothing......any ideas please.
Sorry for inglish
When you do a Wipe in Clockworkmod, it is different from a factory reset, and obviously, you will have to flash a ROM after it. Trying to reboot your phone after Wipe Data will result in a frozen start logo.
After you do a wipe, select Install Zip from SDCard, and select the ROM's ZIP file, which you want to install.
NOTE: If you have Clockworkmod 3.x, you can only install Gingerbread ROMs, and, if you have Clockwork 2.x, you can only install Sense / Froyo ROMs
3xeno said:
When you do a Wipe in Clockworkmod, it is different from a factory reset, and obviously, you will have to flash a ROM after it. Trying to reboot your phone after Wipe Data will result in a frozen start logo.
After you do a wipe, select Install Zip from SDCard, and select the ROM's ZIP file, which you want to install.
NOTE: If you have Clockworkmod 3.x, you can only install Gingerbread ROMs, and, if you have Clockwork 2.x, you can only install Sense / Froyo ROMs
Click to expand...
Click to collapse
I trie like you say but no sucess. Give a error message;
"E:failed to verify whole-file signature"
"E:signature verification failed"
I had install "root tool.apk" to try fix permissions because of clockworkmod was not properly installed. gave errors
Problem solve
Problem solve, just run 0001_WildPuzzleROM_v0.2
hi
motoroladefy plus MB526 from australian
i copy many of files to SD (downloaded till i finsh my monthly limit) change the name to update.zin files
same msg
now my phone cant start system freezing @ motorola logo
when i chioce power and down button then down + up open a windows wrote this :
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
copy may ROMs to SD and i choiced 2.apply update from sd
show me after check this msg:
E: signature veification failed
install aborted
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote: Error validating image file ..when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
how can i solve this please
can i get australian service center for motoroladefy plus email ?
thank you
Questions go in the Q&A section
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
need help
MarcinRN said:
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
Click to expand...
Click to collapse
in first thank you
yes installed 2ndinit and super1c,rom manger = cwm and <3e rerovery>..(byaway still <3e> see it when i prss down volum:
Android system recovery <3e> isnt mean its not stack recovery?
in first the recovery boot work with all option ( backup,recovery,back,...) i think it mean root succeed _saw blue LED
but cant install ROM ...E:signature verification failed Installation aborted)-nothing accept to install same error ..thats mean NO i cant install any ROM
restarted and wiped data,cache, again and again + (system formt) after restart cant see all option @ recovery mode only that 4 option:
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
this time i have use both -,+ volum to enter recoverymode!
i dont remember i choice unroot under recoverymode!
about LED now only white when i off the phone and connect cable but not charging only white LED
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
dlshad said:
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
Click to expand...
Click to collapse
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
MarcinRN said:
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
Click to expand...
Click to collapse
thank you
im sure im in bootloader the white fonts black backgraound
usb conected andthe RSD see the phone
the secount of your note
i install may of files from here:
http://sbf.droid-developers.org/umts_jordanplus/list.php
all of that same error
sure i remove last 2 word (.gz)
in past i upgrate to 2.3.6 seccesed from official site
when i bought it they said its unlocked maybe not factory unlocked is that help!
in recovery mode there is <32> isnt mean its rooted not stock recovery
can i add backup option to recovery mode coz i have backup file
any help
thank you
dlshad said:
sure i remove last 2 word (.gz)
Click to expand...
Click to collapse
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Downloaded sbf file but unable to unpack
MarcinRN said:
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Click to expand...
Click to collapse
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
rahulpillai said:
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
Click to expand...
Click to collapse
what error does it actually give? which program are you unpacking archive with?
E:signature verification failed. Installation aborted; after rooting spice mi 500
Just yesterday I rooted my spice mi 500. Was fine untill i paid and downloaded a bunch of pro apps like ROM Manager Pro, and ran some scripts, thinking it might be routine clean up. but after running some script...I am only getting the followin message. I can see my spice phone in device manager on my PC, and drivers are up to date. I am unable to use the USB properly as the PC is not recognizing my device...Pls help asap. thanks.
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
Plese Help... !!!
:crying:
I m having MMX A25 .
i have installed CWM 5.x.x.x.version
whenever i tried to install custom Rom in it .
It just shows me an error SIGNATURE VERIFICATION FAILED
i am totally stuck,.. !! plese somebody help me out to install custom rom.
Help would b appriciated. :good:
I have same problem with galaxy s gt i9000 Froyo with recovery 3e.
I read that this recovery doesn't allow installation of files not signed.
Tried many but no luck I'm rooted but cannot install even a custom recovery.
Did you find the solution please.
Thanks
Sent from my GT-I9000 using Tapatalk 2
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
http://forum.xda-developers.com/showpost.php?p=34616788&postcount=1
--> FAQ2
It should work for both. Same as latest builds of CM10.
thubi said:
http://forum.xda-developers.com/showpost.php?p=34616788&postcount=1
--> FAQ2
It should work for both. Same as latest builds of CM10.
Click to expand...
Click to collapse
Sorry I was meaning the 4.1.2 so it should be the 10.0
Cid156 said:
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
Click to expand...
Click to collapse
2ndboot builds: they are one build for both mb525 &5 26 .... so you can download the 26.03 nightly build and update on your MB525 :good:
Cid156 said:
Hello,
I own a defy mb525 with CM7.2.0. I am not so happy with this version (bad 3g access; battery life very short)
So I decided to install the CM10.1.
On the develloper page I saw that the status has been updated on the 26.03. But if I look for my model (mb525), I can find only a version dated on the 120904.
Is there a newer version for the mb525 or is it only for the mb520 and mb526 ?
Regards
Click to expand...
Click to collapse
Yes, there is CM10 from Quarx. Your device can be either mb525 or mb526 with red lens or green lens. CM10.1 from the same person also can.
hi
I have a similar question I have MotoDefy 525 running 2.3.7 I want to install ([ROM][JB+][4.3.1] MokeeOS 43.1 Defy/Defy(+) Official) http://forum.xda-developers.com/showthread.php?t=2453395
but it needs TWRP I tried installing on my 2.3.7 but it dosent install I looked around the forms I read that I have to up date my android version.
being a newbi im a little worried about bricking
A little help
can some one give the steps in Newbi language on how to update my phone to MokeeOS 43.1 please.:fingers-crossed:
Super_Moto said:
hi
I have a similar question I have MotoDefy 525 running 2.3.7 I want to install ([ROM][JB+][4.3.1] MokeeOS 43.1 Defy/Defy(+) Official) http://forum.xda-developers.com/showthread.php?t=2453395
but it needs TWRP I tried installing on my 2.3.7 but it dosent install I looked around the forms I read that I have to up date my android version.
being a newbi im a little worried about bricking
A little help
can some one give the steps in Newbi language on how to update my phone to MokeeOS 43.1 please.:fingers-crossed:
Click to expand...
Click to collapse
First of all, none of you guys ever read the stickies. It is packed with good info.
Our phone has a locked bootloader, it is almost impossible to brick.
Download latest CM10 and then install.
Ive come across a newbi problem im on the link of the latest cm10 (http://forum.xda-developers.com/showthread.php?t=1768702) and the file I try to flash wont install it gets aborted, I searched the forms for other cm10 and same issue file gets aborted.
If possible to be directed to the file I need to flash to cm10
not easy being newbi these days :crying:
Motorola 525 green lens running 2.3.7
What error do you get?
Sent from my MB526 using Tapatalk
hotdog125 said:
What error do you get?
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
the error shows when I try to flash the .zip file _Install zip from sdcard_choose zip from sdcard I pic the file and it doesn't install it says aborted show me the yellow triangle symbol I was assuming im flashing the wrong file.
before I do an install I wipe data/factory reset and wipe cache partition
Super_Moto said:
the error shows when I try to flash the .zip file _Install zip from sdcard_choose zip from sdcard I pic the file and it doesn't install it says aborted show me the yellow triangle symbol I was assuming im flashing the wrong file.
before I do an install I wipe data/factory reset and wipe cache partition
Click to expand...
Click to collapse
You are trying to flash through stock recovery. Install through custom recovery.
hotdog125 said:
You are trying to flash through stock recovery. Install through custom recovery.
Click to expand...
Click to collapse
I tried that and im also giving me (installation aborted) I used file cm-10-20130918-NIGHTLY-mb526 but no luck
Super_Moto said:
I tried that and im also giving me (installation aborted) I used file cm-10-20130918-NIGHTLY-mb526 but no luck
Click to expand...
Click to collapse
The file is ok, i've installed it on my defy
MikBre said:
The file is ok, i've installed it on my defy
Click to expand...
Click to collapse
Im clue less what im doing wrong I looked on u tube on installing jelly bean im following the same steps but Im getting (file aborted) when I try flashing the file
what r the steps u take on installing the file ?
At first I tried: Reboot in _Recovery _Install zip from sdcard_choose zip from sdcard_pick the the file _yes install
it starts by saying
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
2nd I tried
Reboot in Bootmenu
Recovery _ Custom Recovery etc ..etc ..
and get the same message
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
always did the factory rest and wiping during both process
Super_Moto said:
Finding update package...
Opening update package...
E:Can't open /sdcard/cm-10-20130918-NIGHTLY-mb526.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
just to be sure, your phone is not connected to a computer when you did the flash, right?
jh20 said:
just to be sure, your phone is not connected to a computer when you did the flash, right?
Click to expand...
Click to collapse
yes phone is disconnected from computer,I had no issues installing cm7
My is CMRecovery v5.0.3.2-jordan
and Bootmenu <v1.1.1> could these be the problem some thing needs to be updated ?
Super_Moto said:
what r the steps u take on installing the file ?
Click to expand...
Click to collapse
If you want a video guide look at the Youtube channel of locslikes.
Therre is a guide call "MOTOROLA DEFY How To Install ClockWorkMod and Cyanogenmod 10 Jelly Bean Android"
MikBre said:
If you want a video guide look at the Youtube channel of locslikes.
Therre is a guide call "MOTOROLA DEFY How To Install ClockWorkMod and Cyanogenmod 10 Jelly Bean Android"
Click to expand...
Click to collapse
Im just guessing.... that my bootmenu seems to be out of date possible being the reason that jellybean wont install,
bootmenu is up to 2ndInit Recovery v2.3 can this file be installed over v1.1.1 ?
Super_Moto said:
Im just guessing.... that my bootmenu seems to be out of date possible being the reason that jellybean wont install,
bootmenu is up to 2ndInit Recovery v2.3 can this file be installed over v1.1.1 ?
Click to expand...
Click to collapse
out of curiousity, i restored my mb525 back to cm7 nightly 20111201 nandroid, which has cwm v5.0.3.2. i did not check the bootmenu version but it should be the same as yours. then, after formatting system/cache partitions, i flashed cm-10-20130918-nightly-mb526.zip, and it worked.
so i don't really know what's wrong with your phone, but i have a couple of suggestions for you to try. not that there's any logical explanations but try it anyway:
1. according to the error messages, you have the cm10 rom in the root folder of the sdcard. try creating a sub-folder called cm10 and copy the cm10 rom and the minimal gapps into it.
2. download the defy_fullwipe_ext4.zip and defy_fullwipe_ext3.zip ( for later use, when you want to revert back your rom) from here and put them in cm10 folder as well:
http://forum.xda-developers.com/showthread.php?t=1818520
3. reboot into recovery but don't do any format or wipe. instead flash the file defy_fullwipe_ext4.zip and this will format your partitions into the ext4 file system.
4. then flash the cm10 rom. if it installs sucessfully, then without any further wiping,nor flashing the minimal gapps, reboot the phone. (note that the os will reboot once more in the middle of booting up, seemingly having a bootloop problem. don't worry it's meant to do that, unless it rebooted more than once)
5. if it boots up sucessfully, do some basic set up first before rebooting back into recovery to flash the minimal gapps.
alternatively you could try flashing cm9.1 (ext3) to get a newer bootmenu and cwm versions before flashing cm10. no need to flash any gapps, just wipe system/cache partitions and flash the cm9.1 rom by itself. reboot into cm9.1, do basic set up. once it's ready reboot into recovery and do the above steps, starting from step 3, to flash cm10.
good luck.....
edit: did you get your cm10 rom from here:
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/
jh20 said:
out of curiousity, i restored my mb525 back to cm7 nightly 20111201 nandroid, which has cwm v5.0.3.2. i did not check the bootmenu version but it should be the same as yours. then, after formatting system/cache partitions, i flashed cm-10-20130918-nightly-mb526.zip, and it worked.
so i don't really know what's wrong with your phone, but i have a couple of suggestions for you to try. not that there's any logical explanations but try it anyway:
1. according to the error messages, you have the cm10 rom in the root folder of the sdcard. try creating a sub-folder called cm10 and copy the cm10 rom and the minimal gapps into it.
2. download the defy_fullwipe_ext4.zip and defy_fullwipe_ext3.zip ( for later use, when you want to revert back your rom) from here and put them in cm10 folder as well:
http://forum.xda-developers.com/showthread.php?t=1818520
3. reboot into recovery but don't do any format or wipe. instead flash the file defy_fullwipe_ext4.zip and this will format your partitions into the ext4 file system.
4. then flash the cm10 rom. if it installs sucessfully, then without any further wiping,nor flashing the minimal gapps, reboot the phone. (note that the os will reboot once more in the middle of booting up, seemingly having a bootloop problem. don't worry it's meant to do that, unless it rebooted more than once)
5. if it boots up sucessfully, do some basic set up first before rebooting back into recovery to flash the minimal gapps.
alternatively you could try flashing cm9.1 (ext3) to get a newer bootmenu and cwm versions before flashing cm10. no need to flash any gapps, just wipe system/cache partitions and flash the cm9.1 rom by itself. reboot into cm9.1, do basic set up. once it's ready reboot into recovery and do the above steps, starting from step 3, to flash cm10.
good luck.....
edit: did you get your cm10 rom from here:
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/
Click to expand...
Click to collapse
I did try using that link but the files still would abort when flashing, also tried http://d-h.st/users/Quarx files it did the same thing
I followed your instruction but decided to goto cm 9 first I flashed the (ext3) file it installed and cm9.1 installed also installed twrp with no issues but when I was going through cm9 and its functions I couldent go on line a popup message (Unfortunately, brower has stopped) also I wasn't able to log on google play a pop up message (Unfortunately,com. google android.gb has stopped). so I got fed up and decided to goto cm10.1 so I first flashed with ext4.zip it installed and then tried to flash 10.1 file once again the file wouldn't install it gave me aborted file message again. I had no choice to reboot and I had to reinstall the factory file(brick). I am now back to where I started :silly: cm7 2.3.7 its been a hell of a weekend ........... ill give it another shot soon :fingers-crossed: