Related
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
Using a viewsonic G Tablet, I had initially loaded the clockwork mod. was working fine. Flashed a few ROMs over the last week. Currently running Cyanogen Mod7 Accidentally wanted to see what the ROM Manager app was about. Went and flashed the Clockword mod. Since then, I'm not able to go back into Clockwork mod. Everytime I try to reboot using the Power and Vol + button, it boots back into CyanogenMod ROM. Has a message related to MRC Erase after it says it detected REcovery Key pressed. I want to go back to using Clockworkmod so that I can flash another ROM. Now my computer doesn't even recognize the g tablet as an external storage so can't even access root. What do I need to do to get back my Clockworkmod to work again and how do I get back to my computer to recognize the g tablet. Appreciate the help. All feedback is welcome.
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
K J Rad said:
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
Click to expand...
Click to collapse
But to install Clockworkmod, I need my computer to recognize the g tab as a external storage device. Something it's not doing. So can't go back to it. CAn I download the clockworkmod on the external SD Card on the computer, put it back in the gtab and let it self recognize it and install clockworkmod? Will that work? And why isn't my computer recognizing my gtab as an external storage device. Is there a way I can mount USB storage without going into clockworkmod?
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
If you read the thread it shows there is a method to load CWM from MicroSD card (external). Once you have CWM back on then you can mount internal through it.
I dont know why Your tablet isn't mounting. Mine mounts automatically but my configuration is very different from yours. Perhaps you could check the ROM developers thread for more information.
Double submission. Please ignore/delete.
tcrews said:
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
Click to expand...
Click to collapse
I used the ROM Manger to flash clockworkmod. That's what messed up the clockworkmod in the first place. Trying to see how to fix that. May need to get rid of the ROM Manager.
Flash the alternate recovery in Rom Manager and then delete Rom Manager
thebadfrog said:
Flash the alternate recovery in Rom Manager and then delete Rom Manager
Click to expand...
Click to collapse
I can't even flash clockwork mod from the ROM manager. Keeps giving me a message "An Error occured while attempting to run privileged commands". Using clockworkmod was just so much easier. Just touching one button the ROM Manager has caused me headaches. I need some serious help.
Then run nvflash from the development froum
thebadfrog said:
Then run nvflash from the development froum
Click to expand...
Click to collapse
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Childpsy said:
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
Click to expand...
Click to collapse
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Thunter75 said:
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Click to expand...
Click to collapse
That's exactly what is happening. Was wanting to load the TNT lite or Vegan to try out a different rom and now I can't do it.
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
I will post the error message once I try it again at home. I do get the black screen. Thanks for your help.
Error message when trying NVFlash
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
The Message that shows up on the command window
"nvflash.exe" ---bct gtablet.bct ---setbct ---bl bootloader.bin ---configfile gtablet.cfg --create --go
NVFlash Started
NVFlash configuration file error: file not found
Please enter to continue
That's exactly what I see when I double click the nvflash_gtablet Windows batch file
Alright so I tried a few things and it seems like I needed to copy the files rather than the folder to the NVFlash folder. So I did that. NVFlash was successful but now it's stuck in boot loop. Now what do I do?
Ok... if you read any amount of the flashing process threads you would know using rom manager is a quote"****ing bad idea"end quote. Nvflash and a repartition using cwm is your only hope.
Flash cwm as an update.zip and repartition
Hello,
I need some help to get the new ICS update. I have a TF101 (no G), serial B80, with firmware HTK75.WW_epad-8.6.6.23.
Previously I was on 8.6.6.19 and used razorclaw to root it. Then I have done the wipe data, and installed 8.6.6.23.
When I boot with Power and Vol- then Vol+ to enter RCK mode I get the green android guy with exclamation mark.
When I boot with Power and Vol-, then Vol+ I get 2 options: Wipe data and android cold boot.
I used some apps to test if the device is root and they say no.
Sorry for my english, but it's not my main language.
Any idea to fix this?
The 8.6.6.23 is firmware for the 3G model. You will not see OTA since ICS is not released for G model yet.
You can try to manually install 8.5.6.21. You could also try rooting and installing cwm recovery and flash the ICS ROM
Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model
mantorrix said:
Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model
Click to expand...
Click to collapse
Easiest way is to root, install CWM recovery and flash an ICS ROM. Either the stock rooted ROM or one of the many custom ROMs
I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!
Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]
DreadKing said:
Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]
Click to expand...
Click to collapse
What you did was put your tablet into APX mode. That's only good if you're doing NVFLash not ADB.
To use ADB just have yourtablet on like normal with USB debugging turn on
Hi,
thanks for your fast reply, you are right. i got my adb device id when beeing in the os, so this works. but, trying to use nvflash/Brk's Asus TF RootKit over apx, i got the initial connection, but when i want to flash it looses the connection or dies or something... no idea what
you got any hints how i can come back to a clean version, which is upgradable?
thx & best regards,
dk
this is the program output btw:
Creating backup of current boot and recovery img
this should take some time... please wait
Loading Bootloader to pad... please wait!
Starting...
Error! Could not load bootloader.
Click to expand...
Click to collapse
alexlarson011 said:
I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!
Click to expand...
Click to collapse
Thanks! This worked for me. Thank you sir! Everything worked fine and I'm now on ICS!
followed exactly alexlarson011's instruction and voila - it works! thanks a lot!
best regards
-dk
How do I restore my tf101 (b80) to stock rom and recovery? I found one thread, but it said it didn't work with ones b70 or higher.
I currently have CWM recovery and Cynogenmod 10 if that makes any difference
scottharris4 said:
How do I restore my tf101 (b80) to stock rom and recovery? I found one thread, but it said it didn't work with ones b70 or higher.
I currently have CWM recovery and Cynogenmod 10 if that makes any difference
Click to expand...
Click to collapse
use this tool, it shld work http://forum.xda-developers.com/showthread.php?t=1688012
scottharris4 said:
How do I restore my tf101 (b80) to stock rom and recovery? I found one thread, but it said it didn't work with ones b70 or higher.
I currently have CWM recovery and Cynogenmod 10 if that makes any difference
Click to expand...
Click to collapse
Go to Asus website, download the latest firmware.
Extract the zip file from within, flash in recovery (clear data, cache and dalvik cache first)
After it's done, reboot and you'll be stock ROM, unroot, w/ stock recovery.
baseballfanz said:
Go to Asus website, download the latest firmware.
Extract the zip file from within, flash in recovery (clear data, cache and dalvik cache first)
After it's done, reboot and you'll be stock ROM, unroot, w/ stock recovery.
Click to expand...
Click to collapse
Same problem. Latest firmware downloaded from Asus website, installed with CWM recovery, rebooted aaaand ... nothing changed!
How's that possible? I can install a custom ROM but not the stock one?
Did you extract the zip before you flashed it like Baseball said?
Asus has a zip within a zip. Wrap your mind around that one.
Woodrube said:
Did you extract the zip before you flashed it like Baseball said?
Asus has a zip within a zip. Wrap your mind around that one.
Click to expand...
Click to collapse
Yes done, even if I don't understand why Asus put a zip inside a zip ...
Anyway, I did a full wipe, reinstalled the stock ROM, but no luck: CWM seemed to install the ROM, but when I rebooted I found the same old custom ROM ...
I must add that in the custom ROM I installed before (AOKP) 3G and WiFi also don't work ... this is why I want to rollback to the stock one.
darkmage1975 said:
Yes done, even if I don't understand why Asus put a zip inside a zip ...
Anyway, I did a full wipe, reinstalled the stock ROM, but no luck: CWM seemed to install the ROM, but when I rebooted I found the same old custom ROM ...
I must add that in the custom ROM I installed before (AOKP) 3G and WiFi also don't work ... this is why I want to rollback to the stock one.
Click to expand...
Click to collapse
You getting any message during flash procedure?
Did it say success or Status 7 or anything?
Try TWRP recovery and see if it work.
Use "easy flasher" to relock and go back to stock ICS...
Sent from my Transformer TF101 using xda app-developers app
catfishbilly said:
use this tool, it shld work http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
i told u already, use the tool i linked, i've used it and it works
I'm getting
Finding update package...
Opening update package...
Installing update...
assert failed: write_raw_image ("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.27.zip
(Status 7)
Installation aborted
I'm going from Megatron ICS
phazer11 said:
I'm getting
Finding update package...
Opening update package...
Installing update...
assert failed: write_raw_image ("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.27.zip
(Status 7)
Installation aborted
I'm going from Megatron ICS
Click to expand...
Click to collapse
Iam getting exactly the same error, does anyone knows how to fix this?
I do remember rolling back to stock by simply flashing the zip provided by asus, but after the RMA Iam getting this error.
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
the only way I can think of is using this method: http://forum.xda-developers.com/showthread.php?t=1622628 just copy the blob file and do the adb magic trick, but I find it kinda risky.
---------- Post added at 11:00 PM ---------- Previous post was at 10:35 PM ----------
So I managed to "fix" this (I had no idea what I was doing):
1. flash old roach 3.2.0.1 recovery http://forum.xda-developers.com/showthread.php?t=1213723 (link at the very bottom of first post)
2. place a zip file from ASUS (one that contains a blob file) on sdcard root and name it "update.zip"
3. in roach recovery wipe cache/data/dalvik and select apply update from /sdcard/update.zip
4. tada
hope this is gonna work for you as well
Thanks
VITUSH said:
Iam getting exactly the same error, does anyone knows how to fix this?
I do remember rolling back to stock by simply flashing the zip provided by asus, but after the RMA Iam getting this error.
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
the only way I can think of is using this method: http://forum.xda-developers.com/showthread.php?t=1622628 just copy the blob file and do the adb magic trick, but I find it kinda risky.
---------- Post added at 11:00 PM ---------- Previous post was at 10:35 PM ----------
So I managed to "fix" this (I had no idea what I was doing):
1. flash old roach 3.2.0.1 recovery http://forum.xda-developers.com/showthread.php?t=1213723 (link at the very bottom of first post)
2. place a zip file from ASUS (one that contains a blob file) on sdcard root and name it "update.zip"
3. in roach recovery wipe cache/data/dalvik and select apply update from /sdcard/update.zip
4. tada
hope this is gonna work for you as well
Click to expand...
Click to collapse
Thanks Vitush, switching back to roach then flashing the zip within zip from ASUS website worked for me.
phoeniix said:
Thanks Vitush, switching back to roach then flashing the zip within zip from ASUS website worked for me.
Click to expand...
Click to collapse
this work for me as well. thanks for the post.
I can't thank you enough Vitush!
it all worked perfectly for me, particularly as I was at this stage 2 days ago when I first got my Asus!
I had done many things since - rooting with 1click went fine, and I made 2 backups before I then I tried roms from here:
http://forum.xda-developers.com/showthread.php?t=2592890 and here: http://forum.xda-developers.com/showthread.php?t=2592890
both went on fine, and seemed great, but then I noticed that my sdcard was not showing in either rom, nor were my USB sticks!
I had lost all external storage! ... all in all quite a disaster, and my wife was doing her head in!
I spent ages trying to sort this out, and failed, so I went to put my backups back on, but they also failed with 'android_secure.img not found'
and my tablet just kept hanging at tha Asus logo. fortunately I was able to get back to CWM and did what you advised.
over the years I have rooted many many Android phones with no problems, but this is my first tablet.
for once I will accept defeat and stick with the stock rom (I may still root it though)
I could hug you!
Normal boot says "encryption unsuccessfull, encryption was interrupted and can't complete" (but I can see the MTP device over USB). In recovery mode, Windows does not see the device at all (can't install APX). Is it possible that the recovery is also bricked ?
To return my TF101 to stock I have used Easyflasher found here http://forum.xda-developers.com/showthread.php?t=1688012. However, you will need to be able to enter APX mode for this to work. To enter APX mode, you must first install the naked drivers. Here is a tutorial on how to install the naked drivers http://www.transformerforums.com/forum/asus-transformer-tf101-development/31927-frederuco-s-guide-root-rom-tf101.html.
barkeater said:
you must first install the naked drivers. Here is a tutorial on how to install the naked drivers http://www.transformerforums.com/forum/asus-transformer-tf101-development/31927-frederuco-s-guide-root-rom-tf101.html.
Click to expand...
Click to collapse
Now that we have the Naked Drivers boot to APX mode. Attach your USB to your tablet (not the dock) and Hold VOL UP and POWER for 15-20 seconds.
Click to expand...
Click to collapse
I am not sure what APX mode is.
In normal boot, I only get the encruption error message. No way to enter normal Android to activate USB debug. TF101 is seen by computer as MTP device.
If I press vol-down, and power, then vol-up, I get a droid with blue cube, then, with a red keyboard and a triangle, and PC can not see device at all.
Both were tried with dock. Without dock, tablet is in heavy trouble to start; proably dead battery.
If it can help, I can open the tablet, change the battery, power directly via the battery pins, or mess a bit with inernal components.
Is that tablet completely bricked ?
TF101s are pretty resilient and can usually be restored to stock. However, your easiest path to doing that is to enter APX mode and use the Easyflasher app. Did you check out the link I included in my post above from Transformerforums? In it, at the beginning it explains how to enter APX mode. It requires the naked drivers to be installed on your computer that you will be connecting the tablet to (undocked). Once the naked drivers have been installed successfully, you can then connect the tablet to the computer via the data cable and hold down the power and volume up (+) at same time till screen goes black. You can verify that the tablet is in APX by opening Device Manager on computer and you should see the ASUS device identified as being in APX mode.
My setup is complicated; I don't have a legacy Windows; Windows is installed inside an emulator inside Linux. So, I plug the tablet on the Linux workstation, and then, I forward the device to the Windows emulator. The thing is that, in recovery mode, Linux does not see any device at all. This means, the tablet does not declare itself at all on the USB bus. The question is not about drivers, or compatibility: the tablet does not annouce itself on the USB bus.
I know how the USB works; I worked a bit on USB drivers. I messed with them a lot a few ears ago. And I know how my Android phones behave.
The tablet behaves like a phone which has "USB debugging" unticked. And since the system is unaccessible, I can not tick that. On my phones, the tick has effect on recovery mode.
Even if I installed the APX drivers on an other computer with a real Windows, I just can't see how it would see the tablet, if the tablet refuses to be a USB client.
But, the cable and plugs are good: when I boot in normal mode, and get the encryption error message, the tablet comes out on the bus, and Windows can see an MTP device.
Are the APX Windows drivers required to make the table become a USB client ? This is very unlikely. Am I in the only case in the world where an emulator would be an issue due to hardware reasons ? Which kind of signal would the Windows driver send to the bus to tell an undeclared tablet "hey buddy, come around, I am waiting for you" ? This would not seem "USB compliant" to me, to have communication with a device hidden on the bus. I am not aware of any kind of USB droadcast.
And yes, I tried withOUT the dock.
Trying again now: in crashed mode, I get: Bus 002 Device 005: ID 0b05:4e0f ASUSTek Computer, Inc.
In recovery mode, I get no new device.
Someone else will have to help you then. Good luck.
First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.
Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory: