Hello to whoever is reading this, I appreciate your help.
I recently saw Cyanogen Mod 10 on lifehacker.com and decided to change my ROM to CM 10. Its was working fine until I wasn't able to open the System Settings. I though I did something wrong and I reinstall CM 10. The first notification popped up was 'Unfortunately, the process com.google.process.gapps has stopped.' and next another one pops up, 'Unfortunately, Android Keyboard (AOSP) has stopped.' It keep crashing the stock keyboard and I only have the stock keyboard.
Next I try to uninstall CM 10 back to stock ROM, I opened ROM Manager and another notification pops up, 'Unfortunately, ROM Manager has stopped.'
So right now, I have a phone that has no system setting, no keyboard and I can't access ROM Manager.
Phone Model : LG OPTIMUS BLACK P970
ROM : CyanogenMod 10
Carrier : Starhub
iReaper said:
Hello to whoever is reading this, I appreciate your help.
I recently saw Cyanogen Mod 10 on lifehacker.com and decided to change my ROM to CM 10. Its was working fine until I wasn't able to open the System Settings. I though I did something wrong and I reinstall CM 10. The first notification popped up was 'Unfortunately, the process com.google.process.gapps has stopped.' and next another one pops up, 'Unfortunately, Android Keyboard (AOSP) has stopped.' It keep crashing the stock keyboard and I only have the stock keyboard.
Next I try to uninstall CM 10 back to stock ROM, I opened ROM Manager and another notification pops up, 'Unfortunately, ROM Manager has stopped.'
So right now, I have a phone that has no system setting, no keyboard and I can't access ROM Manager.
Phone Model : LG OPTIMUS BLACK P970
ROM : CyanogenMod 10
Carrier : Starhub
Click to expand...
Click to collapse
Use recovery. (Not ROM Manager the actual Recovery.)
Sent from my LG-P970
use smart flash tool again to flash patched firmware
do full 3 wipes
I can't boot into recovery and I don't have smart flash installed.
search for smartflashtool in the p970 forum
install a stock rom with ot and cwm recovery
DON'T USE ROM MANAGER WITH OUR PHONE damn people...read...don't just take any advice on youtube
How do you want me to install it? Sorry but I'm a bit confused.
HEY!A FELLOW SINGAPOREAN!Anyways best is to dwnload the bin and fls stock rom files and use smartflashtool to flash it.I recommend v20o or v20s firmware(though there's not much difference).But your FC problem should not happen if you do all wipes b4 flashing:Wipe Data/factory reset,Wipe cache,Wipe Dalvik Cache.
Sent from my LG-P970 using xda app-developers app
Related
My SGS was confiscated at school about 2 months ago by the school adminstration because bringing phones to schools wasn't allowed. I had removed the battery and SIM when it was confiscated. By then it was running on Onecosmic's ICS 4.0.3 RC3.1 ROM. It was working perfectly with a custom boot animation. Today I got my SGS back and it wont fully boot. When I turn it on I can see the Galaxy S GT-I9000 text plus the 'WITH OUR POWERS COMBINED WE ARE...PLATYPUS KERNEL' logo but it stays black after this. The menu and back button light up on touch but there is no response or activity on the screen. I have tried almost everything from
wiping every data to re-rooting it, blah...blah. I installed 2.3.5 and it works, 2.3.6 ValuePack works too and even CM7 works fine. But it won't accept ICS. Any idea why, please help?
PS: I can enter both recovery mode and download mode.
Fully wipe, install stock firmwares in Odin and did all step to install custom ICS rom.
yup did all that. Flashed stock 2.3.5 first, then flashed 2.3.6 valuepack, then rooted it, after that installed cm7. Everything is perfect upto this. After that wiped all data plus cache, and tried installing ics onecosmics 4.0.3 rc3.1, after reboot phone stays blank after the logos. The menu and back buttons light up on touch, but no vibration no action and no response.
I did the same with success but from 2.3.6 directly and with that :
1. Boot into Clockwork Mod Recovery Mode using volume buttons.
2. (optional) Backup your current ROM.
3. Select "install zip from sdcard".
4. Select "choose zip from sdcard".
5. Select the .zip that you downloaded and confirm it.
*(optional) Flash newer kernel if you want to.
6. Reboot the phone.
7. Wait for phone to boot (this may take up to ten minutes)
tried it from 2.3.6 just now, still no luck. Phone just stays blank...
Why not move to rc4.2. Also have you tried flashing twice. One after the other. Not sure why but this sometimes helps.
Also in recovery advanced menu have you cleared dalvik cache, cleared init'd and ns tools settings?
Sent from my GT-P7500 using xda premium
scubadude said:
Why not move to rc4.2. Also have you tried flashing twice. One after the other. Not sure why but this sometimes helps.
Also in recovery advanced menu have you cleared dalvik cache, cleared init'd and ns tools settings?
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
Read the bold. I've seen this in a handful of tutorials on how to flash to ICS. After you've flashed to ICS and you're stuck in a bootloop, simply go into CWM (Recovery) and reflash it. This should fix your problem.
Good luck!
thanks ya all, finally managed it n it works now. I just installed another ics rom (i dont exactly know what it is, its got a boot screen of android rocketing with the galaxy logo) and installed onecosmic's rc3.1 again n it works now.
tamrat_a said:
thanks ya all, finally managed it n it works now. I just installed another ics rom (i dont exactly know what it is, its got a boot screen of android rocketing with the galaxy logo) and installed onecosmic's rc3.1 again n it works now.
Click to expand...
Click to collapse
When you get a bootloop flashing to ICS, simply flash again—as in, flash twice in a row. This is effectively what you did by trying another ROM, as they both have the same base. Keep that in mind for the future.
Have fun!
Hi everyone,
I recently purchased a P970 through the Koodo network. I used smartflash, rom converter 2.0, etc. to root the phone.
I booted my phone, superuser was installed. Everything works well, however, if I go to Google Play store to install any app, the phone freezes and I have to take the battery out to get it started again or the phone will just reboot as soon as it tries to install it. I tried downloading the apk and uploading it to the phone and installing it with superuser but it does the same thing.
I reinstalled everything twice now and it still does the same thing. I've read around the website but can't find any answer. Can anyone help please?
Try to flash another rom.
The phone came with V20j. There's a Telus rom that's V20i. It's ok to try that one?
darrenp76 said:
The phone came with V20j. There's a Telus rom that's V20i. It's ok to try that one?
Click to expand...
Click to collapse
I meen that you can try to flash a custom rom like zeus.
I can't download rom manager or anything like that without it rebooting.
I followed these instructions found on this site:
1. Get original Koodo firmware
2. Extract BIN/FLS with LGExtract.exe
3. Patch in CWM image with Linux DD (I used p970 rom converter 2.0 to do the extract and CWM image)
4. Flash with SmartFlashTool
The only apps that came with the superuser was anreboot and es file explorer
Can I just flash a rom like zeus with the rom conerter 2.0?
You have CWM,right? If not, try cwm flasher by redy in Development sector
When the phone is restarting at LG logo, press Volume Down to Recovery.
If u not have e/g-recovery, power off and try to press Power button and Volume down in the same time
And u can wipe all data or flash any custom rom
Already U know about CWM and injecting root
So, just download Gingerbread V20S Rooted .bin and .fls files from google
And flash with Smart Flash tool
Or else, U can try Zeus (excellent ROM) with (if u have to install Zeus, U should have some ROM installed with root and ROM manager)
If now ur phone has root option, just install ROM manager (download separately ROM manager and install)
Even if yours is not rooted, basic features of ROM manager will work for Reboot into Recovery, so that you can flash the zip file of Zeus ROM (try to install latest is 6.39n and its update file)
If unable to install just Factory Reset, even that is not working..
Try to open the settings of Play Google and clear all the cache or history u can find and restart the phone..
Try the Zeus ROM, amazing ROM and No. 1 now..
Press THANKS if I helped you
Hi there,
darrenp76, I too had just rooted my own LG P970 (my carrier is also Koodo). I used a different method to root my phone, but the result was a success.
I found myself in the same situation as you; every time I tried to download an app, the download would complete but then the phone would hang on when the installation portion began. The phone would power off, and boot back up.
I have solved this issue by doing the following:
1) Go to Settings
2) Go to Privacy
3) Select "Factor data reset"
4) Reset phone. I did NOT check off "Erase SD card"
My phone restarted, I saw the ClockWorkMod screen, then my phone continued to restart normally.
I was then prompted with LG's little tutorial, and I entered my gmail information when prompted.
I was then able to access the Market - which updated to the Play store. I was able to keep Superuser on my phone, but I lost the 2 applications that were automatically installed when I rooted my phone (one was a file browser and the other was some sort of restart.) I did not have these programs installed for very long because I reset my phone shortly after rooting, and so I wasn't able to familiarize myself with those 2 apps, and I don't remember the names of them.
Anyways, I really hope that this helps you. Having been through the situation myself, I was very worried, but the factory reset seems to have fixed this issue.
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
adobih said:
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
Click to expand...
Click to collapse
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Samtan4326 said:
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Click to expand...
Click to collapse
First off all thanks for helping.
I tried this one:
CF-ROOT-4.4-I9000BGJW5-1187857
CF-Root-4.4-I9000BOJW6-CL1177078
CF-Root-JP6-v1.2-Busybox-1.17.1 (this one didn't want to start recovery at all)
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
all I got from all of them is this
imageshack.us/f/805/08032008449.jpg (copy link to address bar )
Member Chainfire said "THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device"
I don't know really what that means. Probably that I have to install something else too, but what ?
Please can you tell me ?
And which of these CF-Roots is the right one, or the newest one, or how do recognize that ?
Thanks everyone who helps me.
eba
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After it's done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
adobih said:
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After is done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
Click to expand...
Click to collapse
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
beckzz said:
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
Click to expand...
Click to collapse
Well, I help you as much as I can and know, just write me where you stuck. And if you have some difficulties explaining it in English, dann kannst du mir auch auf deutsch schreiben, das verstehe ich auch
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & -->release buttons the moment u see bootanimation<--) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough). If not getting into recovery with waiting the first time just try to keep getting in recovery with 3 button combo & wait a couple of minutes. Eventually it does. I had the same thing 2 months ago coming from jb-->ics-->cm10, thats how I remembered.
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen. Didnt wipe nothing in between the flashing
Then flashed gapps & voila
Donovan662 said:
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & release buttons the moment u see bootanimation) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough)
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen
Then flashed gapps & voila
Click to expand...
Click to collapse
I tried like hundred times or more, but every time with the same result and I also tried with different kernels without success. Maybe some other error caused your status 7 error than mine. But anyway, it's always good to try all possibilities to resolve the problem.
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Donovan662 said:
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Click to expand...
Click to collapse
Unfortunately I wasn't that lucky, but I tell you something else. Now I know that no matter what I do and how badly i brick my phone I can always use that method to bring it to life back. So it's kind of final help that works if nothing else works
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Donovan662 said:
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Click to expand...
Click to collapse
I choose zip from sd card because I forgot to rename the file before copying to sd card, and when I lost my bricked my phone it was already to late to rename it. But i don't think that that was the problem, I mean it's just a name string that has no meaning after all.
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
beckzz said:
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
Click to expand...
Click to collapse
More or less I think we both had the same problem, because I also used this link wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide and heimdall 1.3.2 for flashing my phone. Just it always finished successfully so I didn't realize it was the root of all problems. I used also then Odin from the youtube video that I posted in a few posts earlier, installed Android 2.3.6 and then installed ROM Manager from Google play, and used the app to flash to ClockworkMod Recovery. After that I installed directly CM10 stable with success, and without CM9 detour.
Hello, i have my Lg optimus 2x P990H for a year now. i was running CM 7.2 stable version last night and I decided to ParanoidAndroid CM10
link below
http://forum.xda-developers.com/showthread.php?t=2097807
I downloaded the last ParanoidAndroid CM10 ROM with the new boot-loader, i used Lite by KonstaT, the latest one. i used the latest kowalski kernel.
now the phone would start,load but i got a message saying "Unfortunately, the process com.google.process.gapps has stopped" message. i clicked okay and i got "Unfortunately, the process com.google.process.gapps has stopped". i cannot do nothing after that. i tried remove the battery, hold down power and volume down button but it seems recovery mode do not exist. i don't know what else to do. I can't understand those Nvflash instructions not those'how to flash stock rom" instructions. Im using Windows 7 64bit.
anyone knows how i can get my phone back to work
1st - why 2 same threads?
2nd - cm7.2 is on old bootloader so you better download & flash pa10 for old bl if you didn't change bootloaders prior flashing the new rom...
3rd - already mentioned "all-in-one tool" if everything above fails...
Yhe only prob is u flashed the wrong gapps
If ur flashin cm10 then install cm10 gapps and of ur flashong cm10.1 use cm 10.1 gapps
This will definately solve your prob
U can find the gapps easily in the forum but choose the correct 1 or else it will show the error again
Good luck
Sent from P990 the beast phone ^_^
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
AllUsernamesAlreadyInUse said:
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
Click to expand...
Click to collapse
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable from here : http://get.cm/?device=galaxysmtd&type=stable
then install any costum rom you want
The Tox said:
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable
then install any costum rom you want
Click to expand...
Click to collapse
Thanks for your reply. Installing CM 9 worked but trying to install CM 10 throws up this error:
assert failed: run_program("tmp/updater.sh") == 0
E: Error in sdcard/cm-10.1.zip
(Status 7)
Installation aborted.
Flash this one :
http://get.cm/get/3Fb
then install this one :
http://get.cm/get/9aJ
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
AllUsernamesAlreadyInUse said:
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
Click to expand...
Click to collapse
did you tried to install other costum roms , like slimbean ?
There MIGHT be a problem with your internal SD card. Slight chance :/
did you tried to install other costum roms , like slimbean ?
Click to expand...
Click to collapse
Yes I did and only Franzys installed successfully but then stopped working after phone reboot.
There MIGHT be a problem with your internal SD card. Slight chance :/
Click to expand...
Click to collapse
I think that might be the case. I get encryption unsuccessful with my sdcard in and CWM doesn't see any files with sdcard out.
I found an article here on forum that explains how to use your external sdcard as the internal one. Will give it a try and see if it works.
For now I don't mind using CM 9.1.
Thanks for your help guys and let me know if you have any other suggestions.