• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [MetroPCS] carbon rom repair project

LoopyD

LoopyD

Android Enthusiast
CARBON ROM REPAIR PROJECT

an interesting point was brought up in the thread so it has been re-directed to fixing the issues with carbon rom kk 4.4.4 by Dm. Bugs may be found in the source code that cause a memory hole on device system object fail. (black screen of death). See below...

Need ideas on fixing settings force closes. Vibration intensity screen and About screen. NFC and Bluetooth needs fixing. If any kernel crashes report here. Kernel may need repairs.

LOLLIPOP FOR LG OPTIMUS F6

has anyone proposed this idea? It requires the bootloader to be unlocked. If I get ahold of the image I can do it. I'm learning snapdragon assembly language.

This is a great phone. I could probably build from CM lollipop source with a proper device tree and a compatability layer for jelly bean device drivers and system objects. I have been messing with Java a lot. No more green kit kat cams. Lol . just so you know if I can dev a proper compatability layer this will solve the issue of missing drivers for new versions of Android

If you want to help or can provide knowledge inbox me please. I want to do this.

Also looking for devs for my group Quad Core . Need resumes for an application. What you can do and your experience and a personal message. Wanna be recognized for doing something awesome for the Android community? Inbox me.
 
Last edited:
we are still having trouble with a fully functional kitkat.until thats accomplished i dont think anyones trying to push further ahead
 
4.4.2 is having system object failure problems from what I see. Do to using hacked drivers. Which causes code to lock up the system in an endless ota update check loop . Removal of that code will fix the lockup. And a new driver must be found.
 
carbon is the most stable but dm is working out his own fixes.i think its best to ask the dev if you can help in any way
 
O.o. uhhh i have not heard of this for the f6 dude lol.there is no ota update the f6 officially stopped at 12b lol whitch is 4.1.2 there is no lockups.its been custom roms galore after that
 
I'll locate the code in comprise and submit it to the developer. With proper edits. When I get my rig...
 
Yeah the ota update code was removed but parts of the code are still looking for the ota update subroutine.
 
Search all source files for subroutine name. Remove lines. Then remove subroutine. Solves lock up on system object failure and massive mobile data waste.
 
idk perhaps you are right.course i havent paid attention to this because it looks like an official update from 12b they are not going to work on.the european model got it,whitch is what all these ports are basing off of.honestly if they would give us a normal ota update the custom roms would be alot better.im trying to get a new rig myself but the f6 im selling because i moved on to the htc one.good luck though,there are still alot of f6 users looking for breakthroughs in stuff
 
@LoopyD i had to make an account just to comment but.. id like to ask you to keep us in update on what happens? ive been running xperion rom for the longest time now and a lolllipop or even just a fully functional kitkat is desperately needed!
 
The issue I have with the these kitkat roms is the flash, my phone came with the camera that isnt supported, but the kitkat roms are stable if you read on how to flash them correctly.
 
Yes. He has not responded yet. If I can obtain the source code I can fix it myself... But he's the DEV and holder of the source code. The device driver failure I'm unsure how to fix though... But I can fix the endless loop lockup issue.
 
ok, i flashed the rom 4.4.2, i had no bootloop on that one, just the flash issue and the back camera that is blue but its because of the kernal they made to support this camera version
 
hroark gave up. If I can get his kernel source. Hmm... Blue cam bug seems as if bytes are shifted somehow wrongly in driver. Rgba. Possible fix if I can look at kernel code...
 
If the cam image is appearing blue take an HTML color code analogy.

#FFF

Red 1 byte
green 1 byte
Blue 1 byte

Blue is #00F

The new cam driver is probably accessing video ram wrong (bug in code?) and the red and green bytes are being dropped.

Could be anything. A mistyped assembler instruction that is only writing to some random fixed location. Do me a a favor. See if any of the pixels in a raw dump of the cam image are not blue. If this is the case there could be a typo. Only one pixel of the image is probably white or a random color.
 
I dont know how do it, : (
If you mean taking a picture, yes the whole image is blue, theres no pixel with a different color
 
You must log in or register to reply here.
Back
Top Bottom