Database Info

[Q] the default build.prop for g2x

Can anyone post the G2x's stock build.prop? There are a few lines I need to edit back to the original and cannot seem to locate the original lines anywhere on the internet. Everyone here seems knowledgeable and helpful so here is hoping. Thanks.

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRG83G
ro.build.display.id=FRG83G
ro.build.version.incremental=2ED2B0648C
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.2
ro.build.date=2011. 03. 27. (일) 10:55:38 KST
ro.build.date.utc=1301190938
ro.build.type=user
ro.build.user=sp9pm_9
ro.build.host=sp9pm2pl3
ro.build.tags=release-keys
ro.product.model=LG-P999
ro.product.brand=lge
ro.product.name=lge_star
ro.product.device=p999
ro.product.board=p999
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=lge
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p999
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=star-user 2.2.2 FRG83G 2ED2B0648C release-keys
ro.build.fingerprint=lge/lge_star/p999/p999:2.2.2/FRG83G/lgp999-V10f.2ED2B0648C:user/release-keys
ro.product.rat=WCDMA_ONLY
# end build properties
rild.libargs=-d /dev/chnlat10
# 20100720, [email protected], Add haptic feedback of touch key
# Touch Key: SEARCH, BACK, HOME, MENU
ro.lge.touchkey=BACK|SEARCH|HOME|MENU
ro.build.lge.version.release=LG-P999-V10f
ro.build.lge.version.hidden=0
ro.opengles.version=131072
keyguard.no_require_sim=true
persist.service.pcsync.enable=0
persist.service.lgospd.enable=0
dalvik.vm.heapsize=40m
rilswitch.vendorlibpath=/system/lib/lge-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=Acoustic_Guitar.ogg
ro.config.alarm_alert=Alarm_Beep01.ogg
ro.config.ringtone=T-Jingle.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.2_r9
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.yt=android-lge
ro.com.google.clientidbase.am=android-tmobile-us
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.media.enc.hprof.vid.bps=4000000
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.enc.hprof.codec.vid=h264
ro.media.enc.hprof.vid.fps=30
ro.browser.useragent=0
persist.service.mount.umsauto=1
ro.sf.lcd_density=240
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/lge-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Sent from my LG-P999 using XDA App

You are a lifesaver.

please post in the proper section next time. should have been in "general"

Thanks for posting. This is exactly what I was looking for also.

I've changed this file build.prop in my LG and the device is corupted now !!
I want to replace this file but I did not how ? I don't install a recovery program in the device I don know how to enter to device files without these programs ?

Mustafa Hamza said:
I've changed this file build.prop in my LG and the device is corupted now !!
I want to replace this file but I did not how ? I don't install a recovery program in the device I don know how to enter to device files without these programs ?
Click to expand...
Click to collapse
Install ADB on your computer (look elsewhere on how to do this)
Connect phone to computer via USB
type "adb remount" to mount phone file system in read-write mode
type "adb push C:\path\to\your\good\build.prop /system
DONE

Nice I'm gonna put some of this on my thrill

[9001][Recovery] Fixed FeaMod V1.4 [FINAL PROPER] [No BootLoops] [NonOC] [NonUV]

This is a fixed version of manveru0's FeaMod recovery V1.4 (aka CWM recovery v 5.5.0.4) so all credits go to him.
Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this piece of software and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !
Terms of use: Remember the power of reading ! If you can't find some particular information on the first page use the search function, it is your best friend.
Besides there are even guides and tutorials all over the forum and in most cases your question was already answered.
If you take a moment and read through the WHOLE post below and a few more moments to read some of all the stuff in other device related threads of this forum, you will find ALL you need just there.
It's not invisible so you CAN find it. And forum rules and good manners tell you to do it exactly like this. And I WILL ignore every question that is already answered here.
Obey the rules !
Recovery feature list
- the internally used kernel to boot CWM recovery is not overclocked and not undervolted and uses Samsung's stock kernel settings so it should work on any i9001 phone (it's different from manveru0's release and I already released this fix in January in the original FeaMod thread)
- reworked the integrated script in recovery startup sequence that takes care about the recovery reboot issue automatically so no more rebooting into recovery again and again once and for all (reported to work finally by wintel_mac, thanks for testing all releases)
- the CWM 5.5.0.4 recovery itself remains totally untouched and is the very same as in FeaMod V1.4; for any more information on that please refer to the original FeaMod thread here:
http://forum.xda-developers.com/showthread.php?t=1331164
- the package includes only the recovery image so anything else on your phone remains untouched including your boot kernel; the recovery partition has its own kernel integrated which is only used for booting CWM recovery, in all other cases your original kernel in the boot partition is used - primarily for booting android that is
​
This version is meant for use with ANY i9001 ROM including stock ROMs, custom ROMs and even AOSP ROMs as well (as soon as the latter are actually available)
Install instructions:
1. If you don't have already any CWM version (FeaMod Recovery) install V1.2 via Odin first. If you never heard of that learn all about it here:
http://forum.xda-developers.com/showthread.php?t=1331164
2. Now make a complete nandroid backup of your phone with CWM
3. Download the attached CWM zip package
4. Copy it to your internal sdcard
5. In CWM choose "install zip from sdcard", then "choose zip from internal sdcard"
6. Select the downloaded file "FeaModV1.4_Fixed_NoBootLoop_NonOC_NonUV.zip"
7. Confirm install with "Yes"
8. Wait till you see the message "Reboot to use Fixed FeaMod V1.4 !"
9. Do so like the message says.
10. On first reboot the fix to cure the recovery reboot wasn't yet executed so you will end up in recovery once again (if your phone is affected with that issue) !
11. So you have to reboot into system once again and from now on everything will be fine, promised That is if you installed it properly and exactly like described above.
​
If anything went wrong during install just try again.
If you can't boot into recovery anymore just install FeaMod 1.2 via Odin again.
If you want to install Fixed FeaMod V1.4 directly via odin just extract the recovery.img only from the zip file and tar it. Then flash it via Odin in one package mode. If you don't know how to do that refer to the flash guides in this i9001 subforum or use the above described method only. If you still can't handle anything of that don't use FeaMod/CWM at all, you will most probably brick your phone with it.
The experienced users (ONLY !!!) can also use dd of course to flash the recovery.img directly to the appropriate partition
If you got severe errors AND didn't make a backup because you knew better than the developer don't even dare to beg for help.
If you encounter any other errors report them here but be sure that this is no feature or problem that was already described above.

