[ROM][Official][6.0.1] CyanogenMod 13 Nightlies For International Oppo R5/R5s (R8106) - Oppo R5

{
"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"
}
https://wiki.cyanogenmod.org/w/r5_Info
Official nightlies for International Oppo R5/R5s (R8106) has arrived!
Code:
#include <std_disclaimer.h>
/*
* 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.
*
*/
CyanogenMod 13 is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Important information
This thread is for CyanogenMod 13 builds for International Oppo R5/R5s (R8106). The following will not be supported here:
Custom kernels
Mods
Xposed
Installation
First time flashing CyanogenMod 13 on your device, or coming from another ROM?
1. Flash Project Spectrum as outlined here.
2. Flash unlockable bootloader obtained from here via stock recovery.
3. Unlock bootloader (fastboot oem unlock).
4. Flash compatible custom recovery.
5. Download the nightly/snapshot zip.
6. Perform a backup of your current ROM (optional).
7. Wipe data/factory reset.
8. Flash CyanogenMod.
9. (Optionally) flash Google Apps.
10. Reboot.
CM recovery is recommended. Official TWRP isn't compatible ATM.
Official Builds
http://download.cyanogenmod.org/?device=r5
Latest nightly: https://download.cyanogenmod.org/get/r5-latest.zip
Latest snapshot: https://download.cyanogenmod.org/get/r5-snapshot.zip
Latest CM recovery (nightly): https://download.cyanogenmod.org/get/r5-latest-recovery.img
Latest CM recovery (snapshot): https://download.cyanogenmod.org/get/r5-latest-snapshot.img
Google Apps
http://opengapps.org/
Known Issue/Bugs
Found a bug? Random Reboot etc.
Please post logs.
Changelog
http://www.cmxlog.com/13/r5/
Source
https://github.com/CyanogenMod
Kernel: https://github.com/CyanogenMod/android_kernel_oppo_msm8939
Device: https://github.com/CyanogenMod/android_device_oppo_r5
Credits
CyanogenMod Community. I'm not the maintainer of it.
Official maintainer: @maniac103

Reserved for future.

Official builds are coming soon: http://review.cyanogenmod.org/#/c/146850/

How do you unlock bootloader?
Sent from my F1f using XDA-Developers mobile app

Why don't you simply wait for me to do that post so I can include proper instructions?
Anyway, short instructions are:
- Flash Project Spectrum as outlined in http://community.oppo.com/en/forum.php?mod=viewthread&tid=44621
- Flash unlockable bootloader obtained from https://www.androidfilehost.com/?fid=24566382913912839 via stock recovery
- Unlock bootloader (fastboot oem unlock)
- From there the procedure above applies
TWRP is explicitly NOT (!) recommended as there's no build of it compatible with the 5.1 firmware that Spectrum installs. Please use CM recovery obtained from get.cm until TWRP is updated!
Edit: And before I forget, this is only for R8106 (the international R5/R5s). It might work on R8107 (the Chinese R5/R5s), but I have absolutely no way of testing that one, so I can't support it.
Gesendet von meinem R7plusf mit Tapatalk

@maniac 103. Thanks but the download link for the nighties as well as for cm recovery is dead so I can't test it
Sent from my R8106 using XDA-Developers mobile app

@maniac103
My bad - I'm kinda too much excited after seeing the commit. If it sounds feasible, then I can request any mod to delete the thread & you can create a new one; or I can add the necessary bits in the OP, after getting proper notes from you.
:highfive:

Titokhan said:
My bad - I'm kinda too much excited after seeing the commit. If it sounds feasible, then I can request any mod to delete the thread & you can create a new one; or I can add the necessary bits in the OP, after getting proper notes from you.
Click to expand...
Click to collapse
No worries. Please just include/reflect my notes in reply #5 in the OP.

The download links for nighties and recovery are dead.
Does any body have them?
EDIT: It is OK now
Testing

Unable to unlock bootloader.
OEM unlocking in developer option , after flashing the zip file still returns to off position

Hello, this ROM is also compatible with Oppo R5s?
Thank y!

pickmod said:
Hello, this ROM is also compatible with Oppo R5s?
Thank y!
Click to expand...
Click to collapse
yes

OK latest nightly flashed successfully. Many thanks
Sent from my F1f using XDA-Developers mobile app

Cyanogen Problem
Hello everybody
I followed the discription
1. Flash Project Spectrum as outlined here.
2. Flash unlockable bootloader obtained from here via stock recovery.
3. Unlock bootloader (fastboot oem unlock)
4. Download the nightly/snapshot zip.
5. Perform a backup of your current ROM (optional).
6. Wipe data/factory reset.
7. Flash CyanogenMod.
8. (Optionally) flash Google Apps.
9. Reboot.
i used the spectrum recovery because i not able to download the stock recovery.
but after i finished i am not able to activate the engineering options ( OEM Unlocker/switch turned back off himself immeadiately).
Can somebody help me.

patre1234 said:
Hello everybody
I followed the discription
1. Flash Project Spectrum as outlined here.
2. Flash unlockable bootloader obtained from here via stock recovery.
3. Unlock bootloader (fastboot oem unlock)
4. Download the nightly/snapshot zip.
5. Perform a backup of your current ROM (optional).
6. Wipe data/factory reset.
7. Flash CyanogenMod.
8. (Optionally) flash Google Apps.
9. Reboot.
i used the spectrum recovery because i not able to download the stock recovery.
but after i finished i am not able to activate the engineering options ( OEM Unlocker/switch turned back off himself immeadiately).
Can somebody help me.
Click to expand...
Click to collapse
Cyanogen recovery is a must
Follow this instructions
https://wiki.cyanogenmod.org/w/Install_CM_for_r5

