i have rooted and unlocked my nexus s. now i have to return my phone and i want it to be completely stock again and locked is there a way to do this?
I wouldnt really worry about it i had to return 2 of them an never had any problems returning the phone
Depends on how you rooted. If you used Superboot, I'm not sure.
The other methods, just use the terminal or adb to delete the su binary from /system/bin. Check /system/xbin and delete any reference to su and any symlinks that busybox created. You'll also want to remove the superuser.apk and busybox, this should be doable from the Market app or app manager in settings.
Finally, do the fastboot oem unlock command again (even though you're unlocked) to completely wipe all personal data from the phone.
Then do the fastboot oem lock command to get rid of the unlocked icon on boot up.
Like the 2nd poster said, no one seems to have had problems returning a rooted phone so far. YMMV.
Related
I was wondering if someone could point me(links) in the right direction for the best/easiest way of going back to stock with the stock recovery and bootloader locked. I need to exchange my phone at best buy. Thanks in advance to anyone who could help!
651stp said:
I was wondering if someone could point me(links) in the right direction for the best/easiest way of going back to stock with the stock recovery and bootloader locked. I need to exchange my phone at best buy. Thanks in advance to anyone who could help!
Click to expand...
Click to collapse
Are you on a custom ROM?
If you're on the 2.3.1 update, every boot of the phone will rewrite the recovery partition back to stock (unless you've renamed the script that does that).
If not, a simple fastboot oem lock, then another fastboot oem unlock will totally wipe all data from the phone, including the sd card space. Then you can fast boot oem lock again to re-lock it.
This won't actually get rid of the root files (su binary, possibly superuser as well), but for exchange purposes you can be pretty sure Best Buy's not going to look for that.
If you really want to gid rid of all evidence of root, you could use a root enabled file explore to delete the /system/bin/su binary, and Titanium or file explorer to uninstall/delete superuser.apk.
The above is the method I'd use. There are several threads about this and other methods, a quick forum search should have revealed them.
Here's one discussion: http://forum.xda-developers.com/showthread.php?t=895728&highlight=return+stock
And it's also covered in the FAQ, not too far from the top. http://forum.xda-developers.com/showthread.php?t=882815
look through my threads for a guide to revert back to stock recovery and unroot phone
Hey guys
(Sorry think i posted this in the wrong section first time round)
Got a MID816R2 stuck on 2.3.1 seen some nice new Roms out there and firmware updates, but cant seem to get them onto the device! Rom manager clockworkmod recovery does not list this device so cant use this (unless someone can tell me different)
Terminal emulator gets denied by Superuser.
even tried ADB, but get a permission denied message
Other issue is even though i can transfer files via USB direct to PC, and device is shown on ADB, there seems to be a driver issue in recovery mode, tell me no driver for android 1.0 strange cos i am running 2.3.1 which came from the seller installed
Is there any kind of Bootloader unlock tool????
Anyone knowing any way to update the firmware or install Roms on this device please help :-(
If you're getting a permission error using ADB then make sure you type sudo in front of it.
ROM Manager put out an update today to help with new or unrecognized devices. But let me ask you this. Have you rooted it first before you try and flash CWM and junk?
Hi,
Thanks for the first response
Yes its rooted (using superoneclick)
I think the bootloader is locked from the seller? i did hear they are releasing rom manager 5 soon, so if they do list the MID816R2 my issue should be solved?
When you say type sudo in front of it, you mean in front of ADB or ADB then SUDO then command?
Thanks again ;-
I mean type sudo before anything else in the command.
If SU is denying you then you're not rooted. Or SU is just being silly. Make sure your binary is updated for SU and if you're still getting permission errors and whatnot try rooting it again. I've seen it before where it only does a halfway root and installs SU without actually gaining root access.
Thanks for the advice, i used root checker, and it says rooted and busy box installed? used superoneclick to get root as nothing else was working, is there anything better to get root? (although i do think its rooted)
Try the super one click root. Put the phone on debug mode. More information add on msn. [email protected]
Sent from my GT-I9000 using xda premium
First off, I've been reading all around here, and this doesn't seem like an uncommon problem.
I'm trying to edit my build.prop file to be able to unlock APN access on my Verizon phone as I need to use it for T-Mobile.
My problem is that nothing in system files that I edit, including build.prop, will stick. I have used Root Explorer Pro, buildprop editor, adb cmd promps. My phone is rooted through weaksauce 2.
Once I edit file, I save it, set chmod to 644 and restart. The build.prop isn't being editted back to the default, it's just being replaced completely-- it will be right back to the default build.prop file that was originally there, with the same original create date and everything.
I've tried everything I know, and I absolutely cannot get anything to stay editted because no matter what I do, the phone will just replace my phones as soon as I boot.
My phone does not have a different ROM installed, and it is still S-ON, but I've tried to stay away from getting that far into it for something that I thought should be pretty simple to fix. Any advice?
storyquest101 said:
First off, I've been reading all around here, and this doesn't seem like an uncommon problem.
I'm trying to edit my build.prop file to be able to unlock APN access on my Verizon phone as I need to use it for T-Mobile.
My problem is that nothing in system files that I edit, including build.prop, will stick. I have used Root Explorer Pro, buildprop editor, adb cmd promps. My phone is rooted through weaksauce 2.
Once I edit file, I save it, set chmod to 644 and restart. The build.prop isn't being editted back to the default, it's just being replaced completely-- it will be right back to the default build.prop file that was originally there, with the same original create date and everything.
I've tried everything I know, and I absolutely cannot get anything to stay editted because no matter what I do, the phone will just replace my phones as soon as I boot.
My phone does not have a different ROM installed, and it is still S-ON, but I've tried to stay away from getting that far into it for something that I thought should be pretty simple to fix. Any advice?
Click to expand...
Click to collapse
I'm pretty sure it comes down to you still being stock & s-on. There's some sort of wp (write protection) which must be turned off in order for you to be able to make changes to the system partition that won't be referred upon reboot. I think wp-off is a feature of all kernels but it may be something from the rom. Maybe it's tied to a locked/unlocked bootloader, he'll I dunno. Either way, whatever exactly it is, wp is your problem. The moment you unlock & s-off your device you'll be able to flash what you want and make such changes.
cntryby429 said:
I'm pretty sure it comes down to you still being stock & s-on. There's some sort of wp (write protection) which must be turned off in order for you to be able to make changes to the system partition that won't be referred upon reboot. I think wp-off is a feature of all kernels but it may be something from the rom. Maybe it's tied to a locked/unlocked bootloader, he'll I dunno. Either way, whatever exactly it is, wp is your problem. The moment you unlock & s-off your device you'll be able to flash what you want and make such changes.
Click to expand...
Click to collapse
Correct. User must s-off since its vzw.
Op- I hate to tell you think but the vzw m8 is a terrible choice for T-Mobile. You might have better luck selling that one on swappa and getting a T-Mobile one off swappa.
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.
Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie
and To do root to a pixel is worth it??
oraned said:
and To do root to a pixel is worth it??
Click to expand...
Click to collapse
Yes.
It's a personal preference. I am rooted for Titanium backup, Adaway, and Flash kernel.
Sent from my Pixel 2 using Tapatalk
Other than OTA updates requiring sideloading, what are the drawbacks of rooting? Does Google Pay still work? Are there any apps which will fail to run? Any other negatives?
huladaddy said:
Other than OTA updates requiring sideloading, what are the drawbacks of rooting? Does Google Pay still work? Are there any apps which will fail to run? Any other negatives?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=why+to+not+root+android
System rooting, if done properly, is just adding the (call it file or utility - it's both from a Linux viewpoint) file su to the system, so it's not a matter of damaging the phone or rendering it useless. And with Magisk (systemless rooting) it's even easier. Magisk will restore the boot partition (which is all it modifies) so you're left with an untouched phone and, if you really want it stock, you can always boot to TWRP (without installing it), back up your data, copy the backup and /sdcard ro a PC, flash the latest factory ROM, boot to TWRP, restore it, copy /sdcard back and aside from the bootloader being unlocked, you haven't done anything.
The question, though, is whether it's worth it. If you're never going to do anything that needs root access, of course not. It's 10 minutes you'll never get back. But if you want to tweak the kernel, or some other parts of Linux, or you want to run something that will only run with root access, I don't see any reason not to - as long as you know what you're doing and don't brick the phone. (I've recovered from what I call a "semi-hard brick" twice [level 2 tech support actually shipped a replacement phone because they were convinced that it was bad hardware, but I figured out how to recover from the problem in software], so I think the phone is pretty "recoverable".) And if you run Linux, running without su or sudo just feels wrong - it's like running on one leg. Just remember to exit if you run su in a terminal, for the usual reasons - rm -r -d --no-preserve-root will still remove the entire partition. (Which should still be recoverable from, unless you get really stupid.)
Rukbat said:
System rooting, if done properly, is just adding the (call it file or utility - it's both from a Linux viewpoint) file su to the system, so it's not a matter of damaging the phone or rendering it useless. And with Magisk (systemless rooting) it's even easier. Magisk will restore the boot partition (which is all it modifies) so you're left with an untouched phone and, if you really want it stock, you can always boot to TWRP (without installing it), back up your data, copy the backup and /sdcard ro a PC, flash the latest factory ROM, boot to TWRP, restore it, copy /sdcard back and aside from the bootloader being unlocked, you haven't done anything.
The question, though, is whether it's worth it. If you're never going to do anything that needs root access, of course not. It's 10 minutes you'll never get back. But if you want to tweak the kernel, or some other parts of Linux, or you want to run something that will only run with root access, I don't see any reason not to - as long as you know what you're doing and don't brick the phone. (I've recovered from what I call a "semi-hard brick" twice [level 2 tech support actually shipped a replacement phone because they were convinced that it was bad hardware, but I figured out how to recover from the problem in software], so I think the phone is pretty "recoverable".) And if you run Linux, running without su or sudo just feels wrong - it's like running on one leg. Just remember to exit if you run su in a terminal, for the usual reasons - rm -r -d --no-preserve-root will still remove the entire partition. (Which should still be recoverable from, unless you get really stupid.)
Click to expand...
Click to collapse
Thanks for the great reply. My experience has been with rooting Samsung phones, and one of my concerns is tripping an equivalent KNOX meter. Reading between the lines, it appears that the Pixel 2 XL doesn't have anything like that and that it should be possible to completely make the phone stock again. Am I correct?
huladaddy said:
Thanks for the great reply. My experience has been with rooting Samsung phones, and one of my concerns is tripping an equivalent KNOX meter.
Click to expand...
Click to collapse
Maybe Knox make economic sense to Samsung, AT&T and Verizon, but I consider it the worst thing ever done to cellphones.
Reading between the lines, it appears that the Pixel 2 XL doesn't have anything like that and that it should be possible to completely make the phone stock again. Am I correct?
Click to expand...
Click to collapse
Unless you format the bootloader partition (which would take a bit of doing). I can imagine it happening, but after 45 years of developing software, I can't figure out how to do it with the tools available.
I like to root for Titanium backup, Adaway, Solid Explorer, Custom kernels, Magisk Modules, ...
This phone has the ringtone and notification volumes mixed. Root is worth it to have that separated; sadly I'm on Verizon. Other than that I'm pretty content.....