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.
Related
My phone is stuck in the CyanogenMod 10 booting animation.
I did the following:
1. Installed RUU (after changing radio and wanted to go back) , unchecked fastboot in the power setting and checked the USB debugging from
the DEVELOPER OPTIONS.
2. Rooted the phone.
3. Installed TWRP2.2.2.0 recovery.
4. Backed up the stock sense 4.0 rom.
5. flashed the CM10 Nightly 20/9/2012. flashing went well (no errors or anything of the sort)
6. fastboot the boot.img from the rom.
7. After 25 min of waiting in the boot animation of the CyanogenMod 10 I rebooted and restored the backup ,during the restore ,in the part of the boot restoring, it took around 400sec(i'm not sure if its bad) - after the restore was done the phone did not boot past the first HTC screen (with the red warning ).
8. I installed Viper One rom and now its working fine.
Does any one have an idea of what went wrong?
I wanna be able to flash the CM10 nightlys...
Thanks
Bad CM10 download? MD5?
Bad Boot flash?
What hboot version you on--
Not really sure--did you do full wipe including System on both flashes. I usually wipe 3X on new/different roms--
rugmankc said:
Bad CM10 download? MD5?
Bad Boot flash?
What hboot version you on--
Not really sure--did you do full wipe including System on both flashes. I usually wipe 3X on new/different roms--
Click to expand...
Click to collapse
I flashed the boot twice and two different CM10 nightly and I did not flash the system at any time.
I had Hboot 1.06 before the RUU installation, now i have 1.13, could this be an issue?
ok
with .13 you probably need to fastboot boot image anyway
i always wipe System 3x unless just updating nightlies or a rom with a minor version cahnge
try cm10 again with System wipe
rugmankc said:
ok
with .13 you probably need to fastboot boot image anyway
i always wipe System 3x unless just updating nightlies or a rom with a minor version cahnge
try cm10 again with System wipe
Click to expand...
Click to collapse
Well I have Hboot 1.13 and I just cant flash the CM10 nightly or mount the SD card cant be mount (i tried the guide didn't worked).
when i go in to the CWM recovery i see these messages.
can it be the problem?
I think i need to make a video of what Im doing because ever since i updated the Hboot (by mistake) i just cant flesh CM10 nightlis.
You might want to try TWRP recovery from Market
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.
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.
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.
bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!
ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.
I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.
the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.
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