Database Users

how to root and install TWRP on OP2 Oxygen os 3.0 beta version

i flashed OOS 3.0 using TWRP first phone got stuck in boot image while i tried to go into recovery but ROM worked........ then i updated "QUALCOMM-HS" and used some recover tool... then stock recovery is working but i cannot root or flash TWRP
can any one help?

nikhil5868 said:
i flashed OOS 3.0 using TWRP first phone got stuck in boot image while i tried to go into recovery but ROM worked........ then i updated "QUALCOMM-HS" and used some recover tool... then stock recovery is working but i cannot root or flash TWRP
can any one help?
Click to expand...
Click to collapse
Use this and follow the instructions https://drive.google.com/file/d/0B60UNIiUexNPOWJPVGc0R0RHSk0/view?pli=1
Make sure you have oem unlock enabled in dev options and make sure you have usb debug on
Then download and flash the zip from here http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713
and then flash OOS3

AndroidBeginNinja said:
Use this and follow the instructions https://drive.google.com/file/d/0B60UNIiUexNPOWJPVGc0R0RHSk0/view?pli=1
Make sure you have oem unlock enabled in dev options and make sure you have usb debug on
Then download and flash the zip from here http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713
and then flash OOS3
Click to expand...
Click to collapse
The second link is deleted from the website
Sent from my ONE A2003 using XDA-Developers mobile app

nikhil5868 said:
The second link is deleted from the website
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Here is the direct link https://www.androidfilehost.com/?fid=24421527759880815

SupersSU not working
AndroidBeginNinja said:
Here is the direct link https://www.androidfilehost.com/?fid=24421527759880815
Click to expand...
Click to collapse
i flashed supersu using twrp but phone got stuck in boot image

Step 1 use adb to flash recovery in Fastboot modus. Use yash98's recovery.
Commands:
Fastboot devices (enter)
Fastboot flash recovery (filename recovery). Img (enter)
Fastboot boot (filename recovery). Img (enter)
Step 2 flash image oos 3 in twrp
Step 3 flash supersu again specific version for oos 3
Step 4 there is no step 5 ?
Verstuurd vanaf mijn ONE A2003 met Tapatalk

OP2 stuck in boot animation after trying to root.

I flashed TWRP and SuperSU onto my op2 and now it doesnt want to go further than boot animation (can boot into TWRP and fastboot). any help?

trying to adb sideload the stock rom, serving stuck at 45% what gives?
EDIT: rom was corrupted downloaded another one and it works

anyone know if super su flashing is broken on the latest op2 firmware or is it just me?

What version of SuperSU you flashed ? If you flashed v2.46 then try flashing latest stable built (v2.65) ---> http://download.chainfire.eu/supersu-stable
Sent from my ONE A2001 using XDA-Developers mobile app

B!Gguy said:
What version of SuperSU you flashed ? If you flashed v2.46 then try flashing latest stable built (v2.65) ---> http://download.chainfire.eu/supersu-stable
Sent from my ONE A2001 using XDA-Developers mobile app
Click to expand...
Click to collapse
i tried flashing both latest stable and beta with same result

lpgfinmark said:
i tried flashing both latest stable and beta with same result
Click to expand...
Click to collapse
What Rom you currently on ? What TWRP (Modified or Official) ?

B!Gguy said:
What Rom you currently on ? What TWRP (Modified or Official) ?
Click to expand...
Click to collapse
Already solved: had to download a modified version of superSU.

lpgfinmark said:
Already solved: had to download a modified version of superSU.
Click to expand...
Click to collapse
@lpgfinmark
Which one and where did you get it? What result were you getting? Which recovery were you in when you flashed? I am currently having an issue gaining root on latest firmware on an encrypted phone.

HypnoSquid said:
@lpgfinmark
Which one and where did you get it? What result were you getting? Which recovery were you in when you flashed? I am currently having an issue gaining root on latest firmware on an encrypted phone.
Click to expand...
Click to collapse
This one i found it in the oneplus official forums. When i tried to flash normal SU i were stuck on boot animation but with this one it worked wonderfully. i believe the recovery i were using is the latest Modified TWRP (for op2)

