yashsingh1/xdaforums huggingface dataset:
[Xiaomi Black Shark 2 Guides, News, & Discussion] 2dogs16:
I guess the black shark 2 is just left in the dust no Android 11 no more security updates just a garbage overpriced phone
[Xiaomi Black Shark 2 Guides, News, & Discussion] peety02:
Not sure what market you are referring to, but the BS2 is rather reasonably priced comparing other vendors releases over the past year. Also, BS is about to release (or did by now) a successor. I assume software development will come to a hold for the BS2
[Samsung Galaxy S8 Questions and Answers] Andr01d.Usr:
Why does fast charging work on some Custom Roms while it doesn't on others?

It worked on Lineage os, Hades Rom.

It didn't on Havoc OS, Bliss Rom, CrDroid and Corvus.

I have a rooted Samsung s8 (SM 950 FD).

Is there a way to force fast charging?
[Samsung Galaxy S8 Questions and Answers] speedson:
Hi...

cause its like you said...thats different Roms :)

solong

speedson 🤘 🙃 🤘
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] danielad200:
Hey

I am with s20 ultra snapdragon version every time that i am going outside to direct sun screen become dimmed instead more bright

Adaptive brightness is on

Another thing..when battery is 5% battery drained faster then usual..please help
[General Questions and Answers] staru22:
Hello!

Sorry if I post in the wrong section.

I have a broken Xiaomi Mijia mjjgtyds01fm 4k, the projector starts with the fans on maximum, no screen at all and doesn't respond to the remote. Someone told me that the motherboard is at fault, can anyone confirm this or it can be something else?

Anyone else had this problem with their projector and fixed it?

Thank you.
[Touch Pro, Fuze General] pikoman:
Hi all!

I use mac and use missing sync to sync the address book to my Touch Pro. Everything is ok but when I try to add a contact on 'People' tab of TouchFLO3D and it's crashed. Any solution to solve this?

Thanks in advance.
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] Arulebin:
CipherOS is a Android Custom OS, Based On AOSP & Fueled by Lineage, Striving to Provide its Users , A Clean , Bloat free & Sturdy Experience with Minimal Customisation !

