Related
Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker
Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?
Hope somebody comes up with an answer - same thing happened to me.
did you use the d3 root method? thats the only one that works 100% on gingerbread.
Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.
SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni
Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.
Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?
Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.
This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!
Awesome! Thanks!
Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!
Awesome!
Thanks! This worked for me as well! (after additional reboot)
Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.
Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew
awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer
It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.
Hello,
I very recently had to remove the FRP lock on a client's Motorola G4 Plus because he had forgot his email and password (EXTREMELY common with old people getting smartphones). I have some experience with dirtycow, Samsung modem commands injection (using Realterm) and other bypass methods. Dirtycow was not working since this phone had security update from December 2016 so I had to use an online service with remote USB support. This service required me to enter Motorola's "Factory Mode" from the boot menu.
My question is: does anyone has experience with this special mode? Is there some literature regarding special commands, COM port settings or else when in this mode, or is everything kept private by the people who provide the service? Any basic information on what it does/how it works?
For what its worth, here's how the process went:
-Connected remotely with USB Redirector
-Booted into bootloader and activated "Factory Mode". Phone boots into OS but seems to operate in a special mode.
-Technician does something. I reboot into bootloader and boot again in factory mode.
-Technician somehow is able to enable ADB in 2nd "Factory Mode" boot. (this was not possible when I had access to Settings menu through "Talkback hack")
-Reboot again in normal mode and FRP seems to be removed. Setup has been bypassed, phone boots directly to Google Now Launcher.
What did he do? What does this "Factory mode" unlocks that permits him to enable ADB and completely bypass the Setup and Google Account verification? Did he erase the PERSIST partition? Did he inject app data from an already finished Setup?
Anyways, I am currently looking into it and will open another thread when I have more information.
Thank you!
If the technician used ADB it's likely you can Google whatever command he could have used. My guess is that he either wiped a file that concerns the Setup and Google Account Verification. Maybe he completely removed GApps remotely using ADB?
Sent from my Moto G (4) using Tapatalk
ironman38102 said:
If the technician used ADB it's likely you can Google whatever command he could have used. My guess is that he either wiped a file that concerns the Setup and Google Account Verification. Maybe he completely removed GApps remotely using ADB?
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
daveribss said:
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
Click to expand...
Click to collapse
Actually now that I think about it, you're right you can't remove GApps without root and you can't wipe Persist partition without root. I suppose he enabled ADB because that Factory Mode maybe has some special sort of commands, but even then what use is ADB when you don't have root?
Sent from my Moto G (4) using Tapatalk
This is the command that he uses in adb:
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
sachingodishela said:
This is the command that he uses in adb:
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Click to expand...
Click to collapse
does anyone know the command to use in Factory Mode to enable ADB?
daveribss said:
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
Click to expand...
Click to collapse
Just to shed some light, adb does allow you to remove system apps or for that fact google apps without root
A tad late to the party but I'll give you a hint on the ADB enabling thing for Moto's.
Before he got ADB he probably set the device into 'factory' mode. This mode lets you send bytes to a certain TCP port via USB that sets system props. One of them is ADB enable.
There's similar tools on Youtube for repair and FRP removal like motoservice.exe
I myself reversed this years back and even found a few bytes that weren't used in the app but able to inject to change device properties.
Anyway, read this wanted to share. Motorola still has this mode, but now some devices won't let you boot factory mode.
Booting in factory mode exposes CQATest. They are using it to run shell commands, in this case to enable adb.
Hello fellow A51 users today i want to share with you a debloat guide so you can get the max performance out of you new smartphone without Samsung clutter.
All credits goes to Khlam and his Samsung Oneui debloat list:
https://github.com/khlam/debloat-samsung-android
I tested it on my device with uninstalling the complete list and it works great.
You do lose some functionality so be careful with what you delete this does only delete the apps one your install of the OS doing a factory reset will reset all apps back to normal this will not void any warranty so i suggest making a backup and trying it on a fresh install and see if you like it.
This guide will strip Oneui to its bare bones so its not for everyone but if you like speed over functionality than give it a try.
Guide:
The following instructions assumes you are familiar with using a command-line interface.
1. On your phone, enable Android's "Developer Options"
2. In "Developer Options", turn on "USB Debugging"
3. On your computer, download Android SDK Platform-Tools for your OS.
https://developer.android.com/studio/releases/platform-tools
4. Extract Android SDK Platform-Tools and start a command-prompt/shell session in the extracted folder's directory.
(The way i do this is putting the platform tools folder in My Documents and en opening the folder then type cmd in the navigation bar and hit enter this will open a command prompt in the folder directory.)
5. Connect your Samsung Android phone to your computer with USB debugging enabled. Verify that adb sees your device and the daemon is running with the following command
adb devices
You should see the device name listed as a "device".
At this point your device should prompt you to accept USB debugging from your computer. Tap "Allow".
6. Enter your device's shell with the following command: adb shell
Once in the device's shell, copy and paste all desired commands from:
https://raw.githubusercontent.com/khlam/debloat-samsung-android/master/commands.txt
(What i do is making a notepad file and copying the whole list in notepad file removing the spaces then copy and paste the whole list in the command prompt.)
Let the script run and when the command prompt reaches the last command you only have to hit enter ones the finish the script.
Thats it you now have a fast bare bone debloated A51 you can close the command prompt and disconnect your phone from your pc.
Enjoy if this all sounds to difficult i suggest you read up on the following articles/guides
https://github.com/khlam/debloat-samsung-android
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
They explain it in more depth if you have any questions please put them bellow and im happy to help.
Zoqy :laugh:
Amazing, was looking for this.
Thanks.
very cool... thx for sharing this
I'm not able anymore to access "Sound quality and effects" in the settings.
Anyway to reinstall?
I found out what the solution was.
So when deleting
pm uninstall -k --user 0 com.samsung.aasaservice
And reinstalling
pm install-existing --user 0 com.samsung.aasaservice
How to fix sms app?
pm install-existing --user 0 com.samsung.android.messaging
it's not helping
senq87 said:
How to fix sms app?
pm install-existing --user 0 com.samsung.android.messaging
it's not helping
Click to expand...
Click to collapse
The ADB-Command for reinstalling is:
adb shell pm enable com.samsung.android.messaging
I get a popup message when trying to edit a picture from the gallery app. It asks to download a picture editor but when i click on download it says "no apps availbe to do this action".
edit: got it myself. this fixed it:
pm install-existing --user 0 com.sec.android.mimage.photoretouching
Just found another one today:
upday for Samsung - Zeropage
a51:/ $ pm uninstall -k --user 0 de.axelspringer.yana.zeropage
Success
tried, broke, fixed
ran this script on the sm-a515u verizion. Lost signal, data, and my nova google companion (no edge swipe). Factory reset works as normal again.
this deletes pretty much everything on your phone, including things like image cropping, youtube or the "find my galaxy" thing
some of these functions are much needed so would sort out whatever you need from that list before attempting to do that
I only deinstalled what I really didn't need, what was about 20 apps and services
seems that one of these packages depends on calling and texting. i'm on a spectrum mobile device and after running the entire script i can use mobile data but can't make or recieve phone calls and text messages. of course a factory reset does the trick but i wonder what app is causing this?
EDIT: i finally got around to troubleshooting it. it was most likely these services i had to re-enable again (through adb shell cmd package install-existing <package name>:
com.sec.ims
com.sec.imslogger
com.sec.imsservice
I am getting frequent reboots and will have to factory reset.
FBK2904 said:
The ADB-Command for reinstalling is:
adb shell pm enable com.samsung.android.messaging
Click to expand...
Click to collapse
This did not help, messaging app crashed. But text message retrieval works.
---------- Post added at 20:26 ---------- Previous post was at 20:23 ----------
AOD no longer works.
Frau Son said:
this deletes pretty much everything on your phone, including things like image cropping, youtube or the "find my galaxy" thing
some of these functions are much needed so would sort out whatever you need from that list before attempting to do that
I only deinstalled what I really didn't need, what was about 20 apps and services
Click to expand...
Click to collapse
would you share those 20 apps and services?
settings not opening. what is the solution to that?
albusdanbledore said:
would you share those 20 apps and services?
Click to expand...
Click to collapse
did you get it ?
hhniloy said:
settings not opening. what is the solution to that?
Click to expand...
Click to collapse
Same here, after Update to Android R (11). My Settings still crash. I reinstalled the bloated s***. then settings works again. But I will try which app it caused.
albusdanbledore said:
would you share those 20 apps and services?
Click to expand...
Click to collapse
for me exactly the same question. Please answer.
I suggest using this debloater instead. More recent, covers many more things (not just Samsung specific) and every single setting is documented and tested. The Samsung Debloater uninstalls things that are better left alone if you don't want an unstable device.
chrisimre747 said:
Same here, after Update to Android R (11). My Settings still crash. I reinstalled the bloated s***. then settings works again. But I will try which app it caused.
Click to expand...
Click to collapse
The app which cause the crash is:
com.osp.app.signin
Tested on my Galaxy A51.
Hello. It's driving me crazy: microphone access permissions for Google Meet, Microsoft Teams, Facebook Messenger keep reverting to disabled state after reboot. I tried setting them from adb (e.g. pm grant com.google.android.apps.meetings android.permission.RECORD_AUDIO) but it behaves the same. I do not have profiles enabled, I already wiped cache from recovery, I do not know what to try next. Storage and Camera permissions remain, just the Microphone is stubborn. Please help, thank you.
Update to 7.3.1.7 (a quick bug-fix release), then go through ALL of the tablet settings and toggle every one of them back and forth one time to end up on the correct setting, even if it looks like it is already on the correct setting (sometimes it isn't).
Just received 7.3.1.7 and the problem is still there after restart. Do you have the same version and for you is the microphone permission working fine for either of the sideloaded apps?
I'm having same problem. It seems to be happening only with sideloaded apps.
Actually I take that back, I just tried facebook app downloaded from Amazon appstore and it's also happening.
Restart your Fire tablet and view logs on your Fire tablet using ADB
Code:
//Enter ADB shell
adb shell
//Start logcat
logcat
and you can see the suspected app that revokes microphone permission.
I followed the instructions on this site to uninstall a program (really just disable it) without root. I use ADB on the command line to do it. However, I get an error and nothing happens. When I follow the directions, it says to type "adb devices" to connect your phone. So I do that and my phone connects. Then it says type "adb devices" again to list your devices. It lists two attached devices: My phone and "emulator". Sooooo, when I try to delete an app, I get an error message that I have multiple attached devices and it doesn't delete the app. I used the adb detach command to try to detach an advice. Doesn't work.
Any advice?
Thanks
Why don't you root and finish the job? You can uninstall after root without any problems. I've never heard that someone is able to uninstall application if the root is needed for uninstalling.
Root is the way to go but it's much easier with the Tmobile version and it's a must these days with the Gogole app being a mandatory update with the new Play Store layout.