I just ordered a droid 4 from ebay. I'm on Fido(Rogers) in Canada BC.
I was wondering what are some good mods/hacks/roms/flashes/etc I should consider doing to this phone?
-I want nice reliable performance out of it.
Also how to unlock it?
It's been a long time since I did this sort of thing which is why I wanted to brush up on this here first?
[INDEX] Development Motorola Droid 4
Sent from my XT1028 using Tapatalk
---------- Post added at 11:01 PM ---------- Previous post was at 11:00 PM ----------
Frequently Asked Questions: Motorola Droid 4
Sent from my XT1028 using Tapatalk
The bootloader isn't unlockable at the moment, it's not supported by Verizon's unlock program (and might not even support the unlock commands).
For "nice, reliable performance", you'll probably want a KitKat-based ROM, as Lollipop isn't quite there yet. CyanogenMod 11 is pretty much the go-to, being based on 4.4.4, and there're several others based on it; SlimKat being my personal preferred.
No matter what you want to run, you will need to first root the stock ROM (using one of the available tools for our phone, popular one-size-fits-all methods probably won't work), then install Safestrap. Safestrap itself allows you to make additional ROM "slots", of which you can boot into instead of the stock ROM.
As for additional things, if Rogers does their service via GSM, you'll need the GSM patch, as most ROMs come configured for Verizon CDMA.
All of the above can be found in either the threads sd_shadow posted, or under the Development subforum
Workflow:
Root stock ROM
Install Safestrap app, then install Safestrap itself via the app
Create a ROM slot (note: will use ~3gb of internal storage)
Install your chosen ROM along with Gapps and the GSM patch (if needed)
Start phone for the first time, may take a while for the first run
Install any extras (JBX kernel for overclocking, Xposed, etc)
Septfox said:
The bootloader isn't unlockable at the moment, it's not supported by Verizon's unlock program (and might not even support the unlock commands).
For "nice, reliable performance", you'll probably want a KitKat-based ROM, as Lollipop isn't quite there yet. CyanogenMod 11 is pretty much the go-to, being based on 4.4.4, and there're several others based on it; SlimKat being my personal preferred.
No matter what you want to run, you will need to first root the stock ROM (using one of the available tools for our phone, popular one-size-fits-all methods probably won't work), then install Safestrap. Safestrap itself allows you to make additional ROM "slots", of which you can boot into instead of the stock ROM.
As for additional things, if Rogers does their service via GSM, you'll need the GSM patch, as most ROMs come configured for Verizon CDMA.
All of the above can be found in either the threads sd_shadow posted, or under the Development subforum
Workflow:
Root stock ROM
Install Safestrap app, then install Safestrap itself via the app
Create a ROM slot (note: will use ~3gb of internal storage)
Install your chosen ROM along with Gapps and the GSM patch (if needed)
Start phone for the first time, may take a while for the first run
Install any extras (JBX kernel for overclocking, Xposed, etc)
Click to expand...
Click to collapse
Thank you very helpful.
Will this make it work on my current network?
Edwii said:
Thank you very helpful.
Will this make it work on my current network?
Click to expand...
Click to collapse
Edit
---------- Post added at 11:54 PM ---------- Previous post was at 11:46 PM ----------
see [Q] Droid 4 in Canada (Rogers?) by demungtoe
and
Droid 4 On Rogers Wireless (Canada) - Incoming "Pay Phone" caller ID Solution by danifunker
and
Rogers Wireless Motorola Droid 4 Internet APN Settings
but I'm guessing that if you install the GSM patch, it should work ok.
Septfox said:
The bootloader isn't unlockable at the moment, it's not supported by Verizon's unlock program (and might not even support the unlock commands).
For "nice, reliable performance", you'll probably want a KitKat-based ROM, as Lollipop isn't quite there yet. CyanogenMod 11 is pretty much the go-to, being based on 4.4.4, and there're several others based on it; SlimKat being my personal preferred.
No matter what you want to run, you will need to first root the stock ROM (using one of the available tools for our phone, popular one-size-fits-all methods probably won't work), then install Safestrap. Safestrap itself allows you to make additional ROM "slots", of which you can boot into instead of the stock ROM.
As for additional things, if Rogers does their service via GSM, you'll need the GSM patch, as most ROMs come configured for Verizon CDMA.
All of the above can be found in either the threads sd_shadow posted, or under the Development subforum
Workflow:
Root stock ROM
Install Safestrap app, then install Safestrap itself via the app
Create a ROM slot (note: will use ~3gb of internal storage)
Install your chosen ROM along with Gapps and the GSM patch (if needed)
Start phone for the first time, may take a while for the first run
Install any extras (JBX kernel for overclocking, Xposed, etc)
Click to expand...
Click to collapse
I forgot to ask, where do I down load the tools and roms I need? Can you link me?
Edwii said:
I forgot to ask, where do I down load the tools and roms I need? Can you link me?
Click to expand...
Click to collapse
[INDEX] Development Motorola Droid 4
Sent from my XT1028 using Tapatalk
sd_shadow said:
Edit
---------- Post added at 11:54 PM ---------- Previous post was at 11:46 PM ----------
see [Q] Droid 4 in Canada (Rogers?) by demungtoe
and
Droid 4 On Rogers Wireless (Canada) - Incoming "Pay Phone" caller ID Solution by danifunker
and
Rogers Wireless Motorola Droid 4 Internet APN Settings
but I'm guessing that if you install the GSM patch, it should work ok.
Click to expand...
Click to collapse
Thank you again for you time and help.
I've been pacing myself though the guides and things seem to be going well. I have saferoot/safestrap installed now, however being the noob I am in this world, can not pick the rom I should use.
Septfox: said I should probably use a kitkat rom, and CyanogenMod is "the go to". That in itself has a lot of versions, and I am unsure which to pick? Also I am unsure if that is the best one for me, or if perhaps I should stay in jellybean? As I said I value stable/reliable first, then battery and performance after.
Could you please give me some guidance as to which to pick, and or atleast which CyanogenMod build is optimal at this point?
Edwii said:
Thank you again for you time and help.
I've been pacing myself though the guides and things seem to be going well. I have saferoot/safestrap installed now, however being the noob I am in this world, can not pick the rom I should use.
Septfox: said I should probably use a kitkat rom, and CyanogenMod is "the go to". That in itself has a lot of versions, and I am unsure which to pick? Also I am unsure if that is the best one for me, or if perhaps I should stay in jellybean? As I said I value stable/reliable first, then battery and performance after.
Could you please give me some guidance as to which to pick, and or atleast which CyanogenMod build is optimal at this point?
Click to expand...
Click to collapse
Safestrap has the option to create rom slots, up to 4.
These are virtual partitions created on the internal sd card.
I suggest creating a rom slot, and installing any new rom there, if you like the rom you can install over stock slot.
but before installing over stock rom you should back it up first.
see my Installing/Upgrading Safestrap 3.75 and Installing a Lollypop Rom
for some basic safestrap options.
As for a rom I would start with cm-11-20150626-SNAPSHOT-XNG3CAO1L8-maserati.zip
It's the last official cm11 build.
Download and verify the md5 checksum see Using Hash Checksums
I used the recommended CyanogenMod rom, and it was alright.
I'm about to try a new rom, and I was wondering if there are any that are more battery efficent/ is CyanogenMod power hungry?
Edwii said:
Septfox: said I should probably use a kitkat rom, and CyanogenMod is "the go to". That in itself has a lot of versions, and I am unsure which to pick? Also I am unsure if that is the best one for me, or if perhaps I should stay in jellybean?
Click to expand...
Click to collapse
Sorry, I never saw this post. Didn't mean to ignore you.
The ROM sd_shadow posted was/is probably the "best" for the common user. I would use even a slightly outdated SlimKat build myself, but that's down to the features it includes, not any real edge it has over CM11.
But, back to today...
Edwii said:
I used the recommended CyanogenMod rom, and it was alright.
I'm about to try a new rom, and I was wondering if there are any that are more battery efficent/ is CyanogenMod power hungry?
Click to expand...
Click to collapse
If CM11 is still battery-hungry these days, it's actually down to Play Services and Google insisting on everything wakelocking the phone as much as possible. It can be worked around with some effort, but you lose automatic/always-on features as you disable more and more things to gain battery efficiency.
Other 4.4-based ROMs will be in the same boat as far as efficiency and requirements to gain more. They vary by features that they offer in addition to CM11's.
CM12/Lollipop's version of Play Services is significantly better at letting the phone sleep, so out of the box it's quite battery-efficient (expect ~1%/hr, 1.2%/hr at most sleeping with wifi on) while retaining capabilities.
Other 5/5.1 ROMs are available too. but I don't know anything about them. At the moment, Liquidsmooth and Resurrection Remix are fairly recent/high in the list in the Development subforum, both based on 5.1, but neither seems to have gained much popularity for whatever reason.
I didn't run Jellybean for very long, but it seemed pretty snappy and word on the streets is that it's still the most battery-efficient of all. The problem is, you miss out on certain modern features, and some of the more desirable apps simply won't work because they target KitKat and later; sometimes this can be worked around and they'll run, sometimes they'll break and fail because of missing APIs.
If you want to run JB, I'd highly recommend grabbing a debloated version, to get rid of most of the preloaded Verizon/Motorola crapware.
Do either liquidsmooth or ressurection remix support overclocking?
Sent from my XT894 using Tapatalk
No, they are lighter.
Related
Hey All,
I have my Droid 3, and its been great to me. Its my first smartphone and first android phone, and it will always have that place in my heart That being said, not getting ics was a letdown from Motorola and sparked my interest in rooting for awhile now. I had always been cautious as I would not want to void my warranty and then brick my device, as that is simply my luck, lol. I was fortunate in that when my device broke due to an abnormal defect (Scoured the forums, never found anything and Motorola support had no idea, immediately shipped me a new device haha) it got replaced this past summer, but now my warranty expired in October and I'm noticing the lag more and more. SO.... I have been looking into the process specific to the droid 3, and I have found bits and pieces, such as using motofail now for the latest ota and what not. But is there a specific, comprehensive how-to guide towards doing so, that is current? I've found threads and get excited, only to see a comment saying "x" is outdated use this instead blah blah blah. I was fine with this, as its an outdated device and all, until noticing such exists for the kindle fire (Girlfriend was open to possibly rooting it as well, have been looking into that too. but that's another story ) I'd post the link, but alas, I'm a noob and do not have the ability to.
I know I am just being paranoid, or just terrible at searching the forum lol. But if a super guide like this exists, I would feel so much more comfortable in proceeding with rooting.
Nor sure about a guide but here's what I did
1) Root device using motofail http://forum.xda-developers.com/showthread.php?t=1497690
2) Install Safestrap http://blog.hash-of-codes.com/how-to-safestrap/
3) Create an additional ROM slot
4) Dowonload the ROM of your choice. This might be a good place to start http://androidforums.com/droid-3-all-things-root/494721-rom-current-droid-3-rom-list.html
5) Activate the blank rom slot and flash the rom
6) reboot and you're up
Good writeup. Also I would suggest you stick with something stock based. Minimoto is very nice and has excellent battery life. JB is still alpha and takes a bit of tweaking to get it stable.
some videos
How to Video's Root, safe strap, kexec, and much more
How to install and use safe strap 3.05 on the droid 3 for true multi booting on ROMs
http://youtu.be/q-qK7kL0W3o
roms to look at
Steel Droid GB 4.5
Steel Droid ICS 5.6
Thanks everyone for the links and videos, rooting the phone today!
I'm looking for verification from the op that he used these videos and links successfully to gain root and install a ROM?
I am very android oriented.... just never played with a D3. GF's stock D3 is running, well, sucky stock. And she asked me to fix it for her. I was going to request something similar as far as a flashing guide so I could get it all set in one night
Thanks to those for posting the links and resources
Sent from my Galaxy Nexus using xda premium
Sorry this is extremely late, I must have not subbed to the thread, stumbled upon it when cleaning my bookmarks haha. Yes, I used these and I've been on minimoto since. No obstacles or anything, was pretty easy just updating my rom today actually, and fell back on them as well. I figure you already went ahead, but figured I'd finally respond nonetheless
Confused Noob.
Hello I just recently ordered my DROID 3 from Ebay (can't wait to get it). Now I know that there are two roms which are the CM 9 and CM 10 and they work with ICS and JB respectively. Also there are variations with KEXEC and stuff like AOKP now this is getting confusing for me. I have never owned an Android my whole life I have been a Linux user. So are the alpha builds of CM9 and 10 working properly? As in can you make calls, use the play store and download apps on both? Which one should I use? I could not care less about cameras. I am not the picture taking type. Advice please. Make a room in your heart for this Noob. Thank YOU!
cm10 is very usable, imo, but that is really up to you
I'm using AOKP JB, which is like CM10
use safestrap 3 for d3, you can install 4 roms and switch between reboots
---------- Post added at 10:55 PM ---------- Previous post was at 10:52 PM ----------
fyi
AvRS said:
Best/most stable ROM threads aren't allowed as they're too subjective, you'll receive lots of differing opinions on the same thing. Only way is to try yourself and find the one that fits you best as that's what these forums are about.!
Click to expand...
Click to collapse
Hey Thanks.
sd_shadow said:
cm10 is very usable, imo, but that is really up to you
I'm using AOKP JB, which is like CM10
use safestrap 3 for d3, you can install 4 roms and switch between reboots
---------- Post added at 10:55 PM ---------- Previous post was at 10:52 PM ----------
fyi
Click to expand...
Click to collapse
Thanks for the reply, so what are the latest versions of AOKP JB and CM10? Safestrap seems very useful. I agree with you better to install both and check which one is more useful.
http://goo.im/devs/hashcode/solana/
Sent from my XT862 using xda premium
Super
sd_shadow said:
hXXp://goo.im/devs/hashcode/solana/[/URL]
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
You Rock!
Sorry, I'm sure this will have been posted before, but I used the search function and couldn't narrow the results to what I was looking for.
I have a UK EE spec S3 LTE (Kernel - 3.0.31-1153417, Build - JZO54K-I9305XXBMF1). I have seen MSkip's excellent S3 Unified Toolkit and I am close to getting the courage to root my device, ready to put a different firmware on it to get rid of all the crap that Samsung "think" I want.
I have a couple of questions first though:
1. Can someone recommend a ROM that is the closest to stock Android (JB of course) as I love the feel of the Nexus devices. Unless 'proper' stock Android is an option.
2. Does anyone know is installing a custom ROM will affect how my 4G data reception/operation.
3. How likely am I to make a total arse of it and brick my phone?
I'm sure I'll get a few "wrong thread". "Q&A"."Theres the door dimwit" responses, but I'm big enough and ugly enough, with a heavy duty flamesuit so I can take the insults!! I'm sure someone can help :fingers-crossed:
Notlaw1976 said:
Sorry, I'm sure this will have been posted before, but I used the search function and couldn't narrow the results to what I was looking for.
I have a UK EE spec S3 LTE (Kernel - 3.0.31-1153417, Build - JZO54K-I9305XXBMF1). I have seen MSkip's excellent S3 Unified Toolkit and I am close to getting the courage to root my device, ready to put a different firmware on it to get rid of all the crap that Samsung "think" I want.
I have a couple of questions first though:
1. Can someone recommend a ROM that is the closest to stock Android (JB of course) as I love the feel of the Nexus devices. Unless 'proper' stock Android is an option.
2. Does anyone know is installing a custom ROM will affect how my 4G data reception/operation.
3. How likely am I to make a total arse of it and brick my phone?
I'm sure I'll get a few "wrong thread". "Q&A"."Theres the door dimwit" responses, but I'm big enough and ugly enough, with a heavy duty flamesuit so I can take the insults!! I'm sure someone can help :fingers-crossed:
Click to expand...
Click to collapse
Well, bricking your phone is nearly impossible, just do whatever the instructions says and you'll be fine.
And the 4G reception won't be affected, since the only thing affecting data is modems, and AOSP ROM got no modems.
And as of question number 1, there's a ROM called SuperNexus, it's exactly like a Nexus 4. But it's rarely updated and sources from CM might be a bit old. I suggest using CM or Carbon since they're being frequently updated.
I hope I answered all of your questions!
Cheers,
Sebastian!
sebbe312 said:
Well, bricking your phone is nearly impossible, just do whatever the instructions says and you'll be fine.
And the 4G reception won't be affected, since the only thing affecting data is modems, and AOSP ROM got no modems.
And as of question number 1, there's a ROM called SuperNexus, it's exactly like a Nexus 4. But it's rarely updated and sources from CM might be a bit old. I suggest using CM or Carbon since they're being frequently updated.
I hope I answered all of your questions!
Cheers,
Sebastian!
Click to expand...
Click to collapse
Thanks Sebastian! Not heard of Carbon, i'll have to Google that one. When it comes to CM, would you recommend going nightlies or a more stable version? I've heard Paranoid Android is decent too, any opinions on that one?
Sent from my GT-I9305 using Tapatalk 2
Notlaw1976 said:
Thanks Sebastian! Not heard of Carbon, i'll have to Google that one. When it comes to CM, would you recommend going nightlies or a more stable version? I've heard Paranoid Android is decent too, any opinions on that one?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Dunno really about Paranoid Android, I don't use it but I find it pretty OK. And if I recall it correctly, there isn't a Stable version of CM for 9305.
sebbe312 said:
Dunno really about Paranoid Android, I don't use it but I find it pretty OK. And if I recall it correctly, there isn't a Stable version of CM for 9305.
Click to expand...
Click to collapse
He's right there isn't a "stable" version but i personally can't live without using CM on my S3 i can highly recommend it, especially the ease of one touch button theme's
nags92 said:
He's right there isn't a "stable" version but i personally can't live without using CM on my S3 i can highly recommend it, especially the ease of one touch button theme's
Click to expand...
Click to collapse
Cheers, what do you use; nightlies? How often do you have to flash a new one? Are they as full of bugs as I imagine them to be?
This might sound like a stupid question, when you flash a new ROM, so you lose all your things like email settings, apps and stuff. Does the Google Play app come with a new ROM or do you have to get that as an APK from somewhere and manually install it?
Sent from my GT-I9305 using Tapatalk 2
Notlaw1976 said:
Cheers, what do you use; nightlies? How often do you have to flash a new one? Are they as full of bugs as I imagine them to be?
This might sound like a stupid question, when you flash a new ROM, so you lose all your things like email settings, apps and stuff. Does the Google Play app come with a new ROM or do you have to get that as an APK from somewhere and manually install it?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
CM is updated every night, hence calling them "nightlies".
CM is very stable, and I often flashed a new nightly every morning.
And question about google apps; you download a different zip file, this file contains all the Google apps.
So you first flash CM then the zip file with google apps.
Sent from my GT-I9305 using xda app-developers app
So I've been using my s4 active for about 2 months now, and I have no problems with it, but I enjoy the tweaks.
I've been debating on trying out safestrap, but havent had time yet. I got another idea from another post I previously read.
1st question is, will I be able to get my phone replaced even though I bought it full price, and live in Canada? (in case of water damage, that's really the only concern, as things like smashed screens aren't covered by anyone)
if not then is it not worth it for me to call at&t and have them unlock my bootloader, seeing how they wouldnt be covering my warranty anyhow in that case?
I just want a change to pure, simple, stock android.
I have no idea why you'd get your phone replaced or if it's possible, that's between you and whatever company you bought it from. If you're tinkering around with it with root and flashing things on it, most likely you'll be voiding the ToS or whatever from the seller so that's up to you do find out from them.
The only "pure, simple, stock android" you're going to get on the I537 right now at this minute is the AOSP ROM provided by LeJay, and that requires:
a) a rooted I537 (meaning it's running either the MF1, MF2, or MF3 build of Android 4.2.2)
b) Safestrap for the I537 provided by Hashcode (not the regular Safestrap found elsewhere, you need the specific version for the I537 and it's found here in this subforum for the GS4A)
c) the AOSP ROM to flash, d) the MF1/MF2/MF3 kernel modules depending on the build/kernel you use as your stock ROM
d) the camera fix also provided by LeJay
The AOSP ROM can be found in LeJay's AOSP thread; the other files can be found in Hashcode's Safestrap thread (again, all in this subforum for the GS4A).
br0adband said:
I have no idea why you'd get your phone replaced or if it's possible, that's between you and whatever company you bought it from. If you're tinkering around with it with root and flashing things on it, most likely you'll be voiding the ToS or whatever from the seller so that's up to you do find out from them.
The only "pure, simple, stock android" you're going to get on the I537 right now at this minute is the AOSP ROM provided by LeJay, and that requires:
a) a rooted I537 (meaning it's running either the MF1, MF2, or MF3 build of Android 4.2.2)
b) Safestrap for the I537 provided by Hashcode (not the regular Safestrap found elsewhere, you need the specific version for the I537 and it's found here in this subforum for the GS4A)
c) the AOSP ROM to flash, d) the MF1/MF2/MF3 kernel modules depending on the build/kernel you use as your stock ROM
d) the camera fix also provided by LeJay
The AOSP ROM can be found in LeJay's AOSP thread; the other files can be found in Hashcode's Safestrap thread (again, all in this subforum for the GS4A).
Click to expand...
Click to collapse
I meant just for warranty purposes, but that sounds simple enough.. I've really only been reading up info in this subforum, safestrap included, since I got the i537 anyhow.
I'm assuming you have experience using this rom on this phone, did you notice improved battery? and is it "better" overall? I don't care for any touchwiz addons obviously.
Thank you for all the advice
It's just Android, not sure what else I can say. I haven't noticed anything particular beneficial or negative either way - it's just another ROM to me to use if I choose to do so. Using Safestrap with the AOSP ROM is just an option that makes the GS4A more useful I suppose. Even if it's pure stock from Samsung, that's fine with me too, doesn't matter.
Still hoping for an actual CyanogenMod build if someone gets around to it but those hopes are dying a bit more each day with what's becoming of that project overall. I don't mean seeing full on support for the GS4A, that will never happen, what I mean is someone talented enough to take the kernel source for the GS4A and make a CM10.1 build for us that we can flash using Safestrap. It'll still be limited because of the locked bootloader so no custom kernel stuff, but most everything else could be useful and I do like CM overall.
I don't know what other people want or do with their devices so I can't comment, I tend to keep mine simple and don't get into the serious modding of most everything (UI, fonts, icons, etc) like others.
I'm pretty much a "stock" kinda person I guess.
br0adband said:
It's just Android, not sure what else I can say. I haven't noticed anything particular beneficial or negative either way - it's just another ROM to me to use if I choose to do so. Using Safestrap with the AOSP ROM is just an option that makes the GS4A more useful I suppose. Even if it's pure stock from Samsung, that's fine with me too, doesn't matter.
Still hoping for an actual CyanogenMod build if someone gets around to it but those hopes are dying a bit more each day with what's becoming of that project overall. I don't mean seeing full on support for the GS4A, that will never happen, what I mean is someone talented enough to take the kernel source for the GS4A and make a CM10.1 build for us that we can flash using Safestrap. It'll still be limited because of the locked bootloader so no custom kernel stuff, but most everything else could be useful and I do like CM overall.
I don't know what other people want or do with their devices so I can't comment, I tend to keep mine simple and don't get into the serious modding of most everything (UI, fonts, icons, etc) like others.
I'm pretty much a "stock" kinda person I guess.
Click to expand...
Click to collapse
Alright, awesome. Thanks for the pointers, I appreciate it.
I'm gonna give safestrap a try.
so I got the mf3 .zip, the safestrap apk, and the aosp rom .zip
I am already rooted so that's taken care of,
The camera fix is the only thing I can't seem to find.. and I feel like it's staring me in the face lol
There are mirror links in that thread (and one of 'em was from me), just gotta find 'em.
br0adband said:
There are mirror links in that thread (and one of 'em was from me), just gotta find 'em.
Click to expand...
Click to collapse
ITS "GONE" !!!!
http://click.xda-developers.com/api...CamPatch.zip&jsonp=vglnk_jsonp_13811789660048
thats the link address... is there anywhere else?
djsdumesh said:
ITS "GONE" !!!!
http://click.xda-developers.com/api...CamPatch.zip&jsonp=vglnk_jsonp_13811789660048
thats the link address... is there anywhere else?
Click to expand...
Click to collapse
SCRATCH THAT got the QR code and downloaded it directly on my phone.. I'm ready to go.
Thanks for all the help!
https://dl.dropboxusercontent.com/u/19019338/SGS4A_CamPatch.zip
And there as well just in case.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.
channing173 said:
Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.
Click to expand...
Click to collapse
The CM Quark dev @Skrilax_CZ just bought a 2nd phone so he can test CM13 while still keeping CM12.1 going on his main phone.
http://forum.xda-developers.com/mot...xx-xt1225-cm12-0-pre-release-t3060089/page100
Rule #1 of Fight Club: Never ask for ETAs.
Sent from my DROID Turbo using Tapatalk
Patiently waiting here too ...
Patiently waiting here too. Marshmallow changes look interesting.
and Thanks in advance,
You'll know as soon as you see a changelog here http://www.cmxlog.com/13/quark/
Sent from my XT1254 using Tapatalk
I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.
EnderKR said:
I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.
Click to expand...
Click to collapse
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was released.
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have -- or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with that ROM let me use my phone the way I wanted, giving me choice back while still using that ROM. The problem with using xposed + custom ROMs is xposed modules are only guaranteed to work on AOSP ROMs that have not been heavily modified. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in the example I gave, "clear all recents".
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options... but I'm comfortable with CM12.1. (CM dev @Skrilax_CZ brought the first custom ROM and kernel for our Quarks, all others that followed are based his work -- especially the kernel.) I'm running CM12.1 on both my Quarks and have been for months. But the point is both Resurrection Remix and CM12.1 are way more advanced than Motorola stock 5.1, as they are both 5.1.1 + custom features.
NOTE: There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else, but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus, Resurrection Remix and even CM12.1 would have the security updates stock ROM does not.
I'm running CM12.1 plus Moto Camera because someone ported the Moto camera for CM users, and CM12.1 has all the other functionality I need (just different names).
ChazzMatt said:
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was .
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with the ROM let me use the phone the way I wanted, giving me choice back while still using that ROM. The problem with that is xposed modules are only guaranteed to work over ROMs that have not been heavily customized already. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in my case, clear all recents.
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options, but I'm comfortable with CM12.1. BOTH are way more advanced than stock 5.1, as they are both 5.1.1 + custom features.
There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus Resurrection Remix would have the security updates stock ROM does not.
Click to expand...
Click to collapse
Fair enough, I appreciate the input. I'm still pretty new to the custom ROM scene, so there's lots to learn. Why not, I'll give Resurrection Remix a try. Sounds like people love it, and I really like the Moto features so I'd want to keep those. Thanks for the advice
I honestly just like the "all my devices are the same" so all my devices that can run cm.
As for CM-13.0, there is still a lot to be done to get it to a daily driver state.
Hurts not having stock mm I'm guessing?
Sent from my XT1254 using Tapatalk
Skrilax_CZ said:
As for CM-13.0, there is still a lot to be done to get it to a daily driver state.
Click to expand...
Click to collapse
koftheworld said:
Hurts not having stock mm I'm guessing?
Click to expand...
Click to collapse
Not necessarily. That didn't stop @Skrilax_CZ from giving us Lollipop (March 2015) before Motorola released stock Lollipop for any of the Quarks. April 2015, Moto Turbo XT1225 was released with stock Lollipop 5.0.2 -- that was the first Quark with stock Lollipop from Motorola. @Skrilax_CZ beat them by using CM12.0 (Lollipop 5.0.2) with Kitkat 4.4.4 kernel, until Motorola publicly released Lollipop 5.0.2 kernel code. (Even though Motorola gave the Moto Turbo XT1225 5.0.2 in April 2015, they didn't release their Lollipop 5.0.2 kernel code publicly for devs to use until a few weeks later.)
Point is, we had Lollipop for Quark before Motorola gave Lollipop to Quark!
And we had CM12.1 (Lollipop 5.1.1) months (mid-April 2015) before Motorola finally gave just 5.1 to the Droid Turbo XT1254 in July 2015:
Skrilax_CZ said:
15th April 2015, 03:37 PM
Done. I have also moved to CM12.1 from now on, so I'll not be backporting latest set of patches back to CM-12.0
Click to expand...
Click to collapse
@Skrilax_CZ used CM12.1 (Lollipop 5.1.1) first with Motorola's 4.4.4 kernel code and then Motorola's 5.0.2 kernel code, until Motorola finally released Lollipop 5.1.x kernel code (September 2015).
Motorola never gave the other Quarks Lollipop 5.1 -- the Moto Turbo XT1225 and Moto Maxx XT1225 officially still have 5.02. and the U.S. Moto Maxx XT1250 (same identical device as the Droid Turbo XT1254, even the same FCC ID) is still "officially" stuck on Kitkat 4.4.4 -- unless you root and install custom Lollipop 5.1.1. ROM. But thanks to devs like @Skrilax_CZ we've had Lollipop 5.1.1 since April 2015!
So, NO, we do not have to wait for Motorola's slow roll-out of stock MM for our Quarks.
____________
mrkhigh said:
I honestly just like the "all my devices are the same" so all my devices that can, run cm.
Click to expand...
Click to collapse
Same here. When I help friends and family, I install CM so I know exactly where all the settings and options are. Two LG G2 phones, a Nexus 7 tablet all owned by other friends or in-laws. My wife's and my Quark XT1225. For some reason I never rooted my wife's Nexus 9 (yet) -- but when I do, it will have CM.
I also install Nova launcher and set all those options the same all all devices (including non-rooted Nexus 9). My wife said, "But my tablet looks like my phone." I replied, "Exactly." That was my intention.
If something isn't acting right, I can quickly diagnose it without having to remember it's set up differently or has an entirely different ROM.
Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.
IonAphis said:
Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.
Click to expand...
Click to collapse
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk
http://forum.xda-developers.com/showpost.php?p=64573429&postcount=1050
cadenmiller60 said:
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears
kitcostantino said:
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears
Click to expand...
Click to collapse
Few things to note and remember that the DPI for the two devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?
GreaterLesser said:
Few things to note and remember that the DPI for the too devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?
Click to expand...
Click to collapse
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.
kitcostantino said:
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.
Click to expand...
Click to collapse
Well for WiFi, Radios, Bluetooth, etc doesn't the drivers need to be added to the build.prop for the system to actually use them? If possible you could use a build.prop for the turbo in Carbon and just tailor it a bit, theoretically of course. I know it's more complicated than I'm making it sound.
lol. yes, but i get what you mean. in older roms (cm10, cm11) to port, youd copy/paste all of the set perm recursives. in cm12.1 i dont know where to start pulling things from. mind you, i know its not as simple as it used to be because of the new dat format. guess i should read up a bit. lol
I've checked multiROM Manager and XT1254 is not supported, however if some dev would like to take a crack at it here is a wiki that explains how to port it (and if you can in the first place). I've also done extensive testing with dual boot patcher. I got it to work once with a 4.4 ROM (I can't remember exactly which), but after switching back and forth between the ROMS once I couldn't "escape" the secondary ROM and had to restore a backup to get back into the primary ROM (crdroid v3.3).
If you have attempted to dual boot on the Droid Turbo please leave your experiences and findings below, I'd love to see a working solution. Thanks!
Edit: I've found two that work with crdroid v3.3
Bliss xda post Specific tested ROM download
AOKP version list (there is no marshmallow xda post) Specific tested ROM download
Well I have found one ROM (AOKP MM unofficial) that worked flawlessly with dual boot patcher running on crdroid v3.3. What's odd is that the nougat version by the same author does not work, and in fact no nougat ROM has worked with dual boot patcher for me.
Just some commentary... I've never understood the multi-ROM booting thing. I really only run one ROM at a time for both me and my wife. (I buy two phones at a time, and keep them identical as far as settings.) I do have many more apps than my wife -- but same phone, same ROM, same settings.
If I wish to save a ROM to try another out, I can always use TWRP backup save my current ROM and settings, and temporarily install another to see if it's better. But I have no desire to constantly switch back and forth between ROMs, for my "daily driver".
I'm not criticizing your desire in any way, I'm just suggesting maybe that's why it's not available with this phone. Not much demand for reasons I stated.
ChazzMatt said:
Just some commentary... I've never understood the multi-ROM booting thing. I really only run one ROM at a time for both me and my wife. (I buy two phones at a time, and keep them identical as far as settings.) I do have many more apps than my wife -- but same phone, same ROM, same settings.
If I wish to save a ROM to try another out, I can always use TWRP backup save my current ROM and settings, and temporarily install another to see if it's better. But I have no desire to constantly switch back and forth between ROMs, for my "daily driver".
I'm not criticizing your desire in any way, I'm just suggesting maybe that's why it's not available with this phone. Not much demand for reasons I stated.
Click to expand...
Click to collapse
I'm actually with you as far as temporarily installing it to test the ROM, however I have a rather annoying reason to still want it. The only ways to cash checks with my bank is to either physically mail the checks or deposit them by photo. As I'd rather have an automatic solution, I'm left with the latter. However, this leaves me with the problem that the camera doesn't work in their app on custom nougat ROMS (which I run). I tried talking their dev team into fixing it, but they reasonably don't want anything to do with supporting custom ROMS. As I'd rather not go through the whole backup/wipe/restore/repeat routine every time I want to cash a check, I am unfortunately left with dual booting a ROM that their app does support (most ROMS marshmallow or older).
I found another one that works (and finally works with my bank as well ). Here is the forum post for the Bliss ROM.
Stuckurface said:
Edit: I've found two that work with crdroid v3.3
Bliss xda post Specific tested ROM download
AOKP version list (there is no marshmallow xda post) Specific tested ROM download
Click to expand...
Click to collapse
Both of those ROMs are by @NepoRood. He posted them over here in the Droid Turbo forum instead of the other Quark forum as he owned a Droid Turbo. But so does @calsurferpunk, and he still posts his CM14/LOS ROM over in the other Quark forum. We used to be one big forum, but after the split most Quark development got posted over there as the Droid Turbo bootloader had not yet been unlocked by Sunshine. After the Sunshine team unlock, devs just continued posting over there for the most part...
@NepoRood shattered his Droid Turbo, and now has a different phone -- but you could ask him what he did differently to allow multi-ROM for those two Marshmallow ROMs that changed with his Nougat ROM. He said he was still going to post AOKP ROM updates with the help of testers in this forum.
Also, for his Nougat AOKP, make sure you are using his PERSONALIZED builds, not any of the "nightlies". To gain official status, he had to agree not to change anything in the AOKP ROM, but he was allowed to make and post personalized builds which have tweaks.
Last, you've tried all these? Current list of Nougat and Marshmallow. I didn't bother keeping track of Lollipop.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=71821604&postcount=73
___________
Stuckurface said:
I'm actually with you as far as temporarily installing it to test the ROM, however I have a rather annoying reason to still want it. The only ways to cash checks with my bank is to either physically mail the checks or deposit them by photo. As I'd rather have an automatic solution, I'm left with the latter. However, this leaves me with the problem that the camera doesn't work in their app on custom nougat ROMS (which I run).
Click to expand...
Click to collapse
OK, that's a practical reason I can understand.
So, it's nothing about "Safety Net" issues, it's basically newer custom ROMs (Nougat) don't work?
The app of the bank I use (a nationwide mega bank) works fine with RR 6.X (Marshmallow) and before that with CM12.1 (Lollipop) in depositing checks via photo. I've not tried Nougat ROMs yet. So, I may run into the same problem...
I've stayed with RR 6.x as it's rock solid and allows me to use a few xposed modules like Google Assistant Enabler (to turn on and unlock display), YouTube Adaway (to block YouTube ads, which regular Adaway does not) and MinMin Guard (which blocks 99.9% of all in app ads). I wish @bhb27 would release one more "rollup" update before development completely ends.
Of course I will switch to Nougat one day, but I didn't switch to Marshmallow until October of 2016, about the time Nougat was being released.
ChazzMatt said:
We used to be one big forum, but after the split most development got posted over there as the Droid Turbo bootloader had not yet been unlocked by Sunshine....
....Last, you've tried all these? Current list of Nougat and Marshmallow. I didn't bother keeping track of Lollipop.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=71821604&postcount=73
Click to expand...
Click to collapse
I knew that Moto Maxx and Droid Turbo were basically the same phone, but I always stuck to the Turbo forum for fear of bricking my phone/messing up my cell connectivity. I didn't realize that most of the ROMS are cross compatible :/
I tested a few of them but I never saw your list. Thanks for maintaining that, I just wish I had seen it sooner!
ChazzMatt said:
So, it's nothing about "Safety Net" issues, it's basically newer custom ROMs (Nougat) don't work?
Click to expand...
Click to collapse
Yep, I've got the photo check deposit to work on ROMS that don't pass safety net multiple times. The problem appears stem from the way custom nougat ROMS (and more specifically the way my bank app) interacts with the camera, though I haven't tried logging the app's behavior so your guess is as good as mine.
I miss Bliss, on my Turbo (heck, I miss my Turbo, lol)
Nougat ROMs have more security than Marshmallow, it's most likely Your bank app that is causing the problems though. I'm running Screw'D Nougat on my Nexus 6P and have no problems with using my banks mobile app (but, we're Rednecks, )
As far as MultiROM goes, I didn't do anything special to my builds, I don't know why Nougat doesn't work...
Stuckurface said:
I didn't realize that most of the ROMS are cross compatible :/
I tested a few of them but I never saw your list. Thanks for maintaining that, I just wish I had seen it sooner!
Click to expand...
Click to collapse
All the ROMs (especially Marshmallow and Nougat) are cross compatible for all Quarks -- except for CF's Verizon stock-based ROM. This is thanks to the CM dev @Skrilax_CZ who adapted the Motorola kernel so all CM (now LOS) based ROMs would work for all Quarks, after Sunshine team unlocked the Droid Turbo bootloader. @bhb27 has continued that work. Even ROMS like "AOSP" still all use that "universal" kernel coding for all Quark ROMs. Again, the exception is CF's ROM, which are purely Verizon stock firmware, just debloated and tweaked.
There was one older Lollipop ROM that never got updated with the "universal" kernel (after the November 2015 Droid Turbo bootloader unlock), but even CM12.1 (Lollipop), RR Lollipop, and @calsurferpunk's "unofficial" CM12.1 was also cross-compatible with all Quarks.
Multi-ROM has now been released by @bhb27, plus we now have SEVEN Nougat ROMs.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=73459132&postcount=80