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?

continuously rebooting[HELP!]

My friend gave me his phone to root.I used kingo root. i rooted as usual and said root successful.
but after the reboot, the phone comes to the homepage and then reboots.I pulled the battery and tried again and even then its rebooting . My friend has some files on the internal memory which he needs and has no backup of.
i have had previous experience rooting and flashing.
Someone please help me.

niyogro said:
My friend gave me his phone to root.I used kingo root. i rooted as usual and said root successful.
but after the reboot, the phone comes to the homepage and then reboots.I pulled the battery and tried again and even then its rebooting . My friend has some files on the internal memory which he needs and has no backup of.
i have had previous experience rooting and flashing.
Someone please help me.
Click to expand...
Click to collapse
hmm i think you miss something, you miss to enable remount reboot fixer. if you root your phone in locked bootloader condition you need to install remount reboot fixer first. you can search in this thread http://forum.xda-developers.com/showpost.php?p=47378231&postcount=1
and for this problem you need to reflash your stock rom and try to re-root your phone and add this script after successfully root your phone ok :good:
have try

[Q] Help with downgrade and/or re-unlock, possible flash new OS

Hi, total noob to Android hacking and rooting here...
I'm in the US and have the HTC Desire 816 (710c) on Virgin Mobile. Really wishing I'd done better research about the Desire 816 and VM before buying this phone. It's a great phone except for the small HD. I didn't realize just how many headaches that small HD--and Virgin's tight-fisted grip regarding their unlock policy--would cause me!
Forgive the length of this, but I'm hoping more detail as to what I've done/tried will help find the right solution...
I was doing fine on KitKat and for some reason decided I wanted to upgrade to Lollipop--mistake number 1! I first installed the update over KitKat but had some issues. Nothing major, but I figured something was definitely wonky when I noticed the basic stock web browser was gone--not that I really use it, just wanted to test something with it. (I was having an issue in Habit Browser, didn't realize 'til later that it was because I had my download folder setting on external SD card. While that worked in KK, it didn't in LP.) So, I did a backup...or THOUGHT I did. HTC Backup app was supposed to have been backing up my phone every day to Drive...turns out, it wasn't, despite notifications that it was working. So, anyway... I went ahead and factory reset the phone and reinstalled Lollipop. UGH! An even bigger mistake. Over 6 GB of the HD gone, just from stock LP!
Then I thought maybe if I unlocked the phone, I could delete most of the junk, even still using the stock OS. I followed the directions on HTCDev and although the proper screen appeared on the phone and asked me if I wanted to unlock, and I replied yes, it didn't work at first. The phone rebooted and everything was the same. Reboot checker confirmed failure.
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
I also tried the flashing via SD card method. It also failed. I thought, what the heck, I'll try steps 3 and 4 of the SD card method, flashing the stock recovery and lock the bootloader, even though I thought my device was locked. Well, I guess I didn't notice when I went into fastboot that the device indeed HAD at some point unlocked, after all.
After those steps, I now had the following show up:
*** Software Status: Modified ***
*** RELOCKED ***
SECURITY ALERT!
I tried flashing the ROM.zip from SD card method again. It failed spectacularly, saying something about about a large file (some of the text was beyond the edges of the screen, so I couldn't read all of it. There was also an instruction to press power to reboot. The phone went back into fast boot screen with red highlighted "!! Image Update FAIL !!" Mind you, this was with the SD card now removed. I did manage to get the phone to boot normally again, back to stock Lollipop.
Now I thought I would try flashing the WWE KK download from HTCDev. Well, I didn't get the large image fail message, but it did fail saying that it was not the right image.
I tried unlocking the phone again, via the instructions at HTCDev. Didn't work. Thought I would try the ROM.zip file from the thread here at XDA one more time. Same fail message as before, same behavior of phone getting stuck on flashboot screen with red error message on initial attempt to reboot the device. I do notice now that although phone status is still modified and relocked, the security alert message is gone.
Can anyone help? I just want KitKat back so I can reload all my previous apps! (or possibly a good KK equivalent non-stock ROM, once I get the phone unlocked again? I have no idea which one though, being a noob :/ )
Thanks!

witchywoman said:
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
Click to expand...
Click to collapse
That ruu file should work it's the vm usa last kitkat version. You need to follow the directions unroot and relock phone. But depending on what you did to the phone that was non standard you might also need to wipe or format internal data before running the ruu.
I think you can:
1) unroot then boot into recovery(twrp)
2) wipe phone/format data.
3) Boot directly from twrp to bootloader so you can get to fastboot usb.
4) Flash stock recovery from your PC.
5) Relock bootloader then run the ruu.exe.
All the other stuff you did afterwards should not be necessary.

pcjunky: The phone is currently relocked. I'm not 100% sure about unrooted, but I think it is. Like I said, when it was unlocked before I didn't even realize it, and I didn't really do anything unusual with it. The phone still had stock Lollipop on it and I just changed some stock settings and preferences.
Also, as I said, I am a total noob. I don't know what you mean about twrp and booting into that to wipe the drive and then from that. I'm sure there is info about that on this site somewhere, but it might be quicker if you (or someone) could explain it briefly, or point me in the right direction.
Updating to answer my own question in this reply. You're telling me to use a custom recovery but I never installed one. So.... currently searching to see how to do that.

