yashsingh1/xdaforums huggingface dataset:
[Honor 9 Lite Questions & Answers] Fredin_:
As you all know there is an inbuilt applocker in emui and a pretty good one too.

But the one that is in emui 8 at least in my phone has a certain bug.

It shows and allows me to lock every single app I've installed except messenger.

It does not even show up in the list shown in the applocker.

This annoys me as I'm gonna have to install another third party applocker which'll consume more ram and affect the performance of the phone.

Now let me tell you that i'd installed a custom ROMs and then reverted back to complete stock. I had this issue then when I got the phone and still have it now.So I'm pretty sure it's a bug.

Does anyone have a fix for this? I really like the inbuilt applocker
[Xiaomi Mi 6 Questions & Answers] Finovsk:
After updating to MIUI 10, I got this strange bootloop.

How can I solve this? D:
[Xiaomi Mi 6 Questions & Answers] Finovsk:
The video isn't uploading, so I uploaded it to YouTube:

https://youtu.be/ZhzCrS_ol8o
[Xiaomi Mi 6 Questions & Answers] G4B33:
I wouldn't call this a bootloop, it looks like the Google services crashing constantly. Is it a global stock ROM, or a custom one?
[Xiaomi Mi 6 Questions & Answers] Finovsk:
Stock! What should I do?
[Xiaomi Mi 6 Questions & Answers] Rick_BR:
You have unlocked bootloader? If yes, I recommend you to install this ROM via MiFlash, erasing all, a real clean installation.
[Mogul, XV6800 ROM Development] jim256:
i myself have never had a titan for more than a week and am a vogue user, but found this very interesting.

just wanted to post this here in order to get in some more exposure and to let you guys have a whack at it!

please contribute if you can

quote from developer: "...It should work on titan (but might be short of memory and keys may not work), doesn't work on kaiser because the hardware is slightly different."

please post here (or in the other thread) on if this works/what works and doesnt!

http://xdaforums.com/showthread.php?t=382265
[Asus ZenFone Max Pro M1  Questions & Answers] heng950620:
Hi.. may i asking u guys that u guys have try to unlock bootloader at ver.318 firmware? cause i unable to unlock my phone bootloader at this latest firmware..does anyone has same issue with me?
[Asus ZenFone Max Pro M1  Questions & Answers] arvinchugh:
What issues are you facing? Unlock method works perfectly.
[Asus ZenFone Max Pro M1  Questions & Answers] heng950620:
i have follow the instruction that to unlock my phone but when i want to unlock my phone bootloader it sometimes show tat code 0kb and wont move anymore...sometimes it until stuck at waiting devices and the phone only show click power to shutdown.. .and sometimes already process all the process in cmd but the phone still at bootloader mode and wont restart..

i have try uninstall and reinstall my driver in my pc still the same.. my operating system is using windows 8.1 and windows 7
[Miscellaneous Android Development] armandop_:
[IMG="Lineage OS Pic"]https://cdn57.androidauthority.net/wp-content/uploads/2018/04/LineageOS.jpg[/IMG]

Disclaimer:

/*
* Your warranty is 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.
*/

What's working:

IDK

Not working:

IDK

Links:

TWRP: https://androidfilehost.com/?fid=5862345805528064784

Google Apps (arm): https://opengapps.org/

ROM: https://www.androidfilehost.com/?fid=5862345805528066888

Source:

Device Tree (cv1): https://github.com/armandopartida0/android_device_lge_cv1

Device Kernel (cv1): https://github.com/armandopartida0/android_kernel_lge_cv1

Shared Device Tree (sd4xx): https://github.com/LG-SD4XX/android_device_lge_sd4xx-common/tree/cm-14.1-32-test

Device Blobs (cv1): https://github.com/armandopartida0/vendor_lge_cv1

Special thanks to:

Travisholt92

deadman96385

Thank you both for working on a common device tree

Remember, this ROM build is a test. It might work just fine, or it could not boot at all. Let me know how the build goes. Also this is a 32bit rom.​

Donate here :) --------> https://paypal.me/APartida332
[Miscellaneous Android Development] armandop_:
*Warning- As of right now, the build will only boot the lineage os boot animation. I will look into it and fix it soon
[Miscellaneous Android Development] tecknight:
That's it, just the animation ? You need a logcat or dmesg ?
[Miscellaneous Android Development] armandop_:
A logcat and a dmesg would be nice
[Miscellaneous Android Development] tecknight:
OK, you got it
[Miscellaneous Android Development] guytalluto:
any luck getting this rom to work?
[Miscellaneous Android Development] HiGhDRo3o5:
Was this ever fixed?
[Miscellaneous Android Development] Deleted member 4135766:
Any work towards this? Or is aristo 2 dead?
[Miscellaneous Android Development] NonStickAtom785:
Hey the LG Aristo 2 is far from dead. Right now we are experimenting on this rom. So just hang in there. The development just kick started since being released January this year(2018). Thanks to tecknight you can root and install twrp custom recovery. And now were working on lineage OS 14.1. So when this is released as a "non-buggy" rom then we pretty much have unlocked all the potential of the Device.

---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------

We are working on the fix still. Don't give up!
[Miscellaneous Android Development] jflow36:
Should I use arm or arm64 gapps?
[Miscellaneous Android Development] NonStickAtom785:
The architecture is arm so use arm gapps
[Miscellaneous Android Development] Isaah E:
Lg aristo 2 lineage os 14.1

Can you update me on development for lineage os for lg aristo 2 or is development completely dead
[Miscellaneous Android Development] NonStickAtom785:
It's dead but I'm gonna reboot the project. I'm determined not to let the Aristo 2 die. Tomorrow I'm uploading the AtomicRom that I created using the iPioneer Rom for the Aristo. That should inspire some more development in the Aristo 2.
[Miscellaneous Android Development] Isaah E:
Does the rom you made work correctly Im really excited can't wait for you to upload it :D
[Miscellaneous Android Development] NonStickAtom785:
It's very unstable if you flash it. But I'm going to make a TWRP Backup and Upload it to remove any errors from flashing.:fingers-crossed:
[Miscellaneous Android Development] PAWGLove:
Is there any simple way to port an existing ROM with the same base Android Version and same chipset? The Galaxy J2 has both and seems to have plenty of development.
[Miscellaneous Android Development] NonStickAtom785:
Hey I'll check that out. I already ported Resurrection Remix and Lineage OS 14.1 from the LG K20 Plus, but the bugs need to be fixed. Theres an issue with the Wifi not connecting and there's an issue with the camera. It opens but shortly after it opens it says Media Server failed to start.

I haven't done much development but I can start trying to fix them. If you want to try and fix my ports here's the links:

Lineage OS 14.1 Port

Resurrection Remix Port

Here's the link I followed for porting and bug fixing.

[Guide] AIO PORTING GUIDE [MTK-QUALCOMM-RECOVERY-BUGFIX-VOLTE]

I'm about to extract the Kernel from our stock boot.img(AKA: boot.img-zimage) using Android Image Kitchen for android.

I'll make a porting thread guide for our device. It won't show you how to fix the bugs but it will show you how to do the basic things such as fixing the error in twrp from the assert. I'll try and get it done today.
[Miscellaneous Android Development] PAWGLove:
Ok Sounds great im downloading your ports now. (Fair warning im a scrub) so dont expect me to work any wonders, but I'll definitely mess around and see if i accodently fix something.

Is that the Lineage Port from the 1st page of this post? Or is it a bootable buggy version?
[Miscellaneous Android Development] NonStickAtom785:
Bootable Buggy One

Btw you don't have to be a pro to fix bugs. And I like that your up to a challenge. You remind me of me. I would do try to fix them myself but I'm up to something else with updating my ROM. My signature is a link to my thread. You could subscribe to it for the new updates. I'm releasing a new one today that will boot quicker.

Here's the zimage for future porting....

https://www.androidfilehost.com/?fid=11410963190603868521
[Miscellaneous Android Development] PAWGLove:
Everything seems good on Resurrection Remix except for no camera and no LED Flashlight.

