Database Users

Q&A, Help & Troubleshooting for Resurrection Remix 5.5.9 by quanganh2627

This is a Dedicated Q&A thread for Resurrection Remix Rom by quanganh2627. Please post all your Questions & all issues related with RR Rom. Any Dev or other Friends here will try to solve your issues.
Please don't tag quanganh2627 for every small issue or bug. He has lots of work to do. Don't ask for any ETA's or Update's because when ever there is one, quanganh2627 will will let us know. Kindly post all your issues here without tagging dev's.
ROM & INSTALLATION : forum.xda-developers.com/zenfone-5/development/resurrection-remix-zenfone-5-t3185403
you can use Unlocking Tool from above
Or
Unlocking Bootloader & install TWRP (Auto-installer): Install-twrp-stable-on-zenfone-5 " NOT PROMOTING ANYTHING " I found it working Efficiently

--RESERVED---

Issues :
1. Random lock when use mobile radio except 3G (sometimes i have to travel to poor signal and just got Edge)
2. After reboot the network type is WCDMA prefered, i have to set to everytime i restrart the phone on *#*#4636#*#* to lock on 3G signal
3.How to save photo on External Memory on Asus Pixel Master Camera
4.How to update Asus Keyboard ? ( on google play say asus keyboard not compatible wth the phone
5,network activity on status bar is default to NO everytime restrart the phone
BTW this is some issues i found,im using kernel beta 7.0 7.2 and Exposed V75
thanks Before

kuranzi said:
Issues :
1. Random lock when use mobile radio except 3G (sometimes i have to travel to poor signal and just got Edge)
2. After reboot the network type is WCDMA prefered, i have to set to everytime i restrart the phone on *#*#4636#*#* to lock on 3G signal
3.How to save photo on External Memory on Asus Pixel Master Camera
4.How to update Asus Keyboard ? ( on google play say asus keyboard not compatible wth the phone
5,network activity on status bar is default to NO everytime restrart the phone
BTW this is some issues i found,im using kernel beta 7.0 7.2 and Exposed V75
thanks Before
Click to expand...
Click to collapse
1. I Face random screen lock very rarely.
2. Select 3g from sim cards > sim settings.
3. Photo can't be saved to extcard as of now.
4. Place the updated apk in /system/priv-app/asuskeyboard folder, set permission to rw r r or 06 4 4 & reboot device.
5. Clear cache & dalvik cache or upgrade to 7.1.

Hey, is there anybody facing phone waking up in your pocket?

Unlocking Bootloader & install TWRP (Auto-installer): Install-twrp-stable-on-zenfone-5 " NOT PROMOTING ANYTHING " I found it working Efficiently[/QUOTE]
Open gapps works with above twrp?

FaizK said:
Unlocking Bootloader & install TWRP (Auto-installer): Install-twrp-stable-on-zenfone-5 " NOT PROMOTING ANYTHING " I found it working Efficiently
Click to expand...
Click to collapse
Open gapps works with above twrp?[/QUOTE]
Haven't tested with this twrp.....i flashed it from quang's twrp.
Just try it out..! If it fails nothing happens......if its success then you can enjoy your open gapps....

[email protected]!$h said:
Open gapps works with above twrp?
Click to expand...
Click to collapse
Haven't tested with this twrp.....i flashed it from quang's twrp.
Just try it out..! If it fails nothing happens......if its success then you can enjoy your open gapps....[/QUOTE]
As you said it is efficient ,so I thought you might have flashed the ROM and opengapps via above recovery.
I also flashed it via quann's recovery

[email protected]!$h said:
1. I Face random screen lock very rarely.
2. Select 3g from sim cards > sim settings.
3. Photo can't be saved to extcard as of now.
4. Place the updated apk in /system/priv-app/asuskeyboard folder, set permission to rw r r or 06 4 4 & reboot device.
5. Clear cache & dalvik cache or upgrade to 7.1.
Click to expand...
Click to collapse
thks before...
random lock is appear when i have poor signal, and 3g is default change to wcdma prefered after restart

FaizK said:
Haven't tested with this twrp.....i flashed it from quang's twrp.
Just try it out..! If it fails nothing happens......if its success then you can enjoy your open gapps....
As you said it is efficient ,so I thought you might have flashed the ROM and opengapps via above recovery.
I also flashed it via quann's recovery
Click to expand...
Click to collapse
I said i found it working Efficiently for unlocking bootloader..........it unlocks bootloader & installs twrp...

When I try to change music by earphone controls with the screen off, the screen lights up instead of exchanging music. Does anyone know how to fix?
This bug is present in versions 6.7, 6.9, 7.0, 7.1 and 7.2 of the RR

hey guys, i got problem when i've install l_speed_v2.3_revolution also with super su and got bootloop. i've tried to wipe the dalvik and cache, it work for an hour and reboot again by it self.
what can i do to solve this problem.? thanks.

No UI after dirty flashing Beta 7.2 with Kernel Auditor ! The Boot animation and "Upgrade in Progress" dialog did show but Android UI didn't !
I have data in internal storage so I can't wipe it ! Any tips guys ?
I flashed the zips in this order : RR ROM, OLD GAPPS, Xposed v78 and then Wipe Cache.
EDIT : When I press the power button for a few seconds for force shutdown, the power menu pops up for a few milliseconds before the device goes off

adnaanbheda said:
No UI after dirty flashing Beta 7.2 with Kernel Auditor ! The Boot animation and "Upgrade in Progress" dialog did show but Android UI didn't !
I have data in internal storage so I can't wipe it ! Any tips guys ?
I flashed the zips in this order : RR ROM, OLD GAPPS, Xposed v78 and then Wipe Cache.
EDIT : When I press the power button for a few seconds for force shutdown, the power menu pops up for a few milliseconds before the device goes off
Click to expand...
Click to collapse
Try to Connect your device to PC & copy your data......

Fernando0258 said:
When I try to change music by earphone controls with the screen off, the screen lights up instead of exchanging music. Does anyone know how to fix?
This bug is present in versions 6.7, 6.9, 7.0, 7.1 and 7.2 of the RR
Click to expand...
Click to collapse
@tank0412 bro.....do you know how to Fix it?

sorry, now i've back to my kitkat stock rom due my device usually reboot after several minutes in RR 7.2 and want to go to RR again. Do i have to install lollypop first or just straight install RR.? thx

ekinodermata said:
sorry, now i've back to my kitkat stock rom due my device usually reboot after several minutes in RR 7.2 and want to go to RR again. Do i have to install lollypop first or just straight install RR.? thx
Click to expand...
Click to collapse
If u r not facing any screen freeze due to unlocking boot loader........ U can directly upgrade to RR......

[email protected]!$h said:
If u r not facing any screen freeze due to unlocking boot loader........ U can directly upgrade to RR......
Click to expand...
Click to collapse
yeah thx, it works.

adnaanbheda said:
No UI after dirty flashing Beta 7.2 with Kernel Auditor ! The Boot animation and "Upgrade in Progress" dialog did show but Android UI didn't !
I have data in internal storage so I can't wipe it ! Any tips guys ?
I flashed the zips in this order : RR ROM, OLD GAPPS, Xposed v78 and then Wipe Cache.
EDIT : When I press the power button for a few seconds for force shutdown, the power menu pops up for a few milliseconds before the device goes off
Click to expand...
Click to collapse
Maybe it has something todo with Auto Brightness and you set it so Low before you upgrade it to 7.2 because i noticed there's that bug in that version , i suggest to flash Multifunctional Kernel by X AnwarMov but if you want the Stock RR ROM kernel then flash it , fix the auto brightness ( by set the brightness slider to middle or really high and turning the auto off ) and then reflash the RR ROM stock kernel
[email protected]!$h said:
Try to Connect your device to PC & copy your data......
Click to expand...
Click to collapse
You Know , you still able to connect via USB to computer from TWRP Recovery ( Dec Build ) By Quanganh just look for the option ( this will make the proses easier ) , but so far as i remember if you want to backup the internal memory you have to boot normal and plug the USB ( Depend if your device if locked )
Sorry for Late Answering
and as you know this is according to my logic so correct me if i'm wrong

RevanEphys said:
Maybe it has something todo with Auto Brightness and you set it so Low before you upgrade it to 7.2 because i noticed there's that bug in that version , i suggest to flash Multifunctional Kernel by X AnwarMov but if you want the Stock RR ROM kernel then flash it , fix the auto brightness ( by set the brightness slider to middle or really high and turning the auto off ) and then reflash the RR ROM stock kernel
You Know , you still able to connect via USB to computer from TWRP Recovery ( Dec Build ) By Quanganh just look for the option ( this will make the proses easier ) , but so far as i remember if you want to backup the internal memory you have to boot normal and plug the USB ( Depend if your device if locked )
Sorry for Late Answering
and as you know this is according to my logic so correct me if i'm wrong
Click to expand...
Click to collapse
You're right It was due to the auto brightness setting ! I turned it off and everything turned out fine. Anyway, I've switched to a stock based custom ROM for the time being, I'll definitely come back for RR 5.6 !

CM reboots when making or receiving calls :confused:

Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.

This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.

Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs

Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.

pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.

J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs

Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.

I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.

Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.

It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.

J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.

pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.

J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.

rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.

Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.

Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps

It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.

Network Solution grayed out/solved

Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?

Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?

SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
Could be. I had tried with Pico and super. Did not work for me
Sent from my Zuk Z1 using XDA Labs

None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...

Fahad305 said:
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Click to expand...
Click to collapse
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs

SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I tried to flash Gapps Stock but it didn't work, Sim selection was still grayed out.
Flashed zui 2.5 Nougat and then clean flashed other Los Nougat ROMs and now Sim selection is working fine.
Thanks for the solution.

SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I've a same problem haunting me in LOS 14.1, I'll try your solution first...will let you know...
Sent from my ZUK Z1 using Tapatalk

Narasimha12 said:
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
my file was corrupt i downloaded it again and bingo. working fine.
thanks

Narasimha12 said:
Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Click to expand...
Click to collapse
COS 12.1 sim selection was working out of the box.
CM 13 selection was working
LOS 14.1 selection stopped working
Flashed ZUI selection is back
& then clean flashed LOS again selection keeps working
Thanks a lot.
It must be radio baseband issue.
Sent from my ZUK Z1 using Tapatalk

Suggestion
Simply I tried this at my own,
And it worked!
Steps :
1. Install Lineage OS ROM from TWRP. (don't install Gapps)
2. Restart your android.
3. Skip all the startup steps after booting-up.
4. Now go to SIM settings and you see, you are able to select SIM for calls.
5. Select any SIM of your choice.
6. Reboot again into TWRP & install Gapps.
7. Reboot into system.
Now you see, you are able to select any SIM of your choice. :good:

Well...try updating kernel...it worked for me...try radioactive kernel(Radioactive reborn acuicultor) for nougat....here is the process
1)Go to twrp/cwm recovery
2)Perform factory reset and wipe dalvik,data,cache,system
3)first install any nougat rom then install any gapp package for nougat and finally the radioactive reborn kernel for nougat
4)reboot
Bam you are there...should work fine

