Develop Bugs

[ROM][UNOFFICIAL][4.4.4] CyanogenMod 11 + crDroid for Xiaomi MiPad

CyanogenMod 11 with crDroid additions for Xiaomi MiPad
!! IMPORTANT !!
xep.8800.org will be temporarely down from 29.03.15 for couple of weeks so it would be great if somebody do mirror of latest buld and post link here. Thx!
About:
Source built CM except proprietary blobs and binary kernel from stock MIUI rom.
This is not a port from another binary rom.
Click to expand...
Click to collapse
What's working:
It seems everything working for now..
Click to expand...
Click to collapse
Not working/Bugs:
"Wi-Fi region code" setting is broken. Do not touch it or it will break your wi-fi.
you tell me.. testing in progess..
Click to expand...
Click to collapse
Instructions:
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
Multirom Instructions:
1. Install TWRP Multirom Recovery
2. Reboot into TWRP and install multirom-20150205-v30-UNOFFICIAL-mocha.zip
3. Click "Advanced->Multirom" and flash your desired second rom.
4. Return to the installed roms listing, click fresh installed rom and click "Remove boot.img" (Due to closed kernel sources kexec-hardboot is not implemented so we need to remove boot.img)
5. Reboot. Select your desired rom from multirom menu
Click to expand...
Click to collapse
Downloads:
cm-11-20150327-UNOFFICIAL-mocha.zip
CWM
Multirom:
TWRP_multirom-v2.8.4-mocha.zip
multirom-20150205-v30-UNOFFICIAL-mocha.zip
I don't know if it is actually compiled with TEGRA optimizations but have created CWM flashable zip with stock bionic libraries. You can flash it on top of CM installation:
tegra_bionic.zip
Changelog:
15.02.15
* apply qcom bionic optimization
* build.prop dalvik etc tweaks
02.02.15
* Reboot to recovery fixed
* Recents view proportion fixed
26.01.15
* Synced with CM repo
* have enabled Display mirroring (miracast) though it does not work with my EZ dongle, sound is ok but screen is black. May be it'll work with another dongles...
21.01.15
* Update to the latest kernel from stock MIUI
20.01.15
* Sleep issue fixed
* Adopt nvcplsvc for CM & implement Performance Profile selection
18.01.15
* Synced up with CM repo.
* Added USB Mass Storage mode for external sd. Though it does not work along with ADB Debug enabled, need to be switched off when using UMS mode.
17.01.15
* Switch to CM's audio_effects and make Dirac plugin work. Equalizer crash fixed.
Click to expand...
Click to collapse
Links:
http://github.com/cyanogenmod
http://github.com/cristianomatos
https://github.com/faust93
Click to expand...
Click to collapse
I take no responsibility for what this may or may not do to your device.
Do not forget to click Donate button! It makes me work harder!

Thanks Pumbaster for your work!

My device doesn't seem to go to sleep...
WakeLockDetector shows Android System --> ConnectivityService as the main issue. BetterBatteryStats shows the same...
I tried turning location services off, froze Mobile Data and Mobile Network Configuration in Titanium Backup but that doesn't help. No checking if the same wakelock appears with wifi off...
Anyone with any clue? Or the same problem?

Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)

Krystanos said:
Will check the ROM and tell you dagrim.
But first thing first, I have to install it. And I have 2 questions, to avoid screwing things.
- Does it works with TWRP instead of CWM?
- Is there a reason to have a June version of minimal gapps where a version of December exist?
Thanks to everyone in the process (romers, informers, helpers)
Click to expand...
Click to collapse
I used pico gapps myself and the june version is way smaller then the december version, then again I actually did try the december version as well and it seemed to work fine. So not sure, apart from the size...
About TWRP vs CWM, not sure. Guess it also should work with TWRP but haven't tried... CWM is needed for True Dual Boot, but that seems bugged anyway.

By me too. Battery drain is to much, device don't go to sleep...

zolikaDB said:
By me too. Battery drain is to much, device don't go to sleep...
Click to expand...
Click to collapse
Yeah, seems to be a common issue.
My device only goes to sleep when wifi is turned completely off. When I have it set to turn off when display is off I still get the wakelocks. I also have set the scanning for open wifi to off, location services turned off, etc.
For now I flashed back to the 0114 version as that one is working fine here...
If I can share some logs or anything, I'd be more then happy to!

@dagrim1: I hope, Pumbaster make new, fixed build

