Related
Hey, everyone.
I just bought an ATT Samsung Focus S i937 off of eBay. It was locked when I received it, so I plunked down 25 bucks and unlocked it. I'm using it on Telus and so far all is well, except for WiFi connection sharing/tethering.
When I try to enable internet sharing, I get a message saying "Connection not shared. To enable tethering on this device go to (ATT's website) or dial 611."
Basically, it sounds like I need to have an ATT tethering plan to enable this on my phone, but since I'm not an ATT customer, there's not mch I can do.
I was wondering if there is a workaround for this. Please let me know!
Thanks,
Taylor
TaylorofCanada said:
Hey, everyone.
I just bought an ATT Samsung Focus S i937 off of eBay. It was locked when I received it, so I plunked down 25 bucks and unlocked it. I'm using it on Telus and so far all is well, except for WiFi connection sharing/tethering.
When I try to enable internet sharing, I get a message saying "Connection not shared. To enable tethering on this device go to (ATT's website) or dial 611."
Basically, it sounds like I need to have an ATT tethering plan to enable this on my phone, but since I'm not an ATT customer, there's not mch I can do.
I was wondering if there is a workaround for this. Please let me know!
Thanks,
Taylor
Click to expand...
Click to collapse
firstly DO NOT INSTALL THE SAMSUNG UPDATE!! and if updating the OSan have it unlocked already read This Website and use the relock prevent + edit your hosts file
Absolutely back up your device at every stage using This Guide
So follow these steps
unlock the device Here follow the instructions which includes installing the diagnostic tool and install XAP deployer or XAP handler Here or Here With the XAP file deployer in the WP7 SDK
Then install WP7 Root Tools Here
Then install WP Bazaar market Here
Open Root Tools, and give Bazaar higher level privileges
Find WinTT on the Bazaar market and install it
Open Root Tools, and give WinTT higher level privileges
you may need to restart to get WinTT working
go through WinTT and turn on ICS
Done
Wow thanks.
That's very complete. One questions though... I didn't mention this, but I am a registered WP7 dev and can unlock this device using my dev access. Can I load any of the XAPs directly instead of having to crack my phone?
Thanks,
Taylor
Yeah, you have limited access to installing xaps, but you will still need to interop unlock and use root tools to give higher level access to WinTT, so your best starting from scratch,
Sent from my SGH-i937 using XDA Windows Phone 7 App
Unable to understand the process
I have purchased an Samsung Focus S i937 locked to AT&T. I have purchased an unlock code and have successfully unlocked my phone. Im also unable to use the Internet Sharing feature of my phone. Firstly, I am not a technical guy hence im unable to understand the process stated by you. Secondly, I wanted to find out that does following the process given by you, expose my device to get BRICKED as I am able to understand that involved a JAIL BREAK of the device. Does it have any other side effects.? Like effecting the radio signals or any other such problem.
Thanks
abhijeetmohan06 said:
I have purchased an Samsung Focus S i937 locked to AT&T. I have purchased an unlock code and have successfully unlocked my phone. Im also unable to use the Internet Sharing feature of my phone. Firstly, I am not a technical guy hence im unable to understand the process stated by you. Secondly, I wanted to find out that does following the process given by you, expose my device to get BRICKED as I am able to understand that involved a JAIL BREAK of the device. Does it have any other side effects.? Like effecting the radio signals or any other such problem.
Thanks
Click to expand...
Click to collapse
ok, first things first.
You won't brick your device, at worst a hardrest all remove all changes you can do, our device, the focus S, isn't fully unlocked, so there are limitations to the amount of damage you can do by arseing it up. With that behind us you have to learn what you are about to do, there isn't a simple way.
So, start by knowing these basics, then read through the guide, any bits you don't understand feel free to ask.
1, AT&T locked your internet connection sharing, so you must re enable that
2, To enable ICS, you must make changes to the registry
3, Microsoft locked you out of making changes to the registry, so you must gain access to do it
4, AT&T left a security hole allowing us to make changes to allow us to change things like registry
5, using that hole we can install software that will give us more access, that software can then allow us to remove the AT&T lock on ics
These things you must do, there is no magic answer, there has been some short cuts made but this in some cases has had a negative effect, such as losing 3g, doing as I said will not have any effect on your signal or anything else
Sent from my Samsung Focus S using XDA Windows Phone 7 App
Have you guys noticed any of the following....
issues after the above procedures were applied (a big thanks to all the brainiacs who know how to hack this stuff):
Slowed Internet Connection
Lower Strength of GPS Signal
Less accuracy and trouble sometime finding location
Less accuracy while using maps because of the above statement
Not complaining, just curious. Thanks to all.:good:
7carisfast said:
issues after the above procedures were applied (a big thanks to all the brainiacs who know how to hack this stuff):
Slowed Internet Connection
Lower Strength of GPS Signal
Less accuracy and trouble sometime finding location
Less accuracy while using maps because of the above statement
Not complaining, just curious. Thanks to all.:good:
Click to expand...
Click to collapse
theres nothing in the code that should have done that, the XML import only fiddles with interop unlock
im not 100% sure what WTT changes but I know the entries it should be fiddling with and shouldnt make any difference, although its been suggested the ICS code does mess with the 3G signal ive not heard anything at all to suggest that it effects GPS as well.
See This Thread for details, ive copied the relevant bits here but all thanks should go to those on the original thread
Option 1
---- 11.3. If your device is not locked to a specific operator, you can use the Samsung Network Profile app (for 1st generation) or Wireless Manager (for 2nd generation)
-------- 11.3.1. Uninstall the Samsung Network Profile / Wireless Manager app.
-------- 11.3.2. Download and install the latest version of the Samsung Network Profile / Wireless Manager app from the Marketplace.
-------- 11.3.3. Open the Samsung Network Profile / Wireless Manager app.
-------- 11.3.4. Select a different Network Operator.
-------- 11.3.5. Now Select your own Network Operator again.
-------- 11.3.6. Exit the Network Profile / Wireless Manager app.
Option 2
Resolve Samsung connection problems
A lot of Samsung owners have complained here about connection problems. They blamed Interop Unlock, but apparently this has more to do with enabling "Internet Connection Sharing" than with "Interop Unlock". You should be able to recover the connection, apply this:
1. Start Diagnosis App> *#32489# ***DOES NOT WORK ON i937***
2. Tap "Back" 2 times to go back to Phone Control
3. Choose: [7] Network Control
4. Choose: [1] GFC
5. Choose: [3] Setting Cancellation
Wait for it to say success, then reboot.
GPS is a completely passive function, I don't have a problem with this, HSDPA may have issues for reasons unknown but using this method doesn't effect mine, perhaps its carrier specific..
dazza9075 said:
theres nothing in the code that should have done that, the XML import only fiddles with interop unlock
im not 100% sure what WTT changes but I know the entries it should be fiddling with and shouldnt make any difference, although its been suggested the ICS code does mess with the 3G signal ive not heard anything at all to suggest that it effects GPS as well.
See This Thread for details, ive copied the relevant bits here but all thanks should go to those on the original thread
Option 1
---- 11.3. If your device is not locked to a specific operator, you can use the Samsung Network Profile app (for 1st generation) or Wireless Manager (for 2nd generation)
-------- 11.3.1. Uninstall the Samsung Network Profile / Wireless Manager app.
-------- 11.3.2. Download and install the latest version of the Samsung Network Profile / Wireless Manager app from the Marketplace.
-------- 11.3.3. Open the Samsung Network Profile / Wireless Manager app.
-------- 11.3.4. Select a different Network Operator.
-------- 11.3.5. Now Select your own Network Operator again.
-------- 11.3.6. Exit the Network Profile / Wireless Manager app.
Option 2
Resolve Samsung connection problems
A lot of Samsung owners have complained here about connection problems. They blamed Interop Unlock, but apparently this has more to do with enabling "Internet Connection Sharing" than with "Interop Unlock". You should be able to recover the connection, apply this:
1. Start Diagnosis App> *#32489#
2. Tap "Back" 2 times to go back to Phone Control
3. Choose: [7] Network Control
4. Choose: [1] GFC
5. Choose: [3] Setting Cancellation
Wait for it to say success, then reboot.
GPS is a completely passive function, I don't have a problem with this, HSDPA may have issues for reasons unknown but using this method doesn't effect mine, perhaps its carrier specific..
Click to expand...
Click to collapse
Thanks for the info. I'll see if it helps. Just as FYI, the code *#32489# does not appear to work on the i937.
7carisfast said:
Thanks for the info. I'll see if it helps. Just as FYI, the code *#32489# does not appear to work on the i937.
Click to expand...
Click to collapse
indeed, so it would seem, many of the diagnostic codes have been disabled which is a pain, even the ones that are left don't always do what you expect them to do
8773 update
dazza9075 said:
firstly DO NOT INSTALL THE SAMSUNG UPDATE!! and if updating the OSan have it unlocked already read This Website and use the relock prevent + edit your hosts file
Absolutely back up your device at every stage using This Guide
So follow these steps
unlock the device Here follow the instructions which includes installing the diagnostic tool and install XAP deployer or XAP handler Here or Here With the XAP file deployer in the WP7 SDK
Then install WP7 Root Tools Here
Then install WP Bazaar market Here
Open Root Tools, and give Bazaar higher level privileges
Find WinTT on the Bazaar market and install it
Open Root Tools, and give WinTT higher level privileges
you may need to restart to get WinTT working
go through WinTT and turn on ICS
Done
Click to expand...
Click to collapse
What if I have already updated to version 7.10.8773.98, is there any other possible way? I don't need any other features. Thanks in advance.
If you have updated the OS and NOT the samsung firmware then reapply the windows break interop unlock, be sure to keep it off the inernet by disabling all coms and then apply the relock prevent xap. if you have applied the Samsung firmware and didn't have it already unlocked or you didn't have a back up, your screwed
Sent from my Samsung Focus S using XDA Windows Phone 7 App
dazza9075 said:
If you have updated the OS and NOT the samsung firmware then reapply the windows break interop unlock, be sure to keep it off the inernet by disabling all coms and then apply the relock prevent xap. if you have applied the Samsung firmware and didn't have it already unlocked or you didn't have a back up, your screwed
Sent from my Samsung Focus S using XDA Windows Phone 7 App
Click to expand...
Click to collapse
First of all I just want to say thanks that you're trying to help me, but I just didn't understand many things u said, I'm not really into technical stuff, but I'll tell you what info I have, in hope of u helping me better.
I don't live in the US and I bought the phone from ebay and it was unlocked and it works perfectly over 2 carriers here in my country, and I have never encountered any problems with it except for the internet sharing feature.
And about 3 months ago the phone notified my to a system upgrade from version 7.10.7740 to version 7.10.8107 then immediatly to version 7.10.8773.98. now I'm guessing these are OS firmwares not samsung software.
but I've noticed something, when I setup my phone for the first time I used a US hotmail account but before I connect to the internet the ICS feature worked, but once I signed in it gave me the dial 611 or go to att.com/mywireless message.
So I am guessing if I restore the device and sign in with a non US hotmail account may result in the feature to be unlocked. The only thing keeping me from trying this because I'll have to redownload all my apps again and reorganize my contacts again. if there's a way to avoid that or someone has tried it please do tell.
Again thanks for your reply.
kholio88 said:
First of all I just want to say thanks that you're trying to help me, but I just didn't understand many things u said, I'm not really into technical stuff, but I'll tell you what info I have, in hope of u helping me better.
I don't live in the US and I bought the phone from ebay and it was unlocked and it works perfectly over 2 carriers here in my country, and I have never encountered any problems with it except for the internet sharing feature.
And about 3 months ago the phone notified my to a system upgrade from version 7.10.7740 to version 7.10.8107 then immediatly to version 7.10.8773.98. now I'm guessing these are OS firmwares not samsung software.
but I've noticed something, when I setup my phone for the first time I used a US hotmail account but before I connect to the internet the ICS feature worked, but once I signed in it gave me the dial 611 or go to att.com/mywireless message.
So I am guessing if I restore the device and sign in with a non US hotmail account may result in the feature to be unlocked. The only thing keeping me from trying this because I'll have to redownload all my apps again and reorganize my contacts again. if there's a way to avoid that or someone has tried it please do tell.
Again thanks for your reply.
Click to expand...
Click to collapse
ok, no problem
can you go to your device settings, in the about section can you tell me your OS version and your firmware version
Samsung Firware Update
dazza9075 said:
ok, no problem
can you go to your device settings, in the about section can you tell me your OS version and your firmware version
Click to expand...
Click to collapse
Dazza,
Kudos for your help as you personally worked with me through this information. Not sure the Samsung update is a concern as I'm running fw2103.11.10.1 and everything works great.
Thanks again.
dazza9075 said:
ok, no problem
can you go to your device settings, in the about section can you tell me your OS version and your firmware version
Click to expand...
Click to collapse
OS version: 7.10.8773.98
Firmware version: 2103.12.05.2
kholio88 said:
OS version: 7.10.8773.98
Firmware version: 2103.12.05.2
Click to expand...
Click to collapse
im afraid to say your firmware is locked,
2103.11.10.1 is unlock-able, im pretty sure anything from xxxx.12.xx.x upwards is locked down solid
I don't suppose you made a backup? if you haven't then there is nothing you can do
the Samsung firmware update was released as a separate update at the same time as the tango 8773 build, it tried to install on mine after the 8773 build
Found a solution =D
dazza9075 said:
im afraid to say your firmware is locked,
2103.11.10.1 is unlock-able, im pretty sure anything from xxxx.12.xx.x upwards is locked down solid
I don't suppose you made a backup? if you haven't then there is nothing you can do
the Samsung firmware update was released as a separate update at the same time as the tango 8773 build, it tried to install on mine after the 8773 build
Click to expand...
Click to collapse
I'm really sorry for the late reply, was busy at work. but during that time I might have found a "Glitch" or a workaround to enable it and I have tested it many times and it works.
Well there are two ways:
1st one which is a sure thing:
1) Turn off the phone, then turn on again.
2) Once the phone is turned on, immediately go to settings>internet sharing and turn it on and BOOM there you go :laugh:
* I have tried this method over a dozen times and it works every single time
** The point here is that you have to enable it immediately after the phone is turned on, I think it happens because the phone doesn't have enough time to send the info. to the servers to know that it's not enabled by default.
2nd one which was succesful over 75% of the time:
1) Go to Settings>cellular>Turn Off, Wait like 5-10 seconds and turn on again.
2) Go to Internet sharing> Turn on, and enjoy :fingers-crossed:
***I don't know why do they work or how, may be it's a Glitch like I said before but the point is they do work
I hope that I've helped someone out there and Thanks to everyone who tried to help me
kholio88 said:
I'm really sorry for the late reply, was busy at work. but during that time I might have found a "Glitch" or a workaround to enable it and I have tested it many times and it works.
Well there are two ways:
1st one which is a sure thing:
1) Turn off the phone, then turn on again.
2) Once the phone is turned on, immediately go to settings>internet sharing and turn it on and BOOM there you go :laugh:
* I have tried this method over a dozen times and it works every single time
** The point here is that you have to enable it immediately after the phone is turned on, I think it happens because the phone doesn't have enough time to send the info. to the servers to know that it's not enabled by default.
2nd one which was succesful over 75% of the time:
1) Go to Settings>cellular>Turn Off, Wait like 5-10 seconds and turn on again.
2) Go to Internet sharing> Turn on, and enjoy :fingers-crossed:
***I don't know why do they work or how, may be it's a Glitch like I said before but the point is they do work
I hope that I've helped someone out there and Thanks to everyone who tried to help me
Click to expand...
Click to collapse
nice find, ICS is disabled locally only, it doesn't have anything to send, the only thing I can think of that makes sense is that the service hasn't been initialised and doesn't call the reg entries that disables ICS, by turning it on manually ASAP it perhaps catches it out. if you enable it, then disable it, can you still enable it again in that session or do you need to restart?
dazza9075 said:
nice find, ICS is disabled locally only, it doesn't have anything to send, the only thing I can think of that makes sense is that the service hasn't been initialised and doesn't call the reg entries that disables ICS, by turning it on manually ASAP it perhaps catches it out. if you enable it, then disable it, can you still enable it again in that session or do you need to restart?
Click to expand...
Click to collapse
Well I tried that, but there is no definite answer to it, sometimes I turn it on and off on and off many times without needing to restart and throughout the whole day, and sometimes it works once and doesn't at the second try. So it all comes down to luck, but still better than nothing
Now the thing is I'm afraid that when the 7.8 update comes, they would fix this glitch =D Haha.
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.
Hey all, so I recently spent some time learning up on these awesome forums, and at least for getting started I decided to just modify stock 2.2, I have just really wanted to be able to play games using my ps3 controller on my nook so I thought the easiest path was to root using the Universal Rev3, and the Unknown Apps, at least to get me started. I have a bluetooth keyboard I also use with this setup for school. Okay so that's the upfront details.
My issue is that, while my bluetooth is connecting fine with everything before I run sixaxis, and my controller works (yay, i got what i wanted!) while I'm running the program, it's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot... I've completely stopped and disabled and cleared the cache on the sixaxis app... and nothing, still won't turn back on. Now this is a cadillac issue, my controller works, my keyboard works, but I just have to reset. The problem is that I know it shouldn't be this way and if it has to be, I'll survive, but if not I'd love a way to make it work right, or at the very least see if there's an option to... "respring" (I know that's an iphone thing I just didn't know if there was a faster equivalent to a reboot without having to completely turn it off and back on)?
Anyone else had this problem? Any thoughts? Any options? Thanks for your time and information, have a great day!
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
sandsofmyst said:
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
Click to expand...
Click to collapse
Hey thanks a ton for the information. I had started to suspect that but since I'm a noob here I thought it was best to ask. Will contact the developer. But hey for now if all I have to do is a reset after a gaming session to make all things right, it's not so bad. Thanks again!
EDIT: Okay, so after doing some fiddling with my own Nook HD+ it looks like the Nook itself has trouble shutting down bluetooth! When I go into my battery use bluetooth is staying on permanently after initially turning it on. The time continues to run no matter what I do or shutdown with Android Task Manger. And it appears I'm not the only one. http://bookclubs.barnesandnoble.com...Bluetooth-won-t-turn-off-Nook-HD/td-p/1462091
Also since mine is rooted and has unknown sources installed I felt like I needed a control group. So I borrowed my wifes Nook HD+ which is completely stock, no mods at all... and it does the exact same thing... This is mind boggling. Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
gregorcarbine said:
Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
Click to expand...
Click to collapse
It could also be this or similar: https://code.google.com/p/android/issues/detail?id=69135
Quote, "Problem: When turning off the Jawbone, it causes the Bluetooth(BT) to misbehave and not turn off nor function."
...Though that's for android 4.4.2 and nook 2.2 is android 2.2... wow that's old... that could of course be it as well - if the problem is with android, it could have been fixed in a later android version.
In the end, it doesn't appear to have to do with the device itself, but perhaps with that android version's bluetooth package or an installed app. And which android version (if any) would work for you idk. I remember people saying cm and sixaxis didn't work with bluetooth on the nook in the past, so if that's still the case, don't know that either.
I'm not sure how far back many apps are going today with android versions but something like: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
could possibly do something(?). But, I'm just reaching there for anything in the you never know category.
But hopefully that gives a better picture as to what it could be. Sorry, I can't give an actual [working] solution, though for all I know I gave a path to the only solution.
I am trying to use cm_ovation-ota-MMB29T.160127.zip (Marshmallow) on my Nook HD Plus. I am having trouble getting root. What Superuser should I be using and how should I install it ?. I am getting root occupied and user not authorized errors. I have tried flashing SuperSu and installing Kingo Root , with no success. Please Help. Thanks.
Nobody????? Really....
Nobody has Marshmallow with root? Nobody has any advice, suggestions or any input at all? Nobody has any links, tutorials or anything? Nobody that knows how to do this ( I have researched this forum and have tried to get this to work before asking for assistance.... So I am making an attempt to do this on my own) can offer me any help? Guys....really?
fire1951 said:
Nobody has Marshmallow with root? Nobody has any advice, suggestions or any input at all? Nobody has any links, tutorials or anything? Nobody that knows how to do this ( I have researched this forum and have tried to get this to work before asking for assistance.... So I am making an attempt to do this on my own) can offer me any help? Guys....really?
Click to expand...
Click to collapse
Been awhile since I did this one, but I see on the card I made UPDATE-SuperSU-v2.46.zip. I assume I flashed that to get root access.
I've attached a copy below. I hope it works for you.
oops....delete....
I appreciate the response . I will give it a try next time I try to install Marshmallow. Thanks again.
Thank you so much for that zip...it did the trick! Another question for you...in another post you mentioned (on Marshmallow), that to get WiFi to connect, you turned off, then turned on the display. Did you have to do this each time? I am using Tasker to do this after boot...which works pretty good. Also, the HDMI output is upside down...did you have this also? I am also using Tasker to toggle this when necessary. Thanks again for the response...it saved the day!
fire1951 said:
Thank you so much for that zip...it did the trick! Another question for you...in another post you mentioned (on Marshmallow), that to get WiFi to connect, you turned off, then turned on the display. Did you have to do this each time? I am using Tasker to do this after boot...which works pretty good. Also, the HDMI output is upside down...did you have this also? I am also using Tasker to toggle this when necessary. Thanks again for the response...it saved the day!
Click to expand...
Click to collapse
My comment about the WiFi was in regard to a Nook Tablet version of CM13. My husband is running CM13 on his HD and I don't recall him complaining about WiFi (which he always has on). On the NT I did always have to wait for the initial lock screen to go dark (or almost dark) before WiFi would connect on its own.
As to the HDMI orientation, see https://forum.xda-developers.com/nook-hd/help/solved-screen-orientation-vs-hdmi-t3701280
After I figured this out my husband asked me to change his back to upside down! You can get used to almost anything.
SuperSU was broken for a little while, but the current installer should install just fine. There are also systemmode installers here on XDA that have the systemless bits removed. Wifi with CM/LN should work, it is AOSP ROMs that have issues.
Hi all. I'm new to the site, so if I'm posting in the wrong forum, please let me know. I hope someone can help.
When I left my last company, they allowed me to take my Note 9 because it was paid in full. New management came in and set up Knox MDM. Because my device was paid for by them, they added my device to Knox and put it in Kiosk mode. I can no longer do anything on it but send/receive calls. I contacted Verizon, and they said even though i pay for the service, the device is technically still owned by the company and couldn't help me. So, i'm left with either buying a new phone or asking new management to remove me from knox. They will not, so I was hoping someone knew how to remove knox, possibly through rooting the phone. However, I can't enable developer mode. When I click on the build number, i get a message saying the feature is disabled by knox.
this is just a suggestion, I'm not saying to follow it. wait for someone else to confirm it's an OK idea or a terrible one.
using a PC or even another rooted phone you could run ADB and remove Knox packages. pretty sure you can do this successfully on newer phones but with Knox ''activated'' and doing stuff I'm not sure.
3mel said:
this is just a suggestion, I'm not saying to follow it. wait for someone else to confirm it's an OK idea or a terrible one.
using a PC or even another rooted phone you could run ADB and remove Knox packages. pretty sure you can do this successfully on newer phones but with Knox ''activated'' and doing stuff I'm not sure.
Click to expand...
Click to collapse
Thanks for the advice. I'm good with that route, and I'm good with wiping the phone to root it. I installed ADB on my laptop and connected the phone, but it when I run adb devices, nothing is returned. I assumed it was because the phone wasn't in developer or usb debugging mode. So, I was hoping there was a way to do it without needed access to settings.
oh crap yeah, I forgot you did say that. curious do you still work for this company ?
either try doing ADB thru the recovery (never tried it, know nothing about it but it's a thing) or give a factory reset a try. the reset should at the very least kill off the companies settings though I'm not sure how much use that'll be.
flashing appropriate firmware with Odin should work for you too.
3mel said:
oh crap yeah, I forgot you did say that. curious do you still work for this company ?
either try doing ADB thru the recovery (never tried it, know nothing about it but it's a thing) or give a factory reset a try. the reset should at the very least kill off the companies settings though I'm not sure how much use that'll be.
flashing appropriate firmware with Odin should work for you too.
Click to expand...
Click to collapse
Thanks 3mel. I'll give those things a whirl. I'm not employed with them anymore, which is why going to new management isn't an option. A friend of mine still works there and they told me that management asked verizon for the device id's for the last 5 years and just put them all on knox. For them, $1/mo for a devices no longer in use by them outweighed the potential of missing devices in the wild.
rainana said:
Thanks 3mel. I'll give those things a whirl. I'm not employed with them anymore, which is why going to new management isn't an option. A friend of mine still works there and they told me that management asked verizon for the device id's for the last 5 years and just put them all on knox. For them, $1/mo for a devices no longer in use by them outweighed the potential of missing devices in the wild.
Click to expand...
Click to collapse
Hello dear friend, I have the same problem, did you find any solve for this issue? I will be happy if u will share the method)
Hello,
I have a similar case.
without debug mode, adb devices doesn't list any devices.
there is really no way to flash a custom ROM on this phone, without log into the old google account?