What is a good way to remove the super user app without root or USB function(hardware issue). I have to send my phone back in a couple days to get a new one and need to get rid of custom lock at the startup. I have the att i337. The only way USB works is in download mode.
You can use triangle away to get rid of the custom status and then use a root Explorer to delete the busybox files after that use SuperSu 's built in uproot to finish up. You might want to delete the busybox before triangle away.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
The script files are not installed so I do not have root.
Sorry, misread your post.
You have to have root to remove the custom status.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Is there a way to root without USB ability on device? It will only connect to pc in download mode. All other USB options won't work because of hardware issue. I just need to find a way to root without usb. I do have a sd card and reader.
It's not a hardware issue. If it is connecting through download mode, it is either a driver issue, a port issue on your computer or the software on your phone is borked and you can ODIN it to fix it. This is not a hardware issue on the phone at all.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Related
Has anyone tried this method? SuperSU has a full unroot option in its settings. I have read many posts saying it is impossible to unroot at this time.
I did a little searching around and didn't find much. Just suggestions to try it and no one ever reported back if it works or doesn't.
I personally don't have the OTA and have a custom ROM, but i would like to know any confirmation of it working or not working by anyone that has tried it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I did the ota to mf3 and successfully rooted it I then realized that I had like 6gbs missing so in an effort to restore I went into the SU settings and chose the remove root option and it seemed to work I checked with root checker and I no longer had root access I still was unable to restore it just bumps me into Odin mode and I have to boot power+home+volume- then cancel to reboot my phone into working order
But as far as I can tell I have no root
Since I can't restore and try and clear up my missing storage I wanted to take it in and try and get a new one under warranty but I'm afraid to use triangle away so I'm just gonna wait it out until we get a mf3 restore firmware for Odin since my phone works fine for now
Sent from my SAMSUNG-SGH-I337 using xda premium
So that is 1 confirmation for an unroot. Basically hit unroot, it sends the phone to bootloop. Remove battery, put it back, then boot to download mode with power+volume down, then hit volume down again to cancel and reboot to a fully functional phone with no root. If that doesn't work, use power+home+volume down. Anyone else?
Btw,
Don't use triangle away. It flashes a temporary recovery to reset the binary. It will brick you or just fail.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Has anyone tried this method? SuperSU has a full unroot option in its settings.
Click to expand...
Click to collapse
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
graydiggy said:
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This method also worked for me as well. Had no problems following the steps.
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good info to know. Thanks graydiggy
I am going to change this to a how to thread later today. Anyone else try it?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
this may be a stupid question, but if you went through the trouble of rooting after the mf3 update.. why would you want to unroot?
Warranty replacement in case of a hardware issue, testing purposes, also, some people only want a temp root to remove bloat. After that, they don't want root anymore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
Click to expand...
Click to collapse
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
05.09.2013 - v1.60
- Added SELinux+Enforcing compatibility (for new SGS4 ROMs)
- Fixed (newest) CWM versions asking you question that break root if answered wrongly
- Fixed issue with the TWRP/CWM binary installer
- Fixed 4.3 OTA survival looping
Click to expand...
Click to collapse
Does the new update have something to do with our mf3 baseband like SELinux?
haremmon said:
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
Does the new update have something to do with our mf3 baseband like SELinux?
Click to expand...
Click to collapse
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
WezzleD said:
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
haremmon said:
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
Click to expand...
Click to collapse
I'm actually not sure. Didn't look at version numbers.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4 confirmed. Let's get 5 and I will post a how to.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
That method worked for me also. I'm so glad it was discovered. Successfully unrooted.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to unlock as well. However my phone stopped showing the custom unlocked symbol at bootup a few days ago (before doing this) and I am at a loss as to why. So I am not sure I can count as a real confirmation.
I did your unroot process, root checker confirms I no longer have root and the unlock symbol has not come back.
Stay tuned guys. Getting everything ready to quickly make a more organized how to.
Being horribly sick is not helping
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Im having trouble deciding if I should root or not.
For the most part I am happy with not. However I want to backup my apps and device settings to either my PC or a memory stick.
I figured I could attach a micro USB to female USB cable and stick a USB memory stick on in and back up to that.
Do I need to root the device for that?
Also I wouldn't mind editing a few saved game files.
What are the risks of rooting, other than invalidating a guarantee? I don't intend to flash the ROM.
Also if rooted, how easy is it to unroot if I had to return it in the event it needed a repair?
Thanks
I wouldn't root if I didn't need tethering. Still happy with stock but that's the only way to get hotspot to work. I know that doesn't really help with your question
Sent from my VS980 4G using Tapatalk
Adaway requires root, and I hate ads
Sent from my Nexus 7 using XDA Premium 4 mobile app
So have we herd yet if we can " re lock" our phones after rooting. I know with my experience with the galaxy nexus that I could do that in case I had a warranty issue with verizon. That is the only worry I have with rooting especially with lg having a root checker or "root trip".
I flashed my D801 to stock because I accidentally wiped both internal data and system in recovery. Now when I try to root using the root tool, I get this. It says the apk is installed already (because I tried it multiple times) but the actualy binaries required for root arent being pushed (probably because it can't mount system)
aranurea said:
I flashed my D801 to stock because I accidentally wiped both internal data and system in recovery. Now when I try to root using the root tool, I get this. It says the apk is installed already (because I tried it multiple times) but the actualy binaries required for root arent being pushed (probably because it can't mount system)
Click to expand...
Click to collapse
SOLVED
Sent from my LG-D801 using XDA Premium 4 mobile app
Put the phone in download mode by turning off device. Hold the volume up button and plug in a usb cable it will tell you if its rooted or unrooted u may still be rootedvif not flash a rooted stock rom
tbishop91 said:
Put the phone in download mode by turning off device. Hold the volume up button and plug in a usb cable it will tell you if its rooted or unrooted u may still be rootedvif not flash a rooted stock rom
Click to expand...
Click to collapse
I appreciate your help but this has been solved as stated above.
Sent from my LG-D801 using XDA Premium 4 mobile app
My computer or any otg cable can't connect to my N4. Trying go back to stock. USB debugging is on.
Sent from my A0001 using XDA Free mobile app
toanau said:
My computer or any otg cable can't connect to my N4. Trying go back to stock. USB debugging is on.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Well, you can theoretically take the stock ROM and stock recovery and flash them, and then use bootunlocker to lock your bootloader, and then removing root from within the root app.
U could do that but it still leave the same problem with the USB not able to connect to the device
Sent from my A0001 using XDA Free mobile app
toanau said:
U could do that but it still leave the same problem with the USB not able to connect to the device
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Well yeah, for that you need some hardware fixing. Go to a service? Or is the phone still in warranty?
Yea It's out of warranty
Sent from my SM-T800 using XDA Free mobile app
same problem
Can't connect to pc for adb & file transfers etc, thought it was a faulty usb connector.
Replaced usb port-microphone part, but problem still persists.
Tried everything, factory reset, flash stock zip, different cables, different computers, re installed drivers & 1000 reboots.
Just keep getting the same result, USB device not recognized. code 43.
I did replace the battery not long ago, but put the old one back in and it still does the same thing.
What could the problem be? If i can replace something, what would that be? :silly:
Bonehead move I know. Now I need some help to fix. I flashed a stock 5.0 ROM and everything was working fine. Got the 5.0.1 prompt so I flashed a stock recovery (4.4.4 hence my problem). Of course the update wouldn't flash. Now to complicate things all of a sudden my PC won't detect my Nexus 4. It detects my wife's Nexus 4 fine so I'm thinking not a cable or driver problem. Ive tried multiple cables and reinstalled drivers with no luck. So now I need to root and or install custom recovery without a PC. Any ideas?
icekold1694 said:
Bonehead move I know. Now I need some help to fix. I flashed a stock 5.0 ROM and everything was working fine. Got the 5.0.1 prompt so I flashed a stock recovery (4.4.4 hence my problem). Of course the update wouldn't flash. Now to complicate things all of a sudden my PC won't detect my Nexus 4. It detects my wife's Nexus 4 fine so I'm thinking not a cable or driver problem. Ive tried multiple cables and reinstalled drivers with no luck. So now I need to root and or install custom recovery without a PC. Any ideas?
Click to expand...
Click to collapse
You're going to need to get your pc to recognize your device. When booted into the bootloader and your device connected to the pc look in device manager. What does it show?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're going to need to get your pc to recognize your device. When booted into the bootloader and your device connected to the pc look in device manager. What does it show?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't show anything. Its as if it isn't connected at all. I've tried from the bootloader and recovery screens and also rebooted both phone and pc. Still shows nothing in device manager. Phone shows charging but no mtp notification or anything that it is connected. As soon as I plug our other nexus 4 in the pc recognizes it immediately.
icekold1694 said:
It doesn't show anything. Its as if it isn't connected at all. I've tried from the bootloader and recovery screens and also rebooted both phone and pc. Still shows nothing in device manager. Phone shows charging but no mtp notification or anything that it is connected. As soon as I plug our other nexus 4 in the pc recognizes it immediately.
Click to expand...
Click to collapse
Is your device still rooted? If so you can flash the stock recovery image file from 5.0 in flashify
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your device still rooted? If so you can flash the stock recovery image file from 5.0 in flashify
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
No I lost root when I flashed the 5.0 stock rom.
icekold1694 said:
No I lost root when I flashed the 5.0 stock rom.
Click to expand...
Click to collapse
I would try deleting your usb drivers on the pc, rebooting and then trying your device again. Flashing the 4.4.4 recovery should not have done anything to mess up your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I would try deleting your usb drivers on the pc, rebooting and then trying your device again. Flashing the 4.4.4 recovery should not have done anything to mess up your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
OK I will try that again and post results. Another possible problem I noticed is in root explorer I have a directory of emulated/0 I don't remember having before.
icekold1694 said:
OK I will try that again and post results. Another possible problem I noticed is in root explorer I have a directory of emulated/0 I don't remember having before.
Click to expand...
Click to collapse
I'm sure that directory was always there. It's a normal directory
Sent from my Nexus 9 using XDA Free mobile app
I uninstalled/reinstalled drivers and still no go. Detects the wifes nexus 4 but not mine. Guess I'm screwed.
icekold1694 said:
I uninstalled/reinstalled drivers and still no go. Detects the wifes nexus 4 but not mine. Guess I'm screwed.
Click to expand...
Click to collapse
To root your device use towelroot from your device. Although I don't know what you're going to do with root. Also, can you get the device detected by your pc when you're booted into recovery or the device?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
To root your device use towelroot from your device. Although I don't know what you're going to do with root. Also, can you get the device detected by your pc when you're booted into recovery or the device?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Towelroot wouldn't work. Says device isn't supported. Maybe it will get updated to work on lollipop. If I could obtain root I can flash custom recovery and start with a fresh install. Just have to find a way to do it with an app