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.
So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
captainjibblet said:
So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
Click to expand...
Click to collapse
So just in case anyone else runs into this problem, I figured it out myself. I am running the MDK build so the only thing you would change is th rooting process.
1. Reflash Stock using ODIN
2. Reroot http://forum.xda-developers.com/showthread.php?t=2381382
3. Install newest 2.6.3 TWRP
4. Back up Stock
5. Flash 4.3 ROM and 4.3 Gapps
I'm not sure if it was reflashing stock or the newest update to twrp but whichever. It worked.
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.
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
I just updated from an old cm 10.2 unofficial build from sometime in september to the latest nightly of cm 10.2. I used the update feature in cm to get the latest nightly and install it. I am running twrp recovery and wipe data cache and delvik after flashing then reboot. this all works fine and the rom boots up and starts re installing my apps. however after I reboot the device it just sits at the tab boot logo and I end up having to wipe data again to boot up and start all over. how can I fix this? I am just not having the best of luck with roms these days. Soon I want to update to kitkat but I am having trouble with that as well. (see other thread)
Edit: it's now having the same issue with my restored backup of my previous rom. Basically my backup is now doing the exact same thing where it just freezes up at the galaxy tab logo after first reboot.
mikee286 said:
I just updated from an old cm 10.2 unofficial build from sometime in september to the latest nightly of cm 10.2. I used the update feature in cm to get the latest nightly and install it. I am running twrp recovery and wipe data cache and delvik after flashing then reboot. this all works fine and the rom boots up and starts re installing my apps. however after I reboot the device it just sits at the tab boot logo and I end up having to wipe data again to boot up and start all over. how can I fix this? I am just not having the best of luck with roms these days. Soon I want to update to kitkat but I am having trouble with that as well. (see other thread)
Edit: it's now having the same issue with my restored backup of my previous rom. Basically my backup is now doing the exact same thing where it just freezes up at the galaxy tab logo after first reboot.
Click to expand...
Click to collapse
Maybe it´s a problem with your emmc. We have a MAG2GA type with a known bug called "MAG2GA TRIM bug" and like i know cm 10.2 runs the trim command once a day. There is a possible patch for this problem, but i think it´s not merged to our device.
Please can you check the emmc memory with the tool eMMC Brickbug Check from Market?