Develop Bugs

[Q] GT-I9195 Black Edition - What to do in which order?

Hi,
please give keywords and guiding advice, I will try to find the corresponding threads by myself
I have a brand new GT-I9195 Black Edition. I want to do as less damage as possible, so what do I have to do to get CM11 with Xposed framework running?
I just switched it on, started KIES 2 and connected. No SIM-card is inserted, no microSD-card, no WiFi connection. The phone is offline.
KIES says that the firmware is the most recent and gives this:
Code:
I9195XXUBML4 / I9195YBTBNA2 / I9195XXUBML4 / I9195XXUBML4 (DBT)
I assume this is not the newest firmware, and according to this thread (German) "I9195XXUCNE6 I9195OXACNE6 DBT 4.4.2 23.05.2014 is newer.
I have or see no possibility to upgrade via KIES.
Would the new firmware give me another, better modem/baseband firmware? If so, I would flash with Odin 3.09.
I think I need root permissions for Xposed and XPrivacy, at least this is what I did with my Sony Xperia mango. Is that correct?
What steps do I have to take to get root access without interacting with KNOX? Does it make sense to avoid the KNOX counter increase?
What part of the warranty will be void if KNOX is triggered?
What recovery should I use? There is already a recovery available, accessible by pressing Volume Up and home button at the same time when switching on.
I wanted to start with CM11 and no special kernel, just what CM11 brings, to keep it easy. So flashing serranoltexx M9 or later should be sufficient?
How do I get Xposed and XPrivacy to work? I want it working before putting in the SIM card and connecting to the internet. Do I have to worry about dalvik and ART?
GApps 20140105 from http://wiki.cyanogenmod.org/w/Google_Apps are the right ones?
Did I forget something?
Thank you
Raubsau

You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.

MarkAndroid.UK said:
You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.
Click to expand...
Click to collapse
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?

Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
Why is it so important to you to install XPrivacy before first boot?

Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
No one wants to brick their device, do they? I've never bricked mine and I've made lots of mistakes. It is highly unlikely unless you try to flash something not meant for your device or something similarly bad.
I certainly haven't found CWM being recommended over TWRP - devs here tend not to recommend, just point things out; ALL choices are yours. There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it. ROM's are built from components and not everything has to be there - one of the brilliant things about Android is how it interfaces with all the different aspects of a mobile device - it appears to be one program running everything but it is extremely modular.
With external apk's I just copy them to external SD and install them on the phone.

Raubsau said:
Do I have to worry about dalvik and ART?
Click to expand...
Click to collapse
Forgot this bit!
No. You can elect to use ART in the system setting of some ROM's (certainly SLIM) and I know some people who do. However, ART is still under development and by no means are all apps ready for it yet. Xposed Framework itself will not work under ART and won't be for quite a while yet.

MarkAndroid.UK said:
There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it.
With external apk's I just copy them to external SD and install them on the phone.
Click to expand...
Click to collapse
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.

Raubsau said:
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.
Click to expand...
Click to collapse
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.

MarkAndroid.UK said:
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.
Click to expand...
Click to collapse
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?

Raubsau said:
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?
Click to expand...
Click to collapse
'Small' would be fine

MarkAndroid.UK said:
'Small' would be fine
Click to expand...
Click to collapse
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help

Raubsau said:
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help
Click to expand...
Click to collapse
That's great, have fun and you're welcome

Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
I intend to buy the 'black edition' too but I am worried whether the internals changed as it's a later model and hence CM wouldn't run on it...
black edition:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
"ordinary" black version:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-1.jpg
Thanks a lot

soikku said:
Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
Thanks a lot
Click to expand...
Click to collapse
If the model number of the device you wish to buy is I9190 or I9195 then you can follow standard procedure.
Black edition is just cosmetic variation. Nothing special about that. Model number is always I9190/2/5.
So use normal procedure from threads in this forum. Good luck.