I Encounter Graphical Glitches with 3rd Party Browsers (Opera and UC Browser)
Chrome works fine so far. Also heavy Battery drain an 17/1

@faust93: what is with battery drain?

Did a very dirty try or replacing frameworks.jar but that didn't work...
Saw some wifiStateTracker errors and that and ConnectivityService seemed to be part of the framework, that's why I gave it a shot. 0118 still has the deespleep/wakelock issue btw...

I don't really care about dual boot. MIUI has so much limits. Once I go to CM, I don't think I'll be able to come back to MIUI...
But I'll stick to CWM, just in case...

I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!

dagrim1 said:
I just tried the wpa_supplicant.bin file posted by pumbaster on 4pda and it seems to solve the deepsleep issues!
Post 351 of the custom mipad 4.4.4. rom thread there...
http://xep.8800.org/mipad/wpa_supplicant.bin
Place in system/bin and set permissions to rwxr-xr-x
@faust93: I hope you don't mind me posting this here but I saw you posted links to the same location in the topic start, if so my apologies and I will remove it asap (but I am going to sleep now, so won't be up until next morning...)
Also had some iussues with stuttering video playback, but setting 'disable hardware overlay' in developer settings fixed that for now...
Thanks for the awesome work!
Click to expand...
Click to collapse
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?

zolikaDB said:
Is this bin file integrated in 2015.01.18 build? What do you know about this ROM? Did you test it?
Click to expand...
Click to collapse
I don't believe it's integrated in 0118, think that fixes some sd stuff...
I am currently running the 0118 build (with the wpa_supplicant.bin file replaced manually) and seems to be working pretty fine. Had some video issues with a certain app (video jumping a bit, stuttering) but think I fixed that with 'disable hardware overlay' in developer options.
Without the replaced .bin I also had a problem with turning off and on wifi. It would work when booting, but if I turned it off I couldn't turn it on again... The replaced .bin also fixes that. Now checking if antutu finishes it's run...

@dagrim1: hope, Pumbaster fix this problem!

Just another small question: full wipe will delete the /data partition too right ? So the ROM zip file will be deleted too ? Or am I missing something ?
Thanks.

I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.

jastonas said:
I tried to install with TWRP and when I reboot, I get to MIUI v6 so I guess it rebooted in the wrong system.
Click to expand...
Click to collapse
Unfortunately I tried to install CWM with fastboot and it failed to install... No specific error message.
I have seen a port of TWRP for MiPad. Have you tried this one, or the standard one?

How I wish I could just flash CM on my MiPad...

[ROM][For GEEHRC][GPROJ][5.1.1][UNOFFICIAL] CM 12.1 + Nitrogen project (NPROJ) ALPHA

