im using cherish os i downloaded from this vid
the rom was working fine but when i got avast it gave a alert saying Cneapp may contain malware, is it a false alarm or something to be worried about?
the app also has perms to phone and an additional permission called android.permission-group.UNDEFINED
i had downloaded the rom from the yotuube vid instead of official website cause the downloads from pling wer always stopping after 60 seconds of download
Bump, HavocOS user here and 2 of us on Telegram have also encountered this same thing
Edit: I found some more info about the service/app itself here: https://forum.xda-developers.com/t/how-to-disable-cneservice-or-its-high-usage-of-data.3642041/
I think it is very possible that it's a false positive since we're getting it across different ROMs, can't know for sure though
Related
I was finding something about t2 ultra then suddenly i have seen this site and they are telling and giving Marshmallow rom can anyone help me to determine is this a working rom
http://androidmarshmallow.tech/373-marshmallow-for-t2-ultra-dual.html
that site has lots of ported rom for various device,
all links are redirecting to same zip file.
for that reason,
I think, I THINK, it is fake..
I am sure but still I think it is fake.
rrd84 said:
that site has lots of ported rom for various device,
all links are redirecting to same zip file.
for that reason,
I think, I THINK, it is fake..
I am sure but still I think it is fake.
Click to expand...
Click to collapse
Absolutely fake. Every post is same,same words,same screenshots, and links to the same file "
benzo-gapps-M-20151011-signed-chroma-r3.zip". Misleading people with references like 'XDA-Developers'. Stay away from it.
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
really ...anyone who gets a brick because of not reading a thread certainly shouldnt be xda or even messing around with the phone in the first place. just stay stock if you wont read
We survived finely when Nougat was still new, so what makes Oreo special?
There's simply no good point to making a whole section for a particular version of Android. The same thing can be done simply with a proper thread title.
The problem isn't purely on the lack of separation of sections — It's the 5 seconds attention span that most seems to have because they can't read the first post of the thread they're in or they're too busy looking at butterflies and they ended up destroying their device and/or data inside the device.
I know we can't fix people, but that doesn't make for a good argument for creating a new section.
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
As stated. This is not gonna happen. If you cant do the proper research needed for what you are doing then you shouldnt be doing it in the first place.
I disagree with OP - there shouldn't be separate section for Oreo stuff. Ask yourself - what would happen, if released mod would be compatible with Marshmallow, Nougat and Oreo?
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
charackthe said:
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
Click to expand...
Click to collapse
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
zelendel said:
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
Click to expand...
Click to collapse
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
charackthe said:
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
Click to expand...
Click to collapse
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
zelendel said:
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
Click to expand...
Click to collapse
I see you all over the place! You are retired? You post on here like its full time lol
ZVNexus said:
I see you all over the place! You are retired? You post on here like its full time lol
Click to expand...
Click to collapse
I am a retired mod. My job allows for me to always be lurking around. Every couple of hours or so I check my email and catch up.
Been that way for as long as I can remember. Heck I used to be on far more in the early years.
[EDIT] it is fixed! I got it working, it was BusyBox etc
Hi. I have a problem that is with lucky patcher, and I don't know how to fix it or if any alternative apps is available for it. My device is originally a Samsung Galaxy S5 2016 (sm-a510f) with swedish carrier known as Comviq(tele2) and has unlocked bootloader and is rooted through magisk. Don't know if following info helps but had a problem when changing from superSU to magisk that involved me flashing stock rom.
My problem with lucky patcher started now after I flashed my rom and THE problem is that I mostly use lucky patcher for in app purchases, and when I used stock rom...it worked flawless(just took it's time but worked 7-10 times. Those 3 times is apps that lucky patcher cannot hack ) but now, I have an app, let's say subway surfers because it should work with lucky patcher... When I had the stock rom... It showed me the process and then creating odex file and then optional patches or something like that... Didn't pay much attention but now... With lineageOS, it doesn't even go that far and then done, patch 1 and 2 are green, and that normally should work ( should work with only number 1 or number 2 green ) and I open the app. When I wanted to buy something before, the prices could look something like 0.33, 0.35, 0.82 etc but now, it shows me the full real price, and when I go to hack a purchase...it doesn't prompt me the usual lucky patcher pop up... It gives me the Google play store. Is there any fix to this like a flashable zip or is lucky patcher not possible because gapps was used for all Google apps. Down below you have some info and links to where i grabbed my lineageOS, my gapps type (stock,full, super etc) and such. I would like if anyone could try to help me with this problem and I haven't tried anything, the only thing I tried was to reinstall it, and that didn't do anything. If there is anything with me running lineageOS, or having Android 8.1, then is there any settings or module that could make it work? If not...is there any alternative apps that works like lucky patcher... (Freedom,gamecih etc don't work either
specs/info that might help you:
Bootloader: unlocked
OS: lineageOS
Is your lineageOS official: no, it's unofficial
Android version: 8.1
Recovery: TWRP
Any access to Odin: yes but computer is my mom's and I'm not really allowed to use it so i would say no. Access is 1-10 but works every
Access to adb: unknown, I have adb on my mom's computer but I have no idea how to use it...
Where I grabbed my lineageOS version: https://goo.gl/cKH1dP
Don't worry, the link is shortened and will redirect you to a XDA thread with lineageOS for Samsung Galaxy A5 2016
Faster download for lineageOS if you need to look into the files (Google drive): https://goo.gl/aHxG95
My gapps os: 8.1
My gapps type: super
If you need any more information, please let me know. I know quite much technical language, so I would say I'm over average. Thanks in advance
Mod Edit
May I remind you of the XDA RULES
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Lucky patcher is deemed warez on this site.
Thread closed
malybru
Senior Moderator
Has anyone tried PAOSP Custom Rom Android 10 for z2 force? I have seen this zip file on mirror lollinet in Nash custom rom section.
https://mirrors.lolinet.com/firmware/moto/nash/custom/posp/
it seems to be flashable zip modified at 2019-Sept-09. I had a little chit chat with the founder of this project today. He replied by saying he had no idea who made this unofficial build for nash and said that we don't back unofficial builds except the phones we have officially released on their website.
I wanted to gave it a shot but that modem issue which has been all going for past couple of months NO baseband imei no turning back etc Stopped :crying: me from flashing it.
If anyone has tried please do share your experience. anyway I have a [XT1789-03] {Sprint} variant
I am downloading it. I will see what failures it has. I also use the sprint version
Jessooca said:
Both of the builds in the folder were made by @erfanoabdi well known guru of rom's. They work, I actually tested both builds for him after he made them. He's over on telegram if you want to join his group and get all the most current up to date methods, or message him here.
If you want to check out the android 10 official gsi image on the phone, you can download it directly from google developer and see what android 10 has to offer as well, I have it on my phone. Although over on his telegram group you'll get all the info if you want to check out his build of it, a minor variation of the actual official Android 10 GSI. No real issues to report, on Android 10 other than missing hardware keys at the bottom which can be enabled via a build.prop edit.
Again, I would suggest you join his telegram group if you want all the info or if you know what you're doing check out the Android 10 official gsi direct from Google. I am always one to try everything and if it breaks, so be it. I'll fix it, but there was literally zero issues with flashing it as an img file in twrp.
Click to expand...
Click to collapse
I was looking at the Google developer page for the Android 10 GSI's. I ran the code "adb shell getprop ro.treble.enabled" and it came back as false. The web page says not to continue since the phone isn't compatible. I was under the impression that the Z2 Force is A/B compatible.
So, how did you go about installing it on your phone?
Thanks for any info and assistance.
I've been around a while so I'm not new to Android or to tech in general but I am new to this Slot A/B stuff and also new to using Verizon 5G/LTE.
After soft-bricking my new phone by flashing TWRP and crDroid 8.2 based on Android 12, everything seems to be working well except I noticed that I'm not receiving MMS. I went to APN settings but I'm not able to edit the existing ones and if I add a new one, I can't change any settings there except the APN field. I also noticed that my build.prop identifies my phone as LE2123. I confirmed before I modified anything that I have LE2125. Any thoughts on this?
Resolution:
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved
If I'm not mistaken crDroid is
LOS based where Derpfest is AOSP based
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
ive had that happen on occasion. the latest bug i seem to have acquired is that during the phone connection where and when the person making the call (me) in said scenario wait's for the other party to answer does not hear anything until either some one answers or their voicemail does.
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Elrey567 said:
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Click to expand...
Click to collapse
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
oneszero said:
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
Click to expand...
Click to collapse
just now read your previous post. DERP!
djsubterrain said:
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
Click to expand...
Click to collapse
I actually did post in the crDroid thread and got no response so then I made a separate thread
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
oneszero said:
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
Click to expand...
Click to collapse
It says lahaina
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
ekin_strops said:
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
Click to expand...
Click to collapse
In my defense, I opened a single thread, not multiple. When I didn't get a response for two days in the crDroid thread, I assumed that if I was going to get any support that a dev would ask for the logs or other info they need. I mean, what's the point of going through the trouble of obtaining logcat and uploading it just to be ignored
Also, FWIW, I searched around this forum and google for a while before I started this thread precisely to avoid this situation.
Anyway from what I'm gathering, it sounds like maybe LOS 19 for this phone is not quite ready. I think I'll flash TWRP and go back to crDroid 7 for a bit. I might try one of the AOSP variants but I've always leaned toward the LOS flavors in the past
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved