Database Users

BEST Rooting and twrp flashing without pc for m9 **TESTED ON ANDROID 7.0**

HTC One (M9) ReadMe Thread
Q4: Which versions of TWRP and SuperSU are the recommended ones?
A: The answer depends on your current firmware version. If you're using firmware 4.x then you'll find your answer here in the FAQ of the TWRP thread. (Click here, if you can't find SuperSU 2.79 SR3.) For firmware 1.x and 2.x the recommended versions are Captain_Throwback's Beta 1 of TWRP 2.8.7.1 and SuperSU 2.49. For firmware 3.x the recommended versions are TWRP 3.1.1-0 (official) and SuperSU 2.65. Using different versions than the recommended ones will probably lead to a bootloop. The M9 isn't compatible with the ramdisk changes that get executed by many flashable system-less SuperSU versions. However, updating the SuperSU app and its binaries via the Play Store after flashing one of the older versions is safe.
Q5: Are there alternative methods for gaining root?
A: Yes, you can use Magisk if you're using firmware 4.x. (Maybe a user with a lower firmware version can test whether Magisk is usable on firmware 1.x to 3.x, as well?)
Click to expand...
Click to collapse
Requirement
1. S-OFF AND UNLOCKED BOOTLOADER OF HTC ONE M9 (FILE PROVIDED IS FOR INTERNATIONAL VERSION. IF YOU WANT CREATE YOUR CARRIER PHONE COMMENT BELOW )
Method
STRAIGHT TO THE POINT just download the 2 zips provided below and place it in external sd card of phone and reboot to download mode
It will ask to flash press the vol up button and after flash you will have twrp flashed (i had included latest twrp recovery in the zip file but you can place in zip the recovery of your choice but you have to rename it to recovery.img)
NOTE DONT RENAME THE ZIP OR ELSE IT WILL NOT FLASH AND SECONDLY DONT CHANGE THE TXT FILE IN THE ZIP
after flash go to recovery and flash supersu zip
Downloads
Mod Removed
Help Section
Comment or pm me if you are facing any problem and want to get help
If you liked my work hit the appreciation button and if you want to grow my projects donate me as i dont have enough resources

Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk

shaqman89 said:
Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post

ahmad.abbas54 said:
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post
Click to expand...
Click to collapse
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.

computerslayer said:
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.
Click to expand...
Click to collapse
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached

ahmad.abbas54 said:
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached
Click to expand...
Click to collapse
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.

computerslayer said:
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.
Click to expand...
Click to collapse
I am also sorry if i used some rude words
Still i had checked recently on twrp.me and there's only 3.0.2 for m9 and i am using it right now with supersu 2.79
I am not facing any problem at all in all matters and it is also much stable
You can still update according to your need as you can open up my provided zip and add recovery.img of your choice and also you can flash supersu of your choice

@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 (unofficial) is capable of installing HTC's official OTAs.

Flippy498 said:
@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 is capable of installing HTC's official OTAs.
Click to expand...
Click to collapse
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post

ahmad.abbas54 said:
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post
Click to expand...
Click to collapse
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc

ahmad.abbas54 said:
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc
Click to expand...
Click to collapse
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.

Flippy498 said:
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.
Click to expand...
Click to collapse
Well thats for obvious that we need pc for atleast bootloader unlock

I'm trying this method to flash TWRP on my unlocked, S-Off m9. (Unlocked with SunShine, my Mac with new USB-C port doesn't see device over ADB) I've unzipped your TWRP package, replaced the old TWRP with the latest--renamed "recovery.img"--and re-zipped it. When I boot phone into Download mode, the script recognizes the zip package, and "start ui-update" appears at the top of the screen. Nothing else happens, and if I eventually force power off, the stock Recovery is still installed. Suggestions?

Do S-OFF AND UNLOCKED BOOTLOADER not need a computer ؟؟؟؟؟؟
!!!!!!!!!!!!!!
Please close this trivial matter

Out of my depth with MultiROM/TWRP problem; could use some guidance

Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!

KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning signifies a mismatched vendor and system partition. The vendor partition was integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS base. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. The phone will fail to boot if you mismatch the vendor.img with a different OS base. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat.
Click to expand...
Click to collapse
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.

SlimSnoopOS said:
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
Click to expand...
Click to collapse
Thanks so much for the swift reply! I'll check these links out right away. I'm sure they will fill in the gaps for me.
Best,
KT

KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.