Thanks for the good port(:!
[Miscellaneous Android Development] NonStickAtom785:
Those issues are understandable. I still need to change the build.prop to cv1 info, but the camera and LED Flashlight are the most common issues with simple solutions.
[Miscellaneous Android Development] AustinGarrick1818:
I could make you a script to do that
[Miscellaneous Android Development] NonStickAtom785:
I already did
[Miscellaneous Android Development] LgPWN'd:
so armondpop's Liniage doesn't work at all?

i ask cause I just flashed it from a gitdroidtips link

and 4 minutes in it's still just the boot animation

any help appriciated thanks
[Miscellaneous Android Development] NonStickAtom785:
Yah. Unfortunately it dosen't boot. Here's another one though. It's LOS 15.1. But there are some bugs still.

https://xdaforums.com/showpost.php?p=78831381&postcount=270
[Miscellaneous Android Development] LgPWN'd:
Thanks for this

I'm downloading it now, possibly in a week or 2 I'll be able to test it out.

the T-mobile Oreo Flash script Killed my Phone completely but I'll be buying a new one in a couple weeks...

maybe I'll be able to help with some of the bugz too.

You know what would be great is to work on something like a network UN-locked Rom usable across all cv1 devices

I really wish my linux box had enough ram to build los or RR .

I can compile twrp but it always dies when I try to compile los or anything.

Been trying to build los for a low-end budget phone.

managed to unlock it's bootloader and get twrp working for it... but

I can't build the whole ROM.

If you know anyone that may be interested in helping build LOS for it They can get all the credit for the ROM

the device is the Maze Speed. and I have Full scatter-file and dumped all parts of the firmware.

so if anyone wants to help build for it, I can save them a lot of prelim. work on it...
[Miscellaneous Android Development] NonStickAtom785:
If you Windows 10 and it's on the latest update, you don't need Virtualbox to run Linux. In the latest updates Microsoft has added a WSL, which stands for Window's Sub Linux. To enable it you go to Programs and Features in the control panel and click on "Turn Windows features on or off".

Restart your PC and then go to the Windows Store and install Ubuntu 18.04.

You can follow this link to setting up the build environment or if you'd like. Me and [MENTION=7890713]AustinGarrick1818[/MENTION] are currently having issues building the kernel for Lineage OS 15.1. The build that I gave you was made by Travis Holt.

Here's our current repo links and references:

Main Github Reference:https://github.com/LG-SD4XX

Kernel Tree: https://github.com/LG-SD4XX/android_kernel_lge_cv1

Device Tree:https://github.com/AustinGarrick1818/android_device_lge_cv1

LG SD4XX Common: https://github.com/AustinGarrick1818/android_device_lge_sd4xx-common

Roomservice.xml: https://github.com/AustinGarrick1818/android_device_lge_cv1_roomservice

Local_manifest: https://github.com/LG-SD4XX/local_manifest

The first Trees made for cv1:

Vendor Tree: https://github.com/armandopartida0/vendor_lge_cv1

Device Tree: https://github.com/armandopartida0/android_device_lge_cv1

Kernel Tree: https://github.com/armandopartida0/android_kernel_lge_cv1

TWRP Device Tree: https://github.com/armandopartida0/twrp_device_lge_cv1

The device chip family is:

msm8917

msm8937

msm8953

msm8998

This link may be of use to you:

https://review.lineageos.org/c/LineageOS/android_hardware_qcom_power/+/217178

All the SD4XX repo are from device chip family above. We have a official pie blobs to from the 8937. Build if you can!
[Miscellaneous Android Development] LgPWN'd:
Has anything more been done with this? I managed to boot it on my new LG K8 2018 unlocked, had to use pitchblack recovery,

the twrp gave error 255.

Camera as you said doesn't work... ANY IDEA WHY? anything I can do to help fix it? I made full dumps of everything before tinkering this time.

is the problem in device blobs or is a kernel problem?
[Miscellaneous Android Development] Recker01:
Is there a way to restore from backup? or at least boot twrp?
[Miscellaneous Android Development] darkherman:
so, there is no development for this LG Aristo 2 to play with rom like LineageOS LineageOS 15.1,RR Oreo etc... the oreo source is available in their web

http://opensource.lge.com/osSch/list...LL&search=x210:fingers-crossed:
[Miscellaneous Android Development] tailstwilight:
Get the Pie firmware for the Aristo 3 X220MA. It's Pie, don't direct flash the KDZ. Some work is going to be needed but these phones are basically identical hardware wise. Aristo 2 and 3 both use X210MA boards. I think the RSA keys are different. Let's try to Trebleize our devices. You should use the X220 base since it will work on devices that have skewed display problems.
[LeEco Le 2 Guides, News, & Discussion] maclee4real:
I recently bought a LeEco Le S3 X522 Qualcomm Snapdragon 652 chip set from aliexpress.com Phone already came WITH EUI 5.8.021S Build IFXNAOP5802141S installed With google apps. No OTA update, and

SIM Slot 1 supports full range of services, including voice call, data services and VoLTE/Wi-Fi calls. While SIM Slot 2 supports GSM voice calls and SMS only.

The only difference between Le 2 and S3 is the version of Quick charge and the ROM, every other thing remains the same.

I know to solve the problem of only one slot using voice call, data services and VoLTE/Wi-Fi calls is simply changing the ROM, which I did and it worked. But I don't like the fact that on the back of the phone, the model is written as Le X522 and the in about phone it is X520, so I decided to update the phone.

So I downloaded a stock ROM from https://devsjournal.com/download-letv-official-stock-rom.html#Le_S3_X522_8211_US_Le_2_Pro_Stock_ROM to download EUI 5.9.028

1523502484_FULL_S2_PLUS_S2_PLUS-CN-FN-HEXCNFN5902812161S.zip tried to install it and i got error message saying "Updater process ended with ERROR: 7 Error installing zip file 1523502484_FULL_S2_PLUS_S2_PLUS-CN-FN-HEXCNFN5902812161S".

Okay, I deleted the 2 lines from updated-script saved it and tried it again and still got the same error.

I downloaded another file. 1523442203_S2_X520-CN-FN-IEXCNFN5902802011S-5.9.028S.zip with the same error 7 but after editing the script it installed but got stock after patching system image i will upload screenshots so I really don't know what to do and where to get a working ROM EUI 5.9.026 or EUI 5.9.028

Thanks in Advance
[LeEco Le 2 Guides, News, & Discussion] Bobfish:
I think you flashed the wrong rom.That rom is for "le_x6" MTK devices (X620/X626).

Download X522 rom and reflash.

Version 28s has problem with google services, better to flash older versions.

Search for it in the forums here or on needrom.
[LeEco Le 2 Guides, News, & Discussion] maclee4real:
Thanks for your reply.

I have that in mind also, but the first ROM I installed is Le S3 (X522 – US Le 2) Pro Stock ROM and the second Le 2 (Qualcomm) Stock ROM hung at the end so had yo force reboot phone. The screenshot is there
[LeEco Le 2 Guides, News, & Discussion] Bobfish:
Is the bootloader unlocked?If bootloader is already unlocked , and Twrp installed, it won't boot stock rom.You need to root with Magisk.

Download Magisk zip and install from Twrp.

Don't do this if bootloader is locked, you'll brick the phone.
[LeEco Le 2 Guides, News, & Discussion] maclee4real:
Thanks, the bootloader is unlocked, if the bootloader is locked I don't think I would be able to install TWRP. I noticed any ROM with S2 will work and ROM with X6 don't work is it that S2 is for snapdragon and X6 is for MTK?

Again I got another phone (same phone) installed TWRP and Backed up the ROM and tried to restore it into the other phone and it didn't load the backup (it didn't see the file just the folder) what do I really need to do to get the restore working or get the latest snapdragon rom for S3?
[LeEco Le 2 Guides, News, & Discussion] Bobfish:
Yes , X6 is Mtk chipset.

Maybe try wipe cache/data/dalvik, then root with Magisk zip.

If that doesn't work, download and flash X522 Eui 5.8 just to get the phone to boot up.

Just saw this:

https://xdaforums.com/le-2/how-to/sd-652-firmware-stock-rom-5-9-023s-t3632277
[Lenovo P2 Questions & Answers] genesian2k15:
hi everyone

my phone was dropped in water.

when i checked it was still working but the screen starts to have like horizontal lines coming from down to up

. so i turned it off, dried it with a towel…

i restarted it later it started well…then it restarted with green and red English words as it it was programming or android installing updates or firmware lines.. hope you understand me...

so i turned it off again to disassembly well and dry it better…

the problem is now when i plug it to charge it, i can feel it vibe in repeat mode when i connect it... as if it was vibering, then wait then vibering...in loop

i tried a recovery mode but still nothing on screen…

my pc don't see it when i connect it…

doesn't smell good at all :crying:

and another problem...when i disassemblied it i think i break a little part of the nap where i connect the screen nap on it...at the top right…

you can see it on the picture i added…

i'll try to disassembly again to see if i can do something

thanks in advance for your advices and help

genesian
[Lenovo P2 Questions & Answers] balugudidiot:
my mob also fell in water 9months ago...i didnt get any lines..,but i my self switched it off...later it didn't switched on shown black screen,only charging led works..that too different colors...so just kept it aside and after few hours magically switched On...
[Lenovo P2 Questions & Answers] genesian2k15:
I juste Hope the little part i broke see the picturee won't Make it dead definitevely
[8.9" Kindle Fire HD Android Development] monster1612:
Sorry for jumping on the bandwagon a little late here. Seems like a promising project. If you managed to get mainline 4.18 to at least boot (which sounds hard in and of itself), how would it work out if it booted nicely on Android? that wouldn't be too bad of a prospect. Complicated, yes, but maybe remotely possible. I'd be willing to test drive it on my non-lte jem - after I give this project a spin, of course. :)
[8.9" Kindle Fire HD Android Development] ipipipipip:
A quick update:

Bluetooth now neither require to be powered on prior reboot (there was a clock that I forgot to enable that prevented bcm module from starting), nor a user-space firmware upload.

It now uses serdev bus and kernel-space driver to upload firmware, that removes the hassle of adding system daemon that will properly initiate bluetooth with the correct tty.

There is no proper way for now to check what version of jem/jemlte device you are using so you have to rebuild the kernel with the correct firmware in "firmware/brcm/BCM2076B1_26MHZ.hcd". The default firmware is for lte version, so if you use non-LTE version please replace the file "firmware/brcm/BCM2076B1_26MHZ.hcd" with the 20MHZ one from the same directory (just remove the 26MHZ one, and change 20MHZ to 26MHZ in file name).

WiFi no longer causes issues on resume, and device suspends and resumes properly (more or less), I haven't measured battery drain)

Bad news:

I've bricked my device and not sure if I still can revive it, looks like eMMC is almost dead. Or another case of crappy samsung moviNand firmware.

It is detected over USB as OMAP4470 device and it looks like cpu does not detect emmc.

After about 5 minutes (some kind of watchdog??) it manages to boot u-boot aka fastboot. Any other action that tries to modify content on emmc causes the flash controller lockup and communication with it is no longer possible.

Soldering wires directly to pcb pads doesn't help much, the card is not detected by card-reader.

The main idea for now is to use vendor command 62, as mentioned in one of #Hashcode's posts to wipe all the content of the chip. The problem is that I have wiped linux partition and can't boot into any kind of working linux system on the device. (Recovery tries to mount some partitions rw and thus makes flash chip inaccessible). Guess it's time to make an NFS rootfs and boot the device over USB network.... Or maybe someone knows how to prevent TWRP from accessing partitions on device?

In the worst case scenario I'll have to replace emmc chip (if it's not glued too hard in place), curious if some 128GB will work :P

Or maybe someone has a spare PCB, or a broken device that they no longer need and may donate?
[8.9" Kindle Fire HD Android Development] ipipipipip:
There will be no GPU or video decoding acceleration, which might be a problem with modern apps, if you wish, go on and try, might be interesting to have a look, I don't have much experience in building android ROM's.
[8.9" Kindle Fire HD Android Development] ipipipipip:
Sup, have some news on the progress of the project

An eMMC on my tablet died completely, thus I had to replace it with another one. My initial intent was to place some 64gig SanDisk emmc 5.1 from ebay, but I was not sure if it'll work with omap4 and that I won't fry it in the process of replacement. So I've bought some similar scrapped 16gig variant from a local reseller for a couple of pennies. After recovering partition layout and bootloaders the tablet came back to life, thus it's pretty safe to put whatever eMMC chip you have on your hands in your tablet) (it's time to order a larger capacity flash now, 16 gig is rather scarce for both android, arch and some content). The trusty old stock kernel, on the other hand, needed a tiny patch to let kernel understand a flash from the future. The driver checks for known emmc protocol version and unloads flash driver if the revision is too high.

Now feeling more confident in unbrickability of my tablet, I've gone an extra mile of porting mainline U-Boot bootloader to the tablet.

The port is pretty minimal, just support for serial port, usb/fastboot, and framebuffer console. Since pinmuxing and HW initialization is done via stock bl, nothing much to do. But it adds ability to freely manipulate boot sources, kernels, ramdisks, supports dtbs and overlays, environment save/restore, and external boot scrips on a FAT boot partition ). For some reason bootloader font is corrupted and hard to read, bit it should be easy to fix.

The good parts:

kernel version is bumped up to the latest 5.0.0

enabled mpu6050 IMU sensor

enabled tmp103 temperature sensor, supposedly case temperature...

enabled hall sensor that is triggered by a case lid magnet, It's mapped as a SW_LID key

some cleanups for display panel code

resolved HDMI edid issue: two part problem of wrong DDC pin mux sequence and wrong HDMI vdda supply regulator match string

Regressions:

Somewhere in the process it lost the ability to resume from suspend, have to find what caused that.

New bootloader does not handle IDME tags, therefore for the stock os I had to hardcode serial and MAC addresses in stock kernel idme driver. But since there is plenty of place to put different bootloaders on our tablets you may use one for stock rom, and another for development.

A second part of the update is coming soon...
[8.9" Kindle Fire HD Android Development] Jack_Kekzoz:
Hi there,

This is very exciting work - how is the tablet doing a year on? I'm wondering how much of your work is applicable to the 7 inch equivalent, seeing as the board is common, just with a few minor hardware differences.

Thanks,

Jack