I asked this in the Jellybean Jellybomb thread, but that's far too fast moving and not necessarily a question about the ROM anyway (tied to root):
I've used the TeamEpic 'Root from Recovery' method to root my phone in the past, to enable wifi tethering as an emergency fallback only for a company-supplied MiFi that I carry on work trips.
This method results in Settings--> About Device showing "modified" status.
I believe this is directly tied to the following undesirable effects:
Google Wallet throwing 'unsupported' warnings and some transactions appear in 'unconfirmed' status, although technically "it works", this isn't good.
'Wifi Tether' app doesn't work more often than it does work (even following configuration suggestions on GS3-specific troubleshooting threads)
Because of these, I unrooted my device [also following the TeamEpic Root from Recovery thread, restore option].
However, since restoring, I've twice been prompted for an OTA update, and both have failed.
And since I'm now interested in installing a custom JB ROM (or manually apply an update, if I don't), I'll need to root again at any rate.
Simple questions:
Is there a root method that doesn't result in the phone showing a 'modified' status in Settings --> About Device?
If not, is there a mod that can be applied to stop Wallet from showing warnings and 'unconfirmed' transaction statuses that don't appear when the device is not rooted?
Note: Triangle Away disclaimers it does not change 'modified' status - and did not on ICS.
Note: I follow the precautions on the Wallet sticky for both rooting and unrooting. This thread does not discuss a solution.
Any help is appreciated, even if the answer is "no, you can't work around either of those".
Thanks in advance!
geolemon said:
I asked this in the Jellybean Jellybomb thread, but that's far too fast moving and not necessarily a question about the ROM anyway (tied to root):
I've used the TeamEpic 'Root from Recovery' method to root my phone in the past, to enable wifi tethering as an emergency fallback only for a company-supplied MiFi that I carry on work trips.
This method results in Settings--> About Device showing "modified" status.
I believe this is directly tied to the following undesirable effects:
Google Wallet throwing 'unsupported' warnings and some transactions appear in 'unconfirmed' status, although technically "it works", this isn't good.
'Wifi Tether' app doesn't work more often than it does work (even following configuration suggestions on GS3-specific troubleshooting threads)
Because of these, I unrooted my device [also following the TeamEpic Root from Recovery thread, restore option].
However, since restoring, I've twice been prompted for an OTA update, and both have failed.
And since I'm now interested in installing a custom JB ROM (or manually apply an update, if I don't), I'll need to root again at any rate.
Simple questions:
Is there a root method that doesn't result in the phone showing a 'modified' status in Settings --> About Device?
If not, is there a mod that can be applied to stop Wallet from showing warnings and 'unconfirmed' transaction statuses that don't appear when the device is not rooted?
Note: Triangle Away disclaimers it does not change 'modified' status - and did not on ICS.
Note: I follow the precautions on the Wallet sticky for both rooting and unrooting. This thread does not discuss a solution.
Any help is appreciated, even if the answer is "no, you can't work around either of those".
Thanks in advance!
Click to expand...
Click to collapse
If you still have a custom recovery (twrp,cwm) ota update will fail and I believe that's tied to the modified status.
Because your modified Google wallet will always say UN supported device.
Since you want to flash a custom rom , your device will say modified and Google wallet will have that message.
Only way around it is to go completely stock including recovery and stay that way.
This is afaik, I could be completely wrong I'm my assuming.
Sent from Pluto.
Speedin07si said:
If you still have a custom recovery (twrp,cwm) ota update will fail and I believe that's tied to the modified status.
Because your modified Google wallet will always say UN supported device.
Since you want to flash a custom rom , your device will say modified and Google wallet will have that message.
Only way around it is to go completely stock including recovery and stay that way.
This is afaik, I could be completely wrong I'm my assuming.
Sent from Pluto.
Click to expand...
Click to collapse
I don't have custom recovery. That's removed in the the "stock restore" process in the Team Epic 'root from recovery' (link is in the OP). Recovery is stock.
Also, If you look at the error issue thread link in the OP, I included screen captures of the error - they are captured in the stock recovery.
Ultimately, OTA updates are a non-issue if I'm re-rooting.
But if I am going to root again, I'd like to work around the 'modified' status and Wallet 'unconfirmed' status if at all possible.
Anyone have any information on those issues? I'm finding little discussion on it, other than a few comments that it's inherent with rooting - I'd like to determine if that's an absolute, or just inherent in the rooting method that I (and many others) have used.
Thanks in advance.
No, once u become "Modified" the only wsy to return is to use an Odin installable. It does not matter if u install a custom recovery, root, unroot and reinstall stock recovery. Once u are modified u stay that way until u reinstall everything through Odin which you will then see Normal.
Sent from my SPH-L710 using Tapatalk 2
billard412 said:
No because being rooted makes it say that. A system check is done on every startup. It will say that if it finds superuser, su or busybox present anywhere in the system
Click to expand...
Click to collapse
I asked your question in the Android Development forum. This is the answer I got.
Sent from my SPH-L710 using XDA Premium HD app
EPayne123 said:
No, once u become "Modified" the only wsy to return is to use an Odin installable. It does not matter if u install a custom recovery, root, unroot and reinstall stock recovery. Once u are modified u stay that way until u reinstall everything through Odin which you will then see Normal.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After I restored using the reversal procedure for the TeamEpic 'root from recovery' process (here, for reference - third "Link"). I did use Odin, both for rooting and restoring back.
My phone no longer shows Modified,and Google Wallet has no issues or messages.
I'm simply looking to avoid it if at all possible, if I root my phone again. I'm tempted to try a JB ROM.
If it is avoidable, I'll use that particular method of rooting.
If it is not avoidable (as so far seems to be the consensus, unfortunately), then no harm in using this process again - particularly being the majority method.
why? no effect on wallet's usability
EPayne123 said:
No, once u become "Modified" the only wsy to return is to use an Odin installable. It does not matter if u install a custom recovery, root, unroot and reinstall stock recovery. Once u are modified u stay that way until u reinstall everything through Odin which you will then see Normal.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Not true. For it to be normal you must be stock with a stock kernel, recovery doesn't matter. Cannot have superuser su or busybox present and your flash count must be 0. Then it will say normal. No Odin required
nicholaaaas said:
why? no effect on wallet's usability
Click to expand...
Click to collapse
Two reasons:
1) It's a bit like saying, having one burgundy interior door panel and a random blue glovebox door in your otherwise grey car interior doesn't impact driveability.
And it doesn't... but it does create a nagging "something isn't right" feeling that leaves you less comfortable and enjoying the drive less, and making needless excuses when you host passengers, than if your car was 100% correct.
2) While technically "it works", some transactions remain in an 'unconfirmed' status, where I'm not experiencing that at all with a stock device. One benefit of Wallet is the ability to track transactions, and while I haven't tried yet, could use an export of this to track spending. I'd like it to work as designed.
billard412 said:
Not true. For it to be normal you must be stock with a stock kernel, recovery doesn't matter. Cannot have superuser su or busybox present and your flash count must be 0. Then it will say normal. No Odin required
Click to expand...
Click to collapse
This is good info that sounds pretty close to a definition...
Is there a workaround for this?
I'd think someone would have possibly created a patch of sorts to change that specific logic to something else by now, if for no other reason than to avoid these sorts of issues - I'm speculating (but can't know) that this is also tied to why Wifi Tether app worked so sporadically (even with settings found in GS3-specific Wifi Tether troubleshooting threads) as well.
If rooted, obviously you need superuser...
Possibly you need busybox...
I believe there are methods of rooting that at least don't involve incrementing the Odin flash counter (I haven't used them).
Resolving one or two of the three won't be very useful however, from what you are saying.
Any thoughts on working around it? Does anyone know where this code specifically is?
Thanks-
I used Triangle away and reset the counter and then used the JB update from this thread:
http://forum.xda-developers.com/showthread.php?t=1941546
afterwards, I ended up with rooted JB, a count of zero, and triangle away states:
Current status
Counter: 0
Binary Official
Device: SPH-L710
I should try Triangle Away. I stopped at the disclaimer on the thread that it changing Modified status was "out of scope". So I didn't even try it.
Does your google Wallet show "unsupported device", out of curiosity?
Even if Triangle away fixes the modified system status(which it wont if you're rooted) Google wallet will definitely still say unsupported. It means just that,
It'll still work but dont try callin them for help because they dont support rooted devices as its a security risk. If its that big a deal try unrooting and running the phone stock with no modifications. Then youll have exactly what your lookin for
geolemon said:
Does your google Wallet show "unsupported device", out of curiosity?
Click to expand...
Click to collapse
Yes, it does.
billard412 said:
Even if Triangle away fixes the modified system status(which it wont if you're rooted) Google wallet will definitely still say unsupported.
Click to expand...
Click to collapse
What do you mean triangle away wont fix the modified status?
My SGS3 is rooted, with JB, with a flash count of zero, and a status of "official" like I stated before.
DCRocks said:
Yes, it does.
What do you mean triangle away wont fix the modified status?
My SGS3 is rooted, with JB, with a flash count of zero, and a status of "official" like I stated before.
Click to expand...
Click to collapse
Perfect information, thanks.
My main concern is with Wallet, less so the warning message, more so the 'unconfirmed' status I was seeing on transactions after rooting. May turn out not to be an issue - at least once I'm on a JB build, per my coworker:
I have other reasons for wanting to update as well -
I'm unimpressed with the battery life that I've been getting, and it's not due to a rogue app. For example, today so far my "Cell Standby" is 55% of my battery stats. A coworker of mine is also on Sprint, has installed one of the official Jellybean leaks, and his Cell Standby percentage is always single-digit.
He's also been using Wallet, and all of his transactions have been completing, none are showing the 'unconfirmed' status I was seeing with my stock, rooted, ICS experience.
I may root and try the Sonic ROM - I especially like the sounds of "killer battery life" in the OP.
Thanks for the help here, that really does help me a lot - obviously Wallet uses something deeper than the device's "modified" status to display that warning message.
I am stock rooted running JB and use Voodoo OTA Rootkeeper to "unroot" my phone as needed for certain apps. The Google Wallet app does not display the unsupported warning when I temporarily unroot using the app. If the unsupported message bothers you, you can always go this route.
Of course there is a way
freeza said:
Of course there is a way
Click to expand...
Click to collapse
Are you actually rooted, or also using Voodoo to temporarily unroot when you don't need it?
If that's not it, please share your method. I was just about to root using the root-from-recovery method, but I'll hold off for now pending learning your method.
Thanks.
freeza said:
Of course there is a way
Click to expand...
Click to collapse
But no reply of how?
That would be helpful.
Sent from my Nexus 7 using xda app-developers app
freeza said:
Of course there is a way
Click to expand...
Click to collapse
would like to know. my wife is enjoying your JB rom and just tried Wallet yesterday and came to me with that message. so i'd like to find a solution for her.
Related
Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
The image that is used in unrooting is a stock ROM. What I want to do is setup my phone - the way I want it with Mikfroyo - with all the tweaks etc and then "just do the unrooting part". If that makes any sense - I don't need any superuser permissions etc.
Long story short - can a phone be unrooted with a custom ROM instead of a stock ROM?
im pretty sure this is impossible dude, sorry, just leave it all rooted, whats the problem
I know you can't unroot and keep a custom ROM but I wonder if there is a way to hide the fact that you're rooted from the app. What kind of message pops up when you install it?
Sent from my PC36100 using XDA App
It just says that Good cannot run on a rooted phone and just locks the app - I have to call IT to get an unlock code using the device ID that is displayed in Good's pop-up message.
It has to be checking for something specific and I bet there is a way to fudge it but unfortunately that's outside my realm of understanding. I would ask one of the devs here about it.
What permissions does the App request when you install? It could just check for SuperUser
SSjon said:
What permissions does the App request when you install? If could just check for SuperUser
Click to expand...
Click to collapse
I which case you could either delete superuser or use it to block the app... perhaps?
I am sure its more complicated than that - if they are touting themselves as a replacement for blackberry security for iPhones and Android - I seriously doubt a simple fudging of the superuser permissions will deceive it. Also, I'd like to comply with my company's requirements for using an Android phone so I don't get into trouble.
So from what I understand - you cannot have a custom ROM on an unrooted phone. Thanks so much guys - I'll just have to learn to live with the bloated stockware and manual restores arghh......
It's not possible.... to unroot, you'd have to RUU, which returns the phone back to stock. And then, you'd have no way of flashing a custom rom unless you rooted again
ok this is one thing that I am starting to not understand here...
so many people when they answer - say "yes" it can be done or "no" it can not be done...
...ummm where is the why? It would be very informative to know such things or if someone has even tried said thing before.
like why can't you just run a ROM or other flash file from renaming the file and letting the stock loader do the flashing? ......answer: because the stock loader does a file signature check - see? that makes sense and answers the why. it also helps users to retain the information as well as understand it.
I would love to know why the OP can't just run the unrevoked s-on tool from here http://unrevoked.com/rootwiki/doku.php/public/forever#custom_splash (in the FAQ section) without removing his custom ROM and just make sure he doesn't use any apps that need the su access. sounds like it should work? has someone done this and found that it does not work? flashing back to s-on should just prevent flashing to any other ROM's I would think from everything I have read in this forum.
or once s-on is back does it also check the current ROM on the phone and would cause some issues? would be great information to know. because if the security only checks file signatures of flies to be flashed and not the current ROM it seems like the OP could do what he is wanting to.
well, just thought I would ask to see if I could gain some more understanding as to the mechanics of everything
It would be good to know if this works with Good for Enterprise. I am stuck on an SGS 2.1 with Telstra and want a non stock ROM but really need to use Good.
ushkand said:
Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
Click to expand...
Click to collapse
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html
bkrodgers said:
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html
Click to expand...
Click to collapse
My thoughts exactly
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
Thanks for the information. What is the ROM that you are using?
bkrodgers said:
Or maybe one of the temp root methods would work.
Click to expand...
Click to collapse
are there still temp root methods that work on the EVO?
I am using Mikfroyo 4.5.
Just came across this thread and was seeing if your GFE was still working? I have a DX and put a custom ROM and could not get it to work. I'm waiting for my new PIN and have removed SU to see if it works.
ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
I rooted my HTC Salsa to install apps2sd which is great, but what commands do i have to run and where to be able to rename su.apk ?
Thanks,
Mike
I recently had to unroot my phone for warranty purposes. Managed to get S-ON but there is still a Superuser Permission (the ninja guy) icon in my app drawer. I want to get rid of this entirely. I can't do so via Manage Applications and I can't use Titanium Back-Up cause that requires root.
Any help?
mapheG2 said:
I recently had to unroot my phone for warranty purposes. Managed to get S-ON but there is still a Superuser Permission (the ninja guy) icon in my app drawer. I want to get rid of this entirely. I can't do so via Manage Applications and I can't use Titanium Back-Up cause that requires root.
Any help?
Click to expand...
Click to collapse
Did you not flash a stock unrooted ROM as part of your unroot process?
If you did, you shouldn't still have the Superuser app.
You should be able to just remove it with "manage applications" in your settings, though...
I think you'll have to root again, remove the apk, and then unroot.
The Superuser apk is saved in the system/app directory which you no longer have permissions to modify.
gee one said:
I think you'll have to root again, remove the apk, and then unroot.
The Superuser apk is saved in the system/app directory which you no longer have permissions to modify.
Click to expand...
Click to collapse
I'm assuming he didn't unroot properly if he still has his ROM on the phone that isn't a perfectly stock unrooted one from a PC10IMG.
The proper unrooting process will completely wipe that system partition and install the stock unrooted ROM back on. He shouldn't have anything left over from rooting.
You're right. I didn't flash the stock ROM. I restored my original 2.2 ROM and then did the unrooting process there without flashing the PC10IMG file or whatever. Is there a possible way to remove it without rooting and unrooting?
I cannot remove the app through Manage Applications.
And I was wondering if this is much of a problem. I got the S-ON so technically, I'm not rooted.. I just have a Superuser.apk installed on my phone and it's widely available on the market. And, what are the chances that the employee checking to see if my device is rooted will enter in a gmail account and look through the apps? I'm gonna send it in as a factory restore. They'll just do the volume down+trackpad+power to see that S-OON right???
mapheG2 said:
You're right. I didn't flash the stock ROM. I restored my original 2.2 ROM and then did the unrooting process there without flashing the PC10IMG file or whatever. Is there a possible way to remove it without rooting and unrooting?
I cannot remove the app through Manage Applications.
And I was wondering if this is much of a problem. I got the S-ON so technically, I'm not rooted.. I just have a Superuser.apk installed on my phone and it's widely available on the market. And, what are the chances that the employee checking to see if my device is rooted will enter in a gmail account and look through the apps? I'm gonna send it in as a factory restore. They'll just do the volume down+trackpad+power to see that S-OON right???
Click to expand...
Click to collapse
Probably, yeah. I'd tend to say if you have S-ON you'll be fine. All they do is hook it up to their machine and reflash the stock RUU anyways.
Could just use psneuter, give adb temp root and remove the apk through adb.
Though it may not stick...
-Nipqer
Yea temproot might be easier if your worried. Are you getting a warranty replacement?
Sent from my T-Mobile G2 using XDA App
Yep, getting a warranty replacement cause my G2's screen is acting up. I'll be sure to record and take pictures of the quality of the phone and that the phone has S-ON before sending it in, in case they wanna play the card that I'm rooted because I have SuperUser.. I'll just say I saw SuperUser advertised on popular Android sites as a powerful tool but never got it to work or something... haha.
What are the chances that I'll get a brand new G2??
mapheG2 said:
What are the chances that I'll get a brand new G2??
Click to expand...
Click to collapse
0%. You'll get a refurb.
It better be a bomb ass refurbished......... I just can't take my phone this way anymore..
You know, you could hide the Superuser icon from the app drawer with LauncherPro. Obviously it can be viewed elsewhere on the phone, but with it hidden from the drawer it will be less conspicuous.
mapheG2 said:
It better be a bomb ass refurbished......... I just can't take my phone this way anymore..
Click to expand...
Click to collapse
The refurbs are usually pretty good. The one I got looked brand new. They don't send out jenky refurbs. They're "like new".
That is a little bit more assuring. I've been pretty bummed out because I've kept my phone in arguably mint condition just to have an issue like this make me have to send it in and get a refurbished... Hopefully the hinge will be tighter to my liking.
And yeah, I thought about hiding it with LauncherPro, but then that means I would have to leave my gmail account intact on the phone which I don't want to do. I plan on doing a factory reset when I send it in, so when they turn on the phone, they'll be prompted with the whole set-up thing. So I don't understand why they would go through that to look at my app drawer when they can simply check to see if I have S-ON. I decided that I don't want to re-root and un-root. I'm technically not rooted, and if anything, I was just a curious user who was told something by some friends who were into that development thing. What's root??
Why can't you reset install launcher pro then delete your g mail?
From the phone not the whole account lol
killj0y said:
Why can't you reset install launcher pro then delete your g mail?
Click to expand...
Click to collapse
I think mapheG2 prefers the google account not be associated with the phone at all... and this makes sense to me. I'm sure you'll be totally fine with S-ON. I've heard of many users sending multiple devices back with S-OFF - no attempt to hide anything - and they've not been billed. Moreover, I've heard that as long as you have security on - you're okay.
+1 to martonikaj's comment - refurbished phones are supposed to be "like new."
Ditamae said:
I think mapheG2 prefers the google account not be associated with the phone at all... and this makes sense to me. I'm sure you'll be totally fine with S-ON. I've heard of many users sending multiple devices back with S-OFF - no attempt to hide anything - and they've not been billed. Moreover, I've heard that as long as you have security on - you're okay.
+1 to martonikaj's comment - refurbished phones are supposed to be "like new."
Click to expand...
Click to collapse
as long as he's S-ON I'm 99% sure it'll be fine. Anyone can install Superuser from the market when they're not rooted, doesn't mean it works.
All HTC will do is open to the bootloader, see if its S-ON, then re-flash it with a stock setup and put it into the pile of 10000 other phones to be refurbished.
Hi all, I'm new to this phone, and new to Android in general. I've read up on rooting, but I'm still not clear on a couple of things:
1) Does flashing a new kernel like zedomax get rid of all the apps that are on there just to get root? I like quite a few of the apps that came from Sprint/Samsung, like Vlingo and all of the google apps, so I don't want to lose them.
2) In the CWM thread, it mentions that after loading CWM you can get root by loading a file linked in that thread. Does this mean that the phone is essentially the stock phone, with the exception of root and CWM as the recovery program? Is the stock ROM still on there until I choose to install other ROMs?
The only thing I'm really interested in for getting root is to run the Cisco VPN client from the app store. I don't mind tinkering around with new ROMs, but I don't want to lose any functionality or have a flakey phone where sometimes the radios don't work properly.
Thanks for the help.
shaklee3 said:
Hi all, I'm new to this phone, and new to Android in general. I've read up on rooting, but I'm still not clear on a couple of things:
1) Does flashing a new kernel like zedomax get rid of all the apps that are on there just to get root? I like quite a few of the apps that came from Sprint/Samsung, like Vlingo and all of the google apps, so I don't want to lose them.
2) In the CWM thread, it mentions that after loading CWM you can get root by loading a file linked in that thread. Does this mean that the phone is essentially the stock phone, with the exception of root and CWM as the recovery program? Is the stock ROM still on there until I choose to install other ROMs?
The only thing I'm really interested in for getting root is to run the Cisco VPN client from the app store. I don't mind tinkering around with new ROMs, but I don't want to lose any functionality or have a flakey phone where sometimes the radios don't work properly.
Thanks for the help.
Click to expand...
Click to collapse
Flashing a new kernel to get root access won't delete any data. About the only visible change is you will have an app called superuser. All data will remain unchanged. The best way to get root access is through ODIN, there are many tutorials on how to do this if you are unsure.
For your second question, unless you install a new rom, you will be left with the stock rom after gaining root access. You will also have cwm for recovery and superuser to give certain apps root access. Hope this helps, let me know.
Sent from my SPH-D710 using xda premium
Thanks, I really appreciate it. I'll give it a try tonight and let you know how it goes.
Thanks, I really appreciate it. I'll give it a try tonight and let you know how it goes.
Just so I'm clear, getting root access through ODIN, you're referring to downloading one of the zedomax kernels from part 4 here that roots the phone?:
http://forum.xda-developers.com/showpost.php?p=17617227&postcount=1
The stock kernel listed there doesn't look like it has root.
shaklee3 said:
Thanks, I really appreciate it. I'll give it a try tonight and let you know how it goes.
Just so I'm clear, getting root access through ODIN, you're referring to downloading one of the zedomax kernels from part 4 here that roots the phone?:
http://forum.xda-developers.com/showpost.php?p=17617227&postcount=1
The stock kernel listed there doesn't look like it has root.
Click to expand...
Click to collapse
I would follow the steps listed here :
http://www.addictivetips.com/mobile/how-to-root-sprint-epic-4g-touch-video-guide/
I did it this way, and it takes less than 10 min. Was running stock rom with no issues for a week but have now since flashed some custom ROMs. Let me know how it works out.
Sent from my SPH-D710 using xda premium
Is there a way I can root without downloading a whole rooted ROM? I don't want to do that for copyright reasons.
I searched and couldn't find an up-to-date insecure kernel for the E4GT (there is a ClockworkMod one from last year, but I expect that's too old). Since kernels are under GPL, modifying and re-distributing them (with source) is fair game.
p.s. I don't want this thread to switch to a discussion of the legal issues with copying and modifying the stock ROM. It may not be a big deal to many people, but I want to keep within the law as best I can.
Ya man head over to the developers section and download the e4gauto.bat file. That will auto root you from the existing rom you're on. It updates whatever stock kernel you have with a rooted stock kernel with CWM. from eg30 kernel to fd16 i think. Just make sure you have the drivers for your phone and plug it into the usb of your pc and go into applications on your phone to make sure you have usb debugging checks and accept files from unknown sources checked. Make sure your phone is not in usb mode and follow the prompts of the batch file. when it finishes running it will r boot your phone and you will have root and a custom recovery to flash roms with.
timmetal6669 said:
Ya man head over to the developers section and download the e4gauto.bat file. That will auto root you from the existing rom you're on. It updates whatever stock kernel you have with a rooted stock kernel with CWM. from eg30 kernel to fd16 i think.
Click to expand...
Click to collapse
I think this doesn't work on EL29.
arpruss said:
Is there a way I can root without downloading a whole rooted ROM? I don't want to do that for copyright reasons.
I searched and couldn't find an up-to-date insecure kernel for the E4GT (there is a ClockworkMod one from last year, but I expect that's too old). Since kernels are under GPL, modifying and re-distributing them (with source) is fair game.
p.s. I don't want this thread to switch to a discussion of the legal issues with copying and modifying the stock ROM. It may not be a big deal to many people, but I want to keep within the law as best I can.
Click to expand...
Click to collapse
What rom version do you have I believe its EL13 or lower sfhubs method does not require a rom to be downloaded...
Edit: sorry started this post 10 minutes ago and just saw responses... then your answer is No
Based on your previous thread, you want your *initial* root to
1) avoid yellow triangle
2) avoid flash count
3) avoid using rooted ROM
4) root a ROM where there is no existing exploit
This is not possible.
If you are willing to concede on 1&2, then just ODIN flash any GB-based kernel repacked with CWM. They will work with any GB-based ROM. It will trigger the yellow triangle and increase your flash count. You will need to reset those by other means if you care about it. Either USB jig or upgrade to ICS and use Triangle Away.
sfhub said:
Based on your previous thread, you want your *initial* root to
1) avoid yellow triangle
2) avoid flash count
3) avoid using rooted ROM
4) root a ROM where there is no existing exploit
This is not possible.
If you are willing to concede on 1&2, then just ODIN flash any GB-based kernel repacked with CWM. They will work with any GB-based ROM.
Click to expand...
Click to collapse
Thanks!
I actually don't care about 1, and I am willing to concede on 2, now that my 14-day in-store return period is almost over and I'm pretty happy with the phone (except maybe for a pinkish tinge along the middle section of the phone with the brightness turned very low with ScreenDim), which is why I asked this in a new thread.
I assume nobody has had any problems with flash-count and warranty service?
Where can I get an appropriate, safe, non-bricking GB-based kernel repacked with CWM?
Can I use Odin to back up the original kernel and restore it after rooting?
arpruss said:
I assume nobody has had any problems with flash-count and warranty service?
Click to expand...
Click to collapse
Most of the time no problem, but sometimes yes. Depends on who you get.
arpruss said:
Where can I get an appropriate, safe, non-bricking GB-based kernel repacked with CWM?
Click to expand...
Click to collapse
Use this:
http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
arpruss said:
Can I use Odin to back up the original kernel and restore it after rooting?
Click to expand...
Click to collapse
ODIN doesn't do backups. Your stock kernel is available in the Auto Root package (Option C) or in the Individual Components Reference Section (2nd Post) of the appropriate ODIN OneClick thread in my signature, provided here for your convenience:
http://forum.xda-developers.com/showpost.php?p=23478866&postcount=869
sfhub said:
Most of the time no problem, but sometimes yes. Depends on who you get.
Click to expand...
Click to collapse
Does the jig work to reset flash count on 2.3.6? One site that sells jigs says it only does that on 2.3.4 and below.
ODIN doesn't do backups. Your stock kernel is available in the Auto Root package (Option C) or in the Individual Components Reference Section (2nd Post) of the appropriate ODIN OneClick thread in my signature, provided here for your convenience:
http://forum.xda-developers.com/showpost.php?p=23478866&postcount=869
Click to expand...
Click to collapse
Thanks!
Presumably, I can also build it from source.
Wow. . Just wow.
Sent from my SPH-D710 using Tapatalk 2
arpruss said:
Thanks!
I actually don't care about 1, and I am willing to concede on 2, now that my 14-day in-store return period is almost over and I'm pretty happy with the phone (except maybe for a pinkish tinge along the middle section of the phone with the brightness turned very low with ScreenDim), which is why I asked this in a new thread.
I assume nobody has had any problems with flash-count and warranty service?
Where can I get an appropriate, safe, non-bricking GB-based kernel repacked with CWM?
Can I use Odin to back up the original kernel and restore it after rooting?
Click to expand...
Click to collapse
Go Spend $2 on ebay for a USB Jig. Best two bucks I ever spent.
By the way, I had a quick look at Samsung's official warranty information, and it says nothing about it being voided by rooting or other unauthorized modifications. Of course, it exempts "defects or damage resulting from improper testing, operation, maintenance, installation, service, or adjustment not furnished or approved by SAMSUNG", but that's only applicable when the damage results from rooting.
Of course, Sprint does have the authority to cut off one's service for rooting (or for any other thing they see fit).
arpruss said:
Does the jig work to reset flash count on 2.3.6? One site that sells jigs says it only does that on 2.3.4 and below.
Click to expand...
Click to collapse
Has nothing to do with Android ROM version. It has to do with your bootloader version. If your phone came with EK02 or EL29, jig will not reset stats, but will get you to ODIN download mode. You'll need to flash EG30/31 bootloader to restore functionality. Look in the wiki if you need it.
sfhub said:
Has nothing to do with Android ROM version. It has to do with your bootloader version. If your phone came with EK02 or EL29, jig will not reset stats, but will get you to ODIN download mode. You'll need to flash EG30/31 bootloader to restore functionality. Look in the wiki if you need it.
Click to expand...
Click to collapse
Ah, but that then runs into my pickiness about copyright, because presumably the bootloader is copyrighted by Samsung, and is not under the GPL. :-(
Well, maybe I just need to take my risk about warranty.
There can be a difference between what the warranty says (or what is enforceable) and what your real-life experience is.
That is why I said most of the time no problem, but sometimes yes. The people you communicate with are humans and they don't always interpret the same set of rules the same way.
What is written is theoretically what you would eventually end up with, either right from the beginning or after some amount of back-and-forth.
This is just to let you have the information so you can make your own informed decision.
sfhub said:
There can be a difference between what the warranty says (or what is enforceable) and what your real-life experience is.
Click to expand...
Click to collapse
How true.
Has anybody had their service with Sprint cut off over rooting?
arpruss said:
How true.
Has anybody had their service with Sprint cut off over rooting?
Click to expand...
Click to collapse
I have personally never once heard of this actually happening, not over rooting alone. (over things that are achieved through rooting, like excessive tethering/data usage/forced roaming, yes)
And in fact, I've very rarely heard of sprint enforcing warr issues over it either, as long as one is smart.
(edit) I'm actually curious about your aversion to copyright issues and using custom ROMs?
(more edit) ah, didn't read your "ps". never mind, even though I'm still fascinated.
Sent from my calculator watch.
After further investigation, it looks like I can't find a fully legal and safe way to root.
I thought that installing an insecure kernel would do the job. But unfortunately the initramfs inside the zImage includes, in addition to the GPL Linux kernel itself, Samsung-copyrighted non-GPL code, such as redbend_ua, various Samsung-copyrighted image files and customized .rc scripts. So it looks like I can't legally download an insecure kernel.
I could build one myself, copying the files that will go into initramfs from my phone, and modifying to make it insecure.
But the problem is that this is unsafe, as I will have no way of restoring the stock kernel if I screw up in building the kernel, since there does not appear to be any legally available download of the stock kernel anywhere. (Check FUS doesn't seem capable of downloading EL29, but in any case in the US there are legal issues--DMCA--with Check FUS's decryption.) And without root, I cannot simply dump the kernel from the device using dd--if I could, that would solve the problem.
So, here's my question: Does anyone know any legal way of restoring the stock EL29 kernel (i.e., without downloading the stock firmware from an unauthorized location)?
This is really frustrating. I am not a lawyer, but it looks like one needs to be one to figure out how to root a device properly. Of course, I expect people think I am nitpicking. (But then again, I am a professional nitpicker in my day job.)
May i ask what is the reason for wanting to go through all this hassle to root your phone "legally"?
Sent from my SPH-D710 using xda premium
arpruss said:
After further investigation, it looks like I can't find a fully legal and safe way to root.
I thought that installing an insecure kernel would do the job. But unfortunately the initramfs inside the zImage includes, in addition to the GPL Linux kernel itself, Samsung-copyrighted non-GPL code, such as redbend_ua, various Samsung-copyrighted image files and customized .rc scripts. So it looks like I can't legally download an insecure kernel.
I could build one myself, copying the files that will go into initramfs from my phone, and modifying to make it insecure.
But the problem is that this is unsafe, as I will have no way of restoring the stock kernel if I screw up in building the kernel, since there does not appear to be any legally available download of the stock kernel anywhere. (Check FUS doesn't seem capable of downloading EL29, but in any case in the US there are legal issues--DMCA--with Check FUS's decryption.) And without root, I cannot simply dump the kernel from the device using dd--if I could, that would solve the problem.
So, here's my question: Does anyone know any legal way of restoring the stock EL29 kernel (i.e., without downloading the stock firmware from an unauthorized location)?
This is really frustrating. I am not a lawyer, but it looks like one needs to be one to figure out how to root a device properly. Of course, I expect people think I am nitpicking. (But then again, I am a professional nitpicker in my day job.)
Click to expand...
Click to collapse
Yes download it strait from Samsung as they have to post the firmware online as its open source...
https://opensource.samsung.com/index.jsp;jsessionid=FF0EE2E3CBD55BC19F669F0AC57CBFC8
Scroll down to sph-d710 there you can get it from them but technically everything in Android is OPEn source except the drivers....
Sent from my SPH-D710 using Tapatalk 2
I don't know why I find this thread so interesting.
Sent from my SPH-D710 using XDA
Ok so here goes a long but detailed read. I am writing this in hopes other fido users searching may find this thread and avoid future questions. Phone came with the TW 4.1.1 from fido and is fully stock.
Brand new S3 Galaxy from Fido (same as rogers) i747M Phone is great but the rooting bug has caught me.
1. I plan to root the device fairly shortly and install a non touchwiz variant. I will be following "High on Android's" Technique. detailed in this youtube video.
Is that method correct for my phone?
or should I be following something different? I just noticed Mr. Robinson posted the Fido TAR with root injected already on it. Does this make any difference? Links to TAR file are here
2. Now assuming I get everything up and running. What is the deal with "Triangleaway" and flash counters? From my understanding, Samsung has a counter installed that ensures they keep an eye on voided warranties due to flashing. Sure thats fine but lets talk about what we can do.
From what I gather, Triangle away will sort me out and get rid of the counters and put them back to zero in case I need to send my phone in for warranty. Is this correct?
Most of the triangle away info I read is for pre 4.1.1 confirmations hence why I ask.
3. Now lets assume I have flashed thephone and I am running CM 10 beautiful. Oh no power button breaks. What will be the required steps to get my phone back to 'stock" to send to Samsung. Will this even be possible to send it in without a worry? I cant seem to find steps online for this.
4. A lot of guides talk about the importance of backing up. Sure sounds great but they dont seem to give detailed instructions. What are the most important things I should backup before, during and after rooting my phone in case I brick it or anything goes wrong? Again any link or detailed explanations would be great.
Sorry for being so exhaustive in my questions. I like to learn it all so I can help other afterwards but also structured the thread so its easy to search for future users.
Happy new year everyone!
sspikey said:
1. I plan to root the device fairly shortly and install a non touchwiz variant. I will be following "High on Android's" Technique. detailed in this youtube video.
Is that method correct for my phone?
or should I be following something different? I just noticed Mr. Robinson posted the Fido TAR with root injected already on it. Does this make any difference? Links to TAR file are here
2. Now assuming I get everything up and running. What is the deal with "Triangleaway" and flash counters? From my understanding, Samsung has a counter installed that ensures they keep an eye on voided warranties due to flashing. Sure thats fine but lets talk about what we can do.
From what I gather, Triangle away will sort me out and get rid of the counters and put them back to zero in case I need to send my phone in for warranty. Is this correct?
Most of the triangle away info I read is for pre 4.1.1 confirmations hence why I ask.
Click to expand...
Click to collapse
I'm going to answer these two questions together, because they're interrelated.
There's no one single root method that's more "correct" than any of the others. The key difference between the end result of most of the methods is whether the flash counter has been tripped, which occurs (under circumstances where you're coming from ICS) if you use Odin to flash something other than a stock image (untouched or rooted as in Mr_Robinson's case). You can also trip the flash counter if you have the Jelly Bean boot loader and boot into a non-stock recovery image.
Thus, if you want to avoid tripping the counter for as long as possible, you want to use a method for rooting that doesn't trip the counter, such as the Mr_Robinson method.
If you're going to flash a custom recovery after working from stock JB, you'll probably end up tripping the flash counter the moment you boot into it, in which case (assuming your phone is still rooted) you could use Triangle Away to reset said flash counter.
sspikey said:
3. Now lets assume I have flashed thephone and I am running CM 10 beautiful. Oh no power button breaks. What will be the required steps to get my phone back to 'stock" to send to Samsung. Will this even be possible to send it in without a worry? I cant seem to find steps online for this.
Click to expand...
Click to collapse
I'd do the following:
Triangle Away, if the flash counter isn't 0;
Boot into download mode;
Flash a normal stock image from here; [*]Boot into stock recovery and wipe data/cache; [*]Boot phone as normal.
sspikey said:
4. A lot of guides talk about the importance of backing up. Sure sounds great but they dont seem to give detailed instructions. What are the most important things I should backup before, during and after rooting my phone in case I brick it or anything goes wrong? Again any link or detailed explanations would be great.
Click to expand...
Click to collapse
There are two major approaches you can take here, and using both of them responsibly is probably a good idea.
Titanium Backup, usable if your device is rooted, can back up all of your application data and some system settings; it's great for transferring data between ROMs and/or between devices altogether (I've done both). Most people I know of only use it for the former, as trying to restore system data with TiBu usually causes bizarre and unpredictable effects (with a few exceptions, such as text message data).
With a custom recovery, you can make what's called a "nandroid" backup, which is a complete image of your current ROM and userland data; it's most useful when you want to make a restore point of sorts for if you're, say, flashing experimental ROM images or other things you don't expect to work very well.
Hope this is of help.
smelenchuk said:
I'm going to answer these two questions together, because they're interrelated.
There's no one single root method that's more "correct" than any of the others. The key difference between the end result of most of the methods is whether the flash counter has been tripped, which occurs (under circumstances where you're coming from ICS) if you use Odin to flash something other than a stock image (untouched or rooted as in Mr_Robinson's case). You can also trip the flash counter if you have the Jelly Bean boot loader and boot into a non-stock recovery image.
Thus, if you want to avoid tripping the counter for as long as possible, you want to use a method for rooting that doesn't trip the counter, such as the Mr_Robinson method.
If you're going to flash a custom recovery after working from stock JB, you'll probably end up tripping the flash counter the moment you boot into it, in which case (assuming your phone is still rooted) you could use Triangle Away to reset said flash counter.
Click to expand...
Click to collapse
It seems the flash counter is a lot less worrysome to me now that you indicated I can always go back to a stock rom and return it for warranty regardless if it has a counter or not. Now I wonder why people even worry about tripping it.
I'd do the following:
Triangle Away, if the flash counter isn't 0;
Boot into download mode;
Flash a normal stock image from here; [*]Boot into stock recovery and wipe data/cache; [*]Boot phone as normal.
Click to expand...
Click to collapse
So Sounds to me like I should not worry about flashing and warranty correct? There will always be a method to go back to my phone in order to deal with warranty if something physical goes wrong? Any guide you could point me towards for this? I found this http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-canadian-galaxy-s3-sgh-i747m-stock-roms/
but it doesnt mention any fido files (understandable since its new)
There are two major approaches you can take here, and using both of them responsibly is probably a good idea.
Titanium Backup, usable if your device is rooted, can back up all of your application data and some system settings; it's great for transferring data between ROMs and/or between devices altogether (I've done both). Most people I know of only use it for the former, as trying to restore system data with TiBu usually causes bizarre and unpredictable effects (with a few exceptions, such as text message data).
With a custom recovery, you can make what's called a "nandroid" backup, which is a complete image of your current ROM and userland data; it's most useful when you want to make a restore point of sorts for if you're, say, flashing experimental ROM images or other things you don't expect to work very well.
Hope this is of help.
Click to expand...
Click to collapse
These two forms of backup I am use to and have used extensively on my nexus S. What I am worried about is more deep "system" type backups people do. is there any for this phone I should do through odin or Kies?
Edit: almost forgot to say thank you!
How come the root66_FMC_I747MVLDLK4.7z download link keep saying searching for mirror, please wait? Waited for 1 hr, no links. Refresh, no links.
thats odd I tried it yesterday and it worked
send a PM to the thread starter he will put up a new mirror I guess