A port of IAmTheDarkOne's 4.2 rom from the Nexus S. Can't really test what works and what doesn't as it keeps displaying an error that the process com.android.phone has stopped. If anyone knows how to fix it hopefully it can help us have a fully working 4.2 rom.
Link to rom
http://www.mediafire.com/?2d8d6yr4abzn5ov
ubnub82 said:
A port of IAmTheDarkOne's 4.2 rom from the Nexus S. Can't really test what works and what doesn't as it keeps displaying an error that the process com.android.phone has stopped. If anyone knows how to fix it hopefully it can help us have a fully working 4.2 rom.
Link to rom
http://www.mediafire.com/?2d8d6yr4abzn5ov
Click to expand...
Click to collapse
The FC ( process com.android.phone ) is kernel related. try to use the stock kernel that came with IAmTheDarkOne's 4.2 rom
khan_frd2002 said:
The FC ( process com.android.phone ) is kernel related. try to use the stock kernel that came with IAmTheDarkOne's 4.2 rom
Click to expand...
Click to collapse
Still happened.
Try using a stock cm10 kernel
Sent from my Nexus S 4G using Tapatalk 2
replace the phone and contact apk files with those from an aosp 4.1.2 rom
this trick help you but you cannot make calls and baseband should be unknown
the only thing is that deleted the phone.apk and contacts.apk and then install the rom. its boots up fine with no fc
build a new kernel aint that hard
Related
Alright, I know the camera isn't broken because the camera works on any rom that isn't cyanogen based. I made sure i wiped all data and cache before installing cyanogen and I got the correct gapps too, but every time i try to load any camera app, it errors and shuts down. the integrated camera app says "cannot connect to camera" and then closes right away after opening it. How is this fixable? what am I doing wrong?
Bump, Im having the same issue. Its perplexing to say the least.
What camera are you using? I was on Paranoid Android 2.54 and when I flashed the 4.2 camera, it did not play nice. Taking a picture will freeze the app and then from that point on it never connected to camera. Are you pulling the right Gapps?
ELStiko said:
What camera are you using? I was on Paranoid Android 2.54 and when I flashed the 4.2 camera, it did not play nice. Taking a picture will freeze the app and then from that point on it never connected to camera. Are you pulling the right Gapps?
Click to expand...
Click to collapse
I flashed black bean v7 along with the gapps they posted on their website for bb7. I've been flashing the 4.1 gapps on the 4.1 Roms and 4.2 gapps on the 4.2 Roms. I did a bit more research and a few people have mentioned a bin file that they grab from the stock image and put into /data on the new rom. I'm going to try that in a bit.
Try this,
http://forum.xda-developers.com/showthread.php?t=2102981
T-Mobile SGS III
I tried to port several AOSP CM based roms from the Galaxy Nexus and the Nexus 4. with these guides. http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=2069850
When I use HERO guide the phone never boots more than the boot logo and when I use the other guide I get error status 7.
Im using CM nightly as a base.
Also I tried to port TW roms from the Verizon forums using HERO guide and this guide http://forum.xda-developers.com/showthread.php?t=2104604 But the only issue I have is the it says ''SIM NOT SUPPORTED, NONE VERIZON SIM''
Although the ported rom works fine with data,calls but that non verizon sim gets stuck on the notification bar.
I have ported all the libs and set up build.prop and cant seem to find the issue.
The rom I ported was PLASMAVIII.
Somebody with more experience can take a look at the rom I ported and see what is wrong? It's not going to brick your phone I have flashed it several times and it works.
Anybody interested in helping me can PM me for the link
gypsy214 said:
I tried to port several AOSP CM based roms from the Galaxy Nexus and the Nexus 4. with these guides. http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=2069850
When I use HERO guide the phone never boots more than the boot logo and when I use the other guide I get error status 7.
Im using CM nightly as a base.
Also I tried to port TW roms from the Verizon forums using HERO guide and this guide http://forum.xda-developers.com/showthread.php?t=2104604 But the only issue I have is the it says ''SIM NOT SUPPORTED, NONE VERIZON SIM''
Although the ported rom works fine with data,calls but that non verizon sim gets stuck on the notification bar.
I have ported all the libs and set up build.prop and cant seem to find the issue.
The rom I ported was PLASMAVIII.
Somebody with more experience can take a look at the rom I ported and see what is wrong? It's not going to brick your phone I have flashed it several times and it works.
Anybody interested in helping me can PM me for the link
Click to expand...
Click to collapse
for the one that gets stuck on the boot animation, you could try to take a logcat to see what the issue is.
The non verizon sim thing should be easy to fix. Upload it and ill try to look at it tomorrow after work
Sent from my SGH-T999 using Tapatalk 2
ziggy46 said:
The non verizon sim thing should be easy to fix. Upload it and ill try to look at it tomorrow after work
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
It sure is. It had something to do with the setupwizard.apk He had the samsung setup wizard and not the stuck google one.
as soon I clear the data of the app it went off. rom runs great, Also it doesnt have tether. Will look into the framework-res.apk with Jovi's tethering mod
Hey guys. So, I've been reading and reading and flashing and everything.
Got an S4. It was running 4.3 and I was having Wifi issues.
I had read it was a software issue and welp, I've always liked Cyanogen Mod so I installed that.
It installed the nightly build which was WAY too buggy (I use my camera a lot and it kept failing) edit: but the WiFi worked perfectly!
I got back to 4.2.2 now but now the WiFi is Totally not working now and i'm getting that message about
Kernel is not Seandroid enforcing
set warranty bit : kernel
and it takes forever to reboot.
Since I was on 4.3 do i need to flash that stock rom to get my stock kernel back?
Or can I install deoxed version??
I still need to put custom recovery too!
I know this is a lot of questions and i'm not much of a n00b.
Any help would be greatly appreciated.
Thanks in advance.
re: wifi not working
djphooka said:
Hey guys. So, I've been reading and reading and flashing and everything.
Got an S4. It was running 4.3 and I was having Wifi issues.
I had read it was a software issue and welp, I've always liked Cyanogen Mod so I installed that.
It installed the nightly build which was WAY too buggy (I use my camera a lot and it kept failing) edit: but the WiFi worked perfectly!
I got back to 4.2.2 now but now the WiFi is Totally not working now and i'm getting that message about
Kernel is not Seandroid enforcing
set warranty bit : kernel
and it takes forever to reboot.
Since I was on 4.3 do i need to flash that stock rom to get my stock kernel back?
Or can I install deoxed version??
I still need to put custom recovery too!
I know this is a lot of questions and i'm not much of a n00b.
Any help would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
If you are using any Cyanogen/AOSP/AOKP/GE/KiKat roms then please ignore the following.
If you are using a M919 Tmobile Samsung S4 Jellybean Touchwiz 4.2.2 based rom then here is
the way to fix your wifi issue.
Here is the download link for Ktoonsez's custom kernel:
http://ktoonsez.jonathanjsimon.com/sgs4/TW/KT-SGS4-JB4.2-TW-TMO-12.12.2013.zip
Download it and flash it using cwm/twrp recovery and the wifi will work for you again.
Good luck!
I'm running the stock rom but it seems like somehow it didn't overwrite the Cyanogen kernel.
re: kernel
djphooka said:
I'm running the stock rom but it seems like somehow it didn't overwrite the Cyanogen kernel.
Click to expand...
Click to collapse
That means that this kernel is for you..... "IF you are really running the stock rom".
If your rom was REALLY stock, I mean if you "ODIN" flashed the stock rom using the
official Samsung M919 4.2.2 Jellybean Touchwiz firmware from http://SamMobile.com
or other sources then whatever kernel you had the stock rom would have over-written it.
If you are sure that it's not over written that means that you have NOT ODIN flashed the
official 4.2.2 M919 MDL firmware.
Good luck!
Hello everyone,
Can someone make a cwm flashable zip from stock camera app in android 4.4.3?
It's much cooler than original CM camera, but 4.4.2 port doesn't work on 4.4.3 CM.
Thanks in advance!
Works good to me on latest nightly.
Well, I tried it on Carbon ROM and it keeps crashing everytime I open it.
it crashes because cm does not have motorola framework for the app to work.
https://mega.co.nz/#!7VBRhQSB!ANqt4QUScgdUsdzZQnc0HWQVKOpm9dK7Yk5r5Oey_vQ
check this out.
http://forum.xda-developers.com/showthread.php?t=2779425
thestory101 said:
check this out.
http://forum.xda-developers.com/showthread.php?t=2779425
Click to expand...
Click to collapse
Yeah, I tried it. It's working.
I wanted to use MIUI V7 on my T989, but there was no MIUI V7 ports. So I tried to flash I727 MIUI V7, since i727 has similar(almost identical) hardware specs. After first reboot just after flashing i727 ROM, it booted, but nothing happened later. I supposed that if I flash i727 rom without t989 kernel, I would end up with dead boot. However, since it gives me bootloop, I would need to do some research to find out how to manage it to boot properly.
use t989 kernel
That MIUI Rom is based on CM11, edit zip file with hercules CM11 updater-script and boot.img, it may work... or not
r.dhaliwal said:
use t989 kernel
Click to expand...
Click to collapse
Tried Sultan Kernel and cm11 nightly kernels for t989, after flashing the rom. It does not boot...
YeshuaGnR said:
That MIUI Rom is based on CM11, edit zip file with hercules CM11 updater-script and boot.img, it may work... or not
Click to expand...
Click to collapse
I would try it soon, and tell about the result afterwards. However, trying most of conventional porting methods, which replaces files, does not manage T989 to boot on MIUI V7.
So tonight I tried replacing files from T989 CM11 on that MIUI ROM for i727. It boots, but it is virtually "unusable" since every app shows force close. I think I need to edit framework related jar files.
panda6024 said:
So tonight I tried replacing files from T989 CM11 on that MIUI ROM for i727. It boots, but it is virtually "unusable" since every app shows force close. I think I need to edit framework related jar files.
Click to expand...
Click to collapse
so have you tried editing framework related jars?? me too curiously waiting to have miui7 running in hercules
vnation said:
so have you tried editing framework related jars?? me too curiously waiting to have miui7 running in hercules
Click to expand...
Click to collapse
I tried to add miui resources to framework-related jars, but after replacing smail, it led to bootloop.