yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] tecknight:
Yes, T-Mobile has decided not to release .kdz files for the Aristo 2 plus.

I have a stock boot image for the Aristo 2 +, but I'm not sure what your problem is.

I could also tell you how to literally turn your phone into an Aristo 2 (they have identical hardware).

I'm not sure if the Aristo 2 image would work with a T-Mobile SIM, but it certainly should.

Alternatively, If you have root on the phone now and could find someone with an Aristo 2 plus that was willing to pull their system image (or whatever other image you would need), you could restore your phone that way. Just make sure you restore the boot image last, so you don't lose root before you restore all needed partitions.
[Miscellaneous Android Development] J4¢K§0Ω.$#!7:
Yessss
[Miscellaneous Android Development] lfc222222:
The phone is stuck in TWRP loop and does not boot to system, no matter what image I flash using TWRP.

LG Bridge, while able to detect the phone, connect ultimately connect, despite trying various suggestions I've seen online to resolve that issue.

The only tool that seems to help at this point is LGUP. I'm able to put the phone in download mode (volume +). LGUP recognizes the phone as LM-X212AT.

When pointing LGUP to the .kdz file for X210MA, the flash process errors out. See image. https://pasteboard.co/HJEwB2aa.png

I suspect it needs the same device variant image to work.

I did reach out to another user with the same device who said they would be willing to provide the .kdz image but have not heard back.

If you have other suggestions how to boot back into system pls let me know.

Also, I'm aware of the HW equivalence of Aristo 2 and Aristo 2+, you mentioned "I could also tell you how to literally turn your phone into an Aristo 2 (they have identical hardware)",

I'd be interested in that method as a last resort, if you can pls share how to do that.
[Miscellaneous Android Development] tecknight:
Yes, the reason LGUP won't flash the Aristo 2 image to your phone is a "variant mixmatch".

However you CAN flash it to your phone using a version of LGUP that I modded to enable developer options.

Here's how you do it:

1. Install LGUP DualMode to your PC. Here are the instructions:

Install LGUP Dual Mode(Dev/User) on your Windows PC

Make sure you run the SetDev.bat file at the end to set it to developer mode.

2. Connect your phone and launch the modded LGUP. You will see a bunch of new options.

3. Select the PARTITION DL option then browse to and select your .kdz file.

4. Click Start. LGUP will display a large list of partitions. Click on Select All then click OK.

LGUP will then proceed to flash your phone, essentially turning it into an Aristo 2.

Your phone will retain it's IMEI, etc, but will now show up in LGUP or LG Bridge as an Aristo 2.

FYI their currently are no .kdz files released for the Aristo 2 +. Nobody will be able to get you one unless T-Mobile changes their policy on the phone. I doubt that will happen. If it does, you can always turn your phone back into an Aristo 2 +.

Regarding your actual problem, I assume you have used TWRP to flash a stock boot image to your phone ?

Cuz I know of 2 or 3 other people that had your exact same issue and they were able to flash a stock boot image and fix it.

I have a stock Aristo 2 plus boot image available.
[Miscellaneous Android Development] lfc222222:
Thanks for the quick response.

Other than the above method, is there any other possible method of "getting out" of the TWRP boot loop?
[Miscellaneous Android Development] tecknight:
2 possible ways I can think of.

1. flash a stock boot image to your phone.

I know of 2 or 3 other people that had your exact same issue and they were able to flash a stock boot image and fix it.

I have a stock Aristo 2 plus boot image available.

or

2. Find someone with an Aristo 2 + and have them pull all the partitions from their phone, using the developer LGUP DUMP option. Then you flash them to your phone one by one until it starts booting. Once you got past the normal partitions, you would have to adb shell into your phone and use the dd command to flash the partitions
[Miscellaneous Android Development] lfc222222:
Would you mind sharing boot image and step-by-step recipe for #1 above?

Would you consider this method "safer" than the dual-mode LGUP method?
[Miscellaneous Android Development] tecknight:
No I don't mind. Give me a couple of minutes to find that image,

and Yes, the boot image thing is probably safer and has the advantage of keeping your phone an Aristo 2 +. I assume you have T-Mobile as your provider ?
[Miscellaneous Android Development] lfc222222:
Thanks! Yep, T-Mobile is the provider.
[Miscellaneous Android Development] tecknight:
OK, here is the Aristo 2 plus stock boot image:

https://www.androidfilehost.com/?fid=11410932744536985814

Download it and transfer it to your phone either by USB or by MicroSD.

If you are in TWRP, mtp should be enabled so you should be able to move the file over.

In TWRP go to the initial screen and select Install, then at the bottom right click Install Image.

Browse to the boot_a2p.img file and select Boot where it asks you to select partition.

Swipe to confirm flash.

When it's done flashing, Reboot System and cross your fingers.

Let me know what happens.

BTW, it may take a while to boot up, as the stock boot image has forced encryption set, which may trigger encryption on your data and cache partitions
[Miscellaneous Android Development] lfc222222:
Followed your steps, but despite booting to system, it goes back to TWRP... :( https://pasteboard.co/HJFzvFS.jpg
[Miscellaneous Android Development] tecknight:
That's unfortunate. Let me ask you a question.

Are you seeing this when you boot up ?

I assume that you either had rooted or were trying to root your phone when this happened ?

---------- Post added at 01:09 PM ---------- Previous post was at 12:36 PM ----------

If you really want to try and keep it a T-Mobile phone, I have 2 things you could try before converting it to a MetroPCS phone.

#1 is to restore several of the partitions from backup. LG keeps flash backups of several of the smaller partitions.

These commands will restore the backed up partition to the main partition, in the event the main partition has been corrupted:

Use adb to connect to the phone. Go to a command prompt and type:

adb shell + ENTER

you should get a root shell prompt:

#

from there type the following commands:

dd if=/dev/block/bootdevice/by-name/lafbak of=/dev/block/bootdevice/by-name/laf

dd if=/dev/block/bootdevice/by-name/abootbak of=/dev/block/bootdevice/by-name/aboot

dd if=/dev/block/bootdevice/by-name/rpmbak of=/dev/block/bootdevice/by-name/rpm

dd if=/dev/block/bootdevice/by-name/keymasterbak of=/dev/block/bootdevice/by-name/keymaster

dd if=/dev/block/bootdevice/by-name/devcfgbak of=/dev/block/bootdevice/by-name/devcfg

sync

sync

reboot

It will then reboot and it might boot up into the system.

If that doesn't work try exactly what I told you earlier to make the phone an Aristo 2, except instead of selecting All partitions, select only the boot and system partitions.

If neither of those work, your best move is probably to select All Partitions
[Miscellaneous Android Development] lfc222222:
Yes, I am seeing that same screen during boot up.

The phone was rooted a while ago, and functioning properly. At some point there was some OS update

rolled out by T-Mobile, and w/o thinking I pressed update. Perhaps that was a mistake. It may also have coincided with an attempt

to uninstall Magisk, not entirely sure (regarding rooting, I was really only interested in applying a "dark" theme using substratum, but that proved impossible as substratum simply did not compile)

Is any of that helpful, or just a curiosity on your side?

Oops, just noticed additional info in your prior response (regarding the partitions) will try that next.

Really appreciate your help on this!
[Miscellaneous Android Development] tecknight:
Yes, allowing a system update would do that. I'm surprised it left your TWRP intact

That's why my rooting procedure has you turn off automatic system updates.

---------- Post added at 01:28 PM ---------- Previous post was at 01:17 PM ----------

Since you ran a system update, try this command as well:

dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota

This blanks out the fota partition, used to apply system updates.
[Miscellaneous Android Development] lfc222222:
so you mean try this dd cmd and reboot before trying the other ones in the longer procedure of prior post?
[Miscellaneous Android Development] tecknight:
You could do it with the other dd commands if you haven't done them already.

If you already run the other commands, just do the one command and reboot.

BTW, you can paste the commands into your command prompt session, so youdon't have to type them all
[Miscellaneous Android Development] lfc222222:
I think I'm hosed. I cannot seem to get adb to recognise the device:

C:\adb_lgaristo2\adb-fastboot-tool-2016>adb shell

error: no devices/emulators found

Volume -, brings up the screen with the tiny letters "Welcome to fastboot mode" etc. but adb is not recognizing a device.

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

Tried same using your adb/fastboot pkg, and got:

C:\LG_platform_tools\platform-tools>adb shell

adb server version (35) doesn't match this client (40); killing...

* daemon started successfully

error: no devices/emulators found

C:\LG_platform_tools\platform-tools>adb shell

error: no devices/emulators found

C:\LG_platform_tools\platform-tools>
[Miscellaneous Android Development] tecknight:
So when you are booted into TWRP, adb is not seeing the phone ?

Have you installed the LG adb drivers from here:

http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
[Miscellaneous Android Development] lfc222222:
I have, that's how I was able to root the phone to begin with.

Regarding TWRP, my understanding is that adb can only functions in "bootloader" mode, which you can either into

from TWRP using "bootloader" reboot, or by holding Volume (-) key while connecting to USB. Those are also your instructions at the beginning of this thread.

Did I misunderstand?

Google search on this topic shows that this "adb server version does not match client" is some error to do with possibly search path

or some SW not sure.

Bottom line, not sure how to proceed from here regarding adb. It used to work, now it does not...
[Miscellaneous Android Development] tecknight:
actually, adb does not function in bootloader mode, fastboot functions in bootloader mode.

OK then do it this way:

download this file:

https://xdaforums.com/attachment.php?attachmentid=4624941&stc=1&d=1540252210

unzip the file fixa2p.sh from the .zip.

copy the file to your phone into a known folder like /sdcard.

Then in TWRP go to advanced and select terminal

Then change to the folder where you saved the file

ie: cd /sdcard

then type:

sh fixa2p.sh + ENTER
[Miscellaneous Android Development] lfc222222:
ok, did all that. So effectively "adb shell" via PC wihle phone is in TWRP, is the same as Terminal via TWRP advanced? it's just more continent for typing?

Regardless, I tried all the dd cmds in sequence, still end up in TWRP after reboot.

I guess there's no escape from flashing the metro-PCS image...
[Miscellaneous Android Development] tecknight:
Sorry to say, it does appear that way..

Well, the script was a long shot, but worth trying.

Yes, essentially adb shell is a convenient way to invoke a linux shell on the phone and use a full size keyboard and display.

Flashing the Aristo 2 should fix it, however. I would give it a 85-90% chance of booting after that.

There was the one other option that I suggested short of turning it into an Aristo 2.

That was:

1. Install LGUP DualMode as documented in earlier post.

2. Connect your phone.

3. Run LGUP in developer mode.

4. Select Partition DL.

5. Browse to your Aristo 2 .kdz and select it.

6. Click Start

7. When Partition select dialog appears, select only boot and system.

8. Click OK.

9. After flash is complete, reboot.

If it boots after that, all we need is the system image from an Aristo 2 plus and you are back in business
[Miscellaneous Android Development] lfc222222:
Just saw your updated suggestion. One question, what did you mean by "If it boots after that"? Boots to system or boots at all?

Am I risking booting into recovery (TWRP) using this procedure?
[Miscellaneous Android Development] NonStickAtom785:
I'm gonna make a variebt of the MetroPCS rom thats debloated and has a couple of diffrent stock apps.

If theres any suggestions for this I'm open and willing to add.:laugh:
[Miscellaneous Android Development] lfc222222:
I went ahead and followed the procedure, it went through w/o errors. The phone re-booted back to TWRP

but now has a different screen message. Does that mean the process was successful? (I suspect not...) Would swiping w/o choosing "read-only" preserve root?

If so, I somehow needs to find someone with system image from an Aristo 2 plus.

I can make a request here and on other threads. Can you pls provide the steps for someone with such a device to dump the image correctly?
[Miscellaneous Android Development] tecknight:
If it boots to Android. After flashing the 2 partitions, it will either boot to Android (Hip hip hooray!!) or it will do what it has been doing, boot to TWRP.

No, you are NOT risking your ability to boot to TWRP, cuz we are not flashing recovery, not with selecting the 2 partitions.

If the 2 partitions thing does not work, then the All partitions would overwrite TWRP.

If the boot and system partition doesn't work, that's a good idea.

We can check all partitions then uncheck recovery for the Aristo 2 flash.

I actually think that flashing the system partition has a good chance of fixing your issue.

So give it a whirl !!

---------- Post added at 12:38 PM ---------- Previous post was at 12:23 PM ----------

Check "Never show this message again" then swipe to enable write.

---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------

By "Followed the procedure",you did what ?

Ran LGUP in dev mode and used PARTITION DL to flash the boot and system partitions ?

If you are in TWRP, you automatically have root.

---------- Post added at 01:11 PM ---------- Previous post was at 12:40 PM ----------

How to pull a binary image of any partition on any LG Phone

1. Follow these instructions to install LGUP DualMode on a Windows PC:

When done, run the SetDev.bat as Administrator to set LGUP into developer mode.

Install LGUP Dual Mode(Dev/User) on your Windows PC

2. Connect your phone to the PC and run LGUP using the Desktop shortcut.

3. Select the DUMP option and click Start.

4. When the partition list dialog appears, check the partition(s) that would like an image for and click OK.

5. LGUP will now ask where to place the image files. Select a folder to save the images to then click OK.

6. LGUP will then pull the requested images. They will be named:

<partitionname>_COMxx, for example system_COM23 for the system partition.

Note that depending on the partition, these images can be flashed to a phone using fastboot, TWRP or with the dd command within a root shell.

OK, give me a few minutes, I'm going to figure out how to pull your kernel log from TWRP so we can find out exactly why it is booting to recovery rather than boot.
[Miscellaneous Android Development] lfc222222:
Yes, I ran LGUP dev mode for the boot & system partitions etc. However, it still only boots back to TWRP. So I guess that means flashing those two partitions was not sufficient to solve system boot issue.

Next, if I understand you correctly, you suggest flashing all partitions other than "recovery" which should preserve TWRP, correct?

Is that significantly different than the process to convert the device to a MPCS device? We are using the MPCS .kdz image after all, just excluding recovery...
[Miscellaneous Android Development] tecknight:
Yes, that is what I am suggesting, however, if you don't mind giving me a few minutes, I'm going to figure out how to pull your bootloader log from TWRP so we can find out exactly why it is booting to recovery rather than boot.
[Miscellaneous Android Development] lfc222222:
Of course. Thanks again for your incredible diligence on this :good:
[Miscellaneous Android Development] camm44:
Google it and look for either a YouTube video about it or someone changing something in terminal. I've had this issue Manny time right now I haven't found the code I used but its there online somewhere in the first few pages of phone keeps booting into twerp mode. Sorry for laziness I looked for like 5 minutes it's there tho I think it's not through xda. And I know one of the YouTube videos shows it for a g3 or something. Video like 40 seconds long

---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------

https://xdaforums.com/showpost.php?p=74320886&postcount=6

Or

https://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/

Not sure which as well I currently don't have issue lol

U may need to use common sense and change a folder or file
[Miscellaneous Android Development] tecknight:
OK, here is what I need you to do.

From TWRP select Boot->System it will come right back to TWRP.

When it does go to Advanced->Terminal

Open up terminal.

then type these 2 commands:

cat /proc/last_kmsg >/sdcard/last_kmsg.txt

cat /proc/kmsg >/sdcard/kmsg.txt

Then upload those 2 text files to pastebin or somewhere. I need to see them

---------- Post added at 02:20 PM ---------- Previous post was at 01:58 PM ----------

I have seen it 3 times before and it was always a bad boot image. but this one is not

---------- Post added at 02:30 PM ---------- Previous post was at 02:20 PM ----------

The only significant effect of Not flashing recovery would be that you would still have TWRP and root. It would still be a Metro PCS phone at that point.
[Miscellaneous Android Development] lfc222222:
kmsg.txt https://pastebin.com/3QxekKQP

last_kmsg is now console-ramoops, see note https://pastebin.com/TDVMfphL

Notes:

1. There's no /proc/last_kmsg. I used "ls -rtl /proc/ | grep -i msg" on the dir and did not see anything with "msg" other than kmsg itself

google search shows new location/name of last_kmsg is: /sys/fs/pstore/console-ramoops so gave you that.

2. /proc/kmsg, seems to be a continuously updated system file, so had to ctrl-c it after a while to stop the dump
[Miscellaneous Android Development] tecknight:
OK, I see the problem. There are no partition problems detected it is sensing that a recovery was flagged when the system was booted. ON LG's this information is stored on the misc partition.

So I need you to run this command:

dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

and this command that we ran yesterday as well:

dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota

then

sync

sync

reboot

Hopefully it will now boot to Android.

If that alone doesn't work, mount system in TWRP first, then run the commands except for the reboot command. replace it with poweroff
[Miscellaneous Android Development] lfc222222:
Ok, that did it. Thank you so much!

Of course now I'm curious:

1. What lines in the kmsg log indicated this issue?

2. I'm not sure I follow your explanation of the problem: "There are no partition problems detected it is sensing that a recovery was flagged when the system was booted". What do you mean there are no partition problems detected?

3. It seems we just zeroed out these two partitions, misc & fota, why did that solve the issue?

4. What kind of device do I have now given all the partial flashing we did (system, boot)?

I hope I'm not asking too many silly questions...

---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------

oh oh, wifi switch is grayed out. Seems like something is preventing me from enabling wifi.
[Miscellaneous Android Development] tecknight:
What I mean is, the bootloader did not take a look at a partition and say "I'm not booting that"

The LGE RECOVERY BOOT value is loaded from the misc partition. If you type reboot recovery in the shell, it actually stores that info in the misc partition and it reads it back right after it boots up. If the misc partition got corrupted somehow and never got blanked out, it could think every boot is a recovery boot, which is basically what happened

The line that told me is this one:

<6>[ 0.000000 / 01-01 00:00:00.000][0] [Touch] LGE RECOVERY BOOT: 1

Try this for wifi:

Boot into recovery.

then try clearing the cache and dalvik cache. If that doesn't work try a factory reset

Easiest way to boot to recovery is to enable adb then open up a command prompt and type:

adb reboot recovery

Now we need to find someone with an Aristo 2 plus and have them get you a system image.
[Miscellaneous Android Development] tecknight:
Looking for an Aristo 2 plus owner to pull system image

As you may know, Aristo 2 plus owners don't have the luxury of reflashing their phone to stock with a .kdz file when it has a problem.

Due to this, I am looking for a volunteer to provide me with some partition images from this phone, so we might have an option when someone's Aristo 2 plus has a corrupted partition.

In fact, someone is currently in that situation, so we are looking for a system image urgently.

I think it would also be a good idea to get images of other partitions as well. If we get all the partitions represented in an Aristo 2 .kdz file, we could restore an Aristo 2 plus as effectively as a kdz file does. It would be a longer and more tedious process,but we would at least have a way to restore a messed up phone.

Please PM me if you have an Aristo 2 plus and are willing to help. The process of pulling images is very simple. You might actually be saving your own phone.

Thanks
[Chromebooks] andDevW:
Anyone interested in trying out Chrome OS can build a bleeding-edge Chromebook with a ThinkPad X220.

Should work with any x86-64 ThinkPad running Coreboot.

https://anddevw.com/gdgsf-chromepad-chromium-for-thinkpad/
[General Questions and Answers] Xero_Gravity:
This is extremely frustrating. About a month ago my touchscreen would freeze up and stop working, but the phone screen was still updating so the phone was not frozen. I tried everything; wiping cache partition, factory reset, etc. When the touchscreen stops working the screen will occasionally dim, and if it freezes while your touching it it will look like your finger is still touching the screen. Sometimes the touchscreen might not work from anywhere between 10 minutes all the way to a few days. A fix would be greatly appreciated.
[General Questions and Answers] Ibuprophen:
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.

https://xdaforums.com/showthread.php?t=3110220

Just an FYI... The area of the forum for the Galaxy S6 is also inclusive with the Galaxy S6 Active device too.

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[HTC 10 Questions & Answers] thisUnkn0wn:
Anywhere I can find a stock kernel for Oreo? I'm on the US Unlocked stock 8.0, and cleanslate seems to have broken my phone.
[HTC 10 Questions & Answers] Tarima:
Can't you just extract it from the RUU using the desktop RUU decrypt tool?
[HTC 10 Questions & Answers] firedown_3:
boot.img

for you

https://androidfilehost.com/?fid=962157660013070847
[HTC 10 Questions & Answers] fagyi:
This is the best way for you. Restore the stock boot.img.
[HTC 10 Questions & Answers] Mr Hofs:
You guys think that's enough? How about the modules, did you pack them along with the boot.img. strange behavior may occur without the stock modules.....

Just saying
[HTC 10 Questions & Answers] fagyi:
I just downloaded the kernel, seems to enough restoring the stock boot.img.

For example the modules, patch, ramdisk, just a placeholder for anykernel, nothing unpacked from here to the system. So basically yes.