Hi all,
So I need some help. I was in the process of rooting and installing a rom on my TF300T a while back. So I got TWRP 2.6.3.0 installed, and before I could get a rom installed I started having issues with my computer. So I reformatted my hard drive and reinstalled windows. After that, I put back on minimal adb and fastboot, the ASUS drivers, etc. and things seemed like they weren't talking to each other anymore. Fastboot will see the device, but I can't do anything, tried flashing a newer version of the recovery to no avail, and adb kill me the "server is out of data. killing..." message.
So this is where I'm at, any help would be greatly appreciated!
Anyone have any insight into this?
macinjosh1 said:
Anyone have any insight into this?
Click to expand...
Click to collapse
if you are already rooted you can flash a newer version of twrp from terminal emulator
Related
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.
Hello, I think I've bricked my device...
I had Google Play issues, error 403, 920, 923, so I tried a fullwipe which I had used without any problems on my Desire HD. But I've encountered big issues on my Nexus 5...
It's stuck in bootloop, but I can get it to fastboot and recovery. I can't get it to mount USB-OTG (think that's wiped)
It won't show up in ADB (I am in fastboot), worked BEOFORE I flashed Custom Recovery (it broke after I installed), and did not work before I got all the errors. I can sideload CM11, but flashing wont help.
Any thoughts?
I'll try to get adb to work in fastboot, reinstalling drivers etc....
Thanks!
EDIT: Here is the zip i flashed do a full wipe. So you scriptheads know what messed things up
Potetsjokolade said:
Hello, I think I've bricked my device...
I had Google Play issues, error 403, 920, 923, so I tried a fullwipe which I had used without any problems on my Desire HD. But I've encountered big issues on my Nexus 5...
It's stuck in bootloop, but I can get it to fastboot and recovery. I can't get it to mount USB-OTG (think that's wiped)
It won't show up in ADB (I am in fastboot), worked BEOFORE I flashed Custom Recovery (it broke after I installed), and did not work before I got all the errors. I can sideload CM11, but flashing wont help.
Any thoughts?
I'll try to get adb to work in fastboot, reinstalling drivers etc....
Thanks!
Click to expand...
Click to collapse
Make sure you are using a recovery designed for the Nexus 5, and not the one you used on your old phone. Link is in my signature.
Flash factory images (return to stock). Link in signature.
Potetsjokolade said:
Hello, I think I've bricked my device...
I had Google Play issues, error 403, 920, 923, so I tried a fullwipe which I had used without any problems on my Desire HD. But I've encountered big issues on my Nexus 5...
It's stuck in bootloop, but I can get it to fastboot and recovery. I can't get it to mount USB-OTG (think that's wiped)
It won't show up in ADB (I am in fastboot), worked BEOFORE I flashed Custom Recovery (it broke after I installed), and did not work before I got all the errors. I can sideload CM11, but flashing wont help.
Any thoughts?
I'll try to get adb to work in fastboot, reinstalling drivers etc....
Thanks!
EDIT: Here is the zip i flashed do a full wipe. So you scriptheads know what messed things up
Click to expand...
Click to collapse
You wiped your os. You either need to side load a zip with adb. Or return to stock with the factory image
Edit, what did you use a script to wipe your device for? That's crazy, especially since it's not for the n5. You may be hosed because that script messes with a whole bunch of partitions which I'm sure don't align with the n5
jd1639 said:
You wiped your os. You either need to side load a zip with adb. Or return to stock with the factory image
Edit, what did you use a script to wipe your device for? That's crazy, especially since it's not for the n5. You may be hosed because that script messes with a whole bunch of partitions which I'm sure don't align with the n5
Click to expand...
Click to collapse
haha, I know, I wanted to wipe the device (get it?). I was affraid I had wiped the adb drivers on my n5 (lol), I got adb in fastboot to work, and I flashed stock image. Everything works now.
Potetsjokolade said:
haha, I know, I wanted to wipe the device (get it?). I was affraid I had wiped the adb drivers on my n5 (lol), I got adb in fastboot to work, and I flashed stock image. Everything works now.
Click to expand...
Click to collapse
Glad it's working. You dodged a bullet. I'm sure you won't do that again.
that zip is not made for the N5... u cant flash wipe zips made for other phones
Potetsjokolade said:
(snip) I got adb in fastboot to work, and I flashed stock image. Everything works now.
Click to expand...
Click to collapse
You mean you got FASTBOOT to work in the BOOTLOADER.
Sent from my Nexus 5
BTW these Google play issues were happening all day today. It wasn't your device.
sent from my hammerhead
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
I did a factory image install of the latest from nVidia then let it update to 5.01. Made sure it was unlocked, put CWM on it, was able to go from bootloader into CWM, installed SuperSU, rebooted. No root. Went into recovery ... and it's the stock recovery ("No command"). Tried this multiple times in multiple ways and no matter what happens, once it boots into the system, CWM is gone.
Is this something I've done wrong or is this something to do with 5.01? I don't understand how it can be the latter given that I'm not seeing anyone else with this problem. Help!
Solved
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
kmellis said:
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
Click to expand...
Click to collapse
can you help me out? Im getting the image of the android on its back with a red triangle and "no command" under it.
not sure if im even doing it correctly
EDIT: Never mind I got it working just had to use the cmd prompt to flash once I did "adb reboot bootloader" from there I followed the steps. thank you everyone who made this possible.
Hello guys,
i have a big problem. My OPO is hardbricked. I have deleted all data from my phone and installed the newest stable cm release recovery. Before was TWRP 2.8.4.1 running on it. Now i cannot access the recovery nor the bootloader with the Volumedown+Powerbutton Combo. The only image I see is the OPO starting screen. On addition to that I cannot use adb because the phone is telling my pc unauthorized or offline. I am on a Linux PC.
Thanks already for your help.
Best regards
Opfergott said:
Hello guys,
i have a big problem. My OPO is hardbricked. I have deleted all data from my phone and installed the newest stable cm release recovery. Before was TWRP 2.8.4.1 running on it. Now i cannot access the recovery nor the bootloader with the Volumedown+Powerbutton Combo. The only image I see is the OPO starting screen. On addition to that I cannot use adb because the phone is telling my pc unauthorized or offline. I am on a Linux PC.
Thanks already for your help.
Best regards
Click to expand...
Click to collapse
solved