Database Info

[Q] Has my phone been flashed?

I bought a Nexus 5 on ebay, advertised as factory reconditioned. However, I have a suspicion that the device has already been flashed as it is on Android version 4.4.4 and won't update to Lollipop. Here's a screenshot of the device info.
Are my suspicions confirmed?
{
"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"
}

itchyfeet said:
I bought a Nexus 5 on ebay, advertised as factory reconditioned. However, I have a suspicion that the device has already been flashed as it is on Android version 4.4.4 and won't update to Lollipop. Here's a screenshot of the device info.
Are my suspicions confirmed?
http://s7.postimg.org/gjbvvsggr/Screenshot_2014_12_18_20_33_10.png
Click to expand...
Click to collapse
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.

I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?

Rarscaryfrosty said:
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.
Click to expand...
Click to collapse
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
itchyfeet said:
I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?
Click to expand...
Click to collapse
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.

wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.
Click to expand...
Click to collapse
Sorry, what I mean is I think the phone has been rooted, which I really don't want. I presume the OTA updates has gone out to official Nexus 5's already, and the reason mine won't recognise an update is because it's been rooted.

itchyfeet said:
Sorry, what I mean is I think the phone has been rooted, which I really don't want. I presume the OTA updates has gone out to official Nexus 5's already, and the reason mine won't recognise an update is because it's been rooted.
Click to expand...
Click to collapse
Not every nexus 5 has gotten the update yet. Be a little patient. Or do it yourself.

Rarscaryfrosty said:
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.
Click to expand...
Click to collapse
wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
Click to expand...
Click to collapse
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked

keylocker said:
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked
Click to expand...
Click to collapse
Cool. Shows how much I know. I just want people to chill out. ............

To find out if your bootloader is unlocked, boot into fastboot mode..from power off hold volume down and power button. It will say on the bottom if it is unlocked. There are apps that will check for root. Google them. There may be a chance that it was once rooted and/or unlocked but flashed back to stock and relocked. In this case the OTA should work just fine. As stated, you should receive notification of update regardless. If rooted or unlocked the OTA will fail when you try to install it.

If you are concerned about the state of the device I would learn how to flash factory images gotten straight from Google. This will completely wipe the device (your data and the ROM) and reinstall it from scratch. There are plenty of tutorials on how to do this and it will give you peace of mind that your device is, from a software perspective, in new condition.

Sekn said:
If you are concerned about the state of the device I would learn how to flash factory images gotten straight from Google. This will completely wipe the device (your data and the ROM) and reinstall it from scratch. There are plenty of tutorials on how to do this and it will give you peace of mind that your device is, from a software perspective, in new condition.
Click to expand...
Click to collapse
This was my exact thought as well. I figure if he had just purchased it, then why not just flash the 5.0.1 factory image and completely wipe the device and start fresh? It's the cleanest way to get the latest everything without having to mess with saving data etc.

keylocker said:
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked
Click to expand...
Click to collapse
Yes you will being rooted has nothing to do with it. As long as you are running your stock Rom and recovery you will get them no problem.
Sent from my super duper HTC m8 custom beast machine
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
itchyfeet said:
I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?
Click to expand...
Click to collapse
Did it say that the phone was rooted and bootloader unlocked when you bought it? Use this to see.
market://details?id=com.jrummyapps.rootchecker
http://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
Either way if it's unlocked and rooted bonus but that will have nothing to do with ota updates. Unless you have a custom recovery installed. Try to boot into recovery and you'll know if it's stock is not
Sent from my super duper HTC m8 custom beast machine

wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.
Click to expand...
Click to collapse
Stop lying

str8str said:
Yes you will being rooted has nothing to do with it. As long as you are running your stock Rom and recovery you will get them no problem.
Sent from my super duper HTC m8 custom beast machine
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
Did it say that the phone was rooted and bootloader unlocked when you bought it? Use this to see.
market://details?id=com.jrummyapps.rootchecker
http://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
Either way if it's unlocked and rooted bonus but that will have nothing to do with ota updates. Unless you have a custom recovery installed. Try to boot into recovery and you'll know if it's stock is not
Sent from my super duper HTC m8 custom beast machine
Click to expand...
Click to collapse
OTA`s will be downloaded but NOT installed if you have root privileges, you can flash factory images manualy though.

Go to the play store get root checker if you don't see a super.su app then most likely not
Turn off the phone hold vol down and power until you boot into fast boot use the volume keys as up and down scroll to recovery press the power button as enter if it pulls up twrp or clockwork mod then it has been rooted at one time if it pulls up a little android with its chest open saying waiting on command no custom recovery just hold down the power button for 10 seconds to reboot as normal

Update arrived!

I am downloading an update that is 568.3 mb. GO GRAB IT!
{
"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"
}

Me too!
Manually went to update...

Update finally
AT LAST
Got it!!

5.1.1?

Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671

wildjeep said:
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
Click to expand...
Click to collapse
You are 100% correct my friend... I hate when people hurry up and jump on the update, then complain non stop they lost root and can't get it back....
Sent from my SM-G925V using Xparent Green Tapatalk 2

Soooperstar said:
5.1.1?
Click to expand...
Click to collapse
+1

If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1

If anyone has taken the update, please report back on whether TWRP and/or Cf autoroot works

Sent from my SM-G925P using Tapatalk

dhonzik said:
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
Click to expand...
Click to collapse
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:

I will say, however, the device seems to run much smoother and early signs show battery improvement as well. Obviously it's early but it seems promising. Just wanted to share my stock experience as I chose to not root for the future payment platform

I updated but I am not root
no ram management .

If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?

Alpine- said:
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Click to expand...
Click to collapse
Take a look at this thread: http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
It is not a looked boot loader that is the problem. T-Mobile solved it so I am sure it will be solved for us very soon.

wildjeep said:
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
Click to expand...
Click to collapse
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.

dhonzik said:
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
Click to expand...
Click to collapse
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery

Soooperstar said:
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Click to expand...
Click to collapse
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.

dhonzik said:
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
Click to expand...
Click to collapse
Did you try to Odin our twrp?

Soooperstar said:
Did you try to Odin our twrp?
Click to expand...
Click to collapse
Yes, it was a no go, $75 later I'll have a new phone in a week

New Samsung user, where do I start?

Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313

misfit0313 said:
Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313
Click to expand...
Click to collapse
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.

Soooperstar said:
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.
Click to expand...
Click to collapse
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???

JediMindTrixx said:
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???
Click to expand...
Click to collapse
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports
{
"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"
}
Sent from my SM-G925P using Tapatalk

Soooperstar said:
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports View attachment 3492662
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
That's right forgot about not being able to go back. Thanks! :good:

Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Yea I had the OG EVO back in the day. I know all about it. Samsung is much simpler when it comes to rooting

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Odin is like RUU and Knox is Sammy's security...
Sent from my SM-G925P using XDA Free mobile app

This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001

misfit0313 said:
This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001
Click to expand...
Click to collapse
Correct.... Be sure to get the 925p

Thank you again. I'm rooted and have TWRP installed. A message popped up afterwards ”unauthorized actions have been detected galaxy s6". It was taken care of by freezing "SecurityLogAgent" with TiBu.

6.0.1 OTA for stock rooted system

Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.

Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.

Safest way.. ruu back to stock everything take ota and re root/download apps etc...

Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"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"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse

What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe

Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse

Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse

Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse

Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse

Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse

First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse

And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...

I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond

txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....

mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.

Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.

Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.

SM-G930T Root Doesn't Void Warranty

The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"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"
}

method
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?

dantehalo said:
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
Click to expand...
Click to collapse
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
And for now here is great video tutorial (also created by Max Lee) The Video

So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.

revulv said:
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
Click to expand...
Click to collapse
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.

Month later
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
KillerClaw321 said:
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Click to expand...
Click to collapse

djdubyah said:
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
Click to expand...
Click to collapse
It is the only root method so far. It is not required but you can unencrypt before rooting. Rooting while already encrypted won't cause any harm since /data is encrypted not /system . But I still recommend unencrypting so you don't run into any issues.

Does this work for the latest November 1st update APK1?

Hello, I too would like to know if this is still the current root method and if there have been any changes?

GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.

i cant root my sm9307
KillerClaw321 said:
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
Click to expand...
Click to collapse
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me

seattlestexan said:
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
Click to expand...
Click to collapse
Did the attempt trip your Knox counter?

GeorgeNYer said:
Did the attempt trip your Knox counter?
Click to expand...
Click to collapse
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.

seattlestexan said:
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
Click to expand...
Click to collapse
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I would try it myself but I'd hate to start over from scratch, I just wanna know if you tried all that is in the video, if not then I would try
Sent from my SM-G930T using Tapatalk

GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
What I listed is what I was able to do. I'm not certain it ever had root access. When it showed "custom" at boot, I couldn't grant anything root access. When it acted more laggy, like was described, the lag was so bad, it wasn't usable. Mind you, these instructions were written prior to the APK1 firmware that was on my G930T from new.

jveewee said:
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
Click to expand...
Click to collapse
It's smg930t, just search smg930t root max lee

I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.

troby86 said:
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
Click to expand...
Click to collapse
And Knox counter wasn't tripped??

GeorgeNYer said:
And Knox counter wasn't tripped??
Click to expand...
Click to collapse
Nope.