My phone looks like this:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
Info in the Settings menu says "GT-I9195".
As I was using XPrivacy fromt the start, some of these problems may have occured because of wrong restrictions:
- orientation of indicator in Google Maps shows wrong direction
- no compass app is working
I use my phone for calling, reading and writing mails, and remote control my media box. In the few cases I needed it for navigation, it worked fine (regardless of the wrong indicator).
Hope that helps.

Thank you for the replies, Raubsau and sasank360
Thank you for pointing out that the 'black edition' indeed is identical to the previous one internally.
I ordered the phone now and am looking forward to happy flashing (CM11 for the time being as freecyngn doesn't work for CM12 (yet)).

Professional help

Ok let me be really specific i have flashed stock firmware through odin, i have done clean wipes, i have done every possible thing in my power but still experience horrible tablet preformance i get app stops and restarts everytime even after i have flashed on odin no one here has been able to help me they tell me to do the same thing over and over download stock firmware and flash, do a clean wipe iv'e done it all please help i know someone can i think its a file in the screenshots i enclosed that is corrupted but i have no idea which one is it. its not the system or the kernel it is something deeper please help i am begging you developers

k,
no offense, but your post is wildly disrespectful. [frowny face]
you are basically putting the proper ownership of your error off on others.
to be fair, in your ignorance you flashed a firmware without first doing some research on the topic.
a noobish mistake, it happens, i've done it.
there were plenty of threads created prior to your experience warning of new samsung releases
overwriting bootloaders and how to navigate the issue.
from my interaction with you, i think i am accurate in saying you did not do the aforementioned research.
i for one took time to describe a way to "fix" your issue. You chose not to attempt it, which is fair. It is risky.
Cool.
However, lots of the users you've interacted with on xda have a fair to expert handle on how to get things done.
they do what they can to help, they cannot be expected to compensate for another's impatience, lack of attention
to detail and/or incompetence/ineptitude.
m

What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago

kgalv419 said:
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
Click to expand...
Click to collapse
hmm,
okay, different approach.
http://m.youtube.com/watch?v=JmvCpR45LKA
just a refresher.
now,
screenshots of directories are next to useless.
what's needed is , at the very least a logcat.
to get that or anything else moving you need,
custom recovery installed.
root.
busybox.
adb setup properly on pc.
the ability to describe you problem in words other than my thing doesn't work.
the sense not to keep creating thread after thread concerning the same issue.
if you are that insistent on undoing what you have done, my previous suggestion to you is probably the best bet.
if you want "Professional" help then seek a repair service.
Savvy?
m

Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer

kgalv419 said:
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
Click to expand...
Click to collapse
k,
okay, cool. sorry for being so rough on you.
i am downloading a copy of 4.4.2 firmware though linking me to the firmware
you initially flashed would be good.
what would be better is if you still have the firmware file crack it open with 7zip and get me a list
of the files [.img, .bin] inside.
run logcat after you boot up. attach to post as text file
then run your routine to where you get your issue, fc's etc and run logcat again and post as text [2]
m
okay it looks like i am not going to be downloading the 4.4.2 firmware.
downloads break from the one source i found
and i have no interest in joining the other site. that's bull****.
so if you can get me the list of files contained in the realease that would be helpful.

OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.

kgalv419 said:
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
Click to expand...
Click to collapse
k,
dude, where's my car ? [log ?] :silly:
m

Here bro

kgalv419 said:
Here bro
Click to expand...
Click to collapse
k,
i am going to guess you are trying to run a battery/governor tweaker ?
i am going to guess when you type getenforce in terminal
your output will be enforcing.
i am guessing when you resend your logcat you will do so after
typing su
and then
logcat -d > /sdcard/logcat.txt
if my guesses as to the app and selinux are correct you;
a- need to let the app go into the dustbin of history
b- need to look for a tutorial on dumping/unpacking/customizing/repacking/reflashing your boot.img
in order to disable selinux and make it stick.
if my guesses are wrong it is because;
the log you posted is super-lame [sorry] use your terminal, not a catlog app.
you have yet to tell me what app are giving you your headache. in which event is an issue between you
and the app's developer.
lastly you should be question the developer of the rom.
m

Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.

kgalv419 said:
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
Click to expand...
Click to collapse
k,
okay, this ---> android.permission.INTERACT_ACROSS_USERS_FULL is the ballbuster.
it's connected to , from what i've read so far , a maybe faulty root and multiuser.
what version supersu are you using ? unroot and then reroot trying from version 1.97 maybe to 1.99.
kill multiuser and clear out any suspect accounts in settings. will post back if i find something more conclusive.
you can jump in as well by searching the error i mentioned.
android.permission.INTERACT_ACROSS_USERS_FULL
m
@kgalv419
edit after rooting set actions to auto grant permission and trust system
EDIT - disable xposed modules - xprivacy if you're running it.
QUESTION - THIS IS A JELLYBEAN ROM ? seems to be a jellybean issue...
EDIT-EDIT i found this... http://forum.xda-developers.com/gal...card-app-data-to-extsdcard-tw-t2178863/page16
read that page looking specifically at the portion concerning /system/etc/permissions/platform.xml
you may need to add/edit the line for
android.permission.INTERACT_ACROSS_USERS_FULL
with the proper uid [user identification] meaning the right number/symbol for root,shell,ewok, etc.
the entry looks something like this;
<assign-permission name="android.permission.INTERACT_ACROSS_USERS_FULL" uid="shell" />
and remember to reset the file's permissions correctly - 644

Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.

kgalv419 said:
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
Click to expand...
Click to collapse
In a situation like this thinking is guessing = no good.
re-read previous post. search, test, verify. Don't guess [think].
m

Yes bro trust me I'm trying

Are you able to flash CWM and root your device ?
I will advise what is next to be done....
Sent from my SM-T211 using XDA Free mobile app

Yes I already have it rooted with philz touch recovery

Wipe format every single partition that you see remove 1st your ext sd card this will empty all folders then redo tne Odin part
Sent from my SM-T211 using XDA Free mobile app

By every single partition you mean including those folders like acc, and others in the device?

Working zip of Chinese stock rom for 6045I

First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system & efs as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : removed due to some problems occurred after flashing.
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
Caution : Does not works on 6045Y & 6045K.
Backup efs also in case u loose ur IMEI or having error of unknown baseband/ no network
If you like my work, dont forget to hit thanks......
Sorry for all the trouble caused.
Well I am also in the same boat as well.....

yash_rathore25 said:
First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : https://mega.nz/#!88t2jJjT!dFpCY6987LAyAO2CcuKr0wmi5EPB3kRu9v8YTrNBgHs
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
May also work on 6045Y and 6045K : just need some willing hands.
If you like my work, dont forget to hit thanks......
Click to expand...
Click to collapse
Woohoo. Gonna download this!!!

For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......

Quick question. Can this rom read/write ExFat? I'd rather have my sd card formatted to that so that i can store larger movie files.

Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:

brian117 said:
Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:
Click to expand...
Click to collapse
One enhancement I read about was that it did have newer camera software. Many of the packages included are newer version levels than the ones included on our phones because the i806 came out after our models.
---------- Post added at 08:58 PM ---------- Previous post was at 08:45 PM ----------
yash_rathore25 said:
For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......
Click to expand...
Click to collapse
You should consider removing the system update checker from your custom rom. The icon appears in your screenshots so I'm assuming it's still included. Since the build.prop says it's a 6045i but it has the i806 codebase patches will never apply since the checksum's won't match.....so depending on what "version" it thinks it's on vs the update version the update checker will either never show an update or always show an update.

OK. I think I have this working. The ROM seems to be functional for me. Downloading all my apps now and getting it set up how I like. Will try to run it through the day tomorrow and see what I like and don't like... not expecting much difference over stock, but we'll see.

Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.

famewolf said:
Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.
Click to expand...
Click to collapse
I might still have a PA micro gapps file somewhere. Just need to see if it's 5.0 or 5.1.
Edit: Here you go. Just pick up the zero gapps. It works perfectly.
http://forum.xda-developers.com/showthread.php?t=2792842
Another option is the Slimgapps official thread here. They do have a "zero gapps" package, and both 5.x I think.
Sent from my 6045Y using XDA Free mobile app

yash_rathore25 said:
May also work on 6045Y and 6045K : just need some willing hands.
Click to expand...
Click to collapse
You mean testers?
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
You mean testers?
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
Yupp bro.
Just edit build.prop with notepad++ and change it to 6045Y instead of 6045I and flash the rom.
Then check the log of TWRP specially before the error in executing updater binary.
It will say something about the check_cu.
If you will open updater script with notepad++ you will see first line of command saying "check_cu("6045I-2AALUS7");"
Just change this line ("6045I-2AALUS7") with the line shown in the TWRP similar to this ( something like 6045Y-XXXXXXX)
Then again flash the rom, gapps and hope it will work.
If it works, dont forget to hit thanks button :laugh:

Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
I rooted my phone the next day it came to me,
Eventually i am also not going to get warranty as I imported this device from US to India.
N I personally dont care about warranty as none of the android device gets bricked completely, there is always a way.
Like I got stucked in bootloops in try of porting cm12.1 from other device.Even my backups failed to boot. Then I followed the mobile updater app provided by Alcatel and it simply restored my device to factory rom which will get updates also.
N warranty will not work if the device got physically damaged.
Yes backup will work.
After flashing this rom I would suggest you to make TWRP backup of this rom also alongwith Stock one.
I am getting a lot of range in network selection as it contains all the radios available for this device.
Screenshots of network range:

Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.

famewolf said:
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.
Click to expand...
Click to collapse
I agree with you bro......:good::good:

Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app

Anghirrim said:
Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion no risk of losing imei no. and radio modems

yash_rathore25 said:
In my opinion no risk of losing imei no. and radio modems
Click to expand...
Click to collapse
I'm attaching a platform.xml file already modded to allow full read/write access to the external sd (just drop the .zip off the filename as that was just to get xda to allow me to upload it...it's a text file)....you might find it useful to replace this in yours.(/etc/permissions)..other options include pre-rooting...adding in init.d support....etc.