jhs39 said:
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0..
Click to expand...
Click to collapse
MultiRom support for this device was released when Marshmallow was out. So MR33 is based on the Marshmallow branch and ships with 3.0.2. The developer just isn't ready to release support for Nougat 7.0 and couple that with the issues of TWRP 3.0.2-x. He's actively pushing commits to support Nougat.
Sent from my Nexus 5X using Tapatalk

jhs39 said:
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
Click to expand...
Click to collapse
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.

KilgoreTrout71 said:
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
Click to expand...
Click to collapse
It might just take a while for the service to go through. Good luck.

[Discussion] DualBootPatcher

I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.

Got now rr as primary rom and will try later on to flash some roms on the second space... Let you know if that works out.

Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk

superior8888 said:
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
Click to expand...
Click to collapse
I have also rr as primary but second rom install ended in error 1 in twrp. Maybe you can try to reset data of second rom with the dualboot patcher zip.

It might be helpful to read the Dual Boot Patcher thread for the OP5, as there may be some important info there that is relevant for getting it to work on the 5T.

I tried rr as primary, no problem. Tried adding 2nd rom as secondary, as data slot 1, and no dice. Even tried removing assert lines in the updater script as suggested in op5 with rr as 2nd rom but that didn't work either; either booted back to twrp or booted to a black screen. If anyone makes it work please document and share your work. I'm encrypted by the way, even though you're "supposed" to be decrypted I was able to switch between primary and the non-booting rom just fine.

Anyone having any luck with this?

matteosaeed said:
Anyone having any luck with this?
Click to expand...
Click to collapse
Nope primary install goes good with a oos rom not stock. But when you try to install a second rom it gives error 1 in twrp and rom don't boot up.

That's great! Old MultiROM user here!

Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?

superior888 said:
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Click to expand...
Click to collapse
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN ?
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.

cubandanger05 said:
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
Click to expand...
Click to collapse
Thanks for updating us, I'm an old multirom user as well and I'm going to keep my eye on this.

cubandanger05 said:
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
Click to expand...
Click to collapse
Thanks! I'll try this next days.

Thanks. Nothing works with Oreo as of yet i suppose :/

superior888 said:
Thanks. Nothing works with Oreo as of yet i suppose :/
Click to expand...
Click to collapse
It may be possible to have oreo as primary and flash Nougat as data slot roms. I tried with Phoenix as primary and I could boot into rr Nougat in data slot but Phoenix wouldnt boot. If someone can try rr oreo as primary and report back. I'm tempted to try with otg and see if I can install secondary roms using extsd option

*Quick update*
I was able to keep latest Phoenix oreo ROM as primary and install and boot Nougat RR as data-slot and as secondary using the latest dualbootpatcher app which may have fixed the "failed to update mbtool" error I was getting on Phoenix ROM. Also I used Magisk 14.0 for root as the latest version 16.0 kept booting back to recovery on non primary ROMs.
I'm still unable to flash Oreo ROMs as data-slot or secondary. At least we're able to keep Oreo as primary and test Nougat ROMs until dualbootpatcher app is compatible with Oreo or until some other fix is released.
Internal storage/data is still encrypted and unreadable on all non-primary ROMs; you must be decrypted prior to installing additional ROMs to have access to it, which I haven't tested yet.
See screenshots

Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.

es0tericcha0s said:
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
Click to expand...
Click to collapse
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Edit: Now that it's working almost as intended we should make an official "how to" thread

cubandanger05 said:
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Click to expand...
Click to collapse
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.

es0tericcha0s said:
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
Click to expand...
Click to collapse
? understandable

TWRP, Rooting and Custom Rom HELP SM-T510 Tablet Tab A 10.1

Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)

You don’t unzip the .tar files. Keep them as is.

secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5

My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.

fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.

is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse

fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!

framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?

framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.

lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.

framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.

lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY

framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.

lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!

framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.

Moto G7 Ready To Install LineageOS, But Scared

