Related
After I replaced the framework-res.apk(modofied) in my phone, my phone restarted auto and still can not enter the system, the screen stuck in the 'X' screen, how could I recover the original framework-res.apk to my phone (I have backup the original one ) ?
pls help,help.......
Umm, boot into recovery and copy it over with ADB...
adb push your backed up framework file as soon as you see the boot animation.
if you don't have it get it from your ROM zip.
may be easier to nandroid restore if you have a recent backup.
adb show "device not found", how could I do?
Like I said, do it in recovery mode.
Are you in a command prompt from within you android ask folder.
E.g c:\ANDROIDSDK\tools
Then open a command prompt from that folder tree.
Then try adb devices
Sent from my Nexus One using XDA App
evilkorn said:
Like I said, do it in recovery mode.
Click to expand...
Click to collapse
Sorry,you mean that I should in the recovery mode, then link to my PC,then run the adb order ? my recpvery version is 3e, is it ok ?
lisalasu said:
adb show "device not found", how could I do?
Click to expand...
Click to collapse
adb logcat , should wait till adb is available. If it never shows a log then recovery/nandroid will be the only way.
britoso said:
adb logcat , should wait till adb is available. If it never shows a log then recovery/nandroid will be the only way.
Click to expand...
Click to collapse
Thought I fail to adb now, anyway,tks all for help
Im using CM 7.2 RC1 hero ported to X8 but when i want check logcat it just blank doesn't appear anything.
Anyone knows about it ?
PLease help
Advance thanks.
weird ...maybe it is a problem with the rom or maybe it is a bug
The ROM it's self have logcat in system/bin/
Others all fine but only this logcat give problem....
Actually i was updated rooting system to SuperSU and Binary plus changed busybox to 1.19.4 version and toolbox too.
Do you thing it's happen because of this updating ?
VillainZ said:
The ROM it's self have logcat in system/bin/
Others all fine but only this logcat give problem....
Actually i was updated rooting system to SuperSU and Binary plus changed busybox to 1.19.4 version and toolbox too.
Do you thing it's happen because of this updating ?
Click to expand...
Click to collapse
I am having a similar concern. Mine says "waiting for device", but nothing happens. The logcat file exists but is blank.
jnow2 said:
I am having a similar concern. Mine says "waiting for device", but nothing happens. The logcat file exists but is blank.
Click to expand...
Click to collapse
do you have usb debugging enabled?
fifo171 said:
do you have usb debugging enabled?
Click to expand...
Click to collapse
Yes, usb debugging is enabled. I am able to copy files between pc and phone, push adb commands via terminal, etc. Logcat is the only issue I'm having.
I was able to find help in another forum. My problem was that I was using adb commands through Terminal Emulator. I initially entered "adb logcat > /sdcard/logcat.txt". As long as you type "su" and receive "#" prompt, type the same command above eliminating" adb". It works. Hope this helps!
Sent from my LS670 using XDA
MIT activity manager
jnow2 said:
I was able to find help in another forum. My problem was that I was using adb commands through Terminal Emulator. I initially entered "adb logcat > /sdcard/logcat.txt". As long as you type "su" and receive "#" prompt, type the same command above eliminating" adb". It works. Hope this helps!
Sent from my LS670 using XDA
Click to expand...
Click to collapse
My adb logcat shows:
W/WindowManager( 152): Window Window{2b2f8b10 com.crashapps.easypccontrol_android/com.crashapps.easypccontrol_android.ServersActivity paused=false} destroying surface Surface(name=com.crashapps.easypccontrol_android/com.crashapps.easypccontrol_android.ServersActivity, identity=152), session Session{2b254ba8 uid 10071}
I want to open it in MIT activity manager any ideias?
Hello all,
I've noticed the lack of a guide for pulling ADB logs for developers. Being a developer, I wanted a quick link to send people to, rather than reexplaining.
If you are looking for a GENERAL explanation on how to get a logcat, or setup your computer for pulling a logcat, look at this amazing guide here:
http://forum.xda-developers.com/showthread.php?t=2274119
Consider this guide an extension for the above thread, making an easy how-to for developers to point people to.
What this guide is NOT:
- A guide on how to pull a logcat in general
- A guide on how to setup adb on a computer
This guide is/will:
-Assume you know how to connect via adb
-Assume you have installed drivers and adb
-A way to show common users to get the logs the developers need
So I personally build for devices I don't own. A LOT. So, should it bootloop(specifically this) or not boot at all, I NEED these logs to help fix the problem. Most users are willing to do so..... as long as you teach them. So this is my one-size-fits-all guide to this.
Note: Later, I will do a write-up on how to pull kernel logs as an extension to this in the second post
To pull a logcat during a bootloop, you need to have adb permissive. This can be done several ways. I have added to the build.prop manually before but that was in TWRP and is a pain to guide users on. It's SUPPOSED to be done with the ramdisk, but I can't ask users to pull their ramdisk and edit it and reflash. So I have made a flashable zip to extract ramdisk and add a permissive adb property to default.prop
The zip will be in the downloads below, all you need to do is flash it when you see a ROM is bootlooping.
Note: Some kernels may not work with this, and it's based off of Anykernel. If the zip fails, don't worry, it has a fallback that it will add same thing to build.prop, and that should usually work.
After flashing, hook the phone/tablet up to your computer and run this in your Terminal:
On Linux:
Code:
adb logcat > ~/log.txt
That will store logcat into your home folder.
On Windows:
Code:
adb logcat > %UserProfile%/Desktop/log.txt
That will store logcat on your Desktop.
How do I stop logging?
You can either stop logging by hitting [CTRL] + C in the terminal or by unplugging device.
How do I know when to stop logging?
Usually, you can safely stop logging after about one minute for MOST problems, BUT I believe 5 minutes of logging would be the best bet to stop logging, so all the errors are caught.
How do I get the log to the developer?
You can get a log to a developer by Dropbox, Google Drive, or a file sharing site, but personally I like pasting sites like hastebin.com, pastebin.com, or paste.ubuntu.com. This is a developers/users personal preference though. Personally, I really, really like hastebin. For a pasting site, just open it in your browser and open the log with notepad or equivalent, and do [CTRL] + A and [CTRL] + C to copy the whole log, then paste onto the site. Then share the link the site gives you with the developer.
How do I get the log, when I didn't even get to the boot animation?
Usually, this is a kernel problem, and is almost deserving of it's own write-up, and instructions will be available in the second post.
Thank you all, and should you see a problem, or need more questions answered, please tell me so in replies.
Keep it cool,
Jacob(USA-RedDragon)
So your kernel didn't boot. Well dang. This can be one of the worst problems. So, I'm going to HOPE you have TWRP, since CWM is pretty much dead.
This is more advanced, because you have to use Terminal command in TWRP.
Now, don't be daunted by this, since it's terminal commands, it's quite easy.
As a general rule of thumb(there are different devices with different kernel logs, though), 3.10 kernels(pretty much anything in the last 2 years) have a log in /sys/fs/pstore/console-ramoops and 3.4 and prior kernels have /proc/last_kmsg.
You can see kernel version in Settings -> About Phone
So to pull these logs, you need to be in TWRP DIRECTLY after a failed boot.
Go to Advanced->Terminal Command and type these commands in. One will fail the other will work. Should both of them fail, restart and try to boot again, then go back to TWRP.
Code:
cp /proc/last_kmsg /sdcard/kernellog.txt
Code:
cp /sys/fs/pstore/console-ramoops /sdcard/kernellog.txt
Now you can restore your backup and boot normally. Once you've booted up, you can either share the files with Google Drive or Dropbox or whatever in Android, or you can pull them to your computer with these Terminal commands:
On Linux:
Code:
adb pull /sdcard/kernellog.txt ~/kernellog.txt
That will store log into your home folder.
On Windows:
Code:
adb pull /sdcard/kernellog.txt %UserProfile%/Desktop/kernellog.txt
That will store log onto your Desktop.
Then share log like you would in the above post
FAQs:
None at this time
when I execute the command, it says waiting for device.
I have a galaxy s5
and the monitor, my device is offline
@Gayos24 what command did you type??? OP and 2ND post show numerous commands. Nobody can help if you don't give details.
The monitor says device offline...is the screen turned on??
HasH_BrowN said:
@Gayos24 what command did you type??? OP and 2ND post show numerous commands. Nobody can help if you don't give details.
The monitor says device offline...is the screen turned on??
Click to expand...
Click to collapse
i type this command adb logcat > %UserProfile%/Desktop/log.txt
yes the screen turning on.
@Gayos24 you use that AFTER you run a logcat, there is a link in the OP on how to do that.
HasH_BrowN said:
@Gayos24 you use that AFTER you run a logcat, there is a link in the OP on how to do that.
Click to expand...
Click to collapse
yes
I flashed logcatflasher zip via twrp and connected my device. I wrote command for windows but there was no logging in the terminal
But the adb via usb need an authorization to enable,how to get pass when bootloop?
Sent from my MI 2C using XDA-Developers mobile app
Sun Shower said:
But the adb via usb need an authorization to enable,how to get pass when bootloop?
Sent from my MI 2C using XDA-Developers mobile app
Click to expand...
Click to collapse
use adbd
Gayos24 said:
use adbd
Click to expand...
Click to collapse
Thank you to answer me,is there any thread or guide can help me,I don't know how to use it.
Sun Shower said:
Thank you to answer me,is there any thread or guide can help me,I don't know how to use it.
Click to expand...
Click to collapse
just donwload the file and extract adbd in system/xbin (rom)
and the command is the same as normal logcat
sorry for my english
awsome, just awsome
what command did you type?
I am currently testing out Custom ROMs for DEVs and I cannot find how to take a Log if I cannot Boot the device or get into TWRP. With newer devices, for example, I am currently working on a OnePlus 6, with A/B Partitions. If the device does not boot on A, it is supposed to Boot on B, so with this application, how to take a Log before the device switches Partitions and Boots on the Partition that CAN Boot?
I tried the adbd archive but there is no xbin folder for me, I just put in sbin folder. I cant get a logcat from boot because it says waiting for device the code i'm trying is this one adb logcat > logcat.txt
USA-RedDragon said:
So your kernel didn't boot. Well dang. This can be one of the worst problems. So, I'm going to HOPE you have TWRP, since CWM is pretty much dead.
This is more advanced, because you have to use Terminal command in TWRP.
Now, don't be daunted by this, since it's terminal commands, it's quite easy.
As a general rule of thumb(there are different devices with different kernel logs, though), 3.10 kernels(pretty much anything in the last 2 years) have a log in /sys/fs/pstore/console-ramoops and 3.4 and prior kernels have /proc/last_kmsg.
You can see kernel version in Settings -> About Phone
So to pull these logs, you need to be in TWRP DIRECTLY after a failed boot.
Go to Advanced->Terminal Command and type these commands in. One will fail the other will work. Should both of them fail, restart and try to boot again, then go back to TWRP.
Code:
cp /proc/last_kmsg /sdcard/kernellog.txt
Code:
cp /sys/fs/pstore/console-ramoops /sdcard/kernellog.txt
Now you can restore your backup and boot normally. Once you've booted up, you can either share the files with Google Drive or Dropbox or whatever in Android, or you can pull them to your computer with these Terminal commands:
On Linux:
Code:
adb pull /sdcard/kernellog.txt ~/kernellog.txt
That will store log into your home folder.
On Windows:
Code:
adb pull /sdcard/kernellog.txt %UserProfile%/Desktop/kernellog.txt
That will store log onto your Desktop.
Then share log like you would in the above post
Click to expand...
Click to collapse
sorry but in my device wasn't have this "/sys/fs/pstore/console-ramoops" I was browse, and did not found it... only have "sys/fs/..." if I try, still work it or not?
I have a couple of questions and I'm hoping that this forum can provide a response.
1. adb logcat not found
I have a linux laptop and have installed platform tools and have used fastboot, adb sideload quite a bit. But adb logcat just does not work.
see below while inside TWRP
5x $ adb devices
List of devices attached
00ca0a5e7fe31c03 recovery
5x $ adb logcat
/sbin/sh: exec: line 1: logcat: not found
5x $ adb shell
~ # logcat
/sbin/sh: logcat: not found
whats missing?
2. When should adb logcat be run if I wanted to capture logs when my phone keeps spinning on google animation? Can i run adb logcat > foo while I'm in recovery and then reboot from recovery or is there a different method?
thanks
I was hoping that someone could respond to the right way to capture logs during bootloop.
My problem:
Trying to capture logs on a bootloop of andrid 10 pixel experience on nexus 5x.
What I have do so far?
Flashed the ROM and zip and rebooted. No logcat seen.
My specific question.
OP says this.
After flashing, hook the phone/tablet up to your computer and run this in your Terminal:
On Linux:
Code:
adb logcat > ~/log.txt
My problem is that when the phone is rebooting, adb devices does not show anything and thus adb logcat always displays a <waiting for device> message. Thus, how can any log be captured to debug the problem?
i was trying to root my onepluse 3t with nougat 7 update but i stuck in twrp asking for password and i cannot use twrp to install super su cuz of that
then after many Attempts i don't know what i did exactly i try to wipe and mount then the system was removed and phone is opening on twrp and bootloader only.
i download nougat 7 update file and i try to install it from twrp but i can't and i try from adb (sdk) more than 100 times but not work giving error (closed)
now my phone is not working and i don't know what to do
pls any one help
Try reformating your internal data (including sdcard) using twrp, plug it to a pc, use mtp to copy the latest full rom to it, flash that and voila.
Jo_Jo_2000 said:
Try reformating your internal data (including sdcard) using twrp, plug it to a pc, use mtp to copy the latest full rom to it, flash that and voila.
Click to expand...
Click to collapse
i try every thing i install stock recovery and i but nougat in internal storage but when trying to press install from internal storage nothing happens it is not active
i try also to install nougat using adb sideload but every time reach to 45% then stop and giving failed message
amrfoudaas said:
i was trying to root my onepluse 3t with nougat 7 update but i stuck in twrp asking for password and i cannot use twrp to install super su cuz of that
then after many Attempts i don't know what i did exactly i try to wipe and mount then the system was removed and phone is opening on twrp and bootloader only.
i download nougat 7 update file and i try to install it from twrp but i can't and i try from adb (sdk) more than 100 times but not work giving error (closed)
now my phone is not working and i don't know what to do
pls any one help
Click to expand...
Click to collapse
So it sounds like the phone had a problem with Encryption. Not a problem.. If you can get into the phone set the password for your screen lock and this will reset your encryption. However it seems like you can't get this far. Again no problem. The password issue is there probably isn't a password on TWRP. When it prompts you for a password hit cancel. If this is the case and you may notice your drive space is zero. If it is post here and I will try to help you through that.
DarqAnshin said:
So it sounds like the phone had a problem with Encryption. Not a problem.. If you can get into the phone set the password for your screen lock and this will reset your encryption. However it seems like you can't get this far. Again no problem. The password issue is there probably isn't a password on TWRP. When it prompts you for a password hit cancel. If this is the case and you may notice your drive space is zero. If it is post here and I will try to help you through that.
Click to expand...
Click to collapse
i try that too and when press cancel the drive space is showing zero i try every password i know and (default_password) too
then i try to install custom rom hydrogen from TWRP and i success but i was stupid to try to update it to official nougat again manually then every thing remain to the same again i am stuck in TWRP window or fastboot
i try to install hydrogen again from TWRB but not success again and i cannot use the phone
amrfoudaas said:
i try that too and when press cancel the drive space is showing zero i try every password i know and (default_password) too
then i try to install custom rom hydrogen from TWRP and i success but i was stupid to try to update it to official nougat again manually then every thing remain to the same again i am stuck in TWRP window or fastboot
i try to install hydrogen again from TWRB but not success again and i cannot use the phone
Click to expand...
Click to collapse
If you can get into TWRP after hitting cancel then this isn't a problem. These are the steps you need to take to load Nougat (or any OS) on to your phone.
Boot into your recovery (TWRP in your case).
You will slide to cancel then hit Advanced.
Wipe The phone of everything (System/cache/etc).
Click Sideload and then plug into your computer of choice.
On your computer open a command prompt and type the following:
ADB Devices
This should show you your devices if your phone is connected to the computer. If you do not see anything then install the drivers onto your computer (If it says that you don't have ADB then install Android Bridge onto your system).
Next type:
ADB Sideload <Name of your Nougat image>
Once this is done your phone should be able to boot into the system.
DarqAnshin said:
If you can get into TWRP after hitting cancel then this isn't a problem. These are the steps you need to take to load Nougat (or any OS) on to your phone.
Boot into your recovery (TWRP in your case).
You will slide to cancel then hit Advanced.
Wipe The phone of everything (System/cache/etc).
Click Sideload and then plug into your computer of choice.
On your computer open a command prompt and type the following:
ADB Devices
This should show you your devices if your phone is connected to the computer. If you do not see anything then install the drivers onto your computer (If it says that you don't have ADB then install Android Bridge onto your system).
Next type:
ADB Sideload <Name of your Nougat image>
Once this is done your phone should be able to boot into the system.
Click to expand...
Click to collapse
i try hundred times giving error: closed
amrfoudaas said:
i try hundred times giving error: closed
Click to expand...
Click to collapse
if you are getting error closed your adb bridge session might be the problem.
Unplug your phone from the USB
From your computer try these commands
Code:
adb kill-server
Code:
adb start-server
Then plug the phone back into the usb and put it into sideload on twrp and type
Code:
adb devices
Do you see a device then?
DarqAnshin said:
if you are getting error closed your adb bridge session might be the problem.
Unplug your phone from the USB
From your computer try these commands
Code:
adb kill-server
Code:
adb start-server
Then plug the phone back into the usb and put it into sideload on twrp and type
Code:
adb devices
Do you see a device then?
Click to expand...
Click to collapse
yes it is there and i start the sideload for nougat but it is stopped in 45% not reach 100 many times
amrfoudaas said:
yes it is there and i start the sideload for nougat but it is stopped in 45% not reach 100 many times
Click to expand...
Click to collapse
and sometimes giving error closed
Try this it should work
http://forum.xda-developers.com/one...k-unbrick-tutorial-oneplus-3t-t3515306/page10
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
pitrus- said:
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
Click to expand...
Click to collapse
Which thread is that? Can you link to it please?
m0d hipp¥ said:
Which thread is that? Can you link to it please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=70403073
Now deprecated. Go here instead. Mods can clean this out. https://forum.xda-developers.com/moto-g8/development/recovery-twrp-3-4-0-0-t4155045
First of all, I did not build this myself. I just pulled it apart and made some modifications to hopefully fix the touchscreen for you folks. I also do not own this device. This is a port from the Moto G8 Plus, and it's based off the awesome work done by @mauronofrio
Disclaimer provided by twrp.me, with an addition by myself;
Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no responsibility for any damage that may occur from installing or using TWRP.
Additional note: I am not responsible for bricked devices, but I will try to help you fix your phone if you turn it into a paperweight. This twrp is very much in the testing phase. We need to figure out what works, and what doesn't, then try to land this plane. Please help me with feedback so that I can help you!
WARNING: You must have the bootloader installed to both slots (if applicable) before making modifications. If not you will brick your device if it changes slots.
Instructions
1. You need fastboot and adb installed, or you can use the portable version (my preference) found here.
2. You need an unlocked bootloader as well. If you don't know how to do that, then follow the instructions found here on Motorola's website.
3. Reboot into fastboot by holding Vol ↓ + Power for approximately 30 seconds.
4. From the command prompt (cmd-here.exe) type in;
Code:
fastboot boot twrp.img
5. To install the image: Copy twrp to your phone and select > advanced > install recovery ramdisk > choose twrp.img > and swipe. Flash Magisk afterwards if you're on stock. If you're using a GSI and need root, then I suggest flashing my Modded Phh SU. Install the apk afterwards.
Download: twrp.img
Source Code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_motorola_doha
i got the phone to boot twrp but the touch screen does not work on the moto g fast xt2045-3
Clothian said:
i got the phone to boot twrp but the touch screen does not work on the moto g fast xt2045-3
Click to expand...
Click to collapse
Awesome feedback. This is exactly what I need to know. Can you run the following command for me? You'll need to use adb or termux for this. I need the output.
Code:
cat /sys/devices/virtual/touchscreen/*/vendor
Spaceminer said:
Awesome feedback. This is exactly what I need to know. Can you run the following command for me? You'll need to use adb or termux for this. I need the output.
Code:
cat /sys/devices/virtual/touchscreen/*/vendor
Click to expand...
Click to collapse
No such file or directory I’m also looking around in there any luck getting a root on this thing? Mine errors when I try to side load the magisk I’m a little new to all this. Also I ran this in adb shell if that matters or not
Clothian said:
No such file or directory I’m also looking around in there any luck getting a root on this thing? Mine errors when I try to side load the magisk I’m a little new to all this. Also I ran this in adb shell if that matters or not
Click to expand...
Click to collapse
Try running this instead from adb...
Code:
adb root
ls /sys/devices/virtual/touchscreen
Spaceminer said:
Try running this instead from adb...
Code:
adb root
ls /sys/devices/virtual/touchscreen
Click to expand...
Click to collapse
so i tried to run this with just adb and got nothing but errors but if i run this in shell with cat it does say this is a directory!!!
also im sorry for slow respond my internet where i am is giving me issues
Clothian said:
so i tried to run this with just adb and got nothing but errors but if i run this in shell with cat it does say this is a directory!!!
also im sorry for slow respond my internet where i am is giving me issues
Click to expand...
Click to collapse
You're going to need proper root access, and termux. I tried without root and get permission denied, with root, no issues.
ran the following in termux with su active after getting root access
the output is in parenthesis (output)
cat /sys/devices/virtual/touchscreen/*/vendor (states nothing)
ls /sys/devices/virtual/touchscreen (NVT-ts)
Clothian said:
ran the following in termux with su active after getting root access
the output is in parenthesis (output)
cat /sys/devices/virtual/touchscreen/*/vendor (states nothing)
ls /sys/devices/virtual/touchscreen (NVT-ts)
Click to expand...
Click to collapse
We're getting somewhere. Now try the following...
Code:
cat /sys/devices/virtual/touchscreen/NVT-ts/vendor
I have root with system. But using adb or termux I get cannot run as root in production builds.
madbat99 said:
I have root with system. But using adb or termux I get cannot run as root in production builds.
Click to expand...
Click to collapse
Hot damn! I haven't seen you since the G6 days. We can really kick this thing off with you hanging around. How have you been?
Are you running a GSI right now? Or is magisk just not giving a prompt?
Spaceminer said:
We're getting somewhere. Now try the following...
Code:
cat /sys/devices/virtual/touchscreen/NVT-ts/vendor
Click to expand...
Click to collapse
i have to run this under su but it opens this
novatek_ts:/data/data/com.termux/files/home #
it seems to be waiting for an input. im fresh to alot of this so if you fancy explaining what your doing as you go id appreciate it tho i understand not wanting to as well i can just as easy google it
TWRP Tests
Clothian said:
i have to run this under su but it opens this
novatek_ts:/data/data/com.termux/files/home #
it seems to be waiting for an input. im fresh to alot of this so if you fancy explaining what your doing as you go id appreciate it tho i understand not wanting to as well i can just as easy google it
Click to expand...
Click to collapse
I'm finding info I need for your touchscreen. You want to give this a go for me? test2.img
Test it with the following command from fastboot, and tell me if the touchscreen works.
Code:
fastboot boot test2.img
Edit: If that doesn't work then try this one. test3.img
Code:
fastboot boot test3.img
You folks had touchscreen drivers and firmware binaries from the Moto G8 Plus in there. I have swapped them out for your native drivers and binaries.
Spaceminer said:
Hot damn! I haven't seen you since the G6 days. We can really kick this thing off with you hanging around. How have you been?
Are you running a GSI right now? Or is magisk just not giving a prompt?
Click to expand...
Click to collapse
Just running stock rooted. Air conditioning service tech, I work like 100 hours per week in summer. I'll try to stop in. Broke my g6 play screen and grabbed this phone.
madbat99 said:
Just running stock rooted. Air conditioning service tech, I work like 100 hours per week in summer. I'll try to stop in. Broke my g6 play screen and grabbed this phone.
Click to expand...
Click to collapse
Hey @madbat99 Long time brother, the last Moto I had was also the G6 Play from Boost Mobile, I've since been through the Coolpad Legacy and now the LG Stylo 6, I bought the Moto G8/G Fast because I missed playing around with root and roms, if yall need help with anything or for troubleshooting let me know, always willing to help the community for this device, I currently have Resurrection Remix rom installed on my Rav right now