Rooted, but never flashed. Best way to unroot to take the updates? - Verizon Samsung Galaxy S III

Hi there, quick question. Searched like crazy, but I think the keywords were just too generic to get any useful results.
Status:
Verizon Galaxy S3
Running 4.1.2 Touchwiz via Verizon
Rooted with some apps frozen & some greenified
Never flashed anything, there are no triangles.
The unlocked icon & "custom" appears at boot.
Issues: None, except my micro USB port doesn't work anymore, so I'm a battery swapper day to day.
I'm on the last few months on my phone, but decided I'd like to take the kitkat update. The quickest & easiest way to do this seems to be to install Universal Unroot from the play store - https://play.google.com/store/apps/details?id=com.universal.unroot
Run it. Then take the updates once I'm no longer rooted.
Before I did this, wanted to get your feedback on this as a process and if anyone has experience with a similar set up??
Thanks!!

aarontsuru said:
Hi there, quick question. Searched like crazy, but I think the keywords were just too generic to get any useful results.
Status:
Verizon Galaxy S3
Running 4.1.2 Touchwiz via Verizon
Rooted with some apps frozen & some greenified
Never flashed anything, there are no triangles.
The unlocked icon & "custom" appears at boot.
Issues: None, except my micro USB port doesn't work anymore, so I'm a battery swapper day to day.
I'm on the last few months on my phone, but decided I'd like to take the kitkat update. The quickest & easiest way to do this seems to be to install Universal Unroot from the play store - https://play.google.com/store/apps/details?id=com.universal.unroot
Run it. Then take the updates once I'm no longer rooted.
Before I did this, wanted to get your feedback on this as a process and if anyone has experience with a similar set up??
Thanks!!
Click to expand...
Click to collapse
Make sure you revert back to factory as much as you can remembered, like build.props, unfreeze all system apps, unroot with Universal unroot, then take the update. But first make a backup of all your apps/settings with Tibu. Worst come to worst it just failed without any harm done and if it failed and you couldn't figure out what's wrong then the fastest way and most reliable way is to Odin stock ML1, then use the OTA to upgrade to 4.4kk then root with Towelroot app, then restore all your apps with Tibu.

buhohitr said:
Make sure you revert back to factory as much as you can remembered, like build.props, unfreeze all system apps, unroot with Universal unroot, then take the update. But first make a backup of all your apps/settings with Tibu. Worst come to worst it just failed without any harm done and if it failed and you couldn't figure out what's wrong then the fastest way and most reliable way is to Odin stock ML1, then use the OTA to upgrade to 4.4kk then root with Towelroot app, then restore all your apps with Tibu.
Click to expand...
Click to collapse
Thanks! That's what I'm thinking. Thinking unfreeze, ungreenify, then unroot. Do a nice reboot for good measure then take the update.
If it fails and I'm still on 4.1.2, just re-root, grab mobile odin, and **** it, let's flash!

I rooted recently using towelroot and uninstalled a bunch of bloat. What would I need to do in order to take the upgrade?

buhohitr said:
Make sure you revert back to factory as much as you can remembered, like build.props, unfreeze all system apps, unroot with Universal unroot, then take the update. But first make a backup of all your apps/settings with Tibu. Worst come to worst it just failed without any harm done and if it failed and you couldn't figure out what's wrong then the fastest way and most reliable way is to Odin stock ML1, then use the OTA to upgrade to 4.4kk then root with Towelroot app, then restore all your apps with Tibu.
Click to expand...
Click to collapse
Huh. Went ahead and gave it a go. Twice. Won't take the update. It's confirmed unrooted. Huh.

my suggestion if you're still on 4.1.2 is to wait till a custom 4.4.2 rom comes out and flash that. or sell me your 4.1.2 lol. this whole locked bootloader stuff is so apple like. shame on you vzw/samsung

suchavibrantthang said:
my suggestion if you're still on 4.1.2 is to wait till a custom 4.4.2 rom comes out and flash that. or sell me your 4.1.2 lol. this whole locked bootloader stuff is so apple like. shame on you vzw/samsung
Click to expand...
Click to collapse
yeah, I may do that. I'm down to the last few months which is why I was like "screw it, let's go vzw". With that in mind, I do need to think about clearing off my personal data, so I may do a factory reset soon because why not and see what happens.
You don't want my phone. While it is in really good condition, the lack of usable micro usb (it flat out doesn't work) gets old.

