my device Note 5 LP 5.1.1
I was not flashing or modifying any thing I was updating Google store apps and out of no where error 504 appeared and apps weren't updating.
cleared Play store cache and switched WiFi off didn't help .
I shot it down and waited then it start bootloobing .
I tried booting TWRP but Samsung recovery appeared and i know for sure I have had TWRP flashed before.
I reflashed TWRP again and tried deactivating xposed modules and then removing it completely it didn't work
clearing cache/art partition cache also didn't work I am out of option what should I do, For now I am not considering hard resting it.
re flashing kernels didn't help
unrooting with unSU Script didn't help
any help...
Related
all of a sudden when i go to the market to update my apps it starts and then returns and error 492.
i have been on overcome 4.0 for almost as long as the rom has been out and i am using overcome 4.0 kernel just as long.
this started happening yesterday and i have not been able to download new apps or update existing apps.
any idea how to fix this.
i have wiped davlik in recovery. i have cleared all cache and still not luck.
any ideas would be greatly appreciated.
thanks in advance
I am also experiencing the 492 error on the Play store. I am using a Wildfire S flashed with Cyanogen Mod 7.2 and the latest version of the play store. So far I have tried:
-Clearing Cache Partition
-Clearing Dalvik Cache
-Fixing Permissions
-Clearing data/cache for Play store and google framework
-Factory reset and repeating above
-chmodding left right and centre
The error occurs both when updating and downloading new apps from the market. I can still install APKs via ADB and the file manager.
I've tried everything I can think of, and google my laptop to bits on the issue and none of the solutions I have found offer anything that I haven't already tried.
Can anybody think of anything missed? The only thing I have not done is reflash the ROM.
Cheers
Mark
I reflashed Overcome and everything was fine since 7/14/2012
today i am getting the error 492... again and apps will not download or update.
does anyone know why this is happening?
its very frustrating
Hi Everyone,
I have just update my phone to slim bean 2.7, everything seems ok except for play store i cannot install apps as it gives 942 error.
I tried all the solutions mentioned in the development forum but still getting errors.
I installed the new play store using the cwm, but then its saying it cannot find the application to be installed.
Please help.
deadmantfa said:
Hi Everyone,
I have just update my phone to slim bean 2.7, everything seems ok except for play store i cannot install apps as it gives 942 error.
I tried all the solutions mentioned in the development forum but still getting errors.
I installed the new play store using the cwm, but then its saying it cannot find the application to be installed.
Please help.
Click to expand...
Click to collapse
reflash device and gapps change dpi reboot clear play store data change dpi done
Yday it happen same on mine so i reinstalled playstore and wipe cache and wiped delvik cache now its workin fine
Tried both, still having the error
mihirr said:
Yday it happen same on mine so i reinstalled playstore and wipe cache and wiped delvik cache now its workin fine
Click to expand...
Click to collapse
Hi,
I am really frustrated, after a factory reset of SlimBean 2.8, which rebooted to often, I have the described problem on my Nexus S.
I tried the above ... one of the steps of the first method described the change of DPI, I guess that is the first value you can change in the "developer options" > "LCD density" to a higher DPI ... reboot and other steps ... didn't work. The second method with clearing cache and dalvik then reinstalling OS and Gapps rebooting, then clearing data of play store and service ... reboot ... still same problem.
Then I installed the latest playstore from an APK file ... after that it tells me my device is not supported (tough it used to run on the device).
If I can't fix this, I'll switch to Cyanogen or stock possibly ROM, though I really like the SlimBean features.
Any further clues before I do this?
Thanks & regards
Joe
I'm running LP. After flashing the zip, it boots (after doing the "Android is upgrading" thing), but then if you shut it down/reboot it bootloops. If I wipe cache through recovery, it boots fine again (after doing the "upgrading" thing once again) and works fine till the next shutdown/reboot.
It doesnt work yet, there is no fix either..
Xposed for lollipop is still an alpha version and should not really be used
Sent from my D5803 using XDA Premium HD app
it does work for some people.
http://forum.xda-developers.com/z3-...osed-custom-recovery-lollipop-backup-t3066716
http://forum.xda-developers.com/z3-compact/development/xposed-lollipop-list-modules-t3061563
Bump
If it is any comfort, I have same issue - and yeah, read in other threads some people it is working perfectly.
Out of desperation I even tried factory-reset but still ended up needing to wipe cache/ Dalvik cache like you.
Hopefully, the Dev will soon release a working-for-all version.
For anyone who has the same issue (and is running on the stock ROM): A factory reset through TWRP did not fix the problem for me. I had to reflash the ROM.
illpillow said:
For anyone who has the same issue (and is running on the stock ROM): A factory reset through TWRP did not fix the problem for me. I had to reflash the ROM.
Click to expand...
Click to collapse
you can just manually uninstall xposed, no need to wipe or reflash anything
Installing XPosed worked fine, the problem was the module installer. Even after removing the installer, the device still was looped. Another explanation could be that I was too dump to remove the installer. For anyone else having the problem, you may post how to remove the installer after being in a boot loop.
I managed to get Xposed to work - got rid of the infernal boot loop issue:
Came from rooted KK 5.77
Flashed pre-rooted Lollipop with R/W enabled, based on CE1
Ran 'Byeselinux' for recovery
Flashed 'Xposed.zip'
Installed 'Xposed alpha2'
Above resulting in the boot loop.
Flashed the 3 files directly on top of my setup, wipe cache/ Dalvik cache & reboot as suggested in this thread: http://forum.xda-developers.com/z3/development/lp-mini-deodex-t3076490
Tested by d/l-ing app from Playstore, installed Amplify from Xposed (had already Lolistat, Xperia/AOSP NavBar & Fix Lollipop Memory Leak running/installed), 5 reboots and all is ok.
Hi. i'm on Galaxy S6 6.0.1 marshmallow (STOCK ROM) that recently rooted and installed Xposed custom build by wanam.
I regret after finding out that i was unable to use barclays banking app and snapchat;
Unsure if my phone is soft bricked due to my history of actions:
First, i have installed normal xposed that caused bootloop and then proceed to replace it with the custom build version by wanam upon researching in the forums.
Upon finding out that i was unable to use the apps mentioned above after booting,
I unrooted my phone believing it was due to the root without removing xposed. It still didn't work so I rerooted it back just to remove xposed.
After flashing the uninstaller.zip, it went on bootloop again. I tried flashing several uninstaller including the one provided by wanam and it all didn't work.
The only solution i found in the internet was to deleting the file on data/data/de.****xposed via TWRP file manager. That didn't work as well and I panicked when the reboot button in TWRP weren't working anymore so i manually rebooted and proceeded to wipe my data heavy-heartedly which also didn't bypass the bootloop.
Now, i am left with no option and only able to use my newly wiped phone after reinstalling Xposed again.
dleeyx said:
Hi. i'm on Galaxy S6 6.0.1 marshmallow (STOCK ROM) that recently rooted and installed Xposed custom build by wanam.
I regret after finding out that i was unable to use barclays banking app and snapchat;
Unsure if my phone is soft bricked due to my history of actions:
First, i have installed normal xposed that caused bootloop and then proceed to replace it with the custom build version by wanam upon researching in the forums.
Upon finding out that i was unable to use the apps mentioned above after booting,
I unrooted my phone believing it was due to the root without removing xposed. It still didn't work so I rerooted it back just to remove xposed.
After flashing the uninstaller.zip, it went on bootloop again. I tried flashing several uninstaller including the one provided by wanam and it all didn't work.
The only solution i found in the internet was to deleting the file on data/data/de.****xposed via TWRP file manager. That didn't work as well and I panicked when the reboot button in TWRP weren't working anymore so i manually rebooted and proceeded to wipe my data heavy-heartedly which also didn't bypass the bootloop.
Now, i am left with no option and only able to use my newly wiped phone after reinstalling Xposed again.
Click to expand...
Click to collapse
Did you wipe dalvik&cache after flashing the uninstaller?
Portgas D. Ace said:
Did you wipe dalvik&cache after flashing the uninstaller?
Click to expand...
Click to collapse
Yes, although i need to manually reboot it as TWRP doesn't reboot automatically for me.
Would you think that might be the problem?
dleeyx said:
Yes, although i need to manually reboot it as TWRP doesn't reboot automatically for me.
Would you think that might be the problem?
Click to expand...
Click to collapse
I don't think so. I would suggest that you ask for help in wanam's Xposed thread as this is the version you installed.
I have Xperia Z3c 5.1.1 rooted with locked bootloader. It is on wifi only. Yesterday I've turned wifi on and suddenly have got device off. I tried to reboot. I see the Xperia logo and bluish Xperia start screen with waving elements. However, the home screen and apps are not appeared, have just black screen. The battery is fully charged (green led). I tried several times reboot today as well with the same result. I believe the phone is soft bricked.
The phone is rooted with NDR Utils and TeamWin Recovery (TWRP). I also have Titanium backup.
After reading this forum I found several ways to unbrick the phone:
1. Soft reset (Power + VolUP) up to 1 vibration.
2. Hard reset (Power + VolUP) up to 3 vibrations.
3.Use flashtool (flashmode) and flash ftf file. Should I flash Kernel as well?
4. Use phone System recovery (Power + VolDown).
Which method I should try first? Can I save root and my current Lollipop firmware or I should go and start from the scratch with rooting and flashing 5.1 again?
Thank you for your suggestions.
Try soft reset and hard reset. This don't break your phone but it is worth a try. If this will not work do NAND backup (full backup of phone) in recovery. Now you can try clear cache in TWRP (wipe -> advanced wipe -> check cache -> swipe to wipe). If this don't work try clear dalvik/art cache.
If this metods didn't work flash same rom (if rom was't pre-rooted root after flash). If system starts you can restore NAND backup without system partition and cache.
If system don't start after restore backup the last chance is clear rom flash.
I don't know where the problem is but in my place I would do that
Thank you krzysiek546 for your help.
I have tried soft and hard reset, both unsuccesful. I made backup and wiped cache and dalvik from within TWRP. The phone after apps optimization has started the system (there was black screen but I was able to see home and Back buttons, which were non-functional, i.e non-responsive.) The screen became black again after a few secs and did not return to the life then.
I think I'm going to flash the Rom. My question is there is any chance to get brick again in case I will restore from the TWRP backup (if there was a virus or something?). May be I should wipe data, cache and dalvik and only then made a backup?
Also, when you saying "a clear rom flash" as a last chance do you mean factory reset?
Thank you.
Don't wipe data before backup. This is like doing backup after format system. It doesn't make sense.
Have you tried this metod with flash with nand backup and flash same rom (zip from twrp or ftf from flashtool) and restoring data without system partition (it's important)? In this i mean something corrupted system files. In this metod you can save your data. You just reinstall system and restore data from nand backup.
When I sayed "a clear rom flash" i mean wiping all data in recovery and flash rom from flashtool or twrp without restoring anything. You can do it first. I think now it's beter because you can check did that fixed your problem and if this "clear rom flash" repair your problem you can restore data from backup.
As to your question. Yes you can get brick from restoring data from twrp but in my opinion this virus or something must have root permissions to do this.
After installing the newest supersu, I also get this bootloop. Is there a chance to undo this without wiping data?
Edit: ok, after hard reset, flashing SU, cleaning caches etc. (which all did not help) I reflashed the ROM, now it works again. Pheeew.
firox said:
After installing the newest supersu, I also get this bootloop. Is there a chance to undo this without wiping data?
Click to expand...
Click to collapse
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
MATPOC said:
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
Click to expand...
Click to collapse
When I had that error, it was still V2.80 and no update round the corner.
Thank you for the link. Worked great for me. Installed per TWRP.
Well, in my case I didn't updated SuperSU, just have turned on wifi. I think the problem may be in Wallpaper app I have installed previously. It changes wallpaper every day, but I noticed sometimes the background of my home screen where all apps are became black.
Anyway, only "clear rom flash" with wiping cache, dalvik and data helped me. I then installed pre-rooted Lollipop ROM I made before and restored all custom apps from the Titanium backup. BTW, don't try to restore system apps from the Titanium, I've got the error with Xperia keyboard and have to make a restore whole system from TWRP.
Thank you krzysiek546 very much for your help.
MATPOC said:
Try to install SuperSU v2.81 - author apologized for inconvenience caused regarding 2.80 update. I got this bootloop too and solved it by installing SuperSU v2.81.
Click to expand...
Click to collapse
I also got bootloop after installing latest SuperSU from Google Play.
How can I install 2.81 (or 2.79) when phone is in bootloop?