Develop Bugs

[REF] Unroot your phone quick n' easy

Hey guys
I noticed that many people are asking around for a way to unroot their phones, and you hear alot about flashing back as a solution for unrooting, but for me that was abit not preferred. So here is a way to do it quick and soooo easy and you don't even need a computer to do it. We start:
1- From the android market download (Terminal emulator) and run it.
2- Once inside the shell type in these commands (you gotta press enter after each line)
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
and Voila, your phone is now unrooted. needless to say that you should also uninstall the terminal emulator as well. Hope this is useful.

Thumbs up! Someone should have posted this quick and easy method earlier.

Meaning we wont have any warranty issues with Samsung if un-root and send back to service center? Thnx.

well, first of all you need to have the same stock rom shipped with the phone (or the officially upgraded one via kies). Then you should unroot it, then in recovery mode you need to clear cache and do factory reset. and format the internal storage (and of course remove SD card if any) then it will be in the same condition when it was shipped to you. Thats how you avoid trouble with the warranty before sending your phone back for service or replacement.
cheers

mmthabet said:
well, first of all you need to have the same stock rom shipped with the phone (or the officially upgraded one via kies). Then you should unroot it, then in recovery mode you need to clear cache and do factory reset. and format the internal storage (and of course remove SD card if any) then it will be in the same condition when it was shipped to you. Thats how you avoid trouble with the warranty before sending your phone back for service or replacement.
cheers
Click to expand...
Click to collapse
Wow....thnx...this make the whole rooting process sweet.

Great stuff man, well done.

