Database Users

[Q] T-Mobile Galaxy S5 Root Lost After Phone auto-updated

Hey Guys, I'm brand new to these forums, and to this whole community so bare with me.
Basically I bought my T-Mobile Samsung Galaxy S5 phone around the time it came out, and I also had installed root on it via towelroot when Towel Root was first released. I did not update the phone at all for a long period of time and everything was working fine, until one day I was browsing under settings and accidentally tapped the "Software Update" button, then T-mobile auto-pushed an update onto my phone.
This update has caused the root on my phone to not work at all (Deemed useless) So I clicked SU and only a black screen popped up when I tried to open the app, so I uninstalled it, reinstalled it then got a message saying "There is no SU binary installed, and SuperSU Cannot install it. If you just upgraded to Android 4.3 you need to manually re-root your device" So I tried to re-root via towelroot method again. It seems the T-mobile update made my phone "Unsupported/Uncompatible" with TowelRoot's obsolete techniques, so now I'm in dire need of help.
My phone tried to push another t-mobile update (This time to upgrade to Lollipop) but it failed after attempting to install it after a reboot. So not only will my phone not update to Lollipop, but I'm not even rooted anymore and am unsure on how to get back rooted, or what to do next since I used rooting as a primary source to store apps on my SD Card. Kind of like i'm stuck in one spot? (Can't update your phone/can't root it the old method)
I'm brand new guys, Please can you break down to me what I should do, in order to obtain root again, and possibly be able to upgrade to Lollipop As well as prevent further pushed T-mobile updates? Here's some info if you need it
S5 Model Number: SM-G900T
Android Version:4.4.2
Kernel Version:3.4.0-262.. etc. (Tell me if you need the full kernel details)
Any help would be greatly appreciated! Thank YOU!

Flash this with ODIN
http://download.chainfire.eu/407/CF-Root1/CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
(Will trip KNOX and void warranty)
Or flash a pre-June 2014 KK Kernel, root with Towelroot again, then flash back your current Kernel

Is this the only solution? And also is it the right one? o.o

Can anyone else please give me some feedback on the situation? I want to make sure I do this right, please just a little helps.

Bump

bump

*Detection* said:
Or flash a pre-June 2014 KK Kernel, root with Towelroot again, then flash back your current Kernel
Click to expand...
Click to collapse
Hey I did exactly what you said and it worked I got root back, but I was wondering how to flash back to my current kernel and keep Root?

[Q] Quick Question If Someone Has a Moment, Please

I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1

Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk

There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.

bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...

N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help

Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.

Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.

mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?

BTV-W09 | NRD90M test-keys | EMUI: 5.0 | Android: 7.0: Bluetooth Not Working?

Is anyone having problems with Bluetooth on their device? Just need to enable it on mine because I used 2FA with my Google account, & have a security token.
Model Number: BTV-W09
Build Number: NRD90M test-keys
EMUI Version: 5.0
Android Version: 7.0
Everything else seems to be working, at least so far. Still only seeing 2.4 GHz frequency with WiFi, but getting 5.0 GHz working is something I can work on later.

My Bluetooth seems to be working fine. I am on EMUI 5 / Android 7.

the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.

tomchism said:
the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.
Click to expand...
Click to collapse
I love how people here use abbreviations so frivilously. TWRP?? I googled that and it seems to be a root method. Rooting the tablet isn't a solution to this and we need bluetooth and 5ghz working for US. I had an EU update installed before this, then I hear the US update is out and I hoped it fixed the bluetooth issue. But now I have a USA version with a disabled bluetooth and no 5ghz wifi radio. This tablet is becoming more of a pain than anything....

When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.

tomchism said:
When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.
Click to expand...
Click to collapse
does the above mentioned operation void my guarantee for the tablet ?

That's a difficult question to answer. The device comes with two recovery systems built in. There are not many scenarios where you can hard brick the device and are unable to restore it back to factory settings, locked unrooted and like new. Any warranty issue are likely to be hardware not software.

Hmm. I am in the process of using the dc-unlocker client to unlock my bootloader. When the client reads my phone, it shows the build number as NRD90M test-keys, but when I look at device info on the phone, it shows a normal build number. Does anybody know what this means?

Help! I just pulled an all nighter

My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.

UPDATE!
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
MajinMight said:
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
Click to expand...
Click to collapse

UPDATE #2
As you can tell I haven't given up yet. I found my current firmware version for download on a different website:
https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/"]https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/
It's another slow download option which really sucks. But I'll be able to test If I can flash the same firmware to the phone (not technically a downgrade and carries the same fused binary). So we shall see. If this doesn't work I'll be looking into the other android 9 or 10 roms and rooting the phone.
Thanks, Derek
MajinMight said:
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
Click to expand...
Click to collapse

TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.

Dang! Well thanks for the info! I guess all the videos I've seen with S7's and custom roms have not been done on the US-Verizon phone. What a bummer. Well this was a major learning experience at least.
My only idea now is to crack her open and make sure the camera didn't come unplugged from a drop. I also seen camera replacements were really cheap online. I don't know if it's worth my time....we are due for a phone upgrade anyway.
SkylineDriver said:
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Click to expand...
Click to collapse

Restore stock and reroot

I have been an XDA member/ reader for over 10 years but this is the first time I think I have ever asked a question.
I have a Tab A 510 WiFi that I rooted back in Dec 2019. Since then I have done no other updates except to my installed apps. I want to basically unroot it and install updates that are desperately needed. I then want to reroot it correctly. Plus install a Android ROM that is a much newer version. When I originally rooted, I am pretty sure I didn't get the process correctly done. I have been running it with TWRP, and MAGISK, installed but I am pretty sure I didn't use the correct kernel or build. The tablet has been slowly loosing app compatibility with newer apps. I really just want to start fresh. I also want to remove system apps that are unneeded.
Is the best way to just reset the device, then let it update to the most current security and Android version then reroot it? I have rooted multiple devices in the past but for some reason on this tab A, I have been intimidated by kernel versions and build numbers so I have just ignored any OS updates and have kept the option in settings to automatically update turned off. And have really done nothing with TWRP. I am pretty sure the version is way out of date on my tablet.
Will resetting, updating to correct build and kernel and then rerooting following the directions posted work still? I just want to make sure that what I end up with is an updated and easier to manage tablet. I know how to unlock bootloader, and how to use Odin. And can follow the instructions for in the forum for rerooting. But, I have not been able to find this question answered anywhere in the Tab A forums.
Any advice would be appreciated.
Thank you
The build numbers I have is *** treble_a64_bvS-userdebug 10 QQ2A.200305.003 200314 test-keys**** my kernel is ****4.4.111# 2 Sun Mar 1 15:16:12 PST 2020 and my security patch level is from November 1, 2019. And serial number is *** R52MA0ZH01R****hope that is enough information to at least show how out of date the system is.