i followed these instructions but i am still not able to akctivate oem unlock (i can see unlock switch but it turns back by himself) .
how can i preceed ?

patre1234 said:
i followed these instructions but i am still not able to akctivate oem unlock (i can see unlock switch but it turns back by himself) .
how can i preceed ?
Click to expand...
Click to collapse
I had the same problem but solved.
Do you have cm recovery?
If yes then enter recovery and enter Factory reset -system reset (keep media) and apply.
Then flash cm and gapps from "Apply update"
It is better to use the side load method. i.e.
1- put cm rom and gapps to your adb folder
2- Open your cmd terminal as administrator and cd\adb
3 - In your phone recovery enter apply from adb
4- type in terminal
adb sideload update.zip - where update it will be cm rom and gapps

It works, thanks a lot.
but i have to try it a few times ( 4 times)

highly appreciated you guys are working on this!
will go for the nightly within the next couple days !

Thanks for this great work. I had some problems with my Linux laptop and OEM Unlock but after some tries it worked...
I couln't side load the ROM and Gapps so i decided to update from the internal memory of the phone.. worked but after the installation Google play services crashed every minute...
After factory reset from CM13 it works like a charm for me

Related

[ROM][Unofficial][20180617]CarbonROM | cr-6.1 [payton]

Credits
Moto X4 is getting some custom rom love, because @erfanoabdi worked in BEAST mode and created the trees for this device, even though he does not own the device.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware zip so both slots have the firmware, when you boot after flashing, you WILL have a bootloop or even a brick.
Warning 4 : This is an Engineering build, which means it's pre rooted and all apps have access to root. Only the SU binary is missing.
Warning 5 : Kernel is permissive.
This is an initial release and it WILL have bugs. If your phone is a daily, and you cannot afford downtime or random reboots then please do not flash.
I am new to this, DO NOT expect fixes on the fly. Post logcats and I will see what I can do.
{
"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:
/*
* 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.
*/
​
About Carbon ROM :
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Not Working :
[*] Engineering Build - you will get a strict mode red-rectangle flash.
no moto onenav gestuers
You tell me
How to Boot into fastboot/bootloader mode
1. Reboot phone, and keep volume down pressed while device is rebooting until you see bootloader mode screen.
2. While phone is off, press volume down and then press power button. Keep holding both until you see bootloader mode screen.
How to Install
Video is for LineageOS, but process is same for Carbon ROM as well.
Video
Moto X4 A/B Slots Explained
Steps
1. Download the ROM, TWRP (zip and Image), Gapps (optional) from Downloads section. Place TWRP image zip in same folder as where you have fastboot.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model). Boot into bootloader mode.
Flash the firmware with the flash_all.bat (Windows) file or the flash_all.sh (Linux & Mac) (See links on Post #2).
Windows
Code:
flash_all.bat
Mac/Linux
Code:
./flash_all.sh
Tested only on XT1900-1 on Android 8.0 model for now. Feel free to try on other models. Check for any errors in the process, DO NOT proceed if you have any errors. Once flashed successfully, reboot into Android to make sure all is well.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
3. Wipe internal data. Reboot back into bootloader mode and run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work). Make sure to remove your external sdcard before doing this. Once done, REBOOT into Android to make sure all is well. Skip all the setups.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
4. Transfer ROM zip and TWRP zip to internal memory of device. Reboot device into bootloader mode.
5. Boot to TWRP using fastboot. Using command prompt/terminal navigate to folder where fastboot is.
Windows
Code:
fastboot boot twrp-3.2.1-1-payton.img
Mac/Linux
Code:
./fastboot boot twrp-3.2.1-1-payton.img
5. Once booted into TWRP, click on Install - and select TWRP zip transferred in Step 1. Once done, Reboot back into system to check all is well.
6. Boot into TWRP again (reboot device, keep volume down pressed while device is rebooting. When you see bootloader mode, let go of volume down. Press volume up until you see recovery mode, press power button to select. Now you will boot into TWRP recovery).
8. Once in TWRP. Go to Wipe and swipe to factory reset. Go back, select Install and select Linage OS Rom zip, also add the TWRP zip file and click on install. Once done, wipe cache/dalvik.
Do note, recovery is built into kernel with our device so flashing any rom or kernel will result in TWRP being overwritten. DO NOT flash Magisk (any root package) or Gapps. Once ROM (and optional TWRP) have flash successfully, go to main menu :-
Now you have two options. If you WANT gapps do step 9. else go to 10. If you install gapps after booting into rom, gapps will crash. So, make your choice now.
9. Go back to TWRP main menu. Click on reboot, note down the slot you are on and select recovery.
You will now boot back into TWRP recovery. Click on reboot, and you should be on the other slot. Go back to main menu, transfer the gapps package to internal memory and install gapps.
10. Go back to TWRP main menu. click on reboot and select bootloader.
11. Once in bootloader mode. issue below command.
Windows
Code:
fastboot -w
Mac/Linux
Code:
./fastboot -w
Once done, reboot.
Windows
Code:
fastboot reboot
Mac/Linux
Code:
./fastboot reboot
11. To ROOT, booting into Android once is necessary whether you want gapps or not. After booting into Android once reboot back into TWRP, and then flash your root package zip, reboot and enjoy.
How to Update
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Coming from Another custom ROM, have already flashed firmware zip
Transfer rom, gapps and twrp zip to internal storage.
Boot to TWRP.
Wipe -> Swipe to factory reset
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
How to go back to stock
Support :
1) Search. Search, search, search. If you make the effort of reading atleast 5 pages back, most if not all your questions will be answered. I personally, will ignore any questions, if I know they have been answered in the last 5 pages. Not being rude, but please read.
2) If you can't find answers in last 5 pages, ask here, be respectful and have a good time.
Downloads :
TWRP (Zip + Image, Download 3.2.1-1): TWRP for Payton
ROM : Unofficial Carbon ROM (payton)
Gapps : OpenGapps
Magisk : Stable Magisk
Notes :
Only Clean Installation Please
Bug Report Without logs means nothing
3rd PARTY ADDONS/MODS :
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
Reporting Bugs :
DO NOT Report bugs if you installed Xposed.
DO NOT Report bugs about Magisk Modules.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format above may be ignored.
Sources :
Carbon ROM
Device tree :
moto-sdm660-common
payton
Kernel :
moto-msm8998
Vendor tree :
moto-sdm660-common
payton
XDA:DevDB Information
Unofficial Carbon ROM cr-6.1 for Payton, ROM for the Moto X4
Contributors
erfanoabdi, mightysween, gee one, Lineage Team, Carbon Team
Donations
Donate to Carbon ROM
Buy me Coffee.
ROM OS Version: 8.1.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: No Requirements
Based On: AOSP
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-17
Firmwares
Firmwares
https://forum.xda-developers.com/showpost.php?p=76775043&postcount=2
mine002
Changelog
17th June 2018
* fixed FM radio
* userdebug build (no more red border) Thanks again @erfanoabdi
Excellent work. What would you say are the main differences between Carbon and Lineage?
sizz-lorr said:
Excellent work. What would you say are the main differences between Carbon and Lineage?
Click to expand...
Click to collapse
Lineage is pure stock android, whereas Carbon offer some customizations! I have not tried the ROM yet, i am on RR right now! But as far as I know, it is going to be stable! :fingers-crossed:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
NetSpeedZ said:
I would like to try this ROM, however, I'm hesitant to due to I have the TWRP v 3.2.1-0 which doesn't make nandroid backups that can be restored.
Does the posted TWRP version (3.2.1-1) make restorable nandroid backups?
------------
Click to expand...
Click to collapse
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Copy that. I don't have lock screen enabled, just the 'screen saver' that shows when phone senses motion nearby and shows the clock, etc.
Appreciate the clarification.
------------
New build is up.
Changelog in post 2.
brandontowey said:
I've restored from a nandroid on the newest twrp and haven't had an issue. Just remove any pin or lockscreen security before buying into twrp or you can't decrypt.
Click to expand...
Click to collapse
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
NetSpeedZ said:
Follow-up question to your reply:
When you made your backup, did you include System Image? If so, when you restored did you enable Boot, Data, System and/or System Image?
------------
Click to expand...
Click to collapse
I did whatever the default in TWRP was, backup and restore. I googled what I should do but there wasn't anything definite. I did get an error 255 from resting the Bluetooth thing so i just omitted it.
I'm on the fence looking at these new custom ROMs available for our X4, so please help me clarify a few points:
1) does Lineage have the option to set navigation bar height? If I'll take the plunge I'm interested in having a navigation bar narrower than Android' standard;
2) is it possible to tweak the kernel with Kernel Adiutor or something similar?
3) is it possible to install and use Moto Display in some way?
Thanks!
P.S. Plese bear with me as I'm asking the same questions all over the three custom ROMs threads.
One button navigation
Is one button navigation still not working on this rom?
superj1018 said:
Is one button navigation still not working on this rom?
Click to expand...
Click to collapse
not yet.

