Related
Hello,
i just updated my sony s with condi's instructions and his AIO tool to ICS 4.0.3.
I followed all the steps in his video. I created the custom-rom and flashed it... everything went fine. ICS is running smoothly but the only downside is, that my tablet seems to NOT be rootet!
I don't have a Superuser app and ad free and titanium backup are telling me that i'm not rootet...
how is that possible? is there anyway to flash my "pre-rootet" rom again?
Im affraid, that you just made your tab unrootable, i dunno if you kernel is changed now maby the AiO tool made some changes, if so, just try to root your tab with the tool,
But if you have a blocked kernel, then its not possible.
check AiO thread, FAQ section, point no.5.
It might help you.
br
condi
thx for the hint condi but since i used AIO 2.9 the path check should be included... the strange thing is i don't have /system/bin/tempsu binary.
i don't know why.. but it seems my tablet is not rooted.. hm, so basically i ended the same as those people who updated OTA???
My kernel build is 2.6.39.4 [email protected] #1...
is wiping my device helping? or should i try to flash the custom rom again? is that even possible now?
lulash said:
thx for the hint condi but since i used AIO 2.9 the path check should be included... the strange thing is i don't have /system/bin/tempsu binary.
i don't know why.. but it seems my tablet is not rooted.. hm, so basically i ended the same as those people who updated OTA???
My kernel build is 2.6.39.4 [email protected] #1...
is wiping my device helping? or should i try to flash the custom rom again? is that even possible now?
Click to expand...
Click to collapse
First just try wipe. If it will still gonna be without root,
then run adb shell and type:
Code:
getprop | grep incremental
getprop | grep sku
and post here your values, gonna give you proper fw for downgrade,
then you could reflash prerooted ICS
br
condi
condi said:
First just try wipe. If it will still gonna be without root,
then run adb shell and type:
Code:
getprop | grep incremental
getprop | grep sku
and post here your values, gonna give you proper fw for downgrade,
then you could reflash prerooted ICS
br
condi
Click to expand...
Click to collapse
Hi Condi, I am in the same situation, I want to try to downgrade, to get preroot and try again with ICS.
I did what you said in ADB shell, but I am getting this: (please help)
[*]*************[*]
[*] ADB Shell [*]
[*]*************[*]
Type EXIT to get out of shell
[email protected]:/ $ getprop | grep incremental
getprop | grep incremental
/system/bin/sh: grep: not found
127|[email protected]:/ $ getprop | grep sku
getprop | grep sku
/system/bin/sh: grep: not found
127|[email protected]:/ $
rfreeman said:
Hi Condi, I am in the same situation, I want to try to downgrade, to get preroot and try again with ICS.
I did what you said in ADB shell, but I am getting this: (please help)
[*]*************[*]
[*] ADB Shell [*]
[*]*************[*]
Type EXIT to get out of shell
[email protected]:/ $ getprop | grep incremental
getprop | grep incremental
/system/bin/sh: grep: not found
127|[email protected]:/ $ getprop | grep sku
getprop | grep sku
/system/bin/sh: grep: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
i get the same results!
@rfreeman: did u install the update OTA or did u create a pre-rootet rom using the AIO tool?
i believe that somehow ( i don't know how because every step had the same results as in the video) the us firmware didn't get rootet during the process... i've got all the files: decrypted_update, custom_update_signed... but i like i said... maybe all we did is decrypt, do nothing and then sign it again... the question remains! why!!! .
is it still usefull to try and see if wyping helps?
lulash said:
i get the same results!
@rfreeman: did u install the update OTA or did u create a pre-rootet rom using the AIO tool?
i believe that somehow ( i don't know how because every step had the same results as in the video) the us firmware didn't get rootet during the process... i've got all the files: decrypted_update, custom_update_signed... but i like i said... maybe all we did is decrypt, do nothing and then sign it again... the question remains! why!!! .
is it still usefull to try and see if wyping helps?
Click to expand...
Click to collapse
I all ready wipe, without success...
thx for letting me know! saves me the trouble ... but i guess i have to do it anyway because ics runs really buggy...
u didn't tell us, if u used a pre-rooted rom or ota update?
lulash said:
thx for letting me know! saves me the trouble ... but i guess i have to do it anyway because ics runs really buggy...
u didn't tell us, if u used a pre-rooted rom or ota update?
Click to expand...
Click to collapse
I followed the procedure, using AIO tool, I decryted, root, sign and flash. It goes well but without root.
Hm... so u did exactly the same as I did.... condi, maybe something involuntarily changed while u updated to 2.9? Anyway... anyone a solution... maybe we can still flash? Thx in advance.
rfreeman said:
Hi Condi, I am in the same situation, I want to try to downgrade, to get preroot and try again with ICS.
I did what you said in ADB shell, but I am getting this: (please help)
[*]*************[*]
[*] ADB Shell [*]
[*]*************[*]
Type EXIT to get out of shell
[email protected]:/ $ getprop | grep incremental
getprop | grep incremental
/system/bin/sh: grep: not found
127|[email protected]:/ $ getprop | grep sku
getprop | grep sku
/system/bin/sh: grep: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Ok. As adb shell did not work for you. Grab the "sku" and "incremental" values from /system/build.prop. Use program such as root explorer (still works without root)
Hopefully the backdoor was still applied (decreasing the incremental)
Post results here so Condi can find correct 3.2.1 to flash so then you can ICS again.
thx for the tip!
incremental= 120410002
there is no sku value ... i guess that's bad news?
lulash said:
thx for the tip!
incremental= 120410002
there is no sku value ... i guess that's bad news?
Click to expand...
Click to collapse
Ro.sony.sku.base=nbx03- etc etc
Judging by the incremental it looks like you won't be able to, but wait for confirmation. Sorry if it is bad news..... my tab is currently unrootable with 3.2.1 build 10.... so same boat lol
stifilz said:
Ro.sony.sku.base=nbx03- etc etc
Click to expand...
Click to collapse
nope. Not there...
Well, so I might not be able to root, but the question remains. Why? How did that happen?
Has anyone else have the same problem besides rfreeman and me? If so, this might be a general problem.
If we could find an answer, maybe others won't end up the same!
Exactly the same problem, after upgrade from a rooted tabletS. The binary comparision showes the system.img before and after the pre-root patch were identical. I won't flash it if I had checked.
Sent from my R800i using Tapatalk 2
Hopefully Condi will read this and implement some kind of check to see if the created custom-rom is different from the original rom... this could be a way to prevent this "bug".
lulash said:
Hopefully Condi will read this and implement some kind of check to see if the created custom-rom is different from the original rom... this could be a way to prevent this "bug".
Click to expand...
Click to collapse
added some checks in v3.0.
i've flashed my tab several times, dont know how it could give untouched system.img..
but now it checks filesize
tell me whats the state of your device?
type:
Code:
adb shell "getprop" > props.txt
and attach file here
br
condi
Many thanks Condi! Please help to check if my tablet can still be reverted to rootable FW version with below "getprop" output:
Code:
getprop
[dalvik.vm.dexopt-flags]: [m=y]
[dalvik.vm.heapgrowthlimit]: [48m]
[dalvik.vm.heapsize]: [256m]
[dalvik.vm.heapstartsize]: [5m]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[dev.bootcomplete]: [1]
[dhcp.wlan0.dns1]: [192.168.1.2]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[dhcp.wlan0.gateway]: [192.168.1.2]
[dhcp.wlan0.ipaddress]: [192.168.1.110]
[dhcp.wlan0.leasetime]: [86400]
[dhcp.wlan0.mask]: [255.255.255.0]
[dhcp.wlan0.pid]: [539]
[dhcp.wlan0.reason]: [BOUND]
[dhcp.wlan0.result]: [ok]
[dhcp.wlan0.server]: [192.168.1.2]
[drm.service.enabled]: [true]
[gsm.current.phone-type]: [1]
[gsm.operator.alpha]: []
[gsm.operator.iso-country]: []
[gsm.operator.isroaming]: [false]
[gsm.operator.numeric]: []
[gsm.sim.operator.alpha]: []
[gsm.sim.operator.iso-country]: []
[gsm.sim.operator.numeric]: []
[gsm.sim.state]: [UNKNOWN]
[init.svc.abtfilt]: [stopped]
[init.svc.adbd]: [running]
[init.svc.bluetoothd]: [running]
[init.svc.bootanim]: [stopped]
[init.svc.dbus]: [running]
[init.svc.debuggerd]: [running]
[init.svc.dhcpcd_wlan0]: [running]
[init.svc.drm]: [running]
[init.svc.hci_event]: [running]
[init.svc.hciattach]: [running]
[init.svc.installd]: [running]
[init.svc.keystore]: [running]
[init.svc.media]: [running]
[init.svc.netd]: [running]
[init.svc.nfx_log_service]: [running]
[init.svc.ril-daemon]: [running]
[init.svc.servicemanager]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.svold]: [running]
[init.svc.vold]: [running]
[init.svc.wifi_init]: [stopped]
[init.svc.wpa_supplicant]: [running]
[init.svc.zygote]: [running]
[media.tegra.max.out.channels]: [2]
[media.tegra.out.channel.map]: []
[net.bt.name]: [Android]
[net.change]: [net.dnschange]
[net.dns1]: [192.168.1.2]
[net.dnschange]: [1]
[net.hostname]: [android-fd0a7f6d23f19e80]
[net.qtaguid_enabled]: [1]
[net.tcp.buffersize.default]: [4096,87380,110208,4096,16384,110208]
[net.tcp.buffersize.edge]: [4093,26280,35040,4096,16384,35040]
[net.tcp.buffersize.gprs]: [4092,8760,11680,4096,8760,11680]
[net.tcp.buffersize.hsdpa]: [4094,87380,1048576,4096,16384,110208]
[net.tcp.buffersize.hspa]: [4094,87380,1048576,4096,16384,262144]
[net.tcp.buffersize.lte]: [524288,1048576,2097152,262144,524288,1048576]
[net.tcp.buffersize.umts]: [4094,87380,196608,4096,16384,110208]
[net.tcp.buffersize.wifi]: [524288,1048576,2097152,262144,524288,1048576]
[net.wlan0.dns1]: [49.0.0.0]
[net.wlan0.dns2]: []
[persist.service.adb.enable]: []
[persist.sys.NV_STEREOCTRL]: [0]
[persist.sys.country]: [CN]
[persist.sys.language]: [zh]
[persist.sys.localevar]: []
[persist.sys.profiler_ms]: [0]
[persist.sys.timezone]: [Asia/Shanghai]
[persist.sys.usb.config]: [mtp,adb]
[rild.libargs]: [-d /dev/ttyACM1 -i rmnet0]
[ro.allow.mock.location]: [0]
[ro.baseband]: [unknown]
[ro.board.platform]: [tegra]
[ro.bootloader]: [0x00000008]
[ro.bootmode]: [unknown]
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1333987721]
[ro.build.date]: [Tue Apr 10 01:08:41 JST 2012]
[ro.build.description]: [SYS_001-user 4.0.3 TISU0077 120410002 release-keys]
[ro.build.display.id]: [TISU0077]
[ro.build.fingerprint]: [Sony/SYS_001/nbx03:4.0.3/TISU0077/120410002:user/relea
e-keys]
[ro.build.host]: [build9]
[ro.build.id]: [TISU0077]
[ro.build.product]: [nbx03]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [integ-build]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [120410002]
[ro.build.version.release]: [4.0.3]
[ro.build.version.sdk]: [15]
[ro.camera.sound.forced]: [0]
[ro.carrier]: [unknown]
[ro.com.google.clientidbase]: [android-sony]
[ro.com.google.gmsversion]: [4.0.3_r0]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.notification_sound]: [OnTheHunt.ogg]
[ro.crypto.fs_flags]: [0x00000406]
[ro.crypto.fs_mnt_point]: [/data]
[ro.crypto.fs_real_blkdev]: [/dev/block/mmcblk0p10]
[ro.crypto.fs_type]: [ext4]
[ro.crypto.state]: [unsupported]
[ro.crypto.tmpfs_options]: [size=128m,mode=0771,uid=1000,gid=1000]
[ro.debuggable]: [0]
[ro.device.bluetooth.bdaddr]: [F0BF97D3B57E]
[ro.device.sensor.accel.offset.x]: [0]
[ro.device.sensor.accel.offset.y]: [0]
[ro.device.sensor.accel.offset.z]: [0]
[ro.device.sensor.gyro.offset.x]: [0]
[ro.device.sensor.gyro.offset.y]: [0]
[ro.device.sensor.gyro.offset.z]: [0]
[ro.device.sensor.mag.b0.x]: [306]
[ro.device.sensor.mag.b0.y]: [195]
[ro.device.sensor.mag.b0.z]: [-919]
[ro.device.sensor.mag.calib.x]: [1.0]
[ro.device.sensor.mag.calib.y]: [1.0]
[ro.device.sensor.mag.calib.z]: [1.0]
[ro.device.sensor.mag.offset.x]: [287]
[ro.device.sensor.mag.offset.y]: [288]
[ro.device.sensor.mag.offset.z]: [310]
[ro.ethernet.autoEnable]: [yes]
[ro.ethernet.interface]: [eth0]
[ro.factorytest]: [0]
[ro.hardware]: [nbx03]
[ro.opengles.version]: [131072]
[ro.product.board]: [nbx03]
[ro.product.brand]: [Sony]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [nbx03]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [Sony]
[ro.product.model]: [Sony Tablet S]
[ro.product.name]: [SYS_001]
[ro.pss.gamepad.buttonmeaning]: [cross-enter]
[ro.revision]: [0]
[ro.runtime.firstboot]: [1337613865480]
[ro.secure]: [1]
[ro.serialno]: [275501730009232]
[ro.setupwizard.mode]: [DISABLED]
[ro.sony.build.id]: [TISU0017700]
[ro.sony.build.incremental]: [111104048]
[ro.sony.dlna.dtcp_pext]: [0]
[ro.sony.network.wwan]: [0]
[ro.sony.serialno]: [27550173 0009232]
[ro.sony.sku.base]: [nbx03_001]
[ro.sony.sku.country]: [US]
[ro.sony.sku.detailed]: [27550100]
[ro.sony.sku.version]: [27550100_18]
[ro.sony.sound.enabled]: [true]
[ro.sony.update.category_id]: [ST002]
[ro.sony.update.server]: [info.update.sony.net]
[ro.sony.update.service_id]: [nbx03_001]
[ro.sony.volume_limit]: [0]
[ro.sony.wan.ipv6.enable]: [false]
[ro.sony.wifisleep]: [0]
[ro.sony.wm.atrac]: [0]
[ro.sony.wm.clearphase_path]: [SGPT1_001.LPS]
[ro.sony.wm.xloud_path]: [SGPT1_001.XLD]
[ro.tether.denied]: [true]
[ro.wifi.channels]: []
[sys.boot_completed]: [1]
[sys.sony.compat]: [true]
[sys.usb.config]: [mtp,adb]
[sys.usb.state]: [mtp,adb]
[system_init.startsurfaceflinger]: [0]
[vold.post_fs_data_done]: [1]
[wifi.interface]: [wlan0]
[windowsmgr.max_events_per_sec]: [120]
[wlan.driver.status]: [ok]
[email protected]:/ $
condi said:
tell me whats the state of your device?
type:
Code:
adb shell "getprop" > props.txt
and attach file here
br
condi
Click to expand...
Click to collapse
The important values like incremental (120410002) and sku_base (nbx03_001) are the same as jgzhang's... i've got some additional entries though... the one that sounds most interesting is:
Code:
[ro.com.google.mcc_fallback]: [262]
I also have different [ro.sony.sku.detailed] & [ro.sony.sku.version] values...
thx for your effort everyone!
Help! Purchased used Verizon Galaxy Note II (SCH-i605) but I didn't realize it had been rooted/unlocked/rom'd/. I want it refreshed back to Verizon factory image locked/factory image/unrooted.
I restored it back to "factory" image/locked and only then did I realize it had been unlocked/rom'd. Now I am getting yellow Verizon triangle unauthorized software.
Here is why I am stuck. I cannot get back into the OS to enable USB Debugging.
I restored the factory ROM and bootloader is Verizon locked.
Problem is factory Verizon bootloader is noticing my "System Status: Custom" and throwing the Yellow Triangle and stopping the boot even though I was able to have the ROM count reset which now says "Custom Binary Download: No".
Triangle Away requires USB Debugging enabled and I cannot get into the OS. I have burned huge time with multiple ROM's/ODIN, dealt with the CASUAL USB driver hijack of the Samsung vendor_id/hw_id head fake, and Verizon thwarts everybody and all versions including Samsung KIES.
f I had enabled USB Debugging before selecting factory restore, I would have saved myself a bunch of time.
Please help, I feel like I fell down the rabbit hole and never offered red pill or blue pill.
Any suggestions to solve this? Detailed steps would be very helpful!!
I
Thanks!
mail for solution at nikhil.kdhand at gmail.com
nikhil.kdhand said:
mail for solution at nikhil.kdhand at gmail.com
Click to expand...
Click to collapse
Or you could share the answer with the community in case others have a problem
Sent from my SCH-I605 using xda app-developers app
Try to go back to stock rom via Odin.... That should solve the problem
Sent from my SCH-I605 Email:[email protected]
nikhil.kdhand said:
Try to go back to stock rom via Odin.... That should solve the problem
Sent from my SCH-I605 Email:[email protected]
Click to expand...
Click to collapse
Try reading again, he stated he already tried Odin
Sent from my SCH-I605 using xda app-developers app
Odin with pit file has worked for me
Sent from my SCH-I605 Email:[email protected]
XDA developers is a site to learn and share. The knowledge you gain, or have, or happen to stumble upon may end up saving someone a lot of time and trouble. I would encourage you all to share as freely as the developers of your favorite roms/kernels/projects all do.
Thank you for you cooperation.
Come on xda community! No credible suggestions to this challenge at all?
I am a total noob and I have stumped all of you with my posted question?!!
What about some suggestions along the lines of remotely enabling USB Debug mode by installing the Android ADK/SDK and using ADB debug or Shell or sideload?
What about ROM versions that might already have USB Debug already enabled?
Or remotely executed code like:
Settings.Secure.putInt(getContentResolver(),Settings.Secure.ADB_ENABLED, 0); /
The challenge is the locked Verizon bootloader won't let me into the OS GUI to enable USB Debugging. To unlock bootloader, I need USB Debugging enabled. CASUAL ultimately requires USB Debugging enabled.
Use hidden menu apk and enable USB debug through it....
Sent from my SCH-I605
Email:[email protected]
nikhil.kdhand said:
Use hidden menu apk and enable USB debug through it....
Sent from my SCH-I605
Email:[email protected]
Click to expand...
Click to collapse
Dude if you're going to try and help please at least read the problem. How can he use the hidden menu if his device doesn't boot?
Sent from my SCH-I605 using xda app-developers app
You better concentrate on the issue and not in evaluating people suggestions....
Sent from my SCH-I605
Email:[email protected]
nikhil.kdhand said:
You better concentrate on the issue and not in evaluating people suggestions....
Sent from my SCH-I605
Email:[email protected]
Click to expand...
Click to collapse
The OP stated that they've tried Odin and can't boot into Android. Without them providing more information about what Odin file(s) they flashed and how they were used (PIT file, what section where they flashed through), nothing you suggested is of any use. You can't use the hidden menu without booting into Android, and we need more info about Odin packages used/tried.
nikhil.kdhand said:
Use hidden menu apk and enable USB debug through it....
Sent from my SCH-I605
Email:[email protected]
Click to expand...
Click to collapse
Can you please troll for increasing your post count somewhere else. Thanks.
Let's stop this here before it becomes an issue. Read before posting, no flaming, follow the rules.:thumbup:
Sent from my YP-G1 using Tapatalk 2
imnuts said:
The OP stated that they've tried Odin and can't boot into Android. Without them providing more information about what Odin file(s) they flashed and how they were used (PIT file, what section where they flashed through), nothing you suggested is of any use. You can't use the hidden menu without booting into Android, and we need more info about Odin packages used/tried.
Click to expand...
Click to collapse
I still cannot figure this out. Trying to get back to full stock/locked and unable to boot OS due to Yellow Triangle unauthorized software message.
I think the issue is no matter what I do, the bootloader is locked and "System Status: Custom" isn't changed back to stock status, and I am unable to get into the OS to enable USB Debugging and unable to run Triangle Away.
I am probably wrong but I think the first thing I need to achieve is an unlocked bootloader without having access to the OS and unable to turn on USB Debugging.
----------------------
Test 1
ODIN 3.07
BootloaderBaseline2.tar.md5.gz
sch-i605-16gb.pit
ODIN: FAIL
sboot.bin
FAIL!
-------------
Test 2
ODIN 3.07
sch-i605-16gb.pit
root66_VZW_stock_system.tar.md5
Result:
Boots into setup wizard, first question select Language.
Withing 20 seconds reverts to Yellow Triangle unauthorized software
"Current Binary: Samsung Official"
"System Status: Custom"
-------------------
Test 3
ODIN 3.07
I605_VRALJB_Restore.tar.md5 ("alternate" no sboot.bin)
sch-i605-16gb.pit
Result:
Yellow Triangle
"Current Binary: Samsung Official"
"System Status: Custom"
For whatever it might be worth, here is the current OS config/properties detail.
[adb.recovery]: [1]
[android.telephony.apn-restore]: [1800000]
[dalvik.vm.dexopt-flags]: [m=y]
[dalvik.vm.heapgrowthlimit]: [64m]
[dalvik.vm.heapsize]: [256m]
[dalvik.vm.heapstartsize]: [8m]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.hwui.render_dirty_regions]: [false]
[init.svc.adbd]: [running]
[init.svc.recovery]: [running]
[init.svc.ueventd]: [running]
[keyguard.no_require_sim]: [true]
[media.enable-commonsource]: [true]
[net.bt.name]: [Android]
[net.change]: [net.bt.name]
[net.streaming.rtsp.uaprof]: [wap.samsungmobile.com/uaprof/]
[persist.eons.enabled]: [false]
[persist.radio.add_power_save]: [1]
[persist.radio.apm_sim_not_pwdn]: [1]
[persist.radio.no_wait_for_card]: [1]
[persist.radio.snapshot_enabled]: [1]
[persist.radio.snapshot_timer]: [22]
[persist.sys.storage_preload]: [1]
[persist.sys.usb.config]: [mass_storage]
[persist.timed.enable]: [true]
[ril.dualmode.change]: [unknown]
[rild.libargs]: [-d /dev/ttyS0]
[rild.libpath]: [/system/lib/libril-qc-qmi-1.so]
[ro.adb.qemud]: [1]
[ro.allow.mock.location]: [0]
[ro.baseband]: [mdm]
[ro.board.platform]: [exynos4]
[ro.boot.baseband]: [mdm]
[ro.boot.bootloader]: [I605VRAMC3]
[ro.boot.debug_level]: [0x4f4c]
[ro.boot.emmc_checksum]: [3]
[ro.boot.odin_download]: [1]
[ro.bootloader]: [I605VRAMC3]
[ro.bootmode]: [unknown]
[ro.build.PDA]: [I605VRALJB]
[ro.build.changelist]: [414933]
[ro.build.characteristics]: [verizon]
[ro.build.date.utc]: [1351399133]
[ro.build.date]: [Sun Oct 28 13:38:53 KST 2012]
[ro.build.description]: [t0ltevzw-user 4.1.1 JRO03C I605VRALJB release-keys]
[ro.build.display.id]: [JRO03C.I605VRALJB]
[ro.build.fingerprint]: [Verizon/t0ltevzw/t0ltevzw:4.1.1/JRO03C/I605VRALJB:user/release-keys]
[ro.build.hidden_ver]: [I605VRALJBd]
[ro.build.host]: [SEP-112]
[ro.build.id]: [JRO03C]
[ro.build.product]: [t0ltevzw]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [se.infra]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [I605VRALJB]
[ro.build.version.release]: [4.1.1]
[ro.build.version.sdk]: [16]
[ro.carrier]: [unknown]
[ro.chipname]: [smdk4x12_prime]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.com.google.apphider]: [off]
[ro.com.google.clientidbase.am]: [android-verizon]
[ro.com.google.clientidbase.gmm]: [android-samsung]
[ro.com.google.clientidbase.ms]: [android-verizon]
[ro.com.google.clientidbase.vs]: [android-verizon]
[ro.com.google.clientidbase.yt]: [android-verizon]
[ro.com.google.clientidbase]: [android-samsung]
[ro.com.google.gmsversion]: [4.1_r2]
[ro.config.alarm_alert]: [Walk_in_the_forest.ogg]
[ro.config.combined_signal]: [true]
[ro.config.media_sound]: [Media_preview_Touch_the_light.ogg]
[ro.config.multimode_cdma]: [1]
[ro.config.notification_sound]: [S_Whistle.ogg]
[ro.config.ringtone]: [Verizon_Airwaves.ogg]
[ro.config.vc_call_vol_steps]: [7]
[ro.debug_level]: [0x4f4c]
[ro.debuggable]: [0]
[ro.emmc_checksum]: [3]
[ro.error.receiver.default]: [com.samsung.receiver.error]
[ro.factorytest]: [0]
[ro.gsm.data_retry_config]: [max_retries=infinite,5000,5000,60000,120000,480000,900000]
[ro.hardware]: [smdk4x12]
[ro.hdcp2.rx]: [tz]
[ro.kernel.qemu]: [0]
[ro.lcd_min_brightness]: [20]
[ro.opengles.version]: [131072]
[ro.product.board]: [smdk4x12]
[ro.product.brand]: [Verizon]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [t0ltevzw]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [GB]
[ro.product.manufacturer]: [samsung]
[ro.product.model]: [SCH-I605]
[ro.product.name]: [t0ltevzw]
[ro.product_ship]: [true]
[ro.revision]: [10]
[ro.ril.ecclist]: [112,911,#911,*911]
[ro.ril.gprsclass]: [10]
[ro.ril.hsxpa]: [1]
[ro.sec.fle.encryption]: [true]
[ro.secure]: [1]
[ro.secwvk]: [220]
[ro.setupwizard.mode]: [DISABLED]
[ro.sf.lcd_density]: [320]
[ro.tvout.enable]: [true]
[ro.uart_debug]: [0]
[ro.use_data_netmgrd]: [true]
[ro.wifi.channels]: []
[telephony.lteOnCdmaDevice]: [1]
[vzw.telephony.appsapn-restore]: [60000]
Hey! I'm a noob as well. Check the files you're using to restore. Odin wasn't playing nice with them after the last update. Is debugging off by default on stock?
Um test 2 makes no sense. If you're getting that triangle you should not boot into the system at all. I would try that one again.
jobrienxda said:
I still cannot figure this out. Trying to get back to full stock/locked and unable to boot OS due to Yellow Triangle unauthorized software message.
I think the issue is no matter what I do, the bootloader is locked and "System Status: Custom" isn't changed back to stock status, and I am unable to get into the OS to enable USB Debugging and unable to run Triangle Away.
I am probably wrong but I think the first thing I need to achieve is an unlocked bootloader without having access to the OS and unable to turn on USB Debugging.
----------------------
Test 1
ODIN 3.07
BootloaderBaseline2.tar.md5.gz
sch-i605-16gb.pit
ODIN: FAIL
sboot.bin
FAIL!
-------------
Test 2
ODIN 3.07
sch-i605-16gb.pit
root66_VZW_stock_system.tar.md5
Result:
Boots into setup wizard, first question select Language.
Withing 20 seconds reverts to Yellow Triangle unauthorized software
"Current Binary: Samsung Official"
"System Status: Custom"
-------------------
Test 3
ODIN 3.07
I605_VRALJB_Restore.tar.md5 ("alternate" no sboot.bin)
sch-i605-16gb.pit
Result:
Yellow Triangle
"Current Binary: Samsung Official"
"System Status: Custom"
Click to expand...
Click to collapse
Hi,
This happens to me a lot as I flash a ton of stuff. Basically, you will need to run Casual. Make sure that you go into your computer settings if you are using Windows and delete any Samsung driver files. Look for any USB drivers like lib drivers etc. Casual will install what a unique driver that will recognize your device when you don't have USB selected on your phone.
Be patient and look at the Casual screen. It will be automatic and eventually put you into TWRP recovery. Remember to flash the rooted version of the Odin version because there is a Blacklist of boot loaders(bin) that will keep giving you the software warning from Verizon. Other than that, you can flash whatever you want. I hope this helps. Also, depending of what type of computer OS you are using, I have found trying different versions of Casual. Please refer to the rooting/boot loader unlocking for more details and of the links. It will work and you will be able to get your phone back! Good luck.
Hey,
I have a DiskStation running both DHCP and DNS servers in my local network, to route some hostnames to local devices. This works pretty well with my PCs and used to work with my Android tablet (Nexus 9) and phone (Nexus 5) as well, but today it stopped working for no apparent reason . Whether I configure them with automatic network settings, DHCP or static IP, gateway, DNS ...., they always use Google's 8.8.8.8 or 8.8.4.4 as DNS servers. Both are running Stock Android 5.0.1 Rooted.
The DiskStation has the IP 192.168.2.10 and a hostname (<myhostname>) thats reachable from outside, but inside the network it should route directly to the DiskStation. The 192.168.2.2 is my router running a DHCPv6 server.
Some relevant output from the N9 (with BusyBox):
getprop | grep dns
Code:
[email protected]_lte:/ $ getprop | grep dns
[dhcp.wlan0.dns1]: [192.168.2.10]
[dhcp.wlan0.dns2]: [8.8.8.8]
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[net.change]: [net.dns3]
[net.dns1]: [2a02:8109:a3c0:1cfc::1]
[net.dns2]: [192.168.2.10]
[net.dns3]: [192.168.2.2]
nslookup <myhostname>
Code:
[email protected]_lte:/ $ nslookup <myhostname>
Server: 8.8.4.4
Address 1: 8.8.4.4 google-public-dns-b.google.com
Name: <myhostname>
Address 1: 2a02:8109:a3c0:1cfc:211:32ff:fe1a:3c52
Address 2: 92.78.140.212 dslb-092-078-140-212.092.078.pools.vodafone-ip.de
nslookup <myhostname> 192.168.2.10
Code:
[email protected]_lte:/ $ nslookup <myhostname> 192.168.2.10
Server: 192.168.2.10
Address 1: 192.168.2.10
Name: <myhostname>
Address 1: 2a02:8109:a3c0:1cfc::2
Address 2: 192.168.2.10
Any idea how I can force them to use my DiskStation as primary DNS server again?
Thanks,
Niko
The same problem on my new DOOGEE Turbo MINI F1
DNS server is assigned by DHCP:
# getprop | grep dns
[dhcp.ipv6.wlan0.dns1]: []
[dhcp.ipv6.wlan0.dns2]: []
[dhcp.wlan0.dns1]: [192.168.6.254]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[net.change]: [net.dns2]
[net.dns1]: [192.168.6.254]
[net.dns2]: [8.8.8.8]
Click to expand...
Click to collapse
# getprop | grep wlan0
[dhcp.ipv6.wlan0.dns1]: []
[dhcp.ipv6.wlan0.dns2]: []
[dhcp.ipv6.wlan0.ipaddress]: []
[dhcp.ipv6.wlan0.leasetime]: []
[dhcp.ipv6.wlan0.result]: []
[dhcp.wlan0.dns1]: [192.168.6.254]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[dhcp.wlan0.domain]: [myhome.domain]
[dhcp.wlan0.gateway]: [192.168.6.254]
[dhcp.wlan0.ipaddress]: [192.168.6.222]
[dhcp.wlan0.leasetime]: [86400]
[dhcp.wlan0.mask]: [255.255.255.0]
[dhcp.wlan0.mtu]: []
[dhcp.wlan0.pid]: [5301]
[dhcp.wlan0.reason]: [BOUND]
[dhcp.wlan0.result]: [ok]
[dhcp.wlan0.server]: [192.168.6.254]
[dhcp.wlan0.vendorInfo]: []
[init.svc.dhcpcd_wlan0]: [running]
[wifi.interface]: [wlan0]
Click to expand...
Click to collapse
But it is not used. Google public DNS is used always.
Thus names of my local computers are not resolved:
# nslookup qnap.myhome.domain
Server: 8.8.4.4
Address 1: 8.8.4.4 google-public-dns-b.google.com
nslookup: can't resolve 'qnap.myhome.domain'
Click to expand...
Click to collapse
Please help.
Some info of Doogee Turbo MINI F1 (rooted):
# getprop | grep version
[dalvik.vm.mtk-vm-version]: [0x01]
[gsm.version.baseband]: [MOLY.LR9.W1423.MD.LWTG.MP.V5.P7, 2015/01/31 16:35]
[gsm.version.ril-impl]: [mtk gemini ril 1.0]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [eng.release.1422693695]
[ro.build.version.release]: [4.4.4]
[ro.build.version.sdk]: [19]
[ro.com.google.gmsversion]: [4.4_r5]
[ro.custom.build.version]: [01.29]
[ro.fota.version]: [DOOGEE-F1-Android4.4-R05-2015.01.31]
[ro.mediatek.version.branch]: [KK2.MP13]
[ro.mediatek.version.release]: [DOOGEE-F1-Android4.4-R05-2015.01.31]
[ro.mediatek.version.sdk]: [3]
[ro.opengles.version]: [196608]
[sys.settings_global_version]: [8]
[sys.settings_system_version]: [22]
Click to expand...
Click to collapse
lucky62k said:
DNS server is assigned by DHCP:
But it is not used. Google public DNS is used always.
Thus names of my local computers are not resolved:
Please help.
Some info of Doogee Turbo MINI F1 (rooted):
Click to expand...
Click to collapse
I have the same problem. I wonder that no one cares...my local network host names are not getting resolved. I dont want to set a static DNS because outside I will get problems. I simply wish Android would accept the DNS from my DHCP
This is still relevant in 2020 ! Disabled "Private DNS" in settings, changed to static ip configuration, nothing seems to help. (Samsung Note 10 +)
Hello,
check about the certificate store at [1] and know that it hasn't got an update on DSC/407 since 16.03.2010. Some of the CA stored there are compromised or obsolete and others came up. You'll find the latest revision for android trusted CAs at [2]
I converted them with BouncyCastleProvider-v1.46 [3] into the old gingerbread format cacert.bks to use in DSC. Just unpack the attached cacerts.zip into /system/etc/security and reboot. I attached also lists with the removed and added CAs in that file.
You can check the installed certificates with info.guardianproject.cacert [4]
Have fun,
hunderteins
[1] http://en.wikipedia.org/wiki/Root_certificate
[2] https://android.googlesource.com/platform/libcore/+/master/luni/src/main/files/cacerts/
[3] http://wiki.cacert.org/FAQ/ImportRootCertAndroidPreICS
[4] https://f-droid.org/wiki/page/info.guardianproject.cacert
About a month ago everything was working perfectly normal. Until I got sent a notification to update to 1.3.3a. What happened was that it got stuck during the update process. Despite waiting for 3 days, when the watch eventually died off it was still stuck at the updating process. To cut long story short, after over a month my bricked watch got revived thanks to Neuer_User.
Now here are my problems. Everything stopped working except for Weather, and receiving notifications. When I tried to record a run, it states that AGPS is expired and it needed to be updated via the App. I turned on the APP, nothing happen despite the watch was still connected to the phone. I skip that process and tried to use the GPS, it just wouldn't lock into the location despite standing in the middle of an open space.
Same thing goes for the Step Counter (not working), sleep (not tracking), Heart Rate Monitor (green flashing light doesn't turn on). I tried flashing to both English and Chinese firmware didn't help either. I couldn't use the update package version 1.3.3a that was uploaded on another thread, cause it would give me back the same problem where it would get stuck in the updating screen.
So I was wondering if there is a way to manually turn these features on via adb or somewhere I can look into to get it updated to 1.3.3a via flashing method instead of updating it.
Thanks!
Sounds tricky.
Did you made a factory reset? You should try to clean as much as possible of the internal memory. Don't know if there are adb commands to wipe data and so on. Unpair the Pace from smartphone and clean data of the Amazfit app. Then flash from scratch PACEfied or other stock ROM, but better with open bootloader and root, to have still all possibilities.
If the hardware is still ok, this should lead to re-enable all sensors.
I guess Neuer_User is one of the experts for such issues.
Why not just install fully the English version from my thread "convert to English"?
Diginix said:
Sounds tricky.
Did you made a factory reset? You should try to clean as much as possible of the internal memory. Don't know if there are adb commands to wipe data and so on. Unpair the Pace from smartphone and clean data of the Amazfit app. Then flash from scratch PACEfied or other stock ROM, but better with open bootloader and root, to have still all possibilities.
If the hardware is still ok, this should lead to re-enable all sensors.
I guess Neuer_User is one of the experts for such issues.
Click to expand...
Click to collapse
Yeah I forgot to include that as well. I've already did a factory reset and fastboot erase data. It still didn't work. I couldn't the PACEfied Rom because it uses update method. The problem with the watch is that, once it goes into update mode it will get stuck and wouldn't proceed.
Neuer_User said:
Why not just install fully the English version from my thread "convert to English"?
Click to expand...
Click to collapse
I've already tried that. But unfortunately it wouldn't work as it uses the update method which will results the watch get stuck in the update process like what is shown in this video I did. I tried requesting for a replacement but my seller is not being responsive at all.
https://www.youtube.com/watch?v=VlngyNCU8mw
alexjong said:
I've already tried that. But unfortunately it wouldn't work as it uses the update method which will results the watch get stuck in the update process like what is shown in this video I did. I tried requesting for a replacement but my seller is not being responsive at all.
Click to expand...
Click to collapse
Once while updating from one version of Pacefied to next, I (and few others) had a problem of getting stuck the update loop. When I say loop, It would go into update process, finish the update and reboot, only to go into update process all over again. The below is what I did to get out of the loop. Not sure if are having loop situation or a update that does not finish...
I also had the issue of the watch getting stuck in update loop. I was updating from Rel 5 to the "New" Rel 6 (Update not Full Install).
After couple of update loops, i issued a Reboot command from adb shell. It did not help, as the watch rebooted into recovery again and started the update again.
As a next step to break out of the update loop, I went into fastboot (adb shell reboot bootloader) and did fastboot continue to start normal boot. This worked, and the watch rebooted normally, did the usual app optimization (for 46 apps) and started. From watch info, I could confirm that the watch was updated to 1.2.11.
Click to expand...
Click to collapse
alexjong said:
I've already tried that. But unfortunately it wouldn't work as it uses the update method which will results the watch get stuck in the update process like what is shown in this video I did. I tried requesting for a replacement but my seller is not being responsive at all.
https://www.youtube.com/watch?v=VlngyNCU8mw
Click to expand...
Click to collapse
Just to clarify: Did you try it, or do you believe it will not work as you had the problem with the official update? (The video is only showing the official update if I am not mistaken.)
madtech360 said:
Once while updating from one version of Pacefied to next, I (and few others) had a problem of getting stuck the update loop. When I say loop, It would go into update process, finish the update and reboot, only to go into update process all over again. The below is what I did to get out of the loop. Not sure if are having loop situation or a update that does not finish...
Click to expand...
Click to collapse
Oh man... The fastboot continue worked pass the upgrade loop. And it updated to 1.3.3a finally. But unfortunately everything else still does not work. Anymore ideas?
Neuer_User said:
Just to clarify: Did you try it, or do you believe it will not work as you had the problem with the official update? (The video is only showing the official update if I am not mistaken.)
Click to expand...
Click to collapse
Yes I did try with the pacefied rom.. But @madtech360 solution worked by using fastboot continue method worked for me.. But despite flashing both original and pacefied roms, the watch features are still disabled. Not sure what else is there for me to try.
Anyone care to do comparison?
Just trying my luck to see if anything is missing from these few selected files. Could someone check theirs to see if it matches?
build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=huangheUS-1.3.0n
ro.build.version.incremental=12
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Mon Nov 28 14:14:15 CST 2016
ro.build.date.utc=1480313655
ro.build.type=user
ro.build.user=ubuntu
ro.build.host=vm10-254-107-57.ksc.com
ro.build.tags=release-keys
ro.build.flavor=huangheUS-user
ro.product.model=Amazfit Pace
ro.product.brand=Huami
ro.product.name=huangheUS
ro.product.device=watch
ro.product.board=watch
ro.build.cmiit.id=XXXXXXXX
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=mips
ro.product.cpu.abi2=mips
ro.product.cpu.abilist=mips,mips
ro.product.cpu.abilist32=mips,mips
ro.product.cpu.abilist64=
ro.product.manufacturer=Huami
ro.wifi.channels=13
ro.board.platform=M200
# ro.build.product is obsolete; use ro.product.device
ro.build.product=watch
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=huangheUS-user 5.1 LMY47D 12 release-keys
ro.build.fingerprint=Huami/huangheUS/watch:5.1/LMY47D/12:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
media.stagefright.use-awesome=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.carrier=wifi-only
dalvik.vm.heapstartsize=64m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.config.low_ram=true
ro.build.oversea=1
ro.build.huami.model=A1612
ro.build.huami.number=14
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
persist.sys.timezone=Asia/Shanghai
ro.sf.lcd_density=238
ro.product.locale.language=en
ro.product.locale.region=US
ro.config.auto_brightness=decrease
sys.fastboot.enable=false
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.mips.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
default.prop
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
ro.zygote=zygote32
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0
adb shell getevent -S
Code:
add device 1: /dev/input/event1
name: "hrtimer-adc-aux1"
add device 2: /dev/input/event2
name: "gpio-keys"
add device 3: /dev/input/event0
name: "fts_ts"
aa00
aa00
aa00
adb shell getprop
Code:
[dalvik.vm.dex2oat-Xms]: [64m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.heapgrowthlimit]: [64m]
[dalvik.vm.heapmaxfree]: [2m]
[dalvik.vm.heapminfree]: [512k]
[dalvik.vm.heapsize]: [384m]
[dalvik.vm.heapstartsize]: [64m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.image-dex2oat-Xms]: [64m]
[dalvik.vm.image-dex2oat-Xmx]: [64m]
[dalvik.vm.isa.mips.features]: [default]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.force_rtl]: [0]
[dev.bootcomplete]: [1]
[huami_launcher_boot_complete]: [true]
[init.svc.adbd]: [running]
[init.svc.bootanim]: [stopped]
[init.svc.console]: [running]
[init.svc.debuggerd]: [running]
[init.svc.delay_sleep]: [stopped]
[init.svc.flash_recovery]: [stopped]
[init.svc.gpsd]: [running]
[init.svc.hardware_adapter]: [stopped]
[init.svc.healthd]: [running]
[init.svc.installd]: [running]
[init.svc.keystore]: [running]
[init.svc.lmkd]: [running]
[init.svc.logd]: [running]
[init.svc.logwatch]: [running]
[init.svc.media]: [running]
[init.svc.netd]: [running]
[init.svc.sdcard]: [running]
[init.svc.serial_numbers]: [stopped]
[init.svc.servicemanager]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.ueventd]: [running]
[init.svc.voicewakeup]: [restarting]
[init.svc.vold]: [running]
[init.svc.wpa_supplicant]: [stopped]
[init.svc.zygote]: [running]
[media.stagefright.use-awesome]: [true]
[net.bt.name]: [Android]
[net.change]: [net.qtaguid_enabled]
[net.hostname]: [Amazfit_Pace-0CD0]
[net.qtaguid_enabled]: [1]
[net.tcp.default_init_rwnd]: [60]
[persist.sys.dalvik.vm.lib.2]: [libart.so]
[persist.sys.profiler_ms]: [0]
[persist.sys.timezone]: [Asia/Kuala_Lumpur]
[persist.sys.usb.config]: [mtp,adb]
[prop.launcher.at_watchface]: [false]
[ro.allow.mock.location]: [0]
[ro.appwidgetserver.disable]: [true]
[ro.baseband]: [unknown]
[ro.board.platform]: [M200]
[ro.boot.revision]: [00000001]
[ro.bootloader]: [unknown]
[ro.bootmode]: [unknown]
[ro.bt.bdaddr]: [D8:80:3C:06:49:80]
[ro.bt.bdaddr_path]: [/data/misc/bluetooth/bt_addr]
[ro.build.characteristics]: [tablet]
[ro.build.cmiit.id]: [XXXXXXXX]
[ro.build.date.utc]: [1497514933]
[ro.build.date]: [Thu Jun 15 16:22:13 CST 2017]
[ro.build.description]: [huangheUS-user 5.1 LMY47D 53 release-keys]
[ro.build.display.id]: [huangheUS-1.3.3a]
[ro.build.fingerprint]: [Huami/huangheUS/watch:5.1/LMY47D/53:user/release-keys]
[ro.build.flavor]: [huangheUS-user]
[ro.build.host]: [vm10-254-107-57.ksc.com]
[ro.build.huami.model]: [A1612]
[ro.build.huami.number]: [11]
[ro.build.id]: [LMY47D]
[ro.build.oversea]: [1]
[ro.build.product]: [watch]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [ubuntu]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [53]
[ro.build.version.release]: [5.1]
[ro.build.version.sdk]: [22]
[ro.carrier]: [wifi-only]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.auto_brightness]: [decrease]
[ro.config.low_ram]: [true]
[ro.config.notification_sound]: [pixiedust.ogg]
[ro.config.ringtone]: [Ring_Synth_04.ogg]
[ro.crypto.fuse_sdcard]: [true]
[ro.crypto.state]: [unencrypted]
[ro.dalvik.vm.native.bridge]: [0]
[ro.debuggable]: [1]
[ro.enableAppScreenshot]: [0]
[ro.factorytest]: [0]
[ro.hardware]: [watch]
[ro.idlemaintenance.disable]: [true]
[ro.opengles.version]: [131072]
[ro.product.board]: [watch]
[ro.product.brand]: [Huami]
[ro.product.cpu.abi2]: [mips]
[ro.product.cpu.abi]: [mips]
[ro.product.cpu.abilist32]: [mips,mips]
[ro.product.cpu.abilist64]: []
[ro.product.cpu.abilist]: [mips,mips]
[ro.product.device]: [watch]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [Huami]
[ro.product.model]: [Amazfit Pace]
[ro.product.name]: [huangheUS]
[ro.revision]: [00000001]
[ro.runtime.firstboot]: [1501060624929]
[ro.secure]: [0]
[ro.serialno]: []
[ro.sf.lcd_density]: [238]
[ro.sn.serial_numbers]: []
[ro.sn.serial_numbers_factory]: []
[ro.wifi.channels]: [13]
[ro.wifi.wifiaddr]: [D8:80:3C:07:0C:D0]
[ro.zygote]: [zygote32]
[selinux.reload_policy]: [1]
[service.adb.tcp.port]: [5555]
[service.bootanim.exit]: [1]
[sys.boot_completed]: [1]
[sys.disable.launcherhome]: [0]
[sys.fastboot.enable]: [false]
[sys.settings_global_version]: [3]
[sys.settings_secure_version]: [9]
[sys.settings_system_version]: [29]
[sys.sysctl.extra_free_kbytes]: [1125]
[sys.uboot.charginglevel]: [96]
[sys.uboot.chargingtime]: [1501059785000]
[sys.usb.config]: [mtp,adb]
[sys.usb.state]: [mtp,adb]
[system_init.startmotioneyes]: [1]
[vold.post_fs_data_done]: [1]
[wifi.interface]: [wlan0]
[wifi.supplicant_scan_interval]: [15]
[wlan.driver.status]: [unloaded]
adb shell pm list features
Code:
feature:reqGlEsVersion=0x20000
feature:android.hardware.audio.low_latency
feature:android.hardware.audio.output
feature:android.hardware.bluetooth
feature:android.hardware.bluetooth_le
feature:android.hardware.location
feature:android.hardware.microphone
feature:android.hardware.screen.landscape
feature:android.hardware.screen.portrait
feature:android.hardware.sensor.accelerometer
feature:android.hardware.sensor.compass
feature:android.hardware.sensor.gyroscope
feature:android.hardware.touchscreen
feature:android.hardware.touchscreen.multitouch
feature:android.hardware.touchscreen.multitouch.distinct
feature:android.hardware.touchscreen.multitouch.jazzhand
feature:android.hardware.type.watch
feature:android.hardware.usb.accessory
feature:android.hardware.wifi
feature:android.software.accessibility
feature:android.software.account
feature:android.software.activity
feature:android.software.alarm
feature:android.software.app_widgets
feature:android.software.appops
feature:android.software.audio
feature:android.software.backup
feature:android.software.batterymanager
feature:android.software.camera
feature:android.software.captioning
feature:android.software.clipboard
feature:android.software.connectivity
feature:android.software.consumer_ir
feature:android.software.country_detector
feature:android.software.device_admin
feature:android.software.device_policy
feature:android.software.display
feature:android.software.download
feature:android.software.dropbox
feature:android.software.fingerprint
feature:android.software.home_screen
feature:android.software.input
feature:android.software.input_method
feature:android.software.input_methods
feature:android.software.jobscheduler
feature:android.software.keyguard
feature:android.software.launcherapps
feature:android.software.layout_inflater
feature:android.software.live_tv
feature:android.software.live_wallpaper
feature:android.software.location
feature:android.software.media_projection
feature:android.software.media_router
feature:android.software.media_session
feature:android.software.netpolicy
feature:android.software.netstats
feature:android.software.network_management
feature:android.software.network_score
feature:android.software.nfc
feature:android.software.notification
feature:android.software.persistent_data_block
feature:android.software.phone
feature:android.software.power
feature:android.software.print
feature:android.software.restrictions
feature:android.software.rttmanager
feature:android.software.search
feature:android.software.sensor
feature:android.software.serial
feature:android.software.servicediscovery
feature:android.software.sip
feature:android.software.sip.voip
feature:android.software.statusbar
feature:android.software.storage
feature:android.software.telecom
feature:android.software.telephony_subscription_service
feature:android.software.textservices
feature:android.software.trust
feature:android.software.uimode
feature:android.software.updatelock
feature:android.software.usagestats
feature:android.software.user
feature:android.software.vibrator
feature:android.software.voice_recognizers
feature:android.software.wallpaper
feature:android.software.wifipasspoint
feature:android.software.wifiscanner
feature:android.software.window
Hi,
I am not sure if you are currently on US Version or Pacified. There is a Watch Self Test that is available in the Lab of Chinese Rom. It runs a test of all hardware.
Settings -> About -> Lab -> Start Self Test
If your accelerator and Gyro don't work, your steps, sleeps cannot be tracked. I suppose you have already mentioned, you Heart Rate sensor is not working. Please wear the watch when you run the test.
Does this test work for you? It doesn't matter if I choose first or second option. The only thing I see is the battery values and the step after shows some numbers with red background. That's all.
madtech360 said:
Hi,
I am not sure if you are currently on US Version or Pacified. There is a Watch Self Test that is available in the Lab of Chinese Rom. It runs a test of all hardware.
Settings -> About -> Lab -> Start Self Test
If your accelerator and Gyro don't work, your steps, sleeps cannot be tracked. I suppose you have already mentioned, you Heart Rate sensor is not working. Please wear the watch when you run the test.
Click to expand...
Click to collapse
Currently on US.. I'll try flashing it to Chinese later to test the watch. but under the US 1.3.3a firmware there is PPG capturing when I tried running it, it just crashed.
Diginix said:
Does this test work for you? It doesn't matter if I choose first or second option. The only thing I see is the battery values and the step after shows some numbers with red background. That's all.
Click to expand...
Click to collapse
If you select the first option (which translates to Test PPG), the watch will perform the below tests in the order listed
Battery Test
Heart Rate Sensor Test
Magnetic (Compass) Test
Pressure (Barometer) Test
MIC Spectrum Test
Vibrator Test
If you select the second option (which translate to Test All), the watch will perform the below test in the order listed
Battery Test
Heart Rate Sensor Test
Battery Consumption Test
ADC Battery Voltage Test
Magnetic (Compass) Test
Accelerator Test
Gyroscope Test
Pressure (Barometer) Test
Ambient Light Sensor Test
LCD Test
Vibrator And Backlight Test
MIC Test
Wifi Test
Blue Tooth Test
GPS Test
Battery Charging Test
ADC Battery Version Test
Apart from the test list and order (which i got by looking at the code), I have no idea how the test is performed and what determines success or failure.
I also get stuck in the Heart Rate Sensor test (with three numbers and Red Background). During retest (by clicking the circular icon at the bottom), by lifting the watch slightly off the wrist and moving it a little , i am able to get past the test. However, i get stuck at the Wifi Test and it does not go past it.
In some tests like Mic, LCD, you need to click the screen or swipe from left (to go back) and indicate success or failure.
The test is also supposed to create a log file in the /sdcard folder, different log file depending on you selected first option or second option.
alexjong said:
Currently on US.. I'll try flashing it to Chinese later to test the watch. but under the US 1.3.3a firmware there is PPG capturing when I tried running it, it just crashed.
Click to expand...
Click to collapse
That's the wrong lab. You are in Huami Lab, but you have to activate the real lab by tapping 7 times the serial number in about screen. Then you will find the lab as last entry in the about section.
PS: No chance to pass the HR test. Tried many times on skin, in air, on white and black undergruound.
Can you post the numbers from HR test, that are valid.
Diginix said:
That's the wrong lab. You are in Huami Lab, but you have to activate the real lab by tapping 7 times the serial number in about screen. Then you will find the lab as last entry in the about section.
PS: No chance to pass the HR test. Tried many times on skin, in air, on white and black undergruound.
Can you post the numbers from HR test, that are valid.
Click to expand...
Click to collapse
I only have 2 test. First is BT HCI snoop log, while the second options is Signal strength,
Diginix said:
That's the wrong lab. You are in Huami Lab, but you have to activate the real lab by tapping 7 times the serial number in about screen. Then you will find the lab as last entry in the about section.
PS: No chance to pass the HR test. Tried many times on skin, in air, on white and black undergruound.
Can you post the numbers from HR test, that are valid.
Click to expand...
Click to collapse
Here is a little video showing the HR Test passing..by moving my finger a little behind the sensor..
Also an image showing the passed value
The logic that is used to check the success or failure below:
Code:
private boolean isPPGOK(int[] results) {
int diff1 = results[1] - results[0];
int diff2 = results[2] - results[1];
if (results[0] < 1500 || results[0] > 4000) {
return false;
}
if (results[1] < 2500 || results[1] > 5500) {
return false;
}
if (results[2] < 3500 || results[2] > 7500) {
return false;
}
if (600 > diff1 || 600 > diff2) {
return false;
}
return true;
}
Damned, with a finger little bit above the center of watch the HR test was passed. Thanks!
As you wrote, the wifi test shows only "..." and nothing happens. But in the signal strength test it fails as well, even I'm connected to an AP.
alexjong said:
I only have 2 test. First is BT HCI snoop log, while the second options is Signal strength,
Click to expand...
Click to collapse
As it seems this features comes first with CN ROM and is missing in latest US. Then your options are limited.
You could reopen your bootloader, if it's closed, and install PACEfied.
Diginix said:
As it seems this features comes first with CN ROM and is missing in latest US. Then your options are limited.
You could reopen your bootloader, if it's closed, and install PACEfied.
Click to expand...
Click to collapse
After flashing back to the PACEfied firmware. I went inside lab, and tried on both options. Only managed to test the battery life, and the 2nd test failed I believe the moment I press the next button.
I encountered the same problem. After flash ROM 1.3.3a to 1.2.29 dev