Database Users

Your device is not compatible with this item - market error (finding a fix)

Hey folks,
This issue has been causing me a lot of trouble lately, but I may have found a fix. It does appear that the lcd density contributes to this error that prevents us from downloading a lot of apps.
Some mentioned that it was an issue with the lcd density.
What finally worked was setting the density back to 240, rebooting and then clearing the market data/cache from the manage applications dialog. This is the first time I tried the combination in this order, and I hope this helps anyone else struggling with this issue.
I will play around tomorrow to see if I am able to set it back to 200. Perhaps clearing the market cache while using an incompatible density caused this error in the first place.
Sent from my HTC Vision using XDA App

I had this problem
One of the solution is to get back with the old market.
The other one is to get the apps from 4shared .com
I have a other bug with the new market, it only shows 49 app under each categories ( top paid app, top free app, etc)

All you have to do is change lcd density to stock and reboot. No need to clear chache or change anything else. It's bothersome but an easy workaround... sometimes clear cache/data too lol had to do that once or twice.

I have been using the default density for weeks now and gave up thinking it was the lcd density to blame. The market consistently gave me that same error until I finally cleared its cache.
Sent from my HTC Vision using XDA App

Man... and I've been sitting here wracking my brain over what could be keeping me from updating and installing... I hope there's a permanent fix. I can't stand the stock density...
EDIT: Aww man! It still won't work! I changed the density to 240, killed market and its cache, restarted, same message. I even tried changing the device name back to "T-Mobile G2" in build.prop, but no go. I removed the updates and went back to the old market.

Heck, I get that error on Market 3.1.6 no matter what on certain apps. I never even touch the lcd density... the only way to fix is to wipe market cache and reinstall 3.1.5 or below. You could delete the marketupdater.apk but that has been known to break stuff. To be safe, you could freeze it or screw up th permissions.

EfemaN said:
Man... and I've been sitting here wracking my brain over what could be keeping me from updating and installing... I hope there's a permanent fix. I can't stand the stock density...
EDIT: Aww man! It still won't work! I changed the density to 240, killed market and its cache, restarted, same message. I even tried changing the device name back to "T-Mobile G2" in build.prop, but no go. I removed the updates and went back to the old market.
Click to expand...
Click to collapse
Try changing density to 240, then reboot, then clear market data/cache. It only worked for me in that order, because the market does not rely on the build.prop file itself. If you're already at 240 and rebooted, try to clear your market/data cache again.
If it doesn't work despite that, what market version are you using? I have 3.1.5 running, and here is my build.prop. Feel free to chop it up. Keep in mind you must reboot the phone with the new build.prop saved before clearing the market data.
I highly advise that you back up your existing build.prop before editing it, or your phone may not survive the restart.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.buildbot.20111005.041044
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Oct 5 04:11:14 UTC 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=buildbot
ro.build.host=cm-build1.public.ca.khresear.ch
ro.build.tags=test-keys
ro.product.model=HTC Vision
ro.product.brand=htc_wwe
ro.product.name=htc_vision
ro.product.device=vision
ro.product.board=vision
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=vision
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=2.42.405.2 CL84109 release-keys
ro.build.fingerprint=htc_wwe/htc_vision/vision:2.3.3/GRI40/84109:user/release-keys
# end build properties
#
# system.prop for vision
#
ro.sf.lcd_density=240
debug.fb.rgb565 = 0
# Modify MMS APN retry timer from 5s to 2s.
ro.gsm.2nd_data_retry_config = max_retries=3, 2000, 2000, 2000
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
ro.ril.enable.a53=1
ro.ril.enable.dtm=0
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.def.agps.feature=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.enable.gea3=0
# vision RF team request
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 12
ro.ril.hsdpa.category = 8
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 2
# Default network type.
# 0 => WCDMA preferred.
ro.telephony.default_network=0
wifi.interface=eth0
wifi.supplicant_scan_interval=15
mobiledata.interfaces=gannet0,rmnet0,rmnet1,rmnet2
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
# For the default value of agps
ro.ril.def.agps.mode = 2
# For HSDPA low throughput
ro.ril.disable.power.collapse = 1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-tmobile-us
ro.com.google.clientidbase.vs=android-hms-tmobile-us
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.com.google.gmsversion=2.2_r5
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
media.a1026.nsForVoiceRec=0
media.a1026.enableA1026=1
htc.audio.alt.enable=0
htc.audio.hac.enable=0
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmodnightly
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-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7-10052011-NIGHTLY-vision
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
If you have trouble editing the build.prop, remember you need to remount the system folder as read/write. I set this script to run with Gscript Lite so I can do it using a shortcut.
mount -o rw,remount -t ext3 /dev/block/mmcblk0p15 /system
chmod 777 /system/build.prop
Sent from my HTC Vision using XDA App

The build.prop reminded me of something.... There was someone a few weeks ago saying that they stopped the error and was able to keep market 3.1.6 by editing the build.prop. they basically changed it so that it identified the device differently. It was copied straight from the stock tmobile G2 GB build.prop. I posted the info from the build.prop but not sure were that thread is... let me look for it.
Oh... here it is. Let us know if it works. I've gotten 3.1.5 to stick for a while so I haven't messed with it. http://forum.xda-developers.com/showthread.php?t=1269032

sino8r said:
The build.prop reminded me of something.... There was someone a few weeks ago saying that they stopped the error and was able to keep market 3.1.6 by editing the build.prop. they basically changed it so that it identified the device differently. It was copied straight from the stock tmobile G2 GB build.prop. I posted the info from the build.prop but not sure were that thread is... let me look for it.
Oh... here it is. Let us know if it works. I've gotten 3.1.5 to stick for a while so I haven't messed with it. http://forum.xda-developers.com/showthread.php?t=1269032
Click to expand...
Click to collapse
I tried the method in that thread; neither the lines listed there, or the ones in funkeee's build.prop solved it. I changed the values, saved, restarted, cleared Market data, but it still brings the error. I'm on 3.1.5.
I can't go back to using the phone in stock density, I really hope we can find a fix...