reserved...

reserved ...

Sorry, but I'm the show stopper... the phone still boots into recovery.
Still need to wipe mmcblk0p14 to get out of this loop

Thanks ! Works perfect for me
I dded the img

wintel_mac said:
Sorry, but I'm the show stopper... the phone still boots into recovery.
Still need to wipe mmcblk0p14 to get out of this loop
Click to expand...
Click to collapse
Ooops, this means the script isn't actually executed. Couldn't test it properly since my phone isn't affected by the issue. Will review that immediately.

Looks like im the wrong person to test this out
It always worked fine for me

nail16 said:
Thanks ! Works perfect for me
I dded the img
Click to expand...
Click to collapse
Which would mean the script works but the CWM install routine doesn't.
@wintelmac: can you please attach the default.prop file that shows up when you boot into recovery ?
Code:
adb shell "cat /default.prop" > default.prop

nail16 said:
Looks like im the wrong person to test this out
It always worked fine for me
Click to expand...
Click to collapse
Funny, couldn't you say that earlier ?

couldn't you refresh your page earlier ?
Should i post my last_log of the recovery ?

nail16 said:
couldn't you refresh your page earlier ?
Click to expand...
Click to collapse
no, because I was already in posting mode
nail16 said:
Should i post my last_log of the recovery ?
Click to expand...
Click to collapse
Won't help since you are not affected by the issue anyway. New version already uploaded, wintel_mac can test it now.

It's kinda funny your's and my phone are not effected by the recovery bug,
but you'r kernel still managed to screw up my sdcard

nail16 said:
It's kinda funny your's and my phone are not effected by the recovery bug,
but you'r kernel still managed to screw up my sdcard
Click to expand...
Click to collapse
Which only proves what I said: no two phones are exactly the same

Yep, here it is
Code:
C:\Users\User>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.035
237 test-keys
ro.build.version.incremental=eng.root.20120216.035237
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Feb 16 04:20:00 CET 2012
ro.build.date.utc=1329362400
ro.build.type=eng
ro.build.user=root
ro.build.host=ANKObian
ro.build.tags=test-keys
ro.product.model=GT-I9001
ro.product.brand=Samsung
ro.product.name=full_galaxysplus
ro.product.device=galaxysplus
ro.product.board=qcom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxysplus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.03
5237 test-keys
ro.build.fingerprint=Samsung/full_galaxysplus/galaxysplus:2.3.7/GINGERBREAD/eng.
root.20120216.035237:eng/test-keys
ro.cm.device=galaxysplus
# end build properties
#
# system.prop for galaxysplus
#
# from init.rc
#service.brcm.bt.srv_active=0
#service.brcm.bt.hcid_active=0
#service.brcm.fm.activation=0
#ro.rfkilldisabled=0
# from build.prop
#
# system.prop for surf
#
debug.sf.hw=1
dalvik.vm.heapsize=64m
ro.sf.lcd_density=240
#ro.dev.dmm=1
#dev.dmm.dpd.trigger_delay=30
#
# system props for the cne module
#
#persist.cne.UseCne=vendor
#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
#
#lpa.decode=false
#ro.hdmi.enable=true
#
# system props for the data modules
#
#ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=16
#
# system props for the MM modules
#
#media.stagefright.enable-player=true
#media.stagefright.enable-meta=false
#media.stagefright.enable-scan=false
#media.stagefright.enable-http=true
#media.stagefright.enable-rtsp=false
# Samsung USB default mode
#persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.supplicant_scan_interval=15
#ro.secdevenc=true
dalvik.vm.dexopt-flags=m=y
#
# ADDITIONAL_BUILD_PROPERTIES
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d/dev/ttyS0
wifi.interface=eth0
ro.opengles.version=131072
ro.config.ehrpd=true
ro.telephony.ril_class=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
mobiledata.interfaces=pdp0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #

I'm still using you'r kernel with a dead sdcard inside my phone

nail16 said:
I'm still using you'r kernel with a dead sdcard inside my phone
Click to expand...
Click to collapse
Please, don't crosspost^^ It's about the recovery (which uses not even the skyhigh kernel), and not the kernel so it's simply uuuuuuseless here

wintel_mac said:
Yep, here it is
Click to expand...
Click to collapse
OK, that's the right one, so the install routine works. Which is actually the only part that I could test on my own phone and it worked properly
A new version is already online, can you test that please ?

nail16 said:
I'm still using you'r kernel with a dead sdcard inside my phone
Click to expand...
Click to collapse
Did you read this already ?
http://forum.xda-developers.com/showpost.php?p=24307493&postcount=213

Code:
V:\Downloads>adb push sky-new-recovery.img /emmc/flash-backup/
2174 KB/s (5083136 bytes in 2.283s)
V:\Downloads>adb shell
~ # mount /emmc
mount /emmc
~ # dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
9928+0 records in
9928+0 records out
5083136 bytes (4.8MB) copied, 2.363983 seconds, 2.0MB/s
~ #
Rebootet... went back into CWM. Rebooted once more... CWM. And just another reboot (you may guess...) CWM.
Code:
~ # cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.035
237 test-keys
ro.build.version.incremental=eng.root.20120216.035237
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Feb 16 04:20:00 CET 2012
ro.build.date.utc=1329362400
ro.build.type=eng
ro.build.user=root
ro.build.host=ANKObian
ro.build.tags=test-keys
ro.product.model=GT-I9001
ro.product.brand=Samsung
ro.product.name=full_galaxysplus
ro.product.device=galaxysplus
ro.product.board=qcom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxysplus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.03
5237 test-keys
ro.build.fingerprint=Samsung/full_galaxysplus/galaxysplus:2.3.7/GINGERBREAD/eng.
root.20120216.035237:eng/test-keys
ro.cm.device=galaxysplus
# end build properties
#
# system.prop for galaxysplus
#
# from init.rc
#service.brcm.bt.srv_active=0
#service.brcm.bt.hcid_active=0
#service.brcm.fm.activation=0
#ro.rfkilldisabled=0
# from build.prop
#
# system.prop for surf
#
debug.sf.hw=1
dalvik.vm.heapsize=64m
ro.sf.lcd_density=240
#ro.dev.dmm=1
#dev.dmm.dpd.trigger_delay=30
#
# system props for the cne module
#
#persist.cne.UseCne=vendor
#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
#
#lpa.decode=false
#ro.hdmi.enable=true
#
# system props for the data modules
#
#ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=16
#
# system props for the MM modules
#
#media.stagefright.enable-player=true
#media.stagefright.enable-meta=false
#media.stagefright.enable-scan=false
#media.stagefright.enable-http=true
#media.stagefright.enable-rtsp=false
# Samsung USB default mode
#persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.supplicant_scan_interval=15
#ro.secdevenc=true
dalvik.vm.dexopt-flags=m=y
#
# ADDITIONAL_BUILD_PROPERTIES
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d/dev/ttyS0
wifi.interface=eth0
ro.opengles.version=131072
ro.config.ehrpd=true
ro.telephony.ril_class=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
mobiledata.interfaces=pdp0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #

wintel_mac said:
Code:
V:\Downloads>adb push sky-new-recovery.img /emmc/flash-backup/
2174 KB/s (5083136 bytes in 2.283s)
V:\Downloads>adb shell
~ # mount /emmc
mount /emmc
~ # dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
9928+0 records in
9928+0 records out
5083136 bytes (4.8MB) copied, 2.363983 seconds, 2.0MB/s
~ #
Rebootet... went back into CWM. Rebooted once more... CWM. And just another reboot (you may guess...) CWM.
Code:
~ # cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.035
237 test-keys
ro.build.version.incremental=eng.root.20120216.035237
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Feb 16 04:20:00 CET 2012
ro.build.date.utc=1329362400
ro.build.type=eng
ro.build.user=root
ro.build.host=ANKObian
ro.build.tags=test-keys
ro.product.model=GT-I9001
ro.product.brand=Samsung
ro.product.name=full_galaxysplus
ro.product.device=galaxysplus
ro.product.board=qcom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxysplus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.03
5237 test-keys
ro.build.fingerprint=Samsung/full_galaxysplus/galaxysplus:2.3.7/GINGERBREAD/eng.
root.20120216.035237:eng/test-keys
ro.cm.device=galaxysplus
# end build properties
#
# system.prop for galaxysplus
#
# from init.rc
#service.brcm.bt.srv_active=0
#service.brcm.bt.hcid_active=0
#service.brcm.fm.activation=0
#ro.rfkilldisabled=0
# from build.prop
#
# system.prop for surf
#
debug.sf.hw=1
dalvik.vm.heapsize=64m
ro.sf.lcd_density=240
#ro.dev.dmm=1
#dev.dmm.dpd.trigger_delay=30
#
# system props for the cne module
#
#persist.cne.UseCne=vendor
#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
#
#lpa.decode=false
#ro.hdmi.enable=true
#
# system props for the data modules
#
#ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=16
#
# system props for the MM modules
#
#media.stagefright.enable-player=true
#media.stagefright.enable-meta=false
#media.stagefright.enable-scan=false
#media.stagefright.enable-http=true
#media.stagefright.enable-rtsp=false
# Samsung USB default mode
#persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.supplicant_scan_interval=15
#ro.secdevenc=true
dalvik.vm.dexopt-flags=m=y
#
# ADDITIONAL_BUILD_PROPERTIES
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d/dev/ttyS0
wifi.interface=eth0
ro.opengles.version=131072
ro.config.ehrpd=true
ro.telephony.ril_class=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
mobiledata.interfaces=pdp0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #
Click to expand...
Click to collapse
Hm, this puzzles me a little bit and will become quite a challenge more than I thought. But I'm still confident that I will work it out soon

s3 clone mt6575 vietnam rom help

i got a phone recently through trade. its a s3 clone made in vietnam. i managed to root and install cwm on it. but after flashing a custom rom for another s3 mt6575 i found out that the rom isnt compatible and thus left me with a messed up partition. i flashed back to cwm restore and all is working fine until i decided to fix the partition (i originally have 2 gb internal which then was divided into 4 500mb parts because of a wrong rom) i accidentally flashed the wrong preloader and dsp_bl. it wont boot but with lots of rom downloads i found the right preloader and dsp_bl which brought my phone back to life. the only problem is i have 2 working roms for my phone but both cant detect my sim cards. i tried copying nvram files and even porting said roms replacing modem.img etc. but nothing would allow my phone to detect my sim cards.
my last resort is to find a stock rom for my device to fix it. i do have backups for cwm but none of it would restore it back. the backups were workinbg before but after flashing wrong preloader and bringing the phone back to life it wont restore properly. i always end up stuck in black screen after restore. even tried proting roms using my cwm restore but still nothing. even tried tinkering with the restore but still nothing. im hoping i could restore it if someone who has the same phone could help and send me a working stock or even custom rom for the same phone. here is my build.prop from my cwm recovery
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D.GT-HI9300ZSALE9
ro.build.version.incremental=eng.root.1369053524
ro.custom.build.version=1369053524
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.2.1
ro.build.date=Mon May 20 20:42:31 CST 2013
ro.build.date.utc=1369053751
ro.build.type=user
ro.build.user=root
ro.build.host=wwd
ro.build.tags=test-keys
ro.product.model=GT-I9300
ro.product.brand=samsung
ro.product.name=GT-I9300
ro.product.device=GT-I9300
ro.product.board=GT-I9300
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=GT-I9300
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=SMDK4x12
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9300
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=mobitek75_ics2-user 4.0.4 IMM76D eng.root.1369053524 test-keys
ro.build.fingerprint=alps/mobitek75_ics2/mobitek75_ics2:4.0.4/IMM76D/1369053524:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.ICS2.MP.V1.20
ro.mediatek.platform=MT6575
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.ICS2.MP
# end mediatek build properties
#
# 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}
# MTK, TeChien {
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.codec.vid=m4v
ro.media.enc.hprof.vid.width=720
ro.media.enc.hprof.vid.height=480
ro.media.enc.hprof.vid.fps=30
ro.media.enc.hprof.vid.bps=3400000
ro.media.enc.hprof.codec.aud=amrnb
ro.media.enc.hprof.aud.bps=12200
ro.media.enc.hprof.aud.ch=1
ro.media.enc.hprof.aud.hz=8000
ro.media.enc.mprof.file.format=3gp
ro.media.enc.mprof.codec.vid=m4v
ro.media.enc.mprof.vid.width=352
ro.media.enc.mprof.vid.height=288
ro.media.enc.mprof.vid.fps=30
ro.media.enc.mprof.vid.bps=990000
ro.media.enc.mprof.codec.aud=amrnb
ro.media.enc.mprof.aud.bps=12200
ro.media.enc.mprof.aud.ch=1
ro.media.enc.mprof.aud.hz=8000
ro.media.enc.lprof.file.format=3gp
ro.media.enc.lprof.codec.vid=h263
ro.media.enc.lprof.vid.width=176
ro.media.enc.lprof.vid.height=144
ro.media.enc.lprof.vid.fps=30
ro.media.enc.lprof.vid.bps=384000
ro.media.enc.lprof.codec.aud=amrnb
ro.media.enc.lprof.aud.bps=12200
ro.media.enc.lprof.aud.ch=1
ro.media.enc.lprof.aud.hz=8000
# MTK, TeChien }
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=128m
# Encrypt phone function
ro.crypto.tmpfs_options=mode=0771,uid=1000,gid=1000
ro.crypto.fs_type=ext4
ro.crypto.fs_real_blkdev=/[email protected]
ro.crypto.fs_mnt_point=/data
ro.crypto.fs_options=noauto_da_alloc
ro.crypto.fs_flags=0x00000406
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
# USB Config Type
ro.sys.usb.storage.type=mtp,mass_storage
# 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,mass_storage
#
# ADDITIONAL_BUILD_PROPERTIES
#
fmradio.driver.chip=3
ril.external.md=1
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
curlockscreen=2
ro.mediatek.gemini_support=true
drm.service.enabled=true
fmradio.driver.enable=1
mediatek.wlan.chip=MT6628
mediatek.wlan.module.postfix=_mt6628
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
hopefully someone has the same phone and could upload a stock firmware for me, im in dire need of help. thanks and god bless

