Related
Hi, I rooted my a9 back in May right around when 6.0.1 came out. Long story short, my device just gave up the ghost after a nasty interaction between the screen and concrete, so now I have a new device being shipped tomorrow. I figured the first thing I'll do is let it run any updates / OTAs it might have to get it up to date then attempt to root again.
I've been looking around for the past several hours trying to determine what the correct rooting method might be now given Nougat's rollout, but I haven't come across anything truly definitive yet. If anyone could enlighten me on what I'll need to do now to root this new version I'd be very appreciative.
Thanks in advance guys!
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
txag2011 said:
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
Click to expand...
Click to collapse
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
JohnRogers23 said:
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
Click to expand...
Click to collapse
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
I'm about to start the process trying to root using the above methods.. I'll post again when I have results.
txag2011 said:
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
Click to expand...
Click to collapse
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
JohnRogers23 said:
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
Click to expand...
Click to collapse
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
txag2011 said:
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
Click to expand...
Click to collapse
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
JohnRogers23 said:
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
txag2011 said:
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
Click to expand...
Click to collapse
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
JohnRogers23 said:
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
Click to expand...
Click to collapse
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
txag2011 said:
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
Click to expand...
Click to collapse
I'm glad you got it working. Strange you had to flash phh's Su separately though. Anyway, glad I could help.
Well Working !
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Click to expand...
Click to collapse
Thanks! I got it more or less and went with magisk. Couldn't pass up a chance to have root and still get OTAs and use android pay. I'm still monkeying around trying to figure out how to use it to get liveboot back up and running.
Problem: After a standard update(flash bootloader & radio, then update image) and standard rooting process(boot twrp, flash supersu), the device will keep rebooting
Possible reason: the latest bootloader(8996-012001-1703151359) may verify the system image in the phone to ensure it unchanged
Solution: after installing supersu in TWRP, flash the previous bootloader(8996-012001-1702151126) back and the device will start normally
If we sideload the ota and then flash old bootloader works?
Or we need to flash the entire factory image?
TENN3R said:
If we sideload the ota and then flash old bootloader works?
Or we need to flash the entire factory image?
Click to expand...
Click to collapse
Just old bootloader afterwards
Great, works for me.
Can you post specific instructions I really would like to unlock and root my phone
Any side effect of using old bootloader? Thank you.
[email protected] said:
Can you post specific instructions I really would like to unlock and root my phone
Click to expand...
Click to collapse
In fact, there are a lot of articles teaching you that.
For example, you can click here to know how to root.
vibranze said:
Any side effect of using old bootloader? Thank you.
Click to expand...
Click to collapse
No more side effects than not verifying the system image found yet.
Steven_Yang said:
Problem: After a standard update(flash bootloader & radio, then update image) and standard rooting process(boot twrp, flash supersu), the device will keep rebooting
Possible reason: the latest bootloader(8996-012001-1703151359) may verify the system image in the phone to ensure it unchanged
Solution: after installing supersu in TWRP, flash the previous bootloader(8996-012001-1702151126) back and the device will start normally
Click to expand...
Click to collapse
THANK YOU!! i have the bootloop issue that was driving me crazy and was unable to root properly, until i flashed the old bootloader
Read here. There is a fix that does not require downgrading the BL.
https://forum.xda-developers.com/showthread.php?t=3600606
Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.
Megin said:
Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.
Click to expand...
Click to collapse
Search the forum, there are a lot of walk through threads.
You won't remove anything, IE Magik.
Download the Factory Image, OTA will not work.
You'll remove "-w" from one file to not wipe data.
Flash update.
Reroot with Magisk.
If you have problems finding the links or threads, I can link them.
Sent from my Pixel 2 using Tapatalk
What diesel said, it isn't really that hard ?.
Nathanchanche made a really good guide for us. Take your time to read it really well and you should be able to solve your problem.
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.
pgarlinski said:
In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.
Click to expand...
Click to collapse
Ok what am I doing wrong here? prntscr.com/iqefpd
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
You need to install fastboot. Download plataform tools from the Android SDK and try again.
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
Follow the full tutorial in my signature, it will cover all the steps in detail.
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
As said previously you need fastboot.exe. Download from https://dl.google.com/android/repository/platform-tools-latest-windows.zip.
Extract everything to folder that contains your extracted image. If the fastboot.exe is still not recognized:
one option is to modify flash-all.bat line: PATH=%PATH%;"%SYSTEMROOT%\System32"; to PATH=%PATH%;"%SYSTEMROOT%\System32";"%cd%"
Telperion said:
Follow the full tutorial in my signature, it will cover all the steps in detail.
Click to expand...
Click to collapse
Worked!! Thanks
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
madhattr999 said:
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
Click to expand...
Click to collapse
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
For your other questions, if you extract the factory image you'll find another zip file in there. That's were the image files are and you need to extract that zip. And, ota's are cumulative so you don't need install previous ones. But specifically to the boot image, a previous months boot image may or may not be the same as the current one, etc.
jd1639 said:
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
Click to expand...
Click to collapse
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Devices with A/B Partitions
Due to the fact that these devices have two separate partitions, it is possible to have the OTA installed to the inactive slot and have Magisk Manager to install Magisk onto the updated partition. The out-of-the-box OTA installation works seamlessly and Magisk can be preserved after the installation.
After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Update).
Wait for the installation to be fully done (both step 1 and step 2 of the OTA), do not press the restart button!! Instead, go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk to the slot that the OTA engine just updated.
After installation is done, press the reboot button in Magisk Manager. Under-the-hood Magisk Manager forces your device to switch to the updated slot, bypassing any possible post-OTA verifications.
After the reboot, your device should be fully updated, and most importantly, Magisk is still installed to the updated system!
Click to expand...
Click to collapse
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
jd1639 said:
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
Click to expand...
Click to collapse
Thanks, I'll back up my files and try that.
Well, as far as I know twrp backups only work for data (with verity and all that). Always bootloop on a vendor or system restore. Back up your data a million times and go for it. Worse thing that happens is back to zero. Wait, you said no computer? Well, put it on a free cloud saving service, have your data backed up out there. Not advertizing for any service in particular, but backing up data is something everyone should be thinking about.
I am about to go for broke on this device for the 4th time. Non boot several times, flashing, flashing, building, flashing. I have the added benefit of figuring out if cell service works as the vendor.img always breaks it. Good times mate.
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
fronten said:
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
Click to expand...
Click to collapse
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Badger50 said:
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Click to expand...
Click to collapse
But the person above you said he was able to do it on both recent updates...
madhattr999 said:
But the person above you said he was able to do it on both recent updates...
Click to expand...
Click to collapse
He doesn't have twrp and if you do have twrp the ota won't work for sure. So you're welcome to try if you're only rooted, no twrp. But patching the boot image and installing it from magisk hasn't worked, but maybe it does now. Let us know.
dracushor87 said:
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
Click to expand...
Click to collapse
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
madhattr999 said:
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
Click to expand...
Click to collapse
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
timg11 said:
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
Click to expand...
Click to collapse
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
dracushor87 said:
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
Click to expand...
Click to collapse
Used this method after the May update finally arrived for me yesterday. Backed up everything just in case, but it worked flawlessly.
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom .
Downloads
S5_Root_Tools_2023.7z
EMMC_15_Rom.zip -- Stock QL1 6.0
Directions For Unlocking Stock Phone
I would recommend Windows defender is turned of before starting
1. Download S5_Root_Tools_2023.7z and unzip
2. Make sure Usb debugging is enabled on your phone
3. Plug in phone and run Safestrap.exe and follow directions on command window
4. This process is pretty much 1 click all automatic except following command window prompts
5. This will detect if your phone is EMMC 11 or 15
6. If it detects EMMC 15 it will automatically unlock your bootloaders.
7. Once process is done reboot too twrp and flash rom of choice or use provide one and flash root zip of choice
Regular Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk Delta
Releases · HuskyDG/magisk-files
Contribute to HuskyDG/magisk-files development by creating an account on GitHub.
github.com
ETFSU
EFTSU Root Solutions
The Largest Database for the Root Solutions on the Internet
eftsu.com
Safteynet Fix Module
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Old Method And Old Downloads
EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip -- Rom Zip
EMMC_11_S5_Root_Tools_2022_V7.7z
-- Files Needed To Root Phone
Instructions To Root And Install Safestrap
**If you already have safestrap installed you can skip to Instructions To Unlock Bootloader
**If you are already rooted but do not have safestrap installed download View attachment S5_Safestrap.apk install then skip to Instructions To Unlock Bootloader**
Directions
1. Download both files and unzip EMMC_15_And_11_S5_Root_Tools_2022_V7.7z
2. Reboot phone too Download Mode by holding Power+VolDwn+HomeButton as phone starts up
3. Plug phone into computer and open the Odin provided in the above file in the Odin_Folder
4. In Odin Choose BL slot and choose the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 Located in the Odin_Folder
5. Flash the file using provided Odin let phone reboot. This will wipe your phone
6. Once phone is rebooted make sure its plugged into computer and phone use recognized by computer
7. Run the Install_One_Click.cmd this should install safestrap. If this method fails countinue with below methods.
8. If above method fails you can reboot and try again or run the Manual_Install_Root_Apps.cmd and try below methods to root
Towel Root Method
These steps are only needed if above root method failed
1. You need too be connected to a network. Try one of towel root apps and if not successful then try the other one. If it doesn't work go to King root section
2. If towel root succeeds then run the click on the super su app and choose to update su binary and choose normal once successfully updated reboot phone
King Root Method
These steps are only needed if towel root failed
1. You will need to be connected to a network. Click on King root app then click try root
2. Once root is successful don't click on the optimize and close the king root app.
3, Run the Manual_Install_SuperSu.cmd
Installing Safestrap
9. This only needs to be done if 1Click bat method failed. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
10. Busybox must be installed ifirst if you used towelroot method too root
Instructions To Unlock Bootloader
11. Enter safestrap now in safetrap it will ask you to swipe to allow modding system make sure to do this now . If you have not copied the EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip from the EMMC_15_Bootloader_Unlock_Zip folder do so now Click install tab and choose EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip and install.
12. When done phone will power off.
13. Reboot phone to recovery you should now have TWRP recovery installed and the choose wipe the advanced wipe and wipe data only then reboot
14. Phone will reboot and stick on red Verizon screen for probably 15 to 20 min be patient. When finally booted you will have an unlocked bootloader with TWRP recovery running a Deodexed Rooted QL1 stock MM 6.0 Rom Rooted with EFTSU with root hide and safetynet pass module
Disabling Reactivation Lock
Thanks bbsc
1. Follow above directions too obtain safestrap and root
2. Download and flash EMMC_11_NCG_KK_Safestrap_Full.zip in safestrap then wipe data
This has Samsung Setup Wizard removed so you can get through setup
3. Set up a wireless connection or use your SIM-card and internet connection from your provider.
4. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Accept too update app then allow google check when it ask
5. Login to your new account and you will be able to untick Reactivation Lock.
6. When it unticked, Navigate to Settings - Backup Reset - Factory data Reset.
7. Phone will reboot too stock recovery and wipe data and remove current samsung account and you are good too go.
8. Now proceed with unlocking bootloader step 11 you have to enter safestrap from the safestrap splash screen on bootup its not installed as a recovery image because stock recovery is needed
Credits
beaups Sourcecode and tool
ryanbg
haggertk For his CID
autonomousperson For compiling the source to a app
magic_man185 For compiling the source
GeTex
klabit87 - Basically Everything
@GSMCHEN Lots of stuff
elliwigy Lots of stuff
afaneh92 -Safestrap and too much too mention
Sourcecode
https://github.com/beaups/SamsungCID
Instructions for downgrading or updating bootloaders can be found here
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
jrkruse said:
mine
Click to expand...
Click to collapse
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms
stang5litre said:
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms
Click to expand...
Click to collapse
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
@jrkruse awesome job...!! :good:You definitely must be bored... Lol. May try that on an old one for craps and giggles... Lol. Again, awesome to bring a lil history back to life... :good:
jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
Nice job man, much appreciated.
If you ever get bored try to make a pre-rooted rom/safestrap recovery (course no bootloader unlock) for the G930U/G935U with the latest firmware UUESACSI1 (Aug 27 2019), since it looks like Samsung has stopped updating this phone, or better yet a root-patcher for a stock sytem.img like you did for the G950/N950. I have uploaded the latest eng-boot vA/10 here: https://forum.xda-developers.com/sho...postcount=1826
jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.
googlephoneFKLenAsh said:
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve...ent/vzwemmc15chipset-dev-bl-unlocked-t4010757
Sent from some device I modified
the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?
bigstack said:
the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?
Click to expand...
Click to collapse
What are you extracting it with?
Sent from some device I modified
First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?
Remedy1230 said:
First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?
Click to expand...
Click to collapse
Its really no easy process to flash an international rom if you are using Verizon then data will probably not work with out some editing. You can always try it but Verizon will probably need Verizon csc stuff to work and build.prop edits.
Sent from some device I modified
Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?
SaltedSand said:
Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?
Click to expand...
Click to collapse
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified
jrkruse said:
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified
Click to expand...
Click to collapse
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but needs device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified
al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Yeah that's what I have in mind.
jrkruse said:
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified
Click to expand...
Click to collapse
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.
SaltedSand said:
Yeah that's what I have in mind.
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.
Click to expand...
Click to collapse
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified
jrkruse said:
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified
Click to expand...
Click to collapse
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.
SaltedSand said:
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.
Click to expand...
Click to collapse
If you stop at 12 you will just have king root and some apps work with kingroot but some do not
Sent from some device I modified