Huawei P20 lite none of sensors are working (magnetometer, gyroscope, accelerometer,...) - Huawei P20 Lite Questions & Answers

Hi,
i am repairing phones and i recently repaired destroyed Huawei P20 lite. After some testing i found out that the compas is stucked at one direction, same with gyroscope (stucked on 9degrees).
I dont know if its a hardware or software issue, all apps are saying that the sensors arent plugged in. I didnt found anyone with this problem.
Where are these sensors located on board? Is there any way to check their functionality?
Thanks in advance for all the answers, sorry if its miss categorized, never posted something there

premino53 said:
Is there any way to check their functionality?
Click to expand...
Click to collapse
Try these apps:
https://mega.nz/file/VoUGQSZJ#JkDKntsLn-dF91Z_Cbgc_leatgFcsVDrXmCvk5n8WJo
https://mega.nz/file/A4UwXAJT#apVRW48u6moVVEHcnAt1xwm1Gi1R_mi2aUWL8i7NO_8

when i wanna copy from jan tursky app it crash, but it showing the sensors that doesnt work. In aida it doesnt show anything or base info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

premino53 said:
when i wanna copy from jan tursky app it crash, but it showing the sensors that doesnt work. In aida it doesnt show anything or base info
View attachment 5893259View attachment 5893261
Click to expand...
Click to collapse
It looks like a system error. I would try factory reset in stock Recovery and update phone by flashing the service ROM via dload method, or via Wi-fi & eRecovery.

-Alf- said:
It looks like a system error. I would try factory reset in stock Recovery and update phone by flashing the service ROM via dload method, or via Wi-fi & eRecovery.
Click to expand...
Click to collapse
already tried factory, ill try flashing new rom via dload.
Thank you, ill get know if it works

-Alf- said:
It looks like a system error. I would try factory reset in stock Recovery and update phone by flashing the service ROM via dload method, or via Wi-fi & eRecovery.
Click to expand...
Click to collapse
So i downloaded sw from androidhost.ru (different than before) and its still same, still stucked at north and 9degrees.

Hard to say. The sensors work depending on each other (especially the accelerometer and gyroscope), it is enough if one is damaged and almost nothing works. For example, compass needs a functional geomagnetic sensor.
Compass doesn't work in google maps either? (just to be sure...)

-Alf- said:
Compass doesn't work in google maps either? (just to be sure...)
Click to expand...
Click to collapse
no, it doesnt. Where are they located on board? Couldnt find that online. Any way to check them from hw side?

premino53 said:
Where are they located on board?
Click to expand...
Click to collapse

By the way, that screen from AIDA is missing some other sensors - proximity, light sensor... I didn't notice it before. I don't have a P20 lite anymore, I made a screenshot on a Mate 10 lite, jfyi:
Some sensors can be tested via the built-in MMI tests, dial on the phone
*#*#2845#*#*
there are other variants:
28465
2847
2846
You can move around the test using the buttons Power and Vol Down.
What is your current full build number (Settings > About phone)?

Compas test error 702011101
Gyroscope test error 702025102
Gravity sensor 702023102
I dont know whats this one - Capacitance P-0F; software_reason 702024102
Hall sensor dont work
Light sensor error 702013102
Sar sensor 702023102
in 2847 testing code gravity error 702023104
-Alf- said:
What is your current full build number (Settings > About phone)?
Click to expand...
Click to collapse
9.1.0.132(C432E5R1P7) - i noticed that is all sw, now im trying bypass another p20 lite with C782 with safe mode files from C432, i can try update this one with C782

premino53 said:
Compas test error 702011101
Gyroscope test error 702025102
Gravity sensor 702023102
I dont know whats this one - Capacitance P-0F; software_reason 702024102
Hall sensor dont work
Light sensor error 702013102
Sar sensor 702023102
in 2847 testing code gravity error 702023104
9.1.0.132(C432E5R1P7) - i noticed that is all sw, now im trying bypass another p20 lite with C782 with safe mode files from C432, i can try update this one with C782
Click to expand...
Click to collapse
I forgot to say, dont know if it matters, but both of them are google frp bypassed via dload safe mode (already tried flashing new rom, but C432 no C782
edit: not both of them, the second is that im trying to bypass now, but that with not working sensor is already bypassed

you cannot install C782 on C432, you would have to change oeminfo C432 to C782 first.

Have you tried update phone via wi-fi & eRecovery?

-Alf- said:
Have you tried update phone via wi-fi & eRecovery?
Click to expand...
Click to collapse
I assume that it should download sw automaticaly from huawei and it is not using sdcard or otg to update, but its saying getting package info failed. Phone is half charged, placed next to router connected to power.

When even the built-in test can't find any sensor, I really don't know what happened to the phone. Something should appear via ADB, try command
adb shell dumpsys sensorservice
Try downgrading to A8 via
HiSuite, it should work on 9.1.0.132.

-Alf- said:
adb shell dumpsys sensorservice
Click to expand...
Click to collapse
Spoiler
Total 8 h/w sensors, 8 running:
0x0000000b) active-count = 1; sampling_period(ms) = {1.0}, selected = 1.00 ms; batching_period(ms) = {0.0}, selected = 0.00 ms
0x00000011) active-count = 2; sampling_period(ms) = {1.0, 200.0}, selected = 1.00 ms; batching_period(ms) = {0.0, 0.0}, selected = 0.00 ms
Sensor List:
0x00000002) orientation | huawei | ver: 1 | type: android.sensor.orientation(3) | perm: n/a
continuous | minRate=50.00Hz | maxRate=100.00Hz | no batching | non-wakeUp |
0x00000006) gravity | huawei | ver: 1 | type: android.sensor.gravity(9) | perm: n/a
continuous | minRate=50.00Hz | maxRate=100.00Hz | no batching | non-wakeUp |
0x00000007) linear Acceleration | huawei | ver: 1 | type: android.sensor.linear_acceleration(10) | perm: n/a
continuous | minRate=50.00Hz | maxRate=100.00Hz | no batching | non-wakeUp |
0x00000008) rotation Vector | huawei | ver: 1 | type: android.sensor.rotation_vector(11) | perm: n/a
continuous | minRate=50.00Hz | maxRate=100.00Hz | no batching | non-wakeUp |
0x0000000b) HALL sensor | huawei | ver: 1 | type: android.sensor.hall(65538) | perm: n/a
on-change | maxDelay=0us | minDelay=0us | no batching | non-wakeUp |
0x0000000f) significant Motion | huawei | ver: 1 | type: android.sensor.significant_motion(17) | perm: n/a
one-shot | maxDelay=0us | minDelay=-1us | no batching | wakeUp |
0x00000011) step counter | huawei | ver: 1 | type: android.sensor.step_counter(19) | perm: n/a
on-change | maxDelay=0us | minDelay=0us | no batching | non-wakeUp |
0x00000012) geomagnetic Rotation Vector | huawei | ver: 1 | type: android.sensor.geomagnetic_rotation_vector(20) | perm: n/a
continuous | minRate=5.00Hz | maxRate=100.00Hz | no batching | non-wakeUp |
Fusion States:
9-axis fusion disabled (0 clients), gyro-rate= 200.00Hz, q=< 0, 0, 0, 0 > (0), b=< 0, 0, 0 >
game fusion(no mag) disabled (0 clients), gyro-rate= 200.00Hz, q=< 0, 0, 0, 0 > (0), b=< 0, 0, 0 >
geomag fusion (no gyro) disabled (0 clients), gyro-rate= 200.00Hz, q=< 0, 0, 0, 0 > (0), b=< 0, 0, 0 >
Recent Sensor events:
HALL sensor: last 1 events
1 (ts=159.310197370, wall=16:15:05.923) 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00,
Active sensors:
HALL sensor (handle=0x0000000b, connections=1)
step counter (handle=0x00000011, connections=2)
Socket Buffer size = 39 events
WakeLock Status: not held
Mode : NORMAL
3 active connections
Connection Number: 0
Operating Mode: NORMAL
com.huawei.health.manager.PreDaemonService | WakeLockRefCount 0 | uid 10117 | cache size 0 | max cache size 0
step counter 0x00000011 | status: active | pending flush events 0
Connection Number: 1
Operating Mode: NORMAL
com.huawei.powergenie.core.contextaware.UserStateManager | WakeLockRefCount 0 | uid 1000 | cache size 0 | max cache size 0
step counter 0x00000011 | status: active | pending flush events 0
Connection Number: 2
Operating Mode: NORMAL
com.huawei.systemserver.cover.CoverManagerService | WakeLockRefCount 0 | uid 1000 | cache size 0 | max cache size 0
HALL sensor 0x0000000b | status: active | pending flush events 0
0 direct connections
Previous Registrations:
06:47:15 - 0x0000000f pid= 1290 uid= 1000 package=com.android.server.DeviceIdleController
22:30:05 + 0x0000000f pid= 1290 uid= 1000 package=com.android.server.DeviceIdleController samplingPeriod=0us batchingPeriod=0us
16:18:30 - 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654
16:18:30 - 0x00000002 pid= 1290 uid= 1000 package=hidl_client_pid_654
16:18:30 - 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654
16:18:29 + 0x00000002 pid= 1290 uid= 1000 package=hidl_client_pid_654 samplingPeriod=10000us batchingPeriod=0us
16:18:29 + 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654 samplingPeriod=10000us batchingPeriod=0us
16:18:28 + 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654 samplingPeriod=10000us batchingPeriod=0us
16:18:27 - 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654
16:18:27 - 0x00000002 pid= 1290 uid= 1000 package=hidl_client_pid_654
16:18:27 - 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654
16:18:18 + 0x00000002 pid= 1290 uid= 1000 package=hidl_client_pid_654 samplingPeriod=10000us batchingPeriod=0us
16:18:18 + 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654 samplingPeriod=10000us batchingPeriod=0us
16:18:17 + 0x00000007 pid= 1290 uid= 1000 package=hidl_client_pid_654 samplingPeriod=10000us batchingPeriod=0us
16:16:15 - 0x00000008 pid= 7097 uid=10122 package=com.huawei.compass.controller.RotationVectorSensorController
16:16:15 - 0x00000002 pid= 7097 uid=10122 package=com.huawei.compass.ui.page.compass.CompassView
16:16:14 + 0x00000011 pid= 6607 uid=10117 package=com.huawei.health.manager.PreDaemonService samplingPeriod=0us batchingPeriod=0us
16:16:08 + 0x00000008 pid= 7097 uid=10122 package=com.huawei.compass.controller.RotationVectorSensorController samplingPeriod=20000us batchingPeriod=0us
16:16:07 + 0x00000002 pid= 7097 uid=10122 package=com.huawei.compass.ui.page.compass.CompassView samplingPeriod=20000us batchingPeriod=0us
14:15:11 + 0x00000011 pid= 2098 uid= 1000 package=com.huawei.powergenie.core.contextaware.UserStateManager samplingPeriod=200000us batchingPeriod=0us
14:15:05 + 0x0000000b pid= 2082 uid= 1000 package=com.huawei.systemserver.cover.CoverManagerService samplingPeriod=0us batchingPeriod=0us
all detected and running, but only few active, perms are n/a, iam woried about this
9-axis fusion disabled (0 clients), gyro-rate= 200.00Hz, q=< 0, 0, 0, 0 > (0), b=< 0, 0, 0 >
game fusion(no mag) disabled (0 clients), gyro-rate= 200.00Hz, q=< 0, 0, 0, 0 > (0), b=< 0, 0, 0 >
geomag fusion (no gyro) disabled (0 clients), gyro-rate= 200.00Hz, q=< 0, 0, 0, 0 > (0), b=< 0, 0, 0 >
im kinda new to this, so sorry if i miss something

-Alf- said:
Try downgrading to A8 via
HiSuite, it should work on 9.1.0.132.
Click to expand...
Click to collapse
Same

premino53 said:
Same
Click to expand...
Click to collapse
One last chance (if it's a SW problem, it probably is) -
1. install via dload method 8.0.0.126 and get bootloader unlock code using dc-unlocker or hcu-client services (4euros)
Link
There is also a free "potatonv" method, but it might not be the best idea in your case. But it's your choice.
2. Install TWRP 3.2.1. "pretoriano80"
Link
3. In TWRP perform "format data" , reboot into TWRP again, wipe Data, System, Dalvik/Art cache, go back in TWRP menu and flash Hurupdater with 8.0.0.344
Reboot Recovery and perform Factory reset.
HOWTO
But I'm not sure if it will solve your problem, so decide for yourself.
By the way, where are you from if I may ask?

Sorry for delay, i am from Czech Republic.
-Alf- said:
flash Hurupdater with 8.0.0.344
Click to expand...
Click to collapse
should i flash just the Hurupdater+miui 8.0.0.344 or add the files that you sended to the guy you are reffering to in HOWTO?

Related

[ Discussion ] Unlock L9 Bootloader

Ok guys. I've started this thread to continue the technical discussion that was being carried on at @carloswii5 's thread [Guide]Unlock bootloader for Noobs P769. With that said, let's carry on...
Stock Dump Files
[ xloader dumps ]
V20H TMobile USA
[ uboot dumps ]
V20H TMobile USA
[ misc dumps and info ]
V20H TMobile USA - Stock recovery partition dump
V20H TMobile USA - omapconf tool device info dump
V20H TMobile USA - nv partition dump. IMEI and WIFI MAC address removed and replaced with markers. View 'edited_nv_README.txt' for details.
[ Links ]
LG Open Source - Source Code Download for P769
Findings
[ nv.img dump - mmcblk0p7 ]
Orange is the offset where the data starts
Blue is the data found
Code:
@ [B][COLOR=DarkOrange]0x1000[/COLOR][/B] - [COLOR=Blue]15 digit hex number[/COLOR] - IMEI number
@ [COLOR=DarkOrange][B]0x1A00[/B][/COLOR] - [COLOR=Blue]LGP769AT-01-V20h-310-260-AUG-14-2013+00[/COLOR] - Software version
@ [COLOR=DarkOrange][B]0x1C00[/B][/COLOR] - [COLOR=Blue]Series of 31 0x01's and 0x02's[/COLOR] - Unknown ATM
@ [COLOR=DarkOrange][B]0x1E00[/B][/COLOR] - [COLOR=Blue]12 digit hex number[/COLOR] - WIFI MAC address
@ [COLOR=DarkOrange][B]0x3C00[/B][/COLOR] - [COLOR=Blue]L6260_MODEM_SIC_01.1305.00\n[/COLOR] - Baseband version
@ [COLOR=DarkOrange][B]0x6403[/B][/COLOR] - [COLOR=Blue]0x69[/COLOR] - Apparently this value varies from device to device.
Compared V20H TMobile USA nv.bin with V20B EURO nv.bin.
Found differences listed below. This has been a combined effort between myself and @kuma82
At offset 0x1603:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x1603 | 0x01 | 0x02 |
=======================================
Starting at offset 0x1615:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x1615 | 0x02 | 0x02 |
0x161D | 0x02 | 0x01 |
0x1625 | 0x02 | 0x07 |
0x162D | 0x02 | 0x07 |
0x1635 | 0x02 | 0x07 |
0x163D | 0x02 | 0x07 |
0x1645 | 0x02 | 0x07 |
0x164D | 0x02 | 0x07 |
0x1655 | 0x02 | 0x07 |
0x165D | 0x02 | 0x07 |
0x1665 | 0x02 | 0x07 |
0x166D | 0x02 | 0x07 |
=======================================
NOTE: Each piece of data is separated by 8 bytes
Starting at offset 0x1C00:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x1c00 | 0x01 | 0x01 |
0x1c01 | 0x01 | 0x01 |
0x1c02 | 0x01 | 0x01 |
0x1c03 | 0x01 | 0x02 |
0x1c04 | 0x02 | 0x02 |
0x1c05 | 0x01 | 0x01 |
0x1c06 | 0x01 | 0x01 |
0x1c07 | 0x01 | 0x01 |
0x1c08 | 0x02 | 0x02 |
0x1c09 | 0x01 | 0x02 |
0x1c0a | 0x01 | 0x01 |
0x1c0b | 0x01 | 0x01 |
0x1c0c | 0x01 | 0x01 |
0x1c0d | 0x02 | 0x02 |
0x1c0e | 0x02 | 0x02 |
0x1c0f | 0x01 | 0x01 |
0x1c10 | 0x01 | 0x01 |
0x1c11 | 0x01 | 0x01 |
0x1c12 | 0x01 | 0x02 |
0x1c13 | 0x01 | 0x01 |
0x1c14 | 0x01 | 0x01 |
0x1c15 | 0x01 | 0x01 |
0x1c16 | 0x01 | 0x01 |
0x1c17 | 0x02 | 0x02 |
0x1c18 | 0x02 | 0x02 |
0x1c19 | 0x02 | 0x02 |
0x1c1a | 0x02 | 0x02 |
0x1c1b | 0x02 | 0x02 |
0x1c1c | 0x02 | 0x02 |
0x1c1d | 0x01 | 0x01 |
0x1c1e | 0x02 | 0x02 |
=======================================
At offset 0x2200:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x2200 | 0x00 | 0x01 |
=======================================
At offset 0x2202:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x2202 | 0x00 | 0x10 |
=======================================
At offset 0x3400:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x3400 | 0x0b | 0x00 |
=======================================
At offset 0x2600:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x2600 | 0x00 | 0x94 |
=======================================
At offset 0x4800:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x4800 | 0x00 | 0x11 |
0x4801 | 0x00 | 0x01 |
=======================================
At offset 0x4A01:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x4A01 | 0x10 | 0x00 |
=======================================
At offset 0x6403:
Code:
=======================================
OFFSET | V20H | V20B | |
=======================================
0x6403 | 0x69 | 0x04 |
=======================================
And the last one.
Just wanted to say real quick that ill be having a 2nd shot at rooting and unlocking a co-workers l9 lets see what the real deal. My first attempt was good. Maybe it'll be one of two:
1. Like some one mentioned, maybe lg only gave a certain open time limited window and than relocked or what not.
2. Steps are being missed, rushed at highly anxious or hyped moments...lmao
Either way its worth another attempt.
Sent from my LGMS769 using XDA Premium 4 mobile app
What we need is a definitive tutorial on unlocking the bootloader. Some say wait 30 minutes while others say an hour. To root or not to root? Flash the radio.zip or paste it over while using offline flash? This is like one big hot mess...lol. :banghead:
Sent from my LG-P769 using XDA Premium 4 mobile app
---------- Post added at 11:25 PM ---------- Previous post was at 11:21 PM ----------
IMHO....LG closed that window long ago.
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
What we need is a definitive tutorial on unlocking the bootloader. Some say wait 30 minutes while others say an hour. To root or not to root? Flash the radio.zip or paste it over while using offline flash? This is like one big hot mess...lol. :banghead:
Sent from my LG-P769 using XDA Premium 4 mobile app
---------- Post added at 11:25 PM ---------- Previous post was at 11:21 PM ----------
IMHO....LG closed that window long ago.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ill try and see if i can record my process.
Sent from my LGMS769 using XDA Premium 4 mobile app
Here's one for ya... Source code for various P769's is available from LG. What I just downloaded was V20H. It also includes the sources for the kernel. Here's the link .
shinobisoft said:
And the last one.
Click to expand...
Click to collapse
Have you had a chance to compare the nv.img?
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Have you had a chance to compare the nv.img?
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I haven't. Actually just had to re-read your PM to find the link for it. LOL. I read the the first time with TapaTalk.
When I sold my phone I left of here :
http://forum.xda-developers.com/showthread.php?t=2016628
trying to get omap flash to dump some data, Im pretty sure I had it recognizing the phone.
This is only for the P769? you should add it to the title if it is. I have a P768 (a weird variant: P778g) with an unlocked bootloader, if i can extract something useful for you guys ill be happy, i want to help with this.
I'd like that, i'm having problems unlocking my p768, maybe it would help. After all, it's not an exclusive problem of the p769 variant.
Wish you all the best of luck.
Sent from my LG-P768 using xda app-developers app
mato_d007 said:
This is only for the P769? you should add it to the title if it is. I have a P768 (a weird variant: P778g) with an unlocked bootloader, if i can extract something useful for you guys ill be happy, i want to help with this.
Click to expand...
Click to collapse
No this discussion is not limited to the P769.
Sent from my LG-P769 using Tapatalk
Glad to have a new thread finally.
i found this in init. lge. usb. rc
isnt any posibility that this make something to block the unlock method?
# adb only USB configuration
# This should only be used during device bringup
# and as a fallback if the USB manager fails to set a standard configuration
# ADB only(631F) is supported from LG driver V3.8
# Set Mass Storage because U2 LG driver is Currently 3.7
on property:sys.usb.config=adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 1004
write /sys/class/android_usb/android0/idProduct 61A6
write /sys/class/android_usb/android0/bDeviceClass 239
write /sys/class/android_usb/android0/bDeviceSubClass 2
write /sys/class/android_usb/android0/bDeviceProtocol 1
write /sys/class/android_usb/android0/functions mass_storage,adb
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}
this is in the root of the phone
Sent from my LG-P760 using XDA Premium 4 mobile app
andras7008 said:
i found this in init. lge. usb. rc
isnt any posibility that this make something to block the unlock method?
# adb only USB configuration
# This should only be used during device bringup
# and as a fallback if the USB manager fails to set a standard configuration
# ADB only(631F) is supported from LG driver V3.8
# Set Mass Storage because U2 LG driver is Currently 3.7
on property:sys.usb.config=adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 1004
write /sys/class/android_usb/android0/idProduct 61A6
write /sys/class/android_usb/android0/bDeviceClass 239
write /sys/class/android_usb/android0/bDeviceSubClass 2
write /sys/class/android_usb/android0/bDeviceProtocol 1
write /sys/class/android_usb/android0/functions mass_storage,adb
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}
this is in the root of the phone
Sent from my LG-P760 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looks like it's setting up the adb daemon on the device.
Sent from my LG-P769 using Tapatalk
I've been trying like crazy to get my friends new L9s bootloader unlocked with no luck. Then my lg offline tool got uninstalled and I couldnt get it working correct again. Well in one last attempt I loaded the stuff on my neighbors laptop (xp) and gave it one last attempt except I did a few things different and it WORKED MY FIRST TRY! Now I think it may of been the steps I skipped/ changed that made it work. Now to what I did. First I flashed v10g except this time I used the 760 version. I ran the bin file in the ICS rootguide folder instead of JB. I then proceeded to flashing v20b as shown in the video how-to except I DID NOT swap the bin file for root instead I added the radio while flashing. After it was complete I ran the bin file from ICS in rootguide again. I let the phone sit for 45 mins on data followed by 45 mins on wifi. Checked adb devices and it did not reconize it so I ran the JB bin file. Checked devices again, it reconized it. Typed the command and it rebooted right to the unlock screen! I should also add my first failed attempts was on windows 8 x64. Hope this helps someone else get it done! I almost gave up on it, luckly I did that one last try!
Sent from my LGMS769 using XDA Premium 4 mobile app
lwg45714 said:
I've been trying like crazy to get my friends new L9s bootloader unlocked with no luck. Then my lg offline tool got uninstalled and I couldnt get it working correct again. Well in one last attempt I loaded the stuff on my neighbors laptop (xp) and gave it one last attempt except I did a few things different and it WORKED MY FIRST TRY! Now I think it may of been the steps I skipped/ changed that made it work. Now to what I did. First I flashed v10g except this time I used the 760 version. I ran the bin file in the ICS rootguide folder instead of JB. I then proceeded to flashing v20b as shown in the video how-to except I DID NOT swap the bin file for root instead I added the radio while flashing. After it was complete I ran the bin file from ICS in rootguide again. I let the phone sit for 45 mins on data followed by 45 mins on wifi. Checked adb devices and it did not reconize it so I ran the JB bin file. Checked devices again, it reconized it. Typed the command and it rebooted right to the unlock screen! I should also add my first failed attempts was on windows 8 x64. Hope this helps someone else get it done! I almost gave up on it, luckly I did that one last try!
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What root guide are you referring to?
lwg45714 said:
I've been trying like crazy to get my friends new L9s bootloader unlocked with no luck. Then my lg offline tool got uninstalled and I couldnt get it working correct again. Well in one last attempt I loaded the stuff on my neighbors laptop (xp) and gave it one last attempt except I did a few things different and it WORKED MY FIRST TRY! Now I think it may of been the steps I skipped/ changed that made it work. Now to what I did. First I flashed v10g except this time I used the 760 version. I ran the bin file in the ICS rootguide folder instead of JB. I then proceeded to flashing v20b as shown in the video how-to except I DID NOT swap the bin file for root instead I added the radio while flashing. After it was complete I ran the bin file from ICS in rootguide again. I let the phone sit for 45 mins on data followed by 45 mins on wifi. Checked adb devices and it did not reconize it so I ran the JB bin file. Checked devices again, it reconized it. Typed the command and it rebooted right to the unlock screen! I should also add my first failed attempts was on windows 8 x64. Hope this helps someone else get it done! I almost gave up on it, luckly I did that one last try!
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You see! im almost completely positive some people are missing steps lol... Cant wait to get my hands on my coworkers l9 and try a 2nd time.
Sent from my LGMS769 using XDA Premium 4 mobile app

