Related
Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Anyone can help?
Install twrp then use supersu v2.65
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I have tried some twrp recovery. It can enter the recovery successfully but it cannot boot normally. It stuck at samsung logo.
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I've tried to dig more in it, and what I get is
1. The only way I succeed is by using KingRoot, and the method it's using is by exploiting and keeping a daemon background and the su file for calling the daemon. So that means after reboot, root is lost.
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
4. In the bootloop, logcat shows that it is repeating a particular normal boot process
5. In the bootloop, using adb shell and typing "su" will not get into root, despite su is located in xbin.
6. Busybox functions normally.
Any ideas?
ProtoAES256 said:
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
Click to expand...
Click to collapse
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
ashyx said:
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
Click to expand...
Click to collapse
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
From my current experience, no. The sad thing is I'm not skilled enough to do it myself, and seemly there is no reason that skilled devs are willing to have a head in to this not-quite-popular device.
Btw, you need to format /system partition before you flash the kitkat(well, maybe it works maybe it don't, it's just my experience.)
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
If you have twrp installed I will upload a modified version of SuperSU which will allow systemless root on 5.0.2.
This will patch the boot image and should prevent a bootloop.
ashyx said:
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
Click to expand...
Click to collapse
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
ProtoAES256 said:
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
Click to expand...
Click to collapse
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
ashyx said:
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
Click to expand...
Click to collapse
here you go, extracted from A700YDZSU1BOL4_A700YDZZT1BOL4_A700YDZSU1BOL4_HOME.tar
https://mega.nz/#!14IE3YoA!mRAhQSJCgZ53r5teACeJGWMwrftIY0g0GvZM0LMX9Kg
Hi everyone!
I found this two files, they are recovery.img and supersu 2.46. I still haven't tested them, because recovery is in img format and it has only the Chinese language. If anyone can help me translate the recovery and convert it in tar.md5 format. I found this 2 files on a700yd chinese forum. Thanks!
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
ashyx said:
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
Click to expand...
Click to collapse
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
ProtoAES256 said:
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
Click to expand...
Click to collapse
Try the supersu version above.
ashyx said:
Try the supersu version above.
Click to expand...
Click to collapse
i just update myphone to new firmware. i see something new eg : About device > "android security patch level"
i have same prolem (myphone boot stuck after flash superuser.zip v2.62-2.72 via twrp). And i try reflash one old boot.img via odin then myphone boot up normally with superuser.
i think the new boot.img make myphone stuck.
Can you please help me patch the new boot.img !?
ps: i'm so sorry for my bad english
https://drive.google.com/folderview?id=0B7uFmNBw-G1QalBCZERkeUpjd0U&usp=sharing
Hi Guys!
I ask you if someone used cf-auto root on this device and it was able to root the phone? Thanks.
hkopenh17071 said:
Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Click to expand...
Click to collapse
http://forum.xda-developers.com/samsung-a-series/development/galaxy-series-cf-auto-root-t3280406
Hi guys! I'm on stock rom Nougat, since i installed magisk i'll always get error when i tried to update my phone from Update setting (samsung things...).
But when i installed Xposed and especially a module known as Firefds which set fake system status to "Official" (it was "Custom"), when i go back to check for a new update i found this (attachement).
So what do you think guys? Should i update? Maybe its November security patch...
But i don't want to lose twrp, magisk and all the stuff !!
This update didn't includes November patch so far I know. This will be listed in the patch notes for sure.
If you install the OTA update...this will end not well I think. You will running in an unstable system because of root, twrp etc. This update will replace files which are eventually needed and so on.
I suggest you flash stock rom with odin, then install the update then re-root and re-flash twrp. Yes it is annoying, but its better to be safe than sorry
zzThrain said:
I suggest you flash stock rom with odin, then install the update then re-root and re-flash twrp. Yes it is annoying, but its better to be safe than sorry
Click to expand...
Click to collapse
What about flash this update using FlashFire and keep twrp & magisk? I saw it in many other phones
Mrbinki said:
What about flash this update using FlashFire and keep twrp & magisk? I saw it in many other phones
Click to expand...
Click to collapse
You can of course do so...but my experience is that such methods will not end well. Do it like @zzThrain wrote it and download firmware from SamMobile with DQJ3 and reflash twrp and re-root to be sure that your system don't come unstable.
Any chance for OTA updates with Magisk only (without Xposed, etc.)?
If there is no chance - is there a place to download only monthly security updates - since full firmware versions (found at sammobile) are at least 10x times larger than the monthly updates?
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.
I'm following the topjohnwu's guide on how to update with Magisk but I do not find it clear enough. Are these the steps I need to take in order to not-brick and update my phone with the Feb update.
1. Uninstall Magisk by "restore images" option.
2. Install OTA
3. Reboot to reinstall Magisk on second slot
Magisk is NOT installed on the second partition! And I prefer not to flash back the original image just to do that. My system should be read only and I do not have twrp, I never had, I updated my Google services framework from apkmirror and I got the update, now how do I apply it without soft bricking?
Update
Step 2 failed, "installation problem". Wtf do I do in order not to lose Magisk or data?
Edit
I've uninstalled Magisk but haven't restarted, hoping to get a solution where I keep my sh*t since that's what the guide said...
Edit 2
I'm reading the other thread but I'm having trouble finding a single useful information there, quote one if you find it, it might be my autism that I don't see a solution in that three pages long thread. Tell me I need to MiFlash this sh*t so I calmly jump through my window instead of wasting the whole night on making it work, then wasting another day on backing my sh*t up.
Edit 3
Fully uninstalled Magisk by instructions of an indian guide. BOOTLOOP.
Note to self, stop following southern asian guides.
Downloaded ROM and MiFlash, flashed flash_all_except_storage.bat.
Shook for 4 minutes until "success" mark, successful reboot.
Edit 4:
follow the regular magisk flash guide https://forum.xda-developers.com/mi-a1/help/how-to-root-mi-a1-february-ota-update-t3757934
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
_mysiak_ said:
If you got into bootloop after Magisk uninstallation, you did modify system partition at some point. This is also the reason why you couldn't install OTA. Magisk OTA update guide works perfectly fine for unaltered system partition.
Click to expand...
Click to collapse
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
A14DWIN said:
That's what I figured, but how? I just did exactly everything I did before the OTA attempt, I just installed few modules and touched nothing else. At which point could've I touched system partition?
So I'm reading now that apps can still alter /system with the Magisk root perm, so, I what about one of these apps.
1. Does anyone know if they can mess with the system?
BusyBox
Greenify
Lucky patcher (this c*nt is my main suspect)
Titanium backup
2. Can we somehow make sure that we haven't touched the system partition before OTA attempt?
3. Once I've redone everything (flash Rom without storage, install OTA, install Magisk), my system shouldn't be touched now, right?
Click to expand...
Click to collapse
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Dang I really need that command.
_mysiak_ said:
Please keep in mind that Magisk is 2in1 package. First of all it provides root access, any app with root access can modify system directly. Second feature are systemless modifications, but you must follow defined rules to make them work.
From your list of apps, BusyBox would be my first suspect. You must use Magisk BusyBox module, the standard BusyBox is installed directly to the system partition. Lucky app might be the culprit too, though it depends on which features exactly did you use.
Yes, once you reflash stock ROM, apply OTA and install Magisk (the correct way), you're system partition will be ready for the next OTA.
Someone mentioned one command which could verify the last modification date of any partition, but can't find it right now.
Click to expand...
Click to collapse
Don't bother trying to find it, it exists, I'll make a dedicated thread at some point, thanks for the answer, BusyBox seems logical.
The correct way to install Magisk? I just flash Ranjit's patched img from the official thread on Magisk root, that should be the correct way.
I just use lucky to patch cirtain apps, so that shouldn't be a problem
Right now, I'm giving Magisk root perm to Greenify, Lucky Patcher and Unified Hosts. Also both Greenify and the Unified hosts adblock have their own modules in magisk.
Hopefully I still haven't touched my system partition.
I encountered the error as well after trying the Pixel OTA method. To flash the update successfully, I flashed stock January system and boot img via fastboot and it updated properly after. Then I just patched the stock Feb boot img and went back to fastboot. Once there, i did the fastboot boot command with the patched Feb boot.img so I got root back after updating.
Sent from my Xiaomi Mi A1 using XDA Labs
HI,
I have a redmi5+ rooted. I use luckypatcher (i applied some patchs to some apps) and i have installed once BusyBox (didn't do anything in special).
I want to know if it is secure to flash the full update?
PS: how do I confirm if the system files and vendor are ok to proceed?
Thanks
cant you flash the ota in twrp and then reflash magisk if needed?
robgee789 said:
cant you flash the ota in twrp and then reflash magisk if needed?
Click to expand...
Click to collapse
Yes, I can do that.
I Know the procedure to flash full zip file via TWRP. Via this toturial: youtube.com/watch?v=oUUzxYHV_ac&t=1s&index=11&list=WL
But i want to know if it is secure to flash, because i used these two applications.
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
Update using local, dont reboot - go to magisk; install to inactive slot(after OTA) *disable module to be safe - Then restart
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
dladz said:
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
Click to expand...
Click to collapse
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
cubeplayer1 said:
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
Click to expand...
Click to collapse
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
I'm rooted with an unlocked bootloader on 11.IN11AA (Global). How do I perform a local upgrade without the OTA file to put into the root folder? It seems like the Global version of the OTA file is nowhere to be found and I can't download it via System Update since it fails due to root. Do we need to just wait for the 11.0.1.1.IN11AA OTA zip file to be posted? Thanks in advance.
Yes, looks like we are in waiting mode for it to show up...
dladz said:
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
Click to expand...
Click to collapse
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
You'd have to install locally even with oxygen updater.
galaxys said:
Yes, looks like we are in waiting mode for it to show up...
Click to expand...
Click to collapse
Yea I guess that's why Oxygen Updater isn't showing anything new for me. Once it shows up on the internet, I'm sure the OU app will refresh and show an available update.
cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
dlhxr said:
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
Click to expand...
Click to collapse
Thanks for these steps, it worked for me. After I flashed Magisk via the Magisk App to the inactive slot, I rebooted and had the latest version installed with root preserved. :highfive:
After I did it I'm getting the com.android.phone stopping and my Sims aren't recognized. I cleared cache, phone and SIM toolkit but didn't work. Grrrrr
I'm a rooted global user and update has never showed until today. It was only 405mb and Google play services was showing the update. Oxygen updater shows nothing and system update shows nothing. I'm gonna wait to see what happens since it's not a full update
Same here global 406 mb ota. It's like not recognizing we have root...
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
Good looking out bro, that worked a charm. :good:
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
^^^^^^This -- easiest and fastest root upgrade I have ever done on any device.
Magisk is now built to do it this way.
bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
This worked for me as well taking the actual partial OTA update from system update and going through the steps in Magisk.
A little nerve wracking considering the many times trying to update has failed on my last couple OP devices, but at least this time, it worked.
Thanks.
anyone have a patched magisk boot for IN2025?
I did the steps of flashing the stock boot.img, then booting the patched img, installed the OTA, used magisk to patch before reboot, but when it rebooted it said installation failed, and i was unable to access magisk after that as it was on the wrong slot... I had to apply the OTA update again, and now am stick without root
IN short, need either a stock IN2025 boot image to patch myself, or a magisk patched one...
TIA