Hi Everyone,
Sorry if this has been discussed in lengths somewhere, I wasnt able to find full information so I just wanted to make sure I got the right idea before proceeding with removing root. I need to go back to full stock no root or recovery. according to some info on this forum
http://forum.xda-developers.com/showthread.php?t=1739426
I need to use Odin to flash the stock image for my phone (bell). after doing that i need to go in with root explorer or adb shell and delete the superuser and associated binary files, this is where I am not 100% sure does this mean the following 3 files:
1- /System/app/SuperSU.apk
2- /System/xbin/busybox
3-/System/xbin/su
are there any other files that need to be removed?
thank you very much for the help.
You just need to use a nonrooted stock img, then boot into factory recovery and do a factory reset. No need to manually attempt to remove root
Related
i am on my way to root it now guys, need help with few questions to remove my confusion. this forum has benn the most helpful for me, i hope i get further answers as well:laugh:
1. what if i root it and dont do anything else , what are its benefits, and will i still get ota
2. if i install a custom ROM , WILL i get ota. and where will be my stock rom and how i can get it back.
3. ehy do ineed to install a custom recovery while rooting.. will it effect my ota and how can i go back to my original recovery. i hope somebody sheds light on all these, as my phone is unlocked and i am waiting for answers to further proceed, thanx
i used jubakuba method to install sdk and pdanet to install driver, it didnot work, it didnot work so i went to samsung website to get latest driver,
what does flashing , reflashing recovery means
1. You'll be able to modify system files and have SuperUser permissions.
2. Assuming you only root and install a custom recovery you will be able to OTA. Your stock ROM gone, you can flash a factory image if you need it back.
3. You need a custom recovery so you can flash custom ROMs.
To be honest I don't think you have any business rooting your phone. You obviously have no need to and lack the drive to research on your own. OTA's also appear important to you so that's another reason to just stick to stock.
063_XOBX said:
1. You'll be able to modify system files and have SuperUser permissions.
2. Assuming you only root and install a custom recovery you will be able to OTA. Your stock ROM gone, you can flash a factory image if you need it back.
3. You need a custom recovery so you can flash custom ROMs.
To be honest I don't think you have any business rooting your phone. You obviously have no need to and lack the drive to research on your own. OTA's also appear important to you so that's another reason to just stick to stock.
Click to expand...
Click to collapse
thank you so mcuh for all these answers, actually i am searching the net quite thoroughly, but some of these basics i needed to learn.
Hi all
My USB connector does not work, I would send him assistance, but unfortunately my device has the bootloader unlocked, with root and rom Mincov6.
I tried to use Mobile Odin, I downloaded directly from the phone the factory image of 4.2.2 and tried to open the file .tgz, however, tells me: "Partition could not be found in file."
What can I do? I'm desperate, I await your response
Thanks in advance.
Sorry for english, but i'm italian :crying:
http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128
bodh said:
http://forum.xda-developers.com/showpost.php?p=27945515&postcount=128
Click to expand...
Click to collapse
My device is GSM, not Verizon
It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.
bodh said:
It's the same method, except you need odin flashable .tars for gsm...Unfortunately the link in that link only leads to verizon, but if you can find or make the tars, and follow that guide, you're in business.
Click to expand...
Click to collapse
From what I understand, who used the Verizon tar in GSM, brock the device.
Now, I can not find anywhere the. Tar for GSM..
This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..
bodh said:
This is something i've looked up, but haven't truly found yet. How to make an odin flashable .tar.. After all, your best bet is to make it yourself and then you know what you're getting.
EDIT: try googling "how to make an odin flashable tar", you'll get better results than the built in xda search..
Click to expand...
Click to collapse
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?
Try this
ciccionicosia said:
I was able to get me by a friend a nandroid backup, I locked the bootloader and I did Unroot with the use of some applications.
Now I should return the stock recovery .. How do I?
Click to expand...
Click to collapse
You should've replaced the stock recovery before locking the bootloader. You can try finding a flashable .zip of the stock recovery, but it'd probably have to be made. Has the device ever gotten an OTA update? I'm thinking you could use the following OTA script and patch to reflash the stock recovery in a very minimal sort of way.
First, you'll have to re-root by installing supersu.zip from sdcard download via custom recovery(which youll need to remove later).
Install Root Browser Lite by jrummy, and say no to installing the additional features (you may have to remove some binaries from your sdcard later after unrooting).
Unzip the attachment.
Place the install-recovery.sh in /system/etc/ with r-xr--r-- permissions and root root ownership and group ownership (via long pressing the file once it is in place, first permissions, then ownership).
Place the recovery-from-boot.p in /system/ with rw------- permissions and root root ownership and group ownership (same way as above).
Now power down.
Boot into recovery from fastboot (vol up+down+power, scroll with volume keys until the top says recovery, then press power).
Does it say android recovery on top, or is it still your custom?
If it's stock, let it sit until it boots on its own.
Remove the supersu.apk and su binary via root browser.
Remove rootbrowser and its binaries on the sd.
You should now be in business.
P.S. You could also look for an odin flashable .tar for your device, and flash it to return, but i think that'd be more complicated for you. Those files I provided are put in place during every ota update, and I believe this should work for you.
Hi,
So there seem to be quite a few tools and methods out there with which you can root your phone, but what if I really only want to root it and nothing else; my only goal is to use apps that require root access.
I've got Android 4.1.1, but I suppose it shouldn't matter that much. Will I be able to update to a newer version with root access though?
Forgot to add:
What will I need to back up and how do I transfer my settings and contacts? I don't care much for lost apps since I don't have many.
Unlock the bootloader and flash a custom recovery. After that you make a nandroid backup and then install the superuser root script to give root acces in the rom.
Flash back the stock recovery and you are able to receive and install official ota's.
Is this all possible with this tool?
Now I don't want to act dumb or seem inept, but could you or someone else give me a more detailed description, maybe with a link or two?
Yes you can use that tool :thumbup:
Did you see my edit to the first post?
>>What will I need to back up and how do I transfer my settings and contacts? I don't care much for lost apps since I don't have many.
Can you tell me why I need to flash a custom recovery? Can't I 'just' root my phone as is and then leave it like that- rooted of course?
You can use an app called carbon to make a backup. You need a custom recovery to install the super user script. A stock one is not capable if doing that. And you don't root a phone. Only its software !
With hassoons tool, how do I flash the stock ROM back on it? I can see no option in his thread...
The stock nandroid backup needs to be installed via the custom recovery. Not with hassons tool kit. You can in that case only flash back the stock boot.img from the stock backup.
Hi, I decided I wanted to go through with my plans to root the phone and already run into a problem:
http://forum.xda-developers.com/showthread.php?p=43066305&posted=1#post43066305
Most recentpost...
EDIT: Selected Power down on the phone because I was getting impatient and paranoid and then disconnected the phone. Everything seems fine so far. I closed the console and the message "Get Token ID.." popped up and then the console reopened, apparently searching for the phone... -_-
Oh well, maybe next time. Right now I want to take a break/try something else.
Can someone tell me why Windows always trys to install new drivers even when they already are installed? Happened when I used the programm- updating drivers blabla...
I'll try again here...
Just a question:
Can I definitely receive official android/sense/hwatever ota updates but still keep the root access?
What i've gathered so far is that I need to use hassoons tool and how to guide,but only the first post.
After that I will have a rooted stock ROM with ClockworkMod recovery, right?
Then I should do a nandroid backup WITH CWM (how is this done exactly? hold volume down +power button, then recovery?)
What will be backed up with the nandroid backup? How big will this be roughly and can I/should I put it on PC to free up some space?
Regardless from this backup, I only need the recovery.img, which in my case will be MY personal backed up STOCK recovery.img,is that correct?
How do I flash my stock recovery?
Edit:
Once I have the stock recovery again, will my phone still have root access? Is everything from then on -stock- except for root access?
Hi All,
I have seen many tutorials here for rooting of Gt-n7100 and have one common doubt on this. I am currently on 4.4.2 (stock firmware) and knowing that we ain't getting Lollipop, finally decided to give the Root a go.
However i am on MAC and just want to know how can i root simply via ADB and without applying any custom rom's to it. Just want to keep the device completely Rooted to access everything inside it. I see everyone saying to download stock rom, but why is that needed? I just want to get complete Root privileges that's it.
So any help or tutorial would be appreciated.
Thanks!
Anyone?
hidden_talent said:
Hi All,
I have seen many tutorials here for rooting of Gt-n7100 and have one common doubt on this. I am currently on 4.4.2 (stock firmware) and knowing that we ain't getting Lollipop, finally decided to give the Root a go.
However i am on MAC and just want to know how can i root simply via ADB and without applying any custom rom's to it. Just want to keep the device completely Rooted to access everything inside it. I see everyone saying to download stock rom, but why is that needed? I just want to get complete Root privileges that's it.
So any help or tutorial would be appreciated.
Thanks!
Click to expand...
Click to collapse
- You need Heimdall: http://glassechidna.com.au/heimdall/
- You need cf auto-root: https://download.chainfire.eu/264/CF-Root1/CF-Auto-Root-t03g-t03gxx-gtn7100.zip?retrieve_file=1
1. Install Heimdall
2. Inside the cf auto-root zip there is a file ending with .tar.md5. Extract that file and inside that file there are two files:
recovery.img and cache.img
3. Place those files in the same folder.
4. Open terminal on your mac. Navigate to the folder where you have place those two files.
5. The type: "heimdall flash --recovery recovery.img --cache cache.img" (without the ")
That should be it.
As the title suggests, my LG G4 is having some trouble taking the 13B update. I am rooted, but still very stock.
I've narrowed down the problem file and I really just want some advice on it, I can fix it but I need to know what the repercussions of the fix will be...
According to the logs in /cache/fota the problem file is app_process64. Upon inspection, something has modified it and nicely backed it up. By modified I mean it's a 0-Byte dummy file, with a 17 KB original file next to it. Of course the obvious fix for the OTA is to restore the original, which is how I fixed the last OTA I had trouble with, but I need to know what might have done this in the first place, and is it safe to undo using root browser?
I am, as always, fully prepared to lose everything and start over with my Titanium Backups and copy of my /sdcard.
EDIT: Looked closer and it appears to have been modified 9/18/15. The file I fixed for the last OTA to work (install-recovery.sh) is also a 0-Byte dummy with a backup again. Weird.
The only thing I can think of that would mess with the system like that is busybox, and I do see that the dummies are symlinked to ../xbin/daemonsu so maybe I should try unistalling the busybox applets.
EDIT 2: It wasn't busybox, and I'm not willing to unroot to test if it was supersu. I'm just going to go for it. Wish me luck.
EDIT 3: Well I guess it was required to be like that for root. After restoring the backups and rebooting SuperSU reports no binaries and closes. *Sigh* At least the OTA worked. But I guess now I need to find a 13B Stock Rooted image to get my root back, right?
Yep, you cannot be rooted or have modified system files, so solutions would include to find and flash an unrooted system image, or find and flash a rooted, 13B image or what you did - unroot step by step.
You can either find and flash one of the many rooted 13B images or take your current image and use the root injection method to make it rooted, then flash it.
Backup your current rooted image as cheap insurance and leave it on internal storage until you very the rooted image is good.
divineBliss said:
Backup your current rooted image as cheap insurance and leave it on internal storage until you very the rooted image is good.
Click to expand...
Click to collapse
Good advice... but how would I backup the system if I have no root?
Starcruiser322 said:
Good advice... but how would I backup the system if I have no root?
Click to expand...
Click to collapse
Look for the "low effort root" G4 thread that refers to using the "dd" command to dump the system partition to internal storage.
Post a link here when you find it.
EDIT: HERE http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
That thread refers to another thread that has the dd command you need to backup your system image.