aarontsuru said:
yeah, I may do that. I'm down to the last few months which is why I was like "screw it, let's go vzw". With that in mind, I do need to think about clearing off my personal data, so I may do a factory reset soon because why not and see what happens.
You don't want my phone. While it is in really good condition, the lack of usable micro usb (it flat out doesn't work) gets old.
Click to expand...
Click to collapse
had a problem w/ a refurb they gave me where the usb port was screwy. i had to firmly hold the cable in at a weird angle and luckly got through a 9min ODIN flash after 4 tries. you could probably chat w/ tech and see if they'll still send you another. i've been outta warranty for awhile but they were really cool, gave me another (although it was a locked 4.3).

suchavibrantthang said:
had a problem w/ a refurb they gave me where the usb port was screwy. i had to firmly hold the cable in at a weird angle and luckly got through a 9min ODIN flash after 4 tries. you could probably chat w/ tech and see if they'll still send you another. i've been outta warranty for awhile but they were really cool, gave me another (although it was a locked 4.3).
Click to expand...
Click to collapse
Giving it one more go, found this little bit of advise on a verizon support board when someone was getting a 402 failure on a Note 2:
https://community.verizonwireless.com/thread/813932
Please wipe your cache partition, then try again. This will not erase data.
• Turn off the device.
• Press and hold the following three buttons at the same time:
• Volume Up key
• Home key
• Power key
• When 'GALAXY Note II' appears on the screen, let go of the Power key but continue to press and hold the Volume Up key and the Home key.
• When the Android System Recovery screen appears, release the Volume Up and Home keys.
• Press the Volume Down key to highlight 'wipe cache partition.'
• Press the Power key to select and wipe the cache.
• With 'reboot system now' highlighted, press the Power key to restart the device.
MarquiaF_VZW
Follow us on Twitter @VZWSupport
Click to expand...
Click to collapse
We'll see! Yeah, if i'm stuck on 4.1.2 and get annoyed, I may re-un-root and give them a shout.

aarontsuru said:
Giving it one more go, found this little bit of advise on a verizon support board when someone was getting a 402 failure on a Note 2:
https://community.verizonwireless.com/thread/813932
We'll see! Yeah, if i'm stuck on 4.1.2 and get annoyed, I may re-un-root and give them a shout.
Click to expand...
Click to collapse
Nevermind.
It failed 402.
lol

I'd wait. If you install OTA, you will NEVER be able to go back and install normal, custom ROMs.

cozzbp said:
I'd wait. If you install OTA, you will NEVER be able to go back and install normal, custom ROMs.
Click to expand...
Click to collapse
Looks like I have no choice. Every attempt to take the OTA has failed.

Related

"Failed to unlock your device, Please try again later"....ugh

OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.
OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably
ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)
Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.
Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.
mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now
OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?
still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?
turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.
Did you manage to get this working?

[Q] I535VRUCNC1 update

does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
esjames said:
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
Click to expand...
Click to collapse
Literally one thing: http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3-4.30.14.pdf
Well, then. Thats a worthy update lol
esjames said:
Well, then. Thats a worthy update lol
Click to expand...
Click to collapse
by all means, if you're traveling to Canada then update away haha
Lmao wow. That's the most pitiful update ever. Seriously, couldn't they have waited until there was something more substantial and then included Canadian roaming in THAT update. As always though, Verizon is dumber than a bag of hammers...
Sent from my iPhone using Tapatalk
Might be worthwhile to extract the modem package and see if the SMS bug is rectified.
wow
i was so sure this was a KK upgrade. been looking around for how to retain root if you take it. thanks for the info!
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
EddieK23 said:
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
Click to expand...
Click to collapse
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
landshark68 said:
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
Click to expand...
Click to collapse
Ah, I see, next time I'm around her I'll re-root it and backup all her stuff with titanium backup, flash the VRUCML1 and factory reset, then restore everything and see if it works.
Strangely enough, when the same update for my Verizon Note 2 came out, I was able to update while rooted even though I unsinatalled theexact same system apps I did on her phone. How strange.
Nonetheless, thank you so much.
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Joe R said:
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Click to expand...
Click to collapse
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Ok thanks. I will try to find an ML1 download.
Sent from my Samsung Galaxy S III using Tapatalk
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
pnuker said:
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Maintained root
twistedillutions said:
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I was able to maintain root on the OTA update by having OTA Survival Mode checked on SuperSU.
SlimSnoopOS said:
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
smalco44 said:
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
Click to expand...
Click to collapse
Apparently I need a refresher on how to properly copy and paste Here's the link again: http://forum.xda-developers.com/showthread.php?p=52515244#post52515244
I have not yet updated to this new patch yet, am I still able to install saferoot as directed on the thread for it or do I need to do something special first?

