Related
I tried to restored a nandroid backup which didnt work, I then tried to lock and unlock bootloader thinking recovery would reset original image and that didnt work and now its wiped. Any suggestions as I'm looping into bootloader screen and I cant even push an image using adb.
Have you tried formatting your data in TWRP?
sting5566 said:
Have you tried formatting your data in TWRP?
Click to expand...
Click to collapse
Yes. But I have no way so far to get an oxygen os rom to my internal storage so I can flash. Just keeps going to fastboot mode.
Did you try reinstalling Twrp thru fastboot?
sting5566 said:
Did you try reinstalling Twrp thru fastboot?
Click to expand...
Click to collapse
How would that help if I have nothing to flash? I can get to twrp no problem.
SysAdmNj said:
How would that help if I have nothing to flash? I can get to twrp no problem.
Click to expand...
Click to collapse
You stated it kept going back into fastboot, sorry if I misunderstood. Your PC should see the phone while in TRWP, try another port on your PC or another cable.
sting5566 said:
You stated it kept going back into fastboot, sorry if I misunderstood. Your PC should see the phone while in TRWP, try another port on your PC or another cable.
Click to expand...
Click to collapse
Yes, my phone is wiped and no OS on it either. Thats probably why its going back to fastboot. Is my only choice to unbrick? Which as I'm seeing would require me to go to hydrogen os before even being able to go to oxygen os?
SysAdmNj said:
Yes, my phone is wiped and no OS on it either. Thats probably why its going back to fastboot. Is my only choice to unbrick? Which as I'm seeing would require me to go to hydrogen os before even being able to go to oxygen os?
Click to expand...
Click to collapse
Even with it wiped, if you have TWRP installed and no OS you should still boot back into recovery, not fastboot. I would still try installing TWRP again, use the codeworkx version, seems to work best for most people.
sting5566 said:
Even with it wiped, if you have TWRP installed and no OS you should still boot back into recovery, not fastboot. I would still try installing TWRP again, use the codeworkx version, seems to work best for most people.
Click to expand...
Click to collapse
Ok so I'm definitely not understanding, once I install twrp codeworkx version then whats my next step to get my device up and running?
SysAdmNj said:
Ok so I'm definitely not understanding, once I install twrp codeworkx version then whats my next step to get my device up and running?
Click to expand...
Click to collapse
After that I would format data in TWRP, reboot back into TWRP and then copy over a rom. Your PC should see the phone plugged in booted up in TWRP.
sting5566 said:
After that I would format data in TWRP, reboot back into TWRP and then copy over a rom. Your PC should see the phone plugged in booted up in TWRP.
Click to expand...
Click to collapse
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
SysAdmNj said:
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
Click to expand...
Click to collapse
Glad it worked out for you. What rom were you trying to flash and why magisk 14, newer ones are out now.
sting5566 said:
Glad it worked out for you. What rom were you trying to flash and why magisk 14, newer ones are out now.
Click to expand...
Click to collapse
OOS 5.0.1 latest version of oreo for oneplus 5 is what I flashed and running now. Now I'm attemping to flash magisk, latest version and hopefully dont run into the black screen.
SysAdmNj said:
OOS 5.0.1 latest version of oreo for oneplus 5 is what I flashed and running now. Now I'm attemping to flash magisk, latest version and hopefully dont run into the black screen.
Click to expand...
Click to collapse
The latest xXx rom is close to stock and runs great if you want to try something custom.
SysAdmNj said:
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
Click to expand...
Click to collapse
It's a known issue. You have to use Magisk 15.2 or higher.
If you flash an older version you will get a black screen with a blue notification led.
maikvitesse said:
It's a known issue. You have to use Magisk 15.2 or higher.
If you flash an older version you will get a black screen with a blue notification led.
Click to expand...
Click to collapse
Yes, I learned the hard way
I thought I could flash 14 and just update to 15.2.
sting5566 said:
The latest xXx rom is close to stock and runs great if you want to try something custom.
Click to expand...
Click to collapse
I actually want to stay close to stock. I dont even want to use nova launcher, I"m staying with OP launcher. So far so good, Not sure upgrade was worth the trouble yet
Is it possible to use the official TWRP app to install on the 6T? Thanks in advance to anyone nice enough to answer ?
Bildo41383 said:
Is it possible to use the official TWRP app to install on the 6T? Thanks in advance to anyone nice enough to answer ?
Click to expand...
Click to collapse
I'm sure it is. I don't see why it wouldn't be seeing how we just got an official TWRP now.
https://www.androidpolice.com/2018/...ble-for-oneplus-6t-moto-z3-and-other-devices/
TheKnux said:
I'm sure it is. I don't see why it wouldn't be seeing how we just got an official TWRP now.
https://www.androidpolice.com/2018/...ble-for-oneplus-6t-moto-z3-and-other-devices/
Click to expand...
Click to collapse
Will I need to reflash majisk as well?
Bildo41383 said:
Will I need to reflash majisk as well?
Click to expand...
Click to collapse
More than likely. A lot of people reported that after flashing Magisk via the zip in TWRP, the phone doesn't boot until you flash Magisk. I as well encountered this issue. If you flash TWRP and reboot recovery and then reboot to system you'll be stuck with a recovery loop until you flash Magisk. Hope this helps.
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
stovo06 said:
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
Click to expand...
Click to collapse
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Click to expand...
Click to collapse
I thought this was for 9.x.x
stovo06 said:
I thought this was for 9.x.x
Click to expand...
Click to collapse
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Click to expand...
Click to collapse
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
flyoffacliff said:
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
Click to expand...
Click to collapse
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Striatum_bdr said:
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Click to expand...
Click to collapse
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
stovo06 said:
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Striatum_bdr said:
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Click to expand...
Click to collapse
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash boot TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash recovery TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
Click to expand...
Click to collapse
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Striatum_bdr said:
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Click to expand...
Click to collapse
That's what I've read as well. And there are many solutions but I find them scattered all over the forms.
And I don't trust YouTube videos lol
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
stovo06 said:
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
Click to expand...
Click to collapse
I don't think there is the need of another thread. Many are already talking about rooting and flashing twrp.
What makes people confuse is that perhaps some of them think things have changed... And that methods are bound to an Android version.
Nothing has changed.
Fastbooting TWRP and then flashing it, is the way we do it since years. Patching boot img as an alternative is also a classical way to root.
People are blinded by tiny differences and don't see that the frame hasn't changed. You unlock the bootloader, then boot to twrp and then either you flash only Magisk either you flash twrp then Magisk. Very simple. Always with latest versions.
It's because xda threads are not moderated except for offenses, etc that many users post their 'own' recipe every 2 pages without anybody cleaning and organizing things to make them understandable. And the fact that threads are not well maintained in time, with titles and first posts instructions that can seem obsolete.... Especially on old phones like our when devs are quitting the scene without designating a maintainer
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
Click to expand...
Click to collapse
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
aaron74 said:
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
Click to expand...
Click to collapse
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Striatum_bdr said:
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Click to expand...
Click to collapse
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
stovo06 said:
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
Click to expand...
Click to collapse
Wait for render zenith
stovo06 said:
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
Click to expand...
Click to collapse
Yeah, this is an awesome device. Only device I've been happy with since my old Samsung note 4. Biggest thing I miss, it'd be nice to have an SD card slot!
Patching a boot image is what Magisk does when you install it. But you just would manually do this.
Last question, I've been reading too install Magisk 19.4.
Does that still apply?
Apologies for all the questions (and great appreciation for the help), but the information here is scattered and at times contradicting when all I need now is a simple magisk manager and mod ?.
Thank you all for your help.
My steps:
1) fastboot flashing unlock
2) fasboot --set-active=_a (system in b slot)
3) fastboot flash boot twrp.img
4) in twrp i choose twrp.zip install and twrp install in both slots
5) reboot in bootloader
6) fastboot --set-active=_b && fastboot reboot
7) after reboot it reboot in bootloader
8) in bootloader choose start
9) it reboot in bootloader again
and this for many times
what to do?
sorry for my english
If you want twrp, you'll need to be on January firmware, the February firmware broke something in twrp (and we're not expecting a update from twrp, they're essentially dead). Your best bet for newer security patches and twrp is January firmware and a custom rom
dragynbane222 said:
If you want twrp, you'll need to be on January firmware, the February firmware broke something in twrp (and we're not expecting a update from twrp, they're essentially dead). Your best bet for newer security patches and twrp is January firmware and a custom rom
Click to expand...
Click to collapse
Thanks for the info, but I have a question. Can I use Orangefox or CWM instead of TWRP? I really like Android Q, and it would be sad to downgrade. Thanks for reading.
TipTopHiatus said:
Thanks for the info, but I have a question. Can I use Orangefox or CWM instead of TWRP? I really like Android Q, and it would be sad to downgrade. Thanks for reading.
Click to expand...
Click to collapse
Afaik Twrp is the only custom recovery available for this device.
CWM hasn't been maintained since around 2012, so I don't think that's coming back. And I couldn't find any mention of Orangefox for mata, though it being based on Twrp, would likely have the same issues as Twrp.
dragynbane222 said:
Afaik Twrp is the only custom recovery available for this device.
CWM hasn't been maintained since around 2012, so I don't think that's coming back. And I couldn't find any mention of Orangefox for mata, though it being based on Twrp, would likely have the same issues as Twrp.
Click to expand...
Click to collapse
Thanks for the info!
It's just that Orangefox says that it supports Treble devices, which Essential PH-1 is, so I am wondering if it would work.
TipTopHiatus said:
Thanks for the info!
It's just that Orangefox says that it supports Treble devices, which Essential PH-1 is, so I am wondering if it would work.
Click to expand...
Click to collapse
Without it being ported to this device, it wouldn't. You'd brick your device if you flashed it
dragynbane222 said:
Without it being ported to this device, it wouldn't. You'd brick your device if you flashed it
Click to expand...
Click to collapse
Flashed it, and it soft-bricked. Luckily, TWRP had me prepared, so my device is fine now. I'm just gonna stick to flashing Magisk without a custom recovery. Thank you for your help.
TipTopHiatus said:
I really like Android Q, and it would be sad to downgrade.
Click to expand...
Click to collapse
If you really need TWRP, then Jan 2020 update is still Q, just one month older than the latest update from Essential. You won't be downgrading Android version - only a security patch level...
kt-Froggy said:
If you really need TWRP, then Jan 2020 update is still Q, just one month older than the latest update from Essential. You won't be downgrading Android version - only a security patch level...
Click to expand...
Click to collapse
Thanks for your help. I'll consider downgrading to Jan build eventually, but I think I'm just gonna stick with Feb. Just flashed Magisk, and It works well. Now, I can have some fun with modules. Thanks to all for the help given. I really do appreciate it.
I just updated to Android 11/OOS11 and I am trying to reroot my phone with Magisk. I had root on android 10. I downloaded the latest OTA package from this thread and patched the boot.img. I can boot my phone and it works fine but I have no root access. I have the latest magisk manager installed.
Am I using the wrong boot image or is there something else going on here?
Thanks in advance.
night hawk said:
I just updated to Android 11/OOS11 and I am trying to reroot my phone with Magisk. I had root on android 10. I downloaded the latest OTA package from this thread and patched the boot.img. I can boot my phone and it works fine but I have no root access. I have the latest magisk manager installed.
Am I using the wrong boot image or is there something else going on here?
Thanks in advance.
Click to expand...
Click to collapse
It can happen sometimes, make sure you're using Magisk Manager Canary and/or Beta, patch the image again and fastboot boot to see if yoy have root if you do fastboot flash and profit
Shredz98 said:
It can happen sometimes, make sure you're using Magisk Manager Canary and/or Beta, patch the image again and fastboot boot to see if yoy have root if you do fastboot flash and profit
Click to expand...
Click to collapse
I tried to find the latest canary but the only link I found was dead. Is there anyway you could point me to a working link?
Bump
night hawk said:
I tried to find the latest canary but the only link I found was dead. Is there anyway you could point me to a working link?
Click to expand...
Click to collapse
This is the last beta and it works great with A11.
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.2/MagiskManager-v8.0.2.apk
Kollachi said:
This is the last beta and it works great with A11.
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.2/MagiskManager-v8.0.2.apk
Click to expand...
Click to collapse
That is so weird. I think my pihole is blocking github links for some reason. I suspect this was my problem. I downloaded it over lte on my phone successfully and will try it after work. I will get back to you with results.
Thanks a bunch.
I used the newest beta of magisk to try and root again after work and it put my phone into crashdump mode. I had to MSM my phone; thankfully it didn't break my fingerprint sensor like I was reading about. After that I tried THE EXACT SAME THING and it worked that time. I'm beginning to think that my pc was the problem here. I always have way to many usb devices connected to my pc (I have 2 usb controller cards installed for extra ports and they are usually all full ) so maybe that was making ADB act up or something. In the future I think I'm going to use a less cluttered machine for rooting/modding.
Thanks for everyone's help.
Kollachi said:
This is the last beta and it works great with A11.
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.2/MagiskManager-v8.0.2.apk
Click to expand...
Click to collapse
I too am having issues re-rooting my OP 8 pro after android 11 update. have installed from this above link and followed the "fastboot" directions and still no luck. When I open magisk manager it shows "installed N/A"
also is there a version of twrp android 11 compatible
cheers
Same happened to me, all the patched Global 11 boot img didn't work after multiple attempts to flash, switched a/b, no luck. Tried downgrading by flashing downgrade zip in repo thread sent me to crashdump had to use msm . Now I'm on os 10 .13 rooted afraid to try again.