Database Info

Just updated my TF300T after not using it for a while, stuck on Asus screen...

So I haven't touched my tablet in a while and figured I'd update it. It was running the official CM 10.1 ROM (4.2.2) without issues. I updated TWRP to 2.6, factory reset it and rebooted it a few times to make sure TWRP didn't **** up, since I had no idea what bootloader I was on and I took a shot in the dark deciding which TWRP file to download. I installed the "-4.2" one and it booted fine several times without issue.
Downloaded the official 08/23 CM10.2 nightly and flashed it with Gapps, now it's stuck on the Asus screen. Boots, Asus, flashes black, Asus, rinse and repeat. So, I get back into recovery, flashed it again just to be sure, same deal. So I flashed back to CM 10.1 -- and it's still doing the same thing.
Anyone have a similar experience and hopefully a solution?

hettbeans said:
So I haven't touched my tablet in a while and figured I'd update it. It was running the official CM 10.1 ROM (4.2.2) without issues. I updated TWRP to 2.6, factory reset it and rebooted it a few times to make sure TWRP didn't **** up, since I had no idea what bootloader I was on and I took a shot in the dark deciding which TWRP file to download. I installed the "-4.2" one and it booted fine several times without issue.
Downloaded the official 08/23 CM10.2 nightly and flashed it with Gapps, now it's stuck on the Asus screen. Boots, Asus, flashes black, Asus, rinse and repeat. So, I get back into recovery, flashed it again just to be sure, same deal. So I flashed back to CM 10.1 -- and it's still doing the same thing.
Anyone have a similar experience and hopefully a solution?
Click to expand...
Click to collapse
I had this issue. It was because I was on the wrong bootloader. -4.2 is for the newest bootloader, and JB is for the JB one before that.
I followed the guide at http://forum.xda-developers.com/showthread.php?t=2187982 to update to the latest stock, which updates the bootloader. After that, the new CM builds work.

L551 said:
I had this issue. It was because I was on the wrong bootloader. -4.2 is for the newest bootloader, and JB is for the JB one before that.
I followed the guide at http://forum.xda-developers.com/showthread.php?t=2187982 to update to the latest stock, which updates the bootloader. After that, the new CM builds work.
Click to expand...
Click to collapse
Thanks.

Wow. I came here to post almost the exact same story. I use my tablet every day, but I haven't updated in months. So when I finally did it was stuck in the boot loop. =( Thanks for the info, L551!

Stuck on boot animation.

Wondering if anybody else is having this problem? If I install a custom rom like cm11 unofficial I just get stuck on the boot animation. It happens on any custom rom I installed and I followed all instructions. Any ideas? Running 1034 16gb on kit kat.

imprzwv said:
Wondering if anybody else is having this problem? If I install a custom rom like cm11 unofficial I just get stuck on the boot animation. It happens on any custom rom I installed and I followed all instructions. Any ideas? Running 1034 16gb on kit kat.
Click to expand...
Click to collapse
Make sure your bootloader is unlocked and your device is rooted. In addition your recovery must be installed correctly.

eddvys said:
Make sure your bootloader is unlocked and your device is rooted. In addition your recovery must be installed correctly.
Click to expand...
Click to collapse
i have the same problem on my xt1032 unlocked and rooted.
how i know if my recovery is installed correctly?
(i can only flash stock rom)

yoyococo said:
i have the same problem on my xt1032 unlocked and rooted.
how i know if my recovery is installed correctly?
(i can only flash stock rom)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2563599 Flash CWM in fastboot
Push ROM files to your /sdcard/
Install using your recovery xxx.zip
Instruction are there just follow them right.

I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk

Worked great thank you
x-Wooboost-x said:
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Works great now on my XT 1034.

x-Wooboost-x said:
I had this problem yesterday. Here is how I fixed it:
Install stock firmware. I installed a 4.4 one. http://forum.xda-developers.com/showthread.php?t=2542219
Then rooted using superboot
Finally, I installed TWRP
It took like three tries to get superboot and twrp to work properly. That's how I fixed it. Goodluck
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Had the same problem with a xt1032 retail.DE version, but didn't work.
I flashed the US umts4.4.2 version, was able to install root using superboot (at 2nd of 3rd try) and installed TWRP. Tried to Cm11 and gapps installed good, but still got stuck on bootanimation.
Losing faith here.

well this just happened on my phone again. the way I fixed it last time isn't working now I have no idea what to do

Why is no one helping with this issue. Ive experienced this a lot and I always have to restore it stock. I have never been able to install a custom ROM no matter how many times I root.
Sent from my XT1034 using xda app-developers app

I have this issues also on 4.4 us global rom. Rooted and recovery cwm
Sent from my XT1032 using Tapatalk

There are two ways to get this fixed:
Fix permissions through TWPR recovery (not available on CWM recovery);
Restore to stock firmware (you can find 4.4.2 firmware here: http://forum.xda-developers.com/showpost.php?p=49861244&postcount=101), flash CWM recovery (or TWRP) and flash CM11 again. This worked for me.
Let me know!

Can anyone confirm these methods? (at least the first one)
Done the 2nd multiple times, same result.

i have same problem , and don't know what to do ?
i flashed 3 different ROMs all stuck on bootanimation .

I'm curious. Did this happen the first time you flashed a rom? When I bought my Moto G (tesco version) it had 4.3 on it, I upgraded to 4.4 via OTA. Unlocked the bootloader, flashed CWM for 4.4 kernel, made backup and flashed various CM builds, booted with no problems.
Now I restored to backup, because of the non-working GPS.
It stucks on CM (the flashed rom) boot screen or the bootloader warning screen?

BBOXPT said:
Can anyone confirm these methods? (at least the first one)
Done the 2nd multiple times, same result.
Click to expand...
Click to collapse
After trying the second one 3 times, I used the TWRP/Fix Permissions method and successfully flashed CM11.

kellerman40 said:
I'm curious. Did this happen the first time you flashed a rom? When I bought my Moto G (tesco version) it had 4.3 on it, I upgraded to 4.4 via OTA. Unlocked the bootloader, flashed CWM for 4.4 kernel, made backup and flashed various CM builds, booted with no problems.
Now I restored to backup, because of the non-working GPS.
It stucks on CM (the flashed rom) boot screen or the bootloader warning screen?
Click to expand...
Click to collapse
I got CM 11 to boot the first time on a dirty flash, but forgot to flash gapps, so got a load of FCs when it loaded up. Since then, any sort of flash, clean or dirty gives me a bootloop.
Even directly flashing boot.img via fastboot doesn't fix it. Reinstalling the stock firmware and starting from scratch doesn't do it either.

[Q] Unable to use Custom Roms

Hi everyone!
I'm the owner of a Moto G 8GB retail.DE xt1032. And i can't install custom Roms.
The phone shipped with good ol' 4.3, and then I flashed the retail.DE 4.4.2 OTA as soon as it came out. But I got tired so I, unlocked bootloader, installed CWM and installed a custom ROM (at the time, CM11, wich I loved).
Then I tried to change the bootanimation (I know, such a lame thing to do) and i wasn't able to boot a custom ROM anymore, even stock based (infusion).
I tried every rom available (cm11, PA, Carbon, AOSP/CodeAurora, Nexus G), and it ALWAYS hangs on bootanimation forever.
If I remember correctly, I had to downgrade to 4.3 Bootloader at that time to install CMW, but since I've had this problem I already reverted to Retail.DE Stock and upgraded via OTA to stock 4.4.2 (so bootloader should have been upgraded to 4.4 too...?).
I still have the 4.3 bootloader .img file on my computer, so should I flash it and try again?

Same here man. We need help!
Sent from my XT1032 using Tapatalk

The latest version of CWM supports 4.4 bootloader.
I was having similar problem, and returning back to full stock and redoing everything solved the problem. As you are already back to stock, I suggest you give it another shot. Good luck...

suhridkhan said:
The latest version of CWM supports 4.4 bootloader.
I was having similar problem, and returning back to full stock and redoing everything solved the problem. As you are already back to stock, I suggest you give it another shot. Good luck...
Click to expand...
Click to collapse
I followed this mans suggestion and it worked for me. I was stuck on nexus g.

I've done it yesterday at least 2 times, with the same result.
I'm really confused, because it shows no error while installing the rom, and it even shows the rom specific bootanimation (which means files were actually copied to /system).
EDIT: just did the whole process again. Return to stock 4.3, update to 4.4.2 via OTA, flash CWM, flash rom (in this case Infusion 4.4.2 Beta (stock 4.4.2 based)) and here i am, stuck @ bootanimation for solid 10minutes.

BBOXPT said:
I've done it yesterday at least 2 times, with the same result.
I'm really confused, because it shows no error while installing the rom, and it even shows the rom specific bootanimation (which means files were actually copied to /system).
Click to expand...
Click to collapse
That's very strange. How did you return to stock? This method worked for me...
http://forum.xda-developers.com/showthread.php?t=2542219 (Note that, you will lose all your data, make a backup on PC)

if i try to flash stock using the downloaded firmware without changing a thing, i end up getting this error message in fastboot:
https://dl.dropboxusercontent.com/u/8675405/Untitled.jpg
what I usually do is delete a few lines in the flashall.bat file:
CALL :fastboot_flash partition gpt.bin
IF %errorlevel% NEQ 0 EXIT /b 1
Click to expand...
Click to collapse
as stated here: http://forum.xda-developers.com/showthread.php?t=2542219 OP point 3a) regarding downgrading.

[Q] My ace plus won't boot after flashing Kitkat roms and even cwm v6

I have 3 android phones, and the oldest one is getting me crazy..
First flashed a JB rom, after a bunch of troubles, finally got it done.
But then this phone had a little problem, i flashed back to stock and send it for repair.
The phone now is returned and reset to GB. And found that there are many Kitkat roms to flash which is really tempting me to do it.
First, i tried to flash Speed rom, with cwm 6.0.3.5. I got Status 7. Flashed back cwm 5.5 and successful in flashing the rom, but it won't boot and stuck in a white screen.
I googled a lot, searched in XDA, found that someone suggested flashed Kitkat with the latest CWM version or TWRP.
But, none of these works on my phone. This is the first time I got stuck in flashing recovery. Both give me a white screen.
Does the CWM version really matter? or it's just my phone's problem which could not work with android 4.4?
Any help would be appreciated..

thyau said:
I have 3 android phones, and the oldest one is getting me crazy..
First flashed a JB rom, after a bunch of troubles, finally got it done.
But then this phone had a little problem, i flashed back to stock and send it for repair.
The phone now is returned and reset to GB. And found that there are many Kitkat roms to flash which is really tempting me to do it.
First, i tried to flash Speed rom, with cwm 6.0.3.5. I got Status 7. Flashed back cwm 5.5 and successful in flashing the rom, but it won't boot and stuck in a white screen.
I googled a lot, searched in XDA, found that someone suggested flashed Kitkat with the latest CWM version or TWRP.
But, none of these works on my phone. This is the first time I got stuck in flashing recovery. Both give me a white screen.
Does the CWM version really matter? or it's just my phone's problem which could not work with android 4.4?
Any help would be appreciated..
Click to expand...
Click to collapse
if your stock rom is indian or chinese flash stock english rom through odin, then you are good to go

ShadowsDie said:
if your stock rom is indian or chinese flash stock english rom through odin, then you are good to go
Click to expand...
Click to collapse
any english rom would be good?

thyau said:
any english rom would be good?
Click to expand...
Click to collapse
any EUROPEAN rom is good, doesnt matter if it is german or irish, must be european
but i recommend any rom from england, as they usually support most of the languages

[Q] help upgrading from 4.1 to 4.3/4

ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.

Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app

Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.

yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.

resolved. thanks guys.

Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.

CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.

jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.

CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.

The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.