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.
Related
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
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!
I managed to root my TF101 using this thread:
http://forum.xda-developers.com/showthread.php?t=1689193
The problem is I TWRP is not installed.
When I press Volume Down + Power buttons and then The Volume Up, my device goes to a screen with 2 icons, "Wipe Data" and "Android" and after 10 seconds it boots to Android. I assume this is the stock recovery.
I Tried:
1) Both EasyFlashers (http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html)
2) Goo Manager
3) Terminal Mathod (http://teamw.in/project/twrp2/109)
All of them failed.
Is there anything else for me to try?
What were your steps when you tried using Easyflasher ?
I confirmed the device was in APX mode, through the device manager.
Run EasyFlasher.exe and chose the SBK1 (my TF101 is B60)
Chose "TWRP 2.2.1" and pressed Flash.
Everything seems to be working, since both in the command prompt and the device I get that the process was successful, but booting to recovery does not run TWRP, instead if goes to the screen I mentioned earlier.
lefterhs said:
I confirmed the device was in APX mode, through the device manager.
Run EasyFlasher.exe and chose the SBK1 (my TF101 is B60)
Chose "TWRP 2.2.1" and pressed Flash.
Everything seems to be working, since both in the command prompt and the device I get that the process was successful, but booting to recovery does not run TWRP, instead if goes to the screen I mentioned earlier.
Click to expand...
Click to collapse
Not sure it matters, but did you run Easyflasher as Admin ?
Ensure the correct APX drivers were installed ?
Reboot the TF once before trying to enter recovery ?
Held the Vol Down & Power from a powered off state until the white text appeared at the top of the screen, then hit volume up to enter RCK ?
*Detection* said:
Not sure it matters, but did you run Easyflasher as Admin ?
Ensure the correct APX drivers were installed ?
Reboot the TF once before trying to enter recovery ?
Held the Vol Down & Power from a powered off state until the white text appeared at the top of the screen, then hit volume up to enter RCK ?
Click to expand...
Click to collapse
1. Yes, I am administrator.
2. I used Universal Naked Drivers 0.72 from here:http://forum.xda-developers.com/showthread.php?t=1514942
3. Yes, after using any of the methods mentioned, I allowed it to reboot once normally.
4. Yes, I get the screen I mentioned with the Wipe Data/Android, when I press Vol Up after the Vol Down+Power combination.
When I say Run as Admin, I mean Right click the exe and choose Run as Administrator
I'd try using the drivers included in the Easyflasher bundle here (EDIT - Dev recommends the drivers you used anyway)
http://forum.xda-developers.com/showthread.php?t=1688012
As it uses APX this shouldn't matter, but make sure USB Debugging is enabled in Developer Options too and let it install the drivers while powered on and connected to the PC
I'd try another USB port too to rule that out
Which SBK/Serial is your TF?
EDIT -Another thought, are you running a stock ROM atm? Which one ?
You could try using Peri to flash TWRP
http://forum.xda-developers.com/showthread.php?t=1681155
I tried the Peri.
Continue? (Y/N) Y
Starting... This will take awhile...
9444+1 records in
9444+1 records out
4835404 bytes transferred in 2.385 secs (2027423 bytes/sec)
Done! You should see some reported #s above.
Now we reboot the TF again, you'll see a blue bar.
It will take awhile to fill, then you have recovery!
Click to expand...
Click to collapse
Unfortunately, I don't see any blue bar. The device just reboots to Android.
The serial is: B60KAS103665
Yes, I use the stock ROM, I never tried to install a custom ROM, until now.
IML74K.WW_epad-9.2.1.27-20120615
Actually, my goal is to install the KatKiss ROM using these instructions:
3w.transformerforums.com/forum/asus-transformer-tf101-development/33773-official-faq-katkiss-rom-formerly-teameos-4-android-4-2-x-tf101.html
Is there any other method, not using TWRP, to install KatKiss?
Update:
I also tried to install CM recovery, using the 3rd option of 1-Click Transformer Root. Again, I don't see anything to get installed (a blue bar is not showing) and it just reboots to Android.
Lately, I have a problem.
I get a "DMClient has stopped" error twice each time I turn the TF101 on. I think this is the ASUS update process. Can this be relevant?
lefterhs said:
I tried the Peri.
Unfortunately, I don't see any blue bar. The device just reboots to Android.
The serial is: B60KAS103665
Yes, I use the stock ROM, I never tried to install a custom ROM, until now.
IML74K.WW_epad-9.2.1.27-20120615
Actually, my goal is to install the KatKiss ROM using these instructions:
3w.transformerforums.com/forum/asus-transformer-tf101-development/33773-official-faq-katkiss-rom-formerly-teameos-4-android-4-2-x-tf101.html
Is there any other method, not using TWRP, to install KatKiss?
Click to expand...
Click to collapse
Your TF is SBK1, so should have no problem getting a custom recovery flashed to it, the only thing I'm wondering is if the stock ROM is causing problems, I seem to remember someone else with stock having problems getting a modern custom recovery flashed too
Unfortunately the only way to flash KatKiss is from custom recovery TWRP as the ROMs are released in flashable .zip format
Do you have another PC you could use to try and flash TWRP via Easyflasher ?
What OS are you running on your PC ?
At least one of the methods you have tried should have definitely worked, so long as the TF is in APX mode, the drivers are installed, and the PC can see the TF, Easyflasher should have done the job
I never recommend flashing CWM as it screws with JB ROMs, but it might be worth trying to flash that recovery first, then a custom ICS ROM, after that if you get that far, try installing TWRP again before trying to flash a JB ROM
Just make sure you don't flash a JB ROM with CWM recovery installed
---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------
lefterhs said:
Lately, I have a problem.
I get a "DMClient has stopped" error twice each time I turn the TF101 on. I think this is the ASUS update process. Can this be relevant?
Click to expand...
Click to collapse
Hmm, you could try clearing the data / cache from DMClient in Settings > Apps > All
Code:
1. Settings
2. Applications
3. Running services
4. All
5. DMClient
6. Clear data
7. Force stop
8. Shut down and restart the tablet
Maybe there is an old update file stuck in cache causing problems
Have you tried factory resetting it 100% ?
I did a few things, at the same time.
1. Changed USB port.
2. Used the original EasyFlasher.
3. Cleared and force stopped the DMClient, which I believe did the trick.
Now, TWRP got installed, although It also did a hard reset to my device. When it opened, I had to setup the device like it was the first time I turn it on.
Anyway, I think I will continue to Kat Kiss installation now.
Thanks for your help.
lefterhs said:
I did a few things, at the same time.
1. Changed USB port.
2. Used the original EasyFlasher.
3. Cleared and force stopped the DMClient, which I believe did the trick.
Now, TWRP got installed, although It also did a hard reset to my device. When it opened, I had to setup the device like it was the first time I turn it on.
Anyway, I think I will continue to Kat Kiss installation now.
Thanks for your help.
Click to expand...
Click to collapse
Ah good news, yea it does sound as if the DMClient was stopping the install, Im not sure exactly how it works, but possibly if the TF thinks there is a pending update, it won't allow the flash until its cleared
Good thing you mentioned it, I was almost at a loss as to what was causing the problem
And yep, now you have it installed, make sure you are up to date 2.3.2.3 (Use GooManager to install the latest version), and then you can install any custom ROM you like from TWRP
lefterhs said:
I managed to root my TF101 using this thread:
http://forum.xda-developers.com/showthread.php?t=1689193
The problem is I TWRP is not installed.
When I press Volume Down + Power buttons and then The Volume Up, my device goes to a screen with 2 icons, "Wipe Data" and "Android" and after 10 seconds it boots to Android. I assume this is the stock recovery.
I Tried:
1) Both EasyFlashers (http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html)
2) Goo Manager
3) Terminal Mathod (http://teamw.in/project/twrp2/109)
All of them failed.
Is there anything else for me to try?
Click to expand...
Click to collapse
this has a beta twrp zip that is flashable, maybe help? http://forum.xda-developers.com/showthread.php?t=2308565
Hello,
I'm trying to install the MarshMallow 6.0.1 Release on my TF101 (SBK2 -BBxxxxx) with stock rom IMLK74K.WW_epad-9.2.1.27-20120615 and easyflasher (universal naked drivers installed correctly on windows 10). I can flash it correctly but I have the same problem as lefterhs.
I have also tried different version of twrp, latest easyflasher, different USB ports, with USB debugging on the device, still same problem, only choice is android and wipe data.
I have also tried with CWM but I had the error can't mount SD card. Rooted with 1-click transformer root. I begin to believe I will not be able to change the ROM. Any idea?
Thanks,
EDIT: Problem solved, managed to flash Roach CWM 5.5.0.4 from EasyFlasher and flash TWRP 2.8.1.1 from zip inside Roach CWM 5.5.0.4 recovery. Then followed the procedure in https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496. Katkiss is running on my tf101.
*Detection* said:
Ah good news, yea it does sound as if the DMClient was stopping the install, Im not sure exactly how it works, but possibly if the TF thinks there is a pending update, it won't allow the flash until its cleared
Good thing you mentioned it, I was almost at a loss as to what was causing the problem
And yep, now you have it installed, make sure you are up to date 2.3.2.3 (Use GooManager to install the latest version), and then you can install any custom ROM you like from TWRP
Click to expand...
Click to collapse
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??
lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?
nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays
So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Hope this worked
s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?
Hi,
I've tried installing the TWRP throught Goo Manager, tried disabling DMClient and cleaning the application cache through android's application manager, but when I power down then, press VOL-DOWN + POWER I find myself only 2 opstion, system wipe and android linux cold boot. It's like if I'm in the official Asus TF101 Recovery mode.
I've tried EasyFlasher way, but I don't know how to install the universal naked drivers.. So I tried entering APX mode with the normal windows driver and hitting the flash button on the EasyFlasher for TWRP. But still it won't boot to recover, just the old 2 options screen.
I've tried also the console way, (dd=if whatever...) and when I reboot the tablet it shows a blue loading bar under the EePad logo. But still no recovery at VOL+DOWN + POWER, just the freaking wipe data or cold boot scrren.
I've tried ROM Manager from google play and it says that I have both ClockworkMode and TWRP already installed on the tablet..
What can I do to install a recovery so I can change the ROM installed? The device is already rooted.
Do you have a CWM bootloop where it always boots to CWM recovery?
frederuco said:
Do you have a CWM bootloop where it always boots to CWM recovery?
Click to expand...
Click to collapse
No Sir. I can't boot into recovery.
Ok, Did GooManager ask for root permissions when trying to install the OpenRecovery script?
Also, here is an EasyFlasher tutorial, including how to update the naked drivers: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
frederuco said:
Ok, Did GooManager ask for root permissions when trying to install the OpenRecovery script?
Also, here is an EasyFlasher tutorial, including how to update the naked drivers:
Click to expand...
Click to collapse
Yes it asked for root permission when I clicked to install OpenRecovery Script. I just saw your post in another forum right before you post your reply and realized that my ATX driver appears with an exclamation on the device manager, this must be why the EasyFlasher is not working... I must install the naked drivers
If you cannot get the naked drivers to install, it could be an issue with your USB cable. I had my USB cable stop working for data (MTP/PTP/APX/ADB) however it still works to charge using the Asus wall wart. New cable fixed it up straight away.
frederuco said:
If you cannot get the naked drivers to install, it could be an issue with your USB cable. I had my USB cable stop working for data (MTP/PTP/APX/ADB) however it still works to charge using the Asus wall wart. New cable fixed it up straight away.
Click to expand...
Click to collapse
Hey man, do you know how can I discover the SBK from my TF101? My serial number is just... numbers.. no B70... no letters...
Am I looking it in the right place? (Android general configs -> about -> status -> serial number )
It is the sticker by the charging port if you didnt remove it or let it fall off. It is also on the original box if you have that.
I followed the procedure you described in your Guide, turns out my TF101 was SBK2.... It successfully flashed the TWRP and displayed that command prompt message. The naked driver was the key to it. Thank you awesome friend! :laugh::laugh: