Related
I am trying to install the G Harmony ROM with BL 1.2[http://forum.xda-developers.com/showthread.php?t=1007455]. The install of the ROM itself is very smooth. After flashing the ROM, I tried to flash the G-apps using the file provided in the OP. The install went on smoothly. On reboot, however, I don't see any Google apps in the system anywhere. Indeed, even Titanium Backup, which was working well before I flashed the G apps, tells me I am not rooted. I tried wiping data,cache,dalvik and fixing permissions, but same result every time. I even tried flashing the CM7 G-apps, but same results. Any ideas, anyone ?
I am in the identical situation with BL1.1 or 1.2. about to try Cyanogen just to see if it's my tablet or not.
Just tried the latest cyanogen mod 7.0.3 and latest gapps. No Gapps or market from that ROM either. Dunno what we are doing wrong. Do we have to wipe our Internal SD's? I used gapps-gb-20110613-signed from cyanogen...and still no apps/market.
I also just tried wiping my SD card (internal), and formatting system. Had to nvflash back to stock. Atttempted G-harmony again. Same results. No apps will install from GoogleApps-GRJ22. It's really strange, the install appears to go fine from clockwork, then there is just nothing there.
Here is what I did to get gapps.
install rom, run it once.
innstall gapps, run it, and the screen will ask for gmail account and password
after failing to connect, its going to ask if you wanna connect by wfi..
done deal.
hungrymr2 said:
Here is what I did to get gapps.
install rom, run it once.
innstall gapps, run it, and the screen will ask for gmail account and password
after failing to connect, its going to ask if you wanna connect by wfi..
done deal.
Click to expand...
Click to collapse
@hungrymr2 - that is what is not happening. After flashing the ROM, I am flashing the G-apps. I would normally expect to see the google set up screen on reboot, but there is nothing - no set up screen, no G-apps.
Interesting, i think it happened to me before. I had to reinstall the rom or a different one.
hungrymr2 said:
Interesting, i think it happened to me before. I had to reinstall the rom or a different one.
Click to expand...
Click to collapse
Went back to CM7 for now.
Looks like the matter has come to the attention of the dev. Hopefully there will be a resolution soon.
Make sure you clear dalvik code and cache. Might be a good idea to format the internal sd as well. Just good practice to clear everything each time you install a new rom.
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.
Hi, I just recently came back to this forum, pleased to find that we now have CM10 working on Amaze ! (Thank you sportsstar!)
However I did have a couple issues when installing, and seeing as how a lot of people in the CM10 thread asked to redirect questions here, I figured I make a thread.
My problem is that it seems as though no matter what I install, there is always a problem. As far as I know, I am using the basic ICS-Ruby kernel that was dumped 6+ months ago. I installed the CM10 rom using 4EXT, with no issues.
However when I installed the Gapps (gapps-jb-20130301-signed) I constantly had the Android keyboard force close on me. So instead I tried to install the JB-4.2-Gapps-signed. With these, the Android keyboard would not force close but the Google Now search app would force close everytime.
I've also tried installing the DARK GLASS 0.6 ROM by jose, but then the wifi would not turn on. (When I would try to turn it on, it would just hang saying "Turning on Wifi").
It is probably worth mentioning that I did do a full wipe everytime I installed the CM10 rom. I was sure to be very thorough. When I installed DARK GLASS 0.6 ROM, again, I did a full format of partiitions, and a wipe. Still the issues above arise.
Can someone maybe help me out as to what I'm doing wrong? Thanks!
------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: I just looked at my phone info, and apparently the kernel I'm using is 3.0.53-gd28c6eb. Is this okay or do I need to flash a new kernel ?
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.
Hi,
I was running a cm 13 ROM on my Galaxy S 3 i9300. With Google Play. But after installing several ROMs it's gone. I have the same ROM but when I now install it it comes without Gapps. How come? Is there a way to switch them off/on somewhere so they won't get installed?
How to get it back? I have tried to intsall Google Play separately but none seam to work. Google services just keeps crashing.
tokintmash said:
Hi,
I was running a cm 13 ROM on my Galaxy S 3 i9300. With Google Play. But after installing several ROMs it's gone. I have the same ROM but when I now install it it comes without Gapps. How come? Is there a way to switch them off/on somewhere so they won't get installed?
How to get it back? I have tried to intsall Google Play separately but none seam to work. Google services just keeps crashing.
Click to expand...
Click to collapse
If it comes without GApps, you can try flashing them... http://opengapps.org/
To check your type of processor, you can try using Droid Info(this one is better I think) or CPU-Z. Since you don't have Play Store, probably APK mirror is a choice.
If this is not what you want, please explain yourself better.
( I am assuming you have a custom recovery to flash OpenGapps, since you tried several ROMs)
I have Clocworkmod recovery (if this answers the question). Since I rooted the phone, I have only tried like 3-4 different CM ROMs. Only one of them came without Google. Others came with Google. But few days ago when I flashed the same ROMs several times I suddenly didn't get Google anymore. How come if it's the same ROM file?
Thanks for the links, I'll check the out later. Gotta run ATM.
tokintmash said:
I have Clocworkmod recovery (if this answers the question). Since I rooted the phone, I have only tried like 3-4 different CM ROMs. Only one of them came without Google. Others came with Google. But few days ago when I flashed the same ROMs several times I suddenly didn't get Google anymore. How come if it's the same ROM file?
Thanks for the links, I'll check the out later. Gotta run ATM.
Click to expand...
Click to collapse
That seems very strange, since its the same file. Did you tried downloading and reflashing the zip again? Something weird could have happened, resulting in a corrupted file.
By the way, I just noticed that CWM 6.0.4.7 and 6.0.4.5 have some problems with the OpenGapps, according to their FAQ(section 5)
DarkAlpha.Sete said:
That seems very strange, since its the same file. Did you tried downloading and reflashing the zip again? Something weird could have happened, resulting in a corrupted file.
By the way, I just noticed that CWM 6.0.4.7 and 6.0.4.5 have some problems with the OpenGapps, according to their FAQ(section 5)
Click to expand...
Click to collapse
Opengapps was what I needed! And it worked. Thanks!
But yeah, I was certainly flashing same ROM files. First few times I got Google and at some point not anymore. I did not download new zip files in the meantime. I don't even remember where I did I get one of them. I have noticed a similar thing some time ago that flashing the same ROM gave me a little different outcome. I don't remember exactly, but I think it was something like although I wiped cache and user data, I still had all my settings in place after flashing.
tokintmash said:
Opengapps was what I needed! And it worked. Thanks!
But yeah, I was certainly flashing same ROM files. First few times I got Google and at some point not anymore. I did not download new zip files in the meantime. I don't even remember where I did I get one of them. I have noticed a similar thing some time ago that flashing the same ROM gave me a little different outcome. I don't remember exactly, but I think it was something like although I wiped cache and user data, I still had all my settings in place after flashing.
Click to expand...
Click to collapse
I'm glad that I helped you!
Also, don't forget to tap that little "Thanks" button