yashsingh1/xdaforums huggingface dataset:
[Huawei P10 ROMs, Kernels, Recoveries, & Other Deve] WILMANS2M:
Next version will be final not beta11 as i suggested. All is working flawlessly so...

So next HuShed 1.0 is

- All Beta 10 features

- Xposed v89

- Updated included xposed modules and apps

- Modded ViPER version. Will be 2.5.0.5 with preinstalled drivers.

Always all in one install script.

Finally no Aroma unfortunately as it is a pain in the ass to navigate to select option without touch (not working, we don't see what we do, where the cursors goes).

But if you really want to try, tell me and will make it.

Envoyé de mon LG-H850 en utilisant Tapatalk
[Android Q&A, Help & Troubleshooting] charackthe:
IT's stuck at boot logo and it doesn't go into recovery nor fasboot mode (bootloader?). It gives a black screen when I try to boot into recovery or bootloader. Something also worth mentioning is that when I press the power button it lights up it's screen once and never does it again until the next boot attempt.
[Honor 9  Questions & Answers] sonneper:
So, is it a way to change honor 9 splash screen ?

More ; is it a way to "take / back up / copy ..." P9 lite-Android7-splash screen ( huawei logo with kind of bubbles ? ) to our honor9 ?

Thanks !
[Honor 9  Questions & Answers] Suibian:
I had it strangely changed when I totally bricked my phone.Splash changed to Google and Animation changed to android...But never able to boot.I didn't intend to do that so don't know why.
[Moto G4 Plus Guides, News, & Discussion] Paraskapoorin:
My Really happy to use new interface of moto g4 plus camera .

Please go to play store and update

Also If you notice we have Google lense option in Google photo after Toady Update :) :)

Thanks
[Moto G4 Plus Guides, News, & Discussion] papy54:
Thank you for the info! Great :good::)
[Moto G4 Plus Guides, News, & Discussion] SnoopDoge:
google lens been out since the second week of Mar
[Tilt, TyTN II, MDA Vario III General] cjk5wf:
Every time I open IE it goes to "http://messaging_sms_new/," now if i go to any page for example yahoo and then set it as the home screen it will always open up at, "http://messaging_sms_new/". Anyone know how I can fix this?
[OnePlus 5T  Questions & Answers] We7dy:
Hello,

I had to go back to the latest version of Nougat, OxygenOS 4.7.5, because it works as root with SuperSu, but I have a problem with Oreo-based OxygenOS. When I flash SuperSu (latest version) with the latest version of TWRP, I restart the phone, but I get stuck on the OnePlus logo, so the phone cannot restart after at least 15 minutes of waiting. Do you have any idea what the problem is? I can't take advantage of Android Oreo by being rooted with SuperSu, it's annoying.
[OnePlus 5T  Questions & Answers] Macusercom:
SuperSU hasn't been updated in a while and I assume it doesn't support Android Oreo. I would use Magisk instead. That's what I tried with Nougat and what I'm currently using on Oreo.
[OnePlus 5T  Questions & Answers] We7dy:
Okay, thank you. It's the same root with Magisk?
[OnePlus 5T  Questions & Answers] Macusercom:
It's not the same binary but it does the same thing. It will allow apps to gain root access just as SuperSU used to do ;)
[OnePlus 5T  Questions & Answers] We7dy:
Fixed with Magisk. ?
[LineageOS News & Discussion] asik_alom_rahman:
There is a huge bug on LINEAGE OS. The bug is when your device has 25% battery or lessthan 25% the phone dead within 1 min. why. in stock rom it will run aronud 1 hour lineage need to fix this
[LineageOS News & Discussion] nezlek:
Do you THINK it might help for you to provide some obscure information such as which device, what ROM 14.1, 15.1, etc.. and maybe, just MAYBE, a log? Developers are NOT all known for their psychic prowess, despite what you have heard. FYI - NONE of my Lineage devices exhibits this problem.
[LineageOS News & Discussion] asik_alom_rahman:
Device ASUS ZENFONE 2 ZE550ML

LINEAGE OS VERSION 14.1
[LineageOS News & Discussion] titans.raid:
I have also suffer this problm
[LineageOS News & Discussion] nezlek:
Is that an official build ?

Don't own that device but also don't seem to see it on the LOS downloads page. If it is an unofficial build, you are not going to get a whole lot of official love on this issue. ASSUMING it is an unofficial build, I would send a log file to the dev and see what can be done about it. Never hurts to ASK, after all. Good Luck.

---------- Post added at 10:23 AM ---------- Previous post was at 10:22 AM ----------

Same device ? Same build ? Difficult if not impossible to offer more assistance without specifics.

ALSO, HOW OLD IS THE BATTERY ?? One of the symptoms of a failing battery (in my limited experience) is sudden death below a certain assumed level of charge. If the battery is trashed, no ROM in the world will save it.
[LineageOS News & Discussion] RockyTV:
This isn't a software issue but a battery issue. Changing it will fix the problem. It could, however, be related to CPU clock.
[LineageOS News & Discussion] Kojoute:
you can solve it by installing a custom kernel. i have a redmi note 3 (kenzo), ive put franco kernel and it works like a charm - at least for me, no more problems. franco kernel you cand find it on goole (cant let the link here, newbie issue :) )
[ZenFone 2 Q&A, Help & Troubleshooting] Mauri_mza:
Hi!!

I need some of help to do a downgrade MM to LP in my z00ad ........stock was LP... but i did a upgrade to MM and flashed RR 8.5.8. nougat..........

But there i has a bug whit whatsapp records audios and lost signal of wireless too .... so i want to come back to LP to fix this inssue.....

Please someone help me to do the downgrade safely ?

thanks in advance brothers.

:)
[ZenFone 2 Q&A, Help & Troubleshooting] kenbo111:
There's already a guide in the general section of the forum. Use the search box to find it.
[Android Head-Units] Snisle:
I recently broke the front glass on my TA701PL. Anyone know where I could get a replacement Digitizer for it?
[Android Head-Units] bundhoo:
check on ali express... search for ZhiYuSun Freeshipping 2PCS/Lot YDT-8088-01-FPC 7inch Capacitive screen For GPS CAR 175mm*100mm Touchsensor glass YDT-8088-01-FPC.

I was looking for one for my similar unit and found that. In the end i managed luckily to get a refund from supplier so just purchased a new unit instead. Howeven this supplier said that this unit would work.

I dont know for sure but it looked like mine.
[Android Head-Units] Snisle:
All I have to say is... YOU ARE FREAKING AWESOME!! Thank you so much been contacting all the xtrons sellers and none of them have been helpful. Your the best!!
[Android Head-Units] bundhoo:
your welcome. Let us know if you ordered one and if it worked.... as i never actually made an order. It would be good to know for the future. Those devices are so easy to break when installing or removing from car.
[Android Head-Units] skezza:
I wonder if he sells the glass only, as there are some without the buttons.
[P8 Lite (2017) Discussion] GokulNC:
Note:

This is not bootanimation, this is the splash screen (the 'Huawei' boot logo which is displayed when device is switched ON)

This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)

For other devices, please send me your splash.img so that I can create a tool for you too.

Requirements:

1. Rooted Huawei P8 Lite 2017 (any ROM)

2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer

3. You're proceeding at your own risk.

Use this tool and instructions:

Huawei OEM_logo Changer

Note: Use a 1080x1920 pic, as .bmp file (in rgb565 format as specified in that post)

Old method:

STEPS to create boot logo:

1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip

2. Make sure you have a picture in BMP format with resolution exactly 1080x1920px. (Can be of any format)

3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)

4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.

STEPS to flash boot logo:

Steps to backup your oeminfo.img:

Open Terminal Emulator, type the following command to save your stock oeminfo.img to your Internal Storage:

su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo_stock.img

Now, choose any one easy method to install:

a. To flash from recovery:

Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.

b. To flash from Terminal Emulator:

Transfer the oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:

su
dd if=/sdcard/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo

c. To flash from Fastboot mode:

fastboot flash oeminfo oeminfo.img

Finally, Reboot and check if the bootlogo has changed!!

Note:

Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.

Credits:

1. [MENTION=7299447]CrimsonBloodfang[/MENTION] who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..

2. [MENTION=6319272]GokulNC[/MENTION] (myself ;)) who wrote this script

Hit the Thanks :good: button if it worked for you :)

You're welcome to post the splash images that you created..
[P8 Lite (2017) Discussion] MIcHiJK:
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
[P8 Lite (2017) Discussion] Striike:
Doesn't work for me., same logo as before.