Nice tip!
If you unroot using your method and then wipe the phone completely (cache/factory reset) then place ClockworkRecovery onto internal memory as update.zip and reboot in recovery and make a nandroid backup (doesn't need root) then carry on, should you need to send it in for warranty just restore the nandroid backup and it will be unrooted, stock firmware and fresh You might need to flash the stock modem back though if you change

xfile087 said:
Nice tip!
If you unroot using your method and then wipe the phone completely (cache/factory reset) then place ClockworkRecovery onto internal memory as update.zip and reboot in recovery and make a nandroid backup (doesn't need root) then carry on, should you need to send it in for warranty just restore the nandroid backup and it will be unrooted, stock firmware and fresh You might need to flash the stock modem back though if you change
Click to expand...
Click to collapse
Hey guys, glad you liked that. And indeed using clockrecoverymod as update.zip is a great tool, no root or whatsoever.
Cheers

After unrooting my sgs, uninstalled all as described, found strange app under settings > manage apps called "com.noshufou.android.su", default app icon, just 8 Kb...
googlin' found a site
(wwwdotmarket4androiddotcomslash-stock-android-2-1-apps-list) that says:
Superuser.apk com.noshufou.android.su yes 16549 Remembers ‘su’ settings
(yes is "safe to remove")...
Anyone knows if this is right?
May I remove it from apps?
Thx

Well I must say this is so strange. But you i'd bet it can be safely uninstalled. If I were you i'd make sure to do factory resetting once more and clear cache again.hope that helps.
Sent from my Galaxy S using tapatalk.

This method works on JP3 froyo firmware ???

nl2006 said:
This method works on JP3 froyo firmware ???
Click to expand...
Click to collapse
Well, technically speaking this method should wwork on any firmware as it is shell based. I tried it on JF3, JM2, and JP2. Plus you have nothing to lose it is 100% safe so you can try it, if it works , fine, if not no harm done.

This method have ruined my phone.
After step rm -r /system/app/Superuser.apk my phone hang and displayed the message "Can't write to readonly memory" and now it refuses to boot again. Have tried removing the battery. I have also tried to hardreset but i don't even get to the screen to select a hardreset. The phone starts but don't get passed the initial samsung splash screen. If anyone have an ide how to fix this please help me.
WARNING! Be really carefull before using this method

Well, sorry it didn't work out for you. But to be honest this should be the safest method as the other option is to flash your phone already to another stock firmware. So as now this method apparently failed and you got a wierd situation where some of the system files were ruined, you can just try to flash the stock rom files using odin.
The stock firmwares and the tools you need (odin) together with a tutorial on how to do it you find in the following link
http://samsung-firmware.webs.com/samsungi9000.htm
good luck

it worked fine for my sgs did it just few minutes ago, but added reboot in the end

not working
Iv entered these codes, and after I hit enter each time it says file.not found. Am I doin something wrong

Hi, my SGS is using XXJPY with voodoo kernel.
Can i use this method on my SGS?
And should i firstly remove the kernel or the commands can be applied directly?

[Q] phone wont load, stuck in bootloop

my phone is stuck in bootloop. im able to get into CWM recovery, but cant restore nandroid or make a nandroid.
keeps looping in google screen
someone please help.

acatabian said:
my phone is stuck in bootloop. im able to get into CWM recovery, but cant restore nandroid or make a nandroid.
keeps looping in google screen
someone please help.
Click to expand...
Click to collapse
Have you tried a wipe from cwm?
Sent from my Galaxy Nexus using xda premium

i wiped data/cache/dalvik and still nothing.
:'(

anyone please, i dont know whats happening

Now that you've wiped it, you won't be able to make a nandroid anyway, you'd be backing up... nothing. When you say you can't restore a nandroid, what exactly is happening when you try? Do you try to restore an existing nandroid and an error stops the process? Does CWM not find any nandroids that should be there? Have you ever restored to a nadroid before that you know there *should* be one that works?
Based on what you've written here I'd suggest just restoring to factory installation and picking up the pieces from there. Before you do, you can try to backup what's on your phone using the command "adb pull /sdcard". If you have a nandroid that might be good but for some reason unusable by your phone right now, it will be copied and you can try to restore it after reverting to factory settings. Otherwise, it should pull off any personal stuff like your photos etc so it's not a total loss.
If you're on a GSM Nexus, follow instructions here.
If you're on a CDMA Nexus, follow instructions here.
It is really the exact same process for either, but you want to make sure you've got the right set of files. This will basically leave you where you were when you first unlocked the bootloader.

JoeSyr said:
Now that you've wiped it, you won't be able to make a nandroid anyway, you'd be backing up... nothing. When you say you can't restore a nandroid, what exactly is happening when you try? Do you try to restore an existing nandroid and an error stops the process? Does CWM not find any nandroids that should be there? Have you ever restored to a nadroid before that you know there *should* be one that works?
Based on what you've written here I'd suggest just restoring to factory installation and picking up the pieces from there. Before you do, you can try to backup what's on your phone using the command "adb pull /sdcard". If you have a nandroid that might be good but for some reason unusable by your phone right now, it will be copied and you can try to restore it after reverting to factory settings. Otherwise, it should pull off any personal stuff like your photos etc so it's not a total loss.
If you're on a GSM Nexus, follow instructions here.
If you're on a CDMA Nexus, follow instructions here.
It is really the exact same process for either, but you want to make sure you've got the right set of files. This will basically leave you where you were when you first unlocked the bootloader.
Click to expand...
Click to collapse
yeah, i ended up unrooting and flashing factory image back. but i did however root and unlock bootloader again.
now, whenever i finish flashing my new rom. it gets stuck looping on the boot animation, not the google logo. is there any reason behind this? could it relate back to what happened before?

acatabian said:
yeah, i ended up unrooting and flashing factory image back. but i did however root and unlock bootloader again.
now, whenever i finish flashing my new rom. it gets stuck looping on the boot animation, not the google logo. is there any reason behind this? could it relate back to what happened before?
Click to expand...
Click to collapse
When you say "it gets stuck", how long are we talking here? Sometimes, depending on what you just wiped/what you're flashing, the phone will just take a longer time to boot. If you assume something's wrong and pull the battery you might just mess it up when really you just needed to be patient and let it finish.
These are probably questions best addressed in threads for specific ROMs, though, where people might have had similar experiences, or the ROM dev might be able to use your feedback. It's especially hard to formulate an opinion that might be useful when you provide barely any specific information to what you're working with.

[Q] G2 temp root automatically kickout while backup

I am in the process downgrading my Tmobile G2.
I got the # , ok
I got the version changed, ok
I got the temp root (maybe).
But once I got the temp root and trying to backup.
The apps says I don't have root access.
It means after I pushed busybox ,etc ,ect. I click the backup apps, the backup apps say good to go. But even I reload the apps the 2nd time. It will show I don't have root access.
But I still have the # sign.
I checked the forum as someone else had the same problem, but I did not find the answer.
Does anyone have some suggestion?
Thanks

be sure to disable the fastboot option. turn your phone off, pull the battery and leave it like this for a minute... then start again

hoffmas said:
be sure to disable the fastboot option. turn your phone off, pull the battery and leave it like this for a minute... then start again
Click to expand...
Click to collapse
I got the same trouble with my Desire Z. You can see my question near the the week ago. And advice was the same, but it didn't help. I think temporary root was honest but may be backup application managed to destroy some reserved memory for root, i don't know. I couldn't to backup system either MyBackup Pro or Titanium.
So I can't rooting my phone.
I will very glad if anybody help me and you.

sure you can root your phone. if the backup doesn´t work just skip it.
"If you have nothing to back up or don't care to back anything up, proceed to the next section." (...from the guide)

I agree
hoffmas said:
sure you can root your phone. if the backup doesn´t work just skip it.
"If you have nothing to back up or don't care to back anything up, proceed to the next section." (...from the guide)
Click to expand...
Click to collapse
After rooting when I tried to backup the stock rom even I got some errors.
"Can't mount..some something"
Googled for it a lot and most of them indirectly said the phone might be bricked. Since I had nothing else to do I continued with the next step i.e. installing custom rom (cynogemod in my case) and everything turned out fine.
I am not recommending that you skip the backup process, if you can find anything then surely take a backup else skip it and continue.

hoffmas said:
if the backup doesn´t work just skip it.
Click to expand...
Click to collapse
I afraid that skipping backup procedure before rooting is not a better advice.
I've bought my device over a year ago and now it has a lot of useful app and files. I usually use MyBackupPro to store non-system data without rooting.
However, it seems to me that's not enough, or am I wrong?
I think that after the rooting and replacement of the firmware I get a new, empty device without my usual things.
Is it enough or not after rooting to restore only the non-system data to continue to use the device as before plus root ?
Thanks.

yes =) just backup your apps and restore afterwards... you wont loose any sdcard content while rooting (except for goldcard). sure you can´t backup system apps, but this doesn´t make sense anyway because they wont work with your new rom
backup while rooting could be important for warranty issues... but actually isn´t really cause you can use a wwe ruu.

[Q] Is there a way to save data before unlocking bootloader?

First, I'm sorry if there's a similar thread, I did search for it.
I'm waiting for the oficial OTA JB update for quite some time now and the only thing that stopped me from unlocking my bootloader and flashing a custom rom till now was the fact that it's going to wipe my data. I'm loosing my patience and am ready to go on with it, but still, I have to try:
Is there a way to unlock without wiping/backup and restore the whole data (incl. apps and their settings) after unlocking the bootloader?
Thanks in advance!

snigna said:
First, I'm sorry if there's a similar thread, I did search for it.
I'm waiting for the oficial OTA JB update for quite some time now and the only thing that stopped me from unlocking my bootloader and flashing a custom rom till now was the fact that it's going to wipe my data. I'm loosing my patience and am ready to go on with it, but still, I have to try:
Is there a way to unlock without wiping/backup and restore the whole data (incl. apps and their settings) after unlocking the bootloader?
Thanks in advance!
Click to expand...
Click to collapse
You've pretty much answered your question.
Backup and restore?

I was almost sure this was the only option, but how?

adb backup will do most of it, but you'll have to get the options right.

So I followed this guide to backup using adb: h**p://www.thesuperusersguide.com/adb-backup--restore.html, but no backup file appears. It takes like 2-3 seconds before it says that the backup is complete (impossible, I think). Drivers are installed, everything seems OK. Any ideas?
EDIT: Found the solution in another thread. The command that worked for me was
adb backup -apk -shared -all -f /backup/backup.ab
Click to expand...
Click to collapse

You might want -nosystem, but I'm not sure. Double check everything, and take multiple backups with different optuobs. Hopefully one will work close enough.

snigna said:
So I followed this guide to backup using adb: h**p://www.thesuperusersguide.com/adb-backup--restore.html, but no backup file appears. It takes like 2-3 seconds before it says that the backup is complete (impossible, I think). Drivers are installed, everything seems OK. Any ideas?
EDIT: Found the solution in another thread. The command that worked for me was
Click to expand...
Click to collapse
BenPope said:
You might want -nosystem, but I'm not sure. Double check everything, and take multiple backups with different optuobs. Hopefully one will work close enough.
Click to expand...
Click to collapse
IIRC, you start with snigna's command first. When it gets stuck along the process, you cancel it (or it stops itself, don't remember now), you use BenPope's switch instead and it resumes where it left off. Please double check.

