Hi,
I have international version of Note, and I was running ICS repack LP1 with MIUI + go launcher, and I was checking out ICS stunner.
I had CWM back up, so I tried to restore MIUI WITHOUT any wipe, and it got to error msg.
I restarted my phone, and tried it again AFTER I wiped Data + Dalvik, and the phone seemed stuck, so i restarted manually again.
And I wiped data + Dalvik to install old MIUI or ICS Stunner, and I am stuck in CWM installation mode FOREVER.
Finding update package...
Opening update package...
Installing update...
That's all it says, and the bar isnt moving either...
Can anyone help advise anything or how i should fix this?
I am tried to use ODIN to re-flash LP1 file I saved on desktop, but having problem with that too...
/cry!!!
Related
After allot of search work I still didn't find any solution for my problem.
(Goal is to flash my stock phone to Onecosmic's ICS 4.0.3)
PDA: I9000XWJVH
PHONE: I9000XXJVO
CSC: I9000XENJV4
What I did:
1. Root my phone with SuperOneClick.
2. Install Rom Manager.
3. Flash ClockworkMod Recovery and select my model.
4. Reboot into Recovery.
After this the phone reboots and ends up in normal recovery mode and starts installing the package? This is what I see.
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Can anybody tell me what am I doing wrong?
what i would've done, is to flash a simple CF-Root trough odin, wich allready contains CWM-recovery.
From there you will have to flash a mtd based rom, like cm7, then Onecosmics build
thats what i did ages ago, and i havent had any big problems afterwards.
Just search for Cf-Root at google and it should guide you to the right page.
its about as far as i can help you, as i never used oneclick-root apps, and had to manually flash CWM.
Thanks for your reply!! I will try that when I get home and post back my results.
*Edit:
It works! I have Onecosmic's ICS 4.0.3 running on my phone.
What I did:
1. Like you suggested rooted the phone again but now with with Odin and CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.zip.
2. Placed the ROM and Kernel on my sd card.
3. Boot in recovery mode and did an wipe data/factory reset and wipe cache partition. (Didn't want to install CM7 so tried it like this first )
4. Selected aply update from sd card and selected ICS_4.0.3.0(RC2.11)_Galaxy-S_Full.
5. It flashed the rom but it didn't go back to CMW recovery and showed the boot animation (colored blocks) way to long.
6. Taken out the batterij and started again in CMW recovery with button combination.
7. This time I did wipe data/factory reset, wipe cache partition and wipe dalvik cache.
8. Selected aply update from sd card and selected ICS_4.0.3.0(RC2.11)_Galaxy-S_Full. This time it went back to CMW recovery.
9. Selected aply update from sd card and selected ICS_I9000_20120107_r3180v_update. Went back to CMW recovery again.
10. Selected reboot system now.
After waiting for like 8 minutes I got an working phone with ICS installed!
*Sorry for the "detailed" explanation but I hopefully help other "noobs" with this issue
Seems that I am not done because Onecosmic's ICS Port Android 4.0.3 RC3 is out!
oh year, RC3 is fantastic
Hi, the same problem i have with CWM, I rooted device with SuperOneClick as well so maybe you can say which file should I download my curent rom is BUJV9?
nikiss said:
Hi, the same problem i have with CWM, I rooted device with SuperOneClick as well so maybe you can say which file should I download my curent rom is BUJV9?
Click to expand...
Click to collapse
Hi. Read this post and use the FAQ to install the latest CM7 nightly on you phone and then just reboot to recovery and install onecosmics ICS RC3
george23kk said:
Hi. Read this post and use the FAQ to install the latest CM7 nightly on you phone and then just reboot to recovery and install onecosmics ICS RC3
Click to expand...
Click to collapse
Thanks for reply I will try it
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
EDIT: I must correct myself. After rolling back to factory rom, I was experiencing the same issues, seems there some hardware issue. I sent the tablet back for repair, seems now it had nothing to do with GalaxianSoup. No need to worry, keep up the good work.
whiplash84 said:
Hello all,
I have an issue with latest CWM 5.5.0.4 recovery. It says the following error:
E:Error in /cache/recovery/last_log
(Read-only file system)
and other similar errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
and I'm unable to reflash GalaxianSoup ROM nor restore the original backed up 3.2 factory rom.
What actually happened ?
Once bought, I managed to root, flash CWM 5.5.0.4 recovery and install the latest GalaxianSoup ROM. Everything based on the guides in development forum and successful (all latest versions). All cool! System was working fine.
Yesterday, I was using tablet, installed few apps, nothing special and later left tablet turned on and charging. When I came back, it was turned off. Okay, tried to turned on, but the system never booted and always looped (seeing only Google logo and moving gears). I rebooted into recovery and noticed the error (see above).
Now, I'm basically unable to do anything. I tried to wipe data, cache and Dalvik cache several times, and reflash GalaxianSoup again (Galaxian + Gapps) or also restore the 3.2 system backup that I've made (always fails).
I've read on some other forums that it might have something to do with damaged SD card partition or something.
I'm out of ideas. Can anyone help me pleeeeease?
EDIT: I've got european Samsung Galaxy Tab 8.9 16GB WIFI version.
Click to expand...
Click to collapse
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
suwandiapr said:
Flash your recovery again through odin..
Then reflash your galaxian soup..
If not success, use odin and flash stock rom..
Dont forget backup your file from sdcard just in case if you need reset factory..
Click to expand...
Click to collapse
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
whiplash84 said:
Flashing of CWM didn't help to fix the issue, installing of GalaxianSoup didnt work at all (corrupted ZIP file error...)
Thanks God, reflashing of stock ROM via Odin did work, tablet is up and running. GalaxianSoup is definitely not stable enough yet, I'll stick to the stock rom fora while. Thank you!
Click to expand...
Click to collapse
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
bdfull3r said:
Galaxian Soup is more then stable enough. Bad flashes happen and you just said you had it up and running.
Click to expand...
Click to collapse
To be honest, it is kind of stable, but not enough, hence the beta label. Some further optimizing will be done once the team has ICS source. In my experience, it was stable, but sometimes it would turn off when in fell into Deep Sleep state. Now, the AOKP milestone 5 is giving me issues with the screen rotation. I've experienced both sides, AOSP and AOKP in their latest versions. Obviously there is more room for improvement, but I'm afraid the team is kinda stuck without source. They've done miracles without source though.
I am trying to install the Cm9 Captivate nightly from 05/22/2012.
*I am using a rooted UCKK4
I've gone through the steps and have successfully installed CwM Recovery (5.1.0.7) via an Odin kernel (Corn kernel for UCKK4). I have successfully booted into CwM (I am 100% positive I am not in the stock recovery). I wiped the cache and did a factory reset.
I have navigated to "install zip from sd card" and have selected the appropriate zip file. I get the following:
- Installing: /sdcard/Cm9.zip (I renamed it)
-Finding update package...
-Opening update package...
-Installing update...
-Replacing stock recovery with ClockworkMod recovery...
***This is where it seems to get "stuck". There is no progress bar to speak of, and can't seem to find any help from the all-knowing Google.
How long should it be "stuck" on this step?
I got a little anxious on a previous try and removed the battery. The phone booted fine into the stock rom.
The help of the community is greatly appreciated.
**EDIT
I've also wiped the DALVIK (sp?) cache to no avail.
**EDIT #2
I seem to have solved the problem. I re-flashed CwM from within Rom Manager (premium) and also downloaded the 5/23/2012 nightly for CM9. Following the steps above, I've now got a running CM9 on my Captivate.
I hope this helps anyone who may have had the same problem.
Don't rename what you flash. same with the backups you make, don't re name them. I know it's easier to find, but resist the temptation and don't rename them.
Enjoy ICS!
I'm currently running the latest CM9 on it with moboot... It seems like every time it boots up it pops up with that error message and literally won't go away and you have to reboot the device.. the only way I've found to temporarily fix it is to just wipe cache.... but it always comes back.
Is there any way to prevent this from popping up? It happened when I was on Classicnerd BUTTA too.
Wipe the system and caches, then reflash
I had this problem as well a while back. Wiping caches and reflashing the ROM worked for me.
And you guys didn't have the problem again, after that?
Help manually moving contacts and choosing a JB ROM.
If a pro could help me out I would appreciate it very much. I have been trying to move from a dangerous ICS build to JB and I am having this same problem.
My N7000 previously had this on it:
android 4.03
radio 19220zclp6
kernal version 3.0.15-i9220zclp1-cl131270 (bad ics kernal)
build number midnote 2.0 iml74k.zclp1
So I used ODIN to flash it to a GB rom but I got the com.android.process error and my phone would lock up.
So then I found this link http://forum.xda-developers.com/showthread.php?t=1424997 and flashed this ROM "N7000UBLR3 N7000UVOLR1 - Download - Argentina" from the bottom of the page. I wiped only the the cache (not the phone reset) and flashed it again but I still get the process error and phone locking up. I don't even know if this ROM is a safe ROM!!
Am I even on a safe kernal now? kernal n7000ublr3-cl890184 build imm76d.ublr3
What I need help doing is the following.
1. Before doing a full wipe, I need to either manually save my contacts to my PC or back them up. (no apps work but my pc can browse my phone) If I knew where my contacts were located, maybe I can manually copy them to my pc? So any help saving data from a partially unusable phone would help.
2. Flash to a safe GB rom, so I can then do the full wipes safely and then flash to a stable JB rom. (I have no clue which roms to choose here and need help).
Thanks for any help..
hello new to flasing obviously had my phone rooted and downloaded cm10.1 file along with gapps seperately but after wiping data . clear partition data, dalvik cache and then trying to install this rom it says error, aborted installation status 7. what can be the cause? im restoring back to stock rom till i can find out why this happened. i tried it several times but kept aborting. please help