Vivo y72 5g mtk how to root - Vivo Y51L Questions & Answers

If i modify ota update boot.img file via magisk and install full ota it will work?
Pls help

adex234 said:
If i modify ota update boot.img file via magisk and install full ota it will work?
Pls help
Click to expand...
Click to collapse
You have to unlock bootloader first... But i am currently looking for a solution on how to unlock it it is very difficult. You may look for it also. Maybe if we are several people to look for that we maight finda solution

Can I manualy move su files via adb?

Related

Root on Android 4.3 [Locked bootloader, but needs to be unlock-able]

Hello Everyone.
Yesterday, I updated my "Global" Z1 firmware to Android 4.3 and then {Of course} I had no root. I already had a TA backup from 4.2 (534) and already un/relocked the bootloader so I am not worried about warranty. So I tried something to get Full root on Locked bootloader.
What I basically did is that I unlocked the bootloader, turned on USB debugging, downloaded doomkernel (Made by @DooMLoRD) and then in fastboot I wrote the command:
Code:
fastboot boot boot.img
Then it restarted and booted doomkernel once (fast boot filename.img makes the phone boot that kernel once) and then flashed the latest SuperSU zip using TWRP recovery (VOL Down) and then went to Advanced → Fix Permissions. Then tried mounting /system as R/W but with no success. So I then flashed doomkernel using the following fastboot command:
Code:
fastboot flash boot boot.img
and then installed the latest XZDualRecovery by @[NUT] and then I had 4 recoveries So I flashed stock kernel and XZDualRecovery wasn't uninstalled, So what I did is that I flashed the SuperSU zip again (using TWRP) and then booted up.
In the first boot, I couldn't mount /system as R/W but I restarted for some reason. and tried to mount as R/W and it worked!
So I relocked my bootloader (by restoring the TA) and now I have full root on TOTALLY STOCK 4.3 Locked bootloader :victory:
Now, when I go to /system/etc/init.d I find a file named "99SuperSUDaemon" and I remember reading somewhere that init.d has something to do with what should work on boot (other than system booting things, cuz I only see that file). So maybe that fixed the "Partial root" problem. Don't know where it came from, but it works :highfive:
Just thought that it might be good to share some info with others, might be useful for people who doesn't want to use ftf's of other places like someone in MEA (me) doesn't want to use UK or US or any other ftf cuz of more bloatware.
Regards,
~J2C
May I ask you how you can verified if you have a Full Root or Semi Root?
Well, I have been removing system apps and I can mount /system as R/W.
If there's a way I can check, please tell me how.
Edit: I actually don't know what does "Semi Root" mean.
Regards,
~J2C
That was allready told here, with links to the description.
http://forum.xda-developers.com/showthread.php?t=2588331
Just2Cause said:
Edit: I actually don't know what does "Semi Root" mean.
Click to expand...
Click to collapse
Not Full Root. Half and Half.
eclyptos said:
Not Full Root. Half and Half.
Click to expand...
Click to collapse
Yes, I have full root.
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Just2Cause said:
Yes, I have full root.
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Click to expand...
Click to collapse
Could you please explain step by step? I mean for example when fid you install dual recovery?
Sent from my C6903 using Tapatalk
Just2Cause said:
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Click to expand...
Click to collapse
I do not use OTA, I don't have it. So I have to find a different way. I can only update to 4.3 from recovery or flashtool.
ArashMiniStar said:
Could you please explain step by step? I mean for example when fid you install dual recovery?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I installed dual recovery after flashing doomkernel
eclyptos said:
I do not use OTA, I don't have it. So I have to find a different way. I can only update to 4.3 from recovery or flashtool.
Click to expand...
Click to collapse
I can go to cwm and create a flashable zip from there and give it to you if you want
@eclyptos
I know you didn't ask for a 4.3 flashable zip but here it is:
Update.zip
I don't know if something needs to be removed from the zip, but all I did is that I wen to cwm and clicked on "Clone ROM to update.zip" and then uploaded it to google drive.
Regards,
~J2C
Which rom it's exactly in the zip file? Stock?
eclyptos said:
Which rom it's exactly in the zip file? Stock?
Click to expand...
Click to collapse
Yes, Global stock.
But I removed some apps that I don't want/use (most of them are extensions for twitter and flickr and such things) and I added some apps.
Regards,
~J2C
Root for locked bootloader but need to be unlock-able?!
If the BL is unlockable then it is useless to say it is for locked bootloader, if it's lock it's lock.
Once it is unlocked user can flash a pre rooted rom or kernel...
babylonbwoy said:
Root for locked bootloader but need to be unlock-able?!
If the BL is unlockable then it is useless to say it is for locked bootloader, if it's lock it's lock.
Once it is unlocked user can flash a pre rooted rom or kernel...
Click to expand...
Click to collapse
Can you try this for me? You'll find attached zip containing the file in the original post in page 1.
Just2Cause said:
In case if you're on 4.2 and you can OTA to 4.3 (and you have root) try to copy the file 99SuperSUDaemon to /system/etc/init.d and then reboot, uninstall dual recovery, update to 4.3 OTA and check if you have full root. If you DO have full root, then you can install XZDualRecovery again and enjoy android.
Edit: uploaded the file, unzip (NOTE: it's NOT a flashable zip!) and copy it to /system/etc/init.d and give it permissions rwsr-xr-x
Regards,
~J2C
Click to expand...
Click to collapse
Works!
I don't have init.d folder but I gained full root as well as my bionz is intact....

OTA Update-DL-Link for french MotoG (Blur_Version.176.44.9.falcon_umts.Retail.en.FR)

This OTA-Update will update your french (Retail.en.FR) MotoG from Blur_Version.174.44.9.falcon_umts.Retail.en.FR to Blur_Version.176.44.9.falcon_umts.Retail.en.FR.
Don't get fooled by the filename this is indeed the 176.44.9 update. You might need to change the file name to "Blur_Version.176.44.9.falcon_umts.Retail.en.FR.zip" in order to install via SDCARD (copy renamed update to /sdcard/ on your phone) method
http://www.file-upload.net/download-8643048/Blur_Version.174.44.9.falcon_umts.Retail.en.FR.zip.html
MD5 checksum: 56934274b7985aad92ea4fc08bc29f12
PS: Please ignore the thread title. I've mixed up OTA and OTG . I've reported myself to get it changed.
... or without renaming it can be installed via stock (!) recovery.
Edit: Philz can be used too.
drfr said:
... or without renaming it can be installed via stock (!) recovery.
Edit: Philz can be used too.
Click to expand...
Click to collapse
Hello,
Is that possible to install this firmware update with root ?
When i try to apply with custom recovery, he say errors happen.
Thanks
Math43 said:
Hello,
Is that possible to install this firmware update with root ?
When i try to apply with custom recovery, he say errors happen.
Thanks
Click to expand...
Click to collapse
My experience is that root is not a problem. And when Philz recovery warns you about non-signed file, just ignore it.

How to update my LG G6 firmware when rooted?

Hey, so I am all new to rooting, I have rooted my G6 H870 with TWRP and Magisk, I have been getting messages on the phone telling me to install a software update, but after some browsing around I am told not to do it directly via the install button and that I need to flash the update, how do I do this?
As far as I know I need to install the update and flash it with FlashFire so all my data won't disappear, is this correct?
I am scared to root my G6 D:
Its easy bro. You need just download the update as a zip file and flash it with twrp without deleting your data or anything
What update have you recevied ? 11i ?
If yes that the zip file
https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-11i-rom-t3743582
DamiDev said:
Its easy bro. You need just download the update as a zip file and flash it with twrp without deleting your data or anything
What update have you recevied ? 11i ?
If yes that the zip file
https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-11i-rom-t3743582
Click to expand...
Click to collapse
Yes, it is 11i. So I just need to flash it with TWRP and none of my data, files or memory will be deleted?
SheepSaysBaah said:
Yes, it is 11i. So I just need to flash it with TWRP and none of my data, files or memory will be deleted?
Click to expand...
Click to collapse
No
I do that everytime .. And read the thread for more details

HELP - Is there any straightforward guide on how to root the latest OP7TPro firmware?

Hi guys, I have the OP7TP ME. I have always managed to root it through:
1)extraction of boot_a.img
2)patch file with magisk
3)flash file through adb
4)boot phone and patch again through magisk direct in order to recover wifi functionality
with the latest update though this process doesn't work anymore. Step 4 does not work which means if I do the first 3 and boot the phone, I have no wifi and after a while the phone crashes and reboots.
The only way to fix my phone so that it works again, is to reflash the full official update file.
Any help will be well appreciated on how to get root access without issues again.
Many thanks in advance
lowrider82 said:
Hi guys, I have the OP7TP ME. I have always managed to root it through:
1)extraction of boot_a.img
2)patch file with magisk
3)flash file through adb
4)boot phone and patch again through magisk direct in order to recover wifi functionality
with the latest update though this process doesn't work anymore. Step 4 does not work which means if I do the first 3 and boot the phone, I have no wifi and after a while the phone crashes and reboots.
The only way to fix my phone so that it works again, is to reflash the full official update file.
Any help will be well appreciated on how to get root access without issues again.
Many thanks in advance
Click to expand...
Click to collapse
Don't extract boot_a but extract boot.img which is from the current partition. Also I'd flash via fastboot. You don't need to patch with Magisk again if it's already patched.
Macusercom said:
Don't extract boot_a but extract boot.img which is from the current partition. Also I'd flash via fastboot. You don't need to patch with Magisk again if it's already patched.
Click to expand...
Click to collapse
Thanks I'll try
Macusercom said:
Don't extract boot_a but extract boot.img which is from the current partition. Also I'd flash via fastboot. You don't need to patch with Magisk again if it's already patched.
Click to expand...
Click to collapse
Hi thanks, I just tried with boot.img and it still doesn't work. No Wifi after flashing the patched version of it, and after a while phone crashes. Do you have a detailed guide to link me to?
lowrider82 said:
Hi thanks, I just tried with boot.img and it still doesn't work. No Wifi after flashing the patched version of it, and after a while phone crashes. Do you have a detailed guide to link me to?
Click to expand...
Click to collapse
Check this out: https://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351
That should do the trick
Hi thanks.. Unfortunately that's the guide I followed and it doesn't work no wifi and crash... Have you managed to root yours this way, with the latest firmware? Also I noticed that the latest magisk manager I have, doesn't offer the two options Prserve AVB 2.0/dm-verity & Preserve force encryption...they are just not present in the application....
Sent from my HD1913 using Tapatalk
lowrider82 said:
Hi thanks.. Unfortunately that's the guide I followed and it doesn't work no wifi and crash... Have you managed to root yours this way, with the latest firmware? Also I noticed that the latest magisk manager I have, doesn't offer the two options Prserve AVB 2.0/dm-verity & Preserve force encryption...they are just not present in the application....
Click to expand...
Click to collapse
Strange. Which OOS version are you running? It is fine for me with my BA version (the EU one)
lowrider82 said:
Hi thanks.. Unfortunately that's the guide I followed and it doesn't work no wifi and crash... Have you managed to root yours this way, with the latest firmware? Also I noticed that the latest magisk manager I have, doesn't offer the two options Prserve AVB 2.0/dm-verity & Preserve force encryption...they are just not present in the application....
Click to expand...
Click to collapse
Use beta magisk manager and try again
Also the lack of wifi is usually a mismatched boot to os ver
I'm on latest global ver of op7tp and rooted this way
Thanks! It worked now!

