yashsingh1/xdaforums huggingface dataset:
[Android General] Duhjoker:
Hehe hoho haha. I dont know why this is so funny but today i got the screen replaced on my k8+ MTK and got the temp root back running. I am having a really horid run of bad luck on lmx210 screens but any way after the surgery was completed i must have done a factory reset somehow after the old screen cracked. I got it set up and the temp root set up as well and decided to play some adb roulette.

Well i have no recovery at all. I cant figure that part out but the funny part is i have no download mode either. Lol because i wiped the laff partition. Fortunately i do have a back up of laff. Im gonna dd it back in place shortly but i dont remember removing recovery at all or why i would. It goes straight to the dead android guy with his case open. Im wondering if i should dd that back as well or what.

I want to start making the twrp recovery but i remember you said a modification needed to be made so im holding back on the port plus the last one i tried to make with android image studio.apk wouldnt let me pack it down any more than 156mb. So im hoping maybe you have a good word on how to get the perma root going with a twrp.

Do you have anything i can help with on research? The K8+ is my only option at the moment until we can revive the 7.1.2 fortune 2. But im kinda liking this phone now. It is 7.1.2 nougat as well so no update and no ARB as well.

Ty for your help so far
[Android General] tecknight:
Well it just so happens that i know someone that is very familiar with perma rooting LG microtek devices using mtk-su.

That is because he followed my advice when he asked me what phone to buy that is rootable.

I told him about the microtek exploit and amonet.

So he bought an LG expression plus 2 yesterday.

He has already perma rooted the phone today
[Android General] Duhjoker:
Im all ears. Sorry ive been doing this a while with out help and am not used to having knowledgeble people even though ive really needed it. Usually means me running in circles chasing my own tail.

I looked around at amonet and xpression plus 2 but didnt find any leads just now.

Please sir would you help me perma root my device. Thank you.
[Android General] Duhjoker:
Ok i have no idea how to compile the twrp witn the karnak exploit but i did port one using the aristo 2 twrp and following the guides here on xda.

I would really rather compile one the right way if you know any one that can help. The guides i have found are confusing and for cm and omni and here i am aosp.

Also they want you repo all the source code which i already have downloaded.

I found something on amonet that pointed me to a kindle firestick rooting but dont know if that is right thread. I also saw on diplomatics thread where yall got permanent root but i dont follow or see any procedure.

This morning i replaced my laf.img to its proper place and am now using salt to make another back up of every thing.

Please any help would be appreciated
[Android General] Duhjoker:
Ok so today i just gave in and frp bypassed an aristo 2 board ive been saving and booted it into fastboot and flash unlocked it then installed the recovery and boot after erasing userdata and cache then rebooting im in a twrp loop. I think the problem is due to me freaking out and pulling the battery after the device started installing an update. I had the updates turned off so i dont know why it was dl'ing. Im gonna use the dd commands for resetting the fota update and reboot. Oh this board was running 7.1.2 nougat as well

edit:

Not good. Now the aristo 2 is bootlooping.

Im thinking about flashing your nougat rom but thats how i killed my fortune 2.

edit:

Ok i fixed it. I downloaded the newer boot.img and flashed it not realizing it til i got back on ubuntu and looked at my command history. Reflashed the older boot.img and alk is good

edit:

Ohh i really like this phone. Right off the bat it permanently unlocked the carrier. Im with crk right now so all i had to do was add apn settings and put the sim card in.

ive been playing around with it for a few hours now. trying to clean up the bloatware and kill that stupid lookout.apk but cant seem to find it. Other wise ive installed the usual apps i use in system and trying to hook it up.

i am having a problem with magisk thiugh. when i install any module at all and reboot it stays on the metro pcs screen and wont boot any further. On my fortune 2 when that would happen letting it sit long enough and it would eventually boot into system. i let the aristo 2 sit over an hour and i end up factory resetting it.

The FRP removal was hell but im going to replace it. Dont know why because i always remove the backdoors into the removal any way. First thing i do is kill talk to speech and all that so it cant be accessed.

edit::::::

ok there is something not kosher with the cheese in twrp land. ok im trying to use twrp to flash the modules. I just spent two freaking hours about to lose my mind because it kept saying it refused to mount system and i had no OS. on a whim i said screw it lets see what happens and well im writing this on my aristo 2

edit:::

other than the twrp claiming no OS weirdness for some reason flashing modules in magisk causes boit freeze at metro pcs logo. also some modules i used with fortune 2 freeze any way on aristo 2

edit::::::::

well today has been a long and trying but fruitful day for me and my lmx obsession. lol. ok so i dont really understand the TWRP weirdness i was experiencing but i think i was able to fix it. The weirdness became a problem when i could not manipulate the system partition exteriorally or interiorally of android. twrp gave invalid argument when trying to mount system and it was the problem causer of flashing modules from magisk. i could not use any root to manipulate the system part at all.

i wiped data cache and system and changed thier file systems to and fro with no change in behaviour. The fix was restoring android using twrp but not checking the system.img box.
[Android General] Duhjoker:
ok so i had put the ulma into a boot loop. i tried some dd stuff and it failed. Any way i managed to reflash it using lgup thank you for your work on that. i would raally like to use it to add a recovery but heres the thing i discovered aftet flashing. i used the original nougat rom and still no fastboot.

its had 5 releases since then. What is up with that
[Android General] spirithandler:
I finally was free to flash this and it wiped my recovery and lost root.

UPDATE got to recovery through adb and flashed magisk and all is fine now.

Also thank you for a working mobile hotspot now I can use my allotted 15GB before using PDAnet
[Android General] Duhjoker:
Working on unbricking my lmx210`s. I found a complete set of firehose firmware for msm8917 but i still cant get qfil to download the programmer to to a device.

Also how would you unbrick an lg mtk device. i know it just needs a preloader but the kdz doesnt have that file in witn it.

Would all mt6755 devices use the same preloader?

I was looking at the source code for the ulma and it seems that to enter fastboot mode that you would have to short the jtag. Once in fastnboot mode you do your unlocking and then do fastboot oem exit jtag or something like that

edit::::

i have the preloader. i remember using salt to back up the phone soon after i got it. only problem i have now is how to flash the preloader. Spft is out since you need a lg da pl.bin file. cant use qfil with out a firehose and lgup wont flash with out download mode
[Android General] Duhjoker:
So far my unbricking attempts for both the QC and MTK lmx210 versions are null but im confident that the mtk version will be unbricked first. I found a flash tool that promises to do the job but the disconnecting preloader is a problem.

I think i might be able to solve the bootloader unlock problem for a lot of LG phones. I dont want to give anything away just yet but there is a way to do with out a pc and with out having to do any dangerous shorting of the mother board. Gonna try a few harmless experiments on fortune 2 and hopefully i will have a answer
[Android General] Duhjoker:
ok so in the unbricking process of the ULMA i have run across something to do with karnak and i know my phone is in boot rom mode now but i dont know enough about the process. Am i supposed to short it before i run the step thing or what, i just keep getting an error about not loading the serial module
[Android General] Duhjoker:
I have been working non stop to find a solution for unbricking the CV1 device and today i was struck with a lil luck. The firehose.mbn are real and easy enough to come across but i cant seem to get the qpst system to work. So i started looking into a way to boot from the Micro Sdcard.

The devices memory and partition table is basically an sdcard but faster. So why shouldnt it be able to launch from an external one. There are a few examples out there on how to do so but i couldnt get any thing to work. So last night i started working on combining the three together.

About two hours ago i saw the first signs of life from my ULM. So heres what i did....

First extract your kdz into a folder. then boot up your linux distro and format your sd to exfat. next you want to clear dmesg and check it after inserting your sd into the machine. you should get an mmcblk0p0 signature for it. now mount the card and use DD to flash the primary gpt on to it. Next use DD to flash each partition by part label except boot and recovery.

Now take Boot and cook it down in your kitchen and modify your fstabs so that they resemble the partitions you flashed on the sd. check out init.rc and any other file that uses /dev/block and change it to /dev/block/mmcblk0px and you should be good to go.

after all of that i slid the card in the back of k8+ qc and immediately the screen lit up and started flashing like a boot loop. It did this for a while but now only lights up with battery out and plugged in. ive tried to go into fastboot and twrp with no luck and no dl mode either so far.

Also it will not show up as being connected in either windows or linux with the card installed. Remove it and you get back to 9008 mode.

Now i know oooh big deal the screen lit up but after no signs of life on wiped boards that amazes me. No shorting required either. I need a whole system partition and image if any one would like to donate. The lil versions are just a pain.

Im wondering also if i should forgo the gpt since i cam write the partition order down. The reason being that the modem should probably be at mmcblk0p0 and not gpt. Of course the sd card mount for the unbrick shoulld be tmp but i could make it easier to play with.

on the k8+ mtk i found out its in bootrom mode and its which isnt quite brick but i dont know much about it. I just wish LG would come up off the proper software to fix bricks wether they are qc or mtk.

I also might be able to fix the ARB issue. I have been studying the source code and to provide the kdz with an ARB number you just add a config in the kernels defconfig file. So it shouldnt be hard to compile a rom with the things we need and downgrade.

i could also use the sbl. bin and sblbak.bin from a k8+ phone that has unlocked bootloader and working fastboot.
[Android General] Duhjoker:
ok so im working a lil backwards as usual. after dding the gpt you should go back and make sure each partucular is properly formatted to the right file system. i hope thats the problem at least.

Heres whats going though. At first it flashed for a while now it only shows life when the battery is removed and the usb plugged in. Apply power and its all gone. It did finally register in windows as an lg android device though
[Android General] Duhjoker:
hey tecknight i could really use a hand here and some advice on what to do next. This is for the benifit of all cv1 devices.
[Android General] Duhjoker:
is there any body that would be willing to make a loader.img from a rooted bootloader unlocked k8+ X210ULM. This .img could possibly be used to unbrick a k8+ according to qualcom. once written to an sd card then placed inside the phone and boot would allow download mode and possibly fastboot to recover the phone.

su

su

dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
[Android General] tecknight:
https://xdaforums.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946

Yes, I have tried this method before, but on a cv1 device with stock partitions, I could only get a flashing battery symbol.

I think this is because cv1 devices use UFS Nand. From the post above:

This method does *not* work for UFS devices (so not for the G5 or later). Details:

Quote:

9008 bricks are not fixable on UFS NAND devices by booting from an SD card. The boot path is stored in QFPROM (on the CPU) and it is something like /dev/block/sdb or /dev/block/sde. On eMMC devices, the boot path is /dev/block/mmcblk0. If you have a 9008 brick, the SD card is seen as /dev/block/mmcblk0 so the phone will boot from it on an eMMC device since that IS the boot path. There is no way to make the SD card appear as /dev/block/sdX. And there is no way to change the boot path once you have a 9008 brick without a firehose. If you have a signed firehose, then you can fix your phone without needing an SD card As for cross flashing. I checked the RSA signature for the H930, H932, H933, and US998 and they are all different. If you flash any of the signed firmware (xbl, abl, hyp, modem, etc) from one of those devices, then you have a 9008 brick and no way to fix it yourself.I didn't bother checking the Verizon or Sprint models since they are even more locked down than the H932 is, but it appears from reading this thread that they have the same key as the US998 (I am not going to waste my time checking).-- Brian
[Android General] Duhjoker:
Ok there is some really odd $#!$& going on in cv1 land. My aristo 2 reads as mmcblk0p1 for the first part, aboot is mmcblk0p2, abootbak is mmcblkop3 and so on to grow according to disk info. The gpt.bin when flashed reads the parts the same way. Am i misunderstanding something.

But yes the flashing battery behaviour.......

ok so i flashed the oldest ULM rom i could find and still got the same behaviour. So today i decided to flash the fortune 2 rom on an sd and see what happened. Nothing at all. No change between the k8 board and fortune 2 board.

See when i put the sd in the k8+ i got light but no drive being recognized. when i put it into the fortune 2 it stayed in 9008. So why wouldnt the fortune 2 rom have the same effect but reversed between the two devices.

Also looking at the produced file system on ubuntu which i now have partitioned on my laptop with windows i saw that the k8+ was still registering as a Aristo 2 in the .prop i found in dsp or something.

in mtk land i ran into a lead on a da file for an x240 with same chip set but something isnt right there either. i dont really know wether its a 6750 6755 0r 6737 chipset for one and is there any other way to flash a preloader other than using spflash.
[Android General] Duhjoker:
Having trouble with k8+ Qc version. Just insrtalled twrp and made my own magisk boot.img from extracted kdz. Cannot mount data no such device and when i reboot i get unencryotion unsuccesful
[Android General] Duhjoker:
Hey there

So my new k8+ ulm is holding up so far but i cannot reboot system after booting to twrp and cannot mount data due to no such device 255 error. I have looked around and cannot find a reason or fix that makes since. Any help would be appreciated
[Android General] Duhjoker:
Ok so i looked at the twrps fstab.recovery and it mounts data as fsf2 or what ever and so i changed that to ext4 and now data mounts upon booting into recovery. I do not understand why data would be mounted as fsf2 because its naturally as ext4 before root and twrp.

Now im still having problems though. System now has to be wiped upon entering twrp to mount it and cannot be backed up. Or it can by backing up system then the .img.

I cant seem to get twrp to mount system after flashing either. Every attempt at rebooting to system from twrp ends in flashing kdz fron lgup dual mode.

At one point i let the phone update to oreo and lost my unlocked bootloader. Tg no arb so just downgraded. But im getting tired of doing so.

Dont undersrand why i get into twrp loop.

Ok now im starting to understand i think. Modem which is normally mounted as vfat is mounted as ext4 in fstab. Why? Could this be my bootooop problem
[Android General] Duhjoker:
This is the correct modified and working version of the twrp for the k8+ 2018 LM-X210ULM. The Firmware and system image blocks had to be changed from ext4 to vfat on firmware and emmc to ext4 on system image to work right. Trial and error sucks but it works. with out both changes the device would go into boot loop and i would have to download mode the firmware back.
[Android General] Duhjoker:
I dont know why but the recovery did not post on the last post. So here it is. I havent tested this on anything but a k8+ LM-X210ULM so id be weary trying it on another cv1 device. It does however it works fine with the aforementioned device now.
[Android General] Duhjoker:
K8+(2018) owners. Would you like to have android 8.1 Oreo and be able to not only keep your fastboot mode but also keep it working and still flashing images? plus Root!!

This method will also work for almost any cv1 device and if you have already upgraded to 8.1 you can downgrade to 7.1.2 and re-install to 8.1 as long as your current firmware does not have an ARB value.

https://xdaforums.com/android/software-hacking/root-upgrade-lg-cv1-x210-to-oreo-t4047453
[Android General] lfc222222:
Missing 3.2.3.0 TWRP download

It seems that the 3.2.3.0 TWRP mentioned in the tutorial here is missing on the host servers. Can anyone upload that version here?
[Android General] Madrox_ffxiv:
stuck on step 9

I am stuck on step 9. My phone is a Metro pcs unlocked LG Aristo 2 K8. LM-X210MA

I enter fastboot flashing unlock and prompt tells me waiting for device.

Is there anyone that can walk me through this?
[Android General] Duhjoker:
Juat compiled my first kernel for cv1 devices. Its rated for perfirmance and debuggibg with full otg support. It has smb charging and fastcharge support. It has perfornance profiling with interactive cpu and governor. Android windows and ntfs support as well as jtag uart and ftdi support and if you cant debug it ill refund your no cash back.

Please give it a try and tell me what you think. If there are any features you think should be included or just want to improve upon my work just shoot me a line and ill get to it as soon as i can and lets make our cv1 devices the best they can be.

Not responsible for bricking your device.

This boot.img was compiled for the K8+ LM-X210ULM. But should work for most cv1`s if it doesnt ill compile the same kernel for your specific aristo 2 or fortune 2 device. Just let me know

https://xdaforums.com/android/help/help-compile-cv1-kernel-userdebug-t4069035

oh i forgot to tell you guys. I also removed any and all restrctions that would stop you from trying to compile a kernel or other software on your device. That parts untested but im gonna try in the next couple days to build one in ubuntu termux,
[Android General] mribraqdbra:
Get the USB Drivers:
[Android General] tecknight:
Is your phone running Nougat (Android 7.*) ?

fastboot on the Oreo image cannot flash unlock or write any partition, so you will have to downgrade to Nougat, as stated in step 1

Step 1:

1. If you are currently running Oreo based firmware on your device and you do not already have TWRP installed, you will have to first downgrade your device to Nougat based firmware, before fastboot will let you flash TWRP.

If your phone is an Aristo 2 (Metro by T-Mobile), I recommend firmware version 10K, available here:

https://www.androidfilehost.com/?fid...63190603847051​
[Android General] Duhjoker:
Hey you guys! Ok so i finally got my compiler to put out working kernels that boot. Sorry the last one might not have booted. it was on and off for a couple days but i think i got it working.

Along with my jokerfish cv1 msm8917 kernel. Its full of performance and debugging features and lightning quick. Only problem is i cant get force_fast_charge to show up in /sys/kernel/ even though its compiling and i can touch the object files.

Any way all you have to do is flash using twrp and have a great day.

edit:::

Wanted to make sure before choking on some smiling fish huhuh but the defconfig for the K8+ and the Aristo 2 are the very one and the same. So have fun kiddies. Sorry fortune 2 fans looks like i will have to complie one for those who ask since it has updated and gone boooooo ARB03.

And if any one has any clue as to how to fix fastcharge not showing up in /sys/kernel/... puhlease let a clown know.
[Android General] bowser001:
My phone is the T-Mobile Aristo 2 plus and the ROM I’m using is the pre-rooted nougat 7.1. Aristo 2 plus (Nougat firmware 10J, T-Mobile), download this;

https://www.androidfilehost.com/?fid...63190603855657
[Android General] tecknight:
OK [MENTION=916298]bowser001[/MENTION] I have modified my latest rooted nougat Aristo 2 plus image.

I have decertified the system update, so the image will remain Nougat.

Try it out and let me know how it works.

Aristo 2 plus Nougat rooted flashable image:

https://www.androidfilehost.com/?fid=4349826312261764112​
[Android General] Duhjoker:
Here are my latest compiled kernels for nougat pre-packed rooted tested and zipped on thier respective devices. I was having a glitch that was causing a panic due to the toolchains exidx arm unwind warnings causing the unwind not to work and rebooting evety few hours. All the goodies and extras are there invluding ntfs devtmpfs msdos usb otg msm-usb-otg a crap load of drivers governor hot plug its all there. So far 3 days no panic and going strong.

fast_charge is compiled but im still working on how to get sysfs to show it in sys/kernel/. New modules are included as well.

Edit:::::

I forgot to mention that i was able to temove the block that caused failures when compiling kernels or othet firmwares on your phone.

As a side note. Buildibg a kernel on your device can be easily achieved by un-tarring the source and running the build in the /sdcard folder.
[Android General] ngocphuoc93:
help ican flasshing G710NOP20k_00_OPEN_KR_OP_1220.kdz in LG G7 koare G7 U+

help me flashing ok but stuck logo help me
[Android General] Duhjoker:
ok try to explain the problem the best you can so we can undersrand. Can you state the device the OS version which rom, recovery or boot image you may have flashrd
[Android General] ngocphuoc93:
help me

I don't have to downgrade to the same version
[Android General] Duhjoker:
if you are downgrading you should down grade with rom specific to your device. But the os version could be a 10k or 20k as long as its for your device. If you got boot loop going on your good. Just flash a whole rom using lgup and wait for it to reboot on its own
[Android General] ngocphuoc93:
help me
[Android General] Duhjoker:
so i wanted to try out the oreo prerooted rom for some testing purposes since im building kernels and have started on gsi`s. First i removed aboot so i could keep my working fadtboot boitloader. but when ever i boot into twrp i have to format and wipe it which means having to set up the device consrantly.

any idea on whats causing that.

also upon switching back to the nouat roe vm i somehow now have the splash for a k8+
[Android General] tecknight:
The TWRP issue you are describing sounds like your partition(s) are being force encrypted.

This is typically caused by the fstab in the system partition.

It can be fixed by modifying the system image and possibly also the boot image.

If you like, I can post instructions here.

Exactly what phone do you have and what firmware are you running ?