[ROM][6.0.1] CM-13.0 Official Nightlies for Find7A/S - Oppo Find 7 and 7a

Hi everyone,
It's time to taste Marshmallow on find7, CyanogenMod 13 nightlies have been now enabled.
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Installation
If you are on stock ColorOS, you need a custom recovery first. You can get CM recovery in the download links below.
If you are coming from stock or other ROMs, you need to make a factory reset.
If you are coming from previous CM versions, you don't need to wipe your data and can simply upgrade. However, if any issues arise, a factory reset is recommended to rule out upgrade issues.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
https://wiki.cyanogenmod.org/w/Install_CM_for_find7
https://wiki.cyanogenmod.org/w/Install_CM_for_find7s
Download links:
Find7a: http://download.cyanogenmod.org/?device=find7
Find7s: http://download.cyanogenmod.org/?device=find7s
Recommended Google Apps: http://opengapps.org/ (choose the variant you want)
XDA:DevDB Information
CyanogenMod for Find7A/S, ROM for the Oppo Find 7a
Contributors
mikeioannina
Source Code: http://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any version of ColorOS. Unified storage not supported.
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-12-04
Last Updated 2016-02-29

Reserved
Known issues:
Find7s:
* SOD (screen of death) issues: Screen randomly doesn't turn on after some time and device needs a forced reboot for the display to work again.
* New R63419 panel is not supported yet.

