Desperate and not working over adb - Eee Pad Transformer Q&A, Help & Troubleshooting

Hello,
I`m in trouble with my EEE pad. I don`t know what to do to recover my software . Yesterday I did make a Revolution HD Super Wipe Full,and forgot that my battery was not enough charged. My pad remained without battery and it shut-down. Now it remains with the Eee pad Asus logo on the screen. I can enter in APX mode. Also connect with the adb. I attach here one print, maybe someone could help me, what to do....

amdtip said:
Hello,
I`m in trouble with my EEE pad. I don`t know what to do to recover my software . Yesterday I did make a Revolution HD Super Wipe Full,and forgot that my battery was not enough charged. My pad remained without battery and it shut-down. Now it remains with the Eee pad Asus logo on the screen. I can enter in APX mode. Also connect with the adb. I attach here one print, maybe someone could help me, what to do....
Click to expand...
Click to collapse
Can you boot into recovery?
Push Vol down + Power button
When you see words scrolling at the top left
immediately push Vol up within 5 sec.

Um im not sure but couldnt you push the individual images??
Do you have NVflash?
Im not sure how you would do it through adb but maybe something like
/adb devices
/adb remount
/adb push system system.img
/adb push recovery recovery.img
/adb reboot
then go into cwm and flash kernel
If that doesnt work and you have nvflash you can push the images through that or use the OLiFE script so you dont have to write
All else falls i hope someone far more knowledgable than me can help i tried
Sent from my tf Enigmatic V1 Alpha 1.59Ghz Panda.test

I tried with Nvflash, but I`m getting everytime error. My pad is very new. The S/N begins with BB0KA, and the flasher does not workThe ony think that work is with the adb. . .I`m recieving this error when running adb -push system.img. Danzano, I did not find the OLiFE script. Where I can get it..

