yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mauix:
If you are willing to experiment, now, while the phone is on, take out the battery. Put it back on and try turn it on. If you get stuck in the Cymbaline screen, then you have the partition or whatever problem a bunch of us have/had.

What I had to do was to ODIN back to the JB official release (install recovery, root, yadayada), and then install Embryo 7. I haven't had the bootloop problem for a week, but I haven't been brave enough to pull the battery to see if that in fact fixed my problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
Typically, I go about 5-7 days before the bootloop causes me to reflash.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mistertim:
you shouldn't have to go more than 2 reboots without worrying about a boot loop. generally speaking, if you don't mess with the boot.img, or drop a wakelock on something like the sysui, then you shouldn't boot loop. if it happens consistently you may want to think about odin flashing your phone to stock and flash a count reset and send it back to the NSA, i mean, AT&T, cause you could have corrupted NAND. it happens. my gnote 1 had a corrupted cmos battery, and anytime you removed the battery it would remove EVERYTHING. JTAG a boot img back on and it would do it again.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Decepticaons:
I'm on like day 8 with no boot loop issues. Only thing I have done different so far is not flashing the Orange themed version. I'm still installing my apps 2 per day and doing a backup, but still so far no issues. I'm going to uv later and change the scheduler ave see what that does. But so far no Orange= no crash, which pisses me off btw :mad:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
It's a coincidence.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] revjwb32:
ok quick question i use USBOTG alot on my phone and only 1 flashdrive that i have works with this ROM, not saying its a rom issue just looking for help

will the phone not recognize anything higher than a 8g or is it the way they are formatted?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Datron:
Possible simple fix...

I think thumb drives need to be formatted as FAT32 to work in this scenario. You should be able to right click the drive on your pc, select properties, and see how it is formatted.

-Datron, sent from afar
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] revjwb32:
must be the problem all of mine are NTFS thanks i was afraid that was the issue as i like NTFS for file size restrictions
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RK:
Exfat works too.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] specter07:
You were right I was forced to do a battery pull and now I'm stuck like everyone. Kinda sucks that a lot of rooms are having issues being reliable.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mauix:
I haven't done this, but someone mentioned that when this happened to him, he got into recovery, made a nandroid backup and then restore from it. It worked for him. You can try this before having to install from scratch and set up all your stuff.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
Once u get past the install issues this ROM is quite smooth, and battery is excellent. Due to the preload though u have less room for apps internally, so I moved them all to SD and erased the preload lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
That someone was me. And that trick only worked the first 4-5 times. Last time I had to wipe and restore to a few weeks in the past, couldn't re-flash my "bad" backup. Dunno, something odd going on.

I flashed with TWRP (instead of CWM this time, trying anything to make it work...), on day 6 now, but I'm not pulling my battery to test if it's stable :P.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Bone_Enterprise:
Just to be another statistic I too had the problem that has been mentioned in the past few posts.

It is odd how randomly it can happen as well, for now I have gone to BeanStalk as I can't use this as my daily driver until this issue is fixed if it can be fixed at all.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
I also left the rom and am using fresh and Slim ... I had multiple issues with boot loop upon any restart. I tried multiple versions of CWM and TWRP... to the same results Only thing i did not try was the ODIN back to stock first. This seemed to be completely random as it would work flawlessly for a week or so then it would reboot to arms for ever... :(

was the best rom i've used when it was working i loved it!! I might flash back to see if i can adb/recovery in to get a log... Does anyone know if Embryo creates a new log on reboot? or would i be wasting my time.. Seems a lot of people have the issue but I for one am unsure how to proceed to find the problem, but am willing to help where i can.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ctalcant:
I have used this ROM without issues or reboots. Coming from multiple ROMs and never had any bootloops either. I've switched back and forth from CM to embryo with no issues.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] hellfreezover:
Me too, from may 12, never had a reboot and I was using the phone for more than 2weeks without restarting, until it started to lag... then rebooted and now back to normal :)

Greatest Rom I used so far

Thank you mohan
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
Just because you guys had no issues means nothing.

I used this ROM since release with very few issues. BUT- once it stopped booting NOTHING would fix it. Clean install, stock kernel, etc. I don't keep many apps on here either.. I have a tablet for that.

I had no issues for a long time but once I started having issues I had to use a different ROM.

Edit: not knocking mohan BTW. I don't have skills like his! If he were around still I'd be glad to help troubleshoot
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mohan_kr:
Yeah..summer and work..not a good combo for deving :).

I need definitely more info, as like it's almost 5 weeks now, that I have not touched my install..Although I don't pull my battery as it is fortified in a otter box..

I need more info (obviously a pull of /data/log from recovery, before you blow it away would be nice, i.e. zip it up)..Also:

- What lockscreen type are you using?

- Are you moving from AOSP type roms and embryo or any TW rom for that matter)? Just speculating here...

Obviously, I am waiting to hit this scenario..but not there yet..which means I need more data about the bootloop issues...All you have to do is:

$ adb reboot recovery

in recovery

mount data

and then

adb pull /data/log
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] veekay:
Just wanted to say I love the build, fav out of the 10 or so I have tried. Looking forward to seeing what comes from 4.2.2 eventually.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
Apologies as i haven't run the rom in a bit. I blew away my install and went to cm for a while since i needed tethering for a job (I'm a contractor).

My setup WAS: default lockscreen. I was coming from AOSP..

I've been crazy busy myself so as soon as i have a moment I'll do a clean install and manual restore of apps. I really love this rom and greatly prefer this setup to embryo 6.

If ANYONE ELSE can provide this data- please do so since anything we post without a log is just useless complaining. (My previous post included! Lol) :D

--

Sent from my mind to your screen.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
I am flashing a clean install now and will attempt to recreate the problem. I will be coming from TW this time... last few times i came from Slim bean.. I have a work phone...iPhone.. but they do pay for tethering lol...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
well that didnt take long... to reproduce it for me..

All i did to phone was clean install.

update SU..

Update Google play... and its apps...

Changed a few sound settings (hate the touch sound)

Soft reboot Things went fine

After reboot i used ROM customizer to uninstall G Books and G Magazines

Disabled Sound on Boot and on Shutdown.

Opened camera..and a few other apps

checked voicemail..

soft reboot

Things are going so great....:D no.....

did a battery pull... Never made it past boot splash screen.

here are the logs from ADB. I zipped them all up just incase they are needed as its not my specialty i'm going to read them more but i'm no dev...:confused::confused::confused:

https://copy.com/UbjpH23gaeuN
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
I'm one of the people with getting stuck at the cymbaline screen. I'm on day 7 now, which is the longest I've went, so I expect getting a bootloop any day now...

To answer your questions in the meantime:

I'm using the AOSP lockscreen, pattern lock security (if it matters)

I'm not moving from AOSP type ROM's. Before Embryo 7 I was on Embryo 6-6.11, and before that on seanscreamz ICS TW builds.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Bone_Enterprise:
If I can deal with a non booting phone again as it inevitability will happen, I will attempt to extract a log. I was unaware on how to do that at all else I would have pulled one many times now, just need a stable phone as I use it all the time so went to something that provides that for now, may do a nandroid of my current ROM and try it again just to get your log(s) however.

I am in the same boat as skyrockets as far as ROM history and coincidentally the lock screen setup as well.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] treadlightly:
Strangely enough my setup just died this morning. I have been on E7 since it's release, love it, and have never had an issue. Updated a few apps last night including Gmail and kerplunk I'm stuck at Cymbaline. I'm using the TW lockscreen. and came from a CM setup

I'll try to pull a log tonight for you Mohan. - thanks for the continued support.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mohan_kr:
Thanks..So I got two logs from two users. And one of the first thing I noticed is both of them have two different kernel versions?

- On one of them it is stock

- on the other it is Cymbaline 3.3

This is definitely not helping :). I am not even sure how this is possible, I need people to follow the install instructions *exactly* and then don't change or install kernels and reproduce the problem..

Either there is some issue with recovery or people are dirty flashing..Dirty flashin WILL NOT WORK..to repeat..Dirty flashing WILL NOT WORK..if you need to wipe /system, /data and /cache..
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
I did not dirty flash, clean as a whistle with no apps installed other than included in ROM, I will reflash again and get a screen shot of Kernal page...then I will flash Cymbline latest... to try to assist further in deduction of problem. :good::good: will also list my CWM version... unsure at the moment...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mohan_kr:
Well don't flash any kernel..since the rom includes the latest cymbaline kernel..And that is what is puzzling..if the ROM flashed correctly, it should say cymbaline..and your logs should say that too..but the logs you provided show the kernel as (stock, 3.0.31) which it definitely should not be...unless the /data was not wiped and it is an old log..
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
Just flashed same file again.. following instructions to the "T"... the only difference is that this time CWM 6.0.2.7 14.4.6 would not see the internal SD card after Full rom Install zip.

So i rebooted into CWM again (recovery to recovery) before flashing Orange theme as per instructions

Then rebooted updated SU...

Changes Zero settings, did not even log into Google. Checked to show the kernal version 3.8 cymbaline...(will get around to pulling screenie from phone)

Soft reboot (granted SU to Rom customizer)

Waited ~10minutes

Battery pull

Suck at boot splash

Pulled "logs" or lack of logs

