Related
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 !
Status:
It still needs some polishing and cleaning up, and there are unresolved issues but nothing serious (check below). Based on user reports this is pretty usable. Battery and performance are both at least as good as stock, with the added benefit of having doze support, being less bloated, coming rooted etc.
Credits:
This wouldn't be possible without DeckerSU's post with an official MM rom. I've used his file to extract the binary stuff.
I've also cloned his device tree to build TWRP on omnirom since I was having a hard time building it on CM.
I started by cloning pivoq's device tree for CM12.1. So credit goes out to him too.
Those are just the things I've used directly but looking at other people's code also helped a ton to figure things out. So I guess credits goes also to the whole community/ecosystem.
Known Issues:
Smart lock isn't preserving settings across reboots. (If anyone is willing to test this and contact me, it can probably be fixed easily)
The bundled camera app (Snap) works well. Stock camera app works well as well (doesn't come with the ROM, maybe I'll provide a zip in the future). But some cam apps have issues.
Not Working / Enabled / Unknown:
Flip cover.
Drm?
Fastdormancy?
No NFC icon on statusbar. ** Won't fix ** - AOSP or CyanogenMod do not have such an icon. Some vendors add it. As such I don't think ROM should come with it by default. Either there's an exposed module for it that people can install, or a flashable zip can be made to add it. I think that's the better route rather than have the ROM come with it.
CNE - ** Won't fix ** - Disabled by choice. It's an anti-feature in my opinion.
Notes:
Doze: Officially doze requires a special motion sensor that our device does not have. Motion will not keep the device from dozing, or awake it. Also, doze by default takes a long time to kick in (about ~1h), and I would advise people to tweak those timings to their usage patterns with Doze Settings Editor (http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130), or some other app like Greenify / Nap time. Lastly doze is supposed to work with GCM, which isn't available on the ROM by default unless you install google apps or an adequate substitute.
XPosed: works with v87+.
SELinux: I've seen a lot of people setting selinux to permissive, often because of some xposed module. SELinux is an integral part of android's security. Things are already pretty bad with it, disabling it isn't recommended. While there will still be many security bugs, often selinux limits their scope or makes it so that multiple bugs will be required for successful explotation. No xposed module is worth that.
Download:
LineageOS 09/04/2017:
https://www.androidfilehost.com/?fid=745425885120723074
TWRP 3.1.0:
https://www.androidfilehost.com/?fid=817550096634753196
- The recovery has support for encryption and adopted storage (including mixed mode).
ROM Changelog:
** 09/04/2017 **
Code:
- April security patch level
- Kernel sync to 1.2.7-rb1.41
** 25/03/2017 **
Code:
- March security patch level
**13/03/2017**
Code:
- Move on to LineageOS
- Fix wifi tethering
- Fix OpenGapps issues
- February 01 security patch level
- Sync kernel to LA.BR.1.2.7_rb1.40
** 16/12/2016 **
Code:
- December 01 security patch level
** 09/12/2016 **
Code:
- Updated kernel for CVE-2016-5195 (November 06 security patch level now).
- Added ZEN IO Scheduler
- Tweaked cpu governor, 200Mhz+ clock (from 533).
- Added zram.
** 25/11/2016 **
Code:
- Fixed SIM regression for dual sim variants.
- Added F2FS support for data and cache (Beware recovery linked above wasn't updated)
- Tweaked minimum brightness setting
- Added 533Mhz as lowest frequency for cpu (from 800Mhz).
- Removed wifi dual band (device doesn't support 5Ghz).
- Compatible with microG/UnifiedNLP:
Permission for signature spoofing (don't give this to apps unless you know what you're doing).
Added location overlays for UnifiedNlp.
** 23/11/2016 **
Code:
- Fixed reported regressions. Unsure about the SIM one,hopefully it's fixed too.
** 21/11/2016 **
Code:
- Fixed modem battery drain
- Fixed FM radio (new app)
- Fixed camera (new app, Snap). As far as i've noticed everything's working under this app.
- Enabled Doze.
- Fixed operator name showing as numerical ID.
- Changed LTE label to 4G.
- November 5 security patch level.
** 09/11/2016 **
Code:
- Fixed wrong power accounting for bluetooth
- Updated wlan firmware blob
** 08/11/2016 **
Code:
- Fixed leds regression
- Fixed location battery drain
- FM radio kind of working:
(to hear sound you need to turn bluetooth on, you can turn it off again afterwards)
- Front camera isn't dark anymore but still crashes with HDR. Cam still has issues but is usable.
- Post processing daemon isn't crashing anymore, which was leading to some hiccups.
- Advanced reboot should be working for everyone now
- IRQ Balancing
- Added cne/dpm vendor libs. Haven't tested further so CNE might be working.
- Minor tweaks/fixes, some selinux stuff.
** 30/10/2016 **
Code:
- Correct variant should now be detected and multisim set up accordingly.
- Built without microG patch (which was incompatible with google apps)
** 27/10/2016 **
Code:
- Fixed camera. Had made a mistake while building previous rom.
(This is not a fix for the front camera darkness issue.)
Recovery Changelog:
**14/03/2017**
Code:
- Update to twrp 3.1.0
**21/01/2017**
Code:
- Update to twrp 3.0.3, fixes .img flashing.
- Removed superfluous mouse pointer.
- Updated kernel with current f2fs support.
Code:
I'm currently creating my first github account etc. As I find the time to clean up the commit history and set things up properly I'll update the post with links to the device tree and kernel sources.
I've decided to post now, perhaps prematurely, because I'm very limited on time I can spend on this (can't afford it). I'm also unsure if there's even many people interested. So the best way forward if there's interest is either other people joining in and carrying this further, or supporting development with some donations.
Donations:
So far got 9 donations.
$50 < Total donations < $100.
Thanks to anyone who's donated and has shown appreciation!.
reserved.
Cool nice to see devrlopment to the 4.7 idol, I'm still waiting for the official marshmallow update (europeu representativas on Twitter and Facebook keep saying its coming) but if that takes too long I might get to use this rom
wow, i never thought that we will ever get cm13! thank you for your hard work! please, don't give up!
Rom is Very good.
downloading it now, i'll have time to flash the rom tonight
does xposed work?
basic functions like phone, sms, 2g, wifi work without any problem?
what about battery?
jani0417 said:
downloading it now, i'll have time to flash the rom tonight
does xposed work?
basic functions like phone, sms, 2g, wifi work without any problem?
what about battery?
Click to expand...
Click to collapse
I noticed I made a mistake on this build and as such the camera is broken. I'm gonna make a new build in a couple hours.
Never tried xposed.
Basic functions are all working for me. At least for the 6039Y I think it should work but we'll find out if people leave feedback. My guess is that it's probably working, with the exception of maybe dual sim variants.
Wifi should be working. Qualcomm CNE isn't, and I'm unsure if I even want it as a feature, need to research on it.
I haven't thought of a way to measure battery performance but I'm using it on my phone daily. If it's worse than it should be it's not by a very large margin. I also haven't run any kind of benchmark. (Too early for that in my opinion).
Thx,
for your work on CM13 for 4,7" Variant. If you upload new build with fixed camera i will test it on my europe 6039Y and leave feedback here.
Have a nice day
alecbl said:
I noticed I made a mistake on this build and as such the camera is broken. I'm gonna make a new build in a couple hours.
Click to expand...
Click to collapse
thank you, i'll check it tonight before flashing. i'd do it now but i'm waiting for important calls
Basic functions are all working for me. At least for the 6039Y
Click to expand...
Click to collapse
perfect i also have an 6039Y (2AALWE7)
Wifi should be working. Qualcomm CNE isn't, and I'm unsure if I even want it as a feature, need to research on it.
Click to expand...
Click to collapse
as for me, i hate it.
i'm using profiles to make sure that when my wifi is on, data is off and vice versa. earlier i had surprising phone bills because of this feature :silly:
I haven't thought of a way to measure battery performance but I'm using it on my phone daily
Click to expand...
Click to collapse
perfect :good:
and again: THANK YOU :good:
Updated original post. Cam should be working now.
Thank you very much! I really liked the hardware, but missing the MM update. But CM13 is even better:good::good:
First time I got into a bootloot updating from CM12.1, had to change data and cache filesystem back to ext4, don't forget.
Gonna test it now, hopefully you can merge the latests @Unjustified Dev commits when he makes them public aswell
Phantom410 said:
First time I got into a bootloot updating from CM12.1, had to change data and cache filesystem back to ext4, don't forget.
Gonna test it now, hopefully you can merge the latests @Unjustified Dev commits when he makes them public aswell
Click to expand...
Click to collapse
Yes, I haven't enabled f2fs support yet. I intend to do it at some point. Pivoq had a kernel source tree in which he updated f2fs, supporting xattr etc. I haven't figured out where did he import those changes from yet. I wanted to do the same, but didn't want to import from him because that's not being kept in sync with upstream.
What commits are you talking about?
Xposed work perfectly.
Nice,
i have installed at this time incl. xposed , but without gapps. After first setup all OK. In the next days i test with all my apps and give you feedback. I`m hopefully. :good:
This is the greatest thing to ever happen to my Idol.
Thank you so much. Root and Xposed work fine. Latest version of Busybox installed fine.
Flashed Gapps Pico successfully.
Seems to be really smooth but time will tell. Themes work perfectly.
Using the advanced reboot menu to try and reboot into recovery doesn't work. Granted i'm not using the recovery linked in the original post. I'm using the recovery made by DeckerSU.
What recovery is linked in your post? Is it Cyanogenmod recovery or TWRP and if so, what version?
EDIT: Not even "Adb reboot recovery" will get the device to boot into recovery anymore. Hmm...
Wow, just wow. You did more in one day, than some of the "DEV's" here for their entire time good job man.
Sparkey159 said:
This is the greatest thing to ever happen to my Idol.
Thank you so much. Root and Xposed work fine. Latest version of Busybox installed fine.
Flashed Gapps Pico successfully.
Seems to be really smooth but time will tell. Themes work perfectly.
Using the advanced reboot menu to try and reboot into recovery doesn't work. Granted i'm not using the recovery linked in the original post. I'm using the recovery made by DeckerSU.
What recovery is linked in your post? Is it Cyanogenmod recovery or TWRP and if so, what version?
EDIT: Not even "Adb reboot recovery" will get the device to boot into recovery anymore. Hmm...
Click to expand...
Click to collapse
I have a very good idea of why that's happening. Did you happen to change your bootloader at any point? Alcatel's kernel source has a non standard way of handling reboot, what's more, it's not exactly the same in their lollipop vs marshmallow sources.
The recovery in the post is twrp 3.0.2 with support for encryption and adopted storage. It's using the same kernel, so if you flash that recovery what I expect will happen is that you wont be able to reboot into bootloader or reboot into recovery from the recovery either. The decision of where to reboot into is done by the bootloader and precedes the kernel, just so you know. Changing the recovery can't fix that. Of course you can always do so using power+volume keys, until I fix it.
alecbl said:
I have a very good idea of why that's happening. Did you happen to change your bootloader at any point? Alcatel's kernel source has a non standard way of handling reboot, what's more, it's not exactly the same in their lollipop vs marshmallow sources.
The recovery in the post is twrp 3.0.2 with support for encryption and adopted storage. It's using the same kernel, so if you flash that recovery what I expect will happen is that you wont be able to reboot into bootloader or reboot into recovery from the recovery either. The decision of where to reboot into is done by the bootloader and precedes the kernel, just so you know. Changing the recovery can't fix that. Of course you can always do so using power+volume keys, until I fix it.
Click to expand...
Click to collapse
I don't think I've changed the bootloader since I got the device. I don't have access to fastboot commands. My idol was a O2 branded one that I brought quite recently. I haven't been able to use Petrov.0's method of restoring the fastboot commands either. I don't really mind losing the ability to reboot into recovery from the system since its worth it for Android Marshmallow.
Thanks, I'll be using your recovery from now on too since its more updated. :good:
Flashed, tested
-unlocked 6039Y 2AALWE7
-tap to wake/sleep works
-sms, phone, wifi works
-gapps works
-front camera in photo mode really dark, in video mode is okay
-tried Google Camera from play store, it crashes everytime, when switching from video to photo mode
-so far I love this rom
https://download.mokeedev.com/?device=zoom
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.
stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?
Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?
linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)
has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing
Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.
The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st
bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.
Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?
Note: Make sure your phone is decrypted and do not turn on the secure boot feature where you need to put in your pattern to boot system!
So as I'm currently without a PC and can't restore the stock images I wanted to share the best method for using Android 10 I've found.
Get the latest phh gsi image v210 is what I used.
Get the latest Lineage OS GSI 17.1 image.
Get the Trinity v2 kernel (beta is what I used).
Get the latest Android 10 pico or nano gapps from opengapps. (I used nano)
Boot to recovery and factory reset.
Install phh gsi IMG to system. When finished don't reboot. (I do this to keep security patches as up to date as possible)
Install LineageOS IMG (DIRTY FLASH).
Install Trinity Kernel to Boot
Reboot system
(Optional once you fully boot you can reboot recovery and flash the f2fs zip from Arter Kernel then reboot recovery and wipe data. When you reboot system you may freeze during setup just reboot by holding the power in until the phone restarts. It will finish setup this time.)
Reboot recovery and flash gapps. If you get error 70 resize the system partition. It will work after resizing once or twice.
When it boots you can do your traditional setup.
Reboot recovery and Install Magisk v20.3.zip
Reboot system and Install Magisk Modules Busybox for Android NDK and Magisk Hide Props Config.
Install terminal app of choice following Reboot
Type su in terminal and hit enter
Type props in terminal and hit enter
Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Congratulations you now have LineageOS Android 10 and are passing safetynet.
Notes:
You can Install v4a if you want.
I highly suggest installing the l'speed module from Magisk as it stabilizes the freezing/kernel.
You can also Install EdXposed and the beta for GravityBox Q ... Still passing safetynet.
Logo++ will fix your Razer logo on the rear of device.
Bluetooth works fine as does everything I've tested.
Downloads needed:
Latest phh GSI for AOSP Android 10
Latest LineageOS 17.x GSI Image
Trinity Kernel (v2)
Magisk v20.3
Pico or Nano GAPPS from OpenGapps
Optional:
V4A (requires the Magisk Module Audio Modification Library)
EdXposed Riru - Core (Magisk Module)
EdXposed - Sandhook Beta / Canary (Installed from manager)
EdXposed - Latest Manager (do not use Taichi)
GravityBoxQ Beta (gives you a lot of customization like the battery icon in statusbar)
Logo+
LSpeed Module for Magisk (lspeed-master.zip)
F2FS_FSTAB.zip from ArterKernel Thread
***Note*** this isn't flawless but when using the LSpeed Magisk Module it's very close**"
**"" LineageOS Freezes every now and then where the AOSP GSI doesn't but I can't get the AOSP to pass safetynet***
Screenshots
Note I changed the font to Comfortaa via Magisk Font Changer Module
SafetyNet
Magisk modules I personally use. Ignore older versions of the same module.
Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Click to expand...
Click to collapse
Will game booster work in cortex app?
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.
Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Try moving the ims.apk to /vendor/overlay and see if that works.
Generic123. said:
Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.
Click to expand...
Click to collapse
Generic123. said:
Try moving the ims.apk to /vendor/overlay and see if that works.
Click to expand...
Click to collapse
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.
Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Reznor7 said:
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.
Click to expand...
Click to collapse
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going
JDBarlow said:
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going
Click to expand...
Click to collapse
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on patched versions of popular GSIs that are more suited for the hardware of the RP2:
f(x)THaxxorX said:
What my real plan is to make patch into the GSI Sources before Building it.. Those patches include voLTE fix and other features. Integrate APTX coming from Razer GSI system.img.. and many more..
Click to expand...
Click to collapse
Generic123. said:
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on a patched version of popular GSIs that are more suited for the hardware of the RP2:
Click to expand...
Click to collapse
Oh nice!
I'll try to contain myself and be a little more patient
So true, I can just imagine the time spent to be a developer for so many devices that are out there!
Happy Valentine's Day
Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?
Reznor7 said:
Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?
Click to expand...
Click to collapse
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.
Generic123. said:
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.
Click to expand...
Click to collapse
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I have the same problems on ArrowOS(the fingerprint sensor problem is pretty rare. The speaker issue is really annoying, but it only happens at low volumes), but I guess it depends on how much you're willing to take. If you want to keep to use Q GSIs, our best option is just to wait for patched GSIs by f(x)THaxxorX that might be coming out at some point(Soon™).
Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I think the speaker itself might have issues as I even had this issue with Android 9 GSIs, from what I remember. At first I suspected buffer-related issues but after some testing it doesn't seem to be the only issue. Setting the media volume to at least 50% would allow most of the audio to get out of the speaker, but at max volume the speaker can be really loud (to the point that I feel the speaker could be potentially damaged) so I usually set it to at most 80% when I need to place the phone a bit far from where I am.
Also, I haven't gotten aptX working on Android 10 GSIs due to a strange null pointer dereference bug which would crash the entire Bluetooth stack. Only SBC works as intended. As I noticed that the author of gjf_bt Magisk module (which adds aptX libraries as well as SBC tweaks) recently blacklisted Android 10 and onwards, I think the issue might have more to do with the Android 10 system itself.
Hey! Can anyone confirm if LDAC is working on this? I have never rooted a phone before just doing it to enable LDAC. Also, does this OS support setting for Refresh rate?
I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.
Lorelily said:
I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.
Click to expand...
Click to collapse
It's a known issue, and unfortunately there is no reliable fix yet.
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)