[Q] Carbon ROM and UBER Kernel Problem - T-Mobile Samsung Galaxy S II SGH-T989

As the title says:
Got a problem when flashing UBER 2 GHz on Carbon ROM. everything goes fine, then when the phone enters lock screen, phone.apk crashes. haven't installed google apps yet, and also use April 4 build of Carbon ROM. Any problems or AM I JUST LOOKING AT A COMPATIBILITY ERROR?
P.S.
Looked through the UBER Kernel Main Thread. Says you need TWRP 2.6.1.0 . I use TWRP 2.7.0.0. Is there anything wrong?
Thanks!

baloushot said:
As the title says:
Got a problem when flashing UBER 2 GHz on Carbon ROM. everything goes fine, then when the phone enters lock screen, phone.apk crashes. haven't installed google apps yet, and also use April 4 build of Carbon ROM. Any problems or AM I JUST LOOKING AT A COMPATIBILITY ERROR?
P.S.
Looked through the UBER Kernel Main Thread. Says you need TWRP 2.6.1.0 . I use TWRP 2.7.0.0. Is there anything wrong?
Thanks!
Click to expand...
Click to collapse
Pretty sure your issue is either you need GAPPS (all roms need GAPPS... unless they have it built in... if the install instrucitons say install gapps, install gapps. I am fairly confident that phone.apk is part of gapps.) OR UBER isn't compatible with Carbon.
Also, are you using the proper UBER for a KK ROM?

baloushot said:
As the title says:
Got a problem when flashing UBER 2 GHz on Carbon ROM. everything goes fine, then when the phone enters lock screen, phone.apk crashes. haven't installed google apps yet, and also use April 4 build of Carbon ROM. Any problems or AM I JUST LOOKING AT A COMPATIBILITY ERROR?
P.S.
Looked through the UBER Kernel Main Thread. Says you need TWRP 2.6.1.0 . I use TWRP 2.7.0.0. Is there anything wrong?
Thanks!
Click to expand...
Click to collapse
I was having the exact same problem, I've tried running it with uber many times so guessing it's an incompatibility. Uber's experimental Sabermod kernel is working okay with carbon though.
EDIT: Forgot to add that I did install gapps, and I'm also using TWRP 2.7.0.0.

Related

[Q] Wind SGH-T999V CM Help

Okay, I'm new to Android and I heard this is the go-to spot for help. Anyway, this is what happened to my Wind SGH-T999V. Mind you i'm VERY new to this rooting thing
I rooted my S3 by using TWRP 2.6.3.0 and i used odin3 v1.85 and it worked. I downloaded a root checker and it said i'm rooted. Then i put CM 10.1.2 on my sd card and wanted to install it via TWRP recovery but it gave me an error that said "No MD5 filed found" or something along those line.
I then tried to use different versions of twrp ( twrp 2.6.1.0) and a different CM (10.1.1) but i still got the same "no Md5 found" error. So, a friend then told me to ditch twrp all-together and download CWM instead. So, I download recovery clockwork touch 6.0.3.7 and put it on my phone.
THEN, i tried to go back to the recovery boot place, but after that small blue font saying "recovery boot", my phone goes black. I dont see the old twrp recovery or the clockwork one.
I just really want to have Cyanogenmod on my phone, i've been having a hard time. Help please?
Just disable the md5 check, most or the ROM files are not going to include a hash file, but will flash fine. TWRP or CWM will error out if the flash fails.
Also, it sounds like your recovery install failed, just reinstall using ODIN and a file from @DocHoliday77 (I recommend TWRP over CWM, but it is just preference)
It's already unchecked.
Install TWRP and try again, should work without issue. Also, redownload the ROM file, preferably the latest version, 10.1.3RC2 (I think)
Sent from my T-Mobile T999L using TapaTalk 4 and delivered by Planet Express.
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
qasde455 said:
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
Click to expand...
Click to collapse
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
http://get.cm/?device=d2tmo&type=stable
"Stable" is relative, the RCs are just as good.
Aerowinder said:
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
Click to expand...
Click to collapse
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
You need to edit the install script because your device isn't supported. Or you can download Doc's version.
Actually I'm pretty sure cm includes the T999V, but I'm betting the firmware needs to be updated.
Look in Aerowinders Sig for the links to the firmware. In that OP you should find a link to the thread with the T999V firmware.
Or, you can go to my T999L thread and get the Rom there. But w/o updated firmware it may be buggy.
Sent from my SCH-I535 using Tapatalk 4
It's already unchecked.
qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
CM10.1.3 is now Stable and will be the last 4.2.2 build. It should has the all of the Asserts, including the MB7 one. Also, update your TWRP, the current is 2.6.3.0.
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
malibu.barbie said:
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
Click to expand...
Click to collapse
You should read the sticky threads, and use xdas search for terms or definitions anytime you run into stuff you aren't familiar with.
Sent from my SGH-T999V using Tapatalk 4