https://forum.xda-developers.com/zuk-z1/help/network-solution-grayed-solved-t3545218

Can anyone help me in camera issue on nougat....after the clean flash when i open default camera app it works fine in auto mode but when switched to hdr mode then it crashes and says unknown error or cannot connect to camera this error occured in all the nougat rom excpet for los 14.1...Now for los 14.1 camera app works fine for few hours then it lags lije hell touch focus doesnt respond....plzz help

Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?

happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
To access the Recovery you have to press the three buttons at the same time (vol+ / vol- / power).
Enviado desde mi ZUK Z1 mediante Tapatalk

happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
Just use "adb reboot recovery" in CMD with USB debugging enabled. Won't have to bother with key combinations. ZUI is installed on system, boot partition, and updates modem partition. Doesn't touch the recovery partition.

(Please reply)Facing a strange problem while flashing miui Pro

Last few days I tried to use custom ROM. Volte doesn't work. I've given up on that issue now. Now problem is Miui pro.
After flashing it keeps showing boot logo ( I waited for more than 30 minutes) but the older version (7... Something) flashes without any problem.
How long should I wait to complete it's booting process( more than an hour??!!!!!)
P.s- device encryption is enabled [ but I don't think it's causing the problem cuz older version is doing fine]

http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks ?