[9.0][EXPERIMENTAL]Resurrection Remix v7.0 [blueline]

Warning: This is an untested unoffical build for the Pixel 3 (blueline), so please take caution in flashing and make a backup.
{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
I am not a developer, I only build this ROM and it reflects the the current status of LineageOS / Resurrection Remix. If there are any device specific things missing or not working. I suggest to contact the LineageOS team, they are the real developers here and deserve all the credits.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process, so make sure you make a backup if needed.
In order to make the right startbase for the ROM you have to install the latest stock Pixel 3 image from Google found here.
Place the ROM and optionally the TWRP zip, a kernel and root on the phone and reboot to recovery by using the command line (fastboot boot twrp.img) or hold the VOL DOWN key while rebooting the phone.
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe or use the slider in TWRP for a factory reset. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip, kernel and root and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM on the phone and reboot or fastboot flash to the TWRP recovery
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when Resurrection Remix has also adapted to the latest monthly sources, you will have to do an extra step:
Download the latest Resurrection Remix ROM and place it on the internal storage
Download the latest image from the Google Factory Images site, extract the bootloader, radio and vendor images and flash them in the bootloader to both slots
From here go to TWRP recovery and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
ROM Download
GApps are already included in the ROM
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
- Active Edge
- Now playing
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.​​
​
turbolukex5 said:
Warning..
Click to expand...
Click to collapse
Is this ROM featuring OpenGapps, like the unofficial LineageOS 16.0 build(s) does?
xFirefly93 said:
Is this ROM featuring OpenGapps, like the unofficial LineageOS 16.0 build(s) does?
Click to expand...
Click to collapse
It features the gapps that come with the Dirty Unicorns ROM.
So excited to finally see RR on my pixel 3. Been a long wait
Thank you ?
Hey, your instructions confused me a little. Do we need to flash our own kernel of choice, or can we stick to the kernel that comes with the ROM?
retr0gr4d3 said:
Hey, your instructions confused me a little. Do we need to flash our own kernel of choice, or can we stick to the kernel that comes with the ROM?
Click to expand...
Click to collapse
You can do both.
I flashed your rom yesterday but got stuck on the bootscreen logo. I let it sit for 15 minutes & nothing.
Spider_Pig27 said:
I flashed your rom yesterday but got stuck on the bootscreen logo. I let it sit for 15 minutes & nothing.
Click to expand...
Click to collapse
This is the exact issue I had, which is why I asked about the kernel situation. It seems like people have had success, however I don't know whether those people flashed this build or not.
The instructions aren't exactly crystal clear.
retr0gr4d3 said:
This is the exact issue I had, which is why I asked about the kernel situation. It seems like people have had success, however I don't know whether those people flashed this build or not.
The instructions aren't exactly crystal clear.
Click to expand...
Click to collapse
I flashed it with a custom kernel & still didn't boot for me. I flashed it like I've been flashing other rooms. Didn't really do anything different or special with this one.
All is running well for most trying it out and that's why it is so quiet ??
Doesn't work, installed latest factory image, installed the ROM, TWRP, and Magisk (no custom kernel). Image fails to boot, stuck at boot image for about 10 minutes and then it kicks me back out to TWRP.
I'm also stuck on the start screen with the loading icon. Just installed RR and TWRP, nothing too special. Everything went perfectly until I attempted to boot. Is there anything I'm missing?
Sad to report same issue here..
To everyone with boot issues: please keep in mind that this is still an experimental built, bugs are to be expected. If you are able to pull some adb logs from the bootloop and post it here, the dev might actually be able to fix those nasty bootloops. This way, you can actually participate in the development process to make this ROM acessible for other members.
Portgas D. Ace said:
To everyone with boot issues: please keep in mind that this is still an experimental built, bugs are to be expected. If you are able to pull some adb logs from the bootloop and post it here, the dev might actually be able to fix those nasty bootloops. This way, you can actually participate in the development process to make this ROM acessible for other members.
Click to expand...
Click to collapse
I haven't tried this one yet but had the same problem in LineageOS. Stuck in the bootscreen. Not sure what it is.
Did the updates and development for blueline just stop with this. I cannot for the life of me find an update version of this.
eezdva said:
I haven't tried this one yet but had the same problem in LineageOS. Stuck in the bootscreen. Not sure what it is.
Click to expand...
Click to collapse
tjcalhoun1221 1 said:
Did the updates and development for blueline just stop with this. I cannot for the life of me find an update version of this.
Click to expand...
Click to collapse
I know the dev, he doesn't know how to fix this.
However, you can flash the RR 7.x.x GSI if you want. I'll leave detailed steps.
Do not I am not some sort of Pixel dev. I did these steps myself with help from a friend in the Proton Kernel team.
1) Boot to your TWRP
2) Flash avbctdisable.zip. It acts like a dm-verity disable afaik, however I can't remember where I found it. I think it's on the internet, I'll edit when I find it, or if I post it myself.
3) Boot to fastboot
4) Flash the stock boot.img from the latest P OTA (fastboot flash boot boot.img)
5) Flash your GSI (fastboot flash system system.img)
6) Flash TWRP temporarily (fastboot boot twrp.img)
7) Wipe your /data (wipe > advanced wipe > data > type "yes") but do NOT reboot yet
8) Flash TWRP installer (blueline/crosshatch respectively, then reboot back to TWRP)
9) Flash your GApps, Magisk and/or kernel
9.1) If this doesn't work (/system isn't big enough) then put "resize2fs /dev/block/by-name/system$(getprop ro.boot.slot_suffix)" into adb shell. It will make /system bigger for GApps.
10) Reboot and you should have RR 7.x.x GSI working.

