Related
Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
MarSOnEarth said:
Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
Click to expand...
Click to collapse
First, TWRP doesn't work well with latest stock ROM (QQ1A.200105.032), if you'd like to use TWRP, you should use one level down (QQ1A.200105.007)
Second, there's no more upgrade for this ROM, Essential stopped support it, and Feb update was the last one.
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
Click to expand...
Click to collapse
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
chanh2018 said:
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
Click to expand...
Click to collapse
Ah, yes! My interest in 4.4.166-stock-twrp-mgk181 image is because, a) I failed to get root with Magisk, and b) this is a `fastboot` image that's already rooted (notice the mgk181 part of the name), BUT because it was made in January of 2019, I think (if it does, and I know too little to know that) it contains older version of Android, hence the question about whether I will be able to update from it.
Thanks
MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?).
Thanks
Click to expand...
Click to collapse
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
MarSOnEarth said:
I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
Click to expand...
Click to collapse
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
IronRoo said:
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
Click to expand...
Click to collapse
True. Eventually, a proper custom recovery, like TWRP, might be essential (har, har) years down the road (although I only now am coming down from a Moto X (first gen, 2013) that between AFWall and XPrivacy I managed to keep on stock firmware all along), but now I need to get this phone prepped up for daily use, and that means getting root first of all (and from kt-Froggy's note I shall... I see now where I goofed).
I appreciate your input. Thanks!
kt-Froggy said:
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
Click to expand...
Click to collapse
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
MarSOnEarth said:
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
Click to expand...
Click to collapse
That was my suspicion from how I read your post... ? Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
kt-Froggy said:
That was my suspicion from how I read your post... Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
Click to expand...
Click to collapse
OK, that worked splendidly. Thanks!
Hi,
just got a HTC U11 Life phone running already Android 10.
I read and serached the forum for quite a while now and I couldn't figure out how to root the phone
According to this there is no working TWRP, but then again I find comments from people who say got TWRP working (here for instance).
In this HowTo Collection there are instructions, but I can't find the referenced patched image
Now I'm wondering if the problem is that my phone is already on Android 10 or did I just miss some important things?
Help appreciated!
Greetings from Greece, is there anything new? with htc u11 life running already Android 10
there is twrp recovery and root for device ?
Οne more question please, the device with android 10 has sense home ui ?
thank you very much and sorry for my bad English.
[A10][TWRP]WWE Google One edition
Hello guys, after so time as i start working on proper twrp for my HTC u11 life, which working on android one 10, it's finally done ✅ Os - 4.73.401.2 It's completely possible to make backup/flash *System *System_Image *Vendor *Vendor_Image *Boot...
forum.xda-developers.com
Root by flashing boot.img by magisk/lygisk.
@Trymitius great news bro ,thank you very much.
Btw your device probably (dont know for sure, cuz didn't test yet) need to be unencrypted. I've provide correct path in fstab for FBE but as i mentioned before it wasn't tested. Just in case, if you need to decrypt your devices, simply edit fstab.qcom + fstab.htc which you can find in /vendor/etc and change "filencryption=" to "encryptable" at system mounting line.
Just be careful, after that you'll need to reboot your device and wipe data or userdata partition. If you going to have any issues about/system partition you can fix it by editing fstab.qcom + fstab.htc and change "ro" --》》 "rw" at /system line.
thanks trymitius but I haven't bought the device yet. I believe in a few days it will be in my hands
sorry for my bad English.
I have a OnePlus 7 Pro running on OxygenOS 10. I want to use the Dialer app that comes with OxygenOS 11, but don't want to upgrade my complete OS to 11. I made a thread in the OP7P forums but no one has answered it yet.
I am rooted with Magisk, so I figured I could simply replace system priv-app apks (namely TeleService.apk, Dialer.apk, TelephonyProvider.apk, Telecom.apk) with the OOS 11 ones but it is not working. I am a noob when it comes to understanding permissions and sysconfig xml files, and any other technical files that also need to be edited/replaced along with the apk.
Can anyone tell me what is the standard procedure to do such a task?
Of course, a detailed answer is greatly welcomed, but even a push in the right direction would help me a lot.
Hi,
I have a Samsung S9+ (star2lte) on which I installed e os 1. This is essentially Lineage with a some tweaks and e Recovery. I would like to root my device, so that I can install AFWall+. Open to alternatives, but most don't offer a comparable deal in term of privacy, security and sideeffects. I will probaby also need MAgisk to hide root from banking apps. So I decided to go for Magisk, which I have used in the past as well.
So there is no lack of guides when you search for this topic. However, noone mentions e os. And this twist seems to matter. While trying to follow various guides (I have by now started from factory a couple of times, as I almost bricked my device...)., I came across a lot of errors, which were not mentioned in either guide. The install would fail, sometimes messing up the entire installation, so that I had to start from scratch.
I think I identified one of the main issues, which happens to be the recovery. The e Recovery won't install the proper magisk boot image. Well, unless there was another issue in the background, but I also found hints towards TWRP being needed to install magisk. So I installed TWRP latest version, which worked fine. Then I tried to install magisk boot image - and it failed. /data could not be mounted, apparently this relates to the encryption of the file system.
I'm also about unclear on the role of Odin (latest). I understand I need it to flash my Samsung device, e.g. with TWRP. I'm somehwhat unclear on the various filetypes one can flash (AP, BL, CSC,...). So I strictly adhere to the guides for this. MEaning, I have never tried to flash Magisk via Odin - is that possible? Does it make sense? How?
One sideeffect of the guides I found would be, that TWRP is installed as recovery. In an ideal solution, I would like to return to e os recovery, so that everything is as close to the orignal setup as possible, except with root (and possibility to hide this for specific apps).
As I have spent two days backing up, flashing, reading guide, reading more guides and still failing all the time with results which forced me to redo everything from vendor image - I finally resorted to asking for help here. Can someone please guide me though the process of installing magisk?
Versions:
Samsung SM-965F DBT (star2lte)
e os 1.0-q-2022052618889-stable-star2lte
TWRP 3.6.1_9_0-star2lte
Odin 3.14.4
Magisk: Latest App.
Best,
YeOldHinnerk
same problem with a oneplus 5, i updated to e/os/ 1.0 and no more magisk/root...i try to update with magic manager (magisk 25), it asks a patch but not proposing install...
You need to extract the boot.img from e. Download the tar/zip, extract and locate the boot.img within. Copy that somehhere on your phone and feed it to magisk.
TWRP will not see the file by magisk since the file system is encrypted, see above.
Btw encryption is a must-have for me, for security reasons and my apps for work won'T run without (Citrix Secure Hub).
it's working Thks a lot !
Was intended as llooking for help here - but glad I could help too
Hi @YeOldHinnerk & @pommedefrance , I wonder if you'd mind taking a look at my post:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Same issues but with Samsung S7.
Any pointers?
Thx
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
You can create dumps of your partitions using ADB shell in system; TWRP is not required to do this.
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
A very similar thread with the same topic has been discussed a few days ago - you can check here
Anyone can compile TWRP - it's opensource. Pixel 6+ owners are unlikely to get an official build from TWRP since it requires a volunteer to maintain the repo, deal with bug reports, etc.
It's recommended to simply compile the image on an individual basis (you really don't want to rely on a third-party supplied image when you have no way of knowing whether it's safe or not). Compiling isn't a difficult process, but does require an hour or two of reading TWRP's and Google's applicable developer pages, along with ~30 - 60 minutes of set up time on a PC/laptop (I prefer to compile within an Ubuntu VM, but I believe it can also be done in Windows' WSL).
robroy90 said:
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
Click to expand...
Click to collapse
They still haven't finished official support for Android 12. Since recovery resources on A12+ are located in vendor_boot, bigbiff is trying to figure out a decent way for TWRP to live there, at least as far as the Pixel 5 is concerned. Not sure what other obstacles may be present on the Pixel 6 series and above.
nooted1 said:
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
Click to expand...
Click to collapse
Hey thanks for this! How did you flash just the recovery partiton on the Pixel? I am an old hand with Odin on the Samsung devices, but Google official devices are still new to me. Will the StagOS recovery recognize an external USB-C flash drive for storage?
s3axel said:
A very similar thread with the same topic has been discussed a few days ago - you can check here
Click to expand...
Click to collapse
Thank you, I went over there and read everything. Much appreciated!