[Rom] [4.3] Ghost_Retail Enginering Build Flashable Zip - Moto X Android Development

Moto X Flashable ROM zip of TMobile 4.3
engineering build System Dump​
Huge thanks to TheOrangeRemix for posing the original files at XDA.
This is a flashable zip of the system and boot.img for Moto X 4.3.
This is an engineering build so there are extra logging tools and whatnot but it runs smooth.
This is ghost_retail which is for Tmobile so radio may or may not work on other carriers but it will flash on any Moto X.
As always I am not responsible for you eatting cats or ruining your device
Flash in CWM or TWRP. If you have issues when you reboot you may have to factory reset or at least wipe cache and dalvik.
Download: http://androidhosting.org/Devs/Dhacker29/MotoX/ghost_retail_13.10.0Q2.X_25_eng.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Going to flash this , thanx dhacker. Just one question is the baseband? Can I inject the Rogers radio into this ? and where is it located in the ROM or dies it have to be flashed in fastboot? Coming from an HTC unit and the baseband ( radio) could be flashed in fastboot mode as an update
Sent on my Moto X

The baseband is stsored in a seperate partition so the baseband will not be changed by this. If you don't have data you may need to update the build.prop to match rogers and possibly use system/lib/libqmiservices.so and system/lib/libril-qc-qmi-1.so from the rogers build. Chances are since they are both GSM it may work without any changes.

dhacker29 said:
The baseband is stsored in a seperate partition so the baseband will not be changed by this. If you don't have data you may need to update the build.prop to match rogers and possibly use system/lib/libqmiservices.so and system/lib/libril-qc-qmi-1.so from the rogers build. Chances are since they are both GSM it may work without any changes.
Click to expand...
Click to collapse
Thank, my HTC phone I could flash different basebands but you had to be s- off to do it. I'll let you know what's happens. Probably a good idea to back up apn's I guess
Sent on my Moto X

You can flash radios on the X through fastboot. the fsg.img and NON-0HLOS.img are the radios. I looked in this build and the apns-conf has rogers listed.

Can anyone confirm or deny data out of the box for VZW?

well thinking no...and if u look at dhacker29's pick thats the vzw baseband
Sent from my XT1060 using xda app-developers app

It flashes fine, I get mobile data out of the box on rogers but the only issue I have encountered is navigation home button does absolutely nothing, I suspect it could be that I restored my data and xposed framework messed up system ui. So I'm trying another flash and restore my backed up apps and see if it works
Edit. Navigation home button works now, so you can't restore data from recovery if you installed xposed framework but I guess it would work if you uninstalled xposed and then did a data back up. Oh well, now I have to set everything again
Sent from my A2109A using Tapatalk 4

I'm on sprint, I haven't flashed this yet. Any thoughts on the Sprint version working
Sent from my XT1056 using Tapatalk 2

flashallthetime said:
It flashes fine, I get mobile data out of the box on rogers but the only issue I have encountered is navigation home button does absolutely nothing, I suspect it could be that I restored my data and xposed framework messed up system ui. So I'm trying another flash and restore my backed up apps and see if it works
Edit. Navigation home button works now, so you can't restore data from recovery if you installed xposed framework but I guess it would work if you uninstalled xposed and then did a data back up. Oh well, now I have to set everything again
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Do you find it slower, same or faster then stock 4.2.2?
Sent from my XT1058 using Tapatalk 2

scorpion667 said:
Do you find it slower, same or faster then stock 4.2.2?
Sent from my XT1058 using Tapatalk 2
Click to expand...
Click to collapse
Way slower than the Rogers image, there's so much more bloatware, also the rogers status bar is cleaner, if you use motoxposed module on this the WiFi and data icons over lap. Also getting system ui crash on start up, boot is so much slower, you must realize this is not an official release so it has its bugs.
I would suggest using the rogers image as a base . Back to my back up
Thanks dhacker for your hard work, waiting for some terrific development
Edit: so o reflashed this but a totally clean install and everything is working fine, if you plan on restoring your data I don't recommend it, my system ui problem was caused by xposed framework and motoxposed
Sent from my A2109A using Tapatalk 4

That's odd I didn't notice it being slow. And what bloatware? Are you referring to the debug utilities?
Sent from my XT926 using Tapatalk 2

dhacker29 said:
That's odd I didn't notice it being slow. And what bloatware? Are you referring to the debug utilities?
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
A reflash worked like a charm, it was the exposed modules which I reinstalled through ROM toolbox that caused me grief, I just removed all those debugging apks and Google magazine,videos games etc
Sent on my Moto X

So this is only working on T-Mobile devices? I'm curious to flash it but I am on sprint.
Sent from my XT1056 using Tapatalk 2

flashallthetime said:
A reflash worked like a charm, it was the exposed modules which I reinstalled through ROM toolbox that caused me grief, I just removed all those debugging apks and Google magazine,videos games etc
Sent on my Moto X
Click to expand...
Click to collapse
Any noticeable differences with regards to RF performance? What about the phone in general?

johnny grep said:
Any noticeable differences with regards to RF performance? What about the phone in general?
Click to expand...
Click to collapse
No noticeable difference although it seems I dont receive LTE signal but it could be the icons from the T-Mobile ROM. I will have to check by doing a speed test at a location where I did receive a LTE signal on the Rogers rom
Edit: LTE is available, got a download speed if over 45mb's
Sent on my Moto X running JB 4.3