rebranded mine too

---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------

https://imgur.com/a/XAup4

just made this btw, it's already in the right format. :)
[P8 Lite (2017) Discussion] CrimsonBloodfang:
1. I am able to create a new "oemlogo.mbn" and a "flashable_logo.zip" through your tool but unfortunately the stock boot logo of Huawei still shows up in every reboot, after using the two files.

2. The zip file works in TWRP Recovery and was flashed without errors but the stock boot logo still shows upon reboot then after rebooting, I checked /product/etc/logo/ and the stock oemlogo.mbn was not replaced with the new one.

3. Here is the oeminfo.img backup, by using this command in a terminal emulator

su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo.img

and this one is the raw file itself. I only used two out of three methods of backing up the oeminfo partition based from this thread because I was unsure as to where in TWRP Recovery should I find the backup for oeminfo partition since it only has the options Boot, Cache, Data, System and Vendor for backup. Maybe in the "Vendor" partition, but the backup size is 394 MB.

4. I'm not sure for the variants of Huawei P8 Lite, maybe only Huawei P8 Lite (2017) and the ones on the "download section" in this link? If you meant the Huawei P8 Lite (2017) variants, the ones I know are Huawei P8 Lite (2017) PRA-LX1, PRA-LX2, PRA-LX3, PRA-LA1 and PRA-TL00. I'm using the Huawei P8 Lite (2017) PRA-LX2.

I've also tried copy pasting the new oemlogo.mbn then changed it to the correct permissions (-rw-r--r--). I even tried renaming it to "oemlogo.mbn.bak" to see if there's any change but it seems that this file is not in control of the boot logo. We also have the boot warning logo too by the way, the one that is caused by unlocking the bootloader.

Here is my own logo.bmp boot logo, 1080x1920 resolution, edited through Gimp 2 and exported as .bmp file format.

Edit: Does anyone know where is the exact location for our boot logo files? I've also found the same oemlogo.mbn file on some folders in /product/hw_oem
[P8 Lite (2017) Discussion] GokulNC:
[MENTION=7299447]CrimsonBloodfang[/MENTION]

The oeminfo.img file had the pictures as I guessed.

I have updated the OP with the new tool. Please check if it's working :)

Also, I think the files in the '/product/hw_oem/whatever' directory are created from the oemlogo partition while booting (not sure though).

So maybe using the old tool, setting the permissions for oemlogo.bin as -r--r--r-- might have worked (since write access is denied).

Edit:

As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???

If yes, this tool MIGHT work for those devices too.
[P8 Lite (2017) Discussion] CrimsonBloodfang:
Thanks! I will be testing it now.

Yes, it is called with different names from different countries and they are more or less, just the same devices.

In the Philippines, this phone is called the Huawei GR3 (2017).

Edit:

Maybe the users need to backup their own "oeminfo.img" first before using the tool and can you add it on OP? They might use my device's oeminfo.img if they forgot to backup and it might change their device's region settings then their stock updates would be based from my country.

I haven't rebranded my phone, just went straight to LineageOS 14.1 so I'm not sure about the consequences of flashing other oeminfo.
[P8 Lite (2017) Discussion] Striike:
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
[P8 Lite (2017) Discussion] CrimsonBloodfang:
[MENTION=6319272]GokulNC[/MENTION]

It also didn't work for me. I've tested it six or more times with both the Terminal Emulator and the TWRP Recovery flash method.

Edit:

The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder. Then flashed the six different files of oeminfo.img and flashable_logo.zip with Terminal Emulator and TWRP Recovery, but on every reboot, the boot logo is still at stock.
[P8 Lite (2017) Discussion] CrimsonBloodfang:
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
[P8 Lite (2017) Discussion] GokulNC:
[MENTION=7299447]CrimsonBloodfang[/MENTION]

Actually there were many .bmp pics inside the oeminfo.img

I didn't look at that properly.

When I extracted them, I saw 2 bootlogo images.

So I've modified the tool to change them both.

Try the new tool that I've uploaded now and see if it's working :D

It should contain 2 files named logo1.png and logo2.png

Nope, I don't think so..

I'm not sure if the oeminfo partition is same across all the different firmwares.

I guess they all must be the same. If you can attach your stock 'oemlogo.img', I'll take a look at it.
[P8 Lite (2017) Discussion] GokulNC:
My tool automatically converts everything to .bmp format, so it doesn't matter ;)

I'm not sure about the rebranded device. Can you please attach your 'oeminfo' file?

I'll check that out.
[P8 Lite (2017) Discussion] CrimsonBloodfang:
Ok, I've flashed the flashable_logo.zip using the new tool and it seems to work. Boot logo is not anymore the stock one but instead, it's replaced by a "glitched image" with a color green background and two rectangles with colors pink and blue, not the boot logo I made. Boot warning sign is still there afterwards though.

It may be a wrong procedure on my part because I just placed my logo.bmp together with the logo1.png and logo2.png but I will continue tinkering and testing it or have a lower file sized image to see if I can finally get the desired boot logo.

---------- Post added at 11:04 PM ---------- Previous post was at 10:52 PM ----------

Also flashed my backup oeminfo.img through Terminal Emulator or TWRP Recovery and everything went back to normal.
[P8 Lite (2017) Discussion] CrimsonBloodfang:
[MENTION=6319272]GokulNC[/MENTION]

Tested it many times, boot logo always end up with the "glitched image" as attached below.

This is not the original image. Just an edited image through Gimp 2, for reference.
[P8 Lite (2017) Discussion] GokulNC:
Does this arise after changing the logo2.png (or logo2.bmp)??

Is that the same output no matter what the logo2 is?

I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??

FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
[P8 Lite (2017) Discussion] CrimsonBloodfang:
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.

I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.

Edit:

The image in this post is what the glitched image of the boot logo, actually looks like.
[P8 Lite (2017) Discussion] honorfan:
Thanks bro

Very useful guide
[P8 Lite (2017) Discussion] GokulNC:
Hi, sorry for my late reply. Got stuck up with something lately.

I have attached a new tool, with little changes.

Please check if it's working.

If it doesn't, I'm not sure what else to do.

Hi, did this work for you?
[P8 Lite (2017) Discussion] CrimsonBloodfang:
Thanks, I will be testing it later. I've also found out from another user that changing the boot logo using the tool, has stopped working in Nougat and Oreo.

Here is what he said, and this thread is also changing their Huawei device using the oeminfo partition.

Maybe you already know these?
[P8 Lite (2017) Discussion] CrimsonBloodfang:
[MENTION=6319272]GokulNC[/MENTION]

Tested it twice, it's still showing the glitched image.

My first attempt was replacing the logo2.png with another image as logo2.bmp. Flashed the files through TWRP Recovery, rebooted and the result is still the glitched image.

Second attempt was to not replace anything in the "pics" folder. Created the files, flashed them in TWRP Recovery, rebooted and the result is still the same.
[P8 Lite (2017) Discussion] CrimsonBloodfang:
I've been searching around xda forums for information about editing Huawei's oeminfo for its boot logo image and I noticed that their tutorials needs to follow a "specific RGB format" when editing the images to be used as a boot logo. (Bitmap file with color depth not less than 16 bit, supported color schemes: RGB555, RGB565, RGB888, RGB8888)

Although, I'm uncertain that this might be the cause of the problems and I haven't tried it yet.

- Follow any of the RGB formats to fix the problem.

I've only tried "RGB565" and "RGB888 with color depth of 24 bits".

On the other hand, seeing the "glitched image" as a boot logo, might just only be an indication of a corrupted oeminfo, when it's not properly recompiled or reconstructed?

Just to be sure, I'll place the links of the threads and posts, that I think might be useful for reference.

You might have already read these threads before.

- How To Change The Splash Screen or Boot Logo In Huawei Honor 7 at post #2

- Scroll down to Part VII - How To Change The Splash Screen

- Solution by Kostyan_nsk

- [HOW TO] Replace initial splash screen (logo) on Huawei P7

- [GUIDE] Changing boot splash image on the Huawei Y6

I will try changing the RGB formats for the image that I'll be editing, to see if it makes a difference.
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] YashGarg10:
​

Android Open Source illusion Project​

About us:​

AOSIP is a quality custom ROM based purely on CAF N source. Twisted with the latest features and blended with stability. We strive for perfection and it shows.​

Team Illusion:​

Josh Fox (@xlxfoxxlx)

Paul Clark(@Dabug123)

