[Q]Recovery Inaccessible and must boot abnormally - Eee Pad Transformer Q&A, Help & Troubleshooting

Whenever I try to access recovery, the bootloader freezes at 'Booting recovery kernel image. I am running the newest Clockworkmod Touch recovery.
Also, when I try to boot normally it freezes on the bootscreen.
It won't interface with the computer when I do boot it through the bootloader.
I'm running Revolver 4 RC0, and want to change roms, but nobody uses nvflash anymore so I'm stuck here until I get help.
So, can anyone help?

If you can do NVFlash with your TF, Team Rouge has an NVFlash version

Alright, I'll try that.

Won't work as tablet does not show up in device manager of my pc.
Update: Duh, nvflash doesn't need normal usb. Working like a charm. Thanks!

Related

TF101 B80 stuck on ASUS boot screen

My tablet recently froze when i was not able to turn off my wifi in the settings of my Revolution 3.1 ROM. I have tried to boot up since this and now it is stuck on the ASUS boot screen with the circle.
I am able to boot to cwm 3.2.0.1 and wipe data/flash the rom again, but no matter what I do, it is stuck on the same screen.
I recently tried doing a cold boot and a factory reset/wipe data in the recovery menu, but when i choose to wipe data, after it loads the recovery kernal image, all i get is the android triangle.
What else can I try?
I have the same problem with my TF101. Are you able to find a solution to your problem.
shutchins said:
My tablet recently froze when i was not able to turn off my wifi in the settings of my Revolution 3.1 ROM. I have tried to boot up since this and now it is stuck on the ASUS boot screen with the circle.
I am able to boot to cwm 3.2.0.1 and wipe data/flash the rom again, but no matter what I do, it is stuck on the same screen.
I recently tried doing a cold boot and a factory reset/wipe data in the recovery menu, but when i choose to wipe data, after it loads the recovery kernal image, all i get is the android triangle.
What else can I try?
Click to expand...
Click to collapse
Maybe a problem in kernel or /system partition, try to flash the ROM again may fix the problem.
Same......
tingtan said:
Maybe a problem in kernel or /system partition, try to flash the ROM again may fix the problem.
Click to expand...
Click to collapse
I have the same problem.....
I rooted, installed Rom Manager to get CWM Recovery installed and then flashed the new CyanogenMod 10 - B1 ♦ K.A.T. As soon as I restarted, after it appeared that the flash went fine, it hung at the boot screen - not frozen just wont go any further.
I tried rebooting by holding the power button, I tried re-flashing both the CY 10 and the original Rom and tried "restoring" my backed up rom.
I have tried recovering through Easy Flasher but I don't think my PC is seeing the transformer properly.
I have ADB drivers installed but because the TF dose not boot properly it dose not seem to get there.
I have let the battery drain as some report a resolve when they get it to power down all the way but as soon as I plug it in and power it up it goes back to the boot screen and stays there.
Please help as I cant afford to lose this pad (yes I knew the risks).
Chaos-sa said:
I have the same problem.....
I rooted, installed Rom Manager to get CWM Recovery installed and then flashed the new CyanogenMod 10 - B1 ♦ K.A.T. As soon as I restarted, after it appeared that the flash went fine, it hung at the boot screen - not frozen just wont go any further.
I tried rebooting by holding the power button, I tried re-flashing both the CY 10 and the original Rom and tried "restoring" my backed up rom.
I have tried recovering through Easy Flasher but I don't think my PC is seeing the transformer properly.
I have ADB drivers installed but because the TF dose not boot properly it dose not seem to get there.
I have let the battery drain as some report a resolve when they get it to power down all the way but as soon as I plug it in and power it up it goes back to the boot screen and stays there.
Please help as I cant afford to lose this pad (yes I knew the risks).
Click to expand...
Click to collapse
Same issue, I can't get my computer to recognize the tablet to push any files to it, and I can't mount it from TWRP. What can I do?
Have you guys tried wiping out before flashing? Wipe out the cache,system, and all other partitions.