Any actual and tangible benefits of this OTA they released?

Are there any real benefits to this OTA? I really don't want to bother with wiping and rerooting unless there are some benefits to doing so...sound off with your opinions everybody!
nateohio said:
Are there any real benefits to this OTA? I really don't want to bother with wiping and rerooting unless there are some benefits to doing so...sound off with your opinions everybody!
Click to expand...
Click to collapse
Don't update until someone finds out if root is patched in it, they may have fixed the root exploit in the update so yeah. Waiting also, apologies if this has been confirmed or non confirmed elsewhere, just saw this thread first.
S1L3nTShaDoWz said:
Don't update until someone finds out if root is patched in it, they may have fixed the root exploit in the update so yeah. Waiting also, apologies if this has been confirmed or non confirmed elsewhere, just saw this thread first.
Click to expand...
Click to collapse
Pingpong has been updated...root is possible with this new OTA
nateohio said:
Pingpong has been updated...root is possible with this new OTA
Click to expand...
Click to collapse
But what's the actual tangible benefit of this OTA update?
Scott was saying it frees up RAM.
s197 said:
Scott was saying it frees up RAM.
Click to expand...
Click to collapse
It does seem a lot snappier
Sent from my SM-G920V using Tapatalk 2
I'm not rooted, another thing I've noticed is better battery life.. could be placebo but cell standby is no longer in my battery stats
Do I need to unroot and reroot to do the update? Is that mandatory?
What is the firmware update number
Sent from my Moto Droid Turbo 64G using Tapatalk.
thcltd said:
Do I need to unroot and reroot to do the update? Is that mandatory?
Click to expand...
Click to collapse
If you want to take the OTA, you need to unroot. Easier way is to Odin to the new update. See the restore to stock thread for instructions.
Plug the phone into your computer, run the verizon installation. Open the app and update your device. Download load the ping pong root apk and side load it. Install and root, reboot. Upgrade and root done without losing any data or apps. I did this 2 days ago successfully. Took maybe 20 minutes. Make sure you have a charge much higher than 50%, say 75% as if you get less than 50% during the upgrade, you soft brick your phone. Charging it while the blue logo saying you need to repair is slow, quick charge doesn't seem to work but leave it plugged a for a while. A repair fixes the install. I actually had to go through this not thinking it falling under 50% would make a difference.
Shawn haz root said:
Plug the phone into your computer, run the verizon installation. Open the app and update your device. Download load the ping pong root apk and side load it. Install and root, reboot. Upgrade and root done without losing any data or apps. I did this 2 days ago successfully. Took maybe 20 minutes. Make sure you have a charge much higher than 50%, say 75% as if you get less than 50% during the upgrade, you soft brick your phone. Charging it while the blue logo saying you need to repair is slow, quick charge doesn't seem to work but leave it plugged a for a while. A repair fixes the install. I actually had to go through this not thinking it falling under 50% would make a difference.
Click to expand...
Click to collapse
So to make sure my dumb ass is clear, this process can be followed using a currently rooted device, without needing to do any special prep work such as uninstalling supersu or otherwise explicitly unrooting the phone prior to using the verizon update service on a PC to get the new OTA loaded?
Shawn haz root said:
Plug the phone into your computer, run the verizon installation. Open the app and update your device. Download load the ping pong root apk and side load it. Install and root, reboot. Upgrade and root done without losing any data or apps. I did this 2 days ago successfully. Took maybe 20 minutes. Make sure you have a charge much higher than 50%, say 75% as if you get less than 50% during the upgrade, you soft brick your phone. Charging it while the blue logo saying you need to repair is slow, quick charge doesn't seem to work but leave it plugged a for a while. A repair fixes the install. I actually had to go through this not thinking it falling under 50% would make a difference.
Click to expand...
Click to collapse
I totally didn't want to thank you. Seriously you don't need to be at 75% or you'll soft brick. WTF are you smoking?
twiz0r said:
I totally didn't want to thank you. Seriously you don't need to be at 75% or you'll soft brick. WTF are you smoking?
Click to expand...
Click to collapse
When my battery fell below 50% my upgrade failed. I had a blue screen that told me it failed and I needed to repair the install. Maybe the term "soft brick" was not correct but it was in an unusable state.
funkybside said:
So to make sure my dumb ass is clear, this process can be followed using a currently rooted device, without needing to do any special prep work such as uninstalling supersu or otherwise explicitly unrooting the phone prior to using the verizon update service on a PC to get the new OTA loaded?
Click to expand...
Click to collapse
I would back up your data just incase but you don't need to do anything prior. I didn't.
Shawn haz root said:
When my battery fell below 50% my upgrade failed. I had a blue screen that told me it failed and I needed to repair the install. Maybe the term "soft brick" was not correct but it was in an unusable state.
I would back up your data just incase but you don't need to do anything prior. I didn't.
Click to expand...
Click to collapse
Unless that happened to you more than once you can't really definitively say that that was the reason it didn't work.
Shawn haz root said:
Plug the phone into your computer, run the verizon installation. Open the app and update your device. Download load the ping pong root apk and side load it. Install and root, reboot. Upgrade and root done without losing any data or apps. I did this 2 days ago successfully. Took maybe 20 minutes. Make sure you have a charge much higher than 50%, say 75% as if you get less than 50% during the upgrade, you soft brick your phone. Charging it while the blue logo saying you need to repair is slow, quick charge doesn't seem to work but leave it plugged a for a while. A repair fixes the install. I actually had to go through this not thinking it falling under 50% would make a difference.
Click to expand...
Click to collapse
I did shawn haz root's way to update my device and did so successfully (i was rooted before update), but now when I try to root again with pingpong beta6, it says my device is not supported. Update at your own risk!
EDIT: with the new update my s6 feels a lot quicker and snappier like the other user mentioned. I haven't had the time to test out battery life yet, but the speed increase is significant and noticeable. Opening apps, clicking the home button is all very smooth
NumberTwoinQQ said:
I did shawn haz root's way to update my device and did so successfully (i was rooted before update), but now when I try to root again with pingpong beta6, it says my device is not supported. Update at your own risk!
EDIT: with the new update my s6 feels a lot quicker and snappier like the other user mentioned. I haven't had the time to test out battery life yet, but the speed increase is significant and noticeable. Opening apps, clicking the home button is all very smooth
Click to expand...
Click to collapse
Try to reboot your phone. Click on "Download Data" under the "Get Root" button, then try to get root. Did you install the Super SU when it popped up after you installed Ping Pong Root? It worked no problem for me.
Shawn haz root said:
Try to reboot your phone. Click on "Download Data" under the "Get Root" button, then try to get root. Did you install the Super SU when it popped up after you installed Ping Pong Root? It worked no problem for me.
Click to expand...
Click to collapse
Thank you!!!!
You have to click download data first before you get root. That solved the problem for me. Many thanks
Ram management still sucks. My apps constantly have to reload. Recent apps tab also lags. This will probably be my last Samsung phone I ever buy.
Sent from my SM-G920V using XDA Free mobile app
Sound like there might be a reason to take this....anybody else notice that cell standby isn't a battery drainer anymore?

