[Q]Need Guidance in Installing Rom for TF201 - Asus Eee Pad Transformer Prime

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

Related

[Q] Help with TF201! (think I might've bricked my prime)

hey guys, I don't know what happened to my Prime, but this is what I did:
I was on a Nexus 7 ported ROM and it was running fine. Tried to flash PARANOID ANDROID and failed. So I tried to flash Androwook, and now it's stuck on the splash screen. The only thing I can do is boot to the recovery (CWM). Is there anyway I can fix it? Is it bricked?
I am going to assume you have ADB working on your computer. Just download a new rom, your choice, and using the command
adb push C:\NAMEOFFILE \sdcard\Downloads
you don't have to put the file in the downloads folder, just an example. May need Gapps as well. Wipe and flash as normal.
JC0406 said:
hey guys, I don't know what happened to my Prime, but this is what I did:
I was on a Nexus 7 ported ROM and it was running fine. Tried to flash PARANOID ANDROID and failed. So I tried to flash Androwook, and now it's stuck on the splash screen. The only thing I can do is boot to the recovery (CWM). Is there anyway I can fix it? Is it bricked?
Click to expand...
Click to collapse
Read post 2 of the androwook thread and get twrp installed.
Make sure you do the ICS to JB upgrade before flashing a Jellybean TWRP. The correct bootloader is the most important part about twrp
And while you still have a chance and are still on the ICS bootloader do this. http://forum.xda-developers.com/showthread.php?t=1774352
It wont work once you have Jellybean

Prime stuck on ASUS splash screen, what now?

I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Official CM10 nightlies are still made for the ICS bootloader, as you discovered. Until they update, you're better off downloading the unofficial builds here.
thefsfempire said:
I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Click to expand...
Click to collapse
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
foxhound08 said:
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
Click to expand...
Click to collapse
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Voyager2k said:
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Click to expand...
Click to collapse
No i can't access anything.
foxhound08 said:
No i can't access anything.
Click to expand...
Click to collapse
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
dunngh said:
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
Click to expand...
Click to collapse
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
eec_ said:
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
Click to expand...
Click to collapse
same here as well so at least you guys arent alone does show up as an apx device but not sure how useful that could be at the moment its just a paper weight just need someone to write an automated recovery from apx mode to flash the appropriate files if thats even possible
Exact same problem. Still no fix?
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
swatsbiz said:
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
Click to expand...
Click to collapse
Your problem was different to theirs and you have been fixed in the Androwook thread. Yours was caused by the pad firmware not installing properly the first time and freezing your screen and buttons.
I have the same problem...
hbhorat said:
Exact same problem. Still no fix?
Click to expand...
Click to collapse
any fixes to this ?
sraghav20 said:
any fixes to this ?
Click to expand...
Click to collapse
Me too.. looking for a fix on this with no luck so far

MAJOR ISSUE evo 4g lte will not boot even though was restored from backup

im having major issues here with my device it all started with me trying to flash it to cynogenmod 10 which apparantly my device has the s-on so i was stuck in the cmod boot logo, luckily i backed up my device prior to that with the stock rom and everything so i restored successfully back to my stock rom. then i was reading along some forums to see what the problem was and i came accrosss this forum "http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-s-h-boot-1-15-a.html" which gave me a few options on how to flash kernels with the right one that will work with cynogen mod, i chose option 1 because it said it is recommended which the steps were to take the rom "boot.img" file and copy it over to the android sdk platform tools folder and open up a cmd and i flashed the rom "boot.img" which according to the forum that contains the kernel that belongs with that rom i did what it ask went to fastboot mode and typed in fastboot boot boot.img, which succeeded, when i rebooted the device it boots up acting like it is trying to open up recovery mode which is twrp recovery, after that it does nothing it blacks out and a little white bar flashes on top of the screen from time to time then it turns off and reboots and do same cyckle, i attempted to go back to twrp and restore my stock rom which said it succeeded but when i rebooted it did the same thing acted like it was tryning to boot up to recovery being inforemd with those red letter about developmental purposes only stuff, so i factory rested my device wiped dalvik cache and cache and even wiped the system rom and restored my back up with stock rom and nothing works still, please help i am stuck please!!
You probably need to pull the boot.img from a stock ROM and send it via fastboot since your trying to go back to your stock backup.
thanks, but now i got the cynogen mod 10 to boot up now for some reason the touch screen does not respond to the touch neither does the capacative touch buttons work either do you have any idea what it could be?
If you have the 3.16 OTA update then you're touchscreen firmware is incompatible. If this is the case your stuck with 3.16 based roms. Cm will not work for you.
Sent from my EVO using Tapatalk 2
well the 3.16 ota update is that the latest one?
Yes. If you have the 3.16 update the only way your going to get cm to work is to s-off and downgrade you're tp firmware.
Sent from my EVO using Tapatalk 2
do you know were i can find these recourses on how to do this? i know that it has something to do with dirtyracun or something like that but i didnt really didnt understand their website on how to s-off and how to i downgrade my tp firmware
droidman89 said:
do you know were i can find these recourses on how to do this? i know that it has something to do with dirtyracun or something like that but i didnt really didnt understand their website on how to s-off and how to i downgrade my tp firmware
Click to expand...
Click to collapse
I'll try..
First and foremost you need to go here http://themikmik.com/showthread.php?13192-RADIOS-RECOVERY-FLASHABLE-Jewel-Radio-Collection&p=220556&viewfull=1#post220556 and download the boot.img only for whatever version of the stock rom your backup is.
Put it in your sdk tools and open a command prompt and fastboot flash boot boot.img
Go to twrp recovery and WIPE cache, dalvik, factory reset, and system.
Restore your stock backup.
Reboot.
If you can get back to your stock rom, then you should read up on dirty racun or possibly facepalm to gain s-off if you want to run cm.

Soft-bricked via botched kernel :(

Ok so I searched the forums before this just to let you know.
I wasn't thinking and the wrong kernel got installed as the title says. So, I got into a bootloop (expected). It hits the fan after my next step :'(
I go to bootloader, then to recovery, start up TWRP, then screen goes blank and goes back to the htc bootscreen.
The odd thing is, it now has that disclaimer on the bottom for normal boot sequence.
I have attempted flashing other recoveries, erasing my cache, fastbooting roms, and fastbooting kernels. I assume my choices are limited with S-On since most of the fastboot commands return "remote:not allowed".
Do I have to wait for a RUU?
Thank you for your time in advance
UPDATE:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
IF YOU FOUND THIS BY SEARCHING
1. Fast boot flash recovery "recovery file" (I used clockwork non touch)
2. Fast boot erase cache MUST!!!
3. Boot recovery
4. Sideload Rom via adb
seamarshall said:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
Click to expand...
Click to collapse
Glad to hear you got it working again. Anytime you install a custom ROM though, you will see the disclaimer on the bootscreen. It isn't a big deal software wise though, it just looks ugly. I'd consider that a minor inconvenience for using a better ROM without the bloat.

[Q] Can't mount partitions

Hey guys,
I got a TF201 tablet.
I was trying to install the crombi-KK rom on it.
After several hours of trying and failing I found out that I had to install TWRP 2.8, but to do so, I needed to run the hairy bean boot loader.
When I figured that out, I shut down the device, and then nvflashed it back to the stock FW.
When the flash finished, the tabled was no longer booting (weird because I have never seen it failing after nvflashing the stock firmware).
After nvflashing it, the bootloader when back to ICS. I installed flashed TWRP using fastboot, when I started the recovery image I got a message asking for the password for data. After doing some research on that I figured that I needed to format the data partition for it to boot again.
Once that was done, the device boot OK to the stock ROM. I tried upgrading back to JB using the asus upgrade procedure and the tablet rebooted back to ICS.
I tried to install the stock JB firmware using twrp, it says it completes OK but when I reboot the tablet it goes back to ICS.
I then flashed several other recovery images, every time I start the tablet in recovery I get a message saying that it cannot mount the /cache partition and others.
If I try to flash any ROM using any recovery sometimes it says it worked but the tablet boots back to ICS, some other times and says it failed and goes back to ICS.
I used to have a BAT that helped me formatting the partitions and then to flash blobs one by one, but I deleted it because I thought I was never going to need it anymore.
I was wondering if what partitions does this tablet has (EX: recovery, boot, app, etc).
Is there any toolkit that formats the partitions and flashes then using stock JB images extracted from the blob files?
Jcascantez said:
Hey guys,
I got a TF201 tablet.
I was trying to install the crombi-KK rom on it.
After several hours of trying and failing I found out that I had to install TWRP 2.8, but to do so, I needed to run the hairy bean boot loader.
When I figured that out, I shut down the device, and then nvflashed it back to the stock FW.
When the flash finished, the tabled was no longer booting (weird because I have never seen it failing after nvflashing the stock firmware).
After nvflashing it, the bootloader when back to ICS. I installed flashed TWRP using fastboot, when I started the recovery image I got a message asking for the password for data. After doing some research on that I figured that I needed to format the data partition for it to boot again.
Once that was done, the device boot OK to the stock ROM. I tried upgrading back to JB using the asus upgrade procedure and the tablet rebooted back to ICS.
I tried to install the stock JB firmware using twrp, it says it completes OK but when I reboot the tablet it goes back to ICS.
I then flashed several other recovery images, every time I start the tablet in recovery I get a message saying that it cannot mount the /cache partition and others.
If I try to flash any ROM using any recovery sometimes it says it worked but the tablet boots back to ICS, some other times and says it failed and goes back to ICS.
I used to have a BAT that helped me formatting the partitions and then to flash blobs one by one, but I deleted it because I thought I was never going to need it anymore.
I was wondering if what partitions does this tablet has (EX: recovery, boot, app, etc).
Is there any toolkit that formats the partitions and flashes then using stock JB images extracted from the blob files?
Click to expand...
Click to collapse
Join our irc sometime, we can give much better support there ..
Channel ##crombi-kk
Network Freenode
Thx Josh

Categories

Resources