So, I was able to successfully unlock my bootloader, got TWRP 2.6 on it, and put a few different ROMs on my machine; however, I have yet been able to install a ROM and get it to move past the boot animation.
I have tried the latest nightly ROMs for CyanogenMod 10.1 and 10.2 for my TF201, both of which get stuck in CM's boot animation. I just tried the same with the newest Baked ROM, only to be stuck in its boot animation as well.
I'm trying to figure out if there was something I forgot to do. I have been able to revert to a backup of my stock Jellybean 4.1.1 that I stored using TWRP, but haven't been able to use anything else.
Are there any thoughts on this? Have I missed something? I was able to use the unlocker utility and each boot offers the confirmation in the top-left that my bootloader is unlocked. I am able to enter TWRP from the recovery mode. Shouldn't it be as simple as selecting a ROM's zip archive and installing it from TWRP?
Have you done a full wipe before installing, including cache and dalvik cache partitions?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Try installing twrp 2.5. AS I just read in another thread there are problems with 2.6..
Sent from my MB526 using xda app-developers app
Factory reset
After flashing CM 10.1 nightly last night i had the same issue. I booted into my recovery console (flatline cwm) and performed a factory reset. This seemed to clear whatever issue was bothering the tablet. Still sat there for about five minutes on the animation after the reset but then progressed into setup.
Doubt if it makes a difference but mine was connected to the dock too.
If you're still stuck the method that worked for me yesterday was:
Used Flatline CWM as the recovery, installed using fastboot
Used an external memory card to copy the relevant zip files to my sdcard, recovery couldnt find them otherwise using adb push
Installed from zip using Flatline CWM
Installed gapps using Flatline CWM
Booted, got the issue you had
Booted into recovery, performed a factory reset
Told recovery to restart the machine
Booted into setup screen after loading for a few minutes
Related
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?
I have a T-Mobile Samsung Galaxy S2 SGH-T989 and tried to install cyanogenmod 10.2, but I can't start it, it gets stuck in the cyanogenmod splash screen and doesn't get any further.
Here's what I did originally: I flashed clockworkmod (via Odin) and booted into recovery. I then installed the cyanogenmod zip file that I had copied onto the sdcard.
When it failed to boot, I tried several things: I flashed TWRP (via Odin) and then did a factory reset and system wipe, installed cyanogenmod (from TWRP) and did the factory reset again. Same problem, the system will get stuck in the boot loop. I also tried an earlier version of cyanogenmod, same problem.
I am quite sure that I downloaded all the right files for my device. I searched online and saw other people who had that problem, and solved it by wiping the cache/data after the install. This didn't work for me.
I don't know what else to try, so please reply if you have any ideas!
Thanks :fingers-crossed:
Not sure bout it but flash only the cm kernel via cwm then reboot to recovery again n factory reset then install the Rom all the best
Sent from my Xperia Live with Walkman using xda app-developers app
Hi i rooted n installed CWM touch recovery on my ASUS TF101 tablet.
The process was not simple as i had to make several flashing attempts before the TF101 booted into CWM recovery.
Once i got CWM recovery working i tried flashing it to a CyanogenMod ROM cm-9.1.0-tf101.zip (stable)
I made sure i wiped Dalvik Cache , wipe data factory reset , wipe cache partition.
After that I renamed the CM Rom to update.zip n then choose apply/update.zip using CWM recovery.
Well the first flashing didnt work bc it just kept on loading to the old stock rom.
After several attempts my TF101 did finally load into CM mod.But the screen kept on loading for 30mins so i restarted the device.
i tried clearing the Dalvik + cache partition n factory reset it again.
But when i rebooted it just goes into CWM recovery.
Ive been trying to even flash it back to stock rom but it just wont boot to the rom.
Could anybody help me plz ? Why did i have to flash my TF101 several times b4 in order to get the ROM to load ?
Could there be something im missing ?
Extra Info
Windows does recognise my TF101 when its plugged in. But in device manager it only comes up as "Transformer" under Universal Serial devices.
I tried using adb to push the stock ROM to my TF101 n then update it but it still wont boot to the rom. Just CWM recovery.
SuperSU was installed b4 i flash the CM rom.But now when i turn it loads to CWM only. Heck i cannot even turn it off
Im stuck dunno what to do