Do a back up and test is all I can say can't hurt
Sent from my XT926 using Tapatalk 2

what all apps are safe to remove from this built ? anyone have a list ? battery drain is high specially in standby mode, not sure if it's due to this being a test built or those extra apps, I like it so far, but if I can't better battery life will go back to 4.2.2

dhacker29 said:
Do a back up and test is all I can say can't hurt
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I might bite the bullet but my bootloader's still locked. I'm holding out because I want to keep my warranty. BTW I think I read about Rogers pushing an OTA update... Anyone notice anything? My OTA app is disabled so I'm not sure.
Sent from my Moto X

Dhacker,
Sent you a hangout msg but not sure if you got it.
This build does flash cleanly on the VZW Droid MAXX Dev Edition and as such I expect it would be fine on the Moto X Dev Edition
For those planning to do the same, please note the following:
Capacitive keys do not presently function. Just like the Moto X, it will have on-screen keys with the hard keys dormant as if they didn't exist. I am working on how to enable them and would appreciate any assistance anyone can offer. This will not affect anyone on the VZW Moto X Dev Edition as they do not have hard keys .
Upon first boot, the phone will be in GSM/LTE mode. This will allow data but WILL NOT ALLOW PHONE CALLS as they are carried on the CDMA network which is disabled by default (this is a Tmobile ROM so that's to be expected).
***Fix: Dial *#*#4636#*#* - Go into Phone Information - Scroll down and change "Set preferred network type" to LTE/GSM/CDMA auto (PRL). Change nothing else. The phone will disconnect from the network momentarily and switch to emergency only mode for about 20sec. Don't be alarmed, it's just re-registering and attaching itself to the CDMA network. Mine took about 45s-1min to complete the cycle. Subsequent reboots will not require this process unless you wipe your cache.***
build.prop will ID your phone to the world as a TMO Moto X. No real issue here but just be aware of it as it may affect some of your apps.

Related

[SOLUTION] How to stop random shut down/rebooting HTC Amaze 4G

Hi there guys!
I have found solution for the problem with random shutting down\rebooting HTC Amaze 4G!
1. I flashed latest STOCK rom for mine T-mobile version
2. See picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now my HTC Amaze 4g works good!
ZeiLanS said:
Hi there guys!
I have found solution for the problem with random shutting down\rebooting HTC Amaze 4G!
1. I flashed latest STOCK rom for mine T-mobile version
2. See picture
Now my HTC Amaze 4g works good!
Click to expand...
Click to collapse
if your gonna tell people to clean contacts they should also do the opposite ones on the phone that those battery contacts touch.
also im skeptical on this as mines rebooted when its not even being held and just sitting there on a table.
thank you for your help, i missed it in the instruction But i never did so
Another solution is trying out different kernels, some might mess with files and cause them to be corrupted. Also, I did some research on the amaze and there's another fix saying that the back cover must be tight and not loose. Not sure if that's a definite solution but people can try it if all else fails! Other information is that apps may have a part in this or maybe you just need to reflash your rom!
I used to have this problem, like it was occurring two or three times a day and it just went away when I flashed the Stock RUU. I stayed on the stock rom for awhile and then moved to the ViperA rom. It's been about a month, that I haven't seen a random reboot on my phone!
Sent from my HTC_Amaze_4G using xda app-developers app
Thanks! Definitely going to try this.
Agree with kevinrubio1 , try superwipe then install backup again . This could be a kernel issue.
Saanus1 said:
Agree with kevinrubio1 , try superwipe then install backup again . This could be a kernel issue.
Click to expand...
Click to collapse
The best kernel out right now imo is the faux v31 kernel. It comes with the matching libs and files.
Sent from my HTC_Amaze_4G using xda app-developers app
Try putting a small folded up piece of paper under the battery. That solved the reboot issue with me.
Sent from my HTC One using xda app-developers app
You're hilarious ZeiLanS
dev_up_10 said:
Try putting a small folded up piece of paper under the battery. That solved the reboot issue with me.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
This is what worked for me undoubtedly. It doesn't make any sense to me, but hey.
dev_up_10 said:
Try putting a small folded up piece of paper under the battery. That solved the reboot issue with me.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That worked for me also, thank you. My battery level has gone back up to where it should be.
Random Reboot
Hi All
I am encountering Reboot problem for the last 3 days
I had reinstall the Stock Rom ARHD 4.0
Fix permissions
Factory Reset (Both from recovery and Phone settings)
Format Internal SD Card
Formatting Internal SD card resolved the issue for a day but today it started again it reboots every 1-3 minutes :crying:
As soon as I touch the phone it reboots I have doubt to have internal SD card corrupted
I am on faux 31 kernel s-off rooted
Thanks in advance
lalit387 said:
Hi All
I am encountering Reboot problem for the last 3 days
I had reinstall the Stock Rom ARHD 4.0
Fix permissions
Factory Reset (Both from recovery and Phone settings)
Format Internal SD Card
Formatting Internal SD card resolved the issue for a day but today it started again it reboots every 1-3 minutes :crying:
As soon as I touch the phone it reboots I have doubt to have internal SD card corrupted
I am on faux 31 kernel s-off rooted
Thanks in advance
Click to expand...
Click to collapse
Hi lalit,
If I were you I would run a RUU because they usually fix software issues. Since you are on Faux 31 I am guessing you have overclocked it, or undervolted it too much and you set it at boot.
SuperAfnan said:
Hi lalit,
If I were you I would run a RUU because they usually fix software issues. Since you are on Faux 31 I am guessing you have overclocked it, or undervolted it too much and you set it at boot.
Click to expand...
Click to collapse
Thanks
I have not touched the CPU/GPU settings
You mean I should restore HTC Stock Firmware
Should I re-lock my BL
Appreciate if you give me a link of latest one and the method
I tried but unsuccessful to get back to Stock RUU
I am little confused sorry for asking
lalit387 said:
Thanks
I have not touched the CPU/GPU settings
You mean I should restore HTC Stock Firmware
Should I re-lock my BL
Appreciate if you give me a link of latest one and the method
I tried but unsuccessful to get back to Stock RUU
I am little confused sorry for asking
Click to expand...
Click to collapse
Yes you should run a RUU, but don't worry I am pretty sure that you retain (keep) S-OFF anyway.
To be honest I am not an expert. Ravike14 is way better at troubleshooting than me lol . Hope he comes to aid a brother.
But I hope these can help you.
http://forum.xda-developers.com/showthread.php?t=2094385
http://forum.xda-developers.com/showthread.php?t=1617644
I think it's best to get the T-mobile one since almost all Amaze 3.6 roms including ARHD, NRG, SuperSense, all my ROMS, etc use the T-mobile base.
Hope it helps and good luck!!! :good::good:
SuperAfnan said:
Yes you should run a RUU, but don't worry I am pretty sure that you retain (keep) S-OFF anyway.
To be honest I am not an expert. Ravike14 is way better at troubleshooting than me lol . Hope he comes to aid a brother.
But I hope these can help you.
http://forum.xda-developers.com/showthread.php?t=2094385
http://forum.xda-developers.com/showthread.php?t=1617644
I think it's best to get the T-mobile one since almost all Amaze 3.6 roms including ARHD, NRG, SuperSense, all my ROMS, etc use the T-mobile base.
Hope it helps and good luck!!! :good::good:
Click to expand...
Click to collapse
Not able to install/flash RUU :crying:
Someone please help
I already put RUU zip file on my external card but nothing happening
Edit: Working RUU update in bootloader after changing ZIp name to PH85DIAG.zip
LOL problem is not solved by RUU
May be SD Card is corrupted
lalit387 said:
LOL problem is not solved by RUU
May be SD Card is corrupted
Click to expand...
Click to collapse
But you already formatted it? Use 4ext to format your internal SD. It will erase everything so copy the data from your internal to your computer.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
SuperAfnan said:
But you already formatted it? Use 4ext to format your internal SD. It will erase everything so copy the data from your internal to your computer.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Well I do not know but I switch to Speedrom 8.0 now things are stable and no reboot
I am not able to run ARHD as stable for me it
Personally this is the best ROM for me :crying:
lalit387 said:
Well I do not know but I switch to Speedrom 8.0 now things are stable and no reboot
I am not able to run ARHD as stable for me it
Personally this is the best ROM for me :crying:
Click to expand...
Click to collapse
I am making an update to Super Sense to 3.0, it will be the most feature rich ROM for the Amaze, EVER released here. It has so many options in AROMA that I'm implementing. So maybe you should get 3.0 when it comes out.
Maybe you should go on the Super Sense thread and ask a request to me there. :good: I am taking requests for stuff people want in AROMA. I will try and fullfill them.
Just paste a piece of insulation tape to the opposite side of terminals side of battery. It will surely solve tendon reboots issues.I solved this problem like this now battery is ok.
Sent from my HTC Amaze 4G using xda app-developers app

HTC Recovery Issue

I am not really sure how to explain what is going on so I made a video to kind of show.
Sorry it is shaky I was holding my camera and trying to use the phone at the same time.
So I did the HTC Unlock Bootloader thing about 2 months ago and I have been stuck with a phone that will not update or anything anymore.
I got fed up with trying to get it to work so I have just been using the phone as is, but it is getting slow and buggy on me so I would like to finish the rooting or get it back to stock or something.
When I boot into recovery as you will see nothing works.
HTC has an update right now on my phone and if I download and go to install the update it reboots into recovery and there is an error saying it could not mount the internal storage or something so update was aborted.
I was hoping someone could watch this video and then point me in the right direction of what to do next.
I tried to get a good shot of the recovery screen so you could see S-ON and the versions n junk.
https://www.youtube.com/watch?v=z2BC1nwo5V4
Thank you guys!
The first problem is CWM does not play nice with the Evo 4G LTE you need to use TWRP.
If you want to take the OTA Update you will need to re-lock your bootloader and install a stock recovery.
bigdaddy619 said:
The first problem is CWM does not play nice with the Evo 4G LTE you need to use TWRP.
If you want to take the OTA Update you will need to re-lock your bootloader and install a stock recovery.
Click to expand...
Click to collapse
^This. You've most likely borked your misc partition with CWM, so you'll need to fix that at some point. As for the rest, you can either do as Bigdaddy says, or install TWRP recovery and flash a ROM.
Sent from my HTC EVO 4G LTE
I downloaded GooManager and attempted to install TWRP. It said it installed but when I rebooted in to recovery it was still using CWM.
Any thoughts on how to force this install? Also when I tried to reboot into recovery using the GooManager app it would not reboot.
I will keep fussing with it and see if I can get TWRP to install.
Oh Bam! I got TWRP working.
Beautiful. I just need to find a ROM to use now..
Psywar28 said:
Oh Bam! I got TWRP working.
Beautiful. I just need to find a ROM to use now..
Click to expand...
Click to collapse
Keep in mind if you're S-on you'll need to install the kernel separately from the ROM. For more info hit the top link in my sig.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Keep in mind if you're S-on you'll need to install the kernel separately from the ROM. For more info hit the top link in my sig.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thank you! I will attempt to use Moonshine to get S-OFF
I was going to download this ROM would I then just download the S-OFF Version?
I was going to do the S-ON before.
If you're S-on use the S-on version.
Sent from my HTC EVO 4G LTE
FinZ28 said:
If you're S-on use the S-on version.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Moonshine was successful! I am now S-OFF!
Psywar28 said:
Moonshine was successful! I am now S-OFF!
Click to expand...
Click to collapse
Good deal:thumbup:
Sent from my HTC EVO 4G LTE
Ran into an issue.. I was attempting to install CM 11
It has failed on me. Any idea's why?
EDIT: weird note too.. I just went to boot back into the System and TWRP told me I lost Root Permissions.. and it attempted to fix it.. Dunno if it did yet or not.
BAH... Wont reboot back into the System.. Cycles twice and then goes back into TWRP Recovery.
EDIT EDIT: Ok.. So I got some of it fixed.. I ended up getting this Sense 5 ROM installed.. now I am installing this CM 10.2 ROM which seems to be working..
I just can't figure out why CM 11 wont install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Psywar28 said:
Ran into an issue.. I was attempting to install CM 11
It has failed on me. Any idea's why?
EDIT: weird note too.. I just went to boot back into the System and TWRP told me I lost Root Permissions.. and it attempted to fix it.. Dunno if it did yet or not.
BAH... Wont reboot back into the System.. Cycles twice and then goes back into TWRP Recovery.
EDIT EDIT: Ok.. So I got some of it fixed.. I ended up getting this Sense 5 ROM installed.. now I am installing this CM 10.2 ROM which seems to be working..
I just can't figure out why CM 11 wont install.
Click to expand...
Click to collapse
You probably have the wrong twrp for cm11. You need to use the recovery that is in the first post of the cm11 thread. To install it you'll need to do fastboot flash recovery.
You can get it from the first post here
http://forum.xda-developers.com/showthread.php?t=2518211
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
You probably have the wrong twrp for cm11. You need to use the recovery that is in the first post of the cm11 thread. To install it you'll need to do fastboot flash recovery.
You can get it from the first post here
http://forum.xda-developers.com/showthread.php?t=2518211
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I noticed I do have the wrong recovery for it.
I will attempt to install the one for CM 11..
Any idea why this Sense 5 ROM I am using will make phone calls but will not send any SMS's to anyone? Just keeps saying failed...
I kinda dig this Sense 5 ROM.. I have not been able to figure it out.
EDIT:
Got the new TWRP.img file installed.. I had a hard time doing it in Terminal Emulator so I just downloaded a freaking app that installed custom recoveries.
So it successfully installed CM11.. Now I am sitting here waiting for it to boot up.
I have the logo spinning around and around.. I hate these boot animations cuz I can never tell if it is stuck in a boot loop or if it is just working hard.
So I will give it 15/20mins.. Then I am not sure wtf to do other than go back to Sense 5.. Which I installed for a second time and I still could not get SMS to send or receive.
Glad you got it to boot.
If it's spinning it will probably boot up.
Since you did moonshine you should have been able to install the recovery with fast boot.
It's a good practice to have.
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
Glad you got it to boot.
If it's spinning it will probably boot up.
Since you did moonshine you should have been able to install the recovery with fast boot.
It's a good practice to have.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah CM 11 finally booted up.
I can make phone calls but I cannot send or receive SMS. Same issue I was having with the Sense 5 ROM.
I have been through all the settings I can find and nothing has worked yet.. Any ideas what might be wrong?
Psywar28 said:
Yeah CM 11 finally booted up.
I can make phone calls but I cannot send or receive SMS. Same issue I was having with the Sense 5 ROM.
I have been through all the settings I can find and nothing has worked yet.. Any ideas what might be wrong?
Click to expand...
Click to collapse
After you did moonshine did you make a call on sense and use the self activate feature in settings?
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
After you did moonshine did you make a call on sense and use the self activate feature in settings?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did.
When I loaded into the Sense 5 ROM it did not have any of my Profile Information so I could not use the phone with out doing the activation thing.
Psywar28 said:
Yes I did.
When I loaded into the Sense 5 ROM it did not have any of my Profile Information so I could not use the phone with out doing the activation thing.
Click to expand...
Click to collapse
Hmm. I don't know then. I never tried any of the sense 5 ROMs.
Personally at this point I would flash stock rooted, then self activate, update prl and profile, then call sprint and ask them to refresh my connection with them.
Then verify everything works, create a backup of that, and then go back to cm11.
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
Hmm. I don't know then. I never tried any of the sense 5 ROMs.
Personally at this point I would flash stock rooted, then self activate, update prl and profile, then call sprint and ask them to refresh my connection with them.
Then verify everything works, create a backup of that, and then go back to cm11.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sounds like a plan! Not a fun one though haha!!
Thanks for the advise!
Turns out I just needed to update to the latest firmware!

02/14/16 CM13 (Unofficial) for ls990

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I actually set this up days ago and shared on my G+ but figured why not share here for those who don't follow me)​
In short this is simply a early look as to what CM13 will have to offer. You will be experiencing Marshmallow the way Google and the Cyan team has set fit. Please keep in mind that these are still early development so there will be issues. ​
!!! Flash on your own risk !!!
We can and will not take any responsibility for bricked devices or lost data. So please watch out!​
Installation
- Make a (Nandroid) Backup of your current ROM
- Full WIPE (wipe data/factory reset + wipe cache partition + wipe dalvik cache)
- Select ROM from sdcard
- Install ROM (Make sure you use anything from 12/12/15 and up)
- After flashing, reboot device (First reboot will take a while)
- Enjoy CM13 on your device!​​
​
BETA 1 [12/12/15]
- First release
Use Builds from 12/12/15 and up
​
Download​
To stay updated on the original post and see what is happening when it happens see my Google Plushttps://plus.google.com/u/0/+IsaiahPEz ​
sub.
Runs pretty good but I am running into an issue with Titanium backup. I cannot find out why It cannot write to the SD card even with the correct entries in the platform.xml file and the Fix SD app doesn't work anymore like it has since KK through LP (Says the entry is missing in the .xml but, it isn't. So :/ )
EDIT: Nevermind, found out what was wrong with TB on the way it access's storage.
"You need to change the way that the app accesses your SD card. Go into the Titanium Backup preferences (Menu > Preferences) and click 'Backup folder location'. Then click on 'Storage provider' and then 'DocumentProvider storage'. Then just select the root of your SD card. You can then use TB to set your backup location on the SD card."
Did that and Boom. Works fine.
Still a few niggling issues but nothing more than 12.1 had so I am still debating on rolling with this or not for a while.
Been running for a couple of days. Everything has ran pretty smooth so far.
I've been running this super smooth for the last couple of days then about an hour ago with 60% battery it just died. I can't get it to charge or turn on at all. Any ideas on where to go from here?
Edit: After tying everything u could think of a few minutes ago it just turned on like nothing was wrong. No idea what caused it.
Edit: It appears that qksms was causing the crashes. Everything else is running great except for the domestic roaming thing.
Sent from my SM-T530 using Tapatalk
AOSP keyboard fails when first booted.
Can't continue with setup
mesacarvin said:
AOSP keyboard fails when first booted.
Can't continue with setup
Click to expand...
Click to collapse
I'd redownload and try again. Additionally you may want to try another gapps package.
What nightly did you flash?
Additionally which Gapps package did you use?
bmtdan said:
I'd redownload and try again. Additionally you may want to try another gapps package.
What nightly did you flash?
Additionally which Gapps package did you use?
Click to expand...
Click to collapse
Flashed the ROM in the OP and did not flash a Gapps package.
So will re-download and flash a Gapps package (any suggestions?)
mesacarvin said:
Flashed the ROM in the OP and did not flash a Gapps package.
So will re-download and flash a Gapps package (any suggestions?)
Click to expand...
Click to collapse
I'd grab them from here: http://opengapps.org/
Select arm,6.0, stock.
Is anyone else getting "domestic roaming"? I'm not sure if it's a bug out something wrong, other than that the data connection seems solid.
Sent from my LG-ls990 using Tapatalk
PlagaDeRock said:
Is anyone else getting "domestic roaming"? I'm not sure if it's a bug out something wrong, other than that the data connection seems solid.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
I get that when I connect to LTE, on 3g it just says sprint..
kangta05 said:
I get that when I connect to LTE, on 3g it just says sprint..
Click to expand...
Click to collapse
I got the same thing. When I go to check the apn's the system crashes. Could this be the problem?
tenchi_kioto said:
I got the same thing. When I go to check the apn's the system crashes. Could this be the problem?
Click to expand...
Click to collapse
I'm hoping its just a bug. Everything else it butter for me
Yea same issue with mine but everything seemed to work.
Went back to CM12.1 though as a lot of my Cardboard apps appear to not be working correctly with 13 yet and a few crashes to hard black screen. Will give it another go in a month or so.
Seeing Domestic Roaming is normal but it is fine to ignore. Everything should be resolved soon
Nexus11 said:
Seeing Domestic Roaming is normal but it is fine to ignore. Everything should be resolved soon
Click to expand...
Click to collapse
I had this on the other MM rom. Is it just a bug with MM/CM mods? Also it's just UI bug right? It's not actually roaming right?
Sent from my LGLS990 using Tapatalk
JESUSARIUS REX said:
I had this on the other MM rom. Is it just a bug with MM/CM mods? Also it's just UI bug right? It's not actually roaming right?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
I just checked on sprints website no roaming showing. I've been on a 6.0 Rom for 2 days now.
Nexus11 said:
Seeing Domestic Roaming is normal but it is fine to ignore. Everything should be resolved soon
Click to expand...
Click to collapse
Cool. I kind of figured it was just a bug and that I wasn't actually on roaming. Other than that and a problem I had with another app this is incredibly smooth and stable. The battery life unreal too. I can leave my phone unplugged while I sleep for 8 hours and only lose 3% of my battery.
Sent from my LG-ls990 using Tapatalk
PlagaDeRock said:
Is anyone else getting "domestic roaming"? I'm not sure if it's a bug out something wrong, other than that the data connection seems solid.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
I'm getting that on XenonHD (latest).
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
tenchi_kioto said:
I just checked on sprints website no roaming showing. I've been on a 6.0 Rom for 2 days now.
Click to expand...
Click to collapse
How do you check on sprint's website? DO I have to log in?
tenchi_kioto said:
I just checked on sprints website no roaming showing. I've been on a 6.0 Rom for 2 days now.
Click to expand...
Click to collapse
Thanks. I switched back to a stock based ROM, but I'll definitely give this a go as my daily. I played with it for about 4 hours and loved it.
Sent from my LGLS990 using Tapatalk

