Search results

The following procedure actually worked for me for the EU Mi9T Pro version (e.g. available in germany) I used this firmeware package: https://downloads.akhilnarang.me/MIUI/raphael/RAPHAELGlobal-V11.0.1.0.QFKMIXM-10.0-vendor-firmware.zip

Lastest April build also has much better battery performance! Thanks for this!

Is it possible to dirty flash the new inofficial LOS 14.1 builds for H815 over the last official LOS 14.1?

Okay, patches are now included: https://review.lineageos.org/#/q/status:open+project:LineageOS/android_external_wpa_supplicant_8+branch:cm-14.1+topic:krack-n

Hi everyone, is in the next nightly build the wpa_supplicant patch for the latest WPA2 attack (KRACK) included? See more here: https://forum.xda-developers.com/general/networking/wpasupplicant-wpa2-patch-androiod-krack-t3689816

Hi everyone, You may have seen recent publication about WPA2 vulnerbilities (called KRACK): https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping/ A wpa_supplicant patch is already released...

Is someone able to make a boot image with a fixed fstab for the sdcard? The sdcard fstab record is wrong. It is /devices/mtk-msdc.0/11240000.MSDC1* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata /devices/platform/mt_usb* auto vfat defaults...

I don't know if anything is not working (did not compile the LineageOS myself). I just wanted to say that camera and other MediaTek hardware will work, but because the code is taken from Redmi Pro it may need some minor tweaks to get it running without any problems. Just copy & paste the...

@all developers In the discord channel of this project the user end222 hinted that in the current Nikel lineagos 14.1 device tree branch there are some MTK symbols corrupted and missing in the "libmtk_symbols". These missing symbols are added in the Redmi Pro Omega device tree you can find here...

Here are the missing Blobs for the Camera by SamarV-121: Missing-Blobs+Camera-Blobs-nikel.zip https://www.androidfilehost.com/?fid=745425885120756749 Just install the zip via TWRP.

Sounds interesting and relatively easy to resolve then. But I don't see any recent activity in the github source code branches :(

Is there an ETA for an update with working camera?

The problem is not the corrupted recovery. I'm even not able to go into fastboot/download mode. The phone will randomly reboot. It really looks like a hardware failure. Believe me, I tried a lot of things, but I'm not able to get the phone in a stable state where it's able to receive commands...

Thank you! Do you know if they will inform me before fixing the issue without warranty (so I have to pay)?

No, it is the same kernel which is coming with the lineage ROM. I made no further modifications, no Xposed or something else. Simply the plain lineageOS ROM. It worked like a charm for weeks or months, and now stopped completely unexpected, from one moment to the other. It didn't fall to the...