The project is based on Cyanogenmod 12.1.
At the moment, compiled alpha version of the firmware 12.1 CM + NPROJ.
Place it just after you make a backup of all data.
What is now present in the firmware:
Driver stock camera, no differences photos from photos taken at the drain, everything works, panorama, skype, etc. The runoff when you press the shutter release triggers auto-focus, so now it is 12.1 CM!
New initlogo.
I actually Russian, and accordingly made Russian the default language (forgive me for that please )
Disabled ADB secure.
Tweaks build.prop (to improve the quality of the photos).
Disabled block Assembly firmware, easily installed on the system, which has a size less than 2 GB (Yes, you can pick zip).
Bugs, jambs (it's not I made them):
Not working cyanogen setup wizard.
Crash software.
You can see the green demigod "AP Watchdog bark detected!" (crash software).
If you see a black demigod (this is the crash kernel), let me know.
Incorrectly read Bluetooth MAC address (Skite how to fix if anyone knows, my brain is not enough).
Source code: https://github.com/nitrogen-project
Attention! Immediately after installation to put Nitrogen Kernel!
Download: https://yadi.sk/d/GqqvKSddenX5R/Cyanogenmod/Cyanogenmod 12.1/Alpha

Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.

Nice work @Mr.MEX, you've really got the point with this ROM.

akahroba said:
Aha! Thanks for this thread. It was really needed. The first ROM with true stock camera.
To bypass the cm setup wizard after installing the ROM we should mount system and go into system folder and delete cynogen setup wizard folder.
To do this on philz touch, we need an aroma file manager placed in clockworkmod/aromafm/aromafm.zip path.
Click to expand...
Click to collapse
Well or through twrp to delete CyanogenSetupWizard.apk
Loller79 said:
Nice work @Mr.MEX, you've really got the point with this ROM.
Click to expand...
Click to collapse
Thanks
P.S. Now compile the version from today, let's see, did they issue the green demigod's.
Well, fix WiFi (From mako N4) added.

Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?

@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.

If I disconnect the cellular network and WiFi lose imei ... how come?

I often appears green screen "AP watchdog detected shoulder." What causes this error?

guidoido004 said:
Have to learn Russian, as I learned English forcing myself to use everything in English, why not do ok t again? Lmao. It comes with your kernel by default?
Click to expand...
Click to collapse
Yes, but this alpha no the second alpha will be delivered.
akahroba said:
@Mr.MEX about the bluetooth mac address, there is a fix by your countryman in this thread: http://forum.xda-developers.com/showthread.php?t=2528556
apparently the problem is caused by freegee unlock. hope it will help.
Click to expand...
Click to collapse
The fix does not work on version 5.
zed923 said:
If I disconnect the cellular network and WiFi lose imei ... how come?
Click to expand...
Click to collapse
But from now on more.
st4ik said:
I often appears green screen "AP watchdog detected shoulder." What causes this error?
Click to expand...
Click to collapse
Curves hands of the guys from CM.

I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it

akahroba said:
I've been checking the thread for whole day long. No new build? And please upgrade linux to 3.4.107. loller did it
Click to expand...
Click to collapse
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.

Mr.MEX said:
The kernel 0.2.9 are left to compile, there's always tomorrow, and maybe if I tell dadi11 how to change the compiler (toolchain), we will collect and firmware (can't figure out how to replace the compiler).
But you do not want then pick the zip and sew it to the core.
Click to expand...
Click to collapse
Can you also send a pull request to cm team to add the camera libs?

Attached Wallpaper, initlogo, bootanimation - will be in the next version.

akahroba said:
Can you also send a pull request to cm team to add the camera libs?
Click to expand...
Click to collapse
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.

Mr.MEX said:
They don't accept pull requests. Only through gerrit and gerrit for me it's the dark forest.
Click to expand...
Click to collapse
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/

It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]

akahroba said:
I see. Maybe xyyx can cherry pick it from your source. I'm not sure if he cares at all :/
Click to expand...
Click to collapse
So he's euphoria compiles, CM hates...

dadi11 said:
It's not that hard. If even I have done some commits to (pac) Gerrit you'll also give the trick [emoji14]
Click to expand...
Click to collapse
Um for one thing, they don't add a vendor for the devices in the source - this may be the reason why they don't add fix for camera + need to make commits to the kernel (the driver from the runoff).

[SGSI][Pie][Semi-bugless]MIUI 11

Welcome to MIUI sGSI For Galaxy J7 2017
TESTED ON J730X​
Some information you should know..
This is a fully working MIUI sGSI with Android version 9.0
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
I don't own any files here, except patch files.
So, we are here with sGSI. It's normally called "unstable" and "not for daily usage" so users are recommended to go for GSI. But GSI lacks features and has AOSP-like design that some users may be bored of that. And now we finally break that law. sGSI can now be used as daily drivers.
As the nature of these sGSI go, it was a non stop battle for almost 3 weeks straight to get it to this point where all features are working as expected. if you appreacite this work Hit the Thanks button
RULES OF POSTING : READ everything before commenting, And especially the instlal steps, the rom has been tested throughly for a long time, so if you have an critical issue like not booting or no sim, you missed the instructions, posts that are irrelevant to this project will be ignored(Constructive criticism is welcomed). If you do face a new bug however, dont just say "hey bug here" provide more information, and a LOGCAT, bug reports without logcats will most likely be ignored.
FEATURES:
Based on MiuiMiX 11 by MMX Team 9.12.26 using ErfanTools
Android 9.0
MIUII 11 Features
Semi-SIM support (Currently one SIM only)
Heavily debloated
Zipaligned
Very Optimised
Battery and performance focused
Full MIUI without missing vital apps
Rootable with Magisk
RMM/KnoxGuard/Defex Free
And many more
Kernel:
You can choose either latest CronosKernel by @ananjaser1211, or KRAKEN kernel by @SPARTANICUS
Install steps:
ensure you have LATEST TWRP from Here
Download all the files in the DOWNLOAD section
Wipe everything (SYSTEM,DATA,CACHE,DALVIK and preferably Internal storage all together)
Flash Project Spaget 3.0 (not X!) here and follow the steps there.
Flash MIUI-Aonly-9-20191230-ErfanGSI.img to SYSTEM
Flash your desired kernel, either Cronos or KRAKEN (must be using Treble version)
[IMPORTANT] Flash Magisk in order to have patch working
Flash sGSI-Patch.zip
Flash NFC Patch
After the boot animation is on for 30~60 Seconds. Hold VolumeDown+power until the device reboots
Install Google Play Services apk in Downloads section in order to get setup working
Setup your rom and READ the F.A.Q for more information.
BUGS:
Signal bar doesn't work (always empty) but it's acturally working
FM Radio (No FM Radio app in image)
Only one SIM is working at the moment
VoLTE not working (need another fixes)
SCREENSHOTS:
Imgur
CREDITS:
IF you helped in this GSI and i forgot you, tell me in a PM or in a reply
@ananjaser1211 for his Project Spaget, CronosKernel and HUGE contribution for Exy7870
@SPARTANICUS for KRAKEN Kernel
@SrCDA for his NFC patch
@erfanoabdi for his tools to port GSIs
And the rest of EliteTeam
DOWNLOADS ARE IN POST 2