up, anyone, help..

[Completed] [Q] access file system via usb on softbricked mtk device

[Q] Social drive
after gaining root acess i was figiting around with vold.fstab and
somehow either converted the external EMMC into the internal Storage
or maybe hidden or moved/removed the external EMMC mount point
lost power booted back up and its stuck on the second screen after booting
the first screen is the manufactures boot logo the second is the word android
in silver letters that have light running across, now im trying to connect to my sd
card to flash my rom back but in cwm all the items i see arent items that are actually
on the physical sd card and attempts to format cache/data say sucess but rebooting
to recovery the same files are there like the format didnt delete anything im stuck
at this point needing advice please thanks
social drive
dual sim card
model number
says "drive"???
android version
4.2.2
baseband version
moly.wr8.w1315.md.wg.mp.v1.p4,
2013/10/17 17:12
kernel version
3.4.5
[email protected] #1Thu Sep 12
19:16:33 cst 2013
build number
Social-Drive-v3.12.24a-FM-BT
Found this under build prop file
ro.sw.version=Social-3251-CE-QB14D-M536-6572V1.0.5
ro.sw.version.incremental=B06
ro.custom.btname = Drive
ro.build.id=JDQ39
ro.build.display.id=Social-Drive-V3.12.24a-FM-BT
ro.build.version.incremental=eng.builder59.1387961 233
ro.custom.build.version=1387961233
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Dec 25 16:48:55 CST 2013
ro.build.date.utc=1387961335
ro.build.type=user
ro.build.user=builder59
ro.build.host=eastaeon-desktop
ro.build.tags=test-keys
ro.product.model=Drive
ro.product.brand=Social
ro.product.name=Drive
ro.product.device=Social
ro.product.board=Drive
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Social
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Social
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Social-user 4.2.2 JDQ39 eng.builder59.1387961233 test-keys
ro.build.fingerprint=Social/Social/Social:4.2.2/JDQ39/1387961233:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=Social-Drive-V3.12.24a-FM-BT
ro.mediatek.platform=MT6572
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB3.MP
ro.mediatek.version.sdk=1
# end mediatek build properties
#
# 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
#
ro.opengles.version=131072

Hi
Thanks for writing to us at XDA Assist. Please take a look at this thread:
[GUIDE] How to 'unbrick' your Mediatek MT65xx

No response in two days, thread closed, thanks.

How to root my Oukitel K10000 Pro ?

