yashsingh1/xdaforums huggingface dataset:
[Essential Phone Guides, News, & Discussion] brqndon:
Quick question: is there anyway to access TWRP? I'm on Oreo and Magisk 14.3, and there doesn't seem to be any way to access TWRP even when trying to go into recovery mode.
[Essential Phone Guides, News, & Discussion] EdwardLThompson:
Thank you very much. Unfortunately, I'm now having an issue where I cannot get into the fastboot, recovery, or bootloader. I have tried both the hardware buttons and the ADB commands with no luck. I tried the sideload command as well. I'm a novice with ADB, is there another command I can use to force the OreoTWRP over there?
[Essential Phone Guides, News, & Discussion] mobileman88:
Does all the hardware like fingerprint, cameras, nfc work after magisk ? Pardon me as the search is not working all that well and i read well over 50 pages in the essential threads.
[Essential Phone Guides, News, & Discussion] ad78:
Yes, also im using android pay without any issues

---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------

Folks, Oreo with rooted will not play along. Over time you will get random reboots or startup stuck.

I revert mine to NMJ51B all is good now
[Essential Phone Guides, News, & Discussion] spotmark:
Speak for yourself. I've been running the Oreo beta, with no problems, since the day after it was released. Rooted and Substratum as well.
[Essential Phone Guides, News, & Discussion] mobileman88:
Thanks!

I am switching to it from a 6P. Shall keep the 6P as a backup till I find the PH1 stable enough. Intend to do the following :

1. Unlock

2. Flash Oreo beta

3. Magisk

4. Restore Titanium Backup

5. Use !
[Essential Phone Guides, News, & Discussion] ad78:
What version of magisk you are running?
[Essential Phone Guides, News, & Discussion] Helper45:
If I wanted to unroot and relock bootloader would I just need to flash the unmodified boot img for my build # and then use the right fastboot command?
[Essential Phone Guides, News, & Discussion] spotmark:
14.3
[Essential Phone Guides, News, & Discussion] redeyss:
I've been round and round with this phone! To unroot i would do it through magisk manager, then in bootloader mode connected to computer run the flash-all command from the unziped in adb folder "back to stock" F or B firmware. Once complete, double check you are unrooted, then back to bootloader and fastboot flashing lock. Good Luck!!

---------- Post added at 09:01 PM ---------- Previous post was at 08:46 PM ----------

To those running oreo beta rooted, can you theme the settings and lockscreen notifications black with substratum and swift black theme? That's all I'm missing on this phone!
[Essential Phone Guides, News, & Discussion] spotmark:
You mean like this?
[Essential Phone Guides, News, & Discussion] ioiomi:
Me too

-------------------------------------------------

update

I solved it. It's my problem.
[Essential Phone Guides, News, & Discussion] avd:
there needs to be two independent threads here:

1) rooting latest stock/sprint software

2) rooting oreo beta images
[Essential Phone Guides, News, & Discussion] Eric_Sheill:
Mmmmm, that's black awesome goodness right there! Are you finding the Oreo beta stable? I suppose I can wait for finished update if not. Any problem rooting and what did you flash to boot after magisk?

And did you have to use Andromeda connected to PC? Thx!
[Essential Phone Guides, News, & Discussion] nicoseb:
Well somehow my Oreo has been far more stable since my post a few days ago... The crashing and hanging on dots has happened a few times only, and I think none within the last 24 hours.

Who knows...works for me!

Hopefully it remain like that.

