Develop Bugs

Rooted, didn't do OTA update, Can I stop the nagging?

I figured I'd start a post for this since some people probably don't want to update after doing the root process, or maybe it would break root.
Is there a way to delete the OTA update off your phone and stop it from downloading it again and nagging you to update?

you could always root after updating since it obviously doesn't stop you from rooting

jonnybueno said:
you could always root after updating since it obviously doesn't stop you from rooting
Click to expand...
Click to collapse
I know, but I had a hell of a time getting done so I don't want to go though it again. It took a long time to get adb running in recovery, after that it was cake.

Think I found it, did its like the droid. Dunno if it will stop the updates yet, but still need to find the file it downloaded.
Went to
/system/etc/security/
renamed otacerts.zip to otacerts.bak
Anyone install the OTA update after doing root? Did it break it?
I would do it but, I already done this twice now and it was hard as hell to get shell in recovery
Damn whenever I reboot it goes back to .zip

TNS201 said:
Think I found it, did its like the droid. Dunno if it will stop the updates yet, but still need to find the file it downloaded.
Went to
/system/etc/security/
renamed otacerts.zip to otacerts.bak
Anyone install the OTA update after doing root? Did it break it?
I would do it but, I already done this twice now and it was hard as hell to get shell in recovery
Damn whenever I reboot it goes back to .zip
Click to expand...
Click to collapse
Unfortunately, even if it stuck, renaming otacerts.zip causes horrible battery life. It will continuously download the update, over, and over. It will download it, check the certs to see if its good. See its bad, go again, and again...
XC

xcsdm said:
Unfortunately, even if it stuck, renaming otacerts.zip causes horrible battery life. It will continuously download the update, over, and over. It will download it, check the certs to see if its good. See its bad, go again, and again...
XC
Click to expand...
Click to collapse
Yea well it doesnt stop it anyway, it already downloaded the file.
I wonder if theres any other way to stop it from nagging.

Much simpler to do the update and then reroot.
via my dinc...

krelvinaz said:
Much simpler to do the update and then reroot.
via my dinc...
Click to expand...
Click to collapse
Will it kill my root, I got superuser.apk installed already and that functions properly, will the OTA mess up anything?

don't know. I don't know anyone else that is doing what you are doing.
Re-rooting isn't that hard. I've done it 10-12 times before there was a way to make it stick. Just a little typing assuming you get access.
Chances are you may re-root again anyways as they come out with better packages to do it.

TNS201 said:
I figured I'd start a post for this since some people probably don't want to update after doing the root process, or maybe it would break root.
Is there a way to delete the OTA update off your phone and stop it from downloading it again and nagging you to update?
Click to expand...
Click to collapse
I'm not rooted yet so I can't say for certain, but you can almost certainly shut down auto-OTA check by editing the build.prop and or userinit.sh in /system. Those two files control most of the automation on your Droid! Good luck, and if I helped you, send me a 16gig SDcard so I can root too

i just deleted the otacerts.zip in /system/etc/security/ and now it says my system is up to day in about phone.

I can confirm that running the OTA after rooting will temporarily break root. You *will* have to redo the adb in recovery > payload before your root apps or superuser.apk will work again.
The good news is that you *can* simply redo it. No big deal once you are comfortable getting into adb in recovery.

crappypunk said:
i just deleted the otacerts.zip in /system/etc/security/ and now it says my system is up to day in about phone.
Click to expand...
Click to collapse
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.

krelvinaz said:
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.
Click to expand...
Click to collapse
I tried rooting my phone since the day root was achieved using a few different sd cards I have and failed every time. Last night I decided to downgrade and got my phone rooted on the first try. I'm no noob. I've established ADB on my HTC Vogue which is a WinMo phone running Android, I've rooted a My Touch 3G and a Hero but until I downgraded my phone I couldn't get root. At least not with my sd cards so for me running the OTA then rooting is just not an option. I will just deal with it until NAND write access is achieved.

krelvinaz said:
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.
Click to expand...
Click to collapse
Some of us are not able to easily get into adb shell, often taking days of trying (hundreds of reboots). I was finally able to get in, and don't ever want to have to do it again. I have wifi tether working, and that is plenty for me until they come up with an easier way to get into adb shell in recovery. I am assuming this guy is in the same boat (as far as how hard it is to get into adb shell).

It won't matter soon. Wait until the Unrevoked custom recovery comes out in a few days and then you can find a nice custom rom that won't bug you.
-------------------------------------
Sent via the XDA Tapatalk App

I have pre order version and so far its been great. When the ota came to me I clicked install and it errored out...it has Not prompted me a single time since and everything has been perfect and I'm rooted...any thoughts on this?
-------------------------------------
Sent via the XDA Tapatalk App

