I'm running into some weird issues with my Fascinate when trying to flash to a 4.X.X ROM.
I've followed the guide here http://forum.xda-developers.com/showthread.php?t=1238070 to the letter, starting from bone stock, clearing caches, factory resetting, etc when installing a new ROM.
The phone and CWM will work perfectly up until a 4.X.X ROM is flashed (usually a Cyanogenmod derivative). The ROM itself will normally flash okay, but when I go back into CWM to install Gapps, I get the following errors on CWM bootup --
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I can run the Gapps install from CWM, and it looks like the installation is taking place (normally no errors I can see) but it won't take after a reboot -- the apps don't show up in my list of installed apps. And yes, I'm checking the version of Gapps against the Android release to see if they're compatible.
So other than the Gapps issues, things are working fine. I tried a 4.2.2 MIUI ROM that had Gapps included, and it's working, but MIUI doesn't feel right to me.
Is there any other way to get Gapps onto my phone other than CWM once I've already installed a 4.X.X ROM, OR to fix the CWM errors (assuming they're what's causing CWM to not install Gapps correctly)?
Chris
It sounds like you have a funky flash coming up from what we refer to as EH03 Stock (Verizon android 2.3.5),, but eh03 is really the radio version,,,
That is what usually causes those mount errors in recovery.
The must effective way to fix is to use odin to go back to stock, then come up to your 4.2.2 ROM of choice.
You did not mention which gapps or rom you wanted to try but keep in mind the gapps you start with needs to be of the same age/time frame as the ROM. If the ROM is dated 7/13/2013 get a gapps package prior to that date.
You will then have to upgrade the apps through the play store to get latest ones compatible with the rom you choose.
.
hhp_211 said:
It sounds like you have a funky flash coming up from what we refer to as EH03 Stock (Verizon android 2.3.5),, but eh03 is really the radio version,,,
That is what usually causes those mount errors in recovery.
The must effective way to fix is to use odin to go back to stock, then come up to your 4.2.2 ROM of choice.
.
Click to expand...
Click to collapse
I downloaded two alternate EH03 ROMs, flashed them, and then upgraded to the Cyanogen nightly. The errors are still showing up in CWM once I install Cyanogen, but not before.
Is there another likely culprit? A bad CWM4?
Chris
Victory?
I downloaded another copy of the Bootloader and CWM4, and then installed Cyanogenmod AND Gapps before booting into 4.2.2. That worked.
Thanks for your help,
Chris
Related
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Do a fresh download of a cm7 nightly.
Put it into your internal sd card.
Boot into cwm recovery
Wipe data/cache/dalvik
Flash cm7 zip
If you get stuck at the screen flash the zip again from recovery and it should boot.
Also, don't flash it via flash update, do it via flash zip.
Sent from my GT-I9100 using XDA Premium App
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Canadianreaper said:
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Click to expand...
Click to collapse
It's weird, seems to be due to custom versions of cwm recovery in most kernels, the other way todo it is to flash codeworx's cwm kernel then cm7, which seems to make it work with one flash of cm, but glad to hear you got it going.
Sent from my GT-I9100 using XDA Premium App
Same Here
Canadianreaper said:
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Click to expand...
Click to collapse
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
gtizon said:
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
Click to expand...
Click to collapse
Pull the battery and boot to cwm again. Wipe data/factory reset, wipe cache and flash cm7 (provided u put it on ur sd card).
If not, flash a stock rom, let boot and place latest cm7 .zip on ur ad card. Flash a kernel with cwm and flash cm7 .
I also have this problem. Also I can't back up my current rom, because it gives the same message as in First post. And I want to flash MIUI -rom. What to do?
Any solutions to this? I rooted using Zedomax's Method. all went smoothly. When I went into Rom Manager to backup, it said I had to flash CWM, I said ok. Now I get the same error as the OG. Don't know if the recovery worked prior to going into ROM Manager. I'm thinking of running the Zedomax's Method again to see if it reinstalls a workable CWM.
Hi peeps
(I've tried looking for related posts but nothing comes up with my stuff)
I have downloaded Rom Manager Premium and also downloaded clockwork recovery, how ever every time I reboot into recovery to install i get this
E:failed to verify whole-file signature
E:signature verification failed
I have flashed the file before using Odin but i get other stuff saying E: cant mount (random stuff)
My phone is rooted
What am i doing wrong?
Rom Manager & CWRecovery don't work together on the SGS2. It's one or the other. For example, if you have CWRecovery installed (as a result of rooting your phone with a CFRoot kernel, for example), using Rom Manager has a tendency to break CWRecovery and/or put your phone into a bootloop.
So you're going to have to decide what you want to use.
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Depends what you used/did to flash the new rom. If you flashed it in CWRecovery, then that's unusual for it to be broken purely by flashing a custom rom meant for a I9100/T. Not completely unheard of mind you, but not usual.
If you used Rom Manager to flash the rom when you already had CWRecovery installed, then as per my previous post, it's obvious CWRecovery was broken by Rom Manager.
Again as per my previous post, one or t'other. Up to you. But use both at your peril.
olster said:
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Click to expand...
Click to collapse
So would you recommend that I remove ROM manager and just flash CW Recovery?
I wouldn't recommend you do anything/use one over the other. I'm just saying that you run the risk of having major problems (bootloop/broken CWRecovery) if you have both on your phone/try to use both.
Personally speaking, I've never had a problem rebooting my phone into CWRecovery every/any time I want to flash a rom/kernel/backup/restore.
Up to you which you use.
olster said:
So would you recommend that I remove ROM manager and just flash CW Recovery?
Click to expand...
Click to collapse
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Also when I use clockwork recovery
Anything I try to do i get this
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
What rom/kernel are you running and how did you root your phone ?
You could try flashing a CFRoot kernel from here, if that doesn't work you should probably get your stock firmware from here and flash that in Odin. After that you can use a CFRoot kernel to root your phone.
That will give you a clean slate with CWRecovery working.
Edit to add - Yes, you're getting that in CWRecovery because Rom Manager obviously broke it as I've already said.
olster said:
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Click to expand...
Click to collapse
I am using 2.3.6 XWKK5 ROM with the CF-Root-SGS2_XW_OXA_KK5-v5.0-CWM5.tar
Then try my suggestions in my previous post.
Right, I have managed to start again and got it working again.
Thanks your help
NP. Glad you got it working
olster said:
Right, I have managed to start again and got it working again.
Thanks your help
Click to expand...
Click to collapse
Hello Everybody,
my boss got me a Galaxy ACE S5830i in order to test some app development and I immediately managed to root it and install a custom ROM.
These were the steps I took
1- I flashed the update.zip I found around the web, for example here -> http://www.theandroidroot.com/root-install-cwm-recovery-samsung-galaxy-ace-s5830i/
2- I flashed CWM 5.0 and immediately, without rebooting, saw the new Recovery. So it really did install!
3- I updated to CWM 6
4- I flashed thunder kernel in order to make the CWM permanent -> http://forum.xda-developers.com/showthread.php?t=2335947
5- I rebooted the phone in recovery mode and got the CWM. Everything was fine up to now
6- I flashed a ROM (after wiping everything). Actually, several roms. I tried first with CGM, then with Aroma and Retribution Beta. http://forum.xda-developers.com/showthread.php?t=1806471 All of them managed to install but none of them works. What ALWAYS happens is that the ROM installs, then I reboot and the phone does not go past the Samsung Logo. Then, and here we come to the weirdest part, when I reboot in recovery mode in order to flash another rom... I get the stock recovery! No CWM, no customizations!
What's happening, in your opinion? I tried to flash a custom ROM with Odin as well, but being on Linux I had to use JOdin and could not manage to flash anything because (as it ALWAYS happens with JOdin) I was not able to load a suitable PIT file. No success with wine+odin as well.
Please, could somebody help me? I can't use my boss phone, and can't return it to him until I get a working ROM on it
Thank you in advance
P.S. When I get to the Recovery I see some rows to the bottom:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Indalid argument)
and (I know 'cause I tried) I can't mount or format the /system partition. Maybe it's related, maybe it's not...
ilsecondodasinistra said:
Hello Everybody,
my boss got me a Galaxy ACE S5830i in order to test some app development and I immediately managed to root it and install a custom ROM.
These were the steps I took
1- I flashed the update.zip I found around the web, for example here -> http://www.theandroidroot.com/root-install-cwm-recovery-samsung-galaxy-ace-s5830i/
2- I flashed CWM 5.0 and immediately, without rebooting, saw the new Recovery. So it really did install!
3- I updated to CWM 6
4- I flashed thunder kernel in order to make the CWM permanent -> http://forum.xda-developers.com/showthread.php?t=2335947
5- I rebooted the phone in recovery mode and got the CWM. Everything was fine up to now
6- I flashed a ROM (after wiping everything). Actually, several roms. I tried first with CGM, then with Aroma and Retribution Beta. http://forum.xda-developers.com/showthread.php?t=1806471 All of them managed to install but none of them works. What ALWAYS happens is that the ROM installs, then I reboot and the phone does not go past the Samsung Logo. Then, and here we come to the weirdest part, when I reboot in recovery mode in order to flash another rom... I get the stock recovery! No CWM, no customizations!
What's happening, in your opinion? I tried to flash a custom ROM with Odin as well, but being on Linux I had to use JOdin and could not manage to flash anything because (as it ALWAYS happens with JOdin) I was not able to load a suitable PIT file. No success with wine+odin as well.
Please, could somebody help me? I can't use my boss phone, and can't return it to him until I get a working ROM on it
Thank you in advance
P.S. When I get to the Recovery I see some rows to the bottom:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Indalid argument)
and (I know 'cause I tried) I can't mount or format the /system partition. Maybe it's related, maybe it's not...
Click to expand...
Click to collapse
can u get temporary cwm recovery when selecting
'apply update from sd'
then look at this thread
forum.xda-developers.com/showthread.php?t=1118688
as9333 said:
can u get temporary cwm recovery when selecting
'apply update from sd'
then look at this thread
forum.xda-developers.com/showthread.php?t=1118688
Click to expand...
Click to collapse
Hello,
thank you for answering.
I can temporary get to CWM recovery for sure, but I don't know how to push the erase_image file (that I found) to the device. I'm only able to copy files on the SD, using another phone, and then flash them from CWM. Is there a way to make adb able to detect the device even when it's in recovery?
Thank you
ilsecondodasinistra said:
Hello,
thank you for answering.
I can temporary get to CWM recovery for sure, but I don't know how to push the erase_image file (that I found) to the device. I'm only able to copy files on the SD, using another phone, and then flash them from CWM. Is there a way to make adb able to detect the device even when it's in recovery?
Thank you
Click to expand...
Click to collapse
First try to flash another rom..if that not work then flash stock rom from odin..
Here is the link for unbrick your device.go here and try to unbrick..
http://forum.xda-developers.com/showthread.php?t=1840645
Sent from my GT-S5830i using Tapatalk 2
Are the ROMs you tried based on CM7/9? Because if they are, you need to format your system partitions to EXT4. You can do that with the multi-formatter.
Also, you say that you have your stock recovery back. Check the ROM zips that you flashed for any boot.img. If there is, check which kernel and which version. Some older kernels still have stock recovery.
As even stock recovery cannot mount /system, clearly your system partitions are corrupt. Format with the multi-formatter and flash a CM7/9 based ROM or flash back stock firmware via Odin.
If you choose the multi-formatter, remember to flash a kernel afterwards. And if you prefer, one with a permanent CWM.
Sent because I <3 Aerith
New too this whole phone, but I've rooted & ROM'd the Kindle Fire (Gen 1.) Samsung Galaxy S3, LG Vortex, and a few other devices so I'm not stupid when it comes too this stuff.
I've never been a fan of CWM, but anyways I used the AIO Vibrant Toolbox too root it, then I added a recovery with the Custom ROM Button, selected the zip and it *Eventually* got me int CWMR v2.5.0.4, I downloaded c-Rom, and http://forum.xda-developers.com/showthread.php?t=2535547, I tried both but they each fail with
"Installing Update...
E: Error in /sdcard/ROM.zip
(Status 0)
Installation Aborted"
I wiped Dalvik, Factory Reset, Wiped Cache, eevrything. But nothing seems too have worked.
Same problem
Hi I'm currently having the same problem and I also have experience rooting other devices with no problem. I even re rooted the device from the beginning and still a no go. If anyone has any solution to our problems please reply thanks.
Bumping, any help available?
depends on what version of android your'e running, i'm assuming 2.2 since you just rooted it. so grab a cm7, cm 10.2, cm11 or any 4.4.2 rom and a 4.4.2 kernel as well. first flash cm7 and let it fully boot into the os, afterwards boot back into recovery and flash cm 10.2 same as before let it boot, now flash that 4.4.2 kernel and while in same recovery session choose "reboot recovery" option now go ahead and flash what ever kitkat rom you like...
Actually I rooted mine to stock eclair from 2.2. I wasn't sure if I needed to stay because all the guides showed to go to 2.1. It is currently rooted with stock rom and I haven't been able to get further than that.
v4vamp said:
Actually I rooted mine to stock eclair from 2.2. I wasn't sure if I needed to stay because all the guides showed to go to 2.1. It is currently rooted with stock rom and I haven't been able to get further than that.
Click to expand...
Click to collapse
try what i mentioned in my previous comment, it should get your device up to date.
Hi there,
Tried to install Hyperdrive but unfortunately I have crazy lags and problems with it. It is almost impossible to move around on the phone with it. The biggest problem I have is that It wont boot into TWRP recovery anymore. I made a backup before but when I try to install it with the android system recovery it fails (E:footer is wrong and E: signature verification failed)
I tried to flash Hyperdrive from recovery again (didn't work); I tried to wipe cache and format (didn't work)
Now I tried to flash a new Rom but apparently you cannot flash with the android recovery environment(I am also getting the two E: errors)?
Would like to get the phone back. Hope someone can help.
Do you remember the system baseband? This is critical. If it was MDK, then you could have used safestrap. If not, then you should have used safestrap, not MDK.
The A.R.E won't work, you need Odin + the tar file..