I'm looking to root with the one click app in the dev section but have a few questions before doing do. Thanks.
1. Will I be able to restore back to the same factory settings if I do a restore and will it keep root or loose root in that situation? Basically if I go to privacy > erase data to restore phone to how I first got it.
2. Will I be able to update to the new froyo one released from root even if I delete things, and will it mess the update up in that situation? Or do I restore it and then update?
1). You won't lose root from merely wiping personal data/factory resetting from the the phones OS menu.
2). Merely being rooted shouldnt block you from getting the Froyo update.
Any significant hacking or customization beyond that might depending on precisely what you do, but it's really a non-issue. The way OTA updates are performed is in batches. They don't just flip a switch and every single phone gets updated at once. Unless you are extremely lucky to be in one of the initial OTA push batches you will likely see the update here long before you'd ever get it as an OTA update anyway.
By the time you even have to worry about the upcoming OTA's you will have options available to you, thanks to the diligence of the members of XDA.
to truly get back to out of the box, you need ODIN, you can find tons of info here, its not hard to go back to out of the box. Check out this thread.
http://forum.xda-developers.com/showthread.php?p=7915809#post7915809
basically to unroot for any reason you just need to setup adb and do:
Code:
adb shell
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
or you can do it in terminal if you download the terminal app. and do
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
this removes everything that was installed when you rooted.
once you root you wont care about the OTA updates because the custom stuff that the devs put out are so much better (eugene's Vibrant/Hybrid roms)
Good luck
I'm probably not going to install roms because I'm scared of the risk at bricking at the moment. So how would I restore back to the original settings basically factory restore without root when as first got my phone once I'm rooted if ever desired.
d_bot said:
http://forum.xda-developers.com/showthread.php?p=7915809#post7915809
or you can do it in terminal if you download the terminal app. and do
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
this removes everything that was installed when you rooted.
Click to expand...
Click to collapse
and i repeat...
If all you are going to do is root, then just download terminal emulator, run the commands i gave you, and uninstall the apps that require root. If you truly want to get back to 100% out of the box, use ODIN.
really the chances of bricking this phone are very slim, not impossible, but slim.
Can i use the One click rooter program by TGA Gunman? And also so as your telling me the only way to get back to stock would be to unroot, then flash odin with a stock rom right? What stock rom is the best one? I see like 200 haha.
Unrooting should get you very close to stock. To get back to true stock ROM you need to simply flash with ODIN. I would suggest you go with the easier method and unroot (no risk of bricking) vs ODIN (chance of bricking your phone).
richan90 said:
Unrooting should get you very close to stock. To get back to true stock ROM you need to simply flash with ODIN. I would suggest you go with the easier method and unroot (no risk of bricking) vs ODIN (chance of bricking your phone).
Click to expand...
Click to collapse
Then if i wish to get my phone back to as was with all the stuff it had i wouldnt be able to do so without putting stock back through odin right?
richan90 said:
Unrooting should get you very close to stock. To get back to true stock ROM you need to simply flash with ODIN. I would suggest you go with the easier method and unroot (no risk of bricking) vs ODIN (chance of bricking your phone).
Click to expand...
Click to collapse
is ODIN really that unsafe?
Related
Stock 2.1 -> Rooted that with Ryan's OCLF
Did Lag Fix V1 cause V2 didn't work..
Everything ran..and ran... then that OTA update came while I was at school
It kept installing then restarting and looping itself...Finally I believe it installed and stopped asking me to reinstall.
My phone shows it has the Update, yet my phone isnt rooted anymore...Yet I still have the lag fix installed. I tried running the update.zip in recovery and it says signature failure. I try booting into clockwork to apply that update ROM that is posted and nothing happens. I hit boot into Recovery with ROM Manager and nothing happens.. I'm really confused..It's like I have partially rooted things like Lagfix on yet I'm not rooted and I cant root my phone ??
Anyone got an idea?
Thank you everyone.
Um, I think you're confused about what root really is. Being rooted just means that you have permissions (and the applications necessary) to modify protected areas of the OS. Even if you lost root access, the lag fix remains because the filesystem modifications to put it in place are already done. The extra commands it adds are run by the system itself during boot up, which of course has root access. It's not like an app that needs to request root access via Superuser every time it runs.
I'm not sure what has actually happened to your phone, but I would recommend rooting the old-fashioned way, via advanced commands, so that you don't have to deal with any recovery issues. If that doesn't work, you may have to flash back to factory stock and start over again.
Sent from my SCH-I500 using XDA App
johnz1 said:
Stock 2.1 -> Rooted that with Ryan's OCLF
Did Lag Fix V1 cause V2 didn't work..
Everything ran..and ran... then that OTA update came while I was at school
It kept installing then restarting and looping itself...Finally I believe it installed and stopped asking me to reinstall.
My phone shows it has the Update, yet my phone isnt rooted anymore...Yet I still have the lag fix installed. I tried running the update.zip in recovery and it says signature failure. I try booting into clockwork to apply that update ROM that is posted and nothing happens. I hit boot into Recovery with ROM Manager and nothing happens.. I'm really confused..It's like I have partially rooted things like Lagfix on yet I'm not rooted and I cant root my phone ??
Anyone got an idea?
Thank you everyone.
Click to expand...
Click to collapse
Flash CMW recovery via Odin. Then do the following..
adb shell (you should have the # prompt, if not su)
cd /system/xbin (or /system/bin if your files are there)
chmod 4755 su
chmod 4755 busybox
all done.
Thankyou very much brandon
I have my vibrant rooted and romed running Teamwhiskey's Fusion 1.2 Rom. I want to go back to stock so I can flash one of the new 2.2 Roms. My question is if I use Odin to go back to JFD so I can flash another rom does flashing back to JFD remove the root and all the root apps like Rom Manager and the one used to make nandroid backups?
Short answer, yes, all of the above.
Sent from my SGH-T959 using XDA App
So then theres no reason to do a nandroid backup because when I go back to stock its going to remove all the apps and backup data anyway correct?
Then after I am back to stock I will have to re-root the phone so that I can re-rom it right?
I rooted my Samsung galaxy SI-9003.But didn't go well for me.Instead of speeding up my phone it became slower.Because it read my phone as a lower version and GT-I9000 device.Now my question is Does ODIN also remove traces of root?For warranty reasons.I had a succesfull flash my phone.But not sure if the traces of superoneclick root is still there?
If you have ADB or terminal from market type this:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
Superuser is gone. If you are not rooted, then you won't get past the entry of su above.
Do you need root permission for ADB?Thanks.Ill check it out later
mikolas_69 said:
Do you need root permission for ADB?Thanks.Ill check it out later
Click to expand...
Click to collapse
Been so long I can't remember but I am pretty sure you don't and all that you need it the USB Debugging checked in settings.
But you can dl any terminal from the market and when you type SU it will say either Superuser permission or it will say that you don't have it. Either way you'll know what to do based on the above.
Thanks guys. I almost bricked my phone by rooting it.but now its doing ok.Because of everyone's help here at the forums.Thumbs up to everyone here at XDA developers.
mikolas_69 said:
Thanks guys. I almost bricked my phone by rooting it.but now its doing ok.Because of everyone's help here at the forums.Thumbs up to everyone here at XDA developers.
Click to expand...
Click to collapse
No problem. Btw only way to really brick it is to screw with the bootloaders, so rooting wouldn't do that. Freak you out, yes but brink, not so much.
My phone became very2 slow and hanged alot.Then I tried to unroot it with the same apps I used to root it.It hanged in the middle of the processed and I disconnected it from my computer.My phone went black screen for awhile.Yup it freaked me out good. ^_^. Some suggested I flash it.The outcome was very good.It's stable now.But then I want to bring it back to the original version.The latest version of the ASIAN Froyo in this site is nit the same as my version when I got the phone.So Ill bring it back to the service center.Just making sure that the traces of the root is gone.My phone is only a month old that's why it's still under warranty. ^_^
I finally gave in to the update nagging screen and tried to update.
My phone was rooted with preinstall method, nothing else.
I was on 2.3.4 (4.5.91).
I installed RootKeeper and unrooted before the update (kept root backup).
The phone downloaded the update, restarted, and I saw the Android Icon and an "unpacking" progress bar. The bar stopped about half way and the icon turned into an exclamation point. I thought I was toast....
The phone rebooted fine, everything still there. I got a message box "Update failed" once I got on my home screen. The phone is still 2.3.4. The update nagging is gone.
I have pretty rare reboots, maybe 2 a month. I am quite happy with it.
Anyone had the same issue? Should I even bother going to 2.3.6?
The only thing I am really missing on the Atrix is HDMI mirroring option with 720p or 1080p up-conversion.
How can I get the cause for the "fail"? Should I use the Moto USB method?
I wouldnt mind going to CM9 but I want the Finger Sensor, Camera etc all to work. I dont want to loose any current functionality going to CM9 and its not there yet, correct?
Thanks!
I would just stay where you are at. Unless you really want the mirroring. You seem to not mind stock so I would wait for Moto to release ICS for the Atrix. They put it on the list.
if you only rooted, did nothing else that requires root (freeze apps, put files in /system, etc) and did not unlock the bootloader, just unroot and then apply the 2.3.6. update.
Code:
1. Open Android Terminal Emulator (ADB)
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
spacev said:
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
Click to expand...
Click to collapse
There have been posts in various 2.3.6 threads where rootkeeper did not work if you used the fastboot preinstall method.
It should work if you manually unroot as long as everything else is stock.
for seeing why the update failed, hold the Volume up and power button when the error appears and you should see some sort of error msg...never tried it myself though.
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
otter9309 said:
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
Click to expand...
Click to collapse
Did you undo everything that requires root access prior to applying the OTA? I usually do the following prior to an OTA (and redo once the OTA is applied):
uninstall Swype beta, restore stock Swype files (the so and apk files)
move ringtones out of /system/media
Help Needed
Hi All,
I am a newbie here and I am not sure if my question makes any sense. Couple weeks back, I bought an Atrix 4g (US version), an unlocked version (the seller told me that this phone is unlocked using AT&T code) and I am using it with Vodafone (India) sim. It works perfectly and so far I didnt face any problems with this phone. But last week, I got an alert in phone saying that software update (2.3.4.5.141) is available for AT&T users and enable wifi to download. However, I didnt download and install the update as I was not sure why is it saying the update is available only for AT&T users. Also wherever I read about this software udpate, the name 'AT&T users' come along with that.
So my doubt here is, what will happen if I, who is not an AT&T user, download and install the software update in my phone ? will it cause any issues in the phone (like getting locked again or bricking the phone)
I have not done any modification like rooting or installing custom ROM and things like that and I am using the phone as I recieved it.
Thanks in advance for your help.
-Qaddaffi
I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
LeonardHatred said:
I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
Click to expand...
Click to collapse
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
BLuFeNiX said:
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
Click to expand...
Click to collapse
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
LeonardHatred said:
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
Click to expand...
Click to collapse
Do it again, but us the su binary found here: https://plus.google.com/103583939320326217147/posts/4FemP5ACLSn
BLuFeNiX said:
Do it again, but us the su binary found here:
Click to expand...
Click to collapse
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
LeonardHatred said:
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
Click to expand...
Click to collapse
No problem.
I would like to ask that if i root now,could i update the stock system in future?
Because i find that something wrong with WIFI,maybe next official update can repair it.
And if i root failed and brick,can i flash stock ROM to recovery my HDX? Where to download the tools and ROM?
zbw0046 said:
I would like to ask that if i root now,could i update the stock system in future?
Because i find that something wrong with WIFI,maybe next official update can repair it.
And if i root failed and brick,can i flash stock ROM to recovery my HDX? Where to download the tools and ROM?
Click to expand...
Click to collapse
I'm interested in knowing this too. Once we root should we still update or block Amazon updates?
Just having root wouldn't itself wouldn't block an OTA update as long as you've not removed/renamed any system files.
However, the root technique currently used is an exploit in the Linux kernel itself which may well get patched in a new update, so you'd lose root and not be able to get it back until a new technique/exploit is, um, exploited
If you do decide you *need* root, it would be a good idea to block updates from Amazon, I believe you need this in your firewall:
Code:
iptables -A "droidwall" -s 72.21.194.208 -j "droidwall-reject"
iptables -A "droidwall" -s 176.32.195.233 -j "droidwall-reject"
iptables -A "droidwall" -s 72.21.195.233 -j "droidwall-reject"
For what it's worth, I'm a fairly advanced user but have chosen to hold back for now...