[Q] TF201 Wont boot after flashing new rom - Asus Eee Pad Transformer Prime

Hello,
I was running the stock ROM, but decided to flash the Energy ROM. I first flashed the JB.4.2.1.Bootloader.and.partitions.zip and then the new ROM. However it just got stuck at the ASUS splash screen. After several unsuccessful attempts I flashed the JB.4.1.1.Bootloader.and.partitions.zip and restored by backup, only for it get stuck in the ASUS splash screen again. I tried to flash the stock 4.1.1 from ASUS, but it fails every time along with any other custom 4.1.1 ROMs I try!
Can anyone help me? I can have still access to fastboot and TWRP. I have been searching these forums for days with no luck.
Edit: the only time I've gotten past the splash screen is if i flash the JB.4.2.1.Bootloader.and.partitions.zip then restore my stock 4.1.1 backup, but then it just hangs in the boot animation. I tried hen to flash the 4.1.1 stock over it only for TWRP to say it has failed.

is your boot loader unlocked ?
careful with TWRP and the JB 4.2.1 bootloader. You can only use the custom TWRP specifically made for the JB 4.2.1 bootloader.

Related

[Q]Need Guidance in Installing Rom for TF201

Father wants JB on his TF201, I thought this shouldn't be difficult doing since I had a droid, and a galaxy nexus before and it was simple. He for some reason already had it unlocked, so that took out one step.
I flashed TWRP (http://teamw.in/project/twrp2/93) for ICS since he was still on ICS. Booted into Recovery, then flashed Energy (http://forum.xda-developers.com/showthread.php?t=1982156).
Now it just sits at the splash screen.
Afterwords I did flash or install nvflash so now it says AndroidRoot 9.4.3.20r01 in the top left when booting... but Not sure what that gets me at this point.
I can boot up into TWRP and re flash Energy but it still doesn't work. Wiped Cache / Wiped system. So what do I need to do to get this working now?
bump
dilutedq said:
Father wants JB on his TF201, I thought this shouldn't be difficult doing since I had a droid, and a galaxy nexus before and it was simple. He for some reason already had it unlocked, so that took out one step.
I flashed TWRP (http://teamw.in/project/twrp2/93) for ICS since he was still on ICS. Booted into Recovery, then flashed Energy (http://forum.xda-developers.com/showthread.php?t=1982156).
Now it just sits at the splash screen.
Afterwords I did flash or install nvflash so now it says AndroidRoot 9.4.3.20r01 in the top left when booting... but Not sure what that gets me at this point.
I can boot up into TWRP and re flash Energy but it still doesn't work. Wiped Cache / Wiped system. So what do I need to do to get this working now?
Click to expand...
Click to collapse
since you have ics bootloader (nvidia logo on bottom center of splash screen) you need to install a rom that has the jellybean bootloader. easiest way to do this is follow this post. After that you can install any jellybean rom that requires official bootloader.
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212

Stuck at first boot screen

When trying to flash a stock rom on a rooted i9100 with Mobile Odin Pro 3.65 it gets stuck at first boot screen.
Even when trying to flash stock 4.0.3 and also with stock 4.1.2 roms it still does the same thing: it gets stuck at first boot screen. Even if i check the wipes and everything. Any information on this?

[Q] Stuck in recovery mode (TWRP)

Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
fr0z1k said:
Hey guys,
I recently flashed a new 4.3 rom to my S3 (Imperium 21.0).
After a while i decided to update the kernel to Googy Max, downloaded it from OTA and went to install it via TWRP, after installing the galaxy decided it wouldn't boot and just returned to the recovery all the time, i thought it must be the broken kernel and re-flashed the rom, everything was fine until i went back to the recovery (to backup the rom), after i finished backup and tried to restart my S3 the same happens, the galaxy just reboots back to the recovery, and the only way i found to get of it is to re-flash the rom :/
I don't want to re-flash it again... Any ideas what can i do?
Click to expand...
Click to collapse
Can close thread, after installing another recovery via Odin it was fixed

4.4.2 Stuck at boot screen

For some reason I am unable to flash to any KitKat Roms; I can however flash 4.3.
I have tried CWM 6.0.4.3 and TWRP 2.7 both have the same effects.
I did flash Carbon once and and it worked for about a week and than my phone froze then rebooted and was stuck at the boot screen. The only way I could fix this was by flashing a 4.3 rom.
I would like to be able to enjoy KitKat..
Thank you in advance for any and all help!

Bricked?? Stuck at samsung logo screen for 1 sec then reboots.

Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.

Categories

Resources