So my transformer will not be detected by any pc over usb. I have tried 3 different pcs, they all give an error that the usb device has malfunctioned.
I installed and reinstalled all the asus software and drivers but can't get it to work. Did a factory reset no go. I am on Prime 1.7
Asus wants me to go in their boot menu (vol down + power) and wipe it. I am just worried this will screw something up since I am rooted and can't connect to a pc if something goes wrong. What do you guys think?
No one has an opinion on this?
You have tried three different transformers and they all error out?
If this is the case it seems like a problem with your computer. Do your USB ports function properly with other USB devices? (Such as USB Flash Drive, etc). Also, have you tried your Transformer on another computer? This will narrow down if it's your computer or your Transformer. If it's your computer than a Wipe is certainly not necessary.
If you are running Windows 7 or Windows Vista there's a bug I get sometimes. In Vista and 7 there's a "generic" built in MTP driver that the operating system has to control the Transformer. Installing the Asus provided driver works as well, however sometimes my computer gets confused and for some odd reason will try to use the generic MTP device driver. Updating the driver forcefully to use the Asus usually does it or simply rebooting my machine.
Sorry if I wasn't clear, I have plugged my one single transformer into 3 different pc's, so I could rule out the pc as the problem.
I am running windows 7 64bit. It has worked fine until all of a sudden. It feels like a hardware problem to me but idk. If I rma I need to put the TF back to factory settings but without the usb working I don't know how.
Since you're already running Prime 1.7, that means you already have CWM working so I would suggest doing a nandroid and then trying out another rom/kernel which might possibly re-trigger your usb to work. You can wipe as well, perhaps even do a wipe all (reset to factory settings) before flashing a new rom. As for RMA, you would unfortunately need to unroot your Asus prior to sending it back, but atm, I don't think there is a method to do so without a physical connection to the PC. Hopefully, reflashing a different rom/kernel will help.... good luck.
heyman123 said:
Since you're already running Prime 1.7, that means you already have CWM working so I would suggest doing a nandroid and then trying out another rom/kernel which might possibly re-trigger your usb to work. You can wipe as well, perhaps even do a wipe all (reset to factory settings) before flashing a new rom. As for RMA, you would unfortunately need to unroot your Asus prior to sending it back, but atm, I don't think there is a method to do so without a physical connection to the PC. Hopefully, reflashing a different rom/kernel will help.... good luck.
Click to expand...
Click to collapse
Good advice, I have just been scared to flash since this happened in case something goes wrong. So what do I flash first a rom or a kernel?
I think maybe the problem was I was running the blade kernel with Prime 1.6 and then just instsalled 1.7 over it. Not sure if thats bad.
So I booted into CM did a factory reset/wipe and installed the revolver rom, no luck, same error, bummer.
lightsout said:
So I booted into CM did a factory reset/wipe and installed the revolver rom, no luck, same error, bummer.
Click to expand...
Click to collapse
looks like you may just be unfortunate with a defective device
was usb working in Prime 1.6? if you came from Prime 1.6, did you do a nandroid before you flashed to 1.7? If you did, try to nandroid back. Other than that, your usb must be somehow borked.
P.S.... just in case, perhaps try a new usb cable?
Actuall I think I have an old backup or two I'll try that. And yah a new usb cable was the first thing I did.
Actuall I think I have an old backup or two I'll try that. And yah a new usb cable was the first thing I did
Click to expand...
Click to collapse
You got a new usb cable from ASUS?
You are connecting with the ASUS connector USB, right?
AustinMartin said:
You got a new usb cable from ASUS?
You are connecting with the ASUS connector USB, right?
Click to expand...
Click to collapse
Yah I got a new asus usb cable. Got it at frys but its is made by Asus for the transformer. And I am plugging it in straight from TF to pc like I always have. I have no dock. I actually just did a nandroid restore and I am hung on the Eee pad splash screen. Gonna give it a minute and I guess reboot. Just rebooted fingers crossed its not stuck.
So how long should it take after a restore? It hung for like 5 minutes so I rebooted into recovery. Wiped it and then tried to restore a different nandroid. Its been sitting again for close to 5 minutes at the asus screen. Should I not be restoring a 3.1 rom when 3.2 was installed.
I ask because I expected to not see the asus splash screen with the nvidia logo but it seems that is still there.
What to do?
**EDIT Idk if its revolver has a different kernel. Does a wipe in CM remove the kernel. I got stuck in a boot loop at the splash screen forever. Went back into CM and flashed Revolver and now I am able to get to the desktop.
Do I need to flash a stock kernel first?
lightsout said:
So how long should it take after a restore? It hung for like 5 minutes so I rebooted into recovery. Wiped it and then tried to restore a different nandroid. Its been sitting again for close to 5 minutes at the asus screen. Should I not be restoring a 3.1 rom when 3.2 was installed.
I ask because I expected to not see the asus splash screen with the nvidia logo but it seems that is still there.
What to do?
**EDIT Idk if its revolver has a different kernel. Does a wipe in CM remove the kernel. I got stuck in a boot loop at the splash screen forever. Went back into CM and flashed Revolver and now I am able to get to the desktop.
Do I need to flash a stock kernel first?
Click to expand...
Click to collapse
Shameless bump any thoughts on this?
Each dev will provide their own kernel they feel that best work with their ROM. You should be able to WIPE ALL, then flash Revolver's 2.1.1 ROM. It will usually take a few minutes the first time it boots up. Once you're able to boot into the OS, you can test your USB connections to see if they work, if not, you can alternatively download Revolver Parts from the Market and download another kernel developed by Clemsyn that works with this ROM. Likewise, you can go the Prime 1.7 route.
Revolver 2.1.1
Prime 1.7
So when I wipe do I clear the cache as well? Also can I flash a HC 3.1rom now? Ifs possible the usb died when I went to prime 1.7
heyman123 said:
Each dev will provide their own kernel they feel that best work with their ROM. You should be able to WIPE ALL, then flash Revolver's 2.1.1 ROM. It will usually take a few minutes the first time it boots up. Once you're able to boot into the OS, you can test your USB connections to see if they work, if not, you can alternatively download Revolver Parts from the Market and download another kernel developed by Clemsyn that works with this ROM. Likewise, you can go the Prime 1.7 route.
Revolver 2.1.1
Prime 1.7
Click to expand...
Click to collapse
lightsout said:
So when I wipe do I clear the cache as well? Also can I flash a HC 3.1rom now? Ifs possible the usb died when I went to prime 1.7
Click to expand...
Click to collapse
when performing a WIPE ALL, you are already clearing the cache, but it won't hurt if you did it again. As long as you do a full wipe, you should be able to flash HC 3.1. But if you already have PRIME 1.6 nandroid, you can nandroid restore that as it is HC 3.1 as well.
heyman123 said:
when performing a WIPE ALL, you are already clearing the cache, but it won't hurt if you did it again. As long as you do a full wipe, you should be able to flash HC 3.1. But if you already have PRIME 1.6 nandroid, you can nandroid restore that as it is HC 3.1 as well.
Click to expand...
Click to collapse
Yah I tried 2 different nandroids. Both from early july. MD5 checked out. But they just hung at the eee pad screen. The last one I left for over an hour. Had to reflash revolver to get it working. I guess I am just going to deal with no usb for now. Better like this than nothing at all. Thanks for your help.
At least you still have Recovery for future rom/kernel release that might possibly fix your current issue, as long as it's not a hardware malfunction. And given time, like most things here on xda, someone is bound to develop a newer/better method, in your case wireless root/unroot, for all of us to take advantage of. Good luck.
should have realized......Just skimmed through the dev thread and saw this --> Easy [UNROOT] without the need for a cable connection!!!!
Make sure to read through that thread and try to unroot your device, then do an RMA =D
heyman123 said:
should have realized......Just skimmed through the dev thread and saw this --> Easy [UNROOT] without the need for a cable connection!!!!
Make sure to read through that thread and try to unroot your device, then do an RMA =D
Click to expand...
Click to collapse
Oh sweet thats great, thanks a lot I will give this a good read!
Related
[Q]Stuck on "Android is Upgrading - Installing Applications" Screen. Any Ideas?
Hi all.
Since 3 days I can't use my Transformer, and everytime I think I fixed an issue, there's another appearing.
At the beginning I was on Mike 1986's AR HD 3.0.1 Rom. Everything went well for like a week. And a morning pressed on the power button, as usual, and tried to slide the lock circle to the small lock icon. Nothing moved. Then I thougt "Perhaps my fingers are cold" I heated them, and nothing changed. I connected my Tab to the dock, and I could mysteriously still use the trackpad.
I rebooted it, still the same problem.
Wiped it and reinstalled ARHD, still the same problem.
Then I tried the NVFlashable stock ICS Rom, and there appeared the problem : The Asus loading screen appeared and stayed... For hours...
Then I re-rooted my tablet, wiped it, and installed the CWM- Flashable ICS. Oh my god! I went further than before! First the asus loading screen : Passed ; Then the "Android is Upgrading - Applying updates" screen - passed; Now I'm stuck on the "Android is Upgrading - Installing Applications" screen.
I'm getting mad!!!
Could someone help me? Is there a solution? Is my TF101 hard bricked? Could I mask the root and so on to send it on RMA ( Final Solution!) ?
Please help me... I read on the prime's forum that flashing a stock Rom after having a custom Kernel wasn't good... The blobs aren't up to date then...
DerSandmann said:
Please help me... I read on the prime's forum that flashing a stock Rom after having a custom Kernel wasn't good... The blobs aren't up to date then...
Click to expand...
Click to collapse
There's no "custom" kernel right now with ICS. Not sure what to tell you, usually an NVFLash would wipe everything and have a "clean" install.
baseballfanz said:
There's no "custom" kernel right now with ICS. Not sure what to tell you, usually an NVFLash would wipe everything and have a "clean" install.
Click to expand...
Click to collapse
+1. You could try doing a restore to true stock by going here
http://forum.xda-developers.com/showthread.php?t=1154947
But usually nvflash or return to true stock fixes most things. If you are still having troubles, bite the bullet and do a RMA.
There's no "custom" kernel right now with ICS. Not sure what to tell you, usually an NVFLash would wipe everything and have a "clean" install.
Click to expand...
Click to collapse
Yeah sorry, I didn't know how to say this, that I read on a Prime thread :
Brick 3: (After messing around with your Prime in recovery it won't boot any ROM anymore, you can however still access fastboot and the recovery)
Update: This particular brick happens due to a bad kernel flash. If you are flashing kernels via the ASUS /staging method, make sure /staging is unmounted before flashing stuff to it, otherwise it WILL faill and brick.
->Please go to Option 3
Click to expand...
Click to collapse
I tried your method, it worked! Thanks! But still no touch input. I'm putting it fully back to stock.. But nothing happens!
RMA'd it. They changed the MB + the Screen...
Since I updated to ICS the pad shuts down or reboots by itself and then it gets stuck on the Asus splash screen, it happens almost every day. Can anyone help me with a solution please??
Sent from my SAMSUNG-SGH-I727 using xda premium
Hi r3dp0is0n2012
I think its safe to safe that this is a ICS/Asus problem. I think in every forum about ics the same complain is there.
I had the same. My tf has nvflash capabilities, so after a week or reboots and hanging, I wiped every thing on my TF. Then put a nvlash version honeycomb back. Then installed cwmrecovery of gnufabio and also rooted the pad again. Then flashed/restored a good working revolver rom 3.11.1 cwm backup on my pad (was my own backup before updating) and all works correct again. Last week I updated/cwm-flashed my pad with revolver 4.0.0. rc1 (after just wiping cache and delvik) and its now rather stable. Only have reboot in 2 or 3 days. but real reboots, so no hanging in boot screen. But this means that ICS is still unstable. So, if you have problems and you know how to go back, or have a good backup, use that......or wait for a fix by Asus.
If you need help to go back, let us know all info of your TF pad? what kind, what serial etc etc....and maybe we can help....
nlheiz said:
Hi r3dp0is0n2012
I think its safe to safe that this is a ICS/Asus problem. I think in every forum about ics the same complain is there.
I had the same. My tf has nvflash capabilities, so after a week or reboots and hanging, I wiped every thing on my TF. Then put a nvlash version honeycomb back. Then installed cwmrecovery of gnufabio and also rooted the pad again. Then flashed/restored a good working revolver rom 3.11.1 cwm backup on my pad (was my own backup before updating) and all works correct again. Last week I updated/cwm-flashed my pad with revolver 4.0.0. rc1 (after just wiping cache and delvik) and its now rather stable. Only have reboot in 2 or 3 days. but real reboots, so no hanging in boot screen. But this means that ICS is still unstable. So, if you have problems and you know how to go back, or have a good backup, use that......or wait for a fix by Asus.
If you need help to go back, let us know all info of your TF pad? what kind, what serial etc etc....and maybe we can help....
Click to expand...
Click to collapse
Thank you for your response, very helpful by the way! I do want to go back and restore it. How can I do this?
Sent from my SAMSUNG-SGH-I727 using xda premium
Sorry was not around a computer yesterday.....
Impotant is to know what kind of TF you have and serial number.
I have a B50.....so I can use nvflash. What is your serial? do you have CWM installed, or can you check if you have a SBK1 or SBK2 TF. Do you have cwm installed, do you have nandroid backup of honeycomb etc etc.....I have some experience with downgrading, but not regarding the SBK2 TF's. Some say that if you download an older updater op asus (see some where in this q&a where you can download it) then unzip it on your sdcard, reboot and your TF will ask if you want to load this "newer" rom. This is also mentioned somewhere in this q&a. maybe that will help. But 1st of all, to be able to help in downgrade, we need your tech info of your TF.
serial number TF
CWM installed (see app of gnufabio)
nvflash possibitities
EDIT: more bad new about this reboot thing
http://forum.xda-developers.com/showthread.php?t=1569670
and see this last post in that thread,
http://forum.xda-developers.com/showpost.php?p=25375664&postcount=87
so, nvflash is your only option seem like.....I hope that you have a nvflash compatible TF (B60 and less and some B70....SBK1)
Hello,
Yep news are getting worst...
my serial number is C10 model TF101
I dont know if that helps.
r3dp0is0n2012 said:
Hello,
Yep news are getting worst...
my serial number is C10 model TF101
I dont know if that helps.
Click to expand...
Click to collapse
Have you tried wiping data?
no I haven't... you mean restoring to factory settings?
Do you have CWM installed on your TF?
Ok I will try to explain this.
If I do the software reset and reboot it comes back on and nothing happens as in nothing gets wiped or reset, nothing changes.
If I do a factory reset it reboots and nothing changes all apps settings even browser history is still there.
If I plug xoom into pc and try to erase storage part of it which windows shows it is and reboot everything comes right back.
I have tried loading the stock img files with fastboot(yes I unlocked it first).
I have even tried a custom rom with a different recovery and after a reboot it is right back the way I left it before I tried anything, no custom rom no custom recovery.
While using the tablet, if I try unistalling an app or several then rebooting it comes back as if I did nothing.
If I install an app it installs then try and use it and it force closes.
I am on 4.04 and IMM76.
It makes no difference what I do to it, after a reboot it goes back to the same stuff that was on there, no changes at all.
Thanks
try to delete everything in sdcard. not external, internal
There is not an sd card in it right now.
Can't you try reflashing your device? Maybe works... I mean the official firmware found on Motodev site.. you can try Stock Install feature of LordAIOTool Linux version (and Linux only! Windows is outdated!) Good luck!
Sent from my 3G Xoom using XDA HD - 1st Xoom Recognized Contributor
I have the same issue
XxLordxX said:
Can't you try reflashing your device? Maybe works... I mean the official firmware found on Motodev site.. you can try Stock Install feature of LordAIOTool Linux version (and Linux only! Windows is outdated!) Good luck!
Sent from my 3G Xoom using XDA HD - 1st Xoom Recognized Contributor
Click to expand...
Click to collapse
I have the same issue as well. Reflashing doesn't do anything because it just reverts back to how it was. It is as if the Xoom is stuck in time
I even contacted Motorola and they had no clue, and I can't get it repaired because it is out of warranty and there is no way I would pay $150 to get it repaired.
Hello, I've got a problem and I'd be very happy for any advice.
I am on rom JellyBean AOSP. I was using my Transformer and sound stopped working. So I decided to turn it off and on again and when I tried to turn it on and I wasn't able to start tablet anymore. I'm stuck on the first screen you see when you turn on the tablet. So I wanted to do factory reset in the recovery. In recovery everything works allright. When I click on the factory reset it says error when deleting something in /data/ and I also can't do "Format /data/" because of the same error.
Here is the log from recovery - https://dl.dropbox.com/u/3045404/recovery.log
How can I completely delete /data/ can I do it somehow from PC for example? I don't care about my data I can lose everything. I just want to get it work. I also tried to flash AOSP JellyBean ROM again, but with the same effect. I think that tablet just can't do the factory reset but I don't know why. Thanks for any advice.
Hi there !
I think you should try to start your tablet into ADB mode, connect it to your computer and use the "adb shell" command. If your tablet was rooted, then you might be able to use the "su" command, but that depends also on your settings (I mean your Android settings... those you can't change anymore ).
Another way to get your TF101 working again is to use the NVflash "unbrick pack". OK, you'll be running the stock non-rooted ROM, but you'll be able to root it again and install a new fresh copy of your Android AOSP. I'm going to search for a link to this nvflash and I'll post it asap.
By the way, were you using the AOSP "alpha" from RaymanFX ?
EDIT : NVflash unbrick pack is here, and you also might want to try with EasyFlasher !
Thanks, I'll try it. Yes, I've been using alpha from RaymanFX. I haven't done anything that could "brick" my device while using the tablet before I turned it off.
This is what tablet shows after I attempt to do a factory reset. https://dl.dropbox.com/u/3045404/DSC05813.JPG
GameEs said:
This is what tablet shows after I attempt to do a factory reset.
Click to expand...
Click to collapse
That's weird. And you're using an old CWM Recovery
I think in most CWM versions there's a "fix permissions" item, you could try this one first. Im' not sure of what it exactly does, but it might do the trick: a permission-related problem seems (to me) a good reason for displaying this kind of errors...
yeah I also tried fix permissions but didn't help. I also remembered that it sometimes freezes even in the recovery. Is it safe to flash a new recovery NOW when I'm not able to startup the tablet? Please could you link me to the best recovery that I should flash? thanks a lot. I'm careful about it and I don't want to do something that would brick my device.
I dunno if it is the best recovery, but I prefer to use the CWM Recovery.
You'll find the 6.x series here.
I actually use the 6.x on my Sony Xperia Ray.
On my TF101, I use this touch Rogue recovery, not as recent as the first one. In fact I never did the update 'cause I'm waiting for the next release of RaymanFX's CM10 release to flash everything
EDIT: And I think you can flash a new recovery safely, because it's not on the same partition as the Android system. And in the case it fails, you should be able to boot in ADB mode and use the NVflash unbrick pack to get your device up and running !
oh god thank you so much. New recovery helped a lot it did factory reset and everything works allright. I would like to ask you one more question. what's in your opinion best rom for Transformer? I just want it to be stable. Because I don't like freezing every day and slow motion through tablet. I tried many roms but it was always unreliable. Thank you )
Great !
About the ROM s, one told me that Revolver is a great one, but I never used it.
I never had problems with CyanogenMod 9. I would recommend that one !
For now I'm running RaymanFX's CM10 build, which is great too !
Sent from my Transformer using xda premium
I'm at wit's end here. My TF101 will not stop rebooting. it doesn't matter what firmware I have on it (stock rooted, stock UNrooted, CM9, Frozn). it just reboots. the majority of the time it goes into a boot loop, or, if I'm lucky, I'll actually get to the homescreen for about five seconds, then it reboots. I just tried flashing the stock rom again. can't even get to the welcome screen now. I Never had this problem until I downloaded a firmware update (for stock ROM)
Using Rogue XM Recovery 1.5.0 (cwm doesn't want to work, for some reason)
S/n: C10KAS158799
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Go back to stock using easyflasher. It'll wipe your device clean, so make sure to back up important data. Then start over. I suggest Fred's guide over at transformeforums, it's the most complete one out there.
frederuco said:
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Click to expand...
Click to collapse
Tried that. Still boot-looping. nothing I do seems to help. so far, I've had the most luck with Frozn. CM9 nor the Stock asus firmware seem to work at all anymore. apparently the recovery is borked too. anytime i try to wipe something, It freezes.
am I just SOL?
(edit) alright, so I tried it again. instead of boot-looping, now it just sits at the Eee pad screen forever
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command (see the terminal method here: http://www.teamw.in/project/twrp2/109)
frederuco said:
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command)
Click to expand...
Click to collapse
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Des0late Law said:
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Click to expand...
Click to collapse
Did flashing the stock ROM replace TWRP? It should have...
frederuco said:
Did flashing the stock ROM replace TWRP? It should have...
Click to expand...
Click to collapse
It did. Now I can actually get into the OS for awhile, but it still reboots randomly (and bootloops, although not as often). I've been doing some googling. apparently the reboot/bootloop problem Is ICS based (or so some think) and, to be honest, I didn't have any problems with it before I updated from Honeycomb. that being said, someone wouldn't happen to have a spare honeycomb ROM lying around, would they? google (oddly enough) turned up nothing, and Android Revolution just leads to dead links...
Edit: never mind, someone fixed the links. will try 3.2 after I get home from work.
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Well, I haven't had the SoD issue, just reboots. I was able to use it most of the day yesterday, before I shut it off myself. It turned on fine this morning, too (rebooted once).
Sent from my LGL75C using xda app-developers app
frederuco said:
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Click to expand...
Click to collapse
Alright. So, I flashed it back to Honeycomb. Haven't had a reset or reboot all weekend. I guess the problem WAS ICS-based. Can't figure why, though.
only downside to that is, can't use some apps on the market. oh well, I'll live!