LG Optimus L3 II E430 E431 E425 E435 ? [ROOT/BOOTLOADER/kernel/rom][TEAM OPTIMA]

E430​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DESCRIPTION:
Code:
GENERAL 2G Network GSM 850 / 900 / 1800 / 1900
3G Network HSDPA 900 / 2100
SIM Mini-SIM
Announced 2013, February
Status Available. Released 2013, April
BODY Dimensions 102.6 x 61.1 x 11.9 mm (4.04 x 2.41 x 0.47 in)
Weight 107 g (3.77 oz)
DISPLAY Type IPS LCD capacitive touchscreen
Size 240 x 320 pixels, 3.2 inches (~125 ppi pixel density)
Multitouch Yes
SOUND Alert types Vibration, MP3 ringtones
Loudspeaker Yes
3.5mm jack Yes
MEMORY Card slot microSD, up to 32 GB
Internal 4 GB (1.6 GB user available), 512 MB RAM
DATA GPRS Class 12 (4+1/3+2/2+3/1+4 slots), 32 - 48 kbps
EDGE Class 12
Speed HSDPA, 7.2 Mbps; HSUPA, 5.76 Mbps
WLAN Wi-Fi 802.11 b/g/n, Wi-Fi hotspot
Bluetooth Yes, v3.0 with A2DP, HS
USB Yes, microUSB v2.0
CAMERA Primary 3.15 MP, 2048 x 1536 pixels
Features Geo-tagging
Video Yes, [email protected]
Secondary No
FEATURES OS Android OS, v4.1.2 (Jelly Bean)
Chipset Qualcomm MSM7225A Snapdragon
CPU 1 GHz
GPU Adreno 200
Sensors Accelerometer, proximity, compass
Messaging SMS (threaded view), MMS, Email, Push Email, IM
Browser HTML
Radio FM radio
GPS Yes, with A-GPS support
Java Yes, via Java MIDP emulator
Colors Indigo Black, Titanium silver, White
- SNS integration
- MP4/H.264/H.263/WMV player
- MP3/WAV/WMA/eAAC+ player
- Google Search, Maps, Gmail
- YouTube, Google Talk
- Document viewer
- Photo viewer
- Organizer
- Voice memo
- Predictive text input
BATTERY Type Li-Po
Capacity 1540 mAh
Stand-by Up to 608 h (2G) / Up to 700 h (3G)
Talk time Up to 11 h 30 min (2G) / Up to 10 h (3G)
MISC SAR US 1.02 W/kg (head) 1.23 W/kg (body)
SAR EU 1.00 W/kg (head) 0.52 W/kg (body)
Warning :
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features of this Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* But since i'm a nice dude i will try to guide you anyway:)
WINDOWS ROOTING GUIDE
*this guide will work on most android phones ​
Download THIS PROGRAM (VROOT)
Install Program
Enable USB Debugging in settings (TICK CHECK-BOX IN Settings>>>Developer options>>>USB debugging)
Plug your phone to PC using usb cable in "LG software" mode
If you are connecting your phone to your pc for the first time you need to install lg drivers from first autorun when phone plugged in ( If autorun disabled navigate to lg removable drive and run LGAutoRun.exe) follow on-screen instructions or download drivers from LG Official Website HERE
Ensure all drivers have installed correctly (no yellow triangles in "Device Manager")
Run VROOT As Administrator On PC
program will connect to your phone and tell you your phone model and if phone is rooted (obviously our's is not)
Click ROOT in right bottom corner
program will install Chinese sync/managment app (you can remove app later) on your phone and install Kinguser superuser app on your phone (you can replace this with your favourite superuser app <i kept Kinguser and i'm happy>)
Your phone will reboot when completed
BOOTLOADER = UNLOCKED AND CWM READY !!!
THANKS TO Cobmaster AND PlayfulGod WE HAVE UNLOCKED BOOTLOADER AND HAVE WORKING CWM v6.0.4.8
WINDOWS INSTALLER HERE *readme.txt
LINUX-UNIVERSAL INSTALLER HERE *THANKS TO Cobmaster
.APK FOR NON PC INSTALL HERE *THANKS TO PlayfulGod
*These will unlock bootloader install and CWM recovery
YOU CAN ENTER RECOVERY USING BUTTON COMBO !!! !!!
​
1. PRESS AND HOLD "HOME" BUTTON
2. PRESS "VOL-" AND "POWER" BUTTONS TOGETHER FOR ~2.5-3 SECONDS AND RELEASE
3. KEEP HOLD OF "HOME" BUTTON UNTIL RECOVERY BOOTED​
Here you can find apk to try on other devices:
MAKE SURE YOU FULL BACKUP AND ARE READY FOR SOFT/HARD BRICK
IT MIGHT BREAK YOU PHONE !!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
OK ONLY IF YOU ARE 100% SURE
WE (NO ONE BUT YOURSELF) TAKE NO RESPONSIBILITY IF THIS WILL DO ANYTHING BAD TO YOUR DEVICE
PlayfulGod said:
Heres the link to the new app build that getprops ro.product.device = vee3e or vee3
Click to expand...
Click to collapse
*if your model is E425 L3II replace boot.img with THIS ONE (1.1ghz overclock E425 S=off )
*if your model is E435 L3II Dual Sim replace boot.img with THIS ONE (1.1ghz overclock E435 S=off )
1. DEVICETREE = CWM READY THANKS TO PlayfulGod LINK HERE
NEEDS FILLING TO BUILD KERNEL/ROM'S
*i'm trying at the moment but it doesn't seems to be going anywhere
ALL AVAILABLE DATA HERE:
Dump of all the partitions using dd if= of= command DROPBOX HERE
Original JB kernel / android source DROPBOX HERE Containing kernel.tar.gz 109 MB<<<Click for tree android.tar.gz 63.8 MB<<<Click for tree
Stock boot partition extracted DROPBOX HERE *zImage and ramdisk
Cwm builder extracted STOCK recovery partition DROPBOX HERE
2. KERNEL = (DRIVERS/OVERCLOCK/DPI{smoothing?})
Yess Thanks To @Cobmaster !!!
We have 1.2Ghz Overclock also its possible to change the DPI setting (I use 105 and "roboto enchanced" font)
1.2Ghz S=off latest build for e430 ONLY. included more governors and I/O shedulers boot.img * download and "dd" flash or replace boot.img in freedom tools above
Stock JB kernel source 3.4.0 DROPBOX HERE
Modded JB kernel by cobmaster GIT HERE​
3. PORTING/MAKING CUSTOM ROM TWEAKS
SEE POST 2*Updating...
I have Ubuntu 13.10 x64 // Windows 7 x86 dual boot sdk/build environments set-up.
AND DEVICE FOR TESTING
I have managed to access few of the partitions, put a name to them Here is what i got till now: *If anyone can help resolve more partitions please do so
Code:
[B] *---------------------------- PartitionTable Info --------------------------*
Index| Partition Name | Logical Start Offset | Logical Size (KB) | File Offset | Physical Start Offset | Partition Size (KB) | Device Location
02 | QCSBL | 0xFFFFFFFF | 0x841CFBCD ( 949734KB) | 0x 100000 | 0x 0 | 0x 829 ( 1044KB) | /dev/block/mmcblk0p2
03 | OEMSBL | 0x3445474C | 0x 3033 ( 6169KB) | 0x 180000 | 0x 829 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p3
04 | EXT | 0x 0 | 0x 0 ( 0KB) | 0x 280000 | 0x 2829 | 0x 1D7D7 ( 60395KB) | /dev/block/mmcblk0p4
05 | APPSSBL | 0x 0 | 0xFFFFFFFF (4194303KB) | 0x 300000 | 0x 20000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p5
06 | WALLPAPER | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 22000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p6
07 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 24000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p7
08 | misc | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 26000 | 0x C000 ( 24576KB) | /dev/block/mmcblk0p8
09 | APPS | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 380000 | 0x 32000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p9
10 | MODEM_ST1 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 38000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p10
11 | MODEM_ST2 | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p11
12 | MODEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x A00000 | 0x 3C000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p12
13 | MODEM_BACKUP | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 1D80000 | 0x 4A000 | 0x E000 ( 28672KB) | /dev/block/mmcblk0p13
14 | SYSTEM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3100000 | 0x 58000 | 0x 1D0000 ( 950272KB) | /dev/block/mmcblk0p14
15 | PERSIST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3D100000 | 0x 228000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p15
16 | CACHE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 22E000 | 0x 140000 ( 655360KB) | /dev/block/mmcblk0p16
17 | RECOVERY | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3DD00000 | 0x 36E000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p17
18 | DRM | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 374000 | 0x 4000 ( 8192KB) | /dev/block/mmcblk0p18
19 | FOTA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 378000 | 0x 6000 ( 12288KB) | /dev/block/mmcblk0p19
20 | USERDATA | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 37E000 | 0x 38C000 (1859584KB) | /dev/block/mmcblk0p20
21 | DLOAD | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70A000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p21
22 | BOOT_LOGO_IMAGE | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E400000 | 0x 70C000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p22
23 | MPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 70E000 | 0x 8000 ( 16384KB) | /dev/block/mmcblk0p23
24 | ENCRYPT | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 716000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p24
25 | CUST | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 3E480000 | 0x 718000 | 0x 10000 ( 32768KB) | /dev/block/mmcblk0p25
26 | rct | 0xFFFFFFFF | 0xFFFFFFFF (4194303KB) | 0x 40280000 | 0x 728000 | 0x 2000 ( 4096KB) | /dev/block/mmcblk0p26
[/B]
Just a Tip
IF someone is pissed off like me when you plug your phone to usb and have to click 3 times before phone connects
1. DIAL 3845#*430# ]425/435[
2. UN-CHECK BOX IN: "Settings">>>"Auto run">>>"AutoRun Enable"
3. Reboot (not sure if necessary but i did)
NO MORE CHECKING FOR DRIVERS / SKIP EVERY-TIME YOU PLUG YOUR PHONE IN
EXTRA CREDITS TO :
Slipsystem
TEAM OPTIMA
x13n0114
linuxxxx
And others
*if you feel left out please pm/mention
Reserve [Updated]
1st ? MOD for E430 LG L3 II Beta State do not use unless you know what you are doing
slipsystem has managed to port he's SLIMSYSTEM MOD to our device.
for info on he's mod go here
I have tested it on my device and there is no errors as such.
some features of the mod might not work at the moment as its a alpha pre-view
please do adb pull /system (to securely fully backup) GUIDE ON ADB
before running this as we cannot confirm compatibility with every firmware yet
(we need people to test on their devices and post fw version (i.e. V10C_00) any errors logcat and screen much appreciated )
PLEASE DOWNLOAD AND RUN THIS
then zip the folder called slipsystem then upload it with a link to help us develop further
Please let us know if MOD works on your device.
Things that may not work (all to disappear)
Maybe left over apps/data from debloat
statusbar systemui
Features (more to come)
*Build.prop Tweaks
* Debloat
* Mod SystemUI
* LG Optimus G Lock
* Multi User
* App Replacements
* Init.d Support
* Ads Block
Q/A
Ota Updater is working!!.
Will we get updates?
Yes, if you guys keep in touch and send us the files that we need.
FIRST 2 ATTACHED IMAGES ARE SCREENS BEFORE
LAST 2 ATTACHED IMAGES ARE SCREENS AFTER
Also stay tuned to THIS thread
@slipsystem @AwesomeSMS
I asked lg if we are able to unlock The e430 bootloader but they said it is not Possible right now.
Sent from my Kindle Fire HD 7 using XDA Premium 4 mobile app
TESTERS
Testers for roms and such:
E430
http://forum.xda-developers.com/member.php?u=4782028 @Aimbot91
http://forum.xda-developers.com/member.php?u=5238274 @dadziokPL
http://forum.xda-developers.com/member.php?u=4302324 @Cobmaster
http://forum.xda-developers.com/member.php?u=4989941 @x13n0114
http://forum.xda-developers.com/member.php?u=3542146 @Daniolki
http://forum.xda-developers.com/member.php?u=5483119 @AwesomeSMS
E425
http://forum.xda-developers.com/member.php?u=5299788 @29y6145
if you want to be added or removed from list please quote or pm me
IGGYVIP said:
I want to unlock/bypass bootloader, probably update kernel and make/port custom rom (CM preferably)
For e430 e430
I know its a lot to do and that i will need a lot of help but it needs to be done
I know basics about the whole process
I have a lot of spare time
I have the phone for testing (not scared of bricking [i will push the life back to it])
I'm very good at research and spamming manufactures for datasheets/drivers etc.
I need some experienced dev to tell me exact what to look for
What would be EXACT steps trough the process of
1 BOOTLOADER = UNLOCKING / 2ND BOOT ?
2 KERNEL = ? (DRIVERS/OVERCLOCK/DPI{smoothing?})
3 PORTING/MAKING CUSTOM ROM (DRIVERS ETC.)
Please someone ( @-CALIBAN666- @linuxxxx @szymel0 ANYONE ) show me the right direction
@AwesomeSMS please help
Click to expand...
Click to collapse
sorry but i am at start of my android experience
i study technology in my country at high school however this is my first android smartphone
in this month i understood a lot of things maybe i can help you in somethings but i am not so big to port rom or rebuild bootloader
if you have informations tell me i would like to understand and learn
We are gonna need all the help we can get. Thank you!!
You can't have any rom
sorry
no one can develop on those, because mediatek is not developer friendly, they don't release any kind of driver for soc so ayone can compile a rom / kernel without them
my gf just bought the phone and want to see cm11 running on it like on my phone
so, how can we support your development?
we are both non it people, living a alternative live in the woods
linuxxxx said:
You can't have any rom
sorry
no one can develop on those, because mediatek is not developer friendly, they don't release any kind of driver for soc so ayone can compile a rom / kernel without them
Click to expand...
Click to collapse
LG L3 2 isn't MTK like the LG l5 2. This phone has no devs. That's Why
Sent from my LG-E430 using XDA Premium 4 mobile app
Hmmm
linuxxxx said:
You can't have any rom
sorry
no one can develop on those, because mediatek is not developer friendly, they don't release any kind of driver for soc so ayone can compile a rom / kernel without them
Click to expand...
Click to collapse
i have original JB kernel / system source
E430(Optimus L3II)_Android_JB_E43010b containing
kernel.tar.gz 109 MB
android.tar.gz 63.8 MB
aren't drivers included in this package ?
Can someone run this tool
https://dl.dropboxusercontent.com/u/51036208/Android/SlimSystem/L3 II/ForPort.zip
then zip the folder called slipsystem on your C drive
then upload it with a link
Okay! I just rooted my phone.
Sent from my LG-E430 using XDA Premium 4 mobile app
slipsystem said:
Can someone run this tool
https://dl.dropboxusercontent.com/u/51036208/Android/SlimSystem/L3 II/ForPort.zip
then zip the folder called slipsystem on your C drive
then upload it with a link
Click to expand...
Click to collapse
AwesomeSMS said:
Okay! I just rooted my phone.
Sent from my LG-E430 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
anyone interested ?
system patrtition tree list.txt
full framework.zip
e430
WOW
AwesomeSMS said:
Okay! I just rooted my phone.
Sent from my LG-E430 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how come you didnt root b4 ?
AwesomeSMS said:
Okay! I just rooted my phone.
Sent from my LG-E430 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
nice you find a way to root the new firmware?
---------- Post added at 08:39 PM ---------- Previous post was at 08:36 PM ----------
IGGYVIP said:
anyone interested ?
system patrtition tree list.txt
full framework.zip
e430
Click to expand...
Click to collapse
nice thanks for this.
one thing I have noticed is that all the files are bigger than mine? strange I would have said it would be the other way around
---------- Post added at 08:52 PM ---------- Previous post was at 08:39 PM ----------
download taking its time. only 47 minutes left and I can start developing for your device
anyone want to be my tester?
slipsystem said:
nice thanks for this.
one thing I have noticed is that all the files are bigger than mine? strange I would have said it would be the other way around
---------- Post added at 08:52 PM ---------- Previous post was at 08:39 PM ----------
download taking its time. only 47 minutes left and I can start developing for your device
anyone want to be my tester?
Click to expand...
Click to collapse
lol it took less time to upload using my milestone 4 shared must be baaad
can you upload yours 4 compare ?
why you think yours should bigger ?
its zipped as store no compression
COUNT ME IN 4 TESTING
Ok if anyone is interested in trying. thanks to
@AwesomeSMS and @IGGYVIP for contributing there framework and apks
I managed to port my mod to your device.
for info on my mod go here
http://forum.xda-developers.com/showthread.php?t=2650588
I havent tested it yet this is a theoretical build so it might not work.
please do adb pull /system
before running this as I haven't tested it yet.
https://dl.dropboxusercontent.com/u/51036208/Android/SlimSystem/L3 II/slimsystemtest.zip
Please let me know if this works. Take some screenshots if you can.
Things that may not work
Calculator
Maybe left over apps from debloat
Features
Xperia Media Apps
Xperia Keyboard with swipe control
init.d support
Build.prop Tweaks
Quick Launch Status bar
Potato status bar gestures
Q/A
Ota Updater is not working?
I haven't added it to my ota account yet.
Will we get updates?
Yes, if you guys keep in touch and send me the files that I need.
Keyboard has switched to google voice?
you need to change the keyboard under settings.
why haven't the status bar icons changed
this mod was by gabi4175 i am still finding the icons he replaced.
slipsystem said:
Ok if anyone is interested in trying.
Click to expand...
Click to collapse
YES downloading as we speak
UPDATE:
Flashed no problem no errors
everything seems(i cannot check mobile network as my imei is damaged) to be working
ANYONE who wants to keep google chrome browser remove
Code:
rm /system/app/ChromeWithBrowser.apk
rm /system/app/ChromeWithBrowser.odex
rm /data/app/com.android.chrome-1.apk
out of slimsystem.sh
I want to keep mine
awesome work dude
after multiple reboots (by me) i have spotted it always opens browser on startup
screen included
ROOT
Rooted for a while (new software V**x_00 ?) here are screens
used superoneclick newest? and vroot superoneclick gave some errors and vroot finished proper
when i tried only with vroot it was rooted but not the shell i couldnt get su in terminal superoneclick must have done something because now i can
@AwesomeSMS
IGGYVIP said:
YES downloading as we speak
UPDATE:
Flashed no problem no errors
everything seems(i cannot check mobile network as my imei is damaged) to be working
ANYONE who wants to keep google chrome browser remove
Code:
rm /system/app/ChromeWithBrowser.apk
rm /system/app/ChromeWithBrowser.odex
rm /data/app/com.android.chrome-1.apk
out of slimsystem.sh
I want to keep mine
awesome work dude
after multiple reboots (by me) i have spotted it always opens browser on startup
screen included
Click to expand...
Click to collapse
Ok this is something to do with a init.d script. Just need to figure out which one. And to think I thought I was going crazy.

Galaxy Mini S3 "sleeps" and cannot recieve msgs/calls

I have a Samsung S3 mini, which I flashed with Kit Kat Cyanogenmod 11.0 from novafusion.pl
Everything in the installation was OK.
However my phone randomly falls "sleep" and cannot recieve msgs or calls. I have to turned Airplane mode on and off, to give it a "shake" and "wake" it up.
These is a report from Logcat, plus the log from yesterday,
Code:
build.board: montblanc
build.bootloader: unknown
build.brand: samsung
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: golden
build.display: cm_golden-userdebug 4.4.4 KTU84Q d39c1e8ca0 test-keys
build.fingerprint: samsung/cm_golden/golden:4.4.4/KTU84Q/d39c1e8ca0:userdebug/test-keys
build.hardware: samsunggolden
build.host: novafusion.pl
build.id: KTU84Q
build.manufacturer: samsung
build.model: GT-I8190
build.product: cm_golden
build.radio: unknown
build.serial: 47900592d6cb30c0
build.tags: test-keys
build.time: 1436279173000
build.type: userdebug
build.user: root
version.codename: REL
version.incremental: d39c1e8ca0
version.release: 4.4.4
version.sdk_int: 19
I can't attach my full log because I'm new on the forum.
This is the top 30 unique lines processed by me in Bash,
Code:
[email protected]:~/Dropbox# cat 2015-07-28-10-25-50.txt | grep " E/" | cut -d "/" -f 2- | sort | uniq -c | sort -rn | head -n 30
166 Drm ( 1669): Failed to open plugin directory /vendor/lib/mediadrm
144 SpannableStringBuilder( 4288): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
118 ActivityThread( 2565): Failed to find provider info for com.google.android.wearable.settings
87 AuthorizationBluetoothService( 2483): Proximity feature is not enabled.
85 ConnectivityService( 2088): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_use_userconfig: open failed: ENOENT (No such file or directory)
85 ConnectivityService( 2088): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_delack_seg: open failed: ENOENT (No such file or directory)
70 audio_a2dp_hw( 1669): adev_set_parameters: ERROR: set param called even when stream out is null
59 WifiNative-wlan0( 2088): doBoolean: disable
57 WifiNative-wlan0( 2088): doBoolean: enable
49 CallDetails( 2409): list is null in setConfUriList
48 ActivityThread(14438): Failed to find provider info for com.google.android.wearable.settings
31 MDM ( 2388): [64] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
31 BluetoothPhoneService( 2409): Could not get a handle on Connection object for the call
30 MDM ( 2388): [89] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
26 MDM ( 2388): [67] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
25 LocationReceiver( 6879): Received bad location: null
17 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x414b3f80 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
16 SpannableStringBuilder(25691): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
15 YSNP_TAG( 5072): [NetworkHelper] : [thread:1]checkNetworkChange() - no active network!
14 bp ( 2374): onStartInput event aborted: com.touchtype.keyboard.c.ag: could not obtain extracted text (class com.touchtype.keyboard.c.ag)
13 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x411acd98 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
11 ENSWrapper( 1673): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x4161b3a0 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x4d2efb3e ]
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x419f8f40
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x416a0f08
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x41490f68
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x412c9f58
9 ENSWrapper( 1673): return OMX_ErrorUnsupportedIndex - SetConfig OMX.ST.AFM.speech_proc h=0x412c8f48
8 VFM ( 1669): ! getSupportedVideoSettings RETURN_XXX_IF_WRONG, condition=(index<mNbVideoSettingsSupported[nPortIndex]), error=-2147479538(0x8000100e)(OMX_ErrorNoMore) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:407
8 VFM ( 1669): ! getSupportedProfileLevel RETURN_XXX_IF_WRONG, condition=(index<mNbProfileLevelSupported), error=-2147479538(0x8000100e)(OMX_ErrorNoMore) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:379
8 VFM ( 1669): ! getParameter RETURN_OMX_ERROR_IF_ERROR, condition=pParam->getIndexParamVideoProfileLevelQuerySupported(pt), error=-2147479538(0x8000100e)(_error) /home/se.infra/jenkins1/workspace/HUDSON_GA_JELLYBEAN_GOLDEN_EUROPEN-PROD-XX/android/vendor/st-ericsson/variant/multimedia/video/vfm/src/VFM_Component.cpp:140
carlosalomar said:
I have a Samsung S3 mini, which I flashed with Kit Kat Cyanogenmod 11.0 from novafusion.pl
Everything in the installation was OK.
However my phone randomly falls "sleep" and cannot recieve msgs or calls. I have to turned Airplane mode on and off, to give it a "shake" and "wake" it up.
These is a report from Logcat, plus the log from yesterday,
I can't attach my full log because I'm new on the forum.
This is the top 30 unique lines processed by me in Bash
Click to expand...
Click to collapse
Hi, you might get better results asking in your specific device help forum.
http://forum.xda-developers.com/galaxy-s3-mini/help
Good luck!

Xiaomi MI Box 3 MDZ-16-AB Boot Log and UART Location

Hey Guys,
I've been tinkering with my MI Box as I've been having packet loss issues with it, long story short its bricked, here is the bootlog + UART Pins if anyone is interested:
Boot Log:
Code:
TE: 98645
BL2 Built : 18:13:36, Jun 17 2016.
gxl g176ecdb - [email protected]
rn5t567_power_init
Board ID = 1
CPU clk: 1200MHz
DDR3 chl: Rank0+1 @ 912MHz - PASS
DQS-corr enabled
DDR scramble enabled
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
aml log : R1024 check pass!
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01700000, size: 0x0000d600
aml log : R1024 check pass!
Load bl31 from eMMC, src: 0x00020200, des: 0x01700000, size: 0x00014400
aml log : R1024 check pass!
Load bl32 from eMMC, src: 0x00038200, des: 0x01700000, size: 0x0002ee00
aml log : R1024 check pass!
Load bl33 from eMMC, src: 0x00068200, des: 0x01700000, size: 0x0007f800
aml log : R1024 check pass!
NOTICE: BL3-1: v1.0(debug):ed1aadc
NOTICE: BL3-1: Built : 11:06:24, May 31 2016
aml log : bl31 detect secure boot !
[Image: gxl_v1.1.3118-31ffc57 2016-09-27 10:04:49 [email protected]]
OPS=0x82
ef be ad de d f0 ad ba ef be ad de bl30:thermal init err
[0.626102 Inits done]
secure task start!
high task start!
low task start!
INFO: BL3-1: Initializing runtime services
INFO: BL3-1: Initializing BL3-2
INFO: BL3-2: ATOS-V1.4-gb959fd4 #13 Tue Sep 6 15:28:58 CST 2016 arm
INFO: BL3-2: chip version = RevA (21:A - 0:0)
INFO: BL3-2: crypto engine DMA
INFO: BL3-2: secure time TEE
INFO: BL3-1: Preparing for EL3 exit to normal world
INFO: BL3-1: Next image address = 0x1000000
INFO: BL3-1: Next image spsr = 0x3c9
U-Boot 2015.01-g57a5217-dirty (Jan 25 2017 - 11:17:54), Build: jenkins-Once_MP-750
DRAM: 2 GiB
Relocation Offset is: 76ef5000
register usb cfg[0][1] = 0000000077f64870
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
SARADC channel(1) is 0x1d2.
adcAvg hw_version is 353
MMC: aml_priv->desc_buf = 0x0000000073ef56e0
aml_priv->desc_buf = 0x0000000073ef7870
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
[mmc_init] mmc init success
mmc read lba=0x4000, blocks=0x400
start dts,buffer=0000000073ef9f30,dt_addr=0000000073ef9f30
parts: 12
00: cache 0000000010000000 2
01: logo 0000000000300000 1
02: encrypt 0000000000100000 1
03: recovery 0000000002000000 1
04: tee 0000000000800000 1
05: crypt 0000000002000000 1
06: misc 0000000002000000 1
07: boot 0000000001400000 1
08: system 0000000060000000 1
09: persist 0000000000800000 4
10: panic 0000000000400000 4
11: data ffffffffffffffff 4
get_dtb_struct: Get emmc dtb OK!
overide_emmc_partition_table: overide cache
[mmc_get_partition_table] skip partition cache.
Partition table get from SPL is :
name offset size flag
===================================================================================
0: bootloader 0 400000 0
1: reserved 400000 800000 0
2: cache c00000 10000000 2
3: env 10c00000 400000 0
4: logo 11000000 300000 1
5: encrypt 11300000 100000 1
6: recovery 11400000 2000000 1
7: tee 13400000 800000 1
8: crypt 13c00000 2000000 1
9: misc 15c00000 2000000 1
10: boot 17c00000 1400000 1
11: system 19000000 60000000 1
12: persist 79000000 800000 4
13: panic 79800000 400000 4
14: data 79c00000 158400000 4
mmc read lba=0x2000, blocks=0x2
mmc read lba=0x2002, blocks=0x2
mmc_read_partition_tbl: mmc read partition OK!
eMMC/TSD partition table have been checked OK!
mmc env offset: 0x10c00000
In: serial
Out: serial
Err: serial
reboot_mode=cold_boot
hardware_version =1
Saving Environment to aml-storage...
mmc env offset: 0x10c00000
Writing to MMC(1)... done
hpd_state=0
cvbs performance type = 6, table = 0
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
read emmc dtb
amlkey_init() enter!
[EFUSE_MSG]keynum is 4
[KM]Error:f[key_manage_query_size]L507:key[sn2] not programed yet
wipe_data=successful
wipe_cache=successful
Boot command:
Boot status:
Boot message
""
upgrade_step=2
[OSD]load fb addr from dts
[OSD]failed to get fb addr for logo
[OSD]use default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]load fb addr from dts
[OSD]failed to get fb addr for logo
[OSD]use default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=5760, height=2160
pull down bt_reset
pull up bt_reset
set hci reset
04 0e 04 01 03 0c 00
set scan parameters
04 0e 04 01 0b 20 00
set scan enable
04 0e 04 01 0c 20 00
pull down bt_enable
IR init done!
[imgread]szTimeStamp[2017012511355519]
[imgread]secureKernelImgSz=0x778000
aml log : R1024 check pass!
aml log : R1024 check pass!
aml log : R1024 check pass!
ee_gate_off ...
## Booting Android Image at 0x01080000 ...
reloc_addr =73f7a130
copy done
load dtb from 0x1000000 ......
Uncompressing Kernel Image ... OK
kernel loaded at 0x01080000, end = 0x01fa8620
Loading Ramdisk to 73e02000, end 73ee3000 ... OK
Loading Device Tree to 000000001fff4000, end 000000001fffff5e ... OK
Starting kernel ...
uboot time: 2832461 us
...
<See Attached>
UART Pins:
<See Attached>
You can hook the TX and RX lines into the 3.5mm headphone jack for easy UART use.
See attached
It turns out JTAG is enabled according to the Android dmesg log, this could mean a neat little BootROM dump...
Can someone makes a flash able rom for Almogic burning tool for mi tv box 3 mdz 16-ab?
Can you boot from usb device (libreelec)?
My mi tv box 3 is totally bricked no boot to recovery, only pc recognize like WorldCub device.
gyb001 said:
Can you boot from usb device (libreelec)?
Click to expand...
Click to collapse
I haven't looked at that yet, I don't really have any expirence playing with AMLogic SoCs, you can boot via USB? This would actually work if you can as I have boot.img and system...
(dylanger) said:
I haven't looked at that yet, I don't really have any expirence playing with AMLogic SoCs, you can boot via USB? This would actually work if you can as I have boot.img and system...
Click to expand...
Click to collapse
Thanks.
unfortunatelly i haven't img.
But i find intresting things
once#usb start
(Re)start USB...
USB0: USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
This box have usb3?
Do you know how can i make full backup from emmc?
I think we can run somehow twrp with this env:
recovery_from_udisk=if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;bootm ${loadaddr};fi;
I won
amlogic login: root
Password:
Last login: Sat Nov 4 12:30:06 UTC 2017 on ttyS0
/etc/update-motd.d/30-sysinfo: line 37: read: read error: 0: Invalid argument
/etc/update-motd.d/30-sysinfo: line 38: [: -le: unary operator expected
____ ___
/ ___|/ _ \__ ____ ____ __
\___ \ (_) \ \/ /\ \/ /\ \/ /
___) \__, |> < > < > <
|____/ /_//_/\_\/_/\_\/_/\_\
Welcome to ARMBIAN 5.34 user-built Debian GNU/Linux 9 (stretch) 3.14.29
System load: 0.44 0.12 0.04 Up time: 0 min
Memory usage: 4 % of 1790MB IP:
Usage of /: 18% of 7.1G storage/: 56% of 128M
[email protected]:~# ls
fstab install.sh
[email protected]:~# uname -a
Linux amlogic 3.14.29 #108 SMP PREEMPT Sat Nov 4 14:50:04 MSK 2017 aarch64 GNU/Linux
[email protected]:~# cat /proc/cpuinfo
Processor : AArch64 Processor rev 4 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: AArch64
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : Amlogic
Serial : 210a82005fb86cbf061167e2b0552e2f
Revision : 020a
gyb001 said:
I won
amlogic login: root
Password:
Last login: Sat Nov 4 12:30:06 UTC 2017 on ttyS0
/etc/update-motd.d/30-sysinfo: line 37: read: read error: 0: Invalid argument
/etc/update-motd.d/30-sysinfo: line 38: [: -le: unary operator expected
____ ___
/ ___|/ _ \__ ____ ____ __
\___ \ (_) \ \/ /\ \/ /\ \/ /
___) \__, |> < > < > <
|____/ /_//_/\_\/_/\_\/_/\_\
Welcome to ARMBIAN 5.34 user-built Debian GNU/Linux 9 (stretch) 3.14.29
System load: 0.44 0.12 0.04 Up time: 0 min
Memory usage: 4 % of 1790MB IP:
Usage of /: 18% of 7.1G storage/: 56% of 128M
[email protected]:~# ls
fstab install.sh
[email protected]:~# uname -a
Linux amlogic 3.14.29 #108 SMP PREEMPT Sat Nov 4 14:50:04 MSK 2017 aarch64 GNU/Linux
[email protected]:~# cat /proc/cpuinfo
Processor : AArch64 Processor rev 4 (aarch64)
processor : 0
processor : 1
processor : 2
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: AArch64
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : Amlogic
Serial : 210a82005fb86cbf061167e2b0552e2f
Revision : 020a
Click to expand...
Click to collapse
Woot! Nice work! So you've managed to boot into a Debian build? Damn nice work! Do you know if its possible to do that without having access to Android in the first place?
Like from UBOOT?
Yes i used to uart.
Write this command to uboot:
setenv bootcmd "run start_autoscript; run storeboot;"
setenv start_autoscript "if usb start ; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi;"
setenv start_mmc_autoscript "if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi;"
setenv start_usb_autoscript "if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 1 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 2 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 3 1020000 s905_autoscript; then autoscr 1020000; fi;"
setenv upgrade_step "0"
saveenv
Click to expand...
Click to collapse
I'm not sure it necessary, but i set the selinux disabled.
Download and write the image to usb drive
https://yadi.sk/d/srrtn6kpnsKz2/Linux/ARMBIAN
gyb001 said:
Yes i used to uart.
Write this command to uboot:
I'm not sure it necessary, but i set the selinux disabled.
Download and write the image to usb drive
https://yadi.sk/d/srrtn6kpnsKz2/Linux/ARMBIAN
Click to expand...
Click to collapse
Can we use this image with Amlogic usb burning tool ?
venioni said:
Can we use this image with Amlogic usb burning tool ?
Click to expand...
Click to collapse
No, the image will not pass the burning tool vertify.
I think you can use the amlogic burning tool only with uart. In uboot write "update" command.
gyb001 said:
No, the image will not pass the burning tool vertify.
I think you can use the amlogic burning tool only with uart. In uboot write "update" command.
Click to expand...
Click to collapse
Can you help me to unbrick my mind that box 3 international?
is totally bricked,no boot to recovery mode.
venioni said:
Can you help me to unbrick my mind that box 3 international?
is totally bricked,no boot to recovery mode.
Click to expand...
Click to collapse
Unfortunately i don't know how its possibile, but That sure, you have to use u boot.
You should buy uart usb device. I have cp2102
gyb001 said:
Unfortunately i don't know how its possibile, but That sure, you have to use u boot.
You should buy uart usb device. I have cp2102
Click to expand...
Click to collapse
If i buy this uart usb device cp 2102 can you make a tutorial how can i use this to unbrick my mi tv box3 and what firmwares i need to do all this?
venioni said:
If i buy this uart usb device cp 2102 can you make a tutorial how can i use this to unbrick my mi tv box3 and what firmwares i need to do all this?
Click to expand...
Click to collapse
Now, i can boot only Armbian.
Stock rom img file
https://mega.nz/#F!BDRG3J4B!VZqB0qJ9fseMhy4Y8anIaA
gyb001 said:
Stock rom img file
https://mega.nz/#F!BDRG3J4B!VZqB0qJ9fseMhy4Y8anIaA
Click to expand...
Click to collapse
Can we flash this stock rom image with Almogic burning tool for unbrick mi tv box 3 ?
venioni said:
Can we flash this stock rom image with Almogic burning tool for unbrick mi tv box 3 ?
Click to expand...
Click to collapse
No.
You have to use uboot

What does this mean to Redmi Note 2?

Occasionally, I found this thread,
[RESEND PATCH v6 7/8] clk: mediatek: clk-apmixed: Add helper function to unregister ref2usb_tx - AngeloGioacchino Del Regno
Subject: [RESEND PATCH v6 0/8] MediaTek Helio X10 MT6795 - Clock drivers
Date: Wed, 21 Sep 2022 11:14:47 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In an effort to give some love to the apparently forgotten MT6795 SoC,
I am upstreaming more components that are necessary to support platforms
powered by this one apart from a simple boot to serial console.
This (very big) series introduces system clock, multimedia clock drivers
(including resets) for this SoC.
Tested on a MT6795 Sony Xperia M5 (codename "Holly") smartphone.
AngeloGioacchino Del Regno (8):
dt-bindings: mediatek: Document MT6795 system controllers bindings
dt-bindings: clock: Add MediaTek Helio X10 MT6795 clock bindings
dt-bindings: reset: Add bindings for MT6795 Helio X10 reset
controllers
dt-bindings: clock: mediatek: Add clock driver bindings for MT6795
clk: mediatek: clk-apmixed: Remove unneeded __init annotation
clk: mediatek: Export required symbols to compile clk drivers as
module
clk: mediatek: clk-apmixed: Add helper function to unregister
ref2usb_tx
clk: mediatek: Add MediaTek Helio X10 MT6795 clock drivers
.../arm/mediatek/mediatek,infracfg.yaml | 2 +
.../bindings/arm/mediatek/mediatek,mmsys.yaml | 1 +
.../arm/mediatek/mediatek,pericfg.yaml | 1 +
.../bindings/clock/mediatek,apmixedsys.yaml | 1 +
.../bindings/clock/mediatek,mt6795-clock.yaml | 66 ++
.../clock/mediatek,mt6795-sys-clock.yaml | 54 ++
.../bindings/clock/mediatek,topckgen.yaml | 1 +
drivers/clk/mediatek/Kconfig | 37 ++
drivers/clk/mediatek/Makefile | 6 +
drivers/clk/mediatek/clk-apmixed.c | 12 +-
drivers/clk/mediatek/clk-cpumux.c | 2 +
drivers/clk/mediatek/clk-mt6795-apmixedsys.c | 157 +++++
drivers/clk/mediatek/clk-mt6795-infracfg.c | 151 +++++
drivers/clk/mediatek/clk-mt6795-mfg.c | 50 ++
drivers/clk/mediatek/clk-mt6795-mm.c | 132 ++++
drivers/clk/mediatek/clk-mt6795-pericfg.c | 160 +++++
drivers/clk/mediatek/clk-mt6795-topckgen.c | 610 ++++++++++++++++++
drivers/clk/mediatek/clk-mt6795-vdecsys.c | 55 ++
drivers/clk/mediatek/clk-mt6795-vencsys.c | 50 ++
drivers/clk/mediatek/clk-mtk.c | 2 +
drivers/clk/mediatek/clk-mtk.h | 1 +
drivers/clk/mediatek/reset.c | 1 +
.../dt-bindings/clock/mediatek,mt6795-clk.h | 275 ++++++++
.../reset/mediatek,mt6795-resets.h | 53 ++
24 files changed, 1879 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6795-clock.yaml
create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6795-sys-clock.yaml
create mode 100644 drivers/clk/mediatek/clk-mt6795-apmixedsys.c
create mode 100644 drivers/clk/mediatek/clk-mt6795-infracfg.c
create mode 100644 drivers/clk/mediatek/clk-mt6795-mfg.c
create mode 100644 drivers/clk/mediatek/clk-mt6795-mm.c
create mode 100644 drivers/clk/mediatek/clk-mt6795-pericfg.c
create mode 100644 drivers/clk/mediatek/clk-mt6795-topckgen.c
create mode 100644 drivers/clk/mediatek/clk-mt6795-vdecsys.c
create mode 100644 drivers/clk/mediatek/clk-mt6795-vencsys.c
create mode 100644 include/dt-bindings/clock/mediatek,mt6795-clk.h
create mode 100644 include/dt-bindings/reset/mediatek,mt6795-resets.h
--
Maybe not much. I'm only in this thread cause I decided to replace the broken screen of my old RN2, only to find out it's still stuck in Android 5, which is definitely insufficient for this day and age. Where did you find this information?

Categories

Resources