I went back to the old market (green and white) don't remember which version it is though. I then changed permissions on marketupdater.apk(in sys/apps) to 400 which prevents it from updating. The old market has never bugged me about incompatibility.
Sent from my HTC Vision using XDA App

Work around
I noticed this issue with google earth, and I'm running a 2.3.5 ROM. I just waited for another app to show an update in the new market, then said to update all. No issues.

OneUp03 said:
I went back to the old market (green and white) don't remember which version it is though. I then changed permissions on marketupdater.apk(in sys/apps) to 400 which prevents it from updating. The old market has never bugged me about incompatibility.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
That's the basic workaround, at least right now. I just froze the updater through Titanium Backup and all is well. I like the new market though
dirtybudha said:
I noticed this issue with google earth, and I'm running a 2.3.5 ROM. I just waited for another app to show an update in the new market, then said to update all. No issues.
Click to expand...
Click to collapse
That didn't work out for me. I actually first noticed it when I went to "Update All", and the Swiftkey update I knew existed wasn't showing on the list. I searched for it manually and it gave me the error.

【Kernel】u8800pro-32&35--overclock-kernel【fixed sensor】

【Kernel】u8800pro-32&35--overclock-kernel【fixed sensor】
Installation Instructions
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see boot.img etc.
(optional) Rename boot.img to boot_backup.img
copy the new boot.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Power on
Max 2Ghz overclock
add smartass2 governor
add BFQ IO
other mod
Download
you could config the enhanced.conf（place it into /system/etc)
maybe somebody could translate enhanced.conf to english, thanks
Enhanced.conf
ONLY for FROYO
-----------------------------------------------
Boot into recovery,dont wipe,flash this package directly, same as flashing a ROM.
Max 2Ghz overclock
add smartass2 governor
add BFQ IO
other mod
ONLY for Gingerbread (stock,CM7,or other gingerbread)
Overclock kernel
if you don't like it ,you could restory to offical kernel
Offical kernel
the gs sensor can't init had fixed,so gs sensor worked now.

respect!
Sent from my ragelis

Just to be clear: This will only work with the Froyo ROM, right?

Doctor Who said:
Just to be clear: This will only work with the Froyo ROM, right?
Click to expand...
Click to collapse
Damn.... why not 2.6.35.7? who uses froyo?

bronxitas said:
Damn.... why not 2.6.35.7?
Click to expand...
Click to collapse
no kernel available

akalos said:
no kernel available
Click to expand...
Click to collapse
You mean no kernel source available. That's right, you can't do OC kernel without source

NForce25 said:
You mean no kernel source available.
Click to expand...
Click to collapse
how can we get this?

We need to annoy huawei's client support service further

huawei's client support say that on monday they will tell us the timeline of release the 35 kernel sources

genokolar said:
huawei's client support say that on monday they will tell us the timeline of release the 35 kernel sources
Click to expand...
Click to collapse
Good news!!!

Hi, thanks for this kernel, i have a question, did u in .config add support for MSM7X30? besides the native MSM8X...?, if you did that maybe this kernel can run on u8800-51, if u didnt, you have your kernel sources to compile it for u8800-51? thanks in advance
Best regards from Chile
Update:
I've flashed this kernel in my U8800-51 and it boot, but some reboots and some paths changed (that's because the init.rc from u8800pro and this phone are different, mount points mostly), so, i've unpacked my boot.img and replaced the kernel image with yours, and doesnt boot dunno what its, but im getting closer i think xD

EDIT: I'm an idiot. Ignore me, please

Tested it with Gingerbread and worked fine. Many thanks.
Buuuut... as soon as I installed it, the phone refuses to rotate. Any ideas on what could be wrong?

