Related
I am upgrading my OP3T from 5.0.1 to 5.0.3. My device is rooted using magisk and I have TWRP installed.
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?
EDIT - I read about Dirty flashing the version I want but I can't find 5.0.3 image on Oneplus website.
shantam2 said:
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?.
Click to expand...
Click to collapse
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
przemcio510 said:
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
Click to expand...
Click to collapse
Re-flashing magisk via TWRP will keep my data ?
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Can you elaborate more on this ?
After I upgrade (and it becomes unrooted). I immediately flash magisk via TWRP ?
I didn't get the part "flash the whole rom and don't exit" ?
Also, Will I lose any data in the process ?
shantam2 said:
Re-flashing magisk via TWRP will keep my data ?
Click to expand...
Click to collapse
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
przemcio510 said:
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
Click to expand...
Click to collapse
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
b4bass said:
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
Click to expand...
Click to collapse
If you flash the update downloaded as zip from downloads.oneplus.com via TWRP, then no, there will be no need to flash it again via fastboot and no need to install TWRP Manager.
Boot to TWRP
Flash 5.0.3 zip
Flash Magisk
Reboot & enjoy
OK thanks! I thought the recovery would go back to stock after flashing the rom
And guys, if other members help you with their posts, don't forget to thank them.
Unleashed by my rooted OP3T on 8.0
b4bass said:
OK thanks! I thought the recovery would go back to stock after flashing the rom
Click to expand...
Click to collapse
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
So magisk is patching bootloader? I thought it was it point not to
Though this method is saving me some serious time!
b4bass said:
So magisk is patching boot, I thought I was it point not to
Though this method is saving me some serious time!
Click to expand...
Click to collapse
Magisk makes a point of not touching the system partition but a lot of its magic is done by changing the boot image.
Sent from my OnePlus3T using XDA Labs
OK thx ! First time I replaced supersu to pet magisk. Will have to find more details on this subject
b4bass said:
So magisk is patching bootloader? I thought it was it point not to
Click to expand...
Click to collapse
Boot image is kernel and ramdisk. Boot image is not the same as bootloader!
I have an Mate 10 AL-L29. 4 days ago l tried to rebrand it to chinese model android 8.1, firmware 321. After rebrand l saw my emei is 0000000000. l did it some days ago and all was fine! Now if l make downgrade to a old firmware, my imei is fine, but if l do an upgrade to a new firmware, it doesn't matter ALP-L29 or ALP-AL00, my imei is gone! Right now l'm on the newest android 8.1- 325 firmware. All works good.....root, phone, google play etc..
The only problem is my Imei 000000000 , but MEID is ok.
Any solution guys? Thanks!
Try factory data reset.
badmania98 said:
Try factory data reset.
Click to expand...
Click to collapse
It was the first thing that l did... It isn't so simple....seems oeminfo don't do its job when l try to restore it. I have 2 backups of oeminfo, with twrp and with HwOta8_Mate10..
Root works on ALP-AL00 8.1.0.326(C00) , how? I tried Magisk but the device gets stuck on 'your device is booting'.
25Swagat said:
Root works on ALP-AL00 8.1.0.326(C00) , how? I tried Magisk but the device gets stuck on 'your device is booting'.
Click to expand...
Click to collapse
Try patching ramdisk.img from Manager but make sure Preserve AVB/DM-Verity is checked, then flash it from fastboot.
ante0 said:
Try patching ramdisk.img from Manager but make sure Preserve AVB/DM-Verity is checked, then flash it from fastboot.
Click to expand...
Click to collapse
Do you mean the stock ramdisk.img of the software I'm in? If so, then I did that and checked Preserve AVB/DM-Verity in Magisk, then flashed the patched ramdisk.img in fastboot. After rebooting, I opened Magisk but it says Magisk is not installed.
Also, after that didn't work, tried installing it from Magisk.zip but it only downloads but doesn't get installed.
25Swagat said:
Do you mean the stock ramdisk.img of the software I'm in? If so, then I did that and checked Preserve AVB/DM-Verity in Magisk, then flashed the patched ramdisk.img in fastboot. After rebooting, I opened Magisk but it says Magisk is not installed.
Also, after that didn't work, tried installing it from Magisk.zip but it only downloads but doesn't get installed.
Click to expand...
Click to collapse
You have to flash the zip from TWRP. It doesn't flash if you aren't rooted already.
ante0 said:
You have to flash the zip from TWRP. It doesn't flash if you aren't rooted already.
Click to expand...
Click to collapse
I can't boot into twrp after flashing patched ramdisk. Do I have to flash twrp again? Somehow, while trying to get into TWRP, I can't but after rebooting Magisk is installed and works but after rebooting it isn't installed. Never mind mate I got it to work. Thanks!
25Swagat said:
I can't boot into twrp after flashing patched ramdisk. Do I have to flash twrp again? Somehow, while trying to get into TWRP, I can't but after rebooting Magisk is installed and works but after rebooting it isn't installed. Never mind mate I got it to work. Thanks!
Click to expand...
Click to collapse
If it's working do explain how you did, in case others with the same problem see this
ante0 said:
If it's working do explain how you did, in case others with the same problem see this
Click to expand...
Click to collapse
I followed @Tecalote instructions posted at https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
I received an update in Magisk just a while. Anx opening up i have found that my magisk is not not installed and so the root is gone.
I clicked on install button, it says Install with zip and another option is install with patched boot.
I clicked on install with zip, it downloaded a zip in download folder, but as we dont have recovery now i dont know what to do with that zip. or should i go for patched boot img. and if yes? then how? thanks!
I had it too and root was detected after I rebooted my phone.
did u update? and how?
+1
I lose my root, magisk don't update, and rebooting don't solved.
I'm getting tired of A2.
pack21 said:
+1
I lose my root, magisk don't update, and rebooting don't solved.
I'm getting tired of A2.
Click to expand...
Click to collapse
What are all of you doing? Just install the modified boot image and be done. Never had any issues here.
Benjamin_L said:
What are all of you doing? Just install the modified boot image and be done. Never had any issues here.
Click to expand...
Click to collapse
need a link of that modified boot image. !
Syed Shahriar said:
need a link of that modified boot image. !
Click to expand...
Click to collapse
It's in the dump thread of the August image
Benjamin_L said:
It's in the dump thread of the August image
Click to expand...
Click to collapse
i m a bit of noob here. i gathered that patched_boot.img from august dump. now what to do in order to get the latest magisk working?
Syed Shahriar said:
i m a bit of noob here. i gathered that patched_boot.img from august dump. now what to do in order to get the latest magisk working?
Click to expand...
Click to collapse
Just use as is, flash with fastboot, or patch the unpatched one with magisk manager and flash that. More wasn't needed on my side.
Benjamin_L said:
Just use as is, flash with fastboot, or patch the unpatched one with magisk manager and flash that. More wasn't needed on my side.
Click to expand...
Click to collapse
I flashed patched_boot.img, now it shows magisk installed . but root is not there still. i have one option INSTALL, clicking it says 1)via zip 2) patched boot
Syed Shahriar said:
my apology, here's what i should do:
1) fastboot flash patched_boot.img
2) reboot set and install latest magisk apk
3) hit install from that app
is it so?
Click to expand...
Click to collapse
No the patched boot image already is like installing magisk. Or to put it differently that's what happens when you install it the normal way so all you need is to flash the boot image and have magisk manager installed
Benjamin_L said:
No the patched boot image already is like installing magisk. Or to put it differently that's what happens when you install it the normal way so all you need is to flash the boot image and have magisk manager installed
Click to expand...
Click to collapse
ok now as its stands, just flash the boot image and then open up magisk. ( i have already magisk installed , but as unrooted, and it asks to update)
Can someone upload the stock boot img from the August security patch so I can patch it with the updated magisk v17 because I have the same problem?
I i already have the august patched boot image, can i just update magisk from the app?
conan_88 said:
Can someone upload the stock boot img from the August security patch so I can patch it with the updated magisk v17 because I have the same problem?
Click to expand...
Click to collapse
Find it in the dump thread
Benjamin_L said:
Find it in the dump thread
Click to expand...
Click to collapse
I couldn't find a boot.img in the dump files. only bootanimations.zip but I don't think that's it.
Can you please tell me the directory or the file name so I can search for it?
Thanks.
conan_88 said:
I couldn't find a boot.img in the dump files. only bootanimations.zip but I don't think that's it.
Can you please tell me the directory or the file name so I can search for it?
Thanks.
Click to expand...
Click to collapse
Dump thread I said: https://forum.xda-developers.com/showpost.php?p=77275242&postcount=25
Benjamin_L said:
Dump thread I said: https://forum.xda-developers.com/showpost.php?p=77275242&postcount=25
Click to expand...
Click to collapse
Found it. Thank you very much. It is working now.
Rom OneOS based A715FXXS7BUJ1
read to all
Hi guys, here I share my ROM for the Galaxy A71, I am not responsible for damaged phones, install at your own risk.
This rom was born from the need to have root or some other modification in stock but Samsung has included many limitations which make it difficult to modify in stock.
Features
Debloat
vaultkeeper disabled
FRP removed
knox counter at 0 (Samsung Health)
Fingerprint animation changed
optimizations
Google Discover enabled
Dolby without headphones
Apply themes without trial time limit
Deknoxed
Full Edge Lighting (extra effects unlocked)
Secure Folder working
Floating Feature tweaks
Mock Locations
Mock Providers
High Volume Warning (disable)
Secure Flag
Recovery Reboot (this is when you press Reboot and he Reboot to recovery)
Click to expand...
Click to collapse
BUGS: At the moment it has not reported any bug.
Installation:
Extract OneOS ROM with an unzip program
Reboot recovery
Format data
Install ROM as "super" image in TWRP
Flash muiltidisabler
Flash Magisk (optional)
Reboot
Downloads:
Version 1:
Link: Google Drive
Credits: Kernel Source (Link)
Hello from Greece
I try this rom for 2 days . Everything looks fine . I have not any problem.
Thank you very match
ZhandarbekD said:
Rom OneOS based A
Click to expand...
Click to collapse
Please check your PM inbox. Thank you.
-Regards: Badger50 FSM
Getting error 255 when flashing custom rom how to fix
Unable to flash any custom rom due to this error occurring
Here the error
Is it possible to dirtflash with NcX?
How to install ?
I get 255 error on TWRP.
papgr00 said:
Hello from Greece
I try this rom for 2 days . Everything looks fine . I have not any problem.
Click to expand...
Click to collapse
Any bug ?
How i can install ?
I getting 255 error on twrp
josegarcia01 said:
Any bug ?
How i can install ?
I getting 255 error on twrp
Click to expand...
Click to collapse
What TWRP version do you use?
Pupet_Master said:
What TWRP version do you use?
Click to expand...
Click to collapse
Twrp 3.5.1
josegarcia01 said:
Twrp 3.5.1
Click to expand...
Click to collapse
Well you may not like to risk but i feel that the error is due to TWRP not being able to write on the device.
First things first, try to download again the ROM, and don't flash the zip file, but flash the .img file inside.
Pupet_Master said:
Well you may not like to risk but i feel that the error is due to TWRP not being able to write on the device.
First things first, try to download again the ROM, and don't flash the zip file, but flash the .img file inside.
Click to expand...
Click to collapse
I did, tried to flash The img file.
And tried With twrp 3.6 too
josegarcia01 said:
I did, tried to flash The img file.
And tried With twrp 3.6 too
Click to expand...
Click to collapse
It could also be TWRP not being able to access the internal storage to write the ROM.. but im not positive
Pupet_Master said:
It could also be TWRP not being able to access the internal storage to write the ROM.. but im not positive
Click to expand...
Click to collapse
Can you help-me to solve this ?
or, how i can find on the internet ?
josegarcia01 said:
Can you help-me to solve this ?
or, how i can find on the internet ?
Click to expand...
Click to collapse
I think you should try to flash magisk and see if it flash ok
If so, i dont know what the issue is... if it wont flash ok, you will need to format your phone data
Pupet_Master said:
I think you should try to flash magisk and see if it flash ok
If so, i dont know what the issue is... if it wont flash ok, you will need to format your phone data
Click to expand...
Click to collapse
Flash ok, i tried magisk, and multidisabler, both Flash ok.
The system img as a super i get these error.
josegarcia01 said:
Flash ok, i tried magisk, and multidisabler, both Flash ok.
The system img as a super i get these error.
Click to expand...
Click to collapse
Ok, i don't know what is the problem.
Either risk format the phone data (but you will lose everything) and try to flash again... or well... wait for the author to reply.
Pupet_Master said:
Ok, i don't know what is the problem.
Either risk format the phone data (but you will lose everything) and try to flash again... or well... wait for the author to reply.
Click to expand...
Click to collapse
Everytime i tried formating data.
I dont tried withouth format data.
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
If you originally patched the Samsung firmware and rooted under OneUI, that same version of Magisk will show up once you flash any GSIs.
Besides that, there's no other way that I know of since you can't simply sideload Magisk through TWRP for this device
You'll have to start over by patching the firmware and flashing through Odin to get back to stock. From there, set up Magisk like you'd normally do. Once that's done, you can proceed and use the same guide to get LOS back and be fully rooted with Magisk
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
You just need to install the magisk apk and run it. There is no need to patch anything.
lewmur said:
You just need to install the magisk apk and run it. There is no need to patch anything.
Click to expand...
Click to collapse
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Simply installing the Magisk APK is not the same. To install Magisk completely to your system you must patch the image.
For this device, you need to complete the patching process first with Samsung's firmware under OneUI. Once that's done, you can return back to LOS and a patched version of Magisk will be waiting for you to install
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
lewmur said:
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
Click to expand...
Click to collapse
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
itscryptic said:
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
Click to expand...
Click to collapse
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
lewmur said:
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
Click to expand...
Click to collapse
I do not see a direct option, it is only showing select a file to patch when I tap install...
itscryptic said:
I do not see a direct option, it is only showing select a file to patch when I tap install...
Click to expand...
Click to collapse
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
lewmur said:
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
Click to expand...
Click to collapse
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
That's normal. Ignore it.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
How did you flash the Magisk.apk with twrp?
gguman said:
How did you flash the Magisk.apk with twrp?
Click to expand...
Click to collapse
Use the "Install" button to flash as if it were a zip file.
lewmur said:
Use the "Install" button to flash as if it were a zip file.
Click to expand...
Click to collapse
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
So long as you know where it is, you should be able to browse to it. You might have to "Select storage" to switch between Internal and Micro SD. If it doesn't show, try renaming it from .apk to .zip.
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
You have to rename it as a ZIP, you cannot flash APK files
kevinco1 said:
You have to rename it as a ZIP, you cannot flash APK files
Click to expand...
Click to collapse
Not necessarily so. I've installed apk files in TWRP many times. It depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Just curious, what other apps can you do this besides Magisk?
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Successfully installed apk:
0) stock firmware
1) install TWRP
2) Formated data
3) Wipe all data
4) adb push magisk.apk to /
5) Install apk from TWRP
6) reboot to fastboot
7) flash LOS20