Repurposing this thread rather than making a new one. I installed two different ROMs that support locked bootloader on my cousin's C2104 (not unlockable) but they both hang on the boot animation. I left them for 10+ minutes but it never went to the setup screen. I flashed using CWM 6.0.5.0 and the ROMs installed successfully. Any idea why this is happening?
I've tried two different 4.2.2 custom roms that support locked bootloader, they install successfully both both get stuck at boot animation. i followed the instructions as described by each rom, not sure what to do next?
fattest said:
I've tried two different 4.2.2 custom roms that support locked bootloader, they install successfully both both get stuck at boot animation. i followed the instructions as described by each rom, not sure what to do next?
Click to expand...
Click to collapse
There is NO 4.4.4. ROM for locked bootloader.
If you want to have ROM for locked bootloader it can only be based on stock fw. Since all KK ROMs are based on CM or AOSP, you need to unlock the bootloader.
Related
Hi,
I was wondering if you had to be rooted to install a custom rom on my phone. Thanks
Rooted no. S-off or unlocked by HTCdev yes.
Once your either one of the above, you need to flash a custom recovery, then you can install roms and root.
my phone was originally on vodafone but today i switched to 3 i was wondering if i flash the 3 ruu to my phone will it come with all the correct settings and 3 boot logo etc? Thanks
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Holyman8388 said:
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Click to expand...
Click to collapse
You must be on Jelly Bean 4.2.1
with the Asus Stock bootloader 10.6.1.8 and TWRP Recovery patched 2.4.4.0
or
Bootloader 10.1.15.3 and TWRP patched 2.5.0.0
You will find all versions of Stock firmwares and Stock kernels here
And the TWRP recoveries here
philos64 said:
You must be on Jelly Bean 4.2.1
with the Asus Stock bootloader 10.6.1.8 and TWRP Recovery patched 2.4.4.0
or
Bootloader 10.1.15.3 and TWRP patched 2.5.0.0
You will find all versions of Stock firmwares and Stock kernels here
And the TWRP recoveries here
Click to expand...
Click to collapse
I am currently running the 10.1.15.3 bootloader and TWRP 2.5.0.0, yet it still does not finish flashing the ROM. I even tried to flash a more simple stock based ROM, ie. black beans 8. This did not work either. It went through the twrp flash and restarted but when it got to the ASUS boot up screen it simply stopped. I waited about 10 minutes for it to possibly load however it never did. So I am restored back to my stock and am awaiting any further help.
Holyman8388 said:
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Click to expand...
Click to collapse
In the OP for PACman rom it says you must be on android 4.1.1 to flash his rom. You need to pick a rom for your 4.2.1. I am also on 4.2.1 and run CROMI 4.6.6 with no issues. Have also succesfully tried the Energy rom. Read carefully the OP for the rom's you are considering and make sure they are for 4.2.1
Holyman8388 said:
I have a asus tf300t running 4.2.1 with unlocked bootloader and root. I am running twrp v2.5.0.0 and I have already made backups of my apps. I am trying to install a custom rom. Preferably PACman rom but at this point any will do. When I try to flash the rom it go through the whole process then reboots but does not get past the asus splash screen.
What is the problem? Is it that the new bootloader does not accept any custom roms, if so how do I downgrade to 4.1? Otherwise I am open to any advice.
Click to expand...
Click to collapse
I am having the same problem! I am running 4.2.1 and im trying to install blackbean 8 using twrp 2.5.0.0. I factory reset in twrp and wipe cache and dalvic. I then install the the rom and reboot but it will not go past the first boot screen with the tegra logo in the bottom right. It always flashes for a second but then does nothing. I have even tried cm 10.1 and it does the exact same thing. I am still able to restore back to stock. This is my first time flashing a rom so any help would be appreciated!
For the latest [ROM][4.2.2][ OFFICIAL] PAC-man v23.0.0 [OC up to 1.7GHz][New Update 22/06/2013], if you read the installation process, you need to be 4.1.1 and not 4.2.1 and also you need installed custom recovery for JB 4.1 BL !
For the latest [ROM]ASU-JellyBean-Hydro 8 (6/29/13)Liquid Butter..- Tf300 -Official 10.6.1.15.3 Base, you need to be on 4.2.1 and 10.6.15.3 bootloader
and you will see to the changelog:
...not sure if any bootloader will work...
Click to expand...
Click to collapse
Hope it's helpful for you
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 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 tried a cm12.1 rom which used to get flashed perfectly without any issues earlier. Then i encountered some problems with the ROM and i decided to flash the stock international kitkat rom(yes, i followed the correct procedure from the guide by @codelover). I didn't unlock the bootloader nor root it nor flashed a custom recovery.
For the past few day's i've been trying to install the same cm 12.1 rom and some new cm12.1 roms(updated versions, here is the link:https://userscloud.com/go/kgu385awbw9z/) but without any luck. After flashing either of the roms, the phone boots up fine till the stage where it shows the static honor logo(non-animated one) but after that it just shows a black screen and just stays there.
If i reflash stock B115, B108-signed 4.2.2 roms and B320 kitkat rom, it happens perfectly. But if i flash any other roms (after unlocking the bootloader and flashing custom recovery by following the guide), the black screen problem pops up(which didn't used to happen earlier). AGAIN i have tried the older cm12.1 ROM whose zip file has been stored on the sd card since that day without any modifications, so there's no chance of the ROM being tampered with.
I have tried hard resetting it by deleting emmc partitions and then reflashing the stock roms, but still the problem pertains after flashing the custom roms.
Does anyone know where i might be going wrong or what the problem is?