lpgfinmark said:
This one i found it in the oneplus official forums. When i tried to flash normal SU i were stuck on boot animation but with this one it worked wonderfully. i believe the recovery i were using is the latest Modified TWRP (for op2)
Click to expand...
Click to collapse
I can't use adb when using a custom recovery and this one fails for me too when trying to flash with the stock recovery. Thanks anyway!

HypnoSquid said:
I can't use adb when using a custom recovery and this one fails for me too when trying to flash with the stock recovery. Thanks anyway!
Click to expand...
Click to collapse
TWRP has adb sideload support built in, doesn't that work?

supersu - maybe these make bootloop?

Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks

I7210I said:
Hi
i saw something interest and maybe you can confirm these, i just upgrade my 6P - upgrade=install from scratch full image from dev site.
and just after instalation i install the supersu zip (originally from site)-after i have the TWRP, i got bootloop.
than i just run the flash all .bat, and like a magic everything is worked, so i tried to install again the zip of super SU and ...bootloop.
it's just leave me the option of install from the app store, is the way of instalation make something?
thanks
Click to expand...
Click to collapse
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk

funnel71 said:
I think your bootloop situation is more software-driven. Most of the people that talk about boot loops with the Nexus 6p have a hardware issue like I do.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
Well keep in mind at the moment I am not rooted. As for updates when I used to be rooted I would flash the stock images for the system recovery bootloader and vendor partitions first. After that was done route would be erased and I could take the OTA update. I should also mention that I have not updated to Oreo. Given the hardware difficulties with my phone I've chosen to stay at 7.1.2
Sent from my Nexus 6P using Tapatalk

so...i'm in 8.1 and these is the conclusion in that state after few tests.

I7210I said:
so...i'm in 8.1 and these is the conclusion in that state after few tests.
Click to expand...
Click to collapse
I would tend to agree with you either you have a version that is not compatible with 8.1 or perhaps you just downloaded a corrupted zip file. I can't speak for root on 8.1 because I don't have that version but I think you've done enough testing to prove your theory that it's the zip that cause your boot loop
Sent from my Nexus 6P using Tapatalk

What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk

stankyou said:
What SuperSU version did you use?
What version TWRP?
I have been on 8.1 Stock with SuperSU and I did not get bootloops whatsoever.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Use Magisk it's latest greatest. Just install the Magisk app from apkmirror and it will prompt to download flaahable zip. As far as TWRP 3.2.1-0 I believe is latest.

I7210I said:
if so, how you can explain that without that the device worked perfect?
also, how you upgrade each time?
Click to expand...
Click to collapse
What are you trying to say? The bootloop you are talking about is different from hardware bootloop of death in nexus 6p.
Supersu works fine for everyone,if its bootlooping for you thn you are doing something wrong or flashing wrong supersu zip.
The most of the reported bootloop of death users are not rooted.

the twrp is 3.2.1 and i used now the Magisk and it works.
the way i used is :
fastboot format userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery <filename>.img
fastboot flash system system.img
Fastboot flash vendor vendor.img
ofcurse with the right names of files..

[SOLVED] Unable to get Magisk Manager to work - Request help

So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
UPDATE:
Got it to work. You need to have the app installed on internal storage. Mine was installed on sdcard. doh!

buggerman said:
So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
Click to expand...
Click to collapse
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I

Haizum74 said:
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I
Click to expand...
Click to collapse
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.

buggerman said:
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.
Click to expand...
Click to collapse
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?

Haizum74 said:
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?
Click to expand...
Click to collapse
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled Magisk Manager because some people said uninstall and reinstall and try again.
I haven't installed/ uninstalled Magisk yet. Only the manager.

buggerman said:
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled it because some people said uninstall and reinstall and try again.
Click to expand...
Click to collapse
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?