Having a problem with my phone status

This is what happen been messing with it going back and forth between Jasmine and stock. Well I flashed the stock .tar with odin and then it won't read my sim card anymore and I can't get flashfire to work. The phone status shows custom no matter what I do. Have odin the OB6 and OF1 stock shows an unlocked lock saying custom on boot screen..I did triangle away and that went away for a little bit then came back after a few restarts. And when I root it fails, when I did have the root I'm the stock it wouldn't let me flash. I'm kinda lost now, anyone have any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry, but if you can't flash any official firmware with odin looks like a motherboard problem to me.
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
Did you try to go to recovery and wipe cache partition then wipe data/factory reset ?
thunderblaster88 said:
This is what happen been messing with it going back and forth between Jasmine and stock. Well I flashed the stock .tar with odin and then it won't read my sim card anymore and I can't get flashfire to work. The phone status shows custom no matter what I do. Have odin the OB6 and OF1 stock shows an unlocked lock saying custom on boot screen..I did triangle away and that went away for a little bit then came back after a few restarts. And when I root it fails, when I did have the root I'm the stock it wouldn't let me flash. I'm kinda lost now, anyone have any ideas?
Click to expand...
Click to collapse
I flash the jasmine rom but some mudule exposed stop working and i got back to 4.4.4 but my note have the same boot image
aaroon200 said:
Sorry, but if you can't flash any official firmware with odin looks like a motherboard problem to me.
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
Did you try to go to recovery and wipe cache partition then wipe data/factory reset ?
Click to expand...
Click to collapse
I can flash the official firmware..that's what it's on with it saying it's custom. That's why I'm not understanding. I did wipe those.
Sent from my VS985 4G using Tapatalk
'Cause you still have a modified firmware, that's why
Sent from my SM-N900V using Tapatalk
aaroon200 said:
'Cause you still have a modified firmware, that's why
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I flashed on Odin the stock one, should t that revert the firmware? If not what do I do?
Sent from my VS985 4G using Tapatalk
I take it this is also causing my sim card problem as well. It does not say insert sim card or anything, only when I go to the mobile data toggle it says to insert one.
Sent from my VS985 4G using Tapatalk
Stock 1?
You should flash the original firmware from keis or from this page :
http://www.sammobile.com/firmwares/database/SM-N900V/
and start all over again, that should fix your problems.
Sent from my SM-N900V using Tapatalk
aaroon200 said:
Stock 1?
You should flash the original firmware from keis or from this page :
http://www.sammobile.com/firmwares/database/SM-N900V/
and start all over again, that should fix your problems.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
That's what I flashed, well I got it from Google drive that someone else uploaded so it wasnt a few hour download. The one I have worked the first 3 times. I'll give this one a download and try because why not
Btw I wanted to say thank you for helping me out with this. I've been rooting and all this since my eris so I know how it goes and This stuff happens. It's not the first time I've had a problem similar to this. I've tried everything I could think of like 5 times today for the last 8 hours or so tho
Sent from my VS985 4G using Tapatalk
thunderblaster88 said:
That's what I flashed, well I got it from Google drive that someone else uploaded so it wasnt a few hour download. The one I have worked the first 3 times. I'll give this one a download and try because why not
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Sometimes files get corrupted try the original. It takes about 2 hours to download [emoji1]
Sent from my SM-N900V using Tapatalk
aaroon200 said:
Sometimes files get corrupted try the original. It takes about 2 hours to download [emoji1]
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I just edited this post of you didn't see lol yeah I know it happens that's why i figured I might as well just download it anyway. Yeah freaking 2 hours is just crazy..see what happens and I'll let you know
Sent from my VS985 4G using Tapatalk
You can always paid the $7 dollars for one week of premium Speed.
[emoji12]
Sent from my SM-N900V using Tapatalk
Now I'm waiting for the download and playing on it and got this too lol
Snapchat is blocking rooted phones again. Lol
Restart it. Your gonna delete all that shiet anyways.
Sent from my SM-N900V using Tapatalk
thunderblaster88 said:
Now I'm waiting for the download and playing on it and got this too lol
Click to expand...
Click to collapse
I believe that's from verizon or Knox when using the root method of 1.tar and 2.tar, try this one instead : http://forum.xda-developers.com/verizon-galaxy-note-3/general/ob6-of1-n900v-note-3-verizon-oneclick-t3333569 after you back to original stock, this is the best method so far, and you will not get any strange warnings.
Ya it is, Knox
Sent from my SM-N900V using Tapatalk
aaroon200 said:
I believe that's from verizon or Knox when using the root method of 1.tar and 2.tar, try this one instead : http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 after you back to original stock, this is the best method so far, and you will not get any strange warnings.
Click to expand...
Click to collapse
This or the one I used. I never did the 1.tar 2.tar one I used the latest one click. Also I did the firmware from sammobile and same thing. So he said Knox then what do I do or are my options?
Sent from my VS985 4G using Tapatalk
thunderblaster88 said:
This or the one I used. I never did the 1.tar 2.tar one I used the latest one click. Also I did the firmware from sammobile and same thing. So he said Knox then what do I do or are my options?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Ok, you already flash the firmware?
any screenshots ?
aaroon200 said:
Ok, you already flash the firmware?
any screenshots ?
Click to expand...
Click to collapse
Yeah I did and it's still says custom..wouldn't let me root. Thing is is that pop up was Knox and said to reset I think that would set it back, cause before I flashed the firmware from SM I did a factory wipe then I'm download mode it said official..but after I flashed the firmware it says custom again lol. I'm gknna. I'm setting the phone back up now and waiting to see if that pops up again. My sim card hasn't been in the phone pretty much all day. Been in my g3. since the note won't read it as of now and yes I've tried putting pressure on the sun cause I know they had problems my other 2 old note 3's had that problem. This happen last Night when I was messing around before bed that's why I didn't mess with it too today.. Sorry and thank you guys for the help again
Sent from my VS985 4G using Tapatalk
thunderblaster88 said:
Yeah I did and it's still says custom..wouldn't let me root. Thing is is that pop up was Knox and said to reset I think that would set it back, cause before I flashed the firmware from SM I did a factory wipe then I'm download mode it said official..but after I flashed the firmware it says custom again lol. I'm gknna. I'm setting the phone back up now and waiting to see if that pops up again. My sim card hasn't been in the phone pretty much all day. Been in my g3. since the note won't read it as of now and yes I've tried putting pressure on the sun cause I know they had problems my other 2 old note 3's had that problem. This happen last Night when I was messing around before bed that's why I didn't mess with it too today.. Sorry and thank you guys for the help again
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Don't do anything yet after flashing , you still have your old data on the phone, now go to recovery and do some wipes, wipe cache partition and wipe data/factory reset and that should fixed.
---------- Post added at 04:32 AM ---------- Previous post was at 04:21 AM ----------

