Database Users

Help! New Nexus S user

Hi there,
I picked up my Nexus S a couple of days ago and i'm totally loving the device. My only problem is connecting to T-Mobile's 3G network, I can only connect for 4-5 mins before it switches back to Edge, which is terribly slow. I've read that this has been an issue for some people and I tried to remove the sim card, change the APN Settings but nothing seems to help.
I read something about updating to newer radio but I'm not sure how to do that, any help would be appreciated !
All the best,
Gianpy

Ploone said:
Hi there,
I picked up my Nexus S a couple of days ago and i'm totally loving the device. My only problem is connecting to T-Mobile's 3G network, I can only connect for 4-5 mins before it switches back to Edge, which is terribly slow. I've read that this has been an issue for some people and I tried to remove the sim card, change the APN Settings but nothing seems to help.
I read something about updating to newer radio but I'm not sure how to do that, any help would be appreciated !
All the best,
Gianpy
Click to expand...
Click to collapse
Go into your settings menu>About Phone and tell us your baseband version please.
I should note that I've not really heard of this happening before and to me it sounds like you're just not in a 3G area.

kenvan19 said:
Go into your settings menu>About Phone and tell us your baseband version please.
I should note that I've not really heard of this happening before and to me it sounds like you're just not in a 3G area.
Click to expand...
Click to collapse
You might not have 3g in your area. Other than that it sounds weird
Sent from my Nexus S using XDA App

I am on the Strip in Las Vegas, NV - I doubt there is no 3G here since there is even 4G here!
Baseband version- I9020XXJK8

