Related
[SIZE=+3]Motorola
Droid X
2010[/SIZE]
[SIZE=+2][INDEX][/SIZE]
[SIZE=+2]Helpful Information[/SIZE][SIZE=+1]Welcome, this thread has been created to encompass everything you may need for your device. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread, ask in the [HELP THREAD] Ask ANY Question. Noob Friendly Thread or create your own thread in the General forum. Do not use this as a general help thread.[/SIZE]Click on a Link below for More Info
Official Motorola Droid X Home Page
Basic Device Information
Official Stock Firmware
Device Tools, Root/Un-root/Un-brick methods
Custom ROMs
Kernels & Radios
MODS, GUIDES and Misc
*Forum Rules | New Users Guide | XDA Tour | Report PostsPlease look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Basic Device Information
Droid X
Codename: shadow
Frequently Asked Questions -Motorola Droid X 2015 by sd_shadow
There are 3 Variants of the X
Same hardware, different firmware.
MB810: Droid X - Verizon - Phone Arena - GSM Arena -
MB809: Milestone X - Non-Verizon -
ME811: Milestone X - Non-Verizon - PDAdb.net -
Factory Reset and other special features
Enable / Disable Data - DROID X by Motorola
Can’t text, sync, or download anything from the play store
Safe Mode - DROID X by Motorola
Safe Mode temporarily disables all apps that have been installed via Google Play. Performing this troubleshooting step is necessary to determine whether a 3rd party app is the cause of an Operating System / App issue
Perform a Factory Data Reset AKA Hard Reset
Hard Reset - DROID X by Motorola Preferred method (in settings) Alternate (android recovery)
Hard Reset via Android Recovery- DROID X by Motorola
Import / Export Contacts to SD Card - DROID X by Motorola
USB Debugging Mode - DROID X by Motorola
SD Memory Card Formatting - DROID X by Motorola
YouTube Video How to bypass activation screen on the Droid X -Mike Simpkins
Official Stock Firmware
There may be other mirrors listed in my
[INDEX]Motorola Unbricking Tools
Firmware Mirror Links
http://motofirmware.center/files/
https://sites.google.com/site/motosbf/droid-x-sbf-files
http://goo.gl/X8hkXA (m.ksy's Mega)
http://www.androidfilehost.com/?a=show&w=files&flid=5529
[SBF and Update] Gingergread 2.3.4 SBF for Droid X MB810 by daywalker04
http://d-h.st/users/sd_shadow
Firmware Details
File Names and md5 checksums (checksums very depending on how they were zipped)
Android 2.1 System Version 1.13.604 (the_gift)
MD5 (the_gift.zip) = b6fae8c1d7badd4829177fd71f31ac4c
Android 2.2 System Version 2.3.15 (the_gift2)
MD5 (the_gift2.zip) = 2e067f1e8fbe3d4e20b43b0e49f22970
Android 2.2.1 System Version 2.3.320 Full (Happy_Holidays_From_TBH)
MD5 (Happy_Holidays_From_TBH.zip) = 7cd6d2bad1f7550d8a066822d9b3cf2a
Android 2.2.1 System Version 2.3.340 System Only (SHADO_X6_2.3.34_SYSTEM-ONLY)
MD5 (SHADO_X6_2.3.34_SYSTEM-ONLY.zip) = 389050194d9572276ec712e287675133
Android 2.2.1 System Version 2.3.340 (VRZ_MB810_2.3.34_1FF_01)
MD5 (VRZ_MB810_2.3.34_1FF_01.zip) = 48c0d5cb3805497a6cbaf120dfb63002
Android 2.3.3 System Version 4.5.596 (VRZ_MB810_4.5.596_1FF_01)
MD5 (VRZ_MB810_4.5.596_1FF_01.sbf.zip) = 878302e99392edd41fbdc3b4d7b08c66
Android 2.3.3 System Version 4.5.602 (VRZ_MB810_4.5.602_1FF_01)
MD5 (VRZ_MB810_4.5.602_1FF_01.sbf.zip) = 039f0e39bc6c92bcd92c0d1d86350784
Android 2.3.3 System Version 4.5.605 (VRZ_MB810_4.5.605_1FF_01)
MD5 (VRZ_MB810_4.5.605_1FF_01.sbf.zip) = eeb8b2c2f05a9162f4536063c3f22ac5
Android 2.3.4 System Version 4.5.621 (1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf.zip)
MD5 (1FF-p3a_shadow_cdma_shadow-user-2.3.4-4.5.1_57_DX8-51-120111-test-keys-signed-Verizon-US.sbf.zip) =
06bbf7ee86c0ed64654e14bcb84c4aed
@palmbeach05 has newer cm7.2 on his gdrive. I lost the link though lol
Tap'd from my Unicorn covered Bionic
Device Tools, Root/Un-root/Un-brick methods
[SIZE=+1]Rooting Method[/SIZE]Framaroot app mirror posted here, a [Video] Super Easy Droid X, Droid 2 Rooting app
[SIZE=+1]Bootstrap Recovery[/SIZE]
[HOW TO] Install/Use Droid 2/X/3 Bootstrap
[SIZE=+1]Restoring Original Stock Firmware/SBFs[/SIZE]
RSD Lite (Windows only) see my page Using RSD Lite to flash a .SBF to restore (Stock Rom)
ezSBF bootable CD or usb flash drive (Windows/Linux/Mac) DX ezSBF & Root 2.3.4/4.5.621
sbf_flash (LInux/Mac) see http://blog.opticaldelusion.org/search/label/sbf_flash
Custom ROMs
[SIZE=+1]Google Apps-Gapps[/SIZE]Best to use the Devs recommended Gapps, but sometimes links are down... Gapps Mirrors
[SIZE=+1]KitKat/ Android 4.4 Roms/ [/SIZE]
NEW [KitKat] LiquidSmooth v3.2 - KitKat 4.4.4 for Droid X
[KitKat] Cm11-Kanged
[Kitkat] CM11 Android 4.4 for the Droid X
[SIZE=+1]Jellybean/ Android 4.1 Roms[/SIZE]
None
[SIZE=+1]ICS/ Android 4.0 Roms[/SIZE]
Liquid ICS v2.1 [UNOFFICIAL] - 2/15/14
ShadowMod for DX (2013-03-09)
LiquiKang (4/22/13), MiKangyUI v4 (1/30/13)/ , GummyKang (01/30/13), AOKP-Kanged?(2/19/13),, CMKang (02/06/13) /
MIUI.us_Shadow_2.7.6_4.0_Eng_Deo_ZipA_Signed_BeansTown106 MIUI_gapps_2_4_27.zip
aokp_shadow-beta-b39.zip
Wifi only Roms
AOKPMedia v1.5 - DX - 2/15/13 by Dubbsy
LiquiMedia beta1 - DX by Dubbsy, 21 Feb 2013
[SIZE=+1]Gingerbread/ Android 2.3 Roms [/SIZE]
MIUI DefX by @Wizard0f0s
Pooka's CM7 flash with (7.1 Gapps) / optional CM7_fixes
OpenAndroid-VXLR V2.2.0 Stable w/Aroma
Simply Stunning X Gingerbread v2.2 - 10/17/2011
(UN)Official CM7.2 RC (2012-08-14) ported for the 621 update by @palmbeach05 post
Mirrors CM-7.2-(UN)OFFICIAL-_20140703.zip --- MD5: c571dd02738bc97b3d5e95d202d7847a ---DevHost----Drive---XDA---
CM7.2-RC_GB_kernel_original.zip ---MD5 Sum: e92264e377981f013e8534317dccd948 ---DevHost ---Drive---XDA---
sd_shadow said:
Those are the files he pm'd me a not long ago
Click to expand...
Click to collapse
Oh okay. Those must be the more official ones then. He sent me some kangs while back that had dif launchers and browsers. That was awhile ago now though
Tap'd from my Unicorn covered Bionic
Kernels & Radios
Kernels & Radios
sd_shadow said:
I'm more than happy to add to the list, just need a link...
Click to expand...
Click to collapse
I think I may have them on my droid x's SD card....I can upload to gdrive for you to mirror but my x is 3hrs away cuz I'm out of state
Tap'd from my Unicorn covered Bionic
MODS, GUIDES, and Misc
MODS, GUIDES, and Misc
[SIZE=+1]Repair Hardware[/SIZE]
Motorola Droid X Take Apart Repair Guide
sd_shadow said:
Don't even care if it has your silly echo scripts
Click to expand...
Click to collapse
Echo scripts? Lol
Tap'd from my Unicorn covered Bionic
Oggie7797 said:
Echo scripts? Lol
Tap'd from my Unicorn covered Bionic
Click to expand...
Click to collapse
wrong word
ui_print("Looking through contacts...");
Click to expand...
Click to collapse
sd_shadow said:
wrong word
Click to expand...
Click to collapse
Heehee... flashing can be boring (I usually go make a sandwich or get a drink) so I figured why not make it a lil more fun..
Tap'd from my Unicorn covered Bionic
sd_shadow said:
I'm more than happy to add to the list, just need a link...
Click to expand...
Click to collapse
If i'm remembering correctly, the second ROM i sent you was the final kang he's talking about. I haven't been able to get back to it and do more work with it since 2.3 support is dying and my skills only go so far. Plus the original build files was on the laptop that died oh so long ago when i started getting cm11 spun up for us before m.ksy and aaahhh took over.
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
If i'm remembering correctly the original build files was on the laptop that died oh so long ago...
Click to expand...
Click to collapse
May it rest in pieces....
Tap'd from my Unicorn covered Bionic
Added: New to Droid X? see Frequently Asked Questions -Motorola Droid X
Major thread reorganization.
Not complete , but big changes are done.
some cm links
http://web.archive.org/web/20161224225455/https://download.cyanogenmod.org/?device=shadow
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best
Dear all,
Currently, I am getting into the development on Android Wear with Moto 360 (1st gen). I got two questions want to solve.
Q1 : I download the source code of Android Wear (Branch : android-wear-5.1.1_r1) from AOSP, but I cannot compile it successfully.
Is it due to the "CLOSED SOURCE CODE" of Moto 360 ? Because I know Android Wear is "PARTIALLY OPEN SOURCE", so I wonder
is this reason affects the process of compile ?
(The compile error indicates [fatal error : hardware/bt_common_types.h : No such file or directory])
Q2 : I would like to change the default behavior of Android Wear on Moto 360 when it find out the device has no GPS functionality.
Is this modification related to the "CLOSED SOURCE CODE" of Moto 360 so that it is impossible to do this modification ?
Thanks for your replies and comments.
Best,
Mike
thought id share this with you guys
https://www.youtube.com/watch?v=wJYXx3J-AWc
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Sent from my XT1254 using XDA Labs
I would expect it to arrive in March, probably with some bugs.
jeffkahlo777 said:
I want Android 8.0 Oreo for Motorola Moto Maxx/DROID TURBO, waiting for LineageOS 15, Resurrection Remix 5.9, etc.
Click to expand...
Click to collapse
It will take @bhb27 coding the current Motorola Marshmallow Quark kernel to Oreo -- the same way he coded it to work for Nougat.
Our previous CM dev @Skrilax_CZ did the original work back in early 2015, first coding Quark Motorola Kitkat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.
@bhb27 started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel @Skrilax_CZ coded. You could use 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install @bhb27's custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.
(For our Quarks, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When Sunshine unlocked the Droid Turbo bootloader @Skrilax_CZ re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quarks. The kernel is the foundation.)
Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)
By this time @bhb27 had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.
When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And @bhb27 did the work to let Nougat ROMs use that kernel.
Will be the same thing with Oreo. But @bhb27 still has to code it to work smoothly with Oreo.
Also, there is no more CM. We now have LOS as the "base". @bhb27 does not release official LOS ROMs, but that's where the device kernel files go that all devs pull from.
So, @bhb27 will use Marshmallow kernel in LOS Oreo tree to make a stock kernel for all ROMs. At that point he will release an Oreo ROM based on that work. (Right now he's the dev for both RR and crDroid ROMs. Last year he surprised us by releasing then-new Nougat crDroid first, whereas he had been dev for Marshmallow RR and Mokee, and RR was his favorite.)
@bhb27 will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.
After he releases his Oreo kernel work, then other Quark devs can use that stock LOS Oreo Quark kernel to release their Oreo ROMs.
The kernel will be the foundation of any Oreo ROMs and it will all depend on @bhb27.
But don't pester him. It will be ready when it's ready.
__________
TLDR: @bhb27 is the man. He'll do the Oreo-compatible stock kernel first and then the first Oreo custom ROM. Everyone else will then follow with other ROMs.
ceelos218 said:
thought id share this with you guys
https://www.youtube.com/watch?v=wJYXx3J-AWc
Click to expand...
Click to collapse
I going have to check with my local church about that, I may not be able to work on Oreo....
how comes up with those videos
https://www.youtube.com/watch?v=twZggnNbFqo
bhb27 said:
how comes up with those videos
https://www.youtube.com/watch?v=twZggnNbFqo
Click to expand...
Click to collapse
first, technically a cross in general and period is sun god worship in itself. so if your church doesn't have any issues with a cross i don't see why it would care about a double cross.
second, that double cross is just on the oreo. it is the nabisco symbol. so if it is evil so is nabisco
I agree with you though where do people come up with this stuff
Safer, smarter, more powerful! All with the Movie trailers voice. Coming this fall*
*TBD
ready to provide support!
bhb27 said:
I going have to check with my local church about that, I may not be able to work on Oreo....
Click to expand...
Click to collapse
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
I got impatient and I tried to build LOS 15 using the existing kernel. It didn't work (because of course it didn't).
GeekyTanuj said:
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
Click to expand...
Click to collapse
you need to search on how is done what you wanna to do, simple things as build a ROM there is plenty of tutorial, kernel not so many but there is tutorial + my how to on kernel tread helps you to understand how I do build a kernel (of course is needed basic shell and/or kernel Knowledge, those are available is searches) or the readme in the device tree can explain the basic, I do this for years this is not a thing I learn over night took me years to now a little thing, some times took me weeks to do a very simple thing to work the things is if you wanna don't ever give it up, rest and try again later but don't just give it up, so you search about, like I wrote there is dedicated xda thread on how to build tihngs, you find those and post yours problems there, if is a quark specific help, open yours on general help thread and post the specific problem you have, but really search before you post anything somethings are simple like I wrote is just a question of patiently read and do exactly hat the tutorial says.
TheSt33v said:
I got impatient and I tried to build LOS 15 using the existing kernel. It didn't work (because of course it didn't).
Click to expand...
Click to collapse
source is not ready yet for any device, even after it may not be ready for quark for some time... + kernel, device and vendor changes are needed...
GeekyTanuj said:
Mr bhb27(@bhb27) I would love to work upon the device once you're up for the kernel sources for our device for Oreo and I still want to work upon our quark and a plethora of Moto collection I have (Moto x 2013 , Moto G 2013 , Moto E 2014 , Moto G 2014 , Moto E 2015 LTE & Moto X Force ) .... And the collection will increase over time...
But the major problem I have is don't have any knowledge about compiling a ROM from the device tree and kernel sources (complete noob about that!) But would love to increase my knowledge about Android ROM development from the zero-level,so wonder if you could help me out!
Click to expand...
Click to collapse
Well I've looked in the same way of you and now I've made it (twice actually (AEX and ViperOS)). Everything that I learned it was just searching here in XDA, taking a look on some videos at YouTube and Google it. But we can't forget the stuff necessary, like a strong computer with Linux (any distro it's fine) or Google Cloud, and, of course, a good internet and patience.
Just building it's simple when you look for the "real" development (working in kernels, device trees, and vendors)
[EDIT]Have a bunch of good ROMs to build. Try look for someone that you liked.
It feels like I'm getting really close, but I didn't get to test to see if it boots . Hopefully I can get it to recognize the device, install, then boot! If I get something stable then I will share it soon.
...
Hey @bhb27. Sorry to bug you, but quick question. I got the kernel to compile (and ROM) but I still get the unfound device (error 7 in TWRP). If I bypass and flash it anyhow, I see my boot logo, then it just keeps resetting back to the bootloader.
I'm sure I've just configured something incorrectly in the kernel, but do you have any suggestion on how I could trace it? It almost makes me think it's not even finding the image. I've only seen methods involving a custom ttl terminal board when I Google it (other than trying to edit the kernel command line using fastboot). Don't want to take up your time but just curious if you had any idea. I'm betting it will just require your knowledge at a later time (since sources aren't ready other than my modifications).
Thanks again.
calsurferpunk said:
Hey @bhb27. Sorry to bug you, but quick question. I got the kernel to compile (and ROM) but I still get the unfound device (error 7 in TWRP). If I bypass and flash it anyhow, I see my boot logo, then it just keeps resetting back to the bootloader.
I'm sure I've just configured something incorrectly in the kernel, but do you have any suggestion on how I could trace it? It almost makes me think it's not even finding the image. I've only seen methods involving a custom ttl terminal board when I Google it (other than trying to edit the kernel command line using fastboot). Don't want to take up your time but just curious if you had any idea. I'm betting it will just require your knowledge at a later time (since sources aren't ready other than my modifications).
Thanks again.
Click to expand...
Click to collapse
you need to update the kernel to boot O, there is a lot of changes to it, like I wrote before shamu and victara must have the changes... shamu lineage source are update for O already, victara is not update yet but you may find the repo of developer releasing the ROM on they threads...
bhb27 said:
you need to update the kernel to boot O, there is a lot of changes to it, like I wrote before shamu and victara must have the changes... shamu lineage source are update for O already, victara is not update yet but you may find the repo of developer releasing the ROM on they threads...
Click to expand...
Click to collapse
Thanks for your patience. I've been looking at a bootable Oreo Shamu build source. I'm guessing it involves lots of kconfig changes and such, just wanted to see if you thought it was anything simple (which I doubted). I appreciate your input.
calsurferpunk said:
Thanks for your patience. I've been looking at a bootable Oreo Shamu build source. I'm guessing it involves lots of kconfig changes and such, just wanted to see if you thought it was anything simple (which I doubted). I appreciate your input.
Click to expand...
Click to collapse
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
bhb27 said:
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
Click to expand...
Click to collapse
Thanks. I'll check it out and see how far I can get. Anything I can contribute to getting it ultimately working will be worth it. I had to make a good number (not major) of device changes already so I'm comfortable with that as well.
bhb27 said:
this is what I'm toking about, they start on September 8
https://github.com/LineageOS/android_kernel_moto_shamu/compare/518881a...f59682b
you can easy cherry-pick them but they will probably conflict and you will need to fix the conflicts and probably add something else to be able to build as the source are not 100% equal that repo may have a change be used by those new changes that doesn't exist on quark yet and some of those like the SU one's alredy exist so you can skip them... binder changes can make stock libraries stop work so many features will need rework...
there may also be device tree changes needed to be done related t those kernel changes... after you can boot probably will be need to work on a lot of libs or not if the kernel binder changes don't mess up the vendor libs features...
Click to expand...
Click to collapse
Hey again @bhb27. I just finished incorporating all of those changes and updating other files (mainly in the fs. directory). It still just starts to boot, but quickly goes back to the bootloader again. Any other suggestions on what I could check to see what causes that?
I'm leaning towards a file partition change that it doesn't recognize now, but just a random guess. It still doesn't install the .zip either (still error 7) unless I modify the device check assert (making me think it can't find the build.prop (due to some other format/partition change).
Here's a link to my repos and the .zip in case it helps. Thanks again for the help but I understand if you don't want to get too involved at this point.
Repo: https://github.com/calsurferpunk
Zips: https://androidfilehost.com/user/?w=settings-dev-files&flid=218810
Update 1: I'm also checking to see if there was anything specific about the cm-14.1 to lineage-15.0 device tree and it looks like there might be a little more.
https://github.com/LineageOS/android_device_moto_shamu/compare/lineage-15.0
Update 2: It looks like everything should be good with the device setup as well. I'm wondering if it's more of a TWRP issue since I've seen references of needing a custom version to install AOSP 8.0/LOS 15 in other device forums.
Update 3: I noticed there were a couple kernel config flags missing according to:
https://source.android.com/devices/architecture/kernel/modular-kernels#core-kernel-requirements
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
Added those, but still no luck. I've been comparing device/kernel files locally in hopes of finding a key difference, but after seeing the kernel requirements match I'm still pretty lost.
Update 4: I was able to find the failed kernel boot log under:
/sys/fs/pstore/console-ramoops
It looks like the error preventing booting is from these lines (attached):
...
1.586240,2] init: init first stage started!
[ 1.586318,2] init: First stage mount skipped (missing/incompatible fstab in device tree)
[ 1.586345,2] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
...
[ 2.131621,0] ueventd: fixup /sys/devices/virtual/stm401/stm401_as/rv_6axis_update_rate 1008 1008 660
[ 2.131679,0] ueventd: fixup /sys/devices/virtual/stm401/stm401_as/rv_9axis_update_rate 1008 1008 660
[ 2.145657,0] drv260x driver found: drv2605.
[ 2.146248,0] drv260x probe work succeeded[ 2.246181,0] ueventd: Coldboot took 0.310706 seconds
[ 2.255910,3] init: Command 'wait_for_coldboot_done' action=wait_for_coldboot_done returned 0 took 262.268ms.
[ 2.255959,3] init: processing action (mix_hwrng_into_linux_rng)
[ 2.256179,3] init: Mixed 512 bytes from /dev/hw_random into /dev/urandom
[ 2.256212,3] init: processing action (set_mmap_rnd_bits)
[ 2.256263,3] init: Cannot open for reading: /proc/sys/vm/mmap_rnd_bits
[ 2.256287,3] init: Unable to set adequate mmap entropy value!
[ 2.256303,3] init: Security failure...
[ 2.256318,3] init: panic: rebooting to bootloader
[ 2.256336,3] init: Reboot start, reason: reboot, rebootTarget: bootloader
[ 2.256367,3] init: android::WriteStringToFile open failed: No such file or directory
[ 2.256391,3] init: Shutdown timeout: 6
[ 2.256422,3] init: terminating init services
[ 2.256476,3] init: Terminating running services took 0.000134532 seconds with remaining services:0
[ 2.256892,3] init: vold not running, skipping vold shutdown
[ 2.357286,3] init: powerctl_shutdown_time_ms:100:0
[ 2.357305,3] init: Reboot ending, jumping to kernel
[ 2.658702,0] mdss_fb_release_all: try to close unopened fb 1! from pid:1 name:init
[ 2.658715,0] mdss_fb_release_all: try to close unopened fb 0! from pid:1 name:init
[ 2.659433,0] Restarting system with command 'bootloader'.
[ 2.659442,0] Current task:init(1) Parent task:swapper/0(0)
[ 2.659457,0] Going down for restart now
[ 2.660756,0] Calling SCM to disable SPMI PMIC arbiter
It appears to be related to not finding the file partitions and this: https://lkml.org/lkml/2015/12/21/336 and https://lkml.org/lkml/2015/10/28/828.
Enjoy new Motorola Apps and some features from Moto G6/Z3P in your Moto Z2 Play.
- Need bootloader unlocked and TWRP installed.
* Mandatory: Make backup from system and boot partitions in TWRP, restore this backup to phone then install this mod.
Don't Factory Reset after this mod is installed. Use original system for that and install only after device is configured .*
This zip is only for Moto Z2 Play with Stock Oreo Rom.
What's New:
- Moto App 6.0.73
- Moto Actions 05.013.1.0-O (Enabled Quick Screenshot)
- Moto Camera 6.2.18.2
- Moto Display 06.091.0 (Enabled Attentive Display)
- Moto Help 5.9.11
- Moto Key 2.00.0183
- Moto Mods Manager 02.05.018
- Moto Suggestions 0.3.27
- Moto Voice Beta 08.18.0.0.0.51.1
- Motorola Audio Effects 02.01.0099
- Motorola Email 00.08.0077
- Motorola Face Unlock 01.02.0257
- Motorola FM Radio 02.02.0508
- Motorola Gallery 530034 (Enabled All Features)
- Motorola Launcher 8.1.0 (Enabled Rounded Google Search Widget, Grid Layout 5x5 or 4x5 and Notification Dots Colored)
- Motorola Notifications 7.8.010
- Motorola Time Weather 1.03.04 (Enabled Red Color in Low Battery Circle)
Extra Tweaks:
- New layout from Moto Devices 2018 (Enabled Rounded Corners and New StatusBar Icons)
- Google Miracast Service (Enabled Screen Mirroring)
Download:
New-Moto-Apps-Oreo-20181128.zip
Credits:
Motorola
Me (Junior Passos)
:fingers-crossed:
Can anyone confirm these work? Did you actually modify these apps or do they just install right over existing apps?
MishaalRahman said:
Can anyone confirm these work? Did you actually modify these apps or do they just install right over existing apps?
Click to expand...
Click to collapse
It works perfectly, I have already shared my work in other places in Brazil and who installed it, confirmed that everything is working.
Some applications I had to modify to enable the new features in Moto Z2 Play, others were through updating in apps by Motorola itself that makes fragmentation the features on their devices.
Can you post screenshots of the new features?
New Motorola apps Oreo 2018
Everything working perfectly. Stayed show!
New apps
Junior Passos said:
It works perfectly, I have already shared my work in other places in Brazil and who installed it, confirmed that everything is working.
Some applications I had to modify to enable the new features in Moto Z2 Play, others were through updating in apps by Motorola itself that makes fragmentation the features on their devices.
Click to expand...
Click to collapse
thank you, great work is working properly here.:legal:
MishaalRahman said:
Can you post screenshots of the new features?
Click to expand...
Click to collapse
Screenshots added.
MishaalRahman said:
Can anyone confirm these work? Did you actually modify these apps or do they just install right over existing apps?
Click to expand...
Click to collapse
Yup, tested and working mate
can't make it work, i did a back up from system and boot and then restore them and i get this error on the attachment.
Nevermind i have checked the option of zip verification and also my zip file was corrupted, thanks
Hi dude,
Can u make it like app normal, not install by twrp ?
Thank you before
Hmm... That's weird... I installed those on my Z2 Play and everything seems to be working with no problem, except for the quick screenshot option in Moto Actions which doesn't appear
Hi,
I installed it flawlessy,but i have no Attentive Display option.
Gesendet von meinem Moto Z2 Play mit Tapatalk
Archerous said:
Hi,
I installed it flawlessy,but i have no Attentive Display option.
Gesendet von meinem Moto Z2 Play mit Tapatalk
Click to expand...
Click to collapse
Moto Actions was update from PlayStore. Original version don't have this feature in Moto Z2 Play.
I modified the original version to enable this feature and I'll upload new zip with new apps versions.
Update 08-08-18
- Moto Actions 04.074.1.0-O
- Moto Display 06.069.0
- Motorola Camera 6.2.14.4
- Motorola FM Radio 02.02.0430
- Motorola Notifications 7.7.025
How to disable Rounded Corners ???
letuanlx said:
How to disable Rounded Corners ???
Click to expand...
Click to collapse
Install this zip.
Is lift to unlock working for anyone here? For me it doesnt work.
Can install on a z2 force?
brajesh.sharma87 said:
Is lift to unlock working for anyone here? For me it doesnt work.
Click to expand...
Click to collapse
Go to smart unlock .Remove face in truted face. Enable face in face unlock
letuanlx said:
Go to smart unlock .Remove face in truted face. Enable face in face unlock
Click to expand...
Click to collapse
Still doesnt work, does it work for you? Or anyone else.