Related
i have problem with Google+ app. When i go to settings and instant upload photos, then app stop working. I did full wipe before install the rom. Have anybody same problem?
how to solve it?
i foudn that my XXELLA original rom is no problem with it, but once flash WANAMLITE V5.3 then i not able to access the setting .
Hey all, I was updating the system apps of my mtk6589 device (infinix X451 - RBoltQ, android 4.2.1) device ie calender, email , deskclock, launcher etc to that of the android 4.4Kkat . Thay all worked perfectly it felt cool. I then updated my camera to that android 4.2.2 (all done with root explorer and link2SD ). Later on I came across the google camera. It always FC so I thought maybe making it a system app (using Link2SD) & deleting my other camera apps will resolve the issue. This didn't work . I even changed some lib files like I saw on a blog (libjn...mosaic,liblightcycle, lib..google.. - backed them all manually 1st though) still no avail. Now I restored the normal camera and the lib files, with their required permissions (root explorer) but ALL CAMERA apps installed FC ..even with a hard reset, the camera icon is NO LONGER there , only the gallery (for the stock camera). Apps like Antutu BM and Dx toolbox can't detect the camera (front and rear) or say Not supported. Same with apps that use Cam or flash or both. Flashlight too is no longer available while I noticed that the Glauncher now FC when I want to change wallpaper and the STOCK RECOVERY now shows an android with a red exclamaition mark. Gone 3 weeks without the camera, FL and now going through blogs and forums & I just don't know what to do.. Please any help will be appreciated as I don't want to loose my mtk device or its camera - even as my joy of getting my first android smartphone last year (dec 29) is turning into a nightmare. Thanks in advance.
(Sorry mods if I posted in the wrong section, kindly help me move it to the right place if possible, thanks)
Did you make backup before? I don't think so. Try to flash stock recovery and then install stock ROM (or custom ROM).
Hi,
I have an Xperia XZ dual sim (F8332) with :
An unlocked bootlader
Android 7.1.1 (build number 41.2.A.2.199)
AndropPlus Kernel version 3.18.31-v24
TWRP version 3.0.2-4,
Root with SuperSU v2.79
All flashed with Flashtool, following this wonderful guide : https://forum.xda-developers.com/xperia-xz/how-to/how-to-unlock-bl-kernel-twrp-root-t3541648
I have noticed that when my device is rooted with this configuration, after about a day (variable), I encounter two problems :
- Facebook app : no more refresh possible. I still have notifications but when clicking on them they lead to nothing. After a couple of try, the app becomes unusable, tells me to refresh as if I was offline and nothing happens. On my device, Facebook is shipped with the phone as a factory application. So is Twitter, but is seems to be OK so far.
- The Play Store works (I can download apps) but I don't have any images : no thumbnails, no screenshots... Only text and green layouts.
I tried to flash again Android 7.1.1 without wiping datas (restoring default kernel and voiding root), the apps work normally again. I assume this has to deal with the custom kernel or the root.
Solutions I tried (but failed) :
1)
boot in recovery mode
wipe dalvik/cache
reboot
wipe cache & datas from : Google Play Store, Google Play Services for Instant Apps, Services Google Play, Facebook
2)
log out from Facebook / Google account and log again
3)
uninstalling Facebook and Google Play with a root app uninstaller
install them again the usual way
So far I don't have more idea of what the problem might be. Do you encounter the same issues or have any idea about it ? Tell me if you need more information.
Thank you.
Maybe this is a very stupid question but I really have no idea why this problem occurs
My phone (HTC One S Ville mit Resurrection Remix (Android 5.1)) worked perfectly fine until last Friday.
At this date a new update of Telegram Messenger was released. I installed it and while installation of this app my phone did a restart and got stuck in a bootloop.
I restored using TWRP and retried - same problem. I also deleted the app and its data to do a fresh install - bootloop after installation.
Furthermore I noticed the exactly same behavior for the last update of WiGLE. All other apps could be updated to their latest versions without problems.
I used Google Play to update these apps.
What could be a problem for that? Is android just too old to these apps or could there be a collision with something installed on my phone/the ROM? How can I debug this?
I am not an android expert and I am very thankful for any kind of help :')
Thank you! =)
Same Problem with LG G2 mini / Android 6
Hello,
I'm facing the similar problems since a few days. Running Resurrection 6.0.1 on LG G2 Mini.
It started with installing maxdome-app at thursday, last week. Phone went into bootloop.
Wiping and or deinstalling the app in safe-mode did not work. So I restored to an older backup. This worked some time but ran into bootloop after a while ( I do not know what I've done exactly to get into this, this time).
I tried around a little. One part was a fresh install of cyanogenmod 13. This worked some time and I could find out that installing telegramm messenger had the bootloop-effect repeatable.
Sorry for not giving any help to the thread-creator but I hope we can give any more information to each other or anyone else can help?
Right now I am installing apps and backing up all the time to get some half-working system, but better ideas would be appreciated
Good to know that I am not alone
I figured out that there are a few more apps causing the bootloop. Here is a list:
WiGLE Wardriving
Telegram Messenger
pr0gramm.com app
Playstore Changelog (XPosed Module)
Statusbar Download Progress (XPosed Module)
Maxdome
I already updated Xposed Framework, Google Play Services and Google WebView to prevent incompatibilities. Problem still exists.
I updated everything as far as possible and made a backup using TWRP so I can restore my OS at any point. Further you could backup your apps using Titanium Backup. I it worth its price!
I started facing a similar problem of app updates causing bootloops on my device which was running CandySix ROM / 6.0.1. Apps causing bootlooping included Greenify and Nova Launcher. I had another device which has a factory 6.0.1 ROM rooted with Xposed and that device didn't have bootloop issues with these same versions of apps. Fortunately I was able to update the first device to a LineageOS 14.1 7.1.2 ROM and once again continue using the latest version of apps without bootlooping issues - but I never did understand exactly what was causing the bootlooping problem. That was a rather frustrating experience.
When the first bootloop happened, I was updating one single app, so I knew it was probably the one I should roll back to the previous version to fix the problem - so I didn't have to resort to a full TWRP restore.
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
In my case I can boot to custom recovery/TWRP to delete the app apk from the its /data/app folder - which basically prevents it from running when I reboot the phone. I also use an apk extractor app to save the apk of all apps I install and I also use Titanium Backup - so between those two I have copies of the older apk versions to install. You can also find older apk versions on apkmirror.com.
Depending on the severity of the bootloop, you can also connect your phone to a PC and use adb to disable/uninstall the app causing the problem if you know which one it is.
-kw said:
How did you do a rollback of an app while you are in a bootloop? I would be glad to know that
Unfortunately my Device One S Ville does not get any updates anymore
Click to expand...
Click to collapse
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Thanks and can confirm that deleting the app folder/apk via twrp can help. I got back into my android 6 again. For me seems more that DavDroid caused it (but Telegram was suspicious, too).
DavDroid mentioned in the last update on 4th November, that they released a workaround against crash and bootloops on some custom roms
Depending on how old your TWRP backup is, restoring from TWRP is an option. But often I have not made a backup in a while or made many recent changes that I didn't want to lose, so the other ways I suggested are more time efficient in some cases.
-kw said:
Thank you for your explanation! This sounds a bit more stressful to me than rather restore via TWRP but could me more time efficient for larger ROMs. I will keep this in mind
Click to expand...
Click to collapse
Upgrade to Android 7
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Glad you were able to update ROMs and escape the bootlooping problem
I have been running LineageOS 14.1 for about a month now without any bootlooping issues due to app updates - so I expect you won't have any issues. I did cause some dread time consuming to resolve bootlooping due to some bad substratum themes, but that's a different issue altogether .
michibr said:
I can add EDS app to the non-working programs.
As far as I could install Telegram (same Version) by downloading .apk I suspect the problem is something depending with playstore. This would explain the many affected apps. But of course I don't know it for sure.
Inspired from divineBliss I upgraded to Android 7 (LineageOS 14.1) and could install everything as I wanted without problems so far. Thanks for that. Looks good, but I will wait some days after I'm convinced.
@-kw: did you try the following link for upgrading to higher android-version?
https://forum.xda-developers.com/htc-one-s/development/7-1-lineage14-1-htc-one-s-ville-t3540981
Click to expand...
Click to collapse
@michibr:
I am very pleased with my Resurrection ROM; but this is stuck on Android 5.1. I will give a new ROM a try when I have the time for that
At this time it seems like this is the only solution of escaping the bootloop-problem
FYI
I updated to Android 7.1 RR and now I can update all my Apps without problems
I am sorry that this is the only solution I can provide, but still better than nothing
Hi all,
I'm having exactly the same problem, it all started with FB, then some other apps.
I had to reboot into Safe Mode to uninstall those apps.
I'm running on cm12.1 and I have my own reason not to upgrade to higher Android.
Am hoping someone can come out with a solution.
For now, here's my list of apps:
- Facebook (Facebook Lite is fine)
- Telegram
- Bluemail
- Local telco app
I am sorry to inform you that I did a lot of research and was not able to find any other solution than upgrading to a higher android.
The problem is with appt2 someone reported it in google's issue tracker and someone from goole descriped it in detail here's it :-
CyanogenMod has this function getPkgName (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/AssetManager.cpp). It creates a ResXMLTree on the stack and points it at a buffer from an asset without making a copy. Then it closes the asset before the ResXMLTree is destroyed.
For apps built by aapt, this is benign. However, aapt2 produces UTF-8 string pools, which cause the ResXMLTree's ResStringPool(mStrings)'s mCache to become non-null in ResStringPool::stringAt (https://github.com/CyanogenMod/android_frameworks_base/blob/cm-13.0/libs/androidfw/ResourceTypes.cpp). Then ResStringPool::uninit dereferences mHeader (which is now dangling), and a crash ensues.
This crash shows up in different ways. On one Cyanogen OS device, the launcher crashes when an app built with aapt2 has been installed, but only if the manifest is large (probably due to how deallocation happens for small vs large blobs). On another device, system_server crashes at boot if an aapt2-built app is installed.
We're attempting to work around this with a custom build of aapt2 that always produces a UTF-16 string pool for the manifest. Results so far are promising.
Can this be patched somehow at the OS via xposed for all of the roms that won't get updated?
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Is this .zip patch for any device with any Lollipop 5.1.1 ROM?
Because I just installed it and my HTC one X with Resurrection Remix ROM (Lollipop 5.1.1) goes black after the HTC logo.
lescht said:
The fix for this issue is available here (CM13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM12.1:
The fix for this issue is available here (12.1):
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Click to expand...
Click to collapse
Hello what is about cm11 kitkat 4.4.4 sameissue but no fix-
could anyone make a fix? Please help.
Disclaimer
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
LineageOS needs no introductions. This version of LineageOS-14.1 is a highly customised version solely for the Amazon Fire HD10
- EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.
- IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required).
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
- Saying something isn't working without proper explanation will not attract any attention.
Known Issues
- Wired headphones do not work
- Camera does not work
- OMX is only partially working
Prerequisites for Installation
- Clean installation is required coming from lineage-12.1
- Unlocked Bootloader
- TWRP Installed
Initial Installation
or coming from another rom
- Enter TWRP
- Enter wipe option
- Format Data
- Then swipe to factory reset
- Copy the ROM to your device
- Copy optional zips like gapps and magisk to device if required
- You also have the option of using micro-g framework
- Flash ROM, then optional zips
- Reboot
- And Enjoy
Upgrading to a new version
- Copy the ROM to your device
- Flash ROM
- And Enjoy
Downloads
*** Please do NOT create any mirrors ***
Lineage-14.1 for Amazon Fire HD10"
Source Code
- Kernel Source: https://github.com/ggow/android_kernel_amazon_mt8173-common
- Suez Tree: https://github.com/ggow/android_device_amazon_suez
- mt8173-common Tree: https://github.com/ggow/android_device_amazon_mt8173-common
Thanks
- @k4y0z and @xyz` for the bootloader hack
- @Goayandi for the mt8173 resources
- LineageOS
Note
Their is a issue with video playback do to the omx library files. This is a link to flash a fix in recovery for this problem below.
https://forum.xda-developers.com/showpost.php?p=80762749&postcount=248
XDA:DevDB Information
LineageOS, ROM for the Amazon Fire HD 8 and HD 10
Contributors
ggow, Ziona
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2019-09-26
Last Updated 2020-08-11
Changelog / Release Notes
26 September 2019
- Initial Release
Release Notes
- Stable with no crashes from base OS
- Wired headphones not working
- WiFi working
- Bluetooth working
- OMX partially broken
- Tested VLC as a work around for local playback works fine
- Youtube audio playing but no video
- Youtube through web browser is working
- Seems to be no lag downloading apps from playstore
- Device configs will be available once I have had time to digest the prototype
New Build is Up
26 September 2019
- Initial Release
Release Notes
- Stable with no crashes from base OS
- Wired headphones not working
- WiFi working
- Bluetooth working
- OMX partially broken
- Tested VLC as a work around for local playback works fine
- Youtube audio playing but no video
- Youtube through web browser is working
- Seems to be no lag downloading apps from playstore
- Device configs will be available once I have had time to digest the prototype
Omg thank you!
Umm.. what is OMX? Also, can I flash this over 12.1?
meanhoe said:
Omg thank you!
Umm.. what is OMX?
Click to expand...
Click to collapse
Its regarding media playback (OpenMaX)
Should be able to flash it over cm-12.1.
Be sure to install arm64 7.1 gapps the first time round.
Amazing, you are the man! Thanks! Lots of stuff already working nicely. The only thing I noticed in a quick test is video playback not working, Netflix won't even start, and YouTube just shows black screen.
Edit: WiFi also still drops occasionally, just like on CM 12.1.
I'm having a couple issues already. i dirty flashed over 12.1. installed magisk, then xposed-v89-sdk25-arm64.zip, and open_gapps-arm64-7.1-nano-20190926.zip.
Not Working:
1. Home and Recent buttons do not work. Does not work in navigation bar or in other apps such as LMT and FNG (Fluid Navigation Gestures)
2. when I open Solid Explorer, I get "requested file was not found. Path: /storage/sdcard1
3. Can't get into Developer Mode. Nothing shows up when I tap.
4. the Play Store does not download at all. it just keeps pending.
5. Plex does not work.
Working:
1. USB C Headphones (Earpods) w/ 2 adapters.
2. Amazon Prime Video does work but very choppy. Unwatchable.
3. YMusic. (gets a choppy slightly)
Update: I did a clean install and so far it's working much better. I'll have to reinstalll all my apps and test the rest later.
TLDR: DO A CLEAN INSTALL. a dirty flash from 12.1 will give you problems.
meanhoe said:
I'm having a couple issues already. i dirty flashed over 12.1. installed magisk, then xposed-v89-sdk25-arm64.zip, and open_gapps-arm64-7.1-nano-20190926.zip.
Not Working:
1. Home and Recent buttons do not work. Does not work in navigation bar or in other apps such as LMT and FNG (Fluid Navigation Gestures)
2. when I open Solid Explorer, I get "requested file was not found. Path: /storage/sdcard1
3. Can't get into Developer Mode. Nothing shows up when I tap.
4. the Play Store does not download at all. it just keeps pending.
5. Plex does not work.
Working:
1. USB C Headphones (Earpods) w/ 2 adapters.
2. Amazon Prime Video does work but very choppy. Unwatchable.
3. YMusic. (gets a choppy slightly)
Update: I did a clean install and so far it's working much better. I'll have to reinstalll all my apps and test the rest later.
Click to expand...
Click to collapse
Looks like a clean install is the way forward coming from another ROM.
konradsa said:
Amazing, you are the man! Thanks! Lots of stuff already working nicely. The only thing I noticed in a quick test is video playback not working, Netflix won't even start, and YouTube just shows black screen.
Edit: WiFi also still drops occasionally, just like on CM 12.1.
Click to expand...
Click to collapse
That's the conclusion I came to. The major issue is video playback. I'll start looking into that shortly.
Great to see Nougat coming to Fire HD10. Thanks!
Just have to unlock my bootloader and will give this a try.
Quick question: if it doesn't work as I expect, can I revert back to stock ROM without any problems?
german_psycho said:
Great to see Nougat coming to Fire HD10. Thanks!
Just have to unlock my bootloader and will give this a try.
Quick question: if it doesn't work as I expect, can I revert back to stock ROM without any problems?
Click to expand...
Click to collapse
If you have an unlocked bootloader and TWRP installed you can make a backup of your fireOS and then try any rom you want. If not satisfied you can restore fireOS. Go back to locked bootloader with stock rom is also possible (but why?).
PS: There is also a fully working Lineage 12.1 if you won't wait for video playback.
@retora Thank you. Tablet wasn't unlocked yet. Just manually debloated and rooted Stock ROM. But not many important things on it, so a factory reset wasn't that much of a headache.
Did the bootloader unlock, no problems at all. After it flashed this 14.1 ROM, GApps and Magisk. So far it seems to work really nice. I am just setting it up and will play around a bit.
Yeah, I saw that there is a 12.1, but I am sure @ggow will get the video playback working soon.
Is the download delay in playstore still present? This seems to be the most important issue as I learned in the 12.1-thread.
One new issue I noticed (was working fine on CM 12.1) is that I can't set up the Gmail app. It asks me to add an account, but if I try to add my Google account it tells me the account is already present on the device. Other Google apps like Photos work fine.
I did do wipe (but no data format) before installing the ROM, and I installed the pico gapps together with the ROM.
retora said:
Is the download delay in playstore still present? This seems to be the most important issue as I learned in the 12.1-thread.
Click to expand...
Click to collapse
Haven't experienced any delay with the Playstore. First I installed some benchmarks to compare it with the Stock ROM. Seems to be 4-5% faster than the Stock ROM, if I look at the average of the benachmarks I used.
Just did an update to all apps for which an update was available via Store (YouTube, Google, Photos) - started downloading right after clicking on "Update all". No delay either with starting the next app after updating the first one.
So far I am very satisfied. Gonna try some bluetooth devices and see how they behave.
ggow said:
Its regarding media playback (OpenMaX)
Should be able to flash it over cm-12.1.
Be sure to install arm64 7.1 gapps the first time round.
Click to expand...
Click to collapse
So if we're coming from your other ROM, we don't need to wipe? Just flash this and the newer gapps?
@GuyInDogSuit Some people are having issues with that so a clean flash is recommended
konradsa said:
One new issue I noticed (was working fine on CM 12.1) is that I can't set up the Gmail app. It asks me to add an account, but if I try to add my Google account it tells me the account is already present on the device. Other Google apps like Photos work fine.
I did do wipe (but no data format) before installing the ROM, and I installed the pico gapps together with the ROM.
Click to expand...
Click to collapse
Grant gmail app permissions and all will be good.
Any idea why I can't install Google Play Games?
Did a fresh install of the ROM with GApps mini. The Games app is downloaded by the store but fails to install with a general "The app can't be installed" message.
GuyInDogSuit said:
So if we're coming from your other ROM, we don't need to wipe? Just flash this and the newer gapps?
Click to expand...
Click to collapse
@GuyInDogSuit i did a dirty flash. i encountered many problems. a clean install is recommended.
@ggow perhaps you can add a note in your post to do a clean install if upgrading from 12.1 to prevent further queries regarding this issue.