I am preparing to use this phone as a dedicated display on a custom embedded system. Changing the boot logo is a must. I have been playing around with it and reading threads for hours and no luck.
Rooted with the latest Magisk, TWRP, unlocked bootloader, the whole 9 yards. A10 Stock ROM. I don't care I break SafetyNet, just need this to work.
I can't put the new bootloader on the system partition because it's mounted as read only. Since it's A10, I haven't found a working way to modify it with TWRP or within the ROM. Has anyone been successful yet?
There are existing Magisk modules for boot animations, but I need a custom one, and I don't know how to make it into a flashable ZIP. How do they do this?
I also tried a Magisk module that is supposed to let you put the boot animation on /sdcard, and it gets overridden on boot by the module, but that did nothing. But it was on a OnePlus forum, so maybe incompatible.
Thanks!
i think you can mount system within twrp then use the twrp file manager to move it. if not, get a terminal emulator, su, mount system, mv file.xxx /system or whatever folder youre looking for
Related
As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.
how did you install the TWRP?
im a noob in this
okay! so after attempting to install TWRP my phone bricked haha
i had to flash again the rom. geez!
i better not attempt again.
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.
sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted. you can still flash zips via sideload as it is though, so that was never a *huge issue*. thing is, modifying system partition on official builds (25, 28) will cause security lockup. kernel needs to be patched, and prolly bootloader for this to be bypassed, and it seems its not easy. consequently root will fail too. on 27 though, you can easily boot twrp and flash a custom zip (except root), so there is nothing preventing you from removing bloat. even xposed works. you can even flash 27 kernel on both 25/28 and clean them too using same flashable zips. as far as custom rom goes, yeah, no, mtk device. prolly not gonna happen. be happy if you get root eventually.
Click to expand...
Click to collapse
can you tell me the procedure on installing twrp?
i really wanted to enable multi window via adb when on recovery mode.
thanks
sikica133 said:
twrp isn't really a problem. it works for the most part, just cant be perma flashed, only booted.
Click to expand...
Click to collapse
I could flash only 3.0.3 . 3.1 never worked for me. Can't even boot.
i never said it could be flashed. it could be booted into. there are plenty of guides around how to boot recovery using fastboot (google fastboot boot recovery.img). once there, you can simply use adb sideload, or integrated file manager to clean system apps and reboot back into os. if you are using 25/28 u'll need to play a bit more to get everything up and running (imei issues), on 27S (multilanguage rom) this is pretty straightforward and no fixing is required
adb devices and uninstall system app
adb devices and uninstall system app
minimal_adb_fastboot_1.4.3_portable --- download androidfilehostcom/?fid=457095661767103465
cmd-here.exe
adb devices
adb shell
pm uninstall -k --user 0 [apk name]
com.letv.agnes
com.icoolme.android.weather
com.letv.android.bugreporter
com.letv.android.carservice
com.letv.android.ecoProvider
com.letv.android.letvyellowpage
com.letv.android.ota
com.letv.android.client
com.letv.android.quicksearchbox
com.letv.android.telextra
com.letv.android.usermanual
com.letv.app.appstore
com.letv.bsp.crashhandler
com.letv.bugpostbox
com.letv.lesophoneclient
com.letv.letvshop
com.singulariti.niapp
com.sohu.inputmethod.sogou.leshi
com.tencent.android.location
sina.mobile.tianqitongletv
com.autonavi.minimap
com.tencent.reading
com.le.share.pro3ai
com.letv.games
com.android.calendar
com.android.noisefield
youtubecom/watch?v=TSwBsw6MgiA
Gapps apk
fex-net/934605209940/246920922 - 4pda
lucky patcher.apk install -- delete all google applications
1-GoogleBackupTransport.apk install and Give all permissions in menu applications
2-GoogleLoginService.apk install and Give all permissions in menu applications
3-GoogleServicesFramework.apk install and Give all permissions in menu applications
4-Phonesky.apk install and Give all permissions in menu applications
5-PrebuiltGmsCore.apk install and Give all permissions in menu applications
İ LOVE TURKEY
Monster 00 said:
As you all know we have been searching for ways to root the Le Pro 3AI but failed. There are even 2 twrp but you can't really do much with them. TWRP 3.1 did not even start for me but 3.0.3 worked but what's the real problem? You can't mount /data and also i found another partition named /custom. It always fails to mount and there is no way to format it.
When you enter TWRP it ask for a password to decrypt. Simply click cancel and go to wipe, advanced wipe and check the data partition. Select repair file system and change it to ext2 and then back to ext4. Reboot to twrp again I don't think this is necessary but better take precautions. Now go to mount and select data you will see that you can actually mount it(~24000mb) .
You can also enable MTP to copy files to your phone in recovery such as .zips. I hope this helps you in way. I hope the devs find a way to make it possible to flash custom ROMs for this phone without any message appearing during boot and that there is no problem with imei. Thanks for reading and don't give up with this phone else it will be money down the drain. If I helped press the thanks button.
Click to expand...
Click to collapse
can you help me enable multi window?
It says that I need to mount system first at the recovery.
Please help me. Thanks a lot.
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
MichRT said:
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
Click to expand...
Click to collapse
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
You have to use last magisk (above 19.4 if my memories are right).
HpNoTiQ said:
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Click to expand...
Click to collapse
This looks like it might work, so thank you! I found a similar, though different solution (below)
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
I ran into the issue that while boot-looping with a magisk patched boot img, I wasn't able to run the command, adb wasn't finding the phone. I tried again after booting TWRP and it basically threw an 'error - command not found'.
HpNoTiQ said:
You have to use last magisk (above 19.4 if my memories are right).
Click to expand...
Click to collapse
I think you are right, in beta/canary channel
@Tulsadiver gave me a hand with this, see here: https://forum.xda-developers.com/showpost.php?p=80398385&postcount=35997
Thank you guys!
finally.... I got Odin to behave - (sadly) no idea what I did it just started working!
What I've ended up with is a fully working magski capable of installing modules and a debloated stock rom - gosh what a horrible user experience Samsung make for there users!
I'd rather not have to rely on the chopped down official recovery though, feeling much more secure with the extra tools available with twrp.
if I dd twrp I'll loose magski, so my question is, can magski patch a twrp img file and will dd'ing this to the recovery partition work, ie will I have twrp while retaining magski
Is there a "better" way to do this (twrp + magski) ?
TIA
Typically Magisk gets installed via TWRP and not the other way around.
AFAIK Magisk creates a new magisk.img partition in phone’s root directory, it also places necessary files in /cache and /data partition, but it does NOT patch /recovery partition. It's TWRP what completely replaces / removes phone's stock /recovery. But I may err as always ...
jwoegerbauer said:
Typically Magisk gets installed via TWRP and not the other way around.
AFAIK Magisk creates a new magisk.img partition in phone’s root directory, it also places necessary files in /cache and /data partition, but it does NOT patch /recovery partition. It's TWRP what completely replaces / removes phone's stock /recovery. But I may err as always ...
Click to expand...
Click to collapse
Samsung user are somewhat force to flash Magisk on recovery partition hence they have to choose between having rooted via Magisk or installing TWRP
But can magski patch a twrp image, for both ?
codifies said:
But can magski patch a twrp image, for both ?
Click to expand...
Click to collapse
After further research it turns out magski's patching is rather sophisticated. Throw an odin tar or raw image at it and it just gets and does the job right.
If like me you didn't want to leave the recovery with a dangerously crippled stock "recovery" it is possible to patch a raw img of twrp, which you can then dd (but please don't guess and DO go by the by-name path !)
I honestly don't know if patching twrp and using it with odin right from the get go is possible I had a nightmare getting windows/drivers/odin talking so I was relieved just getting the patched stock firmware to flash....
Its also a relief to be finally rooted, debloated, degoogled with a proper recovery, of course if samsungs UX wasn't so horrible I might not have bothered (providing all bloat could actually be disabled)... still at least it feels like I own what I bought now....
@ineedroot69 never managed to get twrp to flash on its own with odin, with unlocked bootloader saying it would only install official software... A70 seems to have a few extra layers of security...
hey i want to install a custom rom (gsi) so i hope some people can help me out
main info: i have a ulefone note 9p with mediatek 6762 (runs with mediatek 6765 android scatter) and android 10.
this twrp is a twrp 3.4.0. built for ulefone note 9p i downloaded from here:
unofficial twrp 3.4.0 Root Ulefone Note 9P - unofficial twrp
download unofficial twrp 3.3.1 root Ulefone Note 9P, user who own Ulefone Note 9P can root it by following the below instructions
unofficialtwrp.com
after going to the painful procedure of unlocking bootloader flashing stock and twrp modified rom + rooting the device
i stuck at the procedure to install a gsi image via twrp.
i already know that the device must be unrooted and i have already gained some experiences in flashing the rom
even after a few softbricks, so i will try installing this image with a stock rom and twrp after i received the help i need.
i use a sd card because twrp always disappears when i transfer a file via my phone and i land on stock recovery.
this problem solves when i root my phone via magisk. as i heard flashing gsi's dont work in a heavy modified state (like with magisk),
so a sd card solved this problem to run files on recovery mode without file transfer and rooting.
the problem i have is the following: i followed some instructions saying to wipe some data first in advanced wipe
- also the system partition which is not available. after that tried to install the image directly. as it finds the rom from my sd card i have to select the partition type to flash image
i only have boot recovery and super available but i need the system partition. i looked in the internet further (the painful process) and it gave me some hints going to mount.
there it finds the system partition but when i set a checkmark on it nothing changes, so this hint didn't helped me.
what should i do now? i'm stuck in some dead end and i don't know what to do it seems like this is the only way for me to get it work.
please help.
i think i found something. since my phone is rooted i also tried to delete system apps which also don't work. i tried many system app removers but it always give error. i think the problem lies in permissions that are not given to this phone. how can i get full access to \ system to gain full permission rights? i also have busybox installed btw
You've to mount the /system partition as RW in order to access this storage location.
Example code:
Code:
adb devices
adb shell "su -c 'mount -t auto -o rw,remount /system'"
/* excuse windows person in advance for poor grammar */
TL;DR:
LG V20 H918
bootloader unlocked
bootable LOS19.1
no fastboot available
no recovery available
Goal: setup magisk using adb root shell
Is it possible?
What happend:
On stock LG V20 H918 no flashing was available in fastboot, probably done by manufacturer.
No stock recovery available as well.
I was able to unlock bootloader and install TWRP using "lafsploit".
Then I installed LOS 18.1 and Magisk with TWRP.
Everything worked perfectly.
Later I decieded to update to LOS 19.1, and probably forgot some step in the process.
LOS 19.1 boots and works OK, but without root/magisk. TWRP now stucks in splash screen.
I unable to install Magisk or restore backup without TWRP.
I unable to reflash TWRP without fastboot.
But I have acces to adb root shell!!!
So I thought it should be possible to repeat all changes Magisk does when patches boot.img, right?
I examined boot_patch.sh from magisk.akp, then compared original and patched img-s.
Waht I concluded magisk does:
1: create ".backup" folder in root
put there original "init" file
put there ".rmlist" file with what to remove on uninstall
put there ".magisk" file with checksum and other variables
2: create "overlay.d" folder in root
create "sbin" folder in "overlay.d"
put there same ".xz" files mentiond in ".rmlist"
3: perform some modifications to "init" file in root
Will it work if i repeat all this changes through shell?
Or do i need to do something else, like changing that checksum somwhere?
I have all this files from patched "boot.img", including that "init" file.
Is this a guide, or a question?
If this is a guide, you need to write it in such a way that others can easily follow it.
I don't know enough about LG devices to tell you whether you can accomplish what you're trying to do. From what I can see, rooting is extremely complicated. This is why I have a Pixel.
This is a question, I just atempted to give as much information as possible.
IMHO this sitiation should not be specific to this particular device.
In other words, is it possible to install magisk by "patching files" on booted system? (without re-flashing boot.img?)
I had to flash the lineage recovery to replace twrp when i installed the 19.1 rom. You can still install magisk using the lineage recovery.
If I recall however you can also patch the bootloader to install magisk through the installed magisk app itself aswell. As for the specifics of your question of installing it without patching of some way to the bootloader... ive no clue.
I was unable to install recovery, and there was no recovery when I got this phone with "stock ROM". thought it was done this way by oem.
Atempting to boot into recovery results in "brocken android icon" with "no command" text.
Yes, this is how I installed magisk first time: install app -> patch boot image in app -> then re-flash patched image with twrp.
My idea is to do all reqired changes manually, as we have root acces from adb shell:
As for now I mimicked difference betwen patched and original 'boot.img', which coresponds to "Ramdisk Patches" section of Magisk's "boot_patch.sh":
'.backup' and 'root/overlay.d/sbin' folders and their contents, init file and all permissions
Phone boots but no changes in magisk
Also added '99-magisk.sh' to /system/addon.d
It seem to launch, but no changes in magisk too.
Posting in case somebody will search for this.
For magisk to work some changes in kernel may be reqired. If kernel in patched boot image is different from original, then there is no solution this way.
Wiping cache and userdata can possibly fix TWRP bootloop, but If your fastboot unable to flash anything, then it probably also will be unable erase/format cache and userdata.
>>>!!! Backup first if you can, this will erase all your files and apps !!!<<<
Try to do hard factory reset this way, it helped in my case:
- Turn the phone off.
- Press and hold "Vol. down" + "Power btn"
- When LG logo appears, release "Power btn" for ~0.5sec. then push again
- Hold "Vol. down" + "Power btn" until hard reset menu appears.