Related
A number of posters either dispute or are no sure of the warranty position regarding rooting in particular .
Fact one the phone provider who is usually responsible for the first twelve months warranty can most certainly reject warranty for non original firmware or rooting .In the UK i have checked the position with O2 and Vodaphone who say they will reject under terms of their warranty .
SAMSUNG own warranty which is also usually paid in the first twelve months to the seller/repairer .
Basically say exactly the same rooting or custom rom voids warranty .
The letter on Samfirmware for starters if you don't believe .
http://www.samfirmware.com/apps/blo...cs-?&fw_comments_page=2&fw_comments_order=ASC
Extract from other sources .
ROOTING:
• Corporate recently added an additional reason for an Android handset to be considered as Out-Of-Warranty.
• Android handsets that have been subject to “rooting”, “jailbreaking” or “hacking” are no longer covered under warranty and may be grounds for termination or modification of service.
• Rooting is a process that modifies a handsets software allowing access to services not supported or tested by the Carrier or OEM.
• While there are more applications out there that allow subscribers to gain root access, a specific example seen on a Samsung Galaxy Indulge is shown below.
• If you see this application on the handset, please explain that the handset is out of warranty and be certain to access the customer’s account and add a memo that the handset has been rooted.
The picture they posted of is super user and some other ones.
another source
The reason I'm posting this now is because Samsung have only this week implemented a system for Service Centres to check if the handset has been rooted.
Point is its very easy in most cases to unroot and flash a stock firmware .
Some service guys may well turn a blind eye to rooting others may not .No good saying some guy on XDA said it was ok .
User choice but i have seen enough to convince me 100% ROOT = VOID WARRANTY .
jje
I thought this was common knowledge anyway?
Coedy said:
I thought this was common knowledge anyway?
Click to expand...
Click to collapse
Yes but its recently been disputed by some so i just pulled out my notes .
jje
^ Some people just don't get it however and seem to think they're still entitled, even if they returned it to stock and reset the counter, etc...
Individual cases may vary, maybe you'll get a "mod friendly" warranty facility, but I wouldn't feel bad for someone who gets denied warranty in the least. If someone can't afford to replace their phone out of pocket, they shouldn't be modding it.
True, i already expect that I'll void the warranty once i root my phone.. it's the point of no return..
I keep a safe distance on messing up my phone, make sure i don't get too far and ended up with a dummy display phone..
Sent from The Center of The Earth
mudferret said:
If someone can't afford to replace their phone out of pocket, they shouldn't be modding it.
Click to expand...
Click to collapse
Exactly. I would hope everyone would understand the risk before doing something like this.
How can they detect the phone was rooted when I reseted the custom fw count and flashed a stock rom ?
There will be no super user app or the like... Furthermore unlike i.e. SE Xperia phones the bootloader of the S2 isn't locked. Unlocking the bootloader of these phones is indeed a one way street. I don't see how this should apply for the S2?
This should be stickied with a tagline along the lines of:-
"Thinking of flashing a custom rom or kernel ? Consider this..."
I'm with Bell and I had a Rooted Atrix with cyanogenmod 7 beta 3 (back in the days..) and I had screens problems, I gave my phone to Bell and they send it to Motorola and it works flawlessly but they put me back on their motoscrap...
I'm sure Samsung will do the same thing
But thanks you anyways
harise100 said:
How can they detect the phone was rooted when I reseted the custom fw count and flashed a stock rom ?
There will be no super user app or the like... Furthermore unlike i.e. SE Xperia phones the bootloader of the S2 isn't locked. Unlocking the bootloader of these phones is indeed a one way street. I don't see how this should apply for the S2?
Click to expand...
Click to collapse
Think of it like a PC. Just because you format the harddrive doesn't mean the info is gone.
Bam !
Beautifully put Zelendel Rooting/flashing (like throwing rocks) is all fun & games until someone gets hurt
zelendel said:
Think of it like a PC. Just because you format the harddrive doesn't mean the info is gone.
Click to expand...
Click to collapse
harise100 said:
How can they detect the phone was rooted when I reseted the custom fw count and flashed a stock rom ?
They are not going to look that far .
Boot screen Custom rom possible if doing the job check for root apps /root.
As i said a lot dont even bother and just flash stock rom and repair .
But a lot is not all .
jje
Click to expand...
Click to collapse
With the new popularity of rooting, checking these things are becoming standard. To be honest I am glad. It will make people think first before they follow a video on youtube that is normally made by someone that has no idea what they are doing other then following a simple how to.
Modding a device is not ment for everyone. Nor should everyone do it.
Wait...the carrier can terminate your line for rooting?
Sent from my x10 mini running the latest version of minicm 7.
aloy99 said:
Wait...the carrier can terminate your line for rooting?
Sent from my x10 mini running the latest version of minicm 7.
Click to expand...
Click to collapse
Yeah they can terminate your contract if you mod your phone is anyway. Not to mention charging you the full price of the phone and the rest of the contract left over.
Main reason there are warnings all over the place about knowing and understanding what you are doing before you do it.
I would like to say that under the Australian law (sorry other nationalities) that Competition and Consumer Act 2010 gives a great coverage of products and if there is a hardware fault from the phone the supplier should not be able to reject your claim if modification of the phones software is unrelated to the issue. Although there is a clause that states:
You may not be entitled to a remedy if you:
damage or use goods in an unreasonable or unintended manner
Click to expand...
Click to collapse
I don't think it is unreasonable or unintended to run custom software on a programmable device. After all Samsung did give phones away so CyanogenMod would run on them.
Bottom line If I brick my phone or mess it up due to software modification I accept full responsibility but if the fault lies with the device itself the warranty should hold and no matter how much crap they put in a EULA or their written warranty Australian law should protect my device.
If I buy a computer and I remove windows to install Linux I still expect a warranty to hold if the hardware fails.
Rooting is the only way to take control of a device that I own so my personal information can stay personal.
Im interested in what the laws are like in the EU.
However my own position on this is that one should be allowed to use any software and mods to software you want.
If there is a hardware malfunction they should fix it whatever software you chose to use. If you brick the bootloader they can JTAG it probably.
And this far i have never had anyone ever say anything about me using custom roms and the like.
However i would still like to know what the laws say.
Sent from my GT-I9100 using Tapatalk
rako77 said:
I would like to say that under the Australian law (sorry other nationalities) that Competition and Consumer Act 2010 gives a great coverage of products and if there is a hardware fault from the phone the supplier should not be able to reject your claim if modification of the phones software is unrelated to the issue. Although there is a clause that states:
I don't think it is unreasonable or unintended to run custom software on a programmable device. After all Samsung did give phones away so CyanogenMod would run on them.
Bottom line If I brick my phone or mess it up due to software modification I accept full responsibility but if the fault lies with the device itself the warranty should hold and no matter how much crap they put in a EULA or their written warranty Australian law should protect my device.
If I buy a computer and I remove windows to install Linux I still expect a warranty to hold if the hardware fails.
Rooting is the only way to take control of a device that I own so my personal information can stay personal.
Click to expand...
Click to collapse
That's the thing. The device is INTENDED to run on the software they install. That's how they justify saying that any custom software could be the cause for hardware issues.
Take the PC example you used. OeM have been known to deny warrenty if you installed any OS other then the one that was on it. Like loading Linux on your windows PC. Mainly due to the use open source drivers instead of the OEM drivers made for the device. Samething goes for AOSP roms. They don't use drivers made for the device. They use generic device drivers that "could" cause hardware issues and that is what they love to say.
Spent a few years doing PC and smartphone repairs and that was the first thing we were trained to look for. If we found any sign of Modding in anyway we were to not repair it till they cleared it with the owner that they were going to be charged for it due to a voided warrenty.
zelendel said:
Think of it like a PC. Just because you format the harddrive doesn't mean the info is gone.
Click to expand...
Click to collapse
Good point.
Amazon repair service didn't use forensic software when I sent them a xperia Neo with the 0%-bug. They replaced it without much ado. Lucky me ;-)
Sent from my GT-I9100 using XDA App
zelendel said:
That's the thing. The device is INTENDED to run on the software they install. That's how they justify saying that any custom software could be the cause for hardware issues.
Take the PC example you used. OeM have been known to deny warrenty if you installed any OS other then the one that was on it. Like loading Linux on your windows PC. Mainly due to the use open source drivers instead of the OEM drivers made for the device. Samething goes for AOSP roms. They don't use drivers made for the device. They use generic device drivers that "could" cause hardware issues and that is what they love to say.
Spent a few years doing PC and smartphone repairs and that was the first thing we were trained to look for. If we found any sign of Modding in anyway we were to not repair it till they cleared it with the owner that they were going to be charged for it due to a voided warrenty.
Click to expand...
Click to collapse
rooting does not mess with the drivers and I am defiantly not touching the cpu clock.
The only reported case of a pc manufacturer that i can find refusing to remedy a hardware problem where the operating system was changed was pc world which later stated that was not there policy and would preform a repair. international law may be different but under Australian law I have full ownership of the device and I think it is outrageous that companies try and weasel there way out of their rights to the consumer.
In my mind if the fault is there's they have to fix it and no way should they be able to say otherwise. Its really just a matter of who has the burden of proof.
Any one done or know if its possable to get the new windows 8 tablet software running on a nexus 7 ??? Or know a good cheep android tablet that will dual boot it ??? Ty
Only want to have a little mess around with it and see how well it runs with an xbox before wasting money on buying one as already have a few tablets.
cubixgames said:
Any one done or know if its possable to get the new windows 8 tablet software running on a nexus 7 ??? Or know a good cheep android tablet that will dual boot it ??? Ty
Only want to have a little mess around with it and see how well it runs with an xbox before wasting money on buying one as already have a few tablets.
Click to expand...
Click to collapse
What exactly do you want it to do with an xbox? It does no more than the SmartGlass app for Android can do.
Does a lot more then what smart glass does, music and video sync on the go sync to mobile phone and so on so many ways to link up the device all to work together. Also be nice to have a play with the new setups see how it runs and feels, what they actulay changed and what they just took from the windows 7.5 mobile edition
Sent from my Nexus 7 using xda app-developers app
Not going to happen for a handful of reasons, not the least of which are it being closed source, no drivers existing for our hardware, too much of a legal liability for anyone who tried, etc.
Sent from my Galaxy Nexus using Tapatalk 2
Not even with as OEM copy of the software. I've seen things
Like the acer tablet on eBay with dual boot android and windows.
Looks like I might just need to invest in a windows tablet as well as my android
Sent from my Nexus 7 using xda app-developers app
No no no no no no no no no no
There is another thread that talks about this in VERY DEEP Details..
First there are two versions of windows 8
Windows 8 x86/x64 . Runs on tradition computer cpus
Windws 8 RT .. the tablet version Runs on Arm (TEGRA CPU) Similar to what nexus 7 has..
Windows 8 tradition version. The one you can buy will not run on ARM CPU
Windows RT is A ROM VERSION OF The os. NOT FOR SALE. Its Protected with boot-loader security beyond anything in the past. Beyond that Microsoft says NO.. You can only get this version From Windows 8 DEVICE PRELOADED..
So if you were to get a raw copy .. Making it work would be VERY ILLEGAL..
THE SHORT ANSWER IS Absolutely NO YOU CAN NOT DO IT..
Look for the other thread if you need to know more on the subject...
:cyclops::cyclops:
No, you CAN do it, it's possible. It's just insanely difficult.
There are no drivers. There is no source code. You'll need to write a UEFI bootloader - which is also possible: it was done with HTC HD2.
And don't give me that bull**** about Microsoft suing you - if somebody wants to do this, they'll do it, and no legal department will stop them.
SilverHedgehog said:
No, you CAN do it, it's possible. It's just insanely difficult.
There are no drivers. There is no source code. You'll need to write a UEFI bootloader - which is also possible: it was done with HTC HD2.
And don't give me that bull**** about Microsoft suing you - if somebody wants to do this, they'll do it, and no legal department will stop them.
Click to expand...
Click to collapse
The intellectually dishonest correlation to the HD2 needs to be put out to pasture as it really bears no relevance.
And you're absolutely right... laws don't deter thieves, or anyone else who is determined to act in a particular manner. Anything and everything outside of the law can get rationalized by someone determined to do it. If laws were alone were an adequate deterrent, then there would be no need for punitive measures. In the case of MS, they have a proven track record of aggressively litigating worldwide when it comes to whatever they consider to be their flagship software at that given time. Far from "bull****", it's quantifiable and qualifiable.
Sent from my Nexus 7 using Tapatalk 2
najaboy said:
The intellectually dishonest correlation to the HD2 needs to be put out to pasture as it really bears no relevance.
And you're absolutely right... laws don't deter thieves, or anyone else who is determined to act in a particular manner. Anything and everything outside of the law can get rationalized by someone determined to do it. If laws were alone were an adequate deterrent, then there would be no need for punitive measures. In the case of MS, they have a proven track record of aggressively litigating worldwide when it comes to whatever they consider to be their flagship software at that given time. Far from "bull****", it's quantifiable and qualifiable.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, this time they are making a new bootloader for UEFI to work. Just because it's a phone that used to run Windows doesn't mean that it's any easier.
I just hate that this place keeps telling people that things are impossible. Impossible and very difficult are two different things.
SilverHedgehog said:
No, this time they are making a new bootloader for UEFI to work. Just because it's a phone that used to run Windows doesn't mean that it's any easier.
I just hate that this place keeps telling people that things are impossible. Impossible and very difficult are two different things.
Click to expand...
Click to collapse
I don't believe it was ever stated to be impossible. At least I know I never termed it that. It is, as I've said, unfeasible for the aforementioned reasons. If someone's determined enough and is able to essentially build a the necessary drivers, bootloader, etc, they would have licked half the problem. The other half being the likely consequence of their endeavour.
The basic Takeaway for anyone sitting bdxdzxxuryack thinking that this is an eventuality is that
V :' dzxzzzsxsrz szr s
S. ent from my Nexus 7 using Tapatalk 2
Arsenal 'x
I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
http://forum.xda-developers.com/showthread.php?t=2001868
Everything will work fine. All that I have ever found not working is my employer's software developed only for the employees. No mass produced app will give you any trouble.
Enjoy CM10!
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
DroidBois said:
I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
You lose everything, including your home and first-born child.
In all seriousness, just about everything will work fine if you only root. Some custom ROMs do introduce incompatibility problems, but it's usually on a pretty small scale (an app here or there might not work if your ROM/kernel choice tweaks how the device handles graphics, for example). By and large, you should be fine, but be careful of certain content apps that will refuse to play on rooted devices.
SacGuru said:
Everything will work fine. All that I have ever found not working is my employer's software developed only for the employees. No mass produced app will give you any trouble.
Enjoy CM10!
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
Come now, you know that's not entirely true. Many stuck-up content providers won't support rooted devices, and you'll also get the standard "unsupported device" claim if you're rooted or have an unlocked bootloader from apps like Google Wallet. By and large though, OP, you should be fine.
Rirere said:
You lose everything, including your home and first-born child.
In all seriousness, just about everything will work fine if you only root. Some custom ROMs do introduce incompatibility problems, but it's usually on a pretty small scale (an app here or there might not work if your ROM/kernel choice tweaks how the device handles graphics, for example). By and large, you should be fine, but be careful of certain content apps that will refuse to play on rooted devices.
Come now, you know that's not entirely true. Many stuck-up content providers won't support rooted devices, and you'll also get the standard "unsupported device" claim if you're rooted or have an unlocked bootloader from apps like Google Wallet. By and large though, OP, you should be fine.
Click to expand...
Click to collapse
You are right, but I was responding to what the OP had asked. Movies from play will work just fine afaik. And yes, there would be some app developers who won't support modified devices (I've heard of some trouble with the Sky tv app), but then again on some devices there are ways to temporarily unroot to allow such apps to run.
Again, how the device handles graphics can be modified as well. I had trouble with the Naked Browser before I modified the dpi using an xposed framework module.
In simple terms, so as to not confuse things, I would say that the huge majority of apps would give him no problems, and he would be missing out a lot if he refuses to root his device in the fear of one or two apps not working.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
You are right, but I was responding to what the OP had asked. Movies from play will work just fine afaik. And yes, there would be some app developers who won't support modified devices (I've heard of some trouble with the Sky tv app), but then again on some devices there are ways to temporarily unroot to allow such apps to run.
Again, how the device handles graphics can be modified as well. I had trouble with the Naked Browser before I modified the dpi using an xposed framework module.
In simple terms, so as to not confuse things, I would say that the huge majority of apps would give him no problems, and he would be missing out a lot if he refuses to root his device in the fear of one or two apps not working.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
There's a fine line between "not confus[ing] things" though and glossing over very real issues. It's significantly better for a new user to go into rooting aware of potential problems than rush in and get screwed on something because they expected rooting to be a land of sunshine, rainbows, and daisies, and found it was actually one that also had blood and tears.
That's especially true when you start getting into things like XPosed modules, which, while simple are much more than a new user should really have to contend with. Full stock+rooted is probably the safest introduction because it's so comparatively trivial to revert if you blow yourself up.
Rirere said:
There's a fine line between "not confus[ing] things" though and glossing over very real issues. It's significantly better for a new user to go into rooting aware of potential problems than rush in and get screwed on something because they expected rooting to be a land of sunshine, rainbows, and daisies, and found it was actually one that also had blood and tears.
That's especially true when you start getting into things like XPosed modules, which, while simple are much more than a new user should really have to contend with. Full stock+rooted is probably the safest introduction because it's so comparatively trivial to revert if you blow yourself up.
Click to expand...
Click to collapse
I know people who went on to custom roms the day they rooted their phones. I myself used one within a fortnight of using my first android device. Rooting isn't exactly rocket science.
I would really like to know what percentage of apps you believe do not work on custom roms/rooted phones out of all apps in the world. Impossible though it might be to have an exact number, I have a slight suspicion you have a larger-than-what-could-be-true figure in your head. While at it, do mention some of the blood and tears you have had while using your device.
In all the time I have been using android devices, I have only once encountered an app which I couldn't run on my device, and I believe that was purely due to lack of effort on my part.
Again, many people turn on to modifying their devices only because they want to use a custom rom, as the OP already wants to. I have never seen a comment by an user who regrets rooting his device as an app isn't working. I have seen numerous from users who are disappointed with the capabilities of their unrooted devices.
Had you understood my second comment, you would have realized that not only had I agreed with what you had said, I had also, unlike you, actually mentioned a couple of apps which might have problems on a rooted device. Glossing over issues might be wrong, but complicating simple questions is worse, in my opinion.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
I know people who went on to custom roms the day they rooted their phones. I myself used one within a fortnight of using my first android device. Rooting isn't exactly rocket science.
I would really like to know what percentage of apps you believe do not work on custom roms/rooted phones out of all apps in the world. Impossible though it might be to have an exact number, I have a slight suspicion you have a larger-than-what-could-be-true figure in your head. While at it, do mention some of the blood and tears you have had while using your device.
In all the time I have been using android devices, I have only once encountered an app which I couldn't run on my device, and I believe that was purely due to lack of effort on my part.
Again, many people turn on to modifying their devices only because they want to use a custom rom, as the OP already wants to. I have never seen a comment by an user who regrets rooting his device as an app isn't working. I have seen numerous from users who are disappointed with the capabilities of their unrooted devices.
Had you understood my second comment, you would have realized that not only had I agreed with what you had said, I had also, unlike you, actually mentioned a couple of apps which might have problems on a rooted device. Glossing over issues might be wrong, but complicating simple questions is worse, in my opinion.
Click to expand...
Click to collapse
You're starting to get a little touchy there.
I've been rooted and flashing ROMs for several years now, so I'm hardly new to the field. Nor do I think that there's even a large portion of apps out there that have trouble on rooted devices-- because that is not the point. From an end-user perspective, it only takes the loss of one app or a misbehaving one to ruin the experience. A great day-to-day example is Foldersync-- while the app "runs" correctly, if it detects you have root privileges it will spam superuser requests to perform a better sync. If you deny the request, your sync may fail, and if you accept it, the app potentially causes a wakelock. Random behavior can be just as bad as an outright crash.
OP's interest with ROMs is also a point of greater concern than just root. You really don't have to look too far to see people having problems, especially if you every venture outside of Nexus-land. The last hulabaloo I saw over this was back in the HTC One forums because a popular AOSP ROM had a misconfigured graphics driver that caused a few games to fall over and die.
As far as blood, sweat, and tears, try a bootlooping Galaxy Player 4.0 with a wiped /efs that was essentially softbricked for about two months before I had a free six or seven hours to manually dd everything back into place. I've also had my share of bootloops on Nexus devices while experimenting, although with a little fastboot or adb knowledge it's not hard to get out of them.
I have seen plenty of people regret their root or flash. I don't think you quite remember how bad the first bootloop or problem can be if you have never messed with this stuff before. Fastboot and adb are pretty easy to learn to use, but when you're first starting and every black screen seems like the death knell, it's a different matter altogether. Yes, I saw your post, and I understood, but it's a lot better to play it safe, especially at first, then charge ahead unaware of the consequences. Don't tell me you haven't seen people whining in countless ROM threads because they've done something stupid, usually because they didn't know not to.
Bottom line: better to play it safe and know than not. The only point I made up top was that you have to be 100% aware that you're playing with fire before you get burned. That doesn't mean fire isn't useful or that it's scary, but it does mean you have to be careful.
Edit
SacGuru said:
The whole point of my second post was that there are alternatives - to roms, to mods, to apps, to hardware limitations. The availability of these alternatives is amongst the prime reasons we love android, you and I.
The Op is not asking us about Softbricks/bootlooping devices, or black screens. He is asking only about apps. As I said before, I haven't yet seen a comment from someone who wants to unroot his device just because a particular app does not work. It might be possible that with your experience you might have seen one or two, but as you mention yourselves, people sometimes tend to be stupid.
It's unfortunate that I sounded touchy to you. My only answer to the Op still remains that it would be highly unlikely for him to have trouble with apps, even though there could be apps which do not work on modded phones (as I did mention in my very first comment).
Click to expand...
Click to collapse
I think we're reading the comment a little differently. This is why I brought up what I did.
I'm about to root my Nexus 10. Will I lose anything? Such as some Google Apps refusing to work like paid for movies or books or anything if it detects it's running on a rooted device?
Or do all Google and other apps still work fine?
Anything to watch out for? I'm considering Cyanogen, and will root with Mskip's tool.
Click to expand...
Click to collapse
Based on the questions being asked, I think it's reasonable to assume OP doesn't know anything about rooting or ROMs, so I'm being a little more liberal in looking at this comment than I would be otherwise. As such, I'd rather err on giving them information a little outside the original scope than too little.
Rirere said:
You're starting to get a little touchy there.
I've been rooted and flashing ROMs for several years now, so I'm hardly new to the field. Nor do I think that there's even a large portion of apps out there that have trouble on rooted devices-- because that is not the point. From an end-user perspective, it only takes the loss of one app or a misbehaving one to ruin the experience. A great day-to-day example is Foldersync-- while the app "runs" correctly, if it detects you have root privileges it will spam superuser requests to perform a better sync. If you deny the request, your sync may fail, and if you accept it, the app potentially causes a wakelock. Random behavior can be just as bad as an outright crash.
OP's interest with ROMs is also a point of greater concern than just root. You really don't have to look too far to see people having problems, especially if you every venture outside of Nexus-land. The last hulabaloo I saw over this was back in the HTC One forums because a popular AOSP ROM had a misconfigured graphics driver that caused a few games to fall over and die.
As far as blood, sweat, and tears, try a bootlooping Galaxy Player 4.0 with a wiped /efs that was essentially softbricked for about two months before I had a free six or seven hours to manually dd everything back into place. I've also had my share of bootloops on Nexus devices while experimenting, although with a little fastboot or adb knowledge it's not hard to get out of them.
I have seen plenty of people regret their root or flash. I don't think you quite remember how bad the first bootloop or problem can be if you have never messed with this stuff before. Fastboot and adb are pretty easy to learn to use, but when you're first starting and every black screen seems like the death knell, it's a different matter altogether. Yes, I saw your post, and I understood, but it's a lot better to play it safe, especially at first, then charge ahead unaware of the consequences. Don't tell me you haven't seen people whining in countless ROM threads because they've done something stupid, usually because they didn't know not to.
Bottom line: better to play it safe and know than not. The only point I made up top was that you have to be 100% aware that you're playing with fire before you get burned. That doesn't mean fire isn't useful or that it's scary, but it does mean you have to be careful.
Click to expand...
Click to collapse
The whole point of my second post was that there are alternatives - to roms, to mods, to apps, to hardware limitations. The availability of these alternatives is amongst the prime reasons we love android, you and I.
The Op is not asking us about Softbricks/bootlooping devices, or black screens. He is asking only about apps. As I said before, I haven't yet seen a comment from someone who wants to unroot his device just because a particular app does not work. It might be possible that with your experience you might have seen one or two, but as you mention yourselves, people sometimes tend to be stupid.
It's unfortunate that I sounded touchy to you. My only answer to the Op still remains that it would be highly unlikely for him to have trouble with apps, even though there could be apps which do not work on modded phones (as I did mention in my very first comment). Somehow your answer seemed pretty similar to mine ('just about everything would be fine'), so I just wondered why you had to mention to me problems with apps like the google wallet which are easily fixed.
By now, I am sure both of us understand what the other is talking about. Also, the op has enough info to take a decision on his own. My only qualm is that the inclusion of some seemingly complex terminology might turn him off rooting his device
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Wow... I just love you guys so much... So much detailed analysis here..
I've rooted all my devices in the past and generally not had any issues if I use a mature solid tool and ROM, I've only had issues with more 'pioneering' ROM's and tools, but for good reason. So I try to stick to the stable well tested mature varieties like Cyanogen and well supported tools, generally where the developer gets some payment (as reward encourages good development).
I'm more concerned with anything like content apps so Google Books / Magazines / Movies / Zinio etc or any other apps that may kick a stink about running on a rooted device?
Spotify seems fine on a rooted device so far though (Nexus 4).
It may not be an issue for some, but I am one of the (possibly rare?) people who PAY for content - specifically reading material. And I have an extensive library so I don't want to lose that.
I'm not so concerned on the technical front as the Nexus should be fairly well community supported and understood mainstream devices and likely to have stable development and mature community support.
I have the mskip tool ready to go so I'm fine with that.
It's not a debate about rooting vs not. I always root because simple things like having a quick tile for WLAN AP can make a HUGE difference through the day as opposed to this retarded idea that people ENJOY diving deep through menu layers for simple on / off functions - it drives me completely and utterly insane over the course of a day. So I like to set up and streamline my device how I need it, and even have accurate time with root tools like ClockSync, or better security support to lock out spyware crap like FaceSpy and so on (if root helps) and also, being able to properly back up my phone.
Or employer mandated junk like Afaria that some companies mandate for BYOD-to-work devices, not that I have any idea what it's for as opposed to a trusted workable solution like Google Apps (I guess everyone has to make their own thing to put their own buggy bloated stamp on everything). Will that mandated junk still work?
The biggest problem I have still is this MTP *CRAP* which which I believe you can't work around? That's another story and Google should be shot for this.
But root vs not has little to do with that. I guess we're stuck with this MTP crap no matter what we do (thanks Google, you tools).
Thanks for the advice here though.
DroidBois said:
Wow... I just love you guys so much... So much detailed analysis here..
I've rooted all my devices in the past and generally not had any issues if I use a mature solid tool and ROM, I've only had issues with more 'pioneering' ROM's and tools, but for good reason. So I try to stick to the stable well tested mature varieties like Cyanogen and well supported tools, generally where the developer gets some payment (as reward encourages good development).
I'm more concerned with anything like content apps so Google Books / Magazines / Movies / Zinio etc or any other apps that may kick a stink about running on a rooted device?
Spotify seems fine on a rooted device so far though (Nexus 4).
It may not be an issue for some, but I am one of the (possibly rare?) people who PAY for content - specifically reading material. And I have an extensive library so I don't want to lose that.
I'm not so concerned on the technical front as the Nexus should be fairly well community supported and understood mainstream devices and likely to have stable development and mature community support.
I have the mskip tool ready to go so I'm fine with that.
It's not a debate about rooting vs not. I always root because simple things like having a quick tile for WLAN AP can make a HUGE difference through the day as opposed to this retarded idea that people ENJOY diving deep through menu layers for simple on / off functions - it drives me completely and utterly insane over the course of a day. So I like to set up and streamline my device how I need it, and even have accurate time with root tools like ClockSync, or better security support to lock out spyware crap like FaceSpy and so on (if root helps) and also, being able to properly back up my phone.
Or employer mandated junk like Afaria that some companies mandate for BYOD-to-work devices, not that I have any idea what it's for as opposed to a trusted workable solution like Google Apps (I guess everyone has to make their own thing to put their own buggy bloated stamp on everything). Will that mandated junk still work?
The biggest problem I have still is this MTP *CRAP* which which I believe you can't work around? That's another story and Google should be shot for this.
But root vs not has little to do with that. I guess we're stuck with this MTP crap no matter what we do (thanks Google, you tools).
Thanks for the advice here though.
Click to expand...
Click to collapse
I've not had any problems with Google Play services and root, although most of my books are sideloaded after ripping DRM off of Amazon purchases (I don't really believe in the idea of a "perpetual lease"). As someone who has spent time working on that "employer junk" for corporate use, it may annoy the living **** out of you as a rooted user, but from a corporate standpoint it's actually pretty damn important.
Now, as far as MTP goes, don't quote me on this, but I remember seeing a setting in DriveDroid a while back (it's an app that lets you mount an ISO on your computer by connecting your device) that would let you change your USB connection mode to something other than MTP/PTP. I dont' remember the acronym, unfortunately, but it was a lot more in line with the way a "standard" USB device would connect (with the attendant issues of not using FUSE).
Without root, can I make a backup, that will allow me to restore to a previous point in time? That means my apps and their data, and my customizations. That means NOT OTA to some pirate's server.
Thanks!
IT_Architect said:
Without root, can I make a backup, that will allow me to restore to a previous point in time? That means my apps and their data, and my customizations. That means NOT OTA to some pirate's server.
Thanks!
Click to expand...
Click to collapse
Without root, you can't backup system apps and data. You can backup user apps and data. In fact...Google will do it for you by having Google backup your app data (since Google Play already has the apps). Settings-General-Backup
Sent from my Note 3 via Tapatalk
donc113 said:
Without root, you can't backup system apps and data. You can backup user apps and data. In fact...Google will do it for you by having Google backup your app data (since Google Play already has the apps). Settings-General-Backup
Click to expand...
Click to collapse
How do I determine exactly which are user apps and data, and which are system apps and data? I would envision:
1. I could restore any apps and data that didn't come with the phone.
2. Not restored would be shortcuts created, screen organization, customized wall papers, custom widgets, settings for WiFi, POP, IMAP, or Exchange E-Mail accounts, SMS/MMS messages, and any changes made in the phone's Settings from factory defaults.
I would also assume that programs such as Holo and Helium leverage the same underlying technology with the option of doing it locally.
Thanks!
IT_Architect said:
How do I determine exactly which are user apps and data, and which are system apps and data? I would envision:
1. I could restore any apps and data that didn't come with the phone.
2. Not restored would be shortcuts created, screen organization, customized wall papers, custom widgets, settings for WiFi, POP, IMAP, or Exchange E-Mail accounts, SMS/MMS messages, and any changes made in the phone's Settings from factory defaults.
I would also assume that programs such as Holo and Helium leverage the same underlying technology with the option of doing it locally.
Thanks!
Click to expand...
Click to collapse
Pretty much anything you can't uninstall is a system app.
To your 1 & 2 items above...yes to both.
No idea what Holo or Helium programs are.
Sent from my Note 3 via Tapatalk
So you actually have a valid reason not to root? You can install SS, do backups, etc. You can root cloak if you want. Odin back to stock if you need to.
Or you can use the slow, bloated, gimped, and otherwise poor excuse of a stock ROM for your DD. not sure why you would want that backed up anyway?
xdadevnube said:
So you actually have a valid reason not to root?
Click to expand...
Click to collapse
It's a brand new phone under warranty, support when needed, automatic OTA updates...
xdadevnube said:
You can install SS, do backups, etc. You can root cloak if you want. Odin back to stock if you need to.
Click to expand...
Click to collapse
Which leaves the KNOX counter at 0x1. There is no exploit to use in KitKat like there was in Jelly Bean and prior.
xdadevnube said:
...bloated, gimped, and otherwise poor excuse of a stock ROM for your DD. not sure why you would want that backed up anyway?
Click to expand...
Click to collapse
I'm accustomed to being able to do a bare metal restore to a previous point in time with my current phone. It has worked several times when things went bad, and I could even restore to a new phone of the same model if that were necessary. I'm trying to duplicate that as much as possible of that with Android.
Situation: I've installed two products, one called Holo, previous named Carbon, and the other called Helium. With Holo, which runs on the PC, I just did a full backup via USB 3 to my laptop. It says it can do the system apps and data too, but doesn't recommend doing it, so I didn't. I then deleted the data and applications through Application Manager. After that, I did a full restore. The apps and data were exactly like they were. Helium I'm guessing uses the same API, but is installed on the phone, and backs up to the SD card. I don't have an SD card yet, and I didn't want to use the one that Android emulates when it doesn't have one, so I haven't tested that one yet. The advantage of Helium is it allows you to select what you want to backup and restore. It doesn't allow backing up any system apps or data.
I'm currently documenting the changes I make to settings while it is all fresh in my mind, so if I do have to do a factory reset later, I can get back to where I was as painlessly as possible. I will do a factory reset tonight to prove the backups work, before I rely on Holo's restores.
Other: I've used custom ROMs in the past. I always ended up returning to the factory ROM due to fewer bugs, and compatibility issues that I encountered when installing programs that needed something the developer removed. The reason rooting Android is tempting for me, is that I'm missing the basic functionality of being able to do call recording while I'm on Bluetooth. OTOH, I can understand why Samsung will not support a phone that has been rooted.
Thanks!
Im not sure why you say that the Knox counter will be tripped. I have had my phone rooted since almost the day I got it when it was on MJE, upgraded it to NC4 after root was available and even just odined it back to stock at the beginning of this week. Screen was cracked and I got a replacement. I had to return the old one and when it got dropped in the mail, it was no longer rooted, fully stock, and a Knox counter of 0x0. This replacement phone with Kit Kat (NC4) on it was rooted withing hours of receiving it, nandroid restored to the identical setup as the phone it was replacing, and the Knox counter is, you guessed it, 0x0.
mikeyk101 said:
Im not sure why you say that the Knox counter will be tripped. I have had my phone rooted since almost the day I got it when it was on MJE, upgraded it to NC4 after root was available and even just odined it back to stock at the beginning of this week. Screen was cracked and I got a replacement. I had to return the old one and when it got dropped in the mail, it was no longer rooted, fully stock, and a Knox counter of 0x0. This replacement phone with Kit Kat (NC4) on it was rooted withing hours of receiving it, nandroid restored to the identical setup as the phone it was replacing, and the Knox counter is, you guessed it, 0x0.
Click to expand...
Click to collapse
Please tell me how to do that, or point to where I can learn how.
IT_Architect said:
Please tell me how to do that, or point to where I can learn how.
Click to expand...
Click to collapse
I just did a chat with One Click Root, which went as follows:
ME: I just purchased a new Verizon Note 3 with the newest KitKat. I don't want to mess up the warranty or support. However, an unrooted phone cannot record calls under Bluetooth. I heard there was a problem with rooting phones with KitKat with files after some date in June. I also want to be able to unroot if necessary for update and warranty purposes. Can One Click Root accomplish these goals?
One Click Root: Warranty will be voided if you root your device and ota updates will remove the root totally. I don't actually know if warranty will be back if you unroot your device.
ME: What about KNOX?
One Click Root: Won't be affected.
ME: How much does One Click Root cost if I decide to do this?
One Click Root: We have 2 packages to choose from: $29.95 package which includes root only and $39.95 which includes rooting + removal of bloatware + 30 days free tech support.
ME: I'm guessing the $39.95 for the tech support would be worth it. The removal of bloatware might not since if I did, and unrooted it to get an OTA update, the update would fail if the bloatware were not there to be patched.
One Click Root:We need to check first if your device is rootable. May I know the exact model number and android version?
ME: OK, I'm going into settings now...
One Click Root: Great! Your device is rootable.
ME: You've helped me TONS! I will make sure I want to do this, but you can be sure here is will I come when I do. I need to learn a little more about rooting, unrooting, and being able to get it back to factory so I can get service if I need it.
Click to expand...
Click to collapse
My question is how/where can I learn how to be able to achieve this?
mikeyk101 said:
...I have had my phone rooted since almost the day I got it when it was on MJE, upgraded it to NC4 after root was available and even just odined it back to stock at the beginning of this week. Screen was cracked and I got a replacement. I had to return the old one and when it got dropped in the mail, it was no longer rooted, fully stock, and a Knox counter of 0x0. This replacement phone with Kit Kat (NC4) on it was rooted withing hours of receiving it, nandroid restored to the identical setup as the phone it was replacing, and the Knox counter is, you guessed it, 0x0.
Click to expand...
Click to collapse
Thank you!
Maybe Im missing what you are asking. There are several threads on here that detail what to do. To root, use towelroot and it will cost you nothing. Then you will have to install SuperSU but make sure to use 2.13 version. This will also give you the option to disable Knox. Then install busybox and finally you can install safestrap.
mikeyk101 said:
...To root, use towelroot and it will cost you nothing.
Click to expand...
Click to collapse
Doesn't it make more sense to use "One Click Root" instead since it allows unrooting?
mikeyk101 said:
Then you will have to install SuperSU but make sure to use 2.13 version. This will also give you the option to disable Knox.
Click to expand...
Click to collapse
Will do
mikeyk101 said:
Then install busybox, and finally you can install safestrap.
Click to expand...
Click to collapse
Got it. I will look for more threads about this. Thanks TONS!
Supersu also allows you the option to do a full unroot as well.
mikeyk101 said:
Supersu also allows you the option to do a full unroot as well.
Click to expand...
Click to collapse
Got it!
Thanks!
xdadevnube said:
So you actually have a valid reason not to root? You can install SS, do backups, etc. You can root cloak if you want. Odin back to stock if you need to. Or you can use the slow, bloated, gimped, and otherwise poor excuse of a stock ROM for your DD. not sure why you would want that backed up anyway?
Click to expand...
Click to collapse
I'm not there yet, but I'm drifting closer to your way of thinking. However, from what I read, custom ROMs have shorter battery life and S-Pen problems. I'm not after a hot rod. I'm after usable, as in not crippled.
I'd like to see a Windows 8.1 ROM for it like is on the Surface Pro 2. Android and IOS are just too limited.
IT_Architect said:
I'm not there yet, but I'm drifting closer to your way of thinking. However, from what I read, custom ROMs have shorter battery life and S-Pen problems. I'm not after a hot rod. I'm after usable, as in not crippled.
I'd like to see a Windows 8.1 ROM for it like is on the Surface Pro 2. Android and IOS are just too limited.
Click to expand...
Click to collapse
If you want Windows....have your boss get you a Nokia. You will never see a Windows ROM on a Note.....talk about a bloated and crippled OS.
Sent from my Note 3 via Tapatalk
donc113 said:
If you want Windows....have your boss get you a Nokia. You will never see a Windows ROM on a Note.....talk about a bloated and crippled OS.
Click to expand...
Click to collapse
I think we have different expectation in how we want to use the phone. LOL!
I have been the CTO of two different tier-1 automotive suppliers, and now own my own IT company, so I am the boss. They haven't made Windows phones in a while. The last Windows phone was Windows Mobile, at which time they were big player. There isn't a trace of Windows in "Windows Phone #x". It's their old game console, with a phone added. Microsoft used the same game console operating system in the tablet market and failed miserably until they put Windows on it with the Surface Pro 2. It will be no different with phones.
With the power coming to p;hones and tablets, this year I got interested in settling on a device that the guys could carry off duty to do emergency tech support when we get a server alarm or frantic call while in the mall. We currently use laptops and Dell XPS 12 convertibles and Windows Mobile phones, which I even had myself until recently. PMing with a developer at XDA that I've worked with over the years, he also laments about the loss of Windows as the most productive and capable development environment, but things are what they are. The problem with the old phones was the small screen and slow data speeds make them something you only use in emergencies. The upside is they did in 2009 everything that the new phones aspire to. I have been attempting to duplicate their capabilities in either IOS or Android. Now that the Note series and Android have achieved parity in the handwriting recognition and speech to text, an HD screen, a usable RDP client, SFTP Terminal and file manager apps, it has shown itself to be usable for us in that role. I have no interest in root per se, in fact I'd rather not because playing with phones is not what we do. I'm simply attempting to fill in the few remaining usability shortfalls. The most major is call recording that works the same whether on or off Bluetooth. Another one we would like to have back is bare metal restores.
Thanks!
IT_Architect said:
I think we have different expectation in how we want to use the phone. LOL!
I have been the CTO of two different tier-1 automotive suppliers, and now own my own IT company, so I am the boss. They haven't made Windows phones in a while. The last Windows phone was Windows Mobile, at which time they were big player. There isn't a trace of Windows in "Windows Phone #x". It's their old game console, with a phone added. Microsoft used the same game console operating system in the tablet market and failed miserably until they put Windows on it with the Surface Pro 2. It will be no different with phones.
With the power coming to p;hones and tablets, this year I got interested in settling on a device that the guys could carry off duty to do emergency tech support when we get a server alarm or frantic call while in the mall. We currently use laptops and Dell XPS 12 convertibles and Windows Mobile phones, which I even had myself until recently. PMing with a developer at XDA that I've worked with over the years, he also laments about the loss of Windows as the most productive and capable development environment, but things are what they are. The problem with the old phones was the small screen and slow data speeds make them something you only use in emergencies. The upside is they did in 2009 everything that the new phones aspire to. I have been attempting to duplicate their capabilities in either IOS or Android. Now that the Note series and Android have achieved parity in the handwriting recognition and speech to text, an HD screen, a usable RDP client, SFTP Terminal and file manager apps, it has shown itself to be usable for us in that role. I have no interest in root per se, in fact I'd rather not because playing with phones is not what we do. I'm simply attempting to fill in the few remaining usability shortfalls. The most major is call recording that works the same whether on or off Bluetooth. Another one we would like to have back is bare metal restores.
Thanks!
Click to expand...
Click to collapse
Hummm.....haven't made a Windows Phone in years? I suggest you look at this site:
http://www.windowsphone.com/en-us
You wanna do "bare metal" recoveries? Just root and it's a piece of cake.
Oh...my background? I did some programming in this new fun language called BASIC in 1963, then moved on to FORTRAN in '68. Switched carreers in '70 so didn't get back to programming until early 80s and that was pure assembly language. Then C and then converting COBOL to SQL.
I had more fun with hardware so became a UNIX System Administrator and Oracle DBA in the mid 80s.
Retired in late 90's from my government job and worked for 14 years as a UNIX SA, Sybase DBA and Window's Administrator for British Telecom here in the US in the VideoConferencing nitch.
So I kind of have a computing background and in my experience, most CTO's come from the sales and marketing side of the business, not the technical side.
Obviously I have no idea if any of the above applies to you.
Sent from my Note 3 via Tapatalk
IT_Architect said:
I think we have different expectation in how we want to use the phone. LOL!
I have been the CTO of two different tier-1 automotive suppliers, and now own my own IT company, so I am the boss. They haven't made Windows phones in a while. The last Windows phone was Windows Mobile, at which time they were big player. There isn't a trace of Windows in "Windows Phone #x". It's their old game console, with a phone added. Microsoft used the same game console operating system in the tablet market and failed miserably until they put Windows on it with the Surface Pro 2. It will be no different with phones.
With the power coming to p;hones and tablets, this year I got interested in settling on a device that the guys could carry off duty to do emergency tech support when we get a server alarm or frantic call while in the mall. We currently use laptops and Dell XPS 12 convertibles and Windows Mobile phones, which I even had myself until recently. PMing with a developer at XDA that I've worked with over the years, he also laments about the loss of Windows as the most productive and capable development environment, but things are what they are. The problem with the old phones was the small screen and slow data speeds make them something you only use in emergencies. The upside is they did in 2009 everything that the new phones aspire to. I have been attempting to duplicate their capabilities in either IOS or Android. Now that the Note series and Android have achieved parity in the handwriting recognition and speech to text, an HD screen, a usable RDP client, SFTP Terminal and file manager apps, it has shown itself to be usable for us in that role. I have no interest in root per se, in fact I'd rather not because playing with phones is not what we do. I'm simply attempting to fill in the few remaining usability shortfalls. The most major is call recording that works the same whether on or off Bluetooth. Another one we would like to have back is bare metal restores.
Thanks!
Click to expand...
Click to collapse
You can root and install safestrap and still retain your normal functionality. Only adding the options to backup and restore. I would root/install busybox/ install safestrap and wipe and flash the stock deodex version. Beans has a nice clean nc4 base posted. Before you end up with to much on your phone that you dont want to wipe it. You will also want to odin the nc2 kernel before booting up your custom setup for the first time. I can assure using the listed setup will keep superb battery life and all stock functions and features.
donc113 said:
...most CTO's come from the sales and marketing side of the business, not the technical side.
Click to expand...
Click to collapse
I've never heard of one that was in a Tier-1 Automotive supplier. BTW, I was also a CIO. Basically, when you are CIO, you are responsible for the direction and implementation of the corporate information structure. You do that after working with department heads and watching the department functions. You discuss your thoughts and direction with the CTO and flesh out the details. As CIO, you then budget the project. You keep the CFO in the loop on requirements, and for optimizations, you work with him to get him on board. During the board meetings, we hammered out the whens because it may be something not IT related makes the most sense to do first. Everyone also scrutinizes your plan and offer suggestions. The marketing side in a Tier-1 Automotive supplier is the sales team and/or organization, who work closely with the Engineering department for costs and timing. It really helps to be technical before you become a CIO.
Social life in high school for me was studying solid state electronics. In college studied automotive technology, and I designed an electronic ignition system for one teacher, and helped another who was writing a book to come up with the formula for calculating ratios for a compound planetary gear set. Prior to my CTO work, I also was military, but full-time guard, aircraft mechanic supervisor, then I bought a plane and learned to fly, then a military academy on an age waiver, then Signal Officer, which means wired and tower communications and COMSEC, then a command, then flight school on an age waiver, then served my commitment flying for the guard. Thus, in civilian life, they threw developing a Tool and Die CNC department, then sent me to their production plant to write an fully integrated ERP package. I used Faircom's C-Tree that time around, and wrote my own translator to use CB86 syntax. I also designed and built the electronic circuits for automation and was farmed out by them to, of all places, a large food distributor who needed a system to monitor their temperatures and gas on weekends so they didn't come back on Monday with thousands in loss. (Who was a friend of the owner) I started an Industrial Design company, only two of us, and did that for two years, but made a lot of money. Someone then made us an offer we couldn't refuse. One of the employees of one automotive supplier became part owner in another, that was in trouble from an IT standpoint and GM expectations, learned I was free, and they started taking me to lunch. I also authored a full ERP system for them, and we went from the cut list to the top 3% GM supplier rating. It was there I was featured in two national publications, one you may remember since you go back that far, was Application Development Trends. This was built on a DBMS. I publicly challenged Oracle at a developer conference on their query optimizer, and they could not deliver.
I enjoyed being high energy, but one day one a friend there said to me, "I have no idea why you do what you do. I would never do what you do even if I could." He got me thinking. I had lots of vacation time, but no time to take them. I wasn't sure of the ages of my kids or their birthdays. After a few months of thinking about it, I told them I was resigning to start my own business, and that I would give them 2 months before leaving. As the time approached, they said they wanted me to do a project, and if I finished it withing 5 months, they would pay me a sizable bonus, and pay me after I left for another 6 months to help start my new business. The CFO didn't think it was possible to get done in that time, and I wasn't too sure either, but I took the gamble. When they wanted to carve a week out of my time for another project, I then told them that they then also need to tack on a week to the 5 months, which they did. I was completely oblivious at the time how important my stipulation would be. It was implemented and in place, and working with only with just under 2 days to spare because I had to cancel 2 roll outs on other weekends for issues. (Shutting down GM can cost you your business) When I was about to get out, I had a daughter wise beyond her years show me her research about home schooling, and said she did that because she noticed how much more enjoyable it was to be around home school kids. I was concerned about socialization, but she did her homework, and in this area, they have a school, gym, and teachers for classes you can't do at home. There was far more socialization, and the kids were totally transformed in 6 months to being nice, with brothers and sisters tripping over themselves to help each other and others. In basketball, they mopped the Class A teams in our area, and finished 3rd Class D in the nation. They started college at 17, and Magna Cum Laude. I've been on my own for several years now. Well, they are gown up. It's easier to build and run a company than what I was doing. I have UNIX servers and one site that does 5 1/2 million unique visitors a month, so this may sound crazy, but I miss the board room and the pressures...and my dad tells me I am crazy to miss it. LOL! I think what I miss most is working with lots of people and lots of critical problems to solve. I also had fun as a speaker at quarterly meetings. While not every move I've made has been a good one, you don't know what works until you try. We seem to have a lot in common, and both like to learn. The chemistry, electronics, math, and physics has been fun to learn, but oddly, the most fun is working with people on projects, at the gym, or running. You may have some time over me, but I haven't been sitting still either.
Lest anyone believe that I had much of a hand in any of this, I will dispel that right now. There are heal marks from being dragged every place I've been. I bought a plane and learned to fly because when flying with them as a crew I would be sick for two days. One day a pilot took me aside and told me that he used to be just like me, and it took learning to fly to get over it. I went to a military academy because people encouraged me to, and that I needed to to achieve my potential. You can't name one thing in my life that didn't go similarly, and all of this happened from the Lord dragging me to through this to prove to me that through trust in Him, all things are possible. All I can say is it worked. An there is a huge thanks on my part to the people who spent time with me to give that opportunity, and I'm far from some religious or pious guy.
donc113 said:
There isn't a trace of Windows in "Windows Phone #x". It's their old game console, with a phone added. Microsoft used the same game console operating system in the tablet market and failed miserably until they put Windows on it with the Surface Pro 2. It will be no different with phones.
Click to expand...
Click to collapse
If you do a little research, you will see what happened there. You can also research and find that killing Windows Mobile was Steve Balmer's greatest regret. In his words, I put Microsoft way behind in this area. There are different kinds of users. Steve saw the boom in the gamey non-technical side, but he didn't have that market. He came late to the party using the gaming platform, but in doing so he lost his mobile business market and developers. Their developers were faced with one of two options, the closed platform of IOS and being Apple's slave, or the open Android market and fierce competition. The new Windows Phone couldn't even connect to Microsoft's own products, while the iPhone/IOS/BSD could. Things are better now, but until Microsoft comes back to the market with a real Windows phone to tie the Enterprise, desktop, and cloud back together, Google will be the Microsoft of mobile devices, and Apple will be happy with their high-end 15%.
donc113 said:
I had more fun with hardware...
Click to expand...
Click to collapse
And you AND I know darn well I shouldn't be playing with phones, but I have the same illness. Currently, we can wear our noise-cancelling Bluetooth and record conversations with customers. It's our note taker and we send them to each other to pick up on. It's a money saver when you confront someone with what they asked someone to do. Now add to that no backups after you get the phone all set the way you want it? I have NovaLauncher not because I don't like Touchwiz, it's because I can restore the setup without rooting, and Helium or Holo can do the non-embedded stuff, but the Bluetooth thing leaves me seething. As far as rooting goes, yes, that can be done, and it complicates things when one needs service. It just rubs me the wrong way when a phone built in 2009, using technology from 2002 (XP), can do what an Android phone from 2013 prevents me from doing without risking and hacking. With WinMo, when you did a factory reset, you actually got a factory reset. It erased everything on the phone, and copied back the factory operating system. I like to put things in place that are a thing of beauty, and get it behind me.
Of course what I really came here for, I don't have an answer for. LOL! How little can I get away with, when rooting a phone? Why do I want Safestrap when I don't want a custom ROM? Isn't just rooting, SuperSU, and Xpose all I want? This is new ground for me.
PS: I'm looking at the best way to root on another thread without messing up the warranty.
So guys,my company is implementing mobileiron on our company devices giving us the possibility to use my personal devices as well.
I have a j6 samsung device from the company and mine op 6t but which is rooted.
Could i install mobile iron in a rooted devices knowing that my company has a well established security and restrictions certificates etc (i dont know if i'm saying all this right) lol
Can't say for sure. But usually companies that use those types of security, you cannot be rooted as it technically opens ups the phone, making it less secure in their eyes. Not speaking from experience, just from what I've seen of say Blackberry Android phones. Known for security and are incredibly locked down and still have never been rooted.
If I am erroneous in some of thinking on this subject, it's again because I'm only basing it off what I've seen elsewhere
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
okbakaka said:
So guys,my company is implementing mobileiron on our company devices giving us the possibility to use my personal devices as well.
I have a j6 samsung device from the company and mine op 6t but which is rooted.
Could i install mobile iron in a rooted devices knowing that my company has a well established security and restrictions certificates etc (i dont know if i'm saying all this right) lol
Click to expand...
Click to collapse
I had mobile iron on my 6T with unlocked bootloader and root. It did work with limitations. It will show as a red light and that you do not meet security criteria, but you be able to use say company wifi, but not email. You need to talk to your IT department to see if they can assist. I re locked and un rooted myself recently as the benefits of root are not as great as they used to be.
Keep in mind that if you try to hide root/unlock from mobile iron you could be fired for it. Companies take security seriously in this day and age. Also the company apps are basically granting an administrator access level to your company so they can track your phone, know anything about any use of it, and wipe it at their pleasure. No way I would let a company get a toehold on my phone.
Only thing I can think of would be to try to hide root via Magisk. But yeah, I wouldn't screw around with security on a work device. My company would fire you immediately, not sure about yours.
My company would fire me if they know im trying to install mobile iron on rooted devices, lol.
Finally i used msm tool to back to stock and locked bootloader, i thought twice about root advantages and figured out that there is no great deals with root.
Many thanks for replies and suggestions