yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] catchjeff:
Oh thanks.

---------- Post added at 12:58 PM ---------- Previous post was at 12:25 PM ----------

Anyone else having trouble with titanium backup on E7.

I have everything loaded and running nice but TB get hung up on asking for root rights. Any suggestions? I uninstalled and reinstalled but getting same all the time.

Thanks Mohan for this ROM

Fixed my issue had to update SU
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] robcore:
Guys,

All feelings aside, if you are interested in supporting this independent development project, posting logs in the format required by its dev will be the only way to realistically make any significant impact on its functionality.

Everything else clutters up the thread and breeds resentment/confusion in the community as opposed to a constructive development environment.

Please move your unrelated conversations elsewhere.

Rob
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mauix:
Use one of these. They are discrete, and don't look messy: http://www.tetrax.com/us/products/iphone-ipod/tetrax-xway
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Naddict:
Thread cleaned

Let's keep this on topic, post only contributory material and assist with development, or move on.

Thanks for adhering to the rules.

Now, back to development.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] specter07:
I have confirmed my theory.

If you get boot loop from a battery pull or a freeze holding the power button to hard restart will not boot the phone. It did for me once but I have tested it and hasn't worked.

What does work is if you do a fresh install of the rom and get stuck on the bootloop, press and hold the power for a hard reset and the phone will boot up normal.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
It will boot again but on the next boot it will stuck. Then works again. It alternates a few times until it is stuck for good.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] specter07:
But at least it's a small solution to this huge issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kinvid:
I have two Skyrockets on embryo rom, mines on version 7 and the other one, my wife's, is on version 6.11. My wife got stuck once on the samsung logo (version 6.11), tried the "hold power button" and it booted fine, never had that problem..as of yet..don't wanna try to pull her battery out lol

On the other hand, Skyrocket that's on embryo 7 has gotten stuck on cymbaline several times...randomly.(i don't have to pull the battery for this to happen!)..so I have tried holding the power button to fix it, a no go. Does not work. I had to re-flash, reinstall apps, customize settings, etc, annoying...anyways I've come to conclusion that some ppl are lucky, some aren't lol Those who aren't should go with asop for the time being! as i did.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] specter07:
Holding the power will only work if your stuck after a fresh install.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Decepticaons:
3 weeks, no fc or forced restarts that cause the boot loop of death. I power of my phone at night every night for 3-7 hrs depending on how much sleep I get. I use an app to clean my caches and remove parts of old unused files. Other than that I haven't used the Orange theme which I'm told isn't related. Off I get stuck I'll chime in, but after flashing twice my problem seems to have gone away.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] suyashc:
Guys can i use different radio with this rom?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
ITS like the 2nd Item on the OP (original post)

you do have to read a little bit....UNDER THE BIG "IMPORTANT" BUTTON

- Currently, ONLY JB RADIOS (UCLK4, UCLL3, UXUMA7 or UCMC1) supported. I will provide add-on for other radios (ICS, GB) later.

-Please read the entire post[/B]. It is IMPORTANT you follow the instructions (including checking always md5sum) and NOT invent your own procedures.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RK:
[MENTION=4565578]mohan_kr[/MENTION], Any reason I should get fc on "com.android.phone" and a non functional mobile data after a factory reset?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Datron:
I get the same when I insert SIM cards that are expired. Makes sense since they're expired.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
Someone else said in previous posts that 7 worked better after an ODIN back to stock.. So i gave that a try.. After flashing I got that same FC close over and over.. SO i reflashed twice the next time. It cleared the FC but did not fix the corrupt partition problem for me as a single battery pull 3 hours later and that was it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RK:
Well.. mine is not expired..

---------- Post added at 02:24 PM ---------- Previous post was at 02:23 PM ----------

I dont believe I have the same issue. This happens to me only when I do a factory reset on a working installation.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Datron:
Sorry. I misread your post. After a factory reset did you go to mobile network settings and verify your APN settings are accurate?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] danaholic86:
Had to go off this ROM.... Wouldn't boot sometimes if the battery died.... stuck on cymbaline screen
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
I literally odin flashed 4.0.4, booted, rebooted to recovery, factory reset, Odin 4.0.4 again, boot, reboot to recovery and factory reset, odin 2.3.5, boot, reboot to recovery factory reset. Then Odin twrp, erase system, data, cache dalvik 3x then flash embryo to solve the corrupt partition issue.

Extreme I know, but it worked and running almost two weeks strong with multiple power offs, so I'm happy. That being said I don't do battery pulls, as holding power button achieves same result
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
That's the key I think. Battery died or pulled seems to create the issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
That is the problem for me... As I need my phone to work and I do have an extra battery just for this type situation...I try to avoid being the guy that has to plug in my phone every where I go....I was at the airport last week and spoke with a guy that was charging his phone in the bathroom' it was the only plug available I guess but screw that as it is not for me.