https://copy.com/DbcR8K81Og3y

:(:(:(

Logs from SD card of phone

https://copy.com/Ep9NGIPvpCpV
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] specter07:
I got past the cymbals screen by holding the power button. See if that works. It did for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
For how long? Long enough to do a hard reboot?

I'll try it next time it gets stuck, thanks.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] specter07:
Yup long enough to hard reboot. I was stuck on the screen and even did a fresh install. For some reason just held the power and let it reboot and phone booted without an issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
Mohan,

I'm a T989 user on Embryo (now back to using 6.10 cymbaline 3.3 for Tmobile.) I get stuck at the cymbaline screen when I was on Embryo 7 and Cymbaline 3.8 kernal for Tmobile. I can try installing Embryo 7 with the Tmobile kernal again. Would the logs from this setup help in anyway?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
I too was stuck at the boot logo when returning to this ROM recently with a fresh install formatting all partitions. What I failed to do that caused that was a factory reset in addition to all other formats and then the install worked just fine past the boot screen.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mohan_kr:
Ok..that log was helpful. But basically, this is what is happening: when you pull the battery the /data partition is getting corrupted. Samsung in JB release have moved a lot of the bootup sequence file to /data (like the tombstones, which used to be in what is now the preload partition). The net result is /data gets mounted read-only and you are basically done at this point. My recommendation is NOT to pull battery on a live system, especially on a TW jb rom. Maybe an fsck (e2fsck) on the partition might help, just like any OS that does during bootup (not sure if it is done in the JB version of TW). So at this point DO NOT PULL BATTERY, DO A LONG PRESS POWER BUTTON or DO A GRACEFULL SHUTDOWN. YOU MUST ALLOW THE SHUTDOWN HOOKS TO BE RUN. Wiping /data at this point will lose all the apps (some of them critical like the weather widgets, email etc), so you will have a slimmed version..

see below..

the root for your internal SDCARD should have the first time flashing log. pastebin that..99% of the time I have seen this (assuming, /system, /data and /cache are wiped correctly) is a bad dowload, check the MD5SUM on the device where you placed the ROM zip file.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
Okay awesome work glad we figured out something! I don't normally pull the battery but it was the fastest way to re create the issues that seem to creep up on me anyway...

I guess i'm to old fashioned and should stop rebooting my phone once a day... lol:cool::cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bradthemarsh:
Now how about those of us who don't battery pull, and always shut down? I was up to almost a week without having to restore a nandroid (using the flashable preload zip never has worked for me). All of the sudden I'm restoring it everyday, and today 4 times throughout the day. The unfortunate thing is that I work in delivery driving, so there's no way to take a logcat while I'm out and about, and I need to get my phone back up and running to communicate with work.

My only theory of what may have caused it for me is that it's a little warmer weather lately, and I use the phone intensively all day. If it got too hot and shut off would that do the same harm as a battery pull? Any suggestions?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Bone_Enterprise:
Also was not pulling my battery, so not sure what was up, when I give this another shot and if by chance there is not a new build by then, and I experience the issues I will be sure to extract logs like mentioned earlier.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jack45:
If it were me I'd select one of two options:

1. Jump off a roof.

2. Save the latest Nandroid and flash another ROM 'til this gets sorted out.

I've been an Embryo fan since version 5, but I'd never put up with the problems you're having.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Texas_Ace:
Did those on 6.10 have these issues with battery pulls corrupting the /data partition?

If I am understanding things correctly, 6.11 moved to the UCMC1 binarys along with embryo 7.

Is it possible that the issue lies in the UCMC1 binary and not so much the JB release?

Just spit balling here.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mohan_kr:
All TW JB ROMS (not sure about AOSP ones), should exhibit this behavior including 6. Basically it will be a hit or miss. I have not dug into whether it is part of Android core changes or not. Anyways, think of it this way, will you keep unplugging your pc? If you do, most probably if running windows you will see the chkdsk, even if you have a journaling file system...It is a fail safe I believe, if you can boot into recovery and do a e2fsck on the partition, it will probably work. Like I said I have not investigated too deeply, it might be doing a e2fsck but if the default is not to take any recovery action it will get mounted read-only which means, your system will NOT boot..

Anyways, I have owned this for almost 2 years and not even had to battery pull even once..not sure who even promoted this nonsense :)..
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Texas_Ace:
Yeah, Thats what I more or less figured as well but didn't seem to see people complaining about these issues with 6.10 or prior releases so was not sure if maybe a pattern could be narrowed down.

While the battery pull is a bit extreme, many have reported issues without doing this. I had a boot loop on 6.11 without a battery pull, it just randomly rebooted for no reason and boot looped. That is what worries me more then the battery pull.

The battery pull is just the fastest way to recreate this issue for most I think as it simulates something going wrong and a random reboot.

Either way, I know just enough about the technical side of android to get into trouble, I will leave it to the experts.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] KaoticEvil:
Just downloaded this after checking out your stock untouched ROM. I'm hoping to fix a radio issue.. So far so good. Great work man! :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
I have not experienced any stuck boot issues on 6.10 and prior. Starting with 6.11 and also on 7, I got stuck on bootloops. I never pulled my battery just long pressed on the power button to force a reboot. Currently I'm on 6.10 still because I had no issue with this build. I might give 7 another shot when I get some time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
Actually doing a long press of the power button creates the same problem for me as pulling the battery.