I have Moto G7 (River, XT1962-4) with the bootloader unlocked by fastboot ("fastboot oem unlock <unlock code>"). I am ready to install LineageOS, and I haven't yet installed a recovery package.
However, it appears that the A/B slots (partitions?) are still causing a lot of ROM install difficulty. especially with the moto g7. So, it's a bit concerning.
The problem seems to stem from the fact that, when slot A is active and one flash esLineage OS using TWRP (or Lineage recovery), the image is written to slot B and and the phone switches to booting from slot B. Then, rebooting fails because there is no bootloader in slot B. Is my understanding correct?
It seems that most favor TWRP over the LineageOS recovery package. So, I would like to install TWRP.
The LineageOS instructions for temporarily booting and installing TWRP differ from the install instructions given on the TWRP Moto G7 page.
The Lineage page directs the user to employ fast boot ("fastboot flash boot <twrp_filename>.img") with "a boot__a" or "boot__b" flag, to install TWRP to the desired slot. Unfortunately, these instructions don't tell how/where to use that flag in the fastboot command syntax.
On the other hand, the TWRP page instructs users to install TWRP via their installer. That TWRP installer puts TWRP in both the A and B slots.
It seems that the TWRP procedure is more foolproof, but does that method bork the later steps given in the LineageOS instructions?
The next step is given in the "Pre-install instructions" on the LineageOS page. It says to sideload the copy-partitions.zip package with TWRP booted (and already installed).
The copy-partitions.zip package copies slot A to slot B (or vice versa), so that it exists in whichever slot the phone chooses. This process is explained in the LineageOS install page for the Moto G7. This process seems easy, but, again, will it be borked by the previous TWRP installer that addressed both slots?
The rest of the procedure seems fairly straightforward, but will my phone be rooted automatically? If not, how does one root the phone (what app/package should I use)?
Also, in most ROM install tutorials on the Interwebs, there usually comes a point in which certain things are "wiped," such as "Dalvic/ART cache," "cache" and "data." I see that there is a "Wipe" step and a "Format" step in the "Installing LineageOS from recovery" section of the Lineage instructions, but neither step specifies "Dalvic/ART cache," "cache" nor "data." Are those the things that are being wiped?
Thanks very much!

go on telegram and get instructions there as XDA is outdated

HueyT said:
go on telegram and get instructions there as XDA is outdated
Click to expand...
Click to collapse
Thank you for the reply!
I am not familiar with Telegram. Does one have to give their phone number and other sensitive information to sign up there?
What do you mean by "XDA is outdated?" I see lots of recent posts on this forum, with one or two that specifically pertain to the problems regarding attempting a LineageOS install on a Moto G7.
Hopefully, somebody here has experience dealing with A/B partitions and can give me a quick answer as to whether or not using the TWRP installer will bork things, when I later try to copy the bootloader to the inactive slot by sideloading "copy-partition.zip."
Thanks!

tuppb said:
Thank you for the reply!
I am not familiar with Telegram. Does one have to give their phone number and other sensitive information to sign up there?
What do you mean by "XDA is outdated?" I see lots of recent posts on this forum, with one or two that specifically pertain to the problems regarding attempting a LineageOS install on a Moto G7.
Hopefully, somebody here has experience dealing with A/B partitions and can give me a quick answer as to whether or not using the TWRP installer will bork things, when I later try to copy the bootloader to the inactive slot by sideloading "copy-partition.zip."
Thanks!
Click to expand...
Click to collapse
Installation instructions on LOS page are not good. If you go to the AEX rom here on XDA, those instructions are better. The thing is XDA is not really used by the devs too much. Its better to go to the telegram group. The only info telegram uses is your phone number to sync up.
http://t.me/motog7river
Also, telegram group has many more roms, and if you have problems its much easier to get help there.

JAS_21 said:
Installation instructions on LOS page are not good. If you go to the AEX rom here on XDA, those instructions are better. The thing is XDA is not really used by the devs too much. Its better to go to the telegram group. The only info telegram uses is your phone number to sync up.
Also, telegram group has many more roms, and if you have problems its much easier to get help there.
Click to expand...
Click to collapse
Thank you!
I searched for a specific AEX (aosp extended) rom section on this forum, and I couldn't find one. I did find a few threads regarding releases, but no official install instructions. Couldn't find anything on the AEX site, too. Do you have a link to those instructions?
I am unable to get on Telegram -- can't give out my phone number and online SMS sites seem to be useless.
It's a shame that folks don't use open forums such as this one.
Thanks!

UPDATE: I am happy to report that _Clon_'s guide to installing Lineage 17.1 worked on my Moto G7!
If you get an error message when using fastboot to set the active slot to "_a" in step 1.4, move on, because setting the active slot to "_a" can wait until step 1.6 whne it is set with TWRP.
By the way, when I ran the "fastboot getvar all" (in step 1.3), it showed that my current slot was "_b" and that slot "_a" was not bootable. Slot "_a" became bootable when I ran the TWRP installer (in step 4.1). My LineageOS 17.1 install runs from slot "_a".
In addition, it seems that Lineage Recovery has some advantages over TWRP. I have seen posts in other forums suggesting that LOS OTA updates will install Lineage Recovery over the installed TWRP (which is what I want).
Thanks, _Clon_!