DOWNLOADS:
Official Treble support Group : Telegram
----------------------------------------------------------------
All files are uploaded here: Google Drive
GSI: Here (My Google Drive acted up and does not let me upload any more files)

FAQ:
Good idea to read this F.A.Q While the rom is installing
Notes:
Q : Brightness bar not working / Camera doesn't work
A : You have flashed Spaget X instead of Spaget 3.0. Reinstall again
Q : Phone doesn't detect any SIM cards
A : Flash latest Cronos/KRAKEN kernel
Q : Everything on my screen is so small [J730 only]
A : Go to Settings > Developer settings > Set screen density to 411
Q : I got front camera stretch
A : Change resolution from 16:9 to 4:3
Q : Can I use front flashlight?
A : No, Samsung has their own libs, for now no apps can use front flashlight. Back flashlight still works
Q : How is battery Life ?
A : With some tests and some cycles, it will be better than stock due to optimzations
Q : the phone wont install any apps
A : Reboot

One more

does the rom have some type of error for daily use

VoLTE : Not work, need flash Magisk Module and using Phone App to VoLTE work
All work normal, just a Android Pie but like Android Q MIUI :good:
Great work

The first boot is so longer? I've waiting more than 10 minutes and don't boot. Or is bootloop?
And i've not found the MIUI-Patch.zip, only sGSI-Patch.zip

What android version is this? Can i flash the official magisk? There's no camera stretch bug? Like other gsi rom?

gabriel.oliveira.brito said:
The first boot is so longer? I've waiting more than 10 minutes and don't boot. Or is bootloop?
Click to expand...
Click to collapse
After the boot animation is on for 30~60 Seconds. Hold VolumeDown+power until the device reboots
gabriel.oliveira.brito said:
And i've not found the MIUI-Patch.zip, only sGSI-Patch.zip
Click to expand...
Click to collapse
Thanks for noticing, I forgot to rename the file.

NindoS said:
VoLTE : Not work, need flash Magisk Module and using Phone App to VoLTE work
Click to expand...
Click to collapse
I don't use VoLTE, so I couldn't test if it works. Can you tell me which Magisk module you used?
NindoS said:
All work normal, just a Android Pie but like Android Q MIUI :good:
Great work
Click to expand...
Click to collapse
Nice

Updated FAQ and sGSI patch. I forgot to add an important fix in patch, so anyone using this MIUI, reflash the new patch right now :good:

I tried again, followed all the steps as requested. On the first boot, I restarted the phone after approximately 30 seconds. But I still bootloop. I'm using Project Spaget 3.0, but I can't find a topic in the forum. Could you send me your Project Spaget zip file?
My logcat is on attachments

nfc not working. I installed the fix on the twrp and it failed, I had to install the fix when I started the cell phone so that it did not give me an error and it appears as a module installed in magisk but it does not work

Working fine but having bug
I have a bug with the WhatsApp application when viewing the stories that contain videos are not played and the app freezes.
I attach my log Cat about the error

I have problems with external storage, the system does recognize it but with third-party apps such as file explorer or streaming apps like spotify they don't detect external storage, I've tried to modify the vold.fstab and nothing. some fix they have

