Last week my phone had some crazy bugs (if I tried to activate Wifi the settings app freezes *wtf*) so I decided to wipe everything and install LOS, its working well, the only problem is that my PC can't detect my phone anymore even if I manually set MTP Protocol at developer options. You can still transfer files via OTG and PC does detect while using twrp recovery. Another complain its that this OS doesn't feature the off-screen navigation option that I use normally :crying::crying:
Those little problems could be fixed by the time you read this tough, as the dev is currently releasing new builds almost everyday (updates need to be installed via TWRP, searching from Settings doesn't work as it is not official)
Here's how:
1. Unlock bootloader
2. Install TWRP from here (Don't use this one, it won't allow you to instal LOS, it will say your device is incompatible.)
3. Wipe everything and format with twrp
4. Download LOS/Gapps from this tread (don't worry as it says it is for the Honor View 10, it will work for the normal Mate 10) and optionally download Magisk for root (root addon from Lineage doesn't work). Right after installing LOS, make sure to install gapps and Magisk before booting into system, otherwise your phone will explode and you die.
Important: The recovery you just downloaded won't work with this OS, so if you need twrp again, flash this. Touch doesn't work with this recovery, so you need to use a mouse via OTG.
What build?As i know last builds have model check?
Maxikus2711 said:
What build?As i know last builds have model check?
Click to expand...
Click to collapse
I'm using 15.1-20180504_232549, to lazy to update to the latest. If you meant by compatibility I think it has to be with your recovery rather than OS build, as they have only minor changes.
dan_729 said:
I'm using 15.1-20180504_232549 (its not the latest)
Click to expand...
Click to collapse
What about check model?
Some Questions to those running Lineage OS on the Mate 10 Pro:
How is the included Camera Quality?
Does Video Recording work?
Can you run the Google Camera Ports with HDR+ and Portrait Mode?
How is the performance in general?
Using the Huawei camera on LOS, do the AI features work?
Thanks!
madphone said:
Some Questions to those running Lineage OS on the Mate 10 Pro:
How is the included Camera Quality?
Does Video Recording work?
Can you run the Google Camera Ports with HDR+ and Portrait Mode?
How is the performance in general?
Using the Huawei camera on LOS, do the AI features work?
Thanks!
Click to expand...
Click to collapse
Camera quality & performance is REALLY bad. I'm not sure if AI works, as I'm unable to download Huawei original camera apk;
Camera recording works, screen recording doesn't;
Not any noticeable performance differences, its battery consumption is a little bit higher though ~+ 10%
+1 subscribe
I tried but I have twrp error failed to unmounts system
Maxikus2711 said:
I tried but I have twrp error failed to unmounts system
Click to expand...
Click to collapse
i still have this problem as well. /system and /vendor don't want to unmount. everything flashed ends with code 70 (not enough free space)
is this maybe because we have to root before installing/using TWRP?
WaxysDargle said:
i still have this problem as well. /system and /vendor don't want to unmount. everything flashed ends with code 70 (not enough free space)
is this maybe because we have to root before installing/using TWRP?
Click to expand...
Click to collapse
No, no root required, you just need to wipe and format data a couple of times. (I also had that error) You can also try formatting /system & /data to exFat, that didn't worked for me though.
I tried more time,and all in all i have google framewotk or google servicrs error
Sent from my Huawei Mate 10 using XDA Labs
dan_729 said:
Last week my phone had some crazy bugs (if I tried to activate Wifi the settings app freezes *wtf*) so I decided to wipe everything and install LOS, its working well, the only problem is that my PC can't detect my phone anymore even if I manually set MTP Protocol at developer options. You can still transfer files via OTG and PC does detect while using twrp recovery. Another complain its that this OS doesn't feature the off-screen navigation option that I use normally :crying::crying:
Those little problems could be fixed by the time you read this tough, as the dev is currently releasing new builds almost everyday (updates need to be installed via TWRP, searching from Settings doesn't work as it is not official)
Here's how:
1. Unlock bootloader
2. Install TWRP from here (Don't use this one, it won't allow you to instal LOS, it will say your device is incompatible.)
3. Wipe everything and format with twrp
4. Download LOS/Gapps from this tread (don't worry as it says it is for the Honor View 10, it will work for the normal Mate 10) and optionally download Magisk for root (root addon from Lineage doesn't work). Right after installing LOS, make sure to install gapps and Magisk before booting into system, otherwise your phone will explode and you die.
Important: The recovery you just downloaded won't work with this OS, so if you need twrp again, flash this. Touch doesn't work with this recovery, so you need to use a mouse via OTG.
Click to expand...
Click to collapse
Does the OTG usb mouse really work on the blanc recovery? i can´t make it work at all.
bihariel said:
Does the OTG usb mouse really work on the blanc recovery? i can´t make it work at all.
Click to expand...
Click to collapse
It works for me, so.. what comes to my mind is that probably its your mouse problem, but considering that it works in your pc.. welp. I dunno really why it doesn't work for ya
dan_729 said:
It works for me, so.. what comes to my mind is that probably its your mouse problem, but considering that it works in your pc.. welp. I dunno really why it doesn't work for ya
Click to expand...
Click to collapse
Oh sorry, yes it works, the otg adapter was the problem, i used another adapter and it works.
Thank you.
Now I will try to install the latest builds of that rom with twrp as the dev doesn´t release system.img GSI format anymore.
BTW, any google camera port that works well on this ROM or any other alternative?
OK, lineage OS successfully installed latest build (2018-05-17).
I had to modify the updater script and installed using Destroy recovery with the help of a mouse via OTG.
Now let´s see how good and stable is this ROM.
Related
I installed LineageOS successfully. But I wanted to try Omnirom too. I made a full wipe in TWRP and then followed the OpenKirin Guide again. But after reboot i couldnt access the EMUI Factory Reset Screen (see Image of Point 14 in the guide). But the phone wont turn off anymore. It just restarts. I can still access Bootloader (Phone and FPR unlocked) when the phone is connected via usb and the TWRP screen with all options (install, wipe, ...). I tried to install LineageOS again but failed.
Reflash EMUI (you need to remember which version you were on). Then try LINEAGEOS or whatever ROM you want
PalakMi said:
Reflash EMUI (you need to remember which version you were on). Then try LINEAGEOS or whatever ROM you want
Click to expand...
Click to collapse
I read a lot of posts here and finally I used HurUpdater. Worked well!
Do you know which of the custom roms comes without any google apps for h9l?
Apfelwurst said:
I read a lot of posts here and finally I used HurUpdater. Worked well!
Do you know which of the custom roms comes without any google apps for h9l?
Click to expand...
Click to collapse
From what I know, none
We already know this phone is arm64,
the GSI rom AOSP v112 has support for this phone.
But how is the rom behave? What works and doesn't?
How are other GSI flavours doing? Like RR, AEX, HAVOC,....
[NOTE: For those who are interested i'll change this post to some GSI guide cepheus,
as soon as i recieve my Mi 9. But until then i'll hope for some of your feedback]
See this: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
and these two: https://forum.xda-developers.com/showpost.php?p=79284072&postcount=46, https://forum.xda-developers.com/showpost.php?p=79295919&postcount=53
It shoudn't be needed to write a guide
a video guide would be interesting
I usually used twrp to flash the Gsi file but now I didn't understand what steps should be taken
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
update: since Phh was ultra vanilla with literally 2 extra settings, tried RR, same greeting, no fp, and no swipe to apps there, i don't really beg for their modifications as i have Xposed Edge for this. Finally went back to Floko knowing how to fix gapps problem, it's got best navbar solution, although with tons of bugs (contradicting navbar user actions, non responsive gestures, nonresponsive buttons), no tap2wake, AOD sucks, fp sucks too, produces blinking screen.
Looks like trebles are unusable, time to go back to XIAOMI EU... so much for "don't need device specific ROMs".
doggydog2 said:
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
Click to expand...
Click to collapse
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
dear mod please close this one, there seems to be already a conversation about this
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
tried to do that, tried to install arm64 Gapps, I'd get an error saying my system is arm, so i install arm gapps, they do get "installed", but when i reboot, there is no gapps at all.
edit: arm64 gapps worked when used LR.Team/wzsx150 twrp.
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
doggydog2 said:
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
Click to expand...
Click to collapse
You can find fastboot image here:
https://en.miui.com/a-234.html
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
thanks but both links redirect me to http://www.miui.com/ in chinese where i can browse to quasi-full roms again. strange.
btw i'm a fan of your kernel except it causes "can't connect to camera".. after many combinations of flashing i tried skipping the kernel (v01, or v02 or any kernel), and camera is back. however without Night mode this time...
update: found stable ROM at least https://c.mi.com/thread-1907373-1-0.html
update: somehow i trust this is the legit link to develop ROM http://bigota.d.miui.com/9.3.1/ceph....1_20190301.0000.00_9.0_global_cdb3885bac.tgz
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
Hey,
Could you make your magisk patch to not require pressing FP scanner twice for FP to register?
Without the patch, works fine from first try, but with it, two presses at least are needed Everytime.
Thank you!
What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020
temp
Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English
Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.
so everything good other than Android Auto? Well done!
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.
How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:
..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?
Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.
Great, glad all went good for you
Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse
Great work! ROM works great, even Google pay is working good!
I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel
Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!
oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse
Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.
We can root in an easy way without unlocking the bootloader
I think this method works with all versions realme
Don't forget to activate OEM unlocking From Developer options
1-You must install drivers:
Realme USB Driver - Realme Firmware
From here you can download USB driver for realme mobile phones. The given USB driver is supported only for the Windows operating system
realmefirmware.com
Realme USB Driver - Google Drive
drive.google.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download SPD Flash Tool R26.21.2801 - Official SPD/Unisoc Flash Tool
Download SPD Flash Tool R26.21.2801 to Flash Stock Firmware on Spreadtrum Smartphone and Tablets.
spdflashtool.com
2-You have to unpack the ROM using SPD_Upgrade_Tool
https://www.gsmmafia.com/ Here are the ROMs
After completing the extraction, make a patch for the boot With Magisk-v24.3
You will get a rooted boot file Replace it with the old boot
In the end, flash the device and you will notice that you have the root
I am attaching an explanatory video
not the group you looking for but thanks for sharing this
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
thanks.
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
How can we create realme c25y group in xda
Excuse me I want to ask, will this delete all internal data?
Doly12 said:
Excuse me I want to ask, will this delete all internal data?
Click to expand...
Click to collapse
yes.
Yo, how did you flash it?
Biglet0w said:
Yo, how did you flash it?
Click to expand...
Click to collapse
spd flash tool
turn off the phone. After that, press and hold the Volume Down button and at the same time connect the phone to the PC using the USB cable. You will see that the Upgrade Download program was able to identify the phone and the flashing process will start automatically.
Hi
When I try to call the emergency numbers, I can't, it says that the credit is not enough to make the call
I rebooted and flashed according to the video you posted, but it didn't work
I changed the chip but the same problem remains
Can you give me a solution to this problem
my phone recognize sim but when call people it said cellular is not available, when i use my sim in other phone it work normal, i try flash the rom again but spd tool said error !!!GSM Cali in phone is not calibrated.Reserved[7]:0x00000000,[ID=0x2] pls help
i have rmx3269_11_A.18 and its not on gsmmafia this build number what i do please help
Can i install twrp from c25 or c25s
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Reyproject said:
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Click to expand...
Click to collapse
1) I don't think so.
2)Yes.
JA sunny said:
1) I don't think so.
2)Yes.
Click to expand...
Click to collapse
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
I think you need to have the bootloader unlocked to boot into custom img
elokuba said:
Can i install twrp from c25 or c25s
Click to expand...
Click to collapse
Don't
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
Can you please check if this works
File
XDA forum
JA sunny said:
Can you please check if this works
File
XDA forum
Click to expand...
Click to collapse
What does it do?
Reyproject said:
What does it do?
Click to expand...
Click to collapse
removes the black bar on the notch/punchhole side that you see on some apps and games when the phone is in landscape. I'll root my phone if this works.
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Leonvrx said:
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Click to expand...
Click to collapse
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Laptapper said:
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Click to expand...
Click to collapse
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Wipe isn't enough, formating with yes is necessary.
Try exactly my procedure (fw isn't necessary for all roms / cherishos don't need, Los need)
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Sheist! said:
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
Click to expand...
Click to collapse
Also elite rom need format data if encrypted (normally data is encrypted!)
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Sheist! said:
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Click to expand...
Click to collapse
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Laptapper said:
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Click to expand...
Click to collapse
I didn't know that; thank you for your help, guidance, and patience.
Tried your steps exactly this morning, so far so good, I'll update in the next days, for better or for worse.
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Leonvrx said:
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Click to expand...
Click to collapse
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Laptapper said:
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Click to expand...
Click to collapse
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Leonvrx said:
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Click to expand...
Click to collapse
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Laptapper said:
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Click to expand...
Click to collapse
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Leonvrx said:
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Click to expand...
Click to collapse
Playstore certified?
Rooted?
Cts matching?
Laptapper said:
Playstore certified?
Rooted?
Cts matching?
Click to expand...
Click to collapse
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Leonvrx said:
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Click to expand...
Click to collapse
Try kernelsu root
Then delete caches of playstore and Google play services.
Reboot
I've got non problems with banking and camera in cherish and kernelsu