Actually I didin't even have to use the backup, after flashing JB it downloaded all the apps I had, which was the main reason I wanted to do it.

On VS98510B, just want to upgrade to latest android, please help.

I have a VS985 LG G3. I was running marshmallow yesterday, but after trying to root and unlock mobile tethering and hotspot (because I am on unlimited data) I managed to brick my phone while typing in adb commands because my phone decided to randomly shut off. So after plugging it into the USB and figuring out a way to put it into download mode, I flashed it to VS98510B. After that, I rooted with Stump Root and installed SuperSU, following some guides. It works fine once again but I'm not where I want to be.
After multiple times trying to open adb shell and get it to just recognize my device, I'm done. I know there are people out there who know this stuff by heart, so please, at this point, just tell me what to do step by step so I can do it and move on with my life. I have spent hours upon hours on this and it never seems to just work. Please.
All I want is to be able to install the latest TWRP or whatever is recommended., and then install either the SkyDragon Rom or the stock marshmallow VS98546A rom, but with the verizon apps disabled since in one guide it warns that those report for modified device, which I am not sure what that means but it doesn't sound good.
I'm on VS98510B. Rooted and SuperSU installed.
I want to be able to use mobile hotspot and tethering.
There's just information overload to the extreme, I'm overwhelmed.
Thanks again if any help is possible.

