[ROM] 13/12 | Fulmics ROM 8.0 ◦ v30N ◦ Tweaks | HUB | OTA ◦ MM 6.0 ◦ All variants

[PonchosoftX]

Is there any other mirror than Mega, it does not allow me to download due to limits.

 

[Keelvin321]

Is there any other mirror than Mega, it does not allow me to download due to limits.

To download the file I had to use a VPN application, because whenever it came to 1.5 gb the download stopped and I had to wait about 4 hours to continue . If you use Chrome recommend this one: https://chrome.google.com/webstore/detail/browsec-vpn-free-and-unli/omghfjlpggmjjaagoclmmobgdodcjboh. I always use this extension when I'm going to download large files in Mega, it helps a lot

 

[AlwaysLucky]

Are there any other mirrors available besides Mega? It downloads fine, but limits me to ~15kbps which will take days.

 

[ezantera]

I am on latest version of Fulmics d855 g3. Network enabled vowofi and volte, but it seems it is not working. In menu settings there is no sign of it and when entering this and trying to go to telephone info it shows error *#546368#*855#

Everything should work but it dont. Anybody have everything working?

edit: It seems that my operator blocked me from using volte. My g3 is not using official theirs ROM and they somehow know.

 

[undertherain]

I respect you.
Do you still have a LG G3?

 

[farvehar09]

thanks for this rom

 

[Wade83]

Big Thanks

@xpirt, thank you. this is just what we all needed. excellent custom rom based on stock, i mean it's the camera right?

 

[Mikha777]

sorry I may have missed your post as it was very simple to do. try flashing this and let me know: invalid_batt_removed.zip

@xpirt


I have the same problem on my LG G3 D851 with Stock ROM it detect my battery as invalid but with custom ROM the battery work fine

Fulmics is draining my battery to fast strangely so I'm back to V30G but I'd like to use my third party battery,

I tried to download "invalid_batt_removed.zip" to flash it but the file is no longer available on Mega could you upload it again somewhere ?

Regards

 

[AtrixHDMan]

@xpirt


I have the same problem on my LG G3 D851 with Stock ROM it detect my battery as invalid but with custom ROM the battery work fine

Fulmics is draining my battery to fast strangely so I'm back to V30G but I'd like to use my third party battery,

I tried to download "invalid_batt_removed.zip" to flash it but the file is no longer available on Mega could you upload it again somewhere ?

Regards

Same here battery all of sudden draining really fast

Sent from my LG-H830 using XDA-Developers Legacy app

 

[jozef_star]

update

LteConfigs
Update sys

Sistem uygulamaları güncellemesi nasıl yapılır.

 

[jozef_star]

Help me

Lteconfigs update

Lte sistem güncellemesi
Lte problem system app update

 

[mauriciognr]

Im using Fulmics 8.0 and having this issues:

- Cant change DPI, the app FCs
- Magisk wont install any modules and FCs all the time, updating to v19 didnt solve the problem.

Edit (Solved):

Got it fixed uninstalling magisk using uninstaller zip and then installing latest magisk v19.3.

 

[cidxtc]

Im using Fulmics 8.0 and having this issues:

- Cant change DPI, the app FCs
- Magisk wont install any modules and FCs all the time, updating to v19 didnt solve the problem.

---------- Post added at 04:46 PM ---------- Previous post was at 04:46 PM ----------

Im using Fulmics 8.0 and having this issues:

- Cant change DPI, the app FCs
- Magisk wont install any modules and FCs all the time, updating to v19 didnt solve the problem.

The apps that are force closing are LG apps? I know some stock app require a set range to operate but don't remember if it was LG, Samsung, or both. Lol. I am pretty sure on the G3 I kept dpi close to stock setting.

 

[marcdw]

On the G3 stockish ROMs I can safely change dpi to 580. I think anything lower would cause problems. But it sounds like the app to change DPI is what's crashing. @mauriciognr, what app are you using to try and change DPI? You could try another like _texdroider(sp?) or just edit the /system/build.prop file. Search for lcd inside the file.

I don't do Magisk so can't comment on that one.


LG G3 D851, PAC-ROM 6, MultiROM, XDA Legacy

 

[mauriciognr]

