RAZR M - XT905 with identity Issues - Droid RAZR M Android Development

I recently purchased a Motorola RAZR M 4G (LTE) here in australia from a local retailer. The details of which can be found at:
http://www.dicksmith.com.au/unlocked-smart-phones/motorola-razr-m-4g-unlocked-dsau-em5184
I have since unlocked the bootloader (I think it may of actually came pre-unlocked anyway), rooted and flashed Carbon KitKat ROM onto the phone.
In flashing Carbon I thought that for an XT905, I should of used the unified moto_msm8960 build. However, the install zip starts with an assert to check that the phone is correct for the ROM and thereby has a check (with others) for "scorpion_mini". But, my phone was returning "scorpion_mini_u". So, I editied the install zip to enable it to flash, and it all went smoothly and has been working fine. But, recently I looked at some logs generated by my phone, and it is showing up as msm8960dt; which if I am not mistaken in used by a MOTO X (among others).
So, it would appear that my Motorola RAZR M thinks it is not a scorpion_mini but a scorpion_mini_u, and it also thinks its a Moto X (msm8960dt ), but is "happy" to run a moto_msm8960 ROM, instead of an msm8960dt ROM.
I guess my questions are:
1. Has anyone else come across the above mix of identities? and understands whats going on?
2. Although the ROM appears to be running well, should I really only be flashing the "dt" ROMS onto my phone? either way, it does NOT match the available options in the assert statement for either ROMs.

I don't know if this helps anyone explain the above, but I found this thread:
http://forum.xda-developers.com/showthread.php?t=2528344
and when I checked the CPU Info
[email protected]_u:/ # cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 4 (v7l)
processor : 0
BogoMIPS : 13.53
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x1
CPU part : 0x04d
CPU revision : 4
Hardware : msm8960dt
Revision : 82a0
Serial : XXXXXXXXXXXXXXXX
Click to expand...
Click to collapse

I've pushed http://review.cyanogenmod.org/64451 for the scorpion_mini_u assert.
I'm not surprised it's confusing for you. The "dt" in "Machine: msm8960dt" you see in dmesg actually means "device tree".
In the case of moto_msm8960dt family (Moto X, Droid Ultra, Droid Maxx, Droid Mini), msm8960dt refers to SoC - MSM8960DT.
SoC used by moto_msm8960 family (Razr HD, Razr M, Atrix HD, Photon Q) is MSM8960.
Builds for your Razr M are moto_msm8960. moto_msm8960dt builds wouldn't boot on xt905 at all.
EDIT: yes, the thread you've found is about the same matter.

Thanks. When trying to find references to the scorpion_mini_u on the web, I also came across references to the "scorpion_mini_t"
https://github.com/mattlgroff/cwm/tree/master/motorola

