Related
Q&A for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [STOCK] [XT1069] [ROOT] Stock ROM - XT1069 - KXB21.85-24. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
You created two scripts?
adrianom said:
I made some scripts to clean (remove stock apps) and optimize the ROM, instead of modifying the main ROM, I created these scripts that must be run in recovery.
For download go to post 2.
...
Click to expand...
Click to collapse
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.
elperroderoke said:
I packed your recoverys and made a zip flashable recovery, but never said I made a recovery. When a new version appears I pointed to your work.
http://www.htcmania.com/showthread.php?t=907314
You have used my script. I'm not a developer as you are, but I don´t think you like that people use your work and say nothing about your effords.
http://www.htcmania.com/showthread.php?t=909354
Regards.
Click to expand...
Click to collapse
Yes, indeed I use some lines of your post, but to be clear, the script that is in the zip is not what is in your post, it has a lote more, and yours don't work on this device, yes a grab some delete lines to simplified the list of apps, but that was it, and I have not mentioned, simply by forgetting it.
I put the reference now:
http://forum.xda-developers.com/showpost.php?p=56221065&postcount=2
scripts
I saw the lines you included and I hope you don't mine I will use some of them to improve my script for X1068.
If you be so kind to solve a question about deleting some files I would thank you.
Is there any way to delete the updates apk in /data/app?
As you know some of them are in /system and in /data once they are updated, but the name changes if is update again.
For instance:
Books.apk is in /system but, com.google.android.apps.books-1.apk is in /data and if is updated again it will be com.google.android.apps.books-2.apk
I tried using
delete("/data/app/com.google.android.apps.books*.apk");
or
delete("/data/app/com.google.android.apps.books-*.apk");
instead of
delete("/data/app/com.google.android.apps.books-1.apk");
delete("/data/app/com.google.android.apps.books-2.apk");
bud didn't work. Is there any way to delete the files that that have similar name.
Thank you for all your work.
Regards.
Any custom rom or rom adapted for xt1069?
Error
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!
xdaVTU said:
Hello man, I'm brazillian, sorry for my english.
I tried to flash a rom from this website: sbf.droid-developers.org/phone.php?device=36 , the last rom, because my Moto G 2 is Duos TV. When I flashed the rom, my camera stopped, just the frontal camera function, my flashlight too stopped... I really like to know, if you can help me with it... How you know, the cam of Moto G 2 has a button to change between Frontal and main camera, but this button doesn't appears, and the options in the configuration is blocked(some of them).
Please help me, I paid R$799,00 (money of Brazil), thanks a lot for everything!
Click to expand...
Click to collapse
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.
help
adrianom said:
You are using the Motorola app or the Google camera app? The button to change are in different places.
About the firmware, you have to flash the correct one? Has to be the with dstv in the name. If you flash the wrong one try flash the correct.
Click to expand...
Click to collapse
Adrianom, thanks for answer my question, but yes, I made the correct download, in the name was wrote DSTV, and about the app.. I don't know what the app that I'm using, is the factory app of the device, probability of Motorola. And all the apps that has the function of camera, neither of them work with me... Thanks for everything, and.... What do you think about my english? Is good or not?
Restarts before finalizing the installation
Friend, did the procedure to install this ROM , already have the unlocked Bootloader and Flash Recovery CWM , however when are installing the phone restarts and crashes in toot screen. Has suggested to solve this?
Using scripts can usually upgrade?
If I install the Rom Stock and use the scripts before the OTA update, I can upgrade later without the applications of Motorola?
Perfect installation
Did all the installation process and everything was perfect, just a detail that installed only by CWM recovey at TWRP was not.
Root is stable? No bootloops? I turn back to kk from 5.0 because link2sd not working in 5.0 rooted and unstable root.
Not W
Its not working on me, i'm getting a black screen at boot time.
Update bootloader
If I flash this rom my bootloader will go to version 46.87?
{
"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"
}
NOTE: PLEASE ALSO READ ALL OF THE FAQ IN THE SECOND POST. IT COVERS MANY OF THE COMMON PROBLEMS AND QUESTIONS!
CyanogenMod 13 is a free, community built, aftermarket firmware distribution of Android 6.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Changelog:
Latest commits for kernel, g2, and device d800 | d801 | d802 | d803 specific (based on date) [by review.cyanogenmod.org]
Universal changelog for d800 | d801 | d802 | d803 (based on nightly builds) [by cmxlog.com]
Requirements:
Custom recovery (either TWRP or CyanogenMod)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 12.x (no dirty flash)
Known Bugs/Issues: (fixed nightly date)
"Slowly charging" displayed. (2016-09-21)
WiFi disconnect during sleep (2016-06-24)
"Preferred network type" can't be manually switched to 3G or 2G (2016-02-05)
Can't seek within songs in music players (2016-02-03)
Video preview garbled in 3rd party apps (2016-01-26)
Unknown baseband. Cosmetic, eratic. (2016-01-22)
IR Port / Apps don't work, gives access denied. (2016-01-22)
Cellular calls disconnected by the remote party results in an "invalid number" error. (2016-01-22)
OTG storage (and possibly other OTG things) does not work (2015-12-07)
Bug reports for this ROM should be officially submitted via CyanogenMod's Jira bug tracking sytstem. Please fully read the FAQ entry on bugs and bug submission before submitting any tickets.
FAQ, other information:
Please read on to the second post in this thread for more information and answers to some frequently asked questions. Please read through it as I will absolutely, positively, and unequivocably NOT offer any help or answers that are already provided in that post.
Download:
D800 - download.cyanogenmod.org/?device=d800
D801 - download.cyanogenmod.org/?device=d801
D802 - download.cyanogenmod.org/?device=d802
D803 - download.cyanogenmod.org/?device=d803
Note to users: I'm not responsible if you brick your phone. See the disclaimer above.
Note to admins/moderators: I'm not a developer / contributor of CyanogenMod and not associated with Cyanogen, Inc. in any way. If this thread is inappropriate, please move/delete it.
Thanks to These People:
@Rashed97
@intervigil
@invisiblek
@PsychoGame
LG Devs
CyanogenMod Devs
Less official CM13 G2 information
Unofficial CM13 on LG G2 FAQ
The following FAQ is from me, the OP, and not from any CM officials or the device devs. I hope you all find it helpful.
What are the common problems? I'm pretty stupid and hate reading...
Users who don't seem to read: Please read the entire FAQ and don't pollute the thread with common questions. Use the "Search Thread" box at the top of the thread to look for your issue or issues like it.
Google apps force closing after an update: This is related to your choice of recovery, please read the recovery section.
WiFi disconnect while sleeping/screen off: This is not a G2 specific issue or even a CM specific issue. It's an Android issue. See: https://code.google.com/p/android/issues/detail?id=196035. Please do not pollute the forums with questions about it, at present there is no fix.
Which bootstack is recommended: None! No bootstack is recommended. Please read the section on best install method and then bootstacks to understand why you shouldn't do this.
Is it stable? I'm worried about trying new things...
Is it stable? Yes. I think it's as stable as a nightly can get. And that could change from night to night, so maybe watch the thread for a day or two and see what people are saying about the releases before installing them.
If you're worried about installing it for fear of, you know... whatever. Then don't install it. This isn't the place where I'm gonna convince you to try it. That's your decision. There's risk to everything. Understand and own the risk.
What is required for CM on the G2? What should my device have?
The required bootloader (aboot) for CM13 on the LG G2 is the KitKat (KK) bootloader. CM13 will fail to install otherwise. The minimum required bootstack (radios, laf, and other firmwares) is a KitKat (KK) bootstack, however a Lollipop (LP) bootstack will work and is preferred. CM-13.0 is bumped and thus does not require loki compatibility.
In order to have a successful update procedure, you will need a recovery that honors sepolicy. Please read the question on the recovery for further details and recommendations.
What is the best install method? Where do I start from?
The best starting point for installing this ROM is from an LG Stock Lollipop installation. While you could in fact install a Lollipop G2 bootstack and then install CM-13.0 on top of that, there's a good chance that it might fail or not work entirely well for you.
If you don't know or remember the history of ROMs on your phone, you may be much better off doing a full KDZ or TOT re-installation of LG Stock on your phone and take it all the way to Lollipop. Then proceed to root and autorec from there, upgrade your recovery and install CM. If you do this you will not require a bootstack and won't run the risks associated with installing one. Doing this sort of installation is beyond the scope of this thread. There are different files and starting points for each device. You will have to search for what works for you.
What about a bootstack? Should I use that if I don't want to update? What if I simply can't?
The recommended course of action is detailed above: return your phone to stock lollipop and then proceed to root your device and run autorec to install a recovery. If for whatever reason you simply cannot do that, whether it's because you can't or just won't, then the bootstack options are available. HOWEVER, this has led to problems for many people and is NOT recommended, not even by the devs that created them.
The bootstacks were created as a crutch for those unwilling or unable to upgrade their phones via kdz/tot or OTA methods. They update several key internal partitions for firmwares and keys and what not to bring the phone up to a base lollipop hardware standard. Not all are replaced, and the bootstacks don't do as good a job as LG's OTA's. This is why they can be problematic.
Issues: If you are absolutely set on installing a bootstack, the lg-devs recommend the lg-devs lollipop bootstack. However some people encounter problems with this as it creates a situation where the phone boots to a black screen and getting to recovery is difficult. If that's the case, you can consider installing Daniel Stuart's hybrid CAF bootstacks (or download direct from his GitHub). His bootstacks aren't recommended by the lg-devs, but they do seem to solve the issue of the black screen after boot.
A bootstack with loki support is not required for CM-13.0 to function. It is also not recommended unless you absolutely know you need it on your device. A bump-compatible bootstack is all that's necessary.
NOTE: The d803 never had an official stock Lollipop release and thus doesn't have an lg-devs LP bootstack. If your device is on a KK bootstack it should work fine, or you could use Daniel Stuart's bootstack which offers a hack to put lollipop firmwares on the d803.
IMPORTANT: If you install any of these bootstacks you run the REAL RISK of BRICKING YOUR DEVICE. Neither I, the G2 CM contributors, nor the CyanogenMod developers are responsible for anything you do to your device. Please proceed with caution before proceeding and have an understanding of what is necessary to recover your phone in case things go horribly wrong.
Which Recovery?
You need a recovery that honors sepolicy. Without that you will see Google applications force close after a CM update, and the only seeming way to fix it is to re-flash your chosen gapps. This is not a problem with a recovery that honors sepolicy properly.
The recommended recovery is Blastagator's TWRP, version 2.8.7.3 or newer. Older versions (2.8.7.1 or older) do not honor sepolicy. The CyanogenMod Recovery also works properly, and has for some time. However it is feature starved and lacks useful/advanced functions like backups or a file manager.
Do I need to install anything else? What is a Gapps?
CyanogenMod can be used standalone. However if you want things like Google's Play Store, Google Calendar Sync, and other Google services, you'll want to install a gapps zip package alongside CyanogenMod. I personally use OpenGapps but have also used SlimGapps in the past. For CM13 on the LG G2, you need a gapps for the ARM architecture and Android 6.0 (Marshmallow). Please read the entry about camera problems as it may affect your choice of Gapps.
Also, look at the FAQ entry for the recovery if you have FC issues.
In what order do I install this all?
The following is MY recommendation. It isn't necessarily law, but it works well for me. This assumes you have a custom recovery and have already booted into it. If you can't get that far, this is not the place for you to learn how. Please search XDA and look around for the relevant threads.
Suggested install order (the more emphasis I add to words, the more I want you to pay attention to them). One last tidbit of important information... The order chosen below was deliberate. I wouldn't recommend changing the order unless you know what you're doing. Here you go:
Recommended: Disconnect anything connected to your USB port, then boot into your recovery
Optional: Upgrade your recovery to the latest version
Install latest recovery zip file (Read recovery section for recommendations)
Reboot Recovery
Recommended: Do a full ROM backup, then copy the backup (and possibly your internal storage files) to your PC. The remaining steps have the potential to be destructive.
Optional, NOT Recommended: Install selected bootstack if deemed necessary
Read disclaimer above in the bootstacks section and make sure you know what you're doing
Re-read aforementioned disclaimer
Install bootstack of your choice
Reboot Recovery
Recommended: If coming from another ROM or CM 12.1, do a factory reset. CM will fail to install over another ROM's user data
Recommended: Wipe the system partition
Install the CyanogenMod zip
Optional: Install your chosen gapps package
Reboot your device and wait for first boot to complete
Need Root?
To enable the built in root on CyanogenMod you must enable Developer Options first. Go to Settings -> About phone and repeatedly press Build number until you are told you have enabled development settings. Then go to Settings -> Developer options, find the Root access option and change it to suit your needs.
My understanding about SuperSU is that it does not easily work with CM. The current "stable" version won't work and will likely cause a bootloop. Unless you've done quite a bit of research and know what you're doing, your best bet would be to stay away from SuperSU for this ROM.
Is OTG working? I can't see my attached device!
The OTG, to my knowledge (and personal experience), works. If you get a notification when you attach your OTG peripheral to your device, then OTG is working.
The PROBLEM is that Marshmallow (Android 6.0) does things differently with attached storage. Locations are all different from the way they were on previous versions of Android (Lollipop and earlier) and mount points are now auto-generated. Your chosen file manager must have been updated to work with the new 6.0 scheme. Not all of them have been.
For example, I just attached an OTG sdcard reader with an SD card inserted, and the storage was mounted at /mnt/media_rw/7E7B-0812
Helpful tip: An option is to go into the CM FileManager, navigate to /mnt/media_rw (or to your OTG device), press the Actions triplet menu in the lower left side and choose "Add to bookmarks." This should place the location into the bookmarks (when you press the hamburger menu or swipe in from the left) for easier access.
My camera doesn't seem to work!!!
We are limited to the proprietary camera libraries from LG for the G2. The latest of these is for Lollipop. That means any cameras that depend on the new Marshmallow API's to operate will fail to work properly (if at all) on our devices. A major example of this is the Nexus edition of the Google Camera. Sadly, this camera is included in many "Stock" editions of Gapps (including the popular OpenGapps distribution). To complicate matters, the "Stock" edition of these Gapps packages remove the stock AOSP/CM camera. AND because the camera is basically named for the Google Camera from the Play Store, you can't install the Play Store edition. Basically, you are stuck with a non-working camera as your only option unless you install something 3rd party.
To fix this problem you'll need to instruct your Gapps to avoid installing the "Stock" Google Camera. This will leave the AOSP/CM camera in place and allow you to install the Google Camera from the Play Store. Both of these options are preferable to the non-working Nexus edition of the Google Camera. The process is detailed in this post: http://forum.xda-developers.com/showpost.php?p=64666238&postcount=501
What about this Snap camera I've heard about?
The "Snap" camera is actually the SnapDragon camera from Qualcomm. It's optimized for qualcomm chipsets and so is faster and generally better on our hardware than other cameras. As of nightly 20160112 it is now built into the system as the default camera. You'll want read and follow the instructions in the above entry "My camera doesn't seem to work!!!" to make sure your Gapps doesn't replace it.
Bugs, I think I genuinely have them. What should I do?
Whine. Just whine and whine, no one will be annoyed at all. Actually, many people will be annoyed and there's a good chance I'll make fun of you.
The first thing you should actually do is to search this FAQ. Please read all the entries to make sure they really don't apply to you. Reading never killed anyone. If that doesn't turn up an answer, use the "Search this thread" box up at the top of the page and see if you can locate posts like yours on this thread. You may very well have a bug that others have solved, but please be mindful not to ask questions that have already been answered. Having to repeatedly answer the same questions over and over again is also rather annoying. If you really haven't found anything, then ask a question. Genuine bug reports are not uncommon and I'd like to see a little bit of a discussion before an official bug report goes in.
Finally, If you really think you have genuine bug, be it in CM generally or on the G2 specifically, you'll want to proceed to posting an official bug report on CyanogenMod's Jira. For more information on that, please read this handy post I made on how to post to Jira. Once you've done all of that, post a link to your bug report on this thread so we can all follow it.
My question isn't here... Should I private message you to ask?
No! I won't be answering any questions that are sent to me privately, UNLESS I have a previous relationship with you (if you are reading this and wondering if that means you... it probably doesn't mean you). The best you can hope for in a response is sarcasm and mockery. Ask your technical questions here, or search the thread. Or search XDA, because there are many problems that are not G2 specific. Hell, there are plenty of issues that aren't even CM specific. Google, or that search box up there... they are your friends.
Is there anyone I should thank?
Well, for me, its the people on this forum that answer questions for everyone else. Believe it or not, there are people reading this thread that DO NOT BOTHER TO READ THIS FAQ. They won't even search the thread to see if their issue has been discussed (ad nauseam) before. Yeah, they're annoying, they repeat questions, and some times they are just plain disrespectful. Usually my first instinct is to make fun of them and be as unhelpful as I can be. But I wait, and these aforementioned saints swoop in and provide help. So thank you helpful forum people. I do really appreciate it
Cm 13 for 800 and 802 are not released yet. OP - please present info about prerequisites like which bootloader or bootstack to install before.
Radac Stunghthumz said:
Cm 13 for 800 and 802 are not released yet. OP - please present info about prerequisites like which bootloader or bootstack to install before.
Click to expand...
Click to collapse
I supposed you missed the part of the post at the bottom that says it's a work in progress. The binaries for 13 were already run for the day, I figure I have till tomorrow morning before the d800 and 802 (and 803) nightlies show up and thus have to have a more complete post. Thanks for your patience.
dr4stic said:
I supposed you missed the part of the post at the bottom that says it's a work in progress. The binaries for 13 were already run for the day, I figure I have till tomorrow morning before the d800 and 802 (and 803) nightlies show up and thus have to have a more complete post. Thanks for your patience.
Click to expand...
Click to collapse
Woo hoo. Eagerly waiting. Great work CM team.
Sent from my LG-D800 using Tapatalk
epapsiou said:
Woo hoo. Eagerly waiting. Great work CM team.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Looks like I was wrong... builds are up.
Radac Stunghthumz said:
Cm 13 for 800 and 802 are not released yet. OP - please present info about prerequisites like which bootloader or bootstack to install before.
Click to expand...
Click to collapse
it's up now for D802
d802
Date Added: 2015-12-06 00:49:07
nightly Download: cm-13.0-20151206-NIGHTLY-d802.zip (296.43 MB)
sha1: 3dd09b76c4efa6eb8375162e7b2676286b68a268
Download: cm-13.0-20151206-NIGHTLY-d802-recovery.img
sha1: 45a62f3c17e922054cf18b624ab6d1b49c7c0ed9 2015-12-06 00:49:07
Click to expand...
Click to collapse
dr4stic said:
Looks like I was wrong... builds are up.
Click to expand...
Click to collapse
Thanks Mate!
OK Google voice search not working from Homescreen and OTG still broken apart from in TWRP.
Apart from that all looks good
Sent from my LG-D802 using Tapatalk
Treboeth said:
OK Google voice search not working from Homescreen and OTG still broken apart from in TWRP.
Click to expand...
Click to collapse
OK Google works for me on the home screen. Have you tried initiating it once by pressing on the mic icon? with 6.0's new permission model, Google's search app needs mic access permission before it can do anything. Maybe that's the key?
Tested OTG and adding it to the list of not working things
If I install Apex launcher OK works from the Home screen but doesn't work with Trebuchet.
Tried initiating but no go.
Clean install ie complete format in TWRP d802.
Edit.
Wiped and reinstalled works OK now [emoji4]
Sent from my LG-D802 using Tapatalk
@dr4stic
LTE cannot be disabled to the list of bugs?
chewdaniel said:
@dr4stic
LTE cannot be disabled to the list of bugs?
Click to expand...
Click to collapse
You are right... though it's an explainable bug, seems related to using the LP libril. Unlikely to be fixed, sadly
Great to see official cm13 ☺
Is anyone else getting slow charging?
Am getting a black screen after LG logo appears momentarily at bootup. D802 with lg-dev's 30d Bump LP bootloader already installed.
Have gone back to CM12.1 after returning to recovery via long-pressing PWR + VOL- buttons.
Anyone knows how to get CM13 to boot up properly in my situation? Thanks.
kaninabu said:
Am getting a black screen after LG logo appears momentarily at bootup. D802 with lg-dev's 30d Bump LP bootloader already installed.
Have gone back to CM12.1 after returning to recovery via long-pressing PWR + VOL- buttons.
Anyone knows how to get CM13 to boot up properly in my situation? Thanks.
Click to expand...
Click to collapse
Same issue here on D802.
I made a complete clean install (Wiped cache, dalvik, system & data) but CM13 won't boot.
After LG Logo it's only a black screen. I waited for about 20 minutes. But nothing happened :-/
I tried also to install it with an without Gapps, but made no difference. ROM just won't boot.
I'm back on 12.1 also for now
C--Mon said:
Same issue here on D802.
I made a complete clean install (Wipe cache. dalvik system & data) but CM13 won't boot.
After LG Logo it's only a black screen. I waited for abaout 20 minutes. But nothing happened :-/
Click to expand...
Click to collapse
Found the fix. I tried restoring just the working Boot partition from the working CM12.1 backup in TWRP after installing CM13 zip, and now it progresses to the CM boot animation. Seems like the 12-06 D802 CM13 zip messes up the Boot partition?
EDIT: Stuck at CM boot animation for 10min - back to CM12.1 for now.
Same here.. after installing CM13 on previous CM12.1 only LG logo and then black screen.
I used CAF bootstack and everything is ok on my D802.. CM13 boots.
http://danielstuart.tk/d80x.html
Dirty flash on previous CM12.1 works too..
brrrrm said:
Same here.. after installing CM13 on previous CM12.1 only LG logo and then black screen.
I used CAF bootstack and everything is ok on my D802.. CM13 boots.
http://danielstuart.tk/d80x.html
Dirty flash on previous CM12.1 works too..
Click to expand...
Click to collapse
Confirmed this works. Have progressed into "Android is starting..." screen using this method. Suggest that this info should be added to the first few posts.
Thanks, It realy works after flashing CAF Bootstack from Daniel Stuart
What gapps did you use? And what package?
Enviado desde mi LG-D802 mediante Tapatalk
Hey guys, I am making this post for everyone to see and to use as a resource.
I OWN NO THREADS THAT ARE LINKED IN THIS POST - HUGE THANKS TO THEM FOR MAKING THESE ROMS
When XDA gave us our own thread, people were really exicted to have our own thread to post ROM's to (we couldn't really find them), but Sony decided to not give us AOSP support. Which means no support from Sony, no kernel updates and no vendor sources, so at this point we were really stuck. There has not been a custom ROM from sources (just hang on, there is, I'll explain in a sec) so that means no CM-based ROM's. Until this point, we only have incomplete, buggy ports and UI modified stock ROM's with some optional settings, but we are still stuck on a stable 4.4.2. So there had to be a miracle...
And there was one.
@Caio99BR made a breakthrough the other day, starting with a custom kernel (Which you can find right here) and then he started on TWRP (a custom recovery which you can find here) and then he got to building CM11 from scratch. Not a port, from sources which we have built over the years. Again, you can find CM11 here. Again, congrats to @Caio99BR for building that kernel, recovery and ROM. He is developing it every day, and soon it'll be stable. Go check him out and give his profile some love
Well done also to the people that have built these ROM's that I am about to mention. Use this as a resource for these ROM's, as most are outdated. I will update this post if I find another ROM, and if I miss you, don't hesitate to comment or PM asking for your ROM to be put up here.
@Killawave 's KillaMade 4.4 ROM - http://forum.xda-developers.com/xperia-e1/development/rom-killamade-v1-1-t3174045
@Kizoky 's CM11 4.4.4 port (not being updated) - http://forum.xda-developers.com/xperia-e1/development/port-cyanogenmod11-4-4-4-xperia-e1-t3217383
@ᵀᴴᴱK!D ᴼᴿᴵᴳᴵᴻᴬᴸ ツ™ 's Illuminated ROM 4.4 for E1 & E1 Dual - http://forum.xda-developers.com/xpe...minated-rom-xperia-e1-d2005-kk-lb-ub-t3230441
@Siokrismarios 's Unoffical CM12 for E1 (in progress, no download link) - http://forum.xda-developers.com/xperia-e1/development/cm-12-xperia-e1-progress-t3171220
@THEZAK 's Unoffical CM12 for E1 (in progress, no download link) - http://forum.xda-developers.com/xperia-e1/development/xperia-e1-unofficial-cm12-t3232545
@Siokrismarios 's CM11 port for locked bootloaders (usable on unlocked don't worry ) - http://forum.xda-developers.com/xperia-e1/development/e1-cyanogenmod-11-locked-bootloaders-t3228810
@ᵀᴴᴱK!D ᴼᴿᴵᴳᴵᴻᴬᴸ ツ™ 's XperiAOSP ROM for E1 & E1 Dual (I'm currently using this one) - http://forum.xda-developers.com/xperia-e1/development/xperiaosp-rom-e1-d2005-lb-ub-e1-dual-t3231513
@Kizoky 's Kizolicious ROM for E1 & E1 Dual (not released, will be in the future) - http://forum.xda-developers.com/xperia-e1/development/kizolicious-e1-rom-single-dual-t3283216
and some useful links towards rooting, flashing and debloating ZIP's:
@mai77 's Xperia E1 all-in-one help (flashing, rooting and all) - http://forum.xda-developers.com/xperia-e1/development/e1-xperia-e1-d2005-semi-official-dev-t2718947
@Kizoky 's Debloater scripts for E1 + Performance tweaks - http://forum.xda-developers.com/xperia-e1/development/flashable-debloater-xperia-e1-t3098724
@George0501 's guide on installing custom recoverys - http://forum.xda-developers.com/xperia-e1/development/tutorial-root-install-recovery-xperia-t3083024
@Sony 's Link to unlocking your bootloader (please note, your phone may not be able to be unlocked. To check, type *#*#7378423#*#* into the dialler to open the service menu, then go Service Info > Configuration > Rooting Status. If 'Unlock bootloader' says no, you can't unlock it.) - http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
And, really that's all. I hope you appricated this post - it took me a long time to make, and if you did give it a :good:. All ROM's here belong to their respected owners - I do not own them.
I hope this helped you, and if so enjoy the new freedom of Xperia E1!
Oh dear, I just realised I posted this in the wrong section, can a mod move it for me? sorry about that
xeonyt12 said:
Oh dear, I just realised I posted this in the wrong section, can a mod move it for me? sorry about that
Click to expand...
Click to collapse
You need to contact a mod to him do this.
Thanks for mentions but this is a little bit fanboy, just saying
Caio99BR said:
You need to contact a mod to him do this.
Thanks for mentions but this is a little bit fanboy, just saying
Click to expand...
Click to collapse
Haha, wasn't suppost to come out that way, just showing some apprication XD
Good job, again, on CM11 for E1, will start using it soon
Just saying, Kizolicious may not be based on Stock ROM
I will wait a bit more until we can finally build ROMs ourselves, then I can finally mod the ROM the way I had planned (Kizolicious 11, Kizolicious 12.1, etc..)
Awesome, i'll update when it's confirmed. I don't think it's a problem about this thread being in here; its just easy access to the threads.
Update: Not updating this thread anymore, I no longer own this device and nothing's really changed anyways. Good luck devs with this device.
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?
Hi
I see in the support page of the OnePlus website, the downloads page have been removed. It only lets me download the latest version of OxygenOS, where can I download older versions still? And why are they doing this?
I can't help to think that they are going to kill off the downloads.oneplus.com website as well. If that is the case, will XDA have OxygenOS listed on their forum in the ROM section of OnePlus devices?
Thank you
333robbie333 said:
Hi
I see in the support page of the OnePlus website, the downloads page have been removed. It only lets me download the latest version of OxygenOS, where can I download older versions still? And why are they doing this?
I can't help to think that they are going to kill off the downloads.oneplus.com website as well. If that is the case, will XDA have OxygenOS listed on their forum in the ROM section of OnePlus devices?
Thank you
Click to expand...
Click to collapse
They are all still there. You need to click on the link to see the older ones.
Edit: I just noticed what you mean after looking at the support page. I've never used that page but have always gone directly to the download site. Hmm
Sent from my OnePlus3T using XDA Labs
Thanks for having a look, do you think they will kill off the downloads page on their domain?
333robbie333 said:
Thanks for having a look, do you think they will kill off the downloads page on their domain?
Click to expand...
Click to collapse
Not sure about OnePlus's history on this (keeping the old download links alive). But I never bet on anything (download-wise) staying on the internet forever. If older versions are important to you, then I would recommend saving them to your PC or some storage device. Storage is cheap nowadays. I always keep versions of old stock ROMs, TWRP backups, etc on my computer. Maybe that is the pack rat in me. But I tend to be over-prepared for any eventuality.
The threads below regarding the official updates have a lot of links to various previous versions. Good number of folks post links on non-OnePlus mirrors (Google Drive, other file sharing websites) and you can often find these links interspersed throughout the thread. The first thread is the current official OOS thread. The second thread, is the old one from FunkWizard, which has a lot of links to older versions - depending on exactly how "old" you are looking for. But again, those links won't last forever (some are already dead).
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
[UPDATE] OnePlus has officially killed that site!!!!!
Try to go to downloads.oneplus.com and it redirects to their main page with only 1 ROM!
333robbie333 said:
Try to go to downloads.oneplus.com and it redirects to their main page with only 1 ROM!
Click to expand...
Click to collapse
Every version of OxygenOS for the 3T posted here on my AFH profile:
OxygenOS Stable Images
OxygenOS Open Beta Images
OxygenOS Special Images (for restoring to "Out of the box" new. Requires a Windows PC.)
SpasilliumNexus said:
Every version of OxygenOS for the 3T posted here on my AFH profile:
OxygenOS Stable Images
OxygenOS Open Beta Images
OxygenOS Special Images (for restoring to "Out of the box" new. Requires a Windows PC.)
Click to expand...
Click to collapse
Thank you so much! I feel that this should be listed on XDA, have you suggested it to one of the admins?
SpasilliumNexus said:
Every version of OxygenOS for the 3T posted here on my AFH profile:
OxygenOS Stable Images
OxygenOS Open Beta Images
OxygenOS Special Images (for restoring to "Out of the box" new. Requires a Windows PC.)
Click to expand...
Click to collapse
This is very minor, but I see that there is no release notes in the description, I have a lot of those for the 3T. If you like me to give it to you, please feel free to contact me
333robbie333 said:
Thank you so much! I feel that this should be listed on XDA, have you suggested it to one of the admins?
Click to expand...
Click to collapse
You don't need an admin for something like that. SpasilliumNexus can start a new thread. If it is deserving, you can ask a mod to make that thread "sticky" (but that usually takes some general consensus). Or if there is an existing applicable thread (Index, guide, etc.) then ask the author of that thread to add the links.
OnePlus pulled OOS 5.0.5 and 5.0.6 from the official Download site
Does anybody know, why OnePlus had pulled OOS 5.0.5 and 5.0.6 for the 3t?
I wonder if this is a revocation by intent (if so: why???), or just an unaware web designer. Sadly enough OnePlus doesn't like to answer my question: https://forums.oneplus.com/threads/download-oneplus-com-where-is-oos-5-0-6.933687/
Interestingly 5.0.6 download is still available for the OnePlus 3.
nvertigo67 said:
Does anybody know, why OnePlus had pulled OOS 5.0.5 and 5.0.6 for the 3t?
I wonder if this is a revocation by intent (if so: why???), or just an unaware web designer. Sadly enough OnePlus doesn't like to answer my question: https://forums.oneplus.com/threads/download-oneplus-com-where-is-oos-5-0-6.933687/
Interestingly 5.0.6 download is still available for the OnePlus 3.
Click to expand...
Click to collapse
Maybe u don't know it, but the oneplus forum is not for officials to reply to public.
Only users are mainly posting there.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Maybe u don't know it, but the oneplus forum is not for officials to reply to public.
Only users are mainly posting there.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Since the officials start threads in the forum I wouldn't have thought they don't answer questions. SCNR: I should have hijacked the 5.0.6 announcment thread... *lol* Anyway, this didn't answer the original question...