I just got the 8.4 Tab Pro, and I had forgotten how much I hate TW. So here is an odd question for all of you...
Theoretically, could I flash CM11 or Slimkat on this, and then UNROOT? My employer doesn't allow rooted devices to connect to their Exchange servers (enforced by a 3rd party MDM application). If this was possible, would you be "stuck" on that ROM?
I am actually thinking I might be better off going to a 2013 N7 instead for the unmodified android experience...
spiff72 said:
I just got the 8.4 Tab Pro, and I had forgotten how much I hate TW. So here is an odd question for all of you...
Theoretically, could I flash CM11 or Slimkat on this, and then UNROOT? My employer doesn't allow rooted devices to connect to their Exchange servers (enforced by a 3rd party MDM application). If this was possible, would you be "stuck" on that ROM?
I am actually thinking I might be better off going to a 2013 N7 instead for the unmodified android experience...
Click to expand...
Click to collapse
Personally, I just stopped reading email on my personal device when my employer enforced root (either I had to stop doing android development on it or give up email, an easy choice...).
It can be hard to convince the mdm software that your device is okay. Depending on the mdm application, it may be doing something simple like checking to see if "su" works or it could be looking for busybox or almost anything else. Figuring out what triggers it can be a pain. If you want to tinker then there is a good chance that you can make the mdm software happy but it's not even guaranteed.
Thanks for the reply...
That is an option too. I already have a phone that I am keeping stock and unrooted so I could skip the email on the tablet. The whole rooting and ROMing experience just seems like a hassle on the Samsung devices with their Knox software now.
Sent from my SM-T320 using Tapatalk
spiff72 said:
Thanks for the reply...
That is an option too. I already have a phone that I am keeping stock and unrooted so I could skip the email on the tablet. The whole rooting and ROMing experience just seems like a hassle on the Samsung devices with their Knox software now.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Knox only does two things. First, it leaves a permanent marker to say that you voided your warranty (which, IMO, you have by flashing custom software). Second, it forever stops you from using Knox secured Samsung software (which it has to because after flashing something you may have violated that security).
Otherwise, it is wide open. Just be sure you don't want to return it before you start flashing...
Related
Hello- I've been reading around this site and I am not sure if what I've found is accurate, I could use the help of those that are informed.
I'm new to Android having only gotten my first incredible yesterday. I tried using unrevoked (v. 3.21 to the best of my knowledge) on windows after installing the appropriate drivers and was unsuccessful two or three times. It would hang at waiting for root or 'we can't get root,' were the two messages I'd receive.
I reset to factory from the bootloader and tried this again on my Mac machine- this was different but still unsuccessful. It would still say 'waiting for root,' however the phone itself was stuck powered on with nothing on the screen. It took me unplugging the mini USB and removing the battery to finally get it to power back on and show something on the screen.
With that said, is there an update from Verizon that causes unrevoked to no longer work? I read that somewhere but am unsure how recent the information is.
Secondly- what I really want to do is enable the Wifi Hotspot feature without having to fork MORE money over to Verizon- am I going down the right path to enable this?
Lastly- can someone please provide a good thread I can read up on regarding handling future updates for Android OS- I assume OTA updates are disabled once rooted, how do I continue to make sure my OS is up to date when this is disabled?
Thanks in advance for your help!
satyr2k2 said:
Hello- I've been reading around this site and I am not sure if what I've found is accurate, I could use the help of those that are informed.
I'm new to Android having only gotten my first incredible yesterday. I tried using unrevoked (v. 3.21 to the best of my knowledge) on windows after installing the appropriate drivers and was unsuccessful two or three times. It would hang at waiting for root or 'we can't get root,' were the two messages I'd receive.
I reset to factory from the bootloader and tried this again on my Mac machine- this was different but still unsuccessful. It would still say 'waiting for root,' however the phone itself was stuck powered on with nothing on the screen. It took me unplugging the mini USB and removing the battery to finally get it to power back on and show something on the screen.
With that said, is there an update from Verizon that causes unrevoked to no longer work? I read that somewhere but am unsure how recent the information is.
Secondly- what I really want to do is enable the Wifi Hotspot feature without having to fork MORE money over to Verizon- am I going down the right path to enable this?
Lastly- can someone please provide a good thread I can read up on regarding handling future updates for Android OS- I assume OTA updates are disabled once rooted, how do I continue to make sure my OS is up to date when this is disabled?
Thanks in advance for your help!
Click to expand...
Click to collapse
You most likely have the latest OTA update, which patches the exploit that UnrEVOked 3.21 used to get root. They are currently working on a new exploit for the recent OTA update now.
If you want free wifi tethering, you don't exactly need to root. This'll do the trick: http://www.tweak3d.net/forums/showthread.php?54386-Android-OS-htc-incredible-free-wifi-tethering
Usually the OTA's get incorporated into later ROM releases, so all you'll have to do is download and install the new release for your custom ROM.
If you prefer to have a stock, but rooted ROM, you can download the rooted stock ROMs that usually come out after OTA updates.
Or, usually, there are leaked updates released before the official update comes out. Those are also rooted and usually posted here as well, if you want early release things.
I hope I helped you out, need anything else cleared up?
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Blah12543 said:
If you want free wifi tethering, you don't exactly need to root. This'll do the trick: http://www.tweak3d.net/forums/showthread.php?54386-Android-OS-htc-incredible-free-wifi-tethering
Click to expand...
Click to collapse
Woah. I've been searching these forums for two weeks looking for this, and thought that my only choice is to root the dang phone. Does this not alert VZW about the usage, or can they only tell how much data is being used?
I just tested this with the "wifi hotspot" app that's on the (unrooted) Incredible, and holy crap it worked! If this works out then I've just solved my only major gripe with having the Incredible on Verizon!
If you want free wifi tethering, you don't exactly need to root. This'll do the trick:
Click to expand...
Click to collapse
I agree- this works wonderfully just with the default preloaded Mobile Hotspot app.
I am wondering if there is still any reason for me to unlock the phone.
GreNME said:
Woah. I've been searching these forums for two weeks looking for this, and thought that my only choice is to root the dang phone. Does this not alert VZW about the usage, or can they only tell how much data is being used?
I just tested this with the "wifi hotspot" app that's on the (unrooted) Incredible, and holy crap it worked! If this works out then I've just solved my only major gripe with having the Incredible on Verizon!
Click to expand...
Click to collapse
By changing the dun nai, its supposed to disable the "tell VZW I'm using this app" thing. I'm not sure about this one, but I think they can still see you're using data, just not that its from the hotspot app. Just know, if they can somehow track/tell you're using it and you get caught, I'm not to be held liable lol. Blame the guy who made the post I showed you lol. Just a little disclaimer, just in case.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
satyr2k2 said:
I agree- this works wonderfully just with the default preloaded Mobile Hotspot app.
I am wondering if there is still any reason for me to unlock the phone.
Click to expand...
Click to collapse
ROMs/kernels/tweaks/mods.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Blah12543 said:
ROMs/kernels/tweaks/mods.
Click to expand...
Click to collapse
Sure. What I mean is- I originally wanted to root it only to enable the functionality of the Wifi Hotspot. What functionality can I add by rooting my phone in addition to this?
I don't really see the advantage of having to update my ROM manually any time there is an Android OS update- what's the value?
satyr2k2 said:
Sure. What I mean is- I originally wanted to root it only to enable the functionality of the Wifi Hotspot. What functionality can I add by rooting my phone in addition to this?
I don't really see the advantage of having to update my ROM manually any time there is an Android OS update- what's the value?
Click to expand...
Click to collapse
SetCPU was a big selling point in my eyes back when I first rooted. You can underclock the processor while the screen is off to help save battery. But, that kind of stuff is built into some kernels now (Kings BFS6, for example). But, if you want your phone to run a bit faster and smoother, you can overclock. I also like running different ROMs with themes and stuff. The customization is pretty neat imo. Like on this ROM: I have a few (6) quick settings I can change in the notifications bar. Just little conveniences like that win me over lol. And, there are leaked versions of official releases incorporated in to ROMs earlier than they're rolled out. I was running Froyo back in late July lol. Applying different ROMs/updates to the ROMs isn't hard or inconvenient at all... Only when your battery is low does it suck lol. If you wanna remove bloatware, no problem. And, if you ever mess up somewhere, you can usually apply a Nandroid backup you previously made and be good to go.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Haha yeah, I won't be blaming anyone but myself if VZ comes after me. It's still nice to try out. I'm posting this now from my Samsung Tab using the tethered WiFi. Connection looks good!
GreNME said:
Haha yeah, I won't be blaming anyone but myself if VZ comes after me. It's still nice to try out. I'm posting this now from my Samsung Tab using the tethered WiFi. Connection looks good!
Click to expand...
Click to collapse
Sweet glad I could help
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
So I'm a first time Android user, just picked up the Verizon LTE Galaxy Nexus. Rooted it with the r3 superboot image. Mainly I just want root access so I can enable tethering, I don't really plan on doing much else with it. After rooting, does that mean I can no longer receive OTA updates? And if so, how would I update Android from here?
Thanks everyone!
Also I should note that other than running a web server, I'm relatively new with linux console as well.
3thereal said:
So I'm a first time Android user, just picked up the Verizon LTE Galaxy Nexus. Rooted it with the r3 superboot image. Mainly I just want root access so I can enable tethering, I don't really plan on doing much else with it. After rooting, does that mean I can no longer receive OTA updates? And if so, how would I update Android from here?
Thanks everyone!
Click to expand...
Click to collapse
you will receive. And it should update just fine, if you didnt change anything in system.
Awesome, thanks.
Also, in case anyone finds this, a lot of tethering apps weren't working for me. Couldn't start ad-hoc and create an SSID. The free one that I found that did work right away was Tethering Widget.
offenberg said:
you will receive. And it should update just fine, if you didnt change anything in system.
Click to expand...
Click to collapse
OTAs will either not install, or will install but remove your root. If you want to preserve your system and not chance anything just wait a few for the update packages to come out and flash them manually.
As far as tethering, I'd take it easy for a little while. Just rooting and installing a 3rd party app doesn't instantly let you tether the Verizon version. They still have their own tracking software thats going to block/ask you to pay for it. You're best off waiting for people to figure out what files need to be removed to make sure VZW isn't watching your tethering activity.
Awesome thanks for the heads up. As long as i can avoid having to reroot and set up all my personalization, then that would be great. So these update packages, do i install them the same way by booting into bootloader mode and installing it with fastboot?
And i think my last question will be is where is a good spot for me to pay attention to in order to find out when evdnts like these discoveries on tethering happen and the updates released?
Again thanks for being so helpful and covering my ass This is a pretty cool community
Is there a way to stop updates if you're rooted?
Literally every time i check for software updates i get
"Communication failed"
The server is currently unavailable.
Your device will automatically check for an update within the next 48 hours.
Then if i check again it says device is up to date, you can check for updates again in XXhours. If i go into application manager -> AT&T Software Update and clear data, i can check for updates again but i get the same communication failed. I also tried clearing data and rebooting phone, and it still wont check.
And i can't get Samsung Kies running on my windows 7 pc for some reason, so i can't get updates from there either.
Is anyone else on AT&T experiencing these problems? Any fix for this? I really want that update that adds brightness control to the notification menu.
jefferson9 said:
I really want that update that adds brightness control to the notification menu.
Click to expand...
Click to collapse
I did not update, but hearing that update would disable local search, add new modem. Nothing about Brightness control
There is no brightness control on ATT update. I was having the same problem you were and exchanged the phone. There is no fix as far as I know for the error you are getting. It is a common issue. Search the annoyances (bugs) thread.
I don't know if the OTA update resolves your issue because they day after I exchanged mine the update came out.
Sent from my SAMSUNG-SGH-I717 using xda premium
I also haven't been able to get the OTA update. I assumed it was because I rooted and the device is listed as 'modified'. Is the update worth it?
It is in my opinion, and my usage habbits, for the WiFi stability increase that is gained.
Universal search is stripped (searches conducted on phone do not include on device results, ie contacts).
In other words, if you use the Google search by long pressing your menu button the results from your search will only be pulled from the internet.
I rarely use the search built in, so it hardly mattered to me.
Check out the developer forum for ways around the universal strip if you are rooted and want to update.
Sent from my SAMSUNG-SGH-I747 using xda premium
Well i reseated the SIM card, and removed the little blue tape from the sd slot and the SIM slot, rebooted and still not working.
I wanted to avoid rooting, since the stock software runs so smoothly and i liked being on the latest at&t software. I guess since i can't get OTA updates now theres no reason not to root.
Will this issue be fixed eventually? Or would i be better off exchanging phones while i can?
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
the1stSecond said:
I'd exchange it. If you have faulty hardware then rooting won't do anything for you.
Peace of mind, if anything, that if you decide to root your phone is functioning as it should from the start.
Others will argue it's software issues.
But, whatever the cause, none of us paid to have a 90% functioning phone from the factory. Go get what you paid for is my take on it.
Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Well speaking as a software engineer, i'm almost certain its a software issue, most likely with at&t's software update app, or on their servers. Mabey reinstalling the at&t software update application will help?
It sounds reasonable to me. Maybe try the method for No trip flash counter in devoplment? You would be upgrading to the newest firmware and have root and not trip the flash counter. You would still be able to check for ota updates (although should just return the status of your software is up to date since it is a totally stock ROM just with root injected). I imagine that would reinstall the software update service. Although with your knowledge you are way over my head. And whether or not when updating ROMs if that application is reinstalled is something I can't answer.
Maybe just try this first:
Settings> Application Manager> All> AT&T Software Update> Clear Data> Confirm
Power off Phone
Remove battery for at least thirty seconds.
Reinstall battery and power on device.
Try again after device boots up.
Sent from my SAMSUNG-SGH-I747 using xda premium
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
k3y0n4 said:
I've been having this same problem
I was thinking that its because of AT&T's controlled release of the OTA.
Its been so long since the release, that I can't imagine that's still true. I also agree that its probably a software thing. I have a number of the bloat apps disabled and also wonder if one or more of those would interfere with such a thing.
I'd love to hear about a resolution.
Click to expand...
Click to collapse
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So, if it's a software issue why is it two identical devices running the same software from the factory yield different results? I.e. my first device would do exactly as your original post outlines, then my replacement device had no issue checking for updates (same stock software, same device form factor).
If you search there are a lot of examples of complaints of this exact issue.
I am also very interested in this because even though there are many complaints out there, the only answers seem to be;
1) who cares this is xda and we update through Odin/cwm etc...
2) replace it.
Good luck, I hope you guys find an answer.
Sent from my SAMSUNG-SGH-I747 using xda premium
jefferson9 said:
That's an interesting theory, I've disabled some boatware too. Have you tried enabling them? I'm going to try that now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
k3y0n4 said:
I haven't tried enabling everything. I've tried enabling 'Samsung Push' which seemed like the likely starting point. I've been trying to do some debug on some battery drain things, so I've been hesitant to change too much at once. Also, I can basically only check every 24 hours so its slow going.
As far as the hardware issue, it just doesn't make too much sense that a hardware issue would be causing a problem because the software update would presumably be using the same hardware as the rest of the working smartphone functions. I think the explanation to one device updating and one not is more likely a server device id filtering or a user changing more than 'just the new hardware'.
Its neither here nor there though. Everyone will have there hair brained theories. Why don't we start asking what features will be on the next iphone. Seriously though, apple has to add a removable battery right? (I'm just kidding, please don't spam a million responses about how that will or will not ever happen.)
Click to expand...
Click to collapse
You can bypass the wait time between checks by going into application managment -> at&t software update and clearing data. Then you can try to update again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I've had similar issues checking for updates. i gave up and pulled the first update with the USALG1 rom posted in the development forum sticky. I too have several apps disabled (actually moved out of the system/app dir) and was wondering if that possibly caused issues. I never did try updating through kies though.
My kies wont even run on my windows 7 64 bit. There seems to be alot of people having problems with kies on win7 64 bit, nothing from samsung either. So theres really no way for me to get updates
This is How I Got My Phone to Update
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
AndroidLonghorn said:
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I force closed all the update apps, cleared all their data, and it worked as soon as I hit update. If force closing and clearing the data from the att and samsung update apps doesn't help, There may be nothing else you can do except take it in to an att shop.
Click to expand...
Click to collapse
When you got it to work, exactly what apps did you force close and clear data? Just AT&T software update? Any others?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I force closed the At&T Software Update app and I think the Samsung Push Service. It is really the AT&T software update app that finally started downloading immediately after trying it again.
So I finally attempted the Keis connection and it worked immediately. I don't know what other problems people are having, but when I installed it on my Win7 x64 machine I had the S3 connected. After I ran the software for the first time it mentioned an update and proceeded to update it. Keep fighting the good fight jefferson9.
I had to go back to stock with injected root to use my allshare dongle. I loathe stock rom with every fiber of my being.
Does anyone know or has anyone tried flashing custom recovery and custom rom and kernel then flash back to stock recovery and allshare still works? Or perhaps a work around other than triangle away. Which I don't enjoy rebooting my phone every time I want to connect.
I use the dongle in my car with the pioneer appradio2 so rebooting the phone everything I connect to my stereo gets old fast.
Sorry if it seems like I'm nitpicking. I had triangle away soft brick on me once before and had to Odin flash to fix.
No, you have to be completely stock for it to work. This is a struggle for many of us and it goes back many months.
None of the devs took the time or interest to take the app apart and remove the part that checks the phone.
Sorry to give you the bad news.
Sent from my SGH-T889 using xda premium
premiatul said:
No, you have to be completely stock for it to work. This is a struggle for many of us and it goes back many months.
None of the devs took the time or interest to take the app apart and remove the part that checks the phone.
Sorry to give you the bad news.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
While I am in no way a dev, I did take some time to take apart the handful of apks and jars that are most obviously related to allshare - but I was unable to find out where exactly the check occurs. I even went through and hacked up SysScope.apk a little in an attempt to emulate an xposed sysscopeblaster mod that I had heard helps, but again to no avail. And by "no avail" I mean "the person that tested it said it didn't work" - as I have no allshare things to really test stuff. I contacted some other actual-dev folks that got things working on other carriers, and while reports indicate that replicating their methods worked with the 4.1.1 base for whatever reason 4.1.2 seems to behave differently, making such a replication no longer effective. This quickly began to land far outside any pseudo-skillset I might possess unfortunately. Hmm... does anyone happen to have the the flashable zip that was used to OTA update from 4.1.1 UVALL4 to 4.1.2 UVBMB4? Or was an OTA not possible (i.e. had to do it via Kies/Odin/etc.)? I just did the Odin approach using stuff from sammobile myself... it's a long shot but there could be a clue in there perhaps.
Anyhoo - long story short my personal attempt at figuring this out has revealed an absence of some needed skill or awareness of where such checks actually occur. Just thought I would chime in to show that it's not necessarily an issue of no one looking into it - just maybe not the right people
Ah. Well that blows. Thanks for the info though. Strange how Samsung is usually one of the manufacturers that condones aftermarket and custom work but would pull a stunt like this with allshare and tethering.
Been eyeballing roms and triangle away. But if everything has to be completely stock to work I'm just a dog barking up am empty tree.
I just rooted AT&T Note 2 & I already had the corporate Touchdown on it. After rooting I got an email saying MASS 360 has blocked my phone as now its rooted.
How can I go back or keep both Rooting as well as Touchdown working
Thanks
Well, essentially you might be done already. Depends how nasty the protection is. As admin I would be keeping phone permanently out of the network until it's flashed directly by it. If this is less nasty then just unroot or use hide root app and see if it works again. If you make it work this way then perhaps would be nice to remove that mass360 thing and see if touchdown world's without it.
DroidBartender said:
I just rooted AT&T Note 2 & I already had the corporate Touchdown on it. After rooting I got an email saying MASS 360 has blocked my phone as now its rooted.
How can I go back or keep both Rooting as well as Touchdown working
Thanks
Click to expand...
Click to collapse
It's been 4 years ... did you ever figure out ... or found a solution?
I have a personal phone with corporate touchdown email and want to root, but want to keep email app working.