Hello all,
I understand that TWRP on our devices is built on the Nougat kernel (hence why we can't boot with it) because the touch-screen doesn't work in TWRP when building it with the Oreo kernel (and presumably the Pie kernel -- I don't know if anyone has tried).
However, even if it still has to be built from the Nougat kernel like the current version of TWRP we are all using, could someone who has the skills and knowledge build the latest 3.2.3-1 version, which was just released a few days ago for the Pixels, for our Essentials? It has the capability to unencrypt data in Pie, regardless if you have a lockscreen pattern, pin, or password (along with many other new features and fixes since 3.2.1-0 was released), so it would finally no longer be necessary to delete all fingerprints and lockscreen pattern/pin/password before going into TWRP and then having to restore them all back after leaving TWRP and then teaching all apps the changed fingerprints.
Much, much thanks in advance to anyone who can do this!! I know that anyone who knows how to build a ROM could build TWRP in almost no time at all.
Thanks again,
Chris
and if the new TWRP can flash Magisk to both slots we wont need stock kernel when rooting. Magisk 17.1 has the ability to flash to both slots, but current TWRP patches only active slot when flashing Magisk zip.
supposedly some devs are working on it. Seems like it'll be a while
https://forum.xda-developers.com/showpost.php?p=77421949&postcount=16
Not to jump too far ahead, but a Developer and friend I am working with wants to build an updated TWRP, especially now that Pie is out, we could use those Treble and Pie fixes.... He is also working on a ROM, but we are at the early stages, and he has an Essential and I got mine today. He was finishing up on another Project at the moment, now that I received my Essential we can get things going and work our way, all the way to Official Perhaps? Time will tell...
AndroidDevices said:
Not to jump too far ahead, but a Developer and friend I am working with wants to build an updated TWRP, especially now that Pie is out, we could use those Treble and Pie fixes.... He is also working on a ROM, but we are at the early stages, and he has an Essential and I got mine today. He was finishing up on another Project at the moment, now that I received my Essential we can get things going and work our way, all the way to Official Perhaps? Time will tell...
Click to expand...
Click to collapse
Simply awesome to hear that! Seriously looking forward to what you guys release in the future!!!
starcms said:
Simply awesome to hear that! Seriously looking forward to what you guys release in the future!!!
Click to expand...
Click to collapse
I am hoping we get started on TWRP this weekend. My friend is adamant about getting us a new Recovery or an update one at the very least, but i believe TWRP is the 1st thing on our to do list.... :good: With September breaking our current, outdated Recovery, made it a Priority....
Those of you who came to the channel, we thank you for your support!
Telegram Essential PH-1 Dev Group : https://t.me/EssentialPH1DEV
By the way, we have another Mata Dev working with us!
AndroidDevices said:
I am hoping we get started on TWRP this weekend. My friend is adamant about getting us a new Recovery or an update one at the very least, but i believe TWRP is the 1st thing on our to do list.... :good: With September breaking our current, outdated Recovery, made it a Priority....
Those of you who came to the channel, we thank you for your support!
Telegram Essential PH-1 Dev Group : https://t.me/EssentialPH1DEV
By the way, we have another Mata Dev working with us!
Click to expand...
Click to collapse
Things are worse than I thought. I didn't use TWRP to root the September release. What exactly did September break on the outdated TWRP we currently have available?
Thanks again in advance for getting us Mata users an updated TWRP!!
starcms said:
Things are worse than I thought. I didn't use TWRP to root the September release. What exactly did September break on the outdated TWRP we currently have available?
Thanks again in advance for getting us Mata users an updated TWRP!!
Click to expand...
Click to collapse
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
AndroidDevices said:
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
Click to expand...
Click to collapse
That's bizarre. I thought that was specifically the reason TWRP for the Essential is built on a Nougat kernel, so that the touchscreen would work in TWRP. I was told if it was built on the Oreo kernel (this was before Pie was released), so that we could boot with TWRP installed, the touchscreen wouldn't work in TWRP.
I don't know how the September update (or any ROM) could stop the touchscreen from working in the existing, old TWRP version we have. I thought you were going to say it couldn't mount /system or /data or something to that effect with September. I'll have to try it myself and see.
Regardless, still really looking forward to what you and your team come up with! It'll be great to have an updated TWRP version for the first time in a year. And being able for it to unencrypt Pie (and possibly being able to boot with it installed like on the Pixels) will be a Godsend.
starcms said:
That's bizarre. I thought that was specifically the reason TWRP for the Essential is built on a Nougat kernel, so that the touchscreen would work in TWRP. I was told if it was built on the Oreo kernel (this was before Pie was released), so that we could boot with TWRP installed, the touchscreen wouldn't work in TWRP.
I don't know how the September update (or any ROM) could stop the touchscreen from working in the existing, old TWRP version we have. I thought you were going to say it couldn't mount /system or /data or something to that effect with September. I'll have to try it myself and see.
Regardless, still really looking forward to what you and your team come up with! It'll be great to have an updated TWRP version for the first time in a year. And being able for it to unencrypt Pie (and possibly being able to boot with it installed like on the Pixels) will be a Godsend.
Click to expand...
Click to collapse
In order to have TWRP boot and have it installed, we actually need a TWRP.img to Fastboot Boot into Recovery. At that point you would flash your ROM and then there is a 2nd TWRP required that is a zip file called an installer. This is what allows you to boot into recovery from either the hardware power and volume button, or a standard Reboot to Recovery without having to use Fastboot. So again, (2) TWRP files are needed, a boot img and a zip installer. 1st we need to get the boot img working properly and then the installer.
Also, I was informed there is another DEV working on TWRP. Hopefully we can put 2 and 2 together and produce the proper Recovery.
I will update this thread as things get accomplished, and then hopefully all said and done and we can create an Unofficial TWRP thread.
I hoped, now that prices came down on this phone people would jump on it and development picking up. But even the current state seems slow.
I wish we had a nice working TWRP already, and as far as a ROM being mentioned, oh how we need some ROMS that don't have Gapps preinstalled.
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
hmm
AndroidDevices said:
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
Click to expand...
Click to collapse
It was not a TWRP issue but an issue with the Sept update. Some files were left out and the flash left the touch screen dead. I had the issue and just had to flash tow additional files that Essential issued in their flash download.
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
Can you choose options or screen frozen? Because we know it boots and options can be chosen with the use of a OTG mouse...
*edit*
Remember guys, TWRP11.img still works for the August Factory Image as well as anything before August...It is only the September Factory Image is the only build at this time, that TWRP is frozen FYI
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
Awesome! So glad this is gaining some traction! What kernel/boot image is this based on? Nougat, Oreo, or Pie?
Do you have an alpha or beta 3.2.3 TWRP boot image that you could share?
Also, just FYI, 3.2.3-1 was the version made specifically for the Pixels that was just released about a week ago to allow lockscreen pin/pattern/password decryption for Pie.
...
Here's the reason why touch stopped working in TWRP. In the September update, the hyp and rpm partitions were updated for the first time ever. This is what broke touch in TWRP. However, to confuse the issue, those who downloaded the September fastboot package when it first came out lost touch in Android, but kept touch in TWRP because Essential failed to update the two partitions in the fastboot download package (the updated partitions were initially only in the actual OTA and the OTA download package). Essential has since fixed their mistake and put the new hyp and rpm partitions in the fastboot download package.
You can't simply go and flash the older versions of those partitions, because even though it will fix touch in TWRP, it will break touch in the September (and newer) versions of Android.
More info here: https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
starcms said:
Here's the reason why touch stopped working in TWRP. In the September update, the hyp and rpm partitions were updated for the first time ever. This is what broke touch in TWRP. However, to confuse the issue, those who downloaded the September fastboot package when it first came out lost touch in Android, but kept touch in TWRP because Essential failed to update the two partitions in the fastboot download package (the updated partitions were initially only in the actual OTA and the OTA download package). Essential has since fixed their mistake and put the new hyp and rpm partitions in the fastboot download package.
You can't simply go and flash the older versions of those partitions, because even though it will fix touch in TWRP, it will break touch in the September (and newer) versions of Android.
More info here: https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
Click to expand...
Click to collapse
So basically twrp needs to be repackaged with the updated hyp and rpm partitions and we should be home free?
stryver said:
So basically twrp needs to be repackaged with the updated hyp and rpm partitions and we should be home free?
Click to expand...
Click to collapse
TWRP needs to be made compatible with the new hyp and rpm partitions. TWRP (or any recovery) lives in the ramdisk in the boot image/partition (kernel). So I don't think it can simply be repackaged with hyp and rpm which are two completely separate partitions.
Related
This is mainly a temporary repost of @rakomancha's TWRP announcement in a new thread. He is the maintainer of this TWRP but has not signed into XDA for a while. There is an updated TWRP that I wanted to share. When he comes back and creates his own thread, I will replace this post with a link to his.
-------------------------------------------------------------------------------------------------------------------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 3S 10 Z500M
The next big step forward for Z500M development is here!
This is the first working custom TWRP recovery for the Asus ZenPad 3S 10 Z500M [P027], based from TWRP v3.2.1.
diplomatic and I had both been working on a port separately, and I offered to test his version. In a few hours we worked out a functional and install-friendly version.
Please NOTE that this is NOT an official TWRP. After this post, I'll be working on making the port official and update here.
ACKNOWLEDGEMENTS
This project, and my own motivation, would not have been possible without the incredible work and input of:
diplomatic, who has been instrumental in propelling Z500M development forward. He worked on the issue of perm root and discovered and revealed important intricacies of the Z500M restrictive bootloader. By the end of Dec 2017, he developed a method to unlock the Z500M bootloader based on his amazing work with the Z380M. With amartolos as his testing assistant, the Z500M bootloader unlocking tool was quickly developed and released Jan 5th 2018.
overkillZ, who in Sept 2017 introduced us all to rooting the Z500M
toineh, who did legwork of establishing temp root by manipulating system permissions & redirecting files through adb. Then he took the boot.img posted by LGiki, explained how to patch it through Magisk and posted the first patched boot image. He also served as a guiding voice on this front.
amartolos, who first attempted perm flashing the patched boot image of toineh's method and worked with diplomatic on the developments afterward, which led us to today. Also has served as a guiding voice.
LGiki, who was the first to post an extracted WW_27 boot image that got things rolling forward
DISCLAIMER
This image has only been successfully tested by me at this point.
Please exercise caution and care when attempting to flash anything to your device.
You are completely responsible for any possible issues or damages resultant from undertaking the following procedures.
That being said, this image and method should be safe.
REQUIREMENTS
ZenPad Z500M tablet, upgraded to Android N
Bootloader Unlocked, using Diplomatic's tool. Tablet should be showing Orange State during initial bootup.
Root with Magisk installed, Permanent Root preferable
BACK UP YOUR INTERNAL USER DATA, in case you need to factory reset
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
Knowledge of adb/fastboot and basic Linux shell
INSTRUCTIONS
Ensure REQUIREMENTS are all met
Ensure to RE-READ all instructions and understand them before starting
Reboot into fastboot mode
do fastboot boot twrp-3.2.1-0-z500m.img, TWRP should boot up in a few seconds. The theme should be blue.
In TWRP, go to BACKUP and back up Boot, Recovery, Data, System and SystemImage. Full backup took me about 10GB of space.
Copy the created TWRP Backup to your PC or an external location for safekeeping
Copy the TWRP twrp-3.2.1-0-z500m.img to tablet storage if not done already.
In TWRP, go to INSTALL, select Install Image and choose the twrp-3.2.1-0-z500m.img. Installation should only take a few seconds.
Unplug from USB and Reboot back into Recovery through the REBOOT menu
If installation went well, TWRP should boot up in a YELLOW theme. From my testing, I'm confident it is functionally the same.
RESOURCES
In this shared folder are
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
version 0.5 of Diplomatic's Unlock Tool
diplomatic's Z500M device source
hxxps://mega.nz/#F!SQlyDapC!XbbW0fftZWFfVx2lmL_JUQ [down, get the file below]
GOING FORWARD
I successfully tested replacement of Magisk with SuperSU. My steps taken were:
"Completely Uninstall" Magisk through the Magisk Manager
reboot directly into Recovery
INSTALL a previously downloaded official SuperSU zip file & REBOOT
I very much enjoyed this process of developing for uncharted regions of Android technologies and I owe all of that to the existence of this forum and the people in it. Next, I am reading up on porting a custom ROM, LineageOS looked very nice. I'll update here with significant progress until I get capability to start new forum threads. Thank you all and enjoy delicious functional TWRP custom recovery on your Z500M for the first time in history. Here's to looking forward to development exploding on this device.
-------------------------------------------------------------------------------------------------------------------------------------------------------
NEW DOWNLOAD
Updated February, 2018
Fixes the yellow color rendering in installed mode
twrp-3.2.1-0-z500m.zip
ADDITIONAL WARNING: At first boot of TWRP, it will ask you if you want to keep system read-only. Touch the Keep Read Only button at this screen and only mount system in read-only mode if you need (rarely needed). This is necessary because of dm-verity and is no different than most Android 6+ devices. Unless you have unlocked your bootloader and installed permanent root with dm-verity disabled, mounting the system partition in r/w mode will make changes to it and your tablet will instantly become unbootable.
This is great. Tempted to try this. thanks for the effort!
Thank you very much, I did this and also switched to SuperSU with no problems!
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
ratus69 said:
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
Click to expand...
Click to collapse
Well, recovery of course. ...because it's a custom recovery.
Hey guys I hope you can help me I had my Z500m partially rooted using the patched Magisk boot method and accidentally erased some stuff before I could permanently root it. Everything snowballed and all I have now is my firmware stored on pc I can get to fastboot mode but I have stock recovery still. can i flash my firmware through fastboot? I’ve been researching and it seems with Mediatek it’s different or at least not as simple. All searches keep coming up for Zenfone and I’m lost. Apologies if Im in wrong area.
diplomatic said:
Well, recovery of course. ...because it's a custom recovery.
Click to expand...
Click to collapse
Well I'm glad having nothing done until I get a reply from the Master himself
Thanks a lot diplomatic !
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
mirek54 said:
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
Click to expand...
Click to collapse
hold volume + and - together for 10s
There was a time that it was unthinkable development. I appreciate the time that cames after. Nice tutorial!
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Hi, soleera,
To install TWRP, you must have some way to flash it and a bootloader that's either unlocked or doesn't care about unofficial images. I'm not sure that's possible in Z500KL. Look into that first. The Z500KL is about as much a version of this tablet as a Lenovo Tab4 is a version of this tablet. They are completely different platforms, just with a similar model name.
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
soleera said:
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
Click to expand...
Click to collapse
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
diplomatic said:
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
Click to expand...
Click to collapse
Sounds good, I'll see what I can do when I get the time.
For some reason one of the official unlock tools for a different model worked on my tablet - I believe it was for the ZE552KL, although I could be wrong since I can't seem to install it any more ("the package conflicts with an existing package by the same name"). I'm definitely unlocked though since I can flash using fastboot without any errors...
Since we now have official unlock. Any chance at custom roms for this device? I would love to see it get some oreo love.
soleera said:
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Click to expand...
Click to collapse
Hello soleera
Have you succeeded to port twrp to Z500KL?
Do you know of any custom recovery for Z500KL?
Do you know how to root it?
Dr.Ghobar said:
Do you know how to root it?
Click to expand...
Click to collapse
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
diplomatic said:
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
Click to expand...
Click to collapse
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Dr.Ghobar said:
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Click to expand...
Click to collapse
Basically, just do the procedure in this post. It's not that complicated. Reading through that thread may also help. Oh, and you have to unlock your bootloader first with an Asus unlock tool, as soleera has mentioned. I think the tool for the Z500M may work. It's essentially the same app for every device.
So the A/B structure of the Pixel (I came from Nexus 5X) took some getting used to, not having a recovery partition was a new wrinkle, and the jimmy jammy required to unlock the bootloader (I bought a Verizon Pixel apparently) was a neat trick. So I got the Pixel bootloader unlocked, booted with TWRP, installed Lineage, rebooted to bootloader, fastboot booted to TWRP, installed TWRP and OpenGapps.. Excellent! Setup the phone, booted to TWRP and installed Magisk. eveything works! great phone!
Then, a week later there is an update to Lineage. So I copy the ZIP file to my phone, flash it and OpenGapps and reboot. Boom. all screwed up. no problem, I'll restore from the backup I made in TWRP. nope. bootloop. then I read that you restore BOOT,SYSTEM IMAGE,VENDOR IMAGE, and DATA. NOT all the partitions as I had naively thought. Turns out I boned the backup and didn't backup the DATA partition so the Restore works but all my setup stuff is gone. My fault.
I went through the entire process again. Phone is working fine. All is well. Heres the question: What is the appropriate method to upgrade Lineage when a new one is released? So that I end up with new lineage, updated OpenGapps, TWRP working, and Magisk keeping me rooted? I can just keep trying to figure it out but I dont want to keep starting at zero with my phone.
Thanks in advance. I searched diligently on the forums but it looks like not that many Pixel users use Lineage.
Cheers
d.
130 views and no one knows how you upgrade LineageOS? is anyone using Lineage on their Pixel? Really?
I just discovered Lineage OS for my VZW Pixel. What build did you use? If I can figure out how to install, I'll try playing with updating, too.
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
Probably here: https://download.lineageos.org/sailfish
post-mortem said:
Probably here: https://download.lineageos.org/sailfish
Click to expand...
Click to collapse
I probably should have looked there. I didn't even realize they supported the pixel. It's been a while since I've messed with things.
I've been using LineageOS and it's great. Super stable compared to most of the other ROMs I've tested. These are the steps I take when upgrading to a newer build.
- reboot to recovery (TWRP)
- install lineage-15.1-xxx-nightly-sailfish-signed.zip (no wipe or anything beforehand)
- install twrp-pixel-installer-sailfish-xxx.zip
- return to TWRP main menu and select reboot, then Recovery (whenever it prompts me to install TWRP app I just hit "Do Not Install")
- once back in TWRP, install MindTheGapps-8.1.0-arm64-xxx.zip
- reboot to system (again, I always decline the TWRP app installation)
- once you've booted to system, reboot to recovery one last time.
- install Magisk-v17.x.zip
- reboot to system and you should be good to go.
I always have a recent backup from TitaniumBackup stored on my computer so if anything goes wrong I can do a clean install and reload all my apps.
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
yeah I got it from lineage website. have you managed to update using Crawdads method?
dcarrco said:
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
Click to expand...
Click to collapse
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
CapriciousCrawdad said:
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
Click to expand...
Click to collapse
dcarrco said:
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
Click to expand...
Click to collapse
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
CapriciousCrawdad said:
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
Click to expand...
Click to collapse
yes thats where i ended up. tried to update and got bootlooped, my backup didnt work for some reason (do i backup EFS partition also?) so i started again with the instructions in that post. i used the Gapps package from @razorloves and it all worked. setup my phone again and now it upgrades fine using the Lineage updater although i have to reinstall TWRP and reroot (using SuperSU from Lineage) when that happens. razorloves hasnt updated his google FI compatible Gapps package yet so i will see how/if i can update those when the times come. on a side note, im getting really good at setting up my pixel. got to look at the upside.
thanks for your suggestions.
Please?
There is TWRP already but it is not publicly available. I believe, it will be released when customer get phones on their hands.
http://talk.maemo.org/showpost.php?p=1560008&postcount=2235
chen said:
PS: When I tried to flash SFOS initial release onto Pro1 I need to flash a custom TWRP, which is I believe also from Lineage OS devs.
Click to expand...
Click to collapse
EDIT: Now it is available: https://drive.google.com/file/d/1IgUjxEKV5MU_3cRkNCyGc-YpRkUQ3xHh/view
Flash-A-Holic said:
There is TWRP already but it is not publicly available. I believe, it will be released when customer get phones on their hands.
http://talk.maemo.org/showpost.php?p=1560008&postcount=2235
Click to expand...
Click to collapse
You're completely right, I'll notice the guys to post it as soon as first market units hit customers.
TWRP available
TWRP for Pro1 is now available. The initial version is TWRP 3.3.1:
https://drive.google.com/file/d/1IgUjxEKV5MU_3cRkNCyGc-YpRkUQ3xHh/view
The version of TWRP linked in this thread works well enough to install Sailfish OS, but YMMV if you want to use it for any other purpose. It cannot decrypt the userdata partition (so you can't use it to make a backup), and you're better off using fastboot to restore the other partitions rather than a nandroid backup made with TWRP.
To be more blunt, don't use the TWRP from the Sailfish OS instructions for anything other than installing Sailfish OS. It has nasty FDE bug that may force you to wipe userdata after you boot it.
Does anyone have any news or updates on TWRP for the pro1?
I'll have mine soon, and happy help testing if needed.
tdm and I have prioritized work on LineageOS over TWRP, so there isn't likely to be a new version from us in the near term. I don't know if anyone else is working on TWRP for the F(x)tec Pro1.
Thx for the info, and thank you too for the Lineage work!
Based on what I hear there is a great need for TWRP mostly for flashing and backups
How did you guys flash the TWRP image? I tried booting and flashing the image, but fastboot only fails with "FAILED (remote: 'unknown command')". I tried different (Windows 10) machines, fastboot versions, USB cables and USB ports ... without any luck
Don't use the SailfishOS version of TWRP for anything other than installing SailfishOS. If you are installing SailfishOS, follow the instructions for how to flash TWRP from the F(x)tec forums.
Too late, I already flashed TWRP ... and regretted it immediately. Apparently, TWRP destroyed the encryption header/footer. No bad feelings though
Looking forward to TWRP with working decryption ...
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Sent from my GM1913 using Tapatalk
Bagpuss said:
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Click to expand...
Click to collapse
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Are you positive? I see TWRP install guides everywhere. From what I've read TWRP with magdisk (not SuperSU, us it's not open source) is the best way to root with the most flexibility. What if I'm running 10.03.0GM21AA, and there is no patched image? Do I need to roll back?
Lossyx said:
There is only one way to root, and that is by using a patched image. Check the guides section, there's probably a patched image of your device, if not, you'll have to make your own.
And what's your version? AA or BA?
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
What's the best phone with SD card feature that can run TWRP magdisk without issues like using banking apps and Netflix?
Forgive my ignorance, I am still in the learning process.
Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
sixisixsix said:
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Click to expand...
Click to collapse
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
QUBiCA said:
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
Click to expand...
Click to collapse
Oh damn, I'm actually stupid... How did I miss were on 7 Pro?!
@sixisixsix please ignore everything I've said! I will edit my posts.
Sorry once again
Sent from my OnePlus7TPro using XDA Labs
sixisixsix said:
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
Click to expand...
Click to collapse
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
QUBiCA said:
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
Click to expand...
Click to collapse
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Lossyx said:
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Click to expand...
Click to collapse
redpoint73 said:
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Click to expand...
Click to collapse
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
sixisixsix said:
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
I don't think TWRP would give you more flexibility when it comes to updates, unless you are planning on switching ROMs often, but if this phone is your daily driver I would recommend against that.
If you unlock the phone your data will be wiped, but only once. After that it is completely up to you, if you switch ROMs and pick something that is completely different from stock, it is indeed recommended to wipe data to prevent weird issues. But for a regular system update (if you simply stick with the stock ROM and use Magisk for root, you can still receive normal updates from OnePlus), or an update of the same custom ROM, you do not need to wipe data. I wiped data only once, when I unlocked it, because I had to.
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct). What @redpoint73 explained is that instead of installing (AKA flashing) TWRP, it is possible to just start it up (boot it) once without installing it. From there you can install Magisk on your stock OnePlus ROM and use the benefits of a rooted system.
QUBiCA said:
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct).
Click to expand...
Click to collapse
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
sixisixsix said:
Wouldn't installing TWRP give me more flexibility for future updates?
Click to expand...
Click to collapse
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
sixisixsix said:
If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
redpoint73 said:
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
Click to expand...
Click to collapse
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
Click to expand...
Click to collapse
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
tech_head said:
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
Click to expand...
Click to collapse
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Click to expand...
Click to collapse
You should get the OTA update and be able to download it through settings. BUT, after you install the update, you still need to do as I already said in order to remain rooted:
redpoint73 said:
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
Click to expand...
Click to collapse
---------- Post added at 09:28 AM ---------- Previous post was at 09:00 AM ----------
sixisixsix said:
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
Click to expand...
Click to collapse
You seem to be mixing the two processes: Install update in Magisk is for when you update in the future. You shouldn't have to do this rooting the existing ROM with the patched boot.img method.
For the patched boot.img method, you should just be able to flash the patched boot.img, flash the Magisk apk, and open Magisk, and it should say rooted.
My recommendation is follow this guide: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
I can't possibly see how it can be any more in depth.
Just a reminder for people who only read the oneplus 9 forum and not oneplus 9 pro one:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
I tested it and flashed it on my oneplus 9 LE2110 and it works.
Again, as i always have to write to people.
Be careful, only do something you can undo.
Before you "Flash Current TWRP" do a full BACKUP!
Does said recovery perform full back-ups of partitions and restore features ?
Edit
I booted it up . Decrypts perfectly. Backed up modem just to see for myself. Rebooted back onto system . Booted twrp again and it found saved partition to restore. This makes life so much easier. Time to go get a full system backup !! Cool
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
noname122414 said:
Exactly. I'm super happy. Now the OnePlus 9 Is finally a good phone. Without TWRP it's just risky.
Im sure some bugs are still there but it looks very promising.
Click to expand...
Click to collapse
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Hi there, I have a question:
When you have a new device, would the following work:
1. Unlock bootloader
In fastboot mode:
2.
Code:
fastboot boot c:\twrp.img
In TWRP
3. Install TWRP
4. Install Magisk
5. Reboot - then you have Root, TWRP?
6. Upgrades can than be done in TWRP by installing the files and than intalling again TWRP and afterwards Magisk?
Best
Axel
It appears you are asking. If I am incorrect, my apologies. With the 6t (also a a/b OP device)
The process I always used was
1) reboot to bootloader
2) boot twrp.img
3) install twro zip
4) reboot recovery
5) upon TWRP reboot, install magisk
6) profit.
Anytime I tried to go ahead and install Magisk in the same round as installing TWRP, it would install to the opposite slot making me have to do the whole process over again. Ymmv
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
barguybrady said:
XDA is Great, and, yet, at the same time: XDA is very challenging.
With so many able to contribute, and the lack of external editing capacity ( unlike SO ),
it's difficult to distill the information.
Okay, Great! There's a TWRP for the OnePlus 9 !
I used TWRP 3.5 and Magisk to root a Lenovo Tab M10, without any need for external input.
The Answer I'm looking for here is: Am I able to install / root / whatever my T-Mo OP 9 with TWRP ?
Does anyone have any definitive solutions ?
Thank You, in Advance, for any assistance !
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
MrSteelX said:
Is your bootloader unlocked? If yes then you could boot to fastboot and fastboot boot twrp.img. You will have your answer then.
Click to expand...
Click to collapse
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
barguybrady said:
Sadly, No, boot-loader is locked. Never encountered this on both previous OP 6t's.
Hence my confusion. When I walked out of the t-Mo store with my 6t, I had No issues.
I used the wonderful mauronofios tool, to do it All with no troubles.
crash my 6t, forced to take a "9 5g" from t-Mo, and now I am regretting it.
Wondering what has changed, and by whom..? t-Mo change policies, or OnePlus ?
Actually, I've been a t-Mo customer for 16 Years ! First time I've ever had to "Ask Permission" to have my phone, or my SIM unlocked...
Click to expand...
Click to collapse
You should start a separate thread for all that. Kinda want to keep on topic to make it less confusing for everyone
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
mattie_49 said:
And this is huge for many people roaming around here on carrier variants . Now super easy to restore modems to make switch to global.or eu or whatever.
Click to expand...
Click to collapse
Just installed it - thanks OP.
Does anyone know if I can jdirtyflash the global rom 11.2.7.7 over the EU rom which is currently on 11.2.7.7 in twrp?
I was originally on global (le2110) but flashed EU via update. Now I want to go back to global.
applyscience said:
Has anyone been able to mount a usb drive? ive tried everything and it just looks to not be functional.
strangely enough, i heard TWRP backups are iffy right now but have already restored from one using this release in the past week. happy that works
Click to expand...
Click to collapse
Full system everything. User data. ? Did it work
mattie_49 said:
Full system everything. User data. ? Did it work
Click to expand...
Click to collapse
i dont know i have been bricked for 5 days ever since i attempted the lineage release
applyscience said:
i dont know i have been bricked for 5 days ever since i attempted the lineage release
Click to expand...
Click to collapse
Just lineage no kernel no special cam?
mattie_49 said:
Just lineage no kernel no special cam?
Click to expand...
Click to collapse
nah. just lineage. pretty sure i deal with support again tomorrow. fun...
Need help...
I typed Fastboot boot twrp.img instead of fastboot flash boot twrp.img
And that was to boot_a
So then i tried fastboot flash boot_b twrp.img
It wont load the recovery now. Phone wont boot up unless i
fastboot boot patched11.2.7.7DA.img
I even try to install Magisk directly and it fails.
Can I get some help. Dont even wanna restart my phone.
Thank you
All Good Now..... I Figured It Out!
How to fix this
id avoid TWRP if on 11.2.8.8 already. it can boot from fastboot and even install itself as your recovery but it will not mount data. i tried the refresh sizes trick in backup and then the default_password for password to decrypt and nothing. pretty sure twrp mishaps are what bricked my phone last too . thankfully it still boots, just the recovry section is effected
ill try and flash the OTA zip tomorrow. sick of messing with it for now lol
Are we still avoiding twrp