Related
So after having played enough with my I9100, I keep on running into, the term "debug" all over the place.
However, this term is used differently in different contexts. So things can get confusing, very quickly.
Let me first list the most common places where I have found this. Then let's try to find out what
they all do and if they're related. I don't know all the answers yet!
0. To turn on "USB debugging" (on the phone):
Settings --> Applications --> Development --> USB debugging
This is the most common question for a first time Android owner, and needless to say the simplest to answer.
It allows you to connect your device as a client via USB to a host, for use with Kies, or anything else.
I have this option always on, and can see no reason why to turn it off, unless you are planning to use
your phone in USB host-mode. (Connecting another USB memory/disk/mouse/keyboard etc to you phone.)
1. Some "properties":
Code:
[B]# getprop
[/B]...
[ro.debuggable]: [0]
[persist.service.adb.enable]: [1]
[ro.secdevenc]: [true]
[init.svc.debuggerd]: [running]
[init.svc.adbd]: [running]
...
This is simply pretty printed concatenated version of both (2) AND (3) below.
Q1: What exactly do these properties do?
Code:
[B]# cat /system/build.prop[/B]
...
persist.service.usb.setting=0
ro.secdevenc=true
...
These are the parameters used for building/compiling the Kernel. They also use the proper format for the get/setprops command argument.
Code:
[B]# cat /default.prop[/B]
...
ro.secure=1
ro.debuggable=0
persist.service.adb.enable=0
...
This is your customized extra properties that can also be set somewhere else...but where?
Q2: Where else and how can we set these?
[Editing the file is not possible for a non-rooted phone.]
Code:
[B]# cat /proc/cmdline[/B]
loglevel=4
console=ram
[COLOR=Red]sec_debug.enable=0
sec_debug.enable_user=0[/COLOR]
c1_watchdog.sec_pet=5
[email protected]
s3cfb.bootloaderfb=0x5ec00000
ld9040.get_lcdtype=0x0
consoleblank=0
lpj=3981312
vmalloc=144m
Now this is a rather cryptic line. However, the two "sec_" prefixed lines, refers to
"Samsung Electronic Corporation" and not to "secure", and are probably used for factory testing. These
are properties, but it is possible that they are used to set/read by the read only properties:
ro.debuggable [0]
ro.factorytest [0]
Q3. What exactly do variables do and say?
[And where can they be set?]
2. ServiceMode Debug options
Then we have some "debug" settings in the ServiceMode application that can be started by dialing:
*#197328640#
Then we are presented with a menu with the following options:
Code:
MAIN MENU --> COMMON --> (a) DEBUG INFO
(b) DIAG CONF
MAIN MENU --> (c) DEBUG SCREEN
a) On the "DIAG CONFIG" menu:
Code:
[1] LOG VIA USB
[*]
[2] LOG VIA UART
[3] LOG VIA IPC
[4] SPEED 115200
[5] SPEED 921600
[*]
[6] [COLOR=Red]DBG MSG ON[/COLOR] (toggle)
[7] RAMDUMP OFF (toggle)
[8] DUMP ALL TRACE
This one is about obtaining diagnostic logs from the hardware.
You can generally play with this, as it will not affect the ordinary
behavior of your
phone. Worst case is that it may fill up your phone with huge log files, so keep it off.
The interesting ones are [1-3] and [6].
Q4: Where exactly is the log located and how to read it?
A4: Probably they just go to /proc/kmsg which is also used by logcat and dmesg, but with added tags and verbosity.
Q5: What debug messages are added there, and where do they go?
b) On the "DEBUG INFO" menu:
Code:
[1] MM REJECT CAUSE
[2] LOG DUMP
[3] PCM LOGGING (OFF)
[4] I2S LOGGING (OFF)
This one is probably also about the phone/modem. What is actually logged here I don't know.
Q6: What is actually logged here? (And where does it go?)
c) On the "DEBUG SCREEN" menu:
Code:
[1] BASIC INFORMATION
[2] MM INFORMATION
[3] RR INFORMATION
[4] NEIGHBOR CELL
[5] GPRS INFORMATION
[6] SIM INFORMATION
[7] HANDOVER
[8] PHONE CONTROL
[9] ANTENNA/ADC
This screen is all about hardware debugging and has nothing
to do with connection software, so don't mess with this one!
3. PhoneUtil UART / USB
Code:
UART
([B]o[/B]) MODEM
( ) PDA
USB
( ) MODEM
([B]o[/B]) PDA
If USB is set to MODEM, you will NOT be able to communicate with, or connect your
phone to your PC via USB, since your PC will no longer recognize your device.
Thus it requires special OEM drivers probably only available to Samsung
technicians. AFAIK. (I'd love to have them!)
However, UART is a different story, it can be used to get a serial terminal shell
directly from a hardware connection, but that is for another thread...
-------------------------------------------------------------------------------
Q7:
a) Where are the local UART ports/devices that are used for this?
b) In this case, does MODEM/PDA specifically refer to BP/AP or something else?
-------------------------------------------------------------------------------
Reserved to me to
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.
Hi
I own a Xiaomi Redmi 5 with stock MIUI Global 10.1.2.0 and I've rooted my phone by flashing TWRP and then I installed Magisk-v.16.0 and no-verity-opt-encrypt-6.0 through TWRP.
Now I added "persist.camera.HAL3.enabled" and value to 1 through build.prop editor, but after rebooting camera2api wasn't enabled.
In my Terminal, it shows the following-
rosy:/ $ getprop|grep camera
[camera.aux.packagelist]: [org.codeaurora.snapcam]
[camera.display.lmax]: [1280x720]
[camera.display.umax]: [1920x1080]
[camera.hal1.packagelist]: [com.skype.raider,com.google.android.talk]
[camera.lowpower.record.enable]: [1]
[init.svc.cameraserver]: [running]
[init.svc.qcamerasvr]: [running]
[persist.camera.HAL3]: [1]
[persist.camera.HAL3.enable]: [0]
[persist.camera.HAL3.enabled]: [1]
[persist.camera.gyro.disable]: [0]
[persist.camera.newhht]: [1]
[persist.camera.stats.test]: [5]
[persist.camera.xm.hht]: [0]
rosy:/ $
It is showing three persist.camera.HAL3 lines
I would be glad if anyone could help me
Same to me, try everything in the new MIUI Global Stable and nothing, I thinking maybe the encryption was the problem, in the past version I don't have this problem.
Hi Folks,
I am basically new to Android and Phones but not new to computing. So, when using abbreviations or acronyms, please include in brackets the full description the first time you use them.
I have a New in Box Unlocked LG G5 H850 with Android 7.0 (Android security patch level is 1 November 2016). It was advertised as being a Europe model.
It has one SIM card slot and an SD Memory Card slot.
A check, on the IMEI number, suggests the phone is an Israel sub-variant. The report, produced by the LG SN & Carrier & Country Check on the IMEI.info website, lists the following:
Firmware File: H85030e_00_OPEN_IL_OP_0206.kdz
Firmware Version: H85030E_00
Suffix: AISROP
Carrier Code: ISR
Country Code: IL
Country: Israel
Carrier: ISRAEL
In the list of Device Properties I extracted are the following entries:
[persist.sys.op_name]: [OPEN_IL]
[ro.lge.acc_nt_type]: [NT_TYPE_EU_GLOBAL]
[ro.lge.factoryversion]: [LGH850AT-00-V20a-GLOBAL-COM-OCT-30-2016+0]
[ro.lge.swversion]: [H85020a]
[ro.lge.swversion_arb]: []
[ro.lge.swversion_rev]: [0]
[ro.lge.swversion_short]: [V20a]
[ro.lge.swversion_svn]: [26]
Does anyone know what the AT, at the end of LGH850AT, refers to?
Does anyone know what the following represents?
[persist.sys.sim-changed]: [2]
At the end of the post are various Configuration Properties, I extracted from the phone using the app kDI Device Info system permission, that I thought might be useful in analysing the situation. There were 741 Properties in total.
kDI Device Info system permission | F-Droid - Free and Open Source Android App Repository
androidSpec(s); GSF, Widevine L1/3, microG, Treble, A/B device infos (+otherIDs)
f-droid.org
Besides trying to determine which variant I have exactly, I am also having Bootloop problems associated with connecting to the Internet using WiFi. I think I have tried just about everything I have seen via searching the Internet except rooting the phone and disabling IPv6.
It doesn't matter whether DHCP or a Static IP is being used. When the Internet is accessed by a Browser, the phone almost immediately goes into a Bootloop and the only way to stop it is to turn off Wi-Fi after it restarts.
When the phone was received, the pre-selected Language was English (United Kingdom).
As this is supposed to be a European variant, why are there references to Hong Kong and South-east Asia as indicated by the following Properties?
[net.ims.country]: [HK]
[net.ims.operator]: [OPEN]
[persist.sys.cupss.subca-prev]: [/cust/OPEN_COM_DS/cust_OPEN_HK.prop]
[persist.sys.cupss.subca-prop]: [/cust/OPEN_COM_DS/cust_OPEN_HK.prop]
[ro.build.target_country]: [HK]
[ro.build.target_operator]: [OPEN]
[ro.build.target_region]: [ESA]
[ro.lge.ntcode_mcc]: [FFF]
[ro.lge.opensw]: [HKG-XX]
Why is there no OTA Software Update for Oreo? Should I avoid Oreo? When I checked for a Software Update, the response received indicated that I already had the latest version installed.
Is baseband "MPSS.TH.2.0.c1.4-00041-M8996FAAAANAZM-1.72241.1" known to have WiFi problems. Does this have anything to do with the functionality of Wi-Fi?
[gsm.version.baseband]: [MPSS.TH.2.0.c1.4-00041-M8996FAAAANAZM-1.72241.1]
[net.tcp.buffersize.wifi]: [524288,2097152,4194304,262144,524288,1048576]
[persist.sys.wificountrymcc]: []
[qc.izat.gtp.wifi.low_power]: [UNKNOWN]
[ro.wifi.channels]: []
[wifi.interface]: [wlan0]
[wifi.lge.common_hotspot]: [true]
[wifi.lge.patch]: [true]
[wifi.lge.profileMgr]: [true]
[wifi.lge.supportp2p5g]: [full]
[wifi_ftm.wififtmd_start]: [1]
[wlan.chip.vendor]: [brcm]
[wlan.chip.version]: [bcm43455]
[wlan.driver.status]: [unloaded]
[wlan.lge.concurrency]: [MCC]
[wlan.lge.dcf.enable]: [true]
[wlan.lge.earpiece]: [false]
[wlan.lge.fastroaming]: [true]
[wlan.lge.gons.scan.completed]: [false]
[wlan.lge.gons.scan.scanonly]: [false]
[wlan.lge.passpoint_setting]: [true]
[wlan.lge.softap5g]: [true]
[wlan.lge.softapwps]: [true]
[wlan.lge.supportsimaka]: [yes]
[wlan.lge.traffic.trigger]: [100]
[wlan.lge.wfd.bitratecontrol]: [true]
[wlan.lge.wfd.source]: [true]
[wlan.lge.wifidisplay]: [both]
[wlan.lge.wifidisplay.state]: [0]
[wlan.monitor.status]: [detach]
[net.ims.country]: [HK]
[net.ims.operator]: [OPEN]
[persist.radio.apm_sim_not_pwdn]: [1]
[persist.sys.factory.status]: [6]
[persist.sys.first-boot]: [1]
[persist.sys.first-mcc]: [FFF]
[persist.sys.first-mccmnc]: [FFFFFF]
[persist.sys.lg.fota_silent]: [0]
[persist.sys.op_name]: [OPEN_IL]
[persist.sys.sim-changed]: [2]
[ro.com.google.gmsversion]: [7.0_r2]
[ro.lge.factoryversion]: [LGH850AT-00-V20a-GLOBAL-COM-OCT-30-2016+0]
[ro.lge.swversion]: [H85020a]
[ro.lge.swversion_arb]: []
[ro.lge.swversion_rev]: [0]
[ro.lge.swversion_short]: [V20a]
[ro.lge.swversion_svn]: [26]
[ro.bootimage.build.date]: [Sun Oct 30 10:49:24 KST 2016]
[ro.bootimage.build.date.utc]: [1477792164]
[ro.bootimage.build.fingerprint]: [lge/h1_global_com/h1:7.0/NRD90U/163041049db12:user/release-keys]
[ro.bootloader]: [unknown]
[ro.bootmode]: [unknown]
[ro.build.characteristics]: [default]
[ro.build.date]: [Sun Oct 30 10:49:24 KST 2016]
[ro.build.date.utc]: [1477792164]
[ro.build.description]: [h1_global_com-user 7.0 NRD90U 163041049db12 release-keys]
[ro.build.display.id]: [NRD90U]
[ro.build.fingerprint]: [lge/h1_global_com/h1:7.0/NRD90U/163041049db12:user/release-keys]
[ro.build.flavor]: [h1_global_com-user]
[ro.build.host]: [LGEACI8R3]
[ro.build.id]: [NRD90U]
[ro.build.product]: [h1]
[ro.build.sbp]: [1]
[ro.build.sbp.version]: [31]
[ro.build.tags]: [release-keys]
[ro.build.target_country]: [HK]
[ro.build.target_operator]: [OPEN]
[ro.build.target_region]: [ESA]
[ro.build.type]: [user]
[ro.build.user]: [jenkins]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [163041049db12]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [7.0]
[ro.build.version.sdk]: [24]
[ro.build.version.security_patch]: [2016-11-01]
[ro.product.board]: [msm8996]
[ro.product.brand]: [lge]
[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.device]: [h1]
[ro.product.first_api_level]: [23]
[ro.product.locale]: [en-GB]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [GB]
[ro.product.manufacturer]: [LGE]
[ro.product.model]: [LG-H850]
[ro.product.name]: [h1_global_com]
Thanks!!, M.
Since you're running the first firmware version on the phone, i'm not surprised you're getting odd issues here and there. Install TWRP, format data & system, then flash the complete 20D zip package here to fix any would-be bootloop issues.
Afterwards, you can flash latest Lineage OS 17.1 (Android 10) or beta 18.1 (Android 11), 17.1 is more stable, but both work great. I'm unsure the odd out-of-region properties you're getting listed, but the more important thing is you're on a H850 and (I assume) is already bootloader unlocked.
DrowningInFreedom said:
Afterwards, you can flash latest Lineage OS 17.1 (Android 10) or beta 18.1 (Android 11), 17.1 is more stable, but both work great. I'm unsure the odd out-of-region properties you're getting listed, but the more important thing is you're on a H850 and (I assume) is already bootloader unlocked.
Click to expand...
Click to collapse
Hi,
I found the following Property listed for my phone.
[ro.boot.bl_unlock_complete]: [false]
I also found the following post on XDA.
Tecknight's Aristo 2 Tutorials
TAT TecKnight's Aristo 2 Tutorials series Click the description below to pull up the detailed post Restore your Aristo 2 / 2 + Images/Animations & Carrier Software to stock Access the Operator HiddenMenu on your Aristo 2 / 2 + Install a...
forum.xda-developers.com
2 things I don't want to lose are Camera functionality and HDMI output.
Thanks!!, M.
That post is just talking about if your bootlocker isn't unlockable and if you're still able to flash a custom recovery (in rare circumstances). Luckily, the H850 is officially bootloader unlockable, so you can easily do that and use custom ROMs/recovery.
Here are some more observations about my phone.
My phone has FascistBook, Insanegram and Evernote installed. This aligns with the User Guides for Israel and the UK and Ireland.
However, the guide for Israel makes no mention of the Cell Broadcast feature as do the guides for the UK and Ireland and the Vodafone guide listed on the following page. I can't find the Cell Broadcast feature in the settings nor Tools for my phone. Also, the Vodafone guide only lists Evernote as an installed app.
Codefire - Listing of H850
The Vendor Manifest extracted by kDI Device Info system permission lists the following.
"ALLOWED_GEOLOCATION_ORIGINS": "http://www.google.com http://www.google.co.uk",
Searching online seems to indicate the above 2 URLs as the only ones used. Is that correct?
There is also a H85020v_00_OPEN_EU_OP_0323.kdz (Nougat 7.1.2) file listed on the LG Fan Club website and the LG-ROMs website.
LG H850(LGH850) aka LG G5 - LG-Firmwares.com
LG H850 download the firmware for free! Detailed installation instruction. Video review of the model and its features. User feedback and latest news.
lg-firmwares.com
Download LG Firmware for LG G5 LGH850 Android 7.x Nougat kdz stock GBR Rom
Download Android 7.x Nougat KDZ stock firmware for download with direct link
lg-roms.com
The H85020j_00_OPEN_IL_OP_0112.kdz file would appear to be the equivalent for Israel?
Download LG Firmware for LG G5 LGH850 Android 7.x Nougat kdz stock ISR Rom
Download Android 7.x Nougat KDZ stock firmware for download with direct link
lg-roms.com
I use MX Linux on my Laptop and I do have the Android Debug Bridge installed.
Enabling Developer options, on the phone, indicates that the following options (pertinent to this thread?) can be enabled or set.
Enable OEM unlock
USB debugging
Revoke USB debugging authorizations
Select debug app
Meanwhile, I am going to start browsing through the following thread by @autoprime .
[INFO] Autoprime's All-in-One G5 Thread (Updated April 11 2017)
LG G5 ALL-IN-ONE THREAD Making a thread where I can throw random info about the G5 in one place. Will add to this as we go. See the changelog in post #2 to keep up with what's been added. Woo! As of April 20th this thread is now a Sticky. Not...
forum.xda-developers.com
Thanks!!, M.
DrowningInFreedom said:
Since you're running the first firmware version on the phone, i'm not surprised you're getting odd issues here and there. Install TWRP, format data & system, then flash the complete 20D zip package here to fix any would-be bootloop issues.
Afterwards, you can flash latest Lineage OS 17.1 (Android 10) or beta 18.1 (Android 11), 17.1 is more stable, but both work great. I'm unsure the odd out-of-region properties you're getting listed, but the more important thing is you're on a H850 and (I assume) is already bootloader unlocked.
Click to expand...
Click to collapse
Further analysis, via the Unlocking your Bootloader feature on the LG website, has revealed the following.
Unfortunately, your device( Israel, (ISRAEL), LGH850.ISR )does not support unlocking the bootloader. Your account will be locked if you enter the wrong information more than 9 times.
Click to expand...
Click to collapse
It seems I have been a victim of the following scam.
https://forum.xda-developers.com/t/official-lg-g5-h850-bootloader-unlock.3363040/post-73450344
jimchee said:
Okay, not sure where you ordered your phone from, but if it was China, don't believe anything they tell you, they consistently sell Israel versions of the H850 refreshed with open EU software, I myself have been cheated in this way and I can tell you if comes from Aliexpress it will almost certainly be a reflashed model that when you submit for official unlocking will be an ISRAELI model, through much painstaking experience I have found that you cannot believe anything a Chinese merchant tells you, I will never buy another product ever from Aliexpress unless it is something l am willing to lose all my money on, so for me like a 10 dollar threshold, otherwise I will now stick with retailers who won't steal your money when their merchants outright lie to get your money, the standard when speaking to a Chinese merchant is "everything they tell you will be a lie!"
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
Is it still possible to update to a later official LG release of Android for the Israel variant?
How can I solve the Wi-Fi problem?
Thanks, M.
I've seen H850's on eBay shipping from China that seemed suspicious, and now all these posts make it all click together. You'd have to look for a KDZ to flash with LGUP for your specific varient, however long it received updates.
DrowningInFreedom said:
I've seen H850's on eBay shipping from China that seemed suspicious, and now all these posts make it all click together. You'd have to look for a KDZ to flash with LGUP for your specific varient, however long it received updates.
Click to expand...
Click to collapse
Can these KDZ files be inspected to see what the Device Manifest and Build Properties are as is provided by the kDI app?
I havn't used that program but it's definitly possible to inspect the KDZ/unpack elements, programs like this one can do that but I haven't tried personally.
DrowningInFreedom said:
I havn't used that program but it's definitly possible to inspect the KDZ/unpack elements, programs like this one can do that but I haven't tried personally.
Click to expand...
Click to collapse
Which of the .img files on the following page should I look at to compare to the Manifest and Build Properties data I was able to extract with the kDI app?
Codefire - Listing of H85020A
Thanks, M.
Probably just the H85020a_00_OPEN_EU_OP_1030.kdz
DrowningInFreedom said:
Probably just the H85020a_00_OPEN_EU_OP_1030.kdz
Click to expand...
Click to collapse
With Linux, can I mount and explore the contents of files like devcfg.img?
DrowningInFreedom said:
Probably just the H85020a_00_OPEN_EU_OP_1030.kdz
Click to expand...
Click to collapse
Do you happen to know what File System LG uses for the .img files?
DrowningInFreedom said:
I've seen H850's on eBay shipping from China that seemed suspicious, and now all these posts make it all click together. You'd have to look for a KDZ to flash with LGUP for your specific varient, however long it received updates.
Click to expand...
Click to collapse
If the Israel variant does not have an Unlockable Bootloader, how would it have been possible to Flash an OPEN_EU ROM?
Which tools would have been required to do that?
Is the installation of the OPEN_EU ROM on an Israel variant the reason that the WiFi loses connectivity and goes into a Bootloop?
Thanks!!
They may have used special phone flashing tools like Octoplus or z3x box
DrowningInFreedom said:
They may have used special phone flashing tools like Octoplus or z3x box
Click to expand...
Click to collapse
If the answer to solving my problem is by having an original LG ROM, for the Israel variant, installed, will I be able to do that using LGUP and/or UPPERCUT?
Thanks!
Download LG Firmware Official By IMEI Free Direct Link
Download official KDZ LG Firmware Update by IMEI (ROM) for Update or Unbrick all LG Mobile phone and Tablets
lg-roms.com
Type your IMEI and find the details by this link
Hi all,
Background (ignore this if you like): I have an air con unit that uses an Android Tablet on my wall, it has recently started crashing with the error "gapps has stopped responding". I called the company and they basically told me I need to pay $500+ for a new tablet. I thought this is outrageous, when old air cons didn't use to use an android tablet as their control hub, they would last the life of the home!! So I'm determined to try updating gapps and fixing this tablet myself, rather than give them money.
Actual question: I'm not linux savvy at all and so I would love if someone can help me determine a way to install TWRP on this device. As I believe that is the first step in order for me to start tinkering. I'll be able to create a proper full backup to avoid bricking this thing.
details of the tablet: It has a USB port and I can connect to it fine via ADB from my PC (Windows 11), I can do shell commands etc. I tried running some queries to see which manufacturer makes this unit so i could install TWRP however everything simply appears as the company name. Example:
[ro.build.version.release]: [4.4.2]
[ro.board.platform]: []
[ro.build.version.sdk]: [19]
[ro.fota.platform]: [MTK_KK]
[ro.hardware]: [mt8127]
[ro.mediatek.platform]: [MT8127]
[ro.mediatek.version.sdk]: [2]
[ro.mtk.hardware]: [mt8127]
[ro.product.brand]: [COMPANY NAME]
[ro.product.manufacturer]: [COMPANY NAME]
[ro.product.model]: [COMPANY NAME]
[ro.product.name]: [em_t8270_nand]
Thank you.
Maybe you just don't need Google Apps and can disable it in Apps settings ;-)
The problem is that twrp needs to be made, or maybe you can try hovatek auto twrp recovery porter for mtk?