PROBLEM SOLVED: For other people that encoured my problem on the TF101,do the following to recover:
1. Download from asus your zip firmware (note: be sure to download the rigt version for you ex: (WW, US).
2. Rename your downloaded file to " EP101_SDUPDATE.zip "
2. Format your sd-card to FAT.
3. Create obligatory on the sd-card a folder "ASUS"
4. Put the renamed "EP101_SDUPDATE.zip" file in the created ASUS folder.
5. Hold power button + Volume key down to enter recovery
6. Press within 10 seconds the +Volume key
7. You will see that the update progress-bar will beginn to work . Thats all, and enjoy it...

Related

HELP! Unroot Without Power Button

Hi. I dropped my TF a few days ago and now the power button stops working. I want to RMA it but it is rooted. Is there any way to unroot the TF without using the power button? thanks.
Get Reboot to Recovery (or from the market here or use the donate version to thank them for getting you out of your jam).
Just curious, where would you RMA it in IDN? How much was it there in Rp?
Thanks for the info. Do I need to have CWM installed first? I didn't install CWM before and I don't think I can do it now. (sorry for noob questions) I bought it in the US. Do they have international warranty or something? I don't think I can spend that much time away from my TF. They sell it here for US $699 net price.
Warranties don't usually apply outside the country of sale, but I haven't read the terms on the ASUS one so I could be wrong. I am certain it doesn't cover physical damage from being dropped, though. I've heard other stories on here that they sent in a damaged device and ASUS offered a repair quote, so you might get lucky and be offered a new bezel with buttons cheap.
I'm sorry, but does it need CWM? and how do I install it without the power button?
Check out the unroot thread on the dev section. Hope it works out.
Even if you did have cwm recovery, you need a working power button to make selections in cwm.
Sent from my Transformer TF101 using Tapatalk
Anything that uses recovery or nvflash won't work because of the power button... you need the staging partition!
You can do it by copying a stock blob to the staging partition. The TF will do all the flashing for you
You do need adb and root, but no power buttons.
Here's the 1 click method!
Be sure ADB is installed on your PC. There are threads on how to do this all over XDA.
Be sure your battery is charged.
Download a stock firmware from the ASUS website. Be sure to match your country code (WW, TW, US, etc.)
Unzip the firmware. It should create an ASUS/Update/some.zip. Unzip the some.zip file too.
If this went well you should be looking at a giant blob! ~500M or so. No kidding- the file will be called "blob"
Use ADB to push the blob to your TF or just copy it to your SD card. Your choice.
Code:
adb push blob /data/local/
Connect your TF to your PC and type "adb shell" to start a shell.
Type these commands into the shell
Now the magic happens....
Code:
su
dd if=/data/local/blob of=/dev/block/mmcblk0p4
reboot
Be sure to get the dd command correct. The last three characters are zero-pee-four. If you pushed/saved the blob somewhere else, you'll have to adjust the "if=" to match the path.
Your TF should reboot and it will flash the stock rom. You'll see a blue progress bar that will flash quickly, but still take longer than you think it should. Be patient. Your TF will reboot automatically.
You can now delete the blob file from your TF.
Thanks. I'll try and let you know.
Did this work for you? I'm in the same boat. I have CWM and latest Revolver installed. Would there be any other steps besides those mentioned here if I have CWM installed?
gee one said:
Anything that uses recovery or nvflash won't work because of the power button... you need the staging partition!
You can do it by copying a stock blob to the staging partition. The TF will do all the flashing for you
You do need adb and root, but no power buttons.
Here's the 1 click method!
Be sure ADB is installed on your PC. There are threads on how to do this all over XDA.
Be sure your battery is charged.
Download a stock firmware from the ASUS website. Be sure to match your country code (WW, TW, US, etc.)
Unzip the firmware. It should create an ASUS/Update/some.zip. Unzip the some.zip file too.
If this went well you should be looking at a giant blob! ~500M or so. No kidding- the file will be called "blob"
Use ADB to push the blob to your TF or just copy it to your SD card. Your choice.
Code:
adb push blob /data/local/
Connect your TF to your PC and type "adb shell" to start a shell.
Type these commands into the shell
Now the magic happens....
Code:
su
dd if=/data/local/blob of=/dev/block/mmcblk0p4
reboot
Be sure to get the dd command correct. The last three characters are zero-pee-four. If you pushed/saved the blob somewhere else, you'll have to adjust the "if=" to match the path.
Your TF should reboot and it will flash the stock rom. You'll see a blue progress bar that will flash quickly, but still take longer than you think it should. Be patient. Your TF will reboot automatically.
You can now delete the blob file from your TF.
Click to expand...
Click to collapse
So this can be used as a way to return a tablet to stock or potentially un-softbrick a tablet?
Sent from my DROIDX using XDA App
This will flash the stock firmware in the blob. If you are softbricked, it might work if you can get to adb.
gee one said:
This will flash the stock firmware in the blob. If you are softbricked, it might work if you can get to adb.
Click to expand...
Click to collapse
Is there any mode that adb does work on? (From Clockwork, APX mode(?), etc.)
Sent from my DROIDX using XDA App
You might try using the dock?
I'm not sure if i can actually select anything with the dock(like using the power button), but if i boot into cwm with the dock connected i can use the arrow keys to scroll up and down. Worth a look anyway.
infazzdar said:
Is there any mode that adb does work on? (From Clockwork, APX mode(?), etc.)
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If it's enabled, you can use adb in the regular system and recovery. It won't work in apx mode/nvflash.
The tricky part is that sometimes, it's not enabled, and that time is usually when you need it to be. You can enable through the system settings or by changing flags in the boot or recovery images.

Bricked my Asus Transformer Eee Pad (Can't boot into APX Mode)

Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
avatarjo3 said:
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
Click to expand...
Click to collapse
Its hold volume down and then hold power...
tweaked said:
Its hold volume down and then hold power...
Click to expand...
Click to collapse
Right. That's to get in to Recovery mode. I can get into recovery mode, but I can't get into APX Mode, which is what I need to do to apply the NVflash. I can't apply the flash via CWM because it's not letting me mount my SDcard.
Thanks for the reply!
avatarjo3 said:
I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Click to expand...
Click to collapse
Go get a micro sd card and try again. Buy one, get it out of your phone if you have it or get one from your sister.
Not 100% sure but my GUESS would be that since you have no OS on your tablet.
Which mean it can't communicate with your dock for you to use the SD card on the dock. If you can still get into CWM recovery you are NOT "bricked"
baseballfanz said:
Go get a micro sd card and try again. Buy one, get it out of your phone if you have it or get one from your sister.
Not 100% sure but my GUESS would be that since you have no OS on your tablet.
Which mean it can't communicate with your dock for you to use the SD card on the dock. If you can still get into CWM recovery you are NOT "bricked"
Click to expand...
Click to collapse
Whew... what a relief. Alrite, I'll get a microSD card. How can I format it? There's a slot on my laptop with an SDcard slot, but not one for microSD. I've tried using a microSD straight out of the package, without formatting it. Even though I didn't put anything on it, it wouldn't mount via the CWM mount feature.
Thanks for the reply!
avatarjo3 said:
Whew... what a relief. Alrite, I'll get a microSD card. How can I format it? There's a slot on my laptop with an SDcard slot, but not one for microSD. I've tried using a microSD straight out of the package, without formatting it. Even though I didn't put anything on it, it wouldn't mount via the CWM mount feature.
Thanks for the reply!
Click to expand...
Click to collapse
They have microSD USB adapter. Mine came with one when I bought it.
Format to FAT32. Use a program like sdformatter for best results.
baseballfanz said:
They have microSD USB adapter.
Click to expand...
Click to collapse
Alrite. I'll give it a shot.
When you say OS, is that the same thing as a ROM? I want to flash this ROM (http://forum.xda-developers.com/showthread.php?t=1514658), so would I transfer that rom to the microSD and flash it via CWM?
Thanks again!
Yes put that ROM filter on the micro sd card, boot into cwm recovery and install zip from sd card
baseballfanz said:
Yes put that ROM filter on the micro sd card, boot into cwm recovery and install zip from sd card
Click to expand...
Click to collapse
So I have the microSD card. It's 2gigs. I followed this guide (http://www.xda-developers.com/android/how-to-root-the-asus-transformer-xda-tv/) while my device was version 8.6.5.21. All I was trying to do was to get CWM on there. I think the best approach now would be to flash back to 8.6.5.13, then try and install CWM from there. I looked at this guide (http://forum.xda-developers.com/showthread.php?t=1281161), but it said it doesn't come with CWM, but comes with CWM support... What does that mean?
Any suggestions?
Thanks!
Don't go to firmware before 8.6.5.19, it is pointless to go any further back. Flash that firmware, then use razorclaw to root and gnufabios recoveryinstaller to get cwm, see the guide in my signature.
luna_c666 said:
Don't go to firmware before 8.6.5.19, it is pointless to go any further back. Flash that firmware, then use razorclaw to root and gnufabios recoveryinstaller to get cwm, see the guide in my signature.
Click to expand...
Click to collapse
Thanks the advice. I won't root from 8.6.5.13, but I don't think I can take the razorclaw approach, because all the links for the 8.6.5.19 roms are dead. I'm looking at Nachoroot (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/) and will report back when finished.
Quick question. Are the commands provided on the website meant to be ran in cmd?
Thanks!
avatarjo3 said:
Quick question. Are the commands provided on the website meant to be ran in cmd?
Thanks!
Click to expand...
Click to collapse
Yes in CMD window.
OK I'm a little lost. Currently my firmware is 8.6.5.21 and I'm not sure how to follow the Nachoroot guide (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/)...
I have ADB setup. I downloaded the 2 files. Do I need to have the files in a certain location? What do I need to do???
avatarjo3 said:
OK I'm a little lost. Currently my firmware is 8.6.5.21 and I'm not sure how to follow the Nachoroot guide (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/)...
I have ADB setup. I downloaded the 2 files. Do I need to have the files in a certain location? What do I need to do???
Click to expand...
Click to collapse
The two files need to go into the SDK (platform-tools) folder.
baseballfanz said:
The two files need to go into the SDK (platform-tools) folder.
Click to expand...
Click to collapse
Great, so I did that and I shift+rightclick in the folder to open up cmd and I type in the commands, but after I get do the second reboot and type in "adb shell id" I never get id 0... I type everything out carefully. Each time the tablet reboots my computer says it's installing the software but fails everytime. Could this have something to do with it? Does this only work with Transformer Prime?
Also, I'm running windows 7 and installed the SDK package in Program Files x86. I put the 2 files in the folder platform-tools and shift+rightclick and ran the commands. What am I doing wrong?
I really appreciate the replies. They're very helpful!
Thank you!
Please anyone? I could really use your help
Just forget everything everyone says. Follow my idiot-proof procedure for dummies.
Part 0
(1) Go to the following website.
ASUS - Eee- ASUS Eee Pad Transformer TF101
(2) Choose android.
(3) Download the latest WW, US, TW, etc. version you need.
(4) Unzip that file. Inside, you will probably find a folder called update. Inside that folder, you will find another zip file. Keep this zip file.
(5) Place this zip file in the root of your micro sd card.
(6) Insert micro sdcard into your TF.
Part I
(1) Download the following zip file from my cloud account.
honeycomb_root_cwm.zip - File Shared from Box - Free Online File Storage
(2) Unzip it onto your desktop.
You should find 3 things after you've unzipped it.
a-folder name "apps"
b-folder name "root honeycomb"
c-file name "root-honeycomb-instructions.txt"
(3) Place the folder "root honeycomb" in your c: directory. where is this? Click on Computer and go into Local Disk (C: ). Place the folder in there.
Part II
(1) Connect your TF to your computer.
(2) On your TF, press on the sync icon in the lower right hand corner of the taskbar. It will fail to sync with your computer. Try again. Keep trying againi until your computer and TF recognize each other.
(3) On your PC, press on the start menu. In the search bar, type in "cmd".
(4) Type in "cd\" and press enter.
(5) In the command prompt, type "cd root-honeycomb".
Part III
(1) Open up the text file "root-honeycomb-instructions.txt".
(2) Copy the first line in the text file.
(3) Right click the command prompt window and choose paste. Press enter.
(4) Copy and paste the 2nd line. Do this for the first 4 lines.
(5) After the 4th line, your TF should restart. Wait for it to completely restart. Unlock your TF.
(6) Copy and paste the 6th and subsequent lines. When you see <wait for boot>, it means you wait for your TF to reboot. Do not copy and paste such lines.
Part IV
(1) Congrats. You are now rooted.
(2) Transfer the folder "apps" into your TF.
(3) Install those 2 apps found in the folder.
(4) Open up the app "superuser". Then go back to your homescreen.
(5) Open up the app recovery installer. Press that big-ass button in the middle of the screen. Allow.
(6) Wait for your TF to restart completely.
(7) Turn off your TF.
(8) Turn on your TF by pressing and holding the power and volume down buttons together. As soon as you see white texts on the upper left hand corner of your TF, immediately release the power and volume down buttons and press the volume up button.
Part V (Final)
(1) You are now in what we call clockworkmod recovery.
(2) Using volume up and down buttons, navigate to "Install from zip file". To enter, press the power button.
(3) Choose "Choose zip file from sd card".
(4) Navigate to the zip file you got from the asus website and choose it.
(5) Watch your TF install ICS.
(6) Once ICS finishes installing, go back and reboot system.
At this point, your system will reboot into ICS. You now have a non-rooted ICS stock rom and stock recovery.
avatarjo3 said:
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
Click to expand...
Click to collapse
If its till bricked press down power and vol down buttons together that should help and your tablet will BOOT back into an existing ROM (Im telling you because i was trying to ROOT with ICS and more than once i was stuck in same situation).
If you want to root then follow my step, it should help you to ROOT as i was able get ROOT and install Revolver ICS and i was on stock ICS (US version). Click on the link below and understand all the steps.
http://forum.xda-developers.com/showthread.php?t=1527926
Sorry for the late reply guys. I lost my microSD card so I haven't tested your method yet.
Thank you for replying with length posts guys. This is most helpful! I will return with positive results!
avatarjo3 said:
Great, so I did that and I shift+rightclick in the folder to open up cmd and I type in the commands, but after I get do the second reboot and type in "adb shell id" I never get id 0... I type everything out carefully. Each time the tablet reboots my computer says it's installing the software but fails everytime. Could this have something to do with it? Does this only work with Transformer Prime?
Click to expand...
Click to collapse
You are typing in --stage1 --stage2 also correct?

[Q] Problems Flashing Recovery on Asus TF300T

I have tried literally every method that I've found on the net to flash recovery on my Asus TF300T, and nothing works. The tablet stays at "Starting Fastboot USB Download Protocol" when I plug it into my computer. When I open a command prompt and enter in the command lines, it just keeps saying "Fastboot is not recognized as an internal or external command". The guides say that after entering the commands, a blue installation bar should appear on my tablet, but nothing happens at all. I don't know what else to do. I updated to the OTA 4.1.1 firmware as soon as I got the tablet I can't root nor can I find a way to flash any type of recovery. Can anyone help? Thanks in advance...
Installing TWRP.
I added the file to the message. The latest version of Android SDK Tools pulled adb and fastboot and made a command file to install it, so as not to type it manually.
This archive should be unpacked in the root of drive C. Folder was adb-t. In this folder, copy the file to your custom recovery tablet model and its version of the android, rename it to twrp.blob. We go on the tablet mode fastboot, connect the tablet to the computer and launch twrp.bat.
Installs the custom recovery, expect to fill the display screen tablet and press the space bar (any key) on the keyboard to restart the tablet. Remove the cables from the tablet.
Attention! The current archive file contains the last (2.3.1.0) custom recovery (twrp.blob) for TF300T with JB. If you have a TG or some version of android - do not forget to replace twrp.blob of the edition you need.
Thank You!
BrateloSlava said:
Installing TWRP.
I added the file to the message. The latest version of Android SDK Tools pulled adb and fastboot and made a command file to install it, so as not to type it manually.
This archive should be unpacked in the root of drive C. Folder was adb-t. In this folder, copy the file to your custom recovery tablet model and its version of the android, rename it to twrp.blob. We go on the tablet mode fastboot, connect the tablet to the computer and launch twrp.bat.
Installs the custom recovery, expect to fill the display screen tablet and press the space bar (any key) on the keyboard to restart the tablet. Remove the cables from the tablet.
Attention! The current archive file contains the last (2.3.1.0) custom recovery (twrp.blob) for TF300T with JB. If you have a TG or some version of android - do not forget to replace twrp.blob of the edition you need.
Click to expand...
Click to collapse
Oh, man! You have no idea how grateful I am to you!!! I have been trying to get this done FOREVER, and this finally got the job done...thank you sooooooooooo much! It is appreciated!

[Q] HELP HELP HELP Bricked

Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me
Meat6911 said:
Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me
Click to expand...
Click to collapse
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:
When I connect to PC it makes the connection sound but doesn't show as a removable drive so I can't use Easyflash or any program like that also like I said APX mode wont work it makes the sound that it detects the tablet but then makes the remove sound right away. and this happened when I installed the Cyangenmod 9. I found someone who says he may be able to fix it for $50 using Odin but I am worried that he wont be able to and its an hour drive to take it to him... At this point I just want it back to stock ...
erm... ODIN won't work with a transformer, it's only for samsung devices.
Alright, you probably used ROM manager judging by your Recovery version.
You need to just NvFlash the device back to stock:
Download your region's Stock ROM from here: (WW if outside of US, US if inside.) Stock Rom
Download Wheelie NvFlash tool from here: Wheelie
Unzip the stock rom .zip first, into it's own folder. Then unzip the wheelie tar.bz2 into the folder you just made by unzipping the stock rom. Overwrite any files with the wheelie files.
Next find out your Sbk variant, Look at the serial number on the sticker on the bottom of your tablet.
If it says B70, or a higher number like B80 or any C, then you are Sbkv2
If the number is B60 or lower, you are Sbkv1.
Remember this for the next step.
Make sure the tablet is off totally, Then hold the Volume-UP key and Then press power, keep holding volume up. It will enter APX mode.
Plug it into your computer, the screen will stay blank.
It should be detected, if it says unknown device or similar, use the windows device manager to select the 'asus bootloader interface' or 'Unknown device' or similar, with Nvidia ASUS or APX or Bootloader, something along those lines, to update the driver, right click this and navigate to the 'usbpcdriver' folder in the folder you unzipped earlier. It will install and detect.
Then run the .bat file that says Reflash_(Your Sbk version).bat while the tab is connected in apx mode.
It will return to stock, give it time, DO NOT UNPLUG IT.
The screen may flash, and the tablet may/will reboot.
When done you will be on Stock latest from ASUS.
If you want safe root / recovery, download and run my PERI tool, link in signature.
good luck.
ok I am trying that now but I wish I had someone to walk me through everything in real time...
OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you
Meat6911 said:
OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you
Click to expand...
Click to collapse
erm, I guess it worked?
The best thing you can do for someone on xda is hit the 'thanks' or donate buttons, and thanks is free!
Any other questions, I'm guessing it worked alright?
frederuco said:
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:
Click to expand...
Click to collapse
I had similiar problem when I tried to downgrade and go back to stock. After flashing stock from asus, I did it wrong by unzipping (stock_ics_kernel_9.2.1.24US-secure) first then flash the file under the downloaded zip files. Now I am also stuck at Eee Pad, can't get into recovery because it probably wiped out everything. Hopefully this can recover my Eee Pad!!!! I got my fingers cross. This may be my only hope for my asus pad .
Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use
Meat6911 said:
Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use
Click to expand...
Click to collapse
You should be able to with Dolphin HD browser and Flash installed, make sure flash is integrated into the Dolphin. That or the sites should just work..
I use Adaway.

[Q] broke asus tf101 eee pad transformer

Hi.
It's been some time since i tried fixing my Asus Transformer...
The problem is : If it has battery life. It boot's and gets stuck on the first screen.
With the logo "eee pad" .
If i turn it off, it automaticly reboots and gets stuck in the same screen.
If i try to get into recovery mode.
Vol down, Powerup... and the vol up , i can see the few line's of code , saying it will boot into recovery mode.
but while trying to start recovery mode the icon changes to a fallen android and an "! triangle above it
I've been looking around forums evrywhere but i cant find a solution for my exact problem.
can anyone help?
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Lethe6 said:
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Click to expand...
Click to collapse
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
DarkCloud98 said:
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
Click to expand...
Click to collapse
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
http://www.xdafileserver.nl/Files/A...OMS/ICS .27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
*Detection* said:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
Click to expand...
Click to collapse
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
DarkCloud98 said:
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
Click to expand...
Click to collapse
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Click to expand...
Click to collapse
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
DarkCloud98 said:
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
Click to expand...
Click to collapse
I edited my post with quick instructions
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
Click to expand...
Click to collapse
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
DarkCloud98 said:
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
Click to expand...
Click to collapse
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
DarkCloud98 said:
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
Click to expand...
Click to collapse
You could flash the pre-rooted versions too although I think it's easy enough to root yourself these days
This is the XDA Fileserver for different ROMs if you need them
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)
I was just reading someone else who had the same display stuck on their TF while trying to use NVFlash and they said re-downloading the ROM and trying it again fixed it
So if this fails for some reason, try another NVFlash ROM from the XDA Server
*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
DarkCloud98 said:
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
Click to expand...
Click to collapse
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
http://forum.xda-developers.com/showthread.php?t=1123429
*Detection* said:
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
Click to expand...
Click to collapse
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
DarkCloud98 said:
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
Click to expand...
Click to collapse
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
http://www.portableandroid.co.uk/androidDL/new Windows.zip
*Detection* said:
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
Click to expand...
Click to collapse
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
EDIT: And the other NvFlash version you linked me, does the same...after it being sent, the CMD closes and thats it
DarkCloud98 said:
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
Click to expand...
Click to collapse
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
*Detection* said:
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
Click to expand...
Click to collapse
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
DarkCloud98 said:
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
Click to expand...
Click to collapse
Great news! Linux vs Linux did the trick
How long have you been without your TF until now? It'll be like having a new toy again I would imagine

Categories

Resources