Hello, it appears that ever since I switched to Project Fi from ATT, I'm starting to see some 'bugs'. I noticed that my current build number of LYM48I is older, and a generic firmware image. I'm wondering if I should upgrade to LVY48H, which according to (https://developers.google.com/android/nexus/images) appears to be the latest Project Fi image for the Nexus 6?
Quick details about my setup:
- I am on the Nexus 6 (purchased directly from Google)
- Android version 5.1.1
- Build number LMY48I
- Baseband version MDM9625_104446.01.02.101R
- I don't want to upgrade to 'Marshmallow' as from what I've read, is not officially supported by Fi
- My phone was rooted before switching over to Fi using the following procedure: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 (did not create a custom recovery, etc)
Thanks in advance
gil_happy said:
Hello, it appears that ever since I switched to Project Fi from ATT, I'm starting to see some 'bugs'. I noticed that my current build number of LYM48I is older, and a generic firmware image. I'm wondering if I should upgrade to LVY48H, which according to (https://developers.google.com/android/nexus/images) appears to be the latest Project Fi image for the Nexus 6?
Quick details about my setup:
- I am on the Nexus 6 (purchased directly from Google)
- Android version 5.1.1
- Build number LMY48I
- Baseband version MDM9625_104446.01.02.101R
- I don't want to upgrade to 'Marshmallow' as from what I've read, is not officially supported by Fi
- My phone was rooted before switching over to Fi using the following procedure: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 (did not create a custom recovery, etc)
Thanks in advance
Click to expand...
Click to collapse
lol, not officially supported by fi. you do realize that the n5x and n6p are both fi phones, right? and you do realize that they both come with marshmallow, right? marshmallow is the build that you should be on, as in its the latest. and there isnt a special m build for fi. there's only ine build if marshmallow, and its for fi as well.
..
Great! Thanks so much.... I guess my question is this , which method should I use to upgrade to Marshmallow? Will I lose all of my data? Keep in mind I 'only' rooted my device using the link in my original post.
..
gil_happy said:
Great! Thanks so much.... I guess my question is this , which method should I use to upgrade to Marshmallow? Will I lose all of my data? Keep in mind I 'only' rooted my device using the link in my original post.
Click to expand...
Click to collapse
cam30era said:
You're going to get plenty of advice on that question from other members. Let's just say, read, understand, and pick your poison.
Click to expand...
Click to collapse
fastest and easiest thing to do would be to flash the factory image. right way is via fastboot while youre in the bootloader. but there are ways using a toolkit as well.
..
cam30era said:
While Project Fi team did originally state that they did not recommend flashing MRA58K, that position changed about 10/15, when the OTA started rolling out to Fi users.
Click to expand...
Click to collapse
Source, please? In the official Project Fi support forum, the company line has not changed. See the relevant thread from the forum's most official spokesperson. It has never been superseded.
Thanks for this... do both methods completely 'wipe' the phone of all its data?
..
cam30era said:
The best source is the OTA from LVY48H to MRA58K that is rolling out to Fi users.
Click to expand...
Click to collapse
I know that the OTAs exist and that most of their URLs have been discovered by the community. That's not the point. I was challenging your assertion that the official policy of Project Fi opposing the flashing of factory image MRA58K has been withdrawn. It has not. For that matter, they have never announced an official rollout of the Marshmallow OTAs. With previous OTAs, there has been such an announcement.
..
cam30era said:
Granted. Google is in an untenable position here. Caught between a rock and a hard point when they started pushing OTAs to Fi users on the one hand...
So, what's your advice to the OP?
Click to expand...
Click to collapse
Depends on his risk tolerance. As a purely technical matter, nothing prevents him from flashing any build he wants. If he prefers an officially sanctioned OTA path, he should probably sit tight and wait for Marshmallow to be pushed out to him.
His concern that he is on the "wrong" build within 5.1.1 is misplaced. Project Fi officially supports three different Lollipop forks: the Fi-specific builds, the T-Mobile builds, and the generic Nexus builds. There will be an OTA path from each fork to the new unified Marshmallow. (But one messy detail is that the most recent round of security updates also spawned a fourth AT&T fork build LMY48W, which so far has no OTA path to 6.0. Some Fi users report that they have been OTAed to LMY48W .)
Personally, I use a daily driver on FI that runs the T-Mobile fork, and I want to keep it stock. I am in no hurry to flash the Marshmallow build because of multiple reports that doing so would probably break my existing Band 12 data service, which I want to keep as long as possible. So I am awaiting the OTA to be pushed out officially, and hoping that the Band 12 issue gets resolved soon somehow, even if that is a subsequent build.
I would assume the reason for the 3 forks is that there must be specific fixes or enhancements to each firmware load, otherwise what is the point of having 3 forks? Meaning, since I'm on Project Fi, it would make sense to be on the specific Project Fi load and not the T-Mobile or generic Nexus build.
gil_happy said:
I would assume the reason for the 3 forks is that there must be specific fixes or enhancements to each firmware load, otherwise what is the point of having 3 forks? Meaning, since I'm on Project Fi, it would make sense to be on the specific Project Fi load and not the T-Mobile or generic Nexus build.
Click to expand...
Click to collapse
We really don't know what was different about the Fi-specific build. Google claimed the difference was not very significant, but never disclosed what it was. The T-Mobile fork was created to support TMO's proprietary WiFi calling. And of course the generic Nexus fork was mainstream Android. It might be that Project Fi management just kept all three as officially supported because they wanted to test performance with three different radios. Remember, it is all beta (or beta-like), and we are all lab rats.
People speculated about the relative merits of the Fi build for months, with no rigorous testing that really proved anything beyond anecdotal placebo effects. But all this specualtion is about to become ancient history with the unification in Marshmallow. This is supposed to happen OTA any day now, and already has happened for some. So I can't see any great value in flashing the old Fi build at this point because it isn't worth the hassle. But it would do no harm.
boomerbubba said:
We really don't know what was different about the Fi-specific build. Google claimed the difference was not very significant, but never disclosed what it was. The T-Mobile fork was created to support TMO's proprietary WiFi calling. And of course the generic Nexus fork was mainstream Android. It might be that Project Fi management just kept all three as officially supported because they wanted to test performance with three different radios. Remember, it is all beta (or beta-like), and we are all lab rats.
People speculated about the relative merits of the Fi build for months, with no rigorous testing that really proved anything beyond anecdotal placebo effects. But all this specualtion is about to become ancient history with the unification in Marshmallow. This is supposed to happen OTA any day now, and already has happened for some. So I can't see any great value in flashing the old Fi build at this point because it isn't worth the hassle. But it would do no harm.
Click to expand...
Click to collapse
Thanks again.... I will attempt to upgrade to Marshmallow in the next day or so after a little more reading about 'how' to do this. As mentioned, I am rooted (no recovery) and will need to find out which of the 2 upgrade methods erase the phone.
I'm on a custom Marshmallow ROM (PureNexus) and easily activated Fi on it. Here's what I did, using a custom recovery (TWRP):
- downloaded M bootloader and M radio, PureNexus ROM and Gapps, and FiFix for dialer
- rebooted into TWRP
- removed my old carrier's SIM and left the SIM slot empty
- flashed M bootloader and M radio
- wiped everything except internal storage
- flashed PureNexus and its Gapps, and Fi Fix for dialer.
- booted and setup wizarded the new ROM on wifi, and updated ALL apps (most importantly Fi, Hangouts and Messenger, though I don't use the latter two) in Play. Had to enable Fi in Settings/Apps/Fi for it to updated by Play. Also allowed all permissions for Fi.
- put the Fi SIM into phone
- finally, ran the Fi app...
DONE.
Hope this is helpful to someone!
Sent from my Nexus 6 using Tapatalk
gil_happy said:
Thanks again.... I will attempt to upgrade to Marshmallow in the next day or so after a little more reading about 'how' to do this. As mentioned, I am rooted (no recovery) and will need to find out which of the 2 upgrade methods erase the phone.
Click to expand...
Click to collapse
I'm on Fi and upgraded to MM using the recovery flashable mages found in this thread. Make sure to read the entire op and also flash the bootloader and radio zips. Fi activated on my first boot and has functioned properly since.
A follow up to this... now today, my phone indicates I have a 'System upload downloaded' notification. When I try to install it, it fails. I believe this is because I have read something in the past that indicated it fails because my phone is rooted (and would need to be manually installed). If I'm going to attempt to manually install, is there any way to figure out via shell, ES File Explorer, etc what the name of this firmware is so that I can attempt to find it online somewhere and download?
Thanks in advance
Related
Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.
File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.
It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve
Hey guys so this was brought to my attention by another user, @daftlush . Dating back to my OGEvo4g we were conditioned to believe Update PRL/Profile could not be done in AOSP, specifically on Sprint. This was somewhat debunked when the Nexus came out to Sprint because it had this feature in AOSP. @daftlush brought up in another thread asking about this and I assumed like before it just wasnt in AOSP, except Google has it working. So I wanted to compile a list of roms that are fully Sprint functional that include Update PRL/Profile.
First, I noticed on roms where it does work it will finish Activating Data you dont have to press skip. I dont know if it is just a coincidence but the one rom I found this feature actually working, I did not have to hit skip once i saw LTE instead it finished and moved onto the next step.
If you know of a rom where this does work, please list it and I will update the list. I am hoping we can track down the necessary code to get this fully working on all AOSP roms.
UPDATE: 01/11/14
I was able to get the fix from team slim it is located in the second post
UPDATE 01/09/14
Newest Slimkat build has the feature confirmed working. (http://forum.xda-developers.com/showpost.php?p=49278373&postcount=3240)
I have sent a PM to the OP of the AOSPA thread to see if they can work on getting this going as well. Still waiting to hear back from AOKP since the first conversation. Lets help spread this info so we can enjoy our hammerhead! If you can help find the code needed on gerrit please let me know I have been looking but I dont have much experience in reviewing code, if it is found I can update post #2 with the detail for all devs to utilize.
UPDATE 01/06/14
I have passed on this information to a few days and so far, AOKP, SLIM, CNA have stated they will look into the code from Vanir and Cyanogenmod to see what they did in order to get these options working. Slim says it is a current WIP for them and last I talked to someone from AOKP they said they would look into it and we should have it working. CNA also said they would look into it.
Unfortunately OMNI doesnt look to be working on it, I did not get this info from someone on team omni but many posts have stated they dont want to include any closed source items from stock, i didnt know sprint hidden menu and prl/profile updates were closed source but that is unfortunate as I know a lot of us Sprint users would love to run OMNI, but for me no prl/profile updates make it hard to run as a DD (fellow Sprint users probably understand as prl updates sometimes fix our data issue)
Full working on Sprint (Activate data works, Update PRL/Profile works):
Vanir
Cataclysm
Stock Google
Anything based off Stock Image
Cyanogenmod
CM Based Variants
Slimkat (fixed per dev http://forum.xda-developers.com/showpost.php?p=49226687&postcount=3155) / now confirmed working as of 1/9 (http://forum.xda-developers.com/showpost.php?p=49278373&postcount=3240)
BobcatRom - confirmed working (http://forum.xda-developers.com/showpost.php?p=49284722&postcount=18)
AOKP 1/12/14 (http://forum.xda-developers.com/showpost.php?p=49340913&postcount=306)
AOSPA - the fix has been merged but no build put out since then, this is as of 1/11/14 future builds after this date should work (http://forum.xda-developers.com/showpost.php?p=49343381&postcount=303) (http://forum.xda-developers.com/showpost.php?p=49346234&postcount=313 confirmed Update PRL/Profile works as well)
Custom Raskat by @soccerfan6768 (http://forum.xda-developers.com/showpost.php?p=49412543&postcount=2624) he said hell pass on the fix to the raskatdevs for officials
Purity
Sprint data works w/o APN hack, but no update PRL/Profile(once you see LTE icon you must hit skip on activating data):
OMNI
Codename Android
Sprint data works with APN hack only:
PSX
First and foremost I want to give a very big THANK YOU to @cordell12 for putting up with my constant nagging surrounding this subject and to @kufikugel from slimteam for figuring it out. I hope cordell12 doesnt mind me posting their fix.
Per cordell12 "yes, it is blobs. those who do not have it(prl/profile update) working are using blobs from google website. those who do(prl/profile update) are using extracted blobs from stock build/device"
here is a link to the slimteams gerrit with the fix that made it work on their rom: https://gerrit.slimroms.net/#/c/1714/
i was told by another member that this fix also needed to be implemented https://gerrit.slimroms.net/#/c/1717/
Help me spread the word to the devs of non-fully functional roms on sprint.
So i have updated the list again today, CM has it working as do a few others. I am not good with git or code, does anyone know what the commit is that fixes this so i can help spread the word to other devs?
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
P.Mobile said:
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
Click to expand...
Click to collapse
The sprint. Zip file that allows you to get past the welcome screen on some roms and have data connection enabled, i few roms will be unusable if you don't flash this after the rom and the gapps,i think
Sent from my Nexus 5 using Tapatalk
On the fully compatible ROMs are you also able to access the Sprint Hidden Dialer Menu(*#*#3282#*#*)? I really hope Sprint users can get full compatibility across all ROMs.
AndrasLOHF said:
On the fully compatible ROMs are you also able to access the Sprint Hidden Dialer Menu(*#*#3282#*#*)? I really hope Sprint users can get full compatibility across all ROMs.
Click to expand...
Click to collapse
The roms that are fully working, have the hidden menu. I just checked for you and it does work, this is only tested on those that PRL/Profile update work!
MY goal of this thread is to figure out what code is missing from the roms so we(sprint users) can enjoy all the goodies.
P.Mobile said:
whats the sprint hack?? im on sprint and i always wanted to try rastakat rom
Click to expand...
Click to collapse
The Sprint hack enables the correct APNs for Sprint so you can have data, otherwise you get no data which makes our phones useless
Just a heads up, Update PRL/Profile is FIXED on SlimKat and will be included in our next Official build :good:
cordell12 said:
Just a heads up, Update PRL/Profile is FIXED on SlimKat and will be included in our next Official build :good:
Click to expand...
Click to collapse
That's great, Thanks. I have a Sprint-purchased Nexus 5 and I haven't ran into any problems so far, which is amazing. I'm glad it's the same phone hardware-wise as the unlocked version.
nerv8765 said:
That's great, Thanks. I have a Sprint-purchased Nexus 5 and I haven't ran into any problems so far, which is amazing. I'm glad it's the same phone hardware-wise as the unlocked version.
Click to expand...
Click to collapse
I really hope this catches on, one device = all providers.
cordell12 said:
I really hope this catches on, one device = all providers.
Click to expand...
Click to collapse
I do too, it's so nice to know that I have the option of going with a prepaid service like T-Mobile or At&t. Basically, anything except Verizon will fully work (and I don't really miss Verizon any.)
thanks to this thread i found about Vanir and will never turn back to anything else!
Tons of great info here, thanks OP!
Thank you cordell for giving us an update!!
I have sent a message to the hammerhead maintainer of AOSPA to see if they will also implement this "fix"
Has anyone been able to see the code from either CM, Slim, or Vanir? I want to update post #2 with that info so the other devs can easily access them.
BobcatRom works flawlessly on sprint, and is an amazing ROM. I highly recommend people to check it out. Its beautiful.
sent from my Hammerhead Nexus
CRIME INC. said:
BobcatRom works flawlessly on sprint, and is an amazing ROM. I highly recommend people to check it out. Its beautiful.
sent from my Hammerhead Nexus
Click to expand...
Click to collapse
can you confirm Update PRL/Profile work?
Circaflex said:
can you confirm Update PRL/Profile work?
Click to expand...
Click to collapse
Yes I can:thumbup:
sent from my Hammerhead Nexus
CRIME INC. said:
Yes I can:thumbup:
sent from my Hammerhead Nexus
Click to expand...
Click to collapse
thanks added to the list
cordell12 said:
I really hope this catches on, one device = all providers.
Click to expand...
Click to collapse
@cordell12: is it at all possible for you to link me to the changes on gerrit that were made to get this feature working, i have receieved answers from a few other rom devs asking me for the code, i tried looking on slimsgerrit but i have no experience in reviewing code and i am not sure what i am looking for exactly. thank you for any help you can provide.
CM12.{0,1} (Lollipop) official/unofficial builds for the Droid 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0/5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
These are WIP builds of porting CM12.{0,1} to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Last official build:
http://droid.cs.fau.de/cm-12.1/official/
Old manual builds:
http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2015-04-16:
Switched CM build-target, new nightlies will now be 12.1: http://review.cyanogenmod.org/#/c/94693/
2015-02-01:
No more unofficial builds! See: http://review.cyanogenmod.org/#/c/87596/
2015-01-28:
Mobile data fixes
Remaining com.android.phone crashes on VZW finally fixed (thanks @joojoobee666)
2015-01-24:
Fixed sw-keyboard popup when hw-keyboard is used (thanks @joojoobee666)
Fixed reboot to recovery
Fixed sepolicy for whisperd (dock service)
2015-01-22:
Fixed su-permissions
Crashes on Verizon most likely fixed, please report back
2015-01-20:
Fixed flashlight
2015-01-18:
SELinux updates.
This requires manual action for applications to continue being able to access their own files when upgrading from 2014-01-14 or 2014-01-15 (older versions are fine)!
Due to SELinux-bugs in 2014-01-1{4,5}, you have to relabel your data-partition on the first boot when upgrading from 2014-01-14/-15. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) and execute via an adb shell:
Code:
su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'
2015-01-1{4,5}:
More fixes for {,umts_}spyder
sepolicy updates
GSM fixes
notable CM changes: su integration fixed
2015-01-11:
Updated SELinux policies (mostly for spyder/umts_spyder)
Added kernel stability fixes
Video decoding fixes
2015-01-09:
Enabled SELinux enforcing
Add SELinux-policies for motorola services
Enable ro.telephony.get_imsi_from_sim on VZW devices (thanks @joojoobee666)
2015-01-02:
Sync CM changes
2014-12-23:
Fixed stock camera
2014-12-22:
Sync CM changes
Fix build due to P2P changes (fix pushed into CM)
Enabled security for adb (keys/not root by default)
2014-11-30:
Added APN fixes for CDMA/LTE
Enabled multiuser mode (might not work yet)
Last update for a couple of weeks
2014-11-27:
Fixed graphics glitches
2014-11-26:
Fixed HW video-decoding
Enabled doze mode (no pickup sensor in the devices!)
CM resync as always
2014-11-23:
Probably fixed mobile data on LTE
Fixed WiFi-tethering
2014-11-22:
Requires a recovery supporting SELinux
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data (at least on GSM/UMTS in Europe)
WiFi
WiFi-tethering
GPS
Camera
Playback of DRM-protected content (using Widevine from OnePlusOne)
What's not working:
Probably most everything else, including, but not limited to:
Some connectivity issues (should be solved now)
Data encryption
Gapps (CM-12.0):
Dhacker29 provides gapps for Lollipop:
http://d-h.st/YQG
http://d-h.st/jzr
http://droid.cs.fau.de/cm-12.0/gapps/ (Mirror)
Gapps (CM-12.1):
https://github.com/cgapps/vendor_google/releases/
Installation:
You need a new recovery supporting SELinux
An updated Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
To use this CM12.{0,1}-ROM on GSM-networks you should install Mentor.37's GSM patch
Source / Repositories:
maserati device-support: https://github.com/CyanogenMod/android_device_motorola_maserati
omap4-common device-support: https://github.com/CyanogenMod/android_device_motorola_omap4-common
omap4-common kernel: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common
local manifest to build cm-12 for the Droid 4: http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/local_manifest.xml
XDA:DevDB Information
CM 12.{0,1} on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2016-02-16
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Once again, thank you so much for your efforts in keeping this device alive.
sharptv said:
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Click to expand...
Click to collapse
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Click to expand...
Click to collapse
No, data encryption is not enabled by default (and still doesn't even work for us).
Cheers,
Michael
Flipping sweet thanks y'all rock i love xda
Cast Screen
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
gabhroo123 said:
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
Click to expand...
Click to collapse
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Shobai said:
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
Click to expand...
Click to collapse
assuming that cm11 is currently installed in your stock slot and you want to update to the new test safestrap by stargo:
uninstall the existing safestrap using the original safestrap, for instance, if the existing safestrap is 3.73, you should install safestrap 3.73 and uninstall the recovery.
DO NOT REBOOT YOUR PHONE IN THE PROCESS
after you have uninstalled the existing recovery, uninstall safestrap(3.73), and then install the new safestrap by stargo, and install the recovery.
your safestrap is now updated, and nothing will be wiped.
YOU MUST NOT REBOOT YOUR PHONE DURING THE PROCESS, you can only reboot after a recovery has been installed.
hope you find this useful
thelolotov said:
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Click to expand...
Click to collapse
It need some kernel changes... but it should work...original gnex have the same cpu/gpu and they make it work... @lucize was seeing that but i dont know what happend with that
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
By the way....thanks michael for your great work!...please make a donation link to send you some beer money!
Cheers, sharptv, much obliged =)
gabhroo123 said:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Click to expand...
Click to collapse
Yes, our GPU driver does not support WFD. And in contrast to the GNEX, Motorola added much stuff to our version, so it's not easy to sync it back with the upstream kernel. Last time I tried that, I ended up with a non-working display and couldn't figure out why...
Shobai said:
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Click to expand...
Click to collapse
Just boot to whatever you currently have installed in the stock slot. And I have to underline what @sharptv said, never reboot your phone in the process (it might work when you have the stock ROM in the stock slot, but it will surely break in every other case).
Cheers,
Michael
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
This App Camera work fine: https://play.google.com/store/apps/details?id=com.radcam.camera
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
sharptv said:
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
Click to expand...
Click to collapse
See this thread: http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
Download and install with recovery
I can confirm that at least on my phone that LTE is working. Great work .
flash these zips in recovery for root i got the from my nexus 7 root toolkit
HOPE IT WORKS FOR YOU :good::cyclops:
TheXG6HD said:
I can confirm that at least on my phone that LTE is working. Great work .
Click to expand...
Click to collapse
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
stargo said:
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
Click to expand...
Click to collapse
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
thelolotov said:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
Click to expand...
Click to collapse
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
LTE was working on first build, just took 10+ mins to connect then worked good.
Sent from my XT907 using Tapatalk
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.
Since the bootloader just got unlocked, does anybody know if the moto maxx roms work on the turbo yet and if they don't how can we get them up and working?
Sent from my XT1254 using Tapatalk
I know CM is not working yet, but I can't vouch for any of the stock modified ROMs.
Sent from my XT1254 using Tapatalk
Just tried flashing XT1225 5.0.2 system. It boots up, but fails to set up. Reboots at the first setup screen.
I guess XT1250 4.4.4 will work since it has same FCC ID.
CM 12.1 s being worked on right now. See this page. Looks like it's been solved. You will probably get it in the next day or so with a new nightly.
Or workaround instructions may be posted before then.
http://forum.xda-developers.com/mot...axx-xt1225-cm12-0-pre-release-t3060089/page85
Once CM 12.1 is sorted, then the other ROMs, especially Resurrection Remix will adopt the same procedure. @Skrilax_CZ, the CM dev and @baybutcher27, the Resurrection Remix and Mokee dev, are helping each other on this. @baybutcher27 also has a custom kernel with lots of neat features, in addition to CM base kernel, so they both want this to work for ALL Quarks.
several trials and errors I did.
XT1250 KK -> XT1254 DOES Work without any FCs. Since it is an identical device, it should work fine. However, it needs LP stock rom which is unavailable I think.
XT1225 LP -> XT1254 DOES NOT Work.
- With XT1225 boot.img : Reboot after choosing language from Setup Wizard
- With XT1254 boot.img : Constant Telephone FC. Device seems to be working I guess
What are the odds of the quark forums being put back together now that we are unlocked? Rather than monitoring 3 diff forums? Not sure how it was before but making it similar to the G2 forums, where you had a general G2 dev forum, then a sub-forum for each specific carrier.
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Skrilax_CZ said:
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Click to expand...
Click to collapse
Code:
[email protected]:/ $ getprop ro.boot.radio
0x4
[email protected]:/ $ getprop ro.boot.carrier
[email protected]:/ $
Skrilax_CZ said:
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Click to expand...
Click to collapse
I attached a screen of my ADB screen
mbarry55 said:
What are the odds of the quark forums being put back together now that we are unlocked? Rather than monitoring 3 diff forums? Not sure how it was before but making it similar to the G2 forums, where you had a general G2 dev forum, then a sub-forum for each specific carrier.
Click to expand...
Click to collapse
That was what some of us suggested -- but the the Droid Turbo owners wanted us far, far away. Now they need us.
I suppose it might have been confusing at the time
I came from a razrm and while I shared a cm11 rom with several phones specs were different on the devices.
Personally I would like to see the forums merged as well. If it didn't make sense then. It does make sense now.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
I suppose it might have been confusing at the time
I came from a razrm and while I shared a cm11 rom with several phones specs were different on the devices.
Personally I would like to see the forums merged as well. If it didn't make sense then. It does make sense now.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Perhaps the same people who petitioned for the divide need to petition for a merger?
I'm not sure who finally approved the Quark forum split, but @TonyStark was very helpful in making it go smoothly. Some stuff got put in wrong forum and he fixed it promptly.
Now with bootloader unlock and common kernels, ROMs, there's no reason to be divided anymore. Everything now works on all QUARKS.
I can see this being an issue. It seems as though a maxx dev put out a kernel for the Turbo that will run RR and CM12.1. Would that dev post it here as well, or link it with flashing instructions?
A lot of us have been sitting idle waiting for the bootloader unlock to happen, and haven't had to delve very deep into the inner workings of lollipop. I personally haven't had a bootloader unlocked phone since 2011 or so, so I m trying to be very cautious in what/how I flash. Having to bounce between forums and even devices is quite worrysome when you haven't been actively flashing for some time.
boomslick08 said:
I can see this being an issue. It seems as though a maxx dev put out a kernel for the Turbo that will run RR and CM12.1. Would that dev post it here as well, or link it with flashing instructions?
Click to expand...
Click to collapse
You are referring to @baybutcher27, who is also the Resurrection Remix dev and OFFICIAL TWRP QUARK dev. And yes he also has his own kernel, based on CM kernel but with additional options.
CM dev @Skrilax_CZ made CM kernel work for XT1254. But that will show up in tomorrow's "nightly".
You can find links to everything here:
Moto Maxx Original Android Development
http://forum.xda-developers.com/moto-maxx/orig-development
Moto Maxx Android Development
http://forum.xda-developers.com/moto-maxx/development
Moto Maxx Themes and Apps
http://forum.xda-developers.com/moto-maxx/themes-apps
Once you go to those links, read the first post and the last few posts. There's plenty of instructions.
Now that the XT2254 bootloader is unlocked, it's just another Quark. Everything will work.
Whether they duplicate those threads over here is up to the devs. That's double work to maintain two threads for the exact same releases.
If they decide to keep the devices separated it really just needs a post with a link saying "go here" in the droid rom section
Sent from my XT1254 using XDA Free mobile app
Has anyone got CM12 to work properly? I did a FDR, flashed the rom, and then butchers updated kernel. I can get it to boot, but it won't update/install any of my apps from the play store.
EDIT: OOps, i flashed one of the radio images in skrilax's CM12 thread. Not i can't get any signal. Anyone have the radio.img from SU4TL-44?
Wouldn't the download for 10/10/15 have what you need?
http://forum.xda-developers.com/showthread.php?p=61752986
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
Wouldn't the download for 10/10/15 have what you need?
http://forum.xda-developers.com/showthread.php?p=61752986
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Thought it did, i found it elsewhere. Got it to connect to cell when it loads up, still having the play store issue on RR as well as CM12.
I think it has something to do with the 'Storage space running out' message i'm getting. Not sure why thats there, never had it on any other rom/phone.
I have RR running without a hitch it seems. Calls, sms, mobile data all working normally. Havent had any google play issues yet either and ive installed quite a few apps. So far, so good here.
brennam7 said:
Thought it did, i found it elsewhere. Got it to connect to cell when it loads up, still having the play store issue on RR as well as CM12.
I think it has something to do with the 'Storage space running out' message i'm getting. Not sure why thats there, never had it on any other rom/phone.
Click to expand...
Click to collapse
I had that happen when I first flashed it this morning. I had done just a factory reset in twrp. When I mounted system and wiped the partition than reinstalled RR I didn't have a single problem. It shouldn't be doing that anyways seeing that the system partition is 5GB
This is a real possibility.
Have managed to compile and sort out some auto build scripts (work to do).
Need to get hold of some TWRP flash-able binaries. Current device state is bootloader locked and unrooted. Waiting for return period to expire........... Hoping current rooted users here can answer a few questions and provide any info so I can progress until I have rooted and personally flashed the kernel.
There are no promises or guarantees here.
https://forum.xda-developers.com/showpost.php?p=73794953&postcount=6
EDIT: waited a week, now applied for bootloader unlock code, unfortunately I have to wait 14 days after creating Huawei ID............ stupid !! I don't wish to unlock via any other method.
Might lose interest in that time .......... and work probably get in the way.
Don't really wish to move on blindly if it does not flash, nor stable as stock build. I need to flash on my own device first. In the mean time, I'll get my auto build scripts in order and do a little research. Was hoping to unlock and pull running STOCK official 307 boot.img from device. Downloaded the official firmware package from Huawei, but couldn't find any boot.img ......
We will be very thankful if you could develop a kernel for us. Hopefully you won't lose your interest on it!
carlchan31 said:
We will be very thankful if you could develop a kernel for us. Hopefully you won't lose your interest on it!
Click to expand...
Click to collapse
What I require is :
boot.img partition size. Check /proc/partitions ............. I'm not sure which it is on DL09 device. I don't want to build a boot.img larger than the actual partition. So need a Huawei user to point his out.
boot directory. check something like /dev/block/platform/_________/by-name/boot ?
Require a stock unmodified boot.img for 307 firmware
As I said, I'm unrooted for the next 14, now 13 days.......... Obtaining the above will assist to finish my build environment, and auto build scripts etc. Then can start on a few commits to fix some build warnings.
Help me to help you
Edit: installed the 'disc info' app, and still no joy to locate the boot.img directory and partition size. Will have to wait another couple weeks unless someone helps out.
Hi!
I just downloaded and compiled the nougat kernel source, but the repacked kernel failed to boot. I'm not sure wheather I should make some modifications prior compiling. I have the wifi version with C100B302. Will investigate when I have more time. @Lazing_About are your sources available on github? I'll push mine once I can sort out the issues.
Edit:
The initial huawei sources are already up in case anyone wants to clone or contribute.
https://github.com/TaRsY/android_kernel_huawei_BTV-W09
TaRsY said:
Hi!
I just downloaded and compiled the nougat kernel source, but the repacked kernel failed to boot. I'm not sure wheather I should make some modifications prior compiling. I have the wifi version with C100B302. Will investigate when I have more time. @Lazing_About are your sources available on github? I'll push mine once I can sort out the issues.
Edit:
The initial huawei sources are already up in case anyone wants to clone or contribute.
https://github.com/TaRsY/android_kernel_huawei_BTV-W09
Click to expand...
Click to collapse
Unfortunately no one provided what I hoped for so I could continue. I presume lack of interest, so whilst waiting for my 14 days, I have decided to buy a Note 8 (considered OnePlus5) and have spent time developing a private kernel for that. Work commitments have now got in the way with that too. At least I managed to patch to the latest Linux mainstream and quite a few patches too. Haven't yet rooted that either (of flashed). So I'll be out of action for all October afraid. My sources are still private until actual collaboration or public release. No need for anyone pulling / cherry-picking **** that is unstable if I haven't tested (at least method) first. Hopefully I'll have some time next month to take a further look at both projects, and eventually filter that work here
movie downloader for huawei mediapad M3
Thread closed at OP request