yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Max 2  ROMs, Kernels, Recoveries, & Othe] pranavaryans:
Humble request to all my dear MI MAX 2 users.

* If you like my work hit like.

* If you don't like my work then please do not post comments on telegram.

* If you are having errors / bugs please provide logs.

Getting unwanted comments like "Not a good work by you" on telegram.

If you don't like to use my ROMs then use other ROMs, MI MAX 2 has bunch of great developers.

BUT PLEASE DO NOT DISCOURAGE ANYONE (INCLUDING ME) WHO IS TRYING TO COMPILE ROMS.
[Xiaomi Mi Max 2  ROMs, Kernels, Recoveries, & Othe] pranavaryans:
https://t.me/pranavaryansROM
[Xiaomi Mi Max 2  ROMs, Kernels, Recoveries, & Othe] Y@SH:
This is the chinese based Flyme Rom, is it possible to build the Global Flyme for a device? i. the Global Rom, because this rom is full of chinese apps which is not comfortable a lot of times, the apps have chinese everywhere evn after seting the language to english,

and yes i can confirm that calling is now workin for me bt there is a catch, The Calling Works ONLY if u insert the Sim in Sim Slot 1 , so sd card is sacrificed
[Xiaomi Mi Max 2  ROMs, Kernels, Recoveries, & Othe] pranavaryans:
not possible as we do not have flyme sources.
[Xiaomi Mi Max 2  ROMs, Kernels, Recoveries, & Othe] jbmc83:
u could try and remove / replace the chinese apps via titanium baclup or a system app remover from playstore.
[Xiaomi Mi Max 2  ROMs, Kernels, Recoveries, & Othe] U Boy:
Full screen gestures workings ??
[Xiaomi Redmi 4X Questions & Answers] Prathu_:
I had rooted my phone a while back but for some reasons I had to unroot it again because Snapchat wasn't working.

I have TWRP recovery, so can I just flash the Rom or do I have to root again.
[Xiaomi Redmi 4X Questions & Answers] G-up@94:
Yes u can. And i u want root on the flashed ROM

Just flash magisk via twrp.
[Xiaomi Redmi 4X Questions & Answers] Prathu_:
So can i just flash the Rom?

Can it lead to bootloop of brick... If I don't root
[Xiaomi Redmi 4X Questions & Answers] G-up@94:
No. It wont lead to any prblm or bootlop. I tested myself.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
"Blobs" are the files specific to each device that we need in order to compile custom ROMS that work on our device. The process of finding them is tedious and slow... I have been picking away at them for months when I have time. There are over 600 files so far! But there are also references to files that are not being found. They are either missing, or they are not located where they are expected to be located. This is where I need help.

So, if you want to help, go HERE:

https://github.com/mightysween/android_vendor_motorola_payton

and look through the proprietary-files.txt file for anywhere that it says "warning".... and then search inside of the firmware (working on 8.0+ now, not 7.1 please) and try to track down the file that it says is missing [obviously, you will need a system dump, or to search on a rooted device]. If you find it, please post below like this:

LINE NUMBER OF THE WARNING (from github)

PATH TO THE MISSING FILE (relative to /system... in other words, don't inlude your own local path)

Once this file is complete, we can use it to automatically pull the correct vendor files into our build environments... having a working recovery, active kernel developement and completed vendor blobs should open us up to more development efforts.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Also, if anyone has done any testing and knows of other proproetary files that are needed, please post them here so I can include them.

My time at the computer to work on this is really limited, so I have only identified a dozen or so daemons that definitely call for proprietary libs... I am sure there are more
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TheBassDude:
I would love to pitch in on this but have zero experience with anything related to development. Do you think I could still be of help? Sounds like a basic enough task that it wouldn't be too difficult. Let me check and see that I understand the process.

Went to github and looked at proprietary-files.txt. The first warning I found was in line 49: "blob file libpn553_fw.so missing or broken". Then searched for that file in my device's system folder using ES File Explorer with Root Explorer enabled.

So is this what you're looking for?

49

/system/vendor/firmware/libpn553_fw.so

---------- Post added at 14:31 ---------- Previous post was at 14:07 ----------

I'd like to contribute in some way but if this is best not left to a complete noob then I totally understand
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] QWZR:
Do you have a link to a system dump?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Thanks, that is all there is to it :)

Just time consuming (especially after the first 500)...lol
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] QWZR:
Mine gets here next week
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ebrandsberg:
If you have root on the system you can find the files for, you should be able to find any given filename with:

find / -name "filename" -print

And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Any way that works is fine by me :)

I am on the road a lot and just don't have enough time to sit and work on it... so it is taking months. I bet a few people helping could finish it in a matter of hours.

I am hoping to have a few hours next week to work on it. But the sooner this is done, the sooner I can shift to trying to compile Lineage OS with working hardware.

