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?
I've tried installing roms 4 times, and each time the same thing happens:
Boot into Clockwork
Wipe everything
install zip from sd card
choose the one i want
choose yes
then the only things it does :finding update package and opening update package, and then, BOOM, back to recovery, lasted only 1 second.
then i reboot system and nothing has changed. i am really confused and quite frustrated, can anyone help or give me some tips?
keen28 said:
I've tried installing roms 4 times, and each time the same thing happens:
Boot into Clockwork
Wipe everything
install zip from sd card
choose the one i want
choose yes
then the only things it does :finding update package and opening update package, and then, BOOM, back to recovery, lasted only 1 second.
then i reboot system and nothing has changed. i am really confused and quite frustrated, can anyone help or give me some tips?
Click to expand...
Click to collapse
Are you sure you're actually rooted? When you say "wipe everything" does that include cache/dalvik cache? If you wiped everything then rebooting the system shouldn't give the result "nothing has changed". Have you checked the MD5 of the ROM zip against the MD5 that it should "be"? If you can, boot into the phone and install terminal emulator and type "su" and tell me what it says...
i'm assuming you followed the steps in this tutorial to get rooted? did everything go as it was supposed to?
also, make sure when booting into recovery that you are not plugged in via usb.
zervic said:
Are you sure you're actually rooted? When you say "wipe everything" does that include cache/dalvik cache? If you wiped everything then rebooting the system shouldn't give the result "nothing has changed". Have you checked the MD5 of the ROM zip against the MD5 that it should "be"? If you can, boot into the phone and install terminal emulator and type "su" and tell me what it says...
Click to expand...
Click to collapse
Hah, yes, it is rooted. i put wipe everything to shorten the steps. I just installed terminal emulator, but when i typed "su" it just forms a new line with a #
am i doing something wrong now?
also, i realized that when i downloaded cm7, my computer (mac) unzipped the file, and then i rezipped before loading to sd card. if that doesn't make a difference then disregard this
keen28 said:
Hah, yes, it is rooted. i put wipe everything to shorten the steps. I just installed terminal emulator, but when i typed "su" it just forms a new line with a #
am i doing something wrong now?
also, i realized that when i downloaded cm7, my computer (mac) unzipped the file, and then i rezipped before loading to sd card. if that doesn't make a difference then disregard this
Click to expand...
Click to collapse
Okay...well try downloading it straight to your SD card from your phone browser. Also, see post above yours regarding having your phone plugged into USB when you boot into clockwork. If you've been doing this with your phone plugged in, that is your problem right there.
zervic said:
Okay...well try downloading it straight to your SD card from your phone browser. Also, see post above yours regarding having your phone plugged into USB when you boot into clockwork. If you've been doing this with your phone plugged in, that is your problem right there.
Click to expand...
Click to collapse
Ok, so i am not plugged in when trying to do this, so thats not the problem. i downloaded CM7 to my sd card, and i followed the instructions to install it, and now it is stuck on Installing update... but its only been here for about a couple mins, so im not sure whether its frozen or it just takes a while to install.
Ok, so it finially loaded, and it said it was complete. but now, i reboot and it goes from the HTC screen to the android intro thing, where the blue android is riding on a skateboard, but it goes about 3/4 across the screen then freezes, and a few seconds later restarts, but keeps doing the same thing over and over again. what should i do now?
Sounds like you are trying to flash a CM7 nightly without formatting system. In addition to wiping data, cache partition, Dalvik, you should go into Partitions menu from Clockwork Recovery and choose format system.
That was a wrinkle that tripped up many including myself when trying out the CM7 nightlies. After you have CM7 running, you don't have to format system again. ie. you can flash a more recent nightly just by clearing both caches.
stone_ship said:
Sounds like you are trying to flash a CM7 nightly without formatting system. In addition to wiping data, cache partition, Dalvik, you should go into Partitions menu from Clockwork Recovery and choose format system.
That was a wrinkle that tripped up many including myself when trying out the CM7 nightlies. After you have CM7 running, you don't have to format system again. ie. you can flash a more recent nightly just by clearing both caches.
Click to expand...
Click to collapse
hah, yes, that was exactly the problem. i figured it out tho. thanks, but now with cm7 i don't have Market, and i can't sync my google account to my phone. any suggestions?
Yea download the gapps package for 2.3 and flash it just like you ddid the rom minus wiping data and caches. That's if you're on CM7. Check the development section
Sent from my Liberty using XDA App
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239
hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.
janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!
Hello,
I have been using the cM7.1-11
My phone was slowing down so I decided to install the CM7.2.0
I did it probably wrong:
- I started my phone with volume down + power
- I did a wipe ((wipe data/factory reset + wipe cache partition)
- I try to do install the zip
But nothing happen. I have the message
E:failed to open /sdcard/update.zip
E:signature verification failed
E: can't mount cache
I can not even reboot my phone it is stuck on the cm7.1-11 logo
I try to flash it with a sbf with RST but it is seem that i do not want to flash it error "0x700"
Do I lost my phone? (I already lost my girl yesterday :/) Not too much bad news please
Cid156 said:
Hello,
I have been using the cM7.1-11
My phone was slowing down so I decided to install the CM7.2.0
I did it probably wrong:
- I started my phone with volume down + power
- I did a wipe ((wipe data/factory reset + wipe cache partition)
- I try to do install the zip
But nothing happen. I have the message
E:failed to open /sdcard/update.zip
E:signature verification failed
E: can't mount cache
I can even reboot my phone it is stock on the cm7.1-11 logo
I try to flash it with a sbf with RST but it is seem that i do not want to flash it error "0x700"
Do I lost my phone? (I already lost my girl yesterday :/) Not too much bad news please
Click to expand...
Click to collapse
You should do the wipe and flashing in CWM recovery and not in the stock recovery.
There's a generic Froyo SBF you can find the Development thread. Flash it via RSDlite in bootloader mode and start all over again.
Sent from Transformer TF101 (B60) via XDA Premium HD
farsight73 said:
You should do the wipe and flashing in CWM recovery and not in the stock recovery.
There's a generic Froyo SBF you can find the Development thread. Flash it via RSDlite in bootloader mode and start all over again.
Sent from Transformer TF101 (B60) via XDA Premium HD
Click to expand...
Click to collapse
Thank but I can not flash it
The battery power is ok But when I click on START I have a error at start. Faled flasing process
http:/ /imageshack.us/photo/my-images/525/sanstitrepiw.jpg/
Sometimes pc related drivers may prevent the flashing to go through. Try different pc with fresh drivers installed then.
Sent from my awesome Defy: JB 4.1.2 - XDA premium
farsight73 said:
Sometimes pc related drivers may prevent the flashing to go through. Try different pc with fresh drivers installed then.
Sent from my awesome Defy: JB 4.1.2 - XDA premium
Click to expand...
Click to collapse
The problem was on the computer side...thx
Thread moved. Please post questions here in Q&A in future.
Thanks
AvRS