Also check this post for more information.
Link:- https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Thanks.

Im running Miui 9.2 global stable 9.2.2.0
Can i do dirty install? I dont wanna lose apps data

Im using stock miui global stable 9.2.2. Android 6.0
If i wanna install miui id, do i need to wipe all , as in format my handset. Or is it ok to just wipe system, cache dv? I dont wanna lose my apps data

@Trovies hi,
Just do titanium or swiftbackup search the apk in google, and u can do dirty flash but i will not recommend it.
Note :- download the premium version of the swiftbackup from the internet.
Thanks

Flash lazyflasher.zip

Sagar_zac said:
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks
Click to expand...
Click to collapse
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036

Vinayakn73 said:
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Click to expand...
Click to collapse
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. ?For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache

Sagar_zac said:
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Click to expand...
Click to collapse
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??

Vinayakn73 said:
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Click to expand...
Click to collapse
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process

Sagar_zac said:
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Click to expand...
Click to collapse
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english

Vinayakn73 said:
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Click to expand...
Click to collapse
Ya i know modules can be a pain in the ass only one suggestion when ever after flashing a module if its stuck in the bootloop then just use magisk Uninstaller then again install Magisk or use magisk for recovery to remove the particular module which is causing boot loop also use root youtube valence and use universal installer it will not cause bootloop. Also use minimal module only what you need. Ok then. Also do as u discreet i am fine in this rom. And its great. ?

