Missing some apps in android market * HELP PLZ * - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hi
After flashing a new ROM. I missing many apps like "Opera", "YouTube" And much more.. Only some apps appears in my market.
I've re-flash the ROM but did fixed. I did many things like clear market cache. Rebooting and... But no way
Any idea please?
[Fixed]
Steps:
* Do a Reset Factory for the device.
* Connect to Wi-Fi (DO NOT ADD YOUR GOOGLE ACCOUNT).
* Enable: Settings -> Unknown source
* Run "Samsung Apps" & update it.
* Download some app from "Samsung Apps".
* Go to "Market" then add your account.
* Enjoy.

Any idea?
Sent from my GT-I9000 using XDA App

This is a know issue with all 3rd party ROMs. You will not get the full list of apps in the market if you use ROMs other than stock from Samsung. It is not the fault of the market it is the fault of the ROM.
This is just one issue of many which devs refuse to warn people about in their threads.

ArtificialSweetener said:
This is a know issue with all 3rd party ROMs. You will not get the full list of apps in the market if you use ROMs other than stock from Samsung. It is not the fault of the market it is the fault of the ROM.
This is just one issue of many which devs refuse to warn people about in their threads.
Click to expand...
Click to collapse
this is speculatory.
web.designer.iq,
check your build.prop signature id. this is what the market uses to identify your device. inquire with the rom developer to see if it has been modified. compare build.prop from your stock rom against your current custom rom's build.prop.

pershoot said:
this is speculatory.
web.designer.iq,
check your build.prop signature id. this is what the market uses to identify your device. inquire with the rom developer to see if it has been modified. compare build.prop from your stock rom against your current custom rom's build.prop.
Click to expand...
Click to collapse
This is not speculatory. Its because the ROMs are changed with different IDs other than original from Samsung. This causes the problem in the market as real developers have no knowledge of these hacked devices hence their apps do not show up to these user.
Such was the case with VMware View in the market. Users with hacked ROMs installed were bombarding VMware stating that their app was not showing up. The Devs over at VMware confirmed that the Tab 10.1 was in the list of compatible devices and they had no issues with any of the units they had in their office. Little did VMware know all the users posting about it in their forum were running ROMs from this website as it was later found.
This is just another reason I am against 3rd party ROMs. They dont work correctly, cause confusion, and generally just wastes everyone time due to incompatibilities and instability. The worst thing about these kind of situations is that the real Devs that make apps for the market get confused and have to waste time deal with these users.

ArtificialSweetener said:
This is not speculatory. Its because the ROMs are changed with different IDs other than original from Samsung. This causes the problem in the market as real developers have no knowledge of these hacked devices hence their apps do not show up to these user.
Such was the case with VMware View in the market. Users with hacked ROMs installed were bombarding VMware stating that their app was not showing up. The Devs over at VMware confirmed that the Tab 10.1 was in the list of compatible devices and they had no issues with any of the units they had in their office. Little did VMware know all the users posting about it in their forum were running ROMs from this website as it was later found.
This is just another reason I am against 3rd party ROMs. They dont work correctly, cause confusion, and generally just wastes everyone time due to incompatibilities and instability. The worst thing about these kind of situations is that the real Devs that make apps for the market get confused and have to waste time deal with these users.
Click to expand...
Click to collapse
So what are you here for then?
Synergy Sensation!

Because he can't use his other two screen names. He gets banned like once a week.
Sent from xda premium app

Stardate Tab 10.1 said:
Because he can't use his other two screen names. He gets banned like once a week.
Sent from xda premium app
Click to expand...
Click to collapse
Dont they ban the IP Address and not just the SN?
Synergy Sensation!

ArtificialSweetener said:
This is not speculatory. Its because the ROMs are changed with different IDs other than original from Samsung. This causes the problem in the market as real developers have no knowledge of these hacked devices hence their apps do not show up to these user.
Such was the case with VMware View in the market. Users with hacked ROMs installed were bombarding VMware stating that their app was not showing up. The Devs over at VMware confirmed that the Tab 10.1 was in the list of compatible devices and they had no issues with any of the units they had in their office. Little did VMware know all the users posting about it in their forum were running ROMs from this website as it was later found.
This is just another reason I am against 3rd party ROMs. They dont work correctly, cause confusion, and generally just wastes everyone time due to incompatibilities and instability. The worst thing about these kind of situations is that the real Devs that make apps for the market get confused and have to waste time deal with these users.
Click to expand...
Click to collapse
You can be against whatever you want. It causes confusion and wastes a considerable amount of forum bandwith, when users take seriously the opinion of evangelists (such as yourself) who are not qualified in this regard to give subjective advice to the populous.

Thanks for all
* I did not installed a custom ROM. I just installed a custom Kernel.
* The market was working perfectly with me. Without any issues. Until i re flashed the ROM to the Samsung Stock Europe ROM.
* I use the Original ROM Provided from Samsung for Europe OR Middle East. By Build No is:: HMJ37.XXKFC P7510XXKFC
* There's very stranger problem. So, When i search for opera the folowing page appears to me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just find a solution please. don't worry about app. I have purcheased many root tools like: Titanium Bakcup, ROM Manager (Premium), Root Explorer and much more. So, I just need a solution how to fix it or i will donate my GT 10.1 to Africa.
Thanks

This is my build.prop file:
* I have also attached a screen capture of my About Tablet.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HMJ37
ro.build.display.id=HMJ37.XXKFC
ro.build.version.incremental=XXKFC
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Thu Jun 23 21:13:45 KST 2011
ro.build.date.utc=1308831225
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-07
ro.build.tags=release-keys
ro.product.model=GT-P7510
ro.product.brand=samsung
ro.product.name=GT-P7510
ro.product.device=GT-P7510
ro.product.board=GT-P7510
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-P7510
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-P7510-user 3.1 HMJ37 XXKFC release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.1/HMJ37/XXKFC:user/release-keys
ro.build.characteristics=tablet,nosdcard
# Samsung Specific Properties
ro.build.PDA=P7510XXKFC
ro.build.hidden_ver=P7510XXKFC
ro.build.changelist=317542
ro.build.buildtag=jenkins-HUDSON_GA_HONEYCOMB_P4-WIFI-TW_MERGE-369
# end build properties
#
# system.prop for P3
#
ro.opengles.version = 131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttys0
keyguard.no_require_sim=yes
# Samsung Tvout Service
ro.sectvout.enable=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=S_Minimal_tone.ogg
ro.config.notification_sound=S_On_time.ogg
ro.config.alarm_alert=Good_Morning.ogg
dev.sfbootcomplete=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=288m
ro.secdevenc=true
ro.carrier=wifi-only
drm.service.enabled=true
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.enterprise_mode=1
ro.com.google.gmsversion=3.1_pre-r1
ro.error.receiver.system.apps=com.google.android.feedback
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-samsung
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Up...
Up...

Related

[Q] Samsung I9300 random Network not registred

Hi,I have a problem with my sgs3, it's working for 5-10 minutes only, after, I cannot make/receive calls/sms,everything else work.
But get connected to 3G/H+ with no problem, and stay connected.
After 5-10 minutes , if i try to make a call or send sms i get "not registred" ,but the 3g/h+ icon is there, and I can navigate in internet through my carrier connection.
I searched every post but didn't find something similar.
It's very strange that a 3G/H+ connection can work and gsm calls/sms not, I don't think it can be a carrier side issue.
SGS3 Int (i9300 exynos)
(wiped)
stock 4.1.2(I9300XXEMC2_ITVEMC1_Italy, tried also other, with the same success )
recovery ->cwm latest
rooted cf autoroot
efs ok
sn ok
imei ok
I tried different modems,different firmwares,same thing.
I really apreciate if someone will share some similar experience so I can get the right direction.Thanks!
try this
http://forum.xda-developers.com/showthread.php?t=1918601
First contact your network operator, probably just a bad SIM card.
Bad SIM Card or Network coverage.
First, try to change you uSIM card.
If it doesn't change the problem, try to change the Modem (some Modem have better performance with some network provider).
Finaly, change your provider.
boomboomer said:
First contact your network operator, probably just a bad SIM card.
Click to expand...
Click to collapse
lelinuxien52 said:
Bad SIM Card or Network coverage.
First, try to change you uSIM card.
If it doesn't change the problem, try to change the Modem (some Modem have better performance with some network provider).
Finaly, change your provider.
Click to expand...
Click to collapse
I call network operator:No problem they said...
I got a new microsim from same operator .same problem, I can make some calls for a while may be for 5 minutes or may be for an hour, the last night had no problem at all , this morning after some calls I get the same message...
the last one is like lelinuxien52 said is to change operator, but it's really strange because I had no problem with the same simcard on my sensation for 1 year...
rednit said:
try this
http://forum.xda-developers.com/showthread.php?t=1918601
Click to expand...
Click to collapse
I have allready tried the ariza patch, I thought that ariza patch have some bug, but wiped ,reflashed original I9300XXEMC2 and also tried different modems :XXEMB5,DXELK1.with the ril match.so... I really don't know what can be....
The only way to get it work is go offline/online, or if doesn't work restart, and I can make/receive some calls...
if I try to manualy connect to my network I get Q message if I want to disconect data service and list available networks(is connected to 3g/h, asks if I want to disconnect),and after another message could not connect to network.Try later...
"Logic"if it ask to disconect, means is connected ,
if I get network not registred when I try to call ...
It means some modem problem, tried other modems,the same ...,may be operator error but i had no problem for 1 year with the same sim with my sensation...
conclusion my logic is.....?Or?..
ps. thanks all for replies!
Try to borrow a SIM from another network, if still the same problem then you may have to return to service centre for warranty repair. You seem to have eliminated all the easy solutions.
boomboomer said:
Try to borrow a SIM from another network, if still the same problem then you may have to return to service centre for warranty repair. You seem to have eliminated all the easy solutions.
Click to expand...
Click to collapse
I don't think I have a valid waranty, I bought s3 from a private and hi had a unreadable payticket,he forgot it in the car and the sun made it allmost all black...so...
nstnkt said:
I don't think I have a valid waranty, I bought s3 from a private and hi had a unreadable payticket,he forgot it in the car and the sun made it allmost all black...so...
Click to expand...
Click to collapse
I have tried other sim .same result.
Can be other software problem ?other than modem/ril?
I opened the phone clean all antenna contacts, inspect antennas patch/joint, also cleaned...nothing.
Installed NoSignalAlert ( https://play.google.com/store/apps/details?id=com.smartandroidapps.missedcall&hl=en )
I have emergency-only event every minute or so...
I make some shots...
moments when everything is good and everyone is happy making a call to operator (155)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and how it's look when it'sad (note imei ,sn, and I don't get [Service state= out of service] and [mobile network state=connected])
nosignalallert
but,
if( I can navigate in internet even the device says: out of service, not registred, emergency call only ,end of the world...)
then(is not hardware issue)
else(use as (media player | digital Picture Frame | kids toy | professional samsung dust collector))
At night it'd a stable signal with no losing network, I made some change in efs if works i post them.
Today, you have news about your trouble ?
The problem can provide from bad tweaks in your /system/build.prop file.
lelinuxien52 said:
Today, you have news about your trouble ?
The problem can provide from bad tweaks in your /system/build.prop file.
Click to expand...
Click to collapse
It stay more time online looking at the log ,it losed connection every 3-4 hours...
about tweaks, it's fresh original flash
I also changed the right gsm/wcdma frequency bands for my carrier...
this is how it looks
build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.I9300XXEMC2
ro.build.version.incremental=I9300XXEMC2
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Mon Mar 11 17:37:01 KST 2013
ro.build.date.utc=1362991021
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-84
ro.build.tags=release-keys
ro.product.model=GT-I9300
ro.product.brand=samsung
ro.product.name=m0xx
ro.product.device=m0
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=m0
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=m0xx-user 4.1.2 JZO54K I9300XXEMC2 release-keys
ro.build.fingerprint=samsung/m0xx/m0:4.1.2/JZO54K/I9300XXEMC2:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=I9300XXEMC2
ro.build.hidden_ver=I9300XXEMC2
ro.build.changelist=1042335
# end build properties
#
# system.prop for smdk4x12
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=320
ro.lcd_min_brightness=20
ro.kernel.qemu=0
ro.tvout.enable=true
persist.sys.storage_preload=1
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=320
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.hdcp2.rx=tz
ro.secwvk=220
ro.sec.fle.encryption=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.com.google.gmsversion=4.1_r4
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
All in your build.prop file seam to be right.
How have you change gsm/wcdma frequency ? The problem can be here !
Have you try to enable only GSM mode for example (only EDGE data connection) ?
Maybe your problem is because your phone always switch between 2.5G and 3G antenna.
change frequency band
*#0011#>option>back>phone control>network control>band selection>gsm||wcdma>bands(850/900/1800......................)
there is other way to get in service mode I not remember the code
first was all automatic, after i changed to manul same thing can make some cals for a while...

How to Debloat MIUI 8.1.15.0? Remove all the Google Apps and MIUI Bloat?!

My Note 4 is running MIUI Global Stable 8.1.15.0 out of the box. There's an update to 8.2.2.0, but I've heard that there are some bugs in the update and decided not to update.
My phone has locked bootloader and is not rooted. I don't plan to either unlock the bootloader or root the phone. I use DNS 66 to block ads, so there's not really a reason for me to root my phone.
Anyway, the current MIUI ROM is full of bloatware - including Google Apps like Google Search, Play Movies, Play Music, Duo etc - and other MI crap. There seems to be no option to uninstall these apps. How does one go about getting rid of this crap?
Scarambay said:
My Note 4 is running MIUI Global Stable 8.1.15.0 out of the box. There's an update to 8.2.2.0, but I've heard that there are some bugs in the update and decided not to update.
My phone has locked bootloader and is not rooted. I don't plan to either unlock the bootloader or root the phone. I use DNS 66 to block ads, so there's not really a reason for me to root my phone.
Anyway, the current MIUI ROM is full of bloatware - including Google Apps like Google Search, Play Movies, Play Music, Duo etc - and other MI crap. There seems to be no option to uninstall these apps. How does one go about getting rid of this crap?
Click to expand...
Click to collapse
Google play --> Help and feedback --> Search delete or disable apps on android --> Click on tap to go to application settings --> Manage applications from there.
Credits to the person who first shared this. I wish I knew where I saw this so that he gets complete credits.
YanOri said:
Google play --> Help and feedback --> Search delete or disable apps on android --> Click on tap to go to application settings --> Manage applications from there.
Credits to the person who first shared this. I wish I knew where I saw this so that he gets complete credits.
Click to expand...
Click to collapse
Doesn't work anymore with the latest Google Play Services update, it opens in a browser instead which doesn't give you that option.
The best way is to get rooted and install Titanium Backup, it gives you the ability to totally remove any app (caution advised as some system apps are critical for the phone to work properly).
So which servics are critical and not advised to be deleted?
jazzh said:
So which servics are critical and not advised to be deleted?
Click to expand...
Click to collapse
This will help:
https://forum.xda-developers.com/redmi-note-3/how-to/redmi-note-3-pro-snapdragon-miui-t3372437
https://forum.xda-developers.com/redmi-note-3/how-to/miui-8-global-dev-bloater-recovery-t3465318
naturist said:
This will help:
https://forum.xda-developers.com/redmi-note-3/how-to/redmi-note-3-pro-snapdragon-miui-t3372437
https://forum.xda-developers.com/redmi-note-3/how-to/miui-8-global-dev-bloater-recovery-t3465318
Click to expand...
Click to collapse
Thank you!
Does it really work for Redmi 4X International Version? Is TWRP enough without root?
Rosetti said:
Thank you!
Does it really work for Redmi 4X International Version? Is TWRP enough without root?
Click to expand...
Click to collapse
I haven't tested in 4X but when I was using MIUI 8, I tested it on Redmi note 3. Now, I'm using RR with RN4 and Lineage on RN3. IMO no harm in trying? the worst could be you've to flash the MIUI rom again. Still you can wait for other comments if you like.
Unfortunately, it's impossible to fully debloat the newer MIUI ROM's.
I have clean xiaomi.eu ROM on my mi4a and I am sure it's independent of the device, I still have my phone making malware requests to chinese servers such as:
Code:
GET http://resolver.msg.xiaomi.net/gslb/?ver=4.0&type=wifi&uuid=nB2UGqmrANkf7xUv&list=app.chat.xiaomi.net%2Cresolver.msg.xiaomi.net&sdkver=27&osver=23&os=Redmi%204A%3AV8.5.4.0.MCCCNED&mi=3&key=adbf3934435aa7ba3609cc2b96d04999
RESPONSE:
{"S":"Ok","R":{"country":"","province":"","city":"","isp":"","X-Forwarded-Ip":"192.160.102.169","ip":"192.160.102.169","stat-domain":"s.mi1.cc","stat-percent":0.05,"ttl":3600,"tid":-1,"extra-for-pa":"debug info","force-use":"false","wifi":{"app.chat.xiaomi.net":["114.54.23.116:5222","120.92.96.2:5222","111.13.142.2:5222","LB-IM-12-2017274345.ap-southeast-1.elb.amazonaws.com:5222"],"resolver.msg.xiaomi.net":["LB-IM-11-1803639322.ap-southeast-1.elb.amazonaws.com:80"]},"wap":{"app.chat.xiaomi.net":["114.54.23.116:5222","120.92.96.2:5222","111.13.142.2:5222","LB-IM-12-2017274345.ap-southeast-1.elb.amazonaws.com:5222"],"resolver.msg.xiaomi.net":["LB-IM-11-1803639322.ap-southeast-1.elb.amazonaws.com:80"]}}}
and persistent XMPP/HTTPS connections to these domains/IPs:
Code:
api.sec.miui.com
app.chat.xiaomi.net
resolver.msg.xiaomi.net
auth.be.sec.miui.com
data.mistat.xiaomi.com
sdkconfig.ad.intl.xiaomi.com
...
114.54.23.116
111.13.142.2
120.92.96.2
42.62.94.2
111.206.200.2
111.13.142.2
114.54.23.2
42.62.94.2
...
These addresses are hardcoded into all system MIUI .apk's and replacing them in a HEX-editor will result the phone into looping a such error on system boot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thus, today I decided to stop using MIUI ROMs forever.
You could add something like this to your /system/etc/hosts file, which should block all those requests:
Code:
0.0.0.0 account.xiaomi.com
0.0.0.0 api.sec.miui.com
0.0.0.0 app.chat.xiaomi.net
0.0.0.0 auth.be.sec.miui.com
0.0.0.0 contactapi.micloud.xiaomi.net
0.0.0.0 data.mistat.xiaomi.com
0.0.0.0 micloud.xiaomi.net
0.0.0.0 pdc.micloud.xiaomi.net
0.0.0.0 resolver.msg.xiaomi.net
0.0.0.0 sdkconfig.ad.intl.xiaomi.com
0.0.0.0 wifiapi.micloud.xiaomi.net
0.0.0.0 xiaomi.com
0.0.0.0 xiaomi.net
DarthJabba9 said:
You could add something like this to your /system/etc/hosts file, which should block all those requests:
Code:
0.0.0.0 account.xiaomi.com
0.0.0.0 api.sec.miui.com
0.0.0.0 app.chat.xiaomi.net
0.0.0.0 auth.be.sec.miui.com
0.0.0.0 contactapi.micloud.xiaomi.net
0.0.0.0 data.mistat.xiaomi.com
0.0.0.0 micloud.xiaomi.net
0.0.0.0 pdc.micloud.xiaomi.net
0.0.0.0 resolver.msg.xiaomi.net
0.0.0.0 sdkconfig.ad.intl.xiaomi.com
0.0.0.0 wifiapi.micloud.xiaomi.net
0.0.0.0 xiaomi.com
0.0.0.0 xiaomi.net
Click to expand...
Click to collapse
Thank you, but it sounds more like a temporary solution for me, which doesn't fix the problem at its roots.
I could have blocked requests by rewriting hosts, but there is always a human factor present, which can make me forget about /etc/hosts file while I mess with system in a way that may affect this file by removing/replacing/modifying it (hypothetically).
Moreover, I have tried that method before and it doesn't work without modifying/creating some iptables rules and making them persistent at the boot time by creating some sh boot scripts, as default iptables xiaomi rules prevent the device from using /etc/hosts records whose objective is breaking MIUI telemetry functionality (at least on newer MIUI's).
Also, living by accepting the fact I have some spyware on my phone is not the best solution, at least for me.
Luckily, there is an official AOSP Extended build for my device, which is being maintained, thanks to Carlos Arriaga.
polartux said:
... Moreover, I have tried that method before and it doesn't work without modifying/creating some iptables rules and making them persistent at the boot time by creating some sh boot scripts, as default iptables xiaomi rules prevent the device from using /etc/hosts records whose objective is breaking MIUI telemetry functionality (at least on newer MIUI's).
Also, living by accepting the fact I have some spyware on my phone is not the best solution, at least for me...
Click to expand...
Click to collapse
I hear you. That is why I abandoned MIUI too. Someone on this forum labelled me as "paranoid" for this, and my response was "each to his own".
DarthJabba9 said:
I hear you. That is why I abandoned MIUI too. Someone on this forum labelled me as "paranoid" for this, and my response was "each to his own".
Click to expand...
Click to collapse
Wow, probably the person called you so has nothing to hide.
I express deep respect to people who consider privacy and security seriously.
polartux said:
Wow, probably the person called you so has nothing to hide.
Click to expand...
Click to collapse
There are other interesting arguments (which I personally don't buy) that people make, including the argument that "everybody else is collecting your data anyway, so what's the problem"?
If I were a MIUI fan, I would probably also find some ways of convincing myself that things are not that bad - after all, I have to find a way of justifying to myself my continued use of it. At the end of the day, it still is a matter of "each to his own".
DarthJabba9 said:
[...] including the argument that "everybody else is collecting your data anyway, so what's the problem"?
Click to expand...
Click to collapse
Saw it several times as well, some people are just too lazy to find ways to secure their digital life and prefer to think that it's impossible by continuing using closed source software and hardware.
I don't count with their opinion, because people with such type of thinking are targets for big data corporations to make money on them.
We indeed have enough open technology instruments to prevent leakage of our data, so those who care will do.
I personally was a big fan of MIUI, but these circumstances forced me to stop using it. I don't need to convince myself to use it because it's privacy-unfriendly, for the same reason i don't use Apple and Microsoft production.
polartux said:
I personally was a big fan of MIUI, but these circumstances forced me to stop using it.
Click to expand...
Click to collapse
Ditto. It is all quite unfortunate. Somebody will eventually come up with a way to clean the system apks, and prevent the "dial home" stuff (some of it will involve cleaning up some stuff in the boot image) - but it seems to be getting almost impossible to really clean things up.

Shinjitsu Rom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For anyone that has followed my work in the past, you will be familiar with the rom name. It was a line of Roms i made for the ZTE Warp, Warp Sequent, Desire 510, and the Motorola Moto G in addition to Awesome Android, Cyanogenmod and AOKP builds.
I will be reintroducing the rom on the Alcatel Idol 4 Cricket Variant
ROM Features
Init.d support
Build.prop Tweaks
Various System Tweaks
Cpu Core Clock Control tweaks
Deodexed
Optimized
All Bloatware Removed
New Bootanimation
Code:
Changelog
To Do: Make more awesomeness!
Test Version 1
-Initial Beta Test
-Deodexed Rom
-Replaced Joy Launcher with Google Now Launcher
-Added Google Assistant
-Debloated
-Added Init.d Support
-Adjusted factory CPU core clockspeed
-Adjusted CPU Core hotplug
-Zipaligned
-Changed BootAnimation
-Adjusted Minfree values
-Adjusted Low Memory Killer Values
This Rom is for the Cricket 6055U
do not install on other variants!
You Have been warned!!
Once you have TWRP flashed to your device
Copy Shinjitsu_Rom_Beta_1.zip to Sdcard
(You May need an external sdcard for this)
Boot into TWRP and flash the zip
Bug report, bug report, bug report
If something isn't working report back and,
i will try to get it fixed in a timely manner
(Keep in mind i do have a full time job)
Code:
Removed APks
JrdFota.apk
Exchange.apk
Email.apk
Compass.apk
JrdUser2Root.apk
NewsWeather.apk
FileManager.apk
Browser.apk
Music.apk
TctSoundRecorder.apk
TctCalculator.apk
TctWeather.apk
Launcher.apk
WallpaperCropperOverlay.apk
VpnDialogs-overlay.apk
TctWeather-overlay.apk
TctSoundRecorder-overlay.apk
TctFMRadio-overlay.apk
TctFileManager-overlay.apk
TctEmail-overlay.apk
TctCamera-overlay.apk
Tag-overlay.apk
SystemUI-overlay.apk
SmartSuite-overlay.apk
Shel-overlay.apk
SettingProvider-overlay.apk
Settings-overlay.apk
Protips-overlay.apk
PrintSpooler-overlay.apk
PrimaryCardController-overlay.apk
PhotoTable-overlay.apk
PhaseBeam-overlay.apk
PartnerBookmarksProvider-overlay.apk
OTAProvisioningClient-overlay.apk
NoiseField-overlay.apk
NfcNci-overlay.apk
Music-overlay.apk
MusicFX-overlay.apk
Mms-overlay.apk
MediaProvider-overlay.apk
MaxxService-overlay.apk
MaxxAudio-overlay.apk
ManagedProvision-overlay.apk
MagicLock-overlay.apk
LiveWallpaperPicker-overlay.apk
LiveWallpapers-overlay.apk
Launcher-overlay.apk
KeyChanin-overlay.apk
JrdSsv-overlay.apk
JrdFota-overlay.apk
InputDevices-overlay.apk
HTMLViewer-overlay.apk
HoloSpiralWallpaper-overlay.apk
Gallery-overlay.apk
Galaxy4-overlay.apk
FusedLocation-overlay.apk
framework-res-overlay.apk
ExternalStorageProvider-overlay.apk
Elabel-overlay.apk
DrmProvider-overlay.apk
DownloadProviderUi-overlay.apk
DownloadProvider-overlay.apk
DocumanetsUI-overlay.apk
Dialer-overlay.apk
DefaultContainerService-overlay.apk
ContactsProvider-overlay.apk
Contacts-overlay.apk
Compass-overlay.apk
ChromeCustomizations-overlay.apk
CertInstaller-overlay.apk
CellBroadcastReceiver-overlay.apk
CaptivePortalLogin-overlay.apk
CalendarProvider-overlay.apk
Browser-overlay.apk
Bluetooth-overlay.apk
BluetoothExt-overlay.apk
BasicDreams-overlay.apk
BackupRestoreConfirmation-overlay.apk
ATTDMClient-overlay.apk
Code:
Debloated apks
Google Books
Cloud Print
Google Drive
Gmail
Hangouts
Play Music
News Stand
Play Games
Plus One
Talkback
Play Videos
YouTube
Proofs of CPU Core hot-plugging and Deep Sleep
Links are in the Download Section!
​
XDA:DevDB Information
Shinjitsu Rom, ROM for the Alcatel Idol 4S
Contributors
shinru2004
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Cricket 6055u
Based On: Stock
Version Information
Status: Beta
Current Beta Version: 3.31.18
Beta Release Date: 2018-03-30
Created 2018-04-01
Last Updated 2018-04-01
Perfect rom but camera recording does not work.
Fix please
Not seeing a link, would like to try it out
Thanks so much for this. Everything working smoothly minus the camera like stated above.
Ok, but i need install any zip of gapps ?
variant 6055b forgotten ???
Orionpax5000 said:
variant 6055b forgotten
Click to expand...
Click to collapse
6055k too
Will 6070k support be available in the future?
where do i download the zip from
Download the file from the OPs other thread
i left in the wrong camera.apk i'll update the zip in a bit and that will fix it.
Updated the Camera.apk everything should work now. New zip can be found in the downloads section
Hi, I installed the rom cause´I thought that I would have the sim unlock off, I had a trouble, My phone was working perfect yesterday and I wanted to get root acces, I followed the instructions using Sugar QCT and I got another android version that has SIM lock. Do you know how can I stop the simlock process or another method to be able to use my sim? I'm from El Salvador, Central America
@shinru2004, This rom wont install on my 2 Cricket phones, model 6055U. The error was this is for Cricket idol4, you have idol 4. When I looked at the updater-script, you have it set to look for 6055K. I changed that according to the info in my build.prop and it installs fine now. For anyone else running into this problem, here is a modified updater-script so this will install on a 6055U Cricket model, for which this rom was made. Nice rom and I thank you much for the time and effort in releasing this.
Modified updater-script https://drive.google.com/open?id=1-DnIa7C3RuzqN80-7kv9-sRIRqRPy-th
To anyone wondering if this will work on any other model idol 4, i'll say this for sure. Any model idol 4 that can swap stock rom with the 6055U and works will work on this rom. Just edit the updater-script or let me know and i'll post a modified updater-script for you. to get this working, simply open the rom with winrar, navigate to where updater-script is and overwrite the original with my modified one and you should be good. Rom looks like a breath of fresh air compared to the stock and will tide me over until @Unjustified Dev releases Lineage OS.
LTE doesnt appear to be working? Checked the APN settings and they are the same as my stock. All my fiances phone is getting is 4G. Other than that, the rom runs great so far.
Compatibility
Is it compatibgle with 6055P?
PizzaG said:
@shinru2004, This rom wont install on my 2 Cricket phones, model 6055U. The error was this is for Cricket idol4, you have idol 4. When I looked at the updater-script, you have it set to look for 6055K. I changed that according to the info in my build.prop and it installs fine now. For anyone else running into this problem, here is a modified updater-script so this will install on a 6055U Cricket model, for which this rom was made. Nice rom and I thank you much for the time and effort in releasing this.
Modified updater-script https://drive.google.com/open?id=1-DnIa7C3RuzqN80-7kv9-sRIRqRPy-th
To anyone wondering if this will work on any other model idol 4, i'll say this for sure. Any model idol 4 that can swap stock rom with the 6055U and works will work on this rom. Just edit the updater-script or let me know and i'll post a modified updater-script for you. to get this working, simply open the rom with winrar, navigate to where updater-script is and overwrite the original with my modified one and you should be good. Rom looks like a breath of fresh air compared to the stock and will tide me over until @Unjustified Dev releases Lineage OS.
Click to expand...
Click to collapse
Here is my build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=~CricketRom~ Beta4
ro.build.version.incremental=~CricketRom~ Beta4
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-07-01
ro.build.version.base_os=
ro.build.date=2018年 05月 25日 星期五 11:05:08 CST
ro.build.date.utc=1496977508
ro.build.type=userdebug
ro.build.user=PizzaG
ro.build.host=aclgcl-ubnt171
ro.build.tags=release-keys
ro.build.flavor=idol452_voltecricket-userdebug
ro.product.model=Alcatel 6055U
ro.product.brand=TCL
ro.product.name=Alcatel_6055U
ro.product.device=idol4
ro.product.board=msm8952
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=TCL
ro.wifi.channels=
ro.board.platform=msm8952
# ro.build.product is obsolete; use ro.product.device
ro.build.product=idol452_voltecricket
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=idol452_voltecricket-user 6.0.1 MMB29M vCCJ-0 release-keys
ro.build.fingerprint=TCL/Alcatel_6055U/idol4:6.0.1/MMB29M/vCCJ-0:user/release-keys
ro.build.characteristics=nosdcard
ro.tct.product=idol452_voltecricket
You can make one updater-script to me ?
you have my rom currently installed and trying to install Shinjitsu rom?
---------- Post added at 10:11 PM ---------- Previous post was at 10:04 PM ----------
oLdSchool991 said:
Here is my build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=~CricketRom~ Beta4
ro.build.version.incremental=~CricketRom~ Beta4
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-07-01
ro.build.version.base_os=
ro.build.date=2018年 05月 25日 星期五 11:05:08 CST
ro.build.date.utc=1496977508
ro.build.type=userdebug
ro.build.user=PizzaG
ro.build.host=aclgcl-ubnt171
ro.build.tags=release-keys
ro.build.flavor=idol452_voltecricket-userdebug
ro.product.model=Alcatel 6055U
ro.product.brand=TCL
ro.product.name=Alcatel_6055U
ro.product.device=idol4
ro.product.board=msm8952
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=TCL
ro.wifi.channels=
ro.board.platform=msm8952
# ro.build.product is obsolete; use ro.product.device
ro.build.product=idol452_voltecricket
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=idol452_voltecricket-user 6.0.1 MMB29M vCCJ-0 release-keys
ro.build.fingerprint=TCL/Alcatel_6055U/idol4:6.0.1/MMB29M/vCCJ-0:user/release-keys
ro.build.characteristics=nosdcard
ro.tct.product=idol452_voltecricket
You can make one updater-script to me ?
Click to expand...
Click to collapse
Updater Script based on your current build.prop so you can install Shinjitsu Rom
https://drive.google.com/open?id=1QH1AyqFpClQSQFUZrQhQYvY-feKrj33n
it's to try new roms, but your rom is incredible
oLdSchool991 said:
it's to try new roms, but your rom is incredible
Click to expand...
Click to collapse
Thank You, I appreciate that:good:
That updater script will only work for installing Shinjitsu Rom though, so be sure to read my instructions on how to put it into Shinjitsu Rom

EVR-AL00 root situation

Thanks to xda member @fatouraee the EVR-AL00 firmware has been posted here. I've taken the time to download and dissect it and found a few interesting tidbits.
For starters it appears to be a engineering or internal build
build.prop lists it as an August security patch, so it is old.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.001
ro.build.version.incremental=eng.root.20181019.195045
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.base_os=
config.disable_consumerir=true
ro.build.version.security_patch=2018-08-05
ro.build.version.min_supported_target_sdk=17
ro.build.date=Fri Oct 19 19:50:42 CST 2018
ro.build.date.utc=1539949842
ro.build.type=eng
ro.build.user=root
ro.build.host=sh0514826b41539948706875-7099393-jgmgb
ro.build.tags=test-keys
ro.build.system_root_image=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=unknown
ro.product.locale=en-US
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-eng 9 PPR1.180610.001 eng.root.20181019.195045 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:9/PPR1.180610.001/root10191950:eng/test-keys
ro.build.characteristics=default
# end build properties
#
# from device/emui/generic_a15/system.prop
#
persist.sys.cpuset.enable=1
persist.sys.cpuset.subswitch=16
persist.sys.iaware.cpuenable=true
persist.sys.fast_h_duration=2000
persist.sys.fast_h_max=50
persist.sys.max_rdh_delay=0
ro.config.enable_rcc=true
ro.config.hw_sensorhub=true
system_init.hwextdeviceservice=1
bastet.service.enable=true
dalvik.vm.boot-dex2oat-threads=4
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.control_privapp_permissions=log
ro.opa.eligible_device=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=9_201806
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
ro.kernel.android.checkjni=1
dalvik.vm.lockprof.threshold=0
dalvik.vm.image-dex2oat-filter=verify-at-runtime
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.expect.recovery_id=0xf227db076aec861e23fda4c530f3156b69ef8804000000000000000000000000
ro.build.display.id=System-FAC 9.0.0.062(00IE)
ro.comp.sys_support_vndk=
But, here's where things get interesting!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It appears to be rooted already. Of course, with no up to date software available, you will more than likely be stuck on this build until shipping/retail firmware becomes available. Someone should take one for the team and flash it.
Join our developer telegram group here for help flashing and testing out theories so that we may soon develop a method and guide to post on XDA regarding root and/or rebrand.
What did you use to extract the img files?
And we need to do a form or comparison of the two and see where the differences are for rebranding. and its possibility. Because rooting wouldnt be an issue to inject into a L29 rom before flashing, or at least i dont think
AngelDeath said:
What did you use to extract the img files?
And we need to do a form or comparison of the two and see where the differences are for rebranding. and its possibility. Because rooting wouldnt be an issue to inject into a L29 rom before flashing, or at least i dont think
Click to expand...
Click to collapse
i used a tool to convert to ext4 then simply browsed with 7zip
you could also probably mount it in linux with no problems.
freeza said:
i used a tool to convert to ext4 then simply browsed with 7zip
you could also probably mount it in linux with no problems.
Click to expand...
Click to collapse
Granted the August security patch. Would the ro.build of 10/19 perhaps say it's a newer build however just old patch?
antiochasylum said:
Granted the August security patch. Would the ro.build of 10/19 perhaps say it's a newer build however just old patch?
Click to expand...
Click to collapse
It's possible. But then again I would assume they were simply pushing builds out quick to iron out bugs, then once it was ready, simply updated it to the latest patch.
freeza said:
It's possible. But then again I would assume they were simply pushing builds out quick to iron out bugs, then once it was ready, simply updated it to the latest patch.
Click to expand...
Click to collapse
Thanks for the direction, last question, have you had trouble opening the update app from the L29 rom? I used the Huawei Update extractor, but if fails with a trustfirmware invalid header error, unchecking verify header checksum in settings let it extract, but then I cant extract the system.img file every app I use crashes, but yet I've had no issues with any of the other img files or from the AL00 rom.
AngelDeath said:
Thanks for the direction, last question, have you had trouble opening the update app from the L29 rom? I used the Huawei Update extractor, but if fails with a trustfirmware invalid header error, unchecking verify header checksum in settings let it extract, but then I cant extract the system.img file every app I use crashes, but yet I've had no issues with any of the other img files or from the AL00 rom.
Click to expand...
Click to collapse
You're probably going to have to mount it in Linux as root. I had to do that on previous Huawei devices . Then you can zip the system and save it.
On previous devices I've used HwOta8 along with the stock rom to roll back to over firmware. I'm not sure if that would still apply to Pie devices.
ajsmsg78 said:
You're probably going to have to mount it in Linux as root. I had to do that on previous Huawei devices . Then you can zip the system and save it.
On previous devices I've used HwOta8 along with the stock rom to roll back to over firmware. I'm not sure if that would still apply to Pie devices.
Click to expand...
Click to collapse
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
AngelDeath said:
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
Click to expand...
Click to collapse
All we need now is a working "TWRP"...
AngelDeath said:
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
Click to expand...
Click to collapse
Here's a link to download the L29 9.0.0.108 system/vendor/cust that I extracted:
https://www.androidfilehost.com/?w=files&flid=285746
And here is the AL00 System:
https://www.androidfilehost.com/?fid=11410963190603853598
ajsmsg78 said:
Here's a link to download the L29 9.0.0.108 system that I extracted:
https://www.androidfilehost.com/?fid=11410963190603853592
Click to expand...
Click to collapse
Thanks, any chance you can pull these two as well?
Cust.img
Vendor.img
AngelDeath said:
Thanks, any chance you can pull these two as well?
Cust.img
Vendor.img
Click to expand...
Click to collapse
Sure, give me a few and I'll add them to the last post. Ok good to go, updated the link.
I'll look at them tomorrow, but in the mean time if anyone is curious the hotword for ok google is located in product.img. One thing I saw unless I read it wrong, the recovery images are the same size in both so I'm going to guess the partiton table are going to be the same. And if anyone wants to disect the apk, its attached below
AngelDeath said:
I'll look at them tomorrow, but in the mean time if anyone is curious the hotword for ok google is located in product.img. One thing I saw unless I read it wrong, the recovery images are the same size in both so I'm going to guess the partiton table are going to be the same. And if anyone wants to disect the apk, its attached below
Click to expand...
Click to collapse
I would compare the files too forget how I did this-recall finding differences even when the size was the same on Samsung models (Latin America versus ROW models for one of their Tablet phones the T705 versus T705M)
edit must have been diff image but it was some offline (not online) checker-there were small differences in the BL and modem on those devices even though they appeared identical size-wise on those devices from what I recall (nevermind that there were actual hardware differences in the radio between those two unlike in the case of the L00 and L29-at least the bands and connectivity appear common)
mac231us said:
I would compare the files too forget how I did this-recall finding differences even when the size was the same on Samsung models (Latin America versus ROW models for one of their Tablet phones the T705 versus T705M)
edit must have been diff image but it was some offline (not online) checker-there were small differences in the BL and modem on those devices even though they appeared identical size-wise on those devices from what I recall (nevermind that there were actual hardware differences in the radio between those two unlike in the case of the L00 and L29-at least the bands and connectivity appear common)
Click to expand...
Click to collapse
I have two offline programs that compare, I'll see what I find and let you know.
AngelDeath said:
I have two offline programs that compare, I'll see what I find and let you know.
Click to expand...
Click to collapse
A quick look by two different apps (Getting an update to one of them for final comparison) shows that either both the Recovery_Vendor.img and Recovery_ramdisk.img are complete different based on comparison, or because one is a internal rooted rom (AL00) and the L29 isnt, could be why there is such a massive difference in coding. Basically the whole file is different in both, My whole screen is red except the last 3 hex lines. But checking to see if updating the app makes a difference (probably not).
I should be receiving my device hopefully sometime next week. Looking forward to seeing what's possible
freeza said:
I should be receiving my device hopefully sometime next week. Looking forward to seeing what's possible
Click to expand...
Click to collapse
Here is a comparison of the ramdisk.img. To me I think the large difference is one is internal testing, the other is released. But just looking at this, you can see from the legend on the left its all red meaning its completely different, but yet its exactly the same partition size, got to see the rest.
AngelDeath said:
Here is a comparison of the ramdisk.img. To me I think the large difference is one is internal testing, the other is released. But just looking at this, you can see from the legend on the left its all red meaning its completely different, but yet its exactly the same partition size, got to see the rest.
Click to expand...
Click to collapse
Just PMd you
fatouraee said:
Just PMd you
Click to expand...
Click to collapse
Got it

Bank apps (RSA?) crashes on Mediatek MT6795 with Android 5.1 / Gionee E8 | Allview X2

Hello, I need help...
Searched and read a lot of last days, can't figure anything about my problem.
Device:
* Allview X2 Xtreme (Aka BLU Pure XL, Gionee Elife E8, ...)
** Mediatek MT6795 a'ka Helio x10
** 3GB RAM, 64GB internal
* Android 5.1, stock V5894 with security patch: 2016-02-01 (yeah, that sucks), rooted, Kernel: 3.10.72+
* HW X2_Soul_Xtreme_Mainboard_P3.1
* Using Lucky Patcher, AdAway, Busybox... typical apps with root.
The problem; TL;DR
Many banking apps crashes or cannot connect with bank on my device. It's not related with bank, not related with my SIM cards or SDCard. Not even related with userdata or system/boot image on device.
Any other applications which I tried and using over years works fine.
Probably hardware problem, but I can't figure it out.
The problem, whole story
About month ago mBank app (Polish bank) just crashed for me after making payment. I couldn't log in into it after typing pin. I though it's Bank API problem and i just waited 2-3 days, without changes, so I finally I've opened complaint - still they not replied to me!!
Ofc meanwhile I've tried to reset and pair application with account - no luck, still doesn't work.
Strange was that I was able to log on wife's S9+. However I still though it's bank problem with my specified smartphone - maybe IMEI identification or something, made a uniqueness violations or something in their databases or other stupid ideas... I'm also developer, so I have some guesses in my head.
Ofc before crash I did not made any changes in OS, not installed any new app or made breaking changes in configs... typical use. App works over year, sun still shines...
I begin to search on my own:
I was unable to debug or find any logs for mBank app.
My holiday approximates so I was started to thinking about new bank... and then I've tried "Moje ING" (ING Nederlands bank in Poland).. without account there's "demo mode"... tap: "You're device might be rooted bla bla bla. continue". -- "Cannot download data, try again". Hmm... It doesn't work on my phone, strange, because on wife's works.. damn.
Yet another application: "IKO" (PKO Polish Bank app) and demo works well. Uff... quite soothing... but it's demo, w/ever. Maybe ING app is broken on roots (S9+ wife without root).
Another app: "Kantor walutowy Alior Bank" (Alior's Bank Exchange)... crash just on start, however on that app I was able to tap "send report", and then what I saw in stacktrace: "Runtime Exception: Not able to create key". Sh1et, that's bother me totally.
I've decompiled class with that thrown, not analyzed it to much, but package is related to RSA and KeyPairs generators.
I've finally installed only other OS available to my device: CM 13 on Android 6. On clean system "Moje ING" not even start and it crashes, same with Alior's Bank. I was unable to test mBank app, because on that cook audio not works... (Polish banks make's call on app pairing with account - I wont hear IVR). Maybe I'll try to switch SIM card to other device and try that...
Strange researches or needles:
* lot of logs files like:
Code:
[email protected]_Soul_Xtreme:/data/system/dropbox # [email protected]
-- encrypted base64 binary or something, not sure what's that, but looks like google service...
My custom build.props over stock
Code:
ro.config.media_vol_steps=35
debug.sf.nobootanimation=1
ro.ril.enable.amr.wideband=1
ro.config.vc_call_steps=9
ro.config.hw_quickpoweron=true
debug.performance.tuning=1
ro.HOME_APP_ADJ=1
What did I tried
* Wiping data, even internal storage, dalvik, cache partition. Formatting /data
* unrooting
* changing app permissions, reverting ad blocks
* I've compared clean /system image with that on my device with hope that some binary corrupted... nope
* also compared BOOT with clean stock, no diffs
* eject SIM cards, SD Card
* flashed clear stock V5894 system, recovery and boot
* flashed only one other OS for that device: CM13 Android 6
* installed current open gapps
* read logcat and other logs with no inspirations
* cleared protect_s and protect_f... dropped SIM card support, but doesn't change anything, rebooted
* tried some other bank apps, nothing new and strange, I think demo modes work on mocks -- will try other sometimes
* wiped data and system: aliors bank app starts on CM13, need to try pair it with account
* replaced bunch of keystore binary from other 5.1 roms, 2-3 of them somehow works, but without whole success
* commented keystore / mobicore services from boot img - crashes on lockscreen / security settings
* compared partitions expdb frp lk para proinfo seccfg secro tee1 tee2 does they changed last day, nope, they wasn't... however I'm not forget about them
* made an app that tries to generate keypair on loop without success, tried to debug android.security packages
* flashed tee1 partition from mobicore.bin E8_amigo3.1.1_T3035.zip , E8_amigo3.1.12_T3149.zip, V5403_66d0c1f4c2dfe8abab357b3d5e6550bb.zip, V5894_160707_gn_system_update_ota.zip, compared with my readback
* tried to Android encrypt, but it nothing happened after reboot - probably bcuz changed recovery / not diggin more about that
* ...?
Stacktrace's
Alior bank:
Code:
java.lang.RuntimeException: Not able to create key
at pl.alior.c.c.a.a.c.a.a(Unknown Source)
at pl.alior.c.c.a.a.a.a(Unknown Source)
at pl.alior.c.c.a.a.a$1.run(Unknown Source)
(if any one what to help I'll upload apk), screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moje ING
(crashed on CM13 if I good remember, probably other, not related problem, gonna try again)
Code:
java.lang.UnsatisfiedLinkError: com.guardsquare.dexguard.runtime.detection.RootDetector
at pl.ing.mojeing.utils.ja.b(SourceFile:2)
at pl.ing.mojeing.payment.hce.l.k(SourceFile:6)
at pl.ing.mojeing.utils.t.i(SourceFile:1)
...
Not tried, but I will:
- readback, change or do anything with preloaders RSA generation on what about I read here and I thing there might be some problem, but I can't find instructions how to do that / not enough experience right now. I've found that on tee1 and tee2 there's somekind "Crypto Driver, Build Feb 12 2015, 17:12:18 CR: t-base-Mediatek-MT6752-Android-302A-V006-39_39 "
- change IMEI, BT or WIFI MAC and any other identification numbers
- any ideas?
...
- finally I'll throw that brick**** f%$#ng mediatek furnace and buy something good.
Ok, I'm sure whats broken, but currently don't know how to handle/fix it.
My AndroidKeyStore which is hardware optimized in Allview X2 Xtreme is currently broken,
Proved with apps:
* andOTP great app which able to select what kind of store you want to use -- It crashes just after setting Android KeyStore:
Code:
java.lang.IllegalStateException could not generate key in keystore
I've found some other banking apps which probably use it and also crashes,
(Also made a second topic more specified to the device with suggested banking apps: https://forum.xda-developers.com/pure-xl/help/readback-tee1-tee2-partitions-help-t4020253 )
Today I was able to get same error "could not generate key in keystore" with Nest Bank's application (god bless differently handled exceptions each bank app...)... so I'm sure right now.
* Alior Bank (on sending report, other functionality works ;O ) - https://play.google.com/store/apps/details?id=pl.aliorbank.aib
* Alior Bank Kantor Walutowy - https://play.google.com/store/apps/details?id=pl.alior.mobile.exchange.prd
* Moje ING - https://play.google.com/store/apps/details?id=pl.ing.mojeing
* Nest Bank nowy - https://play.google.com/store/apps/details?id=pl.nestbank.nestbank
As I read changing security settings (unlock for swipe, pin, other sh1t) should force somekind of change on the store, but that's not happening in my case.
I'm gonna try to do that with CM13, however apps looks like they're works fine on it so maybe our handicapped ported rom isn't even support HAL / hardware chip/module responsible for the crypto. Ok, I checked: CM13 applications work fine, andOTP is also able to use store with Hardware optimization. Setting finger/swipe/pin to unlock gave me option "Clear all certificate data"... however it freezes: on changing security or on clear attempt.
I've found some code snippets for java on stackoverflow which might help / will find now some apps which might "move" my store or do whatever just to bump it...
Any advice, please?
____
seo tags: could not generate key in keystore, AndroidKeyStore, HAL cryptography, Android TEE, Trusted Execution Environment...
Finally after many many hours I have... only a workaround, but it's better that nothing :F
I've changed names for two libs:
Code:
/system/lib/hw/keystore.mt6795.so
/system/lib64/hw/keystore.mt6795.so
After reboot without with any errors or warnings android changed it's Cert Storage to /only software supported/.
Bank apps began to work after wiping it's data and re-pairing/re-activating... however it's not solution for me: on rooted device software based security storage it's too weak....
"Moje ING" still doesn't work and can't download data, however is unit specified problem - other test-cases works.
Still I've not figured out why CM13 (with Hardware Support) works well on my device.
Might be newer Android / Kernel / Dedicated HAL support included in Android 6.0. To much differences, I can't find that point vs. 5.1 stock.
I have almost gave up last days...

Categories

Resources