Here goes:
I have a TF101 WW with root and CWM. I recently had a bootloop problem, which I managed to fix with roach's version of CWM. Then the next update from Asus came out (9.2.1.24), which failed to install, apparently because CWM is in the way.
I then waited for the downloadable update to be available on Asus' website, I temporarily unrooted with OTA Rootkeeper and installed the zip through CWM.
Upon reboot, everything seemed fine, version checked out, until I tried rerooting with Rootkeeper. Rootkeeper apparently lost its protected backup of su and couldn't reroot.
So I tried rebooting to CWM to install Superuser-3.0.7-efghi-signed.zip and get my root back, only to see the dead android logo with a red warning sign.
Next I tried connecting through adb, which has always worked before... until now.
When I insert the usb in my pc, I don't even get the usual 'new device' sound and the adb devices list remains empty. Same in apx mode.
Any ideas? My device works just fine, except for apps that require root, booting into recovery and connecting through adb. I really would like these things fixed if possible...
[email protected] said:
Here goes:
I have a TF101 WW with root and CWM. I recently had a bootloop problem, which I managed to fix with roach's version of CWM. Then the next update from Asus came out (9.2.1.24), which failed to install, apparently because CWM is in the way.
I then waited for the downloadable update to be available on Asus' website, I temporarily unrooted with OTA Rootkeeper and installed the zip through CWM.
Upon reboot, everything seemed fine, version checked out, until I tried rerooting with Rootkeeper. Rootkeeper apparently lost its protected backup of su and couldn't reroot.
So I tried rebooting to CWM to install Superuser-3.0.7-efghi-signed.zip and get my root back, only to see the dead android logo with a red warning sign.
Next I tried connecting through adb, which has always worked before... until now.
When I insert the usb in my pc, I don't even get the usual 'new device' sound and the adb devices list remains empty. Same in apx mode.
Any ideas? My device works just fine, except for apps that require root, booting into recovery and connecting through adb. I really would like these things fixed if possible...
Click to expand...
Click to collapse
OTA Rootkeeper only work when you let it OTA update. When you flashed the firmware from Asus, you unrooted and restore stock recovery, that's why you see the Android with red ! mark.
See if you can get into system/bin if there's a su there try and copy it to system/xbin and see what happen (hopefully you still have partial root).
No such luck. Su is gone from both bin and xbin.
So I gather I can't boot to recovery because it has been restored to stock recovery. Bummer.
Some additional questions [semi-noob alert]:
If updating through OTA doesn't work with CWM, and updating through CWM removes root and CWM, how am I supposed to update?
If restoring to stock and unrooting is that simple, why does Wolf go through so much trouble?
Why did I lose usb-connectivity?
If adb doesn't work, is there a way to reroot my Transformer?
For future cases, once I am rooted again, is it possible to put a copy of su on an external microsd, give it the right permissions and stuff, and keep that as a backup to re-acquire root in similar cases? Or can su only work on /system?
I know it's a lot of questions, I'd be happy with answers to any one of them
-you update by waiting for a cwm flashable zip from one of the dev.
-wolfs thread has nothing to do with unrooting, his is downgrading to a rootable version or striaght pushing a recovery to flash su binary plus su zip
-some peoples report loosing usb when updating to ics, try going into system settings, storage, usb pc connection and see if mtp is check off
-for adb try another driver
sorry for all lower case, some reason shift button not working on my mac any more.
Yeah, sorry your going to have to re-root
On the bright side, you can use NvFlash now if you're inclined too xD
[email protected] said:
No such luck. Su is gone from both bin and xbin.
So I gather I can't boot to recovery because it has been restored to stock recovery. Bummer.
Some additional questions [semi-noob alert]:
[
For future cases, once I am rooted again, is it possible to put a copy of su on an external microsd, give it the right permissions and stuff, and keep that as a backup to re-acquire root in similar cases? Or can su only work on /system?
I know it's a lot of questions, I'd be happy with answers to any one of them
Click to expand...
Click to collapse
No, because microsd is mounted with nosuid.
You must place the backup on a filesystem which is mounted without nosuid.
Thx for the replies. Now I understand how I got into this situation. Still don't know how to get out of it, though
Key to the solution seems to be to get adb working.
I enabled usb debugging on the tablet, checked MTP off in storage settings and removed and reinstalled asus sync. I tried connecting both with asus sync running and with asus sync disabled on the pc. I made sure to shut off the splashtop streamer service.
I tried this on my usual pc (where adb used to work before update) and on a seperate laptop.
I took pretty good care of my connection cable so far, so I strongly suspect it is still in working order.
Result is nothing at all. No notification sound upon connecting, no tray popup discovering new hardware, no device in asus sync, no devices in adb, no usb debugging icon on transformer.
(EDIT: I lied. Result is that the transformer screen turns on upon insertion and removal of the usb plug in the pc.)
Anything else I can try?
@baseballfanz: what exactly do you mean by 'for adb try another driver'. Where can I find alternate drivers?
EDIT: I dual-boot W7 and Ubuntu, how do I go about trying to connect with adb from Ubuntu?
Hi.
I assume you're running windows.
Kill the process "asusUPCTLoader.exe" and try adb again.
If you need to reroot, flash CWM with nvflash, then flash SU from cwm.
Wheelie has been released and allows for SBK2 (b70+) devices to use nvflash.
http://forum.xda-developers.com/showthread.php?t=1676845
You will need a linux virtual machine/livecd though.
Ubuntu doesn't need drivers, just download the android-sdk and put it somewhere, it'll have executable adb in it.
whitekidney said:
Hi.
I assume you're running windows.
Kill the process "asusUPCTLoader.exe" and try adb again.
Click to expand...
Click to collapse
no luck, same thing. Also, I tried reinstalling the android-sdk platform-tools to get the latest and greatest adb, but no dice.
Tried getting adb to work in Ubuntu also, but no luck.
whitekidney said:
If you need to reroot, flash CWM with nvflash, then flash SU from cwm.
Wheelie has been released and allows for SBK2 (b70+) devices to use nvflash.
http://forum.xda-developers.com/showthread.php?t=1676845
You will need a linux virtual machine/livecd though.
Click to expand...
Click to collapse
Ok, I went to that Wheelie site, looked at the instructions and didn't understand anything about it. What exactly is nvflash? Do I need adb for that or (as I understand it) is it more low-level and doesn't require drivers and such?
Obviously that link is for users who have a basic knowledge of what nvflash is, what it can do and how to do it.
Both nvflash and wheelie require access to the usb device with Vendor ID 0×955 and Product ID 0×7820. If you are unable to set this up yourself, it’s recommend to run the tools with “sudo” or as the root user.
All usage requires booting your tablet into APX mode by connecting it to USB, turning it off and turn it back on while holding Volume Up!
Included scripts (full reflash)
SBKv1
./reflash_sbkv1.sh
SBKv2
./reflash_sbkv2.sh
In order to use this, you will need to download a full update from ASUS for your SKU and unpack the “blob” file from within the zip using the provided blobunpack tool. We recommend sticking to 100% stock blobs for this step and then root afterwards!
Click to expand...
Click to collapse
Vendor-id? Product-id? SBKv1 or v2? Help!
Before trying NvFlash, uninstall any ADB related or asus-sync stuff, and try my PERI root tool (In my signature) It might help you out getting recovery adb and root back.
it seems that i thoroughly wiped my tablet and now it has no OS at all the pic below is all i got and i cant do anything else. so how screwed am i?
*EDIT* ok so i managed to get it to the point where the 4 icons are :RCK android USB wipe data: by running the command abd reboot bootloader. but it says its in cold boot and was stuck there where i could do nothing but shut it back down. any ideas what i should try next?
You are doomed!
J/K.
Have you try to install TWRP and flash a custom ROM? Looks like your tablet is already unlocked.
i did have twrp and was running clean rom 2.5. i was gonna sell it today and my eagerness to wipe it clean i failed to have a ROM zip file ready to go and wiped the system. from what i can tell i no longer have an OS.
so i might in fact be doomed
hellcatt said:
i did have twrp and was running clean rom 2.5. i was gonna sell it today and my eagerness to wipe it clean i failed to have a ROM zip file ready to go and wiped the system. from what i can tell i no longer have an OS.
so i might in fact be doomed
Click to expand...
Click to collapse
As long as you can still get in the bootloader you'll be fine (others might correct me here). You should be able to get into USB mode and use ADB on another machine connected via USB to copy a ROM to the internal SD card. I also think TWRP can load a ROM off the removable SD card.
Good luck.
i mean i have no recovery now or anything. i can turn it of with the reset button and vol+ but if i turn it on that pic is all it does. and i cant even find a twrp download
*EDIT* ok so i managed to get it to the point where the 4 icons are :RCK android USB wipe data: by running the command abd reboot bootloader. i cant flash a rom off of my external sd card
is there anything i can flash from my exsd using twrp 2.2.1.5. right now my tablet is still not found in abd or fastboot
You'll be fine.. go here
http://forum.xda-developers.com/showthread.php?t=2029364
Follow directions 2nd post... that'll get back so you can flash a rom...
Sent from my ASUS Transformer Pad TF300T using xda premium
well that updated twrp to 2.3.0.1 but i still cant flash a rom. i still have no OS
download a rom to your external SD card, flash it from twrp...
Sent from my ASUS Transformer Pad TF300T using xda premium
yea i was doing that with a few roms but finally that overclock rom worked and now im flashing blackbean. thanks for the help i think im all good.
hope someone else gets help from this short thread
i started out bu using this site for my info to flash cwm to my tablet. after my research i was able to get it on and open it. however i could not mount my internal sd or extrenal sd for the life of me. i tried with usb debug on and with it off. nothing. i then read that twrp had a working recovery image for the tf300 so i tried that as well. i flashed it over but now my tablet will not boot into the custom recovery, it just freezes. i couldnt care which recovery i use i just want to be able to root my tablet and have a recovery for it. neither of which i have despite my work. i understand how to get root but i can not get my custom image to work.
extra details. the image is for jelly bean 4.2 and the asus tf300. i also flashed twrp straight over cmd.
thanks in advance
Hi did you fix this problem? I have same problem now
Hi all,
I have a TF300T with stock 4.2.1 android.
As i also own a nexus 7 with cyanogenmod, i decided to also give it a try on my TF300T
Unfortunately it ended in a endless loop of CWM recovery :crying:
This is what i did :
- i started with this thread http://forum.xda-developers.com/showthread.php?t=2055430
- it reference to another thread that describes how to install CWM recovery - > http://forum.xda-developers.com/showthread.php?t=1668173
I followed all 9 point in the CWM installation guide.
After that i wanted to flash the root zip and recognized that the CWM is not able to mount the sdcard and internal memory.
So i was not able to root the device and also not able to flash any custom rom.
After reading in the forum i was able with "adb reboot fastboot" to boot again into the stock ROM.
- Reading more in the forum i learned that TWRP should have been used . So i tried with fastboot to overwrite the existing recovery , but with no success.
- Reading even more in the forum i saw that there is a way to remove the CWM by restoring the orginal stock ROM with the folloing command.
"fastboot -i 0x0B05 flash staging blob" with blob coming from TW_epad-user-10.6.2.6.zip from asus web page.
After that i can not even reboot to the stock android ROM.
I still have CWM after booting of the device.
I can still open adb shell. But su is not working as i do not have root.
What is the best way now to get back to a working android on my TF300T?
Many thanks in advance for any good hints.
/BR
Is that the firmware that was already on it? I'd try installing 10.6.1.15.3 which is the newest firmware via fastboot. Should erase the recovery. I wouldn't do the 27.3 firmware, not all ROMs support it
as i do not have fastboot anymore , how to flash the stock ROM?
Can this be done with adb?
Or is there a way to get fastboot again?
I currently have endloess boot loop into CWM.
And as i can not access in CWM the sdcard and internal memory i am not able to flash anything.
I just saw this thread here - > http://forum.xda-developers.com/showthread.php?t=2236885
They had similar problems and also no fastboot
Other point is , do i need root access to fix it?
Even with adb i can not push files as the partitions are not mounted.
What about using sideload feature in CWM? will this allow to send a custom rom zip?
I finally got back my fast boot.
I made an hard reset (with hole below sdcard)
After that I could start the tablet with volume down and got back to fastboot
By that I am now able to start again the stock android that was already installed. So as long as I do not shutdown the tablet I at least can use it.
I see quiet a lot of discussions in the forum about soft brick tf300 after 4.2.1 ubdates.
I will now follow these and see if there will be a proper solution for my issue.
Thx
Sent from my Nexus 7 using xda app-developers app
kreutpet said:
I finally got back my fast boot.
I made an hard reset (with hole below sdcard)
After that I could start the tablet with volume down and got back to fastboot
By that I am now able to start again the stock android that was already installed. So as long as I do not shutdown the tablet I at least can use it.
I see quiet a lot of discussions in the forum about soft brick tf300 after 4.2.1 ubdates.
I will now follow these and see if there will be a proper solution for my issue.
Thx
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Found a recovery that actually works with 10.6.1.8 (4.2 bootloader): http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Good to get you back to flashing happy. Not sure if it works with the 10.6.1.27. update though.
Finally have reached my goal...
CyanogenMod 10.1 nightly , trap, rooted....
After Ben back to stock I used this guideline staring from 4.2.1 stock
http://www.android-hilfe.de/root-cu...1-10-6-1-15-3-twrp-recovery-2-5-0-0-root.html
Sent from my Nexus 7 using xda app-developers app
Asus TF300T issues with CWM 6.0.2.3
I bought an Asus TF300T for Christmas 2014. It had JellyBean 4.2.1 on it.
I decided to try to update the device to Lollipop CM12 and admittantly I am a noob when it comes to Android tablets.
So, I installed the ClockworkMod (which installed correctly), but it has my tablet stuck in a loop. It won't mount the /sdcard
and when I open a Command Prompt with Administrator Privileges and attach the usb cable to the device, it won't find it.
I've downloaded the stock rom from Asus for the device and placed it on a 2 GB MicroSD Card that the device will not find or see.
After reading through this thread, I am feeling a bit out of my league on how to recover the device.
Any assistance would be greatly appreciated.
Just got my Nexus 5 and I decided to root it. I used the Nexus 5 Multi-Tool to first install the drivers and then continued to unlock the bootloader and root it.
The bootloader unlocked just fine and I got the choice to install CWM or TWRP. I chose CWM first. CWM then gave me a messae that it couldn't mount my sdcard, but it did ask me to fix root permissions. I selected yes and rebooted. My phone then went into bootloop. I tried to restore to avail. Installing TWRP gave me the same message as in CWM (can't flash any ROMs in both recoveries either).
What's weird is, that when I connect my phone to my PC Windows detects it as a MTP USB Device. It isn't supposed to do that if I enabled USB Debugging, right? (I did enable USB Debugging before anything).
How do I proceed? Help is appreciated.
wouwousoft said:
Just got my Nexus 5 and I decided to root it. I used the Nexus 5 Multi-Tool to first install the drivers and then continued to unlock the bootloader and root it.
The bootloader unlocked just fine and I got the choice to install CWM or TWRP. I chose CWM first. CWM then gave me a messae that it couldn't mount my sdcard, but it did ask me to fix root permissions. I selected yes and rebooted. My phone then went into bootloop. I tried to restore to avail. Installing TWRP gave me the same message as in CWM (can't flash any ROMs in both recoveries either).
What's weird is, that when I connect my phone to my PC Windows detects it as a MTP USB Device. It isn't supposed to do that if I enabled USB Debugging, right? (I did enable USB Debugging before anything).
How do I proceed? Help is appreciated.
Click to expand...
Click to collapse
Don`t you guys ever NOT get in trouble when using toolkits. Toolkits are only suitable for users that know what they are doing and can fix the issue they have and not for lesser experienced users that will be stuck when something goes wrong. Learn how to install and use adb and how to flash .img files. Post your question in the toolkit thread bro, maybe someone can help you there. Good luck
Read this http://forum.xda-developers.com/showthread.php?t=2508292 and this http://forum.xda-developers.com/showthread.php?t=2507905 and this http://forum.xda-developers.com/showthread.php?t=2513701 and you`ll never be in trouble again.
Thanks for your reply.
I have done this many times before on my Galaxy Nexus. That's why I used that tool this time aswell.
However, I got it back to stock with the tool, which reverted to stock android and recovery. I then installed TWRP recovery manually and through there I rooted.
I have no idea what went wrong the first time, but in the future I'll just manually install recovery/root devices since it seems to be much safer.
The same thing happened to me today. I managed to get out of it by flashing TWRP (using the tool) and then in TWRP doing a complete wipe and rebooting. Not sure why the CWM wipe did not do the trick, but that worked for me.