I travel a lot so I do spend plenty of time fiddling around on phone if I can't turn the phone off then I can't use the ROM... My n7 is awesome but I try to save that for the flights... :)

On a development note could this be a place to start looking? I'll dig around and see what I can learn/discover
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpuckett:
I've been using this for about 2 weeks straight with zero issues. Today I updated to the Galaxy s4. While there I mentioned I had a micro sd card. Before I realized what the guy was doing, he pulled my battery to take out the sd card. Guess what happened, I got stuck at the cymbaline screen. Fortunately, I had anandroid backup to restore from 9 days ago, so I was fine.

Anyway, all that to say, yes this ROM is awesome but don't pull the battery.

Thanks for the awesome ROM! I will be looking for an EMBRYO equivalent for the S4.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] specter07:
Why would he pull the battery out to remove the SD card?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpuckett:
That's what I was trying to out.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RK:
Yes the APN settings are blank but even then I add a new APN manually I still have no data and when I reboot I still get process phone force close
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seniar:
Never had a problem with this Rom... then I dropped my phone and the battery fell out... you know where this is going lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
Just curious-

I NEVER pulled the battery on the rom not would i ever for any reason. I still want to come back to this rom and for me anecdotal evidence can sometimes be enough.

That being said- has anyone who HASN'T had an issue let the battery run down to 0% and shut itself off? I think that's what happened to me.

After that is when it wouldn't get past the kernel boot and corruption blah blah.

--

Sent from my mind to your screen.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] EQ811977:
I'll let you know in 5%. Doing all I can to kill it now.

Edit-Well...it's not getting passed the kernel boot. 8 days this was on one of my rockets without a problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
I have issues, and have let me phone run to 0% once or twice (accidentally) and it did NOT bootloop.

Only when I pull the battery, hold the power button for 10 seconds or something crashes and it restarts on it's own.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RK:
[MENTION=4565578]mohan_kr[/MENTION] if you are still around, I was building my own ROM using the UCMC1 base and your stock modded kernel. I encountered the exact same stuck on kernel boot screen issue when I added an aosp browser.apk to the ROM. It was perfectly repeatable. Add browser.apk to /system in the zip, flash reboot and battery pull -> stuck on kernel boot. Remove the browser.apk from the zip, flash and battery pull -> everything OK. Just thought I'd let you know.

I know t you don't have aosp browser in embryo but it could be another rogue app.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] EQ811977:
I just think everyone has different issues on how this problem occurs. After 8 days of running this not one freeze..rr..crash..nothing of that sort. Battery goes dead...charged it a few minutes..turned it on and it stuck on the cymbaline screen. Only thing I can think of that starts these issues is user error.

Edit-Going to flash again..with same setup and apps and let the battery die to see if it happens again. Let you know what happens as soon as I know what happens.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
It's definitely not user error lol, it happened to me several times, and I'm by no means a noob
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
Did anyone try using an earlier version of the cymbaline kernel and see if it get stuck? I'm wondering could it be a kernel issue instead of the rom.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
Well earlier versions of the kernel aren't ucmc1 based. Since this issue didnt occur on <=6.10 which is based on ucla4 I'm going to assume it has to do with binary commits made by Samsung after, to the ROM and/or kernel.

I suppose flashing the 6.10 kernel wouldn't hurt. Anyone wanna extract it and give it a try?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] EQ811977:
Let me rephrase my user error comment. Pulling the battery is user error in my opinion. All the crashes..rr's..freezes that lead to getting stuck at the cymbaline screen because the battery was pulled or the power button was held..user error. If flashed correctly..should not have any of these problems. However, I agree with many people and it is quite obvious that there is a big problem. If I offended anyone with my user error comment I apologize.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Texas_Ace:
I think this should get a closer look. Best hypothesis I have seen posted yet.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
Wrong.

I've had days where my phone would crash multiple times (on it's own, no battery pull, etc.). Then I've had weeks where it would work with no problems at all.

Do you know why people pull the battery? It's the quickest way to reproduce the problem. It's not to complain about some side effect of some random action that leads to an avoidable problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ddxv:
I've also had this problem. Usually happens randomly, not directly connected to a battery pull or the phone dying, just kinda randomly tries to reboot and then hangs.

I've since tried moving on to some of the new CM 10.1 mods, but none will install (Status 7 error), is that related this?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrfeuss:
I'm pretty sure you have to update your recovery.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
I agree with you, I pulled the battery numerous times in my previous posts reproducing the problem to get logs for Mohan. I personally don't pull the battery... pressing the power button is easier than taking the back off anyway lol.