Akhil Narang(@akhilnarang)

Sri Harsha(@srisurya95)

Sean Grondin​

Support/Community:​

Full support is always on the top of the list. Visit our AOSiP Google plus community for all your ROM needs. There we have all the latest links to gapps and other helpful communities. Or just stop and engage in off topic fun.​

Bug reporting:​

This is a big one. We work very hard for you guys so please help us out and follow these steps to report your bug. I've even provided links to help you out.

1. Very first step will be to attempt a re-download followed by a clean flash.

2. Pull a logcat and copy / paste it to hastebin .

3. Visit AOSiP and post your issue with your log in the bug reporting section.

4. Any bug reported without following procedure will be disregarded.​

Source code:​

As the name states we are open source and encourage anyone to skim through the code. However the builds we release are not to be taken apart and parted out.

AOSiP Gerrit Review

AOSiP Github

Vibe K5 Sources​

Downloads:​

AOSiP ROM

GApps​

Installation Instructions:​

--> Clean flash (ie, wipe data, system, caches)

--> Flash ROM

--> Flash gapps

--> Flash theme ready gapps (optional)

--> Flash Magisk/SuperSU for root (optional)​

While updating:​

--> Wipe caches

--> Flash ROM + gapps + Magisk/SuperSU​

Note : If you experience any bugs, clean flash before reporting them.​

Credit/Thanks:​

Mike Williams(founder and creator of AOSiP)

Google

Dirty Unicorns

AICP

ABC Rom

Screwd

Omni

Krexus

Cyanogenmod

SlimRoms

ChainFire (SuperSU)

Beanstown106

Cory Collins

Any others I may have forgotten

All our testers​

Donations:​

Donations are never asked but things such as server, gerrit, & website do cost the team money. If you're feeling like were deserving of a little tip please feel free to send it.​

XDA:DevDB Information

AOSiP Nougat, ROM for the Lenovo Vibe K5 Plus

Contributors

YashGarg10

Source Code: http://github.com/AOSiP

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.10.x

ROM Firmware Required: TWRP/RWRP , Bootloader Unlocked

Based On: AOSP

Version Information

Status: Stable

Current Stable Version: v6.3

Stable Release Date: 2018-04-05

Created 2018-04-06

Last Updated 2018-04-06
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] T3Techno:
On Going for test, how about camera?

---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------

Sorry i think oreo :D How about headset?
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] T3Techno:
Clean flash

Gapps

Magisk 16.0

Dolby+Viper

Bluetooth pop up FC issue

Menu Doze on Display Setting, if touched setting FC

Kernel not support dt2w, but any option on Additional Menu

No FM radio

Headset plugged when enter voice ass, volume + by itself, can't use button on headset

Sep 17 security patch

Thanks
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] run faiz:
Working fine in my device a6020a46 2gb

Google assistant working fine.
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] run faiz:
Lack of music app as a system.

No stylish home screen google search bar is old style, bigger icons, should be little bit smaller for good looking.

No charging current info on lock screen only temp. and voltage shows.

Security patch is old but good layer of security.

Need to work on battery backup.

Device is pre-certified no need to install google framework from magisk download.

I found a bug that is battery led colour setting while charging not work.

Headphone is not working in online streaming such as youtube.
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] run faiz:
Earphone issue

Sometimes Earphone not work specially while watching utube.

distortion audio volume in earphone, sometimes.

Here is the logcat i attatched

My device is a6020a46 2gb.

Rom is working fine battery backup is good.

Smooth rom Nice work thanks.
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] mathpfvr:
Great rom, thanks friend :D
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] mathpfvr:
No more updates for the rom? :/
[Lenovo Vibe K5 Plus ROMs, Kernels, Recoveries, & O] mathpfvr:
camera does not work correctly and the sound is too low with the headset
[YU Yureka General] 22lovejeetgill:
Sir,when i am trying to connect my hardbricked yu5510a (H/w P2,S/w P0.160314) to pc,during installation of "qualcomm hs usb loader 9008" drivers,My pc is getting hanged..

please help me
[YU Yureka General] vikram1985:
Yurek hang

Same problem
[Samsung Galaxy S8 Questions and Answers] mmm273:
Hi is there any way to complete disable navbar on Oreo without root ? Because every app i tried, when I swipe up it show navbar...