BTW, Lineage *does* compile if I comment out all the stuff causing make errors... not much works, obviously.

The next step will be compiling with these blobs, then logging all the new errors and chasing down all the additional broken symlinks... and then adapting the kernel as needed.

Then, MAYBE we can get a base Lineage tree up and open up the X4 to building for other roms. I know someone started a skeleton tree for Carbon already on Github... they are likely just waiting for the completed device tree, too.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] BLuFeNiX:
I don't own this device yet, but I was thinking of getting one. I figured this might help you all out (you'll need to be running linux):

First, let's get a list of all the files on the phone, to make searching faster.

adb shell
su
find / > /sdcard/allfiles.txt
exit
exit
adb pull /sdcard/allfiles.txt

Now you should have allfiles.txt on your machine. Also grab the proprietary-files.txt, and then run this:

grep -Po '(?<=(blob file )).*(?= missing or broken)' proprietary-files.txt | xargs -I @ grep "@" allfiles.txt

That should find the paths of all the missing files (except the ones marked "wildcard")
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Thanks, I had recently completed this, but your code worked fantastic for double checking, and actually helped me find one that I had missed :) :good:

Now, on to identifying any more daemons that need proprietary files... and then assembling the tree itself... PROGRESS!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
PHASE 1 is complete!

https://github.com/mightysween/android_vendor_motorola_payton

I am 99% sure that this is only ~75% of what will be needed to actually build LOS15. But it is a good foundation to work off of now.

My plan is to start attempting to compile LOS and take error logs to chase down the remaning missing stuff. LOTS to be done still to get to that point...hoping for some other builders/devs to materialize here and help out :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] christianrj:
Hi! Just a question: it´s mandatory to use A/B partition scheme to build a custom ROM for this device or it will be possible to use a traditional partition scheme and free up some GBs of internal storage for use?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
It would seem that we will still be stuck with A/B, as the bootloader does the initial check of the active slot. Perhaps there may be some clever ways around this in the future...but nothing I will be tackling.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] BLuFeNiX:
You would probably need a custom kernel to do it properly. The bootloader passes a kernel param (androidboot.ro.boot.slot_suffix) specifying which slot to use. In the absense of a kernel param, the value is read from the ro.boot.slot_suffix build property.

That being said, you might be able to just repartition your device to only have 1 slot, flash your ROM, and use

fastboot --set-active=_a

. If your ROM has disabled OTA updates from the OEM, you should be fine.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] navenedrob:
I'm going to get an X4 in the coming weeks. I'd like to help with this soon. I'm a seasoned developer by trade and can collab on GitHub. Hope to be able to start working with you soon. :good:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Hariiiii:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:

https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] DustArma:
[MENTION=1829889]vache[/MENTION] at the Moto G5 Plus forums has already managed it using the /oem partition which is otherwise unused for custom ROMs
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Cool... seems it may be possible. Will follow the progress on the Redmi and G5 devices
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
The more I am reading about enabling Treble, the more I think it is entirely possible.... and probably the best direction to focus our efforts.

Seems like we have partitions that could be used as /vendor. I am reading up on exactly how the Treble vendor partition is set up. Tricky, but not implausible.

EDIT: Actually, none of the partitions we could potentially re-purpose for /vendor are big enough. So, it may be harder on this device than on others. It may require repartitioning.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] radjad:
If it's possible to turn off AB, then the B partition seems like an obvious candidate. It's more hacking than one would want to do, though.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Indeed... a lot to consider and research
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I'm updating my build environment now. I don't have a ton of time either, but I'll do what I can.

Is this the device tree you are using? https://github.com/mightysween/lineage_device_motorola_payton
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Sort of... :) I pushed that one just to have a separate one started. But I haven't linked it to the vendor stuff yet. It is enough to initialize with.

Problem for me now is that LOS 15.1 won't make it through compile... runs out of memory even on an 8GB machine, and with usual java tweaks.

I may need to revert to 14.1 to test
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Did you add this to your environment?

export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"

https://wiki.lineageos.org/devices/bullhead/build#configure-jack-1

I have 16gb in my buildbox if that is worth anything. I am building 15.1 for bullhead currently and it just finished so I'll try to cook up some homebrewed payton later tonight. First run took 3 hours. Hopefully, ccache will shave this down a little.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Yes, I did add that.

And it appears I now only have 6GB. That's never a good sign :) Think I have worked this old thing too hard
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Sorry to hear about the memory issues.

Quick status update- I am trying to build for 15.1 but I'm running into a few build errors. When I build for bullhead, the build completes without error, so I think the build environment is OK.

The prebuilt kernel no longer seems to work since the build complains about missing kernel headers. I tried including the kernel sauce, but ran into a few errors (release name is greater than 64 characters). I'll try to sort this out tomorrow.

The A/B bootloader seems to be throwing lots of errors. The update_engine package seems to be missing a few files. I'll try adding them the proprietary list.

This device doesn't seem to have a real vendor partition. I can see the simlink for vendor to system/vendor, but the OEM partition seems to be bloatware.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
I had been following the build attempts for Xiaomi M1 for some insight into the A/B stuff, and also on a similar board/GPU... but looks like not many updates recently

https://github.com/tissot-dev/android_device_xiaomi_tissot/tree/lineage-15.0?files=1

device.mk is going to need a lot of work.

...am browsing for a new PC tonight. Need some more beef for video/audio projects anyway, so maybe will bite the bullet this week and have a better build machine
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] radjad:
Tell me if you need any grunt work done, I'm relatively technical and will provide pull requests as desired.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
The more helping, the better! I am time-crunched with work until mid April, so won't be doing much until then

We need to get at least basic includes in the makefiles, and then start build attempts to log what is missing.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I've been trying to get the kernel to compile so that I can test what is missing, but so far no dice. There is one commit at seems to rely on proprietary qcom stuff, so I just reverted that. I'm still getting build errors for the kernel, so I need to trace that down some more.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Maybe take a look at [MENTION=4825505]kraatus90[/MENTION] kernel tree
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
Official TWRP was ported from "nash" (Moto Z2) with only one change for USB OTG.

They have LOS 15.1 building as well.

Should be able to fork, plop in our proprietary list, make necessary changes for the device name and get to a point where we can start debugging. I should have more time in coming weeks.

https://github.com/betaxab/android_device_motorola_nash?files=1
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] LucasGalasini:
Why the Custom Roms delay?

Hey guys, I was wondering when custom roms will start appearing for the Moto X4 (Payton) I'm really anxious, because I deeply hate Stock Roms, is it around or is it going to take some time yet?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jbaumert:
PLEASE!!!! - DO NOT ASK FOR ETAs!!!

Most Devs are doing this on their own time for nothing. If you don't like stock ROMs that much, you should have bought a device with an established development history.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Neffy27:
Big no no dude....
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Well, I'm working on building a lineage rom for this phone, but I can't get the thing to boot. I am using a copy of the device tree for the nash/moto Z2 force.

The boot.img will work with the stock rom, but I can't get lineage to boot. I just get bootloops until it falls back to the other A/B partition. I can boot into the lineage recovery mode from the boot.img I made, so at least that works.

I think the issue is with init. Does anyone have any hints on what will work? The marlin has the same a/b partitions, so I might try building aosp for the marlin and hope that will give me some hints about what is missing.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mightysween:
I am almost through my busy work season...

Can you push to github and I will try to jump on board soon
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I will push soon- It's not bootlooping anymore and I just get stuck on the boot screen, no animation. I've got another build cooking, so hopefully, I can get it to a debuggable state soon.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Hariiiii:
Looks like a developer for the Moto Z has found a way around not having a /vendor partition:

https://xdaforums.com/project-trebl.../tool-capire-le-treble-terble-vendor-t3774629
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] brunopio:
How can I help this in Windows 10? I have a XT1900-06.

Totally noob here in development.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Knuxyl:
I am assuming this job has been completed?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
The trees are here. It's set up as a common and Payton specific vendor trees. erfanoabdi and munchycool did the heavy lifting for us.

https://github.com/moto-SDM660/

themuppets also have a vendor tree on github. I haven't checked to see if there are any differences, but I suspect they are identical.
[Honor 8 Pro  Guides, News, & Discussion] shailendra1993:
1. Download the Dload File For Your System.

2. Download: http://www.mediafire.com/file/xxbrn6iicw683zw/DUK-RECOVERY_RAMDISK_NoCheck.img

Follow this:

1. Extract the firmware and copy the dload folder in exfat formatted SDcard.

2. Copy dload folder to your SDcard.

3. Flash the recovery:

fastboot flash recovery_ramdisk DUK-RECOVERY_RAMDISK_NoCheck.img

4. Thanks to [MENTION=256656]morph[/MENTION]. Dial *#*#2846579#*#*.

i. Click on software upgrade.

ii. Now Click on SDcard update.

It will stuck at 99% and failed but Voila! U will successfully on nougat. The bootloader will be unlocked. Then normally upgrade to b150 by system update.

Thanks to [MENTION=5826312]jitendra772[/MENTION] For His Awesome Guide:

https://xdaforums.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223/page3#post75478984
[Honor 8 Pro  Guides, News, & Discussion] androgenius:
I am on Oreo stable 8.0.0.322 but the rom is very buggy and a battery hog.

I would like to revert to Nougat. Would this method work for me as well?

Also, why do I need to flash recovery, wouldn't the existing recovery work?
[Honor 8 Pro  Guides, News, & Discussion] shiva797:
Did you try it?? And did it work??

