Database Info

930A ATT S7 Snapdragon Xposed framework

Hey guys, so I just found out about this site and am a super noob but managed to Root my ATT S7 last night. I have been trying to install the Xposed framework but it looks like I cant get a custom recovery program onto my S7. Does anyone know how to get TWRP or CWM or any custom recovery onto the 930A? Or for that matter, Xposed install without a custom recovery?

jk_9982 said:
Hey guys, so I just found out about this site and am a super noob but managed to Root my ATT S7 last night. I have been trying to install the Xposed framework but it looks like I cant get a custom recovery program onto my S7. Does anyone know how to get TWRP or CWM or any custom recovery onto the 930A? Or for that matter, Xposed install without a custom recovery?
Click to expand...
Click to collapse
Hi mate
Nothing yet ...... maybe soon now that is possible to root

MAX 404 said:
Hi mate
Nothing yet ...... maybe soon now that is possible to root
Click to expand...
Click to collapse
Actually I found out how to do everything and make it pretty smooth. Rooted, with Xposed and a bunch of fixes to make it almost as smooth as stock. Let me know if you are still looking.

jk_9982 said:
Actually I found out how to do everything and make it pretty smooth. Rooted, with Xposed and a bunch of fixes to make it almost as smooth as stock. Let me know if you are still looking.
Click to expand...
Click to collapse
Hi
of course mate , please share

