Database Info

CM10 Alpha 3 Problem?

Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
Click to expand...
Click to collapse
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.

Phizban said:
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Click to expand...
Click to collapse
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.

Droid111 said:
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Click to expand...
Click to collapse
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.

mjwhirly said:
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
Click to expand...
Click to collapse
Thanks for the help. I'm going to try it within the next few days. Right now I have SKY-ICS going fine but I'll definitely try that.
What do the different kernels do?

Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Click to expand...
Click to collapse
I used TWRP and flashed over CM9 with no problems. Did it as an upgrade. Wipe system> install CM10> install gapps> Wipe cache
Several people have reported that TWRP worked for them.

clean rom

Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?

chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.

Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail

chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.

oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...

i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.

What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!

elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running

chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.

Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.

[Q] phone will not boot after installing any kernel

about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks

and to clarify , it was gapps 4.2.2

Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.

If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app

i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .

You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.

actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.

i figured out twrp. never gave it achance. ill see if that does the trick

tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks

Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?

Frustrated! Soft bricked?

I was running LiquidSmooth 2.9. Decided to try the latest KK nightly. Downloaded everything, made a backup, etc. Went to flash and it said (status 7) error. Tried again, same thing. Decided to update to the latest TWRP and try again. Same error. Tried one more time and it worked. After the rom was loaded I immediately noticed that the rom was not stable enough for a daily driver.
Booted into recovery and tried to restore to my previous backup. For whatever ready TWRP could not locate the backup. I tried to move the back up for a while but it wouldn't move to the correct folder. I said screw it I will just download the Liquid Smooth 2.37 which was the latest official release and just reflash. Downloaded everything, then flashed it. Everything set successful, gaps and rom, but now it wont get past the splash screen. I have reflashed like 5 times now all without issue but stuck at splash screen. I can get into recovery fine.
What is my next step to revert back to my previous backup or reflash to a working rom? Any help would be greatly appreciated.

Odin my friend
Sent from my SCH-I535 using Tapatalk

I had the same problem on kk i had to do a factory reset wipe catche dalvik then flash liquid smooth kk pa gapps im working fine. Honestly my own opinion i prefer liquid 2.37 over kk. I read couple post ppl had to get the latest cwm recovery to flash KK roms

Were you able to revert back to 2.37? I'm stuck here in limbo at the moment.

1967ls2 said:
Were you able to revert back to 2.37? I'm stuck here in limbo at the moment.
Click to expand...
Click to collapse
Yes after couple tries I just factory reset flashed rom
i did these steps
factory reset install rom 2.9 or 2.37 then after all set up i went bck to recovery flashed a backup file I had of 2.37

twistedillutions said:
Yes after couple tries I just factory reset flashed rom
i did these steps
factory reset install rom 2.9 or 2.37 then after all set up i went bck to recovery flashed a backup file I had of 2.37
Click to expand...
Click to collapse
what recovery are you using? TWRP or CWM?
I'm getting no where.

1967ls2 said:
what recovery are you using? TWRP or CWM?
I'm getting no where.
Click to expand...
Click to collapse
Twrp

cm-11-20140227-NIGHTLY-falcon --- Bootloop issue after OTA-Update

Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.

Did you try to wipe cache and dalvic cache in CWM?

Dizzyrul3z said:
Did you try to wipe cache and dalvic cache in CWM?
Click to expand...
Click to collapse
No. I just make a dirty flash over the Cyanogemod-Updater under Settings.

So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.

Volkan66 said:
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Click to expand...
Click to collapse
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.

Volkan66 said:
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Click to expand...
Click to collapse
What recovery do you have installed?

january waower
kieranc said:
What recovery do you have installed?
Click to expand...
Click to collapse
I have installed ClockworkMod-Recovery (CWM): cwm-6.0.4.6
I don't have any problems with the recovery but with the Nightly Update from 27th February.
I can't understand how the cm-11-20140227-NIGHTLY-falcon can get official, when a lots of people have the same problem: bootloops.

=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I totally agree with you. I won't do a full format of the internal card. Just waiting for the next Nightly in the hope that dhacker improves this issue.
Do you have also problems with GMAIL. After each restart GMAIL is lost. I must install it each time new.

I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....

kieranc said:
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
Click to expand...
Click to collapse
So, I installed by mfastboot for now the newest stock rom 4.4.2 DE, updated to the latest release and rooted.
Maybe I'll flash also kernel to faux's release. Very strange issue. I flashed CM several times and today's issue was the first time.

=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I've just wiped /data/media ("sdcard") and have successfully installed and booted feb 27th build. Strange problem but that looks like the solution....

I was at the 0224 build and flawlessly updated to the 0227 build... no issue so far. i am using twrp...

Hey guys,
i have flashed the newest Nightly cm-11-20140228-NIGHTLY-falcon.zip today and everything was solved. No bootloops or lost of apps.
With pink kernel the system rocks. This is awesome. Thanks to dhacker29, pinkflozd, faux123, razrqcom-dev-team :good::good::good:

Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11

hydromän said:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
Click to expand...
Click to collapse
I can confirm your sound problem.
I am using the nightly version 0228 and pink kernel 0228 and would recommend you to use the pink kernel because you will feel the boost in performance.
Yes the battery will drain a little bit more than on stock-cm but it is worth it. I can use my phone with pink kernel two days long without charging it.

So I will try Again Pink Kernel =).. I hope the Sound in Call Problem get fixed soon
Android-CM11

I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11

hydromän said:
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
Click to expand...
Click to collapse
Yeah this version of pink kernel is great. I hope this kernel will leave soon the beta-stadium and will get official.

0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app

tohigh said:
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
Please flash the TWRP 2.6.3.3 recovery first then flash the newest nightly cm-11-20140304-NIGHTLY-falcon.zip .
I am using 0303-NIGHTLY with TWRP 2.6.3.3 and don't have such issues like bootloop again.
But it is very important to flash the recovery first, then flash cm-11-20140304-NIGHTLY-falcon.zip with Cyanogenmod-Updater under settings.
If you do otherwise flash cm first you will encounter the same problem.