Related
Hi
I have a ASUS TF300T and have installed the TWRP bootloader as recommended by another site.
I have tried Cyanogenmod 9, Cyanogenmod 10 and Cyanogenmod 10.1 nightly and none of them will boot. The device gets stuck at the ASUS logo screen and I get no further.
Obviously I have cleared cache etc (I'm familiar with the basics of installing a different ROM).
Can anyone advise me what to do? I have restored to the default ASUS software through a backup I made but I am really not happy with the performance of this.
I either want to be able to get Cyanogenmod on this tablet or I'd like to restore it to the default bootloader to make it ready for sale.
Thanks so much in advance.
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
mattburley said:
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
Click to expand...
Click to collapse
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
mattburley said:
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
Click to expand...
Click to collapse
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
EndlessDissent said:
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
Click to expand...
Click to collapse
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
mattburley said:
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
Click to expand...
Click to collapse
Since you're using the unofficial build, you won't be able to use the CM Updater. Or, at least, I would assume you can't. I'm pretty sure that it would download the newest official version, and the official ones won't boot. So you'll have to watch the unofficial thread for updates for now, until everything's fixed and it becomes official.
As for waiting to update, that applies to the ASUS OTA updates, not the CM updates. ASUS, as I've mentioned, makes changes to the bootloader in some of their OTAs that can cause bricks. If you're just updating CM nightlies, you shouldn't have anything to worry about. It's the stock updates that get hairy.
If you would like more stuff working, you could downgrade your tablet to 4.1 (forum.xda-developers.com/showthread.php?t=2195883), and install CyanogenMod 10.
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Me too. Just sits there spinning. Went to my backup for now.
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
roberto767 said:
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
Click to expand...
Click to collapse
I have the 4.2 boot loader. So I finally figured out you the 4.2 version recovery instead of the JB version. That unofficial one still would not work so I flashed this and it works great.
http://forum.xda-developers.com/showthread.php?t=2204166
thx for this thread, I had these issues myself,,, shame it wont work on 4.2 bootloader
Stuck at CyanogenMod Logo durng boot
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
roberto767 said:
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Click to expand...
Click to collapse
rdh23 said:
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
Click to expand...
Click to collapse
Just an FYI: the official CM10.1 now supports the 4.2 bootloader. It has for over a month now. Plus, the experimental build has been abandoned.
Same story again
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
p.s. I did make sure to get the right recovery for my bootloader, i.e. openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Emalice said:
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
Click to expand...
Click to collapse
What OS is your PC running??
lj50036 said:
What OS is your PC running??
Click to expand...
Click to collapse
windows 7 64bits...
adb
Emalice said:
windows 7 64bits...
Click to expand...
Click to collapse
You have the adb driver install?? if so turn your tablet off and in a command window move to the directory that adb is in and type
Code:
adb logcat > logcat.txt
now boot your tablet.... your PC will pick it as adb device and output the logcat to a text file in that directory post the logcat file....Let the logcat run for about 90 sec or so.....
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!
i installed cm 11 unofficial from this thread http://forum.xda-developers.com/showthread.php?t=2608377 but when i turn my moto g on it gets stuck in the cyanogenmod loading screen if anyone can help it will be great
You didn't want to post your issue in that thread?
I'm having same problem.. Also same problem for bam ROM
Sent from my XT1032 using xda app-developers app
managed to get out of the CM11 bootloop after applied Fix Permissions (or something similar) in TW's Custom Recovery.
Seems that only TW recovery can fix this through a permissions fix.
Got the same problem last night and the only thing to do to get it works was to re-flash the stock firmware, flash the recovery and reinstall the CM build. Latest build seems to be pretty good.
Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk
imxdot said:
Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Not for me, sadly.
I've also tried to re-flash the rom through the recovery but the only fix that worked for me was to flash the stock firmware and then install the CM via recovery.
Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step
Do you have the XT1032 version?
xavier66 said:
Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step
Click to expand...
Click to collapse
I´m tired of the mess made it because of the three different Moto G versions, i'm waiting for official Recovery from CWM, maybe 3 months it's to early but I wanna try this method. (I hope to don´t hardbrick haha)
I was having the same problem with every rom i tried. After going back complete stock with Alonsoch's tool in the original Dev thread, I was then able to get past the boot on any rom
Sent from my XT1034 using Tapatalk
stuck in loop after installation
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.
sandeepg9 said:
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.
Click to expand...
Click to collapse
please use the thread for the ROM you have issues with.
thread closed
Hey guys,
I have followed many tutorials (video and text) on how to flash ROMs on the Moto G, but to no avail.
I followed all the steps correctly, and my Moto G is stuck in a boot loop after 10 minutes. This happens every time I want to flash a ROM, and it has happened with many different ROMs, what am I doing wrong?
I have wiped all the wipey stuff and whatnot, I just don't know why it isn't working!
This is my first post, so please call me out if i missed any details I need to write down
Custom ROMs I have tried:
CyanogenMOD (Nightly)
Paranoid Android (unoffical)
C-Rom
Any help at all is much appreciated
Regards,
barky02
barky02 said:
Hey guys,
I have followed many tutorials (video and text) on how to flash ROMs on the Moto G, but to no avail.
I followed all the steps correctly, and my Moto G is stuck in a boot loop after 10 minutes. This happens every time I want to flash a ROM, and it has happened with many different ROMs, what am I doing wrong?
I have wiped all the wipey stuff and whatnot, I just don't know why it isn't working!
This is my first post, so please call me out if i missed any details I need to write down
Custom ROMs I have tried:
CyanogenMOD (Nightly)
Paranoid Android (unoffical)
C-Rom
Any help at all is much appreciated
Regards,
barky02
Click to expand...
Click to collapse
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Z-WolF said:
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Click to expand...
Click to collapse
Thanks a lot so how do I downgrade? and where can I find the 4.3 CWM recovery?
Edit: also, isnt 4.3 the upgrade? or is that a typo
barky02 said:
Thanks a lot so how do I downgrade? and where can I find the 4.3 CWM recovery?
Edit: also, isnt 4.3 the upgrade? or is that a typo
Click to expand...
Click to collapse
What i meant was that you need to flash the 4.3 stock recovery, along the 4.3 rom. those files normally come together.
Then you flash the custom recovery of your choice (i used CWM 6.0.4.7 touch) and CM11.
Look Here
4.3 = Jelly Bean Android
4.4 = KitKat Android
alezardstar said:
Dude, I completely understand you but I want to be very sure about what I will do foot try another time.
I back to 4.3 image downloading it here ( http://sbf.droid-developers.org/phone.php?device=14) and it already has the 4.3 recovery inside or I must to download it (from where?). Can you share the thread where you found the CWM recovery, please? Just to do it identical as you.
Thanks in advance.
Click to expand...
Click to collapse
let me see...
the guide to downgrade to 4.3 is this one
the guide to install CMW and CM11 is in cyanogenmod's wiki, you can find it here
as far as i know every (or at least most) stock ROM zip or tar file out there comes with a "recovery.img"
Yup downgrade to 4.3 needed then you'll have no problems
Sent from my Moto G using xda app-developers app
Happened to me as well (mine was rooted too), I followed the exact same steps Z-Wolf mentioned after searching and this seems to be a common problem.
I bought my device already upgraded to 4.4.2. I was able to install c-rom with no issue. I'm using tweaky ROM right now.
I'm curious as to why some devices need to downgrade and some don't?
Sent from my XT1032 using Tapatalk
What I did was installing cm11 from GPE and then wipe all cache and wipe system data or something like that (it deletes everything un your infernal sd), it worked for me after having bootloop with every ROM I tried. Ask the guys for those wipes ( I think it was format system/data but I don't remember very well).
ATRIXXIRTA said:
I bought my device already upgraded to 4.4.2. I was able to install c-rom with no issue. I'm using tweaky ROM right now.
I'm curious as to why some devices need to downgrade and some don't?
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
How did you do that man? I tried almost every found on this forum and I wasn't abble to get this done, always the same problem with encrypted partition comes up
---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------
Z-WolF said:
Happened to me at first too, when i had 4.4.2 stock in my Moto G, CM11 gets stuck in the bootanimation forever, what i did is downgrade to 4.3 (including the recovery) and then installed CM11.
Click to expand...
Click to collapse
Did you get the downgrade version from here, which one did you use? I tried several and without success. I have a Moto G GPE
I will share my history with my phone since it can be useful for someone... Well I got the phone about a month ago, since i ordered from amazon, there's no way im going to return it for garanty if it broke, flashed cwm and rooted the same night, but when i was going to flash cm, l encountered a bootloop, since i didn't make a backup... i was at lost, my computer doesn't detect the phone in cwm, so I was with bootloop and not able to flash anything... Tried fastboot... Yes! so I downloaded stock and flashed away in fastboot, then i tried again with cm11, and this time it booted fine! I guess something prevented us to flash anything directly over stock, dunno what
I was stuck on boot loop for the past 24h, trying to flash a Lego ROM.
After a few factory resets and stock ROM flashes, I came across the solution of downgrading from KitKat 4.4.2 to Jelly Bean 4.3, then flash Lego again, and now all is well and good !
Here's the guide : http://forum.xda-developers.com/showthread.php?t=2542219
Flash Radios and New Kernel.
1031_Boost_US_CDMA_390.81.01P.zip
https://www.androidfilehost.com/?fid=23681161096070097
1031_Boost_US_CDMA_Kernel_3.4.42-gb89c9dd.zip
https://www.androidfilehost.com/?fid=23681161096070111
in my case I was flashing a Falcon, Boost Moto G, keep getting bootloops.
This is the first time in years I have ever had to sideload the Kernal and Radio, but non the less it stopped my bootloop.
Now if I get the error 16 voice mail message taken care of and input my MSL......
https://www.androidfilehost.com/?fid=23681161096070097
So i was trying to flash CM 11 onto my Razr HD following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2518701&highlight=boot+loop
However, after flashing and everything, my phone ends up in a bootloop... I'm on 4.4.2, 183.46.10XT926, kernel 3.4.42 and an unlocked bootloader
Any help?
braube said:
So i was trying to flash CM 11 onto my Razr HD following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2518701&highlight=boot+loop
However, after flashing and everything, my phone ends up in a bootloop... I'm on 4.4.2, 183.46.10XT926, kernel 3.4.42 and an unlocked bootloader
Any help?
Click to expand...
Click to collapse
i dont think cm is updated to 4.4 source yet, i could be wrong. (as it turns out, i was wrong and cm is on 4.4 source)
if it is not, you cant install it over 4.4, that's why it is bootlooping.
What do you talking about? CM11 is 4.4.4, maybe @braube is trying to install an old version of CM11 that is based on 3.0 kernel, just try the latest versions available here: http://download.cyanogenmod.org/?device=moto_msm8960
DorianX said:
What do you talking about? CM11 is 4.4.4, maybe @braube is trying to install an old version of CM11 that is based on 3.0 kernel, just try the latest versions available here: http://download.cyanogenmod.org/?device=moto_msm8960
Click to expand...
Click to collapse
i said "i could be wrong", learn to read, or at least reply more politely with a correction.
So you answer any question without a minimal knowledge? That's how you get so many thanks?
DorianX said:
So you answer any question without a minimal knowledge? That's how you get so many thanks?
Click to expand...
Click to collapse
jealous?
Yup I'm so jealous ;(
braube said:
So i was trying to flash CM 11 onto my Razr HD following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2518701&highlight=boot+loop
However, after flashing and everything, my phone ends up in a bootloop... I'm on 4.4.2, 183.46.10XT926, kernel 3.4.42 and an unlocked bootloader
Any help?
Click to expand...
Click to collapse
I know you stated you followed the directions, but just in case, this is what I do:
1. Boot into TWRP
2. Wipe cache, dalvik cache, data and system
3. Install CM11.
4. Install GAPPS
5. Wipe cache and dalvik (from the Install screen)
6. Reboot and profit.
If this still doesn't work for you, you might have a corrupted download for CM11 and/or GAPPS, so try downloading them again and make SURE you are using the correct CM11 image.
If you are getting them from epinter, then make sure you choose the correct one. There are a LOT of ROM images there (for XT925, for CM10 for JB-based phones, CM11 xt926 I believe is for JB based phones, you want the CM11 with msm9690 in the file name).
I get mine from here -> http://download.cyanogenmod.com/?device=moto_msm8960
Also, make sure you have the correct TWRP installed (2.7.1.0) that is KK based. Do NOT use earlier versions which are based off of JB.
You can also use CWM recovery, but make sure it's 6.0.4.9. Anything else is for JB-based phones that haven't been upgraded to KK.
Thanks for all the replies. I just did a standard wipe with TWRP so maybe thats the problem.
Another question, is the msm8960 CM11 compatible with XT926? I read somewhere that it was but i just want to make sure
That's what you want and it's what I linked you to.
Sent from my DROID RAZR HD using Tapatalk