Code:
**Disclaimer
*I am not be responsible for any bricked devices, data loss or thermonuclear wars.
*You are using this at your own risk.
Introduction
Welcome to TWRP for Lenovo Tab M10 X505X. Make sure you read the entire post carefully before you proceed with installation.
Pre-installation
Install ADB and Fastboot. Refer to this link if you need help installing ADB and Fastboot.
Unlock the bootloader. Refer to this link if you need help unlocking the bootloader.
Installation
Flash the TWRP image from bootloader.
Code:
fastboot flash recovery twrp.img
Warning:
Do not reboot the system yet. Remove the connection from the device. Hold the power button until it turns off. Then turn it on again with the recovery combo: Power button + Volume Up + Volume Down.
Once booted into the TWRP recovery mode, if you want to flash it permanently(otherwise it will be replaced with stock recovery after a reboot), install Magisk from recovery.
You can goto advanced option in TWRP and use the "ADB Sideload" option to sideload the Magisk zip file. In case sideload doesnt work, use adb to push the Magisk zip file to /tmp and then install the zip normally.
Warning:
Do not push the zip file to /data. The data partition is encrypted and any damage done messing with the data partition will not be my responsibility. You have been warned.
Downloads
TWRP image for X505X
Magisk
Known Issues
From android 9.0 onwards, the data partition is force encrypted and is not available to the TWRP. This is not much of an issue because update zips and ROM flashes usually dont use the data partition. So the data partition is encrypted.
Changelog
Code:
This is the first version
Upcoming Features
Support for decryption of data partition permanently/temporarily.
Upcoming Project
A custom rom for this device if I get enough support.
Donations
I have spent a lot of time on this project. Consider buying me a coffee or donating. It will be great support.
Google Pay
Feel free to ask me if you encounter any problems.
Device Tree
For those who are curious. This is the device tree I ported for X505X.
If this helped you, hit the thanks button.
It would mean a lot to me if you could follow me on :-
Github
Instagram
Special Thanks
Code:
Yahoo Mike - For his great support
XDA:DevDB Information
Custom Recovery for Lenovo Tab M10 X505X, Tool/Utility for the Lenovo Thinkpad Tablet
Contributors
Shamil Niyas, Yahoo Mike
Version Information
Status: Beta
Current Beta Version: 2.84
Beta Release Date: 2020-11-12
Created 2020-11-13
Last Updated 2020-11-13
Reserved
Hi, Useful thread here, I flashed this recovery to X505F and it's working fine except MTP and data partition does not unencrypt.
Can it be fixed somehow?
looking for a custom rom for this device as well.
Please help!
Hi, i dont have a pc currently with me, how can i do it using a mobile.
zubair1836 said:
Hi, Useful thread here, I flashed this recovery to X505F and it's working fine except MTP and data partition does not unencrypt.
Can it be fixed somehow?
looking for a custom rom for this device as well.
Please help!
Click to expand...
Click to collapse
I'm still working on the data encryption. I will update as soon as possible.
Look forward to the custom rom..
cYBER~VeTeRaN said:
Hi, i dont have a pc currently with me, how can i do it using a mobile.
Click to expand...
Click to collapse
Unfortunately you cannot flash it without pc. Or if you can access fastboot using your mobile and termux you might be able to flash, though I cannot guarantee it.
Pls update twrp to latest verison 3.5
cYBER~VeTeRaN said:
Pls update twrp to latest verison 3.5
Click to expand...
Click to collapse
Thanks...I will update asap...
Sir, i would like to know which rom u r planning to port, expecting a gaming rom, also i would like to know the current progress , thanks in advance
I have a lenovo m10 tablet as well but it's said to be a X306F instead? Will it work you think?
Ooo_64 said:
I have a lenovo m10 tablet as well but it's said to be a X306F instead? Will it work you think?
Click to expand...
Click to collapse
Do try booting thr recovery without flashing and post the result.
For booting without flashing run :
fastboot boot recovery.img
cYBER~VeTeRaN said:
Sir, i would like to know which rom u r planning to port, expecting a gaming rom, also i would like to know the current progress , thanks in advance
Click to expand...
Click to collapse
I'm still working out the device tree for the rom. Will update as soon as possible.
Forgive me for wondering, but I'm looking at buying a tablet, and I wonder a few things, first of which would be, what is everyone's experiences with this tablet??? The next thing I wonder is if you only plan on doing a single rom??? Say for instance, you started out with a CM rom, then did my personal favorite, ressurrection remix... Or maybe do remix first
Either way, I love android, but am missing ressurrection remix since back when I had a phone that supported it... The ressurrection remix rom has so many options it could take a 30$ device and make it feel like a 300$ device, but that's also a problem, because with lots of extra features and settings comes the greater possibility of bugs
Wiebenor said:
Forgive me for wondering, but I'm looking at buying a tablet, and I wonder a few things, first of which would be, what is everyone's experiences with this tablet??? The next thing I wonder is if you only plan on doing a single rom??? Say for instance, you started out with a CM rom, then did my personal favorite, ressurrection remix... Or maybe do remix first
Either way, I love android, but am missing ressurrection remix since back when I had a phone that supported it... The ressurrection remix rom has so many options it could take a 30$ device and make it feel like a 300$ device, but that's also a problem, because with lots of extra features and settings comes the greater possibility of bugs
Click to expand...
Click to collapse
RR is available on Project Treble as a GSI. You could try that.
So, I flashed recovery, tried rebooting by holding down power button and the volume buttons and now it's stuck in an infinite boot loop. Screen shows lenovo logo, and then it goes blank, vibrates, and then restarts to lenovo logo again. Holding down the power button won't even shut it off. Please help.
TWRP flashed successfully but sadly the data partition didn't work.
so to make it work, I first formatted the data partition and through the adb sideload I flashed disable-dm-verity (attached) and it now works, data-partition is not encrypted anymore.
I also compiled an orange fox recovery for it and the data partition is also working on it.
Yahoo Mike said:
RR is available on Project Treble as a GSI. You could try that.
Click to expand...
Click to collapse
Is the GSI Booted?
One update guys.
I accidently wiped system of TB-X505X and flashed Android 12 Beta 2 GSI and it worked.
only Bluetooth is dead.
and when plugging aux getting grounds from both system speakers and earphone
Wiebenor said:
Forgive me for wondering, but I'm looking at buying a tablet, and I wonder a few things, first of which would be, what is everyone's experiences with this tablet??? The next thing I wonder is if you only plan on doing a single rom??? Say for instance, you started out with a CM rom, then did my personal favorite, ressurrection remix... Or maybe do remix first
Either way, I love android, but am missing ressurrection remix since back when I had a phone that supported it... The ressurrection remix rom has so many options it could take a 30$ device and make it feel like a 300$ device, but that's also a problem, because with lots of extra features and settings comes the greater possibility of bugs
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...top-style-tb-x505x-lenovo-tab-m10-hd.4306713/.
You can go here for RROS for lenovo tab M10 Hd x505x
cYBER~VeTeRaN said:
Hi, i dont have a pc currently with me, how can i do it using a mobile.
Click to expand...
Click to collapse
Use Termux in other device
I tried rooting my lenevo tab M10 hd and flashed a incorrect boot img as I am new to rooting and bricked up my device then from some where I got the correct boot img and recovered my device but now I am unable to use its internal storage , its shows some random letters when I open the file manager can you guys help me out resolving this issue.
Related
Hello All,
NOTE: You should unlock your bootloader.
These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.
WARNING:
- Be sure to have a working /system partition before proceeding with installation.
Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:
Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download
- Apollo Recovery Image
- Thor Recovery Image
Thanks
- @vortox for the exploit
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
r3pwn said:
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
Click to expand...
Click to collapse
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
vortox said:
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
Click to expand...
Click to collapse
Ah.
I wrote the recovery on my apollo device which is running 14.3.2.3.2_user_323001720 version and it appears to work flawlessly. I booted into recovery (TWRP) successfully and rebooted the system successfully as well. Awesome!
Thanks for the feedback, glad it's all working
I haven't got a device at the moment to try it out on.
Sent from my Kindle Fire HDX using Tapatalk
Thanks ggow. Could we expect CM roms soon from your new release?
Working on 14.3.1.0
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
Hello tuanda82,
It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.
They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .
I hope I have luck with the new device been on the required firmware.
But yes I definitely would like to make such a release.
dangerous
jeryll said:
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
Click to expand...
Click to collapse
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
tbm13 said:
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
Click to expand...
Click to collapse
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
r3pwn said:
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Click to expand...
Click to collapse
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Håvi said:
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Click to expand...
Click to collapse
Flash the rollback image to stock slot. This will then enable you to get back to 3.1.0
ggow said:
Flash the rollback image to stock slot. You need to be on stock version < 3.2.4.[/QUOT
Edit, found answer in OP
Click to expand...
Click to collapse
I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.
Sent from my KFAPWI using Tapatalk
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
GSLEON3 said:
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Click to expand...
Click to collapse
Thanks gsleon but don't rob your mom
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
ggow said:
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
Click to expand...
Click to collapse
Crossing fingers
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_mate9_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** @Tecalote - He was the main tester for this version and also he was the one that convinced me to open this thread in first place
**** @Blackball
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_mate9_0.1.img - initial release
Thank you for such a great project!
I am very happy with this TWRP. Everything is working so far on EMUI, Android 8.
Data wipe is possible, cause OEM Path is excluded.
Vendor.img and System.img and recovery_ramdisk can be flashed by choosing img to the related img.
Backup, restore of all shown Partitions working perfectly.
Decryption of storage if using Fingerprint /PIN is working. Full encryption support for data..
Many thanks to @Pretoriano80 for this awesome and first most complete TWRP for Mate 9 :good::good:
BTW: @Blackball had tested this TWRP for P10 Plus and it is also working on this Device (so it will run also on P10).
Many thanks for testing too :good:
This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?
Wirmpolter said:
This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?
Click to expand...
Click to collapse
Format data is only necessary if installing AOSP based Roms which require this (in installation guide)
But for Stock Firmware you don't need to decrypt (format) anything because encryption is fully supported
Of course, you can't install older Stock based Custom Rom which mount data in the updater-script without /dev/block/dm-0
I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.
osk4rin said:
I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.
Click to expand...
Click to collapse
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.
Tecalote said:
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.
Click to expand...
Click to collapse
Oh right, thanks.
Seems to work perfectly, in my case the rom doesn't even seem to be overwrite twrp upon normal boot
Thanks a lot!
osk4rin said:
Oh right, thanks.
Click to expand...
Click to collapse
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.
i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password
Caguayote said:
i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password
Click to expand...
Click to collapse
If it's ask for password, then insert the same passwords/pin/pattern that you are using in Android, so TWRP can decrypt the internal storage.
That's the whole purpose of having a TWRP with decryption support.
10-4
Thank you for the clarification
Pretoriano80 said:
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.
Click to expand...
Click to collapse
how can I get them?
osk4rin said:
how can I get them?
Click to expand...
Click to collapse
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop
Work this nougat .. ??
Tecalote said:
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop
Click to expand...
Click to collapse
I just attached the build.pro files .Using RR remix treble project
Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!
_Nostromo_ said:
Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!
Click to expand...
Click to collapse
No, it's designed to work like this!
Pretoriano80 said:
No, it's designed to work like this!
Click to expand...
Click to collapse
Ok, thought so, it definitely makes sense, just being a bit lazy... Thanks a lot for your prompt response, Pretoriano80! :good:
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Gesendet von meinem xXx_NoLimits_6.0 on ONEPLUS 6T mit Tapatalk
MarcoG: said:
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Click to expand...
Click to collapse
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
ultyrunner said:
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
Click to expand...
Click to collapse
I'd like to see a resolution to this ^
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Causical said:
I'd like to see a resolution to this ^
Click to expand...
Click to collapse
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
se7ensde said:
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Click to expand...
Click to collapse
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
ultyrunner said:
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
Click to expand...
Click to collapse
Awesome, you sir are THEE man. Please get a job with XDA or something
Causical said:
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Um ... OK ... ?
Causical said:
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Yeah sure you can mix up the steps or skip whatever you want..
se7ensde said:
Yeah sure you can mix up the steps or skip whatever you want..
Click to expand...
Click to collapse
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
ultyrunner said:
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
Click to expand...
Click to collapse
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Causical said:
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Click to expand...
Click to collapse
Nope. I was surprised because ...
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
ultyrunner said:
Nope. I was surprised because ...
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
Click to expand...
Click to collapse
Cool I'm glad you can explain the "tone" and characteristics of my own words to me. I'll remember to try and not be so nice towards you next time, at least if I really be a **** it won't be mistaken.
I WAS originally thrilled by your simple and to the point response, but since you decided to twist my words and make yourself look like a jack ass... well nicely done, is all I have to say ?
Words of a Wise Guy: "hmmm seems odd after receiving a like..."
Huh, just think about that one for a second.
Causical said:
Cool I'm glad you can explain the "tone" and characteristics of my own words to me.
Click to expand...
Click to collapse
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
ultyrunner said:
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
Click to expand...
Click to collapse
Oooo scary...I guess I'll take my "like" or thanks back whatever you call it.
the.emilio said:
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
Click to expand...
Click to collapse
Thank you it works[emoji16]
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
se7ensde said:
Fastboot format userdata
Click to expand...
Click to collapse
What is formatted? The complete internal sdcard?
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Ryano89 said:
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Click to expand...
Click to collapse
Yes.
Mannan Qamar said:
Yes.
Click to expand...
Click to collapse
Thanks, I only ask because I see a lot of disagreement about it on different threads. Some say you can do it, other's say you can't do it if you are flashing back to an older security patch. It's not urgent for me so I might just wait until I have access to my laptop again, but I was hoping to do it now. Won't format completely erase the device?
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to Decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
Flash official recovery from twrp website. If I remember right it will work. But change language to English
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
strakell said:
If you haven't already find solution you must do factory reset through twrp option to unlock it ,of course this action will wipe all your data.
Click to expand...
Click to collapse
Data partition he needs to wipe.
ianseer said:
Hello guys,
just wanna asking again,.. I was going to flash magisk on red magic. I already succeed in flashing the TWRP. But, unfortunately, the TWRP was asking for a password to decrypt Data...
Does anyone know the solution for this?
I already try to put pin on android and use it on TWRP still no luck here. Is there is a way to decrypt the phone from the system itself??
any suggestions will be great :fingers-crossed:
Click to expand...
Click to collapse
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened you appetite!
have fun!
Click to expand...
Click to collapse
You answering all of my question very nice and clear... Yes i will having fun next week, i hope... (Still in other city now, i need my phone)... But, when the time comes, i will try it and post the update here... big thanks, Appriciate it... Yes i'm hungry now
methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
If only i can help you guys out cooking the rom... I'm only animator and designer... Not chef programmer or coder
methuselah said:
Does the songs are getting played into the gsi? Treble GSI have issues like overheating and no sound while playing music. Means no ringtones either. I had put logs for phh but he didn't worked as he is busy. As all gsi uses phh base and fixes, the issues are same across the gsi.
Plus- in pie Chinese vendor the treble support is gone. So no more treble in pie update. Only we have legacy support on 8.1.
I had tried to work onto updating Omni but my motherboard went down. It got burnt. You know how to cook ROMs right ! Why don't you try?
Plus the latest gsi no longer boot idk the reasons with the July updates. Reply to me I am trying to donate a device to anyone who can work on this phone
Click to expand...
Click to collapse
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
ABM30 said:
YES, at this moment sound is a problem in GSI ROMs. In call you have sound but not in media.
I am still looking for solutions.
Click to expand...
Click to collapse
There are logs on phh thread about sound and other issues on gsi. Take a look if you have any knowledge. You don't need to take logs again I guess. But new GSI don't even boot last time this month when I checked. Maybe I was wrong.
It's just my point of view. You should try to bring up lineageOs with Omni sources coz lot of developers are there to help you if you have knowledge. The device tress are there from Omni. Well 8.1 is still there as lineageOs is still updating and giving security fixes. And most of commits are there for ok our phones in Omni GitHub.
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list ,
or here:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
About treble experimentation here: https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29
For example I like the DESCENDANT 3.1.1 : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578 but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
ianseer said:
Hello, me again...
I'm trying to do the method that you've explained...
there's a new problem... right now, already try to connect my phone to USB on pc, it always says "USB supplying power on attached device" even for fastboot mode it doesn't work the computer still not recognize anything.. already tried different computer, already tried different cables too... no luck...
Now, I can go to emergency recovery with stock nicely but cannot go to the usual recovery cuz i already installed twrp but the phone itself is encrypted device so nothing to do there, I'm thinking about wiping userdata from emergency recovery,... is it okay to do this? cuz maybe I'm thinking after I wiping the userdata and everything I can get my USB connection again (cuz before i've had similar issue but after install new rom it's working nicely almost with every cable),... what do u guys think? thanks in advance
Click to expand...
Click to collapse
Well, if you are encrypted you will need to uncrypt your phone.
!!!!!!!But you will lose everithing saved in internal memory!!!!!!!!
Just follow steps 1 to 8 from my previous guide. Then you can reinstall the ROM. If you will install International ROM you will get encrypted again if you don't run Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip right after installing ROM in TWRP!!!!!!!
Wiping everything with original recovery is the best way to clear your phone!!! sometimes is mandatory this, even with advanced wipe in TWRP you wont achieve what you can with original recovery wipe!
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
methuselah said:
Why are flashing without any output. Flash phh treble and help in sorting out bugs.
Click to expand...
Click to collapse
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
well it doesn't work. It's a part of kernel I guess. There are no sounds from loudspeaker. and there are huge issues with pie in phh treble. He needs logs for that. You can't even login into the google account. There are logs with on treble Phh thread. August images are there. Start taking logs after reading the thread. You will be happy to help him.
ianseer said:
I will... btw, do u know if we in treble. what happened with led strip on the back? is it only for notification? or turned off completely?
Click to expand...
Click to collapse
Did you posted any log?
ABM30 said:
1. You need to go in boot-loader mode: VOL DOWN and POWER - preferable from power off state and when logo appear release buttons.
2. unlock boot-loader (every time is needed if you want to modify recovery or anything else)
3. install original international recovery: [url]http://www.mediafire.com/file/s3dyqlhsytsflpd/recovery-114.img/file[/URL]
4. restart in RECOVERY...now you see original recovery : choose English and go and wipe USER DATA (!!!!!!IT WILL ERASE EVERYTHING, ANY IMG< MP# < EVERYTHING FROM INTERNAL MEMORY and DECRYPT IT !!!!!),
erase also cache!!!!!
5. Power OFF
6. Unlock boot-loader (yes, again!)
7. install TWRP 3.3.1 : [url]http://www.mediafire.com/file/nsu9nr0pdknruxw/recovery-331.img/file[/URL]
8. Boot into TWRP Recovery
9. now install "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" : [url]http://www.mediafire.com/file/hquo5qjoi45hy9c/Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip/file[/URL]
In this way you will decrypt your phone and prevent to encrypt it again on reboot. If you don't Disable verity and force encrypt phone will re-encrypt itself on reboot because Vendor partition contain settings to encrypt data. There is a chance that after step 8 you will need to reinstall original international ROM ver. 114 and immediately after that the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip"
After reboot successfully (and no encrypting data) go back to TWRP and flash the last magisk.
....If you want to try something else: Download the Resurrection Remix 8. 1, version 64 bit A only gapps from here: [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/resurrection-remix-phh-treble-t3767688[/URL]
This one I found that is working also gapss.
You can find also other ROM (as system image!) here:
[url]https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list[/URL] ,
or here:
[url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development[/URL]
About treble experimentation here: [url]https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-%28FAQ%29[/URL]
For example I like the DESCENDANT 3.1.1 : [url]https://forum.xda-developers.com/project-treble/trebleenabled-device-development/descendant-android-pie-custom-rom-ver-t3840578[/URL] but I can not make working gapps on it....till now at least
So, I think i have opened your appetite!
have fun!
Click to expand...
Click to collapse
Hello sir, I followed each and every step, but device ended up in bootloop. Mostly a soft brick. Every time I power on the device, the logo comes and phone turns off.
I even tried to patch the fstab in /vendor/etc. Same results.
By the way, I could not get the V114 stock global rom which you have mentioned but was able to get V109 stock global rom. If you have the link of the stock rom you mentioned, please provide a link for it. I will just revert back to stock and use it that way. Seems like the device doesn't wants to have an unlocked bootloader and a uncrypted data state ?
ianseer said:
Back to report...
Already finished all the things need to be done... and ABM30 method is working nicely.... now, I can enjoy all the root goodness in my red magic with original global rom.
really this is what I'm looking for... Thanks a lot.
Ps: just wanna share for the USB to pc connectivity problems: what I did was connect it on fastboot mode, and do fastboot command for unlocking your red magic.... wait around 5 min, unplug it if nothing happens, plug it again and wait again (until many times), after that you will see your fastboot command from wait mode into something successful... (i dunno why).
and then do reflash the recovery...
for the resurrection remix, I will try it and post it on new thread.... seems interesting
Click to expand...
Click to collapse
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Zenith9082 said:
I'm facing issues with this. I followed every step as mentioned by ABM30. But the device in now on bootloop. Infact, I do have the twrp as recovery but device state is locked and the system isnt booting up. Help please
Click to expand...
Click to collapse
you mean twrp mentioned that your device is locked?
Team Win Recovery Project 3.x, or twrp3 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.5.0-0-rav-sofia.img
drive.google.com
XDA:DevDB Information
TWRP, Tool/Utility for the Moto G8
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-31
Hello, I'm trying to port TWRP to the motorola edge plus and right now I'm running into an issue where my touchscreen and adb do not work. Could you publish the device tree you used here so I can take a look at it and potentially get it working on my phone?
Thanks.
pixlone said:
Hello, I'm trying to port TWRP to the motorola edge plus and right now I'm running into an issue where my touchscreen and adb do not work. Could you publish the device tree you used here so I can take a look at it and potentially get it working on my phone?
Thanks.
Click to expand...
Click to collapse
You'd better check the moto edge tree : https://github.com/boulzordev/android_device_motorola_racer/tree/twrp
Unified one for trinket devices is here : https://github.com/moto-sm6xxx/android_device_motorola_sofiar/tree/twrp
Where to look at :
recovery/root/vendor/firmware - firmwares for touchscreen and vibrator
recovery/root/sbin/modules - drivers for touchscreen/battery/vibrator
recovery/root/sbin/load_ts_firmware.sh - in charge to load modules and tell touchscreen driver which firmware to load
Just like to confirm that this is working great either booted or installed. Thanks for the hard work vache :good::good:
There is no system partition to install to in TWRP. Super is listed twice. It may be nice to know what partitions listed actually mean.
No checkbox activation:
System
Vendor
product
USB storage
swear000 said:
There is no system partition to install to in TWRP. Super is listed twice. It may be nice to know what partitions listed actually mean.
Click to expand...
Click to collapse
It would be nice to see users searching by themself.
Google for "dynamic partitions" and "fastbootd". That could also help you to understand why omni is shipped as images for now instead of flashable zip.
vache said:
You'd better check the moto edge tree : https://github.com/boulzordev/android_device_motorola_racer/tree/twrp
Unified one for trinket devices is here : https://github.com/moto-sm6xxx/android_device_motorola_sofiar/tree/twrp
Where to look at :
recovery/root/vendor/firmware - firmwares for touchscreen and vibrator
recovery/root/sbin/modules - drivers for touchscreen/battery/vibrator
recovery/root/sbin/load_ts_firmware.sh - in charge to load modules and tell touchscreen driver which firmware to load
Click to expand...
Click to collapse
Oh thanks, I didn't even know you had a moto edge tree. I'll take a look at it and see what I can do with it.
OMNI
vache said:
It would be nice to see users searching by themself.
Google for "dynamic partitions" and "fastbootd". That could also help you to understand why omni is shipped as images for now instead of flashable zip.
Click to expand...
Click to collapse
Most people agree OMNI is a great ROM. System, Vendor, and product are critical partitions for ROM flashing so I am surprised TWRP does not toggle them correctly.
Update : https://drive.google.com/file/d/17QLv1Pzq9x1FCzAYKULfUTwn3R0akMXI/view?usp=sharing
Changelog :
-Fixed Novatech touchscreen
vache said:
Update : https://drive.google.com/file/d/17QLv1Pzq9x1FCzAYKULfUTwn3R0akMXI/view?usp=sharing
Changelog :
-Fixed Novatech touchscreen
Click to expand...
Click to collapse
I can confirm that it is fixed. I used Magisk's adb/fastboot module to unlock my Moto G Fast with my rooted G7 Play with a USB C to C cable, boot twrp, and make a back up. This is epic!
It took some digging to figure this out, so I'm going to outline the steps for getting this installed without a boot loop.
1. Unlock your device. (I'm not holding your hand here.)
2. Reboot into fastboot.
3. Temporarily boot twrp.
4. Install magisk by flashing the latest zip from twrp. Then flash the copy partitions zip so you don't hard brick.
5. Reboot to system, and you're now rooted.
6. Reboot into recovery.
7. From stock recovery select "enter fastboot" this takes you to "fastboot d" mode.
8. Flash twrp while you're in fastbootd mode.
9. Enjoy! Everything is working perfectly. Rebooting to recovery takes you to TWRP. Rebooting to system gives you root. We also have full decryption support.
Great work
Spaceminer said:
I can confirm that it is fixed. I used Magisk's adb/fastboot module to unlock my Moto G Fast with my rooted G7 Play with a USB C to C cable, boot twrp, and make a back up. This is epic![/QUOTE @Spaceminer View attachment g8fast-nexus7.zip
([emoji88]Omni Rom[emoji88])
Click to expand...
Click to collapse
asineth said:
Great work
Click to expand...
Click to collapse
Great work fixing the Bluetooth audio [emoji817]
([emoji88]Omni Rom[emoji88])
is it to much to ask for a more through explanation on how to flash twrp and magisk on this phone?.....
ninjakira said:
is it to much to ask for a more through explanation on how to flash twrp and magisk on this phone?.....
Click to expand...
Click to collapse
If you have telegram I walk you threw it PoochyX
([emoji88]Omni Rom[emoji88])
PoochyX said:
If you have telegram I walk you threw it PoochyX
([emoji88]Omni Rom[emoji88])
Click to expand...
Click to collapse
just send the invite to whatever telegram group then i suppose.....
Spaceminer said:
It took some digging to figure this out, so I'm going to outline the steps for getting this installed without a boot loop.
1. Unlock your device. (I'm not holding your hand here.)
2. Reboot into fastboot.
3. Temporarily boot twrp.
4. Install magisk by flashing the latest zip from twrp. Then flash the copy partitions zip so you don't hard brick.
5. Reboot to system, and you're now rooted.
6. Reboot into recovery.
7. From stock recovery select "enter fastboot" this takes you to "fastboot d" mode.
8. Flash twrp while you're in fastbootd mode.
9. Enjoy! Everything is working perfectly. Rebooting to recovery takes you to TWRP. Rebooting to system gives you root. We also have full decryption support.
Click to expand...
Click to collapse
I'm rather new to the scene, everything you're saying here makes sense except the copypartions.zip. Is this something that is the same for all phones or is there a special file i should have for the g fast?
and still bootloop lmao, im doing the exact steps provided exactly as i see them on this thread, christ ill send 20 bucks through paypal to whoever makes a actual detailed guide with explanations on what to do like for example what is the copy partitions zip? whats it for? do i make a patched boot image first if im coming from full stock? do i do any of this to the other partition? treat it like your making it for noobs like christ is it that hard to help out now lmao
ninjakira said:
and still bootloop lmao, im doing the exact steps provided exactly as i see them on this thread, christ ill send 20 bucks through paypal to whoever makes a actual detailed guide with explanations on what to do like for example what is the copy partitions zip? whats it for? do i make a patched boot image first if im coming from full stock? do i do any of this to the other partition? treat it like your making it for noobs like christ is it that hard to help out now lmao
Click to expand...
Click to collapse
If you have done an OTA update on the phone, AFAIK you don't need the copy-partitions.zip. The zip copies needed partitions from the used slot to the unused slot. So if it does change from one to another, you aren't left with a completely blank slot with nothing on it. (As i said, if you have done a OTA update, both slots will be populated, so it isn't necessary to flash the zip..)
SOMEONE SMARTER THAN ME CORRECT ME IF IM WRONG ON THE ABOVE STATEMENT PLEASE
So.. assuming you are on clean stock and you have done an OTA update... In fastboot:
(make sure you have a magisk.zip on your phone or sd card)
Code:
fastboot flash recovery <twrpfilename>.img
Then enter recovery mode from the bootloader menu you are still in.
Wait for twrp to load, install magisk, reboot.
Profit.
Now you are rooted, with twrp permanently installed.
p.s: Keep the 20 bucks and send it to vache :silly: