Related
I've looked at a few threads but they seem to involve flashing before rooting...
Is there a way to root without flashing? if so... how?
Thanks
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
unremarked said:
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
Click to expand...
Click to collapse
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
sinatosk said:
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
Click to expand...
Click to collapse
The bootloader is built into the phone, there's nothing to flash for that.
Think of it as a pre-recovery. Fastboot is a feature in the Android SDK which works with the bootloader to flash things such as recovery, or boot.imgs prior to actually having a custom recovery/root. However, it does require the bootloader to be unlocked which is where the fastboot oem unlock command comes in. Once you have a custom recovery on your phone, you flash things like normal.
From the stickied FAQ:
unremarked said:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot (aka the bootloader) mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
Click to expand...
Click to collapse
The first step helps you set up the SDK and drivers. The second step will tell you how to root, install recovery, and flash Superuser.
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
xspyda said:
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
Click to expand...
Click to collapse
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
unremarked said:
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Click to expand...
Click to collapse
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
xspyda said:
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
Click to expand...
Click to collapse
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
sinatosk said:
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
Click to expand...
Click to collapse
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
unremarked said:
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
Click to expand...
Click to collapse
well yeah I know about ADB... just nothing about rooting
Hmm the phone shipped with 2.3 and I have yet to update but as 2.3.1 is an official update I can't see that being reason not to accept a return.
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
There's a script in the thread that gives you cwm on boot. The catch is it goes to recovery first EVERYTIME you boot.
ubersoft said:
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
Click to expand...
Click to collapse
In the situation that you describe, even the CWM on boot that mtnlion mentioned, still may not get you into CWM. In that case your ONLY option is to flash the fxz file with rsd lite, that will restore you to a full stock out of the box atrix 2, which you then have to re-root, then re-install bootstrap, then restore your backup.
Sorry there is not an easier way right now, but until the bootloader is unlocked we can't flash CWM, so that we can get to it, as you would the default android recovery, because that does require the default recovery to be replaced, and an unlocked bootloader is required for that to work.
Safestrap is really a tool that is only useful to those actually developing, or people that we have asked to test something out, and since lfaber06 and I don't have a version to release to the public that we are happy with yet, that is not an option.
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
ubersoft said:
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
Click to expand...
Click to collapse
No, if you get a bad flash you still may not be able to get into CWM, since it requires files that are actually in the Android ROM, to fully work. Read my post above ^^^
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
ubersoft said:
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
Click to expand...
Click to collapse
No, it is perfectly safe, but the restore is just a little more complex than you had to deal with, with other phones. I have done exactly what I mentioned above SEVERAL times, with out issue, since I am doing a ton of dev work on this phone.
The ROMs that are out there are great right now, and lfaber06s ROM is really good, and I will be releasing a version of CM7 very soon. If you wait for a bootloader unlock, it may never come, or at least it may not be very soon.
The worst thing that happens is that you have to flash the fxz, which it is documented how to do that with RSD lite very well in the noob thread here. then you can restore your backup with out issue, it is just a few extra steps.
Bootstrap is really safe as is all of lfaber06 Roms right now. I have no problem recommending either of his roms to anyone. They are both very good. As Jim has stated the only problems we have is if something wrong happens on boot, but with the fastboot files, RSD lite, and the one click root method you have everything available to get you right back to where you were before you flashed.
I can promise you everything works very good as I have soft bricked my phone so many rimes in the last 2 weeks that I have become very efficient at getting back to stock, rooting and then flashing a backup with bootstrap and can be back in business n around 20 mins. Just always be near a computer when you start flashing things. One thing that will help out is to keep a backup of the bootstrap on tour SD card so if you have something go wrong you don't have to redownload it again.
We have a very good group of people here and if anyone has any problems we can get you through them and back running
Well there we are then!
So after getting a clearer picture of the situation (thanks for the explanation) I blocked off most of the night, installed bootstrap, then installed lfaber06's Supercharged v4. It took forever, but it worked flawlessly.
Thanks everyone for your patience and encouragement.
Okay, as a newby poster on this forum, I can ask this question here, hopefully someone reads here that can help *smile*.
I've followed the rooting guide for my post JB OTA updated Galaxy S3. My phone is now apparently rooted, I can grant root access to apps and all. I should have a custom recovery installed as well (I chose TWRP since a lot of people seem to choose CWM, and I'm a rebel without a cause), but I'm not sure, since when I booted out of recovery after installing the SU app, I didn't see the "Disable recovery flash" prompt. And I haven't tried to boot into recovery mode yet to verify whether the TWRP version that I installed is still there. Doesn't seem to have affected the resulting root access ability one way or the other, though.
My question is that when I boot my phone normally now, I see an unlocked lock icon, and "CUSTOM". Since I re-flashed the stock boot when I was done, this is a bit disturbing, I didn't expect that. I've read that if I have a custom recovery that I'll see this even if I have stock boot. Is this true? I think that stock boot is a good idea, but am not convinced that I have it. Is there any way to tell if I have a stock boot or not?
A little puzzled, although I definitely like the rooted phone better than the non-rooted one, so thanks much for that.
Just rebooted the phone into TWRP recovery a couple of times this morning, so I guess that I still have the custom recovery installed *smile*. And I'm also assuming that flashing the stock boot at the end of rooting worked, despite the unlocked lock icon and "CUSTOM" when I boot my phone now.
I guess there's no need for a reply here, since I've answered at least part of my own questions. I'm assuming then that I'm seeing "CUSTOM" and the unlocked lock icon when I boot because I have the custom recovery installed, and when I un-root it will go away. I've already set my flash count back to 0, since I wanted to remember to do that while I still had root, in case I un-root to send the phone to Samsung, and forget to do that.
Again, thanks for the guide thread on rooting, very helpful. The only first-time snag was booting into TWRP from Odin mode so I could install the SU app. Eventually figured out how to do that, so when/if I do this again should be much quicker.
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
tuffluck said:
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
Click to expand...
Click to collapse
As long as you're familiar with adb/fastboot run the following:
Code:
[U]From Bootloader[/U]
fastboot oem unlock
fastboot flash recovery [URL="https://dl.twrp.me/hammerhead/twrp-2.8.6.1-hammerhead.img"]twrp-2.8.6.1-hammerhead.img[/URL]
Boot into recovery....
[U]From Recovery[/U]
adb sideload [URL="https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1"]UPDATE-SuperSU-v2.46.zip[/URL]
tuffluck said:
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
Click to expand...
Click to collapse
Both are right. There is a manual way (flashing SuperSU through TWRP) and there is an "automated" way (the chainfire auto-root). Pick your poison.
The manual way will most likely wipe your device because the "unlock" step does that. I'm honestly not sure about the auto-root method, but I'm going to guess it probably also wipes.
As for OTA, yes, you need a stock recovery to get OTA, because.... well... the OTA uses the stock recovery to update. Most people are of the mind that if you're the type of person who flashes a custom recovery like TWRP, you're also the type of person who doesn't care about OTAs (the .zip is typically posted here within hours of the OTA going live anyway).
There are risks and drawbacks to any kind of hacking of your phone. Risks obviously include bricking, but the drawbacks usually include having to wipe and reinstall things once in a while, and also the lack of OTAs. Pick your poison.
fosser2 said:
As long as you're familiar with adb/fastboot run the following:
Code:
[U]From Bootloader[/U]
fastboot oem unlock
fastboot flash recovery [URL="https://dl.twrp.me/hammerhead/twrp-2.8.6.1-hammerhead.img"]twrp-2.8.6.1-hammerhead.img[/URL]
Boot into recovery....
[U]From Recovery[/U]
adb sideload [URL="https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1"]UPDATE-SuperSU-v2.46.zip[/URL]
Click to expand...
Click to collapse
Being a Nexus device this process is pretty straightforward and does not need all of the utilities to obtain root
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
SGJ3 said:
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
Click to expand...
Click to collapse
It's better to let them on.
You can remove the TWRP recovery by flashing stock recovery. But TWRP can backup your whole android partitions (nandroid backup) that can restore your android if anything goes wrong.
TWRP can flash custom roms, mods, mount partitions, and many more. So, it's better to you have TWRP(custom recovery) installed.
If you are using SuperSU superuser app then in option you found OTA survival that prevent root from OTA updates.
I think you can't get OTA updates because you are rooted. If you get OTA updates and applied on rooted android then it chances of brick your android.
Hi every one. First sorry for bad grammar I am not so good at english. Now to the problem at hand.
Jester day I bought a smj320fn and realise it is not what I paid for, so I tried to root witk KingoRoot and fail. Then I realised there is a "bootlock" witch prevents root (I think it does that).
So I tried ODIN and installed a custom FMW and it worked, allso I instaled a custom twrp and boot win.rar file. and there is the problem.
Every time I hold the power buton the samsung logo apears for 5 seconds and then goes black. It wont take any commands. I tride the recover meny to open, no it wont, but I can restars it to boot again and fails every time.
I tried to do it from a youtube tutorial and maby I know what I did wrong. I Instaled a Sm-j320h boot on my smj320fn so I think thats the problem. Any whay how do I fix this. All and any solution are good.