Auto-Rotate isn't working for me, too.
If I were to guess what's wrong, I'd suspect the sensor stuff but I'm just talking out of my ass here:
Code:
--- huaweiconfig 2011-11-21 17:19:00.923151198 +0000
+++ genokolarconfig 2011-11-21 17:13:00.633364620 +0000
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.35.7
-# Fri Nov 4 12:29:15 2011
+# Mon Nov 21 18:58:01 2011
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
@@ -40,9 +40,9 @@
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_LZO=y
-CONFIG_KERNEL_GZIP=y
+# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
-# CONFIG_KERNEL_LZMA is not set
+CONFIG_KERNEL_LZMA=y
# CONFIG_KERNEL_LZO is not set
# CONFIG_SWAP is not set
CONFIG_SYSVIPC=y
@@ -136,7 +136,8 @@
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
-# CONFIG_SLOW_WORK is not set
+CONFIG_SLOW_WORK=y
+# CONFIG_SLOW_WORK_DEBUG is not set
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
@@ -158,8 +159,11 @@
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_CFQ=y
+CONFIG_IOSCHED_BFQ=y
+# CONFIG_CGROUP_BFQIO is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
+# CONFIG_DEFAULT_BFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
@@ -359,7 +363,9 @@
# CONFIG_MSM_SDIO_SMEM is not set
CONFIG_MSM_DALRPC=y
CONFIG_MSM_DALRPC_TEST=m
-# CONFIG_MSM_CPU_FREQ_SET_MIN_MAX is not set
+CONFIG_MSM_CPU_FREQ_SET_MIN_MAX=y
+CONFIG_MSM_CPU_FREQ_MAX=1024000
+CONFIG_MSM_CPU_FREQ_MIN=245760
# CONFIG_MSM_AVS_HW is not set
# CONFIG_MSM_HW3D is not set
CONFIG_AMSS_7X25_VERSION_2009=y
@@ -522,12 +528,16 @@
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
+# CONFIG_CPU_FREQ_DEFAULT_GOV_SMARTASS2 is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
+# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_INTERACTIVE=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_CPU_FREQ_GOV_SMARTASS2=y
# CONFIG_CPU_IDLE is not set
CONFIG_CPU_FREQ_MSM=y
@@ -1136,7 +1146,7 @@
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
-# CONFIG_TUN is not set
+CONFIG_TUN=y
# CONFIG_VETH is not set
CONFIG_PHYLIB=y
@@ -1326,6 +1336,7 @@
# CONFIG_BOSCH_BMA150 is not set
CONFIG_HUAWEI_FEATURE_PROXIMITY_EVERLIGHT_APS_12D=y
CONFIG_HUAWEI_FEATURE_PROXIMITY_EVERLIGHT_APS_9900=y
+CONFIG_HUAWEI_FEATURE_PROXIMITY_LITEON_LTR_558=y
#
# Hardware I/O ports
@@ -1761,6 +1772,7 @@
CONFIG_HUAWEI_CAMERA=y
CONFIG_HUAWEI_SENSOR_HI701=y
CONFIG_HUAWEI_SENSOR_S5K5CA=y
+CONFIG_HUAWEI_SENSOR_MT9T113=y
# CONFIG_HUAWEI_SENSOR_OV7690 is not set
CONFIG_HUAWEI_SENSOR_OV7736=y
# CONFIG_HUAWEI_SENSOR_HIMAX0356 is not set
@@ -2521,7 +2533,12 @@
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CEPH_FS is not set
-# CONFIG_CIFS is not set
+CONFIG_CIFS=y
+# CONFIG_CIFS_STATS is not set
+# CONFIG_CIFS_WEAK_PW_HASH is not set
+# CONFIG_CIFS_XATTR is not set
+# CONFIG_CIFS_DEBUG2 is not set
+# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
@genokolar:
Do you have a diff of your changes?
You keep your source here: https://github.com/Victor-android/kernel_huawei_u8800pro/

did u try to overclock?

I set the phone to 1500 MHz for a few minutes using SetCPU. The device didn't crash. Not sure what to say really, except that the multitouch app was more responsive...

Yeah, using setcpu. It did overclock successfully up to 1.5GHz - didn't try higher (And then came the rotation issue).

@ qwerty12 are u with stock rom or 2.3.5?

2.3.5.
Just to be sure, I reinstalled the ROM (using the dload folder method). Accelerometer works (web browser rotates).
As soon as I install the new kernel (without any o/c) rotation breaks. I think I'll wait until it's sorted out.
EDIT: Sorry, didn't see you directed the question to qwerty.

1500Mhz its nice to see that is stable...

[GUIDE]Root Yoga Tablet 2 Pro 8, 10, and 13.3 android KitKat!!

New Firmware For 1380F:
New firmware for the 1380F: http://pan.baidu.com/s/1eQiuJoI Pw to extract is: bbs.lenovomobile.com
Thank you to bbslenovomobile.
UPDATED BELOW:
Those who have issue with trying to update via OTA on stock rom, can start over following this step : http://forum.xda-developers.com/showpost.php?p=57846051&postcount=233
Original Firmware for the 10" version F- https://mega.co.nz/#!eEth0YKI!tRcpe8LwKhLGvXmnlBH5hy2MbaAtnQTJ0W6V5k4ex_w
Original Firmware for the 10" version L-
https://cloud.mail.ru/public/f22489d084ae/YT2-1050L_USR_S000066_1410301706_WW21_ROW.rar
Original Firmware for the 13" pro version - https://cloud.mail.ru/public/056cdecc66dc/YT2-1380F_S068_140926_WW21_ROW.rar
If you are already on a rooted rom for your tablets, you need to install root explorer on your tablets, and follow this post: http://forum.xda-developers.com/showpost.php?p=57705744&postcount=146 . Please replace the appropriate .md5 based on your rom. For example, if it's "YT2-1380F_S068_140926..." , replace it with the system68.md5.txt attached file but remove the numbers!
HOW TO ROOT: ALL VERSIONS
http://forum.xda-developers.com/thi...guide-cwm-root-lenovo-yoga-2-8-10-13-t2998498
----------------------------------------------------------------------------------------------------------------------------------------
Thank you to bodivas on here for HUGE HUGE help in figuring out how to root this wonderful tablet! I will post instruction and hopefully everyone can install it like I can without having to do research and read russian translation by google I am not held responsible if you brick or burn your tablet, but if you follow this guide step by step you should not have issue.
Pre-req:
1. Download and install both files here: https://yadi.sk/d/BQDlz3kVcHK7p
2. Install PhoneFlashTool 4.4.4.1 from here: http://pan.baidu.com/wap/link?uk=86756550&shareid=735291514&third=0 . Click on the right button in chinese to download.
3. Download this recovery firmware for the LTE variant of the tablet: https://yadi.sk/d/__IkHVXtcUD9P . Make sure you extract the file and you will have system.img file.
You will need this file to flash. Wondering why the LTE variant work, and not the Wifi only. Also bodivas, do you know where to download the original firmware for
the Wifi in case we want to restore it?
Flashing:
1. Once you have everything install, it is reccommended to restart your PC, or laptop. Turn on developer mode in the tablet by going into Settings, About Tablet, Click on the Build Number repeatedly, about 5 or 6 times until it said developer mode turned on, and you will see Developer Options above the About Tablet. Turn off your tablet, make sure it is completely off. Hold down power and the Volume Down button until the screen turns off and let go. This will put you in the droidboot recovery menu of lenovo to begin flashing.
2. Plug in your tablet to your PC or laptop, and open PhoneFlashTool. Click on Custom Flash on the left hand side, go down to where it said "Android Image", and check the box next to "system" and browse in the system.img you just downloaded.
3. Once loaded, click on the Start to Flash button, and wait. The status bar will be green from 0% to 50% to 60% and you have to wait about 5 minute or so then it will say Complete while maintaining the Green color to let you know everything is fine. Once this is done, your tablet will be rebooted automatically and voila, you are rooted!
4. SuperSU will be installed, and it will ask you for permission to grant some access once fully loaded. Enjoy!
I will try to help as much as I can if this does not work, but according to the OP, this will work on all variants of the new yoga tablet 2 pro Android version only. Bodivas, if you see this, can you please follow up on the russian forum to see if this will stay rooted if you use the system update via the settings menu?