See my modules

I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.

Sagar_zac said:
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Click to expand...
Click to collapse
yup there is no doubt this is best custom miui rom out there. But this bootloop and boot time driving me nuts. I wonder why all this problems are popping up though the rom is based on official firmware and I've never faced such problem with official roms. I will give it a try again after two days. I just hope that time it will go smooth.

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)
Note:================
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
========================
LineageOS is an operating system for smartphones, tablet computers, and set-top boxes, based on Android with mostly free and open-source software
All the source code for LineageOS is available in the LineageOS Github Repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
I've built this operating system with select userdebug .
It's unnoficial LineageOS17.1 for Galaxy S6 (ZEROFLTEXX)(SM-G920F).
I strongly recommend to perform a backup of your current rom before installation.
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
SeLinux run in enforce mode,
also you can opt to have SeLinux run in permissive mode.
Installation process from stock rom
01. Boot into the download mode.
02. flash TWRP with Odin (comes in AP). The hooks at Auto Reboot and F. Reset Time out.
03. disconnect USB cable after flash, battery out and in again.
04. boot into recovery -> Allow Modifications
05. Advanced Wipe: Dalvik/ART Cache, System, Data, Internal Storage, Cache (lasts a while)
06. install -> select lineage image, then add more zips and gapps, then flash
07. patching system image unconditionally runs through with progress bar
08. Open Gapps are flashed, progress bar runs through
09. when done, tap reboot system, Swipe to install TWRP app (or not, if you don't need it)
10th reboot
11. Lot 17.1 boots. (quite a while ^^)
12. type through the facility
13. ready
Download:
==> tajaribsoft-en.blogspot.com/2020/09/unofficial-lineageos-171-samsung-galaxy.html
Because i'm new , i can't create link

Hi gapps included in ur ROM?
And can I install other boot.img files? I have tried that.
I know it won't work but a question..
Still will download and test..
---------- Post added at 07:25 AM ---------- Previous post was at 06:32 AM ----------
Almost everything works except Volume control while calling the same problem on 17.1 ROMs but everything else works fine I can just adjust volume from my file I'll just patch it with profile text lol thanks.. Very nice work ??????☎?

Yup this is my other account here.
and only on my laptop..
But i managed to get my favourite Kernel to be installed thanks to this beautiful work and kernel i installed is enforced and my ( favourite Kernel )
is pemissive so it depends on kernel and i don`t give a f... nice work man.. Thanks..
I can`t say thank you enough because i have tried other roms to get my thing install`d lol THANK YOU..

Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue

add support 925f zeltexx pls

AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
It has that same sound software problem.
But I think everything else is working. I try to restore boot from my previous backup it works but (sim not showing).
I try to restore other backup stuff but, of course did not working.
But it amazing i can use other kernel just by restoring from backup
They might be better ways to use other Rom's kernel.
I will use it like that soon without any possibility to have Sim card
I like my kernel lol..
This phone ( I ) use is near death so let end it Battery life with that Kernel I use... Lol
I'll test permissive only file download soon and try to restore boot from backup. And see
Or I should try to install Boot.img from the zip
Edit: It didn't work but first with enforcing SE always boot up no matter what i restore from my backup boot/cache/data/efs. I didn't test other rom enough yet.
And I will test more soon for fun..
Btw.. I got 3 mods installed on my backup so I'm gonna have to test new install's from all rom's and re-test from all over.. Or from start lol..
I want to know you guy's have any mods to make system faster or battery-friendly mods
I have added some text to build.prop and installed 3 mods I think. Maybe not all installs patches:
First for Fullscreen Gesture (Q) from Magisk modules.
Because my ROM is old and I removed some system apps.
And then I install kernel mod from this site. Lol (kTweak) it can be seen from Magisk
And 1 patch from here XDA post few days ago
And my build.prop tweak it looks funny:
ro.min_pointer_dur=0
ro.max_pointer_dur=40
wifi.supplicant_scan_interval=9000000000
windowsmgr.min_events_per_sec=0
windowsmgr.max_events_per_sec=60
debug.sf.nobootanimation=1
logcat.live=disable
ro.media.enc.jpeg.quality=100
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.mot.eri.losalert.delay.delay=1000000000
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
persist.android.strictmode=0
ro.config.nocheckin=1
That it if I didn't forget something
And make Settings less cpu hog or how to say make it CPU friendly lol .
1 more thing I have edited Sound mixer from System files
You can search it on my comments on my other account Johannes Davidsen
On Enezusun's 17.1 Lineage Os Multitarget rom
I couldn't post attachment's so I have to copied text
That all.
Here, there are 3 sections i think : https://forum.xda-developers.com/showpost.php?p=83187603&postcount=310

This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.

About Enes ROM
0x0rbit said:
This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.
Click to expand...
Click to collapse
Why don`t you test them by yourself sometimes same device have different problem with same rom and it is very confusing..
For me all of them have working camera and all of them have, calling sound software problem that i just fix by editing sound file..
Have a nice day..
And yes cam is working on this new august build,
same on sound problem too
---------- Post added at 08:13 AM ---------- Previous post was at 08:02 AM ----------
AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
For me cam is working, only problem i so is the same software problem when trying to lowèr volume on calling or say on earpiece i`ll just replace sound file with the file i already have edited but it is very low.
You can test it i have commented on Enesuzun`s rom i think it started on page: 31 or 32 there are 3 comment sections i use for text
Here: https://forum.xda-developers.com/ga...ageos-17-1-t4053959/post83187603#post83187603

good

Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.

schlombie said:
Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.
Click to expand...
Click to collapse
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?

bemek01 said:
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?
Click to expand...
Click to collapse
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.

hello or a little problem with the download link, just don't have the link, can you try s create a link on mega or google drive ???
to another thing i wanted to say, i am surprised that you are creating a rom for android 10 with the SElinux Enforcing, i wanted it a lot to increase the security, but the problem of this that lead to lose some battery, however i am interested to try this rom on my samsung galaxy s6 SM-920F i just have to understand where the link lol.
in my opinion, however, thanks to the rom with the SElinux Enforcing maybe this rom could become official if you want, and put on the lineage os website, but honestly I don't know how it works, this is just my opinion
I wanted to say another thing, that second it was better to do lineage os 16.1 because it is much more stable for this device, in fact existing official resurrection remix with android 9 that I use that not a bug, or tried official evolution x with android 10 but the problem of the wi fi that turns off and that you can disable it on the lock screen, and this and these 2 are a big problem, and that problem also exists in the lineage os 17.1 of another creator, everything to see if in the future when there will be lineage os 18.1 for this device with android 11 maybe the wi fi and lock screen security will work prevent you from turning off the wi fi from the lock screen
i am using google translator, hope the translation is right

schlombie said:
Than I installed the 17.1rom without format data. Only wipe system, data and the caches.
Click to expand...
Click to collapse
A wipe basically formats a partition, so what exactly do you mean, that you wiped the encryption too?
I'm sure this ROM doesn't support whatever encryption /e/ may support that you're suggesting.
But maybe I've got this all wrong

schlombie said:
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.
Click to expand...
Click to collapse
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.

gerardomare said:
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.
Click to expand...
Click to collapse
Someone please can explain to me step by step how do this trick for enable encryption ?
I've tried 6 times and nothing works maybe I'm misleading something.

Hi, i just wanted to ask how you compiled lineageos for the s6. I tried to compile los 17.1 with the files provided by enesuzun and have massive problems with lunch detecting the files. Many are missing and even if i collect all it just acts weird. Since enes provided many working images these file should work to compile, don't they? Do you know any good tutorial? Most of them are only either for official builds or completely new unsupported devices.
Thank you in advance.
Chasbrot

What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.

szazs89 said:
What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.
Click to expand...
Click to collapse
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.

Chasbrot said:
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.
Click to expand...
Click to collapse
Oh, I mean: what gapps does this ROM (17.1) need? (with opengapps 10.0 I got into bootloop)