Related
I cannot find anything on point to this direct question (all the guides/forums seem to have you flashing/installing TWRP first then installing Magisk).
I am already unlocked and installed Magisk/rooted with Magisk SU by using the Magisk Manager method with stock recovery.
At this point can I just flash/install TWRP to have a custom recovery without issue? I ask because I want to try out J to the 4n's Active Edge plus but want to make a backup first before tinkering with it. Loved his stuff as a long HTC viper guy.
Thanks in advance.
bakemcbride21 said:
I cannot find anything on point to this direct question (all the guides/forums seem to have you flashing/installing TWRP first then installing Magisk).
I am already unlocked and installed Magisk/rooted with Magisk SU by using the Magisk Manager method with stock recovery.
At this point can I just flash/install TWRP to have a custom recovery without issue? I ask because I want to try out J to the 4n's Active Edge plus but want to make a backup first before tinkering with it. Loved his stuff as a long HTC viper guy.
Thanks in advance.
Click to expand...
Click to collapse
I cannot find the specific thread (if I do find it I will update) but from what I recall you will need to flash an unpatched boot img and then flash twrp. After that you can reinstall Magisk. I know TWRP modifies the boot so that will interfere with Magisk. I hope this was helpful.
xBlu3 said:
I cannot find the specific thread (if I do find it I will update) but from what I recall you will need to flash an unpatched boot img and then flash twrp. After that you can reinstall Magisk. I know TWRP modifies the boot so that will interfere with Magisk. I hope this was helpful.
Click to expand...
Click to collapse
Extremely helpful! Sounds like I would boot loop the phone if I just flashed TWRP in my current configuration.
I'll uninstall magisk, reboot, then flash the stock boot.img and then follow the twrp/magisk install directions.
Much appreciated!
Here's what I did:
1) Boot twrp img file from fastboot
2) Flash the latest twrp zip in twrp. DON'T REBOOT. If you are going to use a custom kernel, you must do step 3 below. Don't later reboot and flash a custom kernel or you can run into bootloader signature issue. If you ARE NOT going to use a custom kernel, jump to step 4.
3) Flash your custom kernel.
4) Flash the latest Magisk zip to root again
5) Reboot.
Enjoy
So as the official bootloader unlock broadened the audience of this from tinkerers/developers to basically everyone I thought this guide might me helpful for some...
PREREQUISITES:
- Unlocked bootloader (official or unofficial)
- latest magisk manager installed on phone (https://github.com/topjohnwu/Magisk/releases)
- latest fastboot and adb binaries from google(https://developer.android.com/studio/releases/platform-tools)
- latest twrp.img to boot (NOT FLASH), zip not needed (https://eu.dl.twrp.me/NB1/)
- Fully stock partitions (if you do not have this reflash latest stock via ostla), as OTA updates will do a integrity check.
- PC with WIN/OSX/LINUX with USB port^^ (on windows you might have to add .exe to the commands)
- disable automatic system updates in developer options, as you will still have to manually root the updated partition, so this makes sure you don't miss it. You still get notifications on available updates and can apply them easily(as you will see)
SETUP_STEPS:
1. Go into Magisk manager and "just download" the latest zip
2.1 Run
Code:
adb reboot bootloader
or reboot into download/fastboot mode via other means
2.2 Run
Code:
fastboot boot twrp-3.2.3-1-NB1.img
(change this when your version of twrp differs)
2.3 Flash the .zip magisk downloaded in 1.)
2.4 Reboot.
Congratulations you now have root!
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
ALTERNATIVE GUIDE (without twrp, using prerooted boot.img)
(works for newest patch level, where twrp isn't working yet)
this guide works on newest patches as long as someone provides a prerooted boot.img.
So basically you either need a boot.img available or twrp...
Hopefully this helps until TWRP is compatible with September Security Patch
LINKS:
stock boot.img: (may to october patches)
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
prerooted boot.img: (may to october patches)
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
PREREQUISITES:
- same as above minus twrp
- patched/prerooted boot image (either create it yourself or use link provided here)
STEPS_TO_ROOT:
0.
Code:
adb reboot bootloader
or get into download mode otherwise
1.
Code:
fastboot boot NB1_prerooted_boot.img
1.1. The phone will boot into an temporarily rooted state,
2. Use magisk manager-> Install -> "Direct Install" to persist the root.
3. Reboot
Congrats you now have root even on versions where twrp isn't working yet....
Edit1:
Added link to all stock boot images from may to october security
Edit2:
Did the same for magisk prerooted
Edit3:
Added November images thanks to @czupyt
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Trissi said:
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Click to expand...
Click to collapse
That would be much appreciated. Alot of people who just unlocked bootloader cant root and the maintainer of our TWRP will take a couple of days
indeed
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
LoaderFabi said:
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
Click to expand...
Click to collapse
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
ironman38102 said:
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
Click to expand...
Click to collapse
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
LoaderFabi said:
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
Click to expand...
Click to collapse
No I get that but its just that I forget cuz this is my first phone with a/b partition. Anyway I got the phone to latest patch rooted so I'll see if I can get the untouched img
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
eric194 said:
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
Click to expand...
Click to collapse
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Trissi said:
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Click to expand...
Click to collapse
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
So did the prerooted Image Boot?
If so it basically has to be your boot/system partition(I had mine compromised too and couldn't fix it with just flashing boot.img had to reflash everything via ostla)
If even the prerooted Image didnt boot im sorry i don't really know how to help, as I have working root with Magisk on September patch and the Image boots just fine for me....
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Trissi said:
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Click to expand...
Click to collapse
Ok I will try that hope it'll work
Edit : thanks dude it worked
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Xayar said:
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Click to expand...
Click to collapse
Flash the full Stock build (i think its even may patch), via ostla (https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487), then follow this guide then reapply all updates by following the update steps...
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Xayar said:
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Click to expand...
Click to collapse
Are you trying to use OST LA 6.1.2? Cuz that doesnt work
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
ozfive said:
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
Click to expand...
Click to collapse
1)Download payload dumper.
2)Extract payload file from rom zip.
3)Put payload file in payload_input folder.
4)Run exe file.
5)After process complete check payload_output folder. All extracted there.
Download payload dumper from here :- https://forum.xda-developers.com/attachment.php?attachmentid=4760222&d=1558078935
Patched boot images are irrelevant and only necessary for devices without a working TWRP recovery. If you want to root, either boot TWRP once or boot and install TWRP (recommended) and then install the magisk zip from there.
larsdennert said:
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
Click to expand...
Click to collapse
How do you extract the boot.img from the phone? I have the tmo version and would like to say on the stock room with root.
Sent from my GM1915 using Tapatalk
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
larsdennert said:
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
Click to expand...
Click to collapse
Not rooted yet, but everything I have read so far is that you need a patched boot.img to root, or you can create one from the boot.img in an oos package with magisk manager. The problem is, there isn't a tmo oos package out there yet, so it looks like rooting the tmo software isn't possible at the moment. Is this correct?
Sent from my SM-T550 using Tapatalk
Is your bootloader unlocked? That would be step one. Read up on the thread for that.
Not yet, but will be....trying to get my research done before I go for it... don't want to mess it up, been a few years since I rooted a phone.
Sent from my GM1915 using Tapatalk
My device Model number: SM-M015G/DS
Build number: QP1A.190711.020.M015GXXU1ATD4
Android security Patch: 1 March 2020
Android version: 10
I want to Root this device.
I read many articles but unable to conclude on final procedure.
Procedure 1
1. Unlock Bootloader -> Done
2. Flash twrp ---> Where can i find the twrp for my device ? Can i flash any twrp with Android 10 ?
3. Install Magisk and root --> I'm not able to install magisk, since twrp is not installed
Procedure 2
1. Unlock Bootloader -> Done
2. Install Magisk without root and create a Magisk patched boot image --> Here magisk(ver 7.5.1) is giving error (Magisk not installed)
3. Root using Magisk --> Failed at step 2.
Can someone please help me with any of the above procedure to root my device ?
I'm not able to find twrp for the this device. OR Get Magisk working without root.
Please please help
dhodidarpan said:
My device Model number: SM-M015G/DS
Build number: QP1A.190711.020.M015GXXU1ATD4
Android security Patch: 1 March 2020
Android version: 10
I want to Root this device.
I read many articles but unable to conclude on final procedure.
Procedure 1
1. Unlock Bootloader -> Done
2. Flash twrp ---> Where can i find the twrp for my device ? Can i flash any twrp with Android 10 ?
3. Install Magisk and root --> I'm not able to install magisk, since twrp is not installed
Procedure 2
1. Unlock Bootloader -> Done
2. Install Magisk without root and create a Magisk patched boot image --> Here magisk(ver 7.5.1) is giving error (Magisk not installed)
3. Root using Magisk --> Failed at step 2.
Can someone please help me with any of the above procedure to root my device ?
I'm not able to find twrp for the this device. OR Get Magisk working without root.
Please please help
Click to expand...
Click to collapse
You can only flash TWRP for your specific model number. If there is not a TWRP for your specific model number, you or someone else will have to make one for your device.
Some devices have to use Magisk to patch the stock recovery.img instead of the boot.img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You can only flash TWRP for your specific model number. If there is not a TWRP for your specific model number, you or someone else will have to make one for your device.
Some devices have to use Magisk to patch the stock recovery.img instead of the boot.img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. I tried using Magisk to patch the stock recovery.img. But I'm facing problems using Magisk app.
Problems like:
1. Magisk app not installed (I had installed Magisk manager version 7.5.1)
2. Install button not popping up on the app
3. Installed Magisk canary builds, but the app getting crashed.
Working with Magisk without root is giving lot of problems.
I am a newbie and not technical enough to create my own twrp image. Can you help me with any procedure to create the twrp image ?
twrp recovery image required for SM-M015G/DS
Can someone please provide me twrp image for this phone. Please.
My device Model number: SM-M015G/DS
Build number: QP1A.190711.020.M015GXXU1ATD4
Android security Patch: 1 March 2020
Android version: 10
Use this method my friend
https://www.full-repair-firmware.com/2020/10/how-to-root-m015g.html
dhodidarpan said:
My device Model number: SM-M015G/DS
Build number: QP1A.190711.020.M015GXXU1ATD4
Android security Patch: 1 March 2020
Android version: 10
I want to Root this device.
I read many articles but unable to conclude on final procedure.
Procedure 1
1. Unlock Bootloader -> Done
2. Flash twrp ---> Where can i find the twrp for my device ? Can i flash any twrp with Android 10 ?
3. Install Magisk and root --> I'm not able to install magisk, since twrp is not installed
Procedure 2
1. Unlock Bootloader -> Done
2. Install Magisk without root and create a Magisk patched boot image --> Here magisk(ver 7.5.1) is giving error (Magisk not installed)
3. Root using Magisk --> Failed at step 2.
Can someone please help me with any of the above procedure to root my device ?
I'm not able to find twrp for the this device. OR Get Magisk working without root.
Please please help
Click to expand...
Click to collapse
My phone is same,i didnt face any probl
There are few things before flashing or making a .tar file from magisk
1st Download stock rom of your country specific
2nd Extract zip file ,
3rd Download magisk in ur non rooted device and select AP file ,it will create .tar file
3rd Download odin in pc(latest stable version)
4th flash your stock rom(i assume u know basic,like unlocked bootlader)
5th After odin has passed it,go to developer option and on usb debugging(most people forgets to on it after 1st flash)
6th flash ur .tar file in ap section along with other section
7th Any error? Post a image of it
So, I rooted my phone, for which I needed to unlock the bootloader and install TWRP. Now, when I want to install an update on my phone, it downloads and when I want to install it, it jumps to TWRP recovery instead of the phone's recovery, so I can't update my phone. Does anyone know how can I install the updates from TWRP?
Else, reinstall the default recovery. (Only the recovery, not the entire OS since that would un-root my phone)
Thanks.
Edit: After it boots to TWRP, it apparently tries to install the update, since I can see it on the log, but when I reboot my phone it has not installed. It errors: "E3994: This package is for "2169B" devices; this is a "". Updater process ended with ERROR: 1. Error installing zip file '/data/ota_package/OTA/.otaPackage/my_manifest_RMX3370_11.F.04_3040_202302282047.44.36402b59_all.zip'
Edit 2: After failing to install it, it prompts me to re-download it and re-install it, but it jumped from ~500MB update to 4.76GB update.
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
SanOne+1 said:
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
Click to expand...
Click to collapse
Your guide is incorrect and will definitely put the device into bootloop.
** The twrp link that you shared doesn't allow system updates to install, it is just a A13 compatable twrp recovery.
1) What if that person has not created any twrp backup of all system partitions? According to his explanation, I'm pretty sure he has not created any backup of the partitions.
2) only flashing recovery image and installing the update will again put the device into bootloop because as confirmed by the OP that his device is rooted and due to root the boot image of the device gets modified so it will put the device into bootloop.
3) unless the OP has stock boot and recovery images at his disposal he should not attempt to install the update to avoid bootloop.
** Kindly avoid sharing incorrect information you aren't sure about the correct procedure.
procedure that I follow to flash updates :
1) in magisk - uninstall magisk - restore images
2) boot device into bootloader and flash stock boot and recovery.
3) boot device and install update.
4) put device again in bootloader and flash twrp and within twrp flash magisk and reboot.
I haven't found any easier way than this. If anyone has, kindly put it below.
There's a way
Rui 4.0 Android 13 f.02
So, any verdict on this new update for the people that did update to it?
forum.xda-developers.com
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Xemi_KryTeT.pl said:
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Click to expand...
Click to collapse
Which rom r u running and is it good?
Sabirsayed09 said:
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Which rom r u running and is it good?
Click to expand...
Click to collapse
Latest stock (4.0), I'm not going to flash custom roms for now