Restarting the phone, via proper ways is not user error.. nor is letting the battery die.. these things happen and the phone should not bork itself because of it.

If my computer OS died every time i lost power I would not use it.. would you?

---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------

Make sure you downloaded the correct rom..

if you are using CM 10.1.0 ensure that it is the "skyrocket" version.

Status 7 is i think the assert match failure meaning that the ROM updater script is checking to ensure the device listed in the ROM matches the device your trying to flash.

If not you can delete the assert text from the updater script in the rom. there is a thread on it somewhere.....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ddxv:
[/QUOTE]

Make sure you downloaded the correct rom..

if you are using CM 10.1.0 ensure that it is the "skyrocket" version.

Status 7 is i think the assert match failure meaning that the ROM updater script is checking to ensure the device listed in the ROM matches the device your trying to flash.

If not you can delete the assert text from the updater script in the rom. there is a thread on it somewhere.....[/QUOTE]

I "succesfully" went back to embryo 6.8 haha.

I tried removing the asserts on the cm roms but it dint fix it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] xcrazydx:
You shouldn't be flashing anything.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
Okay...I just flashed Embryo 7 again with an earlier version of the cymbaline kernal. While the screen is on, I pulled the battery 4 times and all 4 times the phone booted up no problem. I only restored a few apps to get the phone going. So far so good. However, I'm using a T989 phone so I flashed a Tmobile cymbaline 3.3 kernal instead of the Skyrocket version. I think Mohan created the the Skyrocket and Tmobile kernal the same way. Maybe any cymbaline kernal before 3.8 might work. I will pull the battery a few more times to attempt to create a boot loop...but so far no problem.

Edit: I pulled the battery a few more times and forced shut down with the power button. The phone still booted up fine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jack45:
It's reasonable to conclude that Mohan has left the building, especially with the S4 in his sight. He has interpreted whatever useful logs he's received and has offered his comments, most recently about a week ago.

If you're having repeated problems with the ROM, why are you staying with it? If I had the issues that some have reported (ad nauseum), I would move on to another ROM. I would

never

put up with what some of you are tolerating. Know when to fold.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
3.3 doesn't have BLN, right?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
That's correct. I don't use BLN so it doesn't matter for me. I've tried all I could to reproduce the boot loop today but so far the phone still boots. I'm restoring the apps and some data now. I'll do a few more battery pulls to see if it get stuck after restoring apps. Who knows...maybe sometime in the future I'll get stuck on boot again.

---------- Post added at 04:55 PM ---------- Previous post was at 04:49 PM ----------

I believe people like me put up with the issue we are having because we like this rom very much. We hope that Mohan will come up with a fix and make it even better. By chatting here we are keeping the thread alive and hope that we'll get an update/fix in the future. I'm on Tmobile and I gave up using other roms with the wifi-calling feature for this rom. Embryo is that good and attractive.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jack45:
How could anyone like a ROM that causes freezes, crashes, randomly reboots, and experiences boot loops? It ceases to be a challenge after a while (and I love challenges) and evolves into sheer madness. Waiting for an update? This has been going on for so long that if a fix was doable, it would have already been done. Mohan may prove me wrong and have a final fling at preventing the maladies, and if he does, good for those having the problems. But in the meanwhile, there's enough suffering going around to make me wonder whether some aren't happy unless they aren't happy.

As for me, the ROM's been rock solid. But I'm still waiting to wake up tall and handsome. And waiting. And waiting.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wildnbig:
I changed kernel to cymbaline RD04-3.5 and pulled battery 8 times and no trouble so far.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
Any still flashing the kernels want to try the stock kernel in the op? I'll give it a shot later on tonight if not done...

If the stock kernel works then we know the cause...if not we can start looking at the mods to the stock kernel as cause for the troubles.. :)

thanks everyone for trying!!! The post above me said it right, we will go the extra step to keep our fav ROM alive and trouble free.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
No it doesnt

But 3.5 does. It was the latest kernel version in 6.11 I believe.

What i believe it boils down to is potentially the ramdisk and the way mohan set it up on 3.8. As a precaution/preventative measure I'm going to flash 3.5.

Anyone else wanna flash 3.3/3.5 and test? I use my phone w/ exchange for work so I can't risk the time to restore, but if someone can reproduce the "cymbaline logo hang" and then flash 3.5 to see if it will boot after that would potentially be quite useful, and a solution to the problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seniar:
Reinstalled with 3.3 kernel and battery pull and holding power no longer boot loop the phone
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
I think we found ourselves a temporary solution to the problem. For those who are getting boot loops, please try using an earlier version of cymbaline kernal. If more people are getting positive results using this method, it may help Mohan pinpoint it down.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
i'm booting now with the stock kernel (modded ramdisk) i'm going to see if that has the issue.. if it does boot loop i will then flash 3.5 to see if it fixes it.

