I am trying to install Android 10 on an LG Nexus 5x (bullhead) smartphone. I installed the TWRP app, downloaded the Pixel Experience (the OS). I booted into TWRP recovery mode, and installed the OS, then rebooted.
After rebooting, the phone starts with the screen of language setup. Right there, the message "Google Services Framew...keeps stopping" keeps popping up, and I can't press on anything else.
I restarted the phone, went back to TWRP recovery mode, wiped data and installed the OS again. But that message still insists. Is there any way to fix it, or I've just broken the phone forever?
I finally found the offical forum for this Android 10 OS: https://forum.xda-developers.com/nexus-5x/development/pixelexperience-nexus-5x-t3861437/page141
Apparently, many people also experience this issue. I will look further for the solution on the official forum.
I finally found the answer. The Pixel Experience ROM must be installed in a decrypted data partition. Mine is encrypted, so I must remove the encryption.
The simple way is, instead of "Wipe", to choose "Format Data" in the TWRP recovery mode, then proceed as usual.
Related
My goal is to get my Moto G6 phone in Root Mode. I bought a blank phone for this purpose, so no data is at risk. After following the steps on the XDA guide, I only got so before things did not work as they described. If I reboot my phone, I get this blue Moto G6 bootscreen and the phone never boots. I can get TWRP running on the phone though. Right now, my phone is not being recognized by either adb or fastboot. The guide I've been following is at
https://forum.xda-developers.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3816569
c:\Software\MotoG6>adb shell
error: no devices/emulators found
c:\Software\MotoG6>fastboot devices
c:\Software\MotoG6>
I have the latest Moto G6 drivers installed, but I don't think they apply anymore. If I unplug and replug in the USB cable into my Windows machine, it says it does not recognize the device.
The firmware I saw on the device when it did boot was OPSS27.82-87
* I do not know how to go back to stock because it won't recognize the device enough for me to push the stock image to it. *
*** FWIW, even on step 3 of that guide, it would say the boot image was not signed or corrupt. This happened when I tried to do
fastboot flash boot <insert-boot-image-name-here>.img
someone else had that problem and the recommendation was to ignore the message and reboot to recovery.
(https://forum.xda-developers.com/moto-g4-plus/development/wip-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586/page2)
For those who would say, "Read the **** manual", bear in mind that I did read the manual. No manual said where to get the firmware information they asked for. Also, many of the image links were bad. They did not say how to handle the case where the image did not install as they said it would. Somehow these manufacturers make each phone just enough different, and each firmware is different that it's impossible to predict what a phone will say ahead of time with certainty.
When it shows no commands, press and hold the power button then tap volume up button once. Then release the power button.
If this doesn't work mostly likely needs to be sent back to the manufacturer.
I had rooted my Yu Yureka plus by unlocking the bootloader using adb fastboot method, then flashing the TWRP recovery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that.
But while playing a game the phone automatically rebooted and ever since have been stuck on "Preparing to start.. Starting apps.."
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls, but can't access anything
Any suggestions what I should do now?
I have tried doing a factory reset from recovery but the problem persists and none of the hardware buttons are working, had to remove battery to access the recovery (still cyanogen recovery is opening).
Please HELP!
you can us this tutorial to get back to stock rom
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Unable to install the drivers for the usb debugging mode on android-system.
The device — Sony Xperia V with Android 4.3, on the PC — Windows 7 Home Premium.
Phone Information in Device Manager. There he defined as "portable device". Sorry for language. It is russian :(
I downloaded the latest ADB drivers from the sit Google, set them manually, and the picture is as follows:
ADB does not see the phone.
Update the Windows driver does not, on the grounds that the best of everything is already.
If remove them when you reconnect a Windows device starts again instantly put all the same his driver.
Disable automatic driver installation failed. In the Home version of Widnows is only possible to disable autostart them with auto-update service, which I did. Set gpedit.msc, where he was to be an item on the prohibition of automatic installation of the device, but it was not there.
You can connect your phone is turned off debug mode and then turn it on. In the Device Manager list is updated, but nothing new in it does not appear.
I faced with this problem for a long time ago when I try to install a custom recovery . Then the phone just was not detected, probably due to lack of drivers. Tried in vain to fix anything, but it was easier to use someone else's car, where the driver got up at once as it should. Now, the problem still want to overcome, for debugging applications on android-emulator inconvenient, it would be nice to do it several times on a real device.
Now I don't know what to do :( Help me please.
You have to install the PC Companion from Sony.
I have a problem debugging apps on my Samsung Galaxy S3, (GTI9300, I believe this is also known as the international version) from Eclipse.
The thing is, debugging actually worked for a time and then it just stopped working. I've tried quite a few things to make it work again. I'll describe my whole experience briefly, to keep you from suggesting things I've already tried, and save us all some time.
When I first got my phone, debugging didn't work. When I plugged in my phone, the system detected it, and I could use it almost like a storage drive (using Media Transfer Protocol or some such thing) But when I started Eclipse and tried to debug, the debugger didn't see the phone.
I googled some, learned that I had to install some specific driver. I honestly don't remember which driver it was, but I believe it was an official one (from Samsung's website). Once I installed this driver, Windows would no longer detect my phone as a storage device. But the debugger did see it, and I was able to debug a few simple apps that I'd made. I could easily live with this tradeoff.
Then I got busy with other stuff and set Android development aside. I came back to it this weekend - after 2 or 3 months - only to find that it no longer works. No matter what I do, the debugger does not detect my phone (Windows still won't detect it either).
I tried all the first aid solutions like restarting Eclipse, rebooting my computer and rebooting the phone. Just for the sake of completeness, I do have usb debugging enabled on my phone.
The only major change of the whole setup that I can think of is that my phone's OS has recently updated. I don't know the exact version it was before, right now it's Android version 4.1.2 (Kernel version 3.0.31-1160235, if this is useful to anyone). I tried plugging the phone into other computers, it gets recognized as a media/storage phone. I can't install the Android development tools and try debugging on any of these computers - I'm stuck with the one I've got.
I've tried reinstalling the usb drivers for my phone. It didn't help. In desperation (and against my better judgement) I tried installing Samsung's software, first AllShare Control, and eventually Kies. None of it helped. When I run Kies, it gives me the option of connecting through USB or via WiFi. However it won't detect my phone when I plug it in. When I click "Troubleshoot connection" (or some such thing, unfortunately Kies decided to use my native language instead of English) it starts reinstalling the USB driver. This process takes quite a while, and fixes nothing.
I'm basically out of ideas, I don't know what to try next. Any help would be appreciated.
I am developing an app and when I uninstall the phone kind of semi-reboots.
This is my old post:
I have a strange problem with my phone. I am using SAMSUNG GALAXY 5
(GT-I5500) with Android 2.2 on it (not rooted).
I am an android developer and I have been doing pretty advanced apps.
However, sometimes when I am testing and installing an application the
phone reboots.
I'm starting it trough Eclipse but I do not know what exactly what
causes the phone to reboot.
It is not heat for sure, as I keep my phone cool enough.
It is not from the app source itself as the phone doesn't reboot while I am using the application but on installing time
It is not storage I think, because I have 26 MB internal and 1GB external memory free and the app is no more than 2 MB.
So my question is what could cause the phone to reboot?
In this context I define "reboot" as the phone showing the initial SAMSUNG screen, like normal booting but without the prompt for PIN. This is why I conclude it is something like semi-reboot or I do not exactly know.
Having experienced the same problem, I found that deleting dalvik cache and formatting cache partition helped - I can't tell which one of those two did the trick, but I can now happily uninstall apps again, without the device spontaneously rebooting.
Both operations I was able to perform in recovery mode, using ClockWorkMod rescue system, and they are non-destructive. No actual data or apps are lost, only next reboot takes longer, due to dalvik cache being rebuilt.
Today, close to a month later, that problem showed again, so I was able to test which of those two action fixes it. Turns out it was erasing the cache. Dalvik cache was left alone, deletion was possible afterwars nevertheless.
I have this exact problem with my LG G4. Whenever I try to uninstall an app the phone will just reboot. Luckily there is a way to remove unwanted apps if your phone has an expandable memory option through micro SD. Just transfer the unwanted app on the SD card then remove the card. The app will no longer exist on your phone. You can then just delete the app from your SD card using a PC. This doesn't help resolve the actual OS issue on your device but at least it's a quick fix for anyone who's looking to free up some space. Hope it helps!
Spontaneous reboots under unclear conditions, one of the "fun" things you get for free with Android. Not on each and every device, OS version or combination thereof, but quite too often.
With the following instructions you will loose all your data on your phone.
Try this: Get into the recovery mode (adb reboot recovery or start the phone with pressing (and holding) volume down, then press and hold the center key, then power on), then wipe data/factory reset, wipe cache partition.
(I experienced similar reboots but not with an I5500, so I don't know if this will help in this situation. It helped with a Motorola Milestone/Droid after upgrading to Android 2.2.)
I was able to fix this problem by wiping the davilk-cache thanks to Deleted User's experience. However, wiping the cache partition was not necessary in my case. I'm rooted stock Android 4.4.2 KitKat on a Galaxy Tab 3 SM-T210R.