Database Info

[Q] com.android.provision has stopped?

So I've been running Graviton 2.0 on my Nexus 5 for a few months and recently I've tried upgrading to 2.6. Problem is, when I install the updated rom, I get the "Unfortunately, com.android.provision has stopped" error message loop times infinity. I tried installing 2.6 by booting into recovery mode and installing the zip using CWM. I then wiped the cache and the Dalvik. I've also tried doing a factory reset prior to the previously mentioned steps and that hasn't worked either. Any help would be much appreciated thank you.

squishywtrmln said:
So I've been running Graviton 2.0 on my Nexus 5 for a few months and recently I've tried upgrading to 2.6. Problem is, when I install the updated rom, I get the "Unfortunately, com.android.provision has stopped" error message loop times infinity. I tried installing 2.6 by booting into recovery mode and installing the zip using CWM. I then wiped the cache and the Dalvik. I've also tried doing a factory reset prior to the previously mentioned steps and that hasn't worked either. Any help would be much appreciated thank you.
Click to expand...
Click to collapse
If it we`re me, i would flash the factory image in fastboot, reroot and start over. Or do you have a working stored recovery to flash back to?

gee2012 said:
If it we`re me, i would flash the factory image in fastboot, reroot and start over. Or do you have a working stored recovery to flash back to?
Click to expand...
Click to collapse
I've been able to recover back to Graviton 2.0 after each unsuccessful attempt through the restore function in CWM.

Reboot loops on KatKiss-5.0_TF300T_014b.zip - HELP me, please

A week ago, more less, I installed KatKiss-5.0_TF300T_014b.zip on my Asus tf300t and everything was ok until today. When I have turned it on this morning I have noticed that it was staying in a reboot loop.
After that, I tried to reinstall this rom again through TWRP 2.8.0.0 but the reboot was there again. Then I tried to flash CM 11 snapshot m12, but the reboot was earlier. And now i don't know what I should do.
More info: when I flash superSU and gapps, the screen says "E: Unable to mount data" . Perhaps I should do a format data to fix it. What do you think?
Thanks for your answers

sergiolopezsan said:
A week ago, more less, I installed KatKiss-5.0_TF300T_014b.zip on my Asus tf300t and everything was ok until today. When I have turned it on this morning I have noticed that it was staying in a reboot loop.
After that, I tried to reinstall this rom again through TWRP 2.8.0.0 but the reboot was there again. Then I tried to flash CM 11 snapshot m12, but the reboot was earlier. And now i don't know what I should do.
More info: when I flash superSU and gapps, the screen says "E: Unable to mount data" . Perhaps I should do a format data to fix it. What do you think?
Thanks for your answers
Click to expand...
Click to collapse
I actually got the same problem with it when I flashed that. I did a factory reset from TWRP, then reflashed the ROM and Gapps to make the rebooting stop.

Format data??
cmendonc2 said:
I actually got the same problem with it when I flashed that. I did a factory reset from TWRP, then reflashed the ROM and Gapps to make the rebooting stop.
Click to expand...
Click to collapse
I have already tried it (factory reset) and the problem remains. What if i do a "format data"?

sergiolopezsan said:
I have already tried it (factory reset) and the problem remains. What if i do a "format data"?
Click to expand...
Click to collapse
The Format data within TWRP will delete all your apps and settings.

Now my tablet is ok after formatting data.

[Recovery][Boot] Recovery mode has highest boot priority?

So I unlocked, rooted and installed Euphoria ROM on my Moto G today, and now I'm perplexed to find that when I select the "Reboot" option either in Android or TWRP, I immediately get shoved back into TWRP. Rebooting to Bootloader works as expected, rebooting to Recovery works as expected, but the normal reboot doesn't.
Also, when my phone is offline and I plug it in, it immediately lights up and boots directly into TWRP. I don't know why this is, but I'd like to fix it since it's hit and miss trying to boot into the ROM normally.
Can anyone help me pin point the problem? In all my years with Android I've never seen an issue with boot priority such as this.
Things I have done:
-I tried to decide on a recovery so I flashed PhilZ, CWM, and TWRP in that order from the fastboot commandline
-wiped system, data, cache, dalvik cache, and flashed Euphoria ROM
Thanks!

One thing I would suggest is to flash the stock recovery and try rebooting, even i had encountered this problem. Later you can flash twrp again and everything will work fine.

Are you getting any errors while wiping partitions

sjandroiddeveloper said:
Are you getting any errors while wiping partitions
Click to expand...
Click to collapse
I'm having the same problem here. Wiping works alright, no errors at all. Although the built-in TWRP file manager is unable to see any files in the system folder.

[SOLVED] Google Apps Not Working And Recovery Refusing To Open

About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat

Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.

acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.

NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.

[Help] Flashed Franco Kernel over CM13 Stock and ended in bootloop

Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please

First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?

leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.

Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.