[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)

[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
After lots of searching and reading, I found a few help threads that offered suggestions for those unable to boot, but they all require adb. My understanding based on the adb tutorial is that it requries configuration within the Android OS, and for the device to be running, which mine does not. And from what I've read, the c20 serial number isn't compatible with nvflash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
edit: to clarify, I never setup ADB, which makes me think that solutions like this won't work: http://forum.xda-developers.com/showthread.php?p=25636698#post25636698
Hello cfbauer,
Did you try this driver pack? after 1st remove all you transformer drivers?
http://forum.xda-developers.com/showthread.php?t=1514942
If you install this, then you can check with adb if there is communication possible with your transformer. if you connect it, is there any life on your pc when you start your TF?
or volume + and power to put tablet in apx mode and see if then the apx driver installs. If it does then try the brks rootkit v7.1 to see if you can install cwm with this tool....maybe your refurbished TF is an old B40 to 70).
unless this is what you already did......
dont forget to disable spashtop and asys sync on your pc.......
Well I managed to get ADB setup, I think. I'm new to this, but when I attempt to boot into recovery, and do "adb devices" I get "0123456789ABCDEF offline".
I'm a little hesitant to try nlheiz's suggestion of brks rootkit v7.1 as it says it's for a serial number that's older than my device is. nlheiz, can you confirm this is safe? Or can someone else suggest an alternate method of getting my 2 week old Transformer to a useful state? I definitely appreciate the help.
-Chris
edit: I just read this
The only thing that differs between SBK1 tablets and SBK2 tablets is the use of NVFlash. SBK2 cannot use NVFlash, so if you end up botching both your recovery and your ROM, and cannot boot into either, then you are SCREWED, so I would suggest reading everything before attempting to mod your device if you are an SBK2 owner.
Click to expand...
Click to collapse
There is no emoticon to convey how sad I am right now
edit2: I'm looking at trying this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html since it appears to be able to fix the issue I'm having.
edit3:attempting the guide posted in edit2 is giving me a "error:device offline" on step 6 when I try the adb push command
edit4: I can't seem to download brk Universal Rootkit 7.1 as neither download link is working
Does anyone have a suggestion? I'd appreciate it. Or is my device totally dead and I'm just screwed?
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Thanks for your response. I get "0123456789ABCDEF offline" when I type adb devices when I boot into recovery mode, which isn't actually recovery mode since the system it hangs when I try to boot into recovery mode.
cfbauer said:
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
Click to expand...
Click to collapse
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
baseballfanz said:
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
Click to expand...
Click to collapse
OMG it worked! I'm back baby! So exited. Thanks for your help! I suppose this means my Transformer is an SBK1. Nice.
To answer your questions if you're curious, I used RecoveryInstaller. It was CWM, but an older version, my mistake. I ran into the random reboots issue, but the version of CWM recoveryInstaller used wasn't compatible with Aroma, which was required to install a custom kernel.
I don't remember the exact text on screen when I try to load into recovery, but I believe it was something like "booting into recovery mode."
And yes, I did try a different usb port for adb, it didn't work. Thanks for the suggestion though!
Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Worked! Thanks for the heads up!
By the way, you don't need Aroma to install a custom kernel with AOKP. Since I utterly refuse to flash touch recovery (no ext-sd support) I can't use aroma. The classic way is to go grab the .zip of the kernel (I recommend Testymehics or Guevor's test kernels) out of development. Clear cache, then flash as if you were flashing a rom, no aroma required.

[Q][SBK2]Can't access/flash recovery (+random reboots&freezes)

Hi everyone, I've got a BIG problem with my sbk2 TF101.
I don't know why but I cannot access the Recovery. I don't know if it is actually installed or not, but I cannot access it nor I can flash it with CWM Manager or Recovery Installer
-When I restart, it simply stucks at the EEE logo.
-I cannot boot in recovery with any of the apps made for this;
-Every time I want to start the tablet, I need to start it using cold-boot (first, vol- and power, and then vol+), because it seems to be always starting in recovery.
-Without recovery I cannot flash a new recovery or a new rom, and I'm stucked with an AOKP cooked in the firsts days of may (I don't remember the name)
-I've got random and frequent reboots, freezes, and can't do something for more than 5 min because the tablet freezes.
-Standard voltages.
-My tablet is not recognized when I plug it in Windows or Mac OSX, didn't try with Ubuntu.
Please help me!
Thank you very much in advance for your great help.
Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.
Thing O Doom said:
Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.
Click to expand...
Click to collapse
First of all, thanks a lot for trying helping me.
The problem is that I don't know how to use ADB or wich commands should I use or where I could find the boot.img. Using a virtual terminal means running a trminal on the tablet? Can I use the internal memory instead of an SD card? I can confirm I've still got root, by the way.
Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.
wanzer said:
Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.
Click to expand...
Click to collapse
Use PERI/my easyflasher tool to reflash recovery from nvflash.
Read more here:
http://forum.xda-developers.com/showthread.php?t=1688012
Hello guys, I have a problem with my tf101! is brick, and only goes with apx.provo easyflasher wheelie but returns error when it finishes loading bootloader towards the closed dell'applicazione!
sorry for the English, are Italian
I figured out that the OP had the ROM manager bootloop :/
Romyfra - is it a Tf101 Wifi-only or a Tf101G, if it's a Tf101 then you can use NvFlash to reflash it
I brick my wifi tf101 with serial bcoka ..., ICS v24ww 1.6e 4.0.3 I can not even come out with a wheelie! This is what I done, done correctly with the root easyflasher 0.4, after I stupidly installed netformer 1.6 (that idiot) and restart it disappeared with the cmw.ho riflashato easyflasher and end of proceedings, the tab will not light! is only apx, so no recovery! the problem is that when I start wheelie crash and does not pass to nvflash! is possible that the flash is corrupt?? as a last resort if you think I'll send you notice of changes in the RMA? ICS had no stock and cmw più.possono dump and see what happened or there is no trace?? thanks