Ran this ROM overnight and through most of my day so far (about 3 hours off the charger). First impression is that it's about the same as stock, not that I was expecting any different. You get the TCL splash screen at boot but the overall UI is pretty much the same. Since I now have root I went ahead and used app quarantine to freeze the bloatware apps I didn't want. Kinda wishing I had installed minimal gapps, but I figure I'll be reflashing again soon since the floodgates are probably about to open with new ROMS anyway.
Conclusion: If you're curious, flash it, it doesn't hurt anything. It may be a hair smoother, and I haven't really tested the camera extensively enough before or after to be able to tell a difference.
Edit: Literally as soon as I submitted this message (from my PC) I went to turn wi-fi off and the phone decided to reboot. Really odd.

@nickalltogether:
Which version of the phone do you have?
Sent from my 6045Y using XDA Free mobile app

[GUIDE] How to correct a wrong shown build number from settings menu

Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
 @BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.​
Be aware, and backup before doing this or everything you're dubious about.
Cheers

nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.

shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.

nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15

sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.

RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:

I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?

BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)

RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.

BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.

RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.

BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?

RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.

BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this

@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited

RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them

RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help

shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)

RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:

shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order

Internet Issue only on some apps - XT1789-05

Hi Everyone, thanks for helping me,
I have XT1789-05, Some apps can't access internet and some apps can access internet, with WiFi or Mobile Data, nothing change, in another device the apps not working in My Moto Z2 Force, will work fine, even I have Moto X 1st, all apps work fine in the Moto X, but in the Moto Z2, some apps when opened error can't access the internet, I searched and googled everywhere, I can't find a solution, can you help me please?
I already did a clear cache, clear data, uninstall and install again, only some apps has this issue, it's a completely strange problem, for example, this app not work as well: Ziraat Mobile (This app for Ziraat Bank in Turkey) here is the Google Play download link: play.google.com/store/apps/details?id=com.ziraat.ziraatmobil
I can't add URL, adding by yourself, please
another app: Radio Javan
play.google.com/store/apps/details?id=com.radiojavan.androidradio
please help me to solve this issue
one time I uninstalled Antivirus (Eset Mobile Security) as well, or any apps I thought to cause the problem, still I have the problem, I'm completely confused, please help me, I have one XT1789-02 and it's working fine with same apps, but my Phone XT1789-05 has problems!!!!!!!!
The Best Paul and Joseph Galvin (I Will Love Motorola Ever...)