Thinking about it, I did change one thing, I managed to make my pixel launcher a system app, that might have been fixing most the issues, in case someone else is stuck!
[Essential Phone Guides, News, & Discussion] bavarianblessed:
You made it an system app by adding it to the system\apps folder and changing permissions?
[Essential Phone Guides, News, & Discussion] avd:
Unlocked bootloader and critical partitions, rooted NMJ51B using TWRP and magisk 14.3, and my debugging and OEM unlocked switches are not greyed out.
[Essential Phone Guides, News, & Discussion] spotmark:
The Oreo beta has been fine. Since installing it, I haven't had the urge to flash anything else. Looking forward to the next beta or an official build. Whatever they want to release. I rooted it using the old method, no problem.
[Essential Phone Guides, News, & Discussion] nicoseb:
No, I did not want to do it manually because I had never done it before (albeit I'm on Linux so nothing weird haha).

After installing magisk manager, I resintalled magisk from there because I was never prompted for root permissions in other apps (just idling). I then reinstalled "/app/system/" from the Google store as well as put a few magisk modules including "App Systemized".

The latter would not installed at first, and the former would tell me that the switch from user to system app failed.

After reboot, I deleted the /app/system thinking it failed, but then realized that the magisk module had now been installed and that my launcher was recognized as a system app.

Anyway, longer answer than necessary but should have all my silly steps...
[Essential Phone Guides, News, & Discussion] 12paq:
On Oreo beta 1, if you get random boot loops that go to lock screen opening and then crashes again and again, hold the power button down until the phone goes off. Then it will do a full reboot and run fine for awhile. This happens to me every day or two. No biggie it's a beta.
[Essential Phone Guides, News, & Discussion] ad78:
I think i just resolve my issue on oreo rooted and random reboots.

Erase by doing fasboot -w then flash-all oreo

Load twrp, adb sideload magisk then load oreo boot.img

Coolstuff!

I tried LOS and its not there yet. The NMJ51B is god damn battery eater!
[Essential Phone Guides, News, & Discussion] JoshuaUB78:
I thought my battery was sucking it down faster!

On the update with Root (stock rooted)

---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------

Anyone changed up the stock kernel settings?
[Essential Phone Guides, News, & Discussion] nicoseb:
Well, my point was that I have not had a single crash like that since my launcher has been turned into a system app... Just good for thoughts ;)
[Essential Phone Guides, News, & Discussion] 12paq:
Good to know!

Edit: No go. I made Nova Launcher a system app and still have crashes. Logs point to system ui. Reported logs to Essential, again.
[Essential Phone Guides, News, & Discussion] Maxr1998:
I experienced exactly this issue on my 6P on 8.1 beta and 8.1 as well, so seems to be an Android issue actually. Thought before reading this that my 6P is starting to experience the hardware bootloop..
[Essential Phone Guides, News, & Discussion] deepu458:
friends i need some help. I currently installed NMJ51b Build Rooted with TWRP as recovery on Slot B and all working. But when i checked with Slot A it the build is running the NMJ32F build. So i did grabbed the NMJ51b Twrp from the op and flashed it to recovery. So now my recovery on Slot A is changed to TWRP. Unable to Upgrade to NMJ51B Build as i cant sidelaod the ota zip from TWRP recovery.

So please let me know if there is any way of obtaining the Stock recovery so tht i can migrate the Slot A to the latest?

Thanks in advance.
[Essential Phone Guides, News, & Discussion] avd:
The unofficial dump thread has a flashall file that would put stock on both stocks.
[Essential Phone Guides, News, & Discussion] q13017:
im on oreo beta1 and trying to root my phone. Buy when I boot to twrp the touch screen not working. Some one can help?
[Essential Phone Guides, News, & Discussion] avd:
Where did you get TWRP? the TWRP linked in the OP should work.
[Essential Phone Guides, News, & Discussion] chiadrum:
Ok, I am confused. Unlocked the bootloader no problem and then I followed the steps outlined above where I don't see anything about flashing a factory image. I installed Magisk twice and multiple root checkers say no root. So there is a system image that needs to be flashed before Magisk? I have barely slept working 2 days straight. Maybe I don't see what is obvious in from of my face? At the very end Magisk throws an error, couldn't mount system. Sorry if I am missing the obvious but like I said,delerium is setting in!
[Essential Phone Guides, News, & Discussion] deepu458:
Thx for the reply.but just wondering will tht flash all script wipe the data completely or just flash the system partition only?
[Essential Phone Guides, News, & Discussion] ad78:
Use the old method. And make sure you have the oreomagisk boot.img
[Essential Phone Guides, News, & Discussion] mobileman88:
Is it the step 4 of the old method to flash oreomagisk boot.img ?

tried flashing oreomagisk.img before flashing Step1 and also did it in Step4. Don't have touch in TWRP. This slot_a and b stuff is still confusing to me
[Essential Phone Guides, News, & Discussion] Eric_Sheill:
Flash oreomagisk.img in fastboot and reboot to rooted Oreo. Don't flash twrp and try to flash magisk, that's what I did. Thanks XDA crew!
[Essential Phone Guides, News, & Discussion] mobileman88:
How do I get TWRP working then? I kinda like the idea of getting working Nandroids which I can restore. Or is it no longer applicable to the new devices like this?

I can't seem to see the Magisk using the methods below :

Method A

1. Flash TWRP to boot

2. Boot into TWRP

3. No touch working

4. adb sideload magisk 14.3

5. flash oreomagisk.img to boot

6. Reboot

A - Can't seem to see MAgisk at all. The flashing seems to be going to slot A which is the active slot

Method B

1. Flash oreomagisk.img to boot