Nexus 6P final OTA DP5.

This is not my creation. I merely took the OTA of DP5 and swapped out the boot.img with @bouchigo 's modified boot.img to keep the OTA from forcing encryption.
Big thanks to @bouchigo for his modified boot.img. And to Google for the Developer Preview.
I hope I answer all question that may be asked upfront. I'll briefly explain what I did and how I tested on my own device. Which is the device and OS I'm posting this thread from.
*****Bootloader must be unlocked******
*****And using custom recovery*****
1. I was on stock 6.0.1 rooted and bootloader unlocked.
2. I have Multirom TWRP installed. I have a Pure Nexus in the secondary slot and stock rooted in the primary.
3. Make a back up before you start. Hell live on the edge and don't back it. But don't come complaining here if something happens. You've been warned.
4. Download my zip of the OTA.
5. Download the beta supersu.zip thats floating around.
6. Make sure bootloader is unlocked and you have some version of custom recovery installed.
7. Flash the OTA then the beta SuperSU.
Now this part is up to you.
I did not wipe anything but cache and dalvik before I flashed. So basically I dirty flashed in my primary rom slot over stock rooted 6.0.1.
And then I flashed the SuperSU zip. Everything booted fine, no issues, no hiccups.
I'm now running DP5 with all my data still here and set up just like it was on the previous OS. The only thing I had to do was uninstall all my layers themes and the layers manager apk then install the layers manager that has been fixed for Android N then install all your themes back.
Beware not all themes work. I've had some issues with some causing the settings to Force Close and some causing Developer Options to force close. So I uninstalled those particular layers and used another theme .
I'm using the unlocked 32 gig variant on T-Mobile.
So enough of the jibber jabber here it is:---:
https://drive.google.com/file/d/0B2OabWtEBQcpMkN2MlN2SFVJQnc/view?usp=drivesdk
So to recap :
Yes you can dirty flash over 6.0.1 .
It doesn't matter if you're rooted or not.
Yes you can flash via TWRP or MultiRom
(I have no idea about any rom slot except
The primary rom slot)
No this will not encrypt.
No you don't have to wipe data.
Yes all your data, apks, and settings will remain
If you dirty flash.
Yes this will attracted bikini clad women.
And yes if you make milkshakes at home it.
will bring all the boys to your yard.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using XDA-Developers mobile app
Awesomeness! Thanks for this and for the funny read!
Sent from my Nexus 6P using XDA Labs
Will recovery work if we want to revert back to our backup?
Sent from my Nexus 6P using Tapatalk
Couldn't get this to flash using Multirom TWRP.
I always get an error on patching system image unconditionally during install :/
Ended up booting even though TWRP swore there was no OS installed. Thanks!
mattwheat said:
This is not my creation. I merely took the OTA of DP5 and swapped out the boot.img with @bouchigo 's modified boot.img to keep the OTA from forcing encryption.
Big thanks to @bouchigo for his modified boot.img. And to Google for the Developer Preview.
I hope I answer all question that may be asked upfront. I'll briefly explain what I did and how I tested on my own device. Which is the device and OS I'm posting this thread from.
*****Bootloader must be unlocked******
*****And using custom recovery*****
1. I was on stock 6.0.1 rooted and bootloader unlocked.
2. I have Multirom TWRP installed. I have a Pure Nexus in the secondary slot and stock rooted in the primary.
3. Make a back up before you start. Hell live on the edge and don't back it. But don't come complaining here if something happens. You've been warned.
4. Download my zip of the OTA.
5. Download the beta supersu.zip thats floating around.
6. Make sure bootloader is unlocked and you have some version of custom recovery installed.
7. Flash the OTA then the beta SuperSU.
Now this part is up to you.
I did not wipe anything but cache and dalvik before I flashed. So basically I dirty flashed in my primary rom slot over stock rooted 6.0.1.
And then I flashed the SuperSU zip. Everything booted fine, no issues, no hiccups.
I'm now running DP5 with all my data still here and set up just like it was on the previous OS. The only thing I had to do was uninstall all my layers themes and the layers manager apk then install the layers manager that has been fixed for Android N then install all your themes back.
Beware not all themes work. I've had some issues with some causing the settings to Force Close and some causing Developer Options to force close. So I uninstalled those particular layers and used another theme .
I'm using the unlocked 32 gig variant on T-Mobile.
So enough of the jibber jabber here it is:---:
https://drive.google.com/file/d/0B2OabWtEBQcpMkN2MlN2SFVJQnc/view?usp=drivesdk
So to recap :
Yes you can dirty flash over 6.0.1 .
It doesn't matter if you're rooted or not.
Yes you can flash via TWRP or MultiRom
(I have no idea about any rom slot except
The primary rom slot)
No this will not encrypt.
No you don't have to wipe data.
Yes all your data, apks, and settings will remain
If you dirty flash.
Yes this will attracted bikini clad women.
And yes if you make milkshakes at home it.
will bring all the boys to your yard.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
How do you put Black theme??
Enviado do meu Nexus 6P através de Tapatalk
r3ix said:
How do you put Black theme??
Enviado do meu Nexus 6P através de Tapatalk
Click to expand...
Click to collapse
The black them is installed by "Layers Manager". It's called "Swift Black".
These are a few dark/black themes I myself have found to work on with DP5. Well except for "Beltz" and the "Transparent Pro". Those two theme everything OK. It's just in settings a few options , like "About Device" & "Developer Options" for close on me. So I usually just don't install the theme portion for the related apks and use another theme to handle those. Oh and the "Transparent Pro" doesn't seem to wanna them Google Contacts or Dialer.
But other than that I believe the rest seem to do pretty good.
Sent from my Nexus 6P using XDA-Developers mobile app
cvsolidx17 said:
Couldn't get this to flash using Multirom TWRP.
I always get an error on patching system image unconditionally during install :/
Ended up booting even though TWRP swore there was no OS installed. Thanks!
Click to expand...
Click to collapse
No problem. I don't know why it said that. Maybe cuz it hasn't built it from the .img files till first boot. I don't know. Just a guess. Did you dirty flash or wipe everything. And was it on primary or secondary rom slot.
Me myself ...I haven't had much luck getting Android N to boot on a secondary slot. I can flash it there but seems like to get it to boot I have to swap it with the primary. And I assume that's mainly due to having to flash the correct vendor for either "MM" or "N". Kinda like back in the day when you had safestrap but you had to stick with the same Android version because of shared bootloader and kernel and stuff.
Sent from my Nexus 6P using XDA-Developers mobile app
cracjackson said:
Will recovery work if we want to revert back to our backup?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ive had no issue with just wiping the main 4 (cache, dalvik, system, data) and restoring your backup as long as it has the boot.img and the vender saved with it. If not you may have to flash the proper vender and it boot.img.
Sent from my Nexus 6P using XDA-Developers mobile app
For some reason the download keeps failing.
Sent from my Nexus 6P using Tapatalk
Yea download keeps failing
Sent from my Nexus 6P using Tapatalk
Let me see why
Sent from my Nexus 6P using XDA-Developers mobile app
It's working for me. Don't click the blue "download" button. Click the download arrow at the top of the page.
Sent from my Nexus 6P using XDA-Developers mobile app
Thanks for this, I have this as my primary ROM in Multirom, but I can't load my secondary which is MM based because it needs the Multirom kernel. After installing the MR kernel, DP5 and the secondary ROM refuses to boot. Any ideas?
You need to flash the MM vendor file. Every time you switch between MM and N you need to flash the appropriate Vendor image.
Sent from my Nexus 6P using XDA-Developers mobile app
Download works, rom works. I did a full wipe from pure nexus rom. Installed as instructed on the 1st post.
Now rocking with latest rooted android N!
Thank you very much @mattwheat!
edit:
@mattwheat It turns out I dont have root. I didnt test it at first but now I did. And I can not enter the twrp anymore, it stays on the twrp splashscreen... Any suggestions?
I thought that was the leaked official OTA but just still DP as title said, i feel dumb lol
petzku said:
Download works, rom works. I did a full wipe from pure nexus rom. Installed as instructed on the 1st post.
Now rocking with latest rooted android N!
Thank you very much @mattwheat!
edit:
@mattwheat It turns out I dont have root. I didnt test it at first but now I did. And I can not enter the twrp anymore, it stays on the twrp splashscreen... Any suggestions?
Click to expand...
Click to collapse
Exact thing just happened to me, Full wipe, flashed rom then beta supersu, booted and runs great but no root and TWRP sticks at the splash screen when booting to recovery. Any ideas how to get back into recovery without starting fresh?
Yep, experienced the same thing. Had to back everything up to the laptop and push a factory image back to stock and start all over. Took awhile but phone is nice and clean now. I like N but too many of my apps don't play well with it yet
joefloater said:
Exact thing just happened to me, Full wipe, flashed rom then beta supersu, booted and runs great but no root and TWRP sticks at the splash screen when booting to recovery. Any ideas how to get back into recovery without starting fresh?
Click to expand...
Click to collapse
Just backup everything and wipe userdata and cache with adb.

Categories

Resources