Database Develop

[Q] Verizon G2 acting crazy after FDR

Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960

Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse

lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse

OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse

lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?

I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse

OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse

lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.

So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse

lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.

OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse

and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse

sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!

lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.

OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?

lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app

Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.

Update Failing

I just got a regular S6 through T-Mobile and for some reason, the initial update is failing. It will download (177 mb), reboot to install, get to 25%, fail, and reboot. The phone is working perfectly other than that. Any idea what I can do to fix it? Thanks.

Since you just got it, why not do a factory reset, then see if the update takes.

roger1955 said:
Since you just got it, why not do a factory reset, then see if the update takes.
Click to expand...
Click to collapse
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.

BTow1105 said:
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.
Click to expand...
Click to collapse
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.

When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?

Alarand said:
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.
Click to expand...
Click to collapse
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mikeyinid said:
When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?
Click to expand...
Click to collapse
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.

BTow1105 said:
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.
Click to expand...
Click to collapse
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?

mikeyinid said:
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?
Click to expand...
Click to collapse
The drivers are installed, Odin recognizes the device, but it just seemed frozen on the blue screen. Odin did a few things and said "started" or something and it said that for about 20 minutes before I decided that couldn't be right. Rebooted it and it went right back to normal.

Have another computer to try, just to cancel out that computer being the problem?

So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:

BTow1105 said:
So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:
Click to expand...
Click to collapse
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.

mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
5.1 the dream

mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.

altimax98 said:
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.
Click to expand...
Click to collapse
Well , to be honest, they should be doing all warranty work and claims and things right there as well. They have such ****ttty customer service that I'd much rather go somewhere so that I could actually discuss things in person. Kinda like......... APPLE!! That's really the only reason I keep these Crapple devices around, because they will swap out anything 4 me on a dime and it can be done in less than an hour. No 2-3-4 weeks without a phone. It seems like being 2015, Samsung should be able to compete in that sense. Oh well, Sorry, I am just daydreaming over here. :cyclops:

Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!

PS4AndroidHacker said:
Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62486197

[Q] First Time Rooter, Gs6 SM-G920T, need help intresting problem cant find fix.

#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!

#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.

How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated

Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!

Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?

Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues

thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?

CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.

Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6

CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002

Any way to root Verizon Samsung SM-T377V tablet?

I'm trying to know if there is any way to root this device cuz I've been looking around and I haven't found a good tutorial on how to root this device in particular and I tried it earlier but it didn't seem to work at all. Any help would be much appreciated.

Is anyone going to help me with this? I have a Samsung SM-T377V tablet and I'm trying to find out how to root it. Thanks!

