Database Develop

Restore FRF85B to stock

Hi guys, I just updated my unrooted AT&T N1 from EPE54B to FRF85B. Now i'd like to reset everything on the phone to restore it to stock FRF85B (remove all my settings, apps, userdata etc). What's the best way to go about doing this? Will I have to root or install a custom recovery? Cheers.

Hmmmm It would have been more idea to do a factory Data Reset PRIOR to the upgrade, but you can do a factory Data Reset via Settings -> Privacy..

ozgreg said:
Hmmmm It would have been more idea to do a factory Data Reset PRIOR to the upgrade, but you can do a factory Data Reset via Settings -> Privacy..
Click to expand...
Click to collapse
Thanks. Will this complete remove everything that i've changed?

nachod0g said:
Thanks. Will this complete remove everything that i've changed?
Click to expand...
Click to collapse
it should but if not you can always wipe through recovery and then reflash

flybyme said:
it should but if not you can always wipe through recovery and then reflash
Click to expand...
Click to collapse
Thanks man. Can you clarify if wipe through recovery and reflash will require root or non stock recovery? Cheers.

nachod0g said:
Thanks man. Can you clarify if wipe through recovery and reflash will require root or non stock recovery? Cheers.
Click to expand...
Click to collapse
You're unrooted stock, and you're already at FRF85B. so all you need to do, is go to like he said settings/privacy and do an ERASE.
That's all. Your enter phone will erase all your user data and when it reboots it will be like a new phone on FRF85B.

Phone app force closing

Hey guys, for the past few weeks my phone app always force closes when someone calls me. I figured out that I can press the call button on the phone, but that doesn't solve the no ringing. I'm currently running Fresh 2.3.3, pleaseeeee can someone help me?
Sent from my HERO200 using XDA App

First try flashing one of the kernels in either of these 2 posts:
http://forum.xda-developers.com/showthread.php?t=705074
http://forum.xda-developers.com/showthread.php?t=750170
If that still doesn't solve your problem, reboot into recovery and wipe dalvik then reboot. If even that doesn't fix it, completely wipe the phone + dalvik then reinstall the ROM. Last case scenario, run the official Sprint 2.1 RUU then re-root.

Does flashing a kernal require anything different then just selecting it and flashing in the boot menu? I've never done it and I don't wanna brick the ohone or something...
Sent from my HERO200 using XDA App

silverballer95 said:
Does flashing a kernal require anything different then just selecting it and flashing in the boot menu? I've never done it and I don't wanna brick the ohone or something...
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
before flashing anything, try and clear the data for the app... go to settings -> applications -> manage applications locate the dialer and clear the data.
if that doesn't get it try recovery mode and wipe.
if it still FC then try nandroid restore or flashing new rom / kernel
just my opinion. there are lots of people on here that know much more than i do, but if it were me this is the route that i would take.

[Q] Help with root

Today I decided to root my captivate and was unsuccessful with the super one click. I then decided to do it manually with the update.zip. After I finished rebooting with recovery mode I saw the su app. I then tried to use titanium backup and it said that it could not get root permission. Could someone please help me figure out what went wrong and help me get a successful root so I can enable normally apps.

rtgould said:
Today I decided to root my captivate and was unsuccessful with the super one click. I then decided to do it manually with the update.zip. After I finished rebooting with recovery mode I saw the su app. I then tried to use titanium backup and it said that it could not get root permission. Could someone please help me figure out what went wrong and help me get a successful root so I can enable normally apps.
Click to expand...
Click to collapse
Did you enable USB Debugging for the one click method? Is your captivate I896? More info please.

I did enable usb debugging and my model number is I897
Sent from my SAMSUNG-SGH-I897 using XDA App

Should I flash back to stock with odin and then try to root
Sent from my SAMSUNG-SGH-I897 using XDA App

What ROM are you running?

Titanuim Backup probably wasn't given su permissions.
1. Have you tried rebooting it. Sometimes all it needs is a simple reboot and when you start TB, it will ask for su permissions.
2. Go to superuser. If you see titanium backup, click on it, forget, and reboot.