I just came across the following web site whuich details some of the mapping between the codes, which may help in fuirther improving the cross over of the unified build.
https://support.google.com/googleplay/answer/1727131?hl=en
Motorola
201M (scorpion_mini_t/201M)
A1680 (umts_lucky/A1680)
Atrix (olympus/MB860)
Atrix (olympus/MB861)
Atrix (olympus/ME860)
Atrix HD (qinara/MB886)
Backflip (motus/MB300)
Backflip (motus/ME600)
Charm (umts_basil/MB502)
Citrus (cdma_ciena/WX442)
Citrus (cdma_ciena/WX445)
Citrus (cdma_ciena/XT301)
CLIQ (morrison/MB200)
CLIQ (morrison/morrison)
Cliq-XT (zeppelin/MB501)
Cliq-XT (zeppelin/ME501)
Defy (umts_jordan/MB525)
Defy (umts_jordan/MB526)
Defy (umts_jordan/ME525)
Defy (umts_jordan/ME525+)
Defy (umts_jordan/unknown)
Devour (calgary/calgary)
Devour (calgary/Devour)
Droid (miler/A854)
Droid (sholes/Droid)
Droid (umts_sholes/A853)
Droid (umts_sholes/Milestone)
Droid (umts_sholes/umts)
Droid (umts_sholes/XT701)
Droid (umts_sholes/XT702)
Droid (umts_sholes/XT720)
Droid 3 (cdma_solana/DROID3)
Droid 4 (cdma_maserati/DROID4)
DROID BIONIC (cdma_targa/DROID BIONIC)
Droid Bionic (cdma_targa/DROID BIONIC)
Droid II (cdma_droid2/A955)
Droid II (cdma_droid2/DROID2)
Droid II (cdma_droid2we/DROID2 GLOBAL)
Droid MAXX (obake-maxx/XT1080)
Droid Mini (obakem/XT1030)
Droid Pro (cdma_venus2/DROID PRO)
Droid Pro (cdma_venus2/DROID Pro)
Droid Pro (cdma_venus2/Milestone PLUS)
Droid Pro (cdma_venus2/XT610)
DROID RAZR (cdma_spyder/DROID RAZR)
Droid RAZR (umts_spyder/XT910)
DROID RAZR HD (vanquish/DROID RAZR HD)
DROID RAZR HD (vanquish_u/XT925)
DROID RAZR i (smi/XT890)
DROID RAZR M (scorpion_mini/XT907)
Droid Ultra (obake/XT1080)
Droid X (cdma_shadow/DROIDX)
Droid X (cdma_shadow/MB810)
Droid X (cdma_shadow/ME811)
Droid X (cdma_shadow/Milestone X)
Droid X (cdma_shadow/MotoroiX)
Droid X2 (daytona/DROID X2)
Droid X2 (daytona/Milestone X2)
DROID4 (cdma_maserati/DROID4)
Falcon (falcon_cdma/XT1031)
Falcon (falcon_umtsds/XT1033)
Flipout (umts_ruth/MB511)
Flipout (umts_ruth/ME511)
Flipout (umts_ruth/MotoMB511)
Glam XT800 (titanium/XT800)
i867 (destino/i867)
i940 (fawnridge/i940)
Iron Rock (umts_irock/XT627)
IS12M (cdma_spyder/IS12M)
Master Touch (umts_primus/XT621)
MB200 (morr/MB200)
MB501 (zepp/MB501)
MB508 (umts_sage/MB508)
MB520 (umts_kobe/MB520)
MB610 (umts_begonia/MB610)
MB611 (umts_begonia/MB611)
MB612 (cdma_kronos/MB612)
MB632 (umts_elway/MB632)
MB865 (edison/MB865)
ME632 (umts_elway/ME632)
ME863 (umts_solana/ME863)
ME865 (edison/ME865)
Milestone (A853/Milestone)
Milestone2 (umts_milestone2/A953)
Milestone2 (umts_milestone2/ME722)
Milestone2 (umts_milestone2/MotoA953)
MILESTONE3 (cdma_solana/MILESTONE3)
Moto E (condor_udstv/XT1025)
Moto E (condor_umts/XT1021)
Moto E (condor_umts/XT1023)
Moto E (condor_umtsds/XT1022)
Moto G (falcon_cdma/XT1028)
Moto G (falcon_cdma/XT1031)
Moto G (falcon_cdma/XT937C)
Moto G (falcon_umts/XT1008)
Moto G (falcon_umts/XT1032)
Moto G (falcon_umts/XT1034)
Moto G (falcon_umts/XT939G)
Moto G (falcon_umtsds/XT1033)
MOTO G (falcon_umtsds/XT1033)
Moto G Google Play edition (falcon_umts/XT1032)
Moto X (ghost/XT1049)
Moto X (ghost/XT1050)
Moto X (ghost/XT1052)
Moto X (ghost/XT1053)
Moto X (ghost/XT1055)
Moto X (ghost/XT1056)
Moto X (ghost/XT1058)
Moto X (ghost/XT1060)
Motoroi (sholest/Milestone XT720)
Motoroi (sholest/Motorola XT720)
Motoroi (sholest/XT720)
MOTOROLA ELECTRIFY 2 (cdma_yangtze/XT881)
Motorola Master Touch (umts_primus/XT621)
Motorola Master Touch XT621 (umts_primus/XT621)
Motorola MOT-XT681 (ironmaxct_cdma/Motorola MOT-XT681)
MOTOROLA RAZR M (smq_t/201M)
Motorola RAZR MAXX (cdma_spyder/Motorola RAZR MAXX)
Motorola Razr V (umts_yangtze/XT885)
Motorola Razr V (umts_yangtze/XT886)
Motorola XOOM 2 (fleming/MZ609)
Motorola XOOM 2 (pasteur/MZ617)
Motorola_i1 (iDEN/Motorola_i1)
MOTWX435KT (Triumph/MOTWX435KT)
MT620 (TAHITI/MT620)
MZ505 (Graham/MZ505)
MZ505 (graham_wifi/MZ505)
MZ604 (wifi_hubble/MZ604)
MZ605 (umts_hubble/MZ605)
MZ607 (fleming/MZ607)
MZ608 (fleming/MZ608)
MZ609 (fleming/MZ609)
MZ616 (pasteur/MZ616)
MZ617 (pasteur/MZ617)
Opus One (rubicon/Motorola Titanium)
Opus One (rubicon/Titanium)
Photon 4G (sunfire/ISW11M)
Photon 4G (sunfire/MB855)
Photon 4G (sunfire/Motorola Electrify)
Quench XT3 (XT502/Motorola-XT502)
RAZR D1 (hawk35_umts/XT914)
RAZR D1 (hawk35_umts/XT915)
RAZR D1 (hawk35_umts/XT916)
RAZR D1 (hawk35_umts/XT918)
RAZR D3 (hawk40_umts/XT919)
RAZR D3 (hawk40_umts/XT920)
Spice (sesame/XT300)
XOOM (stingray/Xoom)
XOOM (umts_everest/MZ601)
XOOM (umts_hubble/MZ601)
XOOM (umts_hubble/MZ605)
XOOM (wifi_hubble/MZ604)
XOOM (wifi_hubble/MZ606)
XOOM (wingray/Xoom)
XOOM 2 (pasteur/XOOM 2)
XOOM 2 ME (fleming/XOOM 2 ME)
XT303 (silversmart_umts/XT303)
XT305 (silversmart_umts/XT305)
XT311 (XT311/XT311)
XT316 (dominoq_umts/XT316)
XT316 (XT316/XT316)
XT317 (XT317/XT317)
XT319 (XT319/XT319)
XT320 (tinboost_umts/XT320)
XT321 (tinboost_umts/XT321)
XT389 (argonmini_umts/XT389)
XT389 (XT389/XT389)
XT390 (XT390/XT390)
XT530 (XT530/XT530)
XT531 (XT531/XT531)
XT532 (XT532/XT532)
XT535 (tinboostplus_umts/XT535)
XT535 (XT535/XT535)
XT550 (ArgonSpin/XT550)
XT550 (argonspin_umts/XT550)
XT555C (tinboostplus_cdma/XT555C)
XT556 (tinboostplus_cdma/XT556)
XT557 (tinboostplus_cdma/XT557)
XT560 (tinq_umts/XT560)
XT560 (XT560/XT560)
XT603 (cdma_pax/XT603)
XT605 (umts_jorian/XT605)
XT610 (umts_venus2/XT610)
XT615 (ironmax_umts/XT615)
XT615 (XT615/XT615)
XT626 (umts_irock/XT626)
XT627 (umts_irock/XT627)
XT687 (ironmaxtv_umts/XT687)
XT701 (choles/XT701)
XT711 (choi/XT711)
XT800+ (cg_tita2/XT800+)
XT800W (ttu_skt/XT800W)
XT806 (qilin/XT806)
XT860 (umts_solana/XT860)
XT882 (swordfish/XT882)
XT897 (asanti_c/XT897)
XT897S (asanti_c/XT897S)
XT901 (solstice/XT901)
XT905 (scorpion_mini_u/XT905)
XT910 (umts_spyder/XT910)
XT910K (umts_spyder/XT910K)
XT910S (umts_spyder/XT910S)
Click to expand...
Click to collapse