/* Your warranty is now void or maybe not?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

With the release of CipherOS Crypto , We Ensure that Every OFFICIAL Device remains Up-to-date with latest Patches , Asap its been released by Google !

Download it from SourceForge!

​

The people working towards bringing you this release are:

Aryan Sinha

Lokesh Vazirani

Jaishanav Prasad

Sakthivel Nadar

Jamie Ho

Bhenom

1. Download the ROM, Gapps, Magisk (Optional).

2. Wipe System, Data, Dalvik, Cache.

3. Flash the ROM, GApps (Optional), Magisk (Optional).

4. Reboot and Enjoy.

We would like to thank the following ROMs, because if they weren't here, we couldn't be there too <3

LineageOS

ProjectSakura

POSP

SuperiorOS

Pixel Experience

The Styx Project

Fusion OS

Source Code:

ROM Source

Device Source

Kernel Source

Donate:

PayPal​
[Moto G7 Power Questions & Answers] Kilo__:
Edit: Found my own solution and did a quick write up in a reply down below. https://xdaforums.com/t/moto-g7-ocean-bricked-recoverable.4278783/post-85038459

Hi Everyone,

I've found posts that have parts of my issues, but not all of them all together. I fear I might have a true hardbrick on my hand.

I'm not a rookie when it comes to custom roms and rooting, so feel free to over more indepth advice. I had the phone on Lineage 17.1, rooted, but I hadn't put Gapps on. I decided I couldn't live without GAPPS, so I downloaded Lineage 18.1, the most recent twrp, the most recent MindTheGapps, and went to following the guide, just in case.

I didn't wipe the system and installed the lineage 18.1 update, rebooted, and it worked like an inplace upgrade. It overwrote the recovery so I had lineage recovery and OS, no root. I rebooted to fastboot, used fastboot boot *twrp path*, and got into twrp. As I was following the instructions, the pre-setup said I NEEDED to run the copy partitions script, and that this step "IS NOT OPTIONAL". After sideloading the copypartitions script, TWRP said a reboot was required. I chose reboot to recovery, but got a different fastboot mode than I'm used to instead. Here's the state of the phone now:

AP Fastboot Flash Mode (Secure) [Not the fastboot I'm used to seeing]

Baseband: *empty*

Serial Number: (7 digits)

OEM locked

no OS

No recovery

FlashBlank - <Waiting for Device>

Trying to flash OEM stock ROM

oem fb_mode command fails, " " returned error

Cannot flash any .img because not in the right mode

Trying to boot to twrp - failed, bootloader locked

Trying to flash twrp - failed, bootloader locked.

Lenovo / Motorola Recovery assistant sees the phone as a model "[]" and won't proceed with "the wrong device selected"

Any one have any ideas? I'm not sure how this got so horribly messed up. The only thing I can think is the upgrade to 18.1 locked the bootloader, and the copy partitions went the wrong way and overwrote the active slot.
[Moto G7 Power Questions & Answers] Kilo__:
(bootloader) version: 0.5

(bootloader) version-bootloader: MBM-2.1-ocean_retail-16222030b3b-200909

(bootloader) product: ocean

(bootloader) board: ocean

(bootloader) secure: yes

(bootloader) hwrev: PVT1

(bootloader) radio: 1

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001

(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F

(bootloader) cpu: SDM632

(bootloader) serialno: 73080661

(bootloader) cid: 0xDEAD

(bootloader) channelid: 0x00

(bootloader) uid: 0000000000000000000000000000

(bootloader) securestate: oem_locked

(bootloader) factory-modes: disabled

(bootloader) iswarrantyvoid: n/a

(bootloader) max-download-size: 536870912

(bootloader) reason: Failed to initialize partition table

(bootloader) imei:

(bootloader) imei2:

(bootloader) meid:

(bootloader) date:

(bootloader) sku:

(bootloader) carrier_sku:

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sbl1.git: sbl1.git

(bootloader) rpm.git: rpm.git

(bootloader) tz.git: tz.git

(bootloader) devcfg.git: devcfg.git

(bootloader) keymaster.git: keymaster.git

(bootloader) cmnlib.git: cmnlib.git

(bootloader) cmnlib64.git: cmnlib64.git

(bootloader) prov.git: prov.git

(bootloader) aboot.git: MBM-2.1-ocean_retail-16222030b3b-200909

(bootloader) frp-state: no protection (err)

(bootloader) ro.carrier:

(bootloader) current-slot:

(bootloader) running-boot-lun: must + g->mlen

(bootloader) running-slot:

(bootloader) slot-suffixes: _a

(bootloader) slot-count: 1

(bootloader) slot-successful:_a: INVALID

(bootloader) slot-successful:_b: INVALID

(bootloader) slot-bootable:_a: INVALID

(bootloader) slot-bootable:_b: INVALID

(bootloader) slot-retry-count:_a: unknown

(bootloader) slot-retry-count:_b: unknown

(bootloader) pcb-part-no:

all: listed above

Finished. Total time: 0.121s
[Moto G7 Power Questions & Answers] Kilo__:
> fastboot oem blankflash

> blank-flash.bat

This has given me a fastboot I recognize and now see a correct serial number and see that flashing is unlocked! I think this is it.
[Moto G7 Power Questions & Answers] Kilo__:
Solution: The following is how I solved my issue. Everything I needed was found in the Stickied help guide

Assets you will need:

I got the OEM Stock Firmware from here, using the lolinet link. https://xdaforums.com/t/index-motorola-stock-firmware.4222605/

I got the blankflash from here https://xdaforums.com/t/booted-from-slot-b-through-twrp-now-hard-bricked.4126001/post-82962207

Steps Taken to Fix:

Ran > fastboot oem blankflash (found here) https://xdaforums.com/t/index-motor...mware-unbrick-your-moto.3042687/post-84347359

Ran the following code (with edits to match the firmware files) found in this help thread: https://xdaforums.com/t/guide-flashing-motorola-firmware.4042039/

fastboot getvar max-sparse-sizefastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

This got me back to stock and I was able to start over and re-flash to Lineage with GAPPS. I'm leaving this full solution up for anyone who might have my same issue.
[Zenfone 2 Laser Android Development] adazem009:
Resurrection Remix Q

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

​

Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome ​

combination of performance, customization, power and the most new features, brought directly to your Device.​

​

Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!​

Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.​

​

Bugs:​

Same as in LineageOS 17.1 - loudspeaker is always on during calls.

Make sure you have a custom recovery installed(TWRP is the preferred recovery)

Download the latest Resurrection Remix Rom & the latest GApps package

Boot into recovery

Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution

Flash ResurrectionRemix Rom

Flash Google Apps package(Optional)

Flash Magisk Root(Optional)

First boot may take up to 10 minutes.

ROM Download (Z00L)

ROM Download (Z00T)

GApps

Resurrection Remix Source

Device Source (Z00L)

Device Source (Z00T)

Common Device Source (for both devices)

Kernel Source

Vendor Tree

XDA Developers

LineageOs Team

AICP

Crdroid

AOSIP

DU

Xtended

Evolution X

Bliss

Omni Team

Asus-MSM8916 team

And Of Course To All The Supporters, Donators And Users

Join our Telegram channel : https://t.me/resurrectionremixchat

If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.

Download the

MatLog

app from the Play Store.

After downloading the MatLog app, go to the app settings, and change the log level to Debug.

Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.

Copy and paste the entire log either to

Hastebin

or

Pastebin

Save the log, and copy and paste the link into the thread with a brief description of the error.

​

Device: Asus Zenfone 2 Laser/Selfie (Z00L/Z00T)
[Zenfone 2 Laser Android Development] jimjack12:
Hi adazem009 and thanks for the hard work.

As for the problem with the speakerphone, could you find the log file made with matlog useful? If so, on Saturday afternoon as soon as I get back from work, I could post it.

Or if someone else can post it these days. One last thing: I flashed ReikaRin's Tsurara kernel, but the speakerphone problem is always there.

Thanks so much
[Zenfone 2 Laser Android Development] eycecandy:
I can provide the matlog if needed but only if its useful
[Zenfone 2 Laser Android Development] adazem009:
It should be helpful, but I think it's better if you use adb shell logcat on a PC (with USB debugging enabled).
[Zenfone 2 Laser Android Development] jimjack12:
OK thank you very much

Hi eyecandy,

could you be kind enough to post the log file these days, as advised by adazem009, so as to speed up development?

Thanks so much
[Zenfone 2 Laser Android Development] eycecandy:
---In order to test I have installed this rom with bitgapps and magisk

Till yesterday my calls were working fine but today I encountered an issue(just now) with my service provider it takes time to solve that

Whatsapp calls are working fine (no loudspeaker problem as of now)-----

--Rom is great

--Sound is working

--battery backup - by the time I booted the os I was having 76 percent battery

by the time I completed my backup through migrate and rebooted the device it went to 30 percent!

--APP Recents and system is lagging

--Lockscreen also causes lag many times which is huge

matlog of the lag for app recents

--- https://pastebin.com/pEvk7gPu

(i can give USB debugging (if wanted) after a few days because there is some problem with my pc)

Thanks for your hard work !
[Zenfone 2 Laser Android Development] adazem009:
Update - 05/22/2021

Download (Z00L)

Download (Z00T)

May 2021 security patches.
[Zenfone 2 Laser Android Development] Loupluttle:
do you use telegram? if yes, I can provide logs faster and keep taking them for bug fixes. I have a spare device. We can use asus zf2 laser group or seperated one for bug fixing and stuff
[Zenfone 2 Laser Android Development] adazem009:
Yes, I'm Korko123.
[Zenfone 2 Laser Android Development] slowpoke.chicken:
Hey adazem009!

First of all Thanks a Lot for working on a this custom ROM for this old device!

A few month ago I was just searching through the XDA Forums and came across LineageOS 17.1[Z00L][Z00T] by markkiths. I gotta admit, I definitely wasn't expecting to find a Android 10.0 ROM for this phone. From then I started using it. But markkiths recently stopped working on it. So, I was a little sad.

But then you came to the rescue! ❤️

First with Havoc-OS v3.12 and now Resurrection Remix.

I am not a developer but I do appreciate sincere efforts from enthusiastic people like you. So, once again, THANK YOU VERY MUCH!

I have a Z00L and, I am more than happy to help out with any king of bug(s) testing. Here's my Telegram.

Best of Luck (y)

Hope this one becomes a master piece of a ROM.
[Zenfone 2 Laser Android Development] adazem009:
I think they're working on LineageOS 18.1 (Android 11) for Z00ED/Z00RD and maybe for Z00L right now, but I'm not sure.
[Zenfone 2 Laser Android Development] slowpoke.chicken:
Hey did you create a group for bug fixing? If yes I would like to help as well.
[Zenfone 2 Laser Android Development] slowpoke.chicken:
Oh! You have any link to the source? Where should I look for? :confused:
[Zenfone 2 Laser Android Development] adazem009:
There's an Asus-MSM8916 group and I've seen some progress there. But, I'm not sure if I can invite anyone there.
[Zenfone 2 Laser Android Development] slowpoke.chicken:
Then I guess I will tighten my seat belt and wait for LineageOS 18.1. In the mean time I am gonna enjoy this ROM. Let me try it out for a few days then I will hopefully make a list of bugs with logs files.

Thanks for the super quick responses by the way!
[Zenfone 2 Laser Android Development] eycecandy:
The battery is draining too fast when compared to hovoc Is this due to the updation of my twrp to the lastest one or any rom problem ??

ALSO should post screenshots of this beautiful rom?

@adazem009
[Zenfone 2 Laser Android Development] adazem009:
I don't have Z00L nor Z00T, so I can't take screenshots. RR is different than Havoc-OS and some processes are probably spamming the logs, which drains battery. Maybe I can debug it on Z00ED.
[Zenfone 2 Laser Android Development] eycecandy:
Some screenshots from zool
[Zenfone 2 Laser Android Development] Loupluttle:
@adazem009 I couldnt find Korko123, so I created a new group for testers and you to fix bugs as soon as possible, here's the link https://t.me/joinchat/dARyuutiGXM2MGFk
[Zenfone 2 Laser Android Development] zenfone selfie:
hey, a z00t user here!

i told this to markkiths and telling you know since you're the active developer.

"Loudspeaker issues during calls." this bug is not happening with the icey kernel.

my cpu is defective and i need a special build with 1.1ghz on little cores removed to be able to boot properly, i don't have the 1.3(d) build, still using 1.3(c). maybe you could try using icey as the default kernel and develop over it?

i didn't try the rr yet, would icey 1.3c work with this rom? i was taking my midterm exams and now my finals are coming. i will be able to test it in a couple of weeks.

can you build a special version of the default kernel for me if you can run the build again?

these are the modified files https://drive.google.com/file/d/1cPqpcd9cbgBpfoCHjRbbOWD2A3HZ_cTd/view

i'm having a laggy ui and random reboots with 1.1ghz on little cores and can't even complete the first setup progress without like 10 crashes.
[Zenfone 2 Laser Android Development] FulipYogow:
I'm a Z00T user. I've switched from Havoc OS to this one, but again, I'm still having a problem where videos have no sound. Am I doing something wrong?
[Zenfone 2 Laser Android Development] adazem009:
Sure, if it works on LineageOS 17.1, it's going to work in RR.
[Zenfone 2 Laser Android Development] Aryan@123:
Q
[Zenfone 2 Laser Android Development] Aryan@123:
P
[Zenfone 2 Laser Android Development] adazem009:
Update - 06/23/2021

Download (Z00L)

Download (Z00T)

June 2021 security patch.

Switched to ICEY-S custom kernel.

Fixed loudspeaker issues.
[Zenfone 2 Laser Android Development] adazem009:
Update: This build seems to cause bootloops (reported on Z00L). In case you're already in a bootloop, flash the previous build without wiping data (dirty flash).
[Zenfone 2 Laser Android Development] tandlion13:
Hello,

Boot loop on Z00T also,

" RROS-Q-8.7.0-20210622-Z00T-Unofficial "

Hope to see the fix soon,

Thank you very much for your work.

---------------------------------

Meanwhile, gonna install one of the previous builds,

Would you recommend Resurrection Remix or Havoc OS?

Thank you.
[Zenfone 2 Laser Android Development] tandlion13:
Hello,

A little update,

I tried installing " RROS-Q-8.6.9-20210521-Z00T-Unofficial "

Most stuff works fine,

Have a little problem with installing Netflix app via Play store,

It says " Your device doesn't support the application " or something,

Haven't tried installing with Netflix apk yet,

Thank you.
[Zenfone 2 Laser Android Development] adazem009:
I think it checks SafetyNet, but I'm not sure. Try a SafetyNet test first.
[Zenfone 2 Laser Android Development] tandlion13:
Hello,

I tried the SafetyNet Test app,

Got a "Failed" result,

Details :

Safty Net Request : success

Response signature validation : success

Basic Integrity : fail

CTS profile match : fail

Is this how it's supposed to be on this build?

Or is it something wrong on my side?

Thank you.
[Zenfone 2 Laser Android Development] adazem009:
I think the devs didn't focus on SafetyNet. Enable Magisk hide if you have Magisk root.
[Zenfone 2 Laser Android Development] adazem009:
Note about latest builds:

The last 2 builds for Z00L and the last one for Z00T don't boot. If you've flashed it by accident, simple dirty flash the previous build.

Last working build (Z00L)

Last working build (Z00T)

I'll be uploading new builds in the next days. I need someone to test if they boot as I don't have Z00L nor Z00T.
[Zenfone 2 Laser Android Development] adazem009:
Update - 06/30/2021

Download (Z00L)

Download (Z00T)

Switched to ICEY-QZ kernel, should boot now. If not, dirty flash last working build.
[Zenfone 2 Laser Android Development] PV-001:
Booted but sound issue remains.
[Zenfone 2 Laser Android Development] adazem009:
Some people got it fixed by rebooting a few times. Maybe that could work.
[Zenfone 2 Laser Android Development] PV-001:
No luck but thx. anyway.
[Zenfone 2 Laser Android Development] jimjack12:
Hi adazem009

Thanks for the hard work; the last rom is installed, but there is always the problem of the speakerphone that cannot be deactivated during calls.

Thanks so much
[Zenfone 2 Laser Android Development] 10HAZARD:
how to set SeLinux permissive to enforcing in this rom??
[Zenfone 2 Laser Android Development] PoopMcDougan:
Hello. Ive installed latest build 20210628 153542 in z00t and I get no sound from the speakers. I have to use headphones to hear.

Now that I think about it I had the same issue with this phone (ze601kl) on a pie rom and i had to flash a kernel patch and libs. I wonder if at least the libs could be replaced with those
[Zenfone 2 Laser Android Development] adazem009:
The attached ZIP file should do it, but I'm not sure if RR will boot after that.
[Zenfone 2 Laser Android Development] adazem009:
I'm not going to fix device specific bugs as I don't have Z00L nor Z00T. My work actually depends on that of the other developers working on these devices. But I'm not sure if they still work on them, I think we need someone to help with the bugs.
[Zenfone 2 Laser Android Development] adazem009:
Update - 07/27/2021

Download (Z00L)

Download (Z00T)

July 2021 security patch.
[Zenfone 2 Laser Android Development] adazem009:
Update - 08/04/2021

Download (Z00L)

Download (Z00T)

Fixed SELinux denials.

SELinux is now enforcing.
[Zenfone 2 Laser Android Development] ghazh:
Unfortunately I was unable to install the latest rom (08/04/2021) on Z00L, I cannot open internal storage it's empty. I've done a full wipe before installing the rom
[Zenfone 2 Laser Android Development] adazem009:
Did it boot successfully? If it's stuck in a bootloop, try formatting data and cache.
[Zenfone 2 Laser Android Development] ghazh:
It did boot successfully, but first of all, opening "Files" shows an empty nothing for Internal Storage and then when I try to download anything with "Browser" the browser crashes and ultimately I can't have access to the storage via MTP on my PC either.

After failing to install this, I installed CrDroid with no problem.
[Zenfone 2 Laser Android Development] adazem009:
It might be because of SELinux. Please get logs using adb shell logcat > logcat.log command and send the logcat.log file.
[Zenfone 2 Laser Android Development] ghazh:
It indeed is, I just installed the previous ROM (RROS-Q-8.7.1-20210727-Z00L-Unofficial.zip) and I have no problem with that ROM either.
[Zenfone 2 Laser Android Development] adazem009:
Ok, I need logs when you use that file manager, it'll help me with the fix.
[Zenfone 2 Laser Android Development] ghazh:
Sent you the log in a private conversation.

Thanks for the effort!
[Zenfone 2 Laser Android Development] adazem009:
Update

Download (Z00L)

Download (Z00T)

August 2021 security patch.
[Zenfone 2 Laser Android Development] ghazh:
Thanks a lot! Are SELinux changes reverted?
[Zenfone 2 Laser Android Development] adazem009:
I'm not going to revert anything. File manager denial will be fixed in the next build