Hello everyone, i want to know how can i root my OnePlus 5. So i purchased it in India, it had oxygen os, and i tried to root it myself but the root file which i got from the internet was corrupt. Because of it my phone lost all it's data and os. I went to a local shop and he installed hydrogen os saying oxygen os is not able to install. I want to know how can i root hydrogen os. It's currently running on 9.0.3 pie.
AkashGerrad said:
Hello everyone, i want to know how can i root my OnePlus 5. So i purchased it in India, it had oxygen os, and i tried to root it myself but the root file which i got from the internet was corrupt. Because of it my phone lost all it's data and os. I went to a local shop and he installed hydrogen os saying oxygen os is not able to install. I want to know how can i root hydrogen os. It's currently running on 9.0.3 pie.
Click to expand...
Click to collapse
Don't know what you did but if you want root simply flash magisk 18.1 or above within twrp, that's it.
If you searching for unlocking bootloader, backup EFS, decrypted etc. See here https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 it also explains what that is in case you have no clue
strongst said:
Don't know what you did but if you want root simply flash magisk 18.1 or above within twrp, that's it.
If you searching for unlocking bootloader, backup EFS, decrypted etc. See here https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 it also explains what that is in case you have no clue
Click to expand...
Click to collapse
So what i did was , i was rooting oxygen os myself but the supersu file was corrupt so it didn't work my phone wasn't turning on and mistakenly i erased os from twrp. I went to the local shop and he installed hydrogen os saying oxygen os is facing error while installing.
So now i need to root hydrogen os, so is there a different process for it?
AkashGerrad said:
So what i did was , i was rooting oxygen os myself but the supersu file was corrupt so it didn't work my phone wasn't turning on and mistakenly i erased os from twrp. I went to the local shop and he installed hydrogen os saying oxygen os is facing error while installing.
So now i need to root hydrogen os, so is there a different process for it?
Click to expand...
Click to collapse
No different process,same as oxygenOS.
strongst said:
No different process,same as oxygenOS.
Click to expand...
Click to collapse
Alright, thanks so nuch !
AkashGerrad said:
Alright, thanks so nuch !
Click to expand...
Click to collapse
But keep in mind to use the thread I linked you and no other suspicious supersu files
If you have further questions, don't hesitate to ask.
Related
Is there any option to root my phone apart from SuperSU? Coz SuperSU gives some error. My sim card is not detecting after installing SuperSU. If I unroot sim card is working.i am using twrp harpia in Moto g4 play and lineage 14.1 rom 7.1.2 nougat.
mathantn said:
Is there any option to root my phone apart from SuperSU? Coz SuperSU gives some error. My sim card is not detecting after installing SuperSU. If I unroot sim card is working.i am using twrp harpia in Moto g4 play and lineage 14.1 rom 7.1.2 nougat.
Click to expand...
Click to collapse
Most Lineage builds come pre-rooted. Enable developer options and look for the root toggle. Might need a reboot to take effect.
Lineage must be compiled differently for SuperSU to work. The ROM builder will know if this was done.
Magisk is an alternative to SuperSU. I don't have experience with it on this device but it should work fine. You'll need to do a little reading to become familiar with the installation procedure.
Davey126 said:
Most Lineage builds come pre-rooted. Enable developer options and look for the root toggle. Might need a reboot to take effect.
Lineage must be compiled differently for SuperSU to work. The ROM builder will know if this was done.
Magisk is an alternative to SuperSU. I don't have experience with it on this device but it should work fine. You'll need to do a little reading to become familiar with the installation procedure.
Click to expand...
Click to collapse
Thanks bro. It worked
I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?
B1lal545 said:
I've read around that unlocking the bootloader on the axon 7 with the orea update (B04 on A2017G) isn't gonna work and that I need to roll back to nougat (7.1) and then unlock the bootloader that way and then install TWRP.
I'm a noob and I need some help. All I want is android pie and lineage os 16 on top. So could you guys link me to some easy to follow guides on how to get pie and LOS16?
But first I need to understand why I can't just use ADB right now on the oreo axon 7 and get an unlocked bootloader. Why do I have to roll back to nougat?
Click to expand...
Click to collapse
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.
runninghamster said:
You're correct on that statement.
You can't unlock the bootloader on Oreo because there is no fastboot support with the Oreo updates. ZTE basically broke another thing. You'll need to EDL flash Nougat 7.1 and then use the EDL Tool or the A7 Toolkit to unlock the bootloader. Afterwards, you can follow the instructions in the LineageOS 16 thread, and flash in this order:
• Flash universal bootstack (Los15.1v2Universal)
• Flash the A2017G Modem
• Flash LOS16 zip
• Flash GApps and/or Magisk
• Reboot to system.
If you get an error whilst trying to flash LOS16 zip, just try flashing it again.
All the guides in the Guides section are outdated.
Click to expand...
Click to collapse
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?
B1lal545 said:
Thanks for replying when nobody else did. Since this post was a bit old I went ahead and unlocked the bootloader and installed TWRP with magisk, thinking that I could install Lineage later and first I should obtain root. So I installed magisk through TWRP but now whenever I reboot it just goes straight to TWRP and I don't know how to boot into the phone. Any idea about how I can exit twrp?
Click to expand...
Click to collapse
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.
runninghamster said:
Magisk doesn't work at all on stock roms unless you use a work-around. The phone not booting is because of that.
For the work-around, check out this thread:
https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
BTW, I'm not sure if this works, I've never tried it. The thread is also a bit old.
Click to expand...
Click to collapse
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.
B1lal545 said:
could it be a possibility that if I reinstall nougat 7.1 on the phone through TWRP, I'd be able to boot? Or does rooting with magisk completely disable us from installing stock roms without some sort of workaround?
My reasoning is that if the rom installs successfully then I would have booted with magisk in magisk manager and root. Maybe my rom got deleted during this process.
Click to expand...
Click to collapse
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.
runninghamster said:
Magisk just prevents the phone from booting. It doesn't delete the rom. If you look in topjohnwu's GitHub page for Magisk, you'll find Magisk Uninstaller right next to where you download Magisk from. Download the Magisk Installer zip, move it over to your phone, and then flash it in TWRP. It'll remove Magisk and you'll be able to boot into your rom again.
Click to expand...
Click to collapse
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?
B1lal545 said:
Ok I've uninstalled magisk with the latest uninstaller. But now when booting up, the phone is stuck on the "please lock bootloader page" and is not proceeding further. Given that I can still use TWRP, should I just follow the LOS 16 pie instructions and install the bootstack, modem, Gapps and the zip file?
I could root the phone by flashing magisk once I'm done flashing these things right?
Click to expand...
Click to collapse
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.
runninghamster said:
Yeah, go ahead and flash Los 16.
Flash your bootstack and modem, and reboot to recovery from TWRP. The TWRP version will have changed. You need to flash latest TWRP image again, use Orden 3.2.3-0 TWRP from LOS 15/16 thread. After that, reboot to recovery and continue with the rest of the steps.
You can flash Magisk whenever you'd like, hell you could even flash it 1 year after running Los 16 haha.
Click to expand...
Click to collapse
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.
B1lal545 said:
You are my saviour. You've helped me so much. But I'm scared of bricking so please don't be annoyed by me when I ask for confirmation.
So basically I installed the vendor partition using party from @Oki like the LOS 16 guide required.
But now as to the things you told me to do.
First I'll install the universal bootstack for LOS and my model specific modem from https://androidfilehost.com/?w=files&flid=270519
Once both are flashed my TWRP version will have changed so I will flash the latest version of TWRP again using fastboot
Then I'll go on ahead and install LOS 16 and GApps
THANK YOU SO MUCH IN ADVANCE.
Click to expand...
Click to collapse
That's correct. Go ahead with the flash, you're welcome for the help
runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
YAAAAAAAAAYYYY!!!
I just installed LOS 16 and everything seems to be working fine.
But the thing is I downloaded and flashed magisk through TWRP, and the installation went fine. When I booted into LOS even the magisk manager was installed.
But when I installed the root verification app from playstore, it said that the device was not rooted. Any advice? Other than that it feels so good to finally be on a custom ROM. Thanks for your help.
I wish you success and happiness from the bottom of my heart.
runninghamster said:
That's correct. Go ahead with the flash, you're welcome for the help
Click to expand...
Click to collapse
Nevermind hahahahah. I checked another app. I'm rooted, forgot to grant Superuser permissions the first time.
Again thank you so much and I apologize if I was overbearing or annoying. You really helped me out and made this process much less painful than it could've been.
Hi, I've got a new update today (11/02) and I want to know if there's already a method to root on Android 10. I've already searched for it but didn't find anything. Thanks.
MatheusPimentel said:
Hi, I've got a new update today (11/02) and I want to know if there's already a method to root on Android 10. I've already searched for it but didn't find anything. Thanks.
Click to expand...
Click to collapse
You searched for it bad, then.
https://dropmefiles.com/PZBqh Here's boot.img patched with current Magisk (canary channel).
kibuuka said:
You searched for it bad, then.
https://dropmefiles.com/PZBqh Here's boot.img patched with current Magisk (canary channel).
Click to expand...
Click to collapse
I have just to flash it on TWRP? In Android 10 I can use the same TWRP as I've been using on Android 9?
MatheusPimentel said:
I have just to flash it on TWRP? In Android 10 I can use the same TWRP as I've been using on Android 9?
Click to expand...
Click to collapse
It's best to wait until a stable twrp is made.
I followed this and it worked perfectly.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
MatheusPimentel said:
Hi, I've got a new update today (11/02) and I want to know if there's already a method to root on Android 10. I've already searched for it but didn't find anything. Thanks.
Click to expand...
Click to collapse
I followed the standard procedure and root remained but lost decryption in twrp:
Rebooted in twrp
Ran latest magisk uninstaller in twrp
Installed Android10
Installed latest twrp of Mauronofrio
Rebooted info twrp
Installed magisk
Rebooted into system
I just updated OxygenOS and didn't see that there was a version change from Android 9 to 10 involved.
TWRP was replaced with the stock recovery during the process. That always happened when running an OxygenOS system update, but I could always flash TWRP again afterwards. That doesn't seem to work anymore now.
I guess my mistake was to reboot to system after updating, correct?
Didn't pay enough attention, I thought it was just another Android 9 update. That'll teach me...
I lost Root mine now is 10.3.0 NO ROOT
help
yahaa08 said:
I lost Root mine now is 10.3.0 NO ROOT
help
Click to expand...
Click to collapse
If you want to root I can help u.
As title, do we have any way to root it with magisk yet?
I'm wondering myself. I tried to root with "magisk_shieldtvpie_r2.zip and although it seemed to have installed, after restarting I still didn't have root
I know you said you wanted magisk but have you tried the Nvidia Sheild developer only OS images?
Those come with included root.
https://developer.nvidia.com/shield-developer-os-images
My problem is I don't know if I can update my developer only OS image 8.1 to 8.2 without losing all my apps. I left the bootloader unlocked. Wondering why I couldn't simply flash developer os 8.2 over 8.1 if bootloader is unlocked?
dovedescent7 said:
I know you said you wanted magisk but have you tried the Nvidia Sheild developer only OS images?
Those come with included root.
https://developer.nvidia.com/shield-developer-os-images
My problem is I don't know if I can update my developer only OS image 8.1 to 8.2 without losing all my apps. I left the bootloader unlocked. Wondering why I couldn't simply flash developer os 8.2 over 8.1 if bootloader is unlocked?
Click to expand...
Click to collapse
u might want to check before anything.. i got the 2019 pro dev os firmware and it was actually just regular firmware lol
but i rooted with latest magisk.. not sure y anyone would have issues rooting
tha kid2012 said:
I'm wondering myself. I tried to root with "magisk_shieldtvpie_r2.zip and although it seemed to have installed, after restarting I still didn't have root
Click to expand...
Click to collapse
i just fastboot boot twrp then flashed latest magisk on my 2019 pro 8.2.0
Maybe I'm doing it wrong, haven't flashed anything in a while and the place I use to get step by step guides from (nvidiashieldzone) shut down. Mind telling me the steps that you used to root?
tha kid2012 said:
Maybe I'm doing it wrong, haven't flashed anything in a while and the place I use to get step by step guides from (nvidiashieldzone) shut down. Mind telling me the steps that you used to root?
Click to expand...
Click to collapse
just check the twrp thread or the many other root threads
elliwigy said:
u might want to check before anything.. i got the 2019 pro dev os firmware and it was actually just regular firmware lol
but i rooted with latest magisk.. not sure y anyone would have issues rooting
Click to expand...
Click to collapse
Did you lose Dolby vision and got Netflix issues when rooting with the dev os image on the Nvidia Shield 2019?
I'm installed the magisk but bootloop in nvidia logo, I have 2017 with 8.2 developers firmware so I can get root privileges any help?
baba702 said:
I'm installed the magisk but bootloop in nvidia logo, I have 2017 with 8.2 developers firmware so I can get root privileges any help?
Click to expand...
Click to collapse
I successfully root on normal firmware 8.2.0 with the lastest magisk. I dont know about the developer firmware.
1. I disable all magisk modules and restart
2. Boot to fastboot mode
3. Download and extract the firmware .
4. Run flash all.bat to flash the 8.2.0 firmware
5. Reboot after complete(let the shield completely boot up)
6. Use magisk manager which previously installed to patch the boot.img
7. Reboot shield to fastboot mode and flash the patched boot.img
8. Rebbot
9. Now i enable modules.
question to you guys who have rooted.
Did you get AFwall+ to work?
I have both 2017 Pro model shield and 2019 Pro model. I would like to root so I can uninstall all the crap, and then install AFwall+ firewall and just enable outgoing twitch, spotify, youtube, and some small services I use..
elliwigy said:
just check the twrp thread or the many other root threads
Click to expand...
Click to collapse
rogeriskira said:
Did you lose Dolby vision and got Netflix issues when rooting with the dev os image on the Nvidia Shield 2019?
Click to expand...
Click to collapse
Also curious.. Did you loose any of these functionalities when using dev image and rooting .. ?
I had developer image 8.2.0 installed on the Nvidia 2017 16gb, updated via Ota to latest 8.2.2 but lose root, how do I root again? Thanks
Has anyone found a way to root 8.2.2 yet?
dovedescent7 said:
I know you said you wanted magisk but have you tried the Nvidia Sheild developer only OS images?
Those come with included root.
https://developer.nvidia.com/shield-developer-os-images
My problem is I don't know if I can update my developer only OS image 8.1 to 8.2 without losing all my apps. I left the bootloader unlocked. Wondering why I couldn't simply flash developer os 8.2 over 8.1 if bootloader is unlocked?
Click to expand...
Click to collapse
flash develop rom
tinhsoftware said:
I successfully root on normal firmware 8.2.0 with the lastest magisk. I dont know about the developer firmware.
1. I disable all magisk modules and restart
2. Boot to fastboot mode
3. Download and extract the firmware .
4. Run flash all.bat to flash the 8.2.0 firmware
5. Reboot after complete(let the shield completely boot up)
6. Use magisk manager which previously installed to patch the boot.img
7. Reboot shield to fastboot mode and flash the patched boot.img
8. Rebbot
9. Now i enable modules.
Click to expand...
Click to collapse
I just got Shield the other day and it came with 8.2. Would flashing with rooted firmware wipe it clean? Same for just rooting it?
Hey, everyone, I'm hoping someone can help me with this issue. So, I was avoiding any updates because I didn't want to lose root. Well, I eventually did update Lineage and lost root. Now for some reason I can't regain it. I have a OnePlus 6T (T-Mobile, bottloader unlocked, obviously ), Linkage 17, and Magisk. Originally I flashed TWRP as a temp recovery, installed Magisk and Lineage (and Root Checker), and everything was fine - until the update. Now when I try to sideload with ADB nothing happens. I just receive a CMD error "ADB: requires an argument..." Long story short. I'd like to know how I can just completely start over, from scratch, flash different OS and keep root. Any help would be appreciated. Thanks in advance.
Do you still have twrp as recovery?
Brettroth said:
Do you still have twrp as recovery?
Click to expand...
Click to collapse
No, Lineage has installed itself as the recovery. I still have TWRP (the app) on my phone, but whenever I try to do anything with it, it crashes.
joshua97542 said:
No, Lineage has installed itself as the recovery. I still have TWRP (the app) on my phone, but whenever I try to do anything with it, it crashes. When I look it up to my laptop (the same one I used to root and install everything, ADB will recognize my device, I can run commands, but something won't allow me to actually install anything. I receive "and.exe: requires an argument". I've tried every which way I could think of to try and make it install, but nothing is working.
Click to expand...
Click to collapse
Couldn't you just use fastboot TWRP?