Both versions have an unlocked bootloader.
I have the Sprint variant and I'm running Oreo Beta 2, rooted with Magisk.
Both versions have an unlocked bootloader.
I have the Sprint variant and I'm running Oreo Beta 2, rooted with Magisk.
Can't believe I didn't even think to check for an SDK update. IT ended up working. Just weird how my brothers 6P and parents 5x's are on Oreo and were recognized just fine.
Yes because that funny code is for the essential phones, so you need a updated config file that has the phone manufacturer code that's only been out for 4 or 5 months.
Sent from my PH-1 using XDA Labs
So reflash ROM and then Magisk after booting once? Or do I need to extract boot.img first?
aer0zer0
Recognized Contributor
You might also need a haxd version of magisk, checkout the discord group, it's floating there. On stock, like OB2, Magisk 15.2 needs to be installed after initial boot if clean installed
Flash ROM, then boot it. Don't set up password or FP yet. Look for the boot.img in the Lineage thread or discord. Otherwise u will have to extract it using method in OP. Then u can reflash twrp, flash boot img, and then Magisk 15.2 (no need for the haxd version).
No, wiping is not necessary. For OB1 or 2, you can just unzip the stock dump (from the back to stock thread in Roms), and copy the boot.img from that folder to ur phone.
Unlocking bootloader and/or critical partitions will wipe device
Sent from my PH-1 using XDA Labs
Sent from my PH-1 using XDA Labs
aer0zer0
Recognized Contributor
The trick is to always leave them unlocked if you are not stock. Even unlocked stock let's you flash anytime we want with no wiping.
Sent from my PH-1 using XDA Labs
Sent from my PH-1 using XDA Labs
Last edited:
Considering there is only one hardware device.
With the practice of Sprint having it's own firmware revision, the rest of the world having another, and being able to sideload Oreo beta unrooted, we have a lot of fragmentation.
At least everyone is using magisk as the rooting solution.
Sent from my PH-1 using XDA Labs
---------- Post added at 02:01 PM ---------- Previous post was at 01:31 PM ----------
Actually the biggest fragmentation is in the aftermarket camera software.
Sent from my PH-1 using XDA Labs
I successfully got twrp to boot up, but it's asking me for the password. As far as I know I did not set a password on this thing. I did set a PIN for the screen, but that does not work.
Suggestions?
Suggestions?
Last edited:
It is stock. I installed all the updates when I first turned on the phone. Build is NMJ88C.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
110WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Useful and important general information can be found in the second post here.
NOTES
1. If you flash the TWRP Installer when you've already got Magisk installed, your device will keep booting to the recovery. You should be able to fix this by just simply reflashing Magisk.
2. If you have TWRP installed via the TWRP Installer, you will not be able to install stock OTA updates. You will have to reflash the stock boot image for whatever build you're running beforehand.
3. The prebuilt TWRP image may not have touch functionality if you're using the September 2018 Update or newer. Patching the boot image, however, for these builds with the TWRP Installer will allow touch to work flawlessly. Here is a pre-patched September 2018 Boot Image with TWRP. It should also work with builds newer than September. Since it's based off the September 2018 update, I suggest not using this as your main boot image but rather just as a replacement for the pre-built TWRP image from the official TWRP thread.
4. Simple "flash and forget" boot images pre-patched with Magisk and TWRP are provided by @aer0zer0 and are available here. They are based on ianmacd's variant of Magisk. If you are running stock, you can flash these boot images to get root and TWRP instead of following the guide to patch it yourself. Here is January's.
If you don't care about TWRP and simply want to just root your device, you can just simply patch the boot image for your ROM with the Magisk Manager and flash it in fastboot withThe link to the boot images for most stock builds can be grabbed from my Google Drive link in the second post or from the back-to-stock zips.Code:fastboot flash boot patched_boot.img
REQUIREMENTS
An unlocked bootloader
Working adb and fastboot environment, along with knowledge on how they work.
The latest build of TWRP along with the TWRP Installer. Read Note 3 above beforehand.
1. Download the latest build of TWRP and the TWRP Installer. Transfer the TWRP Installer zip to your device.
2. Reboot your phone into fastboot. Once in fastboot, change your device's current slot using the commandIf the command above doesn't work for you, use fastboot getvar current-slot followed by fastboot -aX, replacing "X" with the slot opposite (a or b) from your current slot.Code:fastboot set_active other
3. Once your device's current slot has been switched, flash the TWRP image you downloaded earlier using the commandDepending on your version of fastboot, the above command might not work either. In that case, you can enter the following command, replacing "X" with your current slot (a or b).Code:fastboot flash boot twrp.img
Code:fastboot flash boot_X twrp.img
4. Once TWRP has been flashed, boot into the recovery.
5. Once you have booted into TWRP, simply flash the TWRP Installer zip.
6. Once you have finished flashing the TWRP Installer zip, boot to recovery on the OPPOSITE slot. You can do this from TWRP by going to "Reboot", then selecting the opposite of the current slot (if on A, select Slot B. If on B, select Slot A), then select "Recovery." You can also do this through fastboot by running the same command from step 2.
7. Once you have booted back into TWRP, simply flash the Magisk zip and you are now good to go! Feel free to flash anything else like kernels while you're at it.
8. Reboot. :good:
NOTE: TWRP WILL remain installed on your device so long as you reflash the installer zip after every update.21https://www.androidfilehost.com/?fid=11410963190603865614
December patched boot.img (stock, TWRP, ianmacd 1203 17.4 magisk
Enjoy
20Important Information for the Essential PH-1 can be found here. Keep it bookmarked.
Tips on updating via OTA after rooting can be found here.
In the case that you mess something up on your device, you may find it helpful to revert back to stock with the unofficial factory images graciously provided by @invisiblek and @aer0zer0 over here.
Official TWRP XDA Thread for the Essential PH-1
Join the Essential PH-1 Discord Server! -- Lots of cool people here!
Join the Essential PH-1 Development Telegram Channel!
Stock Boot Images for most builds can be found at my Google Drive link here.
Have a Red Verity Warning when booting your device? Click here.
If the link to the boot.fix.red image isn't working, you can also find it here or in my Google Drive link in the first post.
Essential Phone (PH-1) Partition Layout
Dumping Boot Images
extractTarFork() error when restoring data from a TWRP backup
16https://www.androidfilehost.com/?fid=1322778262904018340
patched boot.img
stock, magisk, twrp....
Enjoy15https://www.androidfilehost.com/?fid=11410932744536995931
nov_patched_twrp_magisk_stock boot.img is up
Enjoy
