Hi,
I've got Redmi Note 8T updated yesterday (I think V11.0.5.0.PCXEUXM).
Today I used adb command to uninstall com.miui.securitycenter app and after a reboot the device doesn't boot anymore.
Bootloader is locked.
Is there a way to recover without deleting user data?
ildani said:
Hi,
I've got Redmi Note 8T updated yesterday (I think V11.0.5.0.PCXEUXM).
Today I used adb command to uninstall com.miui.securitycenter app and after a reboot the device doesn't boot anymore.
Bootloader is locked.
Is there a way to recover without deleting user data?
Click to expand...
Click to collapse
yes there are a few apps which you can't uninstall otherwise you'll face bootloop like mi security, digital wellbeing etc..but the good news is since you uninstalled using adb so you don't have to do a lot of work to recover your phone..use the following command to reinstall the app :
Code:
adb shell cmd package install-existing <name of package>
This works because applications truly aren’t being fully uninstalled from the device using adb command, they are just being uninstalled for the current user (user 0 is the default/main user of the phone) and come back when you reset your phone or use the above mentioned command.
Thank you @the_weird_aquarian for your reply, but I couldn't access adb shell anymore so I had to wipe data.
(digital wellbeing as far as I know can be disabled/uninstalled without problems).
Same here, I use redmi note 8 pro. Just go to recovery mode, wipe data... Ur phone should working now. Wipe data make factory reset. I don't see other option to keep data. Except u ever back up using mipcsuite
where to use this command ? in twrp or fastboot mode ?
loopypalm said:
is there a way to freez or delete "com.miui.securitycenter" and "com.android.updater" without bootloop ???
where to use this command ? in twrp or fastboot mode ?
is this the right way to use it :
adb shell cmd package install-existing com.android.updater
Click to expand...
Click to collapse
Unfortunately you cannot uninstall com.miui.securitycenter or else your phone will go into bootloop...It's a core miui component and xiaomi designed it that way..
regarding the com.android.updater I haven't tried deleting it so I can't confirm if your phone will enter bootloop after deleting it or not...
adb shell cmd package install-existing com.android.updater
is the command to install any package back if you want..but it'll only work if you've only removed packages via adb..I've already explained why it works that way in my previous reply...If you delete folders right away from /system/app or /system/priv-app like I do, then this command won't work.
To uninstall any package via adb, download minimal adb and fastboot, connect phone normally to pc (no twrp or fastboot required), open cmd in adb and fastboot drivers path and use following commands (Hit ENTER after each command):
Code:
adb shell
pm uninstall -k --user 0 packagename
the_weird_aquarian said:
Unfortunately you cannot uninstall com.miui.securitycenter or else your phone will go into bootloop...It's a core miui component and xiaomi designed it that way..
regarding the com.android.updater I haven't tried deleting it so I can't confirm if your phone will enter bootloop after deleting it or not...
adb shell cmd package install-existing com.android.updater
is the command to install any package back if you want..but it'll only work if you've only removed packages via adb..I've already explained why it works that way in my previous reply...If you delete folders right away from /system/app or /system/priv-app like I do, then this command won't work.
To uninstall any package via adb, download minimal adb and fastboot, connect phone normally to pc (no twrp or fastboot required), open cmd in adb and fastboot drivers path and use following commands (Hit ENTER after each command):
Code:
adb shell
pm uninstall -k --user 0 packagename
Click to expand...
Click to collapse
yes, i did the command while the phone is on and it worked
but i'm speaking about when the phone is in bootloop
what do you do in that case ? (beside restore the twrp image)
loopypalm said:
yes, i did the command while the phone is on and it worked
but i'm speaking about when the phone is in bootloop
what do you do in that case ? (beside restore the twrp image)
Click to expand...
Click to collapse
oh just connect your device to pc while it's in twrp and then use the commands.
the_weird_aquarian said:
oh just connect your device to pc while it's in twrp and then use the commands.
Click to expand...
Click to collapse
Thx ! I'll try that .
the_weird_aquarian said:
oh just connect your device to pc while it's in twrp and then use the commands.
Click to expand...
Click to collapse
dosn't work
i try : adb shell pm list packages
while the phone is ON = worked
while the phone is in TWRP = not work
Does adb respond while device is in bootloop?
OliveReeve said:
Does adb respond while device is in bootloop?
Click to expand...
Click to collapse
yes but as far as i know, only adb fastboot commands work
OliveReeve said:
Does adb respond while device is in bootloop?
Click to expand...
Click to collapse
Yes It works. Just try installing the com.miui.securitycenter package through "adb shell pm install-existing com.miui.securitycenter" while the MIUI logo appears in the bootloop.
Tried and saved my bricked device.
Thanks for the tip on "install-existing", folks. Saved my bacon.
the_weird_aquarian said:
yes there are a few apps which you can't uninstall otherwise you'll face bootloop like mi security, digital wellbeing etc..but the good news is since you uninstalled using adb so you don't have to do a lot of work to recover your phone..use the following command to reinstall the app :
Code:
adb shell cmd package install-existing <name of package>
This works because applications truly aren’t being fully uninstalled from the device using adb command, they are just being uninstalled for the current user (user 0 is the default/main user of the phone) and come back when you reset your phone or use the above mentioned command.
Click to expand...
Click to collapse
thanks! You just safed my phone xD
same problem here. had to wipe data. never going to buy this **** again. **** xiaomi. **** them
Saved my data!
Reminds me of when I use to play with Regedit... dependencies, dependencies, dependencies
can i disable (not delete) security center via ADB or causes this also bootloop? What About Gallery & Theme App?
droi1 said:
can i disable (not delete) security center via ADB or causes this also bootloop? What About Gallery & Theme App?
Click to expand...
Click to collapse
the adb command :
pm uninstall -k --user 0
just freez the app for user 0 , it does not remove it (check with a file explorer after a reboot)
and you can't touch security app or you will face bootloop
that app alone is what made me look for a custom rom ...
about gallery and theme you can, but i suggest you do a full backup just in case ...
Related
rootzwiki.com/_/articles/twrp-20-touchscreen-recovery-officially-released-r236
Thanks for all the hard work guys.
Sent from my Kindle Fire using Tapatalk
really want to flash this but I cant get adb to recognize the device. dont know what the issue is can anyone help
wtphoto said:
really want to flash this but I cant get adb to recognize the device. dont know what the issue is can anyone help
Click to expand...
Click to collapse
Do you have Droid Explorer installed? If so, either find a way to disable it starting, or uninstall it.
sl0ttedpig said:
Do you have Droid Explorer installed? If so, either find a way to disable it starting, or uninstall it.
Click to expand...
Click to collapse
I have root explorer will that cause it as well?
wtphoto said:
I have root explorer will that cause it as well?
Click to expand...
Click to collapse
You mean on your device? No, that would make any difference. I'm talking about software installed on your PC.
no I dont, running mint 12 and can connect to my evo no problem but doesnt see the fire for some reason
wtphoto said:
no I dont, running mint 12 and can connect to my evo no problem but doesnt see the fire for some reason
Click to expand...
Click to collapse
Make sure you don't have any command windows open, then open Task Manager, and see if adb.exe is running. If it is, then you have a program that is using it's own version which is potentially overriding yours. Stop it or uninstall it.
At this point, I'm also presuming that you are rooted and so have 0x1949 in your adb_usb.ini file?
do i need to put the "twrp-blaze-2.0.0RC0.img" in a certain folder before flashing?
Did you add the edited USB vendor id?
Have someone tried to boot normally from this recovery
Sent from my Nexus One using XDA App
sl0ttedpig said:
Make sure you don't have any command windows open, then open Task Manager, and see if adb.exe is running. If it is, then you have a program that is using it's own version which is potentially overriding yours. Stop it or uninstall it.
At this point, I'm also presuming that you are rooted and so have 0x1949 in your adb_usb.ini file?
Click to expand...
Click to collapse
I am rooted but when I open the usb_.ini file there is nothing listed there, this is all I have in it
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
wtphoto said:
I am rooted but when I open the usb_.ini file there is nothing listed there, this is all I have in it
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Click to expand...
Click to collapse
Add 0x1949 to it. Not sure how you could be rooted without having done this step at some point!
---------- Post added at 11:44 PM ---------- Previous post was at 11:43 PM ----------
devastater said:
do i need to put the "twrp-blaze-2.0.0RC0.img" in a certain folder before flashing?
Click to expand...
Click to collapse
Put it in the same directory as fastboot.exe, which generally goes in the same directory as adb.exe.
sl0ttedpig said:
Add 0x1949 to it. Not sure how you could be rooted without having done this step at some point!
Click to expand...
Click to collapse
yeah i did that and it worked, when I rooted I was running mint 11 and then my HDD fried and I had to reinstall and when I did I switched to mint 12 but never updated the usb.ini. I feel about retarted now
thanks for the help
I decided to flash this a different way then said in their post - the way JackpotClavin has us, it sounds a bit firmer. Also, I have FIREFIREFIRE installed, in most cases installing this recovery is pointless unless your have FIREFIREFIRE, so assuming you have FIREFIREFIRE installed you can skip some steps.
This method does NOT require fastboot, so you don't have to go searching around for a bin! (then again, if you have FIREFIREFIRE installed I assume you already have a bin, >_<)
Requirements for my instructions:
FIREFIREFIRE installed
ADB up and running!
adb push *DIRECTORY OF YOUR IMG*\twrp-blaze-2.0.0RC0.img /sdcard
You may need to put the path in parentheses if you have a space anywhere in the path!
adb shell
cd /sdcard
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
reboot
Now it is installed, and it rebooted so press the power button to get into recovery! It'll install it then reboot again, just go into recovery again.
There, you successfully installed it.
Help!!!!
I flashed it according to the instruction in their homepage.
But the KF doesn't wake up,just hangs on the yellow fire picture.
I think it's in fastboot mode(because i set bootmode to 4002)
But my PC can't recognize it,so I can't use fastboot to change the bootmode.
Anyone can help me?
adam900710 said:
Help!!!!
I flashed it according to the instruction in their homepage.
But the KF doesn't wake up,just hangs on the yellow fire picture.
I think it's in fastboot mode(because i set bootmode to 4002)
But my PC can't recognize it,so I can't use fastboot to change the bootmode.
Anyone can help me?
Click to expand...
Click to collapse
How could you make those instructions work?
Mine doesn't go further than the below ...
adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ su
su
# idme bootmode 4002
idme bootmode 4002
<idme> write 4002 to offset 0x1000
# fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot: not found
#
Click to expand...
Click to collapse
andTab said:
How could you make those instructions work?
Mine doesn't go further than the below ...
Click to expand...
Click to collapse
You should reboot you KF and the KF will boot into fastboot.
Then you type fastboot command in you terminal.
It will be a screen showing that the recovery is installing and will reboot.
edit: fixed myself
adam900710 said:
You should reboot you KF and the KF will boot into fastboot.
Then you type fastboot command in you terminal.
It will be a screen showing that the recovery is installing and will reboot.
Click to expand...
Click to collapse
I'm rebooted once i set the bootmode and the kindle fire logo is showing, but when i type
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
all i get is a list of fastboot options
loki154 said:
I'm rebooted once i set the bootmode and the kindle fire logo is showing, but when i type
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
all i get is a list of fastboot options
Click to expand...
Click to collapse
Change "twrp-blaze-2.0.0RC0.img" to the path of the img you downloaded.
Not just "twrp-blaze-2.0.0RC0.img".
_-_
phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/
_-_
adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??
_-_
Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....
_-_
phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
MunkeyBoy14 said:
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
Click to expand...
Click to collapse
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
ahent said:
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes I did, and nothing changed.
Hogyoku said:
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
Click to expand...
Click to collapse
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
MunkeyBoy14 said:
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
Click to expand...
Click to collapse
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
When I run the "adb shell" commad I get the following:
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Not sure if this helps at all
Hogyoku said:
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
Click to expand...
Click to collapse
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
MunkeyBoy14 said:
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
Click to expand...
Click to collapse
No problem
Block this site in your router:
nvcare.nvidia.com
not suggest block the ip as it also use for other things, and it will take a longer time to check the update, just wait for it to finish.
This also block the force update when system setup.
p.s. dunno if anyone post this before, tested on shield tv 2017 firmware 5.1
or freeze the system update app which should work.
you need this when you want to stay on older version after full reset, I don't know if there a method to skip the force update when setup the shield.
someone may want to stay on 5.1 as the 5.2 had some problem to change refresh rate in KODI
@DummyPLUG
Didn't it use to be ota-downloads.nvidia.com?
yojoe600 said:
or freeze the system update app which should work.
Click to expand...
Click to collapse
This worked perfectly for me after I deleted the OTA in flashfire.
I have blocked both "nvcare.nvidia.com" and "ota-downloads.nvidia.com" in my router, but would also like to get rid of the update notification that pops up on the Shield TV. What is the best way to do this? I am not rooted, have an original 2015 Shield as well as a Shield Pro, both running Nougat. I was looking at using adb and using the following commands: "adb shell" then "pm uninstall -k --user 0 com.nvidia.ota". Does anyone know if this would theoretically work? Is "com.nvidia.ota" the name of the app that handles the update process? If anyone has a better idea on how to disable the update app I would appreciate the info. I have no desire to go to Oreo after hearing some of the issues people are having.
Download the dev_root shield tv recovery os image, you can easily find it with a google search.
hook up your shield to PC via a usb to micro usb or if its the 2017 model u need a usb-a to usb-a cable.
download minimal adb & fastboot drivers ...google search them.
Turn on usb debugging in shield tv options and with shield running at its home screen Open CMD as admin and flash the older 6.3 (android 7) OS.
Type these commands one by one pressing enter after each one.
adb devices ________________________ (it should pop up a box asking for permission grant it)
adb reboot bootloader ________________(wait for it to boot into bootloader mode)
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot reboot
DO NOT unplug usb cable leave ADB in CMD still running.
When it reboots and is at the controller/remote pairing screen...Enter this it stops the auto upgrade back to 8 Oreo
adb root
adb remount
adb shell
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
yojoe600 said:
or freeze the system update app which should work.
Click to expand...
Click to collapse
Can I ask what the system update app is called? .... and could I just use something like Titanium Backup?
TIA.
BIOYAM said:
Can I ask what the system update app is called? .... and could I just use something like Titanium Backup?
TIA.
Click to expand...
Click to collapse
Pretty sure the name is called system update or something close. And yes I used titainium backup
Sent from my HTC 10
right now I am blocking "ota.nvidia.com", don't have any notification nor ask me to update the firmware after reset.
I heard the latest OTA updates don't unroot you. True story? Also, are you at risk of being bricked by an OTA if you patched your boot (presumably for Magisk)?
Hi
I accedently pressed the update button, and it started downloading the s9 firmware update.
I paused it, but I can't seem to cancel it.
I tried restarting the phone, but it won't go away.
Cant find a way to remove the annoying notification.
Help?
Boot to recovery and clear CACHE
Necromancer3 said:
Hi
I accedently pressed the update button, and it started downloading the s9 firmware update.
I paused it, but I can't seem to cancel it.
I tried restarting the phone, but it won't go away.
Cant find a way to remove the annoying notification.
Help?
Click to expand...
Click to collapse
dont forget , Developer options and activate USB debugging
use adb shell (no need root) to uninstall this file com.wssyncmldm.apk
use this comands
adb start-server
adb shell
pm uninstall -k --user 0 com.wssyncmldm.apk
PeterParker said:
dont forget , Developer options and activate USB debugging
use adb shell (no need root) to uninstall this file com.wssyncmldm
use this comands
adb start-server
adb shell
pm uninstall -k --user 0 com.wssyncmldm
Click to expand...
Click to collapse
I did exactly as you instructed and got back
Failure [not installed for user 0]
Click to expand...
Click to collapse
Is there another file to uninstall?
overclockxp said:
I did exactly as you instructed and got back
Is there another file to uninstall?
Click to expand...
Click to collapse
Sorry, file name is com.wssyncmldm.apk, try it work very well for me
PeterParker said:
dont forget , Developer options and activate USB debugging
use adb shell (no need root) to uninstall this file com.wssyncmldm.apk
use this comands
adb start-server
adb shell
pm uninstall -k --user 0 com.wssyncmldm.apk
Click to expand...
Click to collapse
PeterParker said:
Sorry, file name is com.wssyncmldm.apk, try it work very well for me
Click to expand...
Click to collapse
I dont have anything with wssyncmldm in the name. I even paid for package Disabler pro and it said nothing existed with that in the name.
What version of the S9 are you using? I have the Verizon S9 model.
Thank you for your help with this.
overclockxp said:
I dont have anything with wssyncmldm in the name. I even paid for package Disabler pro and it said nothing existed with that in the name.
What version of the S9 are you using? I have the Verizon S9 model.
Thank you for your help with this.
Click to expand...
Click to collapse
My version is SM-G960F
I used Package disable pro and disabled anything that said system update and never had an update notification. The section for system update in settings even disappeared.
PeterParker said:
My version is SM-G960F
Click to expand...
Click to collapse
You have the European version. Lucky you can cancel the update.