2. Flash TWRP to boot

3. Boot into TWRP

4. Touch still does not work

5. adb sideload magisk 14.3

6. flash oreomagisk.img to boot

7. Reboot

B - Can't seem to see MAgisk either. Still flashing and booting slot A

Method C

1. Flash TWRP to boot

2. Boot into TWRP

3. No touch working

4. adb sideload magisk 14.3 *hacked by invisiblek

5. flash oreomagisk.img to boot

6. Reboot

C - Can't seem to see MAgisk at all. The flashing seems to be going to slot A which is the active slot

7. Reboot to slot b

C - Can't seem to see MAgisk either.

Method D

1. Flash oreomagisk.img to boot

2. Flash TWRP to boot

3. Boot into TWRP

4. Touch still does not work

5. adb sideload magisk 14.3 *hacked by invisiblek

6. flash oreomagisk.img to boot

7. Reboot to slot a

D - Can't seem to see MAgisk either. Still flashing and booting slot A

8. Reboot to slot b

D - Can't seem to see MAgisk either.

Not sure what I am doing wrong. I want to have MAgisk and TWRP working on the Oreo preview. Anyone able to help me here?
[Essential Phone Guides, News, & Discussion] vergilbt:
Dumb question: did you install Magisk manager as an app as well?
[Essential Phone Guides, News, & Discussion] mobileman88:
Isn't it part of the 14.3 installer? Forgive me if I did something dumb. Have not had to install Magisk from scratch for a long time now.
[Essential Phone Guides, News, & Discussion] vergilbt:
https://www.apkmirror.com/apk/topjo...se/magisk-manager-5-4-3-android-apk-download/
[Essential Phone Guides, News, & Discussion] aer0zer0:
See OP
[Essential Phone Guides, News, & Discussion] vergilbt:
[MENTION=5447216]aer0zer0[/MENTION] [MENTION=2385005]invisiblek[/MENTION]

great job... tried it and all is running fine!

go ahead!
[Essential Phone Guides, News, & Discussion] mobileman88:
Good work! Thanks. Just one small item here. Do I need to mount System RO or RW? Thanks.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Honestly not sure if it matters. I check the box to mount it, but I'm not entirely certain. You do have to mount system manually in order to keep the error from popping up that doesn't matter anyways
[Essential Phone Guides, News, & Discussion] mobileman88:
Thanks. Shall try to mount it read only first if it works

---------- Post added at 09:13 AM ---------- Previous post was at 08:46 AM ----------

Read only did not seem to work. Mounting it writable and it works. However, I forgot to enable unknown sources before flashing Magisk and Settings keeps FC whenever I try to enable that setting. Not sure if I need to reflash system all over again.
[Essential Phone Guides, News, & Discussion] aer0zer0:
Huh?
[Essential Phone Guides, News, & Discussion] mobileman88:
Managed to delete the cache of the settings app which fixed "Settings" app having continuous FC. Seems good so far. Doing a Titanium restore now
[Essential Phone Guides, News, & Discussion] aer0zer0:
I'm surprised it would have broke settings

What magisk?
[Essential Phone Guides, News, & Discussion] brqndon:
Quick noob question: why can't I access TWRP from the recovery menu? It always defaults back to the Android bot laying down with the red square.
[Essential Phone Guides, News, & Discussion] mobileman88:
Not broken. Just corrupted cache causes it to fc. Happened twice after a couple of reboots. Using Magisk 14.3
[Essential Phone Guides, News, & Discussion] avd:
If TWRP is installed, it is not in the active slot.
[Essential Phone Guides, News, & Discussion] mobileman88:
What's the best way to wipe data without erasing all the data on the SD card?
[Essential Phone Guides, News, & Discussion] brqndon:
Another noob question: how do I make it so that it is in the active slot? Thanks in advance.
[Essential Phone Guides, News, & Discussion] mobileman88:
Go to fastboot mode

You can do either of the following :

fastboot set_active [a,b]

fastboot set_active a <----- switch to slot a

fastboot set_active b <----- switch to slot b

fastboot set_active other <------- switches to the other slot

Then just do a

"fastboot reboot"
[Essential Phone Guides, News, & Discussion] brqndon:
[MENTION=1306570]mobileman88[/MENTION], is this immediately after performing "fastboot flash boot twrp.img"?
[Essential Phone Guides, News, & Discussion] 1Krima:
Beta 2 for Oreo rolling out now. Does anyone know if we have to uninstall Magisk before installing the OTA?
[Essential Phone Guides, News, & Discussion] gk1984:
You will at least need to return to the stock recovery and boot image, which will remove Magisk. But I don't see TWPR for Beta 2 yet (it takes time).
[Essential Phone Guides, News, & Discussion] 1Krima:
I ended up just sideloading Oreo Beta 2.