askwhy said:
I can confirm that running the OTA after rooting will temporarily break root. You *will* have to redo the adb in recovery > payload before your root apps or superuser.apk will work again.
The good news is that you *can* simply redo it. No big deal once you are comfortable getting into adb in recovery.
Click to expand...
Click to collapse
Yeah if it were only true, but cannot get back into adb recovery unless i down grade, now what?

PDAnuby said:
Yeah if it were only true, but cannot get back into adb recovery unless i down grade, now what?
Click to expand...
Click to collapse
Doesn't matter now. You should be able to start flashing ROMs soon with the Recovery Reflash tool from Unrevoked http://unrevoked.com/recovery/
Those Unrevoked guys are really hooking us up

I too had an incredibly hard time getting into the shell... I finally down graded, was able to get in (I don't' think that got me in, as it all ended up in being timing that I just had to get).
anyways, i've now installed the unrevoked recovery tool and updated to the latest clockwork via rom manager.
Anyways... that nag screen is getting old, so which rom are people installing on their systems that's getting rid of the nag / is an updated one?
I do NOT want to have to go through the root process again, what a pain it was for me...

[Q] Unroot EVO and still keep a custom rom?

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

Rooting Question

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

[Q] Custom ROM with un-root ability

Hey everyone,
Just got a GN a few weeks ago, and I am dying to try a custom ROM, but I got dinged by my work with my infuse because they have a no-root policy strickly enforced when accessing our corporate email.
I was not able to use an un-root app like root keeper, apparently because the ZEUS rom I was using had an autoroot on startup.
I am hoping the nexus has better options for using the un-root app, to (temporarily) unroot my phone when accessing my mail.
I have been reading that it is better to manually root the handset, rather than use a toolkit, which I am OK with; but I really would be interested in hearing from someone that has successfully used an unroot app to remove root.
- Thanks!

KevinAlbrecht said:
Hey everyone,
Just got a GN a few weeks ago, and I am dying to try a custom ROM, but I got dinged by my work with my infuse because they have a no-root policy strickly enforced when accessing our corporate email.
I was not able to use an un-root app like root keeper, apparently because the ZEUS rom I was using had an autoroot on startup.
I am hoping the nexus has better options for using the un-root app, to (temporarily) unroot my phone when accessing my mail.
I have been reading that it is better to manually root the handset, rather than use a toolkit, which I am OK with; but I really would be interested in hearing from someone that has successfully used an unroot app to remove root.
- Thanks!
Click to expand...
Click to collapse
C m9 has this option I believe
Sent from my Galaxy Nexus

How can they tell if you are rooted just through email use?

CM9 lets you restrict root access to ADB only. Might want to check that out

imnuts said:
How can they tell if you are rooted just through email use?
Click to expand...
Click to collapse
We access our corporate mail through the GOOD for enterprise application, and and that scans for root on load.
Sent from my Galaxy Nexus using xda premium

If the app scans for just the root binary or Superuser app, then I don't see a way to prevent it from detecting root without actually being unrooted. It likely looks in all $PATH dirs for su, and then in /system/app or /data/app for the application to grant permissions. Any ROM can be unrooted, just remove the su binary (and any symlinks) and the Superuser app before flashing.

Damn, they take the fun out of the whole Nexus experience.
Sent from my Galaxy Nexus using Tapatalk 2

imnuts said:
If the app scans for just the root binary or Superuser app, then I don't see a way to prevent it from detecting root without actually being unrooted. It likely looks in all $PATH dirs for su, and then in /system/app or /data/app for the application to grant permissions. Any ROM can be unrooted, just remove the su binary (and any symlinks) and the Superuser app before flashing.
Click to expand...
Click to collapse
Yeah, thanks. I guess what I am asking is if any of the unroot apps work with the custom ROMs the Nexus has. The ZEUS rom I was using with the infuse had something related to voodoo that kept ROOT, and the unroot apps did not have an affect.
I have only flashed two android ROMs with my infuse, but am an application developer by trade, so I am not skeered by the command prompt. I know there are a few CM9 based ROMs out there. I was looking at the PARANOID rom just cause that seemed interesting with the tablet hybrid. I just would like to know before I go through the whole flashing proc. that I can unroot before I connect to my work email (about once a week).
- Thanks for the replys so far. - Kevin

Just wondering...what is so dangerous about having root when accessing email?

fredryk said:
Just wondering...what is so dangerous about having root when accessing email?
Click to expand...
Click to collapse
Depending on the apps, root permission allows an app to gain full control of your device, so if one is not careful, he may let a rouge app into the phone. From a security standpoint, the rouge app may steal data from the email, which no company wants.
Think root as your computer's "Run as Administrator", same reason companies/schools limit user permission using User Policy(or whatever it's called)

Could just make a script to delete su and superuser and busybox, and make a flashable zip to put them back again.
Would require a couple of reboots every time but would still be quick to do once you had the zips set up
Sent from my Cyanogenmodded GNex

