{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We will not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our instructions word by word
are unfriendly
WIKI
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Tilapia_Info
INSTRUCTIONS
First time installing CyanogenMod 12.0 to your Nexus 7 or coming from another ROM:
Read the official Wiki page
Unlock your bootloader if you haven't done so already
Flash a custom recovery via Fastboot
Push GApps and the CM 12.0 zip to your device
Boot into Recovery
Perform factory reset
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Reboot (be patient, "optimizing apps" takes a while)
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 12.0:
Push the new CM 12.0 zip to your SD card
Boot into Recovery
Flash the CM 12.0 zip from SD card
Optionally flash the most recent GApps for Lollipop if you encounter problems
Reboot (be patient, "optimizing apps" takes a while)
Upgrading from CyanogenMod 11.0:
Read the last paragraphs from http://www.cyanogenmod.org/blog/the-l-is-for-lollipop
DO A BACKUP
Push GApps and CM 12.0 ZIP to your SDCard
Boot into Recovery
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Reboot (be patient, "optimizing apps" takes a while)
DOWNLOADS
Official CM 12.0 builds: http://download.cyanogenmod.org/?device=tilapia
Google Apps: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Recovery (SR) : http://puu.sh/ftbeN.img (md5: 18c7841b395e5f6f04718efd65123bc0)
BUGS
Report bugs for nightly builds at https://jira.cyanogenmod.org/browse/NIGHTLIES. Please keep in mind that bugs are expected on these builds. If you want something stable, choose the Snapshot branch.
Tilapia specific features
CMHW: Adaptative Blacklight (Nvidia SmartDimmer)
F2FS support (you can use both ext4 or f2fs, no need of patches or custom kernels)
SMS and MMS support
Tethering
MiraCast
Convert to f2fs for cm
It will wipe your data! No need of custom kernels or patches
Download the lastest twrp here
Sideload it via fastboot boot recovery.img
Go to wipe > data > Repair or Change File System > f2fs
Go to wipe > cache > Repair or Change File System > f2fs
Reboot and enjoy
FAQ
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all do not flash any supersu/superuser/superman zip package to get root. Go to Settings>Developement Settings>Root acces > Apps Only
How do I update from nightly to snapshot and vice versa?
You must download the update manually, wipe data and flash the zip file
Can i send messages with the sim?
Yes you can send SMS
Can i use my connection to create an hotspot?
Yes you can
Are these gapps <insert random gapps package here> working with cm12?
Use the suggested package
Why today I got no nightly?
There were a build error or it means there's something wrong with the rom and I've choosen to stop nightlies until the problem gets fixed
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 12.0, ROM for the Nexus 7
Contributors
linuxxxx
Source Code: https://github.com/cyanogenmod
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
Version Information
Status: Nightly
Created 2015-02-03
Last Updated 2015-05-16
F2Fs Support
Information
Builds now have experimental support for F2FS for /data and /cache. A compatible recovery is requiried.
WARNING
The F2FS version used by CM is newer than the one used by existing ROMs, recoveries and custom kernels. Features like inline_dentry and inline_data have been enabled to save disk space and improve the performance. Those features are not available on older kernels and this can cause corruption and data loss if you switch back! Just rebooting into a unsupported recovery or any other f2fs kernel can be enough to corrupt your userdata partition. Always make a backup when you switch ROMs!
F2fs is NOT supported on /system and it will never be!
Convert to cm's f2fs from any other fs/rom
It will wipe your userdata!
If you're already on f2fs for any reason, flash a factory image to revert to stock partitions (DO NOT USE ANY OTHER WAY TO REVERT TO EXT4)
Download the this recovery
Sideload it via fastboot boot recovery.img
Go to wipe > data > Repair or Change File System > f2fs
Go to wipe > cache > Repair or Change File System > f2fs
Reboot and enjoy
FAQ
FAQ
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all do not flash any supersu/superuser/superman zip package to get root. Go to Settings>Developement Settings>Root acces > Apps Only
How do I update from nightly to snapshot and vice versa?
You must download the update manually, wipe data and flash the zip file
I switched to f2fs and I booted recovery/f2fs-kernel device, now it doesn't boot anymore, what can I do?
Read the next post about f2fs
Can i send messages with the sim?
Yes you can send SMS and MMS
Can i use my connection to create an hotspot?
Yes you can with usb and wifi tethering
Are these gapps <insert random gapps package here> working with cm12.x?
Use the suggested package
Why today I got no nightly?
There were a build error or it means there's something really wrong with the rom and I've choosen to stop nightlies until the problem gets fixed
Finally! Yehuuu! Thank you very much for so operative work. Waiting for download. Can't wait to test it!
Sent from my Nexus 7 using XDA Free mobile app
dinozaur516 said:
Finally! Yehuuu! Thank you very much for so operative work. Waiting for download. Can't wait to test it!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Nightlies should start tomorrow
linuxxxx said:
Nightlies should start tomorrow
Click to expand...
Click to collapse
Ooops!))) anyway, i am waiting for tomorrow
Sent from my Nexus 7 using XDA Free mobile app
So... They should appear sometime tonight?
cmstlist said:
So... They should appear sometime tonight?
Click to expand...
Click to collapse
http://jenkins.cyanogenmod.com/job/android/
yay!!! finally!!!
been waiting so long for this. time to download and flash
b4b4.4l1 said:
yay!!! finally!!!
been waiting so long for this. time to download and flash
Click to expand...
Click to collapse
Let me warn you: some grouper users with ext4 had problems booting on the today build, I haven't test it yet on tilapia (with ext4), but I can tell for sure f2fs is working (I have to convert mine back to ext4). Will report later.
well done mate! just a question: for f2fs installation do i need to convert the zip? ...now i'm on slimkat f2fs version...
EDIT: it seems somehow automatic!
linuxxxx said:
Let me warn you: some grouper users with ext4 had problems booting on the today build, I haven't test it yet on tilapia (with ext4), but I can tell for sure f2fs is working (I have to convert mine back to ext4). Will report later.
Click to expand...
Click to collapse
Oh, I see. I've reverted mine back to ext4 when testing out lollipop out of curiosity. Was using f2fs when running cm11 though. I'll test it out first with ext4.
Btw, I've read some comments debating about staying with ext4 or switch to f2fs. Does f2fs really give any benefit over ext4? Sorry for the dumb question which may have been asked too many times before :s
b4b4.4l1 said:
Oh, I see. I've reverted mine back to ext4 when testing out lollipop out of curiosity. Was using f2fs when running cm11 though. I'll test it out first with ext4.
Btw, I've read some comments debating about staying with ext4 or switch to f2fs. Does f2fs really give any benefit over ext4? Sorry for the dumb question which may have been asked too many times before :s
Click to expand...
Click to collapse
Yes, especially on this device. Cm supports f2fs on /cache and /data
linuxxxx said:
Yes, especially on this device. Cm supports f2fs on /cache and /data
Click to expand...
Click to collapse
Thanks for the reply. And I see from the other post here stating that now CM12 fully supports f2fs out of the box, so I guess I'll switch back to f2fs.
Thanks for the answers :highfive:
b4b4.4l1 said:
Thanks for the reply. And I see from the other post here stating that now CM12 fully supports f2fs out of the box, so I guess I'll switch back to f2fs.
Thanks for the answers :highfive:
Click to expand...
Click to collapse
Working on ext4 too. Have fun!
linuxxxx said:
Working on ext4 too. Have fun!
Click to expand...
Click to collapse
Final edit : Ah, finally I found it where to change the partition system
Btw, why restoring app+data with titaniumbackup is not recommended? Since I have several apps and games backed up with titaniumbackup
Trying it now.
First big Lollipop peeve: There is no way to disable mobile data when you are not yet connected to a mobile network. This is irritating because the default APN for my SIM card in all Android installations is wrong and any attempt to connect to that mobile network costs me several dollars per second. So every time I have flashed a new ROM on this tablet I have had to boot it without the SIM, disable mobile data first, then insert the SIM, then boot it up, then fix the APN, then I can finally turn mobile data on.
On Lollipop the mobile data toggle just refuses to show up if the SIM is out or I'm in airplane mode. So it forced me to let it connect on the wrong (expensive!) APN first before I could actually fix any of the settings. Garr.
Also still working out some Gapps issues.
cmstlist said:
Trying it now.
First big Lollipop peeve: There is no way to disable mobile data when you are not yet connected to a mobile network. This is irritating because the default APN for my SIM card in all Android installations is wrong and any attempt to connect to that mobile network costs me several dollars per second. So every time I have flashed a new ROM on this tablet I have had to boot it without the SIM, disable mobile data first, then insert the SIM, then boot it up, then fix the APN, then I can finally turn mobile data on.
On Lollipop the mobile data toggle just refuses to show up if the SIM is out or I'm in airplane mode. So it forced me to let it connect on the wrong (expensive!) APN first before I could actually fix any of the settings. Garr.
Also still working out some Gapps issues.
Click to expand...
Click to collapse
I cant test cuz my sim has no internet connection, I just use it to test ril, but it looks like I can toggle it on off with no problems, try to manage it via adb shell su -c 'svc data disable'
And adb shell su -c 'svc data enable'
Updated op, now you can find SR (Cyanogen Simple Recovery), it's great for cm and it can manage both ext4 and f2fs, but there's no toggle to switch to f2fs or ext4
Ah, dang, I'm still getting error to change /data partition to f2fs. It gives me:
E: Unable to wipe '/data'
E: Unknown MTP message type: 1
E: Error changing file system.
What should I do? Or should I use the old modded TWRP 2.7.0.0 all-f2fs recovery from the thread?
/system and /cache went just fine and switched to f2fs.
b4b4.4l1 said:
Ah, dang, I'm still getting error to change /data partition to f2fs. It gives me:
E: Unable to wipe '/data'
E: Unknown MTP message type: 1
E: Error changing file system.
What should I do? Or should I use the old modded TWRP 2.7.0.0 all-f2fs recovery from the thread?
/system and /cache went just fine and switched to f2fs.
Click to expand...
Click to collapse
See op
Related
{
"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"
}
PAC-ROM is built with our own tweaks and options, including picks and features from the best ROMs out there!
Why choose among ROMs, when you have All-in-One !!
* By flashing this, you automatically void your warranty! *
* If your phone breaks, blows up or runs away from you, do not cry to us! *
* Do not ask for ETAs!! *
* Download the ROM and GApps *
* Reboot to recovery *
* Wipe data/factory reset *
* Flash the ROM and then GApps *
* Reboot your phone *
* Enjoy *
* Download the latest version *
* Reboot to recovery *
* Flash the ROM *
* Wipe both dalvik cache and cache *
* Reboot your phone *
* Enjoy the latest version of PAC-ROM *
* Submit a bug report *
* Submit a patch *
* None for now *
* PAC-ROM Downloads *
* GApps *
* PAC-ROM Team *
* Cyanogen Team *
* AOKP Team *
* DirtyUnicorns *
* SlimRoms *
* Vanir *
* Omnirom *
* Special thanks to all our Build Bot Providers (see Contributors list for all names) *
* PAC Graphix Team - Graphics, logos and images (see Contributors list for all names) *
* And of course, thank you for your love and support! *
Support us with these banners:
Help with server costs
XDA:DevDB Information
PAC-ROM, ROM for the AT&T HTC One X
Contributors
josegalre
Source Code: https://github.com/PAC-man/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 3.0
Beta Release Date: 2015-09-24
Created 2015-03-08
Last Updated 2015-09-24
F2FS
Starting from nightly of 17/MARCH/15 F2FS is now available. our kernel always support ext4
if you do not want to use F2FS there is no problem, you do not have to do anything the kernel automatically detect the type of file system.
if you want to use F2FS note these considerations:
* Do a clean install!
* F2FS reserve about 200MiB of space on each partition, so you can not use that space
* You must format the data and cache partition using TWRP recovery with F2FS support(can use this unofficial version compiled by me),
* When you format in F2FS as in any installation clean your files will be deleted, please do backup their stuff
* Only you can format data and cache partitions
How to format in F2FS?
into TWRP
1 - Go to Wipe -> Advanced Wipe.
2 - Select /data or /cache (one partition at time, if you wish to use f2fs on both partitions, you will need to do it later in this way) and select Repair or change filesystem.
3 - Select Change filesystem.
4 - Select F2FS.
5 - Slide to agree for formatting selected partitions.
6 - Done
Reserved
Feeling awesome seeing PACMAN lollipop ROM for evita,
Reserved ?
Cann't wait to try it.
this ROM works incredibly well! i mean, wow. almost no lag, everything is smooth and snappy.
and with Torched kernel and F2FS, it just flies!
question: the download link eventually brings me to BasketBuild where nightly builds reside. very nice, but do you guys maintain a changelog? how do i know when it's worth to download a new build?
thank you so much for your great work!
--Pavel
thelonewolf_pav said:
this ROM works incredibly well! i mean, wow. almost no lag, everything is smooth and snappy.
and with Torched kernel and F2FS, it just flies!
question: the download link eventually brings me to BasketBuild where nightly builds reside. very nice, but do you guys maintain a changelog? how do i know when it's worth to download a new build?
thank you so much for your great work!
--Pavel
Click to expand...
Click to collapse
Were you using CM12 prior by chance? If so, can you compare the two with respect to battery performance and other key areas? Thx
droydr said:
Were you using CM12 prior by chance? If so, can you compare the two with respect to battery performance and other key areas? Thx
Click to expand...
Click to collapse
I was using Candy5.
Both are equally bad battery-wise (won't last a day with gapps enabled, unless you tweak the system).
However, this ROM is an order of magnitude faster than Candy5 1.0. I'm not kidding. I get near zero lag no matter what I do (I have F2FS, which speeds things up a lot on its own)
thelonewolf_pav said:
this ROM works incredibly well! i mean, wow. almost no lag, everything is smooth and snappy.
and with Torched kernel and F2FS, it just flies!
question: the download link eventually brings me to BasketBuild where nightly builds reside. very nice, but do you guys maintain a changelog? how do i know when it's worth to download a new build?
thank you so much for your great work!
--Pavel
Click to expand...
Click to collapse
our change log is our gerrit friend http://review.pac-rom.com/#/q/status:merged and http://pvyparts.com/?device=evita , you can see everything new in this place xD
I'm making adjustments in my personal group on F2FS if all goes well in a couple of days this ROM will have official support for F2FS
Sorry if I'm slow to respond, sometimes step occupied with the study, please mention me in the comments so the notification arrive to my email and I'll see much faster!
also I'm making adjustments for using zram! in the tests I've done evita it is faster!
josegalre said:
our change log is our gerrit friend http://review.pac-rom.com/#/q/status:merged and http://pvyparts.com/?device=evita , you can see everything new in this place xD
I'm making adjustments in my personal group on F2FS if all goes well in a couple of days this ROM will have official support for F2FS
Sorry if I'm slow to respond, sometimes step occupied with the study, please mention me in the comments so the notification arrive to my email and I'll see much faster!
also I'm making adjustments for using zram! in the tests I've done evita it is faster!
Click to expand...
Click to collapse
Thanks man! these are good news indeed!
about zram: are you guys sure it's a good idea? i hear using zram makes almost no sense on android: the compression doesn't work too well on the type of data we're storing in memory, so you get almost no memory gain but waste a lot of cpu power.
i once tried to enable zram in my rom on my very old but still kicking htc hd2 -- and reverted really quickly it slowed the things down a little bit and gave absolutely no improvement on memory
thelonewolf_pav said:
Thanks man! these are good news indeed!
about zram: are you guys sure it's a good idea? i hear using zram makes almost no sense on android: the compression doesn't work too well on the type of data we're storing in memory, so you get almost no memory gain but waste a lot of cpu power.
i once tried to enable zram in my rom on my very old but still kicking htc hd2 -- and reverted really quickly it slowed the things down a little bit and gave absolutely no improvement on memory
Click to expand...
Click to collapse
PAC is doing awesome, I followed the steps st forth by thelonewolf_pav, and it is just awesome, but for some reason my internal storage for my system got filled up really quickly, with just Gapps, facebook, Titaniam Backup, Trickster Mod, Kernal Turner and whatsapp. It says Swap is not enabled, so I don't think its swap that is taking the space. Everything else is good. Also I just saw in the changelog u added support for f2fs, so is it official now? Since I am already running on f2fs like
thelonewolf_pav
Click to expand...
Click to collapse
, do I need to do anything special when I flash the new rom zip with official f2fs support?
harpin14789 said:
PAC is doing awesome, I followed the steps st forth by thelonewolf_pav, and it is just awesome, but for some reason my internal storage for my system got filled up really quickly, with just Gapps, facebook, Titaniam Backup, Trickster Mod, Kernal Turner and whatsapp. It says Swap is not enabled, so I don't think its swap that is taking the space. Everything else is good. Also I just saw in the changelog u added support for f2fs, so is it official now? Since I am already running on f2fs like , do I need to do anything special when I flash the new rom zip with official f2fs support?
Click to expand...
Click to collapse
Starting from nightly of tomorrow F2FS is now available. our kernel always support ext4
if you do not want to use F2FS there is no problem, you do not have to do anything the kernel automatically detect the type of file system.
if you want to use F2FS note these considerations:
* Do a clean install!
* F2FS reserve about 200MiB of space on each partition, so you can not use that space
* You must format the data and cache partition using TWRP recovery with F2FS support(can use this unofficial version compiled by me),
* When you format in F2FS as in any installation clean your files will be deleted, please do backup their stuff
* Only you can format data and cache partitions
How to format in F2FS?
into TWRP
1 - Go to Wipe -> Advanced Wipe.
2 - Select /data or /cache (one partition at time, if you wish to use f2fs on both partitions, you will need to do it later in this way) and select Repair or change filesystem.
3 - Select Change filesystem.
4 - Select F2FS.
5 - Slide to agree for formatting selected partitions.
6 - Done
josegalre said:
Starting from nightly of tomorrow F2FS is now available. our kernel always support ext4
if you do not want to use F2FS there is no problem, you do not have to do anything the kernel automatically detect the type of file system.
if you want to use F2FS note these considerations:
* Do a clean install!
* F2FS reserve about 200MiB of space on each partition, so you can not use that space
* You must format the data and cache partition using TWRP recovery with F2FS support(can use this unofficial version compiled by me),
* When you format in F2FS as in any installation clean your files will be deleted, please do backup their stuff
* Only you can format data and cache partitions
How to format in F2FS?
into TWRP
1 - Go to Wipe -> Advanced Wipe.
2 - Select /data or /cache (one partition at time, if you wish to use f2fs on both partitions, you will need to do it later in this way) and select Repair or change filesystem.
3 - Select Change filesystem.
4 - Select F2FS.
5 - Slide to agree for formatting selected partitions.
6 - Done
Click to expand...
Click to collapse
I already have a f2fs enabled TWRP, and I followed what thelonewolf_pav did to get f2fs without losing data. I took backups of cache and data partitions and changed their names from ext4 to f2fs and restored which made TWRP reformat the partitions as f2fs and also restore my data, so that is how I am f2fs, given that, would I be alble to just flash the rom zip and gapps?
Thanks
josegalre said:
Starting from nightly of tomorrow F2FS is now available. our kernel always support ext4
if you do not want to use F2FS there is no problem, you do not have to do anything the kernel automatically detect the type of file system.
if you want to use F2FS note these considerations:
* Do a clean install!
* F2FS reserve about 200MiB of space on each partition, so you can not use that space
* You must format the data and cache partition using TWRP recovery with F2FS support(can use this unofficial version compiled by me),
* When you format in F2FS as in any installation clean your files will be deleted, please do backup their stuff
* Only you can format data and cache partitions
How to format in F2FS?
into TWRP
1 - Go to Wipe -> Advanced Wipe.
2 - Select /data or /cache (one partition at time, if you wish to use f2fs on both partitions, you will need to do it later in this way) and select Repair or change filesystem.
3 - Select Change filesystem.
4 - Select F2FS.
5 - Slide to agree for formatting selected partitions.
6 - Done
Click to expand...
Click to collapse
for f2fs, does only the cache and data have to be f2fs, why doesn't the system partition switch to f2fs instead ext4?
harpin14789 said:
I already have a f2fs enabled TWRP, and I followed what thelonewolf_pav did to get f2fs without losing data. I took backups of cache and data partitions and changed their names from ext4 to f2fs and restored which made TWRP reformat the partitions as f2fs and also restore my data, so that is how I am f2fs, given that, would I be alble to just flash the rom zip and gapps?
Thanks
Click to expand...
Click to collapse
yep only flash rom and gapps, them reboot xD
harpin14789 said:
for f2fs, does only the cache and data have to be f2fs, why doesn't the system partition switch to f2fs instead ext4?
Click to expand...
Click to collapse
for the moment not yet. to use F2FS on the system partition we have to modify our script installation, possibly in a future we can use, but at the moment no. xD
Fixed*
Respected brothers, kindly help me with the dialer bug. Sometimes my app freezes on hanging up until reboot, but the rest works fine. Im unable to find a fix for it. Is there any need of update anything or any idea, any fix? Plz bro!!!
My mobile looking awesome on ur works, but except this bug.
Dialer bug fix:
Dialer -> settings -> number look up, turn off everything. But didnt work for me ?
VPN is not working for me on build 03/26 ...
Anyone experiencing this?
kateyblue said:
VPN is not working for me on build 03/26 ...
Anyone experiencing this?
Click to expand...
Click to collapse
some logcat friend?
you did a clean install? xD
Does every nightlies require a clean install?
I flashd above 3/09, i got errors in downloading apps from playstore, tried to fix it by flashing gapps, i got stuck in Htc logo.
Atlast i clean wiped. EVERYTHING IS GOING GOOD. KEEP UP THE WORK ?DEVs?
Jaheen said:
Does every nightlies require a clean install?
I flashd above 3/09, i got errors in downloading apps from playstore, tried to fix it by flashing gapps, i got stuck in Htc logo.
Atlast i clean wiped. EVERYTHING IS GOING GOOD. KEEP UP THE WORK DEVs
Click to expand...
Click to collapse
I just dirty flash the ROM, flash SU to keep root, and wipe caches. Works great.
This is the only LP ROM that lets me listen to Pandora while reading Kindle (or any other program) at the same time.
:good:
Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
How it looks :
{
"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"
}
* This must work on all devices model quark (XT1250 and XT1254) or quark_umts (XT1225) * custom ROM may display only quark
To know you device model just open the app Terminal Emulator for Android and see the quark after the @ like below.
Main download folder
Mirror download folder
The folder contains the Mod TWRP version base on the latest official with proper support to all android versions (The one from TWRP site doesn't have the proper support For Nougat, Oreo or newer OS's, I tryed to push the changes so the one from they site can be updated they did not answer me so I give it up), the mod other than having the proper support for all OS that prevent bug as the "Bootloop to TWRP after a Factory Reset" it has extra backup option (Radio/Modem, boot logo etc), NTFS support for USB-OTG devices, all possible TWRP languages, full encryption support (For Nougat and earlier, Oreo and up encryption is not suported) and etc improves...
All the extras featuring can be seen in the Changelog click here
Big thanks:
A big thank for those that donating to thanks for my work on TWRP.
@ChazzMatt for his donation, and his help on many other threads of Moto Maxx on XDA.
Renan R. R. for his donation
And all the other users that I contribute.
On the developer side, thanks to:
@Dees_Troy for his work on TWRP, for the tutorial and help to bring the official support...
@Skrilax_CZ for his hard work on building the first stable CM to this device
@Aadi for a tutorial.
@respider for his original work on TWRP for quark.
Developer donation link:
To donate via paypal click here
No other donation option is available.
XDA:DevDB Information
TWRP For all Quark(Moto Maxx/Turbo and Droid Turbo)
Contributors
fgl27
Source :
Android :
omnirom M source
LineageOS source
Device :
Device tree for omnirom source
Device tree for LineageOS base source
Kernel tree for LineageOS source
TWRP Version: 3.3.1
Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-08-16
Last Updated Check changelog (click here)
I use many tutorial to make this TWRP, here some to help those who want to do the same.
tags: how to port TWRP recovery, how to compile TWRP recovery, how to make TWRP recovery.
http://forum.xda-developers.com/showthread.php?t=1943625
http://forum.xda-developers.com/showthread.php?t=2294800
http://wiki.cyanogenmod.org/w/Build_for_quark#Build_CyanogenMod_and_ClockworkMod_Recovery
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://source.android.com/source/building.html
https://source.android.com/source/building-running.html
https://source.android.com/source/initializing.html
http://review.cyanogenmod.org/#/c/89474/1/recovery.te
Check Changelog click here
How to install it.
Using Fastboot:
Download mfastboot
The fastboot I share is need replace fastboot with mfastboot in the commands below...
Copy the file you download form OP to the folder of fastboot and use the command in the bootloader screen
Code:
fastboot flash recovery recovery_name.img
! replace recovery_name with the name of the file, example:
Code:
fastboot flash recovery twrp-3.0.2-0-quark.img
Via app Flashify (for root users)
If you have root, try Flashify is really simple.
Install the app, download the recovery to the phone internal memory, open the app, chose recovery image, chose from file, confirm and flash, after you will go straight to the new recovery.
Via TWRP:
Yes TWRP can flash images recovery and boot image.
- install
- images... (is in the bottom right of the screen)
- select the image and image type (boot or recovery)
- swipe
- reboot to test, to recovery if flash a recovery or to system if is a boot...
...............................................................................
keep system read only?
This will be asked in the first time you boot to recovery after flash the recovery, if you not accepts it TWRP may be replace by the previously recovery of your device, but read way...
Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
..............................................................................
Note about restore from Stock 5.x.x to 4.4.4 and vice versa:
The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.
I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.
TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.
That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.
To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>
For Kitkat android 4.4.4 choose EXT4
For lollipop android 5.x.x choose F2FS
Swipe to change
Now restore.
But be aware that the data partition is were internal memory is, so if you change the file system you will loose all the files in internal memory
The wipe of internal memory doesn't happening if you only wipe data partition without change file system.
This will not affect custom ROM, but i recommend to use f2fs.
.....................................................................................
Note about encrypt
Test done in Nougat in the link below
Last Nougat test
Test done in Lollipop below
TWRP supports backup a encrypted system, but i only test this on lollipop stock ROM.
This is a simple description how to encrypt backup and restore the encrypted system.
Stock ROM
You can only encrypt if you have stock recovery and no modification to yours ROM, that means no root or rooted app like xposed modules etc, so if you have uninstall everything and do a full un-root.
To encrypt go to setting>secure>encryption the process take a while...
If you already have stock encrypted ROM you can flash TWRP and make a backup of it.
To remove the encryption you need to flash back the stock recovery and do a factory reset in Settings>Backup & Reset>Factory Reset
Factory Reset will deleted all the files of the device! so make a copy of important data...
Wiping all the partition in TWRP will not remove the encryption.
After the device finish the factory reset all the data of you phone will be deleted and the encryption will be gone.
Now you can flash back TWRP again and have fun...
If you need to restore that encrypted backup you can but after it finish restoring you will see that it is un-encrypted.
Custom ROM
I tested encrypt on custom Marshmallow AOSP base ROM (all the CM's), it is not need any recovery the only thing that is need to encrypt is that the encryption block of data be clean before encrypt.
Cleaning the encryption block of data
TWRP can't clean that so if the user encrypt the device the only way of clean that is by erasing the data via fastboot:
Code:
mfastboot erase userdata
The down side of it is that the partition will be erased lost every file of data and internal memory + when the system boot the data partition will be formatted as EXT4 that have a small performance lost over F2FS, to have it back to F2FS is need to give the command then start the OS, after the device finish boot and optimized it will format the partition and is need to go back to recovery and format the data as F2FS, going on wipe > advanced > select data > "repair change..." >change file sys> F2FS... then boot to the device and use it...
Note about official TWRP, USB driver via USB-OTG work, but your driver need to be formatted as FAT32(small drivers) or exFAT (big drivers), on the Mod version I have update the NTFS support and it now works
...........................................................
Collection of "Special_flash_zip" to go with the Mod TWRP
As some things are not directly attainable through TWRP menus, but they can be achieved via extra zips...
Clean_modem_status.zip
Logo_Flasher.zip
Modem_Flasher.zip
Clean_modem_status.zip
as the name implies this will erase the modem status partition, and erase any bad modem status, this can help in situations were the users is with some radio problem, one most famous on Quark is when user can get a GPS lock...
I test the GPS after flashing this and it works... (I did not had a GPS problem, but will test after I get one...)
Logo_Flasher.zip
This is a zip that can flash logo.bin via TWRP, is need of the user to have the logo.bin then place it inside of the root of the zip, then flash it over TWR.
Modem_Flasher.zip,
This is a zip made to flash the Radio.img + Clean modem status, thus achieving the update of Radio and clean any bad old radio status.
This zip is empty need the user to add the files on the future I will make a zip with the radio image inside... the below explain how to put the files inside.
As on Quark the radio.img is complex image that can't be flash via TWRP it is need to have a special zip, this zip contains the content of radio image after the user have flash it via fastboot, then for that I made this tutorial in how to use the zip, see the below hide...
Tutorial how to make this zip to work...
This zip must be used with a full backup of stock Modem image that can be achieve via app using apk called partition backup or via ADB
1# APP process... config the app Click on the tool, then in backup formats section, mark only Raw partition image
The partitions name to backup are
modem
mdm1m9kefs3
the file must be in sd/Partitionsbackups, the file names need to be just like describe below
before you put they on the zip so rename the files according the below...
modem.img
mdm1m9kefs3.img
make no modifications to the files, and place it on the root of this zip
The just flash the zip via TWRP
#############
2# ADB process, you must have SuperSu from Chainfire installed before making this, CM root will not work.
use the commands "adb devices" to check if the device is connected it will show the device serial number if it is...
then do the next two lines
Code:
adb shell
su
* after command "su" press enter 3 or more times... until the cmd displays
[email protected]:/ #
then... do the next 4 lines
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.img
dd if=/dev/block/mmcblk0p32 of=/sdcard/mdm1m9kefs3.img
the files will be on the internal memory, the file names need to be just like describe below before you put they on the zip
modem.img
mdm1m9kefs3.img
make no modifications to the files or to the file name, and place it on the root of this zip
The just flash the zip via TWRP
The recommendation is to make a modem backup of yours device after you get a GPS lock, and store it to use whenever you need because you have a radio related problem, or make one to share on XDA with other users, be aware to share Radio zip and describe from with device model and ROM you pull it from, because flashing other device Radio may cause problem...
............................................................
This TWRP is theme-able, go to the tread to change the looks:
[THEME][TWRP] TWRP Materialised - Dark / Light / Play
Support, any bugs and errors just post in here, I will answer as soon as possible.
Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk
icondeg said:
Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk
Click to expand...
Click to collapse
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:
baybutcher27 said:
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:
Click to expand...
Click to collapse
It works fine!!!
Thanks for all
Enviado desde mi Moto MAXX mediante Tapatalk
omg great work! congrats
muito obrigado!
Awesome work! Thanks man! Can't thank you enough!!
Thank you!
Paypal donation sent.
Confirmation number: 08S12817NX2219226.
Thank you guys i really appreciate the supporter. Of every one.
Small, but big improvement change.
Change log in the 2° post. The TWRP now is much faster to wipe, restore or install a ROM, no more lag to format...
Ok
I believe in you men
If you say that this no affect anything, that's fine by me
Regards
Enviado desde mi Moto MAXX mediante Tapatalk
Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
baybutcher27 said:
Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
Click to expand...
Click to collapse
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Jejejeje
Regards
Enviado desde mi Moto MAXX mediante Tapatalk
icondeg said:
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Click to expand...
Click to collapse
@w4tchout
@Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
ChazzMatt said:
@w4tchout
@Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
Click to expand...
Click to collapse
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
##W4TCH0UT## said:
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
Click to expand...
Click to collapse
I don't know much about Kernel yet so i cant see what is going wrong in yours...
But i find a workaround, to compile the recovery.img without compile the boot.img i generated a boot.img but use pre build dt + kernel.
That way i can compile recovery in under 13 min and without a kernel folder in the source, before it take over 30, and when i'm resolving bug and error, how much fast i can produce a image better.
The workaround i copy from victara and put in the omni folder of my device source, is need the mkbootimg.mk + dtb (dt image renamed) + kernel.
Then check BoardConfig.mk kernel lines, the dt and kernel i use from a previously build of my on, after you have one no need to compile the kernel every time...
Don't know if this will help but this way you may grub a previously working dt + new kernel or vice versa, and combine to see what works.
My CM source folder is working but not update do to that yet but i believe will work in others source other then omni.
if something work or not let me know.
I finished all the tested with TWRP compile in omni source, i update the download link.
No need to change TWRP unless you use a encrypted device, or you wanna to test it.
Put a note about encryption on 2# post.
If any bug found let me know.
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
respider said:
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
Click to expand...
Click to collapse
too bad bro
i hope you're ok
regards!
#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.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM13.0 Marshmellow Nightlies brought to you by Open Desire Project and TeamCodefire as a continuum to CM 11.0, CM 12.0 and CM 12.1 builds. Builds are generated automatically on Mon/Wed/Fri/Sun. Process starts around 00:30 PST/PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Last 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
Mustaavalkosta
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card
Reboot to recovery
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON
Reboot and enjoy
Update instructions:
Download Nightlies
Put the file on SD card
Reboot to recovery
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON
No need to flash gapps as CM backuptool script should take care of them (results may vary depending on which gapps package you are using)
Reboot and enjoy
Kernel
Source: github
Compiler: stock AOSP gcc-4.8
Branch: cm-13.0
Kernel Version: 3.0.101
defconfig: saga_defconfig
Contact:
My Google+
#opendesireproject @ freenode
Donations:
For build server & hosting: codefi.re (use the donation button)
Do not donate to me, but if you insist on donating, I suggest you donate that money to Mustaavalkosta or EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Download and install the latest recovery here.
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: Hey, my old phone is running the latest Android version, i want to thank someone!
A: Press thanks button here
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM13.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm13.0
cd cm13.0/
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-13.0/local_manifest.xml -O .repo/local_manifests/local_manifest.xml
repo sync
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: My problem is not listed here.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[ROM][UNOFFICIAL] CyanogenMod 13.0 Nightlies OpenDesireProject, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl, PhantomShadow
Source Code: https://github.com/OpenDesireProject
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Twrp 2.8.7.0
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-12-04
Last Updated 2017-01-04
Bugs (Device specific):
Glitches here and there
Headset Mic in call
SAGAOPT SETUP INSTRUCTIONS (see also Mustaavalkosta dhd post)
Disclaimer: You will lose everything on your sdcard if you follow these instructions so take appropriate steps to secure your data before continuing. Also this will be a "clean flash" from the start due to different partition layout.
Prerequisites:
TWRP for sagaopt by @jrior001
saga cm13 zip
Gapps and addons if you want them. IIRC, there was around 400-500MB space left on new /system partition after flashing base gapps package so there's a bit more room for addons.
If you have already partitioned your sdcard you may want to repartition it to have only single partition because you won't benefit from having separate sd-ext partition with this variant build. I won't write anything about this as I expect you can reverse what you have done yourself.
Installation instructions:
Flash TWRP in fastboot or your current TWRP (Install > Images > etc.)
Reboot to recovery even if you are already in TWRP. You need to reboot to be in newly flashed sagaopt TWRP.
Wipe cache and system under Advanced wipe.
Convert your sdcard to either EXT4 or F2FS under Advanced wipe by choosing data partition > Repair or Change File System > Change File System > EXT4 or F2FS.
(Optional) If you had your old /data partition formatted as F2FS you also need to convert it to EXT4 meaning converting system partition in the sagaopt recovery.
At this point your sdcard is completely empty so you will need to move the ROM zip and any additional zips into sdcard or use adb sideload.
Install cm-13-XXXXXXXX-UNOFFICIAL-sagaopt.zip and gapps.
Reboot
kylon said:
Bugs (Device specific):
Glitches here and there
Headset Mic in call
Click to expand...
Click to collapse
Thank you very much Kylon for putting up the thread for CM-13. I have already tried 20151203 and 20151204 nightlies with no CM Account and facing problem on flashing either Open GApps or Delta GApps for MM, it is showing Setting Wizard has stop mainly and some time Google play service has stop and System does not response all the time making setting up impossible. Anyway no problem on ROM flashing. Thanks.
It s a known problem on cm13.
You have to delete setup wizard
kylon said:
It s a known problem on cm13.
You have to delete setup wizard
Click to expand...
Click to collapse
Thanks for your prompt reply. I shall do that.
<Reserve>
aakashasaj said:
<Reserve>
Click to expand...
Click to collapse
Hi Kylon,
I am wondering if the keyboard and google play service stop could be solved on CM-13 sagaopt. Thank you very much.
yea, the official cm-13 is still in testing, every fc will be fixed when cm is more stable
f2fs test
kylon said:
yea, the official cm-13 is still in testing, every fc will be fixed when cm is more stable
f2fs test
Click to expand...
Click to collapse
Thanks. I will try the kernel.
kchaisu said:
Thanks. I will try the kernel.
Click to expand...
Click to collapse
It caused boot loop at the HTC logo. Thanks for your kind contribution. I have noticed that system partition is always formatted to ext4 no matter how you have changed to f2fs and finally it will be formatted back to ext4. Thanks.
Can you take a log?
kylon said:
Can you take a log?
Click to expand...
Click to collapse
I do not know how to take a log when it did not boot up. Please tell me. Thanks.
kylon said:
Can you take a log?
Click to expand...
Click to collapse
I flashed your kernel and everything is all right! Any bootloop I didn't get. Work well, don't see any difference.:highfive:
kchaisu said:
I do not know how to take a log when it did not boot up. Please tell me. Thanks.
Click to expand...
Click to collapse
Mmh, can you try with a clean install?
Maybe something went wrong on your phone.
Thats ok, this will not turn saga in a quad-core phone but it should be a better f2fs version, maybe faster and more stable
kylon said:
Mmh, can you try with a clean install?
Maybe something went wrong on your phone.
Thats ok, this will not turn saga in a quad-core phone but it should be a better f2fs version, maybe faster and more stable
Click to expand...
Click to collapse
I made a clean install, factory reset and all wiped except internal memory and SD-Ext and also change file system to f2fs. It did not boot up with black screen. So, if you and Lapyyy have no problem with the kernel, it should be my device problem or set up. However, I have tried with every nighlies and Open Gapps and Delta Gapps and have faced the same problems. Now I shall try with difference SDcard with different format. Thanks for your kind contribution.
I don t have a saga xD
Cannot test.
You should be able to take a log with android monitor and a boot.img with secure=0
kylon said:
I don t have a saga xD
Cannot test.
You should be able to take a log with android monitor and a boot.img with secure=0
Click to expand...
Click to collapse
Thanks for your prompt reply. We will see how the problem could be solved. Now I reformatted the Data partition to EXT4 and all the stuff was gone. I have to copy all necessary files to the SDcard again and will try your kernel. By the way replaceing AnySolfKeyboard by F-Droid eliminated FC on keyboard issue and making Google Account setup possible. Thanks.
Amazingly mature
I'm running 2015-12-06 since yesterday evening, and I'm amazed how mature it already is. It seems quick stable and "slick."
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
As hinted by @kchaisu (thanks!) I've installed an alternative keyboard app (Google's kbd), and now it's running really well.
The old Facebook problem (that often the device reboots when installing the app) can still be observed, but maybe it's just that our Saga has too little RAM.
Thanks, @kylon and @Mustaavalkosta, and all others who contribute to this, for breathing new life into our little Sagas...
ralfbergs said:
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
Click to expand...
Click to collapse
Well, nothing is removed per se but system hides the camera icon etc. if it can't find appropriate camera hardware which it currently can't find because camera libs won't load due to missing symbols.
ralfbergs said:
I'm running 2015-12-06 since yesterday evening, and I'm amazed how mature it already is. It seems quick stable and "slick."
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
As hinted by @kchaisu (thanks!) I've installed an alternative keyboard app (Google's kbd), and now it's running really well.
The old Facebook problem (that often the device reboots when installing the app) can still be observed, but maybe it's just that our Saga has too little RAM.
Thanks, @kylon and @Mustaavalkosta, and all others who contribute to this, for breathing new life into our little Sagas...
Click to expand...
Click to collapse
Actually, I got the idea from HD CM-13 forum which was post by @marek287. Thanks to him.
Thanks to Mustaavalkosta and Kylon for the CM-13-20151211-sagaopt nightly. This bulid is fast booting up for GApps. However, SetupWizard and AOSP Keyboard still remains FC. Thank you very much.
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
[SIZE="2"]* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
[/SIZE]
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working:
Boots
RIL (Calls, SMS, Data, 2G/3G Switch)
MSIM
Wi-Fi
Bluetooth
GPS
Camera ( Videos And Photos )
Video Playback
Enforcing SELinux
Not Working:
You say!
Read post 2 before reporting bugs.
Install instructions:
Reboot into recovery (TWRP recommended).
Wipe Data, System and Cache if it's a fresh install.
No wipes required if you're updating from a previous version of CM 13.0 (Wipe Cache and Dalvik Cache recommended).
Flash ROM + Gapps.
Reboot.
Download links:
ROM: https://goo.gl/3XdMnF (IMPORTANT: READ THIS)
Gapps: http://opengapps.org
Kernel source: https://github.com/TheStrix/android_kernel_cyanogen_msm8916
Device Tree:
msm8916-common: https://github.com/TheStrix/android_device_cyanogen_msm8916-common/tree/cm-13.0
lettuce: https://github.com/TheStrix/android_device_yu_lettuce/tree/cm-13.0
XDA:DevDB Information
CyanogenMod 13 for YU Yuphoria, ROM for the YU Yuphoria
Contributors
TheStrix
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 13.0
Created 2015-12-18
Last Updated 2016-01-23
Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.
Reserved
Finally!! Great work
Solved : Gapps not able to flash
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work
Great Work!
Uc browser not working......
jayent said:
Uc browser not working......
Click to expand...
Click to collapse
Download UC Browser from here
please help
Hey I am facing problem while flashing thus ROM. Please help please
sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe/factory reset
Yash98 said:
wipe/factory reset
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted
---------- Post added at 04:59 AM ---------- Previous post was at 04:58 AM ----------
TheStrix said:
Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted
Update!
CyanogenMod 13.0 R2 Update:
Download: http://goo.gl/h7CkVJ
Changelog:
AOSP 6.0.1_r10 tag.
January 2016 security patches.
Fix offline charging issue (Screen didn't go completely off while offline charging earlier).
Fix Google+ app installation bug present in previous build.
Increased in-call volume speaker gain (reported by some users).
Updated build fingerprint from YU's latest COS release.
Some Wi-Fi updates.
Fix for external SD Card in CM file manager.
Replaced Toybox with Busybox (This may cause some root apps to crash, but CM now uses Toybox!).
Latest CyanogenMod sources with much new patches..
CyanogenMod 13.0 Jan 23rd update:
Download: https://www.androidfilehost.com/?fid=24385658843824514
Just don't hurry up. Read the whole post for once!
Changelog:
Support for F2FS for /data and /cache
Update audio configs to cope up with CyanogenMod's latest changes in audio HAL.
Switch to qcom libhealthd.msm standard library for offline charging (Also it shows battery % now while offline charge)
Switch to Snap camera
Enable USB MIDI support
RIL and connectivity updates
Update new regenerated blobs from crackling
CyanogenMod updates. (CM API v5, new wallpaper, etc. find out own ) [Many changes are made in CyanogenMod repo everyday, so of course can't list all]
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Damn, that was just copy paste from wikipedia and I just didn't get it! So what is F2FS in our language?
It a better file system than ext4 in terms of performance.
Useful Link: http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
To get a better idea, XDA forum have a dedicated thread highlighting F2FS features and a very detailed comparison between EXT4 (file system we use by default) and F2FS!
Have a look here: http://forum.xda-developers.com/showthread.php?t=2697069
So, I liked F2FS and wanna try it! But, how do I?
First of all, backup your internal SD Card as it will be wiped if you are switching to F2FS.
So, to start with, first you'll need a new recovery. I compiled modified TWRP recovery with F2FS support and some other cool features like pressing power button will now switch device display off, also wiping the partitions should not take much time now as it did earlier! (EXT4 users can use the same recovery. I just made it for my convenience)
1. Download TWRP: https://www.androidfilehost.com/?fid=24385658843824749
2. In recovery, go to 'wipe' -> 'Advanced Wipe'
3. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
4. Here select 'F2FS' and Swipe to Change
5. Repeat step 3 and 4 for 'Cache' by checking only 'Cache' in Wipe menu.
6. Reboot! Enjoy!
I want to get back to EXT4 again from F2FS, how should I?
Again, while you are changing your file system, the partition gets wiped. So do backup your data of Internal SD Card and proceed!
1. In recovery, go to 'wipe' -> 'Advanced Wipe'
2. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
3. Here select 'EXT4' and Swipe to Change
4. Repeat step 2 and 3 for 'Cache' by checking only 'Cache' in Wipe menu.
5. Reboot
PS: Only support for F2FS is added on /data and /cache. It still uses EXT4 by default and is just same as it was in previous builds!
first of all
its an amazing rom
but would absolutely love it if i know how to activate power save mode
and a small request " can you add the theme engine from cyanogen os??????"
i really hate the cm theme engine
hello, why cm13 isn't official because there aren't no bugs?
aminvishwas said:
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work
Click to expand...
Click to collapse
Can't we use the gap 6.0 Full
problm in 5.0.2 ?
there is problm of wake up while charging that it may not happen while m charging phone sir can u pls tell me to fix this problm it will be appreciated could you help me pls....??
sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
bro before flashing the zip file.
do following in TWRP
wipe davlik
wipe data
wipe cache
wipe system
and install the zip file the above error will not appear
reserved
sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe data and system and install and that will fix the error and one more thing can you make a system backup with twrp and give me i need this rom but my devices is irulu v3 and i try cm12 but its old now.
Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"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"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.
ext4 decrypted fine on OnePlus 3 OOS 4.0.2.
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.
Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T
Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.
Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?
chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.