Related
I'm hoping that someone might be able to help me with a problem I'm having with the Franco Kernel. I have a rooted Galaxy Nexus, running on stock Android 4.0.2. I have a bit of experience running various custom ROMs and kernels with a OG Droid and HTC Thunderbolt. Until now, I've been content to run stock ICS on the GNex, along with the stock kernel.
I was impressed with the amount of praise I have recently read (I'm a habitual lurker on a number of Android forums) about the Franco kernel, however, and thought I would give it a go. If it can improve performance and battery life, that is fantastic. So, I bought the franco.Kernel updater from the Market, downloaded the zip file (#15), proceeded to recovery and installed it.
That seemed to all go smoothly. The problem is that when I rebooted, the phone got hung up on the black and white "Google" screen. I know sometimes, it can take a while for the phone to do what it needs to do under the hood before it boots up, but after ten minutes on the "Google" screen I did a battery pull, went straight to recovery and reverted to my latest backup.
I've done some searching for anyone who's had a similar issue, but I can't seem to find what the problem might be. Most likely, I'm simply missing something small but critical to the successful installation of this kernel. I'm hoping someone with more experience than me might recognize what it is I'm doing wrong.
Any patient assistance or advice would be heartily appreciated. Cheers!
I could be wrong, but Franco works for 4.0.3, not 4.0.2.
Which could be precisely the one small thing I am missing. I will check this out. Thanks for the suggestion.
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
P4p3r1n0 said:
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
Click to expand...
Click to collapse
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
bowsersoulstar said:
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
Click to expand...
Click to collapse
cool! thanks! good to know I read a bit everywhere.
I mean, I know how a kernel is, and thinking about it it's true that is not needed to wipe, but if he has some problems he could try this out :/ maybe a fresh installation of everything could be good
I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.
Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.
All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?
I'm currently running GB El29 and am looking to update. I've done a lot of reading around the forum, the wiki, and a few other websites, and I'd just like a little bit of clarification. I figure I'd ask now, before doing anything, as opposed to asking later, after something's gone wrong.
Looking at the Wiki, I was considering updating to Calkulin's E4GT 2 v1.6, or unrooting and then waiting for the Official ICS update (it was rerolled today, apparently.) Or, to Blazer, but I'm not sure if going to the ICS version or GB version is best.
My question - The process to update - Nandroid, Flash Format All, Flash Rom, Success? I've noticed a lot of installs say to "Wipe All", and I assume that's what Flashing Format All does, correct? I just don't want to mess up - I had no problems rooting, following that guide I mentioned, and I've done a lot of reading...I just want to confirm before doing anything. I mean, I know, wipe delvic and clear cache, but Format All does that, correct?
I rooted my phone using "How to Root Galaxy S2 Epic 4G Touch! [NEW][SPH-D710]" rom Epic4gtouchroot.com. I'd post a link, but I've fewer than 10 posts. All I've done, outside of root, is install the Beats sound files. That's really it.
Any help at all would be greatly appreciated.
Read this 10 times over then you should be fine.
http://forum.xda-developers.com/showthread.php?t=1525495
If you are interested in certin roms read threw the rom post to see if people have already answerd the questions you seek. Some devs request you flash different ways so read the OP in the post of the roms you are considering
UnOfficial
Read this once, stay with gingerbread, try Calks E4GT V. 3.0 YOU won't regret it.
Pp.
Delivered to you via Mayan technology .
PanchoPlanet said:
Read this once, stay with gingerbread, try Calks E4GT V. 3.0 YOU won't regret it.
Pp.
Delivered to you via Mayan technology .
Click to expand...
Click to collapse
Yeah, that's what I was thinking of going with. I've read over his topic several times, and even though I'm really not a fan of the transparent notification tray, most of the included mods sound really, really useful. Thanks for the heads up.
And thank you too, jugaloo. I actually have that page bookmarked on my phone lol. I've already made several nandroid backups - I plan on making a titanium backup in a moment. My only concern now is th process from going from El29 GB to E4GT 3. Rereading that thread several times has me wondering - I download the ROM, place it on the SD, boot into recovery, clear delvic and cache, run Format all, then install the ROM, correct? I already have a nandroid backup, so in case anything here goes wrong, I can just flash the backup back on, correct?
IceCatraz said:
Yeah, that's what I was thinking of going with. I've read over his topic several times, and even though I'm really not a fan of the transparent notification tray, most of the included mods sound really, really useful. Thanks for the heads up.
And thank you too, jugaloo. I actually have that page bookmarked on my phone lol. I've already made several nandroid backups - I plan on making a titanium backup in a moment. My only concern now is th process from going from El29 GB to E4GT 3. Rereading that thread several times has me wondering - I download the ROM, place it on the SD, boot into recovery, clear delvic and cache, run Format all, then install the ROM, correct? I already have a nandroid backup, so in case anything here goes wrong, I can just flash the backup back on, correct?
Click to expand...
Click to collapse
I just run the format x2 script made by ruj in the blu kuban thread. Then i follow the devs op to install. From what i see you have your feet planted and ur about to make that plunge. Id take the next step and try the flash. Id go with a different rom the the fe22 is out of date and calk has moved on. Try blu kubans rom its super stable and ita built from source. I myself like gb better.
UnOfficial
juggalo1300 said:
I just run the format x2 script made by ruj in the blu kuban thread. Then i follow the devs op to install. From what i see you have your feet planted and ur about to make that plunge. Id take the next step and try the flash. Id go with a different rom the the fe22 is out of date and calk has moved on. Try blu kubans rom its super stable and ita built from source. I myself like gb better.
UnOfficial
Click to expand...
Click to collapse
I was thinking that - Calk's topic was updated in May, while blukuban was updated in February. I mean, I can always try both, right? I'd like to go with Calk's first, then try blukuban, only because BK is heavily themed. But either way, thanks!
Edit
I didn't realize the blukuban thread had updates outside of the OP. It was very recently updated. I might check that one out first.
Yes the blu kuban ics is always up todate and he is there for the people. If you want ics builds that are more stockish id aokp they have theming going on but is nice and stable. Read all of the op and there sites for correct install. Cm9 alpha 6 is also really good. Blazers rom is also really good. Those are all stockish built from source. For gb roms id go with either calks 3.0 or UnOfifcials ics gb rom. For me gb gives me most bang for battery and bandwith. Those last two roms are highly recomended. Calks is super fast stock with options for themes. Unofficial gb ics is themed lightly and is very good for battery and the animations are nice
UnOfficial
Alright, awesome. Waiting for my battery to finish charging (my phone reset while performing a titanium backup, and the battery life dropped from 44 to 9, so I'm getting it back up to at least 50.)
So just to recap
-
To Install
Boot to recovery
Make a NAND Backup
Wipe Phone (Format All/wipe delvic/wipe cache)
Install ROM
Right? That's what Blukuban's install requires, and Calk's doesn't have any special instructions, outside of " a wipe is recommended BEFORE flashing if coming from another ROM", which is what the Format All is for, correct?
You've been insanely helpful. Thank you so much! I'm also looking into UnOfficial (it's not on the Wiki, so I didn't really know about it until you mentioned it.
IceCatraz said:
Alright, awesome. Waiting for my battery to finish charging (my phone reset while performing a titanium backup, and the battery life dropped from 44 to 9, so I'm getting it back up to at least 50.)
So just to recap
-
To Install
Boot to recovery
Make a NAND Backup
Wipe Phone (Format All/wipe delvic/wipe cache)
Install ROM
Right? That's what Blukuban's install requires, and Calk's doesn't have any special instructions, outside of " a wipe is recommended BEFORE flashing if coming from another ROM", which is what the Format All is for, correct?
You've been insanely helpful. Thank you so much! I'm also looking into UnOfficial (it's not on the Wiki, so I didn't really know about it until you mentioned it.)
Click to expand...
Click to collapse
Charge the bartery more. Use a wipe script dont touch the fomat that is built into the cwm while flashing a ics rom. If you use the wipe x2 script found here
http://forum.xda-developers.com/showthread.php?p=25448865
U should be good. It wipes everythings even both of the caches twice. If you already have a newer nandroid id just go with that instead of making a new one everytime you flash. If possible download the roms to pc check the md5 check sums make sure they match. If they match transfer to the phone. When downloading to the phone it has a higher chance of a bad download. I try and flash at 75% battery incase of error and you have to restore a previous nandroid. If you want read this post about the eMMc bug. Most roms are safe now but some are not current.
http://forum.xda-developers.com/showthread.php?t=1644364
Not trying to scare you with that last link you should know about it before hand so you know the dangers of flashing a non safe ics roms. If you have any more queations shoot. But i think your good to go
UnOfficial
One more thing. Qbking27 has install video guides for 90% of the roms in the threads of the rom. Id watch those before installing that rom you want. Some times they are buried in the op. You can use them as a step by step as you install. Best if luck to you and i want a report once you get your new custom rom on your phone.
UnOfficial
You got it!
I'm doing a GB build - from what I've come across, GB just gets better battery life, and I just feel more comfortable using it. At least, until the official ICS rolls out from Samsung. If that one is well received, and it's worth it, I'll unroot/wipe fresh and try it out.
That being said though, I'll use x2 then. Will it matter if I do both, just for good, measure? (Both x2 and FormatAll)
And yes, I'll be downloading to PC first, then transferring. I feel more comfortable doing it that way. I'll be doing Calk's 3.0 first, and if I don't like it, I'll try either Unofficial or BluKuban.
And once it's done charging more, and I perform the install, I'll report back, with a screenshot or two as well.
IceCatraz said:
You got it!
I'm doing a GB build - from what I've come across, GB just gets better battery life, and I just feel more comfortable using it. At least, until the official ICS rolls out from Samsung. If that one is well received, and it's worth it, I'll unroot/wipe fresh and try it out.
That being said though, I'll use x2 then. Will it matter if I do both, just for good, measure? (Both x2 and FormatAll)
And yes, I'll be downloading to PC first, then transferring. I feel more comfortable doing it that way. I'll be doing Calk's 3.0 first, and if I don't like it, I'll try either Unofficial or BluKuban.
And once it's done charging more, and I perform the install, I'll report back, with a screenshot or two as well.
Click to expand...
Click to collapse
Just use the wipe x2 that does everything you need. Blu kubans gb rom is good but wifi is whacky. Id go with his ics build. Well your set good luck!
UnOfficial
Alright so, I installed it, and all is working well. It's actually a bit...erm, slow? Whenever I swipe from screen to screen on the homepage it's a bit laggish. But it works! I'll run around with it for a little while and see how it works. I'm in the process of reinstalling my older apps, updating my contacts and such.
Thanks for all of your help!
Edit
A little worried, to be honest. Some of the apps I'm trying to install is giving me the "Package file is invalid" error off of the Google Market. Dropbox, Amazon, etc. Not sure what to make of it, to be honest.
Try and clear the cache for the market. If your using tb try to unmount the sd card if that dont work do fresh installs off the market place . Also go into recovery and clear the cache and dalvik.
UnOfficial
juggalo1300 said:
Try and clear the cache for the market. If your using tb try to unmount the sd card if that dont work do fresh installs off the market place . Also go into recovery and clear the cache and dalvik.
UnOfficial
Click to expand...
Click to collapse
Done. I cleared both caches, and so far, all of the problems I've had with the market is gone. (Dropbox didn't install on the first try, but it did after the second.)
I've replaced the default touchwiz interface with Launcher Pro (TW was running wicked slow - loads of lag with just basic scrolling) and it seems to be running well. And it's definitely saving on battery life.)
That being said, it's not really my cup of tea. I restored my contacts and such, but eh. I think I'll try UnOfficial, and if it's not better, either go back to el29 or update to official ics.
I'll likely keep this one until tomorrow. You've been such a huge help. Thank you so much.
Actually, with launcher pro replacing it, this is pretty good. I want to mess with it more. I'll run it for a few days and see how it fairs.
Ok wait before everyone leaves, Ive got some questions too!
I just got my replacement(after a hard brick trying JB) and figure Id ask my questions in this thread rather than starting a new one..
1. Ive decided to odin EL29 EVERY TIME I want to flash a new rom, just to be safe. If I use CMW with EL29 and decide to try out CM9, Do I always need to flash a aokp kernel? Or is that built into the CM9 install?
2. If I like CM9, and want to make a nandroid backup of it, do I need to Odin back to EL29 first to back it up? Or is it safe to do it with the recovery that comes with CM9?
3. If the answer to #2 is yes, meaning I do have to odin back to EL29, how do I restore my backup? Let me explain:
Lets say I flash CM9, make a nandroid of CM9, then decide to try out say a different rom, like a TW rom. Then I hate the TW rom and wanna restore my backup of CM9. Do I need to ODIN back to EL29 to restore the nandroid? I read in the "how not to brick my..." thread its bad to restore a ICS rom from a GB Kernel. Can someone please explain?
Ive really, really tried to search and read as much as possible before asking, but a lot of the threads are old and have contradicting information. Sorry for being so noobish, but I dont wanna brick my new phone. I come from Evo, Evo3d, Hp Touchpad, etc, where there arent as many issues to flash customs roms. Ive rooted and flashed custom roms ever since the PPC6600, 100's of times and NEVER had a problem. Sorry, this just really confuses me for some reason!!!
Can't help you with CM9 or AOKP because I've never tried either one. The OP was talking about launcher pro. I highly recommend Nova launcher or Apex. They are both specifically built for ICS and look and act like stock android with great customization features.
Was going to make another topic, but I thought I'd ask here first
- The notification tray in this rom (Calk 3.0) is transparent, and I'm not fond of the icons in the Notification Tray. I tried using Rom Tool Box lite to change it, but the tray won't change, no matter what I do. Does anyone know how to fix this? I've tried before - it just won't change.
IceCatraz said:
Was going to make another topic, but I thought I'd ask here first
- The notification tray in this rom (Calk 3.0) is transparent, and I'm not fond of the icons in the Notification Tray. I tried using Rom Tool Box lite to change it, but the tray won't change, no matter what I do. Does anyone know how to fix this? I've tried before - it just won't change.
Click to expand...
Click to collapse
I don't mess with rom tool box. I hear good and bad things about it. If you start at page 1080 and read to the end people post new system ui's but it may theme it a little bit. They have blazers UI in there and one other one I think. I'm not sure it is transparent or not. Or even make a post in the thread about it. I know its still active and you may find your answer. Sorry I can't really help you on this.
Sent from my SPH-D710 using XDA
Alright, cool. Thanks a lot. You wouldn't happen to have the link to that thread, would you? I've searched, and I'm a bit lost. Sorry for the trouble.
Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!
As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:
I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Ya its all kernel related and user error.
Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.
Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.
Okay, so I have been a flashaholic for the past couple of years and been on the AOKP nightlies for a very long time.
However, since the last month or so, every time I try to flash (clean and dirty) a new ROM or upgrade to a newer nightly, the flashing process goes on pretty smooth as expected. But, here is the thing.... after booting up fine, it starts to optimize the apps and I see it going through the entire cycle of apps. When all the apps are optimized, it says "Starting apps" and this is when I feel a vibrate and the phone reboots and does this over and over. My only way out of this is to boot it back into Recovery (TWRP 2.5) and restore my backup and sadly continue using what I had before this exercise.
I have tried various combinations of wipes, fix permissions, kernels, radios, etc. and am totally stumped here!!
Help please as it bugs me to no end when I see crazy new features the newer ROMs are dishing out and I cannot taste them
by clean what are your actual steps you mind elaborating a bit more of your steps, and with which ROM this happens on have you tried a stable as oppose to a nightly to see if it will fix your errors, as far as flashing do you ever format system in mounts and storage when you flash ROMs ???
Clean: Wipe Cache, Dalvik, Format System, Data. I haven't tried formatting the Internal SD or Preload partitions yet.
This happens with quite a few ROMs... I have tried SlimBean, CM 10.1, AOKP M2, PA so far. See the same behavior on nightlies or stables. I haven't tried Stock ROM yet... maybe should give that a try as well.
Let me know if I can give you more information to help me out.
since it seems to be happening on every ROM for you i would suggest you try going back to stock and re-root and try again, it doesn't take that long it just really sucks to do everything from scratch, but its the only way you are going to know where this problem is coming from also if you are on TWRP 6 that might be the problem everyone has been having lately it sometimes works sometimes doesn't have you tried opening ROM MANAGER and fixing permissions only from within the app...see if that squashes your bugs just trying to give some ideas ....
I would hate to go back to stock and re-root all over again. But if all else fails... I guess that remains as my only option.
I am on TWRP 2.5 for quite some time now and have successfully flashed using that numerous times before this problem started... not sure what you mean by TWRP 6 (you mean 2.6?)
I do not have ROM Manager on my phone, will give that a shot as well before resorting to the "Stock" option.
Thanks for your help!
yeah i ment 2.6 lol DOOHH!! and yeah you def sound like you know what you are doing so im sure you will figure it out just wanted to give you some ideas ... and for the record its always nice to take a break but good luck bro sorry i couldn't help you more
It was an issue with the Kernel I guess!!
Flashing SlimBean b8 + gapps followed by the UBER Kernel after wiping the hell out of everything as my last ditch effort I went past the "Starting apps" while I was feverishly holding onto the Vol UP + DN to get into recovery if it fails again.... to my surprise, it went past that screen and there was the start screen I have been looking forward to.... what drama )
I guess will follow all my flashes with the UBER kernel going forward.
awesome man!! glad you got it fixed - Like i said i knew you would figure it out good stuff man, now you got more knowledge and can help others if they run into the same issue happy flashing ! take care