Database Info

[Q] Unable to boot G-Tab after updating ClockworkMod inside of ROM Manager.

I have a new G-Tab. I was able to install ClockworkMod and update to the latest version of TnT Lite without an issue.
I stupidly installed ROM Manager and allowed it to install the new ClockworkMod Recovery. I realize now that I should not have allowed it to do that, as cwm 0.8 works better than cwm 0.12.
Now, I am unable to boot my tablet, specifically every time I shut the tablet off it goes into APX mode.
I have installed the APX drivers, the NVidia Tegra SDK, and have used NVflash. Using NVflash I am able to flash back to stock. I have tried using NVflash to flash clockworkmod back to recovery. Despite this, whenever I reboot the tablet, I am right back into APX mode. The only way to get my tablet back to working is to flash back to stock and allow NVflash to boot directly into the stock image. Once I turn off the tablet, I am unable to do anything except run NVflash again to get myself back into stock TnT.
I did not use NVflash with anything other than "nvflash_gtablet_2010110500". I did not use --odmdata. I have tried both Power+Vol(-), Power+Vol(+), Power+both Vols. With any of these methods I am unable to tell any difference in the power state of the tablet. The NVflash batch file is able to reflash the device without issue.
The battery is fully charged and I did not flash without using AC power.
Please excuse my verbosity but I am trying to answer all possible questions and be as specific as possible.
I am unable to boot my GTab after updating ClockworkMod to the newest version through ROM Manager. I have tried every recovery method I have found, and am unable to do anything but boot the stock image. Once I power down the tablet, I am unable to do anything except flash the stock image again. What are your suggestions?

There is an option to install bekit08 from the ROM Manager I think. Down towards the bottom. Once you nvflash into the stock OS have you tried installing ROM manager and letting it reflash the 08 CWM?

Join the limited club
You can nvflash the recovery.img from Bekit, just hold the Volume + when you push enter on your computer's keyboard.
ie...(recovery named bekit.img in this example)
have tablet attached via USB, have tablet in APX mode..
nvflash --bl bootloader.bin --download 9 bekit.img --go
press and hold Volume + on the tablet and immediately press ENTER on the computer to execute the above line.
This will push clockworkmod to the tablet and then boot into recovery. Use recovery to mount USB so you can copy whichever ROM you want to the device....
dismount USB, wipe system (factory reset option in recovery) then install ROM from sdcard.
When completed....and you reboot....of course it won't do anything...
So....while attached and in APX mode...
nvflash --bl bootloader.bin --download 9 bekit.img --go [ENTER]
This reflashes the recovery and boots the tablet.
Voila....VEGAn or TnT-lite installed. Configure, use....never reboot or power off.
If you must power off.....use nvflash to "force boot" the tablet again.
I have to do this on one of mine.
See this post...
http://forum.xda-developers.com/showthread.php?t=903684

