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 I just picked up a Pixel 3 while on sale to replace my failing Nexus 5 that was literally falling apart. I managed to unlock the bootloader easily. Used a USB C to USB A cable from my Nintendo Switch used for charging the controller for unlocking the bootloader. Next step was to install TWRP and eventually Magisk.
So I followed the instructions to install TWRP from the TWRP website and grabbed the latest image and zip. Initially when I ran the command to boot the image, I would get a "too many links" error. Everything I found in relations to this said I needed a better cable. Odd but okay. I had planned to pickup a new one anyways for transferring music and pictures and such. Got it today, reboot into fastboot and now the command completes successfully with no error. Unfortunately instead of booting into TWRP temporarily as per the instructions, to then install the ZIP for TWRP, the phone boots straight into Android. I have tried the following commands. The first being from the official TWRP guide, and the second being from another guide I had found.
fastboot.exe boot twrp-3.2.3-0-blueline.img
fastboot.exe boot recovery twrp-3.2.3-0-blueline.img
Obviously both result in the same issue. Namely the phone simply reboots right into Android. I am using the latest Platform SDK tools from google, and am using the most up to date drivers for the phone. I am at a loss of what I might be missing. I do see info about boot slots A and B (My phone is B), but nothing in relation to that as far as installing TWRP is concerned. Any help would be appreciated!
What Android version is your Pixel 3 device running?
BobPony said:
What Android version is your Pixel 3 device running?
Click to expand...
Click to collapse
Android 10. Latest OTA.
Ultratails42 said:
Android 10. Latest OTA.
Click to expand...
Click to collapse
Twrp doesn't work on 10. Maybe it will some day but not now.
jd1639 said:
Twrp doesn't work on 10. Maybe it will some day but not now.
Click to expand...
Click to collapse
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Ultratails42 said:
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Click to expand...
Click to collapse
If you want, you can downgrade to Android 9 using the factory images with the flash-all script. But, it requires to have the bootloader unlocked.
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
Did you ever get any help? I am in the same boat.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
Piricho said:
Did you ever get any help? I am in the same boat.
Click to expand...
Click to collapse
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
RokCruz said:
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
saurabh_op7 said:
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
Click to expand...
Click to collapse
Just flash stock boot.img
RokCruz said:
Just flash stock boot.img
Click to expand...
Click to collapse
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
saurabh_op7 said:
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
Click to expand...
Click to collapse
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
RokCruz said:
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
RokCruz said:
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
Click to expand...
Click to collapse
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
saurabh_op7 said:
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
Click to expand...
Click to collapse
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
RokCruz said:
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
Click to expand...
Click to collapse
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
saurabh_op7 said:
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
Click to expand...
Click to collapse
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
RokCruz said:
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
Click to expand...
Click to collapse
My model is GM1901, in support intro for the link you provided, that's not included?
saurabh_op7 said:
My model is GM1901, in support intro for the link you provided, that's not included?
Click to expand...
Click to collapse
Wait GM1901 is a OnePlus 7(non pro) right?
RokCruz said:
Wait GM1901 is a OnePlus 7(non pro) right?
Click to expand...
Click to collapse
Yeah.. ?
saurabh_op7 said:
Yeah.. ?
Click to expand...
Click to collapse
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from HereI
Click to expand...
Click to collapse
Yeah man, I realised.. anyway, I flashed the boot image from Xda for OP7.. nevertheless, mom tool it is.. thanks..!
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
Click to expand...
Click to collapse
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Update: I have been roaming around the corridors of this forum since about a week now. Thanks @RokCruz !!
Finally, used msm tool, although I suspect I still had the option of flashing TWRP and Magisk as I had access to phone and fastboot, but the system was super glitchy.
saurabh_op7 said:
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Click to expand...
Click to collapse
I guess that the only way is using the fastboot ROM
RokCruz said:
I guess that the only way is using the fastboot ROM
Click to expand...
Click to collapse
Any idea if we're gonna get one soon?
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