Related
Just got a Sensation this last Sat, my first Android phone, and am interested in rooting it. Never done this on any phone and am a little confused as many guides are for people who want to flash roms. For now, I would just like to root in order to get rid of some preinstalled apps. Is there a guide that has the minimal steps needed to just root? Also, does rooting do anything to my settings or apps that are there now?
MANTI5 said:
Just got a Sensation this last Sat, my first Android phone, and am interested in rooting it. Never done this on any phone and am a little confused as many guides are for people who want to flash roms. For now, I would just like to root in order to get rid of some preinstalled apps. Is there a guide that has the minimal steps needed to just root? Also, does rooting do anything to my settings or apps that are there now?
Click to expand...
Click to collapse
Follow steps one to three on the first post of this.. and that is it
Ok, didn't quite understand the guide here but found a video that made it easy and now I'm rooted. Will this keep me from receiving updates? When I get updates will this unroot the phone? Also, which apps are safe to remove without messing anything up?
Bump for answers.
MANTI5 said:
Ok, didn't quite understand the guide here but found a video that made it easy and now I'm rooted. Will this keep me from receiving updates? When I get updates will this unroot the phone? Also, which apps are safe to remove without messing anything up?
Click to expand...
Click to collapse
Hello and welcome to the forums.
To property receive OTA updates you need a stock recovery - that's a must! We cannot predict what HTC is going to update next so if you delete a package that is going to be updated - yeah, this may cause troubles. So deleting kinda anything as root may cause a OTA update to fail. I suggest that you buy a application that does a backup when uninstalling a package. I'm using Root Uninstaller Pro to "freeze" some apps just in case HTC releases a OTA that needs one of those disabled apps.
In case you have any other questions feel free to ask.
Jackos said:
Hello and welcome to the forums.
To property receive OTA updates you need a stock recovery - that's a must! We cannot predict what HTC is going to update next so if you delete a package that is going to be updated - yeah, this may cause troubles. So deleting kinda anything as root may cause a OTA update to fail. I suggest that you buy a application that does a backup when uninstalling a package. I'm using Root Uninstaller Pro to "freeze" some apps just in case HTC releases a OTA that needs one of those disabled apps.
In case you have any other questions feel free to ask.
Click to expand...
Click to collapse
If you are running the stock ROM you can just update OTA right? I'm not running a stock ROM so i dont have any OTA at all, but just curious...
I'm running stock rom, nothing changed except it's rooted. Are you saying I won't get any OTA updates from HTC? Would I get them if I took the phone in to a T-Mobile store, say when ICS is released or would it still not update because it's rooted?
MANTI5 said:
Ok, didn't quite understand the guide here but found a video that made it easy and now I'm rooted. Will this keep me from receiving updates? When I get updates will this unroot the phone? Also, which apps are safe to remove without messing anything up?
Click to expand...
Click to collapse
what video did you follow?
Not sure of it's exact location because I didn't bookmark it, but it was on youtube.
Anyone know the answer to my last question?
to find your answer boot into recovery on your phone, if you see it orange or blue with lots of options and on top it says CWM custom recovery, then no you will not receive OTA's, but to be honest thats ok, usually we root users get OTA leaks before its even released, expamle ICS some one is already working on ICS port so we will see ICS before even official release is even out
and if your rooted i found best way to remove bloat is to use titanium backup
back up the apps you want to remove in there and from the same app there is an option to uninstall it
Ok, got TB. Is there a list somwhere of apps that are safe to remove from the sensation? Also, when ICS is released, will putting it on my phone myself erase anything I currently have or not work at all if I start removing apps? Sorry for all the questions, this is my first smartphone.
Hi, I'm looking for advice on when (not how) to root/unlock my phone. I'm coming from the "unbrickable" Captivate, and I really miss the peace of mind that came along with that. Here's my situation: I used to be a software developer, so the command prompt doesn't scare me, and I can follow directions carefully. However, I really cannot risk bricking my phone--I can't afford to waste extra money or spend time without a phone just because I wanted to tinker (the married folks will understand).
I've been following the dev forum for the last month. Originally I had decided to just leave my phone bone stock until there was a reliable and time-tested root/unlock method. But the idea of a "window" in which to unlock the bootloader has me a little bit spooked. Could I miss my chance? I also know there's no working root for 1.85 (I'm on 1.73). Is it possible that when AT&T pushes the official OTA, whenever that is, that I could be stuck without root? Or is it just a matter of devs being motivated to do it once everyone is there?
Finally, is there any bricking risk to simply rooting my phone, and not trying to mess with the bootloader? I would at least like to get ad blocking back on.
Thanks for any advice, it's much appreciated.
There is always risk, it can not be avoided.
No mater how careful you are something can go wrong.
Me I look at the risk vs reward.
The only issue I have for example is the phone once I put it into Airplane mode locks into Airplane mode, intermittantly.
No ROM I know says this bug is fixed, and even if there is a fix is it worthwhile for me to take a chance?
..... I am waiting so far seen no compelling reason to root my device.
AstroDigital said:
There is always risk, it can not be avoided.
No mater how careful you are something can go wrong.
Me I look at the risk vs reward.
The only issue I have for example is the phone once I put it into Airplane mode locks into Airplane mode, intermittantly.
No ROM I know says this bug is fixed, and even if there is a fix is it worthwhile for me to take a chance?
..... I am waiting so far seen no compelling reason to root my device.
Click to expand...
Click to collapse
Thanks for the reply. Yes, it's all about "risk vs. reward". I'm pretty clear on the "reward" part: rooting lets me block ads and run a few other nice things like tethering, memory management tweaks, etc., and unlocking the bootloader lets me install a custom recovery and third-party ROMs which, for me, will be pretty important to my long-term satisfaction.
What I'm looking for is specific and reliable advice on the "risk" side of the equation, both for rooting and for unlocking, and for waiting to do either of those. In particular, is there a risk that if I wait too long to unlock, I'll end up stuck with it locked forever? I guess it wouldn't matter so much, since dev support would probably dry up in that scenario, but it's something I've been worrying about. This is only my second Android phone.
1.73 is the best place you can be In my opinion for rooting and unlocking. Kennethpenn's one click root for our phone is stupid simple to use. The One click SuperCID is the same. Stupid simple, but I havn't really needed any reason to unlock really. I've unlocked but havn't flashed any roms or anything or even installed recovery yet.
The "window" too unlock/root your device is pretty much before you upgrade to 1.85. With all the one-click scripts available there's a lot less risk than if you had to say, copy/paste or type out all the commands yourself, but again there's always risk.
As long as you root, unlock your bootloader, AND install with CWM Recovery or TWRP BEFORE you upgrade to 1.85 then you're good.
As long as you're SuperCID, you can reunlock using HTCDev (I used the same unlock token that was provided when I was on 1.73...may or may not work for all though). Since you installed a custom recovery before upgrading, you can flash SU and have it manually update the binary and boom, you're rooted again.
Just be sure to follow all instructions to the letter. The only insanely risky part was changing the CID manually (I spent a good 5 minutes staring at my hex editor to make sure things were right), but there's a one click for that now.
yes. while your on 1.73, do the supercid and get the unlock token from HTCDev. keep this token!!!! forever even, as you will be able to use it again and again to relock and reunlock bootloader. as long as you know what you are doing, i'd recommend you go ahead root unlock bootloader, relock, ruu to 1.85, and reunlock. devs are starting to spit out some really cool stuff.
Thanks guys, that's exactly the kind of advice I'm looking for. One more question: I know around the time that the BL unlock was first achieved, there was some worry that HTC would "patch" it, or do something, so that it would stop working. Is that worry justified, or can I count on being able to unlock whenever I choose as long as I'm still on 1.73?
Edit: ethantarheels123 answered exactly this before I even got done typing it. Awesome!
Tinyboss said:
Is it possible that when AT&T pushes the official OTA, whenever that is, that I could be stuck without root? Or is it just a matter of devs being motivated to do it once everyone is there?
Click to expand...
Click to collapse
If AT&T pushes out 1.85 as an OTA and you install it, then you will be stuck without root and without bootloader unlock (unless AT&T also decides to unlock the bootloader officially). Devs coming up with a new root method is always possible, but I wouldn't count on it. A lot of people are already rooted, superCID and unlocked bootloader on 1.85. So not sure how much interest there will be on rooting 1.85 when other things are higher priority (S-Off, custom ROMs, kernels), even if 1.85 gets pushed out as an OTA.
The one-click root method is ridiculous simple, and not much can go wrong. If for some reason anything goes wrong, you can just run the RUU to get back to stock. One clock SuperCID is also simple, with little risk as well. As mentioned, everything has a risk. But if you use these methods to root and unlock, it seems the risk is quite small. If root privileges, and the ability to flash custom ROMs is important to you, I'd say the odds are highly in your favor. If not, and you are thinking of doing it just in case the "window" closes, than that's a tougher call to make, and its up to you to judge.
---------- Post added at 12:31 PM ---------- Previous post was at 12:27 PM ----------
Tinyboss said:
Thanks guys, that's exactly the kind of advice I'm looking for. One more question: I know around the time that the BL unlock was first achieved, there was some worry that HTC would "patch" it, or do something, so that it would stop working. Is that worry justified, or can I count on being able to unlock whenever I choose as long as I'm still on 1.73?
Edit: ethantarheels123 answered exactly this before I even got done typing it. Awesome!
Click to expand...
Click to collapse
There is always the possibility that HTC may plug the hole by which SuperCID allows you to get an unlock token. Whether they will or not, who knows.
Also keep in mind that keeping the token to reuse does not always work. It worked for me, but not other people. So no guarantees.
I'm on 1.73 and I'm rooted only. (I'm also married and love this stuff but just don't have time to be redoing over and over and/or getting stuck). For now, root is enough for me and from what I've seen, there isn't much reason to rush into unlocking bootloader. Most things are WIPs or unoffical ports or have a list of "stuff not working" which makes it pointless unless you are into that beta experience.
Root is awesome and when the other stuff becomes official or fully working, I'll get do that stuff too.
Anyone get this yet?
Someone that gets the update notification AND is rooted.. can you pull the update zip and send it to me?
This needs to be done BEFORE you run the update.
File should be in the /cache partition.
Need to know if root changed.. also wanna see if they blocked the loki exploit. Thx :good:
I ws at work today with no WiFi on, and when I pulled the phone out of my pocket this update had already applied itself. I have knock knock on so that could have allowed my nether regions to authorize the update. Anywho, if I can still safely use lg flash tool to go back to 80010d then I can flash back and see if the server will push 10q again. Nothing in stone but it be nice to have some clue from someone with greater understanding if i can flash back to 10d without creating problems from this new update. The AT&T variants have Carrier IQ installed. Is it possible LG is aware of my flashing back and forth from Cymod to stock and forced the update without a prerequisite consent toast popup?
COMROM said:
I ws at work today with no WiFi on, and when I pulled the phone out of my pocket this update had already applied itself. I have knock knock on so that could have allowed my nether regions to authorize the update. Anywho, if I can still safely use lg flash tool to go back to 80010d then I can flash back and see if the server will push 10q again. Nothing in stone but it be nice to have some clue from someone with greater understanding if i can flash back to 10d without creating problems from this new update. The AT&T variants have Carrier IQ installed. Is it possible LG is aware of my flashing back and forth from Cymod to stock and forced the update without a prerequisite consent toast popup?
Click to expand...
Click to collapse
you can certainly downgrade back to 10d using LG Flash without causing issues. That may not ALWAYS be the case with future OTA updates but LG has not yet enforced "anti-rollback"
As for the update being installed.. I have read that you can only delay the update install so many times.. but after a certain amount of time the update is forced. Now I've only read this and can't say from first hand experience.. but maybe thats what happened to you. If that is the case and updates are being forced after a set time.. the only way to get around the update would be to freeze or remove the apk responsible for updates.. not even sure which apk is responsible offhand.
HERE's the link to where I read about the update.
"You can delay the update up to three times for four hours each time. After the fourth delay, the update will automatically get installed on the phone."
The fact that it auto installs at all is worrisome
Thanks for that. The responses in your link indicate they were not asked permission explicitly to apply the update. The fact that this, "paves the way for future updates," worries me that the bootloader has changed. I can confirm the radio has not. I work odd hours. When I'm off in the AM I'll see if i can't warm up LG Flash Tools and revert to 10d from download mode. If so I'll see whats up with root and pulling the update. Considering multiple sources are stating there was no confirmation it gives me a hunch this may have something to do with patching loki exoloit, though I have no emperical evidence of prior statement.
Soooo, if you Google "lg d80010q" there are three entries now. One of which is this
http://csmg.lgmobile.com:9002/csmg/b2c/client/agent_phonesw_notice_list.jsp?country=US
Not being a deepweb database expert I wonder if this might allow the update to be retrieved directly from LG.
COMROM said:
Soooo, if you Google "lg d80010q" there are three entries now. One of which is this
http://csmg.lgmobile.com:9002/csmg/b2c/client/agent_phonesw_notice_list.jsp?country=US
Not being a deepweb database expert I wonder if this might allow the update to be retrieved directly from LG.
Click to expand...
Click to collapse
nope just notifies LG service centers whats newly available.
Was running stock. Used LGFlashTool to go back to 10d and 10o and can't get the server to push the update even after trying to check for it from both cellular data and several different IP's while on WiFi. No dice. Software update 10q simply hasn't come to me yet. Out of time and energy at the moment. Sorry.
This update put my phone into a recovery loop and was unusable. I finally got it back to stock and about 48 hours later it just updated itself . There is barely any warning, a box pops up saying its updating and it does it! I dont like this at all ,any update should require some kind of approval from the user . But at least my phone runs great now!
Anyone with new "q" update....can you confirm that root works? I got stuck in bootloop when it installed and ended up restoring nandroid backup before I fixed it so i'm still on "o" for now.
Thanks,
The other afternoon I was busy pecking away at my laptop with my phone on the charger. All of the sudden my phone has the pretty blue sky over a green, grassy field and it's updating! I did not have the device on WiFi and I did not confirm this update. This update is being forced upon us AT&T users without any confirmation. I suppose it's small size and their over confidence in SHA/CRC checks make them think installing an update loaded over a cellular connection is a good idea. Heck, at least this is rumored to be paving the way for some official form of KitKat. The folks that work on this phone and produce such things as Cyanogenmod and other Android Remixes are amazing! I simply like the clip tray, knock-knock, my back LED working and better bench numbers to much to be swayed from stock. That is just my preference. Y'all still rock chicks off socks with the "ROMs"!
COMROM said:
The other afternoon I was busy pecking away at my laptop with my phone on the charger. All of the sudden my phone has the pretty blue sky over a green, grassy field and it's updating! I did not have the device on WiFi and I did not confirm this update. This update is being forced upon us AT&T users without any confirmation. I suppose it's small size and their over confidence in SHA/CRC checks make them think installing an update loaded over a cellular connection is a good idea. Heck, at least this is rumored to be paving the way for some official form of KitKat. The folks that work on this phone and produce such things as Cyanogenmod and other Android Remixes are amazing! I simply like the clip tray, knock-knock, my back LED working and better bench numbers to much to be swayed from stock. That is just my preference. Y'all still rock chicks off socks with the "ROMs"!
Click to expand...
Click to collapse
Not sure if this helps at all...
I had this update (d80010q) installed and tried to root (for the first time). I was unable to. Superuser was transferred, but did not have root access. Looks like I may have to downgrade before rooting. Is this correct? Thanks!
Can anyone provide tot for the d80010q
Root not working.
I can attest to not being able root my G2 with D80010q on it. Hop4efully a fix soon?
lostangelintx said:
I can attest to not being able root my G2 with D80010q on it. Hop4efully a fix soon?
Click to expand...
Click to collapse
manual iotroot steps for the att 10o update should work just fine.
Hmm
I have Lg G2 (Att) & hours b4 I have reflash'd back 2 stock and applied root about an hour later i got OTA so I click'd 2 recieve OTA it came back sayin Cant download OTA on rooted device if that helps and thatt was almost 24\hrs ago n still runnin smoothly but file was only like 16MB
This is n another thead then I start'd readin here so I thought this should b post's here 2
So will a bigger OTA push current root'd stock rom out n brick my fone¿
autoprime said:
manual iotroot steps for the att 10o update should work just fine.
Click to expand...
Click to collapse
Should I change the command to d80010q on the copy / paste command for this phone? or leave it at d80010o?
lostangelintx said:
Should I change the command to d80010q on the copy / paste command for this phone? or leave it at d80010o?
Click to expand...
Click to collapse
d80010o isnt part of the command. it starts at "adb"
I got this update few days ago.. I was rooted on "d", it went to "o" after i postponed it 4 times, and it went to "q" automatically without asking.
I use pattern as my screen lock, at random times, phone will reboot from AT&T logo.. it's very annoying, and i'm not sure what to do about it.. I can go back to "d" but ATT will eventually update it.
Anyone get TWRP to install after root on this? I used FreeGee with mine. Says installed successfully, but TWRP app is nowhere to be found.
Also, Root Browser never asks for SU access, as the other root apps do, and the apps I can supposedly safely remove are not in the /system/app folder. Very confused now.
---------- Post added at 05:48 PM ---------- Previous post was at 05:05 PM ----------
Root. Checker and terminal emulater both show me to have root access.
However root explorer doesn't show any of the apps that are supposed to be safe to remove, and it never asks for su permission like the other root apps do.
Also there is no/ system/apps folder. There is only/ system/app. Are these folders hidden somehow?
Sent from my LG-D800 using xda app-developers app
Sent from my LG-D800 using xda app-developers app
My phone tried to install this automatically with root the other day, and soft-bricked... Had to delete the files via adb and got back in relatively scot-free. Anyway apparently there is actually a 4.4 update being pushed right now for the d800. I would go for it but I am still rooted and would like to keep my root... And am also waiting for Aospa so I may let it settle before I jump in
LG G2
I'm considering jumping to the S7. Is there a reliable, working root yet?
reliable yes
working yes
some issues yes
issues can be remedied for most people
sacnotsack said:
reliable yes
working yes
some issues yes
issues can be remedied for most people
Click to expand...
Click to collapse
What kind of issues? I'm getting mine tomorrow and I would like to root pretty much right away. I've been through the threads and didn't see much as far as issues.
metalfan78 said:
What kind of issues? I'm getting mine tomorrow and I would like to root pretty much right away. I've been through the threads and didn't see much as far as issues.
Click to expand...
Click to collapse
overheating, lag, extreme batter drain, but these can be fixed by setting the cpu governor to on-demand or interactive. those were the only issues I personally experienced, but was easily fixed.
occasionally I will have bad lag, but after a reboot all is well. speaking of boots....boot time is horrendous.
Well, the lag is what I'm trying to get rid of, which is what I'm currently getting with my LG G5. So, I guess switching to the S7 won't make much difference.
Sent from my LG-H830 using Tapatalk
Sounds fixable. I think I'll go stock for a day or so then root it.
I have read that if you freeze the bloat, that helps with battery and lag issues as well.
So, from what I've read, it has to do with the modified boot.img. I really just want to restore all my stuff from titanium backup
Maybe rooting isn't even worth it right now. Unless I root, restore, then flash stock boot.img, if possible.
metalfan78 said:
So, from what I've read, it has to do with the modified boot.img. I really just want to restore all my stuff from titanium backup
Maybe rooting isn't even worth it right now. Unless I root, restore, then flash stock boot.img, if possible.
Click to expand...
Click to collapse
Not really worth it... there are some workarounds. But, you will never get rid of the lag. Stay on stock until there is either a new root method or unlocked bootloader.
EDIT: Echoe Rom is out for the SMG930T and SMG935T !!!!!! No lag at all
Thats what I plan on doing for now
metalfan78 said:
Thats what I plan on doing for now
Click to expand...
Click to collapse
Flash the U firmware. Removes the bloat.
Is the bloat the only cause of the lag?
metalfan78 said:
Is the bloat the only cause of the lag?
Click to expand...
Click to collapse
No. The eng boot will cause a little lag and more battery drain than compared to stock.
lvpre said:
No. The eng boot will cause a little lag and more battery drain than compared to stock.
Click to expand...
Click to collapse
Ok, that's what I was reading. I think I'll wait it out a bit. I've had the phone for 24 hrs and that's the longest I've gone without rooting in like 7 years, lol.
https://drive.google.com/open?id=0B0yzuMcMjykeV0wwYnVmbmp0SnM
download this it will help with the CPU , lag , wifi not saving, battery drain, can log in to snapchat, debloat,.. etc
You'll brick your s7
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
The US models are able to be rooted. You are not well informed if you believe otherwise. I highly doubt you "bricked" your phone, probably just a boot loop or stuck at a screen. it can be fixed.
The engineering boot is how we are able to obtain root. There are a ton of details on how it works, so I am not going to go into details.
please don't post misinformation, it only confuses the ones trying to learn.
-sent from my Rooted and stable Tmo S7
sacnotsack said:
The US models are able to be rooted. You are not well informed if you believe otherwise. I highly doubt you "bricked" your phone, probably just a boot loop or stuck at a screen. it can be fixed.
The engineering boot is how we are able to obtain root. There are a ton of details on how it works, so I am not going to go into details.
please don't post misinformation, it out lyrics confuses the ones trying to learn.
-sent from my Rooted and stable Tmo S7
Click to expand...
Click to collapse
You are right... there are working root methods... that works flawlessly with a few tweaks... In regards to the bricking, The firmware I've had the most issues with is PG1 but it is a simple fix, just disable or block security updates with titanium backup ... or alternatively you can install Echoe Rom which debloats, deodex's and deknox's. I've had zero issues with this rom. No bricks no boot loops and no lag. I hope this helps
boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
It may not be the prettiest root, but it is a working root none-the-less. Other than the eng boot lag issues (which can be mitigated mostly through things like Govtuner, etc.), all apps that require root permissions work fine as intended. Bootloops can be avoided by disabling security policy services. Other than the random reboot every now and again, I'm running strong since the day root came out.
boobteg2 said:
Looks guys, if you knew anything about locked bootloaders, or rooting at all, its not as simple as an odin flash then a root.bat execution and your done. It might root for a while as did mine, then security will catch up with the phone. C'mon so many people are going to have bricked phones because of these fake postings.
I tried it for fun, knew it would brick the t-mobile S7, and it did. I just wanted to be 100% positive before I wrote this. Don't root your U.S. S7, it is impossible and will lead to nothing but problems and stuck boot because of google/samsung security. They went as far as blocking the google account registered with the S7 on google at the time. So think before you just odin then root.bat, your opening more than just a door, trust me.
On top of that, non of the so called odin flashable recovery firmwares are real. They just lead to advertising websites that collect cookie data and make you click links you don't want to click. Be advised.
Of course advertising and spam companies are going to take advantage of people like the android rooting community, who know they are taking a risk rooting in the first place, so you cannot complain when you get malware from these sites, because technically your doing something your not supposed to. Don't just go clicking random downloads because they sound legit. 90% are not.
---------- Post added at 11:08 AM ---------- Previous post was at 10:39 AM ----------
If I am wrong about the recovery file, or a flashable image file that actually roots the phone (custom recovery TWRP, cwm anything) please prove me wrong. Root is not root without the recovery. Don't try to root any android phone without an available custom recovery and legit recovery files at hand.
The S7 has a locked bootloader for a reason, attempting root without a custom recovery available to work with is plain stupid.
Click to expand...
Click to collapse
Wow talk about uninformed. I've been running a rooted Galaxy S7 for just about a month now. I had rooted even earlier then that but I didn't know about the security policy updating. Yeah, security caught up but it didn't brick the phone. Just reflash the stock files and everything is fine. Now that I've been able to freeze the security update policy I haven't had a problem.
Ok, if you're an owner of the Hydro Wave model from Kyocera, I think we all can agree that it is a nice phone. Being water proof, shock resistant, and still have decent enough software. However it is a bit buggy. There are a few kinks that need to be worked out. And can we get an OS update for Christ's sake? Had this phone a little over a year, still running 5.1. Glad we got a little bug update the other day!
But the point of this thread is so that we can get together and keep a discussion about the phone, finding new exploits, actually getting a good root, new attributes, abilities updates, whatever. If you are here, than you already know how much of a pain this phone is to research and find out any information on it. Especially when you go to root.
I hope to see you in the comments, maybe I can share a little bit of info with you, and hopefully you can teach me a few things. And please let's keep this a civil thread and stay on subject as much as you can.
What was in the update?
What was in the update?
Not exactly what they did. It said they were fixing a few bugs. But didn't give any explanation and it still runs 5.1
Have you or any one you know managed to get root?
Not for they hydro phone c6740. I've gained root access from KingRoot. But it wouldn't read superuser or BusyBox
Anybody ever give root to work for more than a little while?
---------- Post added at 03:03 PM ---------- Previous post was at 02:53 PM ----------
And if anybody knows how to root please let me know
Yeah let us all knoe please! Or even if you grt super user to work for just a little while. Long enough to flash a custom rom on it or something.
has anyone have a firmware that can be flash through fastboot?
or anyway to do a complete wipe and reinstall the whole software?
I can't believe there is no root method for this phone yet. My 8 year old loves his but it has mass bloatware.
Deleting Bloatware
Atlantisvip said:
I can't believe there is no root method for this phone yet. My 8 year old loves his but it has mass bloatware.
Click to expand...
Click to collapse
You can delete bloatware... Just use kingroot (no restart), use kingroot (open), has its own tool, image attach.
You must use it with caution and under your responsibility
Is a root temporary, just reset to disable root.
Ch0nGu1 said:
You can delete bloatware... Just use kingroot (no restart), use kingroot (open), has its own tool, image attach.
You must use it with caution and under your responsibility
Is a root temporary, just reset to disable root.
Click to expand...
Click to collapse
What version do you used?
zkar1011 said:
What version do you used?
Click to expand...
Click to collapse
4.3.5
Is there a debloated version of the ROM that you can flash? I'm guessing this phone is never getting a marshmallow update.