CM & unified partiotn(chinesse layout)
Here is instruction how to make unified partitions and install CM 13(CM 12.1).
The main tool is a binary image downloader for chinese version. You can get in here:
for FInd 7a
for Find 7
mirror
There are 3 exe and 2 pdf files.
1. Install(if you don't have them) the QcomMtk_Driver_Setup.exe, reboot.
1-1. (not nessesary) If you want check md5 of ROM, start md5...v2.0.exe, choose X9007_Android5.0_16G_20150520.exe(or X9077_Android5.0_32G_20150520.exe) with upper button. It will generate md5 of ROM and compare it with one in file md5.txt.
3. Check drivers installation. Put away battery, hold vol+ and connect to PC. In device manager it shoud be like in screenshot.
{
"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"
}
4. Disconnect from PC.
5. Then start X9007_Android5.0_16G_20150520.exe(or X9077_Android5.0_32G_20150520.exe) as Administrator.
6. Agree with license.
7. Press left top button to start "waiting for device" mode.
8. Take battery of, hold Vol+ and connect device to pc again. Downloading should start automaticaly.
9. Wait about 5 minutes, while the bottom line will become green and stops growing.
10. Press left bottom button and disconnect phone from USB.
Now we have ColorOS 2.1 beta(lolipop) with only chinese and english languages and unified parttions(NOT LVM!).
Start the device and let it load.
Install TWRP modifeied by Wuxianlin, for this partion layot.(Fastboot flash recovery).
TWRP Unified(Wuxianlin)
Install CyanogenMod:
Find7a
Find7s
Install GAPPS
GAPPS
!important
This and every time after installing or updating ROM you should install path, made by Wuxianlin.
CM13.0 Unified parttion Patch
CM12.1 Unified parttion Patch
mirror
For not get bricked I recomend flash Chinese ColorOS firmware after each update of CM.
ColorOS 5.0 firmware
Finish.

Tried installing it on find7s, and it didn't recognize my internal storage, while refusing to format it (due to an error).
How should I proceed?
EDIT: Haven't unified my storage, ever...

Why unified while LVM is the road that also Oppo follows and is less dangerouys!
Sent from my SM-T520 using Tapatalk

munky-head said:
Tried installing it on find7s, and it didn't recognize my internal storage, while refusing to format it (due to an error).
How should I proceed?
EDIT: Haven't unified my storage, ever...
Click to expand...
Click to collapse
Have you made a clean install or upgrade from cm-12.1?

munky-head said:
Tried installing it on find7s, and it didn't recognize my internal storage, while refusing to format it (due to an error).
How should I proceed?
EDIT: Haven't unified my storage, ever...
Click to expand...
Click to collapse
Format it to fat in twrp
Отправлено с моего Find7 через Tapatalk

mikeioannina said:
Have you made a clean install or upgrade from cm-12.1?
Click to expand...
Click to collapse
I did a upgrade from CM12.1 with new 6.0 gapps but couldnt access the internal storage in CM13.

fremar said:
I did a upgrade from CM12.1 with new 6.0 gapps but couldnt access the internal storage in CM13.
Click to expand...
Click to collapse
Format it to FAT in TWRP recovery
Отправлено с моего Find7 через Tapatalk

tashimotor said:
Format it to FAT in TWRP recovery
Отправлено с моего Find7 через Tapatalk
Click to expand...
Click to collapse
I am pretty sure this will break things... Do not do this. I will try to reproduce the issue tomorrow and might temporarily disable nightlies until I find out what's going on

mikeioannina said:
I am pretty sure this will break things... Do not do this. I will try to reproduce the issue tomorrow and might temporarily disable nightlies until I find out what's going on
Click to expand...
Click to collapse
I've tried it myself, it's ok. You can always format it back to EXT4.
Отправлено с моего Find7 через Tapatalk

only 3 gb internal storage accessible after installing the latest version.

tashimotor said:
Here is instruction how to make unified partitions and install CM 13(CM 12.1).
Install TWRP 2.8.7.0 modifeied by Wuxianlin, only chinse language for this partion layot.(Fastboot flash recovery).
TWRP 2.8.7.0 Unified(Wuxianlin)
View attachment 3565131
Click to expand...
Click to collapse
After this unification process can you swith back to usual TWRP Version? Or is it just this chinese modified TWRP that can be used?!

Nu_Pogodi said:
After this unification process can you swith back to usual TWRP Version? Or is it just this chinese modified TWRP that can be used?!
Click to expand...
Click to collapse
Unfortunly, only chenese, but positiona of buttona are the same, so all operations are available. I'm on it sinse august and have no problems.
Отправлено с моего Find7 через Tapatalk

tashimotor said:
Unfortunly, only chenese, but positiona of buttona are the same, so all operations are available. I'm on it sinse august and have no problems.
Отправлено с моего Find7 через Tapatalk
Click to expand...
Click to collapse
Hi All
I have a big big problem after updating from CM 12.1 to CM13 with clear flash. I can't open camera and other apps because the internal portable storage sd0 appears corrupted!!
If I downgrade to CM 12.1, no problem with it!
What I can do? ANyone found the same issue?

kirkal01 said:
Hi All
I have a big big problem after updating from CM 12.1 to CM13 with clear flash. I can't open camera and other apps because the internal portable storage sd0 appears corrupted!!
If I downgrade to CM 12.1, no problem with it!
What I can do? ANyone found the same issue?
Click to expand...
Click to collapse
Format it to FAT in TWRP
Отправлено с моего Find7 через Tapatalk

tashimotor said:
Format it to FAT in TWRP
Отправлено с моего Find7 через Tapatalk
Click to expand...
Click to collapse
Can you explain me how to do?
Thanks

I've found the issue, the internal storage can't be mounted because of SELinux denials. Working on a fix...
The storage is not actually corrupted, so you can either go back to cm-12.1 or wait until the fix is out. No need to format your internal storage.

mikeioannina said:
I've found the issue, the internal storage can't be mounted because of SELinux denials. Working on a fix...
The storage is not actually corrupted, so you can either go back to cm-12.1 or wait until the fix is out. No need to format your internal storage.
Click to expand...
Click to collapse
Good news.
Отправлено с моего Find7 через Tapatalk

Fix submitted: http://review.cyanogenmod.org/123045
Just waiting for code review and merge now

Related

[MOD] [Experimental] MultiROM v33 for LG G4

{
"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"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for LG G4. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still very experimental!
I've only tested this with stock M as the primary ROM and AICP M as the secondary ROM
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
The MultiROM Manager app does not currently support the LG G4
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (recovery_yourvarient.img) - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
MultiROM (multirom-YYYYMMDD-vXX-yourvarient.zip) - download the ZIP file from second post and flash it in recovery.
Your current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive
Untested on clark
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/Hashbang173/multirom/tree/master
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project
kexec-hardboot patch - https://github.com/genesixx/android_kernel_lge_msm8992-mr
Device tree: https://github.com/genesixx/g4-common-mrom​
Thanks
This port is based on the hard work of Tassadar, Geoff Levand, webgeek1234, Mike Kasick, 500 Internal Server Error, and many others. Thank you.
Thanks to @HashBang173 for all the help
Issues
* Does not yet support encrypted devices
* Please report
XDA:DevDB Information
MultiROM v33 for LG G4, Tool/Utility for the LG G4
Contributors
genesixxbf3
Version Information
Status: Beta
Created 2016-07-08
Last Updated 2016-07-14
Reserved
Download link : https://www.androidfilehost.com/?w=files&flid=51689
compatible only with LlamaSweet kernel R6 (alpha3) as first kernel available here http://forum.xda-developers.com/g4/development/kernel-llama-sweet-kernel-t3286514
Reserved
known problem:
green screen when booting secondary rom
I'm a noob with MultiROM, but there is no option in recovery for multiROM ?
azZA_09 said:
I'm a noob with MultiROM, but there is no option in recovery for multiROM ?
Click to expand...
Click to collapse
Have you flashed the recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
genesixxbf3 said:
Have you flashed the recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
Click to expand...
Click to collapse
Yep
azZA_09 said:
Yep
Click to expand...
Click to collapse
Have you rebooted to the new recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
genesixxbf3 said:
Have you rebooted to the new recovery ?
Envoyé de mon Nexus 6 en utilisant Tapatalk
Click to expand...
Click to collapse
Yea,ofc. Do you have Skype or something else? It's simple to tell you there what's wrong or not
azZA_09 said:
Yea,ofc. Do you have Skype or something else? It's simple to tell you there what's wrong or not
Click to expand...
Click to collapse
I use hangout
Envoyé de mon Nexus 6 en utilisant Tapatalk
Which kernel are you using for the stock Rom?
nicholasknicks said:
Which kernel are you using for the stock Rom?
Click to expand...
Click to collapse
atm kernel patch aren't working
Closing the thread until I get progress
Envoyé de mon Nexus 6 en utilisant Tapatalk
I'm getting closer ! now it just security ****

[ROM] ► [8.0.0] ► [UNOFFICIAL] ► Nitrogen OS ► [cheeseburger]

{
"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"
}
Android OS version: 8.0.0_r17
For devices: cheeseburger
Source code: https://github.com/nitrogen-project | https://github.com/nitrogen-os-devices
Developers: xyyx, poad42
Thanks: ezio84, mydongistiny, Mazda--, beanstown106 and etc.
Google Apps: http://opengapps.org
Recovery: TWRP
The rich functionality is based on AOSP, development was begun in November, 2015.
xyyx (Max) - main developer
Copy the ROM and Gapps in SD card.
- Make a full backup including all data in your internal storage
- Flash in fastboot this TWRP
- Flash latest full firmware Zip
- In recovery format data (this will wipe your internal storage MAKE A BACKUP)
- Reboot into recovery
- Wipe System, Data, Cache and Dalvik cache
- Flash latest ROM
- Flash Gapps
- Flash the no_verity_op5.zip from here
- Flash Magisk or SuperSU (optional)
- Reboot and profit!
Enjoy
https://sourceforge.net/projects/poad42/files/cheeseburger
Translated to EN, RU
Nitrogen Project | Nitrogen Devices
Known Bugs:
Alert slider
Portrait mode
Off screen gestures
XDA:DevDB Information
Nitrogen OS, ROM for the OnePlus 5
Contributors
poad42
Source Code: https://github.com/LineageOS/android_kernel_oneplus_msm8998
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2017-10-07
Last Updated 2017-10-07
This ROM is encrypted by default. However it can be disabled by flashing this zip https://drive.google.com/file/d/0B86MMdsJ-sNgenZuaHViX1pkSzQ/view?usp=sharing
Its recommended that you use this twrp : https://androidfilehost.com/?fid=817550096634801490 as the official twrp in my experience has /data mounting issues.
For root use magisk: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Credits
-GZOSP(Base ROM)
-amartinz
-xyyx
-darkobas
Screenshots.
Very nice rom
Is everything working on this rom?
prajnay said:
Is everything working on this rom?
Click to expand...
Click to collapse
yup everything works. Just use the correct twrp and you should be fine.
poad42 said:
yup everything works. Just use the correct twrp and you should be fine.
Click to expand...
Click to collapse
Will try later today and report.
Looking forward testing this tomorrow! Looks like you might have the first stable Oreo build flashable in twrp!-:highfive:
poad42 said:
yup everything works. Just use the correct twrp and you should be fine.
Click to expand...
Click to collapse
What is the correct twrp? Can I use no verity zip for oneplus 5 to boot this rom on a decrypted device? How is everything working but the op says there are many bugs?
se7ensde said:
What is the correct twrp? Can I use no verity zip for oneplus 5 to boot this rom on a decrypted device? How is everything working but the op says there are many bugs?
Click to expand...
Click to collapse
The twrp linked in the second post.
Omg!! I can't believe that famous and best rom of Rn3 is available for my op5 too.. ???
Del. (the post was removed right before my eyes lol)
Unfortunately camera continue to close! What a pity!
Macchinista said:
Unfortunately camera continue to close! What a pity!
Click to expand...
Click to collapse
Did u try patched google camera?
What gapps do yall recommend?
buski said:
Did u try patched google camera?
What gapps do yall recommend?
Click to expand...
Click to collapse
Open GApps has released official 8.0 GApps
Macchinista said:
Unfortunately camera continue to close! What a pity!
Click to expand...
Click to collapse
Works fine here...
https://imgur.com/a/v8kgF
Issue seems to be with one plus camera, will fix it in next build.
buski said:
Did u try patched google camera?
What gapps do yall recommend?
Click to expand...
Click to collapse
No, i can't try because in recovery linked in OP it didn't appear pin input so the directories are encrypted and i can't install nothing!
After coming back to twrp "classic" i have the message "could not mount /data and unable to find crypt footing"
Macchinista said:
No, i can't try because in recovery linked in OP it didn't appear pin input so the directories are encrypted and i can't install nothing!
After coming back to twrp "classic" i have the message "could not mount /data and unable to find crypt footing"
Click to expand...
Click to collapse
Don't need to flash anything for that, it's an apk install lel.
Is volte working. I can receive calls but cannot make
poad42 said:
Don't need to flash anything for that, it's an apk install lel.
Click to expand...
Click to collapse
I'll try it! But can i ask if i have to install something with twrp multirom linked by you if there is a way to have access to sd cards contents? I try to re-add and remove pin in settings>security but, opposite of "classic" twrp it didn't appear the pin digit message necessary to read phone contents

[ROM][9.0] LineageOS 16.0

Unofficial LineageOS 16 for Lenovo Vibe Z2 Pro
(kingdom_row/kingdomt)
Lin·e·age /ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
What does work?
Sound, FM Radio
RIL (msim)
Wifi, Bluetooth, NFC, GPS, Sensors
Camera, Flashlight
4K Video recording / HFR 720p 120fps, 1080p 60fps
Faceunlock (use gApps from 1/1/2020)
K920 variant detection, USB
Can shoot 10bit RAW / DNG with FreeDCam
OTA Update from settings
Known issues
SELinux is permissive
Zip signature verification needs to be disabled in TWRP
Echo on some devices
Individual SIM cannot be disabled from settings
NotesRequires wiping /data & /cache.
Format /cache with F2FS
Don't install TWRP app it may cause boot problems
General Installation Instructions
Sources: https://github.com/K920 | https://github.com/janforman
Branch: lineage-16​
Downloads
lineage-16.0-20201118-UNOFFICIAL-kingdom.zip
TWRP 3.2.3 - required
​
Archived 14.1 official
lineage-14.1-20190202-nightly-kingdom-signed.zip​
XDA:DevDB Information
LineageOS 16.0, ROM for the Lenovo Vibe Z2 Pro
Contributors
frantisheq, janforman, electry
Source Code: https://github.com/K920
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
ROM Firmware Required: S288 firmware, latest TWRP 3.2.3
Based On: LineageOS
Version Information
Status: Stable
Created 2019-01-10
Last Updated 2020-11-18
Let me be the first one to congratulate. [emoji122]
Soon one of my k920 will be eating pie.
testing start n_n
thank you again frantisheq...
sorry, download again. this time it will boot
No boot in rom
Raskardpoupout said:
No boot in rom
Click to expand...
Click to collapse
download again, there was a bug in previous build
1. Backed up everything with TitaniumBackup
2. Fastboot new TWRP,
3. Formated and for a good measure wiped everything ('cuz OCD that's why)
4. Sideloaded LineageOS 16.0
5. Sideloaded Magisk 18.0
6. Sideloaded Gapps
7. Restored user apps with TitaniumBackup
No major bugs as of yet. Pixel launcher works for me. If I find something will post here.
Sent from my K920 (ROW) using Tapatalk
And this is my battery usage (no FB tho). Keep in mind this battery was never switched.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my K920 (ROW) using Tapatalk
frantisheq, first of all, congratulations for this great work.
Secondly, thanks for the work done and the time allocated for this project.
I have only one question ... how can I move from Lineage 14.1 to 16.0, given that I tried to switch to 15.1 and did not succeed due to cache formatting (f2fs vs ext4) ? What procedure should I follow ?
Thanks in advance !
chili71 said:
I have only one question ... how can I move from Lineage 14.1 to 16.0, given that I tried to switch to 15.1 and did not succeed due to cache formatting (f2fs vs ext4) ? What procedure should I follow ?
Thanks in advance !
Click to expand...
Click to collapse
Two posts above I explained the procedure. Step by step.
EDIT: I'm using ext4 (it seemed more stable to me).
Sent from my K920 (ROW) using Tapatalk
Works perfectly you are the best Electry and Frantisheq
su (arm) for 16.0
thanks for this ROM you are the best!??
what about lag? is it worse than on 15.1?
GPS working for everyone?
underr.t said:
Two posts above I explained the procedure. Step by step.
EDIT: I'm using ext4 (it seemed more stable to me).
Sent from my K920 (ROW) using Tapatalk
Click to expand...
Click to collapse
For me, it does not matter how the cache is ... f2fs or ext4 ...
Lineage 14.1 on my phone has the f2fs cache and I did not manage to format to ext4, in order to install 15.1 and I go back to 14.1.
Is the same problem for 16.0 or this new TWRP knows how to format the cache in ext4 ?
I want to know clearly before I start this upgrade, because this phone is the daily phone and I don't want to go back to 14.1 every time and set it up for a whole day ... that's my concern...
Thank you !
frantisheq said:
what about lag? is it worse than on 15.1?
GPS working for everyone?
Click to expand...
Click to collapse
I'm not noticing much of a lag (I've set animations at .5 as I always do). GPS working.
Sent from my K920 (ROW) using Tapatalk
chili71 said:
For me, it does not matter how the cache is ... f2fs or ext4 ...
Lineage 14.1 on my phone has the f2fs cache and I did not manage to format to ext4, in order to install 15.1 and I go back to 14.1.
Is the same problem for 16.0 or this new TWRP knows how to format the cache in ext4 ?
I want to know clearly before I start this upgrade, because this phone is the daily phone and I don't want to go back to 14.1 every time and set it up for a whole day ... that's my concern...
Thank you !
Click to expand...
Click to collapse
This is mine, but to be honest I can't remember the last time I switched it (was probably at the time of 14.1).
Sent from my K920 (ROW) using Tapatalk
благодарю за ваши совместные труды ребята!
но для меня в прошивках самое главное это камера на телефоне.
к сожалению видео съемка не работает, сканер штрих кодов тоже, а также качество фото на среднем уровне по сравнению со стоком.
возможно ли исправить данный недочёт в основной камере? спасибо.
Hi Guys, error 7 during instalation probably because of diffrent firmware than s288 but i'm searching and searching... And cant find :/ could someone link it?
I'm trying to (from LOS 14.1) wipe data, chatch, dalvik and system, then just install LOS 16 + OpenGapps micro x64
Lag and lag! please update soon this version

(NX563J) Android 9 pie vendor.img boot.img and radio 615

I close this thread cause of can't support it anymore by hardware lost sry....
aljoscha81 said:
Here a fully patched vendor.img with patched nfc for more compability with more devices (body sensors etc.) And patched overlay folder for automatic brightness also patched for 22,6mp camera usage
The boot.img is build with eas kernel for ultimate fast charge and is on latest update so far
You need mokee twrp so your device no longer uses the ext4 file system but f2fs what gives your device a massive speed improofment as far as i can say at last candy on top the android 9 pie radio 610
Installation is simple put the folder you downloaded (you have to unzip first) in your twrp backup folder and restore but first you have to wipe every partition formate data and do factory reset otherwise your device will not use f2fs file system the twrp and radio you can flash the zip. as known in twrp
Ps the radio is only test on pie so far!
This configuration is the maximum we can get out of our device at the moment and runs absulute bugfree so far for me and the speed is amazing in my opinion
The configuration is for gsi usage and my tip is to run it with the havoc 2.4 nightly builds
If the configuration will not boot wipe dalic and cache then reboot
At last many thanks to all the devs and users on xda make this possible
Twrp:https://mega.nz/#!zywk1QzA!_P9FMRosTSvWf42bYnG0rc_-4p2Qv2ZevsHp4E3kDLg
Radio:https://mega.nz/#!eu4gSIjK!-OuxzO13DDFY4_oDu1v3XHIwg16uJGJ9BISNMtBzXvw
Vendor and boot:https://mega.nz/#!yioSzCzK!p2gCH_JlV51o0B-CKbJCXgkf_LNQyebmayiWEJcbKZk
If you like my work you can buy me a beer:
Paypal mail adress: [email protected]
Click to expand...
Click to collapse
vendor and boot --> The file you are trying to download is no longer available.
also what is required install order?
MrBlubke said:
vendor and boot --> The file you are trying to download is no longer available.
also what is required install order?
Click to expand...
Click to collapse
Yes i reupload now 15min. and it should available
1 flash twrp then wipe everything
2 flash radio
3 restore the backup
4 flash gsi
5 boot
6 reboot to recovery
7 factory reset
8 install gapps
9 enjoy
This TWRP and radio is only for GSI builds (Android 9) or for rest builds dedicated specially for our device?
Tell me how to make the format of the system f2fs?
Отправлено с моего NX563J через Tapatalk
The twrp is the mokee one i think should work with every rom
The twrp automaticly will format partitions to f2fs when not choose a other filesystem manually
surfer30 said:
This TWRP and radio is only for GSI builds (Android 9) or for rest builds dedicated specially for our device?
Click to expand...
Click to collapse
You can test if radio work with other rom and give a feedback here
The vendor and boot is reuploaded again ..have fun
johnny_king said:
Tell me how to make the format of the system f2fs?
Отправлено с моего NX563J через Tapatalk
Click to expand...
Click to collapse
It will do automatic the vendor and boot file is now online ..happy flashing
MrBlubke said:
vendor and boot --> The file you are trying to download is no longer available.
also what is required install order?
Click to expand...
Click to collapse
Ok file is online back again ..happy flashing
Will I lose my data in the internal memory? after vendor firmware
Отправлено с моего NX563J через Tapatalk
johnny_king said:
Will I lose my data in the internal memory? after vendor firmware
Отправлено с моего NX563J через Tapatalk
Click to expand...
Click to collapse
Better do backup on an external memory like usb stick or so cause you have to wipe the whole phone for f2fs support but can say it will be reward you with massive better performance
Understand thanks, what is your rom now?
Отправлено с моего NX563J через Tapatalk
I dont get it..currently using mk90 latest build..can anyone help me on how to install it for a newbie.
aljoscha81 said:
Better do backup on an external memory like usb stick or so cause you have to wipe the whole phone for f2fs support but can say it will be reward you with massive better performance
Click to expand...
Click to collapse
well... I seem to have a problem with mouting USB storage... so usb OTG doesn't seem to be working... or is there a trick to this, or something I've forgotten (in developer settings maybe?)
Radio work for mokke 04.19
Отправлено с моего NX563J через Tapatalk
MrBlubke said:
well... I seem to have a problem with mouting USB storage... so usb OTG doesn't seem to be working... or is there a trick to this, or something I've forgotten (in developer settings maybe?)
Click to expand...
Click to collapse
Mount otg issue every twrp have so far i can tell you do better mount manally in twrp before use otg
{
"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"
}
johnny_king said:
Radio work for mokke 04.19
Отправлено с моего NX563J через Tapatalk
Click to expand...
Click to collapse
Havoc gsi
Fingerprint and camera 22mp full work?
Отправлено с моего NX563J через Tapatalk
SoKa1993 said:
I dont get it..currently using mk90 latest build..can anyone help me on how to install it for a newbie.
Click to expand...
Click to collapse
So you got the right recovery installed
1 flash the radio zip in twrp
2 look for the twrp folder on your device look in that folder for the backup folder if it not exist backup boot.img first after that it should be there put the folder of vendor and boot you have downloaded in it go to restore in twrp choose the folder you have put in there and check the both files and restore:good:
johnny_king said:
Fingerprint and camera 22mp full work?
Отправлено с моего NX563J через Tapatalk
Click to expand...
Click to collapse
Yes:good:
With havoc it is very nice the dev worked a lot on it to make it perfect working

[Recovery][v3.0.0][Curtana] Unofficial PBRP Recovery

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
This particular build is based on the amazing work done by the PBRP team and Joyeuse devs with some little changes to get it working on Curtana.
This build is really experimental so flash at your own risk.
However, the main use cases are fully covered as the most important functions of the recovery are working correctly.
Working
Data decryption
Flash
Wipe and format data
Backup and restore
Bugs
ADB sideload
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
The recovery always asks for encryption password, even if the device is not encrypted: if your device is not encrypted just press cancel and it will work just fine.
Error 7 when flashing a ROM: check that System, Vendor and Product partitions are not mounted in the Mount section of the recovery before flashing a ROM.
Changelog
20200730
Updated to the new 3.0 UI
Language selection now works properly
Timezone selection now works properly
20200722
Initial Build
Downloads
20200730
20200722
Source Code
android_device_xiaomi_curtana-pbrp
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
kheno said:
Hey,
great work!
thanks!
I saw on github you changed that version from joyeuse to curtana.
Would you be able to compile a joyeuse version too for all the joyeuse owners?
Add it here too and change the title [curtana-joyeuse]?
I've unpacked your version and changed build.prop and repacked.
It's working beautifully on my joyeuse_eea device.
It is the only version that:
- does not lock touch after wake up
- can decrypt
- is not closed source as LR-twrp
- backup works
So great work!
PS: have no clue howto compile myself, otherwise I would have tried that path
Click to expand...
Click to collapse
Hi!
dungphp already did a version of PBRP for joyeuse that you can download here:
https://androidfilehost.com/?fid=8889791610682886707
On the other hand PBRP devs are working on a official device tree for joyeuse, but as far as I know there are still no official builds. You can check their progress here:
https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_joyeuse-pbrp
Hey,
Thanks for the info.
For some reason the version of dungphp did not backup the existing install.
Can't remember the actual error.
Another version was 3.4.0 and did not decrypt.
So i stated looking into altering different curtana versions.
The LR twrp is closed source and locks up touch after waking up from sleep.
This version works flawlessly for me. 
I will track the progress of the official build.
Many thanks!
@end222 after flashing joyeuse version of recovery, recovery booted fine but internal storage folders have random names and no files in them, also backup dont work with error that folders dont exist or something like that, also phone didn't been able to boot system after installing recovery.I needed to reflash stock firmware to fix system.Any ideas?
You shouldn't have installed any recoveries because they are in alpha phase.
You can install some roms by using factory recovery and fastboot.
Thanks for the recovery.
patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
Which boot image should I patch and then flash?
mtolgae said:
Thanks for the recovery.
Which boot image should I patch and then flash?
Click to expand...
Click to collapse
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
end222 said:
You have to patch the image of the ROM you're using. To get it just extract the ROM's zip and you'll see it
Click to expand...
Click to collapse
Thanks
Updated to 20200730:
- New 3.0 UI
- Language selection works well now
- Timezone selection works fine as well
Flashing Magisk results in bootloop: if you want to use Magisk you can patch a "boot.img" file from Magisk Manager and then flash that img to the Boot partition from recovery.
Click to expand...
Click to collapse
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Yoss Roness said:
If I flash the patched boot image, will it be fully rooted or will my device get bricked by file mangers like other's in the forum have mentioned?
Click to expand...
Click to collapse
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
end222 said:
It should work just fine. I've been using the recovery as a daily driver ever since I released the build and I've flashed Magisk using that method several times, all of them successfully.
Click to expand...
Click to collapse
Great, thank you!
Thank you
Sent from my Redmi Note 9 Pro using Tapatalk
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
keiner99 said:
is it safe to install this recovery over lr-twrp? i don't want to reinstall my whole phone btw. thanks for this project!!
Click to expand...
Click to collapse
Yes, at least I did...
Sent from my Redmi Note 9S using Tapatalk
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
trinity_user said:
how you guys install ROMs? i did everything described in Bugs Section... unmount system, vendor, product.
press cancel and ignore encryption password.
then i try to install mi-globe rom and get error 256 because system partition is unmounted
Click to expand...
Click to collapse
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Timmiotool said:
I have the same issue with miglobe Rom it endet up in System unmounted and Read Only... After that only flash the original Rom with MiFlash fixed this.
With the EU ROM everythings OK.
I have the Issue with LRTWRP to.
I think the Script from MIGlobe ROM that run after flash the .zip - doest work with the unoficial TWRP Versions for now...
Click to expand...
Click to collapse
sounds logical to me. hm and its possible to fix this? @end222
Method installation
Thanks for the recovery, in the post initial no have installation explication, is "fastboot flash recovery filename.img" the best method? Or fastbootd? I just unlocked the bootloader. Thanks.

Categories

Resources