Magisk isn't working with patching to stock boot.img. I hope to get root back soon.

If anyone has a working Oreo beta 2 boot.img, that would be great.
[Essential Phone Guides, News, & Discussion] mobileman88:
no need to do that, just select recovery using your Volume buttons and press power to boot to it. It's always default to the current slot.

---------- Post added at 07:37 AM ---------- Previous post was at 07:36 AM ----------

bummer.... could be the Treble changes in the changelog.

How did you sideload it and what does the version and updates show in Settings?
[Essential Phone Guides, News, & Discussion] brqndon:
The problem is, I'm always prompted with the "No command" message when I attempt to boot into recovery. I've followed the directions in this thread and I have root just fine, but I'm just trying to have TWRP without having to sideload each time.
[Essential Phone Guides, News, & Discussion] wolfu11:
[MENTION=4550123]bmg1001[/MENTION] procedure for Oreo B2 work great thank you
[Essential Phone Guides, News, & Discussion] kirschdog1:
Where is this located?
[Essential Phone Guides, News, & Discussion] mobileman88:
Wouldn't taking the B2 OTA while in B1 (booted to A) get B2 flashed into slot_b leaving slot_a with B1? Sorry to sound dumb. Still trying to figure this slot thing out.

Thanks

---------- Post added at 09:36 AM ---------- Previous post was at 09:35 AM ----------

From what I have been reading thus far. I think this is the only way as Recovery is an image within the main boot image.
[Essential Phone Guides, News, & Discussion] SuperNickyP:
Just curious, why do we need a modified boot image for this? (Why not just use the dumped stock boot image?)