Hi,
I have spend 2 days to try root my Oukitel K10000 Pro.
I have unlock OEM fastboot.
I m sure it's OK, because I can flash a recovery file with "fastboot flash recovery recovery.img" (but this is a bad recovery, it's reboot after 5S I think a Kernel Panic [nothing on the screen apear when it's try to boot])
I have tried SF Flash boot (Windows and Linux) I have many errors
I have tried a lot of APK and software like Framaroot AutoRoot some chines with spywares etc ...
My phone can boot actualy in the Original OS Android 7, Fastboot, but now, no recovery (I have find olso a test mode).
I realy need to root it if I use it. Actualy I have a working brick, but cannot use it !
Some file can help:
Code:
K10000_Pro:/ $ uname -a
Linux localhost 3.18.35+ #1 SMP PREEMPT Thu Jun 1 13:42:41 CST 2017 aarch64
K10000_Pro:/ $
Code:
K10000_Pro:/ $ cat /proc/cpuinfo
Processor : AArch64 Processor rev 2 (aarch64)
processor : 0
model name : AArch64 Processor rev 2 (aarch64)
BogoMIPS : 26.00
BogoMIPS : 26.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 2
Hardware : MT6750T
K10000_Pro:/ $
Code:
K10000_Pro:/ $ cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.display.id=OUKITEL_K10000_Pro_V1.0_20170531
ro.build.version.incremental=1496290182
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=2017年 06月 01日 星期四 12:09:35 CST
ro.build.date.utc=1496290175
ro.build.type=user
ro.build.user=release
ro.build.host=release14
ro.build.tags=release-keys
ro.build.flavor=full_hct6750_66_n-user
ro.product.model=K10000 Pro
ro.product.brand=OUKITEL
ro.product.name=K10000_Pro
ro.product.device=K10000_Pro
ro.product.board=K10000_Pro
# 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=OUKITEL
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=mt6750
# ro.build.product is obsolete; use ro.product.device
ro.build.product=hct6750_66_n
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=full_hct6750_66_n-user 7.0 NRD90M 1496290182 release-keys
ro.build.fingerprint=OUKITEL/full_hct6750_66_n/hct6750_66_n:7.0/NRD90M/1496290182:user/release-keys
ro.build.characteristics=default
# end build properties
#
# from device/haocheng/hct6750_66_n/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=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
#
ro.opengles.version=196608
#ro.kernel.qemu=1
#ro.kernel.qemu.gles=0
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
# 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=1
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=1
#ro.kernel.qemu.gles=0
#ro.boot.selinux=disable
ro.sf.lcd_density=480
# performance
ro.mtk_perf_simple_start_win=1
ro.mtk_perf_fast_start_win=1
ro.mtk_perf_response_time=1
# MAL
persist.mal.mode=0
persist.sys.gestureup = false
persist.sys.gesturedown = false
persist.sys.gestureleft = false
persist.sys.gesturedouble = false
persist.sys.gestureright = false
persist.sys.gesturec = false
persist.sys.gesturev = false
persist.sys.gesturem = false
persist.sys.gesturee = false
persist.sys.gestureo = false
persist.sys.gesturew = false
persist.sys.gesturez = false
persist.sys.gestures = false
persist.sys.gestureonoff = false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=Lovely.ogg
ro.config.notification_sound=Default.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
ro.mediatek.chip_ver=S01
ro.mediatek.platform=MT6755
ro.telephony.sim.count=2
persist.radio.default.sim=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.mtk_cam_lomo_support=1
ro.sf.hwrotation=0
persist.radio.fd.counter=150
persist.radio.fd.off.counter=50
persist.radio.fd.r8.counter=150
persist.radio.fd.off.r8.counter=50
drm.service.enabled=false
fmradio.driver.enable=1
ro.mtk_rebootmeta_support=0
mtk.eccci.c2k=enabled
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_MT6755
mediatek.wlan.module.postfix=_consys_mt6755
ril.read.imsi=1
ril.radiooff.poweroffMD=0
ro.frp.pst=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp
ro.mtk_protocol1_rat_config=Lf/W/G
ro.mediatek.version.branch=alps-mp-n0.mp7
ro.mediatek.version.release=OUKITEL_K10000_Pro_V1.0_20170531
ro.mediatek.version.sdk=4
ro.num_md_protocol=2
persist.radio.multisim.config=dsds
ro.mtk_besloudness_support=1
ro.mtk_wapi_support=1
ro.mtk_bt_support=1
ro.mtk_wappush_support=1
ro.mtk_agps_app=1
ro.mtk_audio_tuning_tool_ver=V2.2
ro.mtk_matv_analog_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_eap_sim_aka=1
ro.mtk_fm_recording_support=1
ro.mtk_send_rr_support=1
ro.mtk_emmc_support=1
ro.mtk_tetheringipv6_support=1
ro.telephony.default_network=9,9
ro.mtk_shared_sdcard=1
ro.mtk_enable_md1=1
ro.mtk_afw_support=1
ro.mtk_flight_mode_power_off_md=1
ro.mtk_pq_support=2
ro.mtk_pq_color_mode=1
ro.mtk_blulight_def_support=1
ro.mtk_wfd_support=1
ro.mtk_wfd_sink_support=1
ro.mtk_wfd_sink_uibc_support=1
ro.mtk_wifi_mcc_support=1
ro.mtk_sim_hot_swap=1
ro.mtk_bip_scws=1
ro.mtk_world_phone_policy=0
ro.mtk_md_world_mode_support=1
ro.mtk_perfservice_support=1
ro.mtk_owner_sdcard_support=1
ro.mtk_sim_hot_swap_common_slot=1
ro.mtk_cta_set=1
ro.mtk_cam_mfb_support=3
ro.mtk_lte_support=1
ro.mtk_rild_read_imsi=1
ro.sim_refresh_reset_by_modem=1
ro.mtk_external_sim_only_slots=0
ro.mtk_hotknot_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_pow_perf_support=1
persist.mtk_nlp_switch_support=1
persist.mtk_vilte_support=0
ro.mtk_vilte_ut_support=0
ro.mediatek.hotknot.module=GT1XX
wfd.dummy.enable=1
wfd.iframesize.level=0
ro.mediatek.project.path=device/haocheng/hct6750_66_n
persist.mtk.wcn.combo.chipid=-1
persist.mtk.wcn.patch.version=-1
persist.mtk.wcn.dynamic.dump=0
service.wcn.driver.ready=no
service.wcn.coredump.mode=0
persist.mtk.connsys.poweron.ctl=0
persist.mtk_epdg_support=1
ro.com.android.mobiledata=false
persist.radio.mobile.data=0,0
persist.meta.dumpdata=0
ro.mtk_deinterlace_support=1
ro.mtk_modem_monitor_support=1
persist.radio.mtk_ps2_rat=W/G
ro.boot.opt_md1_support=14
ro.boot.opt_lte_support=1
persist.log.tag.AT=I
persist.log.tag.RILMUXD=I
persist.log.tag.RILC-MTK=I
persist.log.tag.RILC=I
persist.log.tag.RfxMainThread=I
persist.log.tag.RfxRoot=I
persist.log.tag.RfxRilAdapter=I
persist.log.tag.RfxController=I
persist.log.tag.RILC-RP=I
persist.log.tag.RIL-DATA=D
ro.boot.opt_eccci_c2k=1
ro.boot.opt_using_default=1
mtk.vdec.waitkeyframeforplay=1
ro.sys.sdcardfs=1
persist.mtk.datashaping.support=1
persist.datashaping.alarmgroup=1
ro.media.maxmem=500000000
ro.product.first_api_level=24
persist.sys.timezone=Asia/Kuala_Lumpur
ro.custom.version.release=OUKITEL_K10000_Pro_V1.0_20170531
ro.custom.build.product=t975g-oq-s23-fhd-256g24g-3m-N-bom17
ro.hct_extra_ringtone_show_more=1
ro.hct_multi_finger_gesture=1
ro.hct_no_browser_navigation=1
ro.hct_support_eyemode=1
ro.hct_support_applock=1
ro.hct_remove_ip_prefix_support=1
persist.sys.fontsize=2
ro.hct_support_miniscreen=1
ro.hct_modify_phone_info=1
ro.hct_suport_anr_tools=1
ro.hct_system_manager=1
ro.hct_support_power_save=1
ro.config.random_lockscreen=yes
ro.gangyun_camera_beauty=1
ro.hct_white_list=1
ro.hct_ask_search=1
ro.hct_fingerprint=1
ro.hct_fingerprint_chip=microarray
ro.com.google.clientidbase=android-hct
ro.com.google.clientidbase.am=android-hct
ro.com.google.clientidbase.yt=android-hct
ro.com.google.clientidbase.ms=android-hct
ro.com.google.clientidbase.gmm=android-hct
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r7
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=cortex-a53
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# start redstone OTA properties
ro.redstone.platform=mt6750
ro.redstone.brand=OUKITEL
ro.redstone.model=K10000 Pro
ro.redstone.version=OUKITEL_K10000_Pro_V1.0_20170531
# end redstone OTA properties
ro.expect.recovery_id=0x51d403331aa2da793860f5b31a4cbdafa045c76b000000000000000000000000
K10000_Pro:/ $
Thanks, and regards for your helping !
--->
I have tried antoher things ... BUT NOW I HAVE BRICKED MY PHONE !!! DO NOT TRY THIS !!!!!
I have download the "OUKITEL_K10000_Pro_V1.3_20170222" ROM, and extract it. in system.img I have seen the buid.pro, the majot difference is the "eng" instead of the "user" version. I want to try it beacause I know the eng is easier to root, and I have the ROM.
I try to flash it throug SP flash Linux, and not get it work. I tried to flash ALL partitons with "fastboot flash 'something' 'something.img'". I have found data in the txt file and SP flash. ALL flash sent me OK, I m happy , But when I reboot it, BLACK SCREEN !!!
Now, my phone is BRICKED ! I have only the mediatek serial USB ...
SO BAD TO TRY IT !!!
I have try to Flash it now with SP Flash Tools, but I m stuck on "Downloading DA 100%" and after few minutes a popup error with "ERROR: STATUS_EXT_RAM_EXCEPTION (0xC0050005)".
Windows or Linux, is the same Tryed to remove USB, change PC, power on/off before / after flash tools, with or without VOL+/-/power/both ....
I have a real big brick :'(
I have screenshoot, but XDA doesn't host images ...

Hi I have the new one, I have only unlock OEM.
What i need to do now ?
I don't want to brick it again

Hi have rooted my phone finaly
0) Unlock OEM bootloader
1) I use Android Kitchen tu unzip the receovery-verified.img from ROM in the thread OUKITEL K10000 Pro - Development & Support - "https://forum.xda-developers.com/android/general/oukitel-k10000-pro-development-support-t3627904".
2) Download TWRP for "K6000 Plus" (recvoery-twrp31jemini.img)
3) Extract it olso in another folder.
4) repalce ramdisk directory ONLY (form recvoery-twrp31jemini.img TO Oukitel K10000 Pro)
--> This keep kernel and somme settings from original recovery
5) Repack it
6) Boot it !
--> I n my case I have in russian, I change to French help from google image.
7) Flash SuperSu
8) Done