dr.m0x said:
Could just make a script to delete su and superuser and busybox, and make a flashable zip to put them back again.
Would require a couple of reboots every time but would still be quick to do once you had the zips set up
Sent from my Cyanogenmodded GNex
Click to expand...
Click to collapse
That's why I asked if anyone had success with the RootKeeper app. Although I would be interested in building an android script, my experience is soley with vb/C# web & desktop applications.
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en

Use SuperSU. What I did was temporarily block root, installed whatever MDM app was needed, set up the stock Exchange information, and allowed root again.
Let me know if this works for you.
Sent from my Galaxy Nexus using Tapatalk 2

Thanks shanky,
I will look into super su. The GOOD application checks on every launch, and so I will need to run it whenever I need to check work email, and but that is only once or twice a week from my phone.
Sent from my Galaxy Nexus using xda premium

KevinAlbrecht said:
Thanks shanky,
I will look into super su. The GOOD application checks on every launch, and so I will need to run it whenever I need to check work email, and but that is only once or twice a week from my phone.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hi Kevin,
did you have success with that? Or any other suggestion?
I have the same problem, my IT wants to wipe GFE container if my device keeps rooted.
Thanks..

Hi RTHppc,
Sorry for the very late reply. I can confirm this does work with GFE. The unroot effectively does not cause a compliance violation.
Overall it was a hassle to verify, even though our infrastructure team was completely on board. GOOD was balking when I attempted to register a second device (even temporarily) with the same sim card. It would only throw an ambiguous error 'unknown error'.
I could go on, but that is the subject for a rant thread.
Sent from my SGH-I997 using xda app-developers app

[Q] Rooted, didn't do nandroid backup -- any chance of recovering data?

My fiancee's EVO 4g was in desperate need of replacing, so we went and got new phones. She had been playing this damned Smurf Village game for about a year and a half, and I thought I'd pull a white knight -- root the phone, back it up on Titanium, transfer the backup to the new phone, root that, restore. She insists she's okay starting over, but I thought it'd be a nice gesture. Rooting the new phone (LG Optimus G) was a piece of cake. The EVO 4g took me some time to get it to work ...
In my poor attempts at multitasking, I didn't do a nandroid backup and completely overlooked where it said it would restore to factory settings.
Is all lost? I did a search on it while it was plugged into the PC as an external drive and found a bunch of (edit: Smurf-related) files, so I feel like the data might still be there.
If not, it's all good. I learned from my mistake (I mean, c'mon, big_onion, every damn set of instructions says "make a nandroid backup") but if there's any way to get it back it might make her day.
Data restoration aside, after flashing Superuser, I still can't get TitaniumBackup to obtain superuser privileges. Any ideas what I might've done wrong? The method I used was to unlock the bootloader via HTC site, then flashboot recovery, then flash superuser. The app is there, but it doesn't seem to issue SU rights to TitaniumBackup.

Best way to gain root is to flash any custom rom here on xda. Unless it is a completely stock rom it is rooted and works without any issues. I rooted my second og evo a few days ago and had the same issue with the stock rom. After flashing a custom rom I had full root access.
Now as far as data goes most apps store that on the sdcard. I suggest installing the game on the new phone then power off and insert your old sdcard into the new phone. Hopefully it will use the old data and return your wife's game to her last state and make you look like a champ.
Sent from my PC36100 using xda app-developers app

jlmancuso said:
Best way to gain root is to flash any custom rom here on xda. Unless it is a completely stock rom it is rooted and works without any issues. I rooted my second og evo a few days ago and had the same issue with the stock rom. After flashing a custom rom I had full root access.
Click to expand...
Click to collapse
Uhm...
You don't root android by flashing a rooted custom rom on a non root phone.
Rooting a phone must be done via a PC there is no other way.
Some stock roms ARE root.
The reason you had problems is because you were root and tried to install a non-root stock rom, if you would have installed a rooted stock rom you would of had no problems.
smh

Umm root is done by rom. Unlocking bootloader is the part done by pc.
You can be unlocked without root but can not root until you are unlocked. Rooting is the granting of admin rights to the user's apps.
I did not have an issue because I installed a non rooted rom. The rom was already on the phone which is the same spot the op is in. He is unlocked but not rooted. The htcdev unlock does not grant root rights to the current stock rom. Also the flashable zip did not grant the rom root rights.

jlmancuso said:
Umm root is done by rom.
Click to expand...
Click to collapse
You don't go from not being rooted to being rooted by flashing a custom rom on the phone from the recovery menu, unless you accidentally flashed a non-root rom while you were already root.
Unlocking bootloader is the part done by pc.
Click to expand...
Click to collapse
They're both done via PC at the same time with the same program (Unrevoked3 is only temporary nand)
Unrevoked Forever unlocks the bootloader permanently via recovery with an .img
http://wiki.rootzwiki.com/UnrEVOked

Wow man this will be my last response here about this but I want to say a couple quick things. First did you even read the link you posted? Yes with unrevoked you can gain nand unlock and root at the same time but if you also read it says this.
Does unrevoked³ give me root?
Yes. It previously did not; as of version 3.0, it does.
So root and nand unlock are not the same and is not always done at the same time. It is possible to be nand unlocked and not have root. Which is the case when you use htcdev unlock. Do your homework before you go making statements please.
I am not here trying to run anyone down and start fights but I am here to spread knowledge and help out others with problems. If you give someone bad information it will cause problems down the line later. Most people will assume you know what you are talking about when you make a post even if the information is not correct. So please take the time and make sure your information is correct before you post it.
So take a look at links I have posted and see what root is, how it is used, and see the difference.
This is a general overview of the root permission (depending on os it is called many different things)
http://en.wikipedia.org/wiki/Superuser
This is what it means with the android
http://www.ubergizmo.com/2012/05/rooting-for-android-what-why-and-how/
Again not fighting but giving information that is benifical to everyone.
Peace,
Love, and
Happiness

Fail troll is fail.
OP has the information he needs.
He already is rooted and needs permanent unlock which is what Unrevoked Forever does, which is linked in the link I posted.
Edit: The PM j sent me.
jlmancuso said:
Hey man. I am not trolling. The information is real. I am a knowledgeable dev and don't want anyone getting the wrong information. Bad information leads to big mistakes that can be a devs worst nightmare. Just read the articles and if you still don't agree well that is fine by me. I at least tried to give you the correct information.
Have a nice day and enjoy this beautiful day.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
I guess he thinks Unrevoked Forever is bad information and harmful to Evos.

Backedup
If you backed up the game, you can always download titanium backup and restore. Make sure you didn't delete the files from sd-card (they should be there). Sorry if this was already answered or i'm wrong. :fingers-crossed:
edit: if its a stock rom and you backup every app with titanium back up you could.

jlmancuso is having a hard week. i would give him a break. as far as i can tell he's genuinely trying to be helpful and is catching crap from all sides these days. eventually he will slow down and not accidentally provoke people (or take things personally). but he seems like valuable asset to the community overall so i'm rooting for him. OP good luck with your issue.

It's already unlocked, via the instructions from the HTC dev site. I didn't use Unrevoked -- I tried, and got a message about something being too new of a version. I'll dig around more, but I before I spent too much time I wanted to make sure I could restore the data on the stupid Smurf game for her.
I did NOT do a Titanium Backup of anything on there before I started. The LG Optimus G doesn't have an SD card, so I can't just swap SD cards. I can copy files from the EVO to the PC then to the LGOG. I think I might install Smurfs on the new phone, root it, then just try and copy the Smurf files from the EVO over to the Optimus G and see if overwriting the data files would restore her game.
Will report back on whether or not it works, or if I can't get superuser working.
And chill out, friends. I appreciate all sorts of info, even if it's not what I'm looking for. Y'all rock.

I am not taking it personally and dont think unrevoked is harmful. I am not going to argue with anyone about the facts. I posted the articles al5uwtqind if anyone wants to read them and learn more than cool. The information is for the benefit of everyone. Call troll or a$$ or whatever. I am here to help like most everyone.
Knowledge is power so empower someone else today.
Peace,
Love, and
Happiness
Sent from my PC36100 using xda app-developers app

big_onion said:
Data restoration aside, after flashing Superuser, I still can't get TitaniumBackup to obtain superuser privileges. Any ideas what I might've done wrong? The method I used was to unlock the bootloader via HTC site, then flashboot recovery, then flash superuser. The app is there, but it doesn't seem to issue SU rights to TitaniumBackup.
Click to expand...
Click to collapse
I think he meant "Htcdev site" then "fastboot flash recovery", but it seems like Big_Onion did everything right as far as rooting the phone, but there can be other reasons why Titanium is not working properly. It could be Titanium data needs to be wiped or it could be an issue with busybox. He never said he was not rooted, he only said that superuser was not giving Titanium root permissions, which has happened to me also. I wish he would have ran the root checker app too, to verify did he really have root or not. Then it would be easier to tell which path to take.
And also, why are we arguing over unrevoked and unrevoked-forever? Those don't work on the newer stock roms, because they were patched in 2011 by the first Gingerbread update on. Since big_onion used the Htcdev site, he is likely on Gingerbread. They, unrevoked3 and forever, would only work if he downgraded the radios to the ones which came with either Eclair or Froyo, the two previous operating systems. Titanium backup only needs an unlocked bootloader from the Htcdev site, and superuser permissions from the superuser app to work. Anything else is just extra, at least on Gingerbread.