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.
*
*/
Hi,
this is nearly completely based on:
LineageOS 19.1 (Android 12L) for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 BETA
/* * 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...
forum.xda-developers.com
Thats why we still have the same bugs, if I solve them, both will receive updates.
Here you can see how far everything is working for now.
Spoiler: Whats working
N8000, N8010, N8013, N8020:
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
GPS
Wifi
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus with gestures and hovering icon
RIL
much more...
Spoiler: Whats not working
Random reboots
sec_keyboard, dock keyboard station, because it drains the battery somehow
Screen lightning bug
Long screenshot
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N8000 / N8005 Rom
N8010 / N8013 Rom
N8020 Rom
Spoiler: Changelog
15.03.2022
01.04.2022
13.07.2022
18.08.2022
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
https://androidfilehost.com/?fid=7161016148664799666
There is no space for gapps, if you don't expand the system partition manually.
I would recommend to use microG instead,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
In some cases the sim card becomes unusable while typing in the code.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][N8000/N801x/N8020][BETA] crDroid 8.3, ROM for the Samsung Galaxy Note 10.1
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: crDroid, LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2022-03-12
Last Updated 2022-08-18
*reserved
First of all, thank you for that ROM. It keeps my beloved Tablet alive
Yesterday I installed it exactly like discribed. After flashing (without Gapps) and the newest version of TWTP. The Rom stucks with the wizard at the "no Sim card inserted" screen. The tablet n8010 didn't got a Sim slot?!
I tried to erase "data" partition, but had no luck.
The lineage os from your page works like a charm.
What can I do?thanks
Avalon01 said:
First of all, thank you for that ROM. It keeps my beloved Tablet alive
Yesterday I installed it exactly like discribed. After flashing (without Gapps) and the newest version of TWTP. The Rom stucks with the wizard at the "no Sim card inserted" screen. The tablet n8010 didn't got a Sim slot?!
I tried to erase "data" partition, but had no luck.
The lineage os from your page works like a charm.
What can I do?thanks
Click to expand...
Click to collapse
Hi,
thanks for your report,
I've honestly thought that I've fixed this problem in the build of yesterday,
did you try this one or the build from the 12.03?
YES! Thank you. It's fixed. Yesterday I tried the Version from the day bevore yesterday
Best regards
Avalon01 said:
YES! Thank you. It's fixed. Yesterday I tried the Version from the day bevore yesterday
Best regards
Click to expand...
Click to collapse
Great .
Update 15.03.2022:
Fixed setup wizard completely
Fixed Updater crash
Hopefully improved screen lightning bug
I didn't get Magisk to work. After flash (the file which is linked here) and starting Magisk app it wants to update. It updates to newest version. After reboot it wants to update boot image. But it fails. "no image found"
If I play this game with the latest version (factory reset, erasing system +flash your image + install 24.3) the all says after opening "there is something to install, do you want to reboot?" like this. If I push yes it says "setup failed" and nothing. Magisk (root) does nothing.
The second problem is video performance. I tested vlc with several configuration. But it lags. Screen freezes. I got a Samsung tab 3 with a custom rom ( Android 7) and it runs like hell
The Gt n8010 must be much better! So I think it's a problem coming from an driver!?
I hope you like that feedback here.
Best regards
Avalon01 said:
I didn't get Magisk to work. After flash (the file which is linked here) and starting Magisk app it wants to update. It updates to newest version. After reboot it wants to update boot image. But it fails. "no image found"
Click to expand...
Click to collapse
Hi,
try Magisk v23 or 24.1, newer version will cause problems.
Avalon01 said:
The second problem is video performance. I tested vlc with several configuration. But it lags. Screen freezes. I got a Samsung tab 3 with a custom rom ( Android 7) and it runs like hell
Click to expand...
Click to collapse
It depends on which video format is used,
in the first version, OMX.SEC.AVC.Decoder was removed,
because it starts some videos the first minute weirdly.
Could you give it a retry with the most recent version?
Also, I would need a logcat while performing some action, otherwise I can't do anything.
And well, this is Android 12, it may also run like hell with Android 7 .
Avalon01 said:
The Gt n8010 must be much better! So I think it's a problem coming from an driver!?
Click to expand...
Click to collapse
It must not, consider that you're running Android 12 on a 10 year old device, it's not a problem of a driver,
it's more a decoding issue.
@html6405
Best new rom for our old N80.. series.......still a lot better than LineageOS19 I think....
@html6405
Sorry, but I have some problems with VPN....
Theres no possibility to customize vpn (no "+" sign)
And another problem (same as with lineageOS17-19):
Some apps (for example covPass or some banking apps (phototan)) are not able to scan (camera function fails)
But nevertheless: Best rom with many customisation possibillities (from crdroid)
Hey,
Good morning, CR Droid 8.3 was released with android 12L, Will this Rom receive this update?
Alexfs said:
Hey,
Good morning, CR Droid 8.3 was released with android 12L, Will this Rom receive this update?
Click to expand...
Click to collapse
Thats already in work
Update 01.04.2021:
Synced with crDroid 8.3 sources (Android 12L)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
Implemented Boeffla sound
Switched from Camera2 to OpenCamera because of implementation problems, this means that the flashlight won't work until I've fixed this
Attention: a clean installation is needed!
html6405 said:
Update 01.04.2021:
Synced with crDroid 8.3 sources (Android 12L)
Fixed boot problem, which mostly appeared after booting from TWRP
Fixed shutdown bug (device restarted sometimes instead)
Implemented Boeffla sound
Switched from Camera2 to OpenCamera because of implementation problems, this means that the flashlight won't work until I've fixed this
Attention: a clean installation is needed!
Click to expand...
Click to collapse
Lets test
@html6405 AVC decoder enabled, right?
Vladdrako said:
@html6405 AVC decoder enabled, right?
Click to expand...
Click to collapse
Still disabled.
What GApps do I install? I tried the Mindthegapps and Nikgapps from the LineageOs 19.1 thread but all of them keep telling me that I "have not enough space to install GApps".
Operator69 said:
What GApps do I install? I tried the Mindthegapps and Nikgapps from the LineageOs 19.1 thread but all of them keep telling me that I "have not enough space to install GApps".
Click to expand...
Click to collapse
None of them will fit, you would have to expand your system partition.
Is there a how to?
Maybe that's the problem here with my n8010. After installing some apps got fc. And magisk definitely DON'T work for me. After install (every time clean) many apps are closing immediately after start. And the system is laggy. I tested versions 22.0,23.0 and 24.1. All with a new and clean installed system. Flashing via twrp.
The only systems which work are lineage 16.0 and 19.1 WITHOUT root
19.1 without root works very stable and fast. Cr doesn't. Maybe you are working with an other device E.G. N8000. And the version for n8010 has a problem. Or I have to increase some partition or space!?
BTW thank you for the great ROM!
Related
Code:
#include
/*
* 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.
*
*/
When coming from any other ROM, you must do a factory reset / clean flash.
The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.
Links
ROM: http://download.cyanogenmod.org/?device=victara
Changelog: http://www.cmxlog.com/13/victara
GAPPS: I don't what is the best one yet, but I am personally using Slim mini. OpenGapps are also recommended often.
PROTIP: Be sure to flash gapps at the same time you flash the rom. If you boot into cm-13.0 without gapps and attempt to flash them later, you're going to have a bad time
Sensors / Ambient Display
If you have "Ambient Display" enabled in Settings >> Display then:
* the stow sensor and flat up sensor will pulse the display when the phone is picked up
* the IR sensors will pulse the display when you wave your hand over the phone
By default the "doorknob" gesture will launch the camera and the chop-chop gesture will toggle the torch.
Finally, when there is an incoming call, waving your hand over the phone will silence the ringer.
If you want to change the behaviour of these various gestures, go to Settings >> Gestures and you can change all of those options.
Known Issues
* TBD
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
XDA:DevDB Information
Official CM-13.0 nightly releases, ROM for the Moto X 2014
Contributors
crpalmer, invisiblek
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly
Created 2015-11-24
Last Updated 2015-11-25
Reserved
Nice !
BEST ANDROID, only facebook & messenger cashes but i found some apks working fine now i guess can't update thm
Thanks a lot!
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
Snapchat and Facebook force closing here
kasrawis said:
BEST ANDROID, only facebook & messenger cashes but i found some apks working fine now i guess can't update thm
Click to expand...
Click to collapse
these should be fixed in the next nightly (assuming i get the patch finished in time, worst case scenario the one after that)
kasrawis said:
BEST ANDROID, only facebook & messenger cashes but i found some apks working fine now i guess can't update thm
Click to expand...
Click to collapse
In other forums, I saw that it can be operated as follows:
Using Root Explorer, find and delete the "libsslx.so" /data/app/com.facebook.orca-1/lib/arm file directory
In my case, it works.
The problem is that I do this, every time you restart the phone
Excuse me for my bad english. Or at least, forgive the translator of Google.
Is root finally working or still broken???
gianboy said:
Is root finally working or still broken???
Click to expand...
Click to collapse
Root works for root apps but does not allow to make changes on /system
Sent from my XT1092 using Tapatalk
invisiblek said:
these should be fixed in the next nightly (assuming i get the patch finished in time, worst case scenario the one after that)
Click to expand...
Click to collapse
Great! So Snapchat should also work with the patch? It force closes every time on cm13.
Sent from my Moto X
Google Camera FC when trying to launch video recorder.
Snapchat and facebook are working on the 11/25 build, Google camera from play store is working to. Thanks!
crpalmer said:
Code:
#include
/*
* 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.
*
*/
When coming from any other ROM, you must do a factory reset / clean flash.
The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.
Links
ROM: http://download.cyanogenmod.org/?device=victara
Changelog: http://www.cmxlog.com/13/victara
GAPPS: I don't what is the best one yet, but I am personally using Slim mini.
Sensors / Ambient Display
If you have "Ambient Display" enabled in Settings >> Display then:
* the stow sensor and flat up sensor will pulse the display when the phone is picked up
* the IR sensors will pulse the display when you wave your hand over the phone
By default the "doorknob" gesture will launch the camera and the chop-chop gesture will toggle the torch.
Finally, when there is an incoming call, waving your hand over the phone will silence the ringer.
If you want to change the behaviour of these various gestures, go to Settings >> Gestures and you can change all of those options.
Known Issues
* TBD
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
XDA:DevDB Information
Official CM-13.0 nightly releases, ROM for the Moto X 2014
Contributors
crpalmer, invisiblek
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly
Created 2015-11-24
Last Updated 2015-11-24
Click to expand...
Click to collapse
gapps ???
http://opengapps.org/?api=6.0&variant=nano
I can't seem to enter recovery since I've installed cm13 (yesterday's build). I'm trying to instal today's build but I'm unable to because I can't enter recovery mode. Initially I was using TWRP, then I installed CM's recovery, but that didn't work either.
Any thoughts?
felipevsw said:
I can't seem to enter recovery since I've installed cm13 (yesterday's build). I'm trying to instal today's build but I'm unable to because I can't enter recovery mode. Initially I was using TWRP, then I installed CM's recovery, but that didn't work either.
Any thoughts?
Click to expand...
Click to collapse
i had the same problem, the only solution was to flash the stock rom back, let it boot once and than reflash twrp.
That's exactly what I was going to try now.
uluf said:
i had the same problem, the only solution was to flash the stock rom back, let it boot once and than reflash twrp.
Click to expand...
Click to collapse
felipevsw said:
That's exactly what I was going to try now.
Click to expand...
Click to collapse
felipevsw said:
I can't seem to enter recovery since I've installed cm13 (yesterday's build). I'm trying to instal today's build but I'm unable to because I can't enter recovery mode. Initially I was using TWRP, then I installed CM's recovery, but that didn't work either.
Any thoughts?
Click to expand...
Click to collapse
I was able to get in with this recovery: http://forum.xda-developers.com/showpost.php?p=61558425&postcount=222
Side note - does anyone else get these weird artifacts in the nav keys area when in landscape mode in certain apps? It's duplicated my bluetooth icon here but it has done all sorts of weird corruption other times...
surrealjam said:
Side note - does anyone else get these weird artifacts in the nav keys area when in landscape mode in certain apps? It's duplicated my bluetooth icon here but it has done all sorts of weird corruption other times...
Click to expand...
Click to collapse
+1
Camera Bug
@crpalmer, @invisiblek: came accross a bug... Took a snap with Google Camera successfully once. Second time I try, the image freezes when I click the shoot button. I can interact with the camera app in some ways, like the swipe-from-left for options, and I can interact with the navbar, status bar, etc. But the image remains frozen, it isn't saved, and I can't proceed to click another pic until I restart the phone. Log attached; verbose; from CMAction to bring up camera, to close of camera.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
It should go without saying, but do not lock your bootloader with this installed. You must be 100% stock, I'd suggest on both slots, in order to re-lock your bootloader. Doing otherwise will likely lead to a brick that Essential really shouldn't warranty.
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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Unofficial LineageOS Builds
Essential PH-1 (mata): https://updater.invisiblek.org/mata
Google apps
Google apps (opengapps nano) are baked in to these builds. This is due to the A/B partition layout and complications backing up/restoring gapps between builds. This is not ideal, and is the major road block to getting this device in to official status with Lineage. At this time I do not plan to release non-gapps builds. Users who require this will have to build their own.
Source
Device | Kernel
Here's a local_manifest for those who want to build at home.
Prerequisites
Unlocked bootloader
OPM1.180104.092 firmware - even if you were on this build, you should flash this firmware package to ensure the firmware is on BOTH slots.
Fastboot and ADB set up (use your google-fu to figure this out)
Installation
This device is different than what most people are familiar with due to the A/B partition layout. If you're familiar with Pixel devices, then you already know what this means. This thread isn't really designed to explain how it all works, that should be handled somewhere else. Instead, I'll assume you can either follow directions or do some research on your own. Additionally I have a discord set up where there are several people who may be able to help if you run in to a snag.
The initial install should go rather smooth, and future updates can be taken through the built-in Lineage updater app (yes, the are the seamless updates you may have heard about). Due to A/B, the recovery's ramdisk is actually on the boot.img partition (the rom's ramdisk is on the system partition now). What this means is once you flash the rom, it essentially (lol) replaces the TWRP that you have installed. This shouldn't be a problem since with the seamless updates, you shouldn't have to ever go into recovery. If you find yourself needing recovery, you'll have to re-flash TWRP to get there.
Phew, now some instructions.
See the prerequisites. You really do need these or things aren't going to work for you.
Boot into bootloader mode and wipe data with:
Code:
fastboot -w
Download twrp (mirror) and flash it with this command:
Code:
fastboot flash boot twrp-mata_11.img
(no, this isn't a typo, you are flashing twrp to the boot partition)
While still in bootloader mode, use vol down to select "Recovery mode" and hit the power button. This should boot you in to TWRP. Enter your previous lock screen password or pin (if it asks) to decrypt your data partition.
Put the device in sideload mode with:
Code:
adb shell twrp sideload
Install the zip via adb sideload with:
Code:
adb sideload <zip name here>
When finished, reboot.
Profit!
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata), ROM for the Essential Phone
Contributors
invisiblek
Source Code: [url]https://github.com/LineageOS[/URL]
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2017-11-12
Last Updated 2017-11-11
Q: What is broken?
A: Nothing I'm aware of
Q: Can I use the stock Essential camera app?
A: Yes
Q: Does the 360 cam work?
A: No.
Q: Is this rooted?
A: No. You're on your own for that.
Q: Does this pass SafetyNet?
A: Yes. Android pay, Pokemon Go, etc work fine. If you root, depending on your root method, you may lose this ability. But the ROM itself does pass SafetyNet.
2017-11-20 FAQ rollup: https://forum.xda-developers.com/showpost.php?p=74580036&postcount=189
FAQ site with some more info (be gentle with the terrible, or should i say complete lack of, css)
"Why no work" bug reports incoming in 5,4,3,2,1....
EDIT: @invisiblek if you need this post for anything, let me know.
THANK YOU!! So glad to see this. Just ordered the essential yesterday.
Any known bugs? How is performance compared to stock? Thanks for this!
Install it and find out. It's a testing build.
Awesome! Mine will be here soon.. glad to see development!!
Sent from my Nexus 6 using Tapatalk
First time with an A/B device, so everytime you update with a new build to the updater site it will prompt us and begin updating in the background? Don't have to be specific with the process itself but I was just curious as I'd like to stay up to date as possible if I start the custom ROM endeavor since it's still early on in development. Thanks!
installing now.. OP the link to twrp is broken
Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.
Oh, and the night mode works great!
^TWRP link worked for me about 30 mins ago
Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.
360 Camera doesn't work.....
CaptainElwood said:
Thanks OP!
Got it up and running, seems pretty solid for the first build. The initial setup wizard hung at the last step for me but after a reboot it worked.
Oh, and the night mode works great!
^TWRP link worked for me about 30 mins ago
Update: I have installed most all of my apps and have been playing around setting up the phone for the last ~30mins....no stutters, no mistouches, everything is working great. LTE+ on VZW works, as well as Verizon messaging app. The phone apk has the option for vvm, haven't tested. Overall I can't believe how well this runs...ROM development has come a long way from the initial releases I'm used to on non nexus devices.
Click to expand...
Click to collapse
Same feelings here. I really hope vvm works. Will test tomorrow... The ROM already kept me up tik now 3:09am
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
Also on vzw don't see LTE + though.
Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?
Sent from my ONEPLUS A5000 using Tapatalk
Works great! Found a wifi bug
Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.
Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot
Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.
EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?
https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing
Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.
omvir said:
Has installing lineage fixed the low signal strength problem for those people that have been experiencing it?
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
My signal strength improved from 2 bars to 3 bars at home, but I'm not sure if the reception has improved or just the number of bars displayed at certain signal strengths..
back2you said:
360 Camera doesn't work.....
Click to expand...
Click to collapse
You betrayed Sony
TWRP DL link not working
tclaybor said:
Following the instructions posted, wifi stops working after flashing twrp and rebooting back into LOS. I flashed addonsu-14.1-arm64-signed.zip to enable App access to root. It worked, but wifi is broken on reboot. It turns itself off immediately after turning on.
Replication steps:
1. Follow steps in OP.
2. Reboot to bootloader (adb reboot-bootloader)
3. Flash twrp_mata-6.img (fastboot flash boot twrp.img)
4. adb push addonsu-14.1-arm64.zip /sdcard/
5. Install .zip in TWRP
6. Reboot
Anybody else getting this issue? The only way I've been able to fix it is to re-flash LOS.
EDIT: Thanks to @bmg1001, this issue is resolved (for me at least) by using this build of TWRP... Sorry, I can't post links yet! Can someone link this please?
https:// drive.google. com/file/d/1Pp9Hep-EEGNHLl6I_ob7ugihpKfrAcWm/view?usp=sharing
Note that flashing this TWRP build will allow you to reboot to recovery at any time without having to reflash TWRP, as mentioned in the OP.
Click to expand...
Click to collapse
Good Morning!
The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started!
makbomb said:
Good Morning!
The URL for TWRP isn't working for me. I copy pasted it in chrome address bar. Could someone please kindly help? I'm drooling to get started!
Click to expand...
Click to collapse
Go to the rooting guide and it's in there. Use the mirror
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
One thing I noticed is cell service is much weaker so far. In this same spot if my bedroom used to go from 99 to 103 dbm. Now it's at a118. Will monitor and report.
Shows 0 bars of service. Used to be 2-3
strictlyphat said:
Go to the rooting guide and it's in there. Use the mirror
Click to expand...
Click to collapse
Thanks, but it sounds like @tclaybor is using a different version, provided to him by @bmg1001 , since you'll see he was trying to link a google drive to that version?
makbomb said:
Thanks, but it sounds like @tclaybor is using a different version, provided to him by @bmg1001 , since you'll see he was trying to link a google drive to that version?
Click to expand...
Click to collapse
The one in bmg1001 thread worked. But have to click mirror.
---------- Post added at 02:54 PM ---------- Previous post was at 02:54 PM ----------
If u do get it installed let me know about signal. Mine taking big hit.
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
I've built a clean version of LineageOS 17.1 for Mi 9 that includes Signature Spoofing, but no other modifications.
This will allow those who are interested to get full MicroG support without the need of using any sort of Patcher or Magisk/XPosed Module. YOu all may have used my previous LineageOS Clean,Stock ROM and this is just an updated build of that ROM + Signature Spoofing to make life easier for those who want MicroG.
I flashed this and followed the simple steps of installing F-Droid, adding the MicroG Repo, and Installing the necessary packages via F-Droid and confirmed MicroG Self-check passes all the tests (once you finish granting the necessary permissions for each).
I prefer this over the NanoDroid or other patching methods as a much cleaner way to use MicroG with LineageOS.
Proprietary Blobs/Device Tree are DRG-Developer's as referenced in their post: here
Kernel source is by DRG-Developer: here
Xiaomi Hardware package used is the primary LineageOS from their github here
My reason for this is that there does not seem to be an officially-supported build for our device on the LineageOS for MicroG project or a recent, unofficial build.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Download:
849.98 MB file on MEGA
mega.nz
Prerequisite:
Make sure you are running a current AOSP/MIUI ROM with the latest firmware flashed and TWRP Installed
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Format Date ---> 'yes'
3) push ROM zip to /sdcard/
4) Flash ROM zip
4b) - OPTIONAL - Flash Magisk Zip for Root
5) Reboot to system
If you want to to install MicroG, just follow the steps outlined here in the "Install" section to get F-Droid installed, add the MicroG Repo, and install the handful of apps needed. No need for any of the patching steps.
DRG-Developer's device trees were last updated on 2020-10-18 so expect this build to reflect that. So far everything seems to function very well.
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Vogie said:
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Click to expand...
Click to collapse
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
ICanTrollU said:
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
Click to expand...
Click to collapse
Later/updated device trees and built-in Signature Spoofing that you don't get with stock Lineage.
photonmedia said:
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
Click to expand...
Click to collapse
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Vogie said:
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Click to expand...
Click to collapse
Yes, I do not believe those are included in stock LineageOS.
photonmedia said:
Yes, I do not believe those are included in stock LineageOS.
Click to expand...
Click to collapse
I didn't find any issue that relate to ROM, it's quite stable
I just have a issue on ANXCamera self camera that force close the ANXCamera that I think is not related to ROM
photonmedia said:
...
What Works:
...
NFC Seems to be working but I don't have a device to test against
Click to expand...
Click to collapse
This morning I checked NFC by sending a picture from my MI 9 to my wife's Mi 9T (also equipped with LOS). The transfer was successfull!
Thank you very much for providing this clean (stock) ROM!
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
nico445 said:
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
Click to expand...
Click to collapse
Did you wipe data AND "Format" Data? When you Format data is asks you to confirm by typing "yes" in the TWRP Recovery. Try Wiping and Formatting data, then push the ROM to the phone and Flash.
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
nico445 said:
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
Click to expand...
Click to collapse
Also, be sure you are coming from an updated ROM running current firmware.
Thank for your build ;-)
Are NFC Payements working on it?
john_matrix said:
Thank for your build ;-)
Are NFC Payements working on it?
Click to expand...
Click to collapse
I have not tested payments. Another user confirmed that file transfer via NFC works. I do not use NFC for payments so cannot test.
Hi, does screen off fod work?
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
theandroid02 said:
Hi, does screen off fod work?
Click to expand...
Click to collapse
No, you have to double-tap to wake or hit the power button to wake the screen before you can use the fingerprint scanner.
Vinicius7 said:
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
Click to expand...
Click to collapse
After installing, did you Install F-Droid and enable the Magisk repositories to install the necessary Magisk Modules and Location Backends? Then in the MicroG settings ensure all the checkboxes are checked?
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
dmahtani said:
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
Click to expand...
Click to collapse
I'm not sure. It could be the Signature Spoofing aspect. I don't think iode has that and I know stock LIneage does not.
Do you have Magisk installed?
{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
Another weebified custom ROM aiming to be a home for weebs - Based on Project Materium, an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Click to expand...
Click to collapse
We offer vanilla, GApps and AuroraOSS variants. If you install a vanilla variant, the only supported GApps package is MindTheGapps (GApps/AuroraOSS builds are not available for a few devices due to space issues).
Download & instructions:
Install MIUI 12.5 if you have updated to anything Android 12.
Fully install custom recovery of your choice.
Flash the ROM. You can also sideload it with ADB if you want to.
!!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
After flashing, reboot to recovery.
Format data.
Flash Magisk if you want to.
Reboot to system and enjoy!
Download (Taken down due to discontinuation)
IMPORTANT: If you are coming from another ROM, you need to format data (TWRP > Wipe > Format Data > *type "yes"*).
IMPORTANT: If you want to keep Magisk after each OTA, you need to make it flash to inactive slot **right before rebooting** (Magisk > Install (In "Magisk" card) > Install to inactive slot)
About:
Features:
Latest security patches merged from LineageOS
SafetyNet passing unconditionally without Magisk/with kdrag0n's SafetyNet fix
Many optimizations coming from Stellar OS/Project Materium/droid-ng
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more! (We accept suggestions!)
What's working:
Almost everything
Bugs:
Microphone doesn't work when speaker is enabled during calls.
You tell me.
Sources are available at https://github.com/ProjectKasumi and https://github.com/Kasumi-Devices
Full list of device sources used;
Device tree
Linux kernel tree used
Vendor tree for proprietary blobs
ROM Founded By: Yuki (AITEx64)
ROM Developed By: Beru Hinode
ROM Designed By: Ayuko, Qirkl and UsiF.
ROM OS Version: 1.3 "PoPiPa" R2
ROM Kernel: Customized Linux 4.14.186 from MiCode
ROM Firmware Required: MIUI 12.5.16.0.RKLMIXM (Global)
Based On: Project Materium 1.0 (LineageOS 18.1)
Version Information
Status: Discontinued
Last Stable Version: 1.4 "PoPiPa"
SELinux Status: Permissive
Initial Release Date: July 20, 2022
poggers! atleast some buildbot didn't post it this time
J6idot said:
poggers! atleast some buildbot didn't post it this time
Click to expand...
Click to collapse
It wasn't even their build, they just took my build and posted it away! XD
Let's goo. Very awesome work here
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
solidamage said:
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
Click to expand...
Click to collapse
I could never get used to MIUI myself so I feel you. For custom ROMs, there are quite a lot built (buildbotted) with practically the same bugs as well; you can check them out in respective Telegram groups/channels!
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
It happens to me too ... Any advice?
Is this available on Android 12?
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Oxydeme said:
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Click to expand...
Click to collapse
yup did all the steps in the thread
nintendobuster420 said:
yup did all the steps in the thread
Click to expand...
Click to collapse
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
nintendobuster420 said:
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
Click to expand...
Click to collapse
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
still no fast charge, will keep it tough
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
@HistoriaXV @nintendobuster420 hope you could success flash in the next days
Oxydeme said:
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
Click to expand...
Click to collapse
System reports "Charging slowly" but my battery fully charges from ~10% in just 1.5~2 hours.
nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
I have recently pushed a boot fix about this, you can flash it and format data to get it fixed.
Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
I use the OFOX from Woomy and it works with it too, so it's not recovery fault.
You mentioned firmware requirement there, good shot! Glad to see someone that's not from the development team finally noticing it!
Oxydeme said:
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
Click to expand...
Click to collapse
The vbmeta required is shipped along with the ZIP itself, so whether if you disable it or not, you can always keep verity enabled AS LONG AS YOU DON'T MODIFY ANYTHING INCLUDING INSTALLATION OF TWRP. The boot problem was due to some missing permissions required with Lawnchair 12.0, which was platform-specific issue. I have mitigated it as the lead developer of Kasumi and now just waiting for LineageOS to merge August '22 ASB on their Lineage 18.1 branches to ship newer builds. Until then, I have placed a little flashable that you can slap in on the recovery. It's global (means will work on all devices with latest Kasumi build installed). In fact, all it does is just putting the new permission XML file.
Oxydeme said:
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Click to expand...
Click to collapse
Not at all. Even though I have Secret, everything should be around the same across all variants, given that Woomy also tested it only for NFC during initial bringup before.
Oxydeme said:
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
Click to expand...
Click to collapse
The dedication and the hassle... My God, it's just pure inspiration to me. XD
Oxydeme said:
still no fast charge, will keep it tough
Click to expand...
Click to collapse
As I said previously, it's what system reports presumably due to some SEL denials. I tried to get as many as possible sorted out, still no luck. But just as a fact, it actually is fast charging.
Oxydeme said:
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
Click to expand...
Click to collapse
Well, thank you I guess. ^^;
Before I begin with replies to these, just referring to "dude", I'm a girl so I would prefer you calling me with "dudess" or "dudette" instead. Again, all up to you. No forces here.
The debloat is rather Lineage talent, I really just based on Materium and added things on top.
That 13 GB system partition is something that's coming from partition values from source, so whatever you do unless you flash GSI, it will always be 13 GB. See GitHub:Kasumi-Devices/[email protected]/BoardConfig.mk (Partitions section, BOARD_SYSTEMIMAGE_PARTITION_SIZE flag) for more info.
Eh, I still can't find a way to get CPU info properly, I guess it's related to kernel? Unsure though.
And some more tweaks will come as well, just stay tight! I'm working hard on another update! ;3
Sambit0789 said:
Is this available on Android 12?
Click to expand...
Click to collapse
Unfortunately no. Kasumi 1.x.x are all Android 11. Android 12 Kasumi will be possible only once our internal tests will be done and I finally finish working on Kasumi v2. Hundreds hyped, gradually widening audience, looking into the release of it. xD