dani_hedz said:
I have problems with external storage, the system does recognize it but with third-party apps such as file explorer or streaming apps like spotify they don't detect external storage, I've tried to modify the vold.fstab and nothing. some fix they have
Click to expand...
Click to collapse
It's sGSI related problem, don't know why it happens

argenmu09 said:
nfc not working. I installed the fix on the twrp and it failed, I had to install the fix when I started the cell phone so that it did not give me an error and it appears as a module installed in magisk but it does not work
Click to expand...
Click to collapse
It works for me

Wi-Fi not working

[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo)

Resurrection Remix Oreo​
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions or bugs should be opened as an issue on the Github.
Please report any issues you have on the Github. The issue tracker helps me keep organized and on top of stuff.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your firmware to the most recent Oreo one via newflasher. I will update this with information regarding this. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 4/19/2020
Last Updated 5/13/2021

Additional info
Changelog:
May 13th, 2021 - 6.2.1-2020.10.11
* Signature spoofing, tweaked building fixing issues
September 4th, 2020 - 6.2.1-2020.09.04
* First build, updated libraries, security update
April 20th, 2020 - 6.2.1-2018.11.08
* Last release from russel5

Has anyone tried it yet?

DerSteppo said:
Has anyone tried it yet?
Click to expand...
Click to collapse
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.

jurko217 said:
Yes, very good rom but i find out on androidfilehost about half year, so old.
USB tethering doesnt work.
Plenty of functions.
Stable, fast, no lags, pretty battery acceptable, more than 1 day of battery life.
Display options from stock, stock camera works very good.
I think, we need upgrade RR to 7 or 8.
I am using it now for about week and its very good as daily.
And at this moment its way better than Q roms.
Click to expand...
Click to collapse
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.

hockeymikey said:
You can't find the most recent version of the rom on AFH, I had to hunt it down from some random forum and the most recent one before that was unstable so wanted to get it out there for people to have. I really like RR. I'll test tethering, I thought it was fine but haven't really used it. Maybe I'll mess with 7 or 8 someday after I have this one developed alittle. I personally don't have any interest in Pie+.
Edit: USB tethering works fine for me. Must be an issue with your computer. I'm using Kubuntu 18.04 and works perfectly.
Click to expand...
Click to collapse
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.

jurko217 said:
I am using Windows 8.1, but in other roms like stock or PE 10 USB tethering works. I push that on and no reaction in computer - networking.
If will be Havoc OS 2.x or BaikalOS, ill start interest in pie, because i had these roms in Mi Mix 2 and they was best. Havoc in general, can be compared with most functions with RR, Baikal from russia brats in battery life, performance and simplicity.
Idk if they dont arrive to XZ1c, but pie i liked was stock, Oxygen, Miui (with some bugs, but with future).
Still, oreo and nougat roms are older, but better in most things except mentioned roms.
Click to expand...
Click to collapse
No idea, it has to be your computer I'm guessing. Make sure you're running the most recent version since that other versions found on the other thread is very buggy. Noted on them.

> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?

asdf2345 said:
> Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Where's the boot.img?
Click to expand...
Click to collapse
It's in the zip file.

Got a new update out https://github.com/hockeymikey/android_device_sony_lilac/releases/tag/6.2.1-2020.09.04
Check it out and let us know how it works. Seems stable on my end from testing.

How does Resurrection Remix compare to CrDroid?

asdf2345 said:
How does Resurrection Remix compare to CrDroid?
Click to expand...
Click to collapse
No idea, can't remember testing out the Pie CrDRoid on here. I'm not a fan of Pie+ so it didn't interest me. Should test and report in, looks like they are similar being LOS based with decent amount of customization. CrDroid has signature spoofing, but I'm making a build with that added in for RR as I type. But yeah, let me know and what other features that CrDroid has that looks cool.