Thank you for sharing this instructions. I am waiting for this great news to get my Yoga Tablet 2 rootet.
Just to be on the save side: This is also for the Yoga Tablet 2-1050L with LTE?
Your title says "Yoga Tablet 2 Pro 8, 10,...." but I only found the 13.3 Yoga Tablet as titled "Pro".
All 3 Tabs (8,10 and 13,3) really got the same System Image?
I don't want to flash the wrong Software and brick my new loved Tab.
1. Once you have everything install, it is reccommended to restart your PC, or laptop. Turn on developer mode in the tablet by going into Settings, About Tablet, Click on the Build Number repeatedly, about 5 or 6 times until it said developer mode turned on, and you will see Developer Options above the About Tablet. Turn off your tablet, make sure it is completely off. Hold down power and the Volume Down button until the screen turns off and let go. This will put you in the droidboot recovery menu of lenovo to begin flashing.
Click to expand...
Click to collapse
Are you sure you only have to activate developer options and don't have to activate debugUSB at developer options?

As their is no Pro in 8 and 10 I will give it a try on my Yoga 2 10 inch without LTE.

Tab s8-50F
Is there any chance of this working on the Lenovo Tab s8-50F? It uses the same Intel Atom z3745 chipset as the Yoga Tablet 2 8.

McMiller said:
Thank you for sharing this instructions. I am waiting for this great news to get my Yoga Tablet 2 rootet.
Just to be on the save side: This is also for the Yoga Tablet 2-1050L with LTE?
Your title says "Yoga Tablet 2 Pro 8, 10,...." but I only found the 13.3 Yoga Tablet as titled "Pro".
All 3 Tabs (8,10 and 13,3) really got the same System Image?
I don't want to flash the wrong Software and brick my new loved Tab.
Are you sure you only have to activate developer options and don't have to activate debugUSB at developer options?
Click to expand...
Click to collapse
It doesn't hurt to do both And yes I meant to say 8, 10, and 13.3" pro hehe

So, being brave I dared to try the above linked system.img
Despite the above description that did not work for me I had to start the tool PhoneFlashTool 4.4.4.1 while my Lenovo Yoga 2 (10 inch - 1050F - this is without LTE) was up and running and connected.
I have choosen Fastboot in the tool, pointed to the system.img and pressed flash.
Yoga rebooting to something like OS prexxxx
Erasing system and then pulling system.img - took about 5 minutes.
Reboot and Yoga2 was back - then a dialog from SuperSU.
Checked with Rootchecker and confirmed to have root.
3 little downsides.
As I do not have a SIM or even a slot for a SIM I can see a message "Sim card not ready" when dragging the Lenovobar from the bottom and I have the symbol on top that normally shows signalstrength of SIM.
Second:
I have the point projector in settings - of course I do not have a projector.
Third:
My Yoga 2 no shows as a Yoga Tablet 2 Pro-1380L in "About your tablet"
All only cosmetics - system looks as before, all apps as before flashing.
So rooting does work this way on the 1050F - I am pretty sure 1050L as well.
So we only need the correct system.img - just a question of time.
At least we have a start