muqali said:
There is an option to install bekit08 from the ROM Manager I think. Down towards the bottom. Once you nvflash into the stock OS have you tried installing ROM manager and letting it reflash the 08 CWM?
Click to expand...
Click to collapse
I will try this.
[Edit]
ROM Manager installed, but the only option now is Advent Vega. I understand they are similar but I am not going to try flashing the Advent Vega CM image, especially considering I don't think it will fix the issue. (I have no problem flashing CMW, I can just never get into recovery.) Thank you for the suggestion though!
[Edit #2]
I tried it anyways, despite my reasoning against it. I had options to change to CMW 2.5.1.0, 2.5.1.1, 2.5.1.3, 2.5.1.4 (curiously no 2.5.1.2, which is what caused this all). I was unable to change to these other CMW recoveries, it gave me an error.
tcrews said:
Join the limited club
...
See this post...
http://forum.xda-developers.com/showthread.php?t=903684
Click to expand...
Click to collapse
This is exactly the symptoms I'm experiencing. That's disappointing. I hope the latest two posts or so end up working!

Are you able to boot into the version of CWM that was installed?

My suggestion....if it's within the return period of wherever you purchased.....take it back and swap it out.

NMCBR600 said:
Are you able to boot into the version of CWM that was installed?
Click to expand...
Click to collapse
Nope.
tcrews said:
My suggestion....if it's within the return period of wherever you purchased.....take it back and swap it out.
Click to expand...
Click to collapse
Yessir, these are the words I was expecting to hear. Gonna do that today...

I believe this is easier
I had issues with mine when I first started as well. I found that by using my sd card and renaming the sdcard in the "command" file I was able to recover. I still have issues but I am able to recover. I also still rely heavily on nvflash but I can install crm without forcing it. I am also able to use the power option on the device.
dcom222 original post: http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7

[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

Semi-Bricked my TF101

Just picked up a TF101 and it had the Cryo (whatever it is called) OS with ClockworkMod Recovery v5.8.3.4. The OS didn't pick up wifi on the apps but it is on and logged into the router so I did a reset. Once I reset the TF101, i am stuck at CWM. It won't boot into any OS or anything else. I tried almost everything I found googling (this site and others) but nothing works. I did, however, got the TF drivers for my laptop so I can connect to it but I can't get the USB debug option on (of course).
So what are my options? how do I "unbrick" this thing? is this what some people call it soft-brick as it does boot but there just isn't any OS in there? I tried to put the OS zip file from Asus on a MicroSD but when I went to install zip from sdcard, it i can't get to the microSD to install it. it doesn't find it at all.
what can I do? what are the steps in unbricking this thing? I got this for my dad for father's day (chinese father's day which is TODAY...) and would like to get it to him.
Thanks in advance!

Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.

baseballfanz said:
Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.
Click to expand...
Click to collapse
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?

chivas228 said:
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?
Click to expand...
Click to collapse
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.

baseballfanz said:
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.
Click to expand...
Click to collapse
Sorry to sound ignorant but what's ad and what command (extra code after the .exe) do I add afterwards?

I'd try to flash a ROM via NVFLASH.
You may download it from here, but you must know if your TF101 is WW version, US version or any other. You must also know if your device is SBK1 or SBK2. That depends on the serial number. For example, mine starts by B50 and it's SBK1. If yours is SBK2 then you'll have to take a look at wheelie. If not, take a look here.
http://forum.xda-developers.com/showthread.php?t=1620758
However, I'm not responsible for any damage your device might suffer.
Take a look at that and tell me

here's the endall- easyflash version 0.8.3b whitekidneys just updated it and saved my brick. it'll save yours too. just install it on your computer, along with naked drivers 0.7, put the tf in apx, and flash. literally that easy.

Follow the link to easy flash / nvflash and follow the steps...
http://forum.xda-developers.com/showthread.php?p=26893961
Sent from my Transformer TF101 using xda app-developers app

i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...

thefunkygibbon said:
i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...
Click to expand...
Click to collapse
Try Install different recovery... download and flash the new recovery through CWM..
Sent from my Transformer TF101 using xda app-developers app

Bricked TF101 Need Some Help!

So I recently tried to install a new ROM and I bricked the TF101. So I will try to elaborate the best I can of the situation. The first thing I did was root the tablet which I was able to with the Peri 0.4 -->http://forum.xda-developers.com/showthread.php?t=1681155
I then installed ROM Manager and I was able to install CWM Recovery v6.0.1.3
At this point, I was like I just install zip from sdcard and just load my ROM. I then try to do so, but I kept getting the error:
E: unknown volume path [/sdcard/]
E: Can't mount /sdcard/
I remember reading somewhere here on XDA to refresh the storage so I went to the main menu of CVM recovery --> mounts and storage
format system/catche/data
After that, the TF101 couldn't boot up anymore. I tried the nvFlash fix here: http://forum.xda-developers.com/showthread.php?t=1123429
I do the Volume up + Power and the thing loads into my computer. I followed everything up until I run the download windows batch file, every time I click it nothing happens. The cmd just comes on for a split second then goes away.
So I am now stuck with a $200 tablet that is a paperweight. If anyone has any solution. It would be great!

Dorianking said:
So I recently tried to install a new ROM and I bricked the TF101. So I will try to elaborate the best I can of the situation. The first thing I did was root the tablet which I was able to with the Peri 0.4 -->http://forum.xda-developers.com/showthread.php?t=1681155
I then installed ROM Manager and I was able to install CWM Recovery v6.0.1.3
At this point, I was like I just install zip from sdcard and just load my ROM. I then try to do so, but I kept getting the error:
E: unknown volume path [/sdcard/]
E: Can't mount /sdcard/
I remember reading somewhere here on XDA to refresh the storage so I went to the main menu of CVM recovery --> mounts and storage
format system/catche/data
After that, the TF101 couldn't boot up anymore. I tried the nvFlash fix here: http://forum.xda-developers.com/showthread.php?t=1123429
I do the Volume up + Power and the thing loads into my computer. I followed everything up until I run the download windows batch file, every time I click it nothing happens. The cmd just comes on for a split second then goes away.
So I am now stuck with a $200 tablet that is a paperweight. If anyone has any solution. It would be great!
Click to expand...
Click to collapse
1. You used ROM manager - that is why your tf seems trashed. There is a warning thread stickied at the top of the general section to this effect.
2. Try a cold boot - power plus volume down (like you were booting to recovery) but don't push volume up and let it take you to the cold boot/wipe option.....select boot from Linux.
3. Hopefully that at least gets you into your ROM or recovery.
4. http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
Read this to try and remedy the problem if you can get into the working system
If not and you've blanked the slate then one of the other guys who have used peri or one of the nvflash tools will hopefully guide you through.
Also what version of tf do you have? Are you B70+ or B60 or lower?
If your B70+ then the nvflash guide you used most likely failed as its not designed for your version.
---------- Post added at 08:28 AM ---------- Previous post was at 08:11 AM ----------
http://forum.xda-developers.com/showpost.php?p=29632231&postcount=3
Try white kidneys tool and see if it gets you back to life.

If I had a dollar for every person I have helped unbrick because they used ROM Manager, I could have a Nexus 7, Nexus 10, Note 10.1 and an Infinity.
Anywho, my recommendation is to use EasyFlasher in APX Mode (VOL UP & POWER)
I wrote a guide on how to install a custom recovery and then root and/or ROM here:
http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
You can skip over the backing up your current ROM most likely, just install a custom recover (if you choose CWM, do NOT use ROM Manager to update it).
I personally like TWRP much better myself.
Hope this helps!

I use the EasyFlasher and it worked brillantly.
Thanks!