Just oneclickstock, load your ROM, and root again.
Maybe it's an app that's getting in the way?

bugmenever said:
Just oneclickstock, load your ROM, and root again.
Maybe it's an app that's getting in the way?
Click to expand...
Click to collapse
Ok thanks I'll try that and I am running the stock JH7 ROM

Odin worked but I'm trying to use Super One Click, I get to where it says "running rageagainstthecage" and then it loops I have tried doing what it says in the OP and it has not worked. How do I fix this.

rtgould said:
Ok so I put it into download mode and tried to use Odin. It said it was done, but nothing was changed on the Captivate. Any ideas?
Click to expand...
Click to collapse
did you follow the directions to a T?
ODIN must be open before you connect phone in download mode

I used a different one click root and it worked thanks for the help.

[Q]Milestone-Problem with root(superuser app) after kernel update from 0.07 to 0.08

Hi,
I have updated kernel from 0.07 to 0.08 on CM RC1, and after that superuser app has FCs eg when a new app requires SU. Old apps have SU, because I rooted again after the update (in androidiani recovery, or z4root app - the same effect)
I tried to clear data of superuser app or cache, wipes in recovery (dalvik and cache) and this hadn`t helped. I think there are some old files which superuser refers to which must be deleted, but dont know where to find them etc.
could u help ??

IFLPI said:
Hi,
I have updated kernel from 0.07 to 0.08 on CM RC1, and after that superuser app has FCs eg when a new app requires SU. Old apps have SU, because I rooted again after the update (in androidiani recovery, or z4root app - the same effect)
I tried to clear data of superuser app or cache, wipes in recovery (dalvik and cache) and this hadn`t helped. I think there are some old files which superuser refers to which must be deleted, but dont know where to find them etc.
could u help ??
Click to expand...
Click to collapse
Droid or Milestone?
Please clarify at title if you want ppl to help.
Sent from my Milestone using XDA Premium App

Milestone - updated first post, thanks for a hint.

IFLPI said:
Milestone - updated first post, thanks for a hint.
Click to expand...
Click to collapse
OK... so now i assume you have AOR... from the AOR menu, find and apply root from there.
Should fix your problem.
Sent from my Milestone using XDA Premium App

still, no result. I did it already as I mentioned it in the 1st post.
Any new app that requires SU; either FCs superuser or doesnt respond or has root access denied.

IFLPI said:
Hi,
I have updated kernel from 0.07 to 0.08 on CM RC1, and after that superuser app has FCs eg when a new app requires SU. Old apps have SU, because I rooted again after the update (in androidiani recovery, or z4root app - the same effect)
I tried to clear data of superuser app or cache, wipes in recovery (dalvik and cache) and this hadn`t helped. I think there are some old files which superuser refers to which must be deleted, but dont know where to find them etc.
could u help ??
Click to expand...
Click to collapse
But... why did you root your device once again??
If i did not misunderstood, you said that... so i assume that you had 0.07 running perfectly with root and when you update it to 0.08 you rooted again?
That's unnecessary and causes ( as i heard) that superuser.apk behaves badly.
So if i were you... i would wipe dalvik...cache partition and factory reset and then apply once again the 0.08 update.zip
And... do not root it again!
Hope it helps.
SENT FROM MY MILESTONE POWERED BY GINGERBREAD

IFLPI said:
still, no result. I did it already as I mentioned it in the 1st post.
Any new app that requires SU; either FCs superuser or doesnt respond or has root access denied.
Click to expand...
Click to collapse
Remove superuser app from your device then root from AOR
Sent from my Milestone using XDA Premium App

OK, finally I got it working.
nothing really helped, removing SU and rooting again, still SU forcecloses etc, wipes (cache, dalvik) the same.
There`s what I did, dont know whats the difference but still. I applied the kernel 0.08 once again (after I wiped cache and dalvik) rebooted > still problems.
Rebooted in the ARecovery, rooted, rebooted > SU forcecloses (only once), but from now on everything`s OK. I can add apps to the SU, root granted, everything is fine.
The difference was that in the first time I applied the kernel in the recovery and rooted at the same time without rebooting the system ...
Strange thing for me with this kernel update, I had the same story on Cronos (they say that u must root after kernel update, but they forgot to mention that system must be rebooted after update and before rooting.)
Thanks to all, maybe this thread will be useful to someone.

sdtaddey said:
But... why did you root your device once again??
Click to expand...
Click to collapse
After the kernel update the root is gone (There is a superuser, but its not working, and root is not granted) u must root it again. But as I said, there must be a reboot between update and rooting.
edit: nope. Still superuser FCs, this is starting to be annoying.

IFLPI said:
After the kernel update the root is gone
Click to expand...
Click to collapse
Says Who??
I update from 0.07 to 0.08 ,change kernels ( Arabic and African) AND THERE'S NO NEED TO ROOT IT AGAIN!!!!
that's why now you're having this kind of issues with su.
SENT FROM MY MILESTONE POWERED BY GINGERBREAD

IFLPI said:
Hi,
I have updated kernel from 0.07 to 0.08 on CM RC1, and after that superuser app has FCs eg when a new app requires SU. Old apps have SU, because I rooted again after the update (in androidiani recovery, or z4root app - the same effect)
I tried to clear data of superuser app or cache, wipes in recovery (dalvik and cache) and this hadn`t helped. I think there are some old files which superuser refers to which must be deleted, but dont know where to find them etc.
could u help ??
Click to expand...
Click to collapse
I would start from scratch with a full wipe first. Something went wrong. Also, i agree with the latest post...i have swapped kernels before and never needed to re-root.
Sent from my Milestone using XDA Premium App

