Related
Q&A for [ROMS][SGH-T679]Mass CM Thread
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:
I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?
fajrero said:
I noticed that the kernels are linked separately from the ROMs. Am I supposed to download and flash the kernels separately? I've flashed about half a dozen ROMs, but I've never flashed a kernel before. From what I've read, though, it sounds like following the same procedure. How about GApps? Do I need to download and flash those, too? And, if so, which pack should I use?
Click to expand...
Click to collapse
Roms come with a kernel the kernel linked is just special some have overclock under volt etc etc.
Explains the kernel options.
If you do flash them do it after rom.
Gapps you dont technicly have to but yes. (for a standard setup flash gapps)And there should be a gapps linked at the start of rom. If not there will be soon.
Can't import contacts from SIM
Thanks! That clears up a lot.
I installed CM, and it looks very cool and smooth. But when I tried to import contacts from my SIM card, it said "No contacts". I thought maybe it was because I hadn't installed GApps, so I downloaded the "small" GApps package linked from the CM wiki and installed it from CWM. Still no contacts on the SIM card. Next, I thought that maybe my contacts actually weren't on my SIM for some reason. So, I booted back into CWM recovery and restored my previous system. Then, from the phone app, I went to Import/Export > Manage SIM card contacts. Sure enough, all of my contacts were there.
It seems like CM isn't reading my SIM. Any idea what's causing this?
Edit: Never mind. I found out that newer versions of Android don't allow you to store contacts locally. Somehow, the contacts got silently added without me having to import them, though. That's odd, because I don't remember allowing Google to store them in the cloud, and the SIM card appears blank... Oh, well, I installed MyLocalAccount, so I'll see if I can store the contacts locally that way.
@cars1189 running 10/18 build with 10/19(PAgapps micro) and 9/9k^k UV vhm kernel and have had no issues! Thanks for the great work, this runs solid and smooth!
I recently installed 10.2 and am loving it so far. One thing I ran into though was that the cLock widget was showing lots of wakelocks, so I disabled it and battery life has been great. Haven't run into any other issues (other than the screen staying on when off and charging), so this one is a keeper for me.
Didn't see this problem with 10.1, so curious if this is a known issue or not with the cLock widget? Also, are there any other planned updates coming for 10.2?
Thanks.
@RobbyG2112 I noticed it too when I was on 10.2 how ever I only ran it for a week maybe b4 going to cm11 I will say not sure if cars will update 10.2 but if you haven't tried cm11 its super stable and gets updated monthly!!
Thanks for confirming canodroid15, I wasn't sure what the lock screen would show when I disabled the widget but it put the default digital clock and date in it's place so it works out ok. I had disabled the weather and alarm widgets also so wasn't sure why having only the clock widget would cause wakelocks.
I'll probably get around to installing CM11 next, I'm a little slow on upgrading. I had been using CM10 for a long time and finally got tired of seeing the green preview pictures every time I used the camera so decided to go to CM10.1/10.2 recently.
Sure man, about the wakelocks you can try to catch it in a log. Enjoy 10.2 bro!!
kernel for cm11 (SGH-T679)
I recently installed @cars1189's CM11 10-4-14 build for the SGH-T679, with kernel 3.4.104-cyanogenmod-gda4bf58. It took a few tries, but it finally succeeded.
However, there's a slight issue in that I can't access my SIM card contacts. When I try to import from the dialer, it says "no contacts." I've searched around these threads and on the internet, and it seems that it is an issue with the kernel. Would it be possible for someone to recommend or point me to a compatible kernel that would fix that issue for me? Thank you so much for your help!
@valmeras I really don't think it has anything to do with the stock cm kernel but if your on 10/4/14 you can flash 9/9k^k kernels safely on that build about sim contacts idk I use my Google account to sync my contacts hope this helps good luck!
Edit: look for the rom & kernel dates/links in OP.
@canodroid15 - thanks for the response and suggestion. I'll give that kernel a try in the next few days. Not sure this is the solution, but hopefully that works. I've also seen some reference to SIM Tool Kit (STK), but I wasn't able to figure out if it that was the issue.
I would definitely use Google for syncing the contacts once I get this fixed, but for now, that's not possible because my phone is not able to read the SIM properly. I've tried saving a contact to the SIM, but I get an error like "unable to write, SIM is full" but I know for sure that's not the case. Alternatively, I might try to revive my old dumb phone and try to retrieve the contacts that way, then hopefully export that in some way.
@valmeras no prob man, if you have contacts on your sim and u put the sim in the dumb phone and export to storage u could then send a vcard via Bluetooth to the exhibit go into contacts and import from storage then Google sync good luck let me kno if u get it
So I flashed the kernel, but that didn't fix my issue. I do have some more free RAM now though
My old phone doesn't support exporting multiple contacts/vcards via bluetooth, but fortunately, Motorola has a contact exporter utility that exported everything into a CSV file to my laptop via USB. I had to install the drivers for the old phone to be recognised first. I was skeptical it would work given it was a new all-in-one driver thingie and my Motorola was quite old, but somehow it did! The whole process took several hours, but my contacts are now synced!
Sensors/rotation problem
Thanks for posting these ROMs! I just upgraded from Peach Sunrise and I'm really impressed with how well CM11 runs on this phone.
I want to report a problem I had and my solution for the next guy's benefit. With the latest 12-9-14 CM11 ROM, my sensors and compass didn't work correctly. The biggest symptom was auto-rotation did not work at all. Downgrading to the 9-9-14 ROM fixed everything. I didn't try any other ROMs, so they might work too.
Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942
masteff said:
Question about getting Google apps running on a SGH-T679
I installed CM 10.2 (cm-10.2-20140627-UNOFFICIAL-ancora_tmo) and it worked fine. I tried a couple different gapps downloads (doing a reinstall of CM10.2 between tries although I may have done that step incorrectly). But no matter what 4.3 gapps build I tried, Google Play Services would crash.
My main goal is to get to 4.3 or higher, so CM 10.2 or CM 11 would be great. (I'm open to other ROMs too. The only reason I'm choosing CM is because those are the only ROMs indicated as still maintained here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G )
My question is whether anyone has either CM version running on a T679 and which gapps did you use? I nearly bricked my phone and would like to know that someone else has gapps running okay before I try again.
Thanks!
EDIT: I followed the 2 following threads to install CM 11 with the PA pico gapp package and added a few other Google apps manually from the Play store. I also made sure to reboot several times to make sure everything got fully initialized.
http://forum.xda-developers.com/showthread.php?t=2542793
http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Hey man! I hope you got it figured out! The only Gapps I use are PA Gapps! There are others but PA is the most complete package & has many options "IMO". You need to use a package that will fit your phone I use the micro package, or the nano. You need to use a package that matches your ROMs version, if your on 4.4.x then use 4.4.x Gapps. If on 4.3 use 4.3 Gapps. PA Gapps has a 4.3 package but its hard to find if you don't know where to look. 4.3 package can be found in the devs (Tkruzze) files on android file host, same place as the 4.4.x Gapps! Sorry if you didn't get answered b4 this I haven't been on this thread for weeks it seems! Hope this helps
So I've been trying out the CM11 OS2SD ROM (the last one in December), but I need to switch back as the bugs are just too much. I need my phone to work and stay charged, which is not happening on this ROM. And since it looks like CM12 is being worked on now that it's not likely the bugs in CM11 OS2SD will get fixed any time soon.
So first the problem. My USB socket on the phone is a little iffy, so I know that is where most of the problem is coming in. However, on the CM11 OS2SD ROM I'm using right now (the one dated 12/25) it frequently says it is plugged in, but is not charging. I've actually seen times where the battery monitor I'm using shows it has discharged the battery as much as 20% before I caught it, yet the status bar battery icon shows it as full and plugged in. On the older ROMs it didn't do this, so something isn't right with how the ROM handles the charging circuits in the phone. Plus, I've had frequent periods of "cpu hogging" (massive CPU load that doesn't seem to come from any one source and that doesn't seem to show up in OS Monitor) that can end up in a crash-reboot of the phone.
So as a result, I want to switch back to an older version of the CM11 ROM. I was using one of the November builds for quite a while, only having to put up with an occasional crash-reboot (the current ROM seems to do this at least every other day, the older one could go a whole week and maybe have it happen only once). What is the process to undo what was done to the phone for the OS2SD build to be loaded?
can't install
I have a problem after installing it via cwm and rebooting, the ensender shows me a screen where I order a factory reset but when I was I do not ensiende the phone
CM 12 Android is upgrading every boot
Ever since I flashed Cyanogenmod 12 every time I reboot it says "android is upgrading optimizing app 1 of 1" and it takes about 8 minutes. There are no odex files in data/app so that cant be the problem. Someone please help. The first time I flashed CM 12 I wiped data and factory reseted but since i seen this happen I flashed Cm 12 again but this time I formatted System, Data, Boot, and SDcard 0 but it still seems to happen. Also, recently my phone has been shutting off by itself every time I turn off the screen. And I know this isn't a hardware problem because the phone never turns off while music is playing with the screen off. It didn't start happening with CM 12. It was already happening with CM11 but it only started happening about a week ago. Im really thankful for cars1189 working on the rom and anyone else who worked on it. You guys are great. Hopefully you can help me out.
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Shplad said:
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Click to expand...
Click to collapse
see the index for correct safestrap version, 3.75 is latest, but you need the Droid 4 one
[INDEX] Development Motorola Droid 4
GApps are android version specific, opengapps.org are good
I haven't used the Droid 4 much since cm11, it's likely still a good option
sd_shadow's How-To Videos for Droid 4
Sent from my XT1254 using XDA Labs
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
The link for safe strap is not dead there are two versions. One from stargo and the other is a modified safe strap for unused partitions redone by some one else. You need to look in the correct posts and thread. Here is the download: http://www.internauta37.altervista....afestrap-maserati-v3.75-unused-partitions.apk
As far as for gsm keep looking you'll probully find something. I can't help you with that because I never needed to use but it shouldn't be to hard to do or figure out.
As far as wich rom you want to use just try a few different ones and see wich one you prefer to use as a daily driver.
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
moodroid said:
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
Click to expand...
Click to collapse
Shplad said:
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
Click to expand...
Click to collapse
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
moodroid said:
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Click to expand...
Click to collapse
Shplad said:
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
Click to expand...
Click to collapse
As far as I understand it (which could be totally wrong), 11 and 12 are no longer being developed and will only receive security updates, so from that point of view, I guess they will be more stable. But 13 and 14 will work, but there may be the odd issue here and there (particularly with 14 which is still quite new). You'd have to have a quick scan through the comments to see if there's anything that's like to be a problem for you.
With reagrds to GSM, I should just try it and see if it works to begin with. If it doesn't, then download the patch, reboot, go into safestrap, install the zip then reboot.
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provides superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Wow, this is a lot to take in. Thanks. So, I don't quite understand the repercussions. Once I root, does that mean any ROM OS that boots is somewhat more vulnerable, cause it's like being logged on as root in Linux, or does it depend which ROM I'm using or something else?
Bobcus Leper said:
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provided superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Click to expand...
Click to collapse
Okay, I figured out after my last post that root status depends on which ROM you are running, and of course installing a ROM without root status would put you back to unrooted status.
I downloaded Lineage OS 13 and verified the MD5SUM. I rooted the phone using Shadow's video.
Now I want to make an image of my NAND or have some other method of restoring the stock ROM before I install a new ROM. At what stage in the process do I do that and what is the safest tool / method to do that? RSDLite? Adding another ROM slot and using Nandroid backup?
Awaiting anxiously...
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Shplad said:
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Click to expand...
Click to collapse
As far as I understand it, and again, this could be wrong, using RSDLite is usually a last resort in the unlikely event that you've completely messed up your phone. You will lose everything, and your phone will back to how it was when you bought it. I've never needed to use RSDLite myself, but from what I've read, it's a pretty reliable way to get your phone working again. As long as you follow all the instructions, and install CM (LOS) 13 into another slot, it's very unlikely that you'll damage your original stock rom and you'll still be able to boot into if ever you need to. Hopefully, someone who knows more about it will comment also...
I got Safestrap 3.75 special version for unused partitions installed. I didn't realize it allows you to make TWRP ROM backups.
I made a backup of the stock ROM. The first time I did that, I got an error stating it couldn't find or access /boot.
Strangely, the second time I tried, it seemed to work fine.
I copied the folder with the stock ROM backup to my PC, just in case. I managed to flash with Lineage OS 13. It booted fine, but I forgot to select the Gapps zip as well. It does not appear to be rooted after bootup.
1. Do I need to reinstall Lineage 13 or is there way to install the apps without reinstalling Lineage?
2. What is the normal state of this ROM? I'm not sure if I have to root Lineage 13. If I don't enable root, will I be unable to run TWRP recovery and add the Gapps zip file and reinstall? I don't want to be stuck with a successful Lineage install and no apps. I'd find another way to install the apps, but I'm guessing you can't without the apps themselves, no?
Help!
Okay, I figured out how to install just gapps 5.1-2015-05-23-24 . However, during configuration, I cannot get the phone to connect to gmail via WiFi (I don't have a data plan).
"Validating Server Settings...
Couldn't open connection to server."
I see other people had this in other version of Android. Is this a particular problem in Lineage 13? Any solutions known?
...AAAANDDD Google Play Services has closed.
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
EDIT:
I tried these suggestions, just in case.
https://productforums.google.com/forum/#!topic/gmail/ACSvDiQoufI
Now, I'm getting the error:
"Problem with account setup
Username or password is incorrect"
Google Play Services keeps closing. Should I uninstall the gapps and install a more compatible one? I think network connectivity is not stable.
Shplad said:
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
Click to expand...
Click to collapse
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
moodroid said:
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
Click to expand...
Click to collapse
Shplad said:
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
Click to expand...
Click to collapse
I meant on this website. In the 'Droid 4 Android Development' section (https://forum.xda-developers.com/droid-4/development), there a thread for each of the roms. The one for CM (LOS) 13 is https://forum.xda-developers.com/droid-4/development/cm13-0-marshmallow-unofficial-builds-t3270938
moo:
Thanks for that. I didn't post there earlier because I thought it was only for developer reports of bugs, and my coding skills are exactly zero. Should I wait to see what happens in that other thread and not post back here until I hear something from there?
Stock ROM, updated several times in the past. Decided it was time to root it.
Downloaded the latest ROM (OnePlus3TOxygen_28_OTA_027_all_1706272156_5be1658723c44eb4.zip) from OnePlus' official website and sideloaded it with adb.
Set the developer settings on the phone then used the OP3(T) Toolkit to unlock the bootloader and install TWRP.
Boot up phone again to double check, everything seems to work fine. So far so good.
Install SuperSU, no bootloop but it simply freezes a few seconds into the boot animation. Hard reset phone.
Attempt to install no-verity through the toolkit (not sure if I should), reboot, same result.
Tried several times, in between wiping Dalvik/cache but nothing seems to make a difference.
Is the ROM simply not supported or something? This is driving me crazy..
For a phone which manufacturer is supposed to embrace community efforts, this is the only phone that has given me a major headache trying to root it.
I'm out of ideas at this point, maybe someone can tell me what's going on here?
What version of SuperSU? The latest releases have had some issues... If you haven't already, I'd use the latest Service Release. Or if that doesn't work version 2.79 (found here).
For rooting, there's also Magisk to consider and phh's superuser.
Thanks for your input.
The toolkit seems to come with 2.79. Should I just give the latest version a shot and see what happens?
I'm on the latest version of the ROM right now with the bootloader unlocked.
Edit: fixed. SuperSU 2.82 stable worked for me. Thanks again
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.