MAX 404 said:
Hi
of course mate , please share
Click to expand...
Click to collapse
Sure, I'll start from the beginning in case any other new people are wondering.
Basically, back up your files and restore your phone to factory so the root goes smoother.
Then proceed to this thread for the root. Oh yeah, install adb if you don't have it. They dont mention it and assume you know what it is, which noobs like me don't.
After a clean root, install Flashfire (you may need to disable samsung updates and reset the phones clock back to 2012 or something if Flashfire doesn't want to start). I used 0.31, maybe the newest will work? Easy to find in google.
On page 8 of the Root thread, there is a dropbox link to the Xposed apk and zip (Here). Move them to your phone and install the apk, then use Flashfire to boot the zip.
I think that's pretty much it, Xposed should be running after the Flashfire reboot (which can take a long time as it will Optimize apps).
psouza4 has an awesome thread on what to do after Root and Xposed to make the phone run smoother.
If you do something wrong and absolutely can't fix it, see here for re-flashing back to stock.
Hope this helps someone, took me about 2 days to search all of this out. The AT&T S7 is such a pain in the ass with it's locked bootloader, but this place is > AT&T!

jk_9982 said:
Sure, I'll start from the beginning in case any other new people are wondering.
Basically, back up your files and restore your phone to factory so the root goes smoother.
Then proceed to this thread for the root. Oh yeah, install adb if you don't have it. They dont mention it and assume you know what it is, which noobs like me don't.
After a clean root, install Flashfire (you may need to disable samsung updates and reset the phones clock back to 2012 or something if Flashfire doesn't want to start). I used 0.31, maybe the newest will work? Easy to find in google.
On page 8 of the Root thread, there is a dropbox link to the Xposed apk and zip (Here). Move them to your phone and install the apk, then use Flashfire to boot the zip.
I think that's pretty much it, Xposed should be running after the Flashfire reboot (which can take a long time as it will Optimize apps).
psouza4 has an awesome thread on what to do after Root and Xposed to make the phone run smoother.
If you do something wrong and absolutely can't fix it, see here for re-flashing back to stock.
Hope this helps someone, took me about 2 days to search all of this out. The AT&T S7 is such a pain in the ass with it's locked bootloader, but this place is > AT&T!
Click to expand...
Click to collapse
Great mate !! i am sure it will help others

OK so which option did you choose on flashfire?
I'm about to do this
jk_9982 said:
Sure, I'll start from the beginning in case any other new people are wondering.
Basically, back up your files and restore your phone to factory so the root goes smoother.
Then proceed to this thread for the root. Oh yeah, install adb if you don't have it. They dont mention it and assume you know what it is, which noobs like me don't.
After a clean root, install Flashfire (you may need to disable samsung updates and reset the phones clock back to 2012 or something if Flashfire doesn't want to start). I used 0.31, maybe the newest will work? Easy to find in google.
On page 8 of the Root thread, there is a dropbox link to the Xposed apk and zip (Here). Move them to your phone and install the apk, then use Flashfire to boot the zip.
I think that's pretty much it, Xposed should be running after the Flashfire reboot (which can take a long time as it will Optimize apps).
psouza4 has an awesome thread on what to do after Root and Xposed to make the phone run smoother.
If you do something wrong and absolutely can't fix it, see here for re-flashing back to stock.
Hope this helps someone, took me about 2 days to search all of this out. The AT&T S7 is such a pain in the ass with it's locked bootloader, but this place is > AT&T!
Click to expand...
Click to collapse

noobtxtech said:
I'm about to do this
Click to expand...
Click to collapse
Yup thats it, hit the check box and then you will have a flash button on the bottom.

jk_9982 said:
Yup thats it, hit the check box and then you will have a flash button on the bottom.[/QUOTE
It worked, thank you!
Click to expand...
Click to collapse

noobtxtech said:
jk_9982 said:
Yup thats it, hit the check box and then you will have a flash button on the bottom.[/QUOTE
It worked, thank you!
Click to expand...
Click to collapse
Awesome, glad I could help.
Click to expand...
Click to collapse

jk_9982 said:
noobtxtech said:
Awesome, glad I could help.
Click to expand...
Click to collapse
Have you successfully been able to disable that annoying high volume warning? Really really need that thing to go. I tried disabling it using gravity box but it doesn't work
Click to expand...
Click to collapse

How do I uninstall xposed? because i cannot log into snapchat

FreshIce21 said:
How do I uninstall xposed? because i cannot log into snapchat
Click to expand...
Click to collapse
Flash the Xposed uninstaller from recovery or factory reset, or flash a stock ROM over the top

*Detection* said:
Flash the Xposed uninstaller from recovery or factory reset, or flash a stock ROM over the top
Click to expand...
Click to collapse
I'm on a galaxy s7 snapdragon (ATT) and I use flash fire to flash the uninstaller. Which uninstaller should I use? The default one, one for samsung devices, or one for galaxy s7

FreshIce21 said:
I'm on a galaxy s7 snapdragon (ATT) and I use flash fire to flash the uninstaller. Which uninstaller should I use? The default one, one for samsung devices, or one for galaxy s7
Click to expand...
Click to collapse
The one for the version of Xposed you flashed I would think, I haven't flashed it on my S7, best to ask in the Xposed main thread

Alcatel OneTouch Flint TWRP

So i was finally able to install TWRP after rooting using this guide from @Casey Campanile
http://forum.xda-developers.com/android/development/alcatel-onetouch-flint-root-t3440088
**You must have ROOT first**
So it is actually pretty simple,
*Download the file i uploaded
*Unzip the TWRP file
*Download FlashFire
Now I did have OEM Unlock in Developer Settings and BusyBox installed when I did this, not sure if it makes a difference.
*Make sure BusyBox is up to date
1. I suggest doing a backup
2. Flash the TWRP file that you unzipped as Firmware Package
3. Done
DO NOT ATTEMPT TO WIPE DEVICE THROUGH THE OPTION IN SETTINGS!!!
P.S. all this is done at your own risk. im not responsible for any bricked devices.
Thanks for the edit suggestions @Casey Campanile

jsowen321 said:
So i was finally able to install TWRP after rooting using this guide from @Casey Campanile
http://forum.xda-developers.com/android/development/alcatel-onetouch-flint-root-t3440088
**You must have ROOT first**
So it is actually pretty simple,
*Download the file i uploaded
*Unzip the TWRP file
*Download FlashFire
Now I did have OEM Unlock in Developer Settings and BusyBox installed when I did this, not sure if it makes a difference.
*Make sure BusyBox is up to date
1. I suggest doing a backup
2. Flash the TWRP file that you unzipped as Firmware Package
3. Done
P.S. all this is done at your own risk. im not responsible for any bricked devices.
Thanks for the edit suggestions @Casey Campanile
Click to expand...
Click to collapse
I can't believe no one has thanked you or at least said good going on this.I've had my Flint for about 6 months and used it as a backup mostly.I was sitting at work tonight waiting on the boss and I decided to look up and see if anyone had did anything with the Flint yet.I was floored when I came across your post. Everything is working great with TWRP but if I let it timeout and screen go dark it won't allow me to swipe to unlock.Not a big deal to me but I wanted to report it to you since no one else seems to be commenting on this.I appreciate your hard work and taking the time to do it. Great job!!! ? ??

jsowen321 said:
So i was finally able to install TWRP after rooting using this guide from @Casey Campanile
http://forum.xda-developers.com/android/development/alcatel-onetouch-flint-root-t3440088
**You must have ROOT first**
So it is actually pretty simple,
*Download the file i uploaded
*Unzip the TWRP file
*Download FlashFire
Now I did have OEM Unlock in Developer Settings and BusyBox installed when I did this, not sure if it makes a difference.
*Make sure BusyBox is up to date
1. I suggest doing a backup
2. Flash the TWRP file that you unzipped as Firmware Package
3. Done
P.S. all this is done at your own risk. im not responsible for any bricked devices.
Thanks for the edit suggestions @Casey Campanile
Click to expand...
Click to collapse
I've got an issue with TWRP I can't seem to find anything on.Wanted to see if you could help me figure it out.Initially after installing all was well.Made a backup and rebooted.Today,a month later I wanted to do a factory reset and Initially tried via settings/backup/device reset.It just rebooted back to home screen.I then rebooted into TWRP and tried via wipe but nothing will mount.My SD card won't even mount and everything shows all 0's.Any ideas?I'm not a noob by any means but I can't figure this one out.

bob24260 said:
I've got an issue with TWRP I can't seem to find anything on.Wanted to see if you could help me figure it out.Initially after installing all was well.Made a backup and rebooted.Today,a month later I wanted to do a factory reset and Initially tried via settings/backup/device reset.It just rebooted back to home screen.I then rebooted into TWRP and tried via wipe but nothing will mount.My SD card won't even mount and everything shows all 0's.Any ideas?I'm not a noob by any means but I can't figure this one out.
Click to expand...
Click to collapse
Hmm, that's seems weird haven't experienced that before. I haven't tried to do a full swipe yet on this phone. Did it complete the wipe?

jsowen321 said:
Hmm, that's seems weird haven't experienced that before. I haven't tried to do a full swipe yet on this phone. Did it complete the wipe?
Click to expand...
Click to collapse
No it didn't.I couldn't get anything to mount in recovery to complete a wipe.I think perhaps that we should do a warning about trying to wipe from backup/reset in settings.At least until we figure this out.I was finally able to do a reset via Flash fire but nothing will mount in recovery still.

bob24260 said:
No it didn't.I couldn't get anything to mount in recovery to complete a wipe.I think perhaps that we should do a warning about trying to wipe from backup/reset in settings.At least until we figure this out.I was finally able to do a reset via Flash fire but nothing will mount in recovery still.
Click to expand...
Click to collapse
That sounds like a good idea only thing I would try is to try and restore the backup you did and try and reflash TWRP see if that does anything I have yet to try and reset this phone considering its my daily phone currently my lg g3 suffered the fading screen and I couldn't get it fixed

jsowen321 said:
That sounds like a good idea only thing I would try is to try and restore the backup you did and try and reflash TWRP see if that does anything I have yet to try and reset this phone considering its my daily phone currently my lg g3 suffered the fading screen and I couldn't get it fixed
Click to expand...
Click to collapse
I can't restore anything. Can't mount anything in recovery.Here in next couple weeks I'll be glad to send you my Flint.I'm getting a One Plus 3.

bob24260 said:
I can't restore anything. Can't mount anything in recovery.Here in next couple weeks I'll be glad to send you my Flint.I'm getting a One Plus 3.
Click to expand...
Click to collapse
Lol I'm actually looking into one of those too or I was looking at the honor line too but OnePlus seems better

jsowen321 said:
Lol I'm actually looking into one of those too or I was looking at the honor line too but OnePlus seems better
Click to expand...
Click to collapse
I highly recommend the Honor 5x if youre budget inclined and the Mate 8 if you have a few extra $$.I had the 5x and it actually is a damn nice device.I beat the Nexus 6 in Antutu scores with it.

bob24260 said:
I highly recommend the Honor 5x if youre budget inclined and the Mate 8 if you have a few extra $$.I had the 5x and it actually is a damn nice device.I beat the Nexus 6 in Antutu scores with it.
Click to expand...
Click to collapse
That's pretty impressive I'm gonna look into that one, one thought just crossed my mind you try flashing your recovery through the fastboot commands on the bootloader?

I tried reflashing every way possible.Still nothing will mount.I think you may want to add a warning to the OP not to try and factory reset via settings.Maybe we can figure it out.

I added it to the OP. Something that might help is when I was digging thru this phone I found out it's the same as the Alcatel pop 3 5.5 looks like they just renamed it

OMG, this has been great. Im all rooted and TWRPd with my Flint now. It is a great feeling, but Im not sure what to do next Are there any benefits to this now? I can't find any custom roms for it...is there a way to get something newer than Android 5.1.1 installed?

molebrain said:
OMG, this has been great. Im all rooted and TWRPd with my Flint now. It is a great feeling, but Im not sure what to do next Are there any benefits to this now? I can't find any custom roms for it...is there a way to get something newer than Android 5.1.1 installed?
Click to expand...
Click to collapse
No custom ROMs rn but u can install Xposed for lollipop and u can remove bloatware with titanium backup

Cool, so, I'm not clear what Xposed gives me though. Is it worth it?

Hey Xposed has different modules you can install, my favorite are YouTube background play and YouTube ad blocker but they have various ones, just take a look on the downloads section in xposed

jsowen321 said:
Hey Xposed has different modules you can install, my favorite are YouTube background play and YouTube ad blocker but they have various ones, just take a look on the downloads section in xposed
Click to expand...
Click to collapse
Wow, my day is complete. This is great. Going to install soon. Ive been looking for a YouTube ad blocker! :good:

Just wanted to follow up again and say thanks for pointing me to this. I've got the framework installed and now im going through the modules, picking what looks good to me. This is pretty much all I needed I dont care if we never get a custom rom at this point.

Your welcome, there's a lot of modules, I would say just be careful which ones you install and use. Ive had some that gave me problems

CyanogenMod a possibility?

I want to root my pixel 2

I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you

ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk

ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
Diesel_Jeremiah said:
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
TWRP actually just came out of beta with 12/12 Walleye(12/14 Taimen) build, hopefully there will be some custom roms soon... You can use the Skipsoft Android toolkit to root, unlock, flash twrp etc. Or do it manually following guides here on XDA under development section https://forum.xda-developers.com/pixel-2/development, ADB has been updated so make sure to have the latest platform tools.

Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.

bland.life said:
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
Click to expand...
Click to collapse
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page

ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?

ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?

ImIntoStuff said:
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
Click to expand...
Click to collapse
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk

Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Oh..so the android system error always happens? Ok..it does not seem to affect anything.
I used the Skipsoft package, which does all the things. Couple snags, it only wanted to accept the beta of magisk.
I'm thinking I got it all right now. I will report back if I find a problem

Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
So rooting your Pixel 2 will invariably trigger this error message on boot, for any user?
Are there other undesirable side effects to rooting your Pixel 2 at the moment?
Thanks

Moto One 5G Ace Rooted with TWRP using stock Firmware

First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.

Your first link doesn't work for me. The Adaway link works. FYI.

RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.

Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.

Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.

iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.

egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.

iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??

egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.

iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.

egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.

Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance

Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.

ADB and 8T

Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R

Try nother USB C cable. Some not able to handle data.

rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!

Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/

BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!

Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R

Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.

BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??

Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.

BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!

Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11

BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,

Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".

BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,

Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!

Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R

Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.

BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..

Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone