A lot of people have been starting new threads asking how to reset their phone to stock in order to return it to Verizon with all their modifications undetected. It's really simple and easy to do.
This is to remove any ROM you've installed, un-root and re-lock your bootloader. I'll also post a link to reset your flash counter if you've tripped it.
Basically I'm just going to post a few links to guides that are already here.
-First is to backup:
Backup literally everything on your phone and external sd card just to be safe. Just imagine that if you lost your phone what you would've wanted backed up. (I'm not saying you're going to mess up your phone, just that the internal sd card will be wiped clean. Pics, settings, videos, etc... all wiped off the internal card. Backup up your ext is just to have your bases 100% covered, none of this process actually uses your ext card. You can just remove it if you'd like also.
-Second, Check your Flash counter:
More than likely unless you've been flashing custom stuff through Odin you haven't tripped it. In otherwords if you haven't used Odin or just rooted your phone using Odin and then flashed everything else in CWM or TWRP, you haven't tripped it.
To check your flash counter you need to enter download mode - 'Vol down+Home button+Power button'
You will need to be in download mode for the next step anyways, so just doublecheck the counter first.
If you have tripped it, use this app from the play store Triangle Away
-Third is to flash the stock rooted image via Odin:(This image version will re-lock your bootloader and un root you)
Go to section #5 of this Guide and follow the instructions. Use the UN rooted official version and Just to clarify, there is really only ONE option to choose if you plan on returning your phone to Verizon.(Official VRALG1 4.0.4)
(Shortcut to the file if you are familiar and already have Odin, Here)
-Lastly, perform a wipe via recovery just for safety's sake:
Hold 'Volume up+Home button+Power' from your phone being power off. And do this BEFORE you boot up the stock version otherwise you could get stuck in a bootloop and have to do a battery pull.
It's that simple and this will leave your phone in an "out of the box" state therefor safe to return to Verizon without them catching on.
Yes but where do i get the stock un-rooted to flash to my device? I cant find it please provide a link. Thanks in advance! :cyclops:
PhenomCorp said:
Yes but where do i get the stock un-rooted to flash to my device? I cant find it please provide a link. Thanks in advance! :cyclops:
Click to expand...
Click to collapse
section 6 of my guide...op linked ya right too it :silly:
droidstyle said:
section 6 of my guide...op linked ya right too it :silly:
Click to expand...
Click to collapse
I an kinda new but I know my way around a phone and its working but I just don't get which one it is lol sorry if this sounds amateur.
PhenomCorp said:
I an kinda new but I know my way around a phone and its working but I just don't get which one it is lol sorry if this sounds amateur.
Click to expand...
Click to collapse
There's three choices(the fourth is a kernel) either of the first two will be fine to un root your phone. The third one(root66) will return you to stock rooted.
Brian Gove said:
There's three choices(the fourth is a kernel) either of the first two will be fine to un root your phone. The third one(root66) will return you to stock rooted.
Click to expand...
Click to collapse
OK I understand now and also do i lock the bootloader before or after i un-root?
---------- Post added at 04:33 AM ---------- Previous post was at 04:25 AM ----------
PhenomCorp said:
OK I understand now and also do i lock the bootloader before or after i un-root?
Click to expand...
Click to collapse
Which two files from the tut do you recomend I use? VRALF2 & Stock VRALF2 Kernel ?
I got it un rooted and now since you put locking the boot loader last on the list the ez app wont work it says I need root access to lock it is there another way or should i re root and then un root? But how would it be possible if it is re rooted then un rooted because at the end of the process after i odin the stock non root back i will not be able to access the menu to do a factory reset or anything
How do I check if my boot loader is locked?
Please help
PhenomCorp said:
I got it un rooted and now since you put locking the boot loader last on the list the ez app wont work it says I need root access to lock it is there another way or should i re root and then un root? But how would it be possible if it is re rooted then un rooted because at the end of the process after i odin the stock non root back i will not be able to access the menu to do a factory reset or anything
How do I check if my boot loader is locked?
Please help
Click to expand...
Click to collapse
FOLLOW SECTION 6 TO THE T AND YOU WONT HAVE ANY TROUBLES. DO NOT skip parts of it, follow ALL STEPS!!! going back to stock via odin locks bootloader, you wipe data factory reset from stock recovery. pay attention to the details!!
droidstyle said:
going back to stock via odin locks bootloader, you wipe data factory reset from stock recovery. pay attention to the details!!
Click to expand...
Click to collapse
It does? I'll remove the re locking part then.
Brian Gove said:
It does? I'll remove the re locking part then.
Click to expand...
Click to collapse
yes because the stock odin package has the secure aboot.img. the relock function on the ez unlock app is pointless. the only time the bootloader should be locked is when flashing back to stock.
Brian Gove said:
It does? I'll remove the re locking part then.
Click to expand...
Click to collapse
see now thats what confused me. Thanks +1
Delete
Glad I found this. Thanks!
Tap'n
Nice thread Brian Gove, I love seeing posts that simplify multiple threads into one well executed guide. Everything posted after just gve me a headache, now I can't sleep....thanks guys!
What is needed to remove the custom unlock icon on boot, or does VZ not care about that? I'm looking to bring my phone in to get my GPS issue resolved.
I've reverted back to stock, tried the triangle away and nothing has worked.
{
"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"
}
ENDonDESIGN said:
What is needed to remove the custom unlock icon on boot, or does VZ not care about that? I'm looking to bring my phone in to get my GPS issue resolved.
I've reverted back to stock, tried the triangle away and nothing has worked.
Click to expand...
Click to collapse
I just had to do thus tonight. I had to re-root then installed ez-unlock then pressed lock and then reinstalled the stock image through Odin again and everything worked after that
Tap'n
So I re-rooted and went to a nandroid backup that I had then started the process over again. I did not re-lock my phone and odined to Root66 first, did a system wipe/cache wipe. Then I Odined the stock image and I no longer get the unlocked image on boot.
Brian Gove and Droidstyle thanks for the write ups!!!!!
ENDonDESIGN said:
So I re-rooted and went to a nandroid backup that I had then started the process over again. I did not re-lock my phone and odined to Root66 first, did a system wipe/cache wipe. Then I Odined the stock image and I no longer get the unlocked image on boot.
Brian Gove and Droidstyle thanks for the write ups!!!!!
Click to expand...
Click to collapse
Credit goes more to Droidstyle and the people who supply us the files and the know how to begin with. Honestly I just got tired of seeing twenty threads about the same thing so I wrote this up and asked one of the MODs to sticky it lol
If i trip the counter and i can only boot into dowload/odin mode how can i reset counter back to zero? My phone wont boot up it gets stuck at 4gLTE screen and i cant boot into a recovery.
Go to section 6 in the droidstyles guide(the link in my sig or in the OP) and follow it. It should get up and running so you can use triangle away.
Related
I have this phone which has the GB obtained from Samsung web site. I then rooted with J Scott option 2. Since then I dont have messaging. What can I do to get this back? I have an app that I use but not really satisfied with that. Can I go back to Aroyo, or try to download GB again. I tried Kies again, but it doesn;t give me any option to download again. I have read hundreds of pages w/o an answer, followed many links only to have spam loaded to my computer. Thanks for any help.
[email protected] said:
I have this phone which has the GB obtained from Samsung web site. I then rooted with J Scott option 2. Since then I dont have messaging. What can I do to get this back? I have an app that I use but not really satisfied with that. Can I go back to Aroyo, or try to download GB again. I tried Kies again, but it doesn;t give me any option to download again. I have read hundreds of pages w/o an answer, followed many links only to have spam loaded to my computer. Thanks for any help.
Click to expand...
Click to collapse
Get goo app then install cwm or twrp recovery from that. Then download a rom and flash it. First flash an ICS ROM then a JB ROM in that order
Sent from my SAMSUNG-SGH-I317 using Tapatalk
eZdubzitmk4 said:
Get goo app then install cwm or twrp recovery from that. Then download a rom and flash it. First flash an ICS ROM then a JB ROM in that order
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
This is all new to me, but I'll give it a try. I dont see cwm or twrp on Goo? Can you recommend ICS and JB ROM I dont want anything fancy, just a working phone, but then I might want to get fancy. Thanks for your reply.
[email protected] said:
This is all new to me, but I'll give it a try. I dont see cwm or twrp on Goo? Can you recommend ICS and JB ROM I dont want anything fancy, just a working phone, but then I might want to get fancy. Thanks for your reply.
Click to expand...
Click to collapse
Can anyone help with this please? Thanks
[email protected] said:
Can anyone help with this please? Thanks
Click to expand...
Click to collapse
You can go back to Froyo using GTG's Unbrick. Link in my sig. And then you can get Gingerbread here. I recommend option C. If you prefer Heimdall to Odin, there are links to those packages in the ISET thread.
Thank you. I'll let you know what happens.
[email protected] said:
Thank you. I'll let you know what happens.
Click to expand...
Click to collapse
I did the unbrick and messaging appears to be working. SU icon is in the apps but I don't think it is working. I tested with root test from apps store and it said it was rooted. What should I do next? Do I still need to do the second thing suggested above? Thanks again
[email protected] said:
I did the unbrick and messaging appears to be working. SU icon is in the apps but I don't think it is working. I tested with root test from apps store and it said it was rooted. What should I do next? Do I still need to do the second thing suggested above? Thanks again
Click to expand...
Click to collapse
If you're on Froyo and root was successful, then you can stay there. Do the second step if you want to move up to Gingerbread.
jkakkanad said:
If you're on Froyo and root was successful, then you can stay there. Do the second step if you want to move up to Gingerbread.
Click to expand...
Click to collapse
No, I'm still on GB, root is not working to remove the AT&T bloat, and I would like to move up to JB if possible?
[email protected] said:
No, I'm still on GB, root is not working to remove the AT&T bloat, and I would like to move up to JB if possible?
Click to expand...
Click to collapse
Follow the instructions in this thread to move up to ICS or JB. Some of the ICS roms and all JB roms (I think) use the MTD file system so make sure you backup your EFS before making the move upward. There are instructions in the linked thread for making an EFS backup. Make sure to read carefully before you attempt anything.
Of course, the first step is to see if you have a custom recovery. It will be your launch pad to sweeter future.
jkakkanad said:
Follow the instructions in this thread to move up to ICS or JB. Some of the ICS roms and all JB roms (I think) use the MTD file system so make sure you backup your EFS before making the move upward. There are instructions in the linked thread for making an EFS backup. Make sure to read carefully before you attempt anything.
Of course, the first step is to see if you have a custom recovery. It will be your launch pad to sweeter future.
Click to expand...
Click to collapse
How do I find if I have custom recovery?
[email protected] said:
How do I find if I have custom recovery?
Click to expand...
Click to collapse
Power down the phone. Then hold Vol+, Vol-, and the Power button when you turn it back on. Once white SAMSUNG comes up, release the power button. This will take you into recovery. At the top, it will tell you which recovery you have: Android 3e (secure) or red CWM (custom).
{
"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"
}
----edit----
If you still have stock recovery, then following the link in post #5 and use Odin to flash option C. This will give you GB with root, red CWM, and AT&T bloatware removed.
jkakkanad said:
Power down the phone. Then hold Vol+, Vol-, and the Power button when you turn it back on. Once white SAMSUNG comes up, release the power button. This will take you into recovery. At the top, it will tell you which recovery you have: Android 3e (secure) or red CWM (custom).
----edit----
If you still have stock recovery, then following the link in post #5 and use Odin to flash option C. This will give you GB with root, red CWM, and AT&T bloatware removed.
Click to expand...
Click to collapse
Nothing comes up, it goes on to load the AT&T rethink possible. So I dont have stock recovery?
[email protected] said:
Nothing comes up, it goes on to load the AT&T rethink possible. So I dont have stock recovery?
Click to expand...
Click to collapse
My instructions were a little unclear the first time around. Try again with the instructions below.
1) Power down the phone
2) Hold Vol+, Vol-, and Power
3) When the white SAMSUNG logo comes up, let go of the Power button only. Continue to hold down Vol+ and Vol-.
This should get you into recovery.
jkakkanad said:
My instructions were a little unclear the first time around. Try again with the instructions below.
1) Power down the phone
2) Hold Vol+, Vol-, and Power
3) When the white SAMSUNG logo comes up, let go of the Power button only. Continue to hold down Vol+ and Vol-.
This should get you into recovery.
Click to expand...
Click to collapse
No your instructions were clear to me. I did it again, same result. Thank you for your time.
[email protected] said:
No your instructions were clear to me. I did it again, same result. Thank you for your time.
Click to expand...
Click to collapse
No problem. I'm not sure why the phone won't boot into recovery. I can only speculate but I'm sure there's someone who can shed some light on the issue. If this was my phone, I would flash the UCBL3 Unbrick in Odin b/c it'll re-establish the original partitions, give you GB and root at the cost of losing all the info on your phone. Then you can use flash a custom kernel to get red CWM. From there, you can move on to ICS or JB. Let me know how things turn out.
jkakkanad said:
No problem. I'm not sure why the phone won't boot into recovery. I can only speculate but I'm sure there's someone who can shed some light on the issue. If this was my phone, I would flash the UCBL3 Unbrick in Odin b/c it'll re-establish the original partitions, give you GB and root at the cost of losing all the info on your phone. Then you can use flash a custom kernel to get red CWM. From there, you can move on to ICS or JB. Let me know how things turn out.
Click to expand...
Click to collapse
The last thing I did was the UCBL3 unbrick in Odin, so should I do it again or flash the custom kernel to get red CWM? Thanks
[email protected] said:
The last thing I did was the UCBL3 unbrick in Odin, so should I do it again or flash the custom kernel to get red CWM? Thanks
Click to expand...
Click to collapse
Flash a custom kernel
jkakkanad said:
Flash a custom kernel
Click to expand...
Click to collapse
I bet you knew I was going to say this ....... How do I do that? Thanks
I really do think these videos should be sticky'd in the forums
Simple search on Youtube ''How to root the samsung infuse 4g''
This video showing how to upgrade to stock 2.3.6 rooted with a custom recovery
This video showing how to upgrade from 2.3.6 to 4.0.4
This video showing how to upgrade from 4.0.4 to 4.1 and up
There is also this Super Everything thread from a while ago with links to everything needed to root and install recoveries with instructions. I highly recommend reading ALL OF IT before proceeding as it answers almost any question you could have and then some
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
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.
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.
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.