Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Removed a ton of tracers
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Voice Changer
Chinese Alpha Launcher
High-end icon animations
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
Mirror app doesn't work.
You tell me.
FIXES:
Reverted the MiuiAod for more stability
Added the Backup app back
Added the Mi Sound app back.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: https://t.me/LiteEDevelopmentGroup
Channel: https://t.me/LiteEDevelopmentChannel
Changelog:
- 1.3:
Working Mi Dialer with call recorder
New charging animation
Deodexed
Fixed flasher issue
I forgot
- 1.2.5:
Changelog in telegram
- 1.2:
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Chinese Alpha Launcher
High-end icon animations
- 1.1:
Never published on XDA
Added the vbmeta patcher in flasher script (this fixes that cannot boot into userspace error)
Changed boot sound and boot animation from Redmi Note 9T
MIUI Launcher Mod by Sipollo (removed)
High-end icon animations
Chinese version of Search (removed)
App Vault from MIUI 13 (removed)
Uses the chinese version of Mi Calendar (removed)
- 1.0:
Initial release
Wow nice., Hoping for more upcoming custom rom for our handset. Thanks
J6idot said:
Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
Removed a ton of tracers
More colorful bootanimation
Uses the chinese variant of File Explorer, Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Custom MiuiAod with "always on" function
Voice Changer
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
I have no idea how to test the Voice Changer function. Could anyone try this?
You tell me.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: not yet
Channel: https://t.me/LiteEDevelopmentChannel
Click to expand...
Click to collapse
big big work
Wow, Great work. Thanks. But is genome karnel stable?
Awesome work, might try it later
IamAlaminislam said:
Wow, Great work. Thanks. But is genome karnel stable?
Click to expand...
Click to collapse
yep
I can't seem to find the telegram channel for the genome karnel. Want to know the change log..
Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.
GildroY said:
Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.
Click to expand...
Click to collapse
why not? rom works perfectly fine
J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Thanks. Will try it out tonight
J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?
GildroY said:
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?
Click to expand...
Click to collapse
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Will try again tonight post work. Many thanks.
J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Worked like a charm!!
Thanks a ton.
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer
J6idot said:
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer
Click to expand...
Click to collapse
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)
angel495 said:
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)
Click to expand...
Click to collapse
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
Can you get advise about make a change for in system and vendor folder (its write protect)... I am try edit a build.prop file, but then i save changes file just gone and i need make a reflash.
angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
For call recording you can use axet's call recorder. It's available on fdroid and is working fine so far, for me, with this rom.
Related
4ndr01d presents a Stock ROM!
Donations Appreciated!
Click here to donate via PayPal if you like my work and want to support further versions of my ROMs.
Features
Rooted
Init.d Support
Script to easily Calibrate Overscan
Improved Performance for Games
Improved Streaming (Video and Audio)
Improved Connection to Google Services
Buttery Smooth
Blazing Fast
Changelog
1.0 (md5: 8c4acc39406a3f3b2d3ec0b74dc33a4c)
initial release
Download
Mod edit: Links removed
Instructions
1. extract zip file on your desktop
2. run installer script and follow instructions
Credits
Google - for Android!
You guys - for all your support and feedback!
reserved
Cool will check it out soon
No go - wont flash the system.img gives the following error:
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.218s]
sending sparse 'system' (497013 KB)...
OKAY [ 17.226s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 17.679s
Click to expand...
Click to collapse
alltubetone said:
No go - wont flash the system.img gives the following error:
Click to expand...
Click to collapse
You are unlocked, right?
Also, if you have issues with the installer, you can just fastboot flash both system.IMG and boot.IMG.
okibi said:
Also, if you have issues with the installer, you can just fastboot flash both system.IMG and boot.IMG.
Click to expand...
Click to collapse
good luck man, paying attention. seems like i had a lot more setup on my nexus player so staying on 5.0 for now.
Yes im unlocked - I also tried to manually fastboot flash the system image but no luck. same error message.
---------- Post added at 10:05 AM ---------- Previous post was at 09:57 AM ----------
Looks like people in the Q&A thread are having the same issues
The ops lack of response is rather concerning.
lafester said:
The ops lack of response is rather concerning.
Click to expand...
Click to collapse
Being at work is concerning? Ok...
Are you guys already on 5.1? If not, you need to flash the 5.1 bootloader. I'll look to improving the process tonight.
Also, are you guys using the fastboot in the zip? Perhaps I bundled the wrong one!
Nothing wrong with fastboot and yes I am on 5.1 bootloader.
lafester said:
Nothing wrong with fastboot and yes I am on 5.1 bootloader.
Click to expand...
Click to collapse
Which fastboot are you using? The one in the package or your sdk version?
Tried yours first, then mine with the same result.
First off, yay for more devs and a new rom for the Nexus Player!
2nd, screenshots or more details would be very helpful. Is casting working? Are bluetooth game pads, Bluetooth keyboards and mice, and most importantly Bluetooth audio devices working? I really want to use Bluetooth headphones!
Is anything currently not working?
Does this rom require a keyboard/mouse to setup initially?
What differentiates you from LolliRock?
I pushed up an R2 build to the primary download link. Can you guys please test this one?
With "stock" do you mean the real Android TV stock image or stock AOSP with a tablet interface which needs a mouse / keyboard combination?
MaluNoPeleke said:
With "stock" do you mean the real Android TV stock image or stock AOSP with a tablet interface which needs a mouse / keyboard combination?
Click to expand...
Click to collapse
Stock means based on the stock Android TV image.
I cannot it install the r2 version because it fails to write the system:
sending sparse 'system' (523231 KB)...
OKAY [ 22.614s]
writing 'system'...
FAILED (remote: flash_cmds error!
The same command works with the Google System Image without a problem
Must be something wrong with the system.img. I'll take a look at it today and get this resolved. Sorry!
Thanks in advance and what exactly have you improved in performance, streaming and connectivity in comparison to the stock image?
DisclaimerThis software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_clt_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working (if it pin/password, pattern fails then try by removing them (password, pin, pattern, fingerprint) from Android before booting to TWRP.
MTP and OTG connection = working
Backup&Restore = working
Note: This was tested only by few P20 Pro owners,so if you test it,please report back!There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_clt_0.1.img - Decryption support (you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk not available for backup./vendor not available for backup (use /vendor_image instead)
Glad to see this. Any chance of sources or a pull request on my device tree to get decryption working?
hum.. it seem that decryption working great.
See :
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
a1Pha said:
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
Click to expand...
Click to collapse
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Pretoriano80 said:
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Click to expand...
Click to collapse
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
a1Pha said:
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
Click to expand...
Click to collapse
Yes, no problem! Also have a look at my Github (pretoriano80). My goal is also to make a fully open source version. ?
Quote: Note: This was tested only by few P20 Pro owners,so if you test it,please report back!
Hi Pretoriano80, Hi All,
Great job ! Just installed... I confirm that it works on my CLT-L29 8.1.0.106(C432)
Internal storage decryption, MTP and usb OTG connection, Backup& Restore (incl /vendor_image) : All working !
Many thanks & Cheers
CLT-L09 (C782) all is working as it should, successful backup and mount of my 1tb hard drive.
Absolutely fantastic work
Thanks :good:
Well this is very positive.
Less than 2 calendar weeks from release to TWRP release.
I think we can possibly have pretty high expectations for development on the P20 Pro.
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
andrewglass3 said:
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
Click to expand...
Click to collapse
You have to unlock bootloader first!
Pretoriano80 said:
You have to unlock bootloader first!
Click to expand...
Click to collapse
Yep - I forgot that step - had the code but missed it out lol - Im an idiot lol
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
Have you made sure that the Google Pay app is selected in the Magisk Hide list in the app? It doesn't tick automatically like it used to with Android Pay. You should pass safetynet with Magisk installed. Also, after flashing TWRP still passes safetynet too.
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
TWRP has nothing to do with SafetyNet! Maybe you installed a firmware which didn't passed Google check yet.
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
m00h said:
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
Click to expand...
Click to collapse
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
DJBhardwaj said:
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
Click to expand...
Click to collapse
I did on the other TWRP thread, worked fine.
The page for getting an unlock code seems to 404 for me. Is this happening for anyone else too?
Update for new year.
1-1-2020 Uploaded a version of twrp for Bold-N1 with working touchscreen.
thanks to the help of @vineethrp in This Post
Original thread hidden, since twrp build is fixed.
This initial version of TWRP, still has major issue. A second issue with the recovery is the screen will not turn on for about 30 seconds after boot. A time that lines up with the screen sleep timer. The touchscreen is not working. This has been a kernel issue on other devices that I am aware of.
The kernel source for th BOLD-N1 is released, and I have been reading through it. To no avail. I can't find the section that is checking for recovery mode.
For the time being, I have confirmed this version is working with the adb command line operations.
Partial list of functions found Here https://twrp.me/faq/openrecoveryscript.html
I have used the "install" and "sideload" operations.
In most cases (mods etc) sideload should be ok to try.
For the mod I was interested in (DM-Verity-No-Forceencrypt). The install does not support being done in sideload.
Because in the install script used, it checks the zip file name. Based on the file name it enables/disables options of the script.
Sideload changes the *.zip name, so more steps were necessary.
In the following steps, the device /data partition will be formatted. This will erase all your stored data, and more importantly,
it will remove the encryption.
The following steps require you to have already unlocked bootloader.
And,
As a reminder, whenever you modify your phone, you should NEVER relock the bootloader
INSTALL the attached TWRP img. Use Fastboot to install it.
Code:
fastboot flash recovery **insert-file-path-&name-here**
fastboot oem reboot-recovery
STEPS USED TO FLASH Disable_Dm-Verity_ForceEncrypt
Download zip file from developers XDA page HERE
Code:
adb shell twrp wipe data
adb shell reboot recovery
adb push Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
adb shell twrp install /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
STEPS USED TO SIDELOAD MAGISK
Download from Developers GitHub repo HERE
I had trouble with the newest V20. Stay on tested version V19.2, unless you can troubleshoot problems on your own.
Code:
adb shell twrp sideload
adb sideload C:\Users\(your user name HERE)\Downloads\Magisk-v19.2.zip
Device tree used
https://github.com/mrmazakblu/Bold-N1_minimum_device
Kernel source
https://github.com/mrmazakblu/Bold-N1-Kernel.git
Released twrp folder on android file host HERE
Stock recovery image HERE
.
Call for help
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?
greeneyez15o said:
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?
Click to expand...
Click to collapse
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed
mrmazak said:
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed
Click to expand...
Click to collapse
Not sure, but now Im bootlooping to twrp :/
greeneyez15o said:
Not sure, but now Im bootlooping to twrp :/
Click to expand...
Click to collapse
do you know if your phone had received the ota update. there was an update made on
Wednesday, 16-Oct-19 03:27:28 UTC not sure when it was released, though.
it is possible, but unconfirmed that this update may have made this bootloop happen. because others have said that the update made them loose there root. Unknown about the unlock status
I am still trying to fix this twrp, as it is still only one I have seen.
I also have a different phone(umidigi F1) with same soc, mt6771.
A Dev made twrp for that device that even works decrypt. @PeterCxy.
I have forked his build tree. And am trying to copy his success. Unfortunately even though devices have same soc, the encryption method is different enough that the files used to make decrypt work on F1 are not present on N1.
A made a full firmware dump of the N1 at
https://github.com/mrmazakblu/blu_n0030ww_dump
working on porting , then building old Carliv touch recovery. since it can be used with the volume rocker as well as touch.
So far i have it ooting and adb works. Of course with device encrypted , the internal storage is not accessed. but once i get the fsab and vold correctly mapped, it will be ok.
am not posting the port till sdcard is fixed, and can be built from source.
sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available
dxpeboiiii said:
sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available
Click to expand...
Click to collapse
Well it's up to you. In this thread I have detailed how I used ADB with twrp to flash first decrypt install package, then magisk. Or you can patch boot.img with magisk manager then flash back to phone with fastboot or sp-flash tool.
Or if you are going to use gsi AOSP, you don't need any of these options.
Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways
dxpeboiiii said:
Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways
Click to expand...
Click to collapse
Did you try either of the 2 ways I explained how to use adb to install zips?
1- adb sideload
2- adb twrp install. Xzxsome-zip-name
But I thought viper4android has not worked on devices higher than marshmallow
I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips
dxpeboiiii said:
I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips
Click to expand...
Click to collapse
That's good, lets us know how the otg mouse works out. I did not have one to try it.
I got viper4android workin .. i downloaded a module called "Magisk SELInux permissive Script" this basically gave me the option to be permissive thats need for viper to work. And busybox but im pretty sure thats already installed from magisk but if not just install busybox. Should be good to go for audio mods?? bout to try dolby now.. let you kno how it goes
Basically i have the device unencrypted and under magisk settings you wanna uncheck "magisk hide" you will fail safety thing but me personally idc. But anyway follow the above comment along with wat i just said you should have no issues installin viper and dolby. I also recommend a otg for custom recovery. Just easier in my opinion. I basically got device setup how i want and backed it up thru twrp. But any question feel free to ask. More then welcome to help anybody .
deleted.
dml0211 said:
deleted.
Click to expand...
Click to collapse
I think you posted in wrong stop. I see you deleted before I got reply. Oh well.
But if you need to know which type of gsi to use on your device. The best bet is to use this app, from play store.
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.
vineethrp said:
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.
Click to expand...
Click to collapse
Thank you. I added the firmware to the recovery ramdisk and repacked. Just like you said. Now I have touch working. THis may have re-sparked my interest. I have more to work with now. Thanks.
Perhaps twrp is not properly mounting the /vendor and this is why we need to add that bin file to recovery/root. May also be same issue making the screen on time lag. Either way this seems like a big step forward.
I am working on adding the goodix firmware to the device tree I am building with, so will not need to do repacking. I have added the test build with working touch to the file host folder linked in OP
Here I bring to you the official Havoc-os ROM for ARM64 A/B devices and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
You can follow his work in the next post: https://forum.xda-developers.com/redmi-note-5-pro/development/rom-havoc-os-v3-0-t3996569
Telegram Support Group: https://t.me/havocofficial
Telegram Announcements Channel: https://t.me/Havoc_OS
What is working:
Everything works perfectly
Bugs
Automatic brightness is not working, (brightness must be adjusted manual for now)
Update to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 and reboot ..... problem solved
the necessary files are at the end of the tutorial
Remember I am not a developer if you are presenting any bugs let us know and you can contact the Havoc team at the links described above
Steps
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32 global version, the version that i tested Havoc-OS-v3.5-20200522-Official-arm64-ab.img.xz
First make a backup of all the necessary information in case something goes wrong you can easily recover,Charge the battery at least 80%
All your data will be deleted during the process
the necessary files are at the end of the tutorial
1) Unlock the Bootloader if you have not already done it or do not know how to, follow this post:http://en.miui.com/unlock/
2) Install a custon recovery and flash vbmeta.img together
Note: TWRP is recommended for this process but you should be aware that depending on your type of screen there may be problems (TWRP work fine on Tianma display), so you can also use Orange fox,
Note2: it is recommended not to use Hyper Shell for the installation of vbmeta.img it can cause problems, cmd can be used in the root folder plattform tools
Note3: If you already have the recovery installed and you are only going to flash vbmeta.img it is recommended to redo the full TWRP installation process together at vbmeta.img, restart in the recovery you can see that the encryption of the data is no longer available if you had it, and then boot in the ROM (in my particular case I did not do it first time and then could not put the files necessary for the installation in the internal memory)
Note4: use only This conmand to flash vbmeta.img " fastboot flash vbmeta vbmeta.img" if you disable the secure boot loader with the Disable_Dm-Verity command then when starting in the ROM you will not be able to configure any lock or passsword for your devices.
3)Format data, if it doesn't format the data you will have bootloop
4)Make wipe only to cache, dalvik, system, data
5) Copy all the files to the phone (Havoc-OS-v3.5-20200522-Official-arm64-ab.img you can find it by unpacking the zip, permisiverv5, magisk,Certification Patch.zip, opengapp recommended nano or pico)
6) Install system image to system partition.
7) Install permissiver V5
8) Resize system partition to flash opengapps.
9) Flash Opengapps
10) Flash Certification Patch
11) Reboot
12) Install Magisk (optional if you want rooted your ROM)
the boot process takes 5 to 10 minutes the first boot in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
How upgrade (Same Android Version)
1 Make a Wipe on Dalvik and cache only.
2 install the 3.x version system image on the system partition
3 Install permissiver V5
4 Resize system partition to flash opengapps.
5 Flash Opengapps ( if you dont flash the gapps you will have a fc on google apps )
6 Flash Certification Patch
7 Reboot
Download link Rom image: https://sourceforge.net/projects/havoc-os/files/arm64-ab/
Download lik Magisk : https://******************/
I hope the guide is helpful and enjoy it
Thread came in just in time... Thanks! It's time to get to work
I tried installing HavocOS GSI before and it didn't boot. No wonder because there's a lot more to the steps. I'm gonna try this later. Thanks.
does fingerprint sensor work?
Volte calls on jio do not work but internet works
satrio_adjie said:
does fingerprint sensor work?
Click to expand...
Click to collapse
Yes, as long as you don't use this command " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable the secure boot verifier when you install vbmeta.img
pokepokepoke said:
Volte calls on jio do not work but internet works
Click to expand...
Click to collapse
the possibility of using VoLTE depends on the following factors:
Your location, the account you have with your operator and the model of your Phone
The operator, operator account, location, and phone model of the person you are calling
Some operators support VoLTE only in certain cities or in certain area codes. Contact your operator for information about your area and your account.
You can verify the VoLTE activation according to your operator using in dialer * # * # 4636 # * # * go to devices information
Darth Inferno said:
Yes, as long as you don't use this command " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable the secure boot verifier when you install vbmeta.img
Click to expand...
Click to collapse
works perfectly! thank you! it even has face unlock! :good:
How to fix no mobile data? There's an x on the signal bars.
volte not working on any gsi
volte works fine on stock rom but not on gsi. this is the only missing feature and reason why many avoid gsi's. I dont understand why can there be a fix for volte. some operators are truly 4g and support only volte like jio in india. any way to fix this?
thanks
P.s : I have not tested this rom but I know it wont work cause its another GSI.
Darth Inferno said:
the possibility of using VoLTE depends on the following factors:
Your location, the account you have with your operator and the model of your Phone
The operator, operator account, location, and phone model of the person you are calling
Some operators support VoLTE only in certain cities or in certain area codes. Contact your operator for information about your area and your account.
You can verify the VoLTE activation according to your operator using in dialer * # * # 4636 # * # * go to devices information
Click to expand...
Click to collapse
Hello !
Any one can test this rom and get feedback pls ?
Thank you for the noob proof guide there. Haha i'll try this next time if i'm bored with miui :victory:
fabien976 said:
Hello !
Any one can test this rom and get feedback pls ?
Click to expand...
Click to collapse
Friend The Rom, goes fine,everything work perfect even face unlock, I get this like daily driver and not facing problem at all
desertfoxtim said:
How to fix no mobile data? There's an x on the signal bars.
Click to expand...
Click to collapse
Hi, Friend, in my screenshot the x appears in the signal bar due to a coverage problem of the service provider in the area where I am, if you wish, as soon as I am in an area where I have coverage, I can send you the screenshot with both Sim active, the rom does not present any problem
Hi, great guide i'm just wondering how do I resize system partition? Thx
Rayane Kch said:
Hi, great guide i'm just wondering how do I resize system partition? Thx
Click to expand...
Click to collapse
If you´are using TWRP you need go to wipe-advanced wipe, then select the system partition push on repair or change File system and you´ll see the button resize file system click on it... thats is all
I noticed that there are video bugs like other aosp custom rom but already fixed it by adding this code on build.prop
add to /system/system/product/build.prop
Code:
debug.stagefright.ccodec=0
coolboyforeva said:
volte works fine on stock rom but not on gsi. this is the only missing feature and reason why many avoid gsi's. I dont understand why can there be a fix for volte. some operators are truly 4g and support only volte like jio in india. any way to fix this?
thanks
P.s : I have not tested this rom but I know it wont work cause its another GSI.
Click to expand...
Click to collapse
I had the same result trying many Gsi's and aosp roms jio only works on stock and miui eu or miuimix
Darth Inferno said:
Here I bring to you the official Havoc-os ROM for ARM64 A/B devices and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
You can follow his work in the next post: https://forum.xda-developers.com/redmi-note-5-pro/development/rom-havoc-os-v3-0-t3996569
Telegram Support Group: https://t.me/havocofficial
Telegram Announcements Channel: https://t.me/Havoc_OS
What is working:
Everything works perfectly
Bugs
Automatic brightness is not working, (brightness must be adjusted manual for now)
Update to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 and reboot ..... problem solved
the necessary files are at the end of the tutorial
Remember I am not a developer if you are presenting any bugs let us know and you can contact the Havoc team at the links described above
Steps
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32 global version, the version that i tested Havoc-OS-v3.5-20200522-Official-arm64-ab.img.xz
First make a backup of all the necessary information in case something goes wrong you can easily recover,Charge the battery at least 80%
All your data will be deleted during the process
the necessary files are at the end of the tutorial
1) Unlock the Bootloader if you have not already done it or do not know how to, follow this post:http://en.miui.com/unlock/
2) Install a custon recovery and flash vbmeta.img together
Note: TWRP is recommended for this process but you should be aware that depending on your type of screen there may be problems (TWRP work fine on Tianma display), so you can also use Orange fox,
Note2: it is recommended not to use Hyper Shell for the installation of vbmeta.img it can cause problems, cmd can be used in the root folder plattform tools
Note3: If you already have the recovery installed and you are only going to flash vbmeta.img it is recommended to redo the full TWRP installation process together at vbmeta.img, restart in the recovery you can see that the encryption of the data is no longer available if you had it, and then boot in the ROM (in my particular case I did not do it first time and then could not put the files necessary for the installation in the internal memory)
Note4: use only This conmand to flash vbmeta.img " fastboot flash vbmeta vbmeta.img" if you disable the secure boot loader with the Disable_Dm-Verity command then when starting in the ROM you will not be able to configure any lock or passsword for your devices.
3)Format data, if it doesn't format the data you will have bootloop
4)Make wipe only to cache, dalvik, system, data
5) Copy all the files to the phone (Havoc-OS-v3.5-20200522-Official-arm64-ab.img you can find it by unpacking the zip, permisiverv5, magisk,Certification Patch.zip, opengapp recommended nano or pico)
6) Install system image to system partition.
7) Install permissiver V5
8) Resize system partition to flash opengapps.
9) Flash Opengapps
10) Flash Certification Patch
11) Reboot
12) Install Magisk (optional if you want rooted your ROM)
the boot process takes 5 to 10 minutes the first boot in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
Download link Rom image: https://sourceforge.net/projects/havoc-os/files/arm64-ab/
Download lik Magisk : https://******************/
I hope the guide is helpful and enjoy it
Click to expand...
Click to collapse
Right now, I'm using This rom.
It's very much customizable , but have some few bugs, and some things should added with it!
Fristly, Internet Speed meter showing speed when i've speed over 100 kbps
Secondly, I don’t find any ringtone changer in this rom ( very much disappointed right now for this problem)
Thirdl, When I was playing PUBG Mobile, sometimes display isn’t rotating
Fourthly , I can't find gaming performance better than MIUI ( It hurted me coz I listened that HavocOs is gaming os and I'm not getting better performance while gaming)
And The big problem is, I can't use any magisk module like Viper4andriod Fx and other.
Except those, I liked this rom?
I think that in future, this problems will no remain??
Thank you
( My English is bad)
I installed it and it works fluently! But there are some issues that needs to be fixed ASAP!
1) The contact app doesn't show contacts saved in SIM card..it only shows contacts which are saved in the device or in gmail.
2) The video recording doesn't work accurately. When I finish recording a video and watch it, it doesn't save the recording accurately. Example- if i record for 30 seconds, the video will be saved as 1 minute video and the first 30 seconds of the video will be a freeze frame.
3) The ambient display (always on display) doesn't work.
4) Fingerprint is slower than stock MIUI and sometime needs to touch twice to unlock the phone.
Please fix these issues as these are some important features.. Besides, everything works just fine!
Hi all:
Here is a LineageOS 19.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-11
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
New: Camera fully working! (with the restriction to 8 MP)
Enforced SELinux support
Fingerprint (sometimes crashes)
FM-Radio (maybe it needs a few restarts before it's working)
GApps
German App AusweisApp2
GPS
Headset
LiveDisplay
Location services
Network Traffic Monitoring
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
Which GApps would you suggest?
I've tested NikGApps, but they are not working stable. Other GApps aren't available for Android 12 as far as I know. So, I suggest none.
Update: NikGApps works after its self-updated service bibliothek and a manual restart of the device flawlessly.
It's a little bit choppy, but I can live with that.
I've set the state of the development to BETA due to quite good overall performance.
After installing this TWRP was changed to the one from Lineage. It no longer picks up my mounts. Must I use ADB to recover from this? How do I revert to TWRP? I can no longer use fastboot.
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Berni-0815 said:
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Click to expand...
Click to collapse
Thanks. I got fastboot working and installed TWRP again. How did the Lineage loader install though? I did not see any prompts for it.
I performed a cache/dalvik/system and data wipe and installed the latest 19.1 release but it never boots up past the swirling animation. It does not reboot either. I added a zip containing pmsg-ramoops-0
I'll take a look into it asap. Please be patient.
I can't find any reason for the crash; I'm sorry.
New version out; see 1st post.
New values for vibration strengths set.
Fixed Fingerprint location hint animation while enrolling.
Screen density reduced because all of the UI elements of Android 12L (Lineage 19.1) are too large for our little screen.
New version out; see 1st post.
Updated from android-12.1.0_r1 to android-12.1.0_r2
Berni-0815 said:
I'll take a look into it asap. Please be patient.
Click to expand...
Click to collapse
Thanks for looking. I flashed with the currently build and my device is working again.
New version out; see 1st post.
Updated from android-12.1.0_r2 to android-12.1.0_r4
Android security patch level: 5 April 2022
Hey friends,
New z5c, had sony stock on it.
I installed TWRP latest using adb/fastboot on ubuntu 20.04
All good
I flashed Lineage 19
On reboot I just get a boot loop, going between Sony logo and swirly android animation
adb recgnises the device but says "offline"
No commands work
I have tried every button combo I could find suggested everywhere, including above
But the phone will not boot into TWRP
Any suggestions, please?
kaivalyam said:
z5c, had sony stock on it
Click to expand...
Click to collapse
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
kaivalyam said:
I installed TWRP latest using adb/fastboot on ubuntu 20.04
Click to expand...
Click to collapse
How have you flashed TWRP?
Berni-0815 said:
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
Click to expand...
Click to collapse
Ok, that's probably why it wont boot then, I didnt know that, and didnt check
Berni-0815 said:
How have you flashed TWRP
Click to expand...
Click to collapse
Downloaded latest and used fastboot
fastboot flash recovery twrp.img
If I can just get TWRP to load, I can flash a different ROM and all will be good ..
Ok. Which version of TWRP have you flashed? My own?
You can flash the latest stock ROM with the flashtool. If you're installing this tool at windows, you can use the integrated XPeriFirm tool to download the latest stock ROM.
Or you install this XPeriFirm version.
If you're not in a hurry: In a few minutes my upload of my latest LineageOS 19.1 boot and system image will be completed.