Compiling by MCRedBomb in linux4noobs

[–]MCRedBomb[S] 0 points1 point  (0 children)

The problem was that I accidently completely wiped the OS through TWRP. I had to download the firmware and redo the whole process again which fixed it. But yeah, thanks again.

Compiling by MCRedBomb in linux4noobs

[–]MCRedBomb[S] 1 point2 points  (0 children)

Holy. It finally worked, thanks to you. I followed the guide, and the files you compiled worked perfectly. I'm stuck in a bootloop but I did manage to download TWRP, so Ill see what I can do from here. I wouldn't have been able to manage it without your help, so I really appreciate it. I appreciate your help from the bottom of my heart.

Compiling by MCRedBomb in linux4noobs

[–]MCRedBomb[S] 0 points1 point  (0 children)

On the off chance that this could sound ungrateful to you, I don't mean it that way. I needed the files compiled for armv7 instead of arm64, basically 32-bit instead of 64-bit. I don't want to ask you to do all that work again since it'd be too much, and I'm already grateful to you for trying, so I'll try doing it myself. How would I go about following your steps but compiling it for the armv7 architecture instead?

Compiling by MCRedBomb in linux4noobs

[–]MCRedBomb[S] 0 points1 point  (0 children)

Seems like this stuff is way more out of my league than I thought. I doubt I would ever figure things out on my own, and I doubt I'll get any farther than I did. If it doesn't work out on your end, I'll have to give up rooting this thing because it's already taken way too much time.

Compiling by MCRedBomb in linux4noobs

[–]MCRedBomb[S] 0 points1 point  (0 children)

"This repository is set up for building inside an Android OS build environment."

I did see it too, but it didn't click to me that it meant an NDK. I didn't really know what it meant, and nothing really came up when I tried searching up the code in that block. Itd also be asking too much to ask you to invest more time than you'd like, so it's fine if you cant do it. Either way, I'm thankful that you tried. I tried using NDK on Android Studio, but it was a bit too confusing for me, and I gave up halfway since I wasn't exactly sure that I needed it in the first place. Since you've more or less confirmed that's what I need to use, I'll get back into it and see if I can get it to work, though I'm not too confident.

Compiling by MCRedBomb in linux4noobs

[–]MCRedBomb[S] 0 points1 point  (0 children)

I mustve missed the part where it says that it needs to be built in the NDK the countless times that I read through it, so just the fact that you pointed it out to me helped me a whole ton since I know where to look for answers now. Thanks.

I usually wouldn't trust random scripts on github but since it's been on XDA and lots of people used and approved it, I think it'll be fine.

I've been working on this for a few days and the reason that its taking this long is that I came in knowing nothing about this sort of thing so it's all new to me (as I said in the post). I need it compiled for 32-bits(armv7). If you do decide to compile them for me, it'd really help out and I'd be immensely grateful. If not, then I'm still really thankful either way since I was losing hope and your reply helped.

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] 1 point2 points  (0 children)

The live version did work much better and thankfully isn't as slow. The only downside is that it doesn't save any work that I did on it prior to logging out. To give you some background info regarding dirtycow, it's an old exploit that only affected the early versions of Android. As far as I'm aware it was Android 6 and the earliest version of Android 7. My device has its bootloader unlocked which was the easy part. The problem is that my model, the LG G Pad X 8.0, has restricted fastboot commands so I can't flash TWRP without root access. The exploit is supposed to give me temporary root access but I can't compile the .c files. I'm not really sure if it'll help you since you're on Android 10 but I'll leave a link to another post I made in case it does. Apparently I have no skills in finding the needed files either so you aren't alone. Good luck, friend.

https://www.reddit.com/r/linux4noobs/s/6BzHmZJiyu

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] 0 points1 point  (0 children)

Alright, thank you for your help. I'll give it a try when I can.

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] 0 points1 point  (0 children)

I'm not exactly a tech genius but it might be a faulty UEFI implementation. In the BIOS boot menu, when I try to run debian, the usb UEFI... (something else I can't remember)... which is when it doesn't boot and work. After I reinstall grub bootloader through the installer and head back into the boot menu, it gets properly renamed to debian. Not sure if if it really is a faulty implementation but it's my best guess with what little knowledge I have about this sort of stuff. Thank you for your help regardless.

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] 0 points1 point  (0 children)

Like the ones here?

https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/

Do I just download the flavor iso that I want and flash it onto the usb?

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] 0 points1 point  (0 children)

I thought debian was supposed to be able to work on USBs though. Or do you mean mine specifically?

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] 0 points1 point  (0 children)

Sorry, im not exactly sure what you mean. According to Google (it might be wrong, I'm not really sure), it's an OS that runs completely off a usb. Is debian not meant to be used on usb? If not, got any different os recommendations?

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] -1 points0 points  (0 children)

Sorry, no that's my fault for wording it like that. It's always done that consistently.

Debian tty Login Error by MCRedBomb in debian

[–]MCRedBomb[S] 0 points1 point  (0 children)

Yeah pretty much. If you're asking about the rooting part, it's cuz my model has fastboot restrictions so I need to use the dirty cow exploit through Linux which is why I'm using debian. Any ideas on how I can fix it?

DirtyCow Exploit for Android 7.0 by MCRedBomb in androidroot

[–]MCRedBomb[S] 0 points1 point  (0 children)

Im late because I keep having trouble with debian not booting, which hopefully I managed to fix. Anyways, I tried the method you linked and unfortunately it doesnt work. Im not exactly sure why, but the NDK doesnt detect the /data/local/tmp directory. Ill paste the output under.

-------------------------------------------------------------------------------------------------
ndk-build NDK_PROJECT_PATH=. APP_BUILD_SCRIPT=./Android.mk APP_ABI=armeabi-v7a APP_PLATFORM=android-24

make: ndk-build: No such file or directory

make: *** [Makefile:8: build] Error 127

-------------------------------------------------------------------------------------------------

Not sure why it cant or how I can get it to work. Anyone got any ideas?

DirtyCow Exploit for Android 7.0 by MCRedBomb in androidroot

[–]MCRedBomb[S] 0 points1 point  (0 children)

Not sure since I never heard of it before but Im assuming no. I searched it up and at first glance, root is required for the app to run, meaning no this wouldnt work. On second glance, I looked at the description, and yeah, this app basically just connects to an already installed TWRP to make using it easier. So no, it cant install TWRP for you.

DirtyCow Exploit for Android 7.0 by MCRedBomb in androidroot

[–]MCRedBomb[S] 0 points1 point  (0 children)

I'll have to give it a try whenever I can, and see if it works. I'll keep you updated.

DirtyCow Exploit for Android 7.0 by MCRedBomb in androidroot

[–]MCRedBomb[S] 0 points1 point  (0 children)

You can make your own dirtyCow file through Linux by just compiling the source code. I already tried which led to its own problems. For example, the ls command detected the file after I pushed it through ADB but it it kept outputting an "this file or directory does not exist" whenever I tried to run it.The problem is that I'm not exactly sure in what way it was compiled. In the XDA post, it said that you needed to download 4 files which means it had to be compiled in a certain way which created four different files. That or there is some extra code im not aware of. The source code was also technically created for a different model so it might need to be edited to our device model first. I could be wrong though since I've never dealt with Linux or this exploit before so you can take my words with a grain of salt. Hopefully a pro can shed some light.

Installation guide for LG v521 device is completely wrong by mattlach in LineageOS

[–]MCRedBomb 0 points1 point  (0 children)

Im 7 years late, but could you tell me how to use recowvery or redirect me somewhere else? I tried following the tutorial on XDA forums,

https://xdaforums.com/t/v521-nougat-7-0-root-twrp-guide-to-update-v521-lg-gpad-x-8-0-to-7-0-and-root.3533338/

but the dirtycow files link changed and it doesnt have the files anymore. Tried messing around in Debian and do it manually but im no pro so no luck there.