Hi,
I'm having an issue. The volume down button on my moto x seems to be stuck down, and if I power down or reboot, I am greeted by the fastboot screen. I cannot use the volume buttons to select a normal boot up, as volume down does nothing, and volumeup scrolls. If I plug my phone into a computer, I can use the adb to type "mfastboot continue" and resume startup. However, this places me in "Safe Mode." After soft rebooting (which bypasses the fastboot screen altogether), I still find myself in safe mode. I have the xt1058. Any help getting out of this mode would be appreciated as soon as possible.
themsftcpu said:
Hi,
I'm having an issue. The volume down button on my moto x seems to be stuck down, and if I power down or reboot, I am greeted by the fastboot screen. I cannot use the volume buttons to select a normal boot up, as volume down does nothing, and volumeup scrolls. If I plug my phone into a computer, I can use the adb to type "mfastboot continue" and resume startup. However, this places me in "Safe Mode." After soft rebooting (which bypasses the fastboot screen altogether), I still find myself in safe mode. I have the xt1058. Any help getting out of this mode would be appreciated as soon as possible.
Click to expand...
Click to collapse
When you type "fastboot reboot", does it also end up in bootloader mode?
I'm a little confused because you say that VOL DOWN does nothing, and VOL UP scrolls....it should be the opposite. VOL DOWN should scroll, while VOL UP should select. I'm curious if you could [carefully] remove the back and see if you can find something obstructing the buttons. Be careful and watch a youtube video on rear case removal if necessary.
samwathegreat said:
When you type "fastboot reboot", does it also end up in bootloader mode?
I'm a little confused because you say that VOL DOWN does nothing, and VOL UP scrolls....it should be the opposite. VOL DOWN should scroll, while VOL UP should select. I'm curious if you could [carefully] remove the back and see if you can find something obstructing the buttons. Be careful and watch a youtube video on rear case removal if necessary.
Click to expand...
Click to collapse
Yes, fastboot reboot still puts the device on the fastboot screen. I'll look into removing the case tommorow, also would doing so void my warranty in any way?
And yes, the volume up button is scrolling, and the volume down button does nothing.
themsftcpu said:
Yes, fastboot reboot still puts the device on the fastboot screen. I'll look into removing the case tommorow, also would doing so void my warranty in any way?
And yes, the volume up button is scrolling, and the volume down button does nothing.
Click to expand...
Click to collapse
If you haven't physically damaged your device (which will likely have voided your warranty already), you might consider requesting a warranty replacement.
Unless you do a bad job of disassembly, I doubt they will even know you did this.
Here is an excellent guide that will help you fix your buttons: http://forum.xda-developers.com/moto-x/moto-x-qa/motorola-moto-x-screen-replacement-t2449765
It is geared toward screen replacement, but you can just follow the disassembly to the part where the volume rocker is removed. Clean it and re-assemble.
Good Luck :good:
PS: Sent you a PM.
samwathegreat said:
If you haven't physically damaged your device (which will likely have voided your warranty already), you might consider requesting a warranty replacement.
Unless you do a bad job of disassembly, I doubt they will even know you did this.
Here is an excellent guide that will help you fix your buttons: http://forum.xda-developers.com/moto-x/moto-x-qa/motorola-moto-x-screen-replacement-t2449765
It is geared toward screen replacement, but you can just follow the disassembly to the part where the volume rocker is removed. Clean it and re-assemble.
Good Luck :good:
PS: Sent you a PM.
Click to expand...
Click to collapse
I figure what I will end up doing (painfully) is unrooting my device and restoring it to as close to factory as possible, and then contacting ATT\Motorola.
Any advice on the best way to sucessfully unroot and not have any evidence of a root in the first place? (Sorry, I've looked at previous posts, but I can't really afford to void my warranty and have to pay to replace this phone, and I'd like direct advice from somebody that does know. thanks for all your support so far)
Also, until I am able to contact ATT and get to a store, is there any way to run third-party apps in safe mode (e.g. nova launcher, twitch, etc.)
themsftcpu said:
I figure what I will end up doing (painfully) is unrooting my device and restoring it to as close to factory as possible, and then contacting ATT\Motorola.
Any advice on the best way to sucessfully unroot and not have any evidence of a root in the first place? (Sorry, I've looked at previous posts, but I can't really afford to void my warranty and have to pay to replace this phone, and I'd like direct advice from somebody that does know. thanks for all your support so far)
Also, until I am able to contact ATT and get to a store, is there any way to run third-party apps in safe mode (e.g. nova launcher, twitch, etc.)
Click to expand...
Click to collapse
First, I have no idea which method you used to root and whether or not you disabled WP, or if you unlocked. You never advised to any of this. In fact, you never even advised that you were rooted at all....
I have no idea how or if you can run 3rd party apps in safe mode.
themsftcpu said:
I figure what I will end up doing (painfully) is unrooting my device and restoring it to as close to factory as possible, and then contacting ATT\Motorola.
Any advice on the best way to sucessfully unroot and not have any evidence of a root in the first place? (Sorry, I've looked at previous posts, but I can't really afford to void my warranty and have to pay to replace this phone, and I'd like direct advice from somebody that does know. thanks for all your support so far)
Also, until I am able to contact ATT and get to a store, is there any way to run third-party apps in safe mode (e.g. nova launcher, twitch, etc.)
Click to expand...
Click to collapse
You will need to restore the fxz/XML with Rsd to unroot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
It is vol up which cancels the fast boot mode. Once you see the screen with the 4 options that is the same one Rsd uses. Unlike the older msm8960 phones the first screen is ap/fast boot & is Rsd ready.
aviwdoowks said:
You will need to restore the fxz/XML with Rsd to unroot.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
It is vol up which cancels the fast boot mode. Once you see the screen with the 4 options that is the same one Rsd uses. Unlike the older msm8960 phones the first screen is ap/fast boot & is Rsd ready.
Click to expand...
Click to collapse
Actually, there are 5 options: Normal Powerup, Recovery, Factory, Barcodes, BP Tools.
Next, he has advised that his buttons are messed up, and that VOL UP scrolls and doesn't select (he even confirmed that after I questioned it).
And third, if he has unlocked, there is NO chance of "hiding" the fact that he unlocked. This is the reason I asked for clarification about about which method he used to root.
I just mean to say that: being in that Bootloader screen is AP/fastboot. No selection/action is needed. A Rsd restore will unroot the phone.
samwathegreat said:
Actually, there are 5 options: Normal Powerup, Recovery, Factory, Barcodes, BP Tools.
Next, he has advised that his buttons are messed up, and that VOL UP scrolls and doesn't select (he even confirmed that after I questioned it).
And third, if he has unlocked, there is NO chance of "hiding" the fact that he unlocked. This is the reason I asked for clarification about about which method he used to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/moto-x-qa/play-store-crashes-download-continues-t2724215 Root information in that post, sorry for not clarifying.
Also clarifying to the post involving RSD, do I just run RSD Lite on windows and flash a vanilla ROM to my phone? (also would I be able to flash cyanogenmod, or would that violate my warranty\tos)
(EDIT: Just did some googling, from what I can tell custom ROMs are against warranty... does the same apply to official ROMs, such as the 4.4 vanilla at&t rom. Only reason I am so concerned about voiding my warranty is that I'll have to take my phone into the store to get the buttons fixed, and I'm sure the first thing they'll do is run a bunch of checks on the phone software)
Rsd is only for a factory restore, just what you need.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
aviwdoowks said:
Rsd is only for a factory restore, just what you need.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Thanks, I restored to stock. Unfortunately, I am still in safe mode which is a bit of a pain.
If you have superSU installed you can use that to unroot as there is an unroot option in there and it does work, after you unroot then uninstall superSU.
Transmissiontech said:
If you have superSU installed you can use that to unroot as there is an unroot option in there and it does work, after you unroot then uninstall superSU.
Click to expand...
Click to collapse
I had thought of that, except I couldn't actually access superSU because of recovery mode. I've already restored to stock, however. Thanks anyways!
Related
Hey guys!
So I really wanted to try out Xposed and get some modules working on my phone. So I unlocked the bootloader by following the directions from Motorola. I then used the moto x 2014 multitool to install twrp recovery and to root (#2 and #7).
I then installed the Xposed apk and flashed the zip file. All Seemed well until I started getting massive amounts of lag if my phone was on for more than 2 minutes. I thought it might be Xposed so I uninstalled it (and the 2 modules that I had installed -- youtube ad blocker and xmultiwindow). That didn't fix it though. So then I thought it might be supersu, so I updated that. That didn't work either.
So then I went back to the multitool and I chose #5... and now it won't boot. It shows the "warning bootloader unlocked" screen and then shows the motorola boot screen for 20 seconds, then shuts off. I also can't boot into fastboot by pressing down the power and volume down buttons.
Any help would be super appreciated!! I'm really not experienced with this stuff but, I had a nexus s with cyanogenmod on it which I loved and then I rooted my note 4 but that's it...
Thank you!!!
EDIT: I can get into fastboot mode, so far I just tried to select 'factory' and it went through the same "bootloader unlocked" then motorola boot for 20 seconds before shutting off...
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
dictionary said:
Maybe try getting to fastboot, selecting recovery, and then wiping cache and dalvik
Click to expand...
Click to collapse
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
HinaPanda said:
Ok I actually just got into fastboot and did a factory reset. It put me back on 4.4.4 so I'm updating to 5.1 right now.
What is the proper method to installing Xposed on this phone? I'd really like the multiwindow and adblock modules... but the intense lag that would freeze my phone after 2 minutes was just too much.
Click to expand...
Click to collapse
If you're on 5.1:
First, go here http://forum.xda-developers.com/showthread.php?t=3034811
You will need to download the XposedInstaller_3.0_alpha4.apk and the Xposed-v74-sdk22-arm.zip. It wouldn't hurt to go ahead and download the xposed-uninstaller-20150831-arm.zip either, in case you have problems.
Now you need TWRP. Flash it using fastboot by typing fastboot flash recovery (name of recovery image file.img) from a terminal. Or download TWRP Manager from the Play Store and flash it from there.
Finally, flash the Xposed-v74-sdk22-arm.zip in TWRP. Reboot and install the XposedInstaller_3.0_alpha4.apk.
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
dictionary said:
For that I don't have an answer. I don't really have a need for Xposed much anymore, so I haven't been following. Sorry
Click to expand...
Click to collapse
Care to share why?
Phoenix232 said:
If you already have root, install TWRP from the Play Store. Otherwise, install it by using fastboot.
Care to share why?
Click to expand...
Click to collapse
I'd used it a lot when I had my htc m7 with sense, and lg g3 with stock. All I used it for were really mods to make it more AOSP like. There were some features that I miss, like FakeWifi, and App Settings, to name two, but overall with AOSP ROMs out, I haven't had as much desire.
Ok... so the update bricked the phone even more I didn't see the threads that said to not do the OTA update from 4.4.4.
I connect it to the computer and see the qhsusb_bulk. I installed the drivers and now I see the qualcomm 9008. I tried using a couple of blankflash files to fix it, but none of them work. Even ones that say they're for the moto x 2014. Is there anything I can do? I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Can I send it into motorola for a warranty repair? I have a pure edition and I live in the US. I don't know if unlocking the bootloader and rooting will cause motorola to not repair it.
HinaPanda said:
I can't get it into fastboot mode... I was able to but then I don't know what happened and now I can't.
Click to expand...
Click to collapse
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
mikeoswego said:
Sometimes when your phone is messed up, it can take quite a while for the bootloader to start. If the phone is off, hold down the volume down/power button combo for a long time, like 20-30 seconds before releasing them. Then wait several seconds for the bootloader screen to appear, be patient. If the phone starts to boot, hold the vol down/power combo until the phone shuts off, continue holding for 15-30 seconds and then release, again wait a long time for the bootloader screen to appear. I don't have anything else for you but know that many times I've caused myself grief by not being patient getting into the bootloader/fastboot mode when a problem has arisen!
Click to expand...
Click to collapse
Thank you! But I actually did try holding down the power button alone and also the power + vol down for like 2 minutes or 30 seconds, etc. The 2 minutes worked the first time, but now it won't It just blinks a green light. Does that mean it's out of battery? I left it plugged into a wall charger overnight though.. how can I tell it's charging?
It sounds like you have a hard brick. Only way to fix it is to send it to a repair center.
Sent from my XT1095 using Tapatalk
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
HinaPanda said:
Yeah.. I just called motorola and the rep said they had to check on the unlocked bootloader voiding warranty thing. I told him that because I have the pure edition phone, it shouldn't void the warranty. Plus, it's bricked because of the OTA update from 4.4.4, which I believe is motorola's fault.
Does anyone have any link to a motorola statement saying that unlocking the bootloader on the pure edition does not void warranty? The rep said they'd call me back tomorrow. I tried searching on the 'netz but didn't find much.
Pure edition = developer edition, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-2014/general/unlocking-bootloader-moto-x-pure-t3004779
Looks like information is all over the place. Bummer. Hope it works out for you, especially since it was an ota. They could be cheats and try to say it failed due to the unlocked bootloader, and if you'd had root, but that would be a lie. If this rep denies you, just call back and speak to someone else.
How to Root Samsung Tab S2 T817T (Step-By-Step Guide)
Obligatory notices
This procedure is only for the Samsung Tab S2 SM-T817T
Performing any of the operations in this post risks bricking your device
Performing any of the operations in this post will irreversibly void your warranty
Performing any of the operations in this post will irreversibly trip Knox and make it unusable for Samsung Pay (and any other features which require Knox)
I am not using a SIM card with my device, so I have no idea how this procedure will impact that functionality. People on the XDA thread (forum.xda-developers.com/tab-s2/help/sm-t817t-root-t3206079) where I pieced together these instructions from suggested that the SIM card still works for mobile data. UPDATE: Later in this thread people have confirmed that mobile data DOES work after rooting. Yay!
Introduction
OK, so a brief story of how/why I was forced to figure this method out. I found a listing on eBay for the Samsung Tab S2 T810N, paid $300 for it and received it into my impatient hands. Without checking the specific version of the tab I push right into the rooting procedure I had thoroughly researched for the T810N. Suddenly my tablet is in a bootloop and I am panicking that it is ruined. In the recovery mode I see that I have the T817T. Anger towards the seller aside, I frantically research how to recover the T817T. There is virtually no documentation for this procedure, so I am forced to mix-and-match. After about 5 hours, the tablet is finally up, running, and rooted!
TL;DR - verify your model number before attempting root
Files
All the files can be found here (drive.google.com/folderview?id=0BxPb6XhrMsaoa01zdjVUVWMzQWs&usp=sharing). Let me explain what each file is:
T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (drive.google.com/file/d/0BxPb6XhrMsaoeGpmbnRoeFA5MUU/view?usp=sharing) - This is an Android 5.1.1 image for Samsung Tab S2 T817T. You may not even need this, but just in case. If you use this, unzip the file to get the .md5 file!
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.51.0.exe (drive.google.com/file/d/0BxPb6XhrMsaoc09qNm41OFhKLWc/view?usp=sharing) - Necessary Windows drivers for Samsung devices. Install this!
Odin3_v3.10.6.zip (drive.google.com/file/d/0BxPb6XhrMsaoLWtkek9UYWZGNGM/view?usp=sharing) - A flashing tool for Windows. Unzip these files!
twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) - This is a custom recovery tool for Android. Although designed for the T810 series, it does work on the T817T. Do not untar these files!
Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) - A custom bootloader for the T817T which is required to root. Do not unzip these files!
BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) - A newer version of SuperSu which works on the T817T. Do not unzip these files!
Preparation
Download all the files above. Install, unzip, and untar (or not) as instructed.
Settings -> About device - Verify that you have the SM-T817T
Settings -> About device - Verify that you are running Android 5.1.1
Backup all your files, contacts, apps, etc.
Verify that your device has at least 80% charge
Rooting Procedure
(OPTIONAL) Flash Android 5.1.1 image. This step is not necessarily required. If you are running Android 5.1.1, then you should be fine. However, this is what I had to do, since I got into a bootloop by not checking my version number first (yes, stupid me). Further, if you have any errors or issues below you absolutely will need to perform this step to recover and restart the rooting procedure. Anyway:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select T817TUVS2AOL1_T817TTMB2AOL1_T817TUVS2AOL1_HOME.tar.md5 file
Press "Start" button and wait for Green "PASS" message to appear. This will take a long time since this is a large file
Your device will automatically reboot
Perform basic setup procedures on Android so that you can access the Settings menu
From this point onward your must perform every step in the exact order as stated. Not doing so seriously risks putting your device into a bootloop or bricking it. You should be able to recover from that, but still...
Enable developer options:
Settings -> About device - click on "Build number" like 10 times until "Developer options" are enabled and button is added to Settings menu
Settings -> Developer options - enable:
Developer options - ON
OEM unlock - ON
USB debugging - ON
Flash TWRP recovery software:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) file
Press "Start" button and wait for Green "PASS" message to appear
Your device will automatically reboot, verify that the tablet boots properly
Copy bootloader and SuperSu to tablet:
With your tablet on, attach it to your computer with a USB cable
Navigate to the root directory of the tablet storage
Copy Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) and BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) files to the root directory
Detach tablet from your computer
Flash custom bootloader with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select Tab_S2_t817T_boot.zip and click "Install"
Verify install with slider
STOP HERE!!! READ THE NEXT STEPS CAREFULLY!!!
TWRP will now offer to install SuperSu for you. DON'T DO IT!! Doing this will cause your tablet to bootloop because it is not the right version of SuperSu
Decline the SuperSu installation and restart your tablet
Verify that the tablet boots properly
REPEAT "Flash TWRP recovery software:" instructions. This is a necessary step. Without it your tablet will go into a bootloop and you will need to start the root procedure over. Weird, I know. Just do it.
Flash SuperSu with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select BETA-SuperSU-v2.52.zip and click "Install"
Verify install with slider
Reboot the tablet
DONE! Assuming your tablet boots properly your should now be rooted and see the SuperSu app installed on your tablet.
Recovery
If you need to recover from some error you will need to start over completely. Use the Android 5.1.1 image file T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (same as above) to perform this. You can also use this Android image to restore the device to an unrooted version. This will not restore your warranty or Knox.
Extras
To get rid of the pesky KNOX security notification which will persist, use a program like ROM Toolbox Lite (play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en). In the App Manager select the following apps and 'freeze' them:
SecurityLogAgent 4.1.4 (this one is critical to freeze!)
KNOX 2.3.0
KNOX 2.3.1
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer 2.4.0
To get rid of the "No SIM card inserted" notification (if you aren't using a SIM card) use the build.Prop Editor in ROM Toolbox Lite. Add the following entry:
Property Name: ro.config.donot_nosim
Property Value: 1
Conclusions
I put this guide together for people who are having trouble finding a simple and easy-to-follow guide for rooting the T817T. Hopefully this can save you a number of frustrating and worrisome hours (not that rooting your Android device is ever a calm undertaking).
Please let me know if there are any errors in the procedure or if you have any suggestions regarding the steps or presentation of the material. Enjoy being a super-user!
Original content: blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T/
phduhblog said:
Long time user, first time poster.
First off, let me say, THANK YOU XDA! You guys have been a crazy valuable resource over the years.
However, with regard to the T817T, the documentation is lacking severely. I have created a comprehensive step by step guide to rooting the T817T. Unfortunately, as a first time poster, I cannot post links or anything like that so...if somebody could fix that I would appreciate it. I spent a long time formatting the posting and adding file download links with the XDA formatter so that it wouldn't look like I was link whoring to my blog, just to be told to **** off... . Seeing as that's not possible, here is the url to my blog with the rooting instructions:
blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Click to expand...
Click to collapse
http://blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Thanks my friend
Edit: Completely professional and well done how to.. written just the way I like it, fantastic!! I think you should just edit your first post and paste all this in here on XDA... and ill be happy to carry your url link for you.
Complete text of the GUIDE
Edited and posted it above. Good luck with the rooting. Thanks!
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
patrioticparadox said:
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
Click to expand...
Click to collapse
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
I had actually tried the non-auto-reboot from Odin method too, but couldn't time the change to VOLUME UP correctly. After a couple times I just gave up and tried things the long way around. Never thought to flash the zip files in the same TWRP session though. I generally like doing things the long way around and getting confirmation that things still work after each and every step. Whatever works though!
Thanks for the reply
phduhblog said:
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
Click to expand...
Click to collapse
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
patrioticparadox said:
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
Click to expand...
Click to collapse
Hmmm, odd. Sorry to hear that. Yes, mine work just fine.
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
patrioticparadox said:
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
Click to expand...
Click to collapse
Whew! I'm glad to hear that. Now people can root their T817T without concern!
Yep! Been using this for two weeks now and no problems!
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
phduhblog said:
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
Click to expand...
Click to collapse
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
androidcues said:
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
Click to expand...
Click to collapse
Hmmm. Well that's good to know at least. Thanks for the update!
Also I'm glad you were able to revert to stock and get it working.
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless ?)
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
androidcues said:
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless )
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
Click to expand...
Click to collapse
Yep, I can definitely see why vibration notifications would be important for you!
As much as I dislike bloatware, from any company, Samsung just makes the most powerful tablets/phones. My best solution is to root and disable all the bloatware.
I'm glad the guide was well received and it seems to work for people.
My mobile data and SIM functions all work fine. Not sure why yours didn't
patrioticparadox said:
My mobile data and SIM functions all work fine. Not sure why yours didn't
Click to expand...
Click to collapse
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
phduhblog said:
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
Click to expand...
Click to collapse
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
patrioticparadox said:
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
Click to expand...
Click to collapse
Wording changed! Thanks for the update.
One question pls. I have the T817V tab 9.7 w/OEM bootloader option button. Is any of this available to use for my tab? TWRP recovery maybe? Any files? Any reply is appreciated. Novice seeking knowledge. Thank you so much.
Hello everyone, I used to have an account on here years ago and I just had to create a new one for the purpose of this thread. Let me know if this type of issue has already been resolved but I have spent a great deal of time trying to locate a solution with no results. I have an older HTC One m7 I started using again to try and use the hotspot on it because I have unlimited data I needed to root it. Only reason for the hotspot is because I just moved and I am still waiting for my internet service to be hooked up on the second. Anyways, down to buisness. I made myself a developer on my device, unlocked the bootloader and installed TWRP V2.5.0.0 onto my phone. All was going well until the phone went to reboot. After it rebooted I was in the TWRP recovery menu, and I went to back up. As soon as I clicked it the phone completely froze up on that screen. And then a lock image appeared with TWRP across where the combination would go and i could still see everything in the background. Install, back up, mount, restore, settings, reboot etc. And beneath the image of the lock, which actually appears to be unlocked it says swipe to unlock and has a slider beneath it. Completely unresponsive on the screen, I cannot select anything at all. No different combinations of presses on the volume keys or power button is resetting or doing anything. I cannot even get it to turn off. I did notice, when i long press the power button the back arrow and home button flash simultaneously (on the HTC One M7 those are touch screen buttons, that are actually visible even when the device is off, but also completely unresponsive. I did notice as well that if I plug in my phone charger in the background above the menu options it shows how charged my battery is, and appears to charge when I plug it in. It is a silver, HTC One M7, AT&T version, running android 5.0.2 Thank everyone in advance, I tried to be as detailed as possible but let me know if more information is required to understand what is going on here. Thank you!
***UPDATE***
Ok everyone, issue resolved luckily since I did not get any responses on here. To anyone experiencing that same issue that I described. I let the phone die completely while it was frozen on the TWRP screen. I plugged it in while pressing down volume, and power button at same time and that allowed me to access the bootloader finally once more! From there you can select fastboot, then select reboot and everything will kick back up like normal! Just in case anyone finally stumbles across this what is a safe way to root my phone other than using TWRP? Thank you in advance!
cbmccown said:
Ok everyone, issue resolved luckily since I did not get any responses on here. To anyone experiencing that same issue that I described. I let the phone die completely while it was frozen on the TWRP screen. I plugged it in while pressing down volume, and power button at same time and that allowed me to access the bootloader finally once more! From there you can select fastboot, then select reboot and everything will kick back up like normal! Just in case anyone finally stumbles across this what is a safe way to root my phone other than using TWRP? Thank you in advance!
Click to expand...
Click to collapse
The best way to root your phone is to use the custom ROM's root manager. This is built in to cyanogenmod based roms, and doesnt require SuperSU. there is no app and it doesnt bother you about installing binaries or updating.
I always used SuperSU until I used CM.
Of all the ways to install root management, are these two the best. There is kingroot if you arent that concerned about the use of this third method.
For many the SuperSU (also installed by TWRP) is the most popular. Many will not know of the Custom ROM settings for root management and will install SuperSU over their setup. Its probably gonna be found in developer options, the root access toggle. It might be found in plain old settings though.
kruc Ire said:
The best way to root your phone is to use the custom ROM's root manager. This is built in to cyanogenmod based roms, and doesnt require SuperSU. there is no app and it doesnt bother you about installing binaries or updating.
I always used SuperSU until I used CM.
Of all the ways to install root management, are these two the best. There is kingroot if you arent that concerned about the use of this third method.
For many the SuperSU (also installed by TWRP) is the most popular. Many will not know of the Custom ROM settings for root management and will install SuperSU over their setup. Its probably gonna be found in developer options, the root access toggle. It might be found in plain old settings though.
Click to expand...
Click to collapse
Also, it always restarts if you hold the power button down for 15 *long* seconds.
KDZ V40 V409N10l
https://drive.google.com/file/d/1abM4BFQXdW2YzEdLPDcKqeMINfwGohLl/view?usp=sharing :good::good::good:
PjLyTam said:
KDZ V40 V409N10l
http://pkg02.lime.gdms.lge.com/dn/d...2JCA1I61965CIN/V409N10l_00_LGU_KR_OP_1015.kdz :good::good::good:
Click to expand...
Click to collapse
Link broken!
nyttliv7 said:
Link broken!
Click to expand...
Click to collapse
fix
Is that the international model?
guytano86 said:
Is that the international model?
Click to expand...
Click to collapse
https://www.getdroidtips.com/download-v409n10l-lg-v40-thinq/
More info on this download.
So it updates that version to 8.1.0?
This phone comes with 8.1.0 out of the box
guytano86 said:
This phone comes with 8.1.0 out of the box
Click to expand...
Click to collapse
the link above says it's 8.0 oreo update....which didn't make sense since mine says 8.1.0 .-.
Ainz_Ooal_Gown said:
the link above says it's 8.0 oreo update....which didn't make sense since mine says 8.1.0 .-.
Click to expand...
Click to collapse
Yea its probably a typo. I got this update last month. More interested in the November security patch with the camera update
guytano86 said:
Yea its probably a typo. I got this update last month. More interested in the November security patch with the camera update
Click to expand...
Click to collapse
Same tbh
Is it work lg g6att us997 converted verson??
munna1123 said:
Is it work lg g6att us997 converted verson??
Click to expand...
Click to collapse
An LG G6 from AT&T converted to a LG V20 US version?????
Guys this is for the LG v40, other devices are highly likely to result in a brick
LG V40 Recovery/Bootloader
Has anyone else had the following experience with the LG V40: I obtained mine about a three weeks ago. It does have the latest Android already loaded. It's from AT&T. While i am no expert, I always root and am usually pretty successful at it and rooting does provide functionality that I have now come to almost need. It gave me comfort that there were already "How to" explanations all over the web on recovery, root, obtain the unlock code, flashing using Fastboot in bootloader mode, etc., specific for the V40. It gave me even more comfort that various explanations were more or less consistent. Other than the fact that the Developers are not yet releasing the .bin to unlock the Bootloader (which, in time, they probably will do), it seemed like the road to rooting would go fairly smoothly.
However, when I decided to perform some very simple tasks which would be necessary to install a TWRP or some other recovery in anticipation of eventually rooting, I discovered that with my version of the V40, there is no “recovery” at all. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a "factory reset" of the phone or back into the system. Again, I am no expert, but for someone at my intermediate level, I do know that I do need to be able to get into a usable recovery and, more importantly, bootloader mode in order to flash a custom recovery and, eventually, to root the phone. All of my efforts lead me to conclude that there is no way of getting the phone into anything but a "factory reset". Forget about bootloader or Fastboot mode. The "factory reset" recovery gives you two choices -- reset or reboot back into the system. There is no other avenue. When I used the ADB tools while in this particular "factory reset" recovery mode, and tried to reboot into bootloader mode from there, the phone would simply boot back into the system. So, that route ended in a place where I could never install TWRP or anything else, for that matter – including the inability to apply an unlocking code if one were available. Next, I tried get into recovery mode using the ADB tools, not the physical buttons. I was able to achieve something that looked more like a “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this particular problem with other phones before and sometimes, using the physical buttons at that stage, I was able to reveal commands. However, with the V40, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, I tried to use the ADB tools to boot into bootloader mode from that more "conventional" recovery. This merely brought me back to the system again! I played around with this for quite some time before contacting the Developer website. Evidently, they aware of it but cannot understand it. I really like the phone but, without a recovery, it's not marketable. Unless someone here has any ideas, I think I and the phone will be paying a little visit to AT&T soon!
EBRJR said:
Has anyone else had the following experience with the LG V40: I obtained mine about a three weeks ago. It does have the latest Android already loaded. It's from AT&T. While i am no expert, I always root and am usually pretty successful at it and rooting does provide functionality that I have now come to almost need. It gave me comfort that there were already "How to" explanations all over the web on recovery, root, obtain the unlock code, flashing using Fastboot in bootloader mode, etc., specific for the V40. It gave me even more comfort that various explanations were more or less consistent. Other than the fact that the Developers are not yet releasing the .bin to unlock the Bootloader (which, in time, they probably will do), it seemed like the road to rooting would go fairly smoothly.
However, when I decided to perform some very simple tasks which would be necessary to install a TWRP or some other recovery in anticipation of eventually rooting, I discovered that with my version of the V40, there is no “recovery” at all. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a "factory reset" of the phone or back into the system. Again, I am no expert, but for someone at my intermediate level, I do know that I do need to be able to get into a usable recovery and, more importantly, bootloader mode in order to flash a custom recovery and, eventually, to root the phone. All of my efforts lead me to conclude that there is no way of getting the phone into anything but a "factory reset". Forget about bootloader or Fastboot mode. The "factory reset" recovery gives you two choices -- reset or reboot back into the system. There is no other avenue. When I used the ADB tools while in this particular "factory reset" recovery mode, and tried to reboot into bootloader mode from there, the phone would simply boot back into the system. So, that route ended in a place where I could never install TWRP or anything else, for that matter – including the inability to apply an unlocking code if one were available. Next, I tried get into recovery mode using the ADB tools, not the physical buttons. I was able to achieve something that looked more like a “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this particular problem with other phones before and sometimes, using the physical buttons at that stage, I was able to reveal commands. However, with the V40, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, I tried to use the ADB tools to boot into bootloader mode from that more "conventional" recovery. This merely brought me back to the system again! I played around with this for quite some time before contacting the Developer website. Evidently, they aware of it but cannot understand it. I really like the phone but, without a recovery, it's not marketable. Unless someone here has any ideas, I think I and the phone will be paying a little visit to AT&T soon!
Click to expand...
Click to collapse
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
LameMonster82 said:
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
Click to expand...
Click to collapse
The option is there for certain models but no official unlock support yet.
LameMonster82 said:
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
Click to expand...
Click to collapse
Without being able to get into bootloader, how do you add TWRP?
EBRJR said:
Without being able to get into bootloader, how do you add TWRP?
Click to expand...
Click to collapse
You're able to access the bootloader without any trouble.
LameMonster82 said:
You're able to access the bootloader without any trouble.
Click to expand...
Click to collapse
I cannot..i cannot get to a place where Fastboot can be used. Only a recovery with no commands. Please tell me how you did it. Thanks!
EBRJR said:
I cannot..i cannot get to a place where Fastboot can be used. Only a recovery with no commands. Please tell me how you did it. Thanks!
Click to expand...
Click to collapse
There are 2 ways
1.) Adb reboot bootloader
2.) USB plugged in.
While restarting holding down vol- key
(It works for the g7 bitte not sure for the v40)
Notes: This trips KNOX so you will void your warranty, read all the steps carefully before beginning, flashing can be dangerous if you do it wrong. Don't blame me if you brick your device.
Backup all of your data and settings before starting as you will need to reset to factory defaults during this process.
With that being said, the process is relatively straightforward and easy.
PS: my device is the A908B, there is also an A908N if anyone wants to test on that be my guest.
Needed:
ADB
SamFirm
Odin
Magisk Manager
Step 1 - Downloading your firmware.
Go to SamMobile SM-A908B
Find the correct firmware for your device according to country and operator.
Note: You can use generic country firmware instead, this will remove carrier added software and limitations but may remove features and disables OTA updates.
Note the 'product code'.
Now open SamFirm.
Type SM-A908B for model
In the region box type the product code you noted earlier.
Click Check Updates.
When it has found the firmware, make sure decrypt automatically is checked and then click download rom.
The firmware is around 4gb.
Part 2 - Unlocking the Bootloader
Go to settings > about phone > software information. Hit build number a bunch of times until you activate developer options.
Go back to settings > developer options
Enable OEM unlocking
Enable USB debugging
Turn off the phone
Hold volume up and volume down whilst inserting the USB cable
This should take you to the bootloader unlock screen.
Long press Volume up to unlock the bootloader.
Part 3 - Obtaining root
After SamFirm finished downloading the rom it should have extracted it into 5 tar files.
Copy the tar file beginning with AP to your device.
Download Magisk Manager on the device and install.
Press Install on Magisk Manager
Confirm the Install
Select the option 'select and patch file', then locate the APdjkfgrsdkfhgkjrg.tar.md5 on your device and select it.
Magisk will then patch the file and dump the patched version to your phone.
Copy the patched.tar to your PC
Reboot phone into download mode
Open Odin
For BL use the BL.tar.md5 file from stock firmware
For AP use the patched.tar file
For CP use the CP.tar.md5 file from stock firmware
For CSC use the CSC.tar.md5 file from stock firmware (not the CSC_HOME)
Press Start and wait for it to flash
After flashing, the phone will reset.
After initial setup, install magisk manager again.
Remove the USB cable and turn off the phone.
Turn on the phone by holding volume up and power, let go when you see the bootloader warning.
Open Magisk Manager Click Install.
Phone is now rooted.
Note: Powering on the device normally will disable root, you must hold volume up to power on the device to activate root.
Awesome job thanks a lot
Going to put a few hours into compiling twrp tonight but this might take me forever, I'm really busy with work and I got 2 kids too so free time is scarce. So feel free to have a go at it yourself.
After root activation with the volume button start up will the root persist? Can the device be restarted without any hidden key?
Thank you
Yes the root persists, but every time you turn the phone off and back on again you will have to hold up to activate the root. Resetting the phone while root is enabled does not disable it though iirc.
More work done on twrp last night, nearly ready to attempt compiling.
Edit: So I made a device tree and compiled twrp fine. Unfortunately it needs a custom kernel to be able to boot. Working on this now.
Any further progress??
No not really. I need to reach out to the twrp Devs of the S10 and see what modifications they did to theirs, but super busy at the moment. Sorry.
johnoponi said:
Any further progress??
Click to expand...
Click to collapse
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Are you still trying?
Failure on Model SM-A9080 (China Version)
Today I did this on model SM-A9080 but unluckily failed, and the OS could not be loaded, with boot loop on the phone.
Really the specified TWRP should be developed.
triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
Hello,
I tried to root my phone today, and I followed every step exactly, but now I am stuck in a Boot Loop, after the Step of Flashing. Can someone help, or knows why this happened? Thank you.
---------- Post added at 07:48 PM ---------- Previous post was at 07:03 PM ----------
Okay I fixed it myself. The Problem was, I only Flashed the BL File. After that I flashed the other files one by one, did a Factory Reset in Recovery mode and now it worked! I even have root now.
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
xijaw said:
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
Click to expand...
Click to collapse
So why did you buy a Samsung.
Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
I live in Australia and here we don't have a market like Europe and India. We only have couple of brands- Apple and Samsung.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
underdog_656 said:
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
Click to expand...
Click to collapse
Lets stick to the topic and get the damn custom rom built. Aren't there any devs who willing to take A90 as a project ?
can you get the ctsprofile pass in the magisk manager？
Steveee101 said:
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
Click to expand...
Click to collapse
can i ask you whather you can get the cts profile pass or false or not after you root by magisk？
Hello please can someone help me root this phone, i have followed the steps but i just seem to be missing something so can someone take me through this step by step for a dumb person like myself lol?
At first i was struggling with part one of this tutorial but once i updated samfirm i was able to download it without a problem. moving over to the last step which is using odin to do its thing with the tar files and upon finishing where it should reboot it is stuck into a boot loop saying "this phone is not running samsungs offical software", i am not sure what i am missing and i am able to fix the phone without any problems but no root is achieved
Hello. May I ask about the progress on TWRP for this phone?