Recent content by lance2010

the bluetooth connection itself runs without problems. but if you start your car the phone won't connect with the car media system without unlocking the screen thanks for your reply

BT and car Hi Freak, if i use your kernel with android 10 i can't connect to my car bluetooth without unlocking the screen via fingerprint. if I use the original kernel from the android 10 image i didn't have this problem, the phone connects without unlocking the display with my car. do you...

Battery 70% got even the same error, i'm on 1910.64 anybody got an solution? regards

With the new V4.0 version you can't phone inside your car. The bluetooth connection will cut every 10 seconds and after that it reconnects automatically. with the 3.9 i got similar problems but not in that speed.

Tested Works like a charm for me. After testing Freedom on OP5 i'd tested Candy and will stay on it. Easy installation, battery drain seems to be normal as for now everything works. good job guys :good:

Here you can have a look at aboot source https://source.codeaurora.org/quic/la/kernel/lk/tree/app/aboot/aboot.c?h=LA.BR.1.3.2_rb3.16#n3280 there's a keychain that has to be modified then the phone will boot with modified aboot... for me to complicated.

SECURE BOOT in this case refferes to qualcomm's secureboot process in which pbls sig checks sbl1, which then checks sbl2 which checks sbl3 which checks aboot, So pbl->sbl1->slb2->sbl3->aboot is all sig checked. This can't be disabled on the optimus g. It's enabled through a qfuse. Now with ics...

nope, won't fix the problem

Sweetheart, thats Not the challenge. But thanks for Input

that unlock_critical is not working is in my opinion true.. i changed in the flashtool the emmc_apps_boot (aboot) file, calculated an md5 checksum of the patched file and put this new checksum inside the md5.img file that's burned on the phone if you recover via the tool. i thought maybe this...

if you not know how to use the OP3 unbrick tool, let it be..in result you got an unbootable device if you change anything inside the bootloader.

i'm out of ideas. used the unbrick tool, changed the emmc_appsboot.img, just the word "Start" to "STart" generated inside the tool an md5, changed the original stored md5checksum in md5.img with the new one....burned the phone with the msmdownload tool and in result -> yes you know it already ...

where did you see it running? editing is not the problem, flashing it back is not the problem...but the phone won't start, even if you change a single bit ! there's an checksum active even if you set your phone to unlock_critical...

the "warning" message is inside the aboot....at the moment there's no way to modify this file....but....we will see.

definitly yapp