my phone is stuck in a bootloop when I tried disabled Fused Location. How can i turn it back on using adb? The line "adb pull /data/system/users/0/package-restrictions.xml" does not work. its not found.
Im running Oreo owith Twrp installed
NabeelUppel said:
my phone is stuck in a bootloop when I tried disabled Fused Location. How can i turn it back on using adb? The line "adb pull /data/system/users/0/package-restrictions.xml" does not work. its not found.
Im running Oreo owith Twrp installed
Click to expand...
Click to collapse
Have u rooted ur device?
If yes, try to install one of this apps, Disable Services or My Android Toolkit. Search for Fused Location in System tab, check it for enable n otherwise
Related
So I am trying to manually sideload the OTA update for 5.1 on my phone and adb and fastboot work just fine but when I reboot to TWRP and choose adb sideload it says 'error device not found' and I'm not sure why as adb devices finds my phone normally so the drivers can't be the issue.
Thanks for the help.
joshua.justice said:
So I am trying to manually sideload the OTA update for 5.1 on my phone and adb and fastboot work just fine but when I reboot to TWRP and choose adb sideload it says 'error device not found' and I'm not sure why as adb devices finds my phone normally so the drivers can't be the issue.
Thanks for the help.
Click to expand...
Click to collapse
Because you need stock recovery to do that...
BigDig said:
Because you need stock recovery to do that...
Click to expand...
Click to collapse
Just in case I tried that too and even with stock recovery it does not load completely. The android is just on his back with a red exclamation mark. And why would twrp put sideload in there if it would not work?
joshua.justice said:
Just in case I tried that too and even with stock recovery it does not load completely. The android is just on his back with a red exclamation mark. And why would twrp put sideload in there if it would not work?
Click to expand...
Click to collapse
you need to press the power button and volume up to get the menu in stock recovery.
simms22 said:
you need to press the power button and volume up to get the menu in stock recovery.
Click to expand...
Click to collapse
I reflashed everything and now the recovery icon is an android with moving ears and spinning gears and when I hit vol up and power it just says formatting data and sits there.
It shouldn't be this hard. I've flashed plenty of ROMs before.
Edit: Stock recovery works just fine but it still cannot find my device with a completely stock phone and when adb works when the phone is on and I Just updated the drivers so I'm at a loss.
Edit #2: For some reason MTP must be turned off which apparently throws the phone for a loop (not literally) if it is on.
Hi,
I've been making tests with some launchers but now I've a problem and I don't know how to solve it.
I've my Fire rooted. I had Nova Launcher as native but I've uninstalled it by mistake and after reboot, the Fire is apparently stuck on "Fire" logo. Does somebody know a way to recover it? Maybe a hard factory reset, maybe extracting the battery...
Any solution?
Thanks.
Darkside1984 said:
Hi,
I've been making tests with some launchers but now I've a problem and I don't know how to solve it.
I've my Fire rooted. I had Nova Launcher as native but I've uninstalled it by mistake and after reboot, the Fire is apparently stuck on "Fire" logo. Does somebody know a way to recover it? Maybe a hard factory reset, maybe extracting the battery...
Any solution?
Thanks.
Click to expand...
Click to collapse
Get into Recovery (Power off, then power+volume down), install update by ADB, download the update.bin from Amazon's website, and do "adb sideload update.bin". It will replace the system folder, so you will have to re root and redo the launcher stuff.
Edit: Do this: http://forum.xda-developers.com/showthread.php?t=3238740
Sent from my KFFOWI using Tapatalk
Thanks! I cannot find the update file. Is it in Amazon site?
Yeah. Look up Amazon Firmware on Google and it will be the first result. Then just click on this device and download the file.
Sent from my KFFOWI using Tapatalk
Thanks again. Now in recovery mode it says "device unauthorized" so I can't sideload the file. I've all ADB drivers properly installed. What's the problem?
Darkside1984 said:
Thanks again. Now in recovery mode it says "device unauthorized" so I can't sideload the file. I've all ADB drivers properly installed. What's the problem?
Click to expand...
Click to collapse
Try installing the adb recovery drivers in device manager when it is in recovery mode.
Sent from my KFFOWI using Tapatalk
Vlasp said:
Yeah. Look up Amazon Firmware on Google and it will be the first result. Then just click on this device and download the file.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Or just use the link in the Index
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
Google search results are customized per user, so what is top result for you may not be for someone else.
Move from Android Development forum for help:
"I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do?*"
Darkside1984 said:
Move from Android Development forum for help:
"I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do?*"
Click to expand...
Click to collapse
Window sees the recovery mode differently than the rom, you need to manually select ADB composite interface drivers in Device manager
sd_shadow said:
Window sees the recovery mode differently than the rom, you need to manually select ADB composite interface drivers in Device manager
Click to expand...
Click to collapse
Yeah. If you do it correctly, it should come up as Sideload in ADB Devices.
Sent from my KFFOWI using Tapatalk
first of all, the driver files here did not work with the stock recovery. i downloaded the latest drivers using android sdk. even though, i installed the latest drivers (you can find it in C:\Users\[user name]\AppData\Local\Android\android-sdk\extras\amazon\kindle_fire_usb_driver as KindleDrivers.exe), windows did not show the exact driver. but i chose "samsung usb adb coposite" or something instead, which did not show up until i installed the latest driver. then, windows recognized the fire and i could reflash the official rom by "adb sideload update-kindle-37.5.2.2_user_522053820.bin".
people should give advice after they tried. not from guessing.
my friend has a stock turbo, running latest ota. no root or unlock, stock.
it is stuck in a loop. i can unlock the phone or double tap windows button and multitasker pops up though i cannot interact with anything because this keeps popping up:
"Unfortunately, the process com.android.phone has stopped" sometimes it says another process like com.motorola.process.system
can't factory reset because the photos haven't been backed up.
how can i get it out of this loop so i can run KINGROOT and get a real rom going? thanks :cyclops:
any advice?
Roflcopter_Down said:
any advice?
Click to expand...
Click to collapse
Clear cache from stock recovery. If that doesn't work I would try pulling the files using a PC and factory reset from recovery.
Sent from my XT1254 using Tapatalk
Can't you plug it in still and get the photos off?
mrkhigh said:
Can't you plug it in still and get the photos off?
Click to expand...
Click to collapse
hey, usb storage isnt enabled so when connected to computer, drive doesnt mount. cant get to settings to turn on usb storage. thats what i really need to figure out, i suppose
tried clearing cache
Roflcopter_Down said:
hey, usb storage isnt enabled so when connected to computer, drive doesnt mount. cant get to settings to turn on usb storage. thats what i really need to figure out, i suppose
tried clearing cache
Click to expand...
Click to collapse
I am not positive that a factory reset deletes your pictures.
That said I wouldn't risk it since I am not positive.
You should be able to pull your files via adb/fastboot.
Then after you have copied it all do a factory reset or simply flash a stock ROM.
Edit: from adb
You can try:
Adb pull /sdcard/dcim
mrkhigh said:
I am not positive that a factory reset deletes your pictures.
That said I wouldn't risk it since I am not positive.
You should be able to pull your files via adb/fastboot.
Then after you have copied it all do a factory reset or simply flash a stock ROM.
Edit: from adb
You can try:
Adb pull /sdcard/dcim
Click to expand...
Click to collapse
how do i enable adb/fastboot from stock recovery? its been a couple years since i had an m7. iirc there was an option after you flashed a custom bootloader or something. i dont see the option now in recovery or boot
Fast boot is boot loader mode. But apparently you can't pull from there.
Try booting the device,
Then try plugging it in and typing
Adb devices and see if your device responds
If it does you can simply use the adb pull command
This assumes you have adb installed and ready on your system.
I think it is included with android SDK and there are tutorials out there.
Sent from my DROID RAZR M using XDA Free mobile app
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Bump.
Bump.
Bump.
Xenomorphs said:
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Click to expand...
Click to collapse
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
qwertz512 said:
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
Click to expand...
Click to collapse
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Xenomorphs said:
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Click to expand...
Click to collapse
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
hakudayo said:
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
Click to expand...
Click to collapse
Thank you so much. I'm going to try.
Xenomorphs said:
Thank you so much. I'm going to try.
Click to expand...
Click to collapse
No problem if you have any questions just ask me
Now I'm stuck with this same issue.,
Got into this while trying to boot TWRP OrangeFox-R12.1_3_A12_FBEv2-Unofficial-lime.zip on xiaomi A12 ROM
I had a root installed on my Google pixel 7 and the little update dialogue popped up for me to restart now and instead of closing it out I accidentally hit restart. Now my phone rebooted. I went to check to see if root was still there and root checker says it's not installed properly. Magisk is still installed but it doesn't give me no ability to do super user options. It's grayed out.
What can I do to get root back on this phone because I have an app that's fully root dependent and won't work without it.
mrnapolean1 said:
I had a root installed on my Google pixel 7 and the little update dialogue popped up for me to restart now and instead of closing it out I accidentally hit restart. Now my phone rebooted. I went to check to see if root was still there and root checker says it's not installed properly. Magisk is still installed but it doesn't give me no ability to do super user options. It's grayed out.
What can I do to get root back on this phone because I have an app that's fully root dependent and won't work without it.
Click to expand...
Click to collapse
Just patch and flash the init_boot image again.
Lughnasadh said:
Just patch and flash the init_boot image again.
Click to expand...
Click to collapse
I attempted to flash the patched init_boot image but ADB Fastboot tool keeps saying <waiting for any device>
phone is currently in fastboot mode...
mrnapolean1 said:
I attempted to flash the patched init_boot image but ADB Fastboot tool keeps saying <waiting for any device>
phone is currently in fastboot mode...
Click to expand...
Click to collapse
What Platform Tools version are you using? Should be 33.0.3 or 34.0.1 IF you downloaded that version withing the last day or so. If you downloaded 34.0.1 before a couple of days ago, don't use it as it's broken.
Also check cables/ports. A to C using USB 2.0 seems to work best for many.
Lughnasadh said:
What Platform Tools version are you using? Should be 33.0.3 or 34.0.1 IF you downloaded that version withing the last day or so. If you downloaded 34.0.1 before a couple of days ago, don't use it as it's broken.
Also check cables/ports. A to C using USB 2.0 seems to work best for many.
Click to expand...
Click to collapse
I used this when I rooted it the first time: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
mrnapolean1 said:
I used this when I rooted it the first time: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Click to expand...
Click to collapse
Try using this. The one you used hasn't been updated for roughly 5 years or so.
Lughnasadh said:
Try using this. The one you used hasn't been updated for roughly 5 years or so.
Click to expand...
Click to collapse
Just tried that and it still says waiting for any device. Im using CMD. Do I need to use powershell?
EDIT: Just tried powershell. same thing. <waiting for any device>
mrnapolean1 said:
Just tried that and it still says waiting for any device. Im using CMD. Do I need to use powershell?
Click to expand...
Click to collapse
Do you have the latest USB Drivers installed? Try different ports/cables?
Command line is fine. If you haven't, try putting patched init_boot.img in the Platform Tools folder and open up the command prompt from the Platform Tools folder.
Lughnasadh said:
Do you have the latest USB Drivers installed? Try different ports/cables?
Command line is fine. If you haven't, try putting patched init_boot.img in the Platform Tools folder and open up the command prompt from the Platform Tools folder.
Click to expand...
Click to collapse
This fixed the waiting for any devices issue. thanks!
Got the init_boot image flashed and now I have root again. Thanks a ton!
mrnapolean1 said:
I had a root installed on my Google pixel 7 and the little update dialogue popped up for me to restart now and instead of closing it out I accidentally hit restart. Now my phone rebooted. I went to check to see if root was still there and root checker says it's not installed properly. Magisk is still installed but it doesn't give me no ability to do super user options. It's grayed out.
What can I do to get root back on this phone because I have an app that's fully root dependent and won't work without it.
Click to expand...
Click to collapse
How were you able to get the OEM unlock option available? I am trying to root my pixel 7 but the place to select to unlock OEM is grayed out.
jeffries6907 said:
How were you able to get the OEM unlock option available? I am trying to root my pixel 7 but the place to select to unlock OEM is grayed out.
Click to expand...
Click to collapse
If the phone isn't carrier locked try it with an internet connection. Phone may need to restart after connecting wifi.