Related
Hi fellow blackers,
My optimus black was on Nova Rom 2.2 v8:
http://forum.xda-developers.com/showthread.php?t=1161015
And I flashed it to v20n:
http://forum.xda-developers.com/showthread.php?t=1441901
I followed the instructions specifically these two before proceeding with the zip install.
1. Wipe Data/Cache (if not wiped, might cause problem)
2. Advanced > Wipe Dalvik Cache (same as data/cache, might cause problem)
After flashing, I can't seem to install any app from Market. It says that I have insufficient space on device.
So did some searching (google and here on XDA):
Here are their suggestions:
1. Install Marketfix - unfortunately, I can't install this because it is already saying I have insufficient space.
2. Clear market cache - after clearing (cache and data), I still says insufficient space
3. Uninstall market update - Going to settings - Application - manage application then selecting Market, I don't see any uninstall button. Just Force close, cancel and clear cache, clear data..
4. Finally I saw knzo's supposedly fix for this: Something to do with file system (nova is on EXT4 while stock is on EXT3)
http://forum.xda-developers.com/showthread.php?t=1212370&highlight=insufficient
I wasn't able to try option 1 because the file was removed on all file sharing sites.
Options 2 and 3 - restore factory settings isn't working. The phone is not doing anything after I click Erase everything. It just hangs
Any other suggestions?
Try reflash ROM with wipe all data and cache in CWM including dalvik cash and formating partitions in "mounts&storage".
Or this!
Try wipe cache and dalvik cache...worked for me
hmm pardon me, but how do I boot into recovery? I tried powering the device on while holding volume down (also tried up and G button) but it didnt reboot into recovery.
Artyomperec said:
Try reflash ROM with wipe all data and cache in CWM including dalvik cash and formating partitions in "mounts&storage".
Or this!
Click to expand...
Click to collapse
Since I can;t install anything (rom manager etc.), I think I needed to do what you advised.
I was able to flash the stock then started up from there
Since I can;t install anything (rom manager etc.), I think I needed to do what you advised.
I was able to flash the stock then started up from there
Click to expand...
Click to collapse
Have you tried flash this MOD for enter in recovery from power off phone pushing "G" button, not pressed and hold, but pushing every time when boot, work for me!
just try this
dsokua said:
Hi fellow blackers,
My optimus black was on Nova Rom 2.2 v8:
http://forum.xda-developers.com/showthread.php?t=1161015
And I flashed it to v20n:
http://forum.xda-developers.com/showthread.php?t=1441901
I followed the instructions specifically these two before proceeding with the zip install.
1. Wipe Data/Cache (if not wiped, might cause problem)
2. Advanced > Wipe Dalvik Cache (same as data/cache, might cause problem)
After flashing, I can't seem to install any app from Market. It says that I have insufficient space on device.
So did some searching (google and here on XDA):
Here are their suggestions:
1. Install Marketfix - unfortunately, I can't install this because it is already saying I have insufficient space.
2. Clear market cache - after clearing (cache and data), I still says insufficient space
3. Uninstall market update - Going to settings - Application - manage application then selecting Market, I don't see any uninstall button. Just Force close, cancel and clear cache, clear data..
4. Finally I saw knzo's supposedly fix for this: Something to do with file system (nova is on EXT4 while stock is on EXT3)
http://forum.xda-developers.com/showthread.php?t=1212370&highlight=insufficient
I wasn't able to try option 1 because the file was removed on all file sharing sites.
Options 2 and 3 - restore factory settings isn't working. The phone is not doing anything after I click Erase everything. It just hangs
Any other suggestions?
Click to expand...
Click to collapse
2 days ago I got this problem too, but SOLVED when I upgrade to CWM 5.0.2.6 (from CWM 4.0.1.5) then re-flashing with redy2006 V20N
what version CWM u have?
dsokua said:
hmm pardon me, but how do I boot into recovery? I tried powering the device on while holding volume down (also tried up and G button) but it didnt reboot into recovery.
Click to expand...
Click to collapse
just try adb reboot recovery from your PC to go to CWM
Just for be able to post new thread. Sorry.
kingtawon said:
2 days ago I got this problem too, but SOLVED when I upgrade to CWM 5.0.2.6 (from CWM 4.0.1.5) then re-flashing with redy2006 V20N
what version CWM u have?
just try adb reboot recovery from your PC to go to CWM
Click to expand...
Click to collapse
Ooh, I didn't update my CWM so I think it was on 4.x.x.x, Was able to flash and install apps in 5.0.2.6
Anyway, Im on temasek kangs build now
dsokua said:
Ooh, I didn't update my CWM so I think it was on 4.x.x.x, Was able to flash and install apps in 5.0.2.6
Anyway, Im on temasek kangs build now
Click to expand...
Click to collapse
so, still got same issue ?
Can anyone please help?
I just installed the Ultimate JB ROM XXLSA 4.1.2 v5 upgrade on top of v4.
All went perfectly well and I was able to enter all my setup and account details after the initial boot of the phone.
When I tried to re-install apps from Google Play, however, (Titanium Backup Pro, Quickboot) the phone hangs at the Samsung Splash screen and won't go any further. I re-tried the procedure 3 times but each time the result is the same.
Can anyone tell me what the problem could be? I followed all the instructions about wiping etc. correctly.
Trevor
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Kangal said:
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Click to expand...
Click to collapse
Mystery solved - well partly. Turns out Titanium Backup Pro was causing it on my phone for some reason. This was naturally the first app I wanted to install so I could restore apps one by one from the Nandroid backup. I tried Quickboot too which also caused the same problem so because TB and then QB did the same thing I assumed every app was going to cause trouble. Shouldn't jump to conclusions, I know.
I have JB Ultimate XXSLA v5 installed and am restoring my apps one at a time from Google Play and making new Nandroid backups as I go along.
And now I just tried installing TB free version - the phone boots normally! Then I installed the TB Pro version and again the phone boots normally. When TB was the first app I installed after the ROM upgrade it hung up the phone every time on 6 attempts. I'll try re-installing Quickboot now and see what happens. Conclusion: I must have been doing something in the wrong sequence but can's see what.
Many thanks for your help.
Trevor
sacentre said:
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Click to expand...
Click to collapse
I suddenly started getting "unfortunately the process android.process.acore has stopped" messages.
My "home launcher" welcomes me as if it's the first time I turned on the phone.
I just rebooted and got a whole series of "has stopped" messages.
Please help me resolve this problem.
"unfortunately, the process Google Partner Setup has stopped"
"unfortunately, DoggCatcher has stopped"
"unfortunately, Talk has stopped"
"unfortunately, Google+ has stopped"
"unfortunately, Titanium Backup has stopped"
"unfortunately, Calendar has stopped"
"unfortunately, Google+ has stopped"
"unfortunately, Astrid tasks has stopped"
I think this all started at about the time I got a message that "Contacts" was adjusting to the change in language (I use English and Hebrew on my phone). But I don't know what caused what.
This is making my phone almost unusable.
Following the instructions at
http://androidforums.com/huawei-ide...ndroid-process-acore-has-stopped-working.html
I went to settings>applications>running>all and scrolled to "contacts" opened it and chose "clear data" - then went back to "contacts storage" and did the same thing.
That did not resolve the problem.
Galaxy S GT-I9000
Android 4.1.2
Cyanogen Mod 10.0.0
webmanoffesto said:
I suddenly started getting "unfortunately the process android.process.acore has stopped" messages.
My "home launcher" welcomes me as if it's the first time I turned on the phone.
I just rebooted and got a whole series of "has stopped" messages.
Please help me resolve this problem.
"unfortunately, the process Google Partner Setup has stopped"
"unfortunately, DoggCatcher has stopped"
"unfortunately, Talk has stopped"
"unfortunately, Google+ has stopped"
"unfortunately, Titanium Backup has stopped"
"unfortunately, Calendar has stopped"
"unfortunately, Google+ has stopped"
"unfortunately, Astrid tasks has stopped"
I think this all started at about the time I got a message that "Contacts" was adjusting to the change in language (I use English and Hebrew on my phone). But I don't know what caused what.
This is making my phone almost unusable.
Following the instructions at
http://androidforums.com/huawei-ide...ndroid-process-acore-has-stopped-working.html
I went to settings>applications>running>all and scrolled to "contacts" opened it and chose "clear data" - then went back to "contacts storage" and did the same thing.
That did not resolve the problem.
Galaxy S GT-I9000
Android 4.1.2
Cyanogen Mod 10.0.0
Click to expand...
Click to collapse
I have the same problem ...
mafian59 said:
I have the same problem ...
Click to expand...
Click to collapse
I had already
Cleared Cache
Reset to Factory
but had not Cleared Dalvik Cache (it's under Recovery / Advanced / Clear Dalvik Cache)
The ROM'ed CyanogenMod
and GApps
I finally did all that with "Clear Dalvik Cache" and that helped a lot.
My phone was working great
but then I got another one of those "process stopped working" messages.
Still, my phone is working well and I do actually have a software keyboard now.
I'll try to work out the remaining "stopped working" problem later.
So far I haven't followed the advice below:
quack75 said:
I advise you to be born again smartphone.
then:
Factory Reset, Wipe Cache and Wipe dalwik
with odin install GINGERBREAD (THE LAST STOCK FOR YOUR COUNTRY)
root with cf-root
now from the recovery install the ROM of your choice
This is the only way to definitely eliminate all the problems of your device
Click to expand...
Click to collapse
Are you using titanium back up?
snapper.fishes said:
Are you using titanium back up?
Click to expand...
Click to collapse
It's a sad story. I have Titanium Backup on my phone, but it wasn't running backups (the folder is empty) so I can run a backup now, but I don't have a "before" backup.
I had it set to run nightly, but I guess after the last time I ROM'ed it reverted to it's default.
Oops, my bad.
I guess a factory data reset in settings / backup&reset / FACTORY DATA RESET would be the trick it is always recommended after flashing a new rom to start it fresh.
Dyn4m1c said:
I guess a factory data reset in settings / backup&reset / FACTORY DATA RESET would be the trick it is always recommended after flashing a new rom to start it fresh.
Click to expand...
Click to collapse
Yes
Cleared Cache
Reset to Factory
Wipe Dalvik Cache (I found it under Recovery / Advanced / Clear Dalvik Cache)
Click to expand...
Click to collapse
Apparently "Wipe Dalvik Cache" is very important
http://www.youtube.com/watch?v=LhSGyN5BGNE
http://stackoverflow.com/questions/7541281/what-is-dalvik-and-dalvik-cache
http://www.xoomforums.com/forum/jelly-bean-general-discussion/19820-wipe-cache-dalvik-cahe.html
http://www.androidgadgematic.com/2012/07/how-to-clear-dalvik-cache-on-android.html
Before flashing the rom its recommended to do the Factory reset + Wipe Cache + Advanced/Wipe Dalvik Cache in the recovery, then after flashing it and the phone its configured you do the factory data reset in the settings/backup&reset and then you have a clean installed rom prolly without any error otherwise its a rom issue.
I Agree
Dyn4m1c said:
Before flashing the rom its recommended to do the Factory reset + Wipe Cache + Advanced/Wipe Dalvik Cache in the recovery, then after flashing it and the phone its configured you do the factory data reset in the settings/backup&reset and then you have a clean installed rom prolly without any error otherwise its a rom issue.
Click to expand...
Click to collapse
I agree that you should
1. Factory reset +
2. Wipe Cache +
3. Advanced/Wipe Dalvik Cache in the CWM Recovery / Advanced, then after
4. Flash the ROM (and also Flash GApps
- Note: it looks like there are lots of great Google Apps to explore http://www.google.com/mobile/android/
Step by Step: How I "Wiped" my Phone and Then ROM'ed It
I use ClockworkMod ROM Manager http://www.clockworkmod.com/
- Cool, during the "research" for writing this I came across the CWM Tether Drivers http://www.clockworkmod.com/tether/drivers. I've been having problems tethering my laptop to my phone. Hopefully this will resolve that problem.
- Copy all .zip files to root of your phone: cm-10.0.0-galaxysmtd.zip, gapps-jb-20120715.zip
- http://download.cyanogenmod.org/?type=stable&device=galaxysmtd
- http://goo.im/gapps
- Long Hold on Power button to open "Phone Options"
- Select Reboot
on "Reboot phone" dialog box select "Recovery"
Phone reboots into "CWM-based Recovery" which is "ClockworkMod"
- in this mode you use the volume button to move up and down the list, and the power button to "select"
- Select the option to "Wipe data/factory reset"
- Arrow down to "Yes" and press the power button to select it
- That runs and you are taken back to the "CWM-based Recovery" screen
- Go down to "Wipe cache partition" and press the power button to select it
- Arrow down to "Yes" and select it
- That runs and you are taken back to the "CWM-based Recovery" screen
- Go down to "advanced" and select it
- Arrow down to "Wipe Dalvik cache"
- Arrow down to "Yes" and select it
You've "wiped" your System. Now it's time to ROM it.
- Choose " ***Go Back ***"
- Choose "install zip form sdcard"
You are taken to the "Apply update from .zip file on SD card" screen
- Choose "choose zip from sdcard"
- Select the ROM you have on the SDCard (you may have to arrow down a lot)
- You arrive at "Confirm install?"
- Select "Yes"
- That will run for a minute
- Again select "choose zip from sdcard"
- Arrow down to GApps and select it
- Arrow down to "Yes"
- Choose "*** Go Back***"
- Choose "reboot system now"
- Welcome to your New old phone. :laugh:
-----------------------------------------
Galaxy S GT-I9000
Android 4.1.2
Cyanogen Mod 10.0.0 :laugh:
Thanks!
Dyn4m1c said:
Before flashing the rom its recommended to do the Factory reset + Wipe Cache + Advanced/Wipe Dalvik Cache in the recovery, then after flashing it and the phone its configured you do the factory data reset in the settings/backup&reset and then you have a clean installed rom prolly without any error otherwise its a rom issue.
Click to expand...
Click to collapse
Thanks for the tip of going into settings and backup and restore after flashing rom. Had been having problem with process android.acore for weeks and this tip solved issue.
Of course wiping all those junks cache are important while flashing. We dont wanna keep some extra garbage (if cash then its allowable ) inside our home rite? juz throw it off
Gidron79 said:
Thanks for the tip of going into settings and backup and restore after flashing rom. Had been having problem with process android.acore for weeks and this tip solved issue.
Click to expand...
Click to collapse
Np any problem u have just tell us
How do I exit an application or go to home page? It doesn't have a button to go back to home or anything. I prob need to reboot to recovery and reflash this rom but I can't even find a way to reboot to recovery.
tonie972 said:
How do I exit an application or go to home page? It doesn't have a button to go back to home or anything. I prob need to reboot to recovery and reflash this rom but I can't even find a way to reboot to recovery.
Click to expand...
Click to collapse
To exit an app you can activate the option "main menu" ==> developer tools ==> last entry called "close apps" or something ...when you have activated the option you can stop it by holding the return-button ...
you can extend your reboot-menu by activating the option "extended reboot menu" under the developer tools ...an tthen you can reboot in the recovery directly...
if you don`t have the menu "developer tools" you must push 7-times on the build-number (About the device)...
snapper.fishes said:
Are you using titanium back up?
Click to expand...
Click to collapse
sir......is tis problem connected with tb? yes i ve tb and this problem happnd to me aftr restoring system datas (data only) from tb.....
Hey all! If none of the above solutions are working for you (like in my case), then please try this solution I found that worked for me:
1. Uninstall the app that is causing the popups (this could be Facebook, OneNote, WhatsApp, Skype, etc...).
2. Disable Goolge+.
3. Reinstall app that was causing the popups (sign in, get it going).
4. Re-enable Google+ (I actually haven't cause I don't use it, but that's up to you).
I'm not allowed to ask this in the dev forum as I'm not up to my 10 posts quota, so sorry for posting this here!
In the LightJB instructions instruction 3 is "wipe data, wipe cache, wipe dalvik-cache, wipe system"
I've got CWM installed (LQ4 and CoCore 6.0) and the options in the CWM recovery menu are "wipe data/factory reset" and "wipe cache partition".
Am I right in assuming that I should choose to do both of those two options, and then also in the "advanced" menu do the "wipe dalvik cache" option too? Just checking! Once I've done this once, I'll become a natural at it...
Cheers!
Matt
I guess you're right... But why don't you just flash a CoCore E kernel with TWRP.. Wouldn't that be much easier?
Its way more user friendly than CWM....
And yes, do have a backup of everything as Factory Resetting and wiping data is going to erase all your apps, etc.
BTW- Questions like this belong to Q & A thread.. Not the Development thread
Sent from my phone, because I'm away from my PC right now
Sami Kabir said:
I guess you're right... Why don't you just flash a CoCore E kernel with TWRP.. Wouldn't that be much easier?
Its way more user friendly than CWM....
Sent from my phone, because I'm away from my PC right now
Click to expand...
Click to collapse
I guess I'd just heard more about CWM than TWRP. I might be a noob here, but I'm not put off by command line-type stuff. I can still remember how to join multiple uuencoded text files together to get lovely pictures of Winona Ryder appearing on my screen in 1993, before I'd even heard of a graphical browser.... happy days!
Cheers for the pointer!
Matt
go advanced ...
tapatalked
larkim said:
Am I right in assuming that I should choose to do both of those two options, and then also in the "advanced" menu do the "wipe dalvik cache" option too? Just checking! Once I've done this once, I'll become a natural at it...
Matt
Click to expand...
Click to collapse
Matt,
Read my thread with CWM guide (see my signature) and i think you will be fine.
Do a Nandroid Backup before start to flash a new ROM.
Wipe data/factory reset
Wipe cache partition
Advanced -> Wipe Dalvik cache
1. Download the ROM from the link given in the article featuring that ROM. It should be a zip file.
2. Connect your phone to your computer via USB and mount its storage card.
3. Copy the downloaded ROM to the root of the storage card.
4. Power your phone off and reboot it into recovery. This will involve using a combination of your device’s hardware keys. Once in recovery, you can navigate its menu using the volume up and volume down hardware keys or your phone’s trackball / optical track pad if it comes equipped with one.
5. Use the ‘backup and restore’ feature of recovery to backup your existing ROM installation, software and data. This step is known as performing a nandroid backup. ALWAYS perform a backup before flashing a custom ROM, UNLESS you can afford to lose everything that’s on your phone at the moment.
Note: ALWAYS choose to perform the following steps 6, 7 and 8 UNLESS the ROM you are attempting to flash is an updated version of the same ROM that you are currently using, and is compatible with the current installation’s data. It is usually mentioned with the update whether you can install it over a previous version without wiping its data or not.
6. Get back to the main recovery menu and use the option ‘wipe data/factory reset’. You will be prompted to confirm this action. Select “Yes – Delete all user data”.
7. From the main recovery menu, select ‘wipe cache partition’. You will be prompted to confirm this action. Select ‘Yes – Wipe Cache’.
8. From the main recovery menu, enter the ‘advanced’ menu. From this menu, select ‘Wipe Dalvik Cache’. You will be prompted to confirm this action. Select ‘Yes – Format/System’.
9. From the main recovery menu, enter the ‘Mounts and Storage’ menu. From this menu, select ‘Format/System’. You will be prompted to confirm this action. Select ‘Yes – Wipe Dalvik Cache’.
10. Go back to the main recovery menu by pressing the back button and select the ‘Install zip from SD card’ option.
11. Select ‘choose zip from sdcard’ to get a list of the files and folders on your SD card. Scroll to the ROM’s file that you copied there in step 3, and select it. You will be prompted to confirm this action. Select ‘Yes – Install file_name.zip’ where file_name.zip is the name of the zip file that you are trying to install.
12. Wait patiently while the ROM is flashed to your phone via recovery.
13. Once the installation is complete, head back to the main recovery menu if you aren’t there, and select ‘reboot system now’. Your phone will now boot into the newly installed ROM.
Click to expand...
Click to collapse
R_a_z_v_a_n said:
Matt,
Read my thread with CWM guide (see my signature) and i think you will be fine.
Do a Nandroid Backup before start to flash a new ROM.
Wipe data/factory reset
Wipe cache partition
Advanced -> Wipe Dalvik cache
Click to expand...
Click to collapse
Done, thanks!
My last question - when i've rebooted, I'm prompted to sign into my Google Account and re-install my apps from the google backup. Is this the "best" way to do it, or is it better to use alternative sch as Titanium? I'm not bothered about lost data, the only data I care about is in my gmail account anyway.
Cheers!
Matt
Reinstall your apps with that app you make backups. If you do it with Titanium, then go for it, and restore with Titanium.
R_a_z_v_a_n said:
Reinstall your apps with that app you make backups. If you do it with Titanium, then go for it, and restore with Titanium.
Click to expand...
Click to collapse
Thanks. Its that sort of common sense stuff which I've found missing from many of the guides - they tell you how to root / flash etc, but leave nagging other questions unanswered - perhaps because the answers are so obvious to the authors that they are just second nature.
As it happens, I didn't bother with a Titanium backup as I wanted a clean phone - I've been trying to resolve a strange issue where my wifi goes really slow and stuttery after the phone has been on for a few hours. No-one else seems to have the issue, so I suspect it is down to at least one of my apps causing some chaos. With that in mind, a fresh install with no baggage seemed to be the best way to go.
(I used to suspect the Facebook apps (particularly Pages Manager) but I don't think they are the cause)
Thanks for all the help!
Matt
Sami Kabir said:
I guess you're right... But why don't you just flash a CoCore E kernel with TWRP.. Wouldn't that be much easier?
Its way more user friendly than CWM....
And yes, do have a backup of everything as Factory Resetting and wiping data is going to erase all your apps, etc.
BTW- Questions like this belong to Q & A thread.. Not the Development thread
Sent from my phone, because I'm away from my PC right now
Click to expand...
Click to collapse
For me cwm is more user friendly and more straight forward compared to twrp. I once tried twrp and after I mount system suddenly it said there's no os installed and I can't boot my phone. Luckily I can still enter download mode to flash back fw with odin. I don't understand how twrp works..haha :silly:
larkim said:
Thanks for all the help!
Click to expand...
Click to collapse
It was my pleasure, Matt. :highfive:
Well, for no other reason than that I wanted to tweak a few things before I started to live with LightJB, I chose to restore my phone using the CWM nandroid restore.
Bad move!
It all seemed to work fine, but on restoring I get the message that "Unfortunately, the process com.google.process.gapps has stopped". Mildly worrying, but moving on...
Then I came to try to reply to a sms message from my wife. Pressing in the reply box didn't bring up a keyboard. Odd.
I went into other apps and found I couldn't type there either.
Went into settings, and neither the samsung keyboard nor the swype keyboard appear to have been re-stored via the backup / restore.
Any hints?
Matt
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
@Tomy_Delmar
Tomy, CyanogenMod is already custom ROM, there is always root access on it
Try it this way:
download Gapps for CM10.2x (Android 4.3.x) and paste them on your external SD card
put the card in your phone
run it in recovery mode
wipe cache and dalvik cache
flash Gapps for 4.3
wipe again cache and dalvik cache.
reboot
Post if it worked.
Tomy_Delmar said:
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
Click to expand...
Click to collapse
As the partition layout is different in cm10.2, you should flash it at least 2 times and wait for system to be stable for about 15-20 minutes
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Tomy_Delmar said:
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Click to expand...
Click to collapse
First of all, don't forget to quote the user whom you want to contact, because he don't get any notification until you quote. I was just checking around the questions and thus I saw this.
Sometimes, there is requirement of g-apps for the core system to be working ( Not sure in case of cm10.2). Try with g-apps (you may choose light package).
In my opinion, it should work. If not, try from the start ( flashing gingerbread with Odin with repartition ticked, then its root and finally cm10.2 from recovery)
Also make sure your handset is i9000 and you are using cm10.2 for the same.
And finally, All the best
CM doesn't neccesarily need Gapps to boot up. In fact most custom roms don't - they are still usable, just that everything Google-related doesn't work.
Its a bit odd seeing as how you've pretty much done what I would have done if I was installing CM to a Galaxy S. I can't think of any reason why it wouldn't work.
As far as I know as well, formatting /system is more of a last-resort method, not something you'd immediately do.
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Sent from my GT-P7510 using Tapatalk
Tomy_Delmar said:
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
Click to expand...
Click to collapse
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Soryuu said:
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Click to expand...
Click to collapse
Unfortunately, Wiping data, cache and Dalvik cache again after I had flashed CM 10.2 didn’t make it start.
tetakpatak said:
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Click to expand...
Click to collapse
When I tried to flash CM 10.2 the first time – at that time RC1 was the newest version – I was asked to flash it a second time, which I did. To be precise, the following message was shown:
This ROM uses an incompatible partition layout
You /data will be wiped upon installation
Run this update.zip again to confirm install
This message hasn’t been shown again since then. I flashed CM 10.1.3 again and tried to flash 10.2 a second time, but the message wasn’t shown again.
Going back to CM 10.1.3 worked without any problem.
------------------------------------------
Now I have CM 10.2 on my phone and it starts normally
I flashed Stock-Android 2.3.6 with Odin (v1.82). Tetakpatak, thank you for the excellent guide and the video! As written in the guide, I used "s1_odin_20100512.pit" as PIT-file.
(I executed Odin on an old computer with Windows XP 32bit, as the guide says Odin 1.82 works better with Win XP.)
Then I installed CM 10.2 over Stock-Android 2.3.6. I followed the official instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd?setlang=en
(I executed Heimdall on my new computer with Windows 7. Heimdall 1.4RC2 doesn’t work on Win XP. If one executes Odin and Heimdall on the same PC, I could imagine this could lead to confusion, because Odin needs the Samsung-USB-drivers and Heimdall needs WinUSB. I’m not sure if this really leads to problems. But one should keep that in mind.)
I didn’t flash CM 10.1.3 before 10.2, because I didn’t need to restore a nandroid backup previously made with CM 10.1.3. There were no important data on the phone.
Many thanks to all who gave me advice and helped my solving the problem!
Tomy
HELP MEEE
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
This is the forum for the original Galaxy S, not the Nexus 5, sorry mate
However I think your problem can be fixed by doing a full data/cache wipe so it might be worth a shot
Flash Boot.Img. This might solve the bootloop!
I think, You just need to flash the boot.img (available in the Cynogen Bundle Zip Folder) after installing Cynogen Mod. Me too got stuck on the animation part for a long time. Then I found out this:
CyanogenMod builds for endeavoru currently do NOT support any bootloader version number below: HBOOT 1.28. As the device is S-ON (security-on bootloader), for a working installation you must extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode.
Source: Cynogen Mod Wiki
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
Which version of CyanogenMod are you using?