Database Users

Zenfone 5 LTE (T00P) Erroneous Behaviour

Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.

Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
I don't think there are custom rom available for zenfone 5 LTE model .So that gives no choice but to stay on stock rom.
---------- Post added at 07:12 AM ---------- Previous post was at 07:10 AM ----------
NightRaven49 said:
Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.
Click to expand...
Click to collapse
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....

Redaki said:
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Like I said in the OP, I cannot authenticate ADB as SystemUI crashes upon generating the notification for verification.
Boomshiva said:
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....
Click to expand...
Click to collapse
Again, in the OP, I've mentioned the Updater does not work.
Are there any other solutions?

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Yes, but there is no custom rom for zenfone 5 lte. maybe neither custom recovery or root.

Sorry i didn't read your post carefully. Did you try to unlock bootloader ? I think it will be the same as the Intel model. Try fastboot and then fastboot OEM unlock, or flash some ifwi file like Intel model.
Then if bootloader is unlocked, flash TWRP and u will have ADB.

Samsung Galaxy Sky J3 SM-S320VL TracFone not flashing....

Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.

Hey folks,
I'm having the exact same issue as the OP. Odin does a successful install on the phone but I get the unauthorized reset message and then Wifi does not work when prompted on the next screen.
Is there a tracfone version of the rom or a fix that anyone here knows of? Thanks!

@drasnah
I have yet to get any kind of reply from anyone on this. Either now one knows, and is not stating so, or doesn't care.

I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!

20eyes said:
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
Click to expand...
Click to collapse
First this is not a wi-fi problem it is a re-flashing of the rom problem.
Second, I do not have access, root or otherwise, to any of the system files on the phone.
Third, with the first two in mind this possible solution is of no help.
Fourth, Re-read my original post. I have given complete detailed information as to what I have access to and what I have done.

Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing

This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..

Curtis1973 said:
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Click to expand...
Click to collapse
Not sure if that's correct? It depends on the firmware and odin version being used.
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Nate1k904 said:
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
Click to expand...
Click to collapse
Post more details on the error, screenshots, firmware and odin version used.

Need to know if works. Or if needing to settle for a different route.
The_WABBIT said:
Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Click to expand...
Click to collapse
J3 sm s320vl... tracfone root availability? Just bought phone hopefully got a good one to root? Or maybe someone knows who maybe be able to... please help

No updates? Interested, I have the same phone.

There is no solution for this phone. It will forever be a Trac-phone.
Yes, it nice to imagine what could had been. If there was a fix for the locked bootloader. Its encrypted, and is highly unlikely to be broken by anyone.
Do not flash the boot.image that some people have suggested
Although that method works on some devices such as the AT&T Samsung Galaxy S5. In this case flashing the boot.image from an unlocked device does nothing but places the phone into an even more precarious situation, that makes it unusable even as a Trac phone.
While its true that this very low budget phone could had been decent with a custom Rom ,
You will not be able to get it working.
I have one that belonged to my daughter a couple of years ago and I managed to get it boot into the system again.
Its only function is as a calculator, or preschool game, the cellular reception and Wifi connections are highly unstable and will not stay connected.
Now it serves as my nieces play toy. I would donate to some poor person at the Salvation Army it if it was useable.
By the way, for anyone reading this.
If you have an old phone that is useable. You could dramatically help a Homeless people, by gifting them with a phone especially, if it has some minutes on it.
This gift will help them schedule job interviews, doctors appointments , etc and you will feel good knowing that you helped someone in need.
I have done this before, and will be dropping off a Blu phone, and Kindle Tablet this week.

tsongming said:
There is no solution for this phone. It will forever be a Trac-phone..
Click to expand...
Click to collapse
It is possible to gain root on this device.

ashyx said:
It is possible to gain root on this device.
Click to expand...
Click to collapse
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.

tsongming said:
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
Click to expand...
Click to collapse
See the thread below. Root was gained, albeit temporary. However I believe this is due to kernel panics which may be solved by a few build.prop edits. We had to do the same on the J327T1.
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-galaxy-j3-sm-s320vl-rooted-t3561762
Also if you firmware S320VUDU1APG2 then why not just update it to the firmware that has been reported to work?

I have found one these phones left on a table of a food truck area, screen was cracked - the device was only getting the android guy with triangle on it, I done some research and found the stock rom and flashed it with odin; as some have mentioned in comments above I also experienced wifi issue, so I thought I had installed incorrect rom - downloaded a different one this was a combination file that was the factory repair rom used for testing the device, but wifi worked - it wasn't a fully working telephone it didnt have the app store, well it really didnt have any apps, but I found I could copy over apk files from my PC to the device and then install them, so the phones not completely useless or junk --- it could be used for something. I myself am using that device as a security camera using IP CAM app works great. I was actually using this device for quiet some time as my roku tv remote, because my actual roku remote grown legs and walked off... i havent tried this, but I am sure you could install a launcher apk such as "apex launcher"
well i wasted enough of your time today...

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.

Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."

Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here

*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!

Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

GS5 verizon 4.4.4 to rooted marshmallow

I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.

bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.

Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.

bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.

Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.

I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!

bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.

Ok. I'll read the guides on the head of this list and see if I can find the right information.

FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.

Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.

bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.

Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.

bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.

The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!

Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.

bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5

Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!

Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!

Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?

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