yashsingh1/xdaforums huggingface dataset:
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] imdeepusingh5:
Review after using 3 days...

Its 3rd day and and i am going to review this rom

Pros-

1. smooth ui and stable ROM

2. Battery backup is far better than stock rom and yu open os ROM.

3. Many handy features included like colour engine and privacy guard

4. No heating or lagging problem

Cons.-

1. Slow charging (approx taking 4 to 5 hours to 100% charging )

2. phone vibration is not working anywhere.

3. Gallery app is not working properly

Please fix that issues॥

Some Suggestions -

Please include some features in new updates...

1. Auto Call Recorder (like ASUS dialer )

2. In built Root Access option (like cyanogen)

3. Font changer (like Samsung Phones)

4. Make the colour engine applicable on app drawer and main menu too..

Final ratings- 4.8/5

Thanks to developer team for hard work..
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] debaadak:
Demanding too much, it was the final build.
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] imdeepusingh5:
Is that mean , there will no update now?
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] Dush4711:
May be for android 8.

But not for 7.1.2
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] iamsj7:
Don't expect More from the 5k device

I can't do any thing regarding your suggestion.

Cz iam not the source maintainer for ViperOS Project to add them in the source.

Demand to viperos team.

Suggest Them.

Your suggestions are like a cocktail..

All Roms have some unique features u can't get all those in a one Rom.

Better u make your own source with that features :)

Gallery is working fine.

Use hyper kernel for charging issue .

Once calibrate it.

Thanks for your review.<3
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] iamsj7:
#Update #Announcement

No more N builds.
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] sameer419:
Rom is smooth but heating is too much.

Clean flashed final 3.1.1 with pico gapps and hyper kernel.

Slow charging exists in stock (linage) and as well as hyper kernel.

Suggest me any custom kernel with version no too.
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] Coolboyshubham.:
How can I change the theme...
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] Criston:
Use subtratum for theming

The inbuilt color engine is just for changing the primary and accent color
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] iamsj7:
update

changelog:

-selinux is enforcing.

-lib light update

-fixed brightness bug some people were facing. :)
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] Rup_R:
We need Android O so please upgrade your self..
[Yu Yunique ROMs, Kernels, Recoveries, & Other Deve] Criston:
Lol U Can't Say Like This U Can Just Request Him
[T-Mobile LG G4] MTN927:
I need to root my G4 on TMO. It's on 6.0 and all I have done is enabled dev options - usb debugging- enable OEM in the menu. I've rooted devices before but it's been awhile. I obviously need to start from the beginning here, I assume by unlocking bootloader. I can't find any thread to start with as they are either outdated or for a different version of Android, or I just couldn't find one. I would really appreciate it if somebody could just link me to the thread/guide I need to be in! Thank you so much if you can!
[T-Mobile LG G4] raptorddd:
note it can only be unlock in this versions.. ill place them from oldest to newest 20i-(20p-20q-20r-20v) if you in any of the versions in parenthesis doent downgrade tp 20i... 20i is antirollback V2 all other in parenthsis is V3 you can switch bak and forth from 20p-to 20v.

well you have developers option enabled and OEM unlock

minimal adb. fastboot install it follow instructions. https://xdaforums.com/showthread.php?t=2317790

download TWRP from here h811 and h815 same app for both. https://twrp.me/devices/lgg4.html

have 2 copies on in SD card other in minmal adb fastboot folder.

Bootloader OEM Unlock + Root:

Starting with the Android 6.0 20x bootloader it has to be unlocked, sorta like a Nexus, with fastboot. Previously only 'OEM Unlock' had to be toggled in Android Developer settings for TWRP or custom boot images to work.

download superSU

connect usb cable to phone.. then go to location folder of minimal adb.. ezample C:programfiles/minimal.

then in the folder in a empty space press shift key.. and right click on mouse button . you should see open command prompt from here.. select it.

a new window should appear. enter this command

adb reboot bootloader and see screen for confirmation to acsess phone select yes.

if it doesnt boot into bootloader try command again

once booted youll see small letter on phone screen then enter command

fastboot oem unlock (this wipes ALL data!!)

it should restart phone. and optimize all apps...and bootloader should unlock

do same for twrp.... make sure command name of twrp is the same in the file example command is like this..

fastboot boot twrp-2.8.7.1-h811.img and file TWRP is say.. twrp.30.00 it wont work rename either command or files or both and name it twrp.img same in command. once it boot into twrp .. go to install then press button that says image. so the twrp.img you have in sd card appears/ select it then on next window tick recovery. swipe left to install permanently and you are done. flash new rom or superSU.

hope i make sense good luck
[T-Mobile LG G4] MTN927:
I'm on 20v, so I should be good.
[T-Mobile LG G4] raptorddd:
yes . thats latest version.. thats good.
[T-Mobile LG G4] MTN927:
OK, I got twrp installed but the two SU's I've flashed don't work. I have SU installed, it needs to update binaires, I try that but it fails every time. Root checkers say I'm not rooted. I think I'm using the wrong SU zip. Any help? Your guide was great btw.

EDIT: OK, now it says i am rooted but I can't get the SU binary to update. It fails every time and then asks me to reboot and try again. Any ideas?

UPDATE: Ok, the SU binary finally updated successfully! I think I'm all good! Gonna check out some custom ROMS later. Any recommendations?
[T-Mobile LG G4] fuzzy_:
Lineage

https://xdaforums.com/g4/development/rom-cyanogenmod-13-0-lg-g4-t3477475
[Samsung Galaxy Core Prime Themes, Apps, and Mods] Patrick_in_SD01:
I have another boot animation for the Core Prime, but it should also work with any Samsung phone that uses .qmg boot animations.

***Requirements***

Backup of your old/stock boot animations just in case the new one doesn't work

Rooted device

File Explorer (Make sure it has root permissions)

***Instructions***

Step 1: Download the attached zip below and extract it to your SD card (or your device storage).

Step 2: Go to your file explorer app and navigate to /system/media, scroll down and you should see three QMG files: bootsamsung.qmg, bootsamsungloop.qmg, and shutdown.qmg. Delete them after you've backed them up.

Step 3: In your file explorer app copy the extracted bootsamsung.qmg, bootsamsungloop.qmg, and the shutdown.qmg files from your SD card/device storage and then navigate to /system/media. Paste all three of these files in this location. Warning! Your phone will boot loop if you don't use the bootsamsungloop.qmg file!

Step 4: Reboot your phone. The boot animation should play as normal. If it doesn't check to make sure that you've followed the above instructions and try again, and post here if you need help with anything.
[Magisk] tomgaga:
Hi, I want to post this there for other people who have problems with safety net even when they don't have magisk installed but maybe tried it in the past.

Turned out my experiments with magisk in the past left some files in my data partition behind which makes safetynet fail.

I found them by going into twrp recovery, starting and adb shell and then executing find . | grep -i magisk

the two files i found were:

data/data/com.google.android.gms/files/backup_diff_script/com.topjohnwu.magisk

data/property/persist.magisk.hide

I deleted them with rm and safety net worked again.

I can also inform that for my phone (yotaphone 2): unlocked bootloader, custom modem and custom recovery does not matter at all for safetynet. But if your filesystem still contains traces of magisk somewhere, its a nono for google safetynet, pretty silly this road they are taking here.
[Magisk] Deic:
are you sure of /data/data/com.google.android.gms/files/backup_diff_script/com.topjohnwu.magisk? So, did it not fix deleting the /data/property/persist.magisk.hide (fixed in latest Magisk) only?
[Magisk] tomgaga:
No, I am not sure, I just deleted them both and then tested. So yes, probably just the last file that matters
[Magisk] emadmahdi:
Thank you tomgaga ... your post saved me big headache ... I found an option in magisk manager settings to "hide magisk from various detections" ... I just enable it and safetynet start to succeed again ...
[Galaxy Note 3 Q&A, Help & Troubleshooting] Blue Soul Slayer ♫:
When will there be a s8 rom port?

and

When long will it take for a note 8 rom port to come out after it has been released?

Extra Questions I have (https://xdaforums.com/galaxy-note-3/accessories/s-pen-styluses-t3639876)
[Huawei Mate 9 Questions & Answers] kubinski:
I cant figure out how to unlock my Huawei Mate 9 model MHA-AL00 Chinese phone. The ABD tools don't seem to work. There is no enable OEM unlock option in the developer options. I have the unlock code. Can anyone help me? I really want to root it.
[Huawei Mate 9 Questions & Answers] rbt001:
I had the same problem....

I had the same problem with my MHA-AL00. It just wouldn't accept the code no matter what I did. I did a lot research and finally found the solution. Surprisingly simple once you know it. I mean....it literally only takes 2 secs to fix.

Unfortunately, I won't be telling you how to fix it, because of your stupid remark. Have a nice day.
[Huawei Mate 9 Questions & Answers] ante0:
Did you enable USB debugging in developer options? You might have to toggle it a few times until you get the approve dialog on your phone. Make sure USB is plugged in.

As far as I know you only need that for AL00, there is no OEM unlock toggle.
[Huawei Mate 9 Questions & Answers] Lykeul:
Crap, he is serious ???
[Huawei Mate 9 Questions & Answers] Stephen:
Moderator Warning,

Thread has been cleaned, we have a zero tolerance policy here on XDA, against racism. Please be more careful how you post in future.
[Huawei Mate 9 Questions & Answers] rbt001:
That doesn't help...

I tried all that to no avail. However finally I found the solution... for some reason it cannot work if you have this "Find my phone" enabled. Once I disabled that and restarted my phone it worked. It is know to cause this problem.
[Huawei Mate 9 Questions & Answers] Stephen:
[MENTION=8420824]kubinski[/MENTION] Please check your PM's
[Samsung Galaxy S8 Questions and Answers] cordobesloco:
Hola me he comprado el Samsung s8 y quería instalarle el modo envolvente para hacer fotos en 360 grados pero al entrar a la parte de descargas de nuevos mod no figura . Como puedo hacer para conseguir ese mod para mi Samsung s8. Desde ya muchas gracias
[Samsung Galaxy S8 Questions and Answers] brigantti:
a mi tampoco me aparece yo tengo el s8 version us de verizon si logras encontrar como hacerlo dejanos saber me interesa usar ese modo tambien.buscare en google si encentro algo te dejo saber

un search rapido encontre la app solo que no sale en la tienda

https://xdaforums.com/galaxy-s8/help/surround-shot-camera-mode-missing-t3594485
[Samsung Galaxy S8 Questions and Answers] cordobesloco:
Mi hermano me pasó la en modo de apk su mod . El tiene un Samsung s5 y la instalé . Se instaló pero no quedó bien . El mod entró pero quedó con un icono enorme y a la hora de abrir el mod no habre. Ahora estoy bajando la apk de la tienda de samsung para ver si ahí figura . Si logro instalarlo y que funcione te aviso . Saludos
[Samsung Galaxy S8 Questions and Answers] brigantti:
usa la app que puse en el link es la del s8 ya la baje y me funcioba perfectamente
[8525, TyTN, MDA Vario II, JasJam General] BorgCymru:
Anything I should update change straight away, any known issues or problems I should check before the 14 days return period is up ?

Thanks
[General Paranoid Android Discussion] reCoded:
Would anyone be willing to share the bootanimation.zip from AOSPA 7.2.1? I would really love to see the boot animation on my phone because Paranoid Android isn't supported with my device. :crying:

Note: Thanks to franlimon6 for the boot animation but if anyone has the boot animation in 1080p (like a OnePlus 3) please share.
[General Paranoid Android Discussion] franlimon6:
From my Nexus 6P

http://cloud.tapatalk.com/s/5971b9a8227a5/bootanimation.zip
[General Paranoid Android Discussion] reCoded:
Thanks! :good:
[Samsung Galaxy J3 (2016) Questions & Answers] Shadeofdoom:
I can boot into download and recovery mode, but any time I attempt to boot into system I am met with this string of text on the top left:

ODIN MODE (HIGH SPEED)

PRODUCT NAME: SM-J327P

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

FRP LOCK: OFF

WARRANTY VOID: 0x1 (0x30c)

QUALCOMM SECUREBOT: ENABLE (CSB)

RP SWREV: S1, T1, R1, A1, P1

RP SWREV: K 0, S 0

SECURE DOWNLOAD: ENABLE

Can't get fdt

download mode ! !

This occurred after I was attempting to uninstall SuperSU and replace it with Magisk. Since then I have attempted to factory reset, to no avail. I cannot continue past this screen. Help please! :(
[Samsung Galaxy J3 (2016) Questions & Answers] IdealInShade:
Same here but I get the error you are leaving out for recovery.img also. Plus, my USB port is fried. Returns all 0000s for hardware IDs, 3 different cords, 3 machines. At least you have a chance to use recovery. I am totally ****ed.

So, that is ODIN/Download mode. I was high and trying to turn off debugging and switching my USB mode to charge only then doing the whole switch to Modem then back to AP and restart to fix the USB connection with my computer.

Know what I flipped? I'm pretty sure you did the same. I accidentally hit the OEM Unlock switch, turning it off, meaning I enabled OEM Lock. The error when you do a normal boot, not download mode (cuz thats what you posted) is "Custom binary blocked by FRP Lock" (boot.img)". Is your phone stolen or something? That why you left it out?

I got a ton of shady phones from shady mofos who ask me to fix them and then cant pay, but I bought this one new myself and know for sure its not. Releax, it doesn't mean its stolen. IN my case it means drugs are bad and Im dumb.
[Samsung Galaxy Tab A series Questions & Answers] mbnoimi:
Hi,

I want to root my tablet Galaxy Tab A 6 SM-T280Q but before that I want to be sure what if I can use same tools for both models SM-T280 and SM-T280Q
[Samsung Galaxy Tab A series Questions & Answers] mbnoimi:
I've exactly have https://www.youtube.com/watch?v=LmqF17FzTUs
[G4 Q&A, Help & Troubleshooting] fuzzy_:
I see this from Hong Kong on Ebay: 3 Colors 5.5" Unlocked LG G4 AT&T H810 32GB Smartphone 4G LTE 16MP 3GB RAM Radio. The Radio is described as FM with RDS. I don't know exactly what that means but it looks like it comes with a real fm radio.

The most interesting item is

Operating System

Android 5.1 Lollipop

Firmware update

Android 6.0 Marshmallow

I don't know if that means the update is already installed or not. If not I think the 810 can be bootloader unlocked and rooted, again I am not positive but from what I have read it that was the way I understood it, but the bootloader has been locked for so long I dont think has been a lot of custom rom development. I may send the seller a message and see if I can find out the OS.

Price for this is $128, with 30 day money back return after i receive it (i pay shipping to send it back), which could take a while, and a one year warranty but I am not sure if LG US honors the warranty. At least with the long shipping time I could read up some on root methods (if possible). I also wonder if it gets an 810 update how that would effect the FM radio since the US versions have the radio disabled. Lots of questions but this could be nice. I have a phone on AT&T and get 4g LTE in my house so even at worst I would think without rooting and just staying stock this could get me a couple of years or so use until 5g starts forcing people to upgrade.

If anyone knows anything about these Hong Kong 810 G4's any info would be very helpful.
[Huawei Mate 9 Questions & Answers] craigzhong:
it recognized as adb device

but , when i enter the twrp recovery.. i connected my phone to win10 pc.. then it showed "cant recognize usb devices"

i already installed the Hisuite and all huawei drivers

ANYBODY can help me with this??
[Huawei Mate 9 Questions & Answers] ante0:
Which adb/fastboot pack did you install?
[Remix Mini General] JustinLu123:
I've made a pre-rooted boot image for Remix Mini. With this image, you can ROOT your Remix Mini without using UART/TTL cable.

Features:

1. Flash the boot image to root the device, without opening the cover.

2. Systemless root: the files in /system are unmodified. You are able to receive future OTA updates (in theory).

3. Factory Reset Protection: you can do Factory Reset in Remix OS or in Recovery mode without lossing root status.

Prerequisite:

A Remix Mini with stock ROM (Tested on my RM1G 8GB & RM1CL)

USB Male To Male cable

Android platform tools (fastboot & adb) on your computer

Steps: (Warning: Backup your data before doing anything)

1. Power on your Remix Mini, press F2 to enter Recovery mode.

2. Choose "reboot to bootloader" and press Enter key, then your Remix Mini will enter fastboot mode.

3. Plug the male to male USB cable into the UPPER USB port on your Remix Mini, then connect it to your computer.

4. Open command line (cmd on your Windows PC, or Terminal on your Mac, etc.), and check the device's connection with following command:

fastboot devices

5. Flash the boot image with following command:

fastboot flash boot <path to the boot.img>

6. When completed, reboot your Remix Mini with following command:

fastboot reboot

7. Your Remix Mini should reboot to Remix OS normally. Install Root Checker from Play Store or via USB drive to check root status.

Known issues:

It seems that SuperSU is not fully compatible with Remix OS. When an app is requesting root access, the dialog of SuperSU is invisable. You are not able to approve or deny the request, and app is hanging. There is a workaround, you can let SuperSU approve or deny all the requests without asking, and later change the per-app settings through SuperSU app.

Back to stock (Unroot or unbrick):

You may using Remix Mini factory image and Allwinner LiveSuite tool (just google them) to reflash your device to stock ROM.

Download link:

(Remove extra spaces in links. I can't post links right now - sorry.)

Dropbox: h t t p s :/ / www . dropbox . com/s/jmhpv0vq7nq83hq/remixmini_rooted_bootimg.zip?dl=0

Baidu: h t t p : / / pan . baidu . com/s/1bpcq3Iv Password: xn9s
[Remix Mini General] Vioner:
[MENTION=8427271]JustinLu123[/MENTION]

Thanks a bunch! Works like a charm on my 16G Remix Mini.

As for the SuperSU invisible popup - try resetting SuperSU data or fiddling with windowed/fullscreen mode of SuperSU/other app. For me the popup works just fine.
[Remix Mini General] bit2:
Thanks for making this boot image public! :) It makes rooting a lot more simple.

Although I'm curious how you accomplished it. Is the original boot image not signed by JIDE? Does the Mini not check the authenticity of this signature?

If the boot image is signed and the Mini does check the signature, how could this modified boot image be put together (without having access to JIDE's private signing key)? :o

If there's no signature check, then how come that nobody (who already rooted the Mini and could read out the boot image from the Mini itself) published the original Mini boot image before? There's a huge Android modding community and modding boot images has a long history with a lot of docs and resources online. So once the original image became accessible, adding SuperSU (or whatever rooting solution one chooses) to an existing image is something that has been done before for lots of phones/tablets/etc..
[Remix Mini General] Vioner:
Boot image can be extracted from publicly available official Mini ROMs used for manual install.

I guess he just pulled the boot.img, extracted it, modified and then repacked.

I've had this idea too, just didn't think it's worth the time since UART method was okay for me.

Since Mini has an unlocked bootloader you can just flash any boot image you want.

If you'll try to flash an update zip from Mini recovery, it has to be signed and follow some more requirements.

Happily, Justin overrode this by rebooting into bootloader.

Sadly, the original boot.img is automatically restored upon reboot... :/

If anyone knows what to do to make it stick, let me know.

Also, since Justin managed to root it via fastboot, maybe now it'll be possible to install Magisk?
[Remix Mini General] JustinLu123:
[MENTION=4606985]bit2[/MENTION]

The bootloader of Remix Mini is unlocked, so we can extract and modify the boot image, and then flash it back though fastboot mode.

[MENTION=4666322]Vioner[/MENTION]

Yes, I extracted the boot image from latest OTA update package ver 2.0.805.

I didn't see the boot.img restored upon reboot. But the boot image may be replaced by OTA updates in the future. Just flash it again if it happens.
[Remix Mini General] Vioner:
[MENTION=8427271]JustinLu123[/MENTION]

I've flashed your boot image like 10 times. It doesn't persist, so I went back to UART method.

Guys, please test for yourself if it persists.
[Remix Mini General] JustinLu123:
[MENTION=4666322]Vioner[/MENTION]

Sorry to hear that the method isn't working on your device.

I've been using this boot image on my 2 Remix Minis (model RM1G and mode RM1CL) for 1 month+ and it does persist. I didn't see any drawback upon reboot or shutdown.
[Remix Mini General] JustinLu123:
[MENTION=4666322]Vioner[/MENTION]

Which version of ROM are you using? I'm using ROM ver. 2.0.805.
[Remix Mini General] Vioner:
[MENTION=8427271]JustinLu123[/MENTION]

2.0.807 - the most recent
[Remix Mini General] JustinLu123:
[MENTION=4666322]Vioner[/MENTION]

I had reflashed / unbricked my device using Phoenix Suite with "verity_block" unchecked. The "verity_block" looks like the feature to secure the boot image. Maybe that makes the modified boot image persist on my device.
[Remix Mini General] Vioner:
Let's see if it persists for others.

Maybe it's just like you said with verity check.
[Remix Mini General] Poeta:
[MENTION=8427271]JustinLu123[/MENTION]
[MENTION=4666322]Vioner[/MENTION]

i can't see any device in "FASTBOOT DEVICES"

PhoenixSuit 1.0.8 installed. USD Debug mode (the two settings on)

Windows 10 x64

What i'm doing wrong? :(
[Remix Mini General] JustinLu:
If you have USB debugging enabled, you may try entering fastboot mode through adb:

adb reboot bootloader

[MENTION=2298413]Poeta[/MENTION]
[Remix Mini General] Poeta:
[MENTION=8427271]JustinLu123[/MENTION]

Have tried Recovery, choose the Bootloader... No fastboot devices detecter

I have tried that too... After enter in the bootloader... No fastboot devices detected.

Fastboot devices empty in the "Fastboot devices"
[Remix Mini General] JustinLu:
[MENTION=2298413]Poeta[/MENTION]

It looks like a driver issue. Try uninstall Phoenix Suite driver and install generic driver for fastboot device in Windows' Device Manager.
[Remix Mini General] sunny5055:
Hi

When i choose reboot to bootloader , it restarts and then its stuck on with Jide Logo

am i supposed to see some screen ?I did a factory reset but didnt help.

when i check fasboot devices its blank does not show any ?

Remix mini is detected using Phoenix Suite under usb debug mode

i tried adb reboot bootloader also it restarts remix mini but again stuck in boot loader..

How do i fix this ?

If i replace boot.dmg in the factory image and restore will it work ?
[Remix Mini General] Poeta:
I think that Jide logo is the fastboot.

[MENTION=295786]JustinLu[/MENTION] or [MENTION=8427271]JustinLu123[/MENTION] that is true?
[Remix Mini General] Vioner:
It is [MENTION=2298413]Poeta[/MENTION]