You are right now on 2.3.2 Stock without root right?
-So, first step is rooting your phone. You can do it without oem unlock and not losing all your archives. But I did this and I just copied all files again(Yes, it's boring to wait all the time transfering archives but it's better).
- Now you have to flash Clockworkmod (It's the same topic, showing how to do it).
- Then flash through CWM (ClockWorkMod) the update. GRH78 is 2.3.1, GRH78C is 2.3.2, GRI40 is 2.3.3. Link: http://forum.xda-developers.com/showthread.php?t=967953
Any douts?
This should solve a lot of issues that you have now.

liquelt said:
You are right now on 2.3.2 Stock without root right?
-So, first step is rooting your phone. You can do it without oem unlock and not losing all your archives. But I did this and I just copied all files again(Yes, it's boring to wait all the time transfering archives but it's better).
- Now you have to flash Clockworkmod (It's the same topic, showing how to do it).
- Then flash through CWM (ClockWorkMod) the update. GRH78 is 2.3.1, GRH78C is 2.3.2, GRI40 is 2.3.3. Link: http://forum.xda-developers.com/showthread.php?t=967953
Any douts?
This should solve a lot of issues that you have now.
Click to expand...
Click to collapse
I am on 2.3.1 Stock without root, should I still follow the same steps?

Ploone said:
I am on the Strip in Las Vegas, NV - I doubt there is no 3G here since there is even 4G here!
Baseband version- I9020XXJK8
Click to expand...
Click to collapse
Well, I just pulled a coverage map of the strip and it seems that there are spots of worse coverage so it all depends on where you are. Nonetheless, I will help you update your radio or even update to 2.3.3 altogether as long as you're willing to root your phone and flash a rom (you can use download and use the update that Google pushes out but a lot of people have problems with it so I think its just easier to root, flash the rom, then just not root again once you have the new ROM). If you want me to help you do this, just say so and tell me if you have a mac or a PC.

kenvan19 said:
Well, I just pulled a coverage map of the strip and it seems that there are spots of worse coverage so it all depends on where you are. Nonetheless, I will help you update your radio or even update to 2.3.3 altogether as long as you're willing to root your phone and flash a rom (you can use download and use the update that Google pushes out but a lot of people have problems with it so I think its just easier to root, flash the rom, then just not root again once you have the new ROM). If you want me to help you do this, just say so and tell me if you have a mac or a PC.
Click to expand...
Click to collapse
Sure, I'd love some help doing that, I appreciate your help!
I am on a Mac.

You should follow the same steps but the update file is different!
Here is the link for you to root: http://forum.xda-developers.com/showthread.php?t=931865

There are a lot of Custom ROMs, you should choose one and flash it.
I put the wrong link, I didn't known that you had a Mac.
Sorry, here is the right one! http://forum.xda-developers.com/showthread.php?t=931865
Enjoy this beautiful phone!

liquelt said:
You should follow the same steps but the update file is different!
Here is the link for you to root: http://forum.xda-developers.com/showthread.php?t=931865
Click to expand...
Click to collapse
****, I'm completely lost..
Kenvan is your method the same as this or something different?

Ploone said:
****, I'm completely lost..
Kenvan is your method the same as this or something different?
Click to expand...
Click to collapse
The method he linked only works for builds prior to 2.3.3 which is a category you fall into. That guide is quite nice and works very well but it will not unlock your bootloader, which means your SDcard partition for your files and music and pictures etc won't be wiped. If you intend to stay rooted, I don't suggest using that guide but instead using the one I wrote here:
http://forum.xda-developers.com/showthread.php?t=970237
Now before you do either, tell me if you want to unlock your bootloader (if you plan to stay rooted after doing the updated) or want to leave it locked (if you plan to remove root after updating).

kenvan19 said:
The method he linked only works for builds prior to 2.3.3 which is a category you fall into. That guide is quite nice and works very well but it will not unlock your bootloader, which means your SDcard partition for your files and music and pictures etc won't be wiped. If you intend to stay rooted, I don't suggest using that guide but instead using the one I wrote here:
http://forum.xda-developers.com/showthread.php?t=970237
Now before you do either, tell me if you want to unlock your bootloader (if you plan to stay rooted after doing the updated) or want to leave it locked (if you plan to remove root after updating).
Click to expand...
Click to collapse
Whichever is easier to be honest and requires less steps, you tell me haha. I don't mind either option.

Or you could just wait for the official 2.3.3 OTA if you don't want to root. Might get it quicker if you do a checkin request. Simply dial *#*#checkin#*#*
Sent from my Nexus S using XDA App

Ploone said:
Whichever is easier to be honest and requires less steps, you tell me haha. I don't mind either option.
Click to expand...
Click to collapse
lol the difference between the two is literally two command. if you unlock the bootloader you add one command (fastboot oem unlock) and you use the command "fastboot boot" for the locked method where as you use fastboot flash for the unlocked. After that the two are exactly the same so if you want to stay rooted after updating (so you can use apps like AdFree, Titanium Backup, Root Explorer, etc or want to install custom roms) you should unlock your bootloader.
To be completely frank, if you don't mind unlocking the bootloader I've had some people have trouble with the command "fastboot boot" which is why I changed my guide to use "fastboot flash". What I'm saying is I recommend using my guide, which again you can find at the link below. Remember though, before you go through any of the steps copy the contents of your SD card to your computer. Actually that is a step I should really add lol
http://forum.xda-developers.com/showthread.php?t=970237
I'm going to go find the link to the 2.3.3 ROM so I can give you that but just take a look at my guide while I'm looking.

kenvan19 said:
lol the difference between the two is literally two command. if you unlock the bootloader you add one command (fastboot oem unlock) and you use the command "fastboot boot" for the locked method where as you use fastboot flash for the unlocked. After that the two are exactly the same so if you want to stay rooted after updating (so you can use apps like AdFree, Titanium Backup, Root Explorer, etc or want to install custom roms) you should unlock your bootloader.
To be completely frank, if you don't mind unlocking the bootloader I've had some people have trouble with the command "fastboot boot" which is why I changed my guide to use "fastboot flash". What I'm saying is I recommend using my guide, which again you can find at the link below. Remember though, before you go through any of the steps copy the contents of your SD card to your computer. Actually that is a step I should really add lol
http://forum.xda-developers.com/showthread.php?t=970237
I'm going to go find the link to the 2.3.3 ROM so I can give you that but just take a look at my guide while I'm looking.
Click to expand...
Click to collapse
Ok, I'll check out your guide. Thank you so much for all your help! I hope my problem is fixed !

Ploone said:
Ok, I'll check out your guide. Thank you so much for all your help! I hope my problem is fixed !
Click to expand...
Click to collapse
No problem man, if you have any questions at all let me know.
Also, here is the link to the full ROM for 2.3.3:
http://forum.xda-developers.com/showthread.php?t=967953
Now I'm not 100% sure if this will update your radio but it will give you the newest update. I'm currently trying to check on that so you can get everything done at once (if it doesn't do the radio there is another file you can install right after installing the ROM that will update your radio. That way you'll be 100% up to date)
EDIT: Yes, it does contain the radio, so that will put you 100% on 2.3.3 with the updated radio.

Do you have any questions?

kenvan19 said:
Do you have any questions?
Click to expand...
Click to collapse
All is well and my problem is fixed, thank you very much!

[Q] Question about rooting

Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!

timour79 said:
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
Click to expand...
Click to collapse
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.

Billchen0014 said:
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Click to expand...
Click to collapse
Can I unlock the bootloader, root, then relock the bootloader and keep the root?

timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
if you choose the relock bootloader option in the toolbox, it removes superuser as well

Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
Alright, thanks

Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock

timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
What's your reason for wanting it relocked?
Sent from my HTC Vision using xda app-developers app

noneabove said:
What's your reason for wanting it relocked?
Click to expand...
Click to collapse
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?

Nate2 said:
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Click to expand...
Click to collapse
Well I dont want to completely void the warranty, unless rooting already does that. If it was mine then i would've unlocked and rooted. I'd probably already have a rom and kernel on it. But it's actually my dad's, and he said I can root it if I don't do anything too serious(like I said, I just want Superuser so I can use things like the sixaxis controller app.)

comminus said:
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
Click to expand...
Click to collapse
Would that be manual rooting?

NRT questions
hey there
have some newb questions about rooting along the same lines of the OP. hope you can help me
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
sorry for the newb questions but there are so many different guides out there and some of them refer to older versions of the NRT so just want to clarify these points.

timour79 said:
Would that be manual rooting?
Click to expand...
Click to collapse
No. All you are doing there is unlocking the bootloader. Unlocking the bootloader is the equivalent of pre-heating your oven. You haven't messed with any ingredients or cooked anything yet.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Lemegeton300 said:
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
Click to expand...
Click to collapse
1. The chances are pretty slim for permanently bricking. That is the beauty of Nexus devices - the entire factory image is available to be flashed back on if you screw things up. That is the equivalent of reformatting your harddrive & reinstalling your OS on your desktop.
2. mkskip's toolkit will install it for you. I am sure wug's will too.
3. You don't have to install CWM, especially if you are thinking that you will pretty much always stay stock. But, the bug might hit you in a month or two to start playing around, and then CWM or TWRP is your friend. I installed CWM & made a backup pretty quickly in case I do something I shouldn't, such as accidentally deleting a vital system app. That way you do not have to do the factory reinstall route. Every few weeks you can make yourself a fresh backup just for fun.
4. You should be fine - the drivers must be working if the toolkit is doing backups for you. I am assuming you are using mkskips toolkit based on this question - his instructions say that sometimes in 1 step it says drivers didn't install correctly when they actually do - Windows is...Windows. If you want to be sure, ask away on mkskip's thread. He is quite helpful.
5. If you reflash the factory image & the bootloader is relocked, there is nothing for them to see...not that they'd really care since the point of a Nexus is to develop on it. You would only be returning it for a hardware issue, and the software unlocking has no impact on the hardware problem, since your hardware issue would've happened no matter what software you had on it. The only way a software thing could cause a hardware issue would be if you over-overclocked it & cooked some parts. You'd really have to work at doing that since these things usually shut down when the temperature gets too high.
In short: root it & enjoy it!

Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app

Lemegeton300 said:
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes. When you restore a backup it will be just as it was when you made it. Have fun!

How to Root with Minimum Impact

Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?

You'll need adb/fastboot + the appropriate drivers.
-unlock BL via fastboot,
-flash recovery via fastboot,
-flash SU zip via recovery,
-leave BL unlocked, no reason to relock it.
That's it. Don't remove, or rename any system apps if you want the OTA to apply. You can even flash OTA's via a custom recovery, this will likely be available here prior to you getting a notification.
Good info here: http://forum.xda-developers.com/showthread.php?t=2010312

So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.

mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You know when you are on other phones, you are actually unlocking the bootloader via a exploit or through the manufacturers developer center.
You need a custom recovery in order to obtain root. It is a must need, without it you cannot be rooted.
Only way to change your recovery is to unlock the bootloader. Having a locked bootloader locks it so your recovery can't be changed. So.... You get the idea
Sent from my Nexus 4 using xda premium

mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You can do it via adb with an insecure boot image, outlined here below the CWM method: http://forum.xda-developers.com/showthread.php?t=1993331&highlight=insecure
If you do it the CWM, or TWRP way you can flash the stock recovery again. You absolutely have to unlock the bootloader however, no way around that.
CF Root is another option: http://forum.xda-developers.com/showthread.php?t=2025274

i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.

phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.

threeclaws said:
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
Click to expand...
Click to collapse
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.

phermey said:
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
Click to expand...
Click to collapse
I also could drop it into dropbox but that is all more work than just hitting "install" on my phone, it isn't like updates are released with enough frequency that the amount of work matters but like I said OTA is more convenient for me and CWM made it even more convenient. The OP may have completely different reasons for wanting OTA.

phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.

ORStoner said:
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
Click to expand...
Click to collapse
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688

phermey said:
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
Click to expand...
Click to collapse
I wasn't being a smart ass nor was I unaware of other ways to get an OTA update, you said there was no reason for OTA on a nexus device and I responded why someone would want it.

clockcycle said:
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Don't use toolkits take the time and learn how to do it yourself so if you get into situations where you messed something up you know how to fix it as you know how adb and fast boot will work.
Toolkits are not worth the short cut
Sent from my Nexus 4 using xda premium

Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium

ORStoner said:
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is the best way to do it. Yes you can fastboot boot cwm so it'll be temp and just install supersu zip. Regarding warranty for bootloader, it originally came locked so should you need to return it, warranty will be voided if you unlock it. However, it would really be just fastboot oem lock if you need to relock it. The state won't show relocked if you do it. It'll be plain locked
Sent from my Nexus 7 using Tapatalk 2

Rooting and unlocking N7

So I am going to be getting a N7 for Christmas, and I was wondering, should I root and unlock the tab before even setting it up? And should I accept the 4.2.1 update before or after doing all this?
Outdated yet young Motorola Photon 4G

I just did mine today on nexus 4 and 7. I had to read everything carefully to find out this was the method that I find it was easy. Make sure you read everything first. Look at the video for 4 and it should be similar to 7 and instructions are provided in link as well. btw I rooted it on 4.2.1.
As rooting will factory reset your device, it will delete all your data. Make sure you backup first.
http://forum.xda-developers.com/showthread.php?t=1766475

Do yourself a favor and learn to do it manually first before using toolkits. There is a lot of tutorials on doing so.http://forum.xda-developers.com/showthread.php?t=1741395 Use fastboot to unlock device:
Command= fastboot OEM unlock
Select yes on your device to unlock boooader.
Install a custom recovery( I would reccomend twrp) and flash supersu zip and you are now rooted.
Need to go back to stock then this is great http://forum.xda-developers.com/showthread.php?t=1907796
Yes toolkits do work but if things go wrong its good to know what to do.

Travisdroidx2 said:
Do yourself a favor and learn to do it manually first before using toolkits. There is a lot of tutorials on doing so. Use adb to unlock device:
Command= adb OEM unlock
Select yes on your device to unlock boooader.
Install a custom recovery and flash supersu zip and you are now rooted.
Need to go back to stock then this is great http://forum.xda-developers.com/showthread.php?t=1907796
Yes toolkits do work but if things go wrong its good to know what to do.
Click to expand...
Click to collapse
I had no intention of using a toolkit lol. Link to the best method to root/unlock?
Outdated yet young Motorola Photon 4G

Lol good deal added another link that you are looking for.
http://forum.xda-developers.com/showthread.php?t=1741395

Travisdroidx2 said:
Lol good deal added another link that you are looking for.
http://forum.xda-developers.com/showthread.php?t=1741395
Click to expand...
Click to collapse
Answered my edit before I could post it. You read my mind!
Outdated yet young Motorola Photon 4G

Nexus 7 root and unlock.
Slender Troll said:
So I am going to be getting a N7 for Christmas, and I was wondering, should I root and unlock the tab before even setting it up? And should I accept the 4.2.1 update before or after doing all this?
Outdated yet young Motorola Photon 4G
Click to expand...
Click to collapse
I bought my Nexus 7 about 2 weeks ago. I set it up then downloaded the jb 4.2.1 update. You will have to unlock before you root. I then downloaded Wugfresh Nexus 7 Tool kit to my computer. Very easy to follow instructions. The kit will take you through the steps on unlocking and rooting. There are videos on this procedure. I did not flash CWM and opted to flash TWRP. Excellent recovery system. I downloaded Goo manager app and you can install TWRP within the app. Very easy. You can then make nandroid backups and install custom roms. I am currently on Cyanogenmod 10.1 nightly.Cyanogenmod now has an updater within and it will search for new nightlys and also install them. Very easy. Hope this helps.

I do prefer twrp over cwm. And I was a long time cwm user before. You can fastboot the twrp.IMG file. And if you Fastboot twrp you will not have to rename .bak the stock recovery.
And yes you will want to unlock it and root it first thing since the unlock wipes the entire device.

What's the difference between CWM and TWRP?
Edit: Swipe was acting up.
Outdated yet young Motorola Photon 4G

In my opinion twrp gets more support and updates. Is way faster than cwm and you will never look back. Twrp is a great recovery.

Ok. So if/when I root the 7, I will be using a computer running windows xp, and I don't know how to install the correct files and where.
Outdated yet young Motorola Photon 4G

Hey, I'd like you to help me decide whether I should root my Nexus 7 or not. This is my first android device and I'm a complete 'noob.' Since then I've been reading about rooting continuously and I would've done it already but I'm a bit concerned. I don't want to lose my warranty and I'm aware that I can unroot the device to get my warranty back but what if something happens to the screen or the power button, or what if it bricks after losing battery power? (I read somewhere that this happened to him during night, the device ran out of juice and he couldn't turn it on ever again) Would I still be able to unroot it so I could return it for repair?
My other concern is about the rooting process itself. I've read that it's 99% safe with a toolkit but anything can go wrong. Is this 1% a big risk? Would I be able to unbrick it if something happened? Since I'm a noob my only reason to root my device is to be able to run memory editors like gamecih or something like that. Are the risks worth it?
Thank you for your answers.

BenFuF said:
Hey, I'd like you to help me decide whether I should root my Nexus 7 or not. This is my first android device and I'm a complete 'noob.' Since then I've been reading about rooting continuously and I would've done it already but I'm a bit concerned. I don't want to lose my warranty and I'm aware that I can unroot the device to get my warranty back but what if something happens to the screen or the power button, or what if it bricks after losing battery power? (I read somewhere that this happened to him during night, the device ran out of juice and he couldn't turn it on ever again) Would I still be able to unroot it so I could return it for repair?
My other concern is about the rooting process itself. I've read that it's 99% safe with a toolkit but anything can go wrong. Is this 1% a big risk? Would I be able to unbrick it if something happened? Since I'm a noob my only reason to root my device is to be able to run memory editors like gamecih or something like that. Are the risks worth it?
Thank you for your answers.
Click to expand...
Click to collapse
In all honesty, a toolkit is almost completely unnecessary for the Nexus 7. You can do everything yourself in about 5 minutes. The thing about the Nexus 7 is that Google knew that people would try and do things with it, so they made it easy (How it should be with every device). One thing you should take into consideration when unlocking/rooting any device is "Why am I doing this?" If the answer is "Cuz I can!", you probably shouldn't. If you want to be able to use advanced apps that require root, go right ahead. Even if you are having performance problems, and just want to fix them by installing a new ROM after you unlock, go for it. If not, don't worry about it.

[Q] regarding: Loki + TWRP + Motochopper CASUAL

Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug

DougYITBOS said:
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
Click to expand...
Click to collapse
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.

Thanks a bunch TheAxman
You said...
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
Click to expand...
Click to collapse
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?

DougYITBOS said:
Thanks a bunch TheAxman
You said...
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
Click to expand...
Click to collapse
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
And btw, if this person xBeerdroiDx gives me a thanks, he is saying I did ok... If you seem to have anymore questions, his guide is one of the best....
[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]
http://forum.xda-developers.com/show....php?t=2314494
Thanks to xBeerdroiDx - For this great Startup Guide

Thanks again!

DougYITBOS said:
Thanks again!
Click to expand...
Click to collapse
Your quite welcome, if you have any other questions, feel free to ask them in the thread I gave you or mine.
http://forum.xda-developers.com/showthread.php?t=2295557

Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.

orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
btw..this is cool, name please.
Dog: [Pitbull Sharpei Mix] Rom: Stock

TheAxman said:
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
Click to expand...
Click to collapse
ah good idea. i suppose airplane mode would accomplish the same thing as well

orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.

CamFlawless said:
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
Click to expand...
Click to collapse
Thank you sir, appreciate the help, and yes, good idea.

TheAxman said:
Thank you sir, appreciate the help, and yes, good idea.
Click to expand...
Click to collapse
might have been a placebo effect for me, lol.

TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Click to expand...
Click to collapse
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G

lilbigdude1 said:
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
Click to expand...
Click to collapse
somewhat, but as soon as you root, your phone status is custom correct? therefor how can it update? Yes, it is better to do a custom rom, but you can still stay on MDL and never get updates, freezing the samsung update will work, but I gave the easiest way in his situation.

TheAxman said:
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
Click to expand...
Click to collapse
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...

texasniteowl said:
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
Click to expand...
Click to collapse
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.

TheAxman said:
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
Click to expand...
Click to collapse
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.

texasniteowl said:
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
Click to expand...
Click to collapse
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.

TheAxman said:
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
Click to expand...
Click to collapse
if you are paranoid then there are 3 files you can freeze. i cant remember which ones, but one is att update something something, thats all i can remember.
im no help

I think everyone gets the picture.
Sent from my GT-I9505 using xda premium