[Q] TF101 Wont boot

I have searched this forum and other, but have not have not been able to find a solution to my problem. A while back I flashed a build of AOKP and rebooted just fine. I saw that a new version of CWM was out available to flash, so I immediately downloaded and flashed it. This was a mistake. Now, for some reason, I cannot boot in either CWM or my Rom. When I turn the power on it sits at the ASUS screen and when I try to get into recovery it displays the text and says to press vol +, which I do, and hangs at that point. Is there any way to flash a new recovery at that point or do I basically have a very expensive paperweight?
Hi.
You can use my nvflash/Wheelie to reflash CWM.
If you are unfamiliar with nvflash or Wheelie you can use my EasyFlasher tool.

[Q] Ubuntu through tubuntu stuck in boot loop, can't enter adb or get out of loop

So, as the title says, i stuck myself in a boot loop after installing ubuntu via the TUbuntu method. I can't access adb, and therefore can't reflash or anything. does anyone have any suggestions about what to do? i've tried everything!
Thanks,
prot0n
_prot0n_ said:
So, as the title says, i stuck myself in a boot loop after installing ubuntu via the TUbuntu method. I can't access adb, and therefore can't reflash or anything. does anyone have any suggestions about what to do? i've tried everything!
Thanks,
prot0n
Click to expand...
Click to collapse
Help, Anybody???
Try flashing an NVFLASH ROM to completely return your TF to stock, NVFLASH uses APX Mode which is available no matter what you have done ROM wise (So long as your TF is SBK1)
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS
Or Easyflasher to flash TWRP recovery and a ROM back to it, also in APX mode (VOL UP & POWER ON)
http://forum.xda-developers.com/showthread.php?t=1688012

Categories

Resources