Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD : https://dl.twrp.me/thea/
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][THEA] TWRP 3.2.3-0 Touch Recovery [OFFICIAL], ROM for the Moto G 2014 LTE
Contributors
luca020400, LuK1337
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2016-02-07
Last Updated 2018-08-07
Reserved
Reserved
Source code : motog2014devteam
Source code : CyanogenMod
ok and how can we install it?
javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
fastboot flash recovery file.img
LuK1337 said:
fastboot flash recovery file.img
Click to expand...
Click to collapse
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
javierutxo said:
aja, and what about unlock bootloader and rooting? the same process than moto g 2014?
Click to expand...
Click to collapse
Yes
javierutxo said:
ok and how can we install it?
Click to expand...
Click to collapse
Take the steps from here http://forum.xda-developers.com/moto-g-2015/general/rooting-moto-g-2015-lte-xt1078-t3086069
Just change the twrp.mg for the one in this post.
Good Luck!
Thank you!! Its worked for me on XT1072
Hello, It worked just fine on my XT1078
Thanks!
Is it possible to make this an "official" release ?
551790 said:
Is it possible to make this an "official" release ?
Click to expand...
Click to collapse
Yes , but I'm not going to do that
luca020400 said:
Yes , but I'm not going to do that
Click to expand...
Click to collapse
Hi Luca! Can you explain shortly how you built this image? Any manual that you can point me to?
I'm asking because I'd like to build it also for peregrine...
New build up
Download
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Maledroid said:
idk whats happening. i unlocked my phone and installed this recovery and when i try to enter in recovery mode it shows and android with the exclamation sign and never continues to the actual recovery. it just stays there forever and then reboots by itself. can anyone tell me what is wrong?
Click to expand...
Click to collapse
You haven't flashed twrp
Reboot to bootloader
By pc
fastboot flash recovery twrp-thea.img
( with admin/sudo )
Then reboot to recovery
luca020400 said:
New build up
Download
Click to expand...
Click to collapse
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
cgb.spender said:
Hi Luca, thank you very much for your hard work on this device.
About this new release of TWRP, I'd like to know, if possible, what are the main differences with the previuos one.
Click to expand...
Click to collapse
TWRP fixes
The TWRP version still 2.8.6 but it's 2.8.7
My encrypted TWRP nandroid backups fail with the following error message:
E:createTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
This only happens when I use encryption, and it always happens right near the end of backing up the Data partition (the System partition backup completes successfully).
N.B. The percentage of files and MB processed do not increase in-step, like with an unencrypted backup. The MB percentage increases to 90%+ far quicker than the percentage of files processed. When the percentages come in-line with each other near the end of the Data partition backup, it fails, and the above error message is given.
I was using a Titan build of TWRP to create nandroid backups on my Thea device previously, and had no issues with encrypted backups.
This is an issue, as there are sensitive security details stored in the backup, which must be encrypted with a strong password.
Internal Storage failure?
sunka1 said:
My encrypted TWRP nandroid backups fail with the following error message:
....
Click to expand...
Click to collapse
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
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.
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.
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.
Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.
Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?
Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.
Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.
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