Haizum74 said:
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?
Click to expand...
Click to collapse
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.

buggerman said:
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.
Click to expand...
Click to collapse
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.

Haizum74 said:
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.
Click to expand...
Click to collapse
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk

Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs

Ahh I thought so, well that yt video is ideal then.

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
buggerman said:
Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
As above

Haizum74 said:
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
As above
Click to expand...
Click to collapse
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
No, not if you still want to keep OTA updates without having to download them manually. From what I am aware, unlocking the bootloader and rooting as per the videos instructions is the only way to keep auto OTA.

buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Click to expand...
Click to collapse
TWRP by mohancm

TWRP not booting for me.

UPDATE:
Got it to work. Moved the app to internal storage. My device installed it on sdcard by default. That was causing the freeze.

Required TWRP for Stock Android Pie........

Hey Folks, I am just a newbie here trying to root and try Custom ROMs. Currently, I am using Stock Android Pie with Unlocked Bootloader and 1 June 2019 Security patch. I can really appreciate some help here coz I cannot find a suitable TWRP and Steps for configuration of my device. Thanks in Advance

these are the steps i used
https://wiki.lineageos.org/devices/tissot/install
its working for me

Which Recovery?
mdude22 said:
these are the steps i used
it's working for me
Click to expand...
Click to collapse
It may be working but which TWRP recovery did you use?

i used twrp-3.3.0-2-tissot.img
i found it in this thread:
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-16-0-xiaomi-mi-a1-t3885100
i can upload it here if you want, but im not sure what website to use to upload because it tried using xda and it says file too large

mdude22 said:
i used twrp-3.3.0-2-tissot.img
i found it in this thread:
i can upload it here if you want, but im not sure what website to use to upload because it tried using xda and it says file too large
Click to expand...
Click to collapse
it's only an img file right? there is no zip file

yes, it's called
twrp-3.3.0-2-tissot.img

You can find TWRP in Mi A1 xda forum but the sad news is you can't get permanent TWRP in latest Stock Pie Rom. I just had the permanent TWRP in 1.0.8.0 Stock rom by flashing eXtreme Kernel then flash Cosmic Dan's TWRP Zip Installer otherwise i tried many times but never get permanent TWRP. You can also use official TWRP Zip installer from TWRP's official site

ranjodhricky said:
You can find TWRP in Mi A1 xda forum but the sad news is you can't get permanent TWRP in latest Stock Pie Rom. I just had the permanent TWRP in 1.0.8.0 Stock rom by flashing eXtreme Kernel then flash Cosmic Dan's TWRP Zip Installer otherwise i tried many times but never get permanent TWRP. You can also use official TWRP Zip installer from TWRP's official site
Click to expand...
Click to collapse
I just need root access for now can you please explain the process for latest stock pie rom? I have already unlocked the bootloader and the remaining process on internet is just confusing

jasmeets7 said:
I just need root access for now can you please explain the process for latest stock pie rom? I have already unlocked the bootloader and the remaining process on internet is just confusing
Click to expand...
Click to collapse
1- Boot from patched boot image (ex: fastboot boot patched_boot.img).
2- Install Magisk Manager app.
3- Open it and Select install then direct install.
4- Reboot.
If you want to unroot then select complete uninstall from magisk manager.

Stealtherthreat said:
1- Boot from patched boot image (ex: fastboot boot patched_boot.img).
2- Install Magisk Manager app.
3- Open it and Select install then direct install.
4- Reboot.
If you want to unroot then select complete uninstall from magisk manager.
Click to expand...
Click to collapse
From where can I get patched boot image?

jasmeets7 said:
From where can I get patched boot image?
Click to expand...
Click to collapse
Download stock june boot image from here - https://forum.xda-developers.com/showpost.php?p=79898593&postcount=3
To patch it,
1- Install Magisk Manager app.
2- Select install then select Patch file.
3- It will ask for the boot image, select the downloaded file.
4- It will automatically generate the patched boot image.