On the G3 stockish ROMs I can safely change dpi to 580. I think anything lower would cause problems. But it sounds like the app to change DPI is what's crashing. @mauriciognr, what app are you using to try and change DPI? You could try another like _texdroider(sp?) or just edit the /system/build.prop file. Search for lcd inside the file.

I don't do Magisk so can't comment on that one.


LG G3 D851, PAC-ROM 6, MultiROM, XDA Legacy

I got around both things

- Fulmics Tweaks was FCs and hanging (think it was magisk related since it needs root), anyway, i used nomone and DPI changer both worked fine, im on 560.
- Uninstall magisk using the uninstaller zip. Then installing latest (v19.3). All good

But now i have a problem with instagram, some icons look like super big (DM icon ie) as well as emojis and gifs when i try to put them in the stories (they look cut off for being super big). I cleared data, cache, restarted the phone and reinstalled the app and also tried the calculated dpi (538) and then 540, and then your 580... The problem with instagram and other apps like AC Display continues. Before, when i was using RR 7.0.2 (Pie) instagram was like super low dpi i could see a lot of content with no icons or visualization problems, same with AcDisplay. Do you have any clues?

 

[marcdw]

Not sure about the Instagram thing. Maybe try this: instead of installing the app from the Play Store, go to apkmirror and find whichever version of Insta you prefer. You'll notice different downloads/variants for different DPI groups. Experiment by installing one or more and see if there's any difference in how they look. Some versions don't have all the variants.
Example, Instagram v102 doesn't have an arm variant supporting anything over DPI 320 but the arm64 variant supports up to 640. I assume that can be installed. Not sure.



Compare to v100 that has an arm variant supporting 360-640 as well as an arm64 nodpi..



Nodpi would be preferable. Still, whatever the Play Store installed I would think it was one supporting 360-640 or nodpi. Not sure why it would look odd.



Essential PH-1, /e/OS 0.7-n ROM, microG (NoGapps), XDA Legacy

 

[pjadec]

LG G3 is only armeabi-v7a 640dpi or 360-640dpi should work

 

[pol098]

I have soft-bricked an LG G3, and would be very grateful for any advice, please. (My background is in software, but my Unix is both out-of-date and very rusty, and I'm not into phones at all. So I'm happy with files, file systems, and binary editing if necessary, but otherwise at sea regarding, e.g., have I deleted the kernel and do I need to attend to that first).

LG G3 D855 16GB/2GB, rooted and Fulmics 6.9 was installed when I bought it, I installed TWRP (v3.1.1.0, which seems to be a mistake). I have an old (2017) nandroid backup, and a new one made AFTER the problem arose.

I was having the "screen stays dark after a phone call" problem, so went into the hidden menu and carefully and correctly went into the bit related to calibrating the motion sensor. The phone shut down and would then no longer boot, with "[670] boot certification verify / secure booting error! / cause: boot certification verify" with the indicator light flashing blue and red, an issue that others have described. I can start up the twerp recovery.

My plan was to restore the working 2017 backup with twerp, then, if possible, use Titanium Backup to restore applications and their data from the post-brick backup. I don't have any important data, but I'd like to get them back, including applications which are no longer available; but at least I'd like my phone back, even if "factory reset".

After restoring the 2017 backup (apparently successfully) the phone remained bricked in the same way. I wiped everything (including ultimately internal, but not external, storage - bye bye); still bricked. I then decided to update to Fulmics 8.0 (latest), so copied the ZIP onto the root of the SD card, wiped again, and ran twerp INSTALL. Result "failed to map file /external_sd/FulmicsROM-8.0.zip". Searched; known problem, use older version of TWRP, easy. Except that I don't know if it's possible to install the older TRWRP on a phone with TWRP 3.1.1.0 installed, but no operating system. I haven't yet done anything with adb on a Windows computer; can adb do that? I don't remember if I had enabled USB debugging; if not I'm presumably stuffed (adb doesn't find any devices). (Or does adb require a working Android?)

So I'm stuck with a dead phone, which I'd like to revive and, if possible, restore data to using Titanium on the post-brick backup. One issue I'm unsure about: having deleted internal storage, should I be able to install Fulmics without first installing a kernel?