EDIT: Now I understand, they really should give us that command if they can. I know that it should work, but the sound of having to flash twrp to the boot partition makes me a nervous wreck after what I did to a samsung device... I accidentally flashed twrp over the boot image on THAT device.
[Essential Phone Guides, News, & Discussion] bmg1001:
The modified boot image is just the stock boot image with the patches that Magisk applies to it when you flash it normally. The reason you need to flash it afterwards is because, in order to actually flash Magisk itself, you need to overwrite the boot image with TWRP (since the Essential bootloader doesn't support the "fastboot boot" command).

There are only two other ways I know of to flash Magisk. One would require you to use a USB OTG mouse to control TWRP so that you could flash the stock boot image from within TWRP, so that Magisk patches that and not the TWRP image that is on the boot partition, and it also flashes the correct boot image at the same time, but since this requires a USB OTG adapter and a USB mouse, it isn't useful for many users.

The other way is by switching to the opposite partition of the system you want to root (A/B partitioning), flashing TWRP, booting into it and using "dd" to make a copy of the boot image of the original partition you wanted to root, switching back to the original partition, flashing TWRP, using "dd" to move the copy of the boot image back into the boot partition (this is the risky part), and then flashing Magisk. This is way too risky and complicated for most users, but you don't have to wait for an updated boot image though. This would also require you to flash the second partition back to stock though to accept OTAs.
[Essential Phone Guides, News, & Discussion] mackentosh:
I can't get the past the 1st step, I keep getting cannot load

fast boot flash boot twrp.img does it go in exactly like that?
[Essential Phone Guides, News, & Discussion] bmg1001:
Make sure fastboot is one word. Also, "twrp.img" is meant to be the full directory of wherever the TWRP image is located on your PC. If its not already named as such and not in the same folder as your fastboot binaries, then it must be the full directory. On my PC, it would look something like "fastboot flash boot C:\Users\bmg1001\Desktop\twrp-mata2.img"
[Essential Phone Guides, News, & Discussion] spotmark:
Also, when you downloaded TWRP is it named twrp or twrp-mata? If it's named twrp-mata the command should be, fastboot flash boot twrp-mata.img. Or rename it so it's just twrp.img. Then the command you're using will work.
[Essential Phone Guides, News, & Discussion] mackentosh:
Thank you so much that did the trick

---------- Post added at 10:13 PM ---------- Previous post was at 09:28 PM ----------

I've fell in love with this phone all over again. Thanks guys for all your hard work
[Essential Phone Guides, News, & Discussion] drocny87:
What were the 2 commands u typed for system and boot
[Essential Phone Guides, News, & Discussion] jorgis1:
Noob question here... Is TWRP being sideloaded itself? or is it replacing stock recovery? So going back to stock loses TWRP correct?
[Essential Phone Guides, News, & Discussion] spotmark:
Fastboot flash system system.img and fastboot flash boot boot.img

In the system dump that I have, the two files don't have .img attached to them, so you just have to add it before flashing.
[Essential Phone Guides, News, & Discussion] mrcooter:
return to stock

If we use the flash all bat in the return to stock zip, does that wipe data?
[Essential Phone Guides, News, & Discussion] SuperNickyP:
I'm not sure. It should give you a choice based on experience with google factory images, but you should check by opening it up in notepad. Its really easy to understand what the batch script is telling fastboot to do.
[Essential Phone Guides, News, & Discussion] drocny87:
​

downloaded the system dump for the build i am on now, took out the 2 files system and boot and added img to the end. loaded twrp and typed in the command you mentioned and it hangs on waiting on device. any idea why that would do that?
[Essential Phone Guides, News, & Discussion] bmg1001:
Fastboot commands only work in the bootloader, adb commands work in the system or TWRP.
[Essential Phone Guides, News, & Discussion] AxxPyrtlexx20:
You will also need the appropriate modified boot image for your current build.

What if your build number is NMI81C, what one would I download?
[Essential Phone Guides, News, & Discussion] drocny87:
in twrp i would type -- adb flash system system.img?

in bootloader -- fastboot flash system system.img?
[Essential Phone Guides, News, & Discussion] bmg1001:
You can't flash images in ADB, you must use Fastboot.
[Essential Phone Guides, News, & Discussion] drocny87:
i was able to flash the boot.img but when i do system.img i get an "invalid sparse file format at header magi"
[Essential Phone Guides, News, & Discussion] AxxPyrtlexx20:
Or is there no supported one yet for my build number.
[Essential Phone Guides, News, & Discussion] cz829x18:
That happened to me, I just waited and it started flashing the image.
[Essential Phone Guides, News, & Discussion] drocny87:
thanks for the info. how long did it take?
[Essential Phone Guides, News, & Discussion] wolfu11:
in the op
[Essential Phone Guides, News, & Discussion] kirschdog1:
I have not been able to root b2 with the method in the op unfortunately.
[Essential Phone Guides, News, & Discussion] aer0zer0:
works perfect, whats wrong?
[Essential Phone Guides, News, & Discussion] kirschdog1:
So I'm on Oreo b2 but am confused how to get magisk 14.3 working I flashed it through twrp right after stock boot image but no magisk shows up?

Ok after I flash all.bat for latest b2 what is the next step? Boot twrp and flash boot image and then magisk?
[Essential Phone Guides, News, & Discussion] aer0zer0:
download the twrp-mata 11 from the op, then flash the twrp, once twrp has booted, copy both the stock boot image from the OP, and the magisk from the beta thread (14.3 beta, dont use the invisblek hax 14.3, it intentionally flashes to the wrong slot (which is what i think happened to you). flash the stock boot.image, then flash the 14.3 beta (again not the hax) and reboot, you should be g2g

this magisk -------> https://xdaforums.com/attachment.php?attachmentid=4302781&d=1508010356

also, before flashing the magisk in twrp, manually mount system, should prevent the unable to mount system error at the end (doesnt matter though)

---------- Post added at 10:42 PM ---------- Previous post was at 10:35 PM ----------

you good?
[Essential Phone Guides, News, & Discussion] trunzoc:
The new Oreo process mentions that TWPR will be.uminstalled when all is done.

Is this a temp thing until a new version of TWRP becomes available, or are we just going to have to repeated the TWRP/magisk/stock whenever we need TWRP?
[Essential Phone Guides, News, & Discussion] aer0zer0:
so the recovery is built into the boot.img, and twrp we have (while being fully functional on oreo) is based on N kernel source. so it wont boot your oreo rom. which is why we have to reflash the oreo stock kernel on the fly, then patch it with magisk to get root.

So the case is we need the twrp, repackaged into the boot.img every single time there is an update.

At least we have fully working twrp :)
[Essential Phone Guides, News, & Discussion] kirschdog1:
Deleted. Waiting for boot up to see if magisk I should there? We good thanks aer0zer!!
[Essential Phone Guides, News, & Discussion] aer0zer0:
yea, that was what my last edit was, need to mount system manually prior to flashing magisk to make that go away, its fine though.

oughhta be
[Essential Phone Guides, News, & Discussion] okgnew:
Does Beta2 work with magisk 14.5?
[Essential Phone Guides, News, & Discussion] kirschdog1:
Thanks..any mods working on Oreo you recommend? I'm really missing viper