Samsung tab a 10.1 SM-T515 can't find custom rom gta3xlwifi ... - Samsung Galaxy Tab A series Questions & Answers

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

Related

[Q] Build.prop please help

i just tried to add
Code:
windowsmgr.max_events_per_sec=26
into my build.prop using flashtool
i rebooted and got stuck at the SE logo
ok, so trying to fix this i rebooted into recovery and mounted the sd card
i copied the system.img out of my backup and extracted it using wunyaffs
undid the changes in my build.prop.
repackaged as a .zip and used recovery to flash the build.prop back...
and it still gets stuck.
what am i doing wrong ?
*EDIT*
damn... i posted this in the wrong forum... sorry
it was meant for Q&A not General :\ mybad
here is my current build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FreeX10-beta4_zdzihu
ro.build.display.id=FreeX10-beta4_zdzihu
ro.build.version.incremental=eng.zdzihu.20110125.133835
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Tue, 25 Jan 2011, 13:39:25 CET
ro.build.date.utc=1295959165
ro.build.type=user
ro.build.user=zdzihu
ro.build.host=zdzihu
ro.build.tags=test-keys
ro.product.model=X10i
ro.product.brand=generic
ro.product.name=Xperia
ro.product.device=es209ra
ro.product.board=es209ra
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=SE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=qsd8k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=es209ra
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.2.1 FRG83 60505 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.sf.lcd_density=240
rild.libpath=/system/lib/libril-qc-1.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=90
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.def.agps.mode=2
ro.opengles.version=131072
dalvik.vm.heapsize=32m
ro.media.dec.jpeg.memcap=20000000
keyguard.no_require_sim=true
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
i am... was... running freeX10 beta4
I didn`t see any error on your build.prop file.
You just add that line? Cause i don`t see it on your build.prop file
I just wonder why that value so low...
oh i removed the line then posed sorry
apparently 26 is optimum
i just thought id try it and now it doesnt boot.
and, stupid me, i should have backed up before changing the file but ... i didnt think it would break it :\
by adding just that line that won`t happen. i`m sure that`s not the cause!
if you just add that. i add so many things...
witch flashtool you use? the last one or 26th?
i didn`t have time to try last myself so do know if there`s any issue regarding that but i doubt
oh dear
i just realised what my problem is
when i made the changes to the build.prop i used FlashTool. waiting for a reply now i was reading your FlashTool Guide and read the bit about JIT, clicking the optimise button and saw the BIG RED TEXT
"PLEASE DON`T USE JIT OPTION THIS WILL MAKE YOUR PHONE STUCK ON BOOT!!!"
guess what i remember clicking
is there anyway to fix this ?
Btw about that number for build.prop. heres where i got that info
http://forum.xda-developers.com/showthread.php?t=881778 posts 5-8
So i presume that you've done that on 26th version.
Download the last one and run optimize cause it was one of the upgrades.
if that wont help your only option is reflash.
yeah 0.2.6... wow i cant believe i did that.
ill try 0.2.7 now.
also... thankyou for your quick replys
0.2.7 is downloading now.
but umm... if my x10 is stuck at the se logo im not going to be able to connect to it over adb will i?
even if you`re stuck you probably get some functions
ok i just tried it
this is what i got
10/042/2011 23:42:23 - ERROR - Cannot identify your device. Found lin while expecting X10, E10, U20 or E15 (read from ro.product.model from build.prop)
10/042/2011 23:42:23 - INFO - Selecting from user input
10/042/2011 23:42:25 - INFO - Connected device : X10
10/042/2011 23:42:25 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
10/042/2011 23:42:30 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
10/042/2011 23:42:31 - ERROR - Please Accept root permissions on the phone
it doesnt give root permission
try press ask root permition
if you can`t do anything or only option is reflash i guess
yeah when i press ask for root perms the phone denies it
i guess its a reflash then ay ?
Sutekhxaos said:
yeah when i press ask for root perms the phone denies it
i guess its a reflash then ay ?
Click to expand...
Click to collapse
the phone denies?! he`s got own life?
didn`t appear to choose yes or no on the phone?
if not...reflash
hahah unfortunatly
no theres no dialog or anything on the screen to ask for root. it just denies it
i have one other idea. get the files that flashtool changes when you click optimise.
repackage them in a .zip and use the recovery console to update them
your opinion ?
don`t believe but...try
nope, not working. thanks for all your help
i will reflash tomorrow its late here

[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.

Fine OS Custom Rom Version-7 For J7 Nxt-Core-Neo By Abdullah AL-Noman

------- Fine OS Custom Rom Version-7 For J7-Nxt-Core-Neo . Exynos 7870
............Feature...........
# Based On J701F Pie 9
# One Ui 1.1
# Binary 8 Firmware .
# Latest Security Patch
# 1 November 2019 Security Patch
# De-Knoxed
# Debloat
# All Latest App Included
# Recycle Bin Supported File Manager App
Special Feature
# Supported One Ui 2.0 Apps Included
# Show Data Speed Enable Menu On Status Bar
# Vpn Suported
# Busy Box Included
# Magisk 20.3 Included
# Twrp 3.2.1 Included
# Oem Lock Disabled
# Mock locations - Hide mock locations status, allowing apps like Pokemon GO to treat them as genuine location updates.
# Secure flag - Allow screenshots/screensharing in secure apps.
# Signature verification - Disable signature verification allowing modification/execution of signed system apps.
# Signature spoofing - Enable signature spoofing app permission.
# Added Screen Capture And Screen Record On Status Bar
# Call Record Allowed By Call App
# LTE Only Option
# Show LTE on 4G Network
# Enable Use Mobile Data Option During Call On Settings
# Enable Google Face Lock Option On Smart Lock
Kernel Information
Kernel Name - Oxygen Kernel Version- 4.0.138
Kernel Creator- Siddhant Naik
# Selinux Status - Permissive
# Binary Lock Disabled
# No Problem For Mount Data Partition And Internal Storage
................... What's New ...............
# Fix wifi
# Add New Charging Logo
# Add J7 Nxt White Boot Logo
XDA:DevDB Information
Fine OS Custom Rom Version-7 For J7 Nxt-Core-Neo By Abdullah AL-Noman, ROM for all devices (see above for details)
Contributors
Abdullah AL-Noman
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest Bootloader
Based On: Samsung One Ui
Version Information
Status: Stable
Current Stable Version: Version-7
Stable Release Date: 2020-03-03
Beta Release Date: 2020-03-03
Created 2020-03-02
Last Updated 2020-08-26

[SM-G355M][LineageOS 14.1] No mobile data, (how to debug?) (disabled during comp?)

Hi All!
I have a Galaxy Core 2 running LineageOS 14.1 (Nougat 7.1.2). It works really well, but ... I can't get the mobile data working.
I downloaded the ROM from "Sandroid Team" (XDA doesn't allow me to post the URL)
The "author" (Ih24n) seems to be unreachable (COVID-19 problems?).
I found that /system/build.prop mentions:
Code:
#
# ADDITIONAL_BUILD_PROPERTIES
#
...
ro.com.android.mobiledata=false
This make me think the mobile data support was disabled at compile time. Is this correct?
What can I test in my phone? I can use adb shell and I have some Linux knowledge.
I took a look to other Nougat ROMs from Ih24n and all has the same value in adb shell.
Note that when I say "I can't make it work" I mean that I don't even see the option to enable it in the settings menu. I already configured the APN.
If I can solve it I'll be forced to try Android 6.
Does anybody has experience with other ROMs from Ih24n?

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.

Categories

Resources