Related
Q&A for [ROM] Official Cyanogenmod 11 4.4.4 for the Moto G 4G (Peregrine)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Notification light not working with cyanogenmod
Hi,
I'm using cyanogenmod (m6 and afterwards the current daily builds) on my moto g and for quite some time I have the problem that my notification light is not working. I tried out installing the motorola led activator widget, but this doesn't help. Even when trying out an LED tester app nothing happens. The LED is not broken though as it lights up when trying to boot my moto g on low battery. Do you have any ideas how to solve this?
Thank you in advance!
Link down
Seems the latest build link is down
not I download the latest build. fallen servers
Does the ROM still have the low ram bug ?
Problem audio speakers CM11 / Stock ROM
How about, first of all, I'm new here and do not speak English, so I excuse my writing.
I have a problem with my Moto G LTE (XT1040) with Stock ROM 4.4.4 KK Brazil, although I am from LatinAmerica.
Well, I have not much to this terminal, but a few days ago I had some problems with the rom Stock, restarting not it caught more, so I decided to flash the latest rom Cyanogenmod (specifically 20,141,012) due to some stability issues decided you go back to the Stock, having the same error when freezing some applications Motorola as usual to, so back to CM and switch to the "20141016" to the few hours I started to fail the camera, remained frozen when taking a photo . After that, it went back to flashing CM rom and had the same errors, updating the "20141018" was the same, but a new bug, and could not hear the music or videos without headphones was added, calls were heard if it was not for speaker, so I decided to go back to the Stock, but apparently the problem was continuing, feel that the speakers are damaged, but the alarms or notification sounds if they worked properly. Now try wipes Cache / Dalvik from CWM but only achieved a temporary solution, put a good song and all, but to change it or put it back the audio is going.
Help me, do not know what else to do, I guess that having unlocked the bootloader and lost my warranty
Thanks in advance if this post is incorrect or I violate any rule, excuse me, I'll delete.
I'm also trying to get GPS to work on my Moto G LTE in cm11:
Based on what I read here, I reflashed stock, and tried it out, had no problems at all. Then restored the cm11 nandroid I had made, and it couldn't see any satellites still. Will restoring the nandroid backup also restore the not-working-gps then? What is being saved by unlocking the gps? Will I have different results from backing up everything with titanium backup, then going back to stock, using gps, reinstalling cm, and restoring the backed up apps? It's much more of a pain to do it that way, but if it works, I'll find the time...
This is a canadian xt1040, btw, in case it makes a difference.
UPDATE: I went ahead and reinstalled stock, played with gps for a while, and it worked without any trouble, then reinstalled CM11 (oct 21 nightly this time) restored my backed up apps with titanium backup (not any system apps). Unfortunately, still no gps at all. It never sees a single satellite. Is there anything else to try?
Hello,
First of all, thank you and all people to contributing and helping developing CM for this device!
I only have one question about GPS bug :
You indicate that it's necessary to have a GPS lock in the stock ROM first to enable GPS in CM.
Does a fix for this bug is intended/possible or the only one solution is to reinstall the stock rom, enable GPS and install CM?
Thanks in advance.
Audio solved
It updated my previous query, I could solve the problem of audio speaker, I began to disassemble the phone and as imagined, I found steel wool at the entrance and were making contact, so the cell believed to have headphones all the time .
Enable GPS in Moto G Nightly
This is in response to jac0708 in the thread this thread who asked:
Mind expanding on these two? What is the low ram bug? And how do you get a lock from stock for the gps fix?
Sorry for noobishness
Click to expand...
Click to collapse
The answer I found for the GPS not working was that when I installed CM11 within hours after taking delivery of my Moto G, the GPS would not get a fix. The solution is explained here by colinw:
Posted 11 October 2014 - 10:42 PM
Okay I just fixed my problem following some other post for a Moto phone.
1) Made a (nandroid) backup using clockwordmod of my current setup (cyanogen 11)
2) Restored old backup of a stock rom (I restored back to the one that came with my phone)
3) Then I had to USE the GPS - hadn't done that yet. Also made sure it was set to Device Only mode in settings->location because someone somewhere suggested it.
4) Restored to cyanogen rom.
5) Working!!
Click to expand...
Click to collapse
Just wanted to add that it doesn't always work. I tried at least three times, restoring stock, using gps, and then restoring my backup before I had gps working in CM. But it does work now! Be patient, and maybe just leave the phone with the stock, sitting on maps for a while. Perhaps I rushed it before?
Hi,
I'm new to ROMs with the Motorola Photon Q, but I have prior experience doing this with other Android devices. I'm also a longtime Linux guy, so "adb" and "adb shell" are both comfortable environments for me.
A few weeks ago my stock JB Photon Q reached a state where it would only reach the yellow "Sprint" screen during the boot process, and hang there. I fiddled a bit with the bootloader, but didn't get very far, and ordered a replacement used Photon Q. Unfortunately my newer phone came with ICS, and I when I attempt the builtin operating system JB update I encounter a message "Unfortunately, Motorola Services has stopped", followed by an indefinite "Checking for available update.* Please wait ..." So I've unlocked both phones, and began fiddling, while using the newer (ICS) one as my active phone for making phone calls, etc.
Fortunately on my older phone (the one that had the yellow screen) I've now been able to install the TWRP 2.7.1.2 Recovery, and I installed the September 26th version of the MoKee KitKat ROM, i.e. MK44.4-moto_msm8960_jbbl-140926-RELEASE.zip. In principle I'd rather use a blessed CyanogenMod version, but am concerned about some of the recent Wifi (and to a lesser extent, Bluetooth) problems that I've read about.
Overall, my primary goals are a stable environment and being able to store Amazon Prime DRM'd files on my SD card, symlink them from the primary storage, and be able to play them using the Amazon Music app. Thanks in advance for your recommendations regarding stable ROMs.
[ on my MoKee KitKat phone, the Amazon app is crashing on most of the DRM'd files that I downloaded from the Amazon Music app, even though I haven't moved them to the SD card or done anything tricky like that ]
My question now is: if I install the same TWRP recovery on my newer phone, will I then be able to install the stock JB image? I've researched to see whether TWRP 2.7 is backwards-compatible with JB ROMs, but haven't found the answer. It would be nice to use the same Recovery when trying out different ROMs, including both JB and KitKat.
Thanks ...
Yes, TWRP should be able to handle any appropriately formed .zip. Regardless of Android version.
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts
(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?
Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.
LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?
Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.
Hi xdadevelopers,
I ordered a Motorola Photon Q 4G LTE (xt897c) phone from FreedomPop for $25 and 28 days later it has arrived. My experience with FreedomPop has been decidedly mixed. Lots of hassle from customer service combined with a product that is sometimes very useful and always cheap. (Unless you use over 2GB of data per month) The phone itself seems very adequate for an excellent price. I would like your assistance in putting Cyanogenmod or another appropriate ROM on it.
Here's where I am,
The phone appears to have been rooted out of the box according to "Root Checker Basic" from Google Play
I installed "Superuser" from Google Play and that seems to work correctly
Busybox seems to be present already according to "Online Nandroid" from Google Play
I have created a TWRP Backup using Online Nandroid without modifying the recovery
The phone currently has Android 4.1.2
Where I want to be
I want to install a custom recovery, preferably one I can make backups from
I want to update to a more recent version of Android such as the stable one found here DUCK RULES cyanogenmod bot org /?device=xt897c or another version where everything just works
Notes. I have ADB and Fastboot installed from "Android Studio". I have an appropriate USB cable. I do not have a microsdhc card right now. It appears "Sandisk 64GB Extreme Micro SD (SDXC) Card + Adapter 60MB/s Class 10 U3 UHS-1" at DUCK RULES amazon bot com /gp/product/B00N98QLRQ is a good choice for a good price. I have this on order and should have it within the week.
I understand this phone has a locked bootloader. The "Messaging" app from FreedomPop available in Google Play seems to control messaging and the phone dialer. I went to the official Motorola Bootloader unlock page DUCK RULES motorola-global-portal bot custhelp bot com /cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-b I booted into recover with Power and volume up and volume down held, selected fastboot, connected to the computer , ran fastboot, as described, got the code, put the code in the webpage as described, and got a blank page. This happened 2x, with no emails form Motorola. I tried a third time 6 hours later, and it loaded a page with more instructions and I had the bootloader unlock code in my email instantly (There were no preceding messages, they didn't go to spam or somewhere else). I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Also thanks to the xdadevelopers community for your past and future efforts. I threw in my lot with Android when the neXus One launched after watching the keynote, buying it full price and paying extra for next day air shipping. I stayed stock despite the cool stuff being done by the development community until Google fell behind in updates. Then I started with CM6 and later went to CM7. That was wonderful software, thanks everyone who was involved in that. Unfortunately way late in the life of my phone I was homeless and got robbed for it. I got a used HTC HD7 Windows Phone for free from a friend. It was great for movies and music with a great screen and touch sensor but it was very early in the life of the new Windows Phone and there wasn't a lot of quality software being developed. That, and it just wasn't Android, and I longed for freedom. The integrated Web browser IE 9 variant sucked, and T-mobile denied me the final Windows Phone 7 update. The phone has gotten less and less useful as time went by though it always sucked for web browsing. This fall I got a One Plus One, it made a wonderful Wifi phablet, but when I tried to use it as a phone I found the radio was severely deficient in range, possibly due to defective manufacture as it got better range in colder weather. I had to initiate a chargeback with my credit card company to get support to talk to me and then ultimately get a refund. That's how I got where I am now and this is the first time I've needed to register for an account here. Thanks again xdadevelopers.
What is the best way to proceed? Semi detailed logical instructions please, as while I am intelligent and not a noob, I have been out of the game since CM7
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Holy wall of text. This seems to be the crux:
Aslan_ said:
I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Click to expand...
Click to collapse
Why would you flash something that is OBVIOUSLY not for your device!? I sincerely hope it did nothing because you could do some permanent damage to your device by flashing stuff that's not made for it.
Did you bother looking for any recovery threads? Say my TWRP thread?
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Flash it per my directions using fastboot in my TWRP thread.
Got it thanks, now which rom?
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post. I like apps, they make me feel like there's less risk in my actions, though after some poking around I see it's probably the opposite. People are doing so much more low level stuff in apps compared to CM7 it's amazing.
arrrghhh said:
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Click to expand...
Click to collapse
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
I'm always hated vague it's broken posts that don't adequately describe the problem, the hardware used and the environment, so I head in the opposite direction with mine.
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Aslan_ said:
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post.
Click to expand...
Click to collapse
I no longer use this as my primary device, so my threads are basically stagnant. fastboot always works, where apps come and go... I'll try to find some time to adjust the post.
Aslan_ said:
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
Click to expand...
Click to collapse
Reason for stopping at 2.7.1.2 was they implemented MTP in 2.8.x, and I could never get it working right for both Win & Lin. I spose my bar was too high and I should've just released it, but I hate releasing half working stuff. It was a new feature that didn't work right.
Again, this is no longer my primary device so I'm not working on it very much at all. I have to pry the thing from my roommate's hands to even play with it, I haven't flashed CM12 yet (because it's no longer my device really).
I'd like to update the official TWRP, but in the meantime the CM maintainer has taken care of updating it so F2FS can be utilized.
Aslan_ said:
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Click to expand...
Click to collapse
Well obviously some of that does go down to choice - if you want CM, it is a little confusing. The device started out in CM10 as its own device, xt897 for GSM xt897c for CDMA. Then in CM11 they merged the devices into moto_msm8960. Of course they had to split again when the new bootloaders were released for the other moto_msm8960's (Razr HD, Atrix HD, etc) and moto_msm8960_jbbl was kind of a stopgap device at the end of CM11. Again, reading is your friend here although I realize all of that history is hard to glean. At least read the OP of the CM thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
Good luck. The device is now semi-unified (GSM & CDMA), as xt897.
Aslan_ said:
[*]I have created a TWRP Backup using Online Nandroid without modifying the recovery
Click to expand...
Click to collapse
Would you mind terribly to share this? My device shipped with a Sprint branded ROM and I'd like a proper backup.
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
turbozapekanka said:
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
Click to expand...
Click to collapse
You don't update PRL/Profile in CM, you do that on the stock ROM. Make sure EVERYTHING works on stock before flashing CM.
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Correct.
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Can you share this "another APN fix"?
already shared here http://forum.xda-developers.com/showpost.php?p=60153295&postcount=18
Anyone still have issues? I was running a June Nightly and it was working somewhat. It would randomly lose connection and I would have to flash the APN.zip. It happened again a few days ago and I decided to go up to 722 Nightly and now I haven't been able to connect. When I go to APNs the list is empty and even if I manually add one it does not seem to stick. The APN zip doesn't help either. The phone is connected but shows an exclamation mark next to the signal and I have no data.
Sort of solved my own problem
Flashed back to stock Spring using RSD lite and a modified XML that didn't flash the system.img since it kept giving me errors. Found a stock TWRP dump on the forums and flashed that. Updated PRL and Profile, reflahsed back to CM11 Snapshot and flashed the 2015 FreedomPOP APN fix. Working for 1 day now.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!