I managed to get my xt925 updated to KKBL, and after flashing cm12.1 I'm stuck in the boot animation. I tried flashing several cm11 versions as suggested somewhere else as step inbetween, but most of them resulted in boot loops (right after unlocked bootloader warning) Any Idea how to fix this ?
btw. I'm trying to flash the lastest cm12.1 . unfortunately I did not make a backup uf stock KK rom before starting this. silly me Is there a stock 4.4.2 ROM available to flash with RSDLite ? I Already tried to restart the whole process - but flashing Stock JB won't work after having KK BL
scherliberli said:
I managed to get my xt925 updated to KKBL, and after flashing cm12.1 I'm stuck in the boot animation. I tried flashing several cm11 versions as suggested somewhere else as step inbetween, but most of them resulted in boot loops (right after unlocked bootloader warning) Any Idea how to fix this ?
btw. I'm trying to flash the lastest cm12.1 . unfortunately I did not make a backup uf stock KK rom before starting this. silly me Is there a stock 4.4.2 ROM available to flash with RSDLite ? I Already tried to restart the whole process - but flashing Stock JB won't work after having KK BL
Click to expand...
Click to collapse
Fixed the Issue by flashing Slimrom 4.4.4 as interlude. Now I'm on CM12.1 and bootup process is normal.
Thank you, so much!
scherliberli said:
Fixed the Issue by flashing Slimrom 4.4.4 as interlude. Now I'm on CM12.1 and bootup process is normal.
Click to expand...
Click to collapse
I was with the same problem and a fixed it after read your tip!! thank you very much!!!!
That is what did the trick for me too.
At first cm12.1 wouldn't run on my XT925. Then i flashed SlimROM 4.4.4, booted it up, rebooted into recovery mode (twpr 2.8.6.0), flashed cm12.1, wiped cache and dalvik and then rebooted.
Now it runs stably on cm12.1. Thanks a lot!
Related
Ok, this is weird, a while ago i didnt had any problems installing any kind of custom rom, used CWM while wiping everything... eveything was OK, ROM worked OK, etc... But one time i installed a ROM (Slimkat) and i lost signal, tried to use my recovery of stock android but it didnt work, so i tried a lot of things untill i got bootlop without being able to install anything since some files were missing, bad luck
After that, i just reflash stock 4.3 and upgrade from there 4.4.2, everything fine again... except that i cant install any kind of ROM, every ROM says "installation succesful" but everyone is stuck into bootloop.
While i havent tried ALL ROMS i have tried the same ones i was using (Nexus G+, LiquidSmooth and CM11), so i guess this problem is coming from my device.
On a side note, i tried to factory reset, but no luck... it shows the Android working but it inmediately turns the screen off, and then it shows it again and then off again... in an infinite loop
Same problem!
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Liberr said:
Bump.
I just got my Moto G yesterday (European XT1032), updated to 4.4.2, unlocked bootloader, rooted with superboot and flashed Philz Touch CWM.
Seems I have done everything by the book, wipes included, but no luck. I tried Slimkat, Paranoid and Codename Lungo (latest builds as of 3/12).
Click to expand...
Click to collapse
Hmmm... Pay attention to which version of Bootloader you are using.
You might want to try both 4.3 and 4.4 to see which one would work.
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Good luck!
neozen21 said:
Extract the motoboot.img from the stock .zip image for your phone, then flash with mflashboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Liberr said:
Thanks. I'll give that a try. Is there a way to check bootloader version on the phone? If that doesn't work out I'll start from scratch and report back in this thread..
Click to expand...
Click to collapse
Hmmm.. I see there is a version number on mine, 41.05 dated 2013-12-06, but I'm not sure if that's the version or not.
And yeah... if changing the bootloader doesn't help, you probably would have to restore from the stock image and start over..
Got root and custom roms working after I 1.) downgraded to 4.3 and 2.) flash TWRP (instead of CWM).
So I'm not sure what the problem was. Besides the two main rooting methods (superboot and custom recovery), there are some other methods described on the forum specifically for people who already did a international variant OTA to 4.4.2. and one that is absolete (here) but apparently works for some when the two main methods fail.
However I'm still not sure if this solved everything. I am not sure if I can flash Cyanogenmod (which is 4.4.2) over a 4.3 firmware. Maybe I need to manually flash a 4.4.2 radio or something... Gonna check that out next...
EDIT: No need to downgrade. Not sure how it works but two main root methods (superboot and custom recovery) didn't work for me. Somehow I got stuck in boot animation. Just installed TWRP instead of CWM after Kitkat firmware (EU Retail) and rooted (/installed Super Su) from there. Everything works fine now.
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
muqy said:
Hey guys, I've seen this issue before yet I've tried everything in a few threads now but have no idea what is happening,I have tried using search function yet no solution has fixed my problem.
Problem:
When installing custom ROMs the installation goes fine. I put the ROM on the sdcard, follow instructions for flashing e.g wipe data/cache etc and then flash GAPPS. However I get stuck on the boot logo of every ROM. I've tried both TWRP and CWM recoveries, both with no luck. Also tried not flashing GAPPS and just trying to flash the ROM to no avail.
Current state of phone:
The phone is currently running stock firmware via downloading factory image and flashing in boot-loader : stock boot, recovery, system image etc
The phone works fine when rooted on stock firmware. E.g no custom rom yet rooted.
Could really do with some help guys, any ideas?
Click to expand...
Click to collapse
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
chairsz said:
same problem simple solution another user informed me of.
simply donwgrade to 4.3 JB stock rom through fastboot. Then you are able to flash a custm rom from the 4.3 stock rom.
Its crazy i have to do this but it worked for me, now im running the xperience rom which is a rom based on 4.4.2 kk.
the 4.3 android stock firmwares are linked somewhere in the FAQ's as well as the guide to ffastboot lash it.
peace.
Click to expand...
Click to collapse
Hey man, worked a charm thanks!
For users who may have the same problem:
After flashing 4.3 onto the device it did NOT boot.
- However I then went into the bootloader flashed custom recovery, I used cwm.
- Then I went into recovery, used adb to push the rom and gapps onto sdcard
- Full wipe and then installed rom. Then installed gapps
Working fine.
Cheers chairsz :good::good:
Hey all,
Its been a while since I have messed around with my XT926 and I am having some trouble flashing a 4.1.2 ROM on it. What I've done so far is to RSDLite to a 4.4.2 build (one that is still compatible with boot loader unlock) and unlocked the boot loader. I was having trouble getting a recovery to flash other than epinters cwm and twrp 2.8. I tried flashing nexesue v3.6 in both recoveries but am stuck on the Motorola symbol on blot. If I RSDLite back to a 4.1.2 build can I then flash an older recovery and then the ROM?
EDIT: phone is also rooted using towelroot.
Any help is appreciated.
DID you try twrp 7.1.0?
lysdexik said:
Hey all,
Its been a while since I have messed around with my XT926 and I am having some trouble flashing a 4.1.2 ROM on it. What I've done so far is to RSDLite to a 4.4.2 build (one that is still compatible with boot loader unlock) and unlocked the boot loader. I was having trouble getting a recovery to flash other than epinters cwm and twrp 2.8. I tried flashing nexesue v3.6 in both recoveries but am stuck on the Motorola symbol on blot. If I RSDLite back to a 4.1.2 build can I then flash an older recovery and then the ROM?
EDIT: phone is also rooted using towelroot.
Any help is appreciated.
Click to expand...
Click to collapse
See my post, had problem to install Nexesque too, but had success with specific CWM version. Also try to wipe all and flash boot.img as the op in Nexesque has stated.
http://forum.xda-developers.com/showpost.php?p=55752257&postcount=170
I have build from source CM12 and when I flashed the ROM it is in an infinite loop in the GOOGLE logo. I have done everything correctly.
I installed a CM12.1 build and there is no problem.
Flashed factory images of 5.0, 5.02 an 5.1.1 and then flashed my build but still it is in loop. No problem when I flash a CM12.1 build.
Can you point out what I did wrong ?
eNVy said:
I have build from source CM12 and when I flashed the ROM it is in an infinite loop in the GOOGLE logo. I have done everything correctly.
I installed a CM12.1 build and there is no problem.
Flashed factory images of 5.0, 5.02 an 5.1.1 and then flashed my build but still it is in loop. No problem when I flash a CM12.1 build.
Can you point out what I did wrong ?
Click to expand...
Click to collapse
If you built from source with no modifications, it should work fine provided that you are installing it on top of the same version of Android. That means if CM12 is 5.0.2 you probably have to install it on top of a fresh install of stock 5.0.2 or some 5.0.2 ROM.
You should also wipe data and dalvik (you probably did seeing as you claim to have done everything correctly).
So i've been running stable slimkat 9.0 (4.4.4) on my galaxy s3 and it has been working great. I want to upgrade it to lollipop but I've had trouble flashing any lollipop rom. CM12, AICP, OctOS, PacROM all fail to boot after I flash in recovery. The boot animation starts, and I get the screen that android apps are initializing. After it runs through the apps, the screen blacks out and the phone resets and the cycle continues.
I've had no issues flashing roms beforehand. I can go back to 4.4. and 4.3 ROMs both AOSP and Touchwiz without any problems. I've flashed with both clockwork mod and TWRP and the results are the same. I do a clean factory reset and wipe prior to flashing the rom and 5.1 gapps.
I have no idea why it won't boot up for me. Would appreciate any help!
alphax_0 said:
So i've been running stable slimkat 9.0 (4.4.4) on my galaxy s3 and it has been working great. I want to upgrade it to lollipop but I've had trouble flashing any lollipop rom. CM12, AICP, OctOS, PacROM all fail to boot after I flash in recovery. The boot animation starts, and I get the screen that android apps are initializing. After it runs through the apps, the screen blacks out and the phone resets and the cycle continues.
I've had no issues flashing roms beforehand. I can go back to 4.4. and 4.3 ROMs both AOSP and Touchwiz without any problems. I've flashed with both clockwork mod and TWRP and the results are the same. I do a clean factory reset and wipe prior to flashing the rom and 5.1 gapps.
I have no idea why it won't boot up for me. Would appreciate any help!
Click to expand...
Click to collapse
same problem here bro
sgs3 i9300
i solved mine so if you are still experiencing that hmu i will show you what i did
alphax_0 said:
So i've been running stable slimkat 9.0 (4.4.4) on my galaxy s3 and it has been working great. I want to upgrade it to lollipop but I've had trouble flashing any lollipop rom. CM12, AICP, OctOS, PacROM all fail to boot after I flash in recovery. The boot animation starts, and I get the screen that android apps are initializing. After it runs through the apps, the screen blacks out and the phone resets and the cycle continues.
I've had no issues flashing roms beforehand. I can go back to 4.4. and 4.3 ROMs both AOSP and Touchwiz without any problems. I've flashed with both clockwork mod and TWRP and the results are the same. I do a clean factory reset and wipe prior to flashing the rom and 5.1 gapps.
I have no idea why it won't boot up for me. Would appreciate any help!
Click to expand...
Click to collapse
Are you on the correct firmware? MF1? There is a flashable zip in the CM12.1 thread for it.
Updating the firmware did the trick, thanks! Was running on ML1 up til now. Glad my s3 can still keep up with the times