I don't really like posyting questions like this, but I was hoping to get CM11 installed on this device but it just won't boot. I've tried one of the unofficial nightlies, and the official M1 release. Is anyone else having this problem? It's just stuck at the bootlogo with the spinning arrow. Yes, I have wiped data, cache and dalvik. I flashed through CWM, too.
EDIT: Got it working by flashing with TWRP.
abtekk said:
I don't really like posyting questions like this, but I was hoping to get CM11 installed on this device but it just won't boot. I've tried one of the unofficial nightlies, and the official M1 release. Is anyone else having this problem? It's just stuck at the bootlogo with the spinning arrow. Yes, I have wiped data, cache and dalvik. I flashed through CWM, too.
EDIT: Got it working by flashing with TWRP.
Click to expand...
Click to collapse
Thanks for the update - i'm having issues with this as well.
Related
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.
I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.
Athanasius said:
I've been using CM and updating nightlys about once per week. Yesterday I updated to 10.1 but when I did Gapp didn't work (of course) I thought. No big deal, I'll just revert back to a 10.0 build... then something went horribly wrong. The phone stuck on the CM splash/boot screen.
I've tried deleteing cache and dalvik cache, Flashing the stable 10.0 build, flashing the 10.1 nightly and gapps... nothing has worked. I'm at a loss as to what to do now.
I should note that i'm using CWM.
Currently i've restored to the last stock build which ate battery like it was candy (ironic since it's jelly bean... carnivore) and this works... but it still won't boot if I try to flash CM. Any help explaining what has happened or how to fix it would be appreciated.
Click to expand...
Click to collapse
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it
mypat said:
Don't flash 10.1 over 10.0 if you do so.
Wipe data factory reset / format boot also format system with cwm later make fresh install. flash gapps right after you flash the rom don't let it boot without it
Click to expand...
Click to collapse
I can't tell you exactly what I did but it seems to be working... somehow a factory reset resulted in CM10.0 and gapps installed correctly... i'm still scratching my head but i'm happy enough.
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?
sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do
I have the original ASUS Transformer and have been having issues. I have tried a 4.3.1 rom and a couple 4.2.2 ROMs. All have the same problem. For some reason after flashing the ROM and the proper GAPPS, the talet cannot be restarted. The ASUS screen comes up and then either a black screen will popup and the tablet will reboot, or the tablet will be stuck in a loop on the ROMs logo screen.
Not sure what is going on. Ideas?
Thanks
Did you wipe the system and data partitions be ore flashing?
frederuco said:
Did you wipe the system and data partitions be ore flashing?
Click to expand...
Click to collapse
Yes, always.
What recovery are you using?
frederuco said:
What recovery are you using?
Click to expand...
Click to collapse
TWRP 2.3.2.3. Latest fro GooManager. I tried the unofficial newer build in the Dev forums...but I could no flash CM 10.2 so had to go to the older official version
Strange...
tell me about it
CM 10 at 4.2.1 seems to be working fine. Odd but it will do. My mom's tablet and she wont know the difference.
By chance did you *not* format after you did the wipe?
I just flashed the pacman nightly over cm11 using philz recovery. and my phone keeps trying to boot up. I get the moto logo for a few seconds then it goes blank and comes back up.
not sure where to begin fixing this. Ive tried to get back into recovery but cant.
any help would be appreciated
oscar the grouch said:
I just flashed the pacman nightly over cm11 using philz recovery. and my phone keeps trying to boot up. I get the moto logo for a few seconds then it goes blank and comes back up.
not sure where to begin fixing this. Ive tried to get back into recovery but cant.
any help would be appreciated
Click to expand...
Click to collapse
You dirty flashed it over CM11? You didn't wipe system, data, cache and dalvik? I always do that, even when I'm flashing an AOSP-based ROM over another AOSP-based ROM.
The only time I won't do this is if I'm flashing say CM11 over CM11.
If you dirty flashed, that might be your problem, but I don't know for sure as I don't use PacMan ROM.
I didn't dirty flash. Cm11 was on there before. I used philz wipe forfor new rom like I always do.
I can get into the fastboot menu. Is there something I can do there to reflash cm11?
oscar the grouch said:
I didn't dirty flash. Cm11 was on there before. I used philz wipe forfor new rom like I always do.
I can get into the fastboot menu. Is there something I can do there to reflash cm11?
Click to expand...
Click to collapse
Not sure then. I always use TWRP to wipe and flash. Could be an issue with the ROM itself or you got a bad download. You might want to try and download the ROM again to ensure it wasn't a bad download.
figured it out. must have had something happen to the recovery file.
in fast boot i flashed a new recovery image and was able to boot into recovery.
Maybe you have the JB bootloader and you flashed a KitKat bootloader based CM11 build... That could explain why your phone is not booting properly.
If nothing works you just can flash a STOCK FIRMWARE to begin again.
The phone has stock kitkat. How can I confirm?
joel_sinbad said:
Maybe you have the JB bootloader and you flashed a KitKat bootloader based CM11 build... That could explain why your phone is not booting properly.
Click to expand...
Click to collapse
That's a no-go. You won't be able to flash a KK-based ROM on a system with a JB Bootloader. The device will abort the installation immediately with a friendly reminder. At least the XT926. Been there, tried that.
^ agree. My atrix HD has a jbbl and I can Confirm this