[RECOVERY][CFW][3.3.1-0][begonia]Unofficial TWRP recovery for begonia(in) [05/06]

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 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.
Code:
#include <std_disclaimer.h>
/*
*
* 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.
*
*/
Features:
- Open Source
- Decryption working
- Padding for notch area
Install Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to bootloader
- Execute:
Code:
fastboot flash recovery twrp-3.3.1-0-begonia_UNOFFICIAL.img
fastboot reboot
- Boot using power and volume up.
Note: MIUI will keep replacing the recovery with it's own recovery. You need to boot to recovery right after flashing it. Booting to MIUI after flashing may cause MIUI to replace TWRP with Redmi-Recovery. So either find and remove the script responsible for this, or just wait for custom roms
Download:
NON-CFW Recovery:
TWRP 3.3.1-0 Unofficial by Agent_fabulous | md5sum
CFW Recovery:
TWRP for CFW 3.3.1-0 Unofficial by Sahil_Sonar
Source code:
Recovery Source
Device tree
Kernel
XDA:DevDB Information
TWRP for Redmi Note 8 Pro, Tool/Utility for the Redmi Note 8 Pro
Contributors
Agent_fabulous, Sahil_Sonar
Source Code: https://github.com/AgentFabulous/twrp_redmi_begonia
Version Information
Status: Alpha
Created 2019-11-12
Last Updated 2020-06-05
Reserved
Changelog
> 12/11
- Initial build
- Decryption working
> 18/11
- Fix compatibility.zip error when flashing ROMs
- Remove flash, backup and reboot to recovery options from TWRP
> 29/12
- Disable compatibility check entirely
- Fix boot-up on newer MIUI builds
- Fix decryption on newer MIUI builds
> 30/12
- Fix backlight for some users.
Archive
everything working?
thanks
good job mate
Thank you very much for your work man ?
Thank you buddy for your efforts ?
Awesome and just in time. My timer is up tomorrow for bootloader unlock.
I followed your instructions and still miui replaces twrp. Is there a fix for that?
finally developers are here. :victory:
Recovery Updated
> 18/11
- Fix compatibility.zip error when flashing ROMs
- Remove flash, backup and reboot to recovery options from TWRP
Note: For some reason, writing to recovery from within TWRP and rebooting back to recovery bricks the device (in my experience).
Thus, the options have been removed for now.
Download
Can I install this on Indonesian rom with miui 11?
Agent_fabulous said:
Recovery Updated
> 18/11
- Fix compatibility.zip error when flashing ROMs
- Remove flash, backup and reboot to recovery options from TWRP
Note: For some reason, writing to recovery from within TWRP and rebooting back to recovery bricks the device (in my experience).
Thus, the options have been removed for now.
Download
Click to expand...
Click to collapse
You should have left both options available. The original twrp worked perfectly on my global phone. Is the twrp updated to support miui 11?
I am so excited to try this out. I'm just about to unlock the bootloader and it might take years lol... Thank you devs for supporting such device!
Edit: Does it support MIUI 11?
uglypish06 said:
I am so excited to try this out. I'm just about to unlock the bootloader and it might take years lol... Thank you devs for supporting such device!
Edit: Does it support MIUI 11?
Click to expand...
Click to collapse
It does and I am using it right now. Just becareful and make sure you follow instructions to a tee. If not the phone will over write the recovery or you will loose your boot.img file. I lost mine and had to open the battery, disconnect, wait 30 seconds, boot into fastboot, and reinstall 10.4.1 to try again.
Are the steps all right?
1. Unlock the bootloader first
2.turn on USB debug
3.reboot to fastboot mode
4.starting flash twrp
5.boot into recovery mode
6.starting flash xiaomi.eu miui 11 stable rom from twrp
7.waiting it reboot
Are the steps all right? I don't have chance to disconnect the battery from cellphone so I have to do this at all RIGHT steps.
mcarden2006 said:
It does and I am using it right now. Just becareful and make sure you follow instructions to a tee. If not the phone will over write the recovery or you will loose your boot.img file. I lost mine and had to open the battery, disconnect, wait 30 seconds, boot into fastboot, and reinstall 10.4.1 to try again.
Click to expand...
Click to collapse
Sorry I am not understanding, did you flash it on miui 11? Everything is working fine? I'm on miui 11.0.1 Global.
And to reboot into twrp after flash it, will the command 'fastboot boot TWRP.img' work or I have to use physical button?
Thanks!
jim.Duke said:
Sorry I am not understanding, did you flash it on miui 11? Everything is working fine? I'm on miui 11.0.1 Global.
And to reboot into twrp after flash it, will the command 'fastboot boot TWRP.img' work or I have to use physical button?
Thanks!
Click to expand...
Click to collapse
I'd prob wait till this gets sorted out there's a few different posts on this and there all different but all seem to be facing bootloop issues. I'm not sure if it's safe to go back to miui 10 or not without bricking it.
fastjohnson said:
I'd prob wait till this gets sorted out there's a few different posts on this and there all different but all seem to be facing bootloop issues. I'm not sure if it's safe to go back to miui 10 or not without bricking it.
Click to expand...
Click to collapse
I am new to Xiaomi and miui, for what I know it is not safe you will brick the device, but maybe I am wrong... anyway I don't want to downgrade, just to root this damn miui 11 until a good rom is out.
Maybe the dev can clear our mind about! : )
jim.Duke said:
I am new to Xiaomi and miui, for what I know it is not safe you will brick the device, but maybe I am wrong... anyway I don't want to downgrade, just to root this damn miui 11 until a good rom is out.
Maybe the dev can clear our mind about! : )
Click to expand...
Click to collapse
Oh it will there developing mods as we speak. I'm sure this root method works. I'm on miui 11 myself and actually liking it so I'm not into setting up my device time n time again cause I looped it.
fastjohnson said:
Oh it will there developing mods as we speak. I'm sure this root method works. I'm on miui 11 myself and actually liking it so I'm not into setting up my device time n time again cause I looped it.
Click to expand...
Click to collapse
I hope so!
Which root method you mean?
Ok , so did you already flash this recovery on miui 11 global and is working fine?