bricked s8+ trying to root

ive tried to root my s8+ following the step by step guide but now its a brick
i have never rooted before and tried it for the first time, everything seemed to be going correctly until i pressed wipe and swiped to confirm, i got error message unable to mount storage, now i have a continuous loop of samsung s8 logo
i have tried connecting to odin again and no joy.
is there any hope or is it for the bin ?
gutted
What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....
i have model SM-955F
Download the stock ROM and download mode should be reachable, where you can then flash it
Pedroc1999 said:
Download the stock ROM and download mode should be reachable, where you can then flash it
Click to expand...
Click to collapse
i need more information if possible ? i have no idea how to do it, its my first and probably last attempt at rooting
It's probably not binned, don't worry. Can you get into Download mode again?
- Press and hold the Bixby, Volume down and Power buttons together until you see anything on screen.
- When you see a warning screen, hit Volume Down to continue to download mode.
GibMcFragger said:
What model do you have? If it's a Snapdragon, they are locked down tight and not rootable. You may have just made a drink coaster....
Click to expand...
Click to collapse
Come on man, if you had a snapdragon version, you can't root or even get that far.
yes i can get into the screen where it says downloading do not turn off
It does look like it's the usual snapdragon variant, yeah. You need the Exynos version for its unlocked bootloader, if you want root and whatnot.
Honestly unless you have specific reasons for root, you probably don't need it.
I was pleasantly surprised at how much I don't miss it so far, but I can't speak for everyone else. I know Brava27 wouldn't dare.
Edit: Okay good. So the Stock ROM is basically the factory image always intended for your phone, from Samsung. You just have to find and download that, then flash it as usual via Odin.
PLEASE triple check around and do your research on whether this link provides you the right one, but here is a first-hit I found when searching for a stock rom for your model. https://forum.xda-developers.com/galaxy-s8/how-to/sm-g955f-stock-odin-firmware-t3585022
brilliant thank you i will give it a try
does it unroot it also if i flash it back to stock and put knox back to normal or is that history now ?
That's right, it's completely stock, so it'd be like you got the phone fresh. It'll be unrooted if you get it working.
So that said, ensure your SIM is in the phone before you set it up, or it'll reset on you again when you insert it later.
I'm not sure what Knox's status would be and if the e-fuse has triggered... you'll know when you're powering on the device, I think. It's no real matter, unless you're concerned about warranty. In which case, you were going to stop caring about that right after attempting to root anyway.
I'm still not certain on what firmware file you want. Might want to search around for something that matches your carrier.
once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.
galarond said:
once you root knox is triggered forever, no way to use samsung pay or samsung health in stock not rooted firmware.
Click to expand...
Click to collapse
can you use them on rooted devices with knox triggered ?
No, I was not able to use Samsung Pay on my Note 5 after I tripped knox. It does some sort of security check on start-up of the app.
The bigger question is whether it "rooted" yet or not. With some luck, the e-fuse has not triggered yet and it's a clean device still.
widget2k13 said:
can you use them on rooted devices with knox triggered ?
Click to expand...
Click to collapse
yes with custom roms can be done or with some build.prop mods too.
So the snapdragon version is not rootable? Damn, I didn't know that.
woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here
widget2k13 said:
woohoo somehow and i have no idea how i managed to get it working again and its rooted
couple of things though now its rooted
i have a security notice always popping up saying there is a problem with my phone and it needs repaired, how do i stop that ?
i found a post about changing a 1 to a 0 to get s health working but when i edit it and try to save it i get error read only file unable to save.
the main reason i wanted it rooted was to stop the annoying heads up display so i installed the noheadsup app which said it installed but i cannot see it on my phone anywhere to change the settings
also the battery drain , normally overnight it uses about 5% battery, last night 32% overnight
apart from that it all seems to be working as normal thanks to the help from people on here
Click to expand...
Click to collapse
For the "Security notice" try this:
root explorer go to /system/app/SecurityLogAgent delete folder
For "S-Health" to work, follow this:
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Good luck.
Totaly different sittuation but I think I have this right from what you say in this thread.
That Knox being tripped cant be reversed? and that Knox is a fuse so it cant be bypassed with otg cable backup?

