[Q] What kind of "loop" do i have? Happens with AOKP devil and glitch ICS and CM10
First I know the phone is not bricked. I can and have repeatedly ODINed to stock EH03, remembering to atlas and repartition as per droidstyle's guide. The problems begin when I go through the rest of the guide section 4, to get and ICS AOKP rom running. (This is staging for my question to be complete. Question at bottom.)
For whatever reason the phone was stuck to only boot into (red) recovery. I had the AOKP rom MS6-devil before and I think flashed another different devil kernel over that. The phone has been completely stable for months now. I tried data wipe/reset and wipe cache, and dalvik too. It still only rebooted to red recovery (sorry don't recall the exact version). This is when i decided to ODIN and start fresh.
Maybe some side questions. Is it ok to flash different devil kernels on the devil kernel rom? I assume yes but I just needed to run through my check list. When I ODINed back to stock did that automatically restore the phone to a stock kernel as well?
So the phone ODINs fine every time and ODINing cmw4 for CW7 and GB bootloaders too. (BTW when i flashed ICS rom several month back i dont think the guild had anything about ODINing bootloaders. Is this new?). 3 finger works and I'm in blue recovery 4, i wipe data and dalvik (I've done this more than 5 times some i also tried a cache wipe with same results).
What kind of boot loop is this?
I flash the ICS rom zip that i want and it starts but the status bar on the phone make a small amount of progress then goes black, reboots to the flash the Samsung logo then goes to some splash screen that shows Icy Glitch Kernel V14 if i try the AOKP M6 official, or a splash screen of Devil Kernel if i flash AOKP M6-devil or even with CM10 i see the splash screen of cyanogenmod. If i let the phone sit on the screens for a long while all i see is a continual booting to these splash screens.
I have mucked something up with the kernel and i thought ODIN would reset that each time. If I can know what kind of boot loop i face i can go to find the right threads or make a post in the right place to get this resolved.
Actually it's normal for that to happen, after you start the install it should reboot the phone to an updated recovery and continue the installation from there. At least that's what it did for me when coming from stock. How long did you wait? Are you getting any errors? If you're still using the stock sd card that could be your problem right there. Also, I highly recommend trying a JB rom, ICS is pretty stale at this point. AOKP just released JB Milestone 1
Good tips. I didn't know that's what it should look like. I was flashing for many hours and waited 20-30 minutes. The only happenings on screen were the splash screens flashing occasionally as if the phone were looping. Im guessing now that's normal in the flashing process. I've flashed the same roms before months ago and probably the process on screen I just forgot. Ill try again later when I have time and try some jb action and report back.
When going from stock to ics are you first flashing ths build 2? There are many versions of devil available some are built for ics and aome for jb only. It's important to know which one you are dashing cause the jb devil kernels have a specific partition layout needed to get jb to run on the fascinate. I could be wrong but anything higher than 1.5.xx is jb specific.
The devil rode a unicorn named jelly bean
forsakenone said:
When going from stock to ics are you first flashing ths build 2?
The devil rode a unicorn named jelly bean
Click to expand...
Click to collapse
You know I think that is it. I just blanked on doing that. I have build 1 and 2, b/c sometimes one works and one doesn't. I think I used 1 this time, but the first time I flashed ics i used build 2. Any way thanks. I am checkin out jb now too. cm10 is working great.
You didn't miss the step (to flash Build2 between EH03 & AOKP/CM10), the step was missing (temporarily) from the guide because some have found it to be unnecessary. I had the same bootloop as you when I didn't go through Build2 on the way to AOKP. Seems like the phone attempts to boot normally rather than into recovery to finish the installation of AOKP/CM10, and can't because it is midway through the installation. So did you state you had the problem when flashing CM10 as well? That's interesting, since some can skip going through Build2 and some can't. I thought maybe AOKP required it and CM10 did not... still trying to figure out what is different between phones that require it and those that don't.
Yeah I had it happen on cm10 too. I tried again but only flashed cm10 and no strange looping like I described. But I didn't flash any build before cm10.
Related
I installed Cyanogenmod 7 a week ago, and everything was pretty much working fine.
Randomly today, all 4 of the soft buttons stopped working in the middle of me using my phone. I believe I was checking scores on an NFL app. Regardless, reapplying the CM7 zip didn't fix it. I tried factory reset, wipe cache, wipe dalvik cache. Nothing.
Decided to try to reroot. Reapplied ED05, which is what I did before I installed CM7. Got back to essentially factory... soft buttons still don't work. Reinstalled CM7... took, but soft buttons won't work.
I thought I read somewhere that this is an issue with gapps, but I can't seem to find that page or people discussing it again. Installing gapps again didn't work.
I'm willing to get my phone back to it's most basic level, and even erase the SD card if I need to, but not sure how to clear my phone moreso than my reverting back to ED05.
Thanks for your input guys.
Also, I had reinstalled my apps using Titanium, but not the app data. Again, everything was just fine for a week.
Also, having done a bunch of flashing and what not, I dont' know what happened, but now when I long press the power button, the menu comes up. When I try to use volume up/down to navigate to power off, all I get is volume going up and down
So, i know this thread is sort of dead, but this happened to my fascinate a while back with a version of CM7 mtd (55 maybe?)... I'm fairly convinced that the sensors for the buttons (and the lights for that matter) are completely shot, but I can't really test that. I have flashed back to stock, re-rooted it,and done everything I can think of to fix it.
You probably messed the phone up for good... my advice (if you haven't already done it): get a new phone.
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Will try this out
JJ5150 said:
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Click to expand...
Click to collapse
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Charcaroth said:
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1488976
If you are already on ICS just wipe cache and dalvik cache and flash. If not just flash up to ICS and flash kernel with ROM (same cwm session). You may want to do some reading in that thread first to make sure you get right version for your ROM.
Sent from my SCH-I500 using xda premium
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
As long as you follow the instructions, it doesn't matter what you're coming from. See full instructions here http://forum.xda-developers.com/showthread.php?t=1419102
Notice that for the CWM method, the third instruction is to flash a particular CWM recovery to avoid potential problems. There are instructions on how to flash on the link to it.
n125 said:
I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
Click to expand...
Click to collapse
Easy enough upgrade path
If you are worried about doing this, flash the ODIN "resurrector" CM9 package - it should sort out wiping and everything else for you.
If you want to do it via zip, put the zip file on the SD, do a nandroid backup, wipe data and cache, then flash the zip and latest ICS gapps.
I don't think you'll have any issues with installing CM9 using that CWM. If you do, ODIN flash latest Siyah Kernel. Go to recovery and flash CM from there and you'll be fine
Thanks for the help guys. I went with the CM9 Odin Resurrection method and then updated to the latest nightly (20120511) with CWM.
I'm very impressed with what I see so far. I'll have to keep an eye on it, but I am a little worried about the battery life. (Though considering that I am on a nightly build, less than optimal battery life might be expected..)
Also, my signal strength seems to be fluctuating a bit, usually between 3 and 4 bars, although sometimes it will go down to 2 bars. The modem that came with this build is XXLPQ. Is there a better modem that I can try, or is it just a matter of going through all of them? I was on MUGKG2 previously and it was quite stable for me.
I think LPQ must be your earlier Modem which is retained after instlling CM9, if I am not wrong CM9 doesnt contain a modem.
try KE7 modem, I have got a very nice experience with KE7 on ICS roms
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
l330n said:
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
Click to expand...
Click to collapse
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
captemo said:
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
Click to expand...
Click to collapse
Cool, thanks for the tips, ill try them once i get home in the morning from work.
I saw someone recommend twrp 2.6.1.0 (still hangs), at first I had 2.6.3.0 (newest i believe) and still kept hanging on splash
Do you know which uber kernal is the correct one for that rom or is it just the one included in newest pacman rom 4.3?
I may just try out carbon and revolt, seems like more people running those roms. I was messing with some of the color setting in PA and phone locked up on me and it was weird, had like a greenish screen that got brighter and brighter and brighter eventually i just shut it off, it was fine when i restarted. Im not too worried about changing the colors really, i was just tryin it out.