I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free. If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.

pcjunky said:
I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free.
Click to expand...
Click to collapse
Well, it's interesting to note that my phone used ~ 4.8 GB when it was new with KK installed. After the Lollipop upgrade, it was using well over 6 GB with just the stock OS, HTC apps and Virgin apps on it. Obviously, that was unacceptable, and it's what got me started on this whole quest. :silly: However, after flashing a custom recover image, rather than the stock recovery I used previously, the stock installation is using 4.97 GB, so I think I should be good to go with that.
If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Click to expand...
Click to collapse
I always have used the SD card as much as was supported. Switching phones is not an option for me as I have a rather limited income and the Desire was an investment. Thus another reason I embarked on trying to make these changes.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.
Click to expand...
Click to collapse
Well, as I said above, the stock/OME installation now, before uninstalling whatever junk it will let me, is using only 4.97 GB, so I should be fine with that.
Thanks for your efforts to help me out with this. :good:

I'm glad you got it to a workable point. It's possible to go back to Kitkat, but I personally wouldn't do it because it gives you better battery life.
From time to time you should check apps under settings and swipe left to see the apps on sd card. Sometimes new app updates will support being moved to sd card or an updated version of an app will need to be moved over to the sd card.

[HELP REQUEST] WILL PAY TO WHOEVER HELPS ME GET THROUGH THIS SOFTBRICK

.

rodagola said:
Hello everyone on xda, please bare with me. Here's my story
I own a Redmi Note 8 pro, chinese rom model. It was running miui 11.0.3 over android 9 If I recall correctly.
Ok so... I was tired of some of the china apps pushing their notifications over and over and auto installing stuff, so I looked up how to apply adb commands to remove such bloatware, which was a fairly simple process. I copied and pasted a list of safe stuff to delete I found around some forums.
then... there were some other packages I checked out using an app called "app inspector", which directly tells you which app is under which package (totally useful for this purpose).
I tried to be careful not go overboard since I don't have any root access, or custom recovery, and wasn't really planning to have these, just wanted to keep this as my simple daily driver cellphone, but also perform this little maneuver to get rid of some bloatware.
little did I know, I was about to somehow softbrick it. More info: I did not use a screen lock method other than the "swipe up".
Ok, so I uninstalled some packages I cannot remember exactly how they went, but they had the terms "xman" and "yman" on them I think, I wasn't so sure about them because I looked them up on the web yet they didn't appear anywhere. I think they went something among the lines of "com.android.miui.xman". I also uninstalled 2 or 3 more, but after googling, they seemed unsuspecting.
Anyways, I'm aware there's a command to reinstall the packages because they're still on the phone's ROM image. That is in case I had to restore anything back to normal. Turns out I later rebooted the phone and when it launches the lock screen, I keep swiping up but it won't take me over to the actual MIUI launcher. The screen is frozen on the lock screen.
I'm not freaking out at this time because I still tried to connect the device to the pc, and it still shows as connected, I then go to the adb console and type "adb devices", it is still recognized, however, it says next to it that it is unauthorized... damn it. So now I might not be able to run the commands that allow me to reinstall the exact packages that are rendering the phone softbricked (I guess), plus I'm not really sure which package caused this.
After about a minute or two on the lock screen, the phone takes me to the "redmi-recovery 3.0",
which displays 3 options:
Reboot to system: which basically forms a loop
Wipe date: godforbid... really don't want to do it since I likely had many files not backedup
Contact miassistant: not sure what to do with this, says "pcsuite.mi.com" at the bottom
on the miassistant option you can apparently sideload stuff, idk how to go about this, maybe it allows me to install a slightly upgraded ROM, which in turn will work the same as if it was an OTA update (so it will keep my data as it was instead of wipe)? Because the point is not to erase my user data!!
I'm not sure how to feel or what to do without losing my pictures, notes and documents
I have hopes this situation can be turned around back to normal, and like the title implies... I'm WILLING to PAY you through paypal or something to WHOEVER offers to guide me through in the best way possible. Please if you have the knowledge/experience don't hesitate I'll also be grateful timelessly.
I'm not an expert at these scenarios so I might as well ask on xda where most are really skilled! Thanks in advance to those amazing souls
Click to expand...
Click to collapse
tldr;
If you can boot into fastboot mode you can just flash a official MIUI fastboot ROM:
Xiaomi Firmware Updater (where you can download official MIUI ROMS): https://xiaomifirmwareupdater.com/
This is the current hard unbrick method: https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
It should also work in your case and there's even a video guide.
This is another video guide for fixing a hard brick:
Both methods above will format your phone though (afaik all data will be lost).
Compass.

.

