Step 1: Download this: http://downloads.codefi.re/savoca/root/titan
Step 2: fastboot flash boot xt1064_lollipop_boot.img
Step 3: Flash SuperSU
http://imgur.com/jJO86tC
Unlocked boot-loader needed right?
surenzxx said:
Unlocked boot-loader needed right?
Click to expand...
Click to collapse
Of course.
savoca said:
Of course.
Click to expand...
Click to collapse
Do you know if any custom recoveries work on Lollipop at the moment?
surenzxx said:
Do you know if any custom recoveries work on Lollipop at the moment?
Click to expand...
Click to collapse
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.
Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
EDIT: Nevermind; sorry for the mistake. It's booting back up.
surenzxx said:
Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
Click to expand...
Click to collapse
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.
savoca said:
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.
Click to expand...
Click to collapse
Thanks for your help. So we just flash the .img, flash SuperSu from the site, and fastboot flash recovery? Thanks again.
EDIT: Uh, I'm not booting past the unlocked bootloader screen after flashing your .img.
EDIT 2: I'm just a person that worries a lot. Gave it a few minutes to load and it works. Thanks. Really sorry to discredit you.
EDIT 3: Thanks man.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't seem to get root, I flash superSu after the boot img but still no root
edit: nevermind I figured it out thanks!
Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app
Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz
savoca said:
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.
Click to expand...
Click to collapse
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."
who_ohw said:
Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app
Click to expand...
Click to collapse
All I did allow the su daemon to init from the ramdisk - similar to how custom ROMs implement this.
luckiesjohnny said:
Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz
Click to expand...
Click to collapse
fathergweedo said:
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."
Click to expand...
Click to collapse
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L
Thanks a lot.
I've tried it already with 2.19 and it worked fine.
savoca said:
All I did allow the su daemon to init from the ramdisk - similar to
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L
Click to expand...
Click to collapse
Gracias. Will get it later today...
ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?
Bobboman said:
ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?
Click to expand...
Click to collapse
If you're talking about the line in the bootloader, just ignore it. Your recovery still flashed.
yea i figured that out...however now i can't even boot my moto g to anything but the bootloader
thank god i have the 4.4.4 stock files on my laptop, time to get flashing...anyone got a link to the most recent version of supersu?
Will this work on XT1063 variant, or will it require a separate kernel patch?
blah i think i bricked my phone, i cant get past the moto logo, but i can get into the bootloader, not that helps anything
Related
Hi all
I have phone Galaxy Nexus and I am having trouble updating ota where it after receiving the update must be recovery is stock and when I tried to retrieve recovery (With Galaxy Nexus ToolKit) does not work with me and show this is Death robot. I've access to Root and Recovery before ( CWM ) and Bootloader is open & I have a Custom Kernel
NOw How To Retrieval The stock recovery ??
sorry for my English
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ahmedsaber20005 said:
Hi all
I have phone Galaxy Nexus and I am having trouble updating ota where it after receiving the update must be recovery is stock and when I tried to retrieve recovery (With Galaxy Nexus ToolKit) does not work with me and show this is Death robot. I've access to Root and Recovery before ( CWM ) and Bootloader is open & I have a Custom Kernel
NOw How To Retrieval The stock recovery ??
sorry for my English
Click to expand...
Click to collapse
Manually flash the latest factory image, job done!
EddyOS said:
Manually flash the latest factory image, job done!
Click to expand...
Click to collapse
This is not a logical solution every time issue a new version of Android will be forced to do so and I have to take copies of the software, games and music and then restored again!!
What is the main reason for this problem?? And what is the solution
ahmedsaber20005 said:
This is not a logical solution every time issue a new version of Android will be forced to do so and I have to take copies of the software, games and music and then restored again!!
Click to expand...
Click to collapse
True, but it's always worth making a backup with Titanium to restore if required. That or make sure you keep the stock recovery after each build is released
EddyOS said:
True, but it's always worth making a backup with Titanium to restore if required. That or make sure you keep the stock recovery after each build is released
Click to expand...
Click to collapse
I always do that, but sometimes we need cwm formal and sometimes I need to air updates
4 Up
that is the stock recovery. something else on your phone is not stock and therefore it is failing.
ahmedsaber20005 said:
4 Up
Click to expand...
Click to collapse
1. Don't bump threads
2. Have you edited/deleted any system files? If so, there's your issue
EddyOS said:
1. Don't bump threads
2. Have you edited/deleted any system files? If so, there's your issue
Click to expand...
Click to collapse
No just root
Zepius said:
that is the stock recovery. something else on your phone is not stock and therefore it is failing.
Click to expand...
Click to collapse
I am have root&unlock bootloder&custom kernel+Busy box
That all
ahmedsaber20005 said:
I am have root&unlock bootloder&custom kernel+Busy box
That all
Click to expand...
Click to collapse
you have a custom kernel and busy box. those 2 things modify system files.
YOU ARE NOT ON A STOCK ROM.
the ota will never work until you return those things to stock (good luck finding all the things busy box changes.)
Zepius said:
you have a custom kernel and busy box. those 2 things modify system files.
YOU ARE NOT ON A STOCK ROM.
the ota will never work until you return those things to stock (good luck finding all the things busy box changes.)
Click to expand...
Click to collapse
If I uninstall this kernel and basybox and flash the stock recovery wiil be working ? Or I should to flash a new factory image?
ahmedsaber20005 said:
If I uninstall this kernel and basybox and flash the stock recovery wiil be working ? Or I should to flash a new factory image?
Click to expand...
Click to collapse
Just flash a system image, so simple
flash the factory images is the best. busybox is known to update system files and just uninstalling it will not revert the changes.
Thanks All For Help me put I have a little questions
1-Does Root Make Errors With OTA ?
2- If I want to flash image factory with Odin or toolkit?
3-If I install custom recovery and I want to back to stock can I do this with toolkit or other?
Thanks
1. Yes
2. Neither - learn to do it manually
3. Flash manually using the stock recovery in the factory image
EddyOS said:
1. Yes
2. Neither - learn to do it manually
3. Flash manually using the stock recovery in the factory image
Click to expand...
Click to collapse
Is there a way combines the powers of Root and ota Together ?? Will the program help on that?
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
No, that only masks root so some apps can run. It won't make any difference to the phone with regards to OTAs. Basically, if you're going to unlock the phone just go custom and ignore OTAs
EddyOS said:
No, that only masks root so some apps can run. It won't make any difference to the phone with regards to OTAs. Basically, if you're going to unlock the phone just go custom and ignore OTAs
Click to expand...
Click to collapse
please dont spread mis-information.
root alone does not stop you from getting OTAs, as i have root and nothing else and get OTAs just fine and they install just fine.. root does allow you to modify system files which can cause OTAs to fail.
what you did mention about rootkeeper is correct. it just masks root to allow certain apps to run and allow a easy way to return root after an OTA.
Just purchased and received Note 10.1 2014 edition.
Model # SM-P605V
Andriod Version 4.3
Baseband Version P605VVRUANB1
Build number JSS15J.P605VVRUANB1
Hardware Version P605V.02
Would love to Root (if possible). Having a difficult time finding instructions and a working method though. I think the Chainfire method was for older OS versions. I did try the CF method and all I get is Error messages in ODIN and on the Tablet itself. (ODIN shows: <ID:0/008> FAIL! (Auth) and the Tablet shows: secure magiccode check fail : recovery )
Is there a method out there yet for P605 with 4.3?
Please note that I have searched these forums high and low and still haven't seen a valid method to get my Note Rooted!
WorldOfJohnboy said:
Just purchased and received Note 10.1 2014 edition.
Model # SM-P605V
Andriod Version 4.3
Baseband Version P605VVRUANB1
Build number JSS15J.P605VVRUANB1
Hardware Version P605V.02
Would love to Root (if possible). Having a difficult time finding instructions and a working method though. I think the Chainfire method was for older OS versions. I did try the CF method and all I get is Error messages in ODIN and on the Tablet itself. (ODIN shows: <ID:0/008> FAIL! (Auth) and the Tablet shows: secure magiccode check fail : recovery )
Is there a method out there yet for P605 with 4.3?
Please note that I have searched these forums high and low and still haven't seen a valid method to get my Note Rooted!
Click to expand...
Click to collapse
BTW, the CF AutoRoot I tried is located here: http://download.chainfire.eu/380/CF-Root/CF-Auto-Root/CF-Auto-Root-lt03lte-lt03ltexx-smp605.zip
Try this it worked on p607
http://forum.xda-developers.com/showpost.php?p=53140560&postcount=12
NexVision said:
Try this it worked on p607
http://forum.xda-developers.com/showpost.php?p=53140560&postcount=12
Click to expand...
Click to collapse
Thanks, but I'm a bit worried about bricking... would rather have/see a "How To" specific to the P605V.
Sooo... nothing? My tablet is now asking to do an OTA and I don't want to do it if there is still a working method for my current firmware.
WorldOfJohnboy said:
Thanks, but I'm a bit worried about bricking... would rather have/see a "How To" specific to the P605V.
Click to expand...
Click to collapse
As long as you don't touch the bootloader, you're safe from bricking your tablet. You can always flash back the stock rom with Odin in auto download mode. Try to install TWRP recovery first, once it's working just flash supersu and your tablet is rooted.
AkiraBBQ said:
As long as you don't touch the bootloader, you're safe from bricking your tablet. You can always flash back the stock rom with Odin in auto download mode. Try to install TWRP recovery first, once it's working just flash supersu and your tablet is rooted.
Click to expand...
Click to collapse
OK, a couple of dumb questions:
1) To flash recovery, would I download the Zip file, go into Download Mode and use ODIN to flash?
2) If something did go awry, would I need to Download the firmware from SamMobile site, could I just use Kies, and finally, would it factory reset my tablet?
Just want to make sure I do it right and that I know the consequences if it goes bad. Thanks in advance.
1. Yes
2. It would (will) just fail. No need to do anything. Just reset. No it didn't reset your tablet.
Our bootloader is locked. I tried and failed. But give it a shot... it was an older version of Odin
Sent from my SM-N900P using Tapatalk
OK, so I see a few posts HERE that people are able to root using De La Vega. I think I may give it a whirl tomorrow and report my status after all is done. (Side note: Seems crazy to me that no one has created a DLV firmware package for the P605 and posted it so others can just flash via ODIN and finish the rest of the process.
WorldOfJohnboy said:
OK, so I see a few posts HERE that people are able to root using De La Vega. I think I may give it a whirl tomorrow and report my status after all is done. (Side note: Seems crazy to me that no one has created a DLV firmware package for the P605 and posted it so others can just flash via ODIN and finish the rest of the process.
Click to expand...
Click to collapse
Just wondering if you rooted your device? If not you could use Towelroot and it should works on 4.4 kk also without tripping Knox counter, good luck!
Sent from my Galaxy Nexus using Tapatalk
buhohitr said:
Just wondering if you rooted your device? If not you could use Towelroot and it should works on 4.4 kk also without tripping Knox counter, good luck!
Click to expand...
Click to collapse
Well, tried De La Vega root and it didn't work (everything up to and including the ODIN step worked, then it failed).
Downloaded Towelroot, ran it, and it worked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BTW, Knox is is still 0x0!
I can second that towel root worked on my 605v.
Sent from my LG-VS980 using Tapatalk
mllacey said:
I can second that towel root worked on my 605v.
Click to expand...
Click to collapse
I assume that (from your signature), it works on the 4.4.2 firmware as well as 4.3 (which is what I have)?
EDIT: Nevermind, I flashed 4.4.2 via ODIN and re-ran Towelroot and all is well. Now if I could only figure out how to update the binaries with a locked bootloader/stock recovery...
WorldOfJohnboy said:
I assume that (from your signature), it works on the 4.4.2 firmware as well as 4.3 (which is what I have)?
EDIT: Nevermind, I flashed 4.4.2 via ODIN and re-ran Towelroot and all is well. Now if I could only figure out how to update the binaries with a locked bootloader/stock recovery...
Click to expand...
Click to collapse
Well, all is good now! Here's what I did:
Flashed stock 4.2.2 ROM from Sammobile
Ran Towelroot
Downloaded latest SuperSU zip from Chainfire
Extracted superuser.apk and installed
When prompted to update binaries, chose to update using normal (non-recovery) method and it succeeded.
I'm glad that worked out.
Now I'm looking to figure out to load a customer recovery aka TWRP.
Sent from my SM-P605V using Tapatalk
Thanks guys... Been waiting for this.
+1 that it works
Hi. I have just rooted my Pixel 2 XL with Magisk after reading the guides here on XDA. This is my first Android phone and my first time rooting so I'm trying to figure out the update situation here. How would I go about installing version 8.1 when I get the OTA update for it? Would I have to wipe my device again and reinstall Magisk?
On a side note, does anyone know if MinMinGuard on systemless Xposed breaks SafetyNet?
Thanks in advance.
Unroot, apply OTA, re-root.
I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Can you install OTA with unlocked bootloader?
dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Thanks. Would this remove all of my data?
darkfire404 said:
Thanks. Would this remove all of my data?
Click to expand...
Click to collapse
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk
dyingearth said:
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk
Click to expand...
Click to collapse
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nitin
turboencab said:
I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Did it work?
Cowbell_Guy said:
Did it work?
Click to expand...
Click to collapse
I don't know, I got impatient and sideloaded the OTA. I essentially followed the procedure listed by dyingearth in post #6 above.
Just went to do this but Magisk says Stock Backup Doesn't Exist... I didn't delete anything, anyone know why this would happen? And now the question is... How do I go about getting an update with forking my phone? I don't mind freshly doing it all over from scratch, but would like to get Magisk to backup the stock stuff so that when I follow the OTA instrustions on the Magisk link tips it would work.
OTA
I'm on rooted Pixel XL 2 already on 8.1, can I take the security patch, or do I need to unroot before taking the update?
nitin.chobhe said:
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
Nitin
Click to expand...
Click to collapse
Bump
Following.
My 2xl unrooted today. On it's own. Went to break around 3 and had magisk notification about installing 15.3zip which I was already on. Looked in manager and it showed not installed. Have been reading yesterday about updating while rooted. Checked system update and shows available update today. So I tried to install but failed. Looks like I'll have to wait till after work....at 7pm!!
After taking ota update with magisk installed did not reboot through Magisk so I lost root. Magisk is still on phone but not installed. How to reinstall? Do I need to reflash or can I just hit install on app? Will gladly provide more info aas needed. I have searched and did not find a exact answer to my problem. Build number pq3a.190801.002
You need to sideload ota manually for updates
prot- said:
You need to sideload ota manually for updates
Click to expand...
Click to collapse
I can't figure out how it took the ota in the first place with no errors. I found the guide on how to do the ota with it installed but after i got the ota. When I open the Magisk it says i can install Magisk and Magisk Manager from the app. Im worried it will mess something up.
The quickest and simplest way to update your phone monthly:
- download the stock taimen image for current month
- unzip and edit the 'flash-all.bat' file by removing/deleting the '-w' from the code. Removing the '-w' ensures that your data is NOT wiped
- boot into bootloader and run the 'flash-all' script from your adb folder
- after it completes the update, let the phone boot into Android
- restart and boot into TWRP. Note: decryption is broken for some people (like me), you will need to remove your PIN code before booting into TWRP
- flash Magisk 19.3 or whatever you prefer (and any additional apps you such as Vanced YouTube, etc.)
- Reboot into rooted phone
- Add your PIN code (or whatever security measure you want to use)
If you need a more detailed information, please check the main rooting thread.
OP follow this exactly, and you will have no problems. https://forum.xda-developers.com/showpost.php?p=80039116&postcount=778
This is the Zenfone 6's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
getting the ZF6 next week, can I use this tool to install twrp and magisk and root in the current android version? from searching it seems to be android 10.
cwucwzz said:
getting the ZF6 next week, can I use this tool to install twrp and magisk and root in the current android version? from searching it seems to be android 10.
Click to expand...
Click to collapse
Yes you can
playing around with the app until i get the phone, but what steps would you take with the all in one tool to rooting the phone assuming the bootloader is unlocked?
cwucwzz said:
playing around with the app until i get the phone, but what steps would you take with the all in one tool to rooting the phone assuming the bootloader is unlocked?
Click to expand...
Click to collapse
Just click on "Recovery Flasher and Device Rooter", choose the TWRP (there is one for pie and one for Q), check "And Root it", choose a magisk version and start the procedure, the tool will automatically download the twrp, boot it, flash it and then will flash also magisk
Is this thing able to unlock the bootloader without using the ASUS method? Or lock it? That's what I'm most interested in.
admirdante said:
Is this thing able to unlock the bootloader without using the ASUS method? Or lock it? That's what I'm most interested in.
Click to expand...
Click to collapse
The unlock function can't be done with the tool for zenfone 6, the lock option i don't know if it will work or not, it's the only thing not tested
speaking of unlocking bootloader. is there any difference between the 2 methods explained in this link? cyano//removethis//genmods.org/how-to-unlock-asus-zenfone-6-bootloader
I would be VERY cautious trying to re-lock the bootloader with this tool.
If a guinea pig tester wants to give it a go and report back though, feel free to take that risk
All other functions will most likely work as expected.
It's also worth noting before anyone asks, the Trojan:Win32/Spursint.Q!cl (or similar) virus detected within the .zip is almost certainly false.
As always though, you use these sort of apps at your own risk.
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
molex329 said:
speaking of unlocking bootloader. is there any difference between the 2 methods explained in this link? cyano//removethis//genmods.org/how-to-unlock-asus-zenfone-6-bootloader
Click to expand...
Click to collapse
As far as I am aware there is only one way to unlock the bootloader, and that is to use the official tool from ASUS:
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
NOTE: Unlocking your bootloader will void your warranty.
Hello, has anyone tried this tool to root latest WW version (android 10)? Once rooted, would OTA updates work?
Jorgepfm said:
Hello, has anyone tried this tool to root latest WW version (android 10)? Once rooted, would OTA updates work?
Click to expand...
Click to collapse
Once the bootloader is unlocked you will no longer get OTA automatically. You can still download them manually to the root of your internal memory and install them.
mauronofrio said:
Just click on "Recovery Flasher and Device Rooter", choose the TWRP (there is one for pie and one for Q), check "And Root it", choose a magisk version and start the procedure, the tool will automatically download the twrp, boot it, flash it and then will flash also magisk
Click to expand...
Click to collapse
Is this still working for zenfone 6?
vernj123 said:
Is this still working for zenfone 6?
Click to expand...
Click to collapse
Yes
OK that's good news. Just putting out there but a nice little YouTube overview instructional video would be cool. In any case Thank you.
isthisadagger said:
Once the bootloader is unlocked you will no longer get OTA automatically. You can still download them manually to the root of your internal memory and install them.
Click to expand...
Click to collapse
Install manully will work even if the phone is rooted and twrp install on it?
Sent from my ASUS_I01WD using Tapatalk
baster72 said:
Install manully will work even if the phone is rooted and twrp install on it?
Sent from my ASUS_I01WD using Tapatalk
Click to expand...
Click to collapse
Yes
Can you help me a little as I can not do it, so what I am doing wrong ? - trying to install TWRP (chosen preoption Adroid Q from context) and Magisk 20.3 (for the lastest WW_17.1810.1911.110, Android 10)
Administrator: Flashing TWRP fails: Booting TWRP .... sending boot.img (22040 kb), Booting, Finished . Total time:: 10.902s and then waiting the TWRP boots .... but nothing happens
Jaripi said:
Can you help me a little as I can not do it, so what I am doing wrong ? - trying to install TWRP (chosen preoption Adroid Q from context) and Magisk 20.3 (for the lastest WW_17.1810.1911.110, Android 10)
Administrator: Flashing TWRP fails: Booting TWRP .... sending boot.img (22040 kb), Booting, Finished . Total time:: 10.902s and then waiting the TWRP boots .... but nothing happens
Click to expand...
Click to collapse
which rom you have actually? your bootloader is unlocked?
mauronofrio said:
which rom you have actually? your bootloader is unlocked?
Click to expand...
Click to collapse
The lastest stock, WW_17.1810.1911.110, Android 10. Bootloader is unlocked.
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
It works now, using MANUAL MODE and your unofficial TWRP - TWRP 3.3.1-24 Zenfone 6 (I01WD) by mauronofrio, thanks. Well, preoption Android Q (from context) and official TWRP did not work ...
Hi everyone,
For those who need the boot image to root their oneplus 8pro global rom Oxygen OS 11.0.5.5.IN11AA.
I had a problem to update from rooted version 11.0.4.4.IN11AA to 11.0.5.5.IN11AA. I backed up all my files and used the MSM tool restore program to version 11.0.4.4.IN11AA then updated to version 11.0.5.5.IN11AA without encountering any error.
then I extracted the boot image to successfully root my 8pro.
GoogleDrive img link :
https://drive.google.com/drive/folders/1YdiopRnGCkx4lTuI0TMursEAVOjw85nh?usp=sharing
OnePlus8ProOxygen_15.O.35_OTA_0350_all_2103221813_3ec450423a214c40
GoogleDrive full OTA link :
https://drive.google.com/file/d/15Qxbp7pZ38CrOO0JSbLx8aFvpeFqF07J/view?usp=sharing
MD5 : 7ddceb429775242f556fb816f49f695c
OnePlus link : https://oxygenos.oneplus.net/OnePlus8ProOxygen_15.O.35_OTA_0350_all_2103221813_3ec450423a214c40.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks!
Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.
PieceKeepr said:
Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.
Click to expand...
Click to collapse
I had the same problem : https://forum.xda-developers.com/t/...magisk-root-permissions.4233391/post-84526447
Backup all your apps and data, messages and call logs in the cloud, or on your phone and paste it on your PC (with SWIFT BACKUP app for exemple).
Then you can use MSM tool for a clean installation with @Some_Random_Username thread (11.0.4.4.IN11AA) : https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Then update to version 11.0.5.5.IN11AA.
Now you can proced to the rooting.
Hello @buu'buu would you have the link for the update version of the rom 11.0.5.5IN11AA - I have the global version model IN2020, but the update does not appear.
PieceKeepr said:
Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.
Click to expand...
Click to collapse
Providing it's a full update, you would download it then instead of just installing, go to system update, click options, then local, then locate the update and run it.
Once complete:
If you're rooted then at this point you wouldn't reboot, you'd open magisk then click install to unused slot OTA.
Then reboot
If you're not then just reboot.
Oxygen updater is the preferred way to do this, always make sure you are using the full update..
It's also possible with an incremental update.
If indeed you are rooted, is recommend stable 22.0, as it's shown to be working as expected in the EU version in my tests, as it has for the OP on the global variant.
jotha.dx said:
Hello @buu'buu would you have the link for the update version of the rom 11.0.5.5IN11AA - I have the global version model IN2020, but the update does not appear.
Click to expand...
Click to collapse
Hello @jotha.dx
No sorry, that's why I went through the MSM tool and then updated to version 11.0.5.5, all of that of course after making a backup of my data. Oxygen updater still did not offer me the latest version.
Either you have to wait or you can use my method and download the latest stable version of magisk 22 and my boot file magisk_patched to perform rooting.
dladz said:
Providing it's a full update, you would download it then instead of just installing, go to system update, click options, then local, then locate the update and run it....
It's also possible with an incremental update.
Click to expand...
Click to collapse
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.
PieceKeepr said:
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.
View attachment 5268281
Click to expand...
Click to collapse
Are you rooted?
Would flashing the stock boot image prior to accepting the update then rooting afterwards work?
Obviously extract the new boot image if you can first.
Quite odd the way the global ROM always comes out with incremental first and not full? Id have thought it would be the opposite way round?
dladz said:
Are you rooted?
Would flashing the stock boot image prior to accepting the update then rooting afterwards work?
Obviously extract the new boot image if you can first.
Quite odd the way the global ROM always comes out with incremental first and not full? Id have thought it would be the opposite way round?
Click to expand...
Click to collapse
Yes I am rooted. I tried booting the stock boot image and the update still didn't work. I then tried flashing the extracted boot.img from the full update obtained from the OnePlus support site and it failed to flash. In both cases I removed all Magisk modules first and rebooted then removed Magisk.
PieceKeepr said:
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.
View attachment 5268281
Click to expand...
Click to collapse
THATS THE EXACT PROBLEM IM HAVING MATE, I tried looking for the frimware on the one plus site but al they had was the beta from march 2 and the 11.0.4 etc, please let me know if u figure this out!
PieceKeepr said:
Yes I am rooted. I tried booting the stock boot image and the update still didn't work. I then tried flashing the extracted boot.img from the full update obtained from the OnePlus support site and it failed to flash. In both cases I removed all Magisk modules first and rebooted then removed Magisk.
View attachment 5268619
Click to expand...
Click to collapse
Ok so you're doing a flash "boot" command which should still work but......
Try this, but change the "magisk_patched" to whatever your boot image is called.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
Bare in mind this may still flash but may not boot, so make sure you have your stock boot image handy to recover.
dladz said:
Ok so you're doing a flash "boot" command which should still work but......
Try this, but change the "magisk_patched" to whatever your boot image is called.
fastboot flash boot_a magisk_patched
Click to expand...
Click to collapse
This worked but I was still unable to update. I tried removing Magisk completely and flashing the stock boot.img but even going that far I was still unable to update using either the system update or manually after downloading through Oxygen Updater. Thanks for trying to help with this. I don't get it.
Can someone confirm that this Oxygen OS 11.0.5.5.IN11AA fixes the DRM Widevine going to L3 for many users (rooted and unrooted)? You should be able to be rooted, and with magisk_props_config keep Widevine L1...
MetroWestMA said:
Can someone confirm that this Oxygen OS 11.0.5.5.IN11AA fixes the DRM Widevine going to L3 for many users (rooted and unrooted)? You should be able to be rooted, and with magisk_props_config keep Widevine L1...
Click to expand...
Click to collapse
But in netflix app specs
Yea -- this sucks. I just took my old OP 7 Pro, MSM'd it updated it to the new 11 release, rooted it and installed Magisk Properties and it gets L1. But my OP 8 Pro now has level L3 -- horrible.
Got it
MetroWestMA said:
Yea -- this sucks. I just took my old OP 7 Pro, MSM'd it updated it to the new 11 release, rooted it and installed Magisk Properties and it gets L1. But my OP 8 Pro now has level L3 -- horrible.
Click to expand...
Click to collapse
Look at post #72
https://forum.xda-developers.com/t/...ll-hd-official-playstore-application.4035219/
PieceKeepr said:
This worked but I was still unable to update. I tried removing Magisk completely and flashing the stock boot.img but even going that far I was still unable to update using either the system update or manually after downloading through Oxygen Updater. Thanks for trying to help with this. I don't get it.
Click to expand...
Click to collapse
what worked, you were able to root or something?