I had luck a few months ago using Kingroot v4.8.5 after downgrading the stock rom to android 5.1.1 (verizon's official build which the tablet originally shipped with at launch, Build LMY47X.T377VVRU1AOL7).
More recent versions of Kingroot simply fail and do not work. Also, the newer builds of the stock rom appear to be patched and I was unable to root via any method so the downgrade is required. (use Odin to flash verizon's original build)
While Kingroot does shoehorn a working way to root a running system, root doesn't appear to stick forever and eventually did stop working for me. I did have enough root time to at least break google apps and disable other bundled apps from running, but I wasn't unable to fully uninstall all the google spyware and verizon cruft - very frustrating!
Kingroot seems to take advantage of a zero-day vulnerability to grant us a rootkit.
I didn't have much luck replacing Kingroot with Chainfire's SU binaries to keep root working with something known-clean and backed by the community, which is a shame since Kingroot does appear to be running in the background doing who-knows-what with said rootkit. If you need root, Kingroot will get us at least that, but it's a two-way backdoor we're opening up and is really not a longterm solution.
Unfortunately, verizon has the bootloader locked down pretty hard. There's no way to flash in a custom Recovery which would open the door for developing a custom rom for SM-T377V with root already built in and none of the google/verizon undesirables. The current bootloader simply rejects any of the custom recoveries I've tried to flash in since they don't pass Verizon's signature checks.
What we really need is help from someone with experience cracking Verizon's bootloaders.. This bit is above my head and I'm at a roadblock.

electronhacker said:
I had luck a few months ago using Kingroot v4.8.5 after downgrading the stock rom to android 5.1.1 (verizon's official build which the tablet originally shipped with at launch, Build LMY47X.T377VVRU1AOL7).
More recent versions of Kingroot simply fail and do not work. Also, the newer builds of the stock rom appear to be patched and I was unable to root via any method so the downgrade is required. (use Odin to flash verizon's original build)
While Kingroot does shoehorn a working way to root a running system, root doesn't appear to stick forever and eventually did stop working for me. I did have enough root time to at least break google apps and disable other bundled apps from running, but I wasn't unable to fully uninstall all the google spyware and verizon cruft - very frustrating!
Kingroot seems to take advantage of a zero-day vulnerability to grant us a rootkit.
I didn't have much luck replacing Kingroot with Chainfire's SU binaries to keep root working with something known-clean and backed by the community, which is a shame since Kingroot does appear to be running in the background doing who-knows-what with said rootkit. If you need root, Kingroot will get us at least that, but it's a two-way backdoor we're opening up and is really not a longterm solution.
Unfortunately, verizon has the bootloader locked down pretty hard. There's no way to flash in a custom Recovery which would open the door for developing a custom rom for SM-T377V with root already built in and none of the google/verizon undesirables. The current bootloader simply rejects any of the custom recoveries I've tried to flash in since they don't pass Verizon's signature checks.
What we really need is help from someone with experience cracking Verizon's bootloaders.. This bit is above my head and I'm at a roadblock.
Click to expand...
Click to collapse
So you're saying that the only way to root the device is to downgrade to an earlier version of Android, and because Verizon locks down the bootloader to the point where it rejects any recoveries to flash an older ROM, it's impossible to downgrade?

Not quite:
We can flash official Verizon roms without issue since these are signed by Verizon and the bootloader will accept them and allow the flash.
Downgrade to the oldest official Verizon rom using Odin, and root with Kingroot v4.8.5.
It's not a permanent solution since root doesn't stick for much longer than about a week, and Kingroot is of questionable safety in terms of privacy and your data. This is the furthest I could get to developing a custom rom for SM-T377V with root already built-in which "just works".
The Verizon bootloader is certainly aware that Kingroot has done something nasty to the stock rom - during bootup it now shows an Unlocked Lock symbol and says "CUSTOM" before loading the Verizon bootup animation (the animation is part of the rom). This behavior gets reset when an official Verizon rom is reflashed. I'm assuming a new official bootloader (signed by verizon) is being updated as part of their package as well.
We need the expertise of someone with experience cracking a Verizon bootloader so that we can flash a custom recovery which will allow flashing custom roms and making full backups.
I did attempt to flash TWRP in via Fastboot using root on a running system to circumvent the boot process and signature checking, but I was unsuccessful getting Fastboot working. I'm not sure that Verizon allows Fastboots for this reason.

electronhacker said:
Not quite:
We can flash official Verizon roms without issue since these are signed by Verizon and the bootloader will accept them and allow the flash.
Downgrade to the oldest official Verizon rom using Odin, and root with Kingroot v4.8.5.
It's not a permanent solution since root doesn't stick for much longer than about a week, and Kingroot is of questionable safety in terms of privacy and your data. This is the furthest I could get to developing a custom rom for SM-T377V with root already built-in which "just works".
The Verizon bootloader is certainly aware that Kingroot has done something nasty to the stock rom - during bootup it now shows an Unlocked Lock symbol and says "CUSTOM" before loading the Verizon bootup animation (the animation is part of the rom). This behavior gets reset when an official Verizon rom is reflashed. I'm assuming a new official bootloader (signed by verizon) is being updated as part of their package as well.
We need the expertise of someone with experience cracking a Verizon bootloader so that we can flash a custom recovery which will allow flashing custom roms and making full backups.
I did attempt to flash TWRP in via Fastboot using root on a running system to circumvent the boot process and signature checking, but I was unsuccessful getting Fastboot working. I'm not sure that Verizon allows Fastboots for this reason.
Click to expand...
Click to collapse
So there's no way to disable Verizon's detection system that would make it reset the to the stock ROM after installing the previous version? I don't think I'd be with it to have my tablet rooted for only a week.

Root is working for the SM-T377V!
!! Great news! Your curiosity got me thinking about this again, and I got root working fully!
We finally have a working Root for the Samsung SM-T377V Galaxy Tab E 8.0" (Verizon)!
The trick is to use KingoRoot. (not Kingroot)
http://www.kingoapp.com/
First, downgrade the stock ROM to the very first version that Verizon shipped with. Build RU1AOL7, dated 2016.02.11. It's about 1.5gig, and I have no way to host such a large file, so search for it before you ask for mine. I found it pretty easily directly from Verzion. Use ODIN to flash it, yadda yadda yadda.
Then, use the Windows version of KingoRoot to actually root the tab. You will need to enable Developer Mode and USB Debugging, which KingoRoot walks you through if you don't know how. Be sure to uncheck the "Install recommended software" checkbox to avoid the bloatware they try to sneak by you.
After it finishes successfully, reboot the tab. During the boot, a message will pop up that says Android is Optimizing 1 new app. Badda boom, you're rooted!
To verify, use a Terminal Emulator and type the command "su" and press enter. If you're rooted, the prompt will change from a $ to a #. I also recommend that you use a root check app to double-check what is actually installed. I used "Root Check" by gsmdev since it's completely free and no frills unlike the other hundreds up on the market.
https://play.google.com/store/apps/details?id=com.gsmdev.rootcheck&hl=en
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm successfully uninstalling all of the Google spyware and Verizon cruft now without any hangups for the first time since getting this tablet It's not on the level of a custom ROM by any means, but this gets us a lot closer to that day!

Please help!
Please post a link to the older version of the SM-T377V Build. I looked endlessly and could not find it.
I have odin and tried to downgrade to T337VVRS3BPL1 (5.1.1) from T377VVRS1BPL1 (6.0.1). It didn't work. Odin got stuck at "checking status".
Said screw it and tried to run kingoroot, on current build (6.0.1) and failed. :crying:
I can not find LMY47X.T377VVRU1AOL7 anywhere. I searched the verizon and samsung but could not find it.

try SAMMOBILE website for stock firmware
BrentM94 said:
Please post a link to the older version of the SM-T377V Build. I looked endlessly and could not find it.
I have odin and tried to downgrade to T337VVRS3BPL1 (5.1.1) from T377VVRS1BPL1 (6.0.1). It didn't work. Odin got stuck at "checking status".
Said screw it and tried to run kingoroot, on current build (6.0.1) and failed. :crying:
I can not find LMY47X.T377VVRU1AOL7 anywhere. I searched the verizon and samsung but could not find it.
I must find a way to change the IMEI number. I can't do that without root access. Please this is the only thread that sounded promising on the WHOLE internet about the SM-T377V Tablet. :good:
Click to expand...
Click to collapse
IDK about the 'LMY47X' prefix but the ROM/firmware T377VVRU1AOL7 (5.1.1) dated 02-10-16 is posted for SM-T377V on the SAMMOBILE site.

I found it, thanks!
I looked again and I was searching in the wrong areas. I couldn't find it on the Verizon website.
I downloaded it off of samsung-firmware.org

Temporary Root Successful
I was able to downgrade my MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow to LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin with no problems.
Then I downloaded Kingoroot for Windows, and it took me three or four times to get it Rooted. The Root is only temporary though and I lose it after restarting the tablet.

BrentM94 said:
Please post a link to the older version of the SM-T377V Build. I looked endlessly and could not find it.
I have odin and tried to downgrade to T337VVRS3BPL1 (5.1.1) from T377VVRS1BPL1 (6.0.1). It didn't work. Odin got stuck at "checking status".
Said screw it and tried to run kingoroot, on current build (6.0.1) and failed. :crying:
I can not find LMY47X.T377VVRU1AOL7 anywhere. I searched the verizon and samsung but could not find it.
I must find a way to change the IMEI number. I can't do that without root access. Please this is the only thread that sounded promising on the WHOLE internet about the SM-T377V Tablet. :good:
Click to expand...
Click to collapse
You're right, I searched quickly and it looks like VZW took it down... no surprise there :laugh:
Here's a MEGA link to my copy (1.39 GB, zipped):
https://mega.nz/#!bB0wyahB!wf4RW4sGoGv5pp9Co9S1mRVJE1e32v7-9hZt8BGlYKw
I'm curious about your intents to change up your IMEI, I've never had much luck and would love to move mine over to sprint.

electronhacker said:
You're right, I searched quickly and it looks like VZW took it down... no surprise there :laugh:
Here's a MEGA link to my copy (1.39 GB, zipped):
https://mega.nz/#!bB0wyahB!wf4RW4sGoGv5pp9Co9S1mRVJE1e32v7-9hZt8BGlYKw
I'm curious about your intents to change up your IMEI, I've never had much luck and would love to move mine over to sprint.
Click to expand...
Click to collapse
I have made a post hoping that someone could help me. I've been having a really hard time trying to make this tablet stay rooted. I'm not sure if you've seen it. Here is the title of the thread "Rooting Samsung Galaxy Tablet E (8.0) SM-T377V Please Help".
https://forum.xda-developers.com/galaxy-tab/general/rooting-samsung-galaxy-tablet-e-8-0-sm-t3553154
Is that your rooted firmware or just the stock? I would really love if you could post your already rooted firmware that you are using because I keep getting stuck in bootloops with Kingoroot (I only get stuck in bootloops with the android version Kingoroot.apk, and Windows Kingoroot gives me a temporary Root and can't seem to figure out how to keep it rooted.
I wanted to ask you if it was possible for you to post your already rooted firmware of stock (5.1.1) since it is still Verizon I don't see how the Bootloader would lock me out. Would that work?
I'm trying to do the same thing you are trying to do and switch over to Sprint. :laugh:
I also cleaned up my posts on this thread so they're not all over the place.

Sadly things don't look too promising for this tablet, considering the bootloader's preventing us from installing custom recovery. Though, in theory, would it be possible to install a custom recovery by temporarily rooting, then using that to write a recovery.img directly to the recovery partition on the tablet? That'd get around the verification for installing custom recovery if that works...

Ugh. I'm seeing bootloops now too, even immediately after a reflash to stock and then running Kingoroot.
The stock recovery shows "dm-verity verification failed..." at the base of the window.
For those that installed Kingoroot, you can undo the boot loops by rebooting into stock recovery
Reboot, PWR + VOL UP + HOME, and select "wipe data/factory reset..." to pull out all the kingoroot binaries. (this step is necessary, unfortunately)
Then, PWR + VOL DOWN + HOME to go into boot loader mode, and use Odin to reflash the stock rom. This will at least get your tab back to factory stock.
I'm going to explore a bit more with Kingroot, I hadn't realized until I went to reflash over the bootlooping system that unless a full "wipe data/factory reset" is run prior to Odin, that most of the existing system remained intact. In my last writeup I did have a functional tab that could be rebooted without problems. I'm wondering now if it was a combination of the root tactics that I had tried earlier that were all still installed in the system that got things working....
When thing worked prior, I had been playing with: Kingroot 4.8.5, Official SuperSU, BusyBox-free, and of course Kingoroot
---------- Post added at 07:00 PM ---------- Previous post was at 06:54 PM ----------
tomiga said:
Sadly things don't look too promising for this tablet, considering the bootloader's preventing us from installing custom recovery. Though, in theory, would it be possible to install a custom recovery by temporarily rooting, then using that to write a recovery.img directly to the recovery partition on the tablet? That'd get around the verification for installing custom recovery if that works...
Click to expand...
Click to collapse
These were my thoughts too. If we can get root, we can flash over recovery.img using ADB and/or Fastboot. The latter appears to be disabled/locked, however. Also, I'm not certain that the sm-t377p recovery image will actually work... They're reportedly the same hardware, but one cannot be sure that things will jive with a crossflash at such a low level. My thoughts were if it's even an option, gamble it, and if the tab is bricked oh well...
This tab is worthless to me anyway if I can't pull out the Google spyware. Should have bought a rootable Tab A anyway, it would have been cheaper

I've gambled it quite a bit, over the process I've gotten stuck in like 7 bootloops, 5 soft bricks, and 3 hard bricks. Which is about 15 Odin flashes, or factory resets.
I had it temporarily rooted with your suggested firmware downgrade and Kingoroot windows version. The android version only gives me bootloops.
I've never been able to install SuperSu. It gets stuck at disable Knox. Which just ultimately fails and I don't get anywhere. I've used my temporary root and pirated Titanium Backup Pro to Freeze and Uninstall Knox. Which for some reason SuperSu still wants me to disable it and detects it, prevents it from installing.
I really wanted to try the rooting method with this tablet that was used on the SM-T377P because like you said about hardware. I'm not going to risk it, mainly because I need a break from running in circles with this damned SM-T377V.
So I recently flashed with Odin to get out of my last bootloop and my tablet came back on it still had the Kingoroot applications and Root Checker which I had downloaded before the bootloop. I was going to ask if these stayed on there because I didn't wipe to factory defaults before flashing?
Good luck and thanks again for all the help you've provided so far. We do have a temporary root with Kingoroot. I believe a lot of progress had been made. I'll update my thread and clean it up, just giving my experience with the rooting process of the SM-T377V. I'll clean it up when I can get around to it.
Thank you electronhacker.

Can I Re-Flash the current firmware (6.0.1) Marshmallow with Odin? I'm still newbie to Flashing firmware.

I'm an S7 Edge owner and one of these Tab E 8.0 SM-T337V and have some possible ideas for you guys to try. I've rooted my S7 Edge on Nougat Android 7.0. You can go into the Verizon S7 Edge forums to find a lot of this. Download the Odin Prince Comsy Edition. You are NOT able to flash a custom recovery to the tablet as Verizon and Samsung keep the bootloader locked down,even with root,there's no possibilities of a custom recovery. That means no custom recovery at all. Follow the steps on these websites and see what you get. There may be some possibilities here.
---------- Post added at 08:23 PM ---------- Previous post was at 08:00 PM ----------
Check out these sites: forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
forum.xda-developers.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039
This may be a good way to try and root the tablets
Sent from my SM-G935V using XDA-Developers Legacy app
---------- Post added at 08:41 PM ---------- Previous post was at 08:23 PM ----------
BrentM94 said:
Can I Re-Flash the current firmware (6.0.1) Marshmallow with Odin? I'm still newbie to Flashing firmware.
Click to expand...
Click to collapse
You should be able to to flash the stock firmware with Odin. I use Prince Comsy Odin as it skips SHA checks. Even with a newer bootloader version,you should be able to flash an older firmware. Just use the AP slot in Odin to do it and nothing else.
Sent from my SM-G935V using XDA-Developers Legacy app

So you're saying that I can temporary flash a previous version of Android on the device but by the time Verizon checks the software the root will be voided almost immediately upon its exploit?

DMon04 said:
I'm an S7 Edge owner and one of these Tab E 8.0 SM-T337V and have some possible ideas for you guys to try. I've rooted my S7 Edge on Nougat Android 7.0. You can go into the Verizon S7 Edge forums to find a lot of this. Download the Odin Prince Comsy Edition. You are NOT able to flash a custom recovery to the tablet as Verizon and Samsung keep the bootloader locked down,even with root,there's no possibilities of a custom recovery. That means no custom recovery at all. Follow the steps on these websites and see what you get. There may be some possibilities here.
---------- Post added at 08:23 PM ---------- Previous post was at 08:00 PM ----------
Check out these sites: forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
forum.xda-developers.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039
This may be a good way to try and root the tablets
Sent from my SM-G935V using XDA-Developers Legacy app
---------- Post added at 08:41 PM ---------- Previous post was at 08:23 PM ----------
You should be able to to flash the stock firmware with Odin. I use Prince Comsy Odin as it skips SHA checks. Even with a newer bootloader version,you should be able to flash an older firmware. Just use the AP slot in Odin to do it and nothing else.
Sent from my SM-G935V using XDA-Developers Legacy app
Click to expand...
Click to collapse
The problem I see with that is that those guides use an engineering bootloader specific for the S7. As far as I know, there isn't an engineering bootloader for the T377V. Sadly, still haven't found any reliable results in getting this thing rooted.

Question Trying to get rid of a pre-configured knox profile from a Tab A8 given out as financial aids for families.

It comes with a pre-configured Knox profile and I was wondering if I can get rid of it through rooting. It basically has a customized start and shut down screen, and persistent notification telling you how generous the government is and such. I could factory reset it but sadly it doesn't do anything. Note that this should be a South East Asian/Asia model, if that matters.
Let's just hope its not a Walmart Xcover situation. Would be nice if someone could help me out, thanks. I don't mind if I can only use the stock A8 roms from Samsung, I just want the government spying out of my device.

You could try to manually flash stock ROM made for other region

nisfta said:
You could try to manually flash stock ROM made for other region
Click to expand...
Click to collapse
I just hope it doesn't trip knox and brick it though, iirc this is a similar system in a telco payment locked phone right?

After doing some reading I've found some tutorial on flashing a stock Samsung rom through recovery via Odin but I don't know if the pre-configured profile would go away or not though

Alright so i tried to Odin reflash it, didn't work. I think the only way is through bootloader unlock root, but I'm afraid that Knox would get in the way and brick my phone though. Anyone else can confirm? Thanks.

nisfta said:
You could try to manually flash stock ROM made for other region
Click to expand...
Click to collapse
Just tried again with a stock rom outside of knox supported region, didn't work either.
So yeah unlocking the bootloader seems to be the only way now. Again, i'm still worried about Knox interfering with the rooting process and brick the phone

coomlord said:
Just tried again with a stock rom outside of knox supported region, didn't work either.
So yeah unlocking the bootloader seems to be the only way now. Again, i'm still worried about Knox interfering with the rooting process and brick the phone
Click to expand...
Click to collapse
I don't think it would brick the device but I don't think it will work either. Knox doesn't get erased by anything the user can do AFAIK. That's why it's called "Knox Secured". It would be useless if you could get rid of it simply by unlocking the bootloader.