Flashed with STOCK OP kernel... It is not a "fix" but it is better....

On a Hard reboot(batt pull) Kernel Loop (samsung screen) Soft reboot fixes it.

On a Soft reboot(hold power) Kernel Loop(samsung scrren) soft reboot fixes it.

I did each scenario a 3 times..each with same result, I think this is solid material that something in the modded Ramdisk and in the Cymbaline 3.8 kernel has a typo :) somewhere

I will now flash cymbaline 3.5 and retry my scenarios .. staytuned.. lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
I just let my phone battery die, unintentionally actually. Its a good thing I did flash 3.5 before this happened as otherwise I would have had to do a full restore, a major pain. 3.5 booted up no problem, no kernel hang
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RK:
I have the exact same experience on stock modded kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] skyrockets:
Same experience on 3.5
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
okay after plenty of experimentation last night.. it seems to me that the biggest problem is cymbaline 3.8...

With the stock kernel i get kernel hangs or loops but its clear able with a soft reboot. Seems a 2nd reboot will clear any leftover hangups.

I did flash 3.5 and I got mixed results... when running my reboots and battery pulls.. it wasn't as consistent as the first test, but I think this was due to the problems caused by the "dirty" flash of RD04 3.5.

I am currently loading up EMB 7.0 with Stock kernel and going to run it for a few days and see what i get... I'm going to dig around and see if i can see any differences in the kernels... from a pure stock.. maybe compare the 3.5 with 3.8 again I'm no dev.. GOOGLE will be my friend.. I might try to see if i can get Team Rook to have a peek at it to see if there is something glaringly easy that was missed. ( Not trying to knock Mohan here its way easier than we think, Hell i can't even find mispelled words much less find syntax errors or simple thing like a ; or a space misaligned)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] daihung1:
I also get similar results using cymbaline 3.5. 3.8 I get completely stuck. It seems to me that only 3.3 is working without an issue. Thanks for all the testing. Please keep us inform of what you find.

Thanks.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tweakecho:
well the stock kernel died after af few hours of use. So i then tried it with 3.5 RD04 and it also had Issues once you actually started using it also for me...worst part is they were both random Reboots about an hour into each test. but boot looped on random reboot before that i had shutdown and did battery pulls with positive results.

Next piece of the puzzle.. went to flash 3.3 following your advice.. TWRP could not wipe the davlik cache...it could not wipe it because it could not find it.. so that may be an important part of the issues if the cache is corrupted then of course the phone will reboot and loop.

I had to reformat the entire phone to fix it.. currently booting on emb 7.0 cymbaline 3.3
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] catchjeff:
WOW, I have been running this ROM for almost a week now without a single problem. No FC no RR and yes I even let my battery die on me and even pulled out the battery and was able to reboot the phone correctly. This is one smooth rom one of the best Mr Mohan has built in my opinion.

I did come from embryo 6.11 and did a dirty flash when I went to 7 then I wiped the phone and did a factory reset and it booted just fine.

Maybe you should flash the correct radio first then reboot into recovery and flash the roms. Tha is what I did and dod not know why this would be an issue.

I did one time flash this rom with a radio not listed and got stuck on bootloop. Once I changed the radio it went just fine.

Good luck
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rkub:
So where are you guys dl'ing the 3.5 kernel? Can someone post here?

Thanks for any assistance.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
To elaborate- just wait.

If you had read the thread you will see many started with the same snide remarks. Just wait :D

I thought everyone was being stupid at first too.......

--

Sent from my mind to your screen.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
I'm guessing u undervolted too much. Can't think of another reason for that RR. Especially for a stable ROM built off stock.

Also I disagree, 3.5 has proven stable so far. I much rather recommend it over 3.3. 3.5 has compatible binaries and is closer to ucmc1/(it is really) whereas 3.3 is based off the older ucla4, while the ROM itself is newer. This should be avoided in my opinion, for countless reasons.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nbnion:
As far as you can tell still stable on 3.5? No more headaches do far?

thanks
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] soupysoup:
I've flashed and run this rom on my t989 t mobile version and never run into this issue, whether my battery died, or rebooting it's always been good, I only got stuck at splash screen once and I just did a manual reboot by holding volume and power buttons and it booted right up, idky so many ppl face this issue
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nucl3archick3n:
I've been running this rom for a month and today was the first day I have experienced many random reboots. I have installed nothing new. Any ideas?