Looking through threads, I find people with the new-TWRP problem on other phones have worked round it by extracting boot.img from the ROM ZIP file, installing it, then installing the ROM as usual. The question that arise with Fulmics: there are two eligible boot files for the D855, d855.img and d855_lz4.img; obviously one using better LZ4 compression, but which do I need? I suppose it depends on the kernel?

So, summarising questions: with a working TWRP but no Android on a D855 LG G3
-Help! What can I do?
- Can I install an older TWRP on a phone with 3.1.1.0 installed but no Android?
- Do I need to install anything before the ROM?
- If it's not possible to downgrade TWRP, should I try d855.img or d855_lz4.img (or neither!) before flashing the ROM?

Apologies for the long post, but I didn't want to leave unanswered questions. Thanks for looking at this and best wishes.

 

[cidxtc]

I have soft-bricked an LG G3, and would be very grateful for any advice, please. (My background is in software, but my Unix is both out-of-date and very rusty, and I'm not into phones at all. So I'm happy with files, file systems, and binary editing if necessary, but otherwise at sea regarding, e.g., have I deleted the kernel and do I need to attend to that first).

LG G3 D855 16GB/2GB, rooted and Fulmics 6.9 was installed when I bought it, I installed TWRP (v3.1.1.0, which seems to be a mistake). I have an old (2017) nandroid backup, and a new one made AFTER the problem arose.

I was having the "screen stays dark after a phone call" problem, so went into the hidden menu and carefully and correctly went into the bit related to calibrating the motion sensor. The phone shut down and would then no longer boot, with "[670] boot certification verify / secure booting error! / cause: boot certification verify" with the indicator light flashing blue and red, an issue that others have described. I can start up the twerp recovery.

My plan was to restore the working 2017 backup with twerp, then, if possible, use Titanium Backup to restore applications and their data from the post-brick backup. I don't have any important data, but I'd like to get them back, including applications which are no longer available; but at least I'd like my phone back, even if "factory reset".

After restoring the 2017 backup (apparently successfully) the phone remained bricked in the same way. I wiped everything (including ultimately internal, but not external, storage - bye bye); still bricked. I then decided to update to Fulmics 8.0 (latest), so copied the ZIP onto the root of the SD card, wiped again, and ran twerp INSTALL. Result "failed to map file /external_sd/FulmicsROM-8.0.zip". Searched; known problem, use older version of TWRP, easy. Except that I don't know if it's possible to install the older TRWRP on a phone with TWRP 3.1.1.0 installed, but no operating system. I haven't yet done anything with adb on a Windows computer; can adb do that? I don't remember if I had enabled USB debugging; if not I'm presumably stuffed (adb doesn't find any devices). (Or does adb require a working Android?)

So I'm stuck with a dead phone, which I'd like to revive and, if possible, restore data to using Titanium on the post-brick backup. One issue I'm unsure about: having deleted internal storage, should I be able to install Fulmics without first installing a kernel?

Looking through threads, I find people with the new-TWRP problem on other phones have worked round it by extracting boot.img from the ROM ZIP file, installing it, then installing the ROM as usual. The question that arise with Fulmics: there are two eligible boot files for the D855, d855.img and d855_lz4.img; obviously one using better LZ4 compression, but which do I need? I suppose it depends on the kernel?

So, summarising questions: with a working TWRP but no Android on a D855 LG G3
-Help! What can I do?
- Can I install an older TWRP on a phone with 3.1.1.0 installed but no Android?
- Do I need to install anything before the ROM?
- If it's not possible to downgrade TWRP, should I try d855.img or d855_lz4.img (or neither!) before flashing the ROM?

Apologies for the long post, but I didn't want to leave unanswered questions. Thanks for looking at this and best wishes.

You need to flash a modification for your kernel. All lg g3 versions required this except the d851 (T-Mobile). Your devices bootloader is not unlocked and requires you to trick it into thinking you are using stock kernels and roms. I have the d851 so don't remember or have the file you need to flash. You should not have much trouble looking through the g3 forums to find it.

 

[marcdw]

@pol098, I do believe he is referring to MR_Bump. Usually flashed after a ROM or custom kernel. You'll probably find a lot of posts regarding it in this thread and maybe existing links.
I have the D851 where bumping wasn't needed so I may not have it in my archives.


Moto G5S Plus XT1806, Validus 8.1.0, microG-NanoDroid, MultiROM, XDA Legacy