General Nothing OS 1.5.2 update rollout

Just received the stable Nothing OS 1.5 based on Android 13. Finally the wait is over. Check for updates.
What country are you in and what build where you on when you got the update?
bariz143 said:
What country are you in and what build where you on when you got the update?
Click to expand...
Click to collapse
I am using an Indian unit and was using 1.5 beta
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
You'll get it by the end of the week.
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Nothing stable version 1.5.2 arrived via OTA right now in Czech Republic EU.
I was an official beta tester!
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Got it overnight, Croatia
Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.
dedors said:
Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.
Click to expand...
Click to collapse
Open magisk, select uninstall and then restore stock images, DO NOT REBOOT, perform the OTA update, after it finishes DO NOT REBOOT, open magisk, select install, select install in the inactive slot.
After it finishes reboot when magisk ask you to.
You can only apply ota updates if system and vendor partitions are not modified.
You have to restore them if you have modified them or deselect the magisk modules that modify them.
Revanced yt is systemless, like busybox, universal safetynet fix and (obv) systemless host.
If a module modifies system it should be noted on the official repo or xda page.
After the update you can re activate all the modules that modify system and vendor.
Update when you feel it, sometimes it's good to wait, sometimes it's pointless.
If you don't have the ota update message you can update with the zip file.
You still have restore stock images, then either install the ota via dialer (which worked for me) or sideload recovery (which didn't).
After it finishes installing, reboot into fastboot and boot the modified boot.img
Open magisk and direct install it.
Depending on WHERE the operation goes wrong you could need just to boot the modified 1.1.8 boot img again to return in the previous context, maybe you could need to flash the full zip because of a soft brick or in the most extreme cases EDL mode with the guide here in xda.

Categories

Resources