OK, so I got a Xoom last week and shortly after that, managed to Root it successfully using this method: http://forum.xda-developers.com/showthread.php?t=1093126
A couple of days later, I decided to try and copy some pictures, etc. over to my Xoom. I plugged it in via Micro USB port to my laptop (the same one that I used to Root the Xoom). After a minute of churning, Windows 7 32-bit tells me "MTP USB Device FAILED" with a big red X next to it. I tried both with debugging mode on and off and tried all of the available ports on my laptop. Rebooted both devices, nothing. Changed USB cords 3 times, still nothing. I also tried debug mode and ran "adb devices" with nothing appearing in ADB.
I brought the Xoom to my work PC and got the same error there. Finally, I installed the Motorola driver Installer (Moto Driver Utility) and ran the Clean and Reinstall and it still gave the same error.
I went into Device Manager while it tried to install the drivers, and under Portable Devices, it listed "MTP USB Device" properly for a minute, then when it gives the error, there is a Yellow Exclamation point on the icon. Upon further inspection, I get the error message "This device cannot start. (Code 10)"
I am really worried that I won't ever be able to do anything via USB with my Xoom again (Un-root, tansfer files from and to the Xoom, etc.) Can anyone help me out with getting this fixed? I would prefer not to have to Wipe data, but I guess if I must, I must. I wouldn't even be against going back to un-rooted stock (if possible without USB connectivity) and starting over. I get the feeling that my Root process messed with something on the USB port software on the Xoom itself. I have not loaded any custom ROMs yet, it is just stock Rooted.
Thanks in advance!
Thats weird. I rooted mine last night, and works fine. Have you tried to factory reset it?
Back up everything w/ Titanium to a SD card if you can. If not then your gonna lose all data. Try to factory reset it, and see if that works.
mithusingh32 said:
Thats weird. I rooted mine last night, and works fine. Have you tried to factory reset it?
Back up everything w/ Titanium to a SD card if you can. If not then your gonna lose all data. Try to factory reset it, and see if that works.
Click to expand...
Click to collapse
I backed up using MyBackup Pro (Titanium force closes on me for some reason), then wiped and it now works properly.
When I first went into MyBackup Pro, it didn't ask for Superuser permissions, nor did it say I had root access like it normally does on first startup after a wipe. I exited out, went back in and now Superuser asked me to give permission and it shows I have root access.
When I ran the Root process (one-click Root by amoamare), I had to run it 3-4 times before I got the "Root Successful" message, so I have a feeling that the Root process may have messed with things on the Xoom causing all the headaches.
I think my problem is just isolated to my Xoom, and I found the resolution on my own by wiping the device per a Developer's suggestion. It is ok to close this thread.
Thanks mithusingh32 for the response, I was in the middle of wiping when you sent your response
WorldOfJohnboy said:
I backed up using MyBackup Pro (Titanium force closes on me for some reason), then wiped and it now works properly.
When I first went into MyBackup Pro, it didn't ask for Superuser permissions, nor did it say I had root access like it normally does on first startup after a wipe. I exited out, went back in and now Superuser asked me to give permission and it shows I have root access.
When I ran the Root process (one-click Root by amoamare), I had to run it 3-4 times before I got the "Root Successful" message, so I have a feeling that the Root process may have messed with things on the Xoom causing all the headaches.
I think my problem is just isolated to my Xoom, and I found the resolution on my own by wiping the device per a Developer's suggestion. It is ok to close this thread.
Thanks mithusingh32 for the response, I was in the middle of wiping when you sent your response
Click to expand...
Click to collapse
In the future it probably would be good to avoid the "one click" rooting methods. Glad it has all worked out.
okantomi said:
In the future it probably would be good to avoid the "one click" rooting methods. Glad it has all worked out.
Click to expand...
Click to collapse
Honestly, it doesn't matter to me using the one-click method or the manual way, the Xoom tablet is really just not an easy device to Root. I manually Rooted my Thunderbolt phone in about 25 minutes (most of that time was rebooting), never having rooted a phone before in my life.
With the Xoom, the one-click method was quirky, but it only took me about 30 minutes all said and done to root it despite the issues.
I tried to go back to stock/locked device (start from scratch) and it took me almost 2 hours, and another hours or so to manually root it properly. This is a very picky piece of hardware.
Related
I have a HTC Thunderbolt and when I try and root it using the SuperOneClick method, it starts the process and almost right away it says waiting for device... and then my computer locks up. I am a beginner and do not know much yet, but if someone has a suggestion on what to do I would sure appreciate it. I have tried restarting computer, doing a factory data reset on phone and nothing seems to make any difference.
Do you have any antivirus software on you pc? If yes, have you tried disabling it (temporarily)?
computer freeze issue
Yes. I have AVG antivirus and I have tried temporarily disabling it for 15 minutes while I try to root my phone but it did not seem to make any difference. Any other ideas?
I would recommend using this method instead to root your Thunderbolt: http://wiki.cyanogenmod.com/wiki/HTC_Thunderbolt:_Full_Update_Guide .
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
HELP! (I used the Debugfs method: http://forum.xda-developers.com/show....php?t=1706588)
I feel like an utter moron at this point, which I think is frustrating me as much or more than my inability to get my new 300T (running .30) rooted, especially as I've managed to root all my other devices with no problems! OK, I'm not terribly familiar with ADB (although I can C/P code to it and not kill things), so I chose this method to try to root. Got everything set on my 300T, downloaded/unzipped the zip, ran batch file. Selected option 1, and watched the code fly by, with lots of "adb out of date, killing". It reboots my 300T a few times, and I get to the end, and check for SU, no dice. I tried downloading it, then running Titanium Backup to test if the root had been done, no luck. AND, now I'm getting an android.process.media error. ARGH!
What am I doing wrong here? Help?
**Also, I just noticed that my computer is no longer recognizing my 300T- as in I pluc the 300T into my computer, and NOTHING happens. I've tried rebooting the computer and the tab, with no luck either way. As far as the computer is concerned (any of them, I've tried it on three computers, same result), there is nothing connected to it at all. I've also tried booting the tab into recovery (pwr + Vol down), and it gives me the dead android with the red triangle/exclamation mark. Somehow, I don't have root, but I've lost recovery.
I have no idea why the computer might stop detecting the tablet. Did you make sure to turn USB debugging on in the developer options? Do other computers recognize it? Have you checked to see if it's listed in Device Manager? Did you try uninstalling and reinstalling the drivers? I would personally recommend using a live Linux distribution and following the step-by-step instructions in Linux. No drivers to install; just install the SDK, and you're good to go.
On another note, the Android on its back when you tried going to recovery, is the stock recovery. It's not meant for you to flash or restore anything. Its only job is to flash OTA updates, which it will only do when there is an OTA.
Edit: I don't know what the prob was originally but I just flashed a different recovery today and it worked. I have no clue what the problem was. I might have been doing something wrong and not even knowing it. Thanks for all the help!
I was trying to root/flash a rom since I haven't touched the tf101 in a long time. I rooted perfectly using 1-Click Transformer Root. At the time I also installed CWM Recovery using 1-Click. Everything was fine. I wanted to use KatKiss ROM and saw that TWRP was one of the better custom recoveries. So I started the process of getting TWRP by using "Frederuco's Guide to Root and ROM the TF101." This is where problem started (and hasn't changed since). I followed the directions carefully- the tf101 can be in APX like its suppose to when using EasyFlasher. I used EasyFlasher to get TWRP recovery. But on the first reboot I got my old recovery from 1-Click. So I just rebooted again. This time I got something completely different. I had two options: "Wipe Data" or "Andriod." Selecting Wipe Data wouldn't do anything other than prompt two messages and would continue as long as I clicked Volume Up on the "Wipe Data" icon. Selecting "Andriod" would "cold-boot linux" as it said on the screen.
Ever since I have retried using EasyFlasher. Since this wasn't working I tried to go back using 1-Click. But I was unsuccessful. Since then I have also tried OneClickRecovery V0.4.2 with no avail. I have tried each of the methods at least five times each yet I still get the same options which basically boot the tablet again.
I have tried using the unbrick feature on OneClickRecovery. It didn't work but I did find something interesting. It said: "/dev/block/mmcblk0p3: cannot open for write: Permission denied." Which meant su wasn't being granted. I did some research on this and I should have been getting asked to grant permission. But I wasn't (I have tried this before and after re-rooting). So I changed SU settings to always grant (confirmed I had root by using numerous different apps that needed root). Which didn't help since I was getting the same error.
I also tried GooManager and trying to install the OpenRecoveryScript. But it didn't work either (it was granted superuser rights).
I also tried flashing Asus Recovery using 1-Click.
Any suggestions? I'm completely lost at this point. I've spend two days and over 7 hours on this reading everything and anything I can find.
I probably forgot to do something but at this point I can't figure it out. If anyone has anything to say let me know! Thanks!
Edit: The OS part works perfectly fine. Its just the recovery.
Are you running the stock ROM at the minute ?
Someone else had a similar issue the other day, and it seemed clearing Cache and Data from Settings > Apps > All > DMClient, then rebooting fixed it and was able to flash TWRP after that
Worth a shot, it sounds like you have the stock recovery installed atm
Your method did not work. I tried it multiple times, each with a different recovery flashing program. Any other suggestions?
Update: Solved.
Summary of issue: two identical devices side-by-side, s-off by Firewater works fine on one and won't work on the other. This rules out a lot of possible issues and so this was not an "I don't know how to use firewater's s-off method" post.
Solution: Factory reset FOUR TIMES. On the fourth factory reset, things worked.
Lesson learned: (After you make sure you're actually doing everything right and with the right files) you might actually have to give this many tries.
Cheers.
Thanks @pjim @Dodge DeBoulet @wtoj34
Hey everybody, Recognized Contributor here, usually the one who’s glad to help everybody else, and I’m totally… at a loss. Thanks X 10 for ANY help. I’m looking forward to contributing and modding on the Verizon M8 soon!
Issue: Two identical CDMA M8 devices, both on my Verizon account. Literally the same activation, using the same usb port, usb cable, computer and human:
Device #1: temproot using WeakSauce.apk; s-off using Firewater; installed the CWM recovery for our device; made a nandroid; flashed iB4STiD’s SkyFall ROM. ALL GOOD 100%.
Device #2: temproot using WeakSauce.apk; …. Firewater’s s-off will not do its thing with device #2. It goes only this far:
Code:
Do you understand the implications of these warnings? (Yes/No)
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
…………………………………
……………………………….
……….. (indefinitely until I disconnect; I've waited 30 minutes just to be sure)
So it STOPS BEFORE the “preparing… the first bottle is open…chugging… ” part.
But… it ran five minutes before. Device #1 is good to go. Device #2? I’ve tried the hold power for 60 seconds thing, used different usb cables, different ports (hey, maybe something broke in the 30 seconds between devices?), redownloaded everything, matched MD5 checksums anyway, hard reboot via adb, repeat, start over like ten times…
For the love of God, can anyone think of what I can be doing wrong?
So funny...........
erikalin said:
Hey everybody, Recognized Contributor here, usually the one who’s glad to help everybody else, and I’m totally… at a loss. Thanks X 10 for ANY help. I’m looking forward to contributing and modding on the Verizon M8 soon!
Issue: Two identical CDMA M8 devices, both on my Verizon account. Literally the same activation, using the same usb port, usb cable, computer and human:
Device #1: temproot using WeakSauce.apk; s-off using Firewater; installed the CWM recovery for our device; made a nandroid; flashed iB4STiD’s SkyFall ROM. ALL GOOD 100%.
Device #2: temproot using WeakSauce.apk; …. Firewater’s s-off will not do its thing with device #2. It goes only this far:
Code:
Do you understand the implications of these warnings? (Yes/No)
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
…………………………………
……………………………….
……….. (indefinitely until I disconnect; I've waited 30 minutes just to be sure)
So it STOPS BEFORE the “preparing… the first bottle is open…chugging… ” part.
But… it ran five minutes before. Device #1 is good to go. Device #2? I’ve tried the hold power for 60 seconds thing, used different usb cables, different ports (hey, maybe something broke in the 30 seconds between devices?), redownloaded everything, matched MD5 checksums anyway, hard reboot via adb, repeat, start over like ten times…
For the love of God, can anyone think of what I can be doing wrong?
Click to expand...
Click to collapse
As an auto technician, when someone says my car wont start my first question is, is there any gas in it? The first thing I would look for is the root. I have literally had weaksauce take up to 3 minutes to get root. If in the excitement you start adb and get firewater running before you get root, it cant write to the system and would get stopped,probably around where you are getting stopped. Make sure root is working before you even plug in the cable. Do something simple like start a root app and grant it before you start. As I read through these forums forums I've seen that this device is not consistent in it's behavior. One will not be the same as the other. Could even be internal, might consider an exchange. Usb ports fail all the time.
Hi. Thanks for taking the time. Yes, I'm waiting for root. Adb wouldn't be able to access root if, well, it didn't have access to root. (Not being sarcastic, just check-listing in my head.) I also have my laptop set to make a noise when it has root access. USB port is fine. Ugh. :/ I'm not sure I can come up with any reason to exchange. Thanks for trying. Cheers.
Sent from my SPH-L710 using Tapatalk
erikalin said:
Hi. Thanks for taking the time. Yes, I'm waiting for root. Adb wouldn't be able to access root if, well, it didn't have access to root. (Not being sarcastic, just check-listing in my head.) I also have my laptop set to make a noise when it has root access. USB port is fine. Ugh. :/ I'm not sure I can come up with any reason to exchange. Thanks for trying. Cheers.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I'm assuming you don't have any additional security measures enabled, such as a pattern or password lock (disabling that stuff is in most of the how-to's I've seen). Have you attempted a factory reset/do-over from scratch?
Try some of these I picked up from other forums. Have you tried factory resetting the device? Have you tried re installing adb on your computer? Have you tried removing the firewater file from your phone, and re download it on the pc? Does the firewater file have a (1) next to it? Have you tried uninstalling weak sauce and super su and do adb reboot on your pc then re root? Are you using the same account on your pc as your other phone?
Sent from my HTC6525LVW using Tapatalk
Dodge DeBoulet said:
I'm assuming you don't have any additional security measures enabled, such as a pattern or password lock (disabling that stuff is in most of the how-to's I've seen). Have you attempted a factory reset/do-over from scratch?
Click to expand...
Click to collapse
Hi. Thanks for taking the time to try to help me out. Yes, no security/lock stuff. Have tried factory reset and do-over from scratch at least twice, no joy.
wtoj34 said:
Have you tried factory resetting the device? Have you tried re installing adb on your computer? Have you tried removing the firewater file from your phone, and re download it on the pc? Does the firewater file have a (1) next to it? Have you tried uninstalling weak sauce and super su and do adb reboot on your pc then re root? Are you using the same account on your pc as your other phone?
Click to expand...
Click to collapse
Appreciate you taking the time. No need to reinstall adb stuff on my computer (I use the Android SDK for a lot of things; it's fine). Accounts on PC don't matter. Just "thinking out loud" here. I think I've done every combination of your other ideas too. Thanks again for sharing the ideas though...
There's either something I can't think of trying OR there's some odd little thing wrong inside the second device, and I can't think of any legit reason to bring it back for replacement because it otherwise acts fine. Ah well. People have bigger problems, lol. Cheers.
Update: Solved. See OP.
erikalin said:
Update: Solved.
Summary of issue: two identical devices side-by-side, s-off by Firewater works fine on one and won't work on the other.
Solution: Factory reset FOUR TIMES. On the fourth factory reset, things worked.
Lesson learned: You might actually have to give this many tries.
Cheers.
Thanks @pjim @Dodge DeBoulet @wtoj34
Click to expand...
Click to collapse
Wow, never would have guessed that repeated FRs would do the trick. Was that 4 in a row after your previous attempts, or 4 total throughout the entire S-OFF ordeal?
My own experience was entirely uneventful; the only bit of panic I've experienced with this remarkable phone was well after the root/S-OFF activity, during the installation of GSAM Battery Monitor. Installation of the root companion package required a reboot, and nothing appeared to happen after the confirmation button was pressed. When I manually rebooted, I got what seemed to be a "White Screen 'o Death," with no response from the usual reboot key combo. At some point the display went dark and I was sure it was bricked. I eventually tried the 60 second power button press, though, and it booted normally. Incidentally, GSAM appeared to be successfully installed as well.
USB 2.0 vs 3.0
I also haven't had any good luck with the firewater s off...mine hangs right after I say "Yes" then my phone diaconnects from adb and I have to start the process over again.
I've tried over 30 times, but I think it's been on usb 3.0 ports. I'm going to try on 2.0 and if that doesn't work...factory reset time...