yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] diplomatic:
I have to say that plan is less than solid. It's actually a lot more likely to brick your phone than have the intended outcome. You're making a lot of assumptions here that have a good chance of not turning out your way. I think what you're mainly not accounting for is the bootloader verification of boot & recovery partitions using cryptographic signatures. Most locked bootloaders will not boot modified/unverified images. I mean, it's possible, but you would have to test it progressively, with a lot more steps involved. I would compare the process to playing minesweeper. But what if something goes wrong and you can't boot Android to fix it? Is there a way to recover your phone that doesn't depend on the OS? If not, this would be very risky to have even if you succeed. Unless you have a way to restore the FW through an outside channel, like SP Flash Tool or some USB-based exploit, or don't care about losing it, I suggest not bothering with this....

If you're just looking to debloat, why not just use the temp root or even bootless root to disable some packages and then be done with it?
[Miscellaneous Android Development] ShadeTreeBiker:
Thank you much for the time you have taken with this [MENTION=8132642]diplomatic[/MENTION].

I thought I was missing something....so,

dm-verity isnt the only checks made. I guess I need to investigate into this...

One question is IF I achieve a temp root shell and take a dd of the entire emmc, all the partitions, etc. will a VM in Android Studio work for a testing environment? I'm thinking no, but if it would work I have a test unit for research.

As far as recovering from bad stuff...unless I can access the FTM/EDM (so far no-go there) I'm thinking I'm outta luck. Fastboot does boot, (it displays it on phone,) but wont communicate with the computer...I think ZTE cut the com port or severely crippled Fastboot...no device info, no "fastboot devices."

I guess for now its diabled junk and lose the space...QLink Wireless turned a good Android system into an 8.5 GB monster...

Thanks a LOT for taking the time to help a newbie out...
[Miscellaneous Android Development] azzadh:
Sorry, my bad, I didn't know that app creator didn't got your permission. I just took the easy way to test if the method actually works. And my mistake was that I used his suboot script because while reading your bootless root post I didn't realize that there was an attachment in the post (should've read the entire thing). Using your suboot init.d excecuted with the following result:

suboot.sh

UID: 0 cap: 3fffffffff selinux: permissive

I guess you can add the junk Lava iris 88s to the list of working devices.

Again sorry for being a bother and thank you for the help.
[Miscellaneous Android Development] mrmazak:
There are other ways to backup, but if you follow the link on first page, to "backup-helper" you can have your full backup, without having magisk installed

Exactly. if not unlocking bootloader, DO NOT go changing recovery and boot partitions. Just disable apps you find as bloat

adb shell pm list -f packages > packages-list.txt

This line will give you a list of packages (apps) installed on your phone. Do your homework over this list, to determine what is and what is NOT needed.

then remove what is not needed with commands like this (replacing the actual package name for the ones you choose to remove)

adb shell pm uninstall --user 0 com.opera.browser

You can take it further if you have multiple apps with similar package names, like this

adb shell pm uninstall --user 0 *amazon.*

And these removed apps, can be restored by simple factory reset
[Miscellaneous Android Development] azzadh:
I was thinking the same thing, why is he going the extra mile, why not just attain temp root and freeze the bloatware using titanium backup? I was just waiting for the expert to speak.
[Miscellaneous Android Development] ShadeTreeBiker:
[MENTION=5312578]mrmazak[/MENTION], thank you for weighing in...I do plan on checking out that backup helper. Wasn't sure though about transferring the BU to a VM...would it work the same as a dd img?

And I fear that to uninstall the system installed bloatware would result in soft-brick or bootloop til I use recovery to reinstall the original system. The recovery doesn't bother me per/se...the possibility of a soft brick when I cant access the fastboot, or EDM/FTM. IF this is not the case, the the temp root shell will be a big WIN for me...
[Miscellaneous Android Development] mrmazak:
OOH, that is what is so nice about the above commands. They do not remove or uninstall the apps, system wide. Only for "user 0", which is the main user. So it is uninstalled and not at same time. --as user 0 you will never know the app is there. it will be gone, but if you add a second user (come on really who does that anyway) it will be installed for them though.
[Miscellaneous Android Development] ShadeTreeBiker:
ThankYouThankYouThankYou!!!!

This is exactly what the doctor ordered....much thanks to you and [MENTION=8132642]diplomatic[/MENTION]

Now, on to the backups and uninstalling that bloat...and IF I understand correctly, I'll gain the space in the user partition, but the /system will remain the same...OK, I can accept that til a BL unlock is found....
[Miscellaneous Android Development] diplomatic:
Are you talking about running that phone's kernel and platform-specific drivers & code in a VM? If so, then no, that's not even remotely possible.

Yep, the temp root is pretty much perfect for your needs. Patching the FW with root would have been overkill, not to mention dangerous. So does mtk-su work on your phone?
[Miscellaneous Android Development] ShadeTreeBiker:
Haven't had a chance to try yet...life happened and I got real busy. I'm gonna try it tonight
[Miscellaneous Android Development] ShadeTreeBiker:
GOT IT!!!

Okay, using the directions in the first post I got a root shell....YAY!!!

Trying the mtk-su and Magisk (from P.14) not working, but havent explored this much this morning...

Thanks LOADS [MENTION=8132642]diplomatic[/MENTION]...and [MENTION=5312578]mrmazak[/MENTION], havent managed to get the backup helper working yet, but gonna explore method above that hasnt worked yet, and work on that backup this afternoon...gotta go lay some linoleum first... :p

But in way of explanation with the BU, Termux won't install...exploring that later today too.

Oh yeah, it's in my first post, but:

ZTE Z3351S running MT6739 on Android 9

I'll post my results from the others later with screenshots of successes and failures...
[Miscellaneous Android Development] matrix145:
Hi Is there an explanatory video to explain how Root works

Hi Is there an explanatory video to explain how Root works plz help me my telephone is nokia 3.1plus
[Miscellaneous Android Development] ineedroot69:
I like to confirm this thread works BLU Vivo XI (MT6762)

Rooted it via Magisk after dumping boot.img with privilege adb shell

i have a off topic question thou can you make a custom TWRP for me i have all partition like boot.img, recovery.img, system.img if you needed it ...
[Miscellaneous Android Development] mariojohn:
Does anyone know if this would work for MT8765A chipset? If not, has anything heard of a root method for it? I searched to no avail.

Thanks!
[Miscellaneous Android Development] diplomatic:
[MENTION=1999573]mariojohn[/MENTION], yes, it will work on that chipset...unless it won't. :) But for real, if you have the device in question on hand, there is no point in asking if mtk-su will work on it. This is my standard response to any "Will it work on..." question. You're really the best person to answer it and it only takes a few minutes to try it out. So do report your results along with the requested materials if it fails.
[Miscellaneous Android Development] mariojohn:
Thanks. I'll give it a whirl and see.
[Miscellaneous Android Development] daLareid:
Tried to root an Amazon Fire 7 (2019) using the guide here but the scripts on init.d but it's not working, I followed the instructions except for using the R16 file because it's no longer available, tried R17 and R19 from the arm folder and it's not working, can't get root.
[Miscellaneous Android Development] diplomatic:
[MENTION=4978910]daLareid[/MENTION], have you checked if your firmware/Fire OS version is lower than or equal to the last agreeable version as listed in post 3? The last mtk-su release is always the current one for every device.
[Miscellaneous Android Development] mariojohn:
Confirmation! Works with mt8765a chipset. Alcatel 3t 9027w.

However, without custom recovery or rooted boot image, can't do much after that.
[Miscellaneous Android Development] ineedroot69:
just dump boot.img or recovery.img and use them to root with magisk ?

my phone still has no custom recovery /TWRP but im rooted with magisk
[Miscellaneous Android Development] diplomatic:
Awesome! Have you seen the bootless full-root method in this thread?

This is only safe to try if the bootloader is unlocked.
[Miscellaneous Android Development] Dat1Developer:
Does this work on an lg stylo 4 running android 9?
[Miscellaneous Android Development] diplomatic:
OK, please don't quote the entire OP in your posts. I have just updated the FAQ section to address your question:
[Miscellaneous Android Development] Dat1Developer:
[QUOTE/]I was just asking if it would work on an LG Stylo 4 on Android 9[QUOTE/]

Crap I did it again
[Miscellaneous Android Development] diplomatic:
[MENTION=10293281]Dat1Developer[/MENTION], it looks like that phone is Qualcomm anyway. So it won't work at all, unless there is a Mediatek variant.

EDIT: Wow, so there actually is a Mediatek version of this phone. If you have that one, feel free to try this root method.
[Miscellaneous Android Development] ineedroot69:
at this point im quite satisfied being root with Magisk

also the main reason i decided to root this device is that i can't screen record that only will capture internal sound(no dogs barking,bird chirping ..etc) now which i can thanks to you

i would probably try bootless full-root method if i experience issue with magisk
[Miscellaneous Android Development] Dat1Developer:
wait what!? Can you give me it?
[Miscellaneous Android Development] diplomatic:
Great. Although I was responding to someone else in that msg...

Everything's already available to download. You have to check if your Stylo 4 is the Qualcomm or Mediatek (MT6750) variant. If it's MTK, go ahead and follow the bootless root directions, and report your results.
[Miscellaneous Android Development] Dat1Developer:
Welp, mine is qualcomm, all hope is lost :'(
[Miscellaneous Android Development] diplomatic:
Oof... well, hope you find another way...
[Miscellaneous Android Development] Romeocruzz:
hello. i have tried everything and all the mtk-su suboots downloaded each and every file but i get errors.

i will attach the files please check.

device - oppo f9 pro (cph1823)

os - Android 9

soc -p60

sec patch - September

well can't upload screenshot here is the error

failed critical init step 4
[Miscellaneous Android Development] mrmazak:
AFAIK there is a security patch (think it is september) that has blocked MTK_SU, sorry.
[Miscellaneous Android Development] diplomatic:
Already addressed by this FAQ:

What are the current and previous firmware versions of your phone? If you can safely downgrade, there may be a chance for mtk-su.
[Miscellaneous Android Development] Romeocruzz:
hey thank you for responding.

currently the security patch is September.

i tried to downgrade but oppo has put something like anti roll back.

i spent 10 hours downloading different different methods. its almost impossible to go back.

thanks for all this hardwork. genius for real

am willing to test any future development or betas . :)

---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------

yeah its September patch. wish there was a way to go back haha.
[Miscellaneous Android Development] diplomatic:
OK, but what is the actual firmware version you have now, so I can put the last working one in the OP? I saw that A.20 is the latest on the web...
[Miscellaneous Android Development] Romeocruzz:
the version is CPH1823EX_11_C.14
[Miscellaneous Android Development] ineedroot69:
i remember the Android 2.0 era were android ask permission if it can download OTA update now you can't even disable it ?

i use host file to block system update
[Miscellaneous Android Development] diplomatic:
I see, so this is the new Android 9 update for this Android 8 phone. So just to confirm, you did get the "This platform is not supported" line from mtk-su R19, right? Just want to make sure it's really blocked and not some simple structural problem, which could be fixed.
[Miscellaneous Android Development] Romeocruzz:
i tried r17-r18-r19 and specials for oppo. nothing worked for me.
[Miscellaneous Android Development] diplomatic:
[MENTION=6878421]Romeocruzz[/MENTION], I know it didn't work. But I'm asking about the specific output from R19. Did it say "This platform is not supported" or something else?
[Miscellaneous Android Development] Romeocruzz:
it says failed critical init 4

this platform is not supported
[Miscellaneous Android Development] diplomatic:
OK thanks, [MENTION=6878421]Romeocruzz[/MENTION]. Yeah, that's the unfixable scenario, sorry.
[Miscellaneous Android Development] Romeocruzz:
thanks for the hard work :)
[Miscellaneous Android Development] Duhjoker:
works on an Lg k8 + lmx210ulma. But i still need help unlocking the bootloader so i can flash the recovery for it. ive been asking around and even Lg is a lil curious as to why i cant get into fastboot mode.

i have tried the key combinations, adb reboot bootloader and going to recovery. using magisk on any reboot just reboots to system.

any help would be appdeciated
[Miscellaneous Android Development] DB126:
Wrong thread for bootloader unkock questions; ask in your device forum.
[Miscellaneous Android Development] Duhjoker:
Funny i was told to come here and ask. I cant seem to find help any where on xda. Either im ignored or told to go somewhere else that has nothing to do with what im asking for.
[Miscellaneous Android Development] Supermatt01:
I tried the newest version on my OPPO F11. It gave me reboot issues again. Will you send me an OPPO friendly version? I haven't updated to the September patches.
[Miscellaneous Android Development] Vortell:
Why would someone direct you to generalized thread to get device specific information? You would be able to back up your device with temp root. Including kernel to root it. However without bootloader unlock you can brick it. With the LGs I have messed with you need to have oem unlock enabled in developer settings then you need to use fastboot commands to unlock bootloader. I think the two commands I know are fastboot oem unlock and fastboot flashing unlock. It could be different commend or not be enabled. If everything goes as planned you fallow directions like almost any unlocked bootloader using magisk. Aka patch in magisk and flash back to phone. For more info though to to device page.
[Miscellaneous Android Development] Duhjoker:
Well guess what? You ready? Ok so my phone will not boot into fastboot mode. This is not my first picnic. Ive rooted a few phones, most were lg the others alcatel. This particular phone is being a pain in my posterior. Else i wouldnt be asking. Its seems the fast boot mode has been hidden. I can get it into down load mode and recovery but thats it. Reboot bootloader, key combos and using the feature to reboot from recovery all produce the effect of rebooting to system. Its a puzzling matter to me and very annoying.
[Miscellaneous Android Development] alecxs:
from what i have read, enable oem unlocking, open root shell, make a backup of laf.img, then wipe laf partition. this will brick your LG and activate emergency fallback fastboot mode. you should be able to reach it with Vol key then. there you can unlock and flash/restore laf.img
[Miscellaneous Android Development] Duhjoker:
Cool thing is i already have all the partitions backed up using the salt program on ubuntu. I was hoping i could do that but the brick word scares the crap out of me. I already bricked two pixi threes that i cant figure out how to recover due to missing auth files when i go to flash.

Thank you though. Now would any one happen to know the command to find the find the laf partition then wipe it and then reinstall it?

edit: found commands will try this and get back to you
[Miscellaneous Android Development] Dat1Developer:
*sigh* If only it were compatible with my Qualcomm lg stylo 4, now I have to suffer in jealousy
[Miscellaneous Android Development] Duhjoker:
Do you have a computer? I can tell you how. You will need a 16gb sdcard, usb sdcard reader, copy of ubuntu 18.04.iso android phone and salt program. Use etchdroid to burn the iso to the sdcard in the reader. Then boot your pc into bios settings change boot order to usb then boit the usb card reader and plug phone in, no drivers needed remove salt from phones internal storage run and save partition dumps.
[Miscellaneous Android Development] diplomatic:
Why? There's not much reason to update it. The one from August already has the -Z option. The other changes from R19 are not very relevant to your phone.

If it's a carrier phone (and even if it's not), it's not designed to be unlocked. No big surprise there. Locked down phones are typical nowadays. Have you seen the bootless root method in this thread? It may be sufficient for your needs.
[Miscellaneous Android Development] Duhjoker:
Bootless root method? Is that the same as adding the init.d folder to your sdcard folder and dowloading the init.d scripts support.apk. Yes i have done that but it doesnt give me much control. I need full root for a project im working on.

Any way so i removed the laf.img or partition using the dd command and tried to boot into download by holding the volume up button and plugging it into my ubuntu machine but it just throws and repeats the k8+ logo over and over again til i let go then it reboots to system. Btw i have the bootloader partition backed up as well as with everything as mentioned. Any ideas?
[Miscellaneous Android Development] diplomatic:
[MENTION=10029946]Duhjoker[/MENTION], yes, that's the one. I don't have any ideas about unlocking, and that's pretty off-topic for this thread anyway.
[Miscellaneous Android Development] CXZa:
I gave you the link to Diplomatic's post as it was the root you wanted. Later here you

revealed a bit more about your plans and needs.

Now thank Diplomatic (yes, there is buttons for it) as without his temp root

you would not be able to recover that laf partition at all...

It seems that your K8+ is like K10 2017. No bootloader/fastboot mode whatsoever...

If you have balls of steel, you could try to wipe recovery and boot and see what it does.

Naturally after you have put laf back to its partition... (or the boot.img instead ?..)

Or better yet, buy/use another phone...
[Miscellaneous Android Development] Duhjoker:
I put too much money out on this phone i wish i could. Plus my challenge level has been made and i now have to figure this out. I have the source code and the compiler set up as iit is. I could compile an lk.bin file as i read that is actuallly fastboot mode and replace the current one. Or you were talking about my testicular fortitude which can be pretty steely, could lk.bin be placed where laf was. i think its just hidden in a way. Btw lg is puzzled as well.
[Miscellaneous Android Development] diplomatic:
As [MENTION=5488402]DB126[/MENTION] likes to say, good luck with that. Before compiling any such modules, you should become familiar with the concepts of secure boot. I suggest, if you're going that route, focus on finding a different official version of the bootloader. It might be an older version that has fastboot enabled. Or if you have a carrier FW, try using a module from the retail version. All these approaches carry significant risk of course.
[Miscellaneous Android Development] Duhjoker:
Using a bootloader or lk.bin from a crarrier that allowed bootloader unlocking is exactly how the alcatel tetra is bootloader unlocked. The cricket version is locked but the at&t version is unlock enabled so we just dd'd the lk.bin into place and voila we were able to unlock it. Well im trying to get tecknights attention hoping he might have an answer or even a clue. I have asked for an lk,bin but no bytes yet.

You know i had this crazy idea earlier i would like some input on if you may. I made the partition dump and i have every thing backed up. like i said the bootloader and fastboot are there just hidden. Would it be possible to put the current lk.img in place of the laf.img. haha laf is gone lol any way but do that unlock the BL and dd back laf
[Miscellaneous Android Development] ineedroot69:
hahaha love the gif :laugh::laugh:

---------- Post added at 04:36 AM ---------- Previous post was at 04:34 AM ----------

what is laf.img ? and why did you remove it :confused::confused:
[Miscellaneous Android Development] Duhjoker:
Ok so there are things called partitions in which cellular data segments are held....... jk. Lol.

Ok the laf.img or laf partition is lg`s downlod mode. So by removing it, it should have forced the phone into a panic when put into download mode by holding volume up and plugging the usb into a pc. That should have forced fadtboot to appear in its place. But it didnt work and the phone just loops the k8+ logo until let go of then reboots to system.

But i have another plan. Im going to dd the lk.img into laf`s place then try again and see what happens.

Unless someone has another idea. Lk.img is the bootloader so i should be abke to place it unlock it and then replace laf.

But my question is... is there a way to boot into each particular partition?
[Miscellaneous Android Development] kobul:
Bro.... I got this :

Failed critical init step 4: Bad address

setns failed:: No such file or directory

New UID/GID: 10232/10232

starting /data/data/com.termux/files/usr/bin/bash

Oppo F7 ColorOS 6.0.1 Android 9

CPH1819EX_11_C.10
[Miscellaneous Android Development] alecxs:
[MENTION=10029946]Duhjoker[/MENTION] You are very welcome to open a new thread! We would like to follow you there, this could help other LG users
[Miscellaneous Android Development] diplomatic:
Nothing good can possibly come out of that. lk and laf are 2 different things. But in any case, LG hacking is not relevant to this thread and I won't be replying here anymore about this topic.

The Android 9 update probably closed off mtk-su. If R19 returns "This platform is not supported", that will confirm it. See the FAQ also.
[Miscellaneous Android Development] kobul:
You right bro... With R19, i got "This platform is not supported".
[Miscellaneous Android Development] Silmedil:
I have tried it on my LG X power 2 (note that it is listed as working near the beginning of the thread).

Running r19, output with the verbose option is the following:

armv7l machine

param1: 0x1000, param2: 0x8040, type: 12

Building symbol table

kallsyms_addresses pa 0x40f336a0

kallsyms_num_syms 49300, addr_count 49300

kallsyms_names pa 0x40f63900, size 631725

kallsyms_markers pa 0x40ffdcb0

kallsyms_token_table pa 0x40ffdfc0

kallsyms_token_index pa 0x40ffe340

Patching credentials

Parsing current_is_single_threaded

Stack protection detected

init_task not found

Parsing avc_denied

c04596d4: MOVW R0, #0x8604

c04596d8: MOVT R0, #0xc190

selinux_enforcing VA: 0xc1908604

Setting selinux_enforcing

Switched selinux to permissive

setns failed: No such file or directory

starting /data/data/com.termux/files/usr/bin/bash

UID: 10266 cap: 0000000000 selinux: permissive

It then drops into a new shell as the exact same user, running multiple times (tried at least 30) consistently produces the same result.

Android version is 8.1.0.

Any feedback would be appreciated, I'll be more then happy to provide additional needed info.
[Miscellaneous Android Development] diplomatic:
[MENTION=10376557]Silmedil[/MENTION], you got a link to your current firmware?