So as the title suggest, I am in a boot loop. I was running TWRP project 2.2.1.4 (I think or something like that) and downloaded the latest blob from TWRP's website (openrecovery-twrp-2.2.2.1-tf201-JB.blob) and booted into fastboot mode and flashed it through terminal. It said everything was good and I rebooted no problem. I hit the menu to reboot into Recovery (from the Power button menu) and it threw me into a bootloop at the startup screen. I can't get into recovery, but I think I'm able to get into APX mode. I have gone through the entire procedure of nvflash and have everything backed up numerous times... Any ideas on how I can get my Prime back up and running? I currently have Androwook JB edition installed and was about to install the latest deodexed stock ROM listed in the Development section.. Please help.
andrewjt19 said:
So as the title suggest, I am in a boot loop. I was running TWRP project 2.2.1.4 (I think or something like that) and downloaded the latest blob from TWRP's website (openrecovery-twrp-2.2.2.1-tf201-JB.blob) and booted into fastboot mode and flashed it through terminal. It said everything was good and I rebooted no problem. I hit the menu to reboot into Recovery (from the Power button menu) and it threw me into a bootloop at the startup screen. I can't get into recovery, but I think I'm able to get into APX mode. I have gone through the entire procedure of nvflash and have everything backed up numerous times... Any ideas on how I can get my Prime back up and running? I currently have Androwook JB edition installed and was about to install the latest deodexed stock ROM listed in the Development section.. Please help.
Click to expand...
Click to collapse
Follow these steps... http://forum.xda-developers.com/showpost.php?p=32535307&postcount=2
Then install TWRP for JB & flash the ROM...
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
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
So here's what happened: I had TWRP and HDX Nexus ROM successfully installed for a while, but I decided I wanted to go back to Fire OS and update to the newest version. I used TWRP to flash the stock backup I had saved, and then I used the KFHDX Tool to re-enable OTA updates. I got the OTA update to .3.2.5, and when the system rebooted it booted into TWRP automatically to flash the update. That kinda surprised me, since I thought doing an OTA update would wipe out any custom recovery, but I guess not. The Kindle booted and completed the .3.2.5 installation, then downloaded the .4.1.1 file. At this point it tried to reboot but hung on the grey Kindle Fire logo. I held the power button to restart it and it booted normally, but the update was unsuccessful. I tried it a couple more times for good measure, with the same result each time. I tried following the instructions here to downgrade to .3.1.0, but it said it couldn't validate the update file. I tried doing a factory reset, but it hung on the grey Kindle logo and was unsuccessful.
Basically, I think my recovery got messed up. I tried the adb reboot recovery command from my computer and it caused the Kindle to hang on the grey logo, so I'm guessing that's what's causing my issues. Not sure where to go from here.
iNTRCPT4lyfe said:
So here's what happened: I had TWRP and HDX Nexus ROM successfully installed for a while, but I decided I wanted to go back to Fire OS and update to the newest version. I used TWRP to flash the stock backup I had saved, and then I used the KFHDX Tool to re-enable OTA updates. I got the OTA update to .3.2.5, and when the system rebooted it booted into TWRP automatically to flash the update. That kinda surprised me, since I thought doing an OTA update would wipe out any custom recovery, but I guess not. The Kindle booted and completed the .3.2.5 installation, then downloaded the .4.1.1 file. At this point it tried to reboot but hung on the grey Kindle Fire logo. I held the power button to restart it and it booted normally, but the update was unsuccessful. I tried it a couple more times for good measure, with the same result each time. I tried following the instructions here to downgrade to .3.1.0, but it said it couldn't validate the update file. I tried doing a factory reset, but it hung on the grey Kindle logo and was unsuccessful.
Basically, I think my recovery got messed up. I tried the adb reboot recovery command from my computer and it caused the Kindle to hang on the grey logo, so I'm guessing that's what's causing my issues. Not sure where to go from here.
Click to expand...
Click to collapse
If you have a thor (7" HDX) try flashing this recovery. It's from stock 3.2.6 but proven to be compatible with 3.2.5. You can use Flashify to install the recovery image. Note there's always some risk messing with recovery. Also assuming you can boot into 3.2.5 and are not stuck at the grey Kindle logo.
Thanks, that worked great. Now that the bootloader is unlocked, I got cold feet about going down the OTA path anyway. I was able to successfully roll back to .3.1.1 after I flashed the .3.2.6 recovery.
iNTRCPT4lyfe said:
Thanks, that worked great. Now that the bootloader is unlocked, I got cold feet about going down the OTA path anyway. I was able to successfully roll back to .3.1.1 after I flashed the .3.2.6 recovery.
Click to expand...
Click to collapse
Thanks for the update! Glad it worked out.
Hello, I need a little advice on getting my phone working again. I got a new Ramos MOS1 Max today and rooted it via Kingo PC software. I checked to make sure it was rooted using RootChecker and it said it was rooted. I was reading up on what to do next and some sites said the next thing you must do is to make a backup of your phone via TWRP. I installed the software and then attempted to use the "reboot and create backup" functionality. The phone rebooted and I was in the Android system recovery menu. I didn't see anything like what TWRP was supposed to show, so I just rebooted via the standard recovery screen method. Now when I try to start the phone, it gives me a logo, then ARMPHONE and it hangs on that.
I've tried wiping my cache partition via recovery menu and rebooting, but no dice. Next they suggested to do a wipe data/factory reset, and since I just received the phone today, I decided to try that. After doing that via system recovery menu it still wouldn't boot past the ARMPHONE screen. I don't have a lot of experience with rooting and modifying Android devices, is there something I can do to fix this? I've installed the android SDK tools for my version of android (5.1 I believe), but I don't know how to proceed. Is there a stock image I can use for this phone, or can I just use a vanilla android image?
Thanks in advance.
sphericon said:
Hello, I need a little advice on getting my phone working again. I got a new Ramos MOS1 Max today and rooted it via Kingo PC software. I checked to make sure it was rooted using RootChecker and it said it was rooted. I was reading up on what to do next and some sites said the next thing you must do is to make a backup of your phone via TWRP. I installed the software and then attempted to use the "reboot and create backup" functionality. The phone rebooted and I was in the Android system recovery menu. I didn't see anything like what TWRP was supposed to show, so I just rebooted via the standard recovery screen method. Now when I try to start the phone, it gives me a logo, then ARMPHONE and it hangs on that.
I've tried wiping my cache partition via recovery menu and rebooting, but no dice. Next they suggested to do a wipe data/factory reset, and since I just received the phone today, I decided to try that. After doing that via system recovery menu it still wouldn't boot past the ARMPHONE screen. I don't have a lot of experience with rooting and modifying Android devices, is there something I can do to fix this? I've installed the android SDK tools for my version of android (5.1 I believe), but I don't know how to proceed. Is there a stock image I can use for this phone, or can I just use a vanilla android image?
Thanks in advance.
Click to expand...
Click to collapse
You can find the firmware here http://4pda.ru/forum/index.php?showtopic=783029