FukTheRegister said:
Hi have rooted my phone finaly
0) Unlock OEM bootloader
1) I use Android Kitchen tu unzip the receovery-verified.img from ROM in the thread OUKITEL K10000 Pro - Development & Support - "https://forum.xda-developers.com/android/general/oukitel-k10000-pro-development-support-t3627904".
2) Download TWRP for "K6000 Plus" (recvoery-twrp31jemini.img)
3) Extract it olso in another folder.
4) repalce ramdisk directory ONLY (form recvoery-twrp31jemini.img TO Oukitel K10000 Pro)
--> This keep kernel and somme settings from original recovery
5) Repack it
6) Boot it !
--> I n my case I have in russian, I change to French help from google image.
7) Flash SuperSu
8) Done
Click to expand...
Click to collapse
Hi mate, thanks for posting this information. Do you mean to replace the "ramdisk.img" by renaming the TWRP "recovery.img" to "ramdisk.img" and copying it to the firmware? And how did you install it? SP Tool?

Hi,
I have publish my recovery online.
It's have A LOT OF PROBLEMS:
Touch screen only works with "fastboot boot recovery-GALOULA_v0.1.img"
Screen is inverted (180°) but touch is ok (touch opposite to get to good button ...)
If you flash it, you have only ADB and NO touch screen, it's strange ...
On my phone, it's Russian by default !
But I arrived to flash the SuperUser.zip and get root on Android side
www.galoula.net/fr/Tutoriels/OK10KP/FTP/recovery-GALOULA_v0.1.img