[UNOFFICIAL][TWRP] OrangeFox Recovery Project [T595][PIE]

OrangeFox Recovery Project
{
"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:
/*
* 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 recovery
* 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.
* bruh moment
*/
OrangeFox is FREE SOFTWARE (cool)​
Downloads:
TWRP TAR archive(For DL Mode): https://drive.google.com/file/d/1XzbUxpkUwL-eyl-rgDZqsuzfiA8PgeOt/view?usp=sharing
Flashable Zip (For TWRP/Old Ver): https://drive.google.com/open?id=1AyK46TWsaLHcOztJP9fSrwdi7wf7FcKV
dm-verity and force encrypt disable: https://zackptg5.com/android.php#disverfe
Rootfix(PIE): https://drive.google.com/file/d/1bgQcaiI-npszWBMruuXT0Hh3i_kzezZx
Rootfix(Q): https://drive.google.com/file/d/1zX2P6ChkjQbdWzyZUvomvp9wt2tkwzq0/view?usp=sharing
Documentation and Frequently Asked Questions: https://wiki.orangefox.tech/en/guides
Installation:
For users on stock:
NOTE: YOU WILL LOOSE ALL YOUR DATA!!!!!!
0. Unlock your bootloader
1. Boot to DL Mode and flash the twrp tar archive through your preferred version of odin (in bl tab)
2. DO NOT LET THE DEVICE BOOT. POWER IT OFF
3. Boot into recovery (Pow + Vol Up + USB plugged)
4. Go To Wipe -> Format Data
5. Flash orangefox recovery zip and reboot recovery
6. Flash Disable_Dm-Verity_ForceEncrypt_*.zip
7. Flash Rootfix.zip (mandatory on pie, q)
Boot the device and set it up again
8. Flash Magisk (optional)
DO NOT SETUP ANY FORM OF SCREEN LOCK ON STOCK ROM
For users who already have TWRP:
Just flash the flashable zip
Bugs
Encryption
You tell me :silly:
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Flashlight
* Password, torch, led
* Support for Miui and Custom ROMs
* Superb new UI and themes
* OrangeFox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Screenshots
https://files.orangefox.tech/Screenshots/R10/
Sources:
DT: https://github.com/rupansh/twrp_device_samsung_gta2xl/tree/android-9.0
Kernel: https://github.com/rupansh/android_kernel_samsung_msm8953 (Rootfix HEAD = d74120555f651b0189e166d96e54605cbca347b4)
Rootfix Q: https://github.com/rupansh/android_kernel_samsung_gta2xl/tree/android-10
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Samsung Galaxy Tab A series
Contributors
rupanshji
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Stable Release Date: 2020-02-26
Created 2020-02-25
Last Updated 2020-12-28
Reserved
Telegram group for testing and general development discussion(T590/T595/T597): https://t.me/smt595
This guide and recovery will work with Samsung Galaxy Tab A (2018) SM-T595N?
kimo9hero said:
This guide and recovery will work with Samsung Galaxy Tab A (2018) SM-T595N?
Click to expand...
Click to collapse
I haven't tested personally. I cant find any info about T595N when I do a google search. what firmware are you on
not working on T597P,when i try to flash it i get size error in TWRP, then tried to flash just the img with tar tool and odin and it hangs. The original TWRP works though.
edit: Used a different version of twrp from another thread and was able to successfully flash.
Good Job, Good Job! Orange fox will be really well used on a custom lineage ROM. Again, Good Job!
koobie777 said:
not working on T597P,when i try to flash it i get size error in TWRP, then tried to flash just the img with tar tool and odin and it hangs. The original TWRP works though.
edit: Used a different version of twrp from another thread and was able to successfully flash.
Click to expand...
Click to collapse
Which version of twrp you used? I have the same size error message.
edit: ok, i have found
https://drive.google.com/drive/folders/1yeSLA6lgyKRVQhec5nbyThN-bVED_B8n
dm.homelinux.com said:
Which version of twrp you used? I have the same size error message.
edit: ok, i have found
https://drive.google.com/drive/folders/1yeSLA6lgyKRVQhec5nbyThN-bVED_B8n
Click to expand...
Click to collapse
that's the one I uploaded and was gonna link to you haha nice
Samsung Galaxy Tab A 2017 SM T385
OrangeFox Recovery Project & Viper OS for "Samsung tab a 2017 sm t385",anybody who can help on this topic.....................Please help me...................
Glad to see some development of SM-T595. Im looking forward to try things soon.
From "For users on stock" -
8. Flash Magisk (optional)
Click to expand...
Click to collapse
Using which method?
Also, how does this conflict/overlap/interact with [root-samsung-galaxy-tab-10-5-2018]?
Is this recovery treble enabled?
for T590 is now Android Q available. Anyone successful tried to use TWRP or Orangefox with it? T590XXU3CTH1_T590OXM3CTH1_DBT
I tried:
Erase all/Flash Stock/Flash TWRP from this Post, wasn´t able to boot to TWRP
Erase all/Flash Stock/Flash TWRP 3.3.1, boot to TWRP. Flash Fox. Run into recovery loop
Updated bugged twrp link
Fixed stock instructions
New update + Q rootfix coming soon
Marpo12 said:
for T590 is now Android Q available. Anyone successful tried to use TWRP or Orangefox with it? T590XXU3CTH1_T590OXM3CTH1_DBT
I tried:
Erase all/Flash Stock/Flash TWRP from this Post, wasn´t able to boot to TWRP
Erase all/Flash Stock/Flash TWRP 3.3.1, boot to TWRP. Flash Fox. Run into recovery loop
Click to expand...
Click to collapse
looking forward to Orangefox release . Alternativ solution for time inbetween to get root acccess on Android Q/10. Tested with T590XXU3CTH1_T590OXM3CTH1_DBT follow instructions on
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
hello,
i tried this on T590 and didn't manage to install it.
bootloader unlock, of course.
1st try : Flash Stock, Flash TWRP from this Post => reboot in download mode at each boot
2nd try :Flash Stock, Flash TWRP 3.3.1, boot to TWRP. Flash Fox from this post. => reboot in download mode at each boot
all on android 9 T590XXU3BTE2_T590OXM3BTE2_AUT
before, i was on android 10 T590XXU3CTH1_T590OXM3CTH1_AUT_10
did someone manage to install orange fox on T590 ?
Lebannen74 said:
hello,
i tried this on T590 and didn't manage to install it.
bootloader unlock, of course.
1st try : Flash Stock, Flash TWRP from this Post => reboot in download mode at each boot
2nd try :Flash Stock, Flash TWRP 3.3.1, boot to TWRP. Flash Fox from this post. => reboot in download mode at each boot
all on android 9 T590XXU3BTE2_T590OXM3BTE2_AUT
before, i was on android 10 T590XXU3CTH1_T590OXM3CTH1_AUT_10
did someone manage to install orange fox on T590 ?
Click to expand...
Click to collapse
Hi, T595 recovery images are not compatible with T590 because of different kernel.
rupanshji said:
Hi, T595 recovery images are not compatible with T590 because of different kernel.
Click to expand...
Click to collapse
thanks for your reply.
ok but sad. I'm stuck with samsung official rom as there is almost nothing for the T590
added rootfix for android q
Helo, im searching for any twrp for Sm T597V thanks

[ End-Of-Life ][ROM][A12]KOSP for OnePlus 7[OFFICIAL][guacamoleb]

Code:
/*
* DISCLAIMER: Read this carefully
* 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.
*/
{
"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"
}
KOSP is a small project based off AOSP and we intend to improve upon AOSP to provide a stable and better alternative to OEM roms with additional features.
Features
There are some cool features, see for yourself
Truth is I'm just lazy to write a long list of features and we intend to focus on the stability rather than adding a ton of features.
Gapps is included!
What's broken?
- WiFi Display on devices using MiraCast
- You tell me!
Bug reporting:
-> DO NOT report bugs if you're running a custom kernel or you installed Xposed
-> Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
-> Do not approach us without any logs for reporting bugs
-> If it is a random reboot, grab everything from /sys/fs/pstore. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
-> Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Downloads: Sourceforge : Mirror
Magisk: https://github.com/topjohnwu/Magisk/releases
INSTRUCTIONS
First time installation:
* Unlock bootloader
* Download the fastboot image of the rom (the zip file with "-img" in it)
* Boot to fastboot
* Type fastboot update <fastbootrom>
* Boot to recovery if you are flashing for the first time and format data
(PLEASE FOR THE LOVE OF GOD DO NOT WIPE DATA FROM FASTBOOT YOU LAZY ****)
* Reboot
Upgrading:
Via recovery:
* Reboot to recovery
* Flash ROM zip from TWRP or sideload with ADB (preferred)
* Reboot to recovery
OR
* Download the fastboot image of the rom (the zip file with "-img" in it)
* Boot to fastboot
* Type fastboot update <fastbootrom>
* Flash Magisk and other stuff (optional)
* Reboot
Via updater app: [WIP]
* Open Settings -> System -> KOSP Updater
* Download the ota if available or if you have already downloaded the zip then use it for local upgrade
* Install the update
* Flash magisk to inactive slot (optional)
* (optional) Reboot to recovery if you have anything else to flash
* Reboot
Follow us on Telegram
Credit/Thanks:
Google for AOSP
LineageOS
YAAP
DerpFest
MSM-Xtended
And all others we may have forgotten to credit
Special thanks to @npv12 and also to @AnnoyingZlatan for his amazing kernel.
Thanks to @Mohammed_Gabr for making our awesome banner.
Last but not the least, thanks to all our testers, who have helped us to squash many bugs as possible
KOSP, ROM for the OnePlus 7
Contributors: @Joker123##, @npv12
Device maintainer: HARISH
ROM source: https://github.com/AOSP-Krypton
ROM Kernel: Dora kernel
Kernel source: https://github.com/AOSP-Krypton/kernel_oneplus_sm8150
ROM Firmware Required: OOS 11.0.5.1
Android Version: 12
Based On: AOSP
Version Information
Version: 2.6
Status: Stable
Created 2021-11-09
Last Updated 2022-04-23
congrats for first official build
maksood2088 said:
congrats for first official build
Click to expand...
Click to collapse
Thank you so much I've been waiting for this!
Sorry for being newbie, can you provide more detailed installation guide? I'm on OOS 11.0.4.1 and have my bootloader unlocked, but no root nor custom recovery.
Also if I removed my phone lock (pin and fingerprint) prior to the installation would I still need to format my personal data?
Thanks again!
mvci said:
Thank you so much I've been waiting for this!
Sorry for being newbie, can you provide more detailed installation guide? I'm on OOS 11.0.4.1 and have my bootloader unlocked, but no root nor custom recovery.
Also if I removed my phone lock (pin and fingerprint) prior to the installation would I still need to format my personal data?
Thanks again!
Click to expand...
Click to collapse
Yes and for installation support join the linked telegram
Great work Harish. Also congratulations for first official. Good ROM, highly recommended. Definitely daily driver and better than A11.
Thanks for still continuing to develop for the OP7.
I was a little confused about how to install it, but I'll try to go to the telegram to understand it better.
Great work.
I have installed it yesterday and it is working great and pretty smooth than A11 roms. I am planning to use it as daily driver, not sure if all apps i use including banking apps are compatible with A12 yet. E.g. HSBC India app is broken on this rom. Please confirm if itbcan work. Thanks.
Also request to include face unlock feature under security tab if possible in the next build. Thanks.
gdp1979 said:
Great work.
I have installed it yesterday and it is working great and pretty smooth than A11 roms. I am planning to use it as daily driver, not sure if all apps i use including banking apps are compatible with A12 yet. E.g. HSBC India app is broken on this rom. Please confirm if itbcan work. Thanks.
Click to expand...
Click to collapse
Sorry for noob questions in advance.
I can see installation is done via fastboot only, but after installation we need to format data from recovery.
1. Which recovery to use to format data? I doubt rom comes with a recovery.
2. Format data to f2fs or ext4?
3. How's the situation with widevine L1? If you have it then can you post steps for that as well.
Right now I'm on stock rom with locked bootloader.
himsin said:
Sorry for noob questions in advance.
I can see installation is done via fastboot only, but after installation we need to format data from recovery.
1. Which recovery to use to format data? I doubt rom comes with a recovery.
2. Format data to f2fs or ext4?
3. How's the situation with widevine L1? If you have it then can you post steps for that as well.
Right now I'm on stock rom with locked bootloader.
Click to expand...
Click to collapse
Once you install ROM from fastboot as mentioned in OP, after installation is complete your phone automatically restarts at that time you have to boot into recovery. The recovery this time will be ROM recovery in which you will have to format data before to reboot to system. Hope this helps.
gdp1979 said:
Once you install ROM from fastboot as mentioned in OP, after installation is complete your phone automatically restarts at that time you have to boot into recovery. The recovery this time will be ROM recovery in which you will have to format data before to reboot to system. Hope this helps.
Click to expand...
Click to collapse
Could you describe the step by step installation? I would like to exit A10 10.3.8 for KOSP.
lvints said:
Could you describe the step by step installation? I would like to exit A10 10.3.8 for KOSP.
Click to expand...
Click to collapse
Steps are pretty simple as mentioned in OP. Update your phone to latest OOS (A11) first before to go for this A12 ROM.
The rom is smooth and responsive, I will use it as daily driver.
Issues I face:
1- my voice sounds digitalized or something, using the phone built in mic.
2- The notification panel sometimes become 100% transparent.
3- Sometimes the whole screen flashes with max brightness during fingerprint unlocking. (Maybe started to happen after enabling single tap to wake)
4- In SIMs settings, only the 1st SIM is showing, and I can deactivate it, however, my 2nd SIM isn't showing there and there's no way to deactivate it (both SIMs are working all the time)
5- I think the vibration intensity while setting the alert slider to vibration is quite high (maybe I'm used to OOS).
6- Vibration intensity for notifications is also a little bit high even though I set it as "low" in settings.
The fingerprint unlocking vibration intensity is the perfect intensity for me (I think it's like the OOS one) I hope you can make the "low" option equal to that
I'll update my reply whenever I face new things.
All are minor issues, otherwise, amazing rom, thank you so much I really appreciate all the hard work you do.
P.S. If anyone wants to enable the "single tap to wake" it's under Settings - krypton settings - device settings - touchscreen gestures - single tap. I thought this could help someone.
Does cromecast work?
Does fingerprint work as good as on oxygen os?
Is battery good? I have bad battery on oxygen os 11.0.4.1, android system is eating my battery...
For root i just instal magisk app through fastboot or in the twrp?
Thank you for your anwsers.
Edit: can not install via ADB. Instalation guide is not good for me. Should I unzip file with image or not. Do not have theese problems when instaling other roms. Any help would be apreciated.
kodrnusa said:
Should I unzip file with image or not.
Click to expand...
Click to collapse
No, you shouldn't unzip it.
mvci said:
No, you shouldn't unzip it.
Click to expand...
Click to collapse
Ok but command fastboot update kosp does not execute. It says file not found...
kodrnusa said:
Does cromecast work?
Does fingerprint work as good as on oxygen os?
Is battery good? I have bad battery on oxygen os 11.0.4.1, android system is eating my battery...
For root i just instal magisk app through fastboot or in the twrp?
Thank you for your anwsers.
Edit: can not install via ADB. Instalation guide is not good for me. Should I unzip file with image or not. Do not have theese problems when instaling other roms. Any help would be apreciated.
Click to expand...
Click to collapse
I don't use Chromecast but on telegram people have reported that it works. Just Miracast is not working.
Battery life cannot be determined this soon
Magisk is reported to be working. Need patched boot.img to be flashed via fastboot
You can't install this rom via adb. Only fastboot method works as of now.
kodrnusa said:
Ok but command fastboot update kosp does not execute. It says file not found...
Click to expand...
Click to collapse
Keep the KOSP fastboot ROM img-ZIP file in the platform/fastboot folder. This issue will be resolved
Looks like a new build is up

Categories

Resources