[Q] How to completly unroot my note

my company just moved there email system from good to airwatch, the problem is airwatch started detecting as my phone as rooted ( which was :lol: ).... So I booted in stocked recovery did a factory reset and re-flashed a stock ROM using ODIN.
The problem is Airwatch still identifies the phone as "rooted /compromised" any idea how to completely unroot it or really reset to default
thankx

Flash a 3 part gb rom. Before flashing do a wipe of cache and data from recovery. Flash with pc odin, then do full wipe from recovery of gb, should clear any traces.
Sent from my GT-N7000 using xda premium

panch said:
my company just moved there email system from good to airwatch, the problem is airwatch started detecting as my phone as rooted ( which was :lol: ).... So I booted in stocked recovery did a factory reset and re-flashed a stock ROM using ODIN.
The problem is Airwatch still identifies the phone as "rooted /compromised" any idea how to completely unroot it or really reset to default
thankx
Click to expand...
Click to collapse
follow the instructions of SpyderTracks only instead of install you can also install jb gb, it is important to do all the wipe format and send it in download mode directly from recovery

panch said:
my company just moved there email system from good to airwatch, the problem is airwatch started detecting as my phone as rooted ( which was :lol: ).... So I booted in stocked recovery did a factory reset and re-flashed a stock ROM using ODIN.
The problem is Airwatch still identifies the phone as "rooted /compromised" any idea how to completely unroot it or really reset to default
thankx
Click to expand...
Click to collapse
Is your counter set to '0'?

Thankx.. for the suggestions, let me give them a try
Also yes the counter is set to zero

panch said:
Thankx.. for the suggestions, let me give them a try
Also yes the counter is set to zero
Click to expand...
Click to collapse
I have tried Google... I am drawing a blank.
Can somebody point me to official 3 part N7000 ROM for StarHub- Singapore.
All the rom I am getting are single file.

There is no need for that rom. Just boot into a Cwm recovery. (if you have already Un rooted then install Philz kernel.) . Format the system, data, cache and preload partitions and then choose reboot download. Then flash a stock rom again.
Sent from my GT-I9500 using xda premium

Thankx ... but did not work
Airwatch still is pain in back side....

use different email app to connect that support airwatch, whatever that is.
Or hack airwatch app if that exists to not check
Or dont allow it root...
Sent from my GT-N7000 using Tapatalk 2

You could also try ota rootkeeper from the playstore to temporarily disable root.
Sent from my GT-I9500 using xda premium