wanting to know best way to root and if the superoneclick root that i used on captivates will work with my Nexus S stock gingerbread 2.3.2
Just pick any of the root guide threads in the development section. Essentially they all do the same thing and end up with the same result. The manual (hardest) method takes no longer than 10 minutes even for a beginner.
Sent from my Nexus S using XDA App
The last time I noticed someone mention superoneclick around here, they said it didn't work.
Which method you use depends on how long you've had the phone, how much data in applications you have that you don't want to lose (because without root yet, you can't back them up), and whether you want an unlocked bootloader or not.
There's several guides in the development section. The one I posted is abbreviated and relies mostly on the steps from other guides, but it is focused on NOT wiping your phone as the original methods had you do with the fastboot oem unlock command. It doesn't seem to be necessary to do that step.
You can follow just about any of the guides and just skip that oem unlock step if you're worried about not wiping all data (ALL data, including your sdcard pics, music, etc).
Even if you want the bootloader unlocked for some reason, I'd suggest following the non-wipe method to root, then running a backup of your apps' data with Titanium (also copy your sdcard contents to your computer), then you can do the wipe method and restore your backup...now you have a oem unlocked phone and no loss of data.
^^ I agree with the guy above. His thread is easy. First time root and no wipe!
I liked this one the best, includes pictures and all.
http://forum.xda-developers.com/showthread.php?t=935819
Hey fellas, I got my Verizon GS3 last Thursday knowing that it had a locked bootloader but was hoping someone would figure out how to get root. Now I see that it has been rooted but is it "completely" rooted? What I mean is, can I overclock it, flash kernals, custom roms, wifi tether? Does it have the same capabilities of all three of the other US carriers' GS3s? Is Cyanogenmod developing CM9 for it yet? I was reading somewhere that you can root it just like any other version but it's just a bigger pain in the ass. I just want to make sure that my Verizon GS3 can be completely rooted so I can do everything I did with my old Droid. Should I just take it back and go with the Sprint version of the GS3? Im sorry if some of these are "noob" questions but I just want to figure out what I should do. Any help would be much appreciated!
Rooting and the other things you spoke of are not the same thing.
Rooting = The ability to write to the system partition, while booted into android. This allows you to delete system files (such as bloatware).
Locked Boot Loader = You will not be able to flash custom files (unsigned) to the phone from Odin. This means no clockwork recovery, roms, kernels ect....
There are ways around some of the locked boot loader stuff on some phones (ex. droid 2 got a special recovery through months of dev work. This did not cicrumvent the locked boot loader, but allowed away around it). This type of recovery (2nd init) is not avalible for Samsung phones.
If you want roms and all access, I would go with the dev unit samsung is selling for verizon. However, there still may not be much for the VZW gs3 because they wont sell tons of the dev units at $600 a pop.
The Verizon S3 already has root, roms and kernels up and working and some really good devs trying to crack it. I have a VG3 and it was rooted in less than a day and I'm having no issues. It's a great phone but the locked bootloader may cause issue in the future.
If I knew that samsung was going to release a dev version I may not have pre-ordered my S3 but I"m still happy with my purchase so far. What I find amusing is the price stated on the dev phone right now is cheaper than buying the phone outright from big V right now. We will see what the price really is when the phone is made available.
Farabomb said:
The Verizon S3 already has root, roms and kernels up and working and some really good devs trying to crack it. I have a VG3 and it was rooted in less than a day and I'm having no issues. It's a great phone but the locked bootloader may cause issue in the future.
If I knew that samsung was going to release a dev version I may not have pre-ordered my S3 but I"m still happy with my purchase so far. What I find amusing is the price stated on the dev phone right now is cheaper than buying the phone outright from big V right now. We will see what the price really is when the phone is made available.
Click to expand...
Click to collapse
I second this post!
locked bootloader means no custom roms or kernels.
chakra said:
locked bootloader means no custom roms or kernels.
Click to expand...
Click to collapse
Not true.
Touchwiz based custom roms are entirely possible and it has already been shown custom kernels work using kexec. Yeah it's not as good as an unlocked bootloader but we have our work arounds until these crazy smart devs figure out how to bypass the locked bootloader.
Sent from my SGS3
tanman21 said:
Rooting and the other things you spoke of are not the same thing.
Rooting = The ability to write to the system partition, while booted into android. This allows you to delete system files (such as bloatware).
Locked Boot Loader = You will not be able to flash custom files (unsigned) to the phone from Odin. This means no clockwork recovery, roms, kernels ect....
There are ways around some of the locked boot loader stuff on some phones (ex. droid 2 got a special recovery through months of dev work. This did not cicrumvent the locked boot loader, but allowed away around it). This type of recovery (2nd init) is not avalible for Samsung phones.
If you want roms and all access, I would go with the dev unit samsung is selling for verizon. However, there still may not be much for the VZW gs3 because they wont sell tons of the dev units at $600 a pop.
Click to expand...
Click to collapse
Thanks for the reply man! The dev phone just may be an option but I really don't feel like forking over $600 when I can go to Sprint on a cheaper plan and have an unlocked bootloader....either way, I have 10 more days to return my phone and cancel my contract if I need to. And btw, I sent a long email to Verizon asking them if they will ever unlock the bootloader ( I read an article saying they may, then today read a article saying they wont. We'll see.) I also said that I may just cancel my contract and go to Sprint and ask them how they can "help" relieve this situation that alot of people are facing. I'll report back and let everyone know what their response is.
Topdroid01 said:
Hey fellas, I got my Verizon GS3 last Thursday knowing that it had a locked bootloader but was hoping someone would figure out how to get root. Now I see that it has been rooted but is it "completely" rooted? What I mean is, can I overclock it, flash kernals, custom roms, wifi tether? Does it have the same capabilities of all three of the other US carriers' GS3s? Is Cyanogenmod developing CM9 for it yet? I was reading somewhere that you can root it just like any other version but it's just a bigger pain in the ass. I just want to make sure that my Verizon GS3 can be completely rooted so I can do everything I did with my old Droid. Should I just take it back and go with the Sprint version of the GS3? Im sorry if some of these are "noob" questions but I just want to figure out what I should do. Any help would be much appreciated!
Click to expand...
Click to collapse
There's some erroneous replies so far, hopefully this will clear it up for you. Root or superuser, is a linux term, which basically provides you with admin rights. With root alone you can run WiFi tether, rename system apps, etc. Root is easily attainable on the Verizon S3, see the dev section for guides.
The S3 recovery partition is NOT signed. This allows us to install custom recoveries (i.e. ClockworkMod, TWRP, etc.) This is very different from say, a Moto phone that had to use bootstrap methods. The S3 can have a fully functioning recovery that will allow you to do backups, flash ROMs and Kernels, etc. Again, very easy to do, see dev section for guides (it's grouped with root).
What's currently being worked on is the "locked" bootloader. Basically we can write whatever we want to the various partitions, however, there is a security check being done that prevents altering various areas, like the boot.img. Right now there is a workaround where custom Kernels are flashed via the recovery partition (see recovery/kexec threads for more info).
There is no official CM9 or CM10 builds yet, but they are being worked on and there are bootable versions of both. Right now the RIL is the bigger issue as it's preventing data but that has nothing to do with the bootloader. The RIL is being worked on, no ETA.
tl;dr - The bootloader is still "locked" but there are already various workaround methods in place to allow for the flashing of custom recoveries, ROMs, Kernels, etc. Reading the guides in the dev section would be a great place to start understanding what's going on better.
s197 said:
There's some erroneous replies so far, hopefully this will clear it up for you. Root or superuser, is a linux term, which basically provides you with admin rights. With root alone you can run WiFi tether, rename system apps, etc. Root is easily attainable on the Verizon S3, see the dev section for guides.
The S3 recovery partition is NOT signed. This allows us to install custom recoveries (i.e. ClockworkMod, TWRP, etc.) This is very different from say, a Moto phone that had to use bootstrap methods. The S3 can have a fully functioning recovery that will allow you to do backups, flash ROMs and Kernels, etc. Again, very easy to do, see dev section for guides (it's grouped with root).
What's currently being worked on is the "locked" bootloader. Basically we can write whatever we want to the various partitions, however, there is a security check being done that prevents altering various areas, like the boot.img. Right now there is a workaround where custom Kernels are flashed via the recovery partition (see recovery/kexec threads for more info).
There is no official CM9 or CM10 builds yet, but they are being worked on and there are bootable versions of both. Right now the RIL is the bigger issue as it's preventing data but that has nothing to do with the bootloader. The RIL is being worked on, no ETA.
tl;dr - The bootloader is still "locked" but there are already various workaround methods in place to allow for the flashing of custom recoveries, ROMs, Kernels, etc. Reading the guides in the dev section would be a great place to start understanding what's going on better.
Click to expand...
Click to collapse
This explains things alot better for me Thank you!!!. Im coming from a OG Droid that I rooted as soon as I got it so its been a while since I've been on the scene. I've kept up with the OG Droid Development for quite some time (which is basically nonexistent) so Im somewhat familiar with rooting and such just not familiar with this lock bootloader and such on my S3. Anyways, I still may just go to Sprint but havent made my mind up yet. And THANKS again for the very knowledgeable answer!
Sorry if this is a request for a lot of other threads out there but I can't find anything definitive, specifically since the release dates for JB are scattered by region and there's not always a clear answer to my situation because of that.
I have an XT925, the international RAZR HD. I got it recently her in Australia on the Telstra network with ICS preinstalled and with JB already released as an upgrade. I did save my root from ICS and still have root currently on Jelly Bean. It does, however, annoy me that I have to pull apart CWM packages, move all the files, and set permissions. In addition to that I've seen some talk about lag and people doing a factory reset to fix that. I have tremendous lag in folders in the default launcher and occasional noticeable lag in Nova launcer (which I prefer to use) window animations. My experience with Android has been with the Galaxy S II, which is still a great phone, however it is a phone that's easy as pie to root and deal with.
I have a lot of questions, some answered elsewhere but not necessarily in a context that applies to the situation I'm thinking of (and all the ins and outs would be too much to list), nor specifically for JB. Things get obscure given the
Please don't ask questions about why I'd want to unlock the bootloader, be rooted, etc. These are things I can decide for myself. Also, I'm aware I need to backup all my apps and app data to the SD card and pull the entire SD card contents. Please don't answer any of the questions unless you have first hand experience; I really would rather not get well intentioned misinformation that leads to a problem.
1. Can root survive a factory reset of JB. I presume it formats everything needed but still have to ask.
2. If the bootloader is unlocked, and I'm on JB, can I flash SuperSU by sideloading? If not, has anyone done it on a bootloader unlocked XT925 with CWM?; I've read some posts that involve a lot of confusion about the ease of installing CWM and using it on this phone. I should mention that I'm not familiar with TWRP and would like to stick to what's more familiar for the time being, assuming I go down this route.
3. Is there some advantage of TWRP over CWM? Honestly I don't even know what TWRP is; is this something I should learn since I have a Motorola phone? Also, is CWM well written for the device so far? Has anyone done a Nandroid backup and restore with it? Does it perserve time stamps (for OTA updates later given that system files have a 2010 timestamp on my device, for example)?
4. Has anyone had any of the more seemingly unlikely problems stated on the unlocking page of the Motorola site that you "may" have and for example, phone calls not working, apps not working anymore etc? Also, it specifically says "You will not be able to watch any movies you downloaded". Does this apply to videos purchased from google or does it mean that videos I've put on my phone will be unplayable? (I'm not even sure we can purchase Google movies from Australia).
5. There's a thread about disabling the unlocked bootloader warning, at boot, by replacing the file that provides the warning with one that does not, however I recall that the thread discussion was before the JB update (in my locale). Is this something that can still be disabled using the same tools in JB (assuming the original discussion was indeed for ICS)?
6. Does a factory reset wipe the system partition?.. specifically asking this because I've been keeping track of all files put to my system partition so that if there's another OTA at some point, it hopefully won't fail because I can remove everything added but if resetting wipes everything it would be easier to just do that.
7. Did anyone with an unlocked bootloader on ICS have a problem with the JB update, or more specifically if you had an unlocked bootloader on ICS, did it interefere with the OTA update to JB?
8. You know when you wake up to an alarm and have responsibilities but you'd rather just go back to sleep, but you get up anyway and it takes time before you accept the day ahead; doesn't that suck?
Any help here is appreciated.
It would be great if we had a master sticky FAQ thread for all the noob questions that one could conceive of. I hope that someone is able to write one.
Hello everyone,
It has been a long time since I have done ROM's or anything on an android device.
I would like to just root my Pixel 2 - is it possible just to do this and not go through the unlocking and adding ROM's process?
I would like the phone to just function as normal, but I need to get access to some of the system junk on the phone.
I am actually in need of getting into the SQL-Lite Database and taking a look at some of the data in there.
I was reading today at work that I needed to root the phone in order to be able to see those files.
Thank you for any help you can provide!
Psywar28 said:
Hello everyone,
It has been a long time since I have done ROM's or anything on an android device.
I would like to just root my Pixel 2 - is it possible just to do this and not go through the unlocking and adding ROM's process?
I would like the phone to just function as normal, but I need to get access to some of the system junk on the phone.
I am actually in need of getting into the SQL-Lite Database and taking a look at some of the data in there.
I was reading today at work that I needed to root the phone in order to be able to see those files.
Thank you for any help you can provide!
Click to expand...
Click to collapse
Unfortunately, no. You have to unlock the bootloader to root your phone. Of course, this wipes the device clean. There's no issue with just rooting though afterwards. I've been rooted and unlocked for a good few months since I've owned this device. I just manually install updates each month using fastboot and OTA images.
Hi there.
Have a Samsung Galaxy A42 5G that was dead here for some reason, and was sent in for service. No online backup of pictures was activated on the phone, and at the workshop they did a factory reset at the phone and upgraded to latest software.
Using any recovery tool at the phone now only tells me that root access is needed in order to have any possibility to recover pictures.
It seems for me that rooting this phone is a bit risky, and I don't know if it is possible to "un-root" it back to normal after.
If I can root this phone, how likely is it to find any pictures at the phone with some recovery tools? Possible that the upgrade of software have overwritten some old picture files?
Is it worth the risk, or better to forget the pictures and move on?
Regards, Nettulf
It's better to forget the photos and move on.
@Nettulf
Your question is asked in this forum almost every 14 days.
The answer is: Do NOT waste your time with trying to recover the wiped data. Blame the service who wiped them.
Thx for your reply, and I have seen similar questions with the same answers before yes ;-)
Just want to be sure that it is not any easy way on this phone. I guess the encryption and safety today make it much harder then before, I rooted some phones myself in the early days.
Recover them from your backups. Or sim card, and everywhere you have stored.
But if you have no backups, you can try some third-party tools.
Check this post: https://joyofandroid.com/data-recovery-software-for-android-phones/