Database Info

[Oh Crap] XOOM is dead and it won't boot up!

I don't have a history of random reboots other than the once in a blue reboot because the browser gets stuck. I was using my Xoom last night before going to bed checking out a couple of website. I laid it down and went to bed and this morning I just put it in my bag and left to work.
The Xoom doesn't get past the Motorola logo and then the screen dims a black-blueish tint as if it were on but not on. I booted into recovery and tried to do a nandroid restore to a prior date. The restore finishes but when I reboot the Xoom still has the same issue.
The last thing I downloaded on the Xoom was that new market but I didn't like it so I uninstalled it. Right now the Xoom is plugged in charging. I don't believe it's the screen because I'm able to navigate through recovery without it shutting off. I'm stuck. What could it be?
By the way I pressed Vol Up + Power to force reboot and it's not working. Still a blackish blue tint screen.

Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?

fleury14 said:
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
Click to expand...
Click to collapse
Not for nothing but you're thread jacking.

Not trying to. Just didn't want to litter with a whole new thread.
Sent from my Nexus S 4G using Tapatalk

It's cool but my Xoom is still dead
I'm going to try and do the update.zip for 3.2 after class and see if it boots up with that. This sucks.
Sent from my PC36100 using XDA App

Update:
I downloaded the 3.2 update that's in the development section and installed it. It still won't boot past the Motorola logo. It goes to the Motorola logo and then the screen turns blackish blue. If I hit the power the screen goes black. It was working g fine yesterday and I'm out of ideas.
Sent from my PC36100 using XDA App

Try going back to the beginning. Flash stock 3.0 and lock. If your xoom boots then you're back in the game. If not, at least its stock to send in for warranty repair.
Sent from my HD2

That will have to wait until tomorrow. What could have caused it?
Sent from my PC36100 using XDA App

Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2

jase33 said:
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
Click to expand...
Click to collapse
I hope it's not an issue with my screen. I just find it weird that the screen shows that weird tint and if I hit the power button it goes black. It's as if the tablet is on but I'm not seeing an image on the screen. When I did a nandroid restore it got past the Motorola logo and went into the next phase (boot animation). It froze on the boot animation within 1 second of entering it. I left it alone for 30 minutes and it didn't do anything.
I don't want to send it back to Moto because G-D only knows when I'll get it back. Does anyone have experience with their repair ETA's? I'm nervous on sending it in because I read a thread where some Xoom owner got accused of having water damage. I don't want to them use that as an excuse so they won't fix it.

I have no personal experience. But there were a couple of posts in the General section (April, May time frame) from users who sent there Xoom to Moto for repair. All reported outstanding service. Call Motorola customer service and they will send you a shipping box overnight. Turn around in most cases was only 2 days. All had their devices back in under a week (departure to return). Good luck. Won't hurt to call Moto and talk to them about it.

Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.

gqstatus0685 said:
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
Click to expand...
Click to collapse
You didn't use an app like screen off and lock did you? I had a problem with that app after the update...at one point my screen went completely black, I could see my soft keys and could access settings but that was it. Had to boot to recovery and wipe all over again.
It's a long shot but sometimes apps that behaved before an update can act whacky.

No nothing like that. I remember I was watching some YouTube videos and ended my night. The last thing I downloaded was the new market but it looked hideous so I removed it. I'm trying different things and I can't get it to work.
Sent from my PC36100 using XDA App

I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App

Oxirane said:
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.

Wipe, wipe, repeat!
This most certainly is a software issue. The fact alone that the device is showing the boot logo proves that the screen is functional. Sounds like a boot img problem.
I have had similar issues on a few occasions with my Evo, doing a full wipe and restore has always done the trick as has been posted above.
Good luck Gq.

dhemke17 said:
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the advice. I was too busy yesterday (Full Time Work and Student) to fix it. I will try today since I don't have class. I really want to see what caused the problem so I will try that command in CMD and will post the output on these forums. Hopefully a dev can use it in the future to prevent this from happening to someone else.
I miss my Xoom.
I'm assuming I would CD to the directory and then run that command, correct?

Ok I guys I included the attachment so maybe someone can tell me what's wrong with my Xoom.
When I ran that command in command prompt a debug window popped up. Let me know if the attachment makes sense.
Uncaught Exception most likely has to do with software as I remember fixing Blackberry's that always had those issues but I could be wrong.
Update:
I followed this thread
Re-Lock & Unroot
http://forum.xda-developers.com/showthread.php?t=1084537
and everything successfully pushed. I ended up getting an error messaage in fastboot (Failed image SOS 0x0002) so I decided to unlock the device by running fastboot oem unlock command. It completed successfully and got rid of the error message in fastboot. When I hit reboot it got past the Motorola logo and froze at that honeycomb animation (right in the beginning. I turned it off and turned it on again and now it won't go past the Motorola screen.
I went on a chat with Motorola and they will be sending me an email so I can send my Xoom for repair. I'm going to lock it again and send it back. I'm giving up unless anyone recommeds something I can try.

[Q] Phone won't boot up / E:Can't mount /sdcard

This is pretty bizarre.
I have been running CM7 nightly 180 with Trinity for about a month now. I woke up to my phone vibrating a bit - my K9 mail app got reset so it was redownloading old emails. I tried to open my Twitter app and that was reset as well. After that a bunch of force close dialogues popped up, so I rebooted my phone thinking it glitched up. Once I did that, it would show the Google logo, then the first Trinity logo, and just hang there. It did not get to the Trinity animation.
I can get into recovery, and from there I tried to restore to a backup, and it says E:Can't mount /sdcard. Do I have to Odin to fix this or is there another option? I remember the same error happening to my Vibrant, and that was the only solution.
Does anyone have any explanation as to why this happened? I didn't do anything unusual with the phone or install anything new/different at all. I plugged it in, went to bed, and woke up to this.

Strange :S. Did you try to mount SD card from recovery while you have your phone conected to PC? I hope it's not faulty storage memory problem...
Sent from my Nexus S using XDA App

I just tried, CWM says "Error mounting /sdcard!" This all happened with my Vibrant. It said all of the same things and I had to use Odin, and it worked, but my /sdcard was completely wiped. It just doesn't make sense since this time I didn't do anything differently; I think on my Vibrant I had installed a new ROM and then it messed up. This time it's like a phantom f**k up.

That doesn't sound so good . Seen few people with same problem, and most of them sent their devices for repairs. It was some hardware error where Odin couldn't help.
Can't be sure if that is the same problem, but it easily could be. I'm not expert, I'm just sharing what I've seen before. Let's hope I'm wrong about this one...

Ugh I really hope not. I bought this phone on eBay in August, I still owe money to Bill Me Later -_-

Off to Samsung it goes
Sent from my Nexus S 4G using xda premium

Get into recovery mode by turning phone off then hold volume up button then press the power button. It should go to recovery. In recovery go to advanced the mount SD card and mount data. Then try doing a restore
Sent from my Nexus S 4G using xda premium

bille3939 said:
Get into recovery mode by turning phone off then hold volume up button then press the power button. It should go to recovery. In recovery go to advanced the mount SD card and mount data. Then try doing a restore
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Try to read again what OP wrote in his/her posts...

Have you tried flashing another recovery? Or even, lock and unlock the bootloader? It should format your sd card and that might fix it.
Sent from my Google Nexus S using XDA App

I recall having a similar problem in recovery, I just can't remember what I did to fix it!
Sent from my Google Nexus S using XDA App

You could also try this.
http://forum.xda-developers.com/showpost.php?p=18316565&postcount=29

Try use other version of recovery. It is a bug from I dunno which version of recovery.
Accidentally sent from my Google Nexus S using XDA Premium

I'm on version 5.0.0.0 of CWM, is that the buggy one by chance?
I can't get the USB driver to install here at work (Windows), I am going to have to wait til I get home to flash an updated version of CWM from my Mac.

Flashing a new recovery didn't help. My /sdcard still says error for everything. I wish Odin worked on Macs.

Just used someone's PC to use Odin and my phone hangs at "verify image (ipbl)... success." I think I'm going to throw in the towel and cut my losses at this point. I don't really have any other options.

Amazing but working solution for the same problem!
There is a post in Google mobile support were many people had the same problem and one guy exposes the solution, because I am new user, I can't link outside xda so I tell you the fix:
It's said to be a common hardware problem in this device, for me it just works when I power on after heating up with a hot air gun (other people say a hair dryer is enough)
I hope that you find this information useful

any news?? i have the same problem :'(

Heating Works
Thanks I have the same problem. I was not able to mount any of the system or sdcard partitions. Heated the phone with a heat gun and it starts up.
palpablo said:
There is a post in Google mobile support were many people had the same problem and one guy exposes the solution, because I am new user, I can't link outside xda so I tell you the fix:
It's said to be a common hardware problem in this device, for me it just works when I power on after heating up with a hot air gun (other people say a hair dryer is enough)
I hope that you find this information useful
Click to expand...
Click to collapse

Stuck in Reboot

So I have a major problem. And I'm probably a moron. This is the first time I've ever gone to flash to a custom rom on this phone.EDIT: I have flashed custom roms multiple times on past phones but never on android. I unlocked (EDIT: ROOTED) it several months ago using ACE kit and worked perfectly. I finally decided I was ready to go to a custom Rom. I downloaded Rom Manager by clockwork mod and paid for the premium version. My phone isn't connecting to my laptop and isn't able to synce. I think it may be my USB cord, but that's what caused me to flash through Rom Manager. I downloaded the ClearDroid Mod, Backed up my phone using Titanium Backup, then went back into Rom Manager and clicked begin flash to new rom or whatever it said. It went through everything and said it was a success. PHone restarts into white HTC screen. Then changes to Black HTC screen with quietly brilliant underneath. It sits there for a few minutes then quietly brilliant "rewrites" itself underneath. I have no clue what to do and obviously am way over my head. I hope I can get help.
Thank you in advance.

This is just a boot loop. One of the reason why I don't use rom manager. Any who. Pull the battery. Put it back in and boot phone up with volume down and power pressed simultaneously. You should see a white screen. This is the boat loader. Scroll down to recovery. In recovery wipe data/cache/dalvik. Then select install from SD. And choose your rom
Sent from my Inspire 4G using XDA

Did as you said. Didn't work. Still the same problem. I wiped everything, which was 2 options, wipe cache, and wipe user data. I think selected install from SD, navigated into the clockword folder in my card until I found the Cleardroid Rom. It installed again (succefully according to the screen) and I went and selected reboot. And back to same problem. I probably should have backed up my current rom shouldn't I?

Live and learn. The first boot does take the longest, give it a few minutes. But if it doesn't boot then it could have been. Bad download. What you can do is download the from again or a differentrom on your PC. Then in clockwork mount the SD card and transfer it over or you can use an adapter which ever is easier
Sent from my Inspire 4G using XDA

Thanks! I was actually in the process of installing another ROM when you responded. I remember reading other threads and put a few pieces together. Seems as though it worked. Thanks for your help though.
One last question. Can I just install ROMs through that method everytime? As in start in bootloader, enter recovery, and install that way?

Yup, that's how I do it. I prefer to manually wipe and install roms. Many roms come with an advance power menu so its even easier as they have an option to boot straight into recovery.
Sent from my Inspire 4G using XDA

Odd behavior when upgrading to cm10.0.0 on HTC one s

I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app

CounterSolar said:
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Getting into fast boot is tricky...hold down arrow and push power, then release vol after boot.
Are you flashing boot.img properly in fastboot?

OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app

CounterSolar said:
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The One S isn't offically supported by CWM. It sounds like you need to try and flash the boot.img in fastboot.

Try TWRP...it will be better
Sent whit HTC ONE S

That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app

Yeah dc211 was right. I'm using hboot 1.14, had to go and flash boot.img in fastboot. Install went smoothly after that. Thanks for the input y'all.
Sent from my Nexus 7 using xda app-developers app

boot loop
CounterSolar said:
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.

I was able to flash 10.0.0 without removing qrngd. So far it hasn't been a problem. I read somewhere that file is some sort of random number generator, but that it isn't clear whether its even used anymore. Also, they say its more of a problem with earlier nightlies, especially with people using HBOOT < 1.14. It might be just junk DNA in the system files, or they may have patched the problem. I will keep my eye on it though, and will report back if I get any spooky behavior.
Sent from my Nexus 7 using xda app-developers app

jazz452 said:
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
Click to expand...
Click to collapse
That was fixed in the 11/09/12 nightly, so its not an issue anymore.
http://forum.xda-developers.com/showpost.php?p=33867937&postcount=2209

[Q] Droid 3 stuck in bootloop

I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.

m3schz8! said:
I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.
Click to expand...
Click to collapse
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2

bbrad said:
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.

m3schz8! said:
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.
Click to expand...
Click to collapse
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2

Droid 3 stuck in bootloop'
bbrad said:
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Yep but phone isn't picking up my data cable and how ever many issues that have come about here, I think I am SOL but gonna try an SD card hoping that it is just a bad SD card or something like that. May end up having to use part of that great tax return also, thanks for the help, I'm going samsung next, that whole fore sight wasn't there two years ago.

In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app

Droid 3 stuck in bootloop
dj2muchxx said:
In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Unfortunately you can easily tell that it is not stock ROM by bootloop

Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2

Droid 3 stuck in bootloop
bbrad said:
Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help

m3schz8! said:
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help
Click to expand...
Click to collapse
NP if you ever need anything just ask
Sent from my SCH-I500 using Tapatalk 2