Related
I completely messed up my Nexus when I was installing something and forgot to back it up. I made some more mistakes and now I don't have an OS. I've been searching for the past 4 hours on how to fix this and literally nothing is working for me.
If someone can help me get my device back up I WILL pay. I'm a total newbie with android... Let me know if you can help.
Describe what you did in detail up to this point.
Username invalid said:
Describe what you did in detail up to this point.
Click to expand...
Click to collapse
First mistake was attempting to install an Audio driver on my nexus. I got stuck on the loading screen so I was told to wipe my storage. Wiped everything! I have no clue what i'm supposed to do now...
I tried to system restore and reformat but the result is the same; When I reboot the device, I get stuck on the Google screen. On my PC, my device manager shows the device as Android Bootloader Interface.
AGul726 said:
First mistake was attempting to install an Audio driver on my nexus. I got stuck on the loading screen so I was told to wipe my storage. Wiped everything! I have no clue what i'm supposed to do now...
Click to expand...
Click to collapse
Did you install through recovery? Which recovery? Which loading screen?
Username invalid said:
Did you install through recovery? Which recovery? Which loading screen?
Click to expand...
Click to collapse
I installed it through TWRP. The loading screen I get is the default Google screen with the small lock button on the bottom.
AGul726 said:
I installed it through TWRP. The loading screen I get is the default Google screen with the small lock button on the bottom.
Click to expand...
Click to collapse
If you selected the format option in TWRP it would have deleted your userdata and internal partition leaving your system intact; unless you also selected to wipe the system in Advanced Wipe options.
Username invalid said:
If you selected the format option in TWRP it would have deleted your userdata and internal partition leaving your system intact; unless you also selected to wipe the system in Advanced Wipe options.
Click to expand...
Click to collapse
Thats the thing... I went into advanced wipe options and wiped the interal and userdata as well...
AGul726 said:
Thats the thing... I went into advanced wipe options and wiped the interal and userdata as well...
Click to expand...
Click to collapse
They probably meant to wipe just the cache and dalvik cache - not your system, userdata and internal.
I still have access to TWRP and bootloader. I'm trying to access fastboot so I can just flash a new ROM and everything should be back to normal but nothing is working for me. Teamviewer would help alot; if someone could come walk me through everything. I will pay, without a doubt, if I get it fixed.
If you still have your recovery and ADB setup on your computer then you can ADB push or ADB Sideload a ROM.
Username invalid said:
If you still have your recovery and ADB setup on your computer then you can ADB push or ADB Sideload a ROM.
Click to expand...
Click to collapse
Could you possibly get on teamviewer and walk me through this? I've been doing this for the last 4-5 hours and nothing is going my way... I'm honestly desperate to get this working again.
Something is wrong with my ADB Sideload; it keeps saying the device can't be found. I don't know what the problem is...
AGul726 said:
Could you possibly get on teamviewer and walk me through this? I've been doing this for the last 4-5 hours and nothing is going my way... I'm honestly desperate to get this working again.
Something is wrong with my ADB Sideload; it keeps saying the device can't be found. I don't know what the problem is...
Click to expand...
Click to collapse
I can try. PM me your Teamviewer ID and Pass.
I can't PM you; says you aren't accepting PMs at this time...
I'm in the same boat. I had a backup I was going to restore (after flashing a zip that gave me a bootloop), I formatted everything, lost my backups, have no OS and I keep getting device not found. Le Sigh.
Update: I used PDAnet, *reinstalled drivers*, currently flashing a rom. Thanks for all the help.
Can't you guys just go into fastboot mode and flash the stock images? And make sure the drivers are installled properly.
Edit: this one may work for you: http://forum.xda-developers.com/showthread.php?t=2381582
Remcotjuuh said:
Can't you guys just go into fastboot mode and flash the stock images? And make sure the drivers are installled properly.
Edit: this one may work for you: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Use the One Click Restore ^
I had done the exact same thing, wiping my OS out b4 copying a ROM onto the internal storage, but for different reasons, but the above link saved me.
This should help too:
http://forum.xda-developers.com/showthread.php?t=2380913
It should help you get out of almost any soft brick if I'm not mistaken.
Hello everyone,
I recently did upgrade my phones OS from 1.2.x to 2.1.5i (ColorOS) via flash, not OTA.
Afterwards I rooted it using TWRP & SuperSu.
I did return to Stock Recovery (community. oppo. com/en/forum.php?mod=viewthread&tid=17397&extra= (Sorry, I can't post links yet, you have to remove the spaces between community oppo and com)).
My problem now is, that I want to use the "Switch Partition" option, to unify my phone storage, but everytime I try the phone does only boot into recovery, as I had a custom recovery.
Do I need a newer Stock Recovery Version? And where/how can I update it?
Or is it possible to unify the storage manually and continue using ColorOS?
Thanks in advance for any help,
Carroll
Probably you need a newer version. Try this.
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash open gapps pico, but I'm not sure this works
javier.pc said:
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash pico, but I'm not sure this works
Click to expand...
Click to collapse
I did just download and install the PlayStore APK, which worked fine.
maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?
Hello, can you please share the stockrecovery.img for fastboot?
nizohio said:
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?
Click to expand...
Click to collapse
I think it is not necessary to download playstore.apk.
create a folder on your PC (Linux and Mac is your top choice), copy all your downloads in this folder (downloads = custom- rom zip, open_gapps zip, SuperSu zip etc)
next you need ADB (android debugging bridge) on your PC.
connect your smartphone with usb to your PC (usb debugging enabled on your phone- you find it under developer)
boot in recovery ( I assume you got lastest TWRP for your phone installed.)
in TWRP go to WIPE / ADVANCED WIPE --> tick Cache, Internal Storage, Data, System, Dalvik/Art Cache.
With this action you are going to lose all data, except data on your external SD and your OS as well. Common sense dictates to back up your data first :good:
after you swiped go to ADVANCED /ADB Sideload --> Swipe to Start Sideload
open your terminal on your pc and cd in your newly created folder with all your zip goodies.
type
Code:
adb sideload custom-zip
Use tab completion - very handy and you know there are no typos.
repeat this command with open-gapps.zip (beware you have to activate sideload in TWRP again) Caution: Do not reboot between installation of your custom - rom and open_gapps.
same procedure with Supersu.zip and so on.
After successful sideload installation, boot your phone to system. Now you should see welcome screen from Android and you have to do a few more setup steps to enjoy your new OS.
Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/
A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?
Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..
@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..
Today i installed LR recovery and rooted my phone then i installed Viper 4 android... everything went well.. at last i uninstalled xiamo sim activation apk because it bothered me every time i reboot my phone... but after uninstalling that my phone is no longer booting up.. it boots to fastboot mode only.. I can manually boot to twrp but my files are also corrupted...
anyway to recover my data? MIUI 11 indonesian rom
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
wang1chung said:
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
Click to expand...
Click to collapse
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
n70shan said:
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
antony.ps said:
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
Click to expand...
Click to collapse
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.7 and it opens now, will see what it does
n70shan said:
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.4 , and the problem is it opens and closes immediately.. what should i do now?
Click to expand...
Click to collapse
I'm using Linux right now, and it only runs on Java 11, maybe it's java version problem? Try to use Oracle Java 11 if Redhat or other OpenJDK distribution doesn't work.
n70shan said:
.......
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
wang1chung said:
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
Click to expand...
Click to collapse
Oh my bad i forget that.. been out of Android from months..
Anyways issues are resolved now with data lost ?
Thanks
Moderators can close the thread
I upgraded my 8 Pro to Android 11 (11.0.1.1 IN11BA) and was able to keep root using Magisk's feature "patch to inactive slot".
However, after two-three reboots on Android 11 (activating some Magisk modules, and installing some apps) the phone suddenly got stuck in a boot loop.
I figured it might be helpful for someone else to know how I recovered my phone without losing any data.
First, I needed to get access to the phone, so I entered fastboot mode by pressing volume button during boot.
Then I downloaded my firmware dump from XDA and patched the recovery.img using this tutorial:
https://forum.xda-developers.com/on...ecovery-oxygen-os-stock-recovery-adb-t4084487
My patched recovery image is linked in post #46 of that thread.
I fastboot flashed (since fastboot boot didn't work) the recovery image to my phone and rebooted to recovery.
Using the patched recovery image I was able to get root access to all partitions, including /data.
When investigating a boot loop on this phone I found the following path useful:
Code:
/mnt/vendor/op2/boot_log/
In that directory you will find logs from the last five or so boots, and at the end of the "android_boot.log" file I found this message:
Code:
StagingManager: Failed to install sessionId: 664232199 Error: APEX activation failed. Check logcat messages from apexd for more information.
I'm not familiar with "StagingManager" and "APEX sessions", but after digging through PackageInstallerService.java it seems this error is caused by some kind of app installation that is done during reboots (now I'm guessing).
Anyway, I didn't care much about the reason for the error, I just wanted my data back, so I deleted this file (containing the failed APEX session):
Code:
/data/system/install_sessions.xml
After deleting that file I was able to boot my system and access all my data again!
Nvm..
dladz said:
Don't need with the recovery is still intact so no need to touch it you'll cause more issues.
So you got the bootloop when you installed some magisk modules.
Click to expand...
Click to collapse
My boot loop was not caused by a magisk module. I did remove all magisk modules and even re-flashed stock boot.img, but that did not help.
adb wait-for-device didn't work since the boot loop occurred before adbd start (it seemed).
And, I absolutely didn't want to wipe my system from recovery.
nilezon said:
My boot loop was not caused by a magisk module. I did remove all magisk modules and even re-flashed stock boot.img, but that did not help.
adb wait-for-device didn't work since the boot loop occurred before adbd start (it seemed).
And, I absolutely didn't want to wipe my system from recovery.
Click to expand...
Click to collapse
No worries man I got the wrong end of the stick. Dw
I've Updated and it's stuck at bootloop . What I can do?
My mobile is the T-Mobile version that I have converted to Android 10 International.
this will help someone, for sure
nice work writing down your expirience
Just to be clear with what I said earlier.
If it fails after a magisk module installation then just boot to safe mode then reboot and all magisk modules will be deactivated.
According your post that's how it happened.
"However, after two-three reboots on Android 11 (activating some Magisk modules, and installing some apps) the phone suddenly got stuck in a boot loop"
1. Safe mode
2. Reboot
3. Remove last module and activate other modules.
Done
PS: I do a lot of module testing and this is my safety net so yes it 100% works.
You're method will help people for sure though
just so you know, you just saved my ass.
i expirienced the same problem
i did cleard data of google, google services, google framework and google play store
after that - google downloaded some kind of update and that's it
at android boot log there was same error
adb shell rm /data/system/install_sessions.xml using modded stock recovery rocks