---------- Post added at 03:55 AM ---------- Previous post was at 03:54 AM ----------

Can you give us the links to download the dload file??
[Honor 8 Pro  Guides, News, & Discussion] shailendra1993:
yes, it will work.
[Honor 8 Pro  Guides, News, & Discussion] shailendra1993:
Sorry, the link I had for Indian version is no longer active, try firmware finder or ask someone on hihonor forum [every region has different firmware, don't flash the rom of other region]. Btw, I got rid of the phone, you should too.
[Honor 8 Pro  Guides, News, & Discussion] shiva797:
No can do, i bought it a month back. Also i got the b130 firmware. Please tell me how do i flash it. Step by step. I dont wanna brick it. Currently i am on 8.0.0.324 oreo.
[Honor 8 Pro  Guides, News, & Discussion] shailendra1993:
Try this:

https://club.hihonor.com/in/lead-th...-8-oreo-to-emui-5-1-nougat-dukl09-c675.166159
[Honor 8 Pro  Guides, News, & Discussion] shiva797:
If it doesn't work will it brick my phone??
[Nexus 6P General] mikaeldalc:
So, I had $200 and I was looking for an android device that can keep me going for a few months til I’m eligibility for an upgrade with my carrier.

After looking around for a few hours, I narrowed my decision down between the Honor 7X and the Nexus 6P.

Ultimately I decided to go for the Nexus 6p due to USB type-C, stock android and dual front facing speakers (3 major things I look for in phones now)

I ordered my 6P from an eBay seller who states the device is in 9/10 cosmetic condition, fully functional and will be here on Saturday.

After searching the web a little more I noticed that a lot of people are talking about the battery shutdown issue.

I remember buying a Nexus 6p at launch and didn’t have this issue, which is why I decided to order it again. But, now I’m kinda scared and wondering if I made the wrong decision.

Can someone shed some light as to whether every Nexus 6P is affected at some point and if replacing the battery will fix this issue.
[Nexus 6P General] Grushteniak:
6P is a great phone, just keep in mind the battery issue (replaceable and relatively cheap) and - more serious - bootloop issue: https://xdaforums.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279 <- read it.

My two cents: install AccuBattery in order to check your battery's health (if below ~ 70%, replace it or you'll suffer from random shutdowns), unlock the bootloader (search here how to), flash TWRP and keep the bootloop fix handy. If things go south, flash it and at least you can have your phone alive again, despite the poor performance.
[Nexus 6P General] btouareg:
Hello

I have Pixel 2 XL and its best android phone i ever used , had op2 op3t note 2 3 , s5 s6 s7 s8+ htc(the one with 2 front speakers develop by beats) , Ive been looking to own 6p since forever then i pull the trigger and bought one recently white 128gb , let me tell you if i know that device is so so so good i wont bother getting pixel 2 xl , as i mentioned pixel 2 xl is the best android i ever used but still not worth to upgrade from 6p to xl2 .

anyway i think u made the right decision ,ive lost 1080 euros :D

best regards
[Nexus 6P General] law16:
I owned a htc 10 but gave it up a little while ago. Had iPhone for 2 years and that was my DD. I got this Nexus 6p 64gb used for 150 $ and I thought the same thing. Hopefully the battery doesn't fail on me , but so far so good. It's been about a month and no complaints. I think you will enjoy the phone . Development seems to have died down a bit or we are just late to the party but I actually can't find anything I dislike.
[Nexus 6P General] coolsid8:
For a 2 year old device, the development is pretty decent. Switch to f2fs. Try crDroid or ABC Rom + f2fs kernel from ABC Rom.
[Nexus 6P General] anon1135:
I'm in the same situation looking for a phone for my father. 6p def seems like the best for budget if it didn't have those battery problems. my other choice is also the 7x but I can tell 6p is more of a phone my father would like because of the front speakers. might have to go with 7x because it can be bought new and will probably have less problems+batter battery. just worse sound and skin. looking into the cheaper Xperia z phones next
[Nexus 6P General] shekinahsmoke:
:) yeah .. u did lol
[Nexus 6P General] xdamember143:
How do u change to f2fs? Noob over here
[Nexus 6P General] sene1983:
Using my phone since 2016 April.

(Android stock 8.1)

With Pixel 2 launcher https://xdaforums.com/android/apps-games/app-rootless-pixel-2-launcher-google-t3688393 and Pixel Camera https://xdaforums.com/nexus-6p/themes-apps/mod-camera-nx-v4-google-camera-zsl-hdr-t3494435 it works awesome.

This is the best phone I have ever used and also my first phone I used so long...

I did not have any battery issiues. But, i had a microphone issiue. But i fixed it by editing build.prop file after rooted. So far, its working perfect and i do not need a phone...

But do not forget that: 2-3 years later, battery performance will be not the same.