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.
Related
Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Can you still get into clockworkmod recovery touch? If you can try using the ADB from there to 'adb push rom.zip filepath/filepath' to get it onto your Internal SD and then reflash from there. I just use cwm 3.2, it's rock stable and never gives me issues, and after reading all of the issues with new versions and lack of ext SD support I refuse to update.
Darth Valda said:
Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Click to expand...
Click to collapse
You 101G is NOT nvflash compatible. You don't have SBK v1.
The only thing you can try is ADB push the necessary files to the internal sd storage.
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Darth Valda said:
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Click to expand...
Click to collapse
Good to hear you got it working. Just a little FYI for the future.
Nandroid restore does not restore the kernel so next time just flash the ROM before or after the nandroid restore. That should put the correct kernel in place for it to boot up.
Did you try reflashing an earlier kernel? Those backups haven't been designed to store/restore kernel data (for us anyway). I think I had a similar experience, back when I was trying early AOSP ICS.
Hey! Thanks for the heads up, everybody!
I always thought that the nandroid backup restores everything (e.g. ROM, settings, base, kernel, etc.). That explains why the restore after the screwed up update to ICS didn't work anymore and why I got stucked in a bootloop again.
So even that seems not to be the last line of defense if you brick your device....
OK. This is an older TF101G, which was running ICS, but needed to go back to stock.
My first mistake was to follow a thread which installed the stock WW HC image, but with an US stock recovery. There, I could not get updates.
I tried to fix this by rooting this monster with nachoroot. I rooted successfully. My second mistake was to use RomManager to install CWM. Though it says it has the right image, this does not work. You can boot into it, but it cannot mount the sdcard, nor can it install any zip. The machine still boots into ICS.
To recover from this, I did my third mistake. I followed an advice to insert a blob from this web page with dd to mmcblk0p4. The blob is the boot blob from CM9.1. However, now this boot blob cannot start the ICS system. It hangs at the boot logo. I can still boot into CWM, however.
To recover from this, I tried booting as far as it goes, and starting adb shell. The screen is showing a boot logo of the Transformer at that time. But the su command now longer works and hangs the shell. This beats me. Otherwise I would have tried the blob from the ICS version I installed.
Is there any way to get out of this mess?
Update:
I tried re-rooting with nachoroot. But trying to push nachoroot.bin to /data/local fails because of "permission denied". Pushing to /mnt/sdcard works. But I am not permitted to chmod to 777 there.
I solved this for the moment
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into HC!
It remains to find out how to get a working CWM recovery to this device, so I can put an ICS ROM on it.
mga010 said:
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into ICS!
It remains to find out how to get a working CWM recovery to this device.
Click to expand...
Click to collapse
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.
frederuco said:
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.
Click to expand...
Click to collapse
Yeah, thanks, I used this tool to flash a working recovery when I was on ICS.
Now I am on rooted HC and a useless CWM. I could use the recoveryblob in the PERI tool and do the same dd trick I did with the boot blob. But I want to make sure this recovery will cooperate with my HC system. At least there should be a way to revert.
I don't see why it wouldn't work with HC.
Experience?
frederuco said:
I don't see why it wouldn't work with HC.
Click to expand...
Click to collapse
There are users which report on the PERI thread about problems with HC.
No Ideas
So nobody knows how to update my Transformer? The remaining problem is that I have HC (stock) running with a disfunctional CWM recovery.
Maybe I will live with it for a while and open a new thread later.
Solved, I hope!
Ok. I solved this too. I found TWPR 2.2 on the net and took the recoveryblob out of it. Then copied this to /dev/block/mmcblk0p4 with
dd if=recoveryblob of=/dev/block/mmcblk0p4
Reboot, and got my new recovery. I hope I can install and decent ROM now.
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the stock ROM?
Hi, I could use a little help. I've flashed a few roms before, but I really got myself into a tough spot this time. I downloaded Slimrom because the one I flashed before that would slow my device down and generally just didn't run as good as I had hoped. I went into TWRP recovery, wiped the caches, flashed the rom and gapps, but it said that the archive/s were corrupt. I have a few backups, but they are all on an external hard drive. I knew I had to get the Android SDK, Java JDK, New ROM, and use adb if I wanted to fix it, but this is where I've been running into a few problems.
I made sure that the drivers for the phone were installed, I kept getting errors though. I looked at the device manager and it shows the yellow triangle and if I try to troubleshoot it says that there are no compatible drivers for my phone. I looked back at the device manager and noticed it connected with the Media Transfer. I can see the device in adb at the bootloader, but not at the recovery. When I push the rom to the phone from the bootloader using adb push ROM.zip /sdcard/ROM.zip. This fails to copy and says there is no directory. Using adb push ROM.zip /sdcard/ it fails and says it is a directory. I've tried more than this, but I can't seem to get it pushed/sideloaded onto my d800 G2.
Thanks in advance for any help or advice. I apologize if I have been doing it wrong the whole time, it's my first time having to use adb.
UPDATE: I got it into download mode and flashed the stock KK update. Thanks anyways
Hi,
I have a 32GB LTE RoW NVIDIA SHIELD Tablet, in France.
I rooted my tablet shortly after receiving it in December 2014, and haven't really upgraded the OS after that, so I'm still on the 2.1 software update (running Android 5.0.1). I never installed CWM or TWRP.
My tablet is one of the tablets affected by the recall (I checked the serial number), but since I'm still running the 2.1 software upgrade and need the 3.1 software upgrade to go through the recall procedure, I tried using the builtin OTA installer, which errored once it rebooted to install. I then told myself it was probably because my tablet was rooted, so I tried unrooting with SuperSU, which errored. I then tried flashing a new recovery.img using fastboot, but when I select `fastboot protocol` from the recovery menu, it just cycles back to the recovery menu. I attempted to re-root with towelroot and SuperSU but towelroot froze and SuperSU failed.
I'm really not sure what to do at this stage and I'm afraid I might have bricked my tablet. It boots into the Android OS just fine, but I'd both really enjoy doing the software upgrade and doing the tablet recall. Any help is greatly appreciated, though I'd like to avoid answers discouraging participation in the recall if possible.
A million thanks in advance,
MrAster
EDIT: I have a machine running both ArchLinux and Windows 10, so I can use any tools available for those platforms. The Linux install has a full Android SDK on it, including fastboot.
MrAster said:
I then tried flashing a new recovery.img using fastboot, but when I select `fastboot protocol` from the recovery menu, it just cycles back to the recovery menu.
Click to expand...
Click to collapse
That's supposed to happen.
In any case, given that you're rooted, the easiest solution would probably be to download the latest recovery image (3.1) from Nvidia and flash boot and system from there (and maybe staging too, not sure if that's needed).
Bogdacutu said:
That's supposed to happen.
In any case, given that you're rooted, the easiest solution would probably be to download the latest recovery image (3.1) from Nvidia and flash boot and system from there (and maybe staging too, not sure if that's needed).
Click to expand...
Click to collapse
Thanks for your reply!
I'm not rooted anymore (although I was), `su` returns -1 and I can't re-root for some reason.
I'm currently downloading the recovery image. Once it's downloaded (I'm at 120KiB/s, so it might take a while) and the images are flashed, what do I do?
Everything seems fixed now, thanks for your help! I did the rebate and am now waiting for my replacement unit to arrive.
Bogdacutu said:
download the latest recovery image (3.1) from Nvidia and flash boot and system from there
Click to expand...
Click to collapse
After doing this, the tablet works fine, but nor MTP nor USB Debugging are working. While booted into Android, the tablet is not getting picked up on any computer, with any cable I try. It gets detected while I'm in TWRP and in fastboot, so I really have no idea what's going on.
I think I saw this same issue mentioned somewhere before. Try also flashing the DTB from the recovery image you've downloaded.