Hi,
Did it work well before?
Did you do a full fw flashing before?
Have you tried to change the radio in *#*#4636#*#* yet?

mr_5kool said:
Hi,
Did it work well before?
Did you do a full fw flashing before?
Have you tried to change the radio in *#*#4636#*#* yet?
Click to expand...
Click to collapse
It's a new Phone
No Full Flashing before or even now
I tried to change Radio, thanks for your trick, but it does not work!!!!
I still need your help

It's a weird problem. I think you should do a full fw flashing if you bought a 2nd phone. If it's a brand new one, I have no idea about this situation :"|

mr_5kool said:
It's a weird problem. I think you should do a full fw flashing if you bought a 2nd phone. If it's a brand new one, I have no idea about this situation :"|
Click to expand...
Click to collapse
I have no Idea too, I'm going to crazy,

Have you tried a factory reset and use a different Google account? It could be restoring a setting or app causing it

Uzephi said:
Have you tried a factory reset and use a different Google account? It could be restoring a setting or app causing it
Click to expand...
Click to collapse
I used new account no restore anything, I don't want to reset factory because, I have Internet Bank with a digital sign, and I'm abroad, can't go to the bank, so reset factory not a good option
thanks a lot, give me another solution please

AHMN48 said:
I used new account no restore anything, I don't want to reset factory because, I have Internet Bank with a digital sign, and I'm abroad, can't go to the bank, so reset factory not a good option
thanks a lot, give me another solution please
Click to expand...
Click to collapse
I can't help further unless you cooperate to troubleshoot. When you are able to factory reset to nuke any stuck bits and start fresh on a new Google account, (not a secondary one you already have, a brand new one) then we can try pulling a log from a fresh install to see what is blocking it.
Edit: the factory reset would need to be followed up with a fastboot -w command to ensure everything is wiped. If you don't want to do this, then you cannot be helped.

