Huh. Just noticed the international version of the Optimus G is now officially supported by CM (via nightly builds):
get.cm/?device=e975
Does this mean we may be seeing the unofficial E971/E973 moving more toward the official side?
Edit: typos and grammar.
Sent through the magic of an LG Optimus G (E971) running RootBox 4.2.2.
Ive already tried the nigtly build, unlike the chad's version, official one doesnt work lol
To be honest it works, but screen showing nothing.
Is the CM team and chad working together? Or are these 2 completely different builds?
Tim4 said:
Ive already tried the nigtly build, unlike the chad's version, official one doesnt work lol
To be honest it works, but screen showing nothing.
Click to expand...
Click to collapse
What do you mean by that?
Gesendet von meinem GT-I9000 mit Tapatalk 2
haasgo said:
What do you mean by that?
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
chad's version:
http://forum.xda-developers.com/showthread.php?t=2229806
It's very stable and nearly completely full-featured apart from phone, notification LED and some modem issues. I'm running it as my daily driver.
As for what Tim is saying, I'm assuming he wants to say that the official version is less complete than chad's version...
I mean on the nightly one, all i can see is nothing but just black screen.
I just found that tread on Google because I was looking for a working CWM for the E975. Does anybody has experience with that CWM?
http://donandroid.com/how-to-install-cm-10-1-on-lg-optimus-g-e975-1016
Edit: It works .
How's the battery life compared to stock rom?
i do not flash this rom dated April 14 by TWRP, why that?
Folowing Ricardo's post on Google + announcing the official CM10.1 for E975, I said give it a try.
I had installed the ClockworkMod from the Play Store (the premium version), I flashed the CWM touch recovery for E975 (in app payment), booted in recovery and installed the official CM10.1 zip.
Rebooted and... bootloop!
The Cyanogenmod logo was spinning but it would not start.
So I got my first softbrick with E975.
I had to reflash the official kzd, reroot, unlock bootloader.
For now I will stay with the official 4.1.2 stock ROM.
I hope that CM10.1 will work with the TWRP and then I'll give it a try.
Just use FreeGee to unlock, reboot and flash. Works everytime
Sent from my LG-E975 w. CM10.1 using xda premium
goodmamba said:
Folowing Ricardo's post on Google + announcing the official CM10.1 for E975, I said give it a try.
I had installed the ClockworkMod from the Play Store (the premium version), I flashed the CWM touch recovery for E975 (in app payment), booted in recovery and installed the official CM10.1 zip.
Rebooted and... bootloop!
The Cyanogenmod logo was spinning but it would not start.
So I got my first softbrick with E975.
I had to reflash the official kzd, reroot, unlock bootloader.
For now I will stay with the official 4.1.2 stock ROM.
I hope that CM10.1 will work with the TWRP and then I'll give it a try.
Click to expand...
Click to collapse
Did you do a factory reset from recovery? This step is very important otherwise you end with a bootloop. So you just had to reboot in recovery and wipe data or do factory reset and reboot.
The ROM is working 100%. Fully working 13 megapixel camera and very smooth.
The easiest way is:
Use FreeGee from Play Store and free your device (void your warranty)
Download RomManger from Play store and flash CWM recovery. Not TWRP !!!
Put the ROM on your Internal storage Download here: http://get.cm/?device=e975
Put Gapps for jb 4.2.2 (20120301) on internal storage Download here: http://goo.im/gapps
Reboot to recovery (Keep Volume up while rebooting and press the Volume down rocker two times and press Power button)
Select option “install zip from sdcard”
Then select “choose zip from sdcard”
Flash CM10.1 rom.
Flash Gapps package.
Go back to main screen in recovery
Important step !!! - Select FACTORY RESET in Recovery and press Power button - !!!
Reboot into system
Enjoy CM 10.1 on your LG OG E975
goodmamba said:
Folowing Ricardo's post on Google + announcing the official CM10.1 for E975, I said give it a try.
I had installed the ClockworkMod from the Play Store (the premium version), I flashed the CWM touch recovery for E975 (in app payment), booted in recovery and installed the official CM10.1 zip.
Rebooted and... bootloop!
The Cyanogenmod logo was spinning but it would not start.
So I got my first softbrick with E975.
I had to reflash the official kzd, reroot, unlock bootloader.
For now I will stay with the official 4.1.2 stock ROM.
I hope that CM10.1 will work with the TWRP and then I'll give it a try.
Click to expand...
Click to collapse
there shouldn't be a reason why CM10.1 from Ricardo won't work with TWRP, u should flash it, and gapps then reboot ur phone, ofc clear cache, dalvik cache and that
puma99dk| said:
there shouldn't be a reason why CM10.1 from Ricardo won't work with TWRP, u should flash it, and gapps then reboot ur phone, ofc clear cache, dalvik cache and that
Click to expand...
Click to collapse
I tried myself and it didn't work with TWRP. Wrong device id E975...
Best to read his Google+ Blog. So I found out myself.
After flashing CWM the ROM flashed fine. The ROM works fine. And I have 13 megapixel camera with focus.
Just delete the phone checking from update script
Are there any issues if you dirty flash from an unofficial 10.1 build to the official 10.1 nightly?
Yeah, it stucks at boot logo. For me at least.
Never dirth flash from another rom.
Thats a NO GO
Sent from your moms bed!
There is no reason for dirty flash anyway as you get all settings back from Google right after install? And if you make backups of your data omce in a while you loose nothing.
You should know, that old settings can screw with a new flash aswell. Then you will need to clear the old data from some apps ( like youtube ).
Thats why a total clean flash without saved data ( from google ) is the best
Then its also easier for a dev to find the right bugs, if there are some
Related
Hello Folks
I have a problem booting my GNex when particularity I flash gapp (20120726). Right now, it has BlackBean Rom that includes gapp. A few days ago I tried flash XenonHD, when I did it, boot everythings is ok, but when I flashed the Gapps, GNex presents GoogleLogo and reboot again, going to Recovery. I made a Full Wipe, Dalki, etc... nothing. it stays trying to reboot and going to Recovery
The same thing happens when yerstady I tried to flash AOKP.
Thank you.
I run into really weird problems if I don't flash the ROM and gapps at the same time, depending on the ROM, anything from boot loops to misbehaving apps. Try and start from scratch: make a titanium backup, wipe everything, then install ROM+gapps. If that doesn't work, it's probably your version of gapps. Maybe a bad download or just a bad package entirely.
Sent from my Galaxy Nexus using xda app-developers app
I did it, same result. It´s weird. I just can flash Roms with Gapps included. I downloaded several times the gapp zip.
Could be kernel? Maybe, I dont know.
On ICS´s times I could flash every rom I want (even MIUI), but on JB no.
What exactly are you doing? Give me a step by step from the beginning.
Sent from my Galaxy Nexus using xda app-developers app
Echo5ive said:
What exactly are you doing? Give me a step by step from the beginning.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Firstly, thank you for you time
Step GNex Maguro
1) FullWipe
2) Wipe cache, Dalvik, etc
3) Flash ROM (XenoxHD or AOKP) JB
4) Flash gapps (ver. 20120726), downloaded from goo.im
5) reboot system
then...
...
Appear GoogleScreen
...(10 secs)
reboot
...
Appear GoogleScreen (again)
...10 secs
(PUFF) Go to Recovery.
...
I reboot again and it keep going back to recovery
But, when I flash a ROM that includes gapp inside (ie Black Bean aokp), everything is ok. Boot normaly.
http://forum.xda-developers.com/showthread.php?t=1778555
Looks like it might just be an issue with your phone. A hand full of other people are experiencing similar things with jb.
There should be a super wipe utility that you can flash before you flash the ROM. You'll have to search for it tho. I'll look for it when I have a second but that's about the best I can do for you right now.
Sent from my Galaxy Nexus using xda app-developers app
Ooh my... Thank you
http://forum.xda-developers.com/showthread.php?t=1361348
Here's the original.. the link is at the bottom of the OP. The direct download is http://goo.gl/Lerzy
I haven't tried it but all it does is format everything except your sdcard... It's technically made for the GSM version but if you have the CDMA, it should do the exact same thing. The same usual disclaimer applies...
If that does not work, I would try and find another GB ROM and take the gapps from that. Try out a few other ones to see if it works. If you install over clean (as mentioned before) it seems to be more stable.
Thank you
Now I can notice that when I flash Rom based CM/AOSP I can flash gapps normally, but AOKP not. Hmm.. it´s wierd.
I dont know what I did, but now I cant flash AOKP Rom, noone, even I can´t restore my backup from CMW... I get /system problem...
Well, for a while I will stay on a ROM based CM/AOSP til I get or find the cause.
Thank everyone.
Hello! I have managed to root my phone, but I got the set up wizard message and the gapps error. After a google search it told me I had the wrong version of gapps. However, when I go to the official gapps page, the download for cm 10.1 only works with 4.2.2 and not 4.1.2. The one for cm 10.0 is for 4.1.2, but on the hercules downloads page, the 10.1 stable release is already out (that's the one I used!). Does this mean I have to run 10.1 without gapps, or downgrade to 10.0 if I want gapps?
Trust me, I have searched for this. Any help would be appreciated.
if you are on 10.1 grab the first one on the page http://goo.im/gapps also double check make sure you have no market installed if you do then you dont need any gapps install everything from the market
Alright
Ok, I'm gonna try that. +1 thanks for you. Man, I'm such a noob. :crying: :crying:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Roulette
krazierokz said:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
It's circling now...it's been at it for about 5 minutes now...the wait is unbearable!
Circling
It appears to have no end to the blue circling boot screen. I tried clearing cache and factory reset using CWM, no cigar still. Any fixes for this?
The CM version is the 10.1 stable release for hercules.
The gapps version is the 20130301 version.
which link did you flash for the CM what thread point in the right direction where you flashed from ? if you booted up the first flash and gapps were incorrect it shouldnt matter when you update the gapps it wipes the old files just make sure to wipe dalvik/cache and reboot
My Idiocy
I am retarded. I decided to go and unroot the phone and flash a stock rom and try again. I then flashed twrp via odin (which I prefer now) with no problems. But for some reason, no matter how many times I clear everything and try different kernels, the device will just not root. I have tried the superuser zips from the official site, I have tried the superuser from CWM's site, nothing works. Gah. Now what? Am I stuck stock forever?
Babbalabba said:
? Am I stuck stock forever?
Click to expand...
Click to collapse
Just use TWRP to flash whatever (Hercules) ROM you want. Make sure you wipe dalvik, cache, system and data.
Alright, I will try a wipe again, and then flash a custom ROM. If it doesn't root me I will report back with the situation. Thank you for all your help!
Um, just another question before I proceed with wipe and rom...if the ROM is based off of JB 4.2.2, such as Cyanogen mod, will my phone just run 4.2.2 as part of the rom, or will it be incompatible?
EDIT: Never mind...
I love you all forever. It works, and I have gapps running and root access. Thank you so much...I really don't know what to say.
I'm with Bell using the E973. Tried installing every 4.2.2 rom here and the same thing happens each time. Black screen after I reboot phone. Is there some sort of procedure aside from wiping data/reset/cache/davlik/system?
Btw, I'm rooted and unlocked. On 4.1.2 right now.
nagameno said:
I'm with Bell using the E973. Tried installing every 4.2.2 rom here and the same thing happens each time. Black screen after I reboot phone. Is there some sort of procedure aside from wiping data/reset/cache/davlik/system?
Btw, I'm rooted and unlocked. On 4.1.2 right now.
Click to expand...
Click to collapse
Which recovery?
Sent from my CM10.2 OGE973
Clockwork 6.0 something.
nagameno said:
Clockwork 6.0 something.
Click to expand...
Click to collapse
So you're
1.rooted
2.unlocked (with FreeGee??)
3.install recovery
4.download custom rom for E973 not E975
5.reboot into recovery
6.***make nandroid backup***
7.after backup, wipe cache-dalvik-data-system (DO NOT WIPE SDCARD)
8.factory/reset
9.flash downloaded custom rom
10.flash Gapps for correct Android version
And you're done.
Give us feedback :good:
Sent from my CM10.2 OGE973
JasonBourne.Qc said:
So you're
1.rooted
2.unlocked (with FreeGee??)
3.install recovery
4.download custom rom for E973 not E975
5.reboot into recovery
6.***make nandroid backup***
7.after backup, wipe cache-dalvik-data-system (DO NOT WIPE SDCARD)
8.factory/reset
9.flash downloaded custom rom
10.flash Gapps for correct Android version
And you're done.
Give us feedback :good:
Sent from my CM10.2 OGE973
Click to expand...
Click to collapse
I don't think I unlocked it with freegee. This was a while ago when I unlocked it. I download the E973 roms ONLY. Those instructions I have been following for all the 4.2.2 roms. None of them seem to want to boot after I restart from recovery. Only way I get back to working phone is if I reinstall the 4.1.2 rom I have backed up on my sd.
nagameno said:
I don't think I unlocked it with freegee. This was a while ago when I unlocked it. I download the E973 roms ONLY. Those instructions I have been following for all the 4.2.2 roms. None of them seem to want to boot after I restart from recovery. Only way I get back to working phone is if I reinstall the 4.1.2 rom I have backed up on my sd.
Click to expand...
Click to collapse
you must unlock with freegee before you can do anything. I was like you, until i actually read all the posts one by one and kept trying.
good luck!
Dear Community,
this is my first post on XDA-devloppers.
I ask you for help as y have a serious promlem with CM 9.1 on my xperia arc.
I flashed CM on my phone using the latest stable rom downloaded from the official cyanogenmod website (cm-9.1.0-anzu.zip)
Everything worked perfectly and i was delightet.
Unfortunately, after two days my phone crashed.
By crashed i mean that it first reacted very slow then froze. After this, the screen went black (backlight on) an then dark.
no button could get me back to lockscreen.
then suddenly the phone rebootet.
this happened every time about one minute after booting my phone.
As the problem didn't seem to get away i decided to reflash it:
wipe SD
delete davlik cache
reseting to factory
and then istalling the same rom and gapps from zip
everything worked fine again, but after one day i got the same problem again.
what can I do to fix this?
I would appreciate any kind of help
and excuse me if this isn't the right forum (search also, didn't help)
sincerly,
PraetorAce
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
popthosegaskets said:
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
Click to expand...
Click to collapse
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
PraetorAce said:
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
Click to expand...
Click to collapse
You can try the nightly versions if the stable doesn't work for you.
Take out the boot.img inside the ROM zip and flash with fastboot. Then put ROM zip onto SD card and flash with CWM.
僕のLT18iから送られてきた
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
PraetorAce said:
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
Click to expand...
Click to collapse
Odin is for Samsung devices only. If CM9.1 doesn't work for you then you might want to try CM10.
僕のLT18iから送られてきた
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
paped said:
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
Click to expand...
Click to collapse
Well, i'm on I9300 and all i can tell you is that i have the same exact problem with the same release, so you're not alone.
I was hoping this new release would work since the one of the 20 may didn't, but this one won't even boot.
I guess I9300 doesn't get love anymore...
You are not alone in this. It is happening with me too since the stable build of 28th May. I tried the on on June 12th too ...but even that is failing as well
How come it is a stable build when it has a bug like this and crashes the phone? Are we making a mistake? Does it require a different kernel or what can I do to make it work?!
~ Manthravadi
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
paped said:
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
Click to expand...
Click to collapse
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
I also have problem but thankfully when I did the steps above, it did finally boot but now I have another problem. My S3 boots properly and I can use it for a while then after a few mins it suddenly reboots with boot animation and all and I dunno what to do. It just keeps rebooting after a certain amount of mins.
@Aledresin: glad that I was able to help you. I am not experiencing any such issues at the moment. When the next PA build is released, try to flash it with boeffla 4 alpha 6.
Afaik ..some memory issues were fixed in alpha 6 and as you are using alpha 3..perhaps you are experiencing those issues.
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Manthravadi said:
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Do you happen to have a copy/mirror of "boeffla-kernel-4.0-alpha3-CM12.1-NG-i9300.recovery.zip"
I've been searching for a few days and can't find it anywhere. The official boeffla site no longer hosts this file and a lot of i9300 users need it to run the latest Paranoid OTA.
EDIT: Found it! It's available here: http://boeffla.df-kunde.de/sgs3/boef...load/Test/old/
Thanks to user Hawaiihemd for the info.
paped said:
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
Click to expand...
Click to collapse
I had a very similar problem and found that if I let it automatically reboot after flashing, then I was stuck just rebooting to recovery. If I manually shut down after flashing and manually booted, then everything worked fine. You may have the same thing happening here. I also used PhilzTouch and like it a lot. Thanks to the devs!