Related

ICS-leak for motorola atrix usable for 2x

Today a ICS-leak for the motorola atrix came out. Since the Atrix shares the Tegra2-chip, can bits of that leak be used for the O2x?
No.
10 chars
Link? Because AFAIK there's no leak for the Atrix. I think you're thinking of the leak for the GSM RAZR, which is OMAP 4 and not Tegra 2.
Jotokun said:
Link? Because AFAIK there's no leak for the Atrix. I think you're thinking of the leak for the GSM RAZR, which is OMAP 4 and not Tegra 2.
Click to expand...
Click to collapse
I looked up the article and I can't believe that I have read it that bad! It says Razr and does not mention the Atrix haha! Razr of course has OMAP4.
Sorry people!
All discussions here http://forum.xda-developers.com/showthread.php?t=1347118

[Q] Moto X?

Now that the Moto X is getting a fact, and more and more is known about specs and prizes (http://www.thefullsignal.com/motoro...rola-x-moto-x-specs-price-release-date-rumors) I wonder:
1, will Moto give us also the 4.3 update (and if yes, when?)?
2, if no 4.3 update for the Razr-i: do you think it is worth to trade our beloved Razr i for a Moto X; pretty cheap, with the newest Android version, fancy sensors -but with a lower clock (benchmark?) speed than the Razr i?
Any ideas/ feelings about?
I think there will be no 4.3 for razr i. And about Moto X - I will wait until it´s available and well tested. I will not give up the advantages of my razr i like excellent signal reception and long standby. If the Moto X can do better (or at least equal), I will think again.
bmszabo said:
Now that the Moto X is getting a fact, and more and more is known about specs and prizes (http://www.thefullsignal.com/motoro...rola-x-moto-x-specs-price-release-date-rumors) I wonder:
1, will Moto give us also the 4.3 update (and if yes, when?)?
2, if no 4.3 update for the Razr-i: do you think it is worth to trade our beloved Razr i for a Moto X; pretty cheap, with the newest Android version, fancy sensors -but with a lower clock (benchmark?) speed than the Razr i?
Any ideas/ feelings about?
Click to expand...
Click to collapse
my motorola experience with updates is bad (i was a defy owner and only thanks cyanogenmod and quarx (the dev) i could realize updates to jb4.1 (cm10)).
mabe motorola will change this behaviour now because owned by google, but i don't believe it. i believe the razr i hardware can run jb4.3 and maybe even the future android 5, but my motorola experience makes me fear, that we will never see those updates.
Well I hope at the time when 4.3 is released. cyanogenmod will hopefully be available for the razr i :fingers-crossed:
+1
Any real custom rom would be great.
Gesendet von meinem XT890 mit Tapatalk 4 Beta
it does not depend on 4.3 but on porting CM to Intel-cpu.
via RazR I & Tapatalk 4
ICuaI said:
it does not depend on 4.3 but on porting CM to Intel-cpu.
via RazR I & Tapatalk 4
Click to expand...
Click to collapse
Which brings up the next question :
Would the multi-core CPU of the Moto X beat our Medfield CPU in terms of speed, snappiness? As for me: fastest phone (Iphone/android) I ever had!
Why wouldn't they? Intel's got libs ready, Motorola is about to come back to life and this phone is not even a year old... It should be updated, and if it doesn't, they should at least release the libs so cm can do it. Now Motorola is owned by Google, things should change
If not 4.3 i'd be happy with 4.2

[Q] porting Moto apps of Moto X 2014 to Moto X 2013

is there a porting of the Motorola apps of Moto X 2014 to our Moto X 2013 ?
like Moto Voice and Moto Display, after the recent update Motorola give us only the sync with Moto 360, but if we want the new features see in the Moto X 2014's spot on youtube there is the app to download and install on my old Moto X ??
toroloco73 said:
is there a porting of the Motorola apps of Moto X 2014 to our Moto X 2013 ?
like Moto Voice and Moto Display, after the recent update Motorola give us only the sync with Moto 360, but if we want the new features see in the Moto X 2014's spot on youtube there is the app to download and install on my old Moto X ??
Click to expand...
Click to collapse
as of right now there is nothing. if you install the apk for the new moto voice it will install but you cannot finish settign up the hotword detection probably because of hardware issues.
When motorola announced the new X they said they will bring the moto suite to deviced whose hardware will support it. but i see no reason why the 2013 moto x won't get the update seeign as those its hardware was designed with voice recognition in mind. the chip has 2 cores set aside for that purpose but for now time will tell. im sure if for some reason moto doesnt bring the suite to the old X someone will than port them to the old X
i find it...
http://forum.xda-developers.com/moto-x/themes-apps/moto-voice-2da-generacion-moto-x-4-4-4-t2871296/page12#post55605830
toroloco73 said:
i find it...
http://forum.xda-developers.com/moto-x/themes-apps/moto-voice-2da-generacion-moto-x-4-4-4-t2871296/page12#post55605830
Click to expand...
Click to collapse
Can you also find the Q&A forum for your questions in future?
Thread moved.

Droid Turbo Service Issues on CM12.1 Snapshot 1/27/16

I seem to be having issues where my service does not seem to be as strong on CM12.1 compared to the stock ROM. Any idea on a fix for this?
IMHO, common problem on almost every device with CM. The difference with stock is noticable but not huge. (Saw it on xt912, xt926, xt1080 etc.)
It is unfortunate as this issue is the difference between getting LTE and 3g. Back to stock I guess...
I get LTE just fine
Sent from my DROID Turbo using Tapatalk
nubia11 said:
I get LTE just fine.
Click to expand...
Click to collapse
Same here. To the op: what carrier do you have? Have you flashed the appropriate radio/BL from the CM12.1 quark thread? It's in the op there.
http://forum.xda-developers.com/showthread.php?p=64074102
I tried everything... Finally just installed freeks ROM... Not much dev in turbo huh?
Not overly much, but then again my old phone was a Casio Commando 4G... You want moribund development try those forums. Yikes!
Also keep in mind that the Moto Maxx XT1225 forum is very helpful as well, being that it's the basically the same phone. If the answers aren't here, they are likely there.
And fwiw I haven't had any problems be it with computerfreek, cm, mokee, or resurrection. I suspect there's more than a few of us lurking about without issues as well. So I figure the devs are doing pretty good. Then again, coming from Casio-land I instinctively expect very little. Having at least 4 roms with varying degrees of activity is awesome as far as I'm concerned.
MazinDLX said:
I tried everything... Finally just installed freeks ROM... Not much dev in turbo huh?
Click to expand...
Click to collapse
You just aren't looking in the right place. All the Quarks have the same hardware, and except for the Droid Turbo they all had unlock-able bootloaders from the very beginning via Motorola websitie. So, there's tons of development.
For almost a year the Quarks were all in this forum. But because the Droid Turbo was locked down (per orders from Verizon), the Droid Turbo people got mad because they saw all this neat dev stuff they couldn't get. So, they petitioned XDA mods to split the forum into the "dead" Droid Turbo dev forum and the active rest-of-the-Quarks forum.
The forum split happened in September 2015...
Then, guess what? About two months later, exploit was found to unlock the Droid Turbo bootloaders! So, now all the Droid Turbo users who want custom ROMs, custom kernels, etc, have to trek over to the rest-of-the-Quarks forum -- aka Moto Maxx forum, but it's also the Moto Turbo forum. Yeah, there's TWO Quarks called Turbo.
After the Droid Turbo bootloader unlock, the CM dev started a CM thread over here --but it's the SAME ROM as in the Moto Maxx forum, and most people (even Droid Turbo users) just post over there.
_______
The only difference in all the Quarks ("international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, Droid Turbo XT1254) are the radios. (In fact the U.S. Moto Maxx XT1250 and Droid Turbo XT1254 are identical in every way, including the radios! Even the same FCC ID.)
The DEVICE called the Droid Turbo was NEVER exclusive to Verizon. The exact same phone is/was sold by U.S regional CDMA/LTE carriers as the U.S . Moto Maxx. Motorola even used the "Turbo" name again for another Quark. Only the "Droid" name was exclusive, because Verizon licenses that name from LucasArts. So, yeah you can only buy a "Droid Turbo" from Verizon, but you can buy the EXACT SAME PHONE (with the same bands) from another carrier in the U.S. Put a Verizon SIM card into a U.S. Moto Maxx and it runs on Verizon just like a non-Verizon Nexus 6...
It would be like Samsung calling their Galaxy S6 the "S6", everywhere but Verizon. For Verizon, it would be called the "Yabba Dabba Do" phone. And Verizon puts out press releases: The "Yabba Dabba Do" phone is EXCLUSIVE TO VERIZON! It's still just a Galaxy S6! Oh, but the Verizon version would have a locked-down bootloader...
____________
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Only the Quark radios are different. Everything else is identical, which is why all these Quark ROMs below work on all the Quarks -- including the Droid Turbo XT1254 (with unlocked bootloader):
CM12.1 ( @Skrilax_CZ dev)
Resurrection Remix ( @baybutcher27 dev)
Mokee (AOSP ROM, @baybutcher27 dev)
Xperia Z5G
as well as custom kernel BHB27 ( @baybutcher27 dev).
Droid Turbo owners are using all of these above. But except for the CM dev, the devs aren't posting duplicate threads over here in the Droid Turbo forum. You have to go over to the Moto Maxx forum to participate.
ChazzMatt said:
You just aren't looking in the right place. All the Quarks have the same hardware, and except for the Droid Turbo they all had unlock-able bootloaders from the very beginning via Motorola websitie. So, there's tons of development.
For almost a year the Quarks were all in this forum. But because the Droid Turbo was locked down, Droid Turbo people got mad because they saw stuff all this neat stuff they couldn't get. So, they petitioned XDA mods to split the forum into the "dead" Droid Turbo dev forum and the active rest-of-the-Quarks fourm.
The forum split happened in September 2015...
Then, guess what? About two months later, exploit was found to unlock the Droid Turbo bootloaders! So, now all the Droid Turbo users who want custom ROMs, custom kernels, etc, have to trek over to the rest-of-the-Quarks forum -- aka Moto Maxx forum, but it's also the Moto Turbo forum. Yeah, there's TWO Quarks called Turbo.
After the Droid Turbo bootloader unlock, the CM dev started a CM thread over here --but it's the SAME ROM as in the Moto Maxx forum, and most people (even Droid Turbo users) just post over there.
_______
The only difference in all the Quarks ("international" Moto Maxx XT1225, Moto Turbo XT1225, U.S. Moto Maxx XT1250, Droid Turbo XT1254) are the radios. (In fact the U.S. Moto Maxx XT1250 and Droid Turbo XT1254 are identical in every way, including the radios! Even the same FCC ID.)
The DEVICE called the Droid Turbo was NEVER exclusive to Verizon. The exact same phone is/was sold by U.S regional CDMA/LTE carriers as the U.S . Moto Maxx. Motorola even used the "Turbo" name again for another Quark. Only the "Droid" name was exclusive, because Verizon licenses that name from LucasArts. So, yeah you can only buy a "Droid Turbo" from Verizon, but you can buy the EXACT SAME PHONE (with the same bands) from another carrier in the U.S. Put a Verizon SIM card into a U.S. Moto Maxx and it runs on Verizon just like a non-Verizon Nexus 6...
It would be like Samsung calling their Galaxy S6 the "S6", everywhere but Verizon. For Verizon, it would be called the "Yabba Dabba Do" phone. And Verizon puts out press releases: The "Yabba Dabba Do" phone is EXCLUSIVE TO VERIZON! It's still just a Galaxy S6! Oh, but the Verizon version would have a locked-down bootloader...
____________
Only the Quark radios are different. Everything else is identical, which is why all these Quark ROMs below work on all the Quarks -- including the Droid Turbo XT1254 (with unlocked bootloader):
CM12.1 ( @Skrilax_CZ dev)
Resurrection Remix ( @baybutcher27 dev)
Mokee (AOSP ROM, @baybutcher27 dev)
Xperia Z5G
as well as custom kernel BHB27 ( @baybutcher27 dev).
Droid Turbo owners are using all of these above. But except for the CM dev, the devs aren't posting duplicate threads over here in the Droid Turbo forum. You have to go over to the Moto Maxx forum to participate.
Click to expand...
Click to collapse
Thanks for explaining this in such detail. A lot of people are probably surprised to know this. It's been going on for many generations of the Android phone,and can get confusing when forums start splitting up. Nice detail!!
Sent from my DROID Turbo using Tapatalk

ROMs for turbo?

Was wondering what the best ROMs are for the turbo?
Sent from my XT1254 using Tapatalk
It depends on what your preference is.
If you want an enhanced stock ROM computer freaks is the way to go.
If you are a fan of cyanogenmod than I reccomend CM13,
If you like lots of customization options Resurrection Remix is the way to go. All the ROMs available are great choices its just up to you which one really suits you best
jb14813 said:
Was wondering what the best ROMs are for the turbo?
Click to expand...
Click to collapse
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
http://forum.xda-developers.com/droid-turbo/development/roms-t3347701
Here's a list of all current ROMs for Quarks, Lollipop and Marshmallow. The threads are listed. You can go in, read user comments.
They work for the Moto Turbo, Moto Maxx, and Droid Turbo. Yeah, there's two Motorola Quarks called "Turbo". But these ROMs work for ALL the Quarks.

Categories

Resources