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.

[Q] Stuck on bootscreen after flashing [JB]Unoffical MIUI 2.9.14 Skyrocket[PORT]

Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!

shentheory said:
Hello Pros! First post, semi-noob here.
I tried flashing the newest [JB][CM10Based]Unoffical MIUI 2.9.14 Skyrocket 9/14/12[PORT] today. I followed all instructions; I wiped wiped wiped, factory and Dalvik, and flashed the kernel.
But I am always stuck on the MIUI bootscreen, and can never fully load up the ROM. I've tried wiping and re-flashing several times, to no avail. I have not had any problems flashing roms before this. Any help or ideas of what causes this would be greatly appreciated.
Thanks so much!
Click to expand...
Click to collapse
Couple things.... did u format data/system? Also what recovery are u using?

Deliberate said:
Couple things.... did u format data/system? Also what recovery are u using?
Click to expand...
Click to collapse
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!

shentheory said:
Yes, I formatted both system and data. And I'm using the recovery that was recommended in the rom thread, Sk8er's Cwm v13.
Thanks for your reply!
Click to expand...
Click to collapse
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!

Deliberate said:
Try reflashing. But when u get into recovery go to extras/darkside tool. And click on the super wipe(idr what's its called but there's only two options.) When that's done factory reset format data/system 3x if u want.( Couldn't hurt) then flash ROM! All should be good... if not keep this thread open. Lol and well try something else. But hopefully that works. Good luck!
Click to expand...
Click to collapse
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?

shentheory said:
Thanks for the steps, but unfortunately I'm still staring at this dang MIUI bootscreen...:crying:
I ran the darkside superwipe, factory reset 3x, and formatted both data/system 3x, flashed the rom, and I'm still staring at this dang MIUI bootscreen... waaa waaaaaaa, what's the DEALIO?
Click to expand...
Click to collapse
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.

Can you boot into recovery or not? If you can, just flash the rom. If you can't, yank the battery, replace it. Then, hold down both volume buttons, the press the power button, release all the buttons, you should be able to get into recovery.

Deliberate said:
Really? Damn. Are u on the latest recovery? If not try flashing the newest. Then do the steps again in my last post. Can't believe your having all these troubles!
Oh also u could try fixing permissions. After doing all the wipes and after flashing. Go to dark side tools again and do the cashe wipe! Then go back to advanced and fix permissions again.
Click to expand...
Click to collapse
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!

You'll have to use odin, and reroot your phone.

Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.

shentheory said:
Wow, still stuck on the boot screen even after the darkside cache wipe. I flashed CWMR Touch v6.0.1.3 by sk8erwitskil which is the newest CWM recovery as far as I believe, and the recommended recovery for this ROM. I EVEN flashed TWRP 2.2 just for the heck of it and flashed MIUI with that and still the same result; stuck on bootscreen. So I'm pretty sure it's not the recovery.
I did a darkside superwipe, and a darkside cache wipe, along with factory reset & format data/system 3x. The rom installs in recovery just fine. It's just once i reboot, i get the MIUI splash loading screen indefinitely. I'm not sure what could be causing this since I do all the important wipes (plus the darkside wipes now) each time. I think I have BAD LUCK!
Click to expand...
Click to collapse
I had the same problem, but while my phone was stuck on the MIUI boot screen i pulled the batter, got into recovery again and simply did a factory data reset just once and then it booted up, but my issue is that i get no data at all no mater what version of MIUI I try to flash.

mimart7 said:
You'll have to use odin, and reroot your phone.
Click to expand...
Click to collapse
Even if my stock rom is already rooted? I'm not against trying it, I'm just curious to how that could affect it. Thanks for your help!
hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
I will do this and update when I do, Thanks for your help!

hechoen said:
Have you checked the MD5 of the ROM? If it's a bad DL it could flash just enough of it to loop you.
Click to expand...
Click to collapse
Ya I agree try downloading it again. Check the md5 and flash that ROM again. If it doesn't work your gonna have to Odin!

There were a lot of complaints of boot loops when flashing, so I pulled the DL link. I actually stopped using miui and moved back to CM or AOKP, depending on which one is most stable at the moment. Every once in a while I give miui a try, but I never stick with it. If you want miui, I suggest you follow Lithium's thread. His version is the officially supported miui rom.

I can confirm heres what i did to fix i had the boot loop.. all i did was run DARKSIDE Superwipe x2 Times. Then i installed MIUI Rom. Then i Factory Reset. Try booting wait a little bit. If still not going threw remove battery and boot to recovery and factory reset one more time then reboot. So once again.
1. DARKSIDE SUPERWIPE x2++ 2. Install MIUI Rom. 3. Factory Reset. 4. Boot. 5. (If still looping) Remove battery Then recovery. and Factory Reset and boot again. Your welcome

Can we move this to q and a?
Sent from my XT894 using Tapatalk 2

Trying to get back to CM 10.0 from 10.1

I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp lets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?

taurius1 said:
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp ets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
Click to expand...
Click to collapse
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it

a box of kittens said:
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
Click to expand...
Click to collapse
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.

taurius1 said:
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
Click to expand...
Click to collapse
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
I've done that. But just to be sure, I'm gonna try a fresh download once more. ^_^ Brb 10 minutes.

Curious what happened, as I think I may be having this same issue.

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
OOh that worked. Thanks a ton! ^_^
Probably was a bad download all three times I tried to download it before. :/ (I should probably buy a lottery ticket now :/ )
Now, Let me try installing my rooted stock rom. :3

Almost Same Problem
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?

lucasjohnsond said:
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
Click to expand...
Click to collapse
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.

taurius1 said:
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
Click to expand...
Click to collapse
Actually, I just remembered. If you're on the new hboot, you should be flashing the boot img through fastboot, and then installing the zip. Since you've been doing all that anyway, perhaps its time to just wipe everything and start over, step by step.
> download cm 10.0
> check md5 to make sure it's proper
> extract boot.img and flash it via fastboot
> reboot into recovery.
> wipe system, cache, dalvik cache, and factory reset
> transfer the rom and flash it via recovery
:/ I'm no expert here, but that's what I'd be doing now.

[Q] Katkiss 4.3 - AOSP keyboard has stopped after flashing

Help, I'm slowing going out of my mind. I've been trying to figure out the problem but no joy here so far.
I think I've successfully upgraded to KissKat 4.3 from EOS 118 . Everything loads, asks me to set up tablet etc but I keep getting the " AOSP keyboard has stopped" so I can't actually finish the set up or see if I've actually upgraded properly.
I use TWRP 2.5 version, all the Gapps and version 20 from the 1st page. I've reflashed and rebooted many times changed the keyboard settings but ended up the same message. I also get the google text to speech has stopped as well and I've disable that as well.
Any suggestions would be appreciated. :good:

I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.

frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.

frederuco said:
I am pretty sure there is an issue with the GAPPS not being loaded properly. Boot to recovery, wipe cache & davilk, flash GAPPS then wipe caches again. It should boot fine.
If that does not work, try downloading the GAPPS from the first post again. Using any other GAPPS could cause issues.
Click to expand...
Click to collapse
GMTN said:
Hi frederuco, I actually followed your guide but I'll try the gaps once more. If that doesn't work then I'll try ver 19.
Click to expand...
Click to collapse
LOL. I can tell you I've done that 4 different times with 4 different download all from the 1st page but it worked on this 4th and I'm not sure why.
Now to see tomorrow if this ROM lives up to all the troubles ( 3 hours worth ) and praise . Thanks for your guides by the way.

Glad it is sorted. I hope you find it worth your time.

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!