Gracefully shutting down is the only way I can turn the phone off and not expect a bootloop.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nyarrgh:
I've never done a battery pull on this ROM. However, this does happen to me when I am using my phone as a GPS and my phone overheats and shuts down. Unfortunately, because of this, this happens to me while I am on a long drive, and need my GPS. I would have to restore an old nandroid of 6.10 if this happens and lose any logs.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Texas_Ace:
So this never happens to you with 6.10? Even with a hard reboot?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mauix:
Mohan: We, the ones having this issue, are not pulling the battery out just because. We found that that was an easy way to reproduce the behavior.

Our phones, at some point, reboot themselves and get stuck. One time, my phone was not even being used, it rebooted itself. When I cleaned everything and re-installed the rom, as I was installing my apps it rebooted and got stuck again.

Somebody mentioned to me that going back to stock through Odin and re-do the whole thing again would keep this stable. It's been more than a week and my rom hasn't had the problem. The only app I didn't install this time is better battery stats, so I'm not sure if that has something to do, or coming through the stock rom or all of the above or none of the above, but my phone is stable now. So I'm happy for now :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
That someone was me, and I mohan has confirmed what I suspected all along, partition corruption issues. That explains why I had to go through such a lengthy process to get it to work.

Suffice to say unless u have clean partitions to begin with this issue will only get worse. Restoring a man droid won't help, and recovery doesn't format the partitions well enough. Thus he need for Odin.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] idlestranger:
Hi all hope everyonez doing good.... sorry but I couldnt find the Q & A for embryo 7 so had to post the question here, have been reading that ppl having issues with the rom ...to me I like the rom thanks to mohan and all involved but have a few question if someone can help me with them ... I have done a fresh installation no restores even for my apps but have faced slowness after using it a little thought may be because of alot of apps and I have reduced thwm aswell but it just does not respond for a few seconds and then sometimes a force close or sometimes I have to go to home screen and back n it works ....last nite was just watching a movie on my browser and the same happened and then I got gaps not responding error and alot of force closes eventually I restarted my fone and then it wpuld never start just got stuk at the cymbaline screen waited long time cleared the cache and dalvik rebooted same prblm.... I had to format and fresh install everything sry because of this reason I dont have a log on me (I have one but dont knw if its for the new installation or the prev issue) since I did a new installation I assume it has nothing to do with prev one. Am I the only one who faced this ??? Is it because of a wrong installation but I did follow the steps exactly .....??? Now on the new installation when my fone starts I dont see cymaline logo rather just the embryo animation.

Should a same incident occur what shuld do ???

http://db.tt/5HVAEOqQ
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
It's a shame. Seems like many of us did the same thing.

Installed. Worked awesome for a while and eventually wouldn't boot.

No. I don't have a log cat. Didn't have the time to mess with it.

For me- I can't be very long without a functional phone since I make my money by receiving phone calls... Sooo as soon as this happened I had to install a ROM that booted.

The shame to me is this:

1. Obviously it's the ROM creating the issue. It's a VERY specific issue of not booting.

2. No. I don't have a log cat already.

3. I know this- if many people have the EXACT same issue.. It's an issue. With or without a log cat. Maybe it can't be fixed without the log.... But it IS an issue and treating users like idiots is just wrong.

4. Get humble bro. Ego is winning over OS.

Edit: if it's a corrupted partition for all of us.. What caused it? Doesn't happen on any other ROM. Doesn't happen on embryo 6 or UCMC1

Edit2: i said my 2 cents and stick to it. Anyone who thinks i don't know what I'm talking about doesn't know me. Look around. I've NEVER cried wolf.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] catchjeff:
I get it to load just fine and get past the boot animation. It loads the applications and all. My issue is that I cannot get google play to work. Everytime I go to sign into google play it forcloses on me. Is this due to the ROM or Gapps? I am using Gapps jb 20130301. Is this the right Gapps package to use with this rom?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] robcore:
You dont need to install gapps separately. They come preinstalled because this rom is stock-based.