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
Related
I am fairly new to Android, but am comfortable with command line operation on other Unix systems, etc. I read every thread I can find on this, but did not find my problem described exactly (there are some similar problems), so here it is:
My phone is a GSM Galaxy Nexus, about a month old. I rooted and unlocked it right away using post 1 from this guide: [VZW/SPRINT/GSM][Guide] Ultimate Galaxy Nexus Guide (Unlock/Root/Flash Roms/FAQ) - thanks Jubakuba!
I did NOT use any of the toolkits or automated methods.
A couple of days ago, I decided to try loading another ROM. I read through post 2 of the above guide. I followed the instructions in that thread and flashed a Trinity ROM. The flash seemed to go fine, and completed normally, but when I rebooted the phone, it was stuck in the Google Lock screen bootloop. I was able to restore a nandroid to get it back to where it was before, and the phone operates normally, no resets, reboots, nada. I inquired in Jubakubas thread as well as in the Trinity ROM thread in the developers section, and got some suggestions, which I tried. None of them worked. I also tried flashing a few other ROMS, a CM9 ROM and the RASCREAM ROM, and they all do the same thing. I have tried flashing these without wiping data or cache or dalvik cache, wiping some of them and wiping all of them, and the results are always the same - boot loop, which I can restore using CWM recovery and my nandroid.
One of the posters in the developers forum suggested taking the phone back to unrooted stock condition, so I did that, using this thread: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid build / Return to stock - another excellent guide, which worked exactly as described.
After that, my phone was back to as new, and I had to go through the whole start-up and restore applications, etc. I made a new nandroid so that recovery would be relatively painless, etc. Not too tough. I then Rooted the phone (it was always unlocked) and tried flashing a ROM again, with exactly the same results. Again, I was able to restore my nandroid and get back to operational.
I guess my question at this point is what on earth could be causing this? Some of the threads on boot loops where peoples phones start to boot loop spontaneously suggest a hardware problem, but the fact that I have NEVER had a boot loop in a month of use while running 4.0.4 stock rooted and unlocked seems to point more toward software as the cause. I will say one thing - I am learning how to use CWM and the bootloader commands! But, I would really like to be able to use some custom ROMS, not that there is anything really wrong with stock - this is a great phone. But, please HELP!
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into fastboot mode, then flashed the bootloader (bootloader-maguro-primela03.img) and radio (radio-maguro-i9250xxla02.img). I rebooted the bootloader, then went into recovery mode. From recovery mode, I selected "Install zip from sd card", "Choose zip from sd card", then selected the zip file in the /Download folder "TNP1536-384-Alpha86b-4.7-lto.zip". It went through its' install and said "System successfully corrupted" at the end and "Install from sdcard complete." I went back to reboot system rom and rebooted. Now, it is not looping anymore, but just sitting at the Google lock screen for about 2 minutes now. I will wait a few more minutes to see if it boots the rest of the way or starts looping, etc.
Okay, it has been 5-6 minutes with no additional changes, so I am pulling the battery. Powering it on now results in the same boot loop as before, so I will need to boot into bootloader mode and restore my nandroid.
are you wiping data when you flash the rom?
if not, you need to do that first inside of cwm
I would let it sit longer before pulling the battery
Sent from my Galaxy Nexus using xda premium
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
CYoung234 said:
"System successfully corrupted"
Click to expand...
Click to collapse
The
BOOM!
System successfully corrupted
Please freak out now
is a joke. By your account the kernel flashed successfully. Try flashing another kernel, perhaps not an Alpha version, although I've run that particular Alpha successfully. Do you have an app that sets kernel settings on boot by chance?
Hmmm thats a Kernel i think try another kernel.. Franco is a option ... maybe ur phone can't handle the undervolt of Trinity? I don't know worth a try download franco and post ur results here
Good luck
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The nandroid I am restoring to is stock 4.0.4. I will wipe everything, then try flashing a known stable aokp build, then report back.
efrant said:
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
Click to expand...
Click to collapse
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
CMNein said:
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
Click to expand...
Click to collapse
Yes, pretty much this. If you are updating CM9 to the next build, no need to wipe. If you are going from CM9 to AOKP, then you need to wipe.
Updating: no need to wipe.
New ROM: wipe.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You are correct, it is a kernel, not a ROM. I have tried 3 different Trinity kernels and one Franco kernel, all with the same results. The specific kernel I flashed for post #3 was TNP-1536-384-ALPHA86b-4.7-LTO.zip. The other two I tried were both stable releases. Morfic asked me to try the alpha kernel.
CMNein said:
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
Click to expand...
Click to collapse
Google Galaxy Nexus i9250.
CYoung234 said:
Google Galaxy Nexus i9250.
Click to expand...
Click to collapse
Okay, was asking in the event that you were also flashing Rascream, or Morfic's build of it.
Re: wiping, since we now know that we're just talking kernel here, wiping dalvik + wiping cache is indeed approaching useless, so they weren't leading you astray. I can't think of what would be causing you to boot loop however.
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
CYoung234 said:
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
Click to expand...
Click to collapse
This got me thinking: is trinity even compatible with a stock ROM (regardless of it being 4.0.4)? Maybe that is why you were having issues.
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Shane24 said:
My phone locks up almost daily and I have to remove the battery and then put it back in to get it going again.
This cant be normal...
I have TeamWin loaded onto it and have installed LiquidSmooth using this. I wiped the Cache, Dalvik, System at least three times before installing LiquidSmooth. I have tried installing it a few times with the same result.
Still, the phone locks up and it generally locks up while I am on a call. It generally doesnt lock up while using an app or browsing.
I am getting kind of sick and tired of removing the back cover and pulling the battery daily....
Any thoughts ?? Help !
INFO:
Phone: Samsung Galaxy S3, AT&T, SGH -I747
Android version 4.2.2
LiquidSmooth: liquid_d2att-userdebug 4.2.2 JDQ39 eng.liquid.20130403.222500 test-keys
LiquidSmooth Version Liquid - JB-v2.1-OFFICIAL
Kernel version: [email protected] #167
(I did try installing AOKP as well, and that gives me an error installing, so I couldnt even get that going - maybe these problems are related??)
Click to expand...
Click to collapse
Hey man,
My suggestion is to use Odin to flash the stock image back to stock and see if the problem persists. If it does, I'd take it back to at&t for a new phone (if you've had it less than a year or you have some sort of insurance plan.)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 02:23 AM ---------- Previous post was at 02:18 AM ----------
If flashing back to stock fixes it, its user error. Make sure you're up to date on everything, I.e boot loader, recovery, everything. If that does nothing for you maybe try flashing the new version of CWM and see if it'll flash right that way.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it just me or is your lean kernel like years old? Isn't the newest version 7.2?
Same with your rom.. 2.9 is out?
Sent from my SGH-I747 using xda premium
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Shane24 said:
Yes, the kernel could be old. I have never updated it... I hate to admit, but I have no idea what the kernel does actually or how to flash a new one.
I have installed the ROM, but not the kernel obviously....
Any info on what a kernel does? Can I flash it easily with TeamWin ?
I can definitely upgrade the ROM to the latest version of liquidSmooth
Click to expand...
Click to collapse
Hey man,
If you're going to be flashing custom ROMs you should probably learn what a kernel is. Use the search feature or simply use google. In fact, the xda TV channel just put out a video on kernels this week on YouTube.
Anyways, as I said previously, make sure EVERYTHING is up to date. Including the ROM version. Dont worry about flashing kernels until you have a solid understanding of what they are. I'm almost positive that you are just flashing out of order. Just start from scratch, make sure EVERYTHING is up to date. Good luck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Shane24 said:
yup, I got up to speed on kernels. (Thanks for the suggestions as I didnt know about Kernels, but now I do...)
So, the plan is to
- wipe: dalvic, cache, etc... (3X)
- install the Bionic Sheep 4.2.2 Kernel
- install ROM (I'll try Hyperdrive and DeadlyVenom and LiquidSmooth again)
- install Google Apps...
I have TeamWin installed obviously.
Hopefully this will get my phone back on track...
Click to expand...
Click to collapse
What the guy above me said about TW roms is correct. Flashing the wrong kernel is not a good idea. Here's what I do on every flash
- wipe system, data, caches, etc.
- flash rom( and gapps if necessary)
- boot up rom and let it settle for 5 min, then boot back into recovery
-flash correct kernel for the rom's version(check kernel number in about device and custom kernels op), then wipe both caches and fix permissions.
-reboot and enjoy:laugh:
DMF1977 said:
Hyperdrive and Deadly venom are touchwiz ROMs, u can't flash bionic sheep with them!!! And u don't need to flash gapps with tw ROMs either!!
Also, u need to flash a kernel after u flash the ROM, otherwise it will be overwritten by the stock kernel for whatever particular ROM u are flashing. I would suggest sticking with the stock kernel for a bit and see how it runs!
Click to expand...
Click to collapse
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Shane24 said:
Which Kernel would I need to use then for Touchwiz ROM's ???
And which kernel for LiquidSmooth and AOKP ??
Click to expand...
Click to collapse
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
DMF1977 said:
Like I said, I would suggest sticking with the packaged kernel that comes with whatever ROM that you are going to flash, run it for a few days, after that if u still feel the need for something more, go with a custom kernel! Ktoonsez makes an excellent kernel, one for tw, and one for aosp, u just have to pick the right one according to which ROM you're running!! Good luck...
Click to expand...
Click to collapse
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Shane24 said:
I did try flashing AOKP with TouchWiz, and it gives me an error that it cant flash.
Is the kernel that Ktoonsez all part of the ROM and just one file ?
Ultimately, I would like to flash AOKP, but my Galaxy S3 wont allow it...
Click to expand...
Click to collapse
What?
What DMF1977 was saying is just flash the ROM you desire to have on your device and just run the kernel that comes with the ROM. After running the ROM you chose for awhile, if you feel the need to flash a new kernel then and only then flash the correct version of Ktoonsez kernel. And its not surprising that if you tried to flash anything AOKP related with TW you got an error.
Just flash an AOKP ROM and Dont worry about flashing an additional kernel.
Goodluck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
brettbee said:
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
Click to expand...
Click to collapse
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
try beanstalk 1.300
brettbee said:
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
Click to expand...
Click to collapse
I have been using beanstalk 1.300 with the b-team CM kernel.it has 4.2.2 and everything works! its fast and smooth with great battery life the 4.3 roms have some issues so I am gonna stick with this one
AFAIK everything in the newest Evervolv works.
phillibl said:
AFAIK everything in the newest Evervolv works.
Click to expand...
Click to collapse
Are you using a nightly? Which one?
Does 3G come back after WiFi is turned on?
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
kahlil88 said:
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
Click to expand...
Click to collapse
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Thanks!
brettbee said:
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Click to expand...
Click to collapse
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
brettbee said:
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
Click to expand...
Click to collapse
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
brettbee said:
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
Click to expand...
Click to collapse
What version of gapps are you installing? Try flashing the ROM without installing gapps and see if it will boot, then if you're successful go back into recovery mode and flash gapps-jb-20130813-signed.zip from here.
funny question, does docking mode work with these roms?
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
flinzak said:
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks - found it and downloaded it! I'll give it a try when I can have my phone out of service.....
I flashed Evervolv 10/30 nightly yesterday and it looks like they have the 3G/WiFi toggle issue resolved. The quick settings were missing but, I'm guessing that'll be corrected in the next build. Also, flashed B-Team Kernel. 4.3-s2w version resulted in bootloops but, the 4.3-v2 version worked just fine. No sound issues as far as I can tell.
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
jonatcer said:
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
ArslanQureshi said:
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
Click to expand...
Click to collapse
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
jonatcer said:
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
Click to expand...
Click to collapse
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
ArslanQureshi said:
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
Click to expand...
Click to collapse
Alright thanks a bunch.
Would you, or anyone else still reading this thread, care to weight in on whether Evervolv or CB's rom (Which? Beanstalk?) is more stable?
Is AOKP broke for the T-Mobile S3? I tried installed and kept getting (status 7). So I modded the file to make it boot and still nothing. I did everything I could and it just wouldnt work. I prefer AOKP so any help is greatly appreciated.
Then I booted CM11 and it worked fine. But now Tapped Out wont work. It goes to start, gets just past the initial screen and force closes. So any help is appreciated on that.
I am pretty sure that if I can get AOKP to run then Tapped Out will work. So there in lies my issue.
I am using TWRP if that helps. Thanks in advance.
In the meantime I went to AOKP JB MR-1. Its their last JB and its a milestone. But I would like to get 4.4 until Dandroid does Wi-Fi calling.
Please update your Recovery to the latest version.
im on a note 2 running the latest PA and also have this issue. my recovery is the latest Philz.
This is not a forum for your device.
Perseus71 said:
Please update your Recovery to the latest version.
Click to expand...
Click to collapse
I am on the latest recovery. Still no workey. I think its an issue with AOKP. I will give them some time before I try again.
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.