Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
I know there has been many threads giving explicit instructions on how to unlock bootloader, gain s-off, and install TWRP recovery. But I am having problems/questions that no one (at least of what I've read) has encountered. I will try and make this clear for y'all but bear with me. Before I start just let it be known that I DO HAVE my bootloader unlocked. I ended up going to a cell phone repair place and paying a small fee to get my bootloader unlocked.
1. Do I need to gain s-off to be able to root and install TWRP recovery?
I say this because the I have tried the has00n application to unlock bootloader, gain s-off, root, and install TWRP recovery, but I ran into problems with my computer recognizing my device. I had all the necessary files downloaded (at least to my knowledge) but it honestly just wouldn't recognize my device.
2. If I do not need to gain s-off to install TWRP recovery and install a custom ROM (I'm going to be installing Cyanogenmod), how do I go about doing that?
Honestly I'm so fed up with this that I just want to sell this phone and get another one, all I want to do is get Cyanogenmod on this phone but it's so immensely difficult.
Please help me! I have been trying to get this accomplished for so long but I feel like because this phone is older all the info about how to root and gain s-off is outdated.....
All of your help is greatly appreciated!!
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. So as of right now I am using the fastboot adb to control my phone from the command prompt on the computer, but there is a problem. When I try and flash the custom recovery (either TWRP or CWM) it says that the files are unrecognizable, so they're pretty much corrupted. I honestly don't know that to do. I know I can achieve root if I just get either one of these recoveries to flash but it seems that all the files for the htc one m8 TWRP and CWM are corrupted. What are you suggestions at this point? The fastboot iadb is working perfect I just need a non-corrupted recovery file and I'm searching around the internet withno luck of finding one. Is there one that you can attest to working? If so that would be amazing. Again, thanks for your help, hopefully we can get this sorted out!
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something ?
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
Click to expand...
Click to collapse
Can you copy and paste your command window to this thread? It would help to see the exact error outputting. You can highlight and right click to copy anything from command window.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either.
Click to expand...
Click to collapse
Is the phone currently on Lollipop, or otherwise? You can't know what version TWRP is correct, without this info. Current TWRP (2.8.7.0) won't work if the phone is on older OS version. Vice versa, if the phone is currently on Lollipop, older versions of TWRP (I believe older than 2.8) won't work. You have to flash the specific TWRP version that matches your OS version. Guessing which TWRP version to flash is not the right way to go about this.
Also, you need to tell us the actual TWRP version number you got, and where you downloaded it from. I've seen quite a few instances where folks thought they had the "most recent" version, but in fact they weren't even close. Its always best to be specific as possible, and provide all the details when getting help here.
Additionally, go into Settings (or do getvar all), and tell us the software number. If you got the Stagefright patch, it might be screwing up install of TWRP as well.
flapjackSam said:
The fastboot command i am using is the same as the one you stated. There's just a problem with the files..
Click to expand...
Click to collapse
Again, just saying you used the "same" command isn't enough. A single wrong character, wrong file name, wrong path will cause the command to fail. As the previous response requested, please cut/paste, or better yet post a screenshot of your command prompt window, so we can see the exact command syntax, and the specific error message.
I can virtually guarantee that as long as you downloaded the file direct from the TWRP website, and tried downloading (and flashing) it more than once (to eliminate the possibility of corruption during file transfer); that the issue is almost certainly pilot error.
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
MistakenUtopia said:
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
Click to expand...
Click to collapse
Press and hold the power button until is hard reboots, then hold vol down as well. You should go to boot loader before the HTC screen pops up.
Back Up!
Just a reminder, after you install TWRP, boot into recovery (TWRP) and create a backup file saved to your SD card first before trying to install a new ROM!
Always can restore if things go wrong or you don't like it.
:fingers-crossed:
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Morky001 said:
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Click to expand...
Click to collapse
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
x.ak**** said:
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
Click to expand...
Click to collapse
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Nivead said:
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Click to expand...
Click to collapse
Nivead, I did unlocked the OEM before downloading that though, but still didn't work. The phone is an unlocked phone.
And, thank you for your help.
Morky001 said:
Kumar, I did unlocked the OEM before downloading that though, but still didn't work.
Click to expand...
Click to collapse
And.. thank you.
Morky001 said:
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
Click to expand...
Click to collapse
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Nivead said:
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Click to expand...
Click to collapse
Deae Nivead,
..Oy! That sounds painful!! Guess, I have no business be doing this lock/unlock/rooting thing, huh?! Not a techie at all, this is very foreign to me! And those guys on YouTube... they lied then, said I could do all these without PC... Yeah, right! Turned out, it wasn't as easy as they were showing on videos. (((sigh))) Would be easier if I just send my phone to you?!?!!!
Thank yoooouuu soooo much for taking the time to write/tell me all this, truly appreciate your help and replies.
<Morky>
x.ak**** said:
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
Click to expand...
Click to collapse
Kumar,
I guess those YouTube tutorials omitted left out a lot of steps and not as easy nor simple as they made it to be.... "without PC" as they claimed. How would someone with no background in computer programing, nor a "techie" like you here at xda... like me would know that?! If you "don't understand how....." I wouldn't understand either!! More so than you. One thing I've learnt now, all those tutorials about rooting and TWRP. on YouTube... are crap.
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!