Uzephi said:
I can't help further unless you cooperate to troubleshoot. When you are able to factory reset to nuke any stuck bits and start fresh on a new Google account, (not a secondary one you already have, a brand new one) then we can try pulling a log from a fresh install to see what is blocking it.
Edit: the factory reset would need to be followed up with a fastboot -w command to ensure everything is wiped. If you don't want to do this, then you cannot be helped.
Click to expand...
Click to collapse
so what next?
I did several times reset factory
one time from Setting
and two times from Recovery Mode
Still has the problem on some apps, ohhhh my god, I'm driving crazy!!!!!
I don't know what's the problem, some apps force close, some apps can't access the internet and most apps work fine
help me, please

is it grey import?
AHMN48 said:
so what next?
I did several times reset factory
one time from Setting
and two times from Recovery Mode
Still has the problem on some apps, ohhhh my god, I'm driving crazy!!!!!
I don't know what's the problem, some apps force close, some apps can't access the internet and most apps work fine
help me, please
Click to expand...
Click to collapse
Did you buy it online?
Besides the model, what is your software channel and build number for your phone?
i had similar problem and factory reset still resulted with the same issue. I had to do a full retail rom reinstallation and that fixed the problem.

harkoliar said:
Did you buy it online?
Besides the model, what is your software channel and build number for your phone?
i had similar problem and factory reset still resulted with the same issue. I had to do a full retail rom reinstallation and that fixed the problem.
Click to expand...
Click to collapse
Yes, I bought it online from coolicool.com, this is first time ever I bought one Moto from outside of USA,
Software Channel: retcn
Build Number: OPXS27.109-52-10
Thanks for helping me