mysticc said:
3 little downsides.
As I do not have a SIM or even a slot for a SIM I can see a message "Sim card not ready" when dragging the Lenovobar from the bottom and I have the symbol on top that normally shows signalstrength of SIM.
Second:
I have the point projector in settings - of course I do not have a projector.
Third:
My Yoga 2 no shows as a Yoga Tablet 2 Pro-1380L in "About your tablet"
All only cosmetics - system looks as before, all apps as before flashing.
Click to expand...
Click to collapse
Nice to read this. Ty for your feedback.
With root it should be possible to change this things at the build.prop
Can you please test if you can eddit the build.prop at /system and save the changes.
Maybe my original build.prop form my Yoga Tablet 2-1050L could help:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.YT2-1050L_USR_S000066_1410301706_WW21_ROW dev-keys
ro.build.version.incremental=YT2-1050L_USR_S000066_1410301706_WW21_ROW
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Thu Oct 30 17:19:26 CST 2014
ro.build.date.utc=1414660766
ro.build.type=user
ro.build.user=buildslave
ro.build.host=bjws89
ro.build.tags=release-keys
ro.product.ota.model=
ro.product.model=YOGA Tablet 2-1050L
ro.product.brand=Lenovo
ro.product.name=YT2_10_row_lte
ro.product.device=YT2
ro.product.board=baylake
ro.product.cpu.abi=x86
ro.product.manufacturer=LENOVO
ro.wifi.channels=
ro.board.platform=baytrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=YT2
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=YT2_10_row_lte-user 4.4.2 KOT49H YT2-1050L_USR_S000066_1410301706_WW21_ROW release-keys
ro.build.fingerprint=Lenovo/YT2_10_row_lte/YT2:4.4.2/KOT49H/YT2-1050L_USR_S000066_141030:user/release-keys
ro.build.characteristics=sdcard,tablet
ro.lenovo.adb=apkctl,speedup
ro.lenovo.series=YOGA Tablet 2
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.streaming.video.drs=true
ro.disablelonglongpress=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
sys.lenovo.romui.version.sdk=2
ro.config.ringtone=Fantastic_Clang.ogg
ro.config.notification_sound=Notice.ogg
ro.config.alarm_alert=New_Morning.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.jit.code_cache_size=1048576
ro.hwui.texture_cache_size=64.0f
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.hwui.layer_cache_size=36.0f
ro.hwui.gradient_cache_size=0.8f
ro.hwui.r_buffer_cache_size=6.0f
ro.hwui.path_cache_size=24.0f
ro.hwui.shape_cache_size=3.0f
ro.hwui.drop_shadow_cache_size=5.0f
ro.hwui.fbo_cache_size=16
ro.hwui.texture_cache_flush_rate=0.6f
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=512
drm.service.enabled=true
ro.opengles.version=196608
ro.blankphone_id=1
persist.tel.lteOnGsmDevice=true
ro.telephony.default_network=9
persist.tel.hot_swap.support=true
ro.spid.gps.pmm=disabled
ro.spid.gps.tty=ttyMFD1
dalvik.vm.extra-opts=-XX:mainThreadStackSize=32K
ro.sf.lcd_density=240
ro.lenovo.operator=open
ro.lenovo.region=row
ro.lenovo.device=tablet
ro.lenovo.sim=single
ro.lenovo.tablet=3gdata
ro.lenovo.platform=intel
ro.lenovo.signalbars=four
ro.lenovo.bqb=pass
ro.lenovo.cta=false
ro.lenovo.videocall=false
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.com.google.clientidbase=android-lenovo
persist.backgrounddata.enable=false
ro.lenovo.wificert=no
ro.lenovo.childmode=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r5
persist.sys.dalvik.vm.lib=libdvm.so
ro.ril.status.polling.enable=0
ro.product.cpu.abi2=armeabi-v7a
ro.config.personality=compat_layout
rs.gpu.renderscript=1
rs.gpu.filterscript=1
rs.gpu.rsIntrinsic=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1

Will try - but tomorrow.
Thanks.
McMiller said:
Nice to read this. Ty for your feedback.
With root it should be possible to change this things at the build.prop
Can you please test if you can eddit the build.prop at /system and save the changes.
Maybe my original build.prop form my Yoga Tablet 2-1050L could help:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.YT2-1050L_USR_S000066_1410301706_WW21_ROW dev-keys
ro.build.version.incremental=YT2-1050L_USR_S000066_1410301706_WW21_ROW
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Thu Oct 30 17:19:26 CST 2014
ro.build.date.utc=1414660766
ro.build.type=user
ro.build.user=buildslave
ro.build.host=bjws89
ro.build.tags=release-keys
ro.product.ota.model=
ro.product.model=YOGA Tablet 2-1050L
ro.product.brand=Lenovo
ro.product.name=YT2_10_row_lte
ro.product.device=YT2
ro.product.board=baylake
ro.product.cpu.abi=x86
ro.product.manufacturer=LENOVO
ro.wifi.channels=
ro.board.platform=baytrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=YT2
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=YT2_10_row_lte-user 4.4.2 KOT49H YT2-1050L_USR_S000066_1410301706_WW21_ROW release-keys
ro.build.fingerprint=Lenovo/YT2_10_row_lte/YT2:4.4.2/KOT49H/YT2-1050L_USR_S000066_141030:user/release-keys
ro.build.characteristics=sdcard,tablet
ro.lenovo.adb=apkctl,speedup
ro.lenovo.series=YOGA Tablet 2
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.streaming.video.drs=true
ro.disablelonglongpress=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
sys.lenovo.romui.version.sdk=2
ro.config.ringtone=Fantastic_Clang.ogg
ro.config.notification_sound=Notice.ogg
ro.config.alarm_alert=New_Morning.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.jit.code_cache_size=1048576
ro.hwui.texture_cache_size=64.0f
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.hwui.layer_cache_size=36.0f
ro.hwui.gradient_cache_size=0.8f
ro.hwui.r_buffer_cache_size=6.0f
ro.hwui.path_cache_size=24.0f
ro.hwui.shape_cache_size=3.0f
ro.hwui.drop_shadow_cache_size=5.0f
ro.hwui.fbo_cache_size=16
ro.hwui.texture_cache_flush_rate=0.6f
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=512
drm.service.enabled=true
ro.opengles.version=196608
ro.blankphone_id=1
persist.tel.lteOnGsmDevice=true
ro.telephony.default_network=9
persist.tel.hot_swap.support=true
ro.spid.gps.pmm=disabled
ro.spid.gps.tty=ttyMFD1
dalvik.vm.extra-opts=-XX:mainThreadStackSize=32K
ro.sf.lcd_density=240
ro.lenovo.operator=open
ro.lenovo.region=row
ro.lenovo.device=tablet
ro.lenovo.sim=single
ro.lenovo.tablet=3gdata
ro.lenovo.platform=intel
ro.lenovo.signalbars=four
ro.lenovo.bqb=pass
ro.lenovo.cta=false
ro.lenovo.videocall=false
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.com.google.clientidbase=android-lenovo
persist.backgrounddata.enable=false
ro.lenovo.wificert=no
ro.lenovo.childmode=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r5
persist.sys.dalvik.vm.lib=libdvm.so
ro.ril.status.polling.enable=0
ro.product.cpu.abi2=armeabi-v7a
ro.config.personality=compat_layout
rs.gpu.renderscript=1
rs.gpu.filterscript=1
rs.gpu.rsIntrinsic=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1
Click to expand...
Click to collapse

Lol.... it's rooted is all that matters. I wonder how did pro100gamer get the root inside the img and recompile the img though? I can't find a newest img firmware for the 1380F american version. The link he provided has the ROW (which I think is russian), and the CN which is Chinese version.

Introducing root directly in the firmware is a temporary solution, until we make CWM-recovery..
Firmware ROW - multilanguage! (International)
So, as all the models yoga2 have the same size partition system (it would be mmcblk0p13) that can flash system.mg from one version to another (at your own risk of course)

Inject root (big thanks to research by chainfire) is only flowers))
The real goal - to compill CWM, Caynogenmod and dual boot for windows. The boys from 4pda.ru are already working but are waiting for your tablet.
Be patient..
---------- Post added at 10:20 AM ---------- Previous post was at 09:33 AM ----------
Forgot: to get into fastboot mode manually, press and hold power + volume- (release after 3 seconds after appearance of any written).
For recovery mode: power + volume- (to exit from recovery after the wipe: press and hold the power button until the tablet turns off)

bodivas said:
Inject root (big thanks to research by chainfire) is only flowers))
The real goal - to compill CWM, Caynogenmod and dual boot for windows. The boys from 4pda.ru are already working but are waiting for your tablet.
Be patient..
---------- Post added at 10:20 AM ---------- Previous post was at 09:33 AM ----------
Forgot: to get into fastboot mode manually, press and hold power + volume- (release after 3 seconds after appearance of any written).
For recovery mode: power + volume- (to exit from recovery after the wipe: press and hold the power button until the tablet turns off)
Click to expand...
Click to collapse
I am patiently awaiting as always and I know this tablet is fairly new! I flashed the tablet last night but I did not do the wipe cache or full wipe bc I don't have anything installed! So the chainfire root from the appstore can root this tablet? I should have tried that first then see what happened, i tried many other root but all failed!

McMiller said:
Nice to read this. Ty for your feedback.
With root it should be possible to change this things at the build.prop
Can you please test if you can eddit the build.prop at /system and save the changes.
Maybe my original build.prop form my Yoga Tablet 2-1050L could help:
[/CODE]
Click to expand...
Click to collapse
I was able to change to correct model - now shows as 1050F
Did not change build etc - I don`t really care.
There are some entries for SIM and LTE - without an original file for 1050F I leave them untouched.

i did it too
mysticc said:
I was able to change to correct model - now shows as 1050F
Did not change build etc - I don`t really care.
There are some entries for SIM and LTE - without an original file for 1050F I leave them untouched.
Click to expand...
Click to collapse
i also did this root lastnight
and it also display me that is 2-pro 13.3
how can i change to the correct model
my tab is 1050L

Edit the build.prop as described some posts before.

mysticc said:
Edit the build.prop as described some posts before.
Click to expand...
Click to collapse
it have another problem i find
i can't use power button to lock screen
do you have the same problem??

oooooh litteraly just got one of these will greatly look forward to work being done on it. though mine is a 1050F so im not sure what that means in term of difference.

mooNlooN said:
it have another problem i find
i can't use power button to lock screen
do you have the same problem??
Click to expand...
Click to collapse
My lockscreen is set to "gesture".
When I choose to lock when pressing power off/on I get the lockscreen when pressing power and screen goes off- power again and screen goes on -> locksckreen. Had to restart to take effect.
When set to lock after 5 seconds when sleeping I too do see the lockscreen.
Reason I did not see before was a little tool I forgot - "nolock" - this was active.

help!
on trying to flash it gets to 66% then it fails the last few lines are
target reported max download size of 1717567488 bytes
error: cannot load 'C:/Users/Mark/Desktop/system/system.img'
11/10/14 19:11:59.036 ERROR : Port 5/5/1/1/4: Flash failure
now the tablet cant boot up i ithkn because its passing the erase stage but then not accepting the new rom image.

mark2410 said:
help!
on trying to flash it gets to 66% then it fails the last few lines are
target reported max download size of 1717567488 bytes
error: cannot load 'C:/Users/Mark/Desktop/system/system.img'
11/10/14 19:11:59.036 ERROR : Port 5/5/1/1/4: Flash failure
now the tablet cant boot up i ithkn because its passing the erase stage but then not accepting the new rom image.
Click to expand...
Click to collapse
What size was the system.img? - It is 1,56 GB on my disk.

Oneplus 8T [Android 12] - Fingerprint Reader Not Working Patch File