hockeymikey said:
Resurrection Remix Oreo​
If you're not familiar with Resurrection Remix (RR), it's a very customizable and feature rich ROM. It's packed with some many great features like a notification ticker (like in the good ol' Kitkat days), styling changes, custom gestures, and more! RR is based on LineageOS. This is a build originally developed on by (russel5), but abandoned in favor of AospEx and Pie projects of his. Personally, I'm not a fan of the direction taken in Pie and will be sticking with Oreo. I'll be developing the rom further with features, bug fixes and enhancements. Any suggestions should be opened as an issue on the Github.
Downloads
GitHub
Installation
1. Download firmware zip
2. Download OpenGapps/MicroG/Whatever
3. Push to phone
4. Reboot to recovery (recommend TWRP) and do a full wipe
5. Flash RR then whatever else after (Gapps, ect)
6. Reboot
7. ???
8. Profit
General Info:
If you have issues with the camera being green, make sure you update your fireware to the most recent Oreo one via newflasher. I will update this with information regarding this.. It's been months since I did it so I need to remember and hunt the files down I used (which is hard since my last computer died and I switched to Linux). I'd backup your Drm keys before doing anything if you do.
Exclude when flashing:
* fotakernel.sin
* kernel.sin
* simlock.ta (if you have it)
* system.sin
* userdata.sin
* vendor.sin
Forced encryption is disabled. If you want it make sure to flash the boot img attached. Many users have bootloops so use at your own caution. To flash use fastboot flash boot boot.img
Special thanks to:
@modpunk
@russel5
Anyone else I'm forgetting
Source:
Repo
XDA:DevDB Information
[G8441, XZ1c] [8.1] Resurrection Remix v6.2.1 (Oreo), ROM for the Sony Xperia XZ1 Compact
Contributors
hockeymikey
Source Code: https://github.com/hockeymikey/android_device_sony_lilac
ROM OS Version: 8.x Oreo
Based On: LOS
Version Information
Status: Stable
Current Stable Version: 6.2.1
Created 2020-04-19
Last Updated 2020-04-20
Click to expand...
Click to collapse
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.

jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted, but magisk app not installed, so i had to install Magisk Manager manually, root installed.
Second boot into recovery and flash BitGapps caused no google store app, like before, so i flashed MindGapps and it works.
It is mine problem, i using alternative gapps but good to notice.
Sometimes not smooth, torn animations. More often than older build.
Red blinkings: Right after successful boot, after some clicks i see weird red blinkings on display. Something similar like in developer options turn on display blinkings after stress GPU/CPU but this happen in random time and is not turned on. Is little bit enyoying, its not happened in older 2018 build.
So my decide will be flash again .228 firmware and stay with Havoc OS, now i used version 3.8 for month and i can say, now is android 10 in lilac flawlessly done. I like more older Oreo UI but fix issue with blinking and i will be your satisfied user.
Thank you and best regards.
Click to expand...
Click to collapse
What's special about Bitgapps? That's really strange, can you grab a log on boot using adb? If not, go to https://github.com/hockeymikey/android_device_sony_lilac/issues and make an issue and help me track it and I'll get around to testing it. It'll help keep in touch with you and solve it especially if for some reason I can't recreate it for some reason. I got that red outline too and I thought it was just me. It went away for me so might be temporary on the initial install. If you could create an issue for that too on the previous link so I can keep you updated for that too.

jurko217 said:
Hi, i have tested update of this rom and found out 2 system bugs.
First thing - bootloop. I flashed it like usually with newest BitGapps arm64 8.1.0 v15 and magisk. BitGapps caused bootloop. Clean install with only magisk booted,......
Click to expand...
Click to collapse
So I did some testing. The red blinking is gone, that fix will be included in the next release (which includes signature spoofing and updates so a few system libraries like base, native and lineage-sdk). BitGapps doesn't cause a bootloop for me. It was kinda buggy, which is odd and crashes. I'll see what I can find for it. Magisk works fine for me. Make sure it's the most recent version but I was using old versions too as well as new so I don't know.

Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?

muebbel said:
Hm, with usb-debugging enabled, it dont ask for permission and dont save the adb-key, so u arent able to adb into twrp. But ADB to the booted device works. Anybody else got this?
Click to expand...
Click to collapse
That's a TWRP reason. Whoever built it disabled adb in it. I repackaged twrp to allow adb for myself, I can share it if you want.

This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?

muebbel said:
This will be nice
And... i get this red-frame too if some higher cpu-usage happens. What did u do against it?
Encrypting the device ends in a infinity-loop at the "Encrypting... time remaining 00:00.."-Screen.
Maybe i missed something (tried with and without the boot.img for force-encryption)?
Click to expand...
Click to collapse
I think this is the correct one, let me know if not. Red frame is an issue I caused with how I built it, building it as a dev build not production. It's fixed on my device. I'll eventually get a new build out, I've been waiting to get OpenDelta done for OTA updates first to streamline the updating process. Maybe I should push one out sooner since the build on here I don't think is really that usable while my phone one I'm using daily. I haven't tested encryption honestly. I'll have to look into. If you could make an issue on github with every little detail to help me track and fix, that'd be cool.

