Search results

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

I Just changed One Single Letter Sent from my OnePlus 3 using XDA Labs

that won't help me...

got problems with the actual TWRP 0.3 and backing up data...always runs into ann create tar fork() process ended with error 255 with the first version and second version of TWRP with multirom support, got no problems

can confirm, working with your fastboot....but changing aboot runs into blackscreen md5 still active i think :laugh::(

ok, i'd tried already. and i can see the commands via oem help, but I can't use most of them. which OS you're using to fastboot and where did you get the fastboot package from. thanks

Fastboot flashing !? we're talking about an OP3? fastboot flashing won't run for me, neither on linux or in windows fastboot oem

so, i tried it the whole way. locked bootloader, 9008 - Tool to Factory. typed in fastboot oem unlock_critical -> say OK fastboot oem device-info: device unlocked: true device critical unlocked: false !!! FAIL Btw: you can write fastboot oem unlock_stupid and the unlock_bootloader menu will...

if there's nobody to test it...i'll give it a try next weekend. so i'll reverse to stock os, then lock and afterwards unlock the bootloader with oem unlock_critical

maybe somebody is undaunted enough to challenge this....

fastboot oem unlock_critical responds already unlocked at my device... maybe you need to lock it first and then use the unlock_critical one. i'm currently on resurrection, what will happen if you lock via fastboot? won't try at the moment, one hardbricked phone yesterday is enough for me cause...

you mean: fastboot flashing unlock fastboot flashing lock fastboot flashing unlock_critical fastboot flashing lock_critical fastboot flashing get_unlock_ability

don't try it... i just changed the "Start" into "START" and replaced aboot and abootbak... blackscreen in result... need ideas

jamesst20 aboot and abootbak got same content. extracted them and made an binary compare.. so maybe it would work if you replace aboot with the patched one and at the same time replace abootbak with the patched one... if this won't run you should try replacing the aboot with an original...

I'll wait for you to explore it out cause i'm also interested in modifying it...I wish i know where to find it

Does your rom comes within the blue spark? my solution was to get into TWRP and flash the blue spark with the install option... not the advanced one inside the multirom tab I meant. hope this helps

I solved it for my self. Used as first ressurection 5.7.1 ROM with ElementalX Kernel which was incompatible to Multirom i think. Flashing the blu_sp★rk Kernel solved my problem and as of now I can use the Multirom menu with touch at boot.

Multirom works fine for me, the only problem is you cant use touch in multirom menu....so i'd always use the multirom settings in TWRP to switch the ROM'S i'd like to boot from.... any other got problems with the touch at boot?

Can confirm problems since june builds too. Bluetooth connections to car stucks sometimes it takes about 5 minutes to connect and then random connections losts.

i got 2 or 3 times an error closing the actual foreground app since the buttons won't work... after a restart everything went fine again. but this error hasn't happen with the actual builds. other errors I didn't recognize as far. since a few days the gestures like "v", "o" and double knock...

Alert Slider is working for me now The Image Quality is faboulus and i'm using the rom sice 3 weeks without any problems...I install the updates from mokee source every 2-3 days. :good:

Short question, i saw Synapse running on screenshots running with AK.005.OPO2.CAF.... where to get this !?

For me the rom runs very smooth, battery life is good but the mute button won't work for me , anyone else got this problem

Hi pongster, installed your update over my v1.2 from you. now my camera won't run. when i start the camera i got an black screen and after a while the message that the camera app is not responding anymore. so i thought installing your camcorder fix would help me out. but same result... any...

MDJ's Cyanogen runs perfect with it. so personally i don't know if there's a needing for EAP or adhoc. all other stuff like market, internet, exchange active sync runs perfectly just the inbound connections via wifi won't run.

logcat will be postet later that day, with other testet nand droids the connection via wifi was no problem. you get quicksshd or smartftp from the market, configure it. the programm will tell you it's ip (inside the range of your local ip network). so normally you can ping or acces via putty...

very nice rom, got the following problem with it, maybe somebody tried this too if you use an ssh deamon or an ftp server on your phone and try to access the phone via wlan you got no connection. on the other hand if you use an proxy via gsm you will get an connection but wlan - no chance. any...

as far as I tested the kernel / rom everything looks fine BUT if I turn off the device and plug it into the USB port, it shows the battery symbol and then freezes. after pluggin off and do the 5 second reset, everything went up fine.... any ideas?

Bluescreen mine got the blues too :-(

That really rocks. thanx for the very fast ringtone and manila fix. updated this morning and no problems until now !!! great work:):):)

works not for me, it only vibrates but no tone at all:mad: so I'l downgrade until everything is fixed.

got the same problem. any idea or beta manila 2.5 ? :confused:

got the same problem. any ide or beta manila 2.5 ? :confused: