Anyone run Rom Manager on their Gtablets?
Moved to general
Be careful with ROM Manager, as it updates you to a newer version of clockworkmod that doesn't play nice with some of our mods (or even the stock updates) - might give you the dreaded magic value mismatch.
Hi,
I have rooted my P500 since Froyo until to Gingerbread. I also helped my friend to root and install JB 4.2 on his Kindle Fire. Now I try to install JB 4.2 in my P500 using Rashed97 build 7 custom ROM but to all failure :crying:
The error was always failed to go into Google Play, there will be an error [RH-01]. After some investigation I found out that this is due to the Google Service Framework was never successfully install and run normally.
I am using this combination:
JB 4.2 ROM - cm-10-20130108-UNOFFICIAL-p500.zip
GAPPS - gapps-jb-4.2.1-light-20130107-signed.zip
I read hundreds of post in that thread and everyone is teaching about trimming the ROM before installing the GAPPS. So I tried to trim it both manually and using the OOne Rom editor. (Moving some apps as User Apps, using trimmed version LatinMe.apk, removing fonts, media, and etc) No luck as well; Google Service Framework just don't want to run According to the internal memory, I should still have 20MB++ of free space and I also check the /system/app and googleserviceframework.apk was in there. When I go to the "Settings -> Apps -> All" to find Google Service Framework but never found, it wasn't running at all even though it is in the system/app.
I try to see if I trim it correctly, so I try JB 4.1 combination:
JB 4.1 ROM - cm-10-20121110-UNOFFICIAL-p500.zip
GAPPS - gapps-jb-4.1.2-light-20121130-signed.zip
This time I use the Bill's tool, OOne Rom Editor, to trim it and try installing it... guess what, it works! Google Service Framework manage to run... So I am confused... Is it me or something else did I missed out in trimming the JB 4.2 Rom?
Anyone manage to make it happen? Can give some guidance?
Thanks
Silly me...
I think I know what is the problem already... Build 7 is CM 10 JB 4.1.2, it is not JB 4.2
Installing GAPPS for version JB 4.2 definitely not going to work... Stupid me... :silly:
After trying to install the GAPPS for JB 4.1. It works fine now :good:
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.
Hey there everyone.
We all love custom roms and we install them in our phone
But some of us might have faced issues with it and would have reported it and would have got it solved.
But I have searched XDA forums and checked that no one provided a solution for Whatsapp not working in CustomRoms.
READ BEFORE TRYING
Errors:
Unable to Connect to the internet?
Or stuck at initializing?
Its Easy to fix
I am using AOSP Based Rom and i owe a LG L90 D410
I installed whatsapp and it showed me a warning message that custom roms dont always work properly with whatsapp
But its just a mesage Proceed and find out if your custom rom supports.
IF NOT
Follow this Thread
Solution :
Go to settings and then apps. Once you are there , reset app preferences.
This must mostly fix the above listed problems.
If this did not solve your problem,Install whatsapp v 2.11.50 (Recommended)
Install it from any website that you like with Playstore Signature.(Or you cannot update your whatsapp)
Then complete verification and let it initialize your profile. It might take you in to your chat section within a minute.
If you are in and if you have your messages backed up,Restore them and update your whatsapp.
THATS IT YOUR WHATSAPP WILL WORK NOW
I hope this thread helps people who face issues with whatsapp (ONLY FOR CUSTOM ROMS)
Stock roms may contact support.(As they wont support custom roms )
any way to work on lineageos16 ? it say incorrect date when install the version u mentioned
I use custom ROM in grand 2 . I installed what's app and I had an issue of not receiving otp . I used parallel space and this time the otp came . then I uninstalled parallel space and then tried for otp again and it worked . hope it helped ..
How to fix this ? Im using RR 6.2.1 Rom Oreo based
I'm using a tablet, with magisk installed (magisk hide enabled for whatsapp) and AOSP based lollipop ROM. It says "tablets not currently supported". Sorry if I'm bumping the thread but I really need help
sarath11kb said:
I use custom ROM in grand 2 . I installed what's app and I had an issue of not receiving otp . I used parallel space and this time the otp came . then I uninstalled parallel space and then tried for otp again and it worked . hope it helped ..
Click to expand...
Click to collapse
How did u do it i cant get it to work :c
my whatshapp is working but camera dosent work but normal camera app is working
so recently I accidentally wiped everything on my phone except TWRP. Then I managed to boot up the phone with liquid remix installed with android 9.0 and now my phone is missing the Samsung apps (which I want on my phone) how can I get them back is there a flashable file or any installable pack I really want them back
so if someone can help please tell me what to do I will really appreciate it
Aosp based roms and Samsung apps usually don't mix very well.
You could backup your Samsung apps using Titanium backup, then try to install them one by one in your android 9.
You could also Google for a site that has Samsung apps apk's.
Don't expect much success ?
Sent from my SM-J700F using Tapatalk
I have the APK s I just can't download them to my device if you know how to install them can you help me or redirect me to someone else that knows what to do
I suppose you've enabled install apps from unknown sources in settings.
Try to install as you would any apk, i.e. open in file explorer.
As mentioned before, don't expect them to install anyway (maybe 1 out of 20??); most are not compatible with aosp roms.
For your aosp custom rom - look for similar gapps or apps from the app store or XDA.