This is development thread for CM11 building on Samsung GalaxyTab3 10.1 devices, based on Intel Clover Trail platform. (x86)
Device tree: https://github.com/Angel666/android_device_samsung_santos103g
CM11 source repo:
Code:
[FONT=Arial]repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0[/FONT]
Patches for CM source needed to build rom. Made by HazouPH:
https://github.com/HazouPH/android_device_motorola_smi/tree/jellybean/patch
Working for now:
hardware accel (with some bugs)
storages and mtp mounting
Ril (partially)
Lights and buttons
Houdini service
anything else I can forgot..
Not working for now:
Wi-Fi (can not obtain mac)
BT (can not obtain mac)
Camera (service works, app can't connect)
SeLinux security (disabled)
Sound (Samsung lib won't work)
Basic CM Launcher3 is glitchy! I don't know why. Third-party launcers works well (testing by GOlauncher)
anything else I can forgot..
Images for testing: >DOWNLOAD< 3g version only for now!
WARNING! This images are for testing purposes only! Don't flash it if you don't know what you doing! Rom is almost UNUSABLE for enduser! Work in progress....
0.Unpack zip's.
1. Flash boot by Odin
2. Flash recovery by Odin
3. Enter to recovery and Wipe cache, dalvik, system and data.
4 Flash system by Odin
I appreciate any possible help (testing, donations, devs and experienced users advices). Let's speedup the process!
Impressive work done so far!
Thanks a lot Angel_666 ?
Sent from my HTC One
I'll be on for testing as soon as the images are uploaded!
Sent from my MB886 using xda app-developers app
Zachisimo said:
I'll be on for testing as soon as the images are uploaded!
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Good. But i must warning all who want to test image. After flash it erase all you data! It means, that only /data/media folder is staying alive.
@Angel_666 I donated you a little bit of money to congrat you for your work
Sent with PotatOS, the new experience of Potatoes
@Angel_666 are the test builds for the p5210 also?
Sent from my GT-P5210
Hey do you think there would be any chance of building this with the abyssplug governor? Or would the fact that hyperthreading is present screw things up? And is it possible to overclock? Thanks for all your work @Angel_666, been following the twrp and manifest threads for a while now, Great progress, just wanted to say thanks.
woopdedoda said:
Hey do you think there would be any chance of building this with the abyssplug governor? Or would the fact that hyperthreading is present screw things up? And is it possible to overclock? Thanks for all your work @Angel_666, been following the twrp and manifest threads for a while now, Great progress, just wanted to say thanks.
Click to expand...
Click to collapse
As about CPU - I don't find any information that it can work stable more than 1.6Ghz. But our GPU runs at 400Mhz and can be overclocked to 533 i think.
First post updated.
OK, didn't know that. That's the same chip that's in the i9500 right? Would comparing the gpu code for that help with hardware acceleration?
I'm now testing CM11
@Angel_666
I flashed the Images and I cant boot CM
I'm always stuck at "Samsung Galaxy Tab 3"
I can only boot to TWRP and Download
logcat doesn't work.
superboom said:
I'm now testing CM11
@Angel_666
I flashed the Images and I cant boot CM
I'm always stuck at "Samsung Galaxy Tab 3"
I can only boot to TWRP and Download
logcat doesn't work.
Click to expand...
Click to collapse
flash boot again, flash recovery, go to advanced wipe in recovery and check ALL options exept last (microSD). After process done, flash system img. Try and tell me.
P.S. "samsung logo" it not a bootloop. In your case system does not even run init process. (cm logo). Just checked all uploaded files on my tab p5200. All ok. CM logo, then system start. Before flashing i formatted my device and it was clean like a baby.
Formatting tried also, doesnt work in my p5210 @Angel_666
Sent with PotatOS, the new experience of Potatoes
For me it failed after wiping /system. I restored it from backup, wiped cache/data, flashed again, it worked.
With pimpdroid, not yet tested with cm11, but the issue is the same.
Gesendet von meinem GT-I9100G mit Tapatalk
Setialpha said:
For me it failed after wiping /system. I restored it from backup, wiped cache/data, flashed again, it worked.
With pimpdroid, not yet tested with cm11, but the issue is the same.
Gesendet von meinem GT-I9100G mit Tapatalk
Click to expand...
Click to collapse
Don't understood - CM works or not? Your device is p5210?
Ok now. I setup stock samsung firmware, and then repeat all process step by step. Will post results later.
Angel_666 said:
Don't understood - CM works or not? Your device is p5210?
Ok now. I setup stock samsung firmware, and then repeat all process step by step. Will post results later.
Click to expand...
Click to collapse
That should have been a reply to superboom.
Gesendet von meinem GT-I9100G mit Tapatalk
Setialpha said:
That should have been a reply to superboom.
Gesendet von meinem GT-I9100G mit Tapatalk
Click to expand...
Click to collapse
Ah. Sorry.
Ok. I flash my device by stock samsung firmware. Then, i flash CM11 as described at first post. CM boots OK and setup wizard turn on. My device is p5200 (3g).
Angel_666 said:
Ah. Sorry.
Ok. I flash my device by stock samsung firmware. Then, i flash CM11 as described at first post. CM boots OK and setup wizard turn on. My device is p5200 (3g).
Click to expand...
Click to collapse
What needs to be altered for it to boot on p5210.
I downloaded cm11 source last night and am gonna try put a build together.... Just need to figure out local manifests to sync your github :thumbup: thanks for that BTW.
Quick question.... How come you are having to flash via Odin? Thought that they could be flashed by recovery. Have you tried any gapps yet
Sent from my GT-I9300 using xda app-developers app
pug1 said:
What needs to be altered for it to boot on p5210.
I downloaded cm11 source last night and am gonna try put a build together.... Just need to figure out local manifests to sync your github :thumbup: thanks for that BTW.
Quick question.... How come you are having to flash via Odin? Thought that they could be flashed by recovery. Have you tried any gapps yet
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
As for img files via odin - "make otapackage" return some errors to me. That's why i use img. As for CM boot on p5210 - give me your build.prop from stock firmware - i'll tru to fix this.
Angel_666 said:
As for img files via odin - "make otapackage" return some errors to me. That's why i use img. As for CM boot on p5210 - give me your build.prop from stock firmware - i'll tru to fix this.
Click to expand...
Click to collapse
Here is the build.prop for the P5210
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.P5210UEUAMK1
ro.build.version.incremental=P5210UEUAMK1
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Tue Nov 26 14:28:02 KST 2013
ro.build.date.utc=1385443682
ro.build.type=user
ro.build.user=se.infra
ro.build.host=R0210-17
ro.build.tags=release-keys
ro.product.model=GT-P5210
ro.product.brand=samsung
ro.product.name=santos10wifiue
ro.product.device=santos10wifi
ro.product.board=clovertrail
ro.product.cpu.abi=x86
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=clovertrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=santos10wifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=santos10wifiue-user 4.2.2 JDQ39 P5210UEUAMK1 release-keys
ro.build.fingerprint=samsung/santos10wifiue/santos10wifi:4.2.2/JDQ39/P5210UEUAMK1:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=P5210UEUAMK1
ro.build.hidden_ver=P5210UEUAMK1
ro.build.changelist=850131
ro.product_ship=true
ro.chipname=clovertrail
# end build properties
#
# system.prop for santos10 wifi
#
ro.carrier=wifi-only
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
# System property for Default Brightness
ro.lcd_brightness=118
# System property for Min Brightness
ro.lcd_min_brightness=10
# System Property for Intel MDS
ro.mds.enable=true
ro.kernel.qemu=0
persist.sys.storage_preload=1
# System property for Font Clarity
persist.sys.font_clarity=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.sf.lcd_density=160
ro.hdcp2.rx=tz
ro.secwvk=144
ro.sec.fle.encryption=true
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.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.crypto.support=recovery_mount|others
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.jit.code_cache_size=1048576
persist.tel.hot_swap.support=true
drm.service.enabled=true
ro.com.google.apphider=off
ro.com.google.gmsversion=4.2_r3
ro.ril.status.polling.enable=0
ro.product.cpu.abi2=armeabi-v7a
ro.config.personality=compat_layout
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
hfase said:
Here is the build.prop for the P5210
Code:
ro.product.model=GT-P5210
ro.product.name=santos10wifiue
ro.product.device=santos10wifi
ro.build.product=santos10wifi
Click to expand...
Click to collapse
I think i need to change boardconfig.mk for wi-fi version
Related
WARNING:
For devs and experts ONLY!
This is not fully functional and it is not well tested yet!
I do not take responsibility for any damage you cause your player!
This is an unofficial port of CM9 alpha to the Galaxy Player 4.0 (USA).
Preparation
MAKE A FULL BACKUP! Make sure you can recover using heimdall or odin.
Backup /system using "dd" use with odin/heimdall, just in case:
dd if=/dev/block/stl9 of=/mnt/sdcard/system.img bs=512
Backup your apps if you care about them
Installation
Download the ROM for your device
Boot into recovery and install the ROM
Do a full wipe. Wipe data, cache, dalvik, everything
Reboot, and you should have cm9!
Issues?
Post any other issue here and I will respond when I get a chance.
Please do NOT send me PM's.
Download
http://www.mediafire.com/?wch69mtgwx4ssra
Note: gapps is not currently included in the ROM.
THIS IS STILL IN TESTING. PLEASE LEAVE A COMMENT TELLING ME HOW WELL IT WORKED.
When will international version be released?
thanks for your efforts
I dont have an international device so i cant release it.
Tcollins412 said:
I dont have an international device so i cant release it.
Click to expand...
Click to collapse
are you aware of what changes must be made to make it compatible with an international device? also i tried installing the usa version but clockworkmod aborts the installation. (i know that if i flash the usa versions my home button won't work, but i just wanted to check)
im sure therell be devs with intl versions willing to help. iean whats the difference between the usa and intl version if its just a few lines in a piece of code it should be easy to change.
but at least be grateful lots of hard works been put into this i was gonna wait beford ruining the show asking for a intl version.
minipot said:
im sure therell be devs with intl versions willing to help. iean whats the difference between the usa and intl version if its just a few lines in a piece of code it should be easy to change.
but at least be grateful lots of hard works been put into this i was gonna wait beford ruining the show asking for a intl version.
Click to expand...
Click to collapse
I've thanked Tcollins twice, trust me I really appreciate his hard work and I'm sorry it didn't come across as such.
I think I found the problem with clockworkmod aborting the installation, inside the .zip file, rather than going straight to the contents of the rom with the system folder, etc. there is another folder named nightly cm9 player inside the original nightly cm9 player folder.
I do have a intl device. The only difference is the home button. As the difference in the build is the kernel where you have to chose in the config aries_EU and remove aries_US (I don't know if you understand what I mean)
zaclimon said:
I do have a intl device. The only difference is the home button. As the difference in the build is the kernel where you have to chose in the config aries_EU and remove aries_US (I don't know if you understand what I mean)
Click to expand...
Click to collapse
so by changing that line in the kernel the home button works? do I need ubuntu to unpack the zimage?
theraf said:
so by changing that line in the kernel the home button works? do I need ubuntu to unpack the zimage?
Click to expand...
Click to collapse
You must do that with the defconfig file. And yes you need linux to unpack. But the problem is where is Tcollins source?
what do you mean by my source?
Tcollins412 said:
what do you mean by my source?
Click to expand...
Click to collapse
Your device tree and kernel source. How have you built that.
@Tcollins412
I just took a look at the zipfile and it seems that there's a folder within a folder and while I haven't tried to flash it yet, I don't think it will flash that way. Thanks.
Mike T
your right. im reuploading it.
Tcollins412 said:
your right. im reuploading it.
Click to expand...
Click to collapse
I just took a look into your updater-script. Have you take a galaxy s CM9? Because it seems to be the case.
Code:
ssert(getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" ||
getprop("ro.product.device") == "galaxysmtd" || getprop("ro.build.product") == "galaxysmtd" ||
getprop("ro.product.device") == "GT-I9000" || getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "GT-I9000M" || getprop("ro.build.product") == "GT-I9000M" ||
getprop("ro.product.device") == "GT-I9000T" || getprop("ro.build.product") == "GT-I9000T");
Tcollins412 said:
your right. im reuploading it.
Click to expand...
Click to collapse
Thanks for the re-upload and thanks for taking on this project for the 4.0. As mentioned in my pm, I will test it over the next couple of days.....or sooner.
Mike T
nope. i took a couple things from it though.
and no problem and thank you
zaclimon said:
Your device tree and kernel source. How have you built that.
Click to expand...
Click to collapse
Agreed.
Could you post your device and vendor files on github, like how tdmcode has done for cm7 amd cm9? That way people could fork your project and try to fix some of the issues there might be. We could also get an aokp and aosp build as well.
Thanks.
Sent using Tapatalk
---------- Post added at 03:07 PM ---------- Previous post was at 02:45 PM ----------
EDIT:
Have you flashed this yourself? I took a look at the build.prop and it seriously looks like you just took an I9000 CM9 nightly and posted it here, hoping that somebody would try it out and brick their device.
Here is the build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.jenkins.20120429.031009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Apr 29 03:10:25 PDT 2012
ro.build.date.utc=1335694225
ro.build.type=userdebug
ro.build.user=jenkins
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.3.5 GINGERBREAD XXJVT release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.5/GINGERBREAD/XXJVT:user/release-keys
ro.build.characteristics=default
ro.cm.device=galaxysmtd
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmodnightly
keyguard.no_require_sim=true
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.cm.version=9-20120429-NIGHTLY-galaxysmtd
ro.modversion=9-20120429-NIGHTLY-galaxysmtd
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.vold.switchablepair=/mnt/emmc,/mnt/sdcard
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
And it won't flash even if someone tried to, due to the getprops in the updater-script that zaclimon posted a few posts above.
Of cource my suspicions could be totally wrong, and I apologize if they are, but until your source is released, I strongly advise people to not flash this. Just take a look at the build.prop and you know that it won't be compatible with the YP-G1.
Tcollins412 said:
WARNING:
For devs and experts ONLY!
This is not fully functional and it is not well tested yet!
I do not take responsibility for any damage you cause your player!
This is an unofficial port of CM9 alpha to the Galaxy Player 4.0 (USA).
Preparation
MAKE A FULL BACKUP! Make sure you can recover using heimdall or odin.
Backup /system using "dd" use with odin/heimdall, just in case:
dd if=/dev/block/stl9 of=/mnt/sdcard/system.img bs=512
Backup your apps if you care about them
Installation
Download the ROM for your device
Boot into recovery and install the ROM
Do a full wipe. Wipe data, cache, dalvik, everything
Reboot, and you should have cm9!
Issues?
Post any other issue here and I will respond when I get a chance.
Please do NOT send me PM's.
Download
http://www.mediafire.com/?wch69mtgwx4ssra
Note: gapps is not currently included in the ROM.
THIS IS STILL IN TESTING. PLEASE LEAVE A COMMENT TELLING ME HOW WELL IT WORKED.
Click to expand...
Click to collapse
Thanks. I'll port a aokp(may be this rom is 4.0.3
Sent from my galaxy s using XDA
klin1344 said:
Agreed.
Could you post your device and vendor files on github, like how tdmcode has done for cm7 amd cm9? That way people could fork your project and try to fix some of the issues there might be. We could also get an aokp and aosp build as well.
Thanks.
Sent using Tapatalk
---------- Post added at 03:07 PM ---------- Previous post was at 02:45 PM ----------
EDIT:
Have you flashed this yourself? I took a look at the build.prop and it seriously looks like you just took an I9000 CM9 nightly and posted it here, hoping that somebody would try it out and brick their device.
Here is the build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.jenkins.20120429.031009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Apr 29 03:10:25 PDT 2012
ro.build.date.utc=1335694225
ro.build.type=userdebug
ro.build.user=jenkins
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.3.5 GINGERBREAD XXJVT release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.5/GINGERBREAD/XXJVT:user/release-keys
ro.build.characteristics=default
ro.cm.device=galaxysmtd
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmodnightly
keyguard.no_require_sim=true
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.cm.version=9-20120429-NIGHTLY-galaxysmtd
ro.modversion=9-20120429-NIGHTLY-galaxysmtd
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.opengles.version=131072
wifi.interface=wlan0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.vold.switchablepair=/mnt/emmc,/mnt/sdcard
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
And it won't flash even if someone tried to, due to the getprops in the updater-script that zaclimon posted a few posts above.
Of cource my suspicions could be totally wrong, and I apologize if they are, but until your source is released, I strongly advise people to not flash this. Just take a look at the build.prop and you know that it won't be compatible with the YP-G1.
Click to expand...
Click to collapse
I took a look into his lib folder and he have the gralloc.aries.so instead of gralloc.s5pc110.so So it can be a CM9 nightly in which he replaced the kernel. Let's see how it will turn.
This is my fourth Samsung Android device, and you'd think I'd be beyond brilliant noob moves... but apparently not.
I got TWRP recovery installed on my device fine (Sprint SPH-L600)... but, since I saw this phone is a Tri-Band, I assumed that it was more or less identical regardless of provider (yeah... I know already... don't say it)
So now I'm looking for my old factory firmware to Odin back in because now my Samsung message just sits on my screen after boot animation.
All I wanted was root... which I managed to find after it was too late... so if I can get back to stock I'm good.
Anybody out there have any ideas on downloading the stock firmware again. I see the customs that are out aren't fully working yet... and all I was really missing with stock was hot spot and root access. I can live w/o hotspot and usb tether for now, and I solved my root issue.
Thanks in advance for any help.
B
Im in same boat as your I soloved it by cwm recovery install silent rom temporarily it worked , now till we get hands on the stock usa version sprint rom, for those who have sprint galaxy mega 6.3 dont do rooting yet till someone figure out a safe way to root sprint version
Sent from my GT-I9200 using xda app-developers app
---------- Post added at 08:09 PM ---------- Previous post was at 07:26 PM ----------
Correction its silentlight rom but no lte or 3g works grrr!
Sent from my GT-I9200 using xda app-developers app
Hmmm
Maybe all we need is some kind soul to make a nand backup of his stock firmware and post that back? Not sure. One of the drawbacks of being the first on your block with the new toy? I think so...
Yea right sprint mega is not the same rom as att or verzion!
Sent from my GT-I9200 using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
One thing is if you had checked about and seen the firmware info what prefix is that for usa region?
Sent from my GT-I9200 using xda app-developers app
How is lte working on this phone? Have the lg g2 and there are serious issues with sprints spark....
Sent from my LG-LS980 using Tapatalk
LTE Performance
Well... off topic, but I boot-looped the phone the first day that I got it... so not a great idea about how it runs on the network. My old phone (Epic4GT) was WiMax and it occasionally had 4g (and was fast when it did...). Sprint is phasing out WiMax in the coming months so I wanted an LTE. BUT... as far as I've observed so far, I NEVER had a 4G connection. Missing in the setup screens is the traditional "4G switch", but you can switch selection between CDMA and LTE/CDMA/Evo (among others)... and I tried toggling in and out of the LTE option and it never indicated to me 4GLTE on the notification area. Again, though... I only had it running for a short time, so I could have missed something. Really hoping someone antes up a stock firmware somehow so I can get on with trying it out for real. (to bring it back around to originating topic)
I think for now you can only pickup the 1900mhz lte until sprint updates the APN with logon info for the other bands. Though you won't see 800mhz for a few years they are converting the wimax towers over to ltd so you will get that once the APN works
Sent from my LG-LS980 using Tapatalk
I finbaly got the phone mode working but stilk at 1x instead of 3g hmmmm
Sent from my GT-I9205 using xda app-developers app
Tri-Band information
I actually read this morning that the S4 Mini is the only one (of the 4 sprint phones that will get Spark LTE) that is actually functioning. They are planning on doing OTA updates to enable it in the other three in the coming months. As for the 800 MHz broadcast... it's not WiMax, but actually the old Nextel hardware that their going to use. So for now, unless you have the S4 Mini, don't plan on using your 4G or Spark at all until Sprint updates your phone OTA.
Firmware Version Anyone?!?
So I found some other stock firmware for the Mega on different carriers by searching the actual firmware build number. Is there anyone out there with a Sprint Mega who would be willing to look into their phone info to see what the build number is on your firmware and pass that along in this thread please?
Thanks so much in advance.
dug though nandroid backups files on laptop and behold! i got the orginal build.prop here it is!!
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.L600VPUAMI6
ro.build.version.incremental=L600VPUAMI6
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Sep 18 00:02:17 KST 2013
ro.build.date.utc=1379430137
ro.build.type=user
ro.build.user=se.infra
ro.build.host=R0302-18
ro.build.tags=release-keys
ro.product.model=SPH-L600
ro.product.brand=samsung
ro.product.name=meliusltespr
ro.product.device=meliusltespr
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=meliusltespr
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=meliusltespr-user 4.2.2 JDQ39 L600VPUAMI6 release-keys
ro.build.fingerprint=samsung/meliusltespr/meliusltespr:4.2.2/JDQ39/L600VPUAMI6:user/release-keys
ro.build.characteristics=phone,chameleon
# Samsung Specific Properties
ro.build.PDA=L600VPUAMI6
ro.build.hidden_ver=L600VPUAMI6
ro.build.changelist=1708610
ro.product_ship=true
ro.chipname=MSM8930AB
ro.build.version.software=MI6
# end build properties
# Evolution RIL (8xxx)
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
debug.compbypass.enable=1
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
#
# System prop for Tvout/HDMI
#
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# System property for cabl
ro.qualcomm.cabl=0
# System property for Default Brightness
ro.lcd_min_brightness=20
ro.lcd_brightness=120
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048
#
# Supports warmboot capabilities
#
ro.warmboot.capability=1
ro.sf.lcd_density=240
# System property for PreloadInstaller
persist.sys.storage_preload=1
# Use CDMALTE Phone
telephony.lteOnCdmaDevice=1
# Enable time services daemon
persist.timed.enable=true
# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1
# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1
# For sys info indication
persist.radio.add_power_save=1
# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22
# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false
# Data modules
ro.use_data_netmgrd=true
# Use CP SE13 Table
persist.radio.use_se_table_only=1
# Default ECCList
ro.ril.ecclist=911,#911,*911
# Support Global Mode (Global Mode project)
ro.config.multimode_cdma=1
# Use data service state for signal display (Except USC CS devices)
ro.config.combined_signal=true
# Chameleon Default Operator (SPR with Chameleon)
ro.cdma.default_numeric=310000
ro.cdma.default_alpha=Chameleon
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=/system/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.sec.fle.encryption=true
ro.hdcp2.rx=tz
media.enable-commonsource=true
ro.secwvk=144
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.media_sound=Over_the_horizon_Acoustic.ogg
ro.monkey=0
ro.error.receiver.default=com.samsung.receiver.error
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.crypto.support=recovery_mount|others
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.2_r3
ro.build.selinux=1
ro.config.tima=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
persist.gps.qc_nlp_in_use=0
see? i was able to find out info about it yep
You da man!
Thanks dude! Exactly what I was looking for. Much appreciated...
Err... I take that back. I thought I was bright enough to figure out how to solve my problem with that information... but I'm just not that smart, darn it.
Any techier types out there who can tell me what I can do with this info (not THAT!)... I'd appreciate being pointed in the right direction. I guess for me the only way I can think to get back running again is to get the L600VPUAMI6 Firmware so I can flash it with Odin again... but I can't find it posted anywhere and (as stated before) I brilliantly neglected to do a nandroid backup of my stock setup before flashing the new firmware (wrong model).
Alternatively, if anyone has a stock SPH-L600 and could make a nandroid backup of all the pretinent files I did figure out how to write that into an "update.zip" (from a helpful online primer...) so I can plunk that in with recovery... but I haven't had any takers yet with the backup intact (for my model).
So I'll keep trying to figure it out I guess.
Of course any help is welcome.
For those planning to roit it please perform a nandroid backup there are apps in google playstore that not need root espically the boot.img! Id want anyone upload virgin sprint stock rom itll help us get back to working normally you can link the uploaded file here
Sent from my GT-I9205 using xda app-developers app
fyi.... you can always go to any sprint store and find that one and go in setting,more,about phone and take a snapshot of that revision including kernel version with your camera phone and post the pic in here simple?
blohman said:
So I found some other stock firmware for the Mega on different carriers by searching the actual firmware build number. Is there anyone out there with a Sprint Mega who would be willing to look into their phone info to see what the build number is on your firmware and pass that along in this thread please?
Thanks so much in advance.
Click to expand...
Click to collapse
---------- Post added at 10:30 AM ---------- Previous post was at 09:54 AM ----------
It has dawned on me that why no 3g or lte is bec the roited boit.img made by other mega from diffrent carrier is not the same kernel version so what I would do is use the boot.ing and extract it theb build a kernel with correct version and make a new boit.img it should restore it the config is very specfic about this model ive done mune on htc evo 4g and it worked like charm what I need is for someone who has stock rom and note the kernel version and adb pull /proc/config.gz and send that to me?
Sent from my GT-I9205 using xda app-developers app
Firmware Version
I actually had done what you suggested yesterday (sort of... since I'd already upgraded my old phone to the Mega, I don't actually have a [working] camera phone at the moment)... so I did it the old fashioned way... pen and paper.
The firmware version for the Sprint version is L600VPUAMI6 (that's a capital "I", like in Ice Cream... not a 1).
I still can't find it, even though I now know the version number. Still hoping someone may post it up here.
The kernel version is really 3.4.0 with build number appended yeah I looked at it in sprint store I noticed in phone satus it should show imei and network status saying evdo,3g ... hmm mine didnt shows so I suspect the sim card or efs protected folder is screwed fyi the sim card I cant figure out how to remove it bec it dies have inei is printed so if those who have mega please use efs pro to back it up!
Sent from my GT-I9205 using xda app-developers app
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
Also those have stock boot imge in mega is pull up /proc/config.gz by mean of adb pull and id like to get that file for compiling kernel
Sent from my GT-I9205 using xda app-developers app
Running wrong rom (sort of...)
Learned a little more last night. Apparently Samsung has a arrangement with Best Buy (learned in chat w/ a Samsung tech). You can take your Samsung phone in and they can reflash it w/ stock rom again. You lose everything you had installed - but my phone was brand new, so I wouldn't lose anything really. The caveat is that they have to HAVE the rom in there proprietary system. They still DON'T have the SPH-L600, so I remained out of luck getting the stock rom. I don't know if they have the T-mobile rom.
What I HAVE ended up doing is putting an I9205 rom in (Cassie's XtraLite?) and "most" of my phone is working again. No 3G (or 4G), but phone works and wifi works... so it's limping along. Going to play w/ Kies today to see if it can figure the phone out, now that it's actually booting. It appears that, like Best Buy, Kies still doesn't have access to the factory rom (online) yet. I may just try to flash some of my old modems onto this and see if I can wake up the 3G if Kies doesn't come up with a complete package.
Will they charge to reflash it? Thanks for the info i was afraid not take it to sprint store for voiding warranty if they find out
So...
About kies, i have trouble with it not reonizing my phone no matter what drivers are properly instalked either kies or kies3 so what gives?
Sent from my GT-I9205 using xda app-developers app
Ive got info from one of xda user that successfully rooted his sprint mega with lte working im going get him to back up the stock rom and hopeflly he agrees to....
Sent from my GT-I9205 using xda app-developers app
Best Buy
They tried to flash my rom (no luck...didn't have the SPH-L600 rom available to their proprietary software [SMART?]... he even called Samsung and they said it's not available yet - have to wait until they distribute it I guess). Anyhow, they didn't charge or say anything about charging. Maybe they have the T-Mobile... not sure on that one.
BTW... Finally got Kies to understand which firmware I wanted (have to ask "case sensitive", i.e. sph-l600 doesn't work... SPH-L600 does!) Then only to have Kies say it doesn't support flashing that rom yet (lol - I detect a theme here, i.e. play the waiting game until either Samsung releases it, or an actual Sprint tech has a heart and leaks the rom so we can get back to stock).
For now still limping along mocking an i9205 w/ Cassie's XtraLite custom rom - no 3G or 4G (or data of any kind). Phone works... so does wifi.
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Thanks man I will try it
Hi I can't find a line sys.config.samp_spcm_enable=
martinforester said:
Hi I can't find a line sys.config.samp_spcm_enable=
Click to expand...
Click to collapse
Which rom do you use?
because I found it in stock rom.
I have stock 5.0.2 oryginal rom
martinforester said:
I have stock 5.0.2 oryginal rom
Click to expand...
Click to collapse
in the #SAMP_SPCM line
victoram said:
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Click to expand...
Click to collapse
Hi, can you give step by step instructions on how to do this? Thanks!
victoram said:
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Click to expand...
Click to collapse
Will this only work for LL 5.x.x? I have KK 4.4.4 and can't find any of these files. Thanks.
I applied this and it works , Less Heat and Phone feels mutch more responsive and snappier .
Thanks for sharing !
cqdiep said:
Will this only work for LL 5.x.x? I have KK 4.4.4 and can't find any of these files. Thanks.
Click to expand...
Click to collapse
i think it is only on lolipop based touch wiz
victoram said:
i think it is only on lolipop based touch wiz
Click to expand...
Click to collapse
Makes sense, I should have read the title more carefully. I'm running KK without any problems.
I don't think so, I have Lollipop and I don't have any of these lines
martinforester said:
I don't think so, I have Lollipop and I don't have any of these lines
Click to expand...
Click to collapse
you shouldd only have this line: "sys.config.samp_spcm_enable=true" change it to false
=====> sys.config.samp_spcm_enable=false
you have to add these 3 manually.
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
I don't have this line
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX22G
ro.build.display.id=LRX22G.G850FXXU2COI3
ro.build.version.incremental=G850FXXU2COI3
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.2
ro.build.date=Fri Sep 11 19:17:32 KST 2015
ro.build.date.utc=1441966652
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHD7522
ro.build.tags=release-keys
ro.product.model=SM-G850F
ro.product.brand=samsung
ro.product.name=sltexx
ro.product.device=slte
ro.product.board=universal5430
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=slte
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=sltexx-user 5.0.2 LRX22G G850FXXU2COI3 release-keys
ro.build.fingerprint=samsung/sltexx/slte:5.0.2/LRX22G/G850FXXU2COI3:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=G850FXXU2COI3
ro.build.hidden_ver=G850FXXU2COI3
ro.config.rm_preload_enabled=0
ro.build.changelist=5614954
ro.product_ship=true
ro.chipname=exynos5430
persist.sys.storage_preload=1
# end build properties
#
# HWUI_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=24
ro.hwui.layer_cache_size=16
ro.hwui.path_cache_size=4
ro.hwui.shape_cache_size=1
ro.hwui.gradient_cache_size=0.5
ro.hwui.drop_shadow_cache_size=2
ro.hwui.r_buffer_cache_size=2
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=512
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
#
# from device/samsung/slte/system.prop
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
#
# system.prop for universal5430
#
# LCD Density
ro.sf.lcd_density=320
ro.arch=exynos5430
ro.kernel.qemu.gles=1
persist.demo.hdmirotationlock=false
#DHA
ro.config.dha_cached_max=4
ro.config.dha_empty_init=24
ro.config.dha_empty_max=24
ro.config.dha_defendth_enable=false
ro.config.dha_th_rate=1.83
#LMK Tuning
ro.config.dha_lmk_scale=1.45
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.tima=1
ro.config.timaversion=3.0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapmaxfree=4m
dalvik.vm.heapminfree=1m
dalvik.vm.heapsize=384m
dalvik.vm.heapstartsize=8m
dalvik.vm.heaptargetutilization=0.75
ro.opengles.version=196608
ro.sf.lcd_density=480
debug.hwc.winupdate=1
debug.hwc.otf=1
ro.hdcp2.rx=tz
ro.secwvk=220
ro.securestorage.support=true
ro.build.scafe=americano
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.build.scafe.cream=white
security.mdpp=None
ro.security.mdpp.ver=1.1
ro.security.mdpp.release=5
ro.security.vpnpp.ver=1.4
ro.security.vpnpp.release=4.1
security.mdpp.result=None
ro.security.mdpp.ux=Enabled
ro.security.reactive.triggered=false
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Morning_flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.security.reactive.active=1
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.security.icd.flagmode=single
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r3
persist.sys.dalvik.vm.lib.2=libart.so
ro.build.selinux=1
dalvik.vm.isa.arm.features=div
ro.config.knox=v30
ro.kernel.qemu=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.version.sdl=2101
martinforester said:
I don't have this line sys.config.samp_spcm_enable=true
Click to expand...
Click to collapse
do you have the smart manager app?
I don't know what is it, I use "Root Browser" to browse files
martinforester said:
I don't know what is it, I use "Root Browser" to browse files
Click to expand...
Click to collapse
you probably don't have the smart manager app, it's an stock app from samsung, the line that you don't have is to disable that app from killing any tasks.
just add the 3 other lines and you should be fine.
I rooted my Alpha today and I would like to do this tweak, but I don't know how. I see the "sys.config.samp_spcm_enable=true" line in my build.prop. My question is where do I add these lines:
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
Do I put them at the very bottom of the file or in the #SAMP_SPCM section where the other line is?
My first time having a rooted android so i'm a noob
Juusoavk said:
I rooted my Alpha today and I would like to do this tweak, but I don't know how. I see the "sys.config.samp_spcm_enable=true" line in my build.prop. My question is where do I add these lines:
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
Do I put them at the very bottom of the file or in the #SAMP_SPCM section where the other line is?
My first time having a rooted android so i'm a noob
Click to expand...
Click to collapse
The first line you can add to #spcm as well, I think.
The second and the third lines can be added to
# ADDITIONAL_BUILD_PROPERTIES.
This is just below the #spcm section.
Note that I don't know that for sure, but I have just done it myself and it seems OK ).
Good luck mate )
Sent from my SM-G850F using Tapatalk
asetmumin99 said:
The first line you can add to #spcm as well, I think.
The second and the third lines can be added to
# ADDITIONAL_BUILD_PROPERTIES.
This is just below the #spcm section.
Note that I don't know that for sure, but I have just done it myself and it seems OK ).
Good luck mate )
Sent from my SM-G850F using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! I already got it working few days after the post though.
I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Bdazzled said:
I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Click to expand...
Click to collapse
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thank you, I found it.
Bdazzled said:
Thank you, I found it.
Click to expand...
Click to collapse
Glad that it worked ?
Sent from my Pixel XL using Tapatalk
Same problem but with an Honor 9 (STL-AL09):crying:
---------- Post added at 06:02 PM ---------- Previous post was at 05:41 PM ----------
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I did it and it worked:good: but I can't find the build number. Can you help me ?
Please.
jacquesallet said:
Quote removed to prevent spam
Click to expand...
Click to collapse
That method only works on Samsung phones on stock ROMs or on non-stock ROMs with stock build fingerprint (aka ro.build.fingerprint property in build.prop)
So how can I find my build number? Please.
PS: when I do the manipulation, I can see:
"MacBook-Pro-de-Jacques:~ jacquesallet$ adb shell cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.version.incremental=eng.jslave.20170604.040710
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2017-05-05
ro.build.version.base_os=
ro.build.date=Sun Jun 4 04:07:10 CST 2017
ro.build.date.utc=1496520430
ro.build.type=user
ro.build.user=jslave
ro.build.host=LFG1000749994
ro.build.tags=test-keys
ro.build.flavor=generic_a15-user
ro.product.model=generic_a15
ro.product.brand=Huawei
ro.product.name=generic_a15
ro.product.device=generic_a15
ro.product.board=
# 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.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic_a15
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-user 7.0 NRD90M eng.jslave.20170604.040710 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys
ro.build.characteristics=default
# end build properties
# begin huawei emui properties
# autogenerated by build_emui_info.sh
ro.build.hw_emui_api_level=13
# end huawei emui properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.carrier=unknown
ro.setupwizard.require_network=any
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r5
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
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.display.id=System 5.1.0.78(055I)
ro.comp.sys_support_vndk=VA7.0-E5.0-B00005
ro.comp.sys_need_sndk=SA7.0-E5.0-B00005
MacBook-Pro-de-Jacques:~ jacquesallet$"
"ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys"
So it works isn't it?
Hi
Need firmware/stock ROM for an unbranded tablet. Tablet got broken and it is a blank screen now and it is not booting, Trying to rebuild and fix the issue for this tablet. I bought this tablet through WISH. unable to get the firmware from the seller. Please help.
Model: KT107
Android Version: 6.0
Android Security patch level: 2016-01-01
Baseband version: MOLY.WR8.W1449.MD.WG.MP.V23, 2016/06/17 13:38
Kernel version: 3.10.72+ [email protected] #1
Build number: KT107_V01
Custom build version: KT107_MID-2017
Ram: 4GB
Internal Storage: 64GB
It is an unbranded tablet with 11.6 Inch screen, with a dual sim card. I think Chipset is MT6580.
Maybe wiping user data can help?
jeyaayyanar said:
Hi
Need firmware/stock ROM for an unbranded tablet. Tablet got broken and it is a blank screen now and it is not booting, Trying to rebuild and fix the issue for this tablet. I bought this tablet through WISH. unable to get the firmware from the seller. Please help.
Model: KT107
Android Version: 6.0
Android Security patch level: 2016-01-01
Baseband version: MOLY.WR8.W1449.MD.WG.MP.V23, 2016/06/17 13:38
Kernel version: 3.10.72+ [email protected] #1
Build number: KT107_V01
Custom build version: KT107_MID-2017
Ram: 4GB
Internal Storage: 64GB
It is an unbranded tablet with 11.6 Inch screen, with a dual sim card. I think Chipset is MT6580.
Click to expand...
Click to collapse
I have a similar tablet, and accidentally softbricked it by doing fastboot oem unlock (I think...). In my case though, the screen did not stay black, but the Android Logo showed forever, and the user's screen never appeared.
What got it working again was locking it again using fastboot oem lock and then wiping user data.
Proceed as follows:
1. Make sure tablet is off
2. Press power and Volume down simultaneously
3. Hold "Volume down", until you see the factory menu
4. Use "Volume down" to navigate to "Clear eMMC"
5. Use power button to select.
However, if you find replacement firmware somewhere, I'd be interested too, as mine was sold with an Android Lollipop 5.1 doctored to look like 7.0. I think I should be able to at least get Android 6.0 for this tablet.
After the reset bootloop, I need this flash file for me.
Please could you help?
Alk142 said:
I have a similar tablet, and accidentally softbricked it by doing fastboot oem unlock (I think...). In my case though, the screen did not stay black, but the Android Logo showed forever, and the user's screen never appeared.
What got it working again was locking it again using fastboot oem lock and then wiping user data.
Proceed as follows:
1. Make sure tablet is off
2. Press power and Volume down simultaneously
3. Hold "Volume down", until you see the factory menu
4. Use "Volume down" to navigate to "Clear eMMC"
5. Use power button to select.
However, if you find replacement firmware somewhere, I'd be interested too, as mine was sold with an Android Lollipop 5.1 doctored to look like 7.0. I think I should be able to at least get Android 6.0 for this tablet.
Click to expand...
Click to collapse
Please I have the same kind of device but mine is stuck on a guest user account and my notification, Developer options and a lot of stuff doesn't work.
Please I would be so grateful if you could dump your stock ROM for me so I could flash mine. Please bro, i have searched everywhere for the ROM but without success until I stumbled on this thread.
***Beware, not all KT107 are compatible with each others, make a backup first if you can and use at your own risk***
****This is for MT6580 with kernel:3.10.72+ , do not even try if you have different kernel or cpu****
I opened the casing of my tablet, here are the models number written on the mainboard:
directly on the board :
KT961C12_80_216_V3.0
on the sticker:
KT107_1+16_D2_31PIN_20170424
BOM:KT107C12_80_216_V3.0_1G 16G_RDA_GSM
四频_NB1_无按體_NDR_最产BOM_N20180928
*There might be mistakes in the chinese characters*
I have a full TWRP backup and the stock images files from a functional tablet with the same device number. My device was working but here's what I did:
1: Root with KingoRoot
KingoRoot: https://www.kingoapp.com/
2: Install Flashify
Flashify : https://play.google.com/store/apps/d...shify&hl=en_US
3: Download this TWRP build :
TWRP : https://mega.nz/#!27QUFQ5J!nj5WNmD8yMTULrS2lc90bk1qWhRs-xY6b_ou229BgYM
4: Install the TWRP image to recovery with flashify
5: Reboot to recovery ( on my device I hold "vol up" + "pwr" to get to the bootloader menu, then choose recovery)
6: Copy the stock twrp backup to your device and restore
Stock TWRP backup : https://mega.nz/#F!jJ83Fabb!raIOtZSsqyMboVbb_5sDVQ
***You won't be able to use this backup without TWRP installed***
If you need the stock img to try to restore from fastboot I have those too:
system.img:
https://mega.nz/#!qY0RlIBI!lxsxP2Jn7bdQW_0zKQ8eoEcsadj0w7kru_CKqqnM_bc
recovery.img:
https://mega.nz/#!mAEiASpD!lJAMH1OilJ68vSdeGuP_wBWT9roDQfEyokqILFnr_Fg
boot.img:
https://mega.nz/#!zAFQlAiK!RMzjBvFZFjdkqwDdJvk_V63hGBgT7fDKUegFls-YGiA
SP Flash Tools Compatible ROM and scatter file:
https://mega.nz/#!rB8T1KjS!qya-pScSPdAV5cWLfmD-KN1nlxgb0yzo2vVmGATXjRo
Thanks a lot, please could you make the scatter file?
fueg said:
I have a full TWRP backup and the stock images files from a functional tablet with the same device number. My device was working but here's what I did:
Thanks a lot Fueg, you have no idea how much I appreciate your sending these files, though I am yet to Flash them.
Please as I understand, the spflash tool requires the scatter file to be able to flash a ROM. Please could you make a scatter file for the phone too? I could have used fastboot to flash but my bootloader is not unlocked and I don't have access to my developer options to enable me unlock it neither could I install any apps on my phone as it is stuck in guest user mode.
I am just a novice in this stuff but if you have any other ways I could flash the ROM without needing a scatter file please could you tell me please?
Thanks you very again!!!
EDIT: Please all the links to the files are not working. It's asking for a decryption key saying the provided key is invalid and I should ask the link creator for the decryption keys. Please check and rectify.
Could you also share me your build.prop file for your phone as well for comparison with mine just to be sure I have similar specs.
Click to expand...
Click to collapse
Please all the links to the files are not working. It's asking for a decryption key saying the provided key is invalid and I should ask the link creator for the decryption keys. Please check and rectify.
Could you also share me your build.prop file for your phone as well for comparison with mine just to be sure I have similar specs.[/QUOTE said:
I updated the download links in my previous post it should hopefully work now.
If you need to flash a version that you can flash with SP Flash Tool I found one that works (everything works but my display is flipped 180 degree, that's an easy fix). I will add a link for it in my previous post with all the other files.
I don't have access to the buil.prop file right now but it is pretty much useless to check the tablet specs anyway because the chinese changed all they can to make it look better than it is :
Reported CPU: MT 6580 : 8 core # 2.5 Ghz
Real CPU: MT 6580 : 4 core # 1.3Ghz
Reported Storage : 64Gb
Real Storage : 16Gb (about 12Gb available)
Reported RAM : 4Gb
Real RAM : 1Gb
Reported Android Version : 6.0
Real Android Version : 5.1
The ROM for SP Flash Tool mostly fixes the fake infos except the Android version, it still reports Android 6.0 when in reality it is Android 5.1
Click to expand...
Click to collapse
Please so sorry, but the download link for the TWRP build still don't work.
fueg said:
I updated the download links in my previous post it should hopefully work now.
If you need to flash a version that you can flash with SP Flash Tool I found one that works (everything works but my display is flipped 180 degree, that's an easy fix). I will add a link for it in my previous post with all the other files.
I don't have access to the buil.prop file right now but it is pretty much useless to check the tablet specs anyway because the chinese changed all they can to make it look better than it is :
Reported CPU: MT 6580 : 8 core # 2.5 Ghz
Real CPU: MT 6580 : 4 core # 1.3Ghz
Reported Storage : 64Gb
Real Storage : 16Gb (about 12Gb available)
Reported RAM : 4Gb
Real RAM : 1Gb
Reported Android Version : 6.0
Real Android Version : 5.1
The ROM for SP Flash Tool mostly fixes the fake infos except the Android version, it still reports Android 6.0 when in reality it is Android 5.1
Click to expand...
Click to collapse
Thank you so very much Fueg, but please so sorry for being so disturbing but the download link for the TWRP build still don't work. All the others now work except the Link for only the custom TWRP recovery build which is the third Link counting from the top. I really need that custom TWRP recovery because the stock recovery is lame.
Please if you could just correct that too, I would finally get out of your hair hopefully!
Thanks again my friend.
EDIT: Please also add the link for the display 180 degree flipped fix you mentioned, I couldn't find it.
Thanks again for your assistance.
Aloydonez said:
Thank you so very much Fueg, but please so sorry for being so disturbing but the download link for the TWRP build still don't work. All the others now work except the Link for only the custom TWRP recovery build which is the third Link counting from the top. I really need that custom TWRP recovery because the stock recovery is lame.
Please if you could just correct that too, I would finally get out of your hair hopefully!
Thanks again my friend.
EDIT: Please also add the link for the display 180 degree flipped fix you mentioned, I couldn't find it.
Thanks again for your assistance.
Click to expand...
Click to collapse
No problem, I added the twrp img as attachment below. For the orientation fix you just have to change a line in build.prop
Look for the line "ro.sf.hwrotation=180"
Change it for "ro.sf.hwrotation=0" if your display is rotated 180 degrees
The first twrp works wit the first "stock" files and with the twrp backup, if you use the SP Flash Tools files you will need the second twrp
Please help, I just ran into serious trouble
fueg said:
No problem, I added the twrp img as attachment below. For the orientation fix you just have to change a line in build.prop
Look for the line "ro.sf.hwrotation=180"
Change it for "ro.sf.hwrotation=0" if your display is rotated 180 degrees
The first twrp works wit the first "stock" files and with the twrp backup, if you use the SP Flash Tools files you will need the second twrp
Click to expand...
Click to collapse
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Aloydonez said:
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Click to expand...
Click to collapse
Do you know the exact brand and model you have? There is a lot of variation under the name KT107 and they are not all compatible with each others. If you really want to be sure you can try to open the device and check the number written on the pcb, mine was on a sticker on the main board. If you are willing to do that send me the information and I can try to find a suitable ROM.
Did you make a backup of you device in SP Flash Tools before you flash the ROM, if you did you can try to restore it...
You can also try this firmware:
https://yadi.sk/d/Gis_kl1y3UjJQC
It's a ROM for another KT107 variant...
Thanks Fueg, this is the information you requested
fueg said:
Do you know the exact brand and model you have? There is a lot of variation under the name KT107 and they are not all compatible with each others. If you really want to be sure you can try to open the device and check the number written on the pcb, mine was on a sticker on the main board. If you are willing to do that send me the information and I can try to find a suitable ROM.
Did you make a backup of you device in SP Flash Tools before you flash the ROM, if you did you can try to restore it......
Click to expand...
Click to collapse
No I couldn't make any backup at all because I was stuck in guest user mode on the phone, so developer options wasn't available to me and MTKdroid tools could not detect the tablet.
Below are all the information I could get about the device. Thank you so very much for all your patience and assistance.
_____________________________________
(Below is what I found on the label on one of the heat sinks on the motherboard.)
TD_KT107_D2_1+16 31PIN-HNHBOE_M1D50-901
BOM:KT107C_A_V1.0_1G+16G_GSM B1_31PIN
MTKL20170818395
_____________________________________
( This below was printed on the PCB)
KT961C-V1.0 2016.07.29
_____________________________________
OS Properties
KERNEL: Linux version 3.10.72+ ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Wed Nov 9 18:16:15 CST 2016
CODENAME: REL
Mainboard: unknown
Bootloader: unknown
Manufacturer: JTY
BRAND: Padking
Model: Padking
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: KT107
DISPLAY: Padking_V01
FINGERPRINT: alps/full_KT107_NL/KT107_NL:5.1/LMY47I/1477364172:user/test-keys
Release= 6.0
HARDWARE: mt6580
ID: LMY47I
TAGS: test-keys
Radio= MOLY.WR8.W1449.MD.WG.MP.V23, 2016/03/18 15:22
_________________________________'_'___
(This below is the build properties)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47I
ro.build.display.id=Padking_V01
ro.build.version.incremental=1477364172
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.version.security_patch=2016-01-01
ro.build.version.base_os=
ro.build.date=2016年 10月 25日 星期二 10:57:29 CST
ro.build.date.utc=1477364249
ro.build.type=user
ro.build.user=azhuo
ro.build.host=azhuo-desktop
ro.build.tags=test-keys
ro.build.flavor=full_KT107_NL-user
ro.product.model=Padking
ro.product.brand=Padking
ro.product.name=KT107
ro.product.device=KT107
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=JTY
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mt6580
# ro.build.product is obsolete; use ro.product.device
ro.build.product=KT107
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=full_KT107_NL-user 5.1 LMY47I 1477364172 test-keys
ro.build.fingerprint=alps/full_KT107_NL/KT107_NL:5.1/LMY47I/1477364172:user/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/vsun/KT107_NL/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp
# USB BICR function
ro.sys.usb.bicr=no
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
# temporary enables NAV bar (soft keys)
qemu.hw.mainkeys=0
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=0
#ro.kernel.qemu.gles=0
ro.opengles.version=131072
#ro.boot.selinux=disable
# Disable dirty region for Mali
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=210
ro.mtk_default_ime=com.sohu.inputmethod.sogou.SogouIME
persist.sys.timezone=
ro.jty.version.release=Padking_MID-2016
ro.jty.showdev=true
ro.elink.gemini=true
#ro.operator.optr=CUST
ro.build.screen_size_inches=10.1
#lqh add for romtool
ro.romtool.jtynetworkType=2G
ro.romtool.homepage=www.google.com
ro.romtool.front.picturesize=1600x1200
ro.romtool.back.picturesize=2560x1920
ro.jty.data.expandNum=0.5
ro.jty.fat.expandNum=1.5
#ro.romtool.fake_userdata=4.00
#ro.romtool.fake_pcstorage=8.00
ro.romtool.fake_memory=1
ro.romtool.fake_lcd=1280x800
ro.romtool.cpu_platform=MT6580
ro.romtool.cpu_corenumber=4
ro.romtool.cpu_frequency=1500.00
ro.romtool.showAddInfo=false
ro.romtool.fontsize=1.08
ro.romtool.screenbrightness=170
ro.romtool.screenofftimeout=60
ro.romtool.hlimit=true
ro.romtool.fat.name=Padking
#lqh add end
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
ro.mediatek.chip_ver=S01
ro.mediatek.version.release=KT107_L1_20160428
ro.mediatek.platform=MT6580
ro.telephony.sim.count=2
persist.radio.default.sim=0
persist.radio.multisim.config=dsds
persist.md.perm.checked=to_upgrade
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=270
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
mediatek.wlan.chip=CONSYS_MT6735
mediatek.wlan.module.postfix=_consys_mt6735
ril.radiooff.poweroffMD=0
ro.frp.pst=/dev/block/platform/mtk-msdc.0/by-name/frp
ro.mediatek.version.branch=L1.MP6
ro.mediatek.version.sdk=4
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r2
ro.com.google.clientidbase=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.ms=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.yt=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.am=alps-full_KT107_NL-{country}
ro.com.google.clientidbase.gmm=alps-full_KT107_NL-{country}
ro.mtk_gemini_support=1
ro.mtk_audio_profiles=1
ro.mtk_audenh_support=1
ro.mtk_lossless_bt_audio=1
ro.mtk_besloudness_support=1
ro.mtk_bessurround_support=1
ro.mtk_gemini_enhancement=1
ro.mtk_wapi_support=1
ro.mtk_bt_support=1
ro.mtk_wappush_support=1
ro.mtk_agps_app=1
ro.mtk_voice_ui_support=1
ro.mtk_voice_unlock_support=1
ro.mtk_voice_contact_support=1
ro.mtk_wlan_support=1
ro.mtk_gps_support=1
ro.mtk_omacp_support=1
ro.mtk_search_db_support=1
ro.mtk_dialer_search_support=1
ro.mtk_dhcpv6c_wifi=1
ro.have_aacencode_feature=1
ro.mtk_fd_support=1
ro.mtk_oma_drm_support=1
ro.mtk_cta_drm_support=1
ro.mtk_widevine_drm_l3_support=1
ro.mtk_eap_sim_aka=1
ro.mtk_fm_recording_support=1
ro.mtk_audio_ape_support=1
ro.mtk_flv_playback_support=1
ro.mtk_fd_force_rel_support=1
ro.mtk_wmv_playback_support=1
ro.mtk_send_rr_support=1
ro.mtk_rat_wcdma_preferred=1
ro.mtk_tb_call_speaker_on=1
ro.mtk_emmc_support=1
ro.mtk_tetheringipv6_support=1
ro.mtk_enable_md1=1
ro.mtk_flight_mode_power_off_md=1
ro.mtk_pq_support=2
ro.mtk_miravision_support=1
ro.mtk_miravision_image_dc=1
ro.mtk_wifi_mcc_support=1
ro.mtk_system_update_support=1
ro.mtk_sim_hot_swap=1
ro.mtk_thumbnail_play_support=1
ro.mtk_bip_scws=1
ro.mtk_world_phone_policy=0
ro.mtk_perfservice_support=1
ro.mtk_cta_set=1
ro.mtk_mobile_management=1
ro.mtk_antibricking_level=2
ro.mtk_cam_mfb_support=0
ro.mtk_cam_mav_support=1
ro.sim_refresh_reset_by_modem=1
ro.mtk_live_photo_support=1
ro.mtk_motion_track_support=1
ro.mtk_privacy_protection_lock=1
ro.mtk_bg_power_saving_support=1
ro.mtk_bg_power_saving_ui=1
ro.have_aee_feature=1
ro.sim_me_lock_mode=0
ro.mtk_dual_mic_support=0
ro.mtk_is_tablet=0
ro.mtk_voice_extension_support=1
wfd.dummy.enable=1
ro.mediatek.project.path=device/vsun/KT107_NL
persist.mtk.wcn.combo.chipid=-1
service.wcn.driver.ready=no
ro.com.android.mobiledata=false
persist.radio.mobile.data=0,0
persist.meta.dumpdata=0
persist.sys.dex2oat_white_list=com.isoftdimension.co.id.sixpay:com.instagram.android:
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=div
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Aloydonez said:
No I couldn't make any backup at all because I was stuck in guest user mode on the phone, so developer options wasn't available to me and MTKdroid tools could not detect the tablet.
Below are all the information I could get about the device. Thank you so very much for all your patience and assistance.
. . .
. . .
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
maybe this:
https://cloud.mail.ru/public/4XAT/4nnv5t5WY
or this one
https://drive.google.com/file/d/19pCWODtS3BdN-PGRQVXt26taGboBJCsp/view
you can also try those:
http://4pda.ru/forum/index.php?showtopic=803557&st=0#Spoil-58377265-8
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware, I have not been able to find an exact match...
Anyway if you keep trying different firmware chances are that you will eventually find one that is compatible with your device (in my case I had to try about 10 and the one that works was not an exact match but it still works 100%)
you can also try those:
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware said:
Thank you so much for your assistance. Now I will get to work.
I will let you know if I am successful. Thanks!
Click to expand...
Click to collapse
Aloydonez said:
you can also try those:
(start with those that have a similar name)
you might have trouble with the display (black screen) with any of those firmware said:
Thank you so much for your assistance. Now I will get to work.
I will let you know if I am successful. Thanks!
Click to expand...
Click to collapse
Best of luck to you, I hope something works!
Click to expand...
Click to collapse
Aloydonez said:
Hi Fueg it's me again, please I need to pick your brain a little bit more.
So I tried flashing the ROM you shared using spflash tool using the "Download only option" but it kept giving me a not enough space errors. So I searched around the net and I found a lot of people saying using the "Format all+Download" options solved the not enough space errors, then I chose that option.
The ROM downloaded alright and I could hear the phone boot to home screen, and pressing the volume keys makes the normal sounds but the screen is filled with black and white colored strips or just blank.
I think maybe the formatting whipped the LCD screen drivers but shouldn't it have worked since I know the ROM was ok? I also thought the LCD screen driver is contained inside the ROM ? Is it not?
Please can this be remedied or is the phone finally dead?
Please help me with some suggestions or a fix in any way you can I would really appreciate. Thank you very much.
Click to expand...
Click to collapse
The display drivers are indeed contained within the ROM. Apparently your display is not the same then the one I have. If you have a backup of your previous firmware you can look for a tutorial on haw to extract the files you need (inside boot.img and system.img), and another tutorial on how to port ROM for mediatek 6580.
If you don't have a backup you will have to try to find a ROM with the display working to have the drivers you need ..
flashing twrp
hello fueg
thank you for your efforts
well i need to flash twrp file but i could not root my tablet. this give me one option ;to use sp flash tool. my questions to you
1- i review the scatter file you submitted and compare it to the one i see when i connect my device; there are many differences in start address and size; so which one i should use?
2- since iam flashing only the twrp file in recovery.img section; do i need to includes other sections in the scatter file?