I am using Realme X7 5g (RMX3092). I used ADB to remove all the bloatware in the phone.
I did not remove the launcher / keyboard or any important apps.
Now the Phone is stuck at the login screen.
Video Link
Is there any way to re-enable the disabled packages while in Recovery or Fast boot mode ?
I tried using both and get the error Screenshot
I have one of the old update packages in the memory of the phone but the system is not allowing to degrade to a older version. Screenshot
Any help is appreciated.
Related
I'm getting an error while installing apps on my redmi 2 prime.I am using windows 10.Apps is not installing even after the pop-up in my phone. See image for futher details.
Thanks for any help.
If It's the case happens with many then it's a common thing in Xiaomi's phones.
Here's what you should do:
Go to developer options (Settings-Additional settings-Developer options).
Swipe to the last option at the bottom.
Disable MIUI customization and restart your phone.
Additionally, you can disable verify apps over ADB.
I am using the latest Phonegap Push Plugin for my Phonegap Application. It's working fine below Nougat but in Nougat the same code does not work. I have tried to debug several times, also cross verified at server side if there is anything missing but found the device is not recognized by the GCMSender. Also everytime I uninstall and reinstall the Application the registered device token is same whereas in case of the Pre Nougat devices, it's always different after each uninstall and fresh install. The device I am having is Nexus 6P.
Finally after searching so much found the below answer:
Reboot your device since it must have got OTA update for Nougat.
System's cache partition might not have been cleared. Seems to be an issue in Nougat. Below are the steps for rebooting and found the same Push Notification code working in Nougat as well:
-Power down your device
-Press and hold Volume Down and Power simultaneously until you see the boot screen
-Use Volume Down to navigate to Recovery Mode
-Press Power to confirm
-Wait until you see the Android robot then hold down Power.
-Press and release Volume Up
-Navigate with Volume Down to the Wipe Cache Partition option
-Press Power to select
-Use Volume Down to highlight the Yes option
-Press Power to select
-Press Power to reboot
Reference Link: https://productforums.google.com/forum/#!topic/nexus/xEssjbdwpgk
I just installed android sdk. And trying to follow these steps to detect my device. Because my phone was disconnected & dead during an unfortunate/accidental/unwelcome software upgrade.
It's frozen on Samsung start up screen. I was able to use volume + power + home buttons to get into another black screen with now send the package you want to apply to the device with adb sideload <file name>. But not sure how to sideload from adb when I can't even detect my device. All I want is to retrieve my data & start up my device as normal.
Within the Command Prompt under platform tools, I typed adb devices. But no device listed. I am currently installing the Samsung Galaxy Note MTB device driver.
Can someone please guide me to the correct steps? There has to be a way to retrieve the data from the internal memory right?
Edit 1:
According to this article, I am not sure if my phone is bricked or trap in a bootloop...First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article)
Edit 2:
PC specs : Win Vista, 32-bit
After installing MTP drivers I am at this point. However within adb devices command I only see <aserial number> recovery. It doesn't say <serial number> device
Do I still have a hope to get to my data?
Your phone may be stuck in a BootLoop It wont get detected using adb try using FastBoot if not you should contact your samsung service center to reload software . Your data is lost in this case.
UPDATE
try downloading sp flash tool check your phone is detected if so you can have some hope in data recovery
I am testing an Android apk in my JellyBean tab (Its a relatively new one in the market, I cant get the drivers and their technical help is also quite useless).
The problem is :
I want to see the log/trace files.
LogCat or any other similar apps can't see the log in Jellybean.
I can't see my tab under adb devices.
The Power + Volume button pressing stops the tab.
Is there any way I can see the log, without rooting the device (I am fairly new to Android, and don't feel very confident doing so)
I can see a “Select debug app” and “Wait for debugger” menu in the tab. Can they be used to debug the application?
Is there any way I can see the log, without rooting the device
No, other than to get and install the ADB driver for your device from the manufacturer.
The version is 4.1.1, I think the developer mode is from 4.2
The change to READ_LOGS was introduced in Android 4.1 IIRC.
My Device shows up on the Android Device Chooser as:
Serial Number -- Ige-vm670-A0000028F1773B
AVD NAME -- N/A
Target -- 2.2.1 (with a green check mark next to it!)
State -- Online
Everything seems fine..So, I press the "OK" button on the bottom right hand corner of the Device Chooser screen. When I do this the Device Chooser closes and the Launching bar in eclipse eventually finishes, but then the application never starts on my phone!! :(. Am I missing something? I tried using different USB cables, switching from USB 3.0, and checking if there is enough memory on my phone but nothing seems to work :(. PLease help this newbie!! I'd much appriciate it!! ALso, i'm running eclipse in windows 8.
following steps may help you
1)Restart your Device
2)Go to application settings and enable the USB debugging.
3)also enable other application to run on your device.
4)make sure that device status is online on android device chooser.
5)make sure that your device appear in device list in android Eclipse.
If above steps wont help you then try to run your project on emualator.And if emulator fails to launch your project then you need to see the android console
Enabling SD-Card access may result failure of connecting to the device.
Please try to switch MTP on instead of either PTP or SD-Card