update or not to update, that is the question

I'm patiently waiting for root for my s8+, and I'm already getting updates pushed to my phone. Should I hold of updating until I can root my device or is it safe to proceed with the update? I don't want to update if it might disable my ability to root later.
SevnSins said:
I'm patiently waiting for root for my s8+, and I'm already getting updates pushed to my phone. Should I hold of updating until I can root my device or is it safe to proceed with the update? I don't want to update if it might disable my ability to root later.
Click to expand...
Click to collapse
you answered your own question
If root is important, then skip the updates. Taking them creates risk of not being able to go back. That said, I wouldn't count on the US version getting rooted. If that is important get an international version or stick with the pixel.
Thing is, root is getting less and less necessary. Used to be 110% for me, now I'm sitting with this device and no root. The only thing I'd like to do is change the Bixbie button.
Android has come a long way.
Aridon said:
If root is important, then skip the updates. Taking them creates risk of not being able to go back. That said, I wouldn't count on the US version getting rooted. If that is important get an international version or stick with the pixel.
Thing is, root is getting less and less necessary. Used to be 110% for me, now I'm sitting with this device and no root. The only thing I'd like to do is change the Bixbie button.
Android has come a long way.
Click to expand...
Click to collapse
I'll hold off for a bit and just purchase the package disabler app. Thank you for feedback.
Aridon said:
If root is important, then skip the updates. Taking them creates risk of not being able to go back. That said, I wouldn't count on the US version getting rooted. If that is important get an international version or stick with the pixel.
Thing is, root is getting less and less necessary. Used to be 110% for me, now I'm sitting with this device and no root. The only thing I'd like to do is change the Bixbie button.
Android has come a long way.
Click to expand...
Click to collapse
there are apps in the playstore for the bixby button remap already
Aridon said:
If root is important, then skip the updates. Taking them creates risk of not being able to go back. That said, I wouldn't count on the US version getting rooted. If that is important get an international version or stick with the pixel.
Thing is, root is getting less and less necessary. Used to be 110% for me, now I'm sitting with this device and no root. The only thing I'd like to do is change the Bixbie button.
Android has come a long way.
Click to expand...
Click to collapse
Same here. Even the last Samsung phone I had didn't really need root which was a note 3. The phone just works.
The s8+ is a great phone so far, I just like the ability to install custom roms and customize my phone how I want.
Don't Update, If you have a Note 7.
If you dont have a Note 7, Update.. By all means.
So, Rather than wasting a post,
I have rooted mine, and I manually flash my updates over ODIN using the Home_CSC, so my data stays intact.
As soon as you flash over odin, you need to boot to TWRP, and then flash the Kernel, or else, you will enable the encryption again.
Root - Was worth it. The only things I lost was SamsungPay and Secure Folder. However, on the other hand - I've got built-in Call recording, Built-in Caller ID, Bixby button remapped to open the Camera, Ads Blocked from Hosts file, iOS Clean Emjoi's installed to system, TouchWiz removed and Nova installed in system... I can go on.
JazonX said:
Don't Update, If you have a Note 7.
If you dont have a Note 7, Update.. By all means.
So, Rather than wasting a post,
I have rooted mine, and I manually flash my updates over ODIN using the Home_CSC, so my data stays intact.
As soon as you flash over odin, you need to boot to TWRP, and then flash the Kernel, or else, you will enable the encryption again.
Root - Was worth it. The only things I lost was SamsungPay and Secure Folder. However, on the other hand - I've got built-in Call recording, Built-in Caller ID, Bixby button remapped to open the Camera, Ads Blocked from Hosts file, iOS Clean Emjoi's installed to system, TouchWiz removed and Nova installed in system... I can go on.
Click to expand...
Click to collapse
Which phone so you have? Root for the US s8+ isn't available yet last time I checked.
The last time you checked AND the next time too. He obviously has a rootable phone(probably F).
albozz said:
But hpow does u know dat fo sho?? TALK TO ME !!!!!!!
Click to expand...
Click to collapse
Why shouting?a simple google search will show snapdragon will not have root
Actually a quick Google search finds a root method supposedly provided by chainfire, but it's not hosted on XDA, soi I didn't trust it.
http://www.teamandroid.com/2017/05/03/root-galaxy-s8-plus-android-firmware/
SevnSins said:
Which phone so you have? Root for the US s8+ isn't available yet last time I checked.
Click to expand...
Click to collapse
Mine's Exynos. G955FD

Categories

Resources