If you're already rooted with TWRP installed, the hard part should really be over. You shouldn't need to be plugging into a computer and running adb commands at this point. You also said you need step by step instructions, and to really spell it all out would be a lot, but considering how far you already got I don't think you really need every little detail, so I'll give you the general idea then if you have questions I can try to fill those gaps.
Basically you'll need to find and download the new ROM you want. The easiest thing to do is download it directly from your phone so you don't have to mess around with transferring it from your computer to your phone. Many custom ROMs will also require Gapps, but if you're flashing a stock ROM (or a custom ROM based on stock) you don't need to do this because it's included in the ROM.
After you've downloaded the ROM (should just be a zip file), you need to reboot to recovery (TWRP). If you don't know how to do this, there's an app called Quick Reboot that can do it for you (01400) personally haven't used it but I assume it works).
Once you're in recovery, you normally want to make a backup first in case anything goes wrong. This is done by selecting the backup button. After you have a backup, you want to "wipe" data before installing. Select the wipe button, then I click advanced and select everything except internal data and external data. This will wipe all apps, settings, etc. from your phone so make sure you're ok with that before you do it,
After wiping, you're ready to install. Back at the first main screen of TWRP, select Install, then browse to where you downloaded the ROM and select it, then select the Install button and swipe to confirm. Assuming all goes well, when it's finished it'll give you the option to reboot. Do this and it should start booting up to your new ROM.
Also, you mentioned SkyDragon, but I just wanted to point out that this isn't the latest version of Android, I believe that's still Lollipop (not Marshmallow). You also mentioned not wanting your rooted status to be reported to Verizon, but if you're currently on stock, rooted, and don't have any apps disabled, then you already are running this risk.
Let me know if you have any questions. I think this will be easier than me trying to walk you through every detail and confirmation screen.

I don't have TWRP installed. What is the best course of action to take to install it?
As far as disabling verizon apps, is it as simple as just going into the application manager and disabling them or is there a tool I need to download?
Thanks for all the help so far!

I see, it's been a couple years since I installed TWRP and I was thinking it was part of the rooting process. I believe this is the post I followed to install TWRP: http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
Like I said, this was a few years ago and it's kind of a one-time thing. I don't know if there's something better available now or what, and I don't remember the details. I don't remember running into any problems, so if you happened to have any I'm not sure how good I could help.
As for disabling things, the things that need to be disabled are system apps and can't just be disabled from the stock application manager (Verizon doesn't want to make it easy for you to disable their software ). There are different ways this can be done, but I personally use Titanium Backup to disable (or "freeze" as they call it) apps. It will let you freeze anything, which also means it gives you the ability to break things, so don't just go in freezing random things. I don't remember if freezing requires the paid version of the app or not, but you can get it from the play store and find out.
Sent from my VS985 4G using Tapatalk

As far as Titanium Backup goes, is it along the same lines as TWRP? Like do they do the same things? Do you recommend I do one over the other?
Also as far as verizon apps reporting root, what do they do and what does that matter?
Also, I'm currently dealing with the LG DemiGod Crash Handler problem that seems to have started up on my phone the other day. I'd never rooted or messed with my phone in any way and that started happening, I thought perhaps flashing a new ROM might fix it, but I guess not. If you have any sort of tips on how to fix that, other than replace the battery (which I have not yet done, but supposedly that can solve the problem) I'd be grateful.

Titanium Backup and TWRP are two different things. Titanium Backup is a "normal" app that you can get from the Play store, while TWRP is a custom recovery and isn't ran from within your ROM. TWRP lets you do full image backups of your phone (like your entire phone in a single backup) and can also be used to install ("flash") ROMs. Titanium Backup lets you backup, freeze, and uninstall specific apps.
I use them both because they both serve a specific purpose. You have to use TWRP to install ROMs, then as far as backups, I use TWRP to make a backup of everything in case I flash a ROM that I end up not liking (I can use the backup to easily go back to my previous ROM and still have apps and everything all setup just like they were). If I do like the new ROM I flashed, I'll use Titanium Backup to restore a lot of my apps/data to the new ROM (ex. text messages, my alarm clock app, etc.)
As far as Verizon knowing about your root status, honestly I'm not sure what all that would mean. I'm sure they wouldn't like it, rooting voids your warranty so you probably couldn't get things replaced under warranty, if you have insurance through Verizon they would maybe use your root status as a reason to deny a claim, etc. I don't think you'd have to worry about them calling you up or cancelling your service or anything like that, but getting them to assist you with problems might be more frustrating than usual
Regarding the demigod crash thing, I know what you're talking about but I don't really know much about it. A while ago I would get those every once in a while and it was frustrating. I think at the time I kind off wanted to try a new ROM anyways and I think I did but I still got it occasionally. Now that you mentioned it though I haven't had one in quite a while. I'm not sure if those ROMs both happened to cause it, if it was a Lollipop thing (doesn't seem like I've had it since Marshmallow), or if it's all just a coincidence or I've just been lucky. I haven't gotten a new battery though, so that's definitely not it (for me anyways).
Sent from my VS985 4G using Tapatalk