Maybe this is off topic and has nothing to do with this ROM: I just wanted to take a picture with the default lineage os camara app. After that the phone stuck and rebooted after few a seconds. Now I only get a black screen after the lg bootloader logo (the point where normally the lingeage os...

Hello everybody, how do you get the su binary installed? I used the twrp version suggested in the second post. This version asks me to install su before rebooting. When I do this the rom will not boot anymore (it's stuck in the "android" animation). When I say "do not install" the rom works...

ADB is, as the name suggests, the android debug bridge. In the download mode, the phone is still executing bootloader programcode. Android is not booted then, so ADB can not work. If anything, try fastboot. But I had the same problem, and the only way to get the TWRP recovery back was to flash...

I had the same problem with recovery bootlooping. Fix: Just flash the CM Recovery. For H815 use cm-14.1-20161125-NIGHTLY-h815-recovery.img from here: https://download.cyanogenmod.org/get/jenkins/187674/cm-14.1-20161125-NIGHTLY-h815-recovery.img For H811 use...

Okay, to clear this: I just updated rox's latest CM to this official CM without wipe and without any problems. It seems to be safe! The official nightly update was also shown in the CM updates in rox's version.

Is it possible to update from rox's CM 12.1 to this official 12.1 without wiping the phone?

You don't need it. It's just if you don't have a custom recovery. Not important if you have TWRP.

The build is running now, wait 30 min and you will have it on the official cyanogenmod site. They are building nearly for 300 devices on just 4 machines, and the s3 neo hasn't the highest prority ;) This takes some time. PS: It finished: https://download.cyanogenmod.org/get/s3ve3g-latest.zip

Yes, the build is scheduled in the jenkins build system. But it can take a few hours until it is in turn. I guess early or late afternoon.

The download page is up already: https://download.cyanogenmod.org/?device=s3ve3g

That is great! Does it mean we will also get nightly builds? What do you mean with "W=Sunday"? Thank you for your work!

Sorry if this is a well known issue: My Wifi is always turning off when the display is a few minutes off (standby). I have enabled the "keep wifi always on", but this doesn't change anything. Latelty I made an cm update and while downloading the display turned off, the wifi turned off and the...

It's useless, because the unlock.bin doesn't contain machine code (at least not as plain text).

Is this confirmed by other users?

Why you want an AOSP rom? As I can see, the discussion started because of the CM camera app (it's open source, but patching this code makes no sense). So, what's the problem to let CM be CM, and just add an own camera app supporting the G4 special features? I guess this is what codeworkx will...

So you'd say the 20151209 build is as stable as the 20151201? No new bugs or issues?:fingers-crossed: What about the SD card issue? When formatting as external storage, it creates a partition of 16 MB (on a 64GB SD card). When resizing on a PC with parted, it's only recognized as invalid SD...

This is caused by the time / date issue. The system clock is set to 2nd of July. The google SSL certificate was signed for november. So the google play services will invalidate this SSL certificate, because from it's point of view (2nd of July) the SSL certificate is still invalid.

codeworkx: Maybe this clock issue is connected to what I described a few pages back yesterday: http://forum.xda-developers.com/showpost.php?p=64115761&postcount=897 You are able to choose date/time with the date/time chooser, but it's not applied. It seems like date and time is hardcoded or the...

The built from yesterday is working fine!

Okay, just tried the nighlty from yesterday (01.12.2015). In this version the date and time settings seems to work. It also synchronized the time from the GSM network. Maybe this is one point to have look?

Just flashed the 20B KDZ and booted it up, gone through the setup etc. Then full wiped and flashed this ROM (02.12.2015 nightly), rebooted, made the setup, rebooted, flashed opengapps nano, wiped again and rebooted. On the first view everthing seemed fine, but I can't get a connection to setup...

Hi everyone, I read a few pages back, but didn't read anything about the bluetooth problems. Is it already fixed? It is not listed at the known issues page anymore? Thank you!

Has someone tried this: http://forum.xda-developers.com/optimus-l9/general/guide-install-custom-roms-locked-t3249828 Maybe the G4 also uses the same signature keys?

Nice, if so. Can you provide a source please?

Please keep calm guys! We don't have an unofficial bootloader unlock yet. And no one knows if the announcement on LGViet was a hoax or real or whether they just wait for the Android 6.0 update to be sure LG don't fix the security bug which made the unofficial unlock (maybe) possible. Please...

Maybe we soon see unofficial bootloader unlock on all devices: http://forum.xda-developers.com/g4/general/unlock-unofficial-bootloader-unlock-t3222737

On twitter autoprime tweeted a few days ago And later on this discussion: Source: https://twitter.com/utoprime/status/649654317939601408 Maybe we will see unofficial unlock on all carrier devices soon ;) But what means "v0"? Where can I see whether my phone is "v0"? Edit: Link to LGVIET...

The entropy of the payload is 7,14 of possible 8. This means there is no logic in this data. It has to be encrypted or is a checksum of something. Do we have few different unlock.bin files? If we have luck, and they used RSA, it looks like they used only 1024 bit modulus (resulting in ~256 byte...

If, and only if, then I would use something like uboot ;) But the problem is that the bootloader is doing much hardware dependend initializations, which you have to reverse engineer from the original bootloader. Another problem is that no one seems to have a developer device which enables you...

What about the stock kernel, is it supporting "kexec" systemcall? http://linux.die.net/man/8/kexec So the stock kernel could be used to feed the bootloader with a signed one and then boot the custom kernel. Misusing the stock kernel as second stage bootloader :D

Yes I think so too. But if they have a running system, they can do proper debugging to find out what's wrong. :good::)

thank you mythos234! Are you working on a CM12.1 on base of this kernel?

Where?

In another thread at (I believe) AT&T G4 device forum I read something about "zeroing out the laf partition" to disable the secure boot feature. Did anyone test this?

mythos234: Nice!! I guess this is becoming a long weekend :)