Related
Hey,
I have JB 4.1.2 by bruce2728 version 10-20121114 kernel 3.0.51-jelly-00183-g0707900-dirty [email protected] #1.
I want to to upgrade to 4.2.x but no version works(I tried almost all latest versions from:
http://bruce2728.mabsoft.dk/
Then I tried to install KANG 4.2.2 from this thread:
http://forum.xda-developers.com/showthread.php?t=2115520,
after installation the system did not start (just HTC logo and nothing happened more).
. After wipe/factory reset all the version did not work.
Where could be problem? old firmware?
Please help, gonna crazy
vasek2 said:
Hey,
I have JB 4.1.2 by bruce2728 version 10-20121114 kernel 3.0.51-jelly-00183-g0707900-dirty [email protected] #1.
I want to to upgrade to 4.2.x but no version works(I tried almost all latest versions from:
http://bruce2728.mabsoft.dk/
Then I tried to install KANG 4.2.2 from this thread:
http://forum.xda-developers.com/showthread.php?t=2115520,
after installation the system did not start (just HTC logo and nothing happened more).
. After wipe/factory reset all the version did not work.
Where could be problem? old firmware?
Please help, gonna crazy
Click to expand...
Click to collapse
if you are S-ON install 4ext recovery(if you don't have it already)
enable smartflash from it
flash the rom
Hi, Could we know your about in settings, and your Hboot Settings (VolDown + PowBtn) read and write informations..
After that we can helps u
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
Hey guys,
I just unlocked my stock xt926 (Build 183.46.10 Kit Kat) using towelroot and motopocalypse. I then installed TWRP 2.7.1.0 (Kit Kat 4.4 build from Original development section) and did a backup of the stock ROM. I tried installing a couple builds of Cyanogenmod 11, but all of them get stuck on the red M. I got the latest snapshot from get.cm, as well as the one posted by epinter. I sent them over USB and used Ubuntu to validate MD5's using md5sum. I do a full wipe (of everything but internal storage) and install just the ROM, not Gapps, kernels or anything else. After a reboot, nothing but the red M. It will flash once every 5-10 minutes, but I let it sit for 45 minutes without anything else happening.
I also tried it in CWM6 (Kit Kat build from original development) and had the same results.
Right now I'm trying Gummy to see if it's just a CM thing, but has anyone else encountered this? If so, did you find a fix?
Thanks!
Make sure you are using a recent nightly. The earlier M snapshots are based on the JB kernel. I think the current nightly use the kk kernel but check the cm11 thread in the development section.
thunder2132 said:
Hey guys,
I just unlocked my stock xt926 (Build 183.46.10 Kit Kat) using towelroot and motopocalypse. I then installed TWRP 2.7.1.0 (Kit Kat 4.4 build from Original development section) and did a backup of the stock ROM. I tried installing a couple builds of Cyanogenmod 11, but all of them get stuck on the red M. I got the latest snapshot from get.cm, as well as the one posted by epinter. I sent them over USB and used Ubuntu to validate MD5's using md5sum. I do a full wipe (of everything but internal storage) and install just the ROM, not Gapps, kernels or anything else. After a reboot, nothing but the red M. It will flash once every 5-10 minutes, but I let it sit for 45 minutes without anything else happening.
Right now I'm trying Gummy to see if it's just a CM thing, but has anyone else encountered this? If so, did you find a fix?
I am having the same issue, I have basically done/flashed the same things but seems like no matter what I just get stuck on splash screen.... And my phone gets HOT- too hot to touch...
Click to expand...
Click to collapse
I think snapshots are for jb bootloader.
And doesn't CM tell you to flash gapps?
Someone will correct me if I'm wrong.
Doug B.
I also used CWM and not TWRP. I'm not much help as I'm on stock kk with xposed at the moment. I need Moto exchange services because AOSP has to many issues. I'm missing lots of CM11 favorites (like working BT with Wifi lol).
dvgb173 said:
I think snapshots are for jb bootloader.
And doesn't CM tell you to flash gapps?
Someone will correct me if I'm wrong.
Doug B.
Click to expand...
Click to collapse
Gapps is not required. It just means you won't have Google Play store and other google apps on the phone until you go back and flash them, but NOT flashing gapps will not cause the phone to hang.
You have to ensure you are using the correct CM11 tree, especially if you are on the KK bootloader.
Go here to grab the latest nightlies for KK bootloaders -> http://download.cyanogenmod.com/?device=moto_msm8960
Grab the latest nightly, not snapshot, as someone else stated.
Hi, yesterday I unlocked bootloader and flashed stock firmware, did back up and tried latest nightly CM11.. but I was experiencing lot of bugs and battery drain so I decided to try latest Snapshot CM11. Everything was ok, but then, I changed boot logo, copied bootanimation to system/media and changed admin rights (as was written in guide), after reboot I was getting message "Unfortunately, the process com.android.systemui has stopped." and since that (even after restoring) everytime I install CM11 Snapshot, I'm getting this message after reboot.
The flashed stock firmware was: Android 4.4.4 - Blur_Version.210.12.40.falcon_utms.EURetail.en.EU (Retail EU) (XT1032)
I can acess the recovery (ClockworkMod Recovery v6.0.4.7) and still have custom boot logo but thats all I can tell you.
What to do now? I was really happy with snapshot until this
2hipso said:
Hi, yesterday I unlocked bootloader and flashed stock firmware, did back up and tried latest nightly CM11.. but I was experiencing lot of bugs and battery drain so I decided to try latest Snapshot CM11. Everything was ok, but then, I changed boot logo, copied bootanimation to system/media and changed admin rights (as was written in guide), after reboot I was getting message "Unfortunately, the process com.android.systemui has stopped." and since that (even after restoring) everytime I install CM11 Snapshot, I'm getting this message after reboot.
The flashed stock firmware was: Android 4.4.4 - Blur_Version.210.12.40.falcon_utms.EURetail.en.EU (Retail EU) (XT1032)
I can acess the recovery (ClockworkMod Recovery v6.0.4.7) and still have custom boot logo but thats all I can tell you.
What to do now? I was really happy with snapshot until this
Click to expand...
Click to collapse
Same stuff happens to me, seems to be because of failed stock firmware flashing, dunno what is has to do with systemui, any rom I flash fails at second boot this way.
betatan said:
Same stuff happens to me, seems to be because of failed stock firmware flashing, dunno what is has to do with systemui, any rom I flash fails at second boot this way.
Click to expand...
Click to collapse
Yes, for me helped clean install of new ROM.. I use new now (signature) and I am 100% happy
2hipso said:
Hi, yesterday I unlocked bootloader and flashed stock firmware, did back up and tried latest nightly CM11.. but I was experiencing lot of bugs and battery drain so I decided to try latest Snapshot CM11. Everything was ok, but then, I changed boot logo, copied bootanimation to system/media and changed admin rights (as was written in guide), after reboot I was getting message "Unfortunately, the process com.android.systemui has stopped." and since that (even after restoring) everytime I install CM11 Snapshot, I'm getting this message after reboot.
The flashed stock firmware was: Android 4.4.4 - Blur_Version.210.12.40.falcon_utms.EURetail.en.EU (Retail EU) (XT1032)
I can acess the recovery (ClockworkMod Recovery v6.0.4.7) and still have custom boot logo but thats all I can tell you.
What to do now? I was really happy with snapshot until this
Click to expand...
Click to collapse
I use the rom in my signature with a custom boot animation and boot logo without issues.
Long time ago now but, think I flashed them via fastboot. No messing around with manual file copying and permissions. Why did you do this manually (the hard way)?
---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------
2hipso said:
Yes, for me helped clean install of new ROM.. I use new now (signature) and I am 100% happy
Click to expand...
Click to collapse
Should have read the whole thread first. My comment above might still help someone looking to stay on CM11 and flash a custom boot logo/animation.