Hmm, same problem -> adb devices -> unauthorized
And there is no dialog for accept/store the ADB-Key if u plugin the PC for the first time.
So.. i was using newflasher to flash the stock oreo rom and guess what... the stock rom does the same... so if u flash the stock rom (47.1.A.16.20) without remove any files from the stock-rom-directory and the adb_key still exists... where can it be?
BTW: i can access the stock-rom with adb add the first start at the "Welcome"-Screen... but twrp cant find/use the key which is stored $somewhere

[ARM32] [9.0] [GSI PORT] Havoc OS 2.9

Before you get started,
i am not responsible for bricking device, dead sdcards,
muted alarm, or even thermonuclear war.
YOU chose to do this modification,
IF you point your finger to me to brick your device,
i will laugh at you.
This is GSI port from Official Havoc OS 2.9 by @vince31fr
Supported Devices
J701X
J730X
J600X
J530X
Details
Debloated /system 1037MB to 754MB
Pixel Launcher instead of Lawnchair
Includes SF-VENDOR 3.0 (Changelogs few days later)
Added M10 Fingerprint
Build.prop tweaks
No Gapps included, flash Open GApps ARM, 9.0, Pico
0.9GB /System with GApps Pico
Credits
Me for SF-VENDOR and Editing.
@vince31fr XDA for GSI
@ananjaser1211 for Cronos Kernel
Installation steps
You need Latest TWRP 3.4.0 or higher, or OFox 11.0
Flash Exynos7870_CreateVendor_2.0.zip
Flash HAVOC_REPARTITIONER.zip
Reboot recovery
Format data, Wipe Dalvik, Cache, System, Vendor, Data, Internal storage
And Flash Havoc-OS_2.9_J6-J5_J730_J701.zip
(Optional) Flash OpenGapps (Needed for Google Apps)
Reboot and Enjoy!
Bugs
HW Keys (Use NavBar instead)
Stretched Camera in J701 (Use 720p camera to fix this)
Downloads
GDrive
Mega
Telegram Support;
SF-GROUP
Everything Allowed but; Respect others. No NSFW/ Instant ban. No Ads. Enjoy
t.me
Contributors
@ichbinahmet
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 2.9
YY-DD-MM
Created 2021-30-09
Last Updated 2021-20-10

reserved

Thank you, but I've got bootloop. SM-J730F

Spargatorul said:
Thank you, but I've got bootloop. SM-J730F
Click to expand...
Click to collapse
Do you have /vendor partition?
You should flash Create Vendor from Project Spaget.
Im using same device, stable.

Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.

Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
You using wrong recovery.

Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Use TWRP 3.5.0
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com

Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Btw, ROM updated, read description, also use lastest TWRP .
Enjoy!

ichbinahmet said:
You using wrong recovery.
Click to expand...
Click to collapse
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?

Spargatorul said:
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?
Click to expand...
Click to collapse
Yes, inthread download links updated.

I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...

how to fix no audio?, j701f

Spargatorul said:
I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...
Click to expand...
Click to collapse
Probably you using custom kernel Kraken.
Flash latest from Magisk github

ichbinahmet said:
Probably you using custom kernel Kraken.
Flash latest from Magisk github
Click to expand...
Click to collapse
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.

Spargatorul said:
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.
Click to expand...
Click to collapse
Yes KRAKEN kernel breaks ROM on magisk flash, so you need to use Cronos kernel
Im trying to fix that broken loudspeaker bug.
Thanks for reporting

not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!

So7urno said:
not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!
Click to expand...
Click to collapse
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review

ichbinahmet said:
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review
Click to expand...
Click to collapse
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up

So7urno said:
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up
Click to expand...
Click to collapse
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again

ichbinahmet said:
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again
Click to expand...
Click to collapse
That fixed the problem! Thanks!
It seems I was using a wrong TWRP....
Most of the bugs I mentioned before are gone\fixed (loudspeaker, whatsapp keypad, sdcard).
except the video recording with the "opencamera" app (recorded videos are unplayable with messed up time lapse),
I tried also "HD camera" app from playstore with same problem.
But if I record video directly through whatsapp videos are ok.
Everything else seems working fine thought, stable and fast !
are you planning to work\fix the "(HW Keys (Use NavBar instead)" bug?
I Will keep using this rom for now, great job @ichbinahmet !