I updated cynaogen to a experimental version, had problems went back to nightly. Then my play store was missing. I attempted to flash gapps and when rebooting the phone. It loads a screen with the droid logo, reading welcome to SCH-1535. Touch the android to begin and when I do it gives me an error unfortunately set wizard has stopped.
I tried to wipe data and reboot. Does not work.
Please please help
you flashed the wrong gapps
Glebun said:
you flashed the wrong gapps
Click to expand...
Click to collapse
WHich gapps do i need?????????
the ones for the android version you're flashing.
One question mark is enough
Glebun said:
the ones for the android version you're flashing.
One question mark is enough
Click to expand...
Click to collapse
Sorry! So i use gapps for Samsung Galaxy s #, or jelly bean (that is what was on the phone before I messed it up) or gapps for cyanogen 10? The phone attempts to load cyanogen then goes to the setup screen.
Would it be an option to flash back to original ROM?
I don't understand the question. CM is jellybean
Glebun said:
I don't understand the question. CM is jellybean
Click to expand...
Click to collapse
Does that mean I have to flash gapps for cyanogen 10?
If you flashed CM10, it's obvious that you need gapps for CM10
Glebun said:
If you flashed CM10, it's obvious that you need gapps for CM10
Click to expand...
Click to collapse
Actually I didn't flash anything. That's how I bought the phone. I don't know anything about flashing, but I really appreciate your help.
what's your point?
if you have CM10, it's obvious that you need gapps for CM10
Related
I'm currently running SHOStock ICS ROM and I want to change it, but every time I try to flash the CM9 ROM in recovery mode, I get an error-
Installation aborted (Status 7). The first time it happened was after I installed the shostock rom (I had the cm9 before and had no problems installing it).
I tried to update CWM through ROM Manager, but it didn't solve the problem.
What can I do to fix it? I searched the forum but didn't find a solution..
Im not sure exactly how to fix that but I've always read that we should avoid Rom Manager on the i777. You might want to sheck the threads about Rom manager errors. I've flashed every rom out there and never used rom manager and never had any problems.
I used rom manager only to update CWM. I haven't installed any rom with rom manager.
last time i found that error with CM9 was because of the build.prop issue. Our phones run i9100 based ROM's alot, there's a line in the updaterscript that looks for phone model, must remove that **** outta there.
And i must say that CM9 sucks if they still have not addressed this well known issue.
Just flash AOKP.
O and, un install ROM manager, its for idiots.
Does this ROM fully support hebrew? (including menus)
yaniv156 said:
Does this ROM fully support hebrew? (including menus)
Click to expand...
Click to collapse
What ROM?
mattdm said:
What ROM?
Click to expand...
Click to collapse
the AOKP
yaniv156 said:
the AOKP
Click to expand...
Click to collapse
Good question. I would say go ask in the AOKP thread, but you don't have enough posts to do that yet...I'll go ask for you. You can just go read the replies to my post.
Problem solved. I flashed AOKP and it worked (no error) ,but after that I flashed CM9 back (more comfortable for me), works perfect. Thanks for the help.
So as I was reading some of the new roms they have tags like RootBox Jelly Bean is a "pure" AOKP/CM. I'm not sure what AOKP/CM is and when i read some of the comments they started talking about the rom being hellraised. Could someone help me understand what they mean by hellraising?
trashcan889 said:
So as I was reading some of the new roms they have tags like RootBox Jelly Bean is a "pure" AOKP/CM. I'm not sure what AOKP/CM is and when i read some of the comments they started talking about the rom being hellraised. Could someone help me understand what they mean by hellraising?
Click to expand...
Click to collapse
Aokp and cm are open source based roms based on vanilla androids with a few tweaks. Hell raise means the rom was originally on the i9100 but was ported to our phones
Sent from my GS4 running CM11 Kandy Kane
does it matter that it was designed for the i9100 vs the i7777? alos I just saw the post here that say DON NOT USE clockwork rom mangers for I7777. If we cant use that application how do we go about installing new roms?
trashcan889 said:
does it matter that it was designed for the i9100 vs the i7777? alos I just saw the post here that say DON NOT USE clockwork rom mangers for I7777. If we cant use that application how do we go about installing new roms?
Click to expand...
Click to collapse
No it doesn't, hellraising makes it 100% compatible. And you do it through recovery. If to don't know that then you have some reading to do.
Sent from my Zanpakuto using Getsuga Tensho!
trashcan889 said:
does it matter that it was designed for the i9100 vs the i7777? alos I just saw the post here that say DON NOT USE clockwork rom mangers for I7777. If we cant use that application how do we go about installing new roms?
Click to expand...
Click to collapse
Our kernels come with recovery built in. So flashing a ROM gives u the recovery.
so I went ahead and flashed to a new rom, pretty diffrent. But I noticed it doesnt seem to have goole play for downloading apps. is that normal?
trashcan889 said:
so I went ahead and flashed to a new rom, pretty diffrent. But I noticed it doesnt seem to have goole play for downloading apps. is that normal?
Click to expand...
Click to collapse
Its normal if u flashed an AOSP based ROM that requires gapps to be flashed afterward.
So when I go to the apps I see an icon for goo. In when I click that there is an option to download gapps. When I download it, it askes if I want to flash. Do I reflash?
nm, IM still pretty new to this. when i tred flashing the one that they had in the goo.im manger i think it was the wrong version since it just keep crashing the apps so I can to the newest version and now it seems to work. this new rom is kinda cool!
THanks for you guys help
im sure ill be back with more questions
im trying to flash beanstalk and when I flash GAPPS ive downloaded I get a FC stating that ASOP keyboard has stopped. I googled it and it appears that I have flashed the wrong GAPPS. can someone point me to the right direction?
thank you
amendolaro1 said:
im trying to flash beanstalk and when I flash GAPPS ive downloaded I get a FC stating that ASOP keyboard has stopped. I googled it and it appears that I have flashed the wrong GAPPS. can someone point me to the right direction?
thank you
Click to expand...
Click to collapse
http://goo.im/gapps
Grab the one that coordinates with your Android version.
mjones73 said:
http://goo.im/gapps
Grab the one that coordinates with your Android version.
Click to expand...
Click to collapse
gapps-jb-20130812-signed.zip should be the right ones... it's the ones I used with Beanstalk and they worked fine, if they still give you trouble try the gapps-jb-20130301-signed.zip version, that would be the one that ROM was originally intended to work with.
Remember if you change Gapps, you should wipe and reinstall, not just flash new ones overtop of the old...
Hi,
Can anybody let me know on how to downgrade my GT-I9100G device from CM11 to CM10.2 ?.
I upgraded to CM11 unofficial build, but then found lots of bugs and so want to revert back to CM10.2
Thanks.
srchandran_72 said:
Hi,
Can anybody let me know on how to downgrade my GT-I9100G device from CM11 to CM10.2 ?.
I upgraded to CM11 unofficial build, but then found lots of bugs and so want to revert back to CM10.2
Thanks.
Click to expand...
Click to collapse
just flash the cm10.2 build if you've root n have installed cwm,
nasheich said:
just flash the cm10.2 build if you've root n have installed cwm,
Click to expand...
Click to collapse
Thanks, doesn't seem like it was so simple. I had tried that many a times before posting this on to the forum. When I try to install CM10.2 again through CWM, it errors out with (Status 7) error. I did a Wipe/Factory Data Reset, Wipe Dalvik Cache and format system. Tried again but the same error re-appeared (status 7).
So I had to reinstall CM11 and GAPPS for CM11 again to make the phone work with some old bugs again . Camera not working, lag in screen rotation, stock browser not working etc.,
Thanks
srchandran_72 said:
Thanks, doesn't seem like it was so simple. I had tried that many a times before posting this on to the forum. When I try to install CM10.2 again through CWM, it errors out with (Status 7) error. I did a Wipe/Factory Data Reset, Wipe Dalvik Cache and format system. Tried again but the same error re-appeared (status 7).
So I had to reinstall CM11 and GAPPS for CM11 again to make the phone work with some old bugs again . Camera not working, lag in screen rotation, stock browser not working etc.,
Thanks
Click to expand...
Click to collapse
status 7 it's cause there's something wrong on the updater script in the Rom build, check the Rom Thread that you've download
nasheich said:
status 7 it's cause there's something wrong on the updater script in the Rom build, check the Rom Thread that you've download
Click to expand...
Click to collapse
Thanks, not sure on what the issue with the Rom could be. I have rooted the device and then installed Blazing Kernel V3 with CWM 6.
Before I decided to upgrade my phone to experimental CM11, I used to apply all CM10.2 Nightlies without any issues.
I have tried to install even CM10.1 stable release through CWM v.6 and the same error comes up.
Further, I have always downloaded ROM's from download.cyanogenmod.org/?device=i9100g or through the CMupdater in the phone.
Can you please let me know, what version of Blazing Kernel should I using on GT-i9100G and how do I flash it safely without fearing of the "Sleep of death" happening.
Thank you.
srchandran_72 said:
Thanks, not sure on what the issue with the Rom could be. I have rooted the device and then installed Blazing Kernel V3 with CWM 6.
Before I decided to upgrade my phone to experimental CM11, I used to apply all CM10.2 Nightlies without any issues.
I have tried to install even CM10.1 stable release through CWM v.6 and the same error comes up.
Further, I have always downloaded ROM's from download.cyanogenmod.org/?device=i9100g or through the CMupdater in the phone.
Can you please let me know, what version of Blazing Kernel should I using on GT-i9100G and how do I flash it safely without fearing of the "Sleep of death" happening.
Thank you.
Click to expand...
Click to collapse
I never use Gallaxy SII, dont know much about it
but, you can learn about your device by going to the SII thread, you'll find out more on there
nasheich said:
I never use Gallaxy SII, dont know much about it
but, you can learn about your device by going to the SII thread, you'll find out more on there
Click to expand...
Click to collapse
Thanks, can you please let me know the link to the GT-i1900G thread and also, on how can "post" a new question in the thread.
srchandran_72 said:
Thanks, can you please let me know the link to the GT-i1900G thread and also, on how can "post" a new question in the thread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s2
that should be the thread for your device
and for posting in a thread(speciallly in the dev thread), you must at least have more than 10 posting in whole xda thread
in general thread, you can post even you didn't have 10+ posting
please read the Rules of Xda for more detail about posting and everything
I Get a notification about the update to version 4.4 BETA 1 of Paranoid Android rom, after downloaded, i flash it via CWM normaly, then flash gapps, but when the phone reboot it stucked at the Galaxy S2 boot logo, and it can boot into recovery, only download mode, but when i open odin to flash CWM but odin can't access the phone and i can't flash, i tried to install usb driver but not success, so what can i do now, please help!
Sorry for my bad English
1) Your English is better than a lot of native English speakers I know.
2) Hopper8's 'Odin troubleshooting' thread stickied in General has all the info you need to get a successful Odin flash. Find the thread, try as many of the troubleshooting steps as many times as you need to in order to get a successful flash.
However, don't try one or two things from the thread, come back here & say 'But I tried some of the stuff in the thread & it didn't work. That thread covers this issue from every possible angle, and it's often persistence that fixes these. There's no easy fix in this situation because we're not there looking over your shoulder seeing what you're doing/not doing, and there's nothing which isn't in the thread that can be suggested in this situation.
So...I've (and Hopper has) given you the tools to get your phone fixed, up to you to fix it now.
@nguyenducanh did you manage to fix this?
I have been speaking with the dev (ayysir) of ParanoidAndroid, 4.4beta1 for S2 had a bug with the kernel. The ROM wouldn't boot at all with the stock kernel, but would with any compatible custom kernel (Dorimanx, Gustavo, Apolo -correct versions of these).
The dev has uploaded a new build now which fixes the problem, so if you've managed to recover your phone the new build is safe to use (tested by me)
Hopper8 said:
@nguyenducanh did you manage to fix this?
I have been speaking with the dev (ayysir) of ParanoidAndroid, 4.4beta1 for S2 had a bug with the kernel. The ROM wouldn't boot at all with the stock kernel, but would with any compatible custom kernel (Dorimanx, Gustavo, Apolo -correct versions of these).
The dev has uploaded a new build now which fixes the problem, so if you've managed to recover your phone the new build is safe to use (tested by me)
Click to expand...
Click to collapse
Ok, tks u, i fixed my phone via odin, and i'm using c-rom v6.6, i will try newest pa now because i'm a big fan of pa
nguyenducanh said:
Ok, tks u, i fixed my phone via odin, and i'm using c-rom v6.6, i will try newest pa now because i'm a big fan of pa
Click to expand...
Click to collapse
Good job, I like to hear that someone recovered their phone using that guide and odin :good: make sure you re-download the ROM, you need the build on 0605, not 0604. 0604 is busted, but 0605 is good
Hopper8 said:
Good job, I like to hear that someone recovered their phone using that guide and odin :good: make sure you re-download the ROM, you need the build on 0605, not 0604. 0604 is busted, but 0605 is good
Click to expand...
Click to collapse
Ok, using 0605 now, and missing see through option
nguyenducanh said:
Ok, using 0605 now, and missing see through option
Click to expand...
Click to collapse
That's because of the new theme engine... I saw something on google+ about that. I think it's planned to be re-implemented but may take a while due to complexity..
Hopper8 said:
That's because of the new theme engine... I saw something on google+ about that. I think it's planned to be re-implemented but may take a while due to complexity..
Click to expand...
Click to collapse
I hope "see through" will come back in the next update