Hi, while I am facing this issue, thanks to @BillGoss for highlighting the changes required for people who root/magisk installed.
OxygenOs 12 Beta
OxygenOs 12 CBT for kb2001 - working on all variants (you install at your own risk) https://mega.nz/file/CVsgyaAB#zrRWx1vIKUc6pMmNesu8ywpaUSAJWJecDcROvwOGOug
forum.xda-developers.com
So I compared the file with the original @kdrag0n Universal SafetyNet Fix, and the files required to change is:
credit to @BillGoss & @kdrag0n
1st --
system.prop [ORIGINAL from kdrag0n]
# Basic MagiskHide properties
# RootBeer, Microsoft
ro.build.tags=release-keys
# Samsung
ro.boot.warranty_bit=0
ro.vendor.boot.warranty_bit=0
ro.vendor.warranty_bit=0
ro.warranty_bit=0
# SafetyNet
ro.boot.verifiedbootstate=green
ro.boot.veritymode=enforcing
ro.boot.vbmeta.device_state=locked
vendor.boot.vbmeta.device_state=locked
# Other
ro.build.type=user
ro.debuggable=0
ro.secure=1
Click to expand...
Click to collapse
system.prop [MODIFIED]
# Basic MagiskHide properties
# RootBeer, Microsoft
ro.build.tags=release-keys
# Samsung
ro.boot.warranty_bit=0
ro.vendor.boot.warranty_bit=0
ro.vendor.warranty_bit=0
ro.warranty_bit=0
# OnePlus
ro.is_ever_orange=0
# SafetyNet
ro.boot.verifiedbootstate=green
ro.boot.veritymode=enforcing
vendor.boot.vbmeta.device_state=locked
# Other
ro.build.type=user
ro.debuggable=0
ro.secure=1
Click to expand...
Click to collapse
2nd --
service.sh [ORIGINAL from kdrag0n]
# Late props which must be set after boot_completed
{
until [[ "$(getprop sys.boot_completed)" == "1" ]]; do
sleep 1
done
# avoid breaking Realme fingerprint scanners
resetprop ro.boot.flash.locked 1
# avoid breaking OnePlus display modes/fingerprint scanners
resetprop vendor.boot.verifiedbootstate green
}&
Click to expand...
Click to collapse
service.sh [MODIFIED]
# Late props which must be set after boot_completed
{
until [[ "$(getprop sys.boot_completed)" == "1" ]]; do
sleep 1
done
# avoid breaking Realme fingerprint scanners
resetprop ro.boot.flash.locked 1
# avoid breaking Oppo fingerprint scanners
resetprop ro.boot.vbmeta.device_state locked
# avoid breaking OnePlus display modes/fingerprint scanners
resetprop vendor.boot.verifiedbootstate green
}&
Click to expand...
Click to collapse
File Replaced from his last latest release 2.2.1(Zygisk):
1. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/service.sh
2. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/post-fs-data.sh
3. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/system.prop
As I don't know how to build from GitHub, I manually replaced the files shown above. All files are copied from @kdrag0n GitHub Repo [Zygisk version]

Thanks, It work
I just upgrade to android 12 today and fingerprints sensor didn't work

Got an error in the installation.
Device is system-as-root
Unable to extract zip file!
Installation failed

bojiokia said:
Hi, while I am facing this issue, thanks to @BillGoss for highlighting the changes required for people who root/magisk installed.
OxygenOs 12 Beta
OxygenOs 12 CBT for kb2001 - working on all variants (you install at your own risk) https://mega.nz/file/CVsgyaAB#zrRWx1vIKUc6pMmNesu8ywpaUSAJWJecDcROvwOGOug
forum.xda-developers.com
So I compared the file with the original @kdrag0n Universal SafetyNet Fix, and the files required to change is:
credit to @BillGoss & @kdrag0n
1st --
2nd --
File Replaced from his last latest release 2.2.1(Zygisk):
1. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/service.sh
2. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/post-fs-data.sh
3. https://raw.githubusercontent.com/kdrag0n/safetynet-fix/master/magisk/system.prop
As I don't know how to build from GitHub, I manually replaced the files shown above. All files are copied from @kdrag0n GitHub Repo [Zygisk version]
Click to expand...
Click to collapse
How come your zip is 223kb when the one I modified is one only 92kb? See https://forum.xda-developers.com/t/oxygenos-12-beta.4383689/post-86562887

This one's updated with the files from @kdrag0n's GitHub that were updated on the 10th and 12th of March 2022.

Hello, the attached file 'safetynet-fix-v2.2.1.1_Realme_FingerprintFix.zip' does not fix the fingerprint reader for me.
But the other file 'safetynet-fix-v2.2.1-ob1.zip' form the other thread works for me.
My phone version is KB2005_11_C.11, Magisk 24.3 .

I've taken a look into the source code, looks like the issue is now fixed in the commit 55f892fb8855a7867a186970e0bfc31e665ab183. However, @kdrag0n hasn't provided a new release with that commit on Github.
I've cloned the repository (https://github.com/kdrag0n/safetynet-fix.git) and compiled the module myself. I can confirm the module I just compiled fixes the fingerprint issue.
Here's the module I compiled, based on commit 57b726c260bb40b838c5d942965282a5a482bdbe

Hello, thanks for your new patch.
I confirm that the fingerprint reader works with it.
Alas, there is a new issue: Niantic games (e.g. Pokemon Go, Pikmon Bloom ....) wont run now. It looks like there is user authentication issue.
So I'm reverting to 'safetynet-fix-v2.2.1-ob1.zip' for now, where I have both finferprint reader and Niantic games working.

Does anyone have an update solution for the fingerprint problem?
The SaftyNetFix v2.3.1 from kdrag0n does not work for me, the SaftyNet is fine but my fingerprint sensor does not work.
Device: Oneplus 8T EU version OOS12 C.20

Ramme said:
Does anyone have an update solution for the fingerprint problem?
The SaftyNetFix v2.3.1 from kdrag0n does not work for me, the SaftyNet is fine but my fingerprint sensor does not work.
Device: Oneplus 8T EU version OOS12 C.20
Click to expand...
Click to collapse
Did you try previous safetynet-fix-v2.2.1-ob1.zip version?

Yes I have tried all versions from the XDA forum, also from other threads.
I have found the problem. I used Magisk Hide and the SaftyNet script in combination.
Without Magik hide my fingerprint sensor works.
But my CTS profile fails without Magisk Hide.
It is due to the version OOS C.20 "C.21".
Everyone in the OOS forum is reporting a Saftynet problem.
I hope there is a solution from Oneplus as soon as possible.