Process com.android.phone has stopped

Hi, I was running the latest AOKP and I decided to install franco kernel. After doing that, on the reboot I had this error repeteadly and I can't get into the system. How do I enter TWRP? Usually I used to longpress power and select reboot -> recovery, but now I can't use that option.
If I turn on the phone by using volume down + power, I get into the recovery stock, but I can't select anything.
How do I resolve? I managed to get into the recovery once, I wiped data, but the error comes out again. Now I'm stucked on the initial wizard with this popup message :crying::crying:
Just keep pressing ok to it and get to settings/apps/all and clear data in contacts and contact storage. Then let it all re sync from Google
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Just keep pressing ok to it and get to settings/apps/all and clear data in contacts and contact storage. Then let it all re sync from Google
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I reinstalled the rom and it seems to work, but then I tried reinstalling franco kernel and the popup is here again. Why? Is the kernel the problem?
Tommolo said:
I reinstalled the rom and it seems to work, but then I tried reinstalling franco kernel and the popup is here again. Why? Is the kernel the problem?
Click to expand...
Click to collapse
I assume the latest AOKP is based off Android 4.3, and you're trying to install Franco r392? Have you tried the modified Franco r392 by @osm0sis?
Sent from Samsung Captivate Glide @ CM10.2
I am experiencing the same behavior on the 2013-11-14 AOKP build. I have tried r392-fixed by osm0sis and was surprised to see the same issue. I've used that kernel on an earlier build of AOKP without issue. I would really like to reinstall Franco kernel. Is there anything else that I can try?
Thank you
lanruid said:
I am experiencing the same behavior on the 2013-11-14 AOKP build. I have tried r392-fixed by osm0sis and was surprised to see the same issue. I've used that kernel on an earlier build of AOKP without issue. I would really like to reinstall Franco kernel. Is there anything else that I can try?
Thank you
Click to expand...
Click to collapse
Did you try my above post? I used to test the official PAC rom for the Xperia S so it happens a lot with test builds. It always sorted the issue
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Did you try my above post? I used to test the official PAC rom for the Xperia S so it happens a lot with test builds. It always sorted the issue
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried the r392-fixed by osm0sis. I used the same .zip file that I have successfully installed on previous AOKP builds. While there is no way to clear Contacts and Contact data once in this "com.android.phone has stopped" loop, I have tried clearing the Contacts & Data, then immediately rebooting into recovery and flashing r392-fixed. Upon reboot I am presented with the same message. Thinking that this may have been something caused by restoring data from Titanium, I did a factory reset and clean install of AOKP 2013-11-14 along with franco r392-fixed and I still see the issue. I have cleared both cache and dalvik on every flash. Could there be some other cache stored on the sdcard somewhere causing issues?
At this point I was planning to wait for the next AOKP release and hope the issue goes away unless someone has other suggestions.
Thank you.
i had the same problem with franco kernel.
go into bootloader mode , and use the wugfresh root toolkit to boot your phone into custom recovery , and flash another kernel.
handofdark said:
i had the same problem with franco kernel.
go into bootloader mode , and use the wugfresh root toolkit to boot your phone into custom recovery , and flash another kernel.
Click to expand...
Click to collapse
I was able to get into recovery and simply restore the ROM, which replaces the kernel. I was posting to see if anyone could help me actually get the franco kernel installed on the 2013-11-14 AOKP build. I would like to have posted this in the kernel dev thread, but my post count isn't high enough.
i think the problem is with the r392 franco kernel , cause i had the problem with the latest cm 10.2 nightly version
For future readers who may find themselves in this situation, I found the following procedure to allow you to get out of the error loop and boot into recovery without pulling the battery provided your power off menu has an option to reboot into recovery [AOKP provides this option].
When the phone first boots you will be stuck in an infinite "Process com.android.phone has stopped" popup loop. Dismissing the dialog simply brings it right back.
1. Turn the display off by pressing the power button.
2. Turn the display back on using the power button.
3. Dismiss the dialog. It did not come back at this point for me, leaving me at a normal looking slide to unlock screen.
4. Long press the power button to bring up the Power Off / Reboot menu.
5. Reboot into recovery.
At this point you can re-flash your ROM which should restore the stock kernel provided with your ROM.
---------- Post added at 01:26 PM ---------- Previous post was at 01:16 PM ----------
handofdark said:
i think the problem is with the r392 franco kernel , cause i had the problem with the latest cm 10.2 nightly version
Click to expand...
Click to collapse
Please try the r392 FIXED version provided by osm0sis. I believe there is a link provided earlier in the thread. While this did not work for me with the 11-14 AOKP build, I have had it work with earlier builds and many have had luck with it using CM based ROMs.
My problem is that even the fixed version left me with the com.android.phone error and I'm not sure why.
im good with leankernel at the moment thanks
I'm having the exact same problem. I'm using AOKP 2013-11-14. I also tried the previous version of the Franco kernel, r391, but it did the same thing.
Is there another kernel that you guys can recommend that's as well supported and has similar features?
Also, I wanted to say that I've seen posts from lots of people using AOKP+Franco, saying that it works perfectly. Why is it suddenly not working for us? Could it be our particular AOKP nightly version?
TheNexian said:
I'm having the exact same problem. I'm using AOKP 2013-11-14. I also tried the previous version of the Franco kernel, r391, but it did the same thing.
Is there another kernel that you guys can recommend that's as well supported and has similar features?
Also, I wanted to say that I've seen posts from lots of people using AOKP+Franco, saying that it works perfectly. Why is it suddenly not working for us? Could it be our particular AOKP nightly version?
Click to expand...
Click to collapse
Did you try the fixed version by osm0sis? If not, you can find a link earlier in this thread and in the Franco kernel thread. If it works for you, please let me know because it didn't for me with this build.
lanruid said:
Did you try the fixed version by osm0sis? If not, you can find a link earlier in this thread and in the Franco kernel thread. If it works for you, please let me know because it didn't for me with this build.
Click to expand...
Click to collapse
I'm sorry, I can't find the link in either of the locations. I did a search for the word "osm0sis" in the franco kernel thread and it doesn't show up.
I'm very much a newbie at rooting and roms at the moment, so please excuse the question, but is there any reason that two identical phones running the same rom, kernel, and recovery should behave differently? My phone's the I9250, and I'm using clockworkmod recovery.
Thanks
try franco r394
I was having the same problem while using CM 10.2 and several Kernels.
I have now flashed franco.Kernel r394. All modification done by osm0sis are included and it's working fine on my Nexus.
Sczep said:
I was having the same problem while using CM 10.2 and several Kernels.
I have now flashed franco.Kernel r394. All modification done by osm0sis are included and it's working fine on my Nexus.
Click to expand...
Click to collapse
Same here. r394 is working fine with AOKP nightly 2013-11-14 on my GNex as well.
I got this error when I try to place or pick a call in PAC or Carbon or crDroid rom. But no such error in slim rom. Can anyone tell me why. I really want to try pac rom.
sent from a phone running on SLIM ROM

[Q] Flashing CM or PAC, Bootlooping

What am I missing? Every time I flash CM it just bootloops at the LG screen. I've flashed before so I'm very familiar with the usual stuff. I downloaded CM from CMs website, the most recent nightly, for my ls980. I'm running TWRP 2.7.0.0 for ls980.
I've heard of things being "lokified". I tried flashing through flashify which I heard "lokifies' files if needed. I'm not sure though.
Only thing I can see is that maybe my file isn't lokified? Anything I am missing?
JamesChilds said:
What am I missing? Every time I flash CM it just bootloops at the LG screen. I've flashed before so I'm very familiar with the usual stuff. I downloaded CM from CMs website, the most recent nightly, for my ls980. I'm running TWRP 2.7.0.0 for ls980.
I've heard of things being "lokified". I tried flashing through flashify which I heard "lokifies' files if needed. I'm not sure though.
Only thing I can see is that maybe my file isn't lokified? Anything I am missing?
Click to expand...
Click to collapse
Never mind, I figured it out. apparently the compatible kernels aren't bundled in the zip? Every other device I have used had the kernel included. If I am wrong please clarify. Also, is there a list of kernels/radios for my device somewhere that say what they support?
Never mind guys it is still not working. I am flashing the Rom, the Gapps, the KK aosp modem and a kernel made for aosp.
JamesChilds said:
Never mind guys it is still not working. I am flashing the Rom, the Gapps, the KK aosp modem and a kernel made for aosp.
Click to expand...
Click to collapse
did you ever solve this i need help flashing roms too.
Are you using the zv8 modem.IMG if not that can cause bootloop also be sure to wipe cache/dalvik
I could never get CM, PA, or PAC to work. I just installed Slimkat rom with no problem. You might need to update your TWRP as well, I think it has been updated since 2.7.0.0 to 2.7.0.2? If I am not mistaken.

No Signal AOSP, IMEI Zero'd Out. Please Help!

Hello, normally I do lots of research and searching in order to figure out problems for myself, but this one I have been stuck on for weeks.
I am on SGH-T999v, here is my issue.
I am trying to use either the latest 1.5 Spirit Rom, or M4 gummy Rom in combination with KTOONSEZ Kernel from here.
If I try to flash the kernel with latest versions of those roms, my baseband says "UNKNOWN" and my IMEI gets zero'd out.
Also it tells me that I have no sim card inserted. I have tried formatting dalvic/cache before and after installation of kernel as well as fixing permissions.
Both Spirit 1.5 and Gummy M4 work no problem without the custom kernel installed.
Also, on only 1.1 Spirit and M3 gummy, am I able to use the custom KT kernel and still have my signal.
Okay now here is the strange part of the problem.
Currently I am using the custom recovery TWRP that lets me use multiboot from here
And after successfully creating a multiboot rom, I go ahead and install Gummy M4 + Gapps + KT Kernel and boot it up, to find out that it actually works perfectly fine.
My baseband shows up, and my signal connects.
Also the version im using of the recovery menu is V2.11
I am just wondering why is it that the rom + custom kernel doesn't work with a regular flash, and that it only seems to work when I multiboot it?
What I want is to not have to create a multiboot rom in order to use this, I want to actually flash these to my phone.
Please help me, anyone who has any idea of what I am talking about..Sorry if I have not been clear enough. Thank you/.
Edit: I also forgot to mention that I have tried flashing the stock modem after the kernel + rom installation through odin, that did nothing.

[Q] Can't install CWM recovery on ICS

Hello, i've seen two methods to install CWM. One for gingerbread using a file on PC.
And a different one for ICS installing x-part which is supposed to be an auto-installer of CWM.
Everything installs ok, but i cannot access the recovery mode.
What should i do? Could be because im using the stock kernel?
My phone details:
Xperia Arc S - ICS 4.0.4 - Bootloader unlocked - Rooted.
If you have a unlocked bootloader I suggest you go and flash a custom kernel with CWM on it.
Thank you, i decided to take the risk to avoid stress and installed a CWM made for gingerbread, and it worked perfectly fine for ICS.
Now i'm running CM10 and everything is good, except sometimes i lose signal and get invalid SIM for no reason.
Madbezier said:
Thank you, i decided to take the risk to avoid stress and installed a CWM made for gingerbread, and it worked perfectly fine for ICS.
Now i'm running CM10 and everything is good, except sometimes i lose signal and get invalid SIM for no reason.
Click to expand...
Click to collapse
You can use CM10.1 or CM11, they're pretty much stable already.
popthosegaskets said:
You can use CM10.1 or CM11, they're pretty much stable already.
Click to expand...
Click to collapse
Really? Because my CM10 started to lag a bit. You think with kitkat it could be more stable?.
I've seen the camera works much better. What are the bugs so far? No hdmi, no radio?.
I've got the "cm-10-20131006-NIGHTLY-anzu" ROM installed, is that supposed to be 10.1 or 10?
Madbezier said:
Really? Because my CM10 started to lag a bit. You think with kitkat it could be more stable?.
I've seen the camera works much better. What are the bugs so far? No hdmi, no radio?.
I've got the "cm-10-20131006-NIGHTLY-anzu" ROM installed, is that supposed to be 10.1 or 10?
Click to expand...
Click to collapse
You're on CM10. Kit Kat should work better for your phone. For the list of bugs, you can go to the ROM page and have a look.
popthosegaskets said:
Kit Kat should work better for your phone. For the list of bugs, you can go to the ROM page and have a look.
Click to expand...
Click to collapse
Thank you very much man, i thought this subforum was dead.
Last two questions hopefully:
1) is there any stable version of CM11 i should consider or should i download anything (like CM11.1, CM 11.2, etc)? Because on the CM page i found nothing with the word "anzu" or "xperia arc" on CM11.
2) Since i already have CM10. Do i need to do anything on the PC with flashtool, etc?. Or can i just put the CM and google apps zips on my SD card, and install from recovery (after clearing cache, etc).
Madbezier said:
Thank you very much man, i thought this subforum was dead.
Last two questions hopefully:
1) is there any stable version of CM11 i should consider or should i download anything (like CM11.1, CM 11.2, etc)? Because on the CM page i found nothing with the word "anzu" or "xperia arc" on CM11.
2) Since i already have CM10. Do i need to do anything on the PC with flashtool, etc?. Or can i just put the CM and google apps zips on my SD card, and install from recovery (after clearing cache, etc).
Click to expand...
Click to collapse
You won't be able to find it on the CM page because it is an unofficial release. The thread is here:
http://forum.xda-developers.com/showthread.php?t=2545354
You need to flash the new kernel that comes with CM11 before you can use it.

Categories

Resources