FukTheRegister said:
Hi,
I have publish my recovery online.
It's have A LOT OF PROBLEMS:
Touch screen only works with "fastboot boot recovery-GALOULA_v0.1.img"
Screen is inverted (180°) but touch is ok (touch opposite to get to good button ...)
If you flash it, you have only ADB and NO touch screen, it's strange ...
On my phone, it's Russian by default !
But I arrived to flash the SuperUser.zip and get root on Android side
www.galoula.net/fr/Tutoriels/OK10KP/FTP/recovery-GALOULA_v0.1.img
Click to expand...
Click to collapse
Thank you! I managed to install it and I'm now reinstalling the rom(I had to unlock OEM through fastboot which erased everything). I didn't get the touch screen to work but I suppose the supersu zip can be installed with the command
adb shell "echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command"
Click to expand...
Click to collapse
Let's see what happens... :fingers-crossed:
EDIT: The touch screen works, I just misread your post I suggest sideloading SuperSU.zip because the screen inversion is confusing. I was finally able to root. You're a lifesaver @FukTheRegister!

sim unlock
Hey
I have an oukitel k10000 pro but the problem is that my sim card is recognized by the device but i can not phone i do not get a network can someone help me if possible send a patch to unlock sim
Greetings knuffel14

the root method on needrom works like a treat. just a few things that are not mentioned in the readme:
1: do EXACTLY as you are told in the readme
2: rooting will factory reset the phone
3: do EXACTLY as you are told in the readme
4: you get a text during boot that the phone is in "orange mode" and boot is delayed by 5 seconds. this is built in android 7 protection and cannot be disabled. the text however is REALLY small and is only visible during the first 10 seconds of booting the phone.
5: do EXACTLY as you are told in the readme
once you enter TWRP it is probably in russian. press the second button from the bottom on the right side, then the globe on the top right and select your own language and press the bottom right button to enable that language.
ps: do EXACTLY as you are told in the readme

FukTheRegister said:
Hi,
I have publish my recovery online.
It's have A LOT OF PROBLEMS:
Touch screen only works with "fastboot boot recovery-GALOULA_v0.1.img"
Screen is inverted (180°) but touch is ok (touch opposite to get to good button ...)
If you flash it, you have only ADB and NO touch screen, it's strange ...
On my phone, it's Russian by default !
But I arrived to flash the SuperUser.zip and get root on Android side
www.galoula.net/fr/Tutoriels/OK10KP/FTP/recovery-GALOULA_v0.1.img
Click to expand...
Click to collapse
hi, you said you've managed to root your k10000 pro (
FukTheRegister said:
Hi have rooted my phone finaly
0) Unlock OEM bootloader
1) I use Android Kitchen tu unzip the receovery-verified.img from ROM in the thread OUKITEL K10000 Pro - Development & Support - "https://forum.xda-developers.com/android/general/oukitel-k10000-pro-development-support-t3627904".
2) Download TWRP for "K6000 Plus" (recvoery-twrp31jemini.img)
3) Extract it olso in another folder.
4) repalce ramdisk directory ONLY (form recvoery-twrp31jemini.img TO Oukitel K10000 Pro)
--> This keep kernel and somme settings from original recovery
5) Repack it
6) Boot it !
--> I n my case I have in russian, I change to French help from google image.
7) Flash SuperSu
8) Done
Click to expand...
Click to collapse
)
but then you say that got problems with touch screen and screen inverted,etc ? your method described works or not? still got problems ? sorry it is very confusing

Hi, Could you tell me what android kitchen tool you used to this phone?, thanks.