Database Develop

[Q] Verizon SGT... where do I start?

Which root method is easiest/best?
what rom? Is there really no CM or MIUI support for this thing?
Thanks for any advice in advance!

My suggestion is you should stay with the stock rom first for at least 2 month before you make decision to root it. Play with it to the fullest, by doing so, then you will notice what its weeknest and find the best way to solve it by 3rd party app. If stil not satistfy, then go with the root thingy. But maybe i should warn you, that more reading is required, equip your self with good knowledge of rooting thing so that you will not screw up your tab. I'm my self already 17 days own this tab and still learning from xda community. I read a lot and found most people are facing big trouble after root. That had down my moral and make me think twice about rooting thing. But if you had confidence, than why not just go for it!!!
Sent from my GT-P1000 using XDA App

Oh I am not new to rooting, I have owned a few Android devices. There is no question I want root, the question is how to go about it.
This devices support is so clustered it is near impossible to get through with anything remotely close to ease. Anyhow for those who follow in my footsteps and find this thread, here is how I have progressed.
First, how to undo and return to stock.
http://forum.xda-developers.com/showthread.php?t=967175&highlight=return+to+stock
Power On + Volume Up is recovery
PoewrOn + Volume Down is downloader mode
Please note: the driver called for by Zadig should be SAMSUNG composite device, and it would not even show up unless the SGT was connected and in download mode already; Also you will have to check for and install the update after using this.
Next to skip Activation press Volume keys in this order
Up Down Up down left right left right B A Start... erm, no, thats not it...
Try
Up down down up up up down down down down
OK now on to root. Search for kies, here or on Google, you will find it. I am not even sure why this is necessary but when I skip this, **** don't work. Install it, check that you are not in USB debug mode (found under applications settings, developer) and connect your SGT. Wait for the error that you need to be in PC Studio mode, which we dont have, then disconnect.
Now you need to have Super One click Downloaded, (search the forums) and run it. Set your device to USB debugging ON then connect it. MAKE SURE YOU DO NOT SKIP THIS... I swear to god every device I get, at least once I will forget about debugging and spend hours reinstalling drivers because the device is not recognized!
Press Root
After it is rooted donate, and reboot the tab (MAKE SURE to reboot, trust me SU can do odd things before you do).
Download Verizon Boot Strapper. Yes it is 2.99, take your cheap ass to the bank, deposit 3 bucks, and support the dev.
CLick Bootstrap Recovery and you will gett a SU request, if you dont, you did not reboot like I said earlier, do so now, and hope you dont get a bad install
After it is done click reboot into recovery like it tells you. Once it is done, do not reboot yet, whipe the cache, then go into advanced and wipe Dalvic. I am not sure if anyone else does this, but the only time I did not, I got stuck at the samsung screen and had to repeat this whole process.
Reboot, and enjoy your Galaxy tab.

Bricked HTC One M7, I need serious help!

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.

Root for people on G920TUVU5EQC2

Okay, so thanks to this thread here: https://forum.xda-developers.com/tmo...t3382856/page6 and the person who did it (to my knowledge) @AZWildcat
Copy & pasted @ktrinh4213
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Sorry if I did tagging wrong I usually lurk

Flash TWRP and then the SuperSU ZIP.

Also auto root still work. At least it did on mine phone

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
The baseband isn't listed on Autoroot which is why I've not used it.

Obievil said:
The baseband isn't listed on Autoroot which is why I've not used it.
Click to expand...
Click to collapse
That is the same reason I havent either ;-;

EncryptedCurse said:
Flash TWRP and then the SuperSU ZIP.
Click to expand...
Click to collapse
sorry it has been a long time since i rooted my phone i know how to install twrp and supersu but how does just installing supersu root my phone i thought you had to have a rooted phone to install supersu

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
what was your base?

timspotatochips said:
sorry it has been a long time since i rooted my phone i know how to install twrp and supersu but how does just installing supersu root my phone i thought you had to have a rooted phone to install supersu
Click to expand...
Click to collapse
Super SU does require root. I was confused by his answer as well. I wondered if I could use the latest Base for my phone from Autoroot but I'm not willing to risk it without knowing for sure.

Obievil said:
Super SU does require root. I was confused by his answer as well. I wondered if I could use the latest Base for my phone from Autoroot but I'm not willing to risk it without knowing for sure.
Click to expand...
Click to collapse
Yeah haha well i dont mind testing it in a few weeks and I can let you know unbricking usually isnt hard just flashing stock usually will fix it I was also curious if I could downgrade by flashing stock roms cause i dont care about knox

timspotatochips said:
what was your base?
Click to expand...
Click to collapse
EQC1, I think... the one before this one... there's actually a tread on how to root s6 with mm

britchel said:
EQC1, I think... the one before this one... there's actually a tread on how to root s6 with mm
Click to expand...
Click to collapse
oh okay do you have the link please and thank you ))?