rodagola said:
are these the kind of roms that you unzip and have the BL, AP, CP, CSC files? I could try that, but I've heard installing home_csc will not override/wipe my personal data. If this is what you meant, can you confirm? Or do you reckon these linked video tutorials would not wipe the data?
Click to expand...
Click to collapse
Nope, it doesn't.
If you can boot into Fastboot, flash the ROM using Mi Flash, otherwise, use this tutorial:

.

Compass Linux and juliusjr have told you the method, so I will just add supplemential infos.
In your case, I think simple upgrade will do the trick, dirty flash is applicable both via fastboot flash (mi flash) and recovery flash (the mi assistant method). If you want to stop the ads, I will recommend you to unlock your bootloader, move to global, root, and use an adblocker (a bare minimum config, in trade of some bangking apps being blocked).
I don't know the corresponding version for miui china rom, but in global rom, prior 12.0.0.7 (the one with the early 2021 security update), you can dirty flash back and forth while keeping your data.

.

rodagola said:
Hi, thanks for your info, I would like to try the mi flash tool as I've been told before the stock recovery thing has less chances of working. However, I had dev options turned on before but didn't manage to turn on the "OEM unlock" option, will flashing original ROMs work this way? or did I need that option toogled on? That's my last doubt, and thanks a lot. Btw, the China ROM this Redmi N8P had never ever showed me any ads, but thanks a lot as well for such input
Click to expand...
Click to collapse
You still have a locked bootloader? (How do I know? You will see "Unloked" on the bottom of the screen everytime your device reboots and showing mi logo if your device is unlocked)
Hmm, mechanically it work like normal ota update. Full recovery update will ony erase nessesary partitions (system, boot, and some other things) while keeping your data intact. So doing this to your phone technically safe. You can do this with MiFlashPro, do a recovery update using a recovery rom (the 2 gigs one) greater than your current MIUI version. But please bear in mind that I have never done this before to a locked phone. A same distribution version IS A MUST (i.e. global with global).
Oh and it will need you to log in to your xiaomi account. My guess is you need the flash permission open for your account (if you have unlocked your phone you shouldn't have a problem). I have never flashed with an account that never have been used to unlock a bootloader, so I might be wrong.
If your phone is bootloader unlocked, Mi Flash is the least demanding and it can retain your data with "save user data" in the bottom right corner option on, regardless your miui version (but I think there will be some problem with installed apps if you downgrade from A10 to A9).
Hope this help.

[SOLVED] Stuck on Splash screen after magisk, Need data off device

So firstly i have been doing this myself when necessary for many years now thanks XDA Devs!
The device im using is always just a pokemon go spoof device, maybe the odd game for kids but strictly trashable in the passed. Part of the saftest method to set up the device was that i couldnt backup via TWRP. I didnt care anything i needed was saved on the cloud via game accounts...
Unfortunalty a few months ago i accidently updated from 10 to 11 and it killed my setup.. i was in the mood to fix it off i went. the same methods appeared to be identical for 10 to 11 just newer versions.....
I destroyed my everyday phones camera so i was using the pixel to save important info , only some of which i backed up correctly.. these include keys to wallets. my backup keys....
I stupidy went headfirst into doing the same thing i had done numerous times for myself and others. Its a pretty noob mistake i know.
Im pretty sure i can flash my way back without loosing data, but i need to be 100%.
I believe sideloading the OTA is safe for what i want, but i also see the backup your data warning hitting me on the forehead. Not trusting myself here at the minute.
was android 10 rooted and smali patcher, updated to Android 11... untoached, unlocked bootloader, dev enabled.
Obviosly Pixle 2 XL
Build rp1a.201005.004.a1
So i simply booted TWRP.img v 3.3.0-0 then installed the zip. normal permission errors FAILED TO MOUNT '/SYSTEM (INVALID ARGUMENT)
never needed to care before and wasnt thinking BACKUP.
I renamed magisk v23.0 apk to .zip like normal... installed via TWRP like normal.... whats not normal is im stuck with the loading bar under the G on the splash screen.
It only ever had this problem with samali but it just takes a bit.
I apologise for the story and not getting straight to it but i feel like a clown for this one and felt the need to explain my noobie mistake.
All i care about it a way back to booting up the device with my data intact so i can make it safe. i can knock down and rebuild the setup i need myself, i have been doing this long enough. really just want the clarity on a sure thing way back to my data.
Cheers yall, FYI u can take the micky out of me if you like i get it hahah.

Hi! Did you try to:
Code:
fastboot boot boot.img
from bootloader?
If you will use untouched boot.img from ROM you have on phone, it could boot normally if bootloop happend after magisk patching.
If you will sideload ota image, your data should stay on their place.

somin.n said:
Hi! Did you try to:
Code:
fastboot boot boot.img
from bootloader?
If you will use untouched boot.img from ROM you have on phone, it could boot normally if bootloop happend after magisk patching.
If you will sideload ota image, your data should stay on their place.
Click to expand...
Click to collapse
I Actually had not tried a thing once i realised what i could be losing, i had to drop my understanding and pride and triple check my methods.
I extracted boot.img from stock Firmware and fastooted back into the OS. Cheers.
I had that ready to go i almost did it before opening the thread..
I appreciate your time thanks buddy, highly appreciated.