Related
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.
Hey everyone, I'm quite the lurker on these forums and don't post very often at all. I just want to first and foremost say that everyone here has been amazing and the work that has gone on for this phone is truly astonishing.
Now, with that being said... I'm bricked.
I was running CM7 today and decided (don't ask why) to try that ICS for the i9003. Dumb move. Hopefully someone is getting a laugh out of this as well.
I expected the results to be bad, but not disastrous. In the process of trying to do this I bricked the phone. When I had the ICS ROM on it, it got stuck on the AT&T screen. No worries, I made a back up this morning... I figured just pop back into recovery and restore myself back to normal and everything's fine.
Well, here's where it gets bad. I cannot get into recovery. After multiple attempts of trying to get into recovery. ADB nor Odin even see my phone in download mode. I do have a USB JTAG jig, which has saved me quite a few times.
I started downloading stock ROM's like crazy today. The only one that I could get to install was stock 2.3.5 with Boog's kernel with CWM. I booted into the OS and all seemed well at the time... except there's no modem! I have no internet, service, or anything. This is the only time ADB can see my phone, is when it's booted up. As soon as it's in download mode, ADB can no longer see my phone. The same with ODIN.
ODIN sees my phone when it's booted up, but doesn't actually make the handshake for an install of another version. I've tried to root it, in hopes of being able to push ROM Manager, Super User, and restore my back up in CWM. This didn't work either. During the rooting, using a one-click, it hangs up trying to run the psneuter exploit.
If I'm booted into this 2.3.5 stock of android with no modem, I tried to reboot into recovery using ADB running reboot recovery. This just boots the phone back into Android as if there's no recovery on the device at all.
Soon as I'm back in download mode I cannot push any files with ODIN or ADB. Neither one of them see my device at this point. Even using the JTAG jig.
This is where I'm now at. I'm not sure what else to try at this point. Is there a reason that my device is no longer being recognized in ADB when in download mode?
Any insight would be greatly appreciated. I've been trying to scour forums and search engines with no luck so far. This is my only phone, so it's a little depressing to be without any means of communication on the go, but that's the chance you take...right?
p.s. I do have all the Samsung USB drivers as I normally push files with ADB and have just done so earlier this week. Had the same luck on my computer at work today. So, I know it's not a PC related issue.
Thank you to everyone in advance.
I've also tried to push a modem to the phone with no luck.
I installed 2.3.5 with the Executable JAR of Heimdall AndroidOS 2.3.5 to push the files and that JAR version is the only device that will install to my phone and makes the handshake. Just no modem
You may want to give Heimdall a try - it installs its own USB drivers, so it's possible it might be able to see your phone that way. Nevermind - just saw your post. Which Heimdall did you grab?
Also try switching USB ports - sometimes a different port makes a difference.
There's a one-click in my signature if you need it.
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
edit: Just to be sure I did try the one in your sig. It installs no problem, but ROM manager crashes and the screen distorts right before home screen loads. Once it's loaded it seems OK. Might be a boot loader issue.. but not sure. Once in download moad Odin3 doesn't recognize the device. The one click app does, but not Odin3 v. 1.3 to flash rooted kernel. It just doesn't recognize the device for some reason, but java installer still recognizes it.
I cannot get into CWM as it just crashes. Doesn't reinstall correctly, gets stuck on running privileged commands. Cannot boot into it since it's a privileged command as well. Only version of odin that recognizes my phone is the one in your link and it's a JAR Exe lol. This is the strange part.. no modem. Just got the wifi to work to at least make it to the market place. Still no modem, broadband is 'unknown'.
When I go back into download mode to flash a kernel in Odin v1.3 it doesn't recognize my device. ADB does not recognize my device. The java installer for the stock rom I just used in your sig still recognizes the device. Only the java installer recognizes it. Tried using Heimdall 1.1 for the kernel flash and it also does not recognize my phone.
I do have an HP TouchPad running CM7 alpha 2.1 as well. Not sure if this will help, unless someone can think of something clever by having an extra Android device. Just throwing it out there.
sunfirex said:
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
Click to expand...
Click to collapse
As far as I know, that should have CWM installed in the file. Depending on which bootloaders you have, either holding V+ and Power from a powered-off state, or V+/V-/Power should put you straight into CWM.
If that isn't working for you, but you're at least on a Gingerbread rom, try this. It appears Heimdall is ok with your phone, and this kernel I'm certain has CWM baked in. You might bootloop, but you should definitely get to CWM from this.
That's exactly what it was. That version of Heimdall in the link you provided solved my issue.
Thank you so much!
Glad to hear it.
Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh
Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans
NS4G
Will boot to fastboot and recovery
CWMR Touch 6.0.1.0
Situation:
My device started bootlooping after about a week of random restarts and freezes. I had just flashed BlackBean and now this, so I decided I was just going to flash a new ROM/Kernel combo. I remembered someone saying I should format /system to install the specific ROM, but I'm fairly sure I formatted /boot along with it, like an idiot. FYI - Fast Charge and a build.prop tweak to set permissions on boot was enabled when this happened. So then I try and flash a new ROM/Kernel combo to fix my bootloop and it wouldn't read the sdcard afterwards. Now it boots straight to fastboot everytime. Toolkit seems to be able to do some things via USB control like reboot the bootloader, but it does not detect an ADB device when I run the driver check or try to restore my CWM backup. I ran the stock+unroot option in Toolkit (was going to send it in thinking the sdcard thing was hardware at first) and it seemed to have went through the whole process correctly... Until the end when it did not reboot automatically like it should have. After doing this, I now get "STANDARD_SET_CONFIGURATION" on the phone when I insert the USB cord while in fastboot. It did not do this before, whether it is the new cord or the flash I do not know. My old cord WAS having problems with data though.
Problem:
I now have no USB debug or SDcard functionality. I assume because of missing files on /boot. I can mount nothing (except cache, but the PC doesn't recognize) without getting a "can't mount" error. This puts a serious dent in my novice ability to fix it. Anything in Toolkit that runs via ADB commands doesn't seem to work properly because it says the device is not in debug mode. PDAnet USB Drivers seemed to install without a hitch and device is recognized on my PC.
Errors:
When trying to mount ANYTHING except the cache while in CWM, I only get: "E:/ Can't mount /sdcard/".
If I try to mount USB storage I get: "E:/ Unable to write to ums lunfile (No such file or directory)Error mounting /sdcard!"
If I try to run any one click methods that use ADB I get: "Daemon not running* No ADB device detected. Make sure you have debugging enabled on your phone"
The log in CWM recovery always shows: "I: Set boot command "" failed to open /sys/class/android_usb/android0/state: No such file or directory" over and over (as many times as I tried to mount something while in recovery for that session)
Questions:
Do you think USB Fast Charge or having the build.prop tweaks enabled could have done something to USB debug? Is there a way to at least just fix the USB Debug problem? Am I correct in assuming that wiping the /system along with the /boot folder is what caused me to not be able to mount the /sdcard to flash another ROM? Is there a way to push the files I need onto the device to restore sdcard function and flash another zip?
Also, what fastboot do I need to be in to do the StockROM+Unroot method in the Toolkit? I have two. Only hold Vol Up/Power takes me to "FASTBOOT". Holding both Volumes+Power puts me into "FASTBOOT - NO BOOT OR RECOVERY IMG"
What is the difference?
I only ask because the Toolkit wants me to hold both volumes and up to get into bootloader mode, but they describe a big green "Start" with an android lying on it's back, mine does not look like that. It simply looks like regular fastboot, but says "FASTBOOT - NO BOOT OR RECOVERY IMG" instead.
It seems you messed with the ROM zip with some tool. Sorry could read your lengthy post completely.
I just want to know one thing clearly, what is the problem basically? where are you stuck?
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
DizturbedOne said:
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
Click to expand...
Click to collapse
Your storage memory is completely inaccessible?
Yes, no way to access it via CWM. ADB stuff does not work either. It seems Fastboot stuff DOES. I would like to find a boot.img and system.img to flash via Toolkit (I believe toolkit uses fastboot or odin for these) to see if that would work for me. Any ideas?
It seems like the easy nature of unlocking, rooting, and customizing this phone leads to less of these kind of discussions, I can usually find many files and discussions pertaining to this for HTC phones, but never for this phone.
My bootloader version is KE1, but my baseband version is LF2, makes no sense to me.
The KE1 bootloader was when I was on ICS, but the LF2 baseband was from Jellybean... wth?
Do you think the time I flashed "stock+unroot" on the toolkit that it only partially took? (I did try to back it up to ICS because the Jellybean download didn't work). It seemed as if it flashed everything via fastboot, but never restarted at the end and still won't boot when done.
same problem kinda
i am having the same problem as this with my nexus. mine started after i downloaded Jellybean.it worked fine for about 1 month. i had changed nothing but when i would change my battery or restart my phone it would get stuck at the google screen every now and then, then it started more often. i could normally pull the battery and restart it and it would work after a couple of times doing that. but now this last time i tried that the phone wouldnt go past google screen at all. i can access my clockwork mods recovery but when i try to install zip from sd i get the error cant load sd i have tried everything i know and cant get nothing to work. please help. i miss my nexus this prevail is too slow and small...
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
polobunny said:
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
Click to expand...
Click to collapse
@ polobunny - There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and manually reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such. I've tried it with PDAnet drivers and the Samsung drivers and have followed every driver install guide on the web... Any other suggestions on how to do this properly? I was even thinking of installing a Google SDK just to see if the drivers would work better...
@ Bamamac82 - Yes, that is pretty much the exact same problem, with the exception of the fact that you didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up. Not having a working USB cord at the time botched me, because I couldn't get my drivers reliably installed before anything happened, I was using AirDroid because my OEM cable wasn't working with data reliably.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
DizturbedOne said:
There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such.
And Bamamac82 has the exact same problem, with the exception of the fact that he didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
Click to expand...
Click to collapse
When you're in fastboot mode on your phone, on your windows PC point the unknown device or the device with an exclamation/question mark to the path where the .inf for the drivers are located. If it still doesn't detect it, you can always try and force it to install a certain device (adb debug bridge or something of the sort).
Once that is done as I said you won't have any problem fastboot'ing to your phone and doing the other steps. Windows drivers and especially the adb drivers can be finnicky.
Your SDcard problem has nothing to do with the fact your formatted boot partition though, those are not linked.
Edit: Oh and I know there is some people, namely with NS4Gs, that had issues with the drivers. I believe for some reason there's some missing IDs in the inf making it impossible to install automatically. Forcing it should work though.
Polobunny thank you so much for your help so far. My device has been softbricked for a week and I'm using a HTC Hero for now! It's atrocious. I'm going to try as you said when I get home tonight and will update if fastboot allows me to flash after that.
Any idea where I can get all the .img's I need? I can only find the complete .tgz for IMM76D (which is fine for now just want it back to working state) and don't know how to extract .img's from it. Can't even find the complete .tgz for JRO03R though, the link is always down. At this point, all I want is a factory img to start from so I can upgrade to JRO03R, root it, and then make a fresh NAND backup from there.
If I were you, I would download Odin, a factory image from Google (just search nexus s factory image), the SDK tools (Google it) and would "reset" the phone.
You will easily find a guide for Odin. Then you'll just have to follow it and your nexus should be fine (but it will be factory reseted and you will have lost all your data )
Sent from my Nexus S using xda premium
Sorry guys, have been putting late hours in at work and haven't had much time until this weekend.
@BenHeng, that's what I am about to look into tonight. I didn't want to learn an entirely new aspect to restore this, I have been limited on free time and am starting to think it will be less hassle than dealing with this.
Only caveat to that, is that I definitely would like to know what happened to cause the SDCARD problem, because that was the main problem that got to me here, would like to prevent that from happening again.
ADB
Make sure ADB debuging is checked under Developer options
localpagefirst said:
Make sure ADB debuging is checked under Developer options
Click to expand...
Click to collapse
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Hi, I don't understand why you want to use ODIN, fastboot commands still don't work after you installed correctly your driver?
Anyway you can find all (new and old) originals google image here:
http://www.randomphantasmagoria.com/firmware/nexus-s/
Listen mate, the best way would be to flash the factory image via fastboot in bootloader mode. Follow this simple step to step guide.
If you have any issues. post them there on the blog post itself :good:
DizturbedOne said:
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Click to expand...
Click to collapse
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
polobunny said:
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
Click to expand...
Click to collapse
I get nothing when I do that. It says "List of devices attached" and a blank line underneath. When I plug the USB in during fastboot I get "STANDARD_SET_CONFIGURATION" at the bottom, which I never get until I install the drivers.
It seems as if the computer must recognize the device in debug mode in some way to properly install the drivers.
Why is my sdcard partition unable to be written to? This never would have been a problem as I always keep a couple backup ROM's on the phone. Either way, it seems as if all of this is for nothing if the phone will not allow me to read/write to the memory in the device.
Alright, I hate being that guy. You know, the one who posts the same question as 50 other people because he is too lazy to search. But in my defense, I have spent the last three days pouring over thread after thread and still can't find the answer, so please be patient and gimme a break!
So, I'm stuck in CWM 5.8.3.4 loop after flashing Katkiss and not knowing I couldn't use the "boot to recovery" option. I've got no access to my micro SD card and my x64 Win 7 won't recognize the TF101 so I can't put my own recover zip on. Cold boot goes to the screen that lets me boot Android or Wipe. If I pick Android, it hangs (for hours). I've wiped everything and reinstalled Katkiss, Revolver, Revolution, but I have the same problems.
Is there a thread that starts from the BEGINNING of the fix and sees it through? I've found dozens of threads that say, "Just input (code), flash, and you're done!", but I guess I'm not that far along. I've bricked Dinc/Dinc2, Razrs, etc., but never had trouble fixing them like this TF101.
I've got ADB, JDK, Ubuntu, etc. since I've tried numerous times. Also, I've had no luck with the one-touch fixes. I know I'm missing something easy, I just can't figure it out.
Thank you.
Incidentally, I've tried ***http://www.transformerforums.com/fo...ry-bootloop-fix-tested-my-c10-windows.html*** , but the SDK files come in a zip, not exe and none of the files execute/install in such a way that will let me input commands. I know I'm missing something because a soft brick isn't that big of a deal.
Huh. I don't know what happened, but it involved me cleaning the screen, accidentally pushing buttons, and rebooting, and now it works. No clue, but as long as I never shut it off again, I'm set!
You're gonna need to get the PC to recognise it to fix it I'd say
Easiest way would be using Easyflasher to get TWRP recovery installed, it sounds like you have stock recovery installed at the minute
http://forum.xda-developers.com/showthread.php?t=1688012
Few people have needed new cables to get the PC to recognise the TF again, might just be needing the correct drivers though which are also linked on that page
Basically install the drivers, put the TF into APX mode,
(Vol Up & Power from powered off state while plugged into the PC)
Then run Easyflasher as admin and choose to flash TWRP (CWM is probably the reason for the bootloop, it doesn't play nice with JB ROMs)
Once you have TWRP installed, flash whichever ROM you want from new recovery and you should be good to go
I appreciate the suggestion, but that isn't doing it. I have the tab booted up and recognized by Windows, but when I try to update to a different CWM or TWRP, nothing happens. I can reboot into CWM 5.8.3.4 all day, but it won't say anything about any different recoveries I've tried to install, though the recoveries appear to be installing correctly according to the dialog given on the tablet.
I've also tried running NVflash, but nothing happens (apx drivers installed). The BAT file briefly says USB not recognized and closes.
Further, I've tried Easyflasher / one click root+recovery and I just get messages saying "ADB server out of date. Killing." The tab still reboots, but upon rebooting, it gets stuck in CWM 5.8.3.4 unless I force cold boot.
I guess the best way to describe this is to say that no matter what I do with the tab or different recoveries, I can't get rid of CWM 5.8.3.4 and no matter what I do, it default boots into CWM.
It default boots into CWM.... I think that is the key here
I remember something about that from a while ago, having to hold Power & Volume Down to boot normally, as if the OS and Recovery partitions were reversed
Unfortunately I can't remember the solution atm, but if you head over to transformerforums.com or give frederuco a PM from here or over there, Im pretty sure I remember him having a solution some time back
I shot him a message. Thanks for the suggestion.
I swear all I did was root, install Katkiss, and reboot into recovery. Is this a common problem to have THIS much trouble with such a simple process? I know now that booting into recovery can cause a loop, but this seems like way too much.
It's having CWM as your recovery when you flash a JB ROM that causes the problems
CWM & JB = Problems
TWRP is the recovery to use once you get out of this mess, good luck