timspotatochips said:
Yeah haha well i dont mind testing it in a few weeks and I can let you know unbricking usually isnt hard just flashing stock usually will fix it I was also curious if I could downgrade by flashing stock roms cause i dont care about knox
Click to expand...
Click to collapse
My phone is out of contract so I don't care about knox anymore, It's been so long I am still a little afraid of bricking it. the last phone I rooted was the Galaxy S3, believe it or not lol!

Obievil said:
My phone is out of contract so I don't care about knox anymore, It's been so long I am still a little afraid of bricking it. the last phone I rooted was the Galaxy S3, believe it or not lol!
Click to expand...
Click to collapse
oh dang last phone I rooted was my nexus 6 and knox is useless im sure you can still encrypt your phone without it and well samsung pay is ass and you can get a new kernal for fingerprint scanner if it no longer works but ill let you know if I am able to root my phone I assume youre on the same firmware as me?

timspotatochips said:
oh dang last phone I rooted was my nexus 6 and knox is useless im sure you can still encrypt your phone without it and well samsung pay is ass and you can get a new kernal for fingerprint scanner if it no longer works but ill let you know if I am able to root my phone I assume youre on the same firmware as me?
Click to expand...
Click to collapse
Yes I am, it's how I landed on this thread.

Obievil said:
Yes I am, it's how I landed on this thread.
Click to expand...
Click to collapse
haha i assumed so just wanted to clarify

Just out of stupidity, and morbid curiosity I tried to Autoroot the last known good rom from that site. And it failed with a FRP lock error message. I'm surprised it didn't brick.

Hey why don't you make your own rom. Pretty easy... you customize it to your like, I made mine and it's pretty stable. And it roots it from pc

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
britchel said:
Hey why don't you make your own rom. Pretty easy... you customize it to your like, I made mine and it's pretty stable. And it roots it from pc
Click to expand...
Click to collapse
I don't think you understand. The rom isn't the issue here, It's getting root access that's the problem.

Okay, so thanks to this thread here: https://forum.xda-developers.com/tm...oot-samsung-galaxy-s6-sm-g920t-t3382856/page6 and the person who did it (to my knowledge) @AZWildcat
Copy & pasted @ktrinh4213
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Sorry if I did tagging wrong I usually lurk

This worked, I just rooted my device! Thank you for linking this!

I Think I Trashed my Tab S2 T713

I am coming with hat in hand fully expecting to find out that there is no solution and I am out the $$$ it will cost me to replace. After having this device for close to 2 years, I decided I would root it. I have 5 other devices currently that are rooted and numerous others that I have rooted over the years (including Samsung). Admittedly, I dislike Odin and a lot of other things about rooting Samsung devices. That is part of the reason this was the only device that I ever kept unrooted for more than a month or two. I installed twrp_3.1.0-1_sm-t713_14417n with Odin with no issues. I had SuperSU 2.82 in internal. When I got into TWRP to install it, I saw nothing but directories in internal and it became clear to me that it was encrypted. Attempts to mount, wipe and even reset data all ended up with me booting back to TWRP. I'm sure frustration set in the more things I tried, but now I can't even shut the device down from TWRP or by long pressing power and volume down. Even that just goes back to TWRP. Obviously, I can't get into download mode or system. I just get the recovery booting set warranty bit: recovery message when it starts back up to TWRP. Can't say I have ever seen a device that can't even be forced to shut down, LOL. Thanks in advance if anyone can help.
*I've made some progress. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power down and volume and spam the home button until I got to the download screen. I was able to get back into Odin, but the full firmware file I tried to install errored out at the end with a rev check fail. Hopefully, it was because it thought it was downgrading, so I am downloading the newest file now. The samsung-firware.org D/L is brutally slow. Has a few more hours to go, and I am not positive if it will work yet. Cross your fingers, and throw out any ideas if you have them.

Well, it's alive. Everything is back to normal (except needing to reinstall). Time to root now, LOL!
OK, tried again and ended up restoring the full image again (minus D/L time at least). I am ready to scrap root on this device. I have tried to do everything in the [TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17 thread. https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 I would have tried installing no verify, but no matter what I do not see the SU and no verify files on the tablet either after format data without reboot or after rebooting into TWRP. After the format, it shows that data is mounted. Looking at the pictures in the thread, I think maybe it needs the work done on the external SD but the instructions say nothing about that. Time to sleep on it, and maybe someone smarter than me can think of what I might be missing and maybe better step by step instructions are available. At least it is up and running, KNOX trips be damned. I'll post to the TWRP/ROOT thread. BTW, the OS version I am running is XAR-T713XXU2BRB2_T713XAR2BRB2-20180206.

Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.

sliding_billy said:
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
Click to expand...
Click to collapse
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk

rholm said:
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The instructions in the TWRP thread are OK, but they could be a little clearer in some places. Take a look at the interaction between ashyx and I towards the end of the TWRP thread.
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627

[Guide] Unlocking Bootloader and gaining root on the A90 5G

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?