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
Related
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.
I'm sure that someone from the Carbon team will make an official post sometime soon but I periodically check their database and noticed that they now have nightlies for the M8! Woohoo! Was one of my favorites on my MoPho 4G LTE and M7 so looking forward to installing this in just a few minutes.
Here's the link: https://carbonrom.org/downloads/?device=m8&type=nightly
P.S. Hope this is not out of line for me to post before someone from their team does I just wanted to share my happiness! =)
Greetings,
I moved your thread to General and removed the link until it can be confirmed working on the Sprint M8.
Thanks BD619
BD619 said:
Greetings,
I moved your thread to General and removed the link until it can be confirmed working on the Sprint M8.
Thanks BD619
Click to expand...
Click to collapse
Fair enough, good sir. I do not know what exactly you require to show as proof but here are some screenshots I just took after installing^^
Don't judge me on my quick theming, was just trying to show the customizations work =P
After first reboot I did get a Gapps FC but I believe that may be due to the outdated binary I was warned of when installing the Gapps package I used(LiquidGapps from the Liquid Rom download page). Also, this ROM appears to be afflicted with the same forgetfulness as the other AOSP ROMs when it comes to WiFi passwords but so far those are the only things I've come across and one of them was likely my fault.
slimbrady said:
Fair enough, good sir. I do not know what exactly you require to show as proof but here are some screenshots I just took after installing^^
Don't judge me on my quick theming, was just trying to show the customizations work =P
After first reboot I did get a Gapps FC but I believe that may be due to the outdated binary I was warned of when installing the Gapps package I used(LiquidGapps from the Liquid Rom download page). Also, this ROM appears to be afflicted with the same forgetfulness as the other AOSP ROMs when it comes to WiFi passwords but so far those are the only things I've come across and one of them was likely my fault.
Click to expand...
Click to collapse
Thanks for confirming, my concern was it was built for GSM devices, and it would soft brick a Sprint device.
I don't see any harm in posting the link again.
BD619 said:
Thanks for confirming, my concern was it was built for GSM devices, and it would soft brick a Sprint device.
I don't see any harm in posting the link again.
Click to expand...
Click to collapse
No problem. I remembered I think Aarrgghh saying that CArbon wouldn't have a m8 build until Cyanogen unified their m8 devices so I knew once I saw it up there it was going to work for CDMA as well as GSM but I should definitely have posted AFTER installing and trying it if I'm going to promote a link, haha. Thanks for keeping me from possibly doing someone else a disservice.^^
Here is the link again if anyone wants to try it out:
http://carbonrom.org/downloads/?device=m8&type=nightly
The 5/20 build is still running stable for me since I installed last night. Haven't tried the 5/22 one yet but I'm about to. ^^
Happy Flashing!
Added the link to post 1 also
Any other bugs besides Wi-Fi passwords?
Yeah, I've came across another...camera app(native or 3rd party) seems to cause a reboot when opened. Possibly one or two more but i don't know if it would be better to wait for an official carbon thread/dev before i start complaining, haha.
Sent from my One M8 using XDA Premium 4 mobile app
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Since this thread is no longer just about me trying to get lollipop running on this phone (I AM still doing that though) I decided to 'rebrand' it as a general development thread for OSA. What's OSA? It stands for Only Some Android...ok so whats that? A team name I came up with to make myself feel more important (btw we're always looking for contributors).
So instead of focusing on just lollipop I will be discussing pretty much anything and everything I am doing in regards to the Desire 510.
Original Post Below:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
OnlySomeDood said:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
Click to expand...
Click to collapse
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
pattyboi:) said:
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
Click to expand...
Click to collapse
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
OnlySomeDood said:
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
Click to expand...
Click to collapse
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
pattyboi:) said:
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
Click to expand...
Click to collapse
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Yeah I have gotten a few of those errors, but not on surfaceflinger, mine are mostly on bionic and libcutils
OnlySomeDood said:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Click to expand...
Click to collapse
gonna be trying that myself,let me know if you get anywhere
for sure, that's what this thread is for afterall
OnlySomeDood said:
for sure, that's what this thread is for afterall
Click to expand...
Click to collapse
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
dip_spit said:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
Click to expand...
Click to collapse
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
OnlySomeDood said:
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
Click to expand...
Click to collapse
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
OnlySomeDood said:
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
Click to expand...
Click to collapse
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
OnlySomeDood said:
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
Click to expand...
Click to collapse
can you post one of the errors when you get a sec?
& none,got so angry at the stupid libqdutils thing i had last night i havent even attempted anything yet,been working on setting zswap/vnswap up so we have some leeway when it comes to ram..you got github at all?
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
OnlySomeDood said:
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
Click to expand...
Click to collapse
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
dip_spit said:
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
Click to expand...
Click to collapse
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
OnlySomeDood said:
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
Click to expand...
Click to collapse
i dont blame you,makes sense to me
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