Ramme said:
Yes I have tried all versions from the XDA forum, also from other threads.
I have found the problem. I used Magisk Hide and the SaftyNet script in combination.
Without Magik hide my fingerprint sensor works.
But my CTS profile fails without Magisk Hide.
It is due to the version OOS C.20 "C.21".
Everyone in the OOS forum is reporting a Saftynet problem.
I hope there is a solution from Oneplus as soon as possible.
Click to expand...
Click to collapse
Hi,
Can you please share the patched boot.img for C.21 IN version, if you have it.
Or tell me the way to patch a boot image.
I am trying with magisk to patch the boot image, but when I do "fastboot boot boot.img" with the patched image, it doesn't work. Magisk doesn't shot Direct install. Basically I am not able to root my C.21 IN version.
Any help would be appreciated.

Samsung tab a 10.1 SM-T515 can't find custom rom gta3xlwifi ...

First of all, I apologize for my mistakes in writing. Because I use google translate to get my point across.
I have a Samsung tab a10.1. SM-T515 with code gta3xlwifi. I had a lot of trouble rooting this device and also installing twrp. I was able to install custom recovery at the end. but none of the lineage os or other custom roms are loaded on this device. As the reason, error code 7 appears in the twrp terminal. at the top it says "this rom is for gtaxlwifi, gta4xlwifi, etc. devices. your device is gta3xlwifi" . I checked not only lineage, but also pixel and caos, the same error code is received and it does not load. I also unzipped the lineage os.zip file and deleted the first error codes from the meta-inf/com/google/script-update file and checked. still not working :/ If you know any gta3xlwifi roms pls help....
I have installed the stock system at the moment, and it freezes a lot... I'll give the tablet a chance for the last time and try my luck here, if it doesn't work, let the tablet think for itself :|

Mecidzade said:
First of all, I apologize for my mistakes in writing. Because I use google translate to get my point across.
I have a Samsung tab a10.1. SM-T515 with code gta3xlwifi. I had a lot of trouble rooting this device and also installing twrp. I was able to install custom recovery at the end. but none of the lineage os or other custom roms are loaded on this device. As the reason, error code 7 appears in the twrp terminal. at the top it says "this rom is for gtaxlwifi, gta4xlwifi, etc. devices. your device is gta3xlwifi" . I checked not only lineage, but also pixel and caos, the same error code is received and it does not load. I also unzipped the lineage os.zip file and deleted the first error codes from the meta-inf/com/google/script-update file and checked. still not working :/ If you know any gta3xlwifi roms pls help....
I have installed the stock system at the moment, and it freezes a lot... I'll give the tablet a chance for the last time and try my luck here, if it doesn't work, let the tablet think for itself :|
Click to expand...
Click to collapse
Hi.
Welcome to xda.
Quick look though the threads, I ran across this one.
(ROM)(UNOFFICIAL)(11.0)NEXUS STOCK and Lineage OS GALAXY Tab A 10.1 "SM-T515" - Link
Quick look at the Lineage build, it seems to be for the T510 gta3xlwifi.
Code:
# Samsung SM-T510 [Build Date - Nov 20 2020]
#
# Device is on certified list
# Samsung Galaxy Tab A gta3xlwifi SM-T510
#
# ro.build.fingerprint=samsung/omni_gta3xlwifi/gta3xlwifi:9/PQ3B.190801.002/chad11202254:eng/test-keys
# ro.build.version.security_patch=2019-10-05
#
# ro.bootimage.build.fingerprint=samsung/omni_gta3xlwifi/gta3xlwifi:9/PQ3B.190801.002/chad11202254:eng/test-keys
# ro.build.description=omni_gta3xlwifi-eng 9 PQ3B.190801.002 eng.chad.20201120.225433 test-keys
# ro.build.fingerprint=samsung/omni_gta3xlwifi/gta3xlwifi:9/PQ3B.190801.002/chad11202254:eng/test-keys
# ro.build.version.release=9
# ro.build.version.sdk=28
# ro.product.device=gta3xlwifi
# ro.product.brand=samsung
# ro.product.manufacturer=samsung
# ro.product.model=SM-T510
# ro.product.name=omni_gta3xlwifi
# ro.build.product=gta3xlwifi
#
# # Pulled from ramdisk/prop.default
Not sure if you tried that one or not.
Cheers.

ipdev said:
Hi.
Welcome to xda.
Quick look though the threads, I ran across this one.
(ROM)(UNOFFICIAL)(11.0)NEXUS STOCK and Lineage OS GALAXY Tab A 10.1 "SM-T515" - Link
Quick look at the Lineage build, it seems to be for the T510 gta3xlwifi.
Code:
# Samsung SM-T510 [Build Date - Nov 20 2020]
#
# Device is on certified list
# Samsung Galaxy Tab A gta3xlwifi SM-T510
#
# ro.build.fingerprint=samsung/omni_gta3xlwifi/gta3xlwifi:9/PQ3B.190801.002/chad11202254:eng/test-keys
# ro.build.version.security_patch=2019-10-05
#
# ro.bootimage.build.fingerprint=samsung/omni_gta3xlwifi/gta3xlwifi:9/PQ3B.190801.002/chad11202254:eng/test-keys
# ro.build.description=omni_gta3xlwifi-eng 9 PQ3B.190801.002 eng.chad.20201120.225433 test-keys
# ro.build.fingerprint=samsung/omni_gta3xlwifi/gta3xlwifi:9/PQ3B.190801.002/chad11202254:eng/test-keys
# ro.build.version.release=9
# ro.build.version.sdk=28
# ro.product.device=gta3xlwifi
# ro.product.brand=samsung
# ro.product.manufacturer=samsung
# ro.product.model=SM-T510
# ro.product.name=omni_gta3xlwifi
# ro.build.product=gta3xlwifi
#
# # Pulled from ramdisk/prop.default
Not sure if you tried that one or not.
Cheers.
Click to expand...
Click to collapse
thank you for the reply. I will check and get back to you