what up yall! My ATT tilt died a few weeks ago (flex cable went bad, decided it was time to move on) so i got a G1 from my buddy that had a broken digitizer and LCD. ordered the parts online and got it put back together today. few questions though.... it seems that about the bottom 1/4 inch of my touch screen dosent respond....its brand new and the rest of it works fin...just the small strip that seems to not work. any ideas? also t mobile are assholes...i cant get them to unlock it but i will work on that one...im quite sure that answer is on here. Also...do i really need to get a data package or can i choose to keep my phone from constantly connecting and updating my gmail and other apps? thats the reason i continue to get HTC is because i think data plans are silly when everywhere in america has WiFI....i think thats all for now...and ive been a member on here for quite sometime but this android mess is totally different. lol. thank yall!
That 1/4" at the bottoms sounds like a bad digitizer. =/ *Most* likely not software. But you can check by flashing a new ROM and if its a software problem, the new ROM will override whatever was causing it not to work before.
You can get it unlocked for $20 from one of many unlocking websites, just google it. You can't get it free anywhere other than T-Mobile sorry to say.
You don't *need* a data package, I don't have one. There are applications that can disable your data connection except for when you need it (i.e. MMS). Or its a built-in widget with the Hero ROMs.
Unless you have a rooted ROM, you will be required to use your data to even use your phone for the first time as it requires you to sign in to your Google account, but doesn't give you the option to use WiFi. But honestly, I think this phone is crippled without a data connection even if you don't use it all the time, I'm currently waiting for my current plan to end to sign another 2-year contract with data. But its up to you, its certainly still usable with enough WiFi connection points.
darn....its not very fun to take apart...plus i have to wait even longer...im currently using an old school , non color green screen nokia probably digitizer and not some random flex cable along the lines? maybe the black one? i guess there wouldnt be any way to check without replacing. and im not real addicted to any apps or anything, just mainly want it as phone/organizer. im a studennt and have wi fi at the house and at school, and every bar i go to has wi fi so i think im covered =) just making sure i could regulate it so it dosent pull and jack my bill up. if i were to flash a new rom, wouldnt that unlock it....and can you still downgrade it to rc29 when you dont have a t mobile sim card....or rather is there any other way besides adp or should i just go ahead and learn how to use it...seems a bit intimidating to anything ive done on a WMo phone.
you can use apndroid to block data from being used accidentally
flashing a rom will not unlock the phone.
Yes you can downgrade to RC29 without a tmo card
mmmk. so rooting and flashing a HTC rom wouldnt do it? if im correct i either have to go through t-mobile or i have to pay like 20 bucks so i can use it with ATT?
ztch10 said:
mmmk. so rooting and flashing a HTC rom wouldnt do it? if im correct i either have to go through t-mobile or i have to pay like 20 bucks so i can use it with ATT?
Click to expand...
Click to collapse
You are correct.
h.nocturna said:
Unless you have a rooted ROM, you will be required to use your data to even use your phone for the first time as it requires you to sign in to your Google account, but doesn't give you the option to use WiFi.
Click to expand...
Click to collapse
I haven't tried it myself, but this thread tells you how to get around that.
note how that thread tells you to obtain root...
B-man007 said:
note how that thread tells you to obtain root...
Click to expand...
Click to collapse
I meant get around not having a Data connection. Rooting is obviously not optional.
Chahk said:
I meant get around not having a Data connection. Rooting is obviously not optional.
Click to expand...
Click to collapse
ah ok i figured he already found that or would.
sorry
You can root without data. Just activate wifi at RC29 when trying to sign in
Chahk said:
I meant get around not having a Data connection. Rooting is obviously not optional.
Click to expand...
Click to collapse
Rooted ROMs usually have an option to just skip signing into Google don't they? I know they have that for Hero for sure, but I was pretty sure they implemented that to all the cupcake/Donut ROMs too no?
Basically, you'll only need to use that with RC29. And if you do need to sign in and don't wanna use the work around, I would just go ahead and use the data, its only a few KB of info I think (I've never actually measured it, but I very small amounts on my bill even if I do use it to sign in, also using ATT btw).
h.nocturna said:
Rooted ROMs usually have an option to just skip signing into Google don't they? I know they have that for Hero for sure, but I was pretty sure they implemented that to all the cupcake/Donut ROMs too no?
Basically, you'll only need to use that with RC29. And if you do need to sign in and don't wanna use the work around, I would just go ahead and use the data, its only a few KB of info I think (I've never actually measured it, but I very small amounts on my bill even if I do use it to sign in, also using ATT btw).
Click to expand...
Click to collapse
all ROM's based on adp (and most modded tmo) have the option to skip (at least im pretty sure)
He just wants to activate his phone without data, which would require him to get down to a root level rom (RC29)
after he logs in, he has the option to root or wait for the OTA update if he wants to stay stock
if he wants to try to use his data, he can try but it doesnt always work (it did for me at first, but not the next few times)
ok so update... believe it was a bad digitizer...sending it back monday for a replacement so a few more days without the new toy) I got it registered to my Gmail and everything, and im currently waiting on my unlock code, so that is squared away. now...new questions.....
1. can i not just uncheck the auto sync and all the other data options or do i have to run adp? to make sure it dosent stay connecting and updating my mail and apps?
2. what positives do i have with rooting/flashing? obviously most of you probably have gone that route, and i really enjoyed flashing with my Tilt and having the newest WinMo, but it was always at the cost of it either being buggy or somethings not working. i know this can be searched but i want the simple answer if yall dont mind
3. i also noticed that the only thing so far that dosent work, is the camera/camcorder. keep in mind i got this phone with a broken lcd/digi. so there may have been other problems but i couldnt tell untill the screen was replaced. could it be i put it back together and missed a cable/contact for the camera, or could it just be software related?
...for now i think thats all the problems i have stumbled across... Thanks you all you are making this very easy for a Android Newbie!
ztch10 said:
ok so update... believe it was a bad digitizer...sending it back monday for a replacement so a few more days without the new toy) I got it registered to my Gmail and everything, and im currently waiting on my unlock code, so that is squared away. now...new questions.....
1. can i not just uncheck the auto sync and all the other data options or do i have to run adp? to make sure it dosent stay connecting and updating my mail and apps?
2. what positives do i have with rooting/flashing? obviously most of you probably have gone that route, and i really enjoyed flashing with my Tilt and having the newest WinMo, but it was always at the cost of it either being buggy or somethings not working. i know this can be searched but i want the simple answer if yall dont mind
3. i also noticed that the only thing so far that dosent work, is the camera/camcorder. keep in mind i got this phone with a broken lcd/digi. so there may have been other problems but i couldnt tell untill the screen was replaced. could it be i put it back together and missed a cable/contact for the camera, or could it just be software related?
...for now i think thats all the problems i have stumbled across... Thanks you all you are making this very easy for a Android Newbie!
Click to expand...
Click to collapse
1. That would stop just contacts, calendar, and gmail not all of the other apps that come with the phone
2. Rooting is definitely worth it, loving my hero rom
3. If your on RC29 there is no camcorder, but if not then it's definitely a hardware issue, when I was on stock everything worked fine
Just FYI: the unlock code is phone specific, so if your getting a replacement, the unlock code wont work on that one if the code you got was for the other.
1) If you want to disable data, download and run APNDroid. You can turn off autosync if you want but data will still be used.
2) Rooting has lots of advantages. Themes, faster updates (i.e youll get the latest android before its released OTA) more modifications, use of certain apps such as Ad-Free, etc. cooked android roms are more stable than winmo cooked roms, and you have the option between stable/experimental
3) if it was stock, its probably a hardware error
so could i potenitally not have any apps and not have a data pull problem? or it seems as though just rooting and flashing to hero (would you all go hero, or newer 1.6 stock rom, or custom 1.6?) and ill be taking it back apart to send the bad digitzer back, so ill check the ol camera out. still is stock T-mobile 1.5....no rc29 or anything....yet...
if you still have 1.5, you can use the 1 click root
im using hero right now, but i switch between hero and cyan using the switchrom script
the g1 on stock android will still use data even if you have everything disabled. the only way to completely disable it is by changing the apns, or by disabling mobile data on a hero rom
what was wrong with the camera? give a little more detail so we know if it really is a hardware or software problem
Quiccest way to get unlock code..just tellem you are goin to the uk or sum and you are in need of unlocking since u will be on there network for a while.. Usually that works!
Hello everyone sorry if I am posting this when there is an answer somewhere already on the forums. I have searched multiple times with no straight forward answer but that doesn't mean there isn't an answer that I overlooked.
I am new to the forum as well as Android. I recently purchased a Samsung Captivate through AT&T. I have been reading up on rooting the device and majorly concidering it to get the AT&T Bloatware off. Of the many, many, sites I have read on up I found One Click Root for Samsung Captivate through this forum, which hopefully will work properly, I do not see why it wouldn't.
This brings me to my first question, if I root my device, install Titanium Backup and uninstall the bloatware, can I then uninstall Titanium Backup and unroot my device? Or must I leave Titanium Backup installed for the "Backup" purposes?
My second question is if I root my device and uninstall bloatware ONLY, will I receive and be able to download OTA updates that become avaliable? ( I am aware I will lose root if installed, just currious as to if it will even let me update. )
My only reason for rooting is to get rid of the bloatware, I am hoping I can remove the bloatware and then unroot because I do not have any use for being rooted once they are removed.
I do not plan on flashing any custom ROM, I am leaving the stock ROM just removing the applications and touching nothing else. I know I have read that if I change from the ROM I will not be able to receive OTAUs...
Any thoughts on this?
Thanks in advance for the help. I am very good with computers and a certified ARES tech, know HTML. Just trying to grasp this whole Android thing comming from a iPhone (SO FAR SO GOOD) ... I don't think I'm too lost... yet.
If all you want to do is get rid of the bloatware, download LauncherPro and hide the icons. Much easier and the phone is much better with LP.
One Click Root works great. I've used it many times without issue.
I have used Titanium Backup to remove unwanted apps. Personally I leave it installed, and use to it to backup all of my apps, and save them to my External SD.
Personally I would leave the root in place, and also consider Sideloading it. It'll allow you to install "unapproved" apps.
I do not know how this might affect your ability to receive OTA. I think I remember hearing something around the time of the JH7 OTA release. I did some looking around and couldn't find it
Thanks for the help. I decided to put my worry aside as far as OTA updates go and go ahead and root the phone and remove bloatware.
I used one click root (which worked perfect) to root the device, downloaded Titanium Backup, and removed all the AT&T junk, and a couple things from Samsung I had no use for. Acually I kinda took my phones life in my own hands and uninstalled more than the lists I have found said to, but I figured if worst come to worst and it bricked I could just return it to Wal-Mart's AT&T kiosk since I was still on my thirty day guarantee. (No ma'am, I have NO IDEA what happened. )
Anyways the phone functioned fine so apparently I didn't do anything I shouldn't have. I only ran in to one problem and that was when I unrooted using the One Click (wanted to try it and see if it worked as good as the root) my phone came back on and was doing crazy stuff... locking out of nowhere, slow, didn't have the notification bar, nor any network connectivity after many reboots. Still in the same mindset that I could just make a trip to Wal-Mart, I did a factory reset. Phone came up and everything is perfect, bloatware is still gone and it took away my root apps which I was probubly going to end up doing anyways.
From what I finally found after a couple hours searching online is that theres a chance I won't be able to OTA update, however I shouldn't have a problem using Kies Mini to update instead of the OTA. Apparently AT&T's servers are getting overwelmed and people are having connection problems... even non rooted users.
We will see I guess when Froyo is (finally) released on AT&T.
Thanks again for the help!
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
I think it's all about what you do with a rooted phone that either makes it a full time job or not just to keep it up and running smooth. Me for instance could really care less about custom roms and what not. I like root just for removing bloatware to make the phone and battery better. And in the case of the AT&T s5 the ability to change my default storage to the external sd card. Once that is done I tweak with it for a week or so finding the best performance settings and enabling tether and then I just leave it alone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I rooted and installed xposed/wanam and no problems whatsoever.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
No issues here, I was happy to root and remove the att and samsung bloatware.
I am also not a fan of touchwiz and that will take a while before we have an unlocked boot loader and are able to load custom roms..
To each their own it is no more of a pain in the ass to run a rooted phone vs a non rooted phone. Im at a loss as to why you think it was that much trouble?
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
I understand where you are coming from, I enjoy root for the ability to use Tibu and remove bloat. I also was like you I had a granfathered plan since 1997, the BellSouth mobility day's. I just recently changed to the Mobile data share plan, after analyzing my data usage for the last couple of years I realized my data was under 12 gigs a month for the whole family. I signed up for the 15 gig data share plan have saved $ 40 dollars or more per month. Just a heads up you may want to look into it. Oh and as for tethering it is included in the mobile data share plan.
I assure you that Xposed and Wanam definitely interfere with some of the phone's processes. In fact, there's a whole thread here that describes the steps you have to take to remove the lag on your phone and allow you to use S Health (which I do). But then, other things get screwy, because the ro.securestorage.support property is set to true because other processes rely on it, so now I have a whole slew of other issues that arise from it.
I can tell you from the outset, all I did was root, install xposed, install wanam, and installed the ISIS Root Bypass module, and then all these issues came from that. I just felt it wasn't worth it, and I can easily freeze/disable/turn off the bloatware so I don't have issues with that, per se.
--Q
The stuff I really wanted root for doesn't cause any ongoing weirdness. I was getting along ok without root but I am a LOT happier now:
- permanently disable the annoying, super-loud boot sound without having to resort to workarounds
- disable the tether provisioning check (my plan includes tethering, but on more than one occasion the provisioning check failed and told me to try later)
- full use of BBS and Greenify to monitor/tame battery suckers
- TiBu for freezing (I don't attempt to delete the bloatware) and backups too
- sdfix to gain full access to my sd card
To me, all of that stuff with the exception of the tether provisioning check really should be possible for everyone if they want it. And the tether check could at least reasonably cache your status.
xposed modules are probably the biggest culprit in rooted-user problems (even more than people deleting stuff they shouldn't), and while I love a lot of the customizations xposed allows (a big one for me was being able to show the setting in the messaging app that says not to turn on the screen when a message comes in - no more pocket-crap for me!), I could live without that. The one xposed module I would say I might miss is Xprivacy. I'm relatively conservative in what I block, but it is amazing the info our apps can have access to.
jdock said:
The stuff I really wanted root for doesn't cause any ongoing weirdness. I was getting along ok without root but I am a LOT happier now:
- permanently disable the annoying, super-loud boot sound without having to resort to workarounds
- disable the tether provisioning check (my plan includes tethering, but on more than one occasion the provisioning check failed and told me to try later)
- full use of BBS and Greenify to monitor/tame battery suckers
- TiBu for freezing (I don't attempt to delete the bloatware) and backups too
- sdfix to gain full access to my sd card
To me, all of that stuff with the exception of the tether provisioning check really should be possible for everyone if they want it. And the tether check could at least reasonably cache your status.
xposed modules are probably the biggest culprit in rooted-user problems (even more than people deleting stuff they shouldn't), and while I love a lot of the customizations xposed allows (a big one for me was being able to show the setting in the messaging app that says not to turn on the screen when a message comes in - no more pocket-crap for me!), I could live without that. The one xposed module I would say I might miss is Xprivacy. I'm relatively conservative in what I block, but it is amazing the info our apps can have access to.
Click to expand...
Click to collapse
Hmm....perhaps I'll revisit rooting again....and keep off of xposed....I too miss xprivacy - keep it nice and updated on my Xoom and S4
Would not mind just using root for tethering, tibu and sdfix.....Do you have links to the tethering and sdfix solution you used? I guess the real litmus test here is if my car's bluetooth doesn't get all EFFED up on the phonebook. The weirdest thing....after I rooted (even before xposed) I would activate voice recognition and say "Call Home" it would repeat back to me in confirmation "Call Home" in the lovely female robotic voice. Then proceed to dial someone completely different. VERY weird.
--Q
PS - I'm not a newb user here...been delving into the guts of phones back when I had the old school Windows Mobile devices
quordandis said:
Hmm....perhaps I'll revisit rooting again....and keep off of xposed....I too miss xprivacy - keep it nice and updated on my Xoom and S4
Would not mind just using root for tethering, tibu and sdfix.....Do you have links to the tethering and sdfix solution you used? I guess the real litmus test here is if my car's bluetooth doesn't get all EFFED up on the phonebook. The weirdest thing....after I rooted (even before xposed) I would activate voice recognition and say "Call Home" it would repeat back to me in confirmation "Call Home" in the lovely female robotic voice. Then proceed to dial someone completely different. VERY weird.
--Q
PS - I'm not a newb user here...been delving into the guts of phones back when I had the old school Windows Mobile devices
Click to expand...
Click to collapse
The only thing I did after I rooted my phone was to get rid of the boot sound and used sdfix to be able to use my sd card. But I was having random problems with some apps not working. I would have to uninstall the app and reinstall it to get it to work again. This was really annoying since I was on a trip and really needed to use the apps without all the bother. So I decided to install xposed to try to fix the problems I was having. That just made everything worse--more apps that I use a lot stopped working. After that I used Kies3 to get back to unrooted stock and reinstalled all my data from backup. I am using silent boot to get rid of the boot sound and adjusting to the way I have to use my sd card now. I plan to wait a while before I try root again.
This will be my first smart phone that I am using unrooted. But everything is working now and I have the most annoying things fixed without root.
Sticking with root. Agreed that it's what you do after root that messes things up. Sometimes when you have the power, you don't stop to think whether you should make changes. Unfortunately the phones are built now where many apps have their hands in others to make the user experience "better". The users in this instance are the general masses who just want a phone to work by statistics. It fails to acknowledge that some people think differently. Sometimes I pick up my sister's phone and wonder why she would have the launcher do what she did but that's her phone.
Would I un-root? That's a firm no good buddy. I appreciate everyone's input in making the rooting process less of a landmine but I would never give up the ability to do what I want at, the time that I want. The first thing I did was freeze att.update.software among other att software. (To the author of the post, att did a pretty good job in making everything work in it's first iteration). Then on to battery extending, greenify and wakelock detector. Finally I will delve into customizing my UI but like the author said, Touchwiz doesn't bother me that much, I just sped things up in the developer's option. Because I'm not a heavy phone user I am now getting about 3 days from my charge and still able to get my message updates albeit on my terms, not pushed to me. Also, not having to see ads anymore? Priceless.
And because of everyone else's efforts, I can still go into UPS in case of those times that I find I can't get access to a charger, which now a days, is not that often.
quordandis said:
Hmm....perhaps I'll revisit rooting again....and keep off of xposed....I too miss xprivacy - keep it nice and updated on my Xoom and S4
Would not mind just using root for tethering, tibu and sdfix.....Do you have links to the tethering and sdfix solution you used?
Click to expand...
Click to collapse
For the sd permissions I used this sdfix app from the play store. There are several and they just edit /system/etc/permissions/platform.xml for you, so you could do it manually too.
I have to admit, for the tether provisioning, right now I'm using the option in Wanam Xposed just because it was quick. Supposedly the X Tether module works too. A non-xposed method is here but I didn't try it since the xposed module worked. On my old phone it was as simple as using an sql editor to change the entitlement_check setting in /data/data/com.android.providers.settings/databases/settings.db - I don't see that in the GS5, but it may be that the default is 1 and just adding it with a value of 0 will work.
Another idea I hadn't tried (no need to) was the old standby wifi tether for root users app; it might not work as-is for the GS5 but it's just a frontend for a couple of scripts that might be fairly easy to get working since the basic idea is the same and not magic at all (load the wifi device modules, start the wpa_supplicant on it, start a dhcp server on it, setup routing/iptables, and off you go - none of that needs to check to see if you're allowed; the obvious downside is no fancy gui to start/configure/monitor it). On my old phone, I used this as a framework for my own script that brought wifi up simultaneously with mobile data - not operating as a hotspot, but connecting to my home wireless - and then I could run a socks proxy on my phone and use that from anything on my home network, wireless or wired.
The weirdest thing....after I rooted (even before xposed) I would activate voice recognition and say "Call Home" it would repeat back to me in confirmation "Call Home" in the lovely female robotic voice. Then proceed to dial someone completely different. VERY weird.
Click to expand...
Click to collapse
That is weird, and if the only thing you did was root, I can't see any reason for something like that to happen.
Edit: this thread has another method for disabling the provisioning check, which looks like a great way if you don't want to use xposed or modify framework.apk.
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
It takes time to learn what you can and can't tweak once you have "root", each device is different, each users needs are different. Where battery life and de-bloating may important to one it might very well be insignificant to another, Development is time consuming and with xPosed and the modules that go with it every time Google comes out with an updated OS or Samsung, HTC,LG or Motorola come out with a device it requires the devs to step back and re-evaluate the code and make appropriate adjustments for the best behavior, modifications for compatibility or in the worst case scenario a complete re-write. We all read (or should read) the disclaimers with every tweak or mod we do and as always if it doesnt work or causes bad behavior we can remove it.
I had small issues at first. Then I used Kies 3 to restore. Started over and immediately rooted. Installed Xposed and all 6 of my favorite Modules. Also did the Tool Kit (Dev Sec) Phone is flying fast and has great battery life. I have no issues at all.
I love root......(( I have the s 5 Active ))
I guess I'm a very conservative rooter. I don't freeze apps unless I know what they are, so there's some on the "safe to freeze" list that I still have enabled. After having CM running on my Galaxy S II Skyrocket for so long, I was really impressed with the S5. Really the only thing I missed was AdFree Android. However having CM made my Skyrocket last a lot longer than it would have on the stock ROM, I only upgraded because the hardware started getting wonky.
So after root, I've only installed AdFree, SDFix, and froze a few bloat apps that were persistently in the running apps list that I couldn't disable in stock form. Really helped with battery life too, I can't use phone much during the day due to my job, but battery life jumped from 75-80% at the end of the day to around 90% if I don't touch it (~85% if I check FB during lunch for a few minutes).
There's a few more tweaks that I would like, but seeing all the issues with Xposed, I'll either deal or figure out a manual change at some point. Maybe I'll research what the ro.securestorage.support module is, since disabling it is really why I haven't tried Xposed. (Yes, I wanted root access, but I don't want to make my phone any less secure than I have to.)
tl;dr If you like the phone is stock form, go easy on the modifications after getting root.
quordandis said:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).
So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).
Anyone else experience something similar? Have another reason for de-rooting? Curious.....
I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).
--Q
Click to expand...
Click to collapse
Wow, I completely 110% disagree with everything you have mentioned here, this has not at all be my experience at all but then again I'm tech savvy. If I were you I would be buying apple products. I for one of the opinion, if I cant root it, I don't want it and won't pay money for it. That goes for knox 0x1 bootloaders as well. Samsung won't see another dime from me again!
Sent from my iPad using Tapatalk
I'm rooted. I froze at&t's crap, chat on, hangouts, and google+.
freezing ANYTHING Samsung seems to create a huge mess on this device.
shortydoggg said:
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Spot on
Sent from my SM-G900T using Tapatalk
barondebxl said:
Spot on
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Apparently, not entirely true. Here's one for you:
Pre-root, the phone connects just fine via bluetooth to my car. Upon initial pairing, I get a request to allow reading of contact list, phone history and messages. I agree. Car syncs contacts and saves to internal car temp memory (this sync occurs each time the car is turned on and the BT connection is established). Activate voice recognition to "Call Home" - car confirms with audible prompt "Call Home. Say yes, no or correction" to which I would reply "Yes" and then the car would call the contact labeled as "Home" on my phone which it synced.
Now, run towelroot, reboots phone with JUST root (su binary). Phone loads up just fine. Car establishes bluetooth connection. Tell it to "Call Home" everything proceeds as expected. I confirm with "yes" and it proceeds to dial a completely different phone number even though the voice prompt confirmed that I indeed wanted to call "home."
Ok - so I unpair the car from the phone, and delete the phone profile from the car. Decide to start from scratch. Phone pairs with the car and I allow the syncing of contacts, etc as was the case pre-root. Attempt to "Call Home" again and the same weird phenomenon occurs where it will confirm it's calling home, then proceed to dial a completely different contact. Ok. I clear the phonebook and force it to resync the contacts. Same issue. Ok. Unpair car from phone, delete phone from car.
Reboot phone into stock recovery and wipe cache. Try pairing again and do the whole shebang. SAME FREAKING ISSUE WITH THE CONTACT SYCN. Meanwhile, ONLY rooted the phone with the added su binary. No other root-enabled apps installed or used. Haven't even USED su yet to do anything other than run "adb shell" and confirm su works. (didn't even install a root checker).
I decide to UNROOT by installing supersu then using it to unroot. Reboot, unroot successful, no su binary, and remove supersu. Pair phone and car again, go through the steps and lo' and behold! CONTACT SYNC WORKED AND CAR DIALS APPROPRIATE CONTACT.
So, in reference to
shortydoggg said:
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
- that's probably true in most cases, just not in this one. I'm not saying it's the root per se, but certainly something about the su binary or how the phone gets rooted through the exploit or something definitely screws something up.......
quordandis said:
Apparently, not entirely true. Here's one for you:
Pre-root, the phone connects just fine via bluetooth to my car. Upon initial pairing, I get a request to allow reading of contact list, phone history and messages. I agree. Car syncs contacts and saves to internal car temp memory (this sync occurs each time the car is turned on and the BT connection is established). Activate voice recognition to "Call Home" - car confirms with audible prompt "Call Home. Say yes, no or correction" to which I would reply "Yes" and then the car would call the contact labeled as "Home" on my phone which it synced.
Now, run towelroot, reboots phone with JUST root (su binary). Phone loads up just fine. Car establishes bluetooth connection. Tell it to "Call Home" everything proceeds as expected. I confirm with "yes" and it proceeds to dial a completely different phone number even though the voice prompt confirmed that I indeed wanted to call "home."
Ok - so I unpair the car from the phone, and delete the phone profile from the car. Decide to start from scratch. Phone pairs with the car and I allow the syncing of contacts, etc as was the case pre-root. Attempt to "Call Home" again and the same weird phenomenon occurs where it will confirm it's calling home, then proceed to dial a completely different contact. Ok. I clear the phonebook and force it to resync the contacts. Same issue. Ok. Unpair car from phone, delete phone from car.
Reboot phone into stock recovery and wipe cache. Try pairing again and do the whole shebang. SAME FREAKING ISSUE WITH THE CONTACT SYCN. Meanwhile, ONLY rooted the phone with the added su binary. No other root-enabled apps installed or used. Haven't even USED su yet to do anything other than run "adb shell" and confirm su works. (didn't even install a root checker).
I decide to UNROOT by installing supersu then using it to unroot. Reboot, unroot successful, no su binary, and remove supersu. Pair phone and car again, go through the steps and lo' and behold! CONTACT SYNC WORKED AND CAR DIALS APPROPRIATE CONTACT.
So, in reference to - that's probably true in most cases, just not in this one. I'm not saying it's the root per se, but certainly something about the su binary or how the phone gets rooted through the exploit or something definitely screws something up.......
Click to expand...
Click to collapse
]
Dunno whats wrong with your setup, but my rooted phone works fine in my wife's Ford and my Subaru.
Hi there, I recently purchased an t710 which I upgraded to 5.1.1. I'm wondering if there is any reason to wait rooting this device and tripping knox. I purchased an extended warranty for accidental etc from squaretrade so I'm not too worried.
What do you think? Also this is the first touch device I ever owned and I've never owned any smart devices other than a blackberry curve 8330. :victory: I am however quite savvy with computers in general. I've strayed from these devices due to high cost and high toss rate.
Couldn't hurt to throw in some app recommendations too! I sure would like to customize a bit more than samsung is allowing me to.
In addition to my original question, what's the best root and image available for my galaxy tab s2 t710 currently? I wasn't quite sure as there are a few. Does flashing one of the images wipe everything?
Also, as I understand it, many knox features have to be paid for with a regular subscription or something and the applications are not fantastic currently. Am I wrong?
Feel free to add anything you think I should know, also app recommendations would be great. Thanks!
Well, I took the plunge anyway, but I didn't do a backup with TWRP, everything is working but I forgot. Besides knox status, I'm assuming there's a way to undo this correct? like factory reset? Or did I screw it up (If I need to that is.)
wirelesskebab said:
Well, I took the plunge anyway, but I didn't do a backup with TWRP, everything is working but I forgot. Besides knox status, I'm assuming there's a way to undo this correct? like factory reset? Or did I screw it up (If I need to that is.)
Click to expand...
Click to collapse
Knox status doesn't totally matter its more for secure environments like corporate or government to know that a device has been compromised.
Samsung and carriers often still warranty devices that have the Knox flag tripped.
To answer your question though, there is no way to undo a Knox flag.
Hey, I said besides knox status lol. I meant since I didn't backup in twrp before flashing root is there still a way to restore default firmware if necessary? Also how do I disable the securitylogger? People have mentioned it on the forums but I can't seem to find how to do that, thanks.
The only adverse effect I have noted so far was having to re-enter my wifi password.
Can anyone recommend a decent busybox? I installed this one https://play.google.com/store/apps/details?id=stericson.busybox&hl=en but is it the best one truly? The only other root program I have installed is AdAway. Actually, any decent app recommendations would be great, thanks!
wirelesskebab said:
Hey, I said besides knox status lol. I meant since I didn't backup in twrp before flashing root is there still a way to restore default firmware if necessary? Also how do I disable the securitylogger? People have mentioned it on the forums but I can't seem to find how to do that, thanks.
The only adverse effect I have noted so far was having to re-enter my wifi password.
Can anyone recommend a decent busybox? I installed this one https://play.google.com/store/apps/details?id=stericson.busybox&hl=en but is it the best one truly? The only other root program I have installed is AdAway. Actually, any decent app recommendations would be great, thanks!
Click to expand...
Click to collapse
For what reason do you need to install busybox? Unless you have a real need for it why install it and cause more issues?
I can't think of a real single time I've ever needed busy box.
Xposed, Root explorer and Titanium backup are the 3 apps I use on every device I have.
auto rotate suddenly stopped working after I rebooted the tablet, I tried doing a factory reset but that hasn't fixed it, it won't go into landscape mode. Any ideas to fix this?
I just rebooted it through TWRP instead of inside the system and that fixed it, why the heck wouldn't a factory reset? anyone ever hear of this issue before?
A slap on the back has been known to fix it.