The model and build is exactly like mine when I first got it.
First off, I think it's how they flashed the rom that's causing the instability. Your phone would most likely have it's bootloader unlocked like mine but they did something to hide the warning message.
Please read my thread.
https://forum.xda-developers.com/z2-force/help/request-advice-experts-tourbleshooting-t3928349
You will see that I flashed a retail rom using instructions from this thread. It would be step E of the thread. Worked like a charm for me in fixing all the unstable apps
https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
You will have to flash your phone so you really have to follow the step by
step instructions.
I did it for the first time in my thread, it's not hard to do step E if you follow it step by step.

Hah, mine was from coolicool with random issues too. Emailed them, no response. Paypal claim, no respond. Full refund!
Will follow the guide above.

Just check first if bootloader is unlocked. (That's step a). Before you proceed to step E.
I'm assuming it's already unlocked because we have the same issues, build and model number. Mine was unlocked when I received mine. Also from China/hk

harkoliar said:
Just check first if bootloader is unlocked. (That's step a). Before you proceed to step E.
I'm assuming it's already unlocked because we have the same issues, build and model number. Mine was unlocked when I received mine. Also from China/hk
Click to expand...
Click to collapse
why it's unlocked?
it's not Original and it's not from Motorola?
I saw in bootloader it's flashing_unlocked and I was surprised why unlocked????
are you sure if I do these steps problem will solve and also are you sure after installing new stock ROM dual sim work well?

AHMN48 said:
why it's unlocked?
it's not Original and it's not from Motorola?
I saw in bootloader it's flashing_unlocked and I was surprised why unlocked????
are you sure if I do these steps problem will solve and also are you sure after installing new stock ROM dual sim work well?
Click to expand...
Click to collapse
This is my pure speculation. the reason why its unlocked is because it was originally a chinese phone with chinese roms that doesnt have playstore. That must have been the original setting. Since they want to sell it to the international market, they had to unlock the phone and voiding the warranty, flash it with the new international rom before selling it.
Since its unlocked, essentially the warranty on your phone is void. The issue i found is that they must have flashed the wrong rom so its causing all these apps to crash.
Again thats all speculation and theory.
Now the only reason why I'm suggesting this method with you is because I had the same issue, I researched and tried the solution I posted. It worked for me. If you are going to flash a stock rom for the first time, you just do your research and do it one step at a time. Instructions have been provided in the second link (step E) including all the files you require to install the retail rom. It worked for me. I can only suggest, but it's up for you to give it a go.

I loaded the latest RETAIL (-05) factory image and all apps are functioning fine now. Issue was supplier had flashed -06 ROM, assuming because it said APAC in the description.

happy it worked
ben0551 said:
I loaded the latest RETAIL (-05) factory image and all apps are functioning fine now. Issue was supplier had flashed -06 ROM, assuming because it said APAC in the description.
Click to expand...
Click to collapse
glad it worked!

harkoliar said:
glad it worked!
Click to expand...
Click to collapse
I was so confused during the last month. The random apps that were impacted by the issue didn't make sense...
Banking app
ABC Kids Listen App
Kids Daycare App
FuelCheck
Images on CyberFlix
Only one of the devs managed to get their app working for me in the odd state it was in. DayCare app of all things!
Thanks for posting, I wouldn't have thought to reflash or even look at the region code of the flashed rom compared to the compatible one.

ben0551 said:
I was so confused during the last month. The random apps that were impacted by the issue didn't make sense...
Banking app
ABC Kids Listen App
Kids Daycare App
FuelCheck
Images on CyberFlix
Only one of the devs managed to get their app working for me in the odd state it was in. DayCare app of all things!
Thanks for posting, I wouldn't have thought to reflash or even look at the region code of the flashed rom compared to the compatible one.
Click to expand...
Click to collapse
Yeah it was so random, i really thought i got a faulty phone. Mine was all GPS/ internet related (Uber, Spotify, maps)
Nothing made sense but I took the research and decided to flash to stock rom, discovering they installed the wrong ROM and HIDING the fact the bootloader was unlocked. Definitely not your average issue and hopefully this would help other people who are in similar situation buying from any china/hk store.
I even bought the moto mods, and they are working perfectly after reflashing. Pretty happy with overall result.