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 this procedure! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I found that hike stucks on scanning contacts on the latest custom roms(Android N) out there. On the initial builds of these custom roms, hike worked flawlessly. But after updating them to latest builds, hike stuck on scanning contacts. I have Moto G4 Plus, Resurrection Remix N OMS(thanks to the developers) and i faced the same issue. I tried a found a way to use hike on custom roms.
Requirements
1) Titanium Backup - http://www.apkmirror.com/apk/titanium-track/titanium-backup/titanium-backup-7-0-0-11-release/titanium-backup/
2) A rooted device having stock or custom rom doesn't matter but on that custom rom hike should be properly working.
Steps:
1) Backup hike using titanium backup on that rom or device which has hike properly working. You can simply backup hike form the previous builds of your custom rom on which hike was working.
2) Now restore that hike backup (especially data) on latest build on which hike stuck on scanning contacts.
3) Wolah hike starts working.
Bugs
1) Hike can only be used to send and receive messages and files. No contacts can be shared.
2) Timeline doesn't show up. Instead a blank page
3) You can't share images directly. You have to select images under file option then only you can share images.
4)News, games coupons, match ups and cricket dont work.
5) On some builds chat dont hide automatically on locking the screen. You have to close the app for hidden chats to hide.
Working
1) Hike can send and receive messages and files
2)Chats can bhi hidden.
3) Hike direct
4) Chat themes, voice and video calls, stickers are working perfectly fine.
Conclusion
Its just a trick to use hike. Not a full proof method. If someone has a better way, please do let me know. I'll update the thread with credits . Do press the thanks button if this trick helped you. This is my first post. Please let me know if i am on the right path or i violated the rules of the community. Thanks:good:
++Addy98++ said:
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 this procedure! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I found that hike stucks on scanning contacts on the latest custom roms(Android N) out there. On the initial builds of these custom roms, hike worked flawlessly. But after updating them to latest builds, hike stuck on scanning contacts. I have Moto G4 Plus, Resurrection Remix N OMS(thanks to the developers) and i faced the same issue. I tried a found a way to use hike on custom roms.
Requirements
1) Titanium /[/URL]
2) A rooted device having stock or custom rom doesn't matter but on that custom rom hike should be properly working.
Steps:
1) Backup hike using titanium backup on that rom or device which has hike properly working. You can simply backup hike form the previous builds of your custom rom on which hike was working.
2) Now restore that hike backup (especially data) on latest build on which hike stuck on scanning contacts.
3) Wolah hike starts working.
Bugs
1) Hike can only be used to send and receive messages and files. No contacts can be shared.
2) Timeline doesn't show up. Instead a blank page
3) You can't share images directly. You have to select images under file option then only you can share images.
4)News, games coupons, match ups and cricket dont work.
5) On some builds chat dont hide automatically on locking the screen. You have to close the app for hidden chats to hide.
Working
1) Hike can send and receive messages and files
2)Chats can bhi hidden.
3) Hike direct
4) Chat themes, voice and video calls, stickers are working perfectly fine.
Conclusion
Its just a trick to use hike. Not a full proof method. If someone has a better way, please do let me know. I'll update the thread with credits . Do press the thanks button if this trick helped you. This is my first post. Please let me know if i am on the right path or i violated the rules of the community. Thanks:good:
Click to expand...
Click to collapse
Instead if you know Android coding add run time contacts permission codes and it will work flawlessly. I have tried to do this but I'm not in this field of development or coding or computer, so I could not do it, anyway maybe if I found exactly where to add those codes of requests I will do it... ?
Sagarmudhale said:
Instead if you know Android coding add run time contacts permission codes and it will work flawlessly. I have tried to do this but I'm not in this field of development or coding or computer, so I could not do it, anyway maybe if I found exactly where to add those codes of requests I will do it... ?
Click to expand...
Click to collapse
Surely
Help us dude, cuz this method really sucks.?
Need hike backup
Can anyone plz upload working hike plus data for cm 14.1??
++Addy98++ said:
Surely
Help us dude, cuz this method really sucks.
Click to expand...
Click to collapse
Yep dude, jus need to know where to add those code I have codes but I don't know where to add it anyway till then use apktool on windows to edit the apk file u can edit it with notepad :good:
I found an easy way
First install hike from play store and then log in into hike as usual it will get stuck at syncing contacts menu now minimum it and go into play store and sign up for beta testing and install the beta version and then open hike viola you will get past that screen but the bugs mentioned above will be the same and contacts wont sync but you can still get messages and if you want to send anything use file sending tool it is working and there is one more bug you can't change profile photos hope this helps
Any new fix?
still stuck on scanning contacts
i followed the same steps as u said. but its not working on rr rom. pls give a fix
Install latest magisk 13.2 through zip.
It passes safety net.
Then enable magisk hide from magisk manager settings nand hide hike .
It will make hike work properly without any issue ( Fully Functional)
prashant1997 said:
Install latest magisk 13.2 through zip.
It passes safety net.
Then enable magisk hide from magisk manager settings nand hide hike .
It will make hike work properly without any issue ( Fully Functional)
Click to expand...
Click to collapse
Not working for me.. Did evrythng told. Hike works perfectly on my old device moto g 1st gen running RR 7.1.2 but gets stuck at loading screen on moto g5 plus also running the same RR 7.1.2. Any work arounds?
suhas_agasthya said:
Not working for me.. Did evrythng told. Hike works perfectly on my old device moto g 1st gen running RR 7.1.2 but gets stuck at loading screen on moto g5 plus also running the same RR 7.1.2. Any work arounds?
Click to expand...
Click to collapse
It is working for me perfectly..
It may be because currently Google is detected magisk.
So you may have to wait for next update of magisk in which fix would be available..
suhas_agasthya said:
Not working for me.. Did evrythng told. Hike works perfectly on my old device moto g 1st gen running RR 7.1.2 but gets stuck at loading screen on moto g5 plus also running the same RR 7.1.2. Any work arounds?
Click to expand...
Click to collapse
try flashing rom with gapps, i too had this prob but flashing gapps micro 7.1.x parallely with the latest custom roms: RR, ViperOS and InvictaOS, i solved this prob!
Hope it works for you too! ^_^
laksh8ster said:
try flashing rom with gapps, i too had this prob but flashing gapps micro 7.1.x parallely with the latest custom roms: RR, ViperOS and InvictaOS, i solved this prob!
Hope it works for you too! ^_^
Click to expand...
Click to collapse
I ll give it a try. Thanks! No problem with magisk though. Everything is green including safetynet.
laksh8ster said:
try flashing rom with gapps, i too had this prob but flashing gapps micro 7.1.x parallely with the latest custom roms: RR, ViperOS and InvictaOS, i solved this prob!
Hope it works for you too! ^_^
Click to expand...
Click to collapse
Tried everything! No use though. Flashed RR rom with gapps of all sizes from mini to pico, still no hike.. Gets stuck at scanning contacts on Resurrection Remix 5.8.4 on Moto g5 plus.
Provide Stable Hike's backup
Hi..., I've same problem with same device. Please send me stable hike backup, as I haven't another rooted device. Thank in advance.
Download hike version 2.1.2.install and setup.then install the newer version.it show till the phone number typing screen but won't stop at syncing contacts. Works in moto g4 plus lineage RR and viper os.
Nifal said:
Download hike version 2.1.2.install and setup.then install the newer version.it show till the phone number typing screen but won't stop at syncing contacts. Works in moto g4 plus lineage RR and viper os.
Click to expand...
Click to collapse
This method works perfectly!
Hike is not woking while connected to wifi. When some times clear cache it works. But still it doesnt download voice notes. And important thing is that it was working properly before
Related
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.
I put together a small TWRP Installer/Magisk module for our OP3 devices
Whats included:
Google Dialer with working Location and Caller ID and Visual Voicemail
Google Contacts
Google Messages
Google Calculator
Carrier Services
Google DeskClock
Dialer Framework
This module removes:
Stock Messages
Stock Dialer
Stock Calculator
Stock Deskclock
Fetures coming soon:
Pixel 2 Launcher (having issues getting it to not force close after install)
Pixel 2 Live Wallpaper
Wallpaper
Pixel 2 Boot Animation
Pixel 2 Sounds
Pixel 2 Accent color
Google Pixel/Nexus Experiance Magisk Module
Google Pixel/Nexus Experiance TWRP Installer(Coming Soon)
I have not tested it on a OP3T since i dont have a 3T but it should work as well
Ive only tested this on OP3 Open Beta 29 but i dont see why it wont work on other versions
If anyone wants to test on 3T and report back that would be much appriciated
Credits:
Wr3ckd90
dustintinsley (for the idea and the base from his OP5 module)
if it didn't touch anything from kernel etc. then should its work on op3T too
also Its only for Hydrogen OS/Oxygen OS?
anyone tried it on other roms (AOSPA oreo/Nitrogen OS)?
is the module for LOS - Based roms or for AOSP and what android version ????
RKBD said:
if it didn't touch anything from kernel etc. then should its work on op3T too
also Its only for Hydrogen OS/Oxygen OS?
anyone tried it on other roms (AOSPA oreo/Nitrogen OS)?
Click to expand...
Click to collapse
I've only tested it on Oxygen OS.. I'll load a version of Hydrogen OS today and try..
ele95 said:
is the module for LOS - Based roms or for AOSP and what android version ????
Click to expand...
Click to collapse
I haven't tried it on LOS yet but you can get all the same fetures this offers if you use the aroma opengapps you can put everything this offers right now
When I try and install via magisk it fails, when I install via TWRP it installs fine - think you have the above the wrong way round
The phone pops up an error each time I open it, says the phone is not compatible and may not work - quite annoying to see it each time. Anyone else have this issue?
When can you give support for twrp?i have super su not magisk
instarobuk said:
When I try and install via magisk it fails, when I install via TWRP it installs fine - think you have the above the wrong way round
The phone pops up an error each time I open it, says the phone is not compatible and may not work - quite annoying to see it each time. Anyone else have this issue?
Click to expand...
Click to collapse
That's weird because it installed perfect in magisk for me I'll run it through a few more test on different versions of Hydrogen/Oxygen
ZeroVirus said:
When can you give support for twrp?i have super su not magisk
Click to expand...
Click to collapse
I'm working on that now I'm running into the problem of it saying not supported if you install via magisk it shouldn't show that message though the magisk installer should install just fine through twrp but you will have a not supported message when opening phone
Wr3ckd90 said:
That's weird because it installed perfect in magisk for me I'll run it through a few more test on different versions of Hydrogen/Oxygen
I'm working on that now I'm running into the problem of it saying not supported if you install via magisk it shouldn't show that message though the magisk installer should install just fine through twrp but you will have a not supported message when opening phone
Click to expand...
Click to collapse
Thanks, look forward to trying again very soon ?
please add support for LOS - Pixel accent clolor , navigationBar animation and round icons , this thread can help you https://forum.xda-developers.com/nexus-6/themes-apps/cool-pixel-mod-android-7-1-1-t3532951
Id love a TWRP flashable zip too (better than Magisk imo)
I'm working on a TWRP flashable I'm just running into the issue with the method I used to remove the pop-up in dialer isn't working in TWRP only Magisk I'll release the TWRP once I figure that out
I tried it on RR and I can't make and receive calls. Almost at all. How can I uninstall it? Is there another way apart from flashing my rom again ?
femiro said:
I tried it on RR and I can't make and receive calls. Almost at all. How can I uninstall it? Is there another way apart from flashing my rom again ?
Click to expand...
Click to collapse
If you installed it via Magisk just uninstall by removing it in the Magisk installer.. I'll create uninstallers for both Oos and AOSP today to restore the removed apps.
Wr3ckd90 said:
If you installed it via Magisk just uninstall by removing it in the Magisk installer.. I'll create uninstallers for both Oos and AOSP today to restore the removed apps.
Click to expand...
Click to collapse
I flashed the zip to install it and then I removed the module from Magisk. Still phone app crashes though.
Edit: I gave manually the permissions to phone app and it seems to work now.
Hi ! I use it on ExperienceOs based on OxygenOs 5.0.1 and work fine but this custom use busybox and don't know if are on permissive SeLinux ? But they had an App to choose it.
After clean Flash and use FreedomOs 3.2.1 based on OxygenOS 5.0 I had always the message in Google Dialer "The Dialer may malfunction on your version..." I had test it again after use Magisk mod "Google Framework" but always the mistake with Google Dialer ??? I don't know why ? Rrrr. I had just remove it in Magisk and use Oneplus App but I don't understand work fine with ExperienceOs and not with FreedomOS perhaps just OxygenOs ? work on 5.0.1 and not on 5.0 ? I stay the update of FreedomOs for see.
Another I had test in my computer to remove Google clock after extract it and compress in zip but won't work with magisk ? It's not a magisk mod.
How can remove exemple Google clock because Oneplus Ckock is better with the calendar option for alarm
But thank you a lot for your work it's the only one work on OOS Oréo
Hi, if I flash it via magisk and I remove it after it will restore stock deleted applications ?
Bryandu13 said:
Hi, if I flash it via magisk and I remove it after it will restore stock deleted applications ?
Click to expand...
Click to collapse
If you remove it after you just loose Clock And Calculator App ! But you can install it with Apk mirror for have Oneplus Clock and Calculator.
For Dialer just choose Oneplus Dialer again and work fine for me same for Oneplus Contact don't uninstall it.
I do to reinstall Google messager too because I use it and when I remove the mod Google messenger are delete too.
The mod had work fine with the custom rom ExperienceOS R32 Stable OOS 5.0.1 no message when use Google dialer all work fine and can apply substratum theme
But I had change and return to FreedomOS 3.2.1 OOS 5.0 and always message in Google Dialer
I stay a TWRP zip or update
So quick update... I'm still working on this I've hit a few more roadblocks I want to fix before releasing anything else
Mms on messages sends but can't use the mms part of messages weird also I'm still having issues with twrp with the dialer message trying to fix that still I hope I'll have something to release this weekend but not 100% sure..
Wr3ckd90 said:
So quick update... I'm still working on this I've hit a few more roadblocks I want to fix before releasing anything else
Mms on messages sends but can't use the mms part of messages weird also I'm still having issues with twrp with the dialer message trying to fix that still I hope I'll have something to release this weekend but not 100% sure..
Click to expand...
Click to collapse
Thanks for the info/update, and for bringing this to us. I love this mod, and prefer using Google's Dialer and Messages over OnePlus.
When you say "Mms on messages sends but can't use the mms part of messages", what do you mean? I thought I was able to send/receive MMS through Google Messages just fine. Are you talking about group messages, pics, etc...
I'm not currently on an OOS ROM, but will probably be moving back soon (today, probably) and can try to verify that for you if you want.
Thanks again!
Hi ! Thanks for your mod. I had rollback to ExperienceOs R32 and flash with Magisk your mod and work fine.
But I had a question if I want Oneplus clock and uninstall google clock how I do ? Please.
I had install the apk of Oneplus clock but isn't System App and google clock are System App and can't uninstall it.
Thanks
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
/* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * 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, and if you point the finger at me for messing up your device, I will laugh at you. * Your warranty will be void if you tamper with any part of your device / software. * Same statement for XDA. */
*Developed by MONSTER-PC on 4pda Forums *
Disclaimer:
I'm NOT the developer of this release. Don't contact me to report bugs
As most people (including myself) had stability problems with EUI 28s I've decided to upload MONSTER-PC release here too.
If the original developer or moderators have problem with that I'll gladly remove this post.
Debloated multilangual EUI 30s stable by MONSTER-PC
Changelog
V5
Updated Magisk
Remove Chinese unwanted apps
Added Russian Language
Disabled throttling
Downloads
V5 Release
Google Apps (OpenGapps)
(https://opengapps.org/ Use arm64 architecture ,6.0 Android version and choose pico variant if the link wont work)
Flashing Instructions
Flash in TWRP
-Wipe everything except Internal Storage
-Flash the ROM
-Reboot
-Complete the setup wizard.
-Reboot into TWRP and flash Gapps
Q&A:
Can I flash this ROM on X62xxx device?
I never had any problem flashing X62xxx ROM on my X626 device. Use with caution thought
My CPU has deep sleep issues
As usual for Helio x20 phones.
Flash this fix from Xiaomi EU forums for Redmi Pro
https://xiaomi.eu/community/threads/guide-battery-problems-fix-deep-sleep-fix-more.37211/
Can I use it on my X52xxx device ?
The tilte clearly states MTK and X62xx
adaa1262 said:
/* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * 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, and if you point the finger at me for messing up your device, I will laugh at you. * Your warranty will be void if you tamper with any part of your device / software. * Same statement for XDA. */
*Developed by MONSTER-PC on 4pda Forums *
Disclaimer:
I'm NOT the developer of this release. Don't contact me to report bugs
As most people (including myself) had stability problems with EUI 28s I've decided to upload MONSTER-PC release here too.
If the original developer or moderators have problem with that I'll gladly remove this post.
Debloated multilangual EUI 30s stable by MONSTER-PC
Changelog
V5
Updated Magisk
Remove Chinese unwanted apps
Added Russian Language
Disabled throttling
Downloads
V5 Release
Google Apps (OpenGapps)
(https://opengapps.org/ Use arm64 architecture ,6.0 Android version and choose pico variant if the link wont work)
Flashing Instructions
Flash in TWRP
-Wipe everything except Internal Storage
-Flash the ROM
-Reboot
-Complete the setup wizard.
-Reboot into TWRP and flash Gapps
Click to expand...
Click to collapse
Thanks for uploading. Pls, how do I get safety net check passed? Also, I can't watch my favourite TV apps because Google is not certified. What do I do?
rexmako said:
Thanks for uploading. Pls, how do I get safety net check passed? Also, I can't watch my favourite TV apps because Google is not certified. What do I do?
Click to expand...
Click to collapse
Just Google both of your problems.
As I've seen before safenet can be passed via a Magisk Module or option I think. Just check Magisk forums or Google it.
You'll have to register your device in order to get "certified" Playstore Google that too I think there's a link to register
new link
EUI 6.0_30S by MONSTER_PC v5 .zip
//mega.nz/&xid=17259,15700023,15700124,15700149,15700186,15700190,15700201&usg=ALkJrhhuFRIXlgZict372dp8KjXq87zHxg#!9nxyEKwb!r-suK3I2_4ZFgH7Pxl8m95Db0UAUWKIQasVy9YkVYcc
elizeu4926 said:
EUI 6.0_30S by MONSTER_PC v5 .zip
//mega.nz/&xid=17259,15700023,15700124,15700149,15700186,15700190,15700201&usg=ALkJrhhuFRIXlgZict372dp8KjXq87zHxg#!9nxyEKwb!r-suK3I2_4ZFgH7Pxl8m95Db0UAUWKIQasVy9YkVYcc
Click to expand...
Click to collapse
Thanks links fixed
weird. i have x626. after installing the rom, rebooting to twrp and installing gapps, the phone starts saying the launcher has stopped and i cant use the phone.
blowingoff said:
weird. i have x626. after installing the rom, rebooting to twrp and installing gapps, the phone starts saying the launcher has stopped and i cant use the phone.
Click to expand...
Click to collapse
Read the instructions carefully
As I said:
Wipe everything except Internal storage
Install the ROM and complete the Setup Wizard
And then reboot to recovery and flash Gapps
adaa1262 said:
Read the instructions carefully
As I said:
Wipe everything except Internal storage
Install the ROM and complete the Setup Wizard
And then reboot to recovery and flash Gapps
Click to expand...
Click to collapse
that's why I said that it's weird because I followed the steps, I know what I'm doing. I MAY have accidentally check internal storage option but don't think so. will try again later.
@blowingoff Same happened to me.
blowingoff said:
that's why I said that it's weird because I followed the steps, I know what I'm doing. I MAY have accidentally check internal storage option but don't think so. will try again later.
Click to expand...
Click to collapse
It happend on me once so the launcher is only crashing?
If that's the case you can easily get to the settings screen via the quick toggles on the top of the recent apps screen .
Find the launcher in apps menu, clear it's data and force stop it
Great rom. It's stable, fast and very good looking.
Thanks for your work MONSTER-PC.
Battety gets empty very fast at nights. With the ROM BB72 i only lost4% at nights with this one its 10-20%. The fastest ROM so far!
bojti said:
Battety gets empty very fast at nights. With the ROM BB72 i only lost4% at nights with this one its 10-20%. The fastest ROM so far!
Click to expand...
Click to collapse
Check the Q&A
There's a flashable zip that fixes deep sleep issues
It was the Messenger app that ate up the battery. With the light version there is no battery issue!
bojti said:
It was the Messenger app that ate up the battery. With the light version there is no battery issue!
Click to expand...
Click to collapse
I have the messenger app too but I doesn't eat up the battery.
The system usually won't leave it running in the background
Some info please!!!
Hi,could you tell me please,if the rom is compatible with le 2pro x625?Thanks in advance!!!
lycon33 said:
Hi,could you tell me please,if the rom is compatible with le 2pro x625?Thanks in advance!!!
Click to expand...
Click to collapse
It probably is
The Helio X25 is an overclocked X20
Okay, this is the rom of the launcher bug. One more rom buggy from leEco to save
Stock roms:
18s: freeze bug restart (no multilanguage)
20s: freeze calls (multilanguage - unique???)
23s: bug baterry
26s: bug (i don't remember, but it's buggy)
28s: there is no link for stock/official rom
The """"""best"""""" rom that i had test is CUCO32 28s, but there are some bugs:
-antutu 44400 score (stock rom is 90000~95000)
-after 4 or 5 days, for any reason, the apps uber and 99taxi stop work because "google services is updating". I had tried a lot methods to solve the problem, nothing works.
I give up, there is not a single rom from LeEco phone that does not have bugs, it's extremely annoying to waste hours and hours of day looking for roms to fix bugs. I'm going to install CUCO32 and try to sell that ****ing cell phone.
amarant_072 said:
Okay, this is the rom of the launcher bug. One more rom buggy from leEco to save
Stock roms:
18s: freeze bug restart (no multilanguage)
20s: freeze calls (multilanguage - unique???)
23s: bug baterry
26s: bug (i don't remember, but it's buggy)
28s: there is no link for stock/official rom
The """"""best"""""" rom that i had test is CUCO32 28s, but there are some bugs:
-antutu 44400 score (stock rom is 90000~95000)
-after 4 or 5 days, for any reason, the apps uber and 99taxi stop work because "google services is updating". I had tried a lot methods to solve the problem, nothing works.
I give up, there is not a single rom from LeEco phone that does not have bugs, it's extremely annoying to waste hours and hours of day looking for roms to fix bugs. I'm going to install CUCO32 and try to sell that ****ing cell phone.
Click to expand...
